Traverse Provisioning Guide - Force10...Release TR3.2.2 Force10 Networks Page 1-7 SECTION...

Force10 Networks Inc.

Traverse System Documentation

Release TR3.2.2Publication Date: April 2009

Document Number: 800-0003-TR322 Rev. A

Provisioning Guide

Copyright© 2009 Force10 Networks, Inc.

All rights reserved. Printed in the U.S.A. April 2009.

Force10 Networks ® reserves the right to change, modify, revise this publication without notice.TrademarksForce10 Networks, and 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 reserves the right to make changes to products described in this document without notice. Force10 Networks does not assume any liability that may occur due to the use or application of the product(s) described herein.

TRAVERSE PROVISIONING GUIDE

Contents

Section 1 Configuring the NetworkChapter 1Traverse Provisioning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Chapter 2Discover the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Chapter 3Traverse SNMP v1/v2c Agent and MIBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Chapter 4Configuring Network Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Chapter 5Creating DCC Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Chapter 6Configuring IP Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Section 2 Configuring TDM EquipmentChapter 1Equipment Configuration Overview (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Chapter 2Configuring SONET Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Chapter 3Configuring SDH Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Chapter 4Creating a TransAccess 200 Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43Chapter 5Creating a TraverseEdge 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47

Section 3 Creating Protection GroupsChapter 1Overview of Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Chapter 2Creating a BLSR/MS-SPRing Protection Group . . . . . . . . . . . . . . . . . . . . . . 3-7Chapter 3Creating a UPSR or SNCP Ring Protection Group. . . . . . . . . . . . . . . . . . . . 3-15Chapter 4Creating Equipment Protection Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Chapter 5Carrier Ethernet Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29Chapter 6Creating a 1+1 APS/MSP Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . 3-35Chapter 7Creating a 1+1 Path Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41Chapter 8Creating a 1+1 Optimized Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . 3-49

Release TR3.2.2 Force10 Networks Page i

Traverse Provisioning Guide,

Section 4 Creating ADM ServicesChapter 1Service Provisioning Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Chapter 2Common Procedures for Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Chapter 3Creating SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19Chapter 4Creating SDH Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41Chapter 5Creating 2-Port OC-48/STM-16 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71

Section 5 Creating Service ApplicationsChapter 1Creating 1+1 Path Protected Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Chapter 2Bridging and Rolling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Chapter 3Creating Drop-and-Continue Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Chapter 4Creating Services over Interconnected UPSR or SNCP Rings . . . . . . . . . . . 5-25Chapter 5Creating Transmux Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33Chapter 6Creating Transparent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49

Section 6 Creating DCS ApplicationsChapter 1DCS Application Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Chapter 2Creating a Multi-Shelf Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Chapter 3Creating a Single-Shelf DCS Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29Chapter 4Upgrade a Single-Shelf DCS to a Multi-Shelf DCS . . . . . . . . . . . . . . . . . . . . 6-43

Section 7 Configuring EthernetChapter 1Configuring Ethernet Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Chapter 2Configuring Ethernet Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Chapter 3Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37Chapter 4Ethernet Over SONET/SDH (EOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49Chapter 5EOS Port Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65Chapter 6Ethernet Over PDH (EOP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-71Chapter 7

Page ii Force10 Networks Release TR3.2.2


EoPDH Services and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85Chapter 8Link Capacity Adjustment Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-89Chapter 9Rapid Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-103Chapter 10Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-119Chapter 11Ethernet Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-147Chapter 12Classifying and Prioritizing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-159Chapter 13Policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-165Chapter 14RED Congestion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-175

Section 8 Changing Network ConfigurationsChapter 1Adding a Node to a Protected Ring Configuration . . . . . . . . . . . . . . . . . . . . 8-3

Section 9 AppendicesAppendix AProvisioning Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Appendix BService Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

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

Release TR3.2.2 Force10 Networks Page iii


Page iv Force10 Networks Release TR3.2.2

SECTION 1 CONFIGURING THE NETWORKSECTION 2CONFIGURING THE NETWORK

Contents

Chapter 1Traverse Provisioning Overview

Configuration Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1TransNav System Access Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Chapter 2Discover the Network

Before You Start Provisioning Your Network . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Discover the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Configure Node Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Chapter 3Traverse SNMP v1/v2c Agent and MIBs

Supported Traverse SNMP MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Configure the Traverse SNMP Agent Parameters from TransNav . . . . . . . . . 1-10Location of SNMP MIB File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Chapter 4Configuring Network Timing

Daylight Saving Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Before You Configure Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Network Timing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Guidelines to Configuring Network Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Configure Global Timing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Configure External Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Configure Line Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Configure Derived References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

Chapter 5Creating DCC Tunnels

DCC Tunnel Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24Before You Tunnel a DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25Disable Control Data Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27Tunneling a DCC Through a Traverse Network . . . . . . . . . . . . . . . . . . . . . . . 1-28

Chapter 6Configuring IP Quality of Service

Before You Configure IP Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32Configuring IP Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33

Release TR3.2.2 Force10 Networks Page v

Traverse Provisioning Guide, Section 1 Configuring the Network

Page vi Force10 Networks Release TR3.2.2

SECTION 1CONFIGURING THE NETWORK

Chapter 1Traverse Provisioning Overview

Introduction This chapter describes the following topics on provisioning a Traverse network.• Configuration Process, page 1-7• TransNav System Access Methods, page 1-8

Configuration Process

Use these steps as a guideline to creating a network.

Table 1-1 Network Configuration Process and References

Step Procedure Reference

1 TransNav Primary management server is constructed and the man-agement software is installed. The server is initialized and started.

TransNav Management System Server Guide

2 TransNav Secondary servers are constructed and the management software is installed (Optional). The servers are initialized and started.


3 Nodes are installed, connected, and commissioned.

Traverse Installation and Commissioning Guide

4 Discover the network and configure optional parameters on each node.

Traverse Provisioning Guide, Section 1— Configuring the Network, Chapter 2—“Discover the Network”

5 Optionally, configure the Traverse SNMP agent to send information to third-party equipment.

Traverse Provisioning Guide, Section 1— Configuring the Network, Chapter 3—“Traverse SNMP v1/v2c Agent and MIBs”

6 Configure timing options for the network.

Traverse Provisioning Guide, Section 1—Configuring the Network

7 Create protection groups. Traverse Provisioning Guide Section 3—Creating Pro-tection Groups

8 If necessary, modify the default parameters for the equipment.

Traverse Provisioning Guide, Section 2—Configuring Equipment

9 For ADM applications, create ADM services.

Traverse Provisioning Guide Section 4—Creating ADM Services

Release TR3.2.2 Force10 Networks Page 1-7

Traverse Provisioning Guide, Section 1: Configuring the NetworkTransNav System Access Methods

TransNav System Access Methods

This document uses the graphical user interface (GUI) to describe all procedures.The following table lists the different access methods you can use to connect to a TransNav management server or a specific Traverse node.

10 For DCS applications, create the DCS application.

Traverse Provisioning Guide, Section 6—Creating DCS Applications

11 For Ethernet applications, create Ethernet services.

Traverse Provisioning Guide, Section 7—Configuring Ethernet

Table 1-1 Network Configuration Process and References (continued)


Table 1-2 Accessing the TransNav Management System

Management System Interface Access Method

TransNav GUI • Installed client application (recommended)• Local connection to node and remote connection

(DCC bytes) to a management server• Installed application on a Citrix server

TransNav CLI • Telnet to a management server• Local connection to node and remote connection

(DCC bytes) to a management server

TransNav TL1 • Local connection to the management system and telnet to a node

Node-level GUI • Installed client application (required to view GUI)• Local connection to specific node

Node CLI • Local connection to the node• Local connection to the node and remote login to a

different node in the domain

Node TL1 • Telnet to the management system and connect to a node

• Local connection to the node

Page 1-8 Force10 Networks Release TR3.2.2


Chapter 2Discover the Network

Introduction This chapter includes the following topics:• Before You Start Provisioning Your Network, page 1-9• Discover the Network, page 1-10• Configure Node Parameters, page 1-11

Before You Start Provisioning Your Network

Complete the following tasks before you start provisioning your network.

Table 1-3 Before Provisioning Your Network Requirements

Requirement Reference

Hardware

You have the correct hardware according to your network plan.

Traverse Product Overview Guide, Section 5—Planning and Engineering, Chapter 4—“Protected Network Topologies,” page 5-33

The hardware is installed and commissioned according to your network plan.

Traverse Installation and Commissioning Guide, Section 1—Installation Overview, Chapter 1—“Installation and Commissioning Overview,” page 1-1

Software

The TransNav Primary management server is constructed and the management software is installed. The server is initialized and started.


The TransNav Secondary server(s) is constructed and the management software is installed. The server(s) is/are initialized and started.


Nodes are installed, commissioned, and con-nected.

Traverse Installation and Commissioning Guide, Section 11—Node Start-up and Commissioning Procedures, Chapter 1—“Node Start-up and Commissioning,” page 11-1

You are logged into the graphical user interface. TransNav Management System GUI Guide, Chapter 3—“Starting the Graphical User Inter-face,” page 2-17


Traverse Provisioning Guide, Section 1: Configuring the NetworkDiscover the Network

Wherever possible, a table listing requirements and guidelines precedes each procedure. See each topic for specific requirements to the task on which you are working.

Discover the Network

Use this procedure to make the nodes in the network appear on the main GUI screen.

Table 1-4 Discover the Network

Step Procedure

1 From the Admin menu, select Discovery to display the Discovery Sources View dialog box.

Figure 1-1 Discovery Sources View Dialog Box

2 For each gateway node, enter the node-ip address of the node in the Host Name box.

Click Add.

3 Click Done to return to the main screen. The nodes appear in the upper left corner of the window.

4 Click and drag nodes to an area on the map to best represent your network.

5 From the File menu, select Save User Preferences to save the placement of the nodes.

6 The Discover the Network procedure is complete.

Continue to the next procedure Configure Node Parameters.

2

3 4


Chapter 2 Discover the NetworkConfigure Node Parameters

Configure Node Parameters

After a node is commissioned, configure the following type of information at each node: node location description, alarm profiles, and NTP server IP addresses. Alarm profiles are established to customize service-affecting and non-service-affecting alarm severities for the node.

Use this procedure to configure parameters for each node.

Table 1-5 Configure Node Parameters

Step Procedure

1 Double-click a node to display the Shelf View.

2 Click the Config tab to display the Node Configuration screen.

Figure 1-2 Node Configuration Screen

3 In the Location field, type a descriptive location for the node. For example: Node1 Central Office.

Use alphanumeric characters and spaces only. Do not use punctuation or any other special characters in the Location field.

4 Alarm Profile: Select an Alarm Profile from the list if additional profiles have been created. The default is default.

Alarm Profiles can be viewed or created from the Admin menu using the Alarm Profiles dialog box.


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfigure Node Parameters

5 Values are displayed in the following fields. Some of these values may have been set during node commissioning using the CLI:• Node ID• Node IP• BP DCN IP• BP DCN Mask• BP DCN Gateway• GCM AIP and GCM B IP• GCM A Mask and GCM B Mask• GCM A Gateway and GCM B Gateway• EMS IP• EMSMask• EMS Gateway

For more information, refer to:• Traverse Installation and Commissioning Guide, Section 11—Node

Start-up and Commissioning Procedures, Chapter 1—“Node Start-up and Commissioning,” page 11-1.

6 You can enter values for the NTP IP 1 and NTP IP 2 fields if they were not set during the initial start-up procedures. The Network Time Protocol (NTP) server IP address is used by the node to derive the Time of Day that is used for performance monitoring, alarm, and event logging.

NTP IP 1Type: the IP address of the primary NTP server. (For example: aaa.bbb.ccc.ddd)

NTP IP 2Type: the IP address of the secondary NTP server. (For example: aaa.bbb.ccc.ddd)

Force10 recommends using the primary TransNav server as the primary NTP source if you do not already have a NTP source defined. Refer to the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 1—“Creating the Management Servers” for information on how to activate the NTP server on the management server.

7 External Alarm 1–16: These fields display a default value of UNKWN. You can select one of the External Alarm input alarm types (based on the environmental alarms input cabling completed during node installation).

Table 1-5 Configure Node Parameters (continued)

Step Procedure


Chapter 2 Discover the NetworkConfigure Node Parameters

8 Proxy ARP: Enable this parameter if this node is to be used as the proxy server for the IP subnet.

See the TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” Proxy ARP, page 2-16 for a complete description of Proxy ARP.

9 Click Apply.

10 Repeat Steps 1 through 9 for each node.

11 The Configure Node Parameters procedure is complete.

Table 1-5 Configure Node Parameters (continued)

Step Procedure


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfigure Node Parameters



Chapter 3Traverse SNMP v1/v2c Agent and MIBs

Introduction Force10 supports an SNMP agent directly on the Traverse system and provides limited standard MIB support for Ethernet card ports.

Note: There is no relationship between the TransNav server and Traverse system SNMP agents. The configuration of the Traverse system SNMP agent (community strings, trap destinations) is not coordinated in any way.

Important: The Traverse SNMP agent access is available on a physical node; Preprovisioned support for the SNMP agent is unavailable.

This chapter includes information about the subnetwork management protocol (SNMP) on a Traverse network element:• Supported Traverse SNMP MIBs, page 1-15• Configure the Traverse SNMP Agent Parameters from TransNav, page 1-16• Location of SNMP MIB File, page 1-17

Supported Traverse SNMP MIBs

The Traverse SNMP northbound interface implements the SNMP v1 and SNMP v2c protocols and maintains a Force10-proprietary MIB. SNMP v2c uses the same security model as SNMP v1, and adds two main features: the ability to GET large amounts of management data in a single request (GETBULK operation) and support for 64-bit counters.

The Traverse SNMP agent supports these MIBs:

Note: The following list does not reflect the set of MIBs supported by the TransNav SNMP agent. The Traverse MIB set supports the direct management of Traverse nodes by third-party applications, such as HP OpenView®.• RFC 1213: System group of MIB-II• RFC 2737: Physical Entity table of Entity MIB, Version 2• RFC 2863: The Interfaces Group MIB used for physical Ethernet interfaces only,

the Interfaces and Extension Interfaces tables• Force10 enterprise (proprietary) SNMP MIB:

– EMS Alert table– Set of traps

All counters are copies of Traverse PM 24-hour counters and are consistent with the way the TransNav MIBs support counters.


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfigure the Traverse SNMP Agent Parameters from TransNav

Configure the Traverse SNMP Agent Parameters from TransNav

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.

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

Figure 1-3 Admin Menu—SNMP Configuration

The Node SNMP Configuration screen displays:

Figure 1-4 Node SNMP Configuration Screen

The Node SNMP Configuration screen allows you to view and change the following Traverse node SNMP configuration information:

Node ID1: Displays the user-defined node name entered during node commissioning.

Node IP1: Displays the node IP address entered during node commissioning.

1 Set through the CLI during node commissioning.


Chapter 3 Traverse SNMP v1/v2c Agent and MIBsConfigure the Traverse SNMP Agent Parameters from TransNav

Read Community: An alphanumeric character string that provides an SNMP management station with read-only access to the Traverse SNMP agent. Public is the default string.

Note: For each of the alphanumeric character string parameters, there is a corresponding Confirm parameter to check for matching string entry.

Write Community: An alphanumeric character string that provides an SNMP management station with read and write access to the Traverse SNMP agent. Public is the default string.

Trap Destination [1 through 4]: Enter the unique IP address assigned by a network administrator of the SNMP management station to receive management data. There are up to four possible trap destinations.

Trap Destination [1 through 4] Community: An alphanumeric character string (corresponding to the Read or Write Community string) that provides the Trap Destination Community with specific access rights to the Traverse SNMP agent. Public is the default string.

Trap Destination [1 through 4] Port Number: The SNMP management station port that receives management data from the Traverse SNMP agent. The default is 162.

Command buttons are as follows:

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

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

Location of SNMP MIB File. The Force10 enterprise (proprietary) SNMP MIB file (filename=ems.mib) is located in the same directory where you installed the server application.


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfigure the Traverse SNMP Agent Parameters from TransNav




Chapter 4Configuring Network Timing

Introduction Configure the timing source for each node in a server domain. For each node, you can configure either external timing or line timing from OC, EC3, or STM interfaces.

Typically, one node in the central office receives redundant timing signals from an external source. This node becomes the primary timing source for the network. The other nodes receive the timing reference from optical interfaces. The primary reference is the shortest route to the primary timing source.

Synchronized primary and secondary timing inputs from the external timing source are connected at the main backplane and bridged to the shelf’s system control cards.

Use the following procedures to configure timing options:• Before You Configure Timing, page 1-16• Network Timing Example, page 1-17• Configure Global Timing Options, page 1-18• Configure External Timing, page 1-19• Configure Line Timing, page 1-22• Configure Derived References, page 1-23

Daylight Saving Time. As part of a United States federal energy conservation effort for 2007, Daylight Saving Time (DST) starts three weeks earlier and ends one week later than in previous years. Certain telecommunications products contain the ability to synchronize to a network clock or automatically change their time stamp to reflect time changes. Each device may handle the recent change in DST differently.

All dates displayed in the TransNav management system CLI for alarms, upgrade times, events, and performance monitoring (PM) include the new DST as part of TransNav Release TN3.1.x and Traverse Release TR2.1.x. The TraverseEdge 100 system CLI will include the new DST as part of Release TE3.2.

Traverse Provisioning Guide, Section 1: Configuring the NetworkBefore You Configure Timing

Before You Configure Timing

Review this information before you configure network timing.

Table 1-6 Timing Requirements


Read the information in the Traverse Provisioning Guide, Chapter 1—“Traverse Provisioning Overview,” page 1-7.

Ensure the requirements listed in Before You Start Provisioning Your Network, page 1-9 are met.

Software

Node is commissioned. Traverse Installation and Commissioning Guide, Section 1—Configuring the Network, Chapter 2—“Dis-cover the Network,” page 1-9

Network is discovered. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 2—“Discover the Network,” page 1-9


Chapter 4 Configuring Network TimingNetwork Timing Example

Network Timing Example

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

Figure 1-5 Network Timing

At any node, if all timing references fail, the node will maintain timing from the internal Stratum 3 oscillator.

Node 2Node 4

Node 1

EXT-A EXT-B

Node 3

Ring ConfigurationWest port = Slot 15East port = Slot 16

Timing Mode: ExternalPriority 1 Ref: EXT-APriority 2 Ref: EXT-B

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

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

Timing Mode: LineReference 1: Slot 15 or Slot 16Reference 2: Slot 15 or Slot 16


Traverse Provisioning Guide, Section 1: Configuring the NetworkGuidelines to Configuring Network Timing

Guidelines to Configuring Network Timing

Use the following guidelines to configure timing in a Traverse network.• If an external clock is present, always configure external timing for the node. • Configure line timing in such a way that the primary reference is the shortest route

to the primary timing source.• For derived timing, the Traverse can generate a timing signal to a DS1or E1

multi-frame, a T1 ESF, a 2 MHz external reference, or a 64 KHz composite clock.

For information on pinouts for each timing interface, instructions on connecting timing inputs from the central office external timing source, and instruction on connecting timing outputs from a node to the external clock, see the Traverse Installation and Commissioning Guide, Section 9—Alarm, Timing, and Management Cabling Procedures, Chapter 2—“Timing Interface Cabling,” page 9-25.

This section contains information on configurable timing parameters. For an explanation of all timing parameters, states, and messaging, see the TransNav Management System GUI Guide, Section 3—Network, Chapter 3—“Node Timing,” page 3-19.

Configure Global Timing Options

Configure the timing options at each node in the domain. Use this procedure to configure the global settings for system timing.

Table 1-7 Configure Global Timing Options

Step Procedure

1 In Shelf View, click the Timing tab to display the Main timing screen (Main subtab).

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

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

3 From Timing Mode list:• Select External to receive timing from an external reference.• Select Line to derive timing from an OC or STM interface.

2

43

5


Chapter 4 Configuring Network TimingConfigure External Timing

Configure External Timing

There are two external references for each node: EXT-A and EXT-B. For redundancy, they both have the same configuration. If both references fail, the node maintains timing from the internal Stratum 3 oscillator. Use this procedure to configure external timing interfaces for a node.

4 Select the Revertive checkbox to revert back to a primary reference source after the conditions that caused a protection switch to a secondary timing reference are corrected.

5 In the WTR Time field, set a time in minutes that the system will wait before considering the primary timing source as valid again. Enter a value between 1 and 12.

Enter 0 to disable this function.

6 By default, the Ignore SSMR (synchronization status message received) parameter is selected. That is, the node will use provisioned priorities to select the best timing reference.

Clear the checkbox to use the SSM level to prioritize timing references.

7 Click Apply to save the timing configuration settings.

8 The Configure Global Timing Options procedure is complete.

If the Timing Mode is External, continue to Configure External Timing, page 1-19.

If the Timing Mode is Line, continue to Configure Line Timing, page 1-22.

Table 1-7 Configure Global Timing Options (continued)

Step Procedure

Table 1-8 Configure External Timing

Step Procedure

1 Complete the procedure Configure Global Timing Options, page 1-18

2 In Shelf View, click the Timing tab, then click the EXT subtab.

Figure 1-7 Shelf View, Timing tab, EXT Subtab

2a

2b3


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfigure External Timing

3 From the Mode list: • Select DS1 if the external clock is a dedicated DS1 port. Go to Step 4.

• Select 2 MHz Clock. Go to Step 5.• Select 64 KHz Composite Clock. Go to Step 5.

4 Set the interface parameters for the DS1 timing references:• Line Coding: Defines the DS1 transmission coding type. Select one

of the following:– HDB3: High Density Bipolar Order 3 (default)– AMI: Alternate Mark Inversion

• Framing: Detects and generates the frame format to be used. Select one of the following:– Basic Frame: The timing interface detects and generates the Basic

frame format per ITU-T Rec G.704/2.3 and G.706/4.1.2. This format does not support the SSM.

– Multi-Frame: The timing interface detects and generates CRC-4 Multi-frame format per ITU-T Rec G.706/4.2. This format supports the SSM.

• LineBuildOut: (read only) 120 Ohm• SSM Sa Bit: Choose the SA bit that transmits the SSM message.

Select one of the following: – Bit_SA4 – Bit_SA5 – Bit_SA6 – Bit_SA7 – Bit_SA8

5 If the external clock does not support SSM and you want to operate using a received SSM, select the SSM quality for the EXT-A Assigned SSMR, and EXT-B Assigned SSMR parameters.• PRC: Primary reference clock• SSUA: Synchronization supply unit type A. Transit• SSUB: Synchronization supply unit type B. Local• SEC: SDH equipment clock• DUS: Do not use for synchronization. • Signal Fail Present• None

Table 1-8 Configure External Timing (continued)

Step Procedure


Chapter 4 Configuring Network TimingConfigure External Timing

6 For each reference, unlock the administrative state to enable the external timing. Click the Lock icon in the Adm State column next to each reference to unlock the administrative state.

Figure 1-8 Timing Tab, EXT Subtab

7 Click Apply to save the external interface settings.

8 Click the Main subtab to return to the Main timing screen.

Figure 1-9 Timing Tab, Main Subtab, Reference Priority

9 Select Priority 1 and Priority 2 external timing references.

A checkmark indicates the active reference.

10 Click Apply to save the reference list settings.

11 The Configure External Timing procedure is complete.

Table 1-8 Configure External Timing (continued)

Step Procedure

76

Indicates active reference9

8

10


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfigure Line Timing

Configure Line Timing

You can establish up to four line timing sources based on your network requirements and the number of OC, EC3, and STM interfaces in the node. You first select the references (up to four per node), then you assign a priority to each one.

The node uses the priority 1 reference unless there is a failure on that reference. If there is a failure, the node switches to the next priority. If all of the references fail, the node maintains timing from the internal stratum 3 oscillator.

You can configure line timing sources (from OC-N/STM-N and EC-3 ports only and using one port per card) and perform switch commands on the Timing tab.

Use this procedure to configure line timing from an OC, EC-3, or STM interface for a node.

Important: Beginning with Traverse Release TR2.1, each OC-N card can provide a single line timing source from any of its available ports.

Table 1-9 Configure Line Timing

Step Procedure

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

2 In the Configure Global Timing Options procedure, you selected Line Time in Timing Mode. The Line Facility and Reference List options display on the Timing screen.

Figure 1-10 Line Timing, Timing Tab, Main Subtab

3 For each line reference, select a port for the timing reference. The port needs to be enabled (in an unlocked administrative state).

Indicates active reference

4

3


Chapter 4 Configuring Network TimingConfigure Derived References

Configure Derived References

Derived timing is the process of providing a timing reference from a line interface and sending it to an external clock. Use this procedure to configure a derived timing reference on a node.

The Traverse can generate a timing signal to an DS1 or E1 multi-frame, a T1 ESF, a2 MHz external reference or a 64 KHz composite clock.

4 Select a priority for each reference. If there is a failure on the first reference, the node switches to the next reference.

A checkmark indicates the active reference.

5 Click Apply to save the settings.

6 The Configure Line Timing procedure is complete.

Table 1-9 Configure Line Timing (continued)

Step Procedure

Table 1-10 Configure Derived References

Step Procedure

1 In Shelf View, click the Timing tab to display the Main timing screen (Main subtab).

Figure 1-11 Shelf View, Timing Tab, Derived Timing Options

2 Select the External Out Enabled checkbox. Line Facility and Reference List options appear on the screen.

3 For each line reference, select an OC, EC-3, or STM port for the timing reference. The port needs to be enabled (unlocked administrative state).

2

3

56 7

8


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfigure Derived References

4 If the value in the Standard parameter is ANSI, select the SSM (synchronization status message) quality for Quality of RES. Select the level of RES by assigning a particular clock standard from the list available. The system will automatically prioritize RES to the clock standard selected from the following SSM values:• Don’t use for sync (default): Do not use for synchronization. • PRS: Primary Reference Source• Synch-Trace Unknown: The BITS clock connected to the Traverse

network may not have SSM enabled or Ignore SSMR has been selected on the Traverse.

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

Transit Clock Node level (primarily used outside North America). • Stratum 3E • Stratum 3 • SONET Minimum Clock • Stratum 4e

5 Select a priority for each reference. If there is a failure on the first reference, the node switches to the next reference.

6 Select a reference in order of priority to generate a signal to EXT-A.

7 Select a reference in order of priority to generate a signal to EXT-B.

8 Click Apply to save the derived timing preferences.

9 The Configure Derived References procedure is complete.

Table 1-10 Configure Derived References (continued)

Step Procedure



Chapter 5Creating 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.

This chapter contains the following information.• DCC Tunnel Example, page 1-16• Before You Tunnel a DCC, page 1-17• Disable Control Data Procedure, page 1-19• Tunneling a DCC Through a Traverse Network, page 1-20


Traverse Provisioning Guide, Section 1: Configuring the NetworkDCC Tunnel Example

DCC Tunnel Example

For example, a third-party vendor uses section bytes of the first STS/STM to carry OAM&P information in their network. In order to tunnel the DCC bytes through a Traverse network, create a DCC tunnel at each node in the network.

In this example, the fibers to the third-party equipment are in a protection group. In order to protect DCC tunnels in a Traverse network, create both a primary and alternate path.

Figure 1-12 Tunneling Third-Party DCC through a Traverse Network

In a Traverse network, the Control Plane uses the DCC bytes of the first, second, and third STS or STM-0 on all trunk interfaces to provide a data communication link between directly connected Traverse nodes. Therefore, the Control Data parameter on the interfaces connected to the third-party equipment must be disabled.

Create a DCC tunnel from the first STS or STM-0 on the working and protecting interfaces connected to the external equipment to the STS or STM-0 on the trunk of the first and last node. The following tables lists each DCC tunnel required in the above example.

Third-PartyEquipment

Node 1 Node 5

2 3

4

Third-PartyEquipment

Facility Protection Group Facility Protection GroupOC-48/STM-16 UPSR/SNCPDCC Tunnels = STS/STM#4

Table 1-11 SONET DCC Tunnels Hop-by-Hop

NodeSource Destination

Type Number Type Number

Node 1 OC-12 workingControl Data = Disabled

STS #1 OC-48 East trunk STS #4

OC-12 protectingControl Data = Disabled

STS #1 OC-48 West trunk STS #4

Node 2 OC-48 West trunk STS #4 OC-48 East trunk STS #4

Node 3 OC-48 West trunk STS #4 OC-48 East trunk STS #4

Node 4 OC-48 East trunk STS #4 OC-48 West trunk STS #4

Node 5 OC-48 West trunk STS #4 OC-12 workingControl Data = Disabled

STS #1

OC-48 East trunk STS #4 OC-12 protectingControl Data = Disabled

STS #1


Chapter 5 Creating DCC TunnelsBefore You Tunnel a DCC

Before You Tunnel a DCC

Review this information before you tunnel DCC bytes through a Traverse network.

Table 1-12 STM DCC Tunnels Hop-by-Hop

Node Source Destination

Type Number Type Number

Node 1 STM-4 workingControl Data = Disabled

STM-0 #1 STM-16 East trunk STM-0 #4

STM-4 protectingControl Data = Disabled

STM-0 #1 STM-16 West trunk STM-0 #4

Node 2 STM-16 West trunk STM-0 #4 STM-16 East trunk STM-0 #4

Node 3 STM-16 West trunk STM-0 #4 STM-16 East trunk STM-0 #4

Node 4 STM-16 East trunk STM-0 #4 STM-16 West trunk STM-0 #4

Node 5 STM-16 West trunk STM-0 #4 STM-4 workingControl Data = Disabled

STM-0 #1

STM-16 East trunk STM-0 #4 STM-4 protectingControl Data = Disabled

STM-0 #1

Table 1-13 DCC Tunnel Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Overview,” page 1-7.

Ensure the requirements listed in Before You Start Provisioning Your Network, page 1-9 are met.

Hardware

Create a DCC tunnel between two SONET or STM interfaces on the same node. You can use any of the following optical interfaces:• OC-3/STM-1 • OC-12/STM-4• OC-48/STM-16• OC-192/STM-64

Traverse Product Overview Guide, Section 3— Card (Module) Descriptions

Interface Types

The interfaces can be of the same or different types. For example, create a tunnel between an STS on an OC-3 interface and an STS on an OC-12 interface.

Or create a tunnel between an STM-0 on an STM-1 interface and an STM-0 on an STM-4 interface.

n/a


Traverse Provisioning Guide, Section 1: Configuring the NetworkBefore You Tunnel a DCC

Interworking

You can create a DCC tunnel between an STM interface and a SONET interface. The interfaces can be the same or different types.

n/a

Software


Timing is configured. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Timing,” page 1-15

Protection Switching

Configure the DCC tunnel hop-by-hop through a Traverse network. Create a primary path and an alternate path to create a protected DCC tunnel.

n/a

Control Data Parameter

For each interface connected to the third-party equipment, the Control Data parameter must be disabled.

See the procedure Disable the Control Data, page 1-19 below.

DCC bytes

For OC-3 interfaces, you can use the D1-D12 bytes of any STS.

For STM-1 interfaces, you can use the D1-D12 bytes of any STM-0.

If the Control Data parameter is enabled on the interface, you can use the D1-D12 bytes of these paths to tunnel DCC traffic:• OC-12: STSs 4-12 • OC-48 and OC-192: STSs 4-48• STM-4: STM-0 4-12• STM-16 and STM-67: STM-0 4-48

If the Control Data parameter is disabled on the interface, you can use the D1-D12 bytes of these paths to tunnel DCC traffic:• OC-12: STSs 1-12• OC-48 and OC-192: STSs 1-48• STM-4: STM-0 1-12• STM-16 and STM-67: STM-0 1-48

Traverse Provisioning Guide, Section 2—Configuring TDM Equipment, Chap-ter 3—“Configuring SDH Equipment,” Config-ure STM-N Port Parameters, page 2-36

Traverse Provisioning Guide, Section 2—Configuring TDM Equipment, Chap-ter 2—“Configuring SONET Equipment,” Con-figure SONET Ports, page 2-21

Table 1-13 DCC Tunnel Requirements (continued)



Chapter 5 Creating DCC TunnelsDisable Control Data Procedure

Disable Control Data Procedure

Use the following procedure to disable the Control Data parameter on the SONET interface.

Number of DCC tunnels supported: • OC-3: up to 3• OC-12: 9 if Control Data is enabled; 12 if

Control Data is disabled.• OC-48 and OC-192: 45 if Control Data is

enabled. 48 if Control Data is disabled;• STM-1: up to 3• STM-4: 9 if Control Data is enabled; 12 if

Control Data is disabled.• STM-16 and STM-64: 45 if Control Data is

enabled; 48 if Control Data is disabled.

n/a

Each STS or STM-0 number connected to the third-party interfaces must match.

n/a

Provisioning model. Hop-by-hop. Traverse Provisioning Guide, Section 4—Creating ADM Services, Chapter 1—“Service Provisioning Concepts,” Service Creation Models, page 4-6

These procedures describe how to tunnel DCC bytes through a network. See the TransNav Man-agement System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide, Section 2—Network, Chapter 4—“DCC Tun-nels,” page 2-31

Table 1-13 DCC Tunnel Requirements (continued)


Table 1-14 Disable the Control Data

Step Procedure

1 Review the information in Before You Tunnel a DCC, page 1-17 before you start this procedure.

2 Double-click the node connected to the third-party equipment to display Shelf View.

3 Click a port that is connected to third-party equipment, then click the Config tab to display the Port Configuration screen.

4 From the Control Data parameter, select Disabled.

5 Click Apply to save the changes.

6 Repeat Steps 2 through 5 for each interface connected to the third-party equipment.

7 The Disable the Control Data procedure is complete.

Continue to the next procedure, DCC Tunnel Configuration.


Traverse Provisioning Guide, Section 1: Configuring the NetworkTunneling a DCC Through a Traverse Network

Tunneling a DCC Through a Traverse Network

Use this procedure to help you tunnel a third-party section DCC bytes through a Traverse network.

Table 1-15 DCC Tunnel Configuration

Step Procedure

1 Complete the procedure: Disable the Control Data, page 1-19.

2 On the first node that is connected to third-party equipment, create a DCC tunnel (Steps 3 through 5).

If the fibers connected to the third-party equipment are in a protection group, it is necessary to create two tunnels on the source node. Create one tunnel from the working port and another from the protecting port. The destination for each tunnel depends on the Traverse network configuration.

3 In Shelf View, click the DCC Tunnel tab, then click New. A row appears on the screen.

Figure 1-13 DCC Tunnel Tab

3a

3b


Chapter 5 Creating DCC TunnelsTunneling a DCC Through a Traverse Network

4 Select the correct source and destination for each DCC tunnel. In each column, click the row to make the list of options appear.

Figure 1-14 Click a Row

Select the source information for the DCC tunnel:• From the SourcePort column, select the port that is connected to the

third-party equipment. • From the Source list, select an STS or an STM-0 number.

Select the destination information for the DCC tunnel:• From the DestinationPort list, click the trunk port for the network.• From the Destination list, select an STS or STM-0 number.

5 Click Add All New to add the DCC tunnel to the node.

6 Repeat Steps 3 through 5 at each intermediate node in the network.

7 On the last node, create a DCC tunnel (see Steps 3 through 5 of this procedure). If this is a SONET DCC tunnel, the destination STS number must match the STS number on the source node. That is, if you use STS #7 on the source interface, you must use STS #7 on the destination interface.

If this is an STM DCC tunnel, the destination STM-0 number must match the STM-0 number on the source node. That is, if you use STM-0 #7 on the source interface, you must use STM-0 #7 on the destination interface.

If the fibers connected to the third-party equipment are in a protection group, it is necessary to create two tunnels on the destination node. Create one tunnel from the trunk carrying the working traffic and another from the trunk carrying the protecting traffic.

8 The DCC Tunnel Configuration procedure is complete.

Table 1-15 DCC Tunnel Configuration (continued)

Step Procedure


Traverse Provisioning Guide, Section 1: Configuring the NetworkTunneling a DCC Through a Traverse Network



Chapter 6Configuring 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 includes the following topics:• Before You Configure IP Quality of Service, page 1-16• Configuring IP Quality of Service, page 1-17

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



Traverse Provisioning Guide, Section 1: Configuring the NetworkBefore You Configure IP Quality of Service

Before You Configure IP Quality of Service

Review the information in this topic before you configure IP Quality of Service (IP QoS).

Table 1-16 IP QoS Requirements


Read the information in Traverse Provisioning, Chapter 1—“Traverse Provisioning Overview,” page 1-7

Software

Node is commissioned. Traverse Installation and Commissioning Guide, Section 1—Configuring the Network, Chapter 2—“Discover the Network,” page 1-9



Chapter 6 Configuring IP Quality of ServiceConfiguring IP Quality of Service

Configuring IP Quality of Service

Use this procedure to block or allow traffic originating from certain IP hosts or networks using an access control list.

Table 1-17 Setting Up the IP Quality of Service

Step Procedure

1 In Shelf View, click the Admin menu, then click IP QoS Configuration.

2 The IP QoS Global Parameters Configuration dialog box displays.

Figure 1-15 IP QoS Configuration Panel Dialog Box

a. Select the IPQOS Feature Enable checkbox to enable the Quality of Service feature.

b. Enter the percentage of the available bandwidth for the queue size of high priority packets in the High Priority Q Size [1..100] field; default is 100.

c. Enter the percentage of the available bandwidth for the queue size of best effort packets in the Best Effort Priority Q Size [1..100] field; default is 100.

d. Click High Priority Q Weight [51...100] to define the weighted fair queuing value of the high priority queue; default is 80.

e. Click Apply.f. Go to Step 3 to enter the Static Classifier addresses for this IP address

or click Cancel to close the IP QoS Global Parameter Configuration dialog box and return to the main screen.


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfiguring IP Quality of Service

3 Click the Static Classifiers tab.

Figure 1-16 IP QoS Configuration, Static Classifier Tab

a. Click New.b. In the IP Address field, enter the static IP address of the site you want

to make static.c. In the Subnet Mask field, enter the area id of the IP address being

made static.d. In the Service Level field, enter the service level of the IP address.

Select one of the following values:– HiPriority– BestEffort

e. Click Add to add the changes to the list. f. Go to Step 4 to enter the ACL or click Done to close the OSI

Parameters Configuration Panel dialog box and return to the main screen.


Step Procedure


Chapter 6 Configuring IP Quality of ServiceConfiguring IP Quality of Service

4 Click the ACL (access control list) tab.

Figure 1-17 IP QoS Configuration, ACL Tab

a. Click New.b. In the IP Address field, enter the IP address to be added to the access

control list.c. In the Wildcard Mask field, enter the network area ID for this IP

address.d. In the Control field, click to select one of the following values:

– Deny– Permit

e. Click Add to add the changes to the list.f. Click Done to close the IP QOS Configuration Panel dialog box and

return to the main screen.

5 The Setting Up the IP Quality of Service procedure is complete.


Step Procedure


Traverse Provisioning Guide, Section 1: Configuring the NetworkConfiguring IP Quality of Service


SECTION 2 CONFIGURING TDM EQUIPMENTSECTION 2CONFIGURING EQUIPMENT

Contents

Chapter 1Equipment Configuration Overview (TDM)

Specific Equipment Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . 2-1Protection Groups and Card Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Change Card Common Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Chapter 2Configuring SONET Equipment

Before You Change SONET Equipment Configurations. . . . . . . . . . . . . . . . . 2-4Change DS1 Mapping Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Configure DS1 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Configure DS3 Clear Channel Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Configure DS3TMX or STS1TMX Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Configure Subports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Configure EC1 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Change the BER Thresholds for an STS Path . . . . . . . . . . . . . . . . . . . . . . . . 2-19Configure SONET Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Chapter 3Configuring SDH Equipment

Before You Configure SDH Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Change E1 Mapping Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Configure E1 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Configure E3 Clear Channel Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32Configure the BER Thresholds for an STM Path . . . . . . . . . . . . . . . . . . . . . . 2-34Configure STM-N Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

Chapter 4Creating a TransAccess 200 Mux

Before You Add a TransAccess 200 Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43Add TransAccess 200 Mux to the User Interface . . . . . . . . . . . . . . . . . . . . . . 2-45

Chapter 5Creating a TraverseEdge 50

Before You Add a TE-50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47Add TE-50 to the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49


Traverse Provisioning Guide, Section 2 Configuring TDM Equipment


SECTION 2CONFIGURING TDM EQUIPMENT

Chapter 1Equipment Configuration Overview (TDM)

Introduction You can customize certain parameters on each card (module) in a Traverse shelf. There are parameters that are common to all cards and parameters that are specific to each card. This chapter explains the following information for the card supported in this release:• Specific Equipment Configuration Procedures, page 2-1• Protection Groups and Card Configuration, page 2-1• Change Card Common Parameters, page 2-2

You can change parameters for each card:• During the preprovisioning process. Upon discovery of the equipment, the

management server downloads the preprovisioned data to the node.• After the equipment is discovered. If a piece of equipment has not been

preprovisioned when it is discovered, it arrives with default values. Change the default values on the Config tab.

Specific Equipment Configuration Procedures

See the following chapters in this section for details on configuring specific equipment:• Chapter 2—“Configuring SONET Equipment,” page 2-3• Chapter 3—“Configuring SDH Equipment,” page 2-27• Chapter 4—“Creating a TransAccess 200 Mux,” page 2-43• Chapter 5—“Creating a TraverseEdge 50,” page 2-47

For information on configuring ethernet equipment, see Section 5—Equipment, Chapter 4—“Ethernet Equipment.”

Protection Groups and Card Configuration

If you have configured a card as part of an equipment protection group, you can configure parameters only on the working card. Down arrows on selections are grayed out 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 creating equipment protection groups, see Section 3—Creating Protection Groups, Chapter 4—“Creating Equipment Protection Groups,” page 3-21.


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentChange Card Common Parameters

Change Card Common Parameters

Use this procedure to change common parameters on any card.

Table 2-1 Change Card Common Parameters

Step Procedure

1 In Shelf View, click any card.

2 Click the Config tab to display the Card Configuration screen.

Figure 2-1 Card Configuration Screen

3 In the Customer Tag field, enter an alphanumeric character string to identify the card to a customer.


5 The Change Card Common Parameters procedure is complete.

2

4

3



Chapter 2Configuring SONET Equipment

Introduction This chapter explains how to change configurable parameters for the following types of ports in a Traverse shelf:• Before You Change SONET Equipment Configurations• Change DS1 Mapping Formats• Configure DS1 Port• Configure DS3 Clear Channel Ports• Configure DS3TMX or STS1TMX Port• Configure Subports• Configure EC1 Ports• Change the BER Thresholds for an STS Path• Configure SONET Ports

These procedures describe how to change configurable parameters only. See the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 2—“SONET Equipment” for explanations of the parameters and fields on each card.


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentBefore You Change SONET Equipment Configurations

Before You Change SONET Equipment Configurations

Review this information before you change any parameters on any SONET equipment.

Table 2-2 SONET Equipment Requirements


Read the information in Section 1— Configuring the Network, Chapter 1—“Traverse Provisioning Over-view,” page 1-7.

Software

Node is commissioned Traverse Installation and Commissioning Guide, Section 11— Node Start-up and Commissioning Procedures

Network is discovered Traverse Provisioning Guide, Chapter 2—“Dis-cover the Network”

Timing is configured Traverse Provisioning Guide, Chapter 4—“Config-uring Network Timing”

Protection groups are configured.

Configure parameters only on working cards when a card is configured as part of a protection group. Parameters on a protection card are auto-matically set to those configured for the same port on the working card.

Traverse Provisioning Guide, Section 3— Creating Protection Groups

The card parameters are configured correctly. Traverse Provisioning Guide, Section 2—Configuring TDM Equipment, Chapter 1—“Equipment Configuration Overview (TDM)”

These procedures describe the steps to change configurable parameters only. See the TransNav Management System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide, Section 5—Equipment, Chapter 2—“SONET Equipment”

To monitor performance on a DS1 port, know how to use the performance monitoring (PM) templates.

TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 1—“Performance Monitoring”

To customize service-affecting and non-ser-vice-affecting alarm severities, know how to use alarm profiles.

TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 2—“Alarms”


Chapter 2 Configuring SONET EquipmentChange DS1 Mapping Formats

Change DS1 Mapping Formats

There are configurable parameters on the DS1 card that control how DS1 channels on the card (module) map to a VT payload or multiplex into an STS or STM path.

Important: Changing these parameters on the DS1 card is service affecting. You cannot complete this procedure if the card is carrying traffic (if there are services activated).

Table 2-3 Change DS1 Mapping Formats

Step Procedure

1 In Shelf View, click a DS1 card.


Figure 2-2 DS1 Card, Config Tab

3 Select how the DS1 channels on this card map to a VT payload from the DS1 Numbering drop-down list. Valid values are: • GR 253 (default): Select for non-sequential numbers. Maps per

GR-253-CORE.• Sequential: Select for sequential numbers.

See the TransNav Management System GUI Guide, Table 5-1 GR-253 and Sequential VT Mapping Formats, page 5-7 for the specific mapping formats.

4 Select how the DS1 channels on this card are multiplexed into an STS or TU container from the DS1 Mapping list. Valid values are:• VT2/VC12 (default): Select to multiplex the DS1 channels into a

VT2-mapped STS or a VC11-mapped TU-12. Only the first 21 ports are available.

• DS3: Select to multiplex the signal into a DS3-mapped STS. All 28 ports are available.

• VT15/VC11: Select to multiplex the DS1 channels into a VT1.5-mapped STS or a VC11-mapped TU-11. All 28 ports are available.

2

3 4

1

5


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure DS1 Port

Configure DS1 Port

Use this procedure to customize the behavior of a DS1 port.

5 Select the framing format to determine how signals will be multiplexed into the DS3 signal from the DS3 Framing Format list. Valid values are:• M23 (default): Select to asynchronously multiplex seven DS2 signals

into the DS3 signal.• CBIT: Select to asynchronously multiplex 28 DS1 signals into the

DS3 signal with the C-bit used as the control bit.


7 The Change DS1 Mapping Formats procedure is complete.

Table 2-3 Change DS1 Mapping Formats (continued)

Step Procedure

Table 2-4 Configure DS1 Port

Step Procedure

1 Review the information in Before You Change SONET Equipment Configurations, page 2-4 before you start this procedure.

2 In Shelf View, click a DS1 port on one of the following cards:• DS1 card• TransAccess 100 Mux

3 Click the Config tab to display the DS1 Port Configuration screen.

Figure 2-3 DS1 Port Configuration Screen

3

4

6 7

5


Chapter 2 Configuring SONET EquipmentConfigure DS1 Port

4 Change any of the following parameters for the DS1 interface:

Line Format: Select one of the following:• ESF (default): Extended superframe format• SF: Superframe format• Unframed: Upon detecting an LOF condition (in Unframed mode), the

system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors

Line Coding: Displays the line coding technique used for performance monitoring at the line layer. Select one of the following:• AMI (default): alternate mark inversion• B8ZS: bipolar 8-zero substitution

AIS Mask (Alarm Indication Signal Mask). Select one of the following:• Yes: Mask AIS/alarm for unused direction• No (default): Do not mask AIS/alarm for any direction

Line Build Out: Displays the distance from the subscriber interface to the physical port on the node. Select one of the following:• 0–133 ft (default)• 133–266 ft• 266–399 ft• 399–533 ft• 533–665 ft

5 Change any of the following general parameters for the interface:

Customer: Select from the list of defined customers.

Customer Tag: Enter an alphanumeric character string to identify the card to a customer.

PM Template: Select from the list of defined performance monitoring templates (of type ds1_ptp_pm). The default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ds1_ptp) to customize service-affecting and non-service-affecting alarm severities. The default is the default ds1_ptp alarm profile.

6 Click the Lock icon to unlock the port. The port must be unlocked to apply changes and monitor potential problems by generating alarms. The Lock icon is located in the lower left corner of the screen.

Table 2-4 Configure DS1 Port (continued)

Step Procedure


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure DS3 Clear Channel Ports

Configure DS3 Clear Channel Ports

Use this procedure to customize behavior of a DS3-CC port.


8 The Configure DS1 Port procedure is complete.

Table 2-4 Configure DS1 Port (continued)

Step Procedure

Table 2-5 Configure DS3CC Ports

Step Procedure

1 Review the information in the topic Before You Change SONET Equipment Configurations, page 2-4.

2 In Shelf View, click a DS3-CC port on one of the following cards:• DS3-CC card• DS3TMX card (DS3-CC port)

3 Click the Config tab to display the DS3 Clear Channel Port Configuration screen.

Figure 2-4 DS3 Clear Channel Port Configuration Screen

3

4

6 7

5


Chapter 2 Configuring SONET EquipmentConfigure DS3 Clear Channel Ports


Line Format: Select one of the following:• M23 (default): Seven DS2 signals asynchronously multiplexed into

the DS3 signal.• CBIT: 28 DS-1 signals are multiplexed into the DS3 signal, with the

C-bit used as control bit.• Unframed: A payload of 44.210 Mbps is supported with M, F, P, X,

and C bits preserved to ensure compatibility. Upon detecting an LOF condition (in Unframed mode), the system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors

In Band Loopback:• Disabled (default)• Enabled

AIS Mask (Alarm Indication Signal Mask): Select one of the following:• Yes: Mask AIS/alarm for unused direction.• No (default): Do not mask AIS/alarm for any direction.

AIS Format: Select one of the following:• NAS (default): North America Standard. All C-bits shall be set to 0.

All X-bits shall be set to 1. The information bits shall be set to a 1010... repeating sequence, with a 1 immediately following each of the control bit positions.

• ONES: Unformatted all ones.

Line Build Out: Select the length of cable between the node and the intermediate DS3 patch panel: • 0–225 ft (default)• 255–450 ft

Table 2-5 Configure DS3CC Ports (continued)

Step Procedure


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure DS3TMX or STS1TMX Port

Configure DS3TMX or STS1TMX Port

Use this procedure to customize behavior of a DS3TMX or an STS1TMX port.




PM Template: Select from the list of defined performance monitoring templates (of type ds_ptp_pm). The default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ds_ptp) to customize service-affecting and non-service-affecting alarm severities. The default is the default ds_ptp alarm profile.

6 Click the Lock icon to unlock the port. The port must be unlocked to apply changes and monitor performance by generating alarms. The Lock icon is located in the lower left corner of the screen.


8 The Configure DS3CC Ports procedure is complete.

Table 2-5 Configure DS3CC Ports (continued)

Step Procedure

Table 2-6 Configure DS3TMX or STS1TMX Ports

Step Procedure


2 In Shelf View, click a port on a DS3TMX card.• To change the port to an STS1TMX port, go to Step 3.• To change the default values on the DS3TMX port, go to Step 5.


Chapter 2 Configuring SONET EquipmentConfigure DS3TMX or STS1TMX Port

3 Select STS1 TMX, then click Switch.

Figure 2-5 Switch to STS1 TMX Port Type

4 In the Confirmation dialog box, click Yes to confirm the change.

Figure 2-6 Confirm Switch Dialog Box

5 Click the Config tab to display the Transmux Port Configuration screen.

Figure 2-7 DS3 Transmux Port Configuration Screen

Table 2-6 Configure DS3TMX or STS1TMX Ports (continued)

Step Procedure

5

6

8 9

7


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure DS3TMX or STS1TMX Port

6 Change any of the following parameters:

Line Format: Select one of the following:• M23: Seven DS2 signals asynchronously multiplexed into the DS3

signal.• CBIT (default): 28 DS-1 signals are multiplexed into the DS3 signal

with the C-bit used as control bit.



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.


Line Build Out (DS3TMX only): Select the length of cable between the node and the intermediate patch panel from the following values:• 0–225 ft (default)• 255–450 ft

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 the TransNav Management System GUI Guide, Table 5-1 GR-253 and Sequential VT Mapping Formats, page 5-7 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


Step Procedure


Chapter 2 Configuring SONET EquipmentConfigure DS3TMX or STS1TMX Port




PM Template (DS3TMX only): Select from the list of defined performance monitoring templates. Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS3 ports.

Alarm Profile (DS3TMX only): Select from the list of defined alarm profiles (of type ds_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default ds_ptp alarm profile.



10 The Configure DS3TMX or STS1TMX Ports procedure is complete.


Step Procedure


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure Subports

Configure Subports

Use this procedure to change parameter defaults for subports on a DS3TMX or an STS1TMX interface.

Table 2-7 Configure Subport

Step Procedure

1 In Shelf View, click a DS3TMX or STSTMX port on a DS3TMX card.

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

Figure 2-8 DS3 Transmux Port Configuration Screen

3 In the Adm State column, click Lock and select Unlock to enable the subport and monitor performance.

4 If DS3 Mapping on the TMX port is DS1, go to Step 5.

If DS3 Mapping on the TMX port is E1, go to Step 6.

5 If DS3 Mapping on the 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


2

3

6

54


Chapter 2 Configuring SONET EquipmentConfigure EC1 Ports

Configure EC1 Ports

Use this procedure to change a port on a DS3-CC or a DS3TMX card to EC1 mode and to customize behavior of an EC1 port.

6 If DS3 Mapping on the TMX port is E1, select one of the following values in the Line Format column:• Basic Frame: Select so the timing interface detects and generates the

Basic frame format per ITU-T Rec G.704/2.3 and G.706/4.1.2. This format does not support the SSM.

• Multi-Frame: Select so the timing interface detects and generates CRC-4 Multi-frame format per ITU-T Rec G.706/4.2. This format supports the SSM.

• Unframed: Select so that, upon detecting an LOF condition (in Unframed mode), the system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors


Alarm Profile: Select from the list of defined alarm profiles (of type ds1_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default ds1_ptp alarm profile.

PM Template: Select from the list of defined performance monitoring templates (of type ds1_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.


9 The Configure Subport procedure is complete.

Table 2-7 Configure Subport (continued)

Step Procedure

Table 2-8 Configure EC1 Ports

Step Procedure


2 In Shelf View, click a DS3-CC or a DS3TMX port on one of the following cards:• DS3• DS3TMX


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure EC1 Ports

3 Click the Config tab to display the DS3 Port Configuration screen.

Figure 2-9 DS3TMX Port Configuration Screen

4 If the port is unlocked, lock the port by clicking the Lock icon , located in the lower left corner of the screen.

5 Switch the port to an EC1 port. Select EC1 and click Switch.

Figure 2-10 Switch to EC1

6 Click Yes to confirm the switch.

Figure 2-11 Confirm Switch to EC1

Table 2-8 Configure EC1 Ports (continued)

Step Procedure

2

3

4 5


Chapter 2 Configuring SONET EquipmentConfigure EC1 Ports

7 The EC1 Port Configuration screen appears.

Figure 2-12 EC1 Port Configuration Screen

8 Change any of the following parameters for the EC1 interface:


Line Build Out: The cable length from the node to the other end of the EC-1 connection. Select one of the following:• 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



• 1E-6 (default). Value equals 1 x 10-6



Step Procedure

8

9

10 11


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure EC1 Ports




PM Template: Select from the list of defined performance monitoring templates (of type ec1_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for EC1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ec1_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default ec1_ptp alarm profile.


11 Click Apply.

12 The Configure EC1 Ports procedure is complete.


Step Procedure


Chapter 2 Configuring SONET EquipmentChange the BER Thresholds for an STS Path

Change the BER Thresholds for an STS Path

Configure the thresholds for the path-level signal failed bit error ratio (SF BER) and signal degrade bit error ration (SD BER) on an OC-N card. When the thresholds are exceeded, the system raises an SF BER-P or SD BER-P alarm.

Table 2-9 Change the BER Thresholds for an STS Path

Step Procedure

1 In Shelf View, click a card with an OC-N interface.


Figure 2-13 OC-192 Card, Config Tab

These parameters appear depending on the speed of the SONET interface and apply to all the paths on the card.

3 Set the transmission quality (bit error ratio) of failed signals in the STS path. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-P) alarm.

Select one of the following values:• 1E-3 (default for STS-1 SF BER). Value equals 1 x 10-3

• 1E-4 (default for STS-3c and STS-12c SF BER). Value equals 1x10-

• 1E-5 (default for STS-48c SF BER). Value equals 1 x 10-5



2

3 4

5


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentChange the BER Thresholds for an STS Path

4 Set the transmission quality (bit error ratio) of degraded signals (SD) in the STS path. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-P) alarm. Select one of the following values:• 1E-4. Value equals 1 x 10-4

• 1E-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-3cand STS-12c SD BER). Value equals 1 x 10-7

• 1E-8 (default for STS-48c SD BER). Value equals 1 x 10-8





6 The Change the BER Thresholds for an STS Path procedure is complete.

Table 2-9 Change the BER Thresholds for an STS Path (continued)

Step Procedure


Chapter 2 Configuring SONET EquipmentConfigure SONET Ports

Configure SONET Ports

Use this procedure to customize the behavior of a SONET port.

Table 2-10 Configure SONET Ports

Step Procedure

1 Review the information in the topic: Before You Change SONET Equipment Configurations, page 2-4.

2 In Shelf View, click any SONET port (if the port is in a protection group, click the working port), then click the Config tab to display the SONET Port Configuration screen.

Figure 2-14 SONET Port Configuration Screen

5

8

4

3

1110

67

9


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure SONET Ports

3 Change any one of the following parameters for the SONET interface:

AIS Mask (Alarm Indication Signal Mask):• Yes: Mask AIS/alarm for unused direction.• No (default): Do not mask AIS/alarm for any direction.

Sync Source: Indicates if this port is used to synchronize status. Valid values are:• Primary: Indicates this port is the primary sync source.• Secondary: Indicates this port is the secondary sync source.• Not used: Indicates this port is not used as the sync source.

SfBer-L: Measures the transmission quality (bit error ratio) of failed signals on the link. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-L) alarm and performs a protection switch. Select one of the following values: • 1E-3 (default). Value equals 1 x 10-3 • 1E-4. Value equals 1 x 10-4 • 1E-5. Value equals 1 x 10-5

Transmitter State: Select one of the following:• On (default): Laser is turned on.• Off: Laser is turned off.

Forced DUS (Do not Use for Synchronization): Select for this port to transmit the SSM (synchronization status message) DUS. This prevents the remote node that receives this signal from using the line as a timing reference.

SdBer-L: Measures the transmission quality (bit error ratio) of degraded signals on the optical link. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-L) alarm and performs a protection switch. Select one of the following values: • 1E-9. Value equals 1 x 10-9





Table 2-10 Configure SONET Ports (continued)

Step Procedure



4 Configure the automatic laser shutdown feature using the following parameters:

Trnsm Auto Shtdwn: Automatically shut down the transmit laser on optical interfaces when the system detects a receive LOS for 500 ms. The system turns the transmit laser off after detecting a receive LOS for 800 ms. The system raises the ALS alarm against the optical facility when the transmitter has been turned off automatically.• Disabled (default). The ALS feature is turned off.• Manual. The operator initiates a single laser pulse from the transmitter

for the amount of time specified in the Recovery Pulse Width parameter. To send the single laser pulse, click the Current Transmitter State button, then click Manual Restart.

• Automatic. The system turns off the transmit laser for a random time between 100 and 300 seconds. The transmit laser turns on if one of the following conditions occur:– The user manually sends a single laser pulse (Current

Transmitter State button). – If the system receives a valid signal for more than 800 ms.– After the random timer expires, the system sends periodic laser

pulses from the transmitter for the amount of time specified in the Recovery Pulse Width parameter.

Current Transmitter State: Click this button to display the current state of the optical transmitter. See Trnsm Auto Shtdwn parameter for details.

Rcvry Pulse Width: The system enables the transmitter for the amount of time specified in this parameter. Valid only if the value in Trnsm Auto Shtdwn is Manual or Automatic. Enter a time between 2 and 10 seconds; default is 5 seconds.


Step Procedure



5 Set the section trace formats and identifiers for this interface:

Fwd Section Trc Fmt (Forward Section Trace Format): This port transmits an access point identifier in the J0 byte of the SDH frame so that the section receiver can verify its continued connection. The valid value is 16 bytes.

Fwd Section Trace: The access point identifier transmitted in the J0 byte. Enter an alphanumeric character string.

SS Bit Transmit: Set the SS bit value that this interface is transmitting. Select one of the following values: • 00 (default): This interface is transmitting SONET frames.• 10: This interface is transmitting STM frames.

Note: To interoperate with equipment configured in SDH mode, change the value to 10.

Rev Section Trc Fmt (Reverse Section Trace Format): This port expects an access point identifier in the J0 byte of the SDH frame to verify its continued connection with the transmitter. If this port receives an incorrect identifier, the system raises an RS-TIM (Regenerator Section - Trace Identifier Mismatch alarm). The valid value is 16 bytes.

Rev Section Trace: The expected access point identifier to be received in the J0 byte. Enter an alphanumeric character string.

SS Bit Receive: Indicates the SS bit value that this interface is receiving.

Current Received Section Trace: Indicates the section trace currently being received.

6 Specify if the system uses the DCC bytes to communicate with other nodes in this network.

In the Control Data parameter, select one of the following:• Enabled (default): The management system uses this interface for

management traffic.• Disabled: The management system does not use this interface for

management traffic.


Step Procedure



7 If this system uses the DCC bytes to communicate with other nodes in this network, specify which DCC bytes are processed. You can change the value in this parameter only if the value in Control Data is Disabled.

In the Terminate DCC parameter, specify one of the following values:• Section: specifies that the interface uses the D1-D3 bytes (192 Kbps)

of the first STS on this interface for management traffic. • Line (default): specifies that the interface uses the D4-D12 bytes (576

Kbps) of the first STS on this interface for management traffic. • Line&Section: specifies that the interface uses the combined section

DCC and line DCC bytes from the first, second, and third STS on the interface (2.3 Mbps) for management traffic.

• Path (TE-100 OC-3 and OC-12 and Traverse OC-3 interfaces only): specifies that the interface uses the F2 byte (64 Kbps) of the STS for management traffic.

8 If the value in Terminate DCC is Path, specify which path (or paths) to carry management traffic. Click the Path DCC Configuration button to display the Path DCC Configuration dialog box.

Figure 2-15 OC-12 Path DCC Configuration Dialog Box

Select the paths on the interface that you want to use to carry management traffic.

Click Done and return to the Config tab on the main screen.


Step Procedure






PM Template: Select from the list of defined performance monitoring templates (of type sonet_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for SONET ports.

Alarm Profile: Select from the list of defined alarm profiles (of type sonet_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default sonet_ptp alarm profile.

10 L2 Protocol: Determines the Layer 2 (L2) protocol for this port. • PPP (default): Point-to-point protocol. Use PPP if this port is

connected to another Traverse or TE-100 platform.• LAPD: Link access procedure D-channel. Select LAPD if this port is

connected to legacy third-party ADM equipment and this node is used as an OSI DCC gateway node.

LAPD Role: Select the role of this node in the OSI DCC gateway application.• Network• User

DWDM wl supp value: The DWDM wavelength supplied value.

LAPD Mode: Select the mode of this node in the OSI DCC gateway application.• AITS: Acknowledge information transfer service. Use this value if the

value in L2 Protocol is LAPD.• UITS (default): Unacknowledge information transfer service. Use this

value if the value in L2 Protocol is PPP.

LAPD MTU: Indicates the maximum transmission unit for this node if the value in L2 Protocol is PPP; default is 512.

DWDM wl: Select from the list of defined wavelength frequencies.


12 Click Apply.

13 The Configure SONET Ports procedure is complete.


Step Procedure



Chapter 3Configuring SDH Equipment

Introduction This chapter explains how to change configurable parameters for the following types of ports in a Traverse shelf:• Before You Configure SDH Equipment, page 2-28• Change E1 Mapping Formats, page 2-29• Configure E1 Ports, page 2-30• Configure E3 Clear Channel Ports, page 2-32• Configure the BER Thresholds for an STM Path, page 2-34• Configure STM-N Port Parameters, page 2-36

These procedures describe how to change configurable parameters only. See the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 3—“SDH Equipment,” page 5-29 for explanations of all the parameters and fields on each card (module).


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentBefore You Configure SDH Equipment

Before You Configure SDH Equipment

Review this information before you change any parameters on SDH equipment.

Table 2-11 SDH Equipment Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Over-view,” page 1-7

Ensure the requirements in Before You Start Provisioning Your Network, page 1-9 are met.

Software




Configure parameters only on working cards when a card is configured as part of a protection group. Parameters on a protection card are auto-matically set to those configured for the same port on the working card.

Traverse Provisioning Guide Section 3—Creating Protection Groups

The card parameters are configured correctly. Traverse Provisioning Guide, Section 2—Configuring TDM Equipment, Chapter 1—“Equipment Configuration Overview (TDM),” page 2-1

These procedures describe the steps to change configurable parameters only. See the TransNav Management System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide, Section 5—Equipment, Chapter 3—“SDH Equip-ment,” page 5-29

To monitor performance on a DS1 port, know how to use the performance monitoring tem-plates.

TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 1—“Performance Monitoring,” page 8-1


TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 2—“Alarms,” page 8-13


Chapter 3 Configuring SDH EquipmentChange E1 Mapping Formats

Change E1 Mapping Formats

There are configurable parameters on the E1 card that control how E1 channels on the card map to a VT2 or VC12 payload or multiplex into an STS or STM path.

Important: Changing these parameters on the E1 card is service affecting. You cannot complete this procedure if the card is carrying traffic (if there are services activated).

Table 2-12 Change E1 Mapping Formats

Step Procedure

1 In Shelf View, click an E1 card.


Figure 2-16 E1 Card, Config Tab

3 Select how the E1 channels on this card maps to a VC payload. From the E1 Numbering list: • Select Non-sequential (default)• Select Sequential

See the TransNav Management System GUI Guide, Table 5-2 E1 Sequential and Non-Sequential Mapping Formats, page 5-30 for the specific mapping format.

4 Select how the E1 channels on this card are multiplexed into an a virtual container. From the E1 Mapping list:• Select VC12 (default) to multiplex an E1 channel into a VC12

container. • Select DS3 to multiplex an E1 channel into a DS3, which is then

mapped to a VC3. E1 ports are mapped according to the TransNav Management System GUI Guide, Table 5-3 DS3-structured VC3-mapped E1 channels, page 5-31.

Important: It is important to know how the E1 ports physically map to the patch panel. See the TransNav Management System GUI Guide, Section 2—Configuring TDM Equipment, Chapter 3—“Configuring SDH Equipment”, E1 Mapping and Patch Panel Ports, page 5-32.

2

3 4

5


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure E1 Ports

Configure E1 Ports

Use this procedure to customize behavior of an E1 port.


6 The Change E1 Mapping Formats procedure is complete.

Table 2-12 Change E1 Mapping Formats (continued)

Step Procedure

Table 2-13 Configure E1 Ports

Step Procedure

1 Review the information in Before You Configure SDH Equipment, page 2-28.

2 In Shelf View, click an E1 port on an E1 card.

3 Click the Config tab to display the E1 Port Configuration screen.

Figure 2-17 E1 Port Configuration Screen

4

76

5

3


Chapter 3 Configuring SDH EquipmentConfigure E1 Ports

4 Change any of the following parameters for the E1 interface:

Line Format: Select one of the following:• Basic Frame: Select so the timing interface detects and generates the

Basic frame format per ITU-T Rec G.704/2.3 and G.706/4.1.2. This format does not support the SSM.

• Multi-Frame (default): Select so the timing interface detects and generates CRC-4 Multi-frame format per ITU-T Rec G.706/4.2. This format supports the SSM.

• Unframed: Select so that, upon detecting an LOF condition (in Unframed mode), the system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors

Line Build Out: Displays the distance from the subscriber interface to the physical port on the node. Select one of the following:• Short Haul (default)• Gain Mode

AIS Mask (Alarm Indication Signal Mask): Select one of the following:• Yes: Mask AIS alarm for unused direction.• No (default): Do not mask AIS alarm for any direction.

AIS Insertion: Select one of the following:• Enabled (default): Generate an AIS when VC12 signal is degraded • Disabled: Do not generate an AIS when VC12 signal is degraded



PM Template: Select from the list of defined performance monitoring templates (of type e1_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ds1_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default e1_ptp alarm profile.



8 The Configure E1 Ports procedure is complete.

Table 2-13 Configure E1 Ports (continued)

Step Procedure


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure E3 Clear Channel Ports

Configure E3 Clear Channel Ports

Use this procedure to customize behavior of an E3-CC port.

Table 2-14 Configure E3CC Port

Step Procedure


2 In Shelf View, click an E3-CC port on a DS3/EC-1 / E3 card.

3 Click the Config tab to display the E3 Port Configuration screen.

Figure 2-18 E3 Port Configuration Screen


Line Format: Select one of the following:• G.751 (default)• G.832• Unframed: Upon detecting an LOF condition (in Unframed mode), the


RDI: Enables the system to send an RDI (remote defect indicator) signal as soon as it cannot identify valid framing or when it determines it is receiving an AIS.• Select Enabled to allow the system to send an RDI signal.• Select Disabled so the system does not send an RDI.

Line Build Out: Select the length of cable between the node and the intermediate patch panel:• 0–225 ft (default)• 255–450 ft


4

76

5

3


Chapter 3 Configuring SDH EquipmentConfigure E3 Clear Channel Ports




PM Template: Select from the list of defined performance monitoring templates (of type e3_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ds_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default e3_ptp alarm profile.


7 Click Apply.

8 The Configure E3CC Port procedure is complete.

Table 2-14 Configure E3CC Port (continued)

Step Procedure


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure the BER Thresholds for an STM Path

Configure the BER Thresholds for an STM Path

Configure the thresholds for the path-level signal failed bit error ratio (SFBER) and signal degrade bit error ratio (SDBER) on the STM-N card (module). When the thresholds are exceeded, the system raises an SFBER-P or SDBER-P alarm.

Table 2-15 Configure BER Thresholds for an STM Path

Step Procedure

1 Review the information in the topic Before You Configure SDH Equipment, page 2-28.

2 In Shelf View, click a card with an STM-N interface, then click the Config tab to display the Card Configuration screen.

Figure 2-19 STM-64 Card, Config Tab

3 In the Customer Tag field, enter an alphanumeric character string to identify the card to a customer.

4 Set the transmission quality (bit error ratio) of failed signals in the High Order path. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-P) alarm.

Select one of the following values:• 1E-3 (default for VC-3 SF BER): Value equals 1 x 10-3

• 1E-4 (default for VC-4 and VC-4-4c SF BER): Value equals 1 x 10-4

• 1E-5 (default for VC-4-16c SF BER): Value equals 1 x 10-5

2

4 5

6

3


Chapter 3 Configuring SDH EquipmentConfigure the BER Thresholds for an STM Path

5 Set the transmission quality (bit error ratio) of degraded signals (SD) in the High Order path. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-P) alarm. Select one of the following values:• 1E-4. Value equals 1 x 10-4


• 1E-6 (default for VC-3 SD BER). Value equals 1 x 10-6

• 1E-7 (default for VC-4 and VC-4-4c SD BER). Value equals 1 x 10-7

• 1E-8 (default for VC-4-16c SD BER). Value equals 1 x 10-8




7 The Configure BER Thresholds for an STM Path procedure is complete.

Table 2-15 Configure BER Thresholds for an STM Path (continued)

Step Procedure


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentConfigure STM-N Port Parameters

Configure STM-N Port Parameters

Use this procedure to customize behavior of a STM port.

Table 2-16 Configure STM-N Ports

Step Procedure


2 In Shelf View, click any STM-N port (if the port is in a protection group, click the working port), and then click the Config tab to display the SDH Port Configuration screen.

Figure 2-20 SDH Port Configuration Screen

5

8

4

3

11

10

6

7

9


Chapter 3 Configuring SDH EquipmentConfigure STM-N Port Parameters

3 Change any one of the following parameters for the STM interface:

AIS Mask (Alarm Indication Signal Mask):• Yes: Mask AIS/alarm for unused direction.• No (default): Do not mask AIS/alarm for any direction.

Sync Source: Indicates if this port is used to synchronize status. Valid values are:• Primary: Indicates this port is the primary sync source.• Secondary: Indicates this port is the secondary sync source.• Not used: Indicates this port is not used as the sync source.

SFBER: Measures the transmission quality (bit error ratio) of failed signals on the link. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-L) alarm and performs a protection switch. Select one of the following values: • 1E-3 (default): Value equals 1 x 10-3

• 1E-4: Value equals 1 x 10-4 • 1E-5: Value equals 1 x 10-5

Transmitter State: Select one of the following:• On (default): The laser is turned on.• Off: The laser is turned off.

Forced DUS (Do not Use for Synchronization): Select for this port to transmit the SSM (synchronization status message) DUS. This prevents the remote node that receives this signal from using the line as a timing reference.

SDBER: Measures the transmission quality (bit error ratio) of degraded signals. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD) alarm and performs a protection switch. Select one of the following values: • 1E-9. Value equals 1 x 10-9





Table 2-16 Configure STM-N Ports (continued)

Step Procedure



4 Configure the automatic laser shutdown feature using the following parameters:

Trnsm Auto Shtdwn: Automatically shut down the transmit laser on optical interfaces when the system detects a receive LOS for 500 ms. The system turns the transmit laser off after detecting a receive LOS for 800 ms. The system raises the ALS alarm against the optical facility when the transmitter has been turned off automatically.• Disabled (default): The ALS feature is turned off.• Manual. The operator initiates a single laser pulse from the transmitter

for the amount of time specified in the Recovery Pulse Width parameter. To send the single laser pulse, click the Current Transmitter State button, then click Manual Restart.

• Automatic: The system turns off the transmit laser for a random time between 100 and 300 seconds. The transmit laser turns on if one of the following conditions occur:– The user manually sends a single laser pulse (Current

Transmitter State button)– If the system receives a valid signal for more than 800 ms– After the random timer expires, the system sends periodic laser

pulses from the transmitter for the amount of time specified in the Recovery Pulse Width parameter

Current Transmitter State: Click this button to display the current state of the optical transmitter. See Trnsm Auto Shtdwn parameter for details.

Rcvry Pulse Width: The system enables the transmitter for the amount of time specified in this parameter. Valid only if the value in Trnsm Auto Shtdwn is Manual or Automatic. Enter a time between 2 and 10 seconds; default is 5 seconds.


Step Procedure



5 Set the section trace formats and identifiers for this interface:

Fwd Section Trc Fmt (Forward Section Trace Format): This port transmits an access point identifier in the J0 byte of the SDH frame so that the section receiver can verify its continued connection. The valid value is 16 bytes.

Fwd Section Trace: The access point identifier transmitted in the J0 byte. Enter an alphanumeric character string.

SS Bit Transmit: Set the SS bit value that this interface is transmitting. Set one of the following values:• 00: This interface is transmitting SONET frames.• 10 (default): This interface is transmitting STM frames.

Note: To interoperate with equipment configured in SONET mode, change the value to 00.

Rev Section Trc Fmt (Reverse Section Trace Format): This port expects an access point identifier in the J0 byte of the SDH frame to verify its continued connection with the transmitter. If this port receives an incorrect identifier, the system raises an RS-TIM (Regenerator Section - Trace Identifier Mismatch alarm). The valid value is 16 bytes.

Rev Section Trace: The expected access point identifier to be received in the J0 byte. Enter an alphanumeric character string.

SS Bit Receive: Indicates the SS bit value that this interface is receiving.

Current Received Section Trace: Indicates the section trace currently being received.

6 Specify if the system uses the DCC bytes to communicate with other nodes in this network.

In the Control Data parameter, select one of the following:• Enabled (default): The management system uses this interface for

management traffic.• Disabled: The management system does not use this interface for

management traffic.


Step Procedure



7 If the system uses the DCC bytes to communicate with other nodes in this network, specify which DCC bytes are processed. You can change the value in this parameter only if the value in Control Data is Disabled.

In the Terminate DCC parameter, specify one of the following values:• Regenerator: Specifies that the interface use the D1-D3 bytes

(192 Kbps) of the first AUG-1 on this interface for management traffic.

• Multiplexer (default): Specifies that the interface use the D4-D12 bytes (576 Kbps) of the first AUG-1 on this interface for management traffic.

• Regenerator&Multiplexer: Specifies that the interface use the combined section DCC and line DCC bytes from the first, second, and third AUG-1 on the interface (2.3 Mbps) for management traffic.

• Path (TE-100 STM-1 and STM-4 interfaces only): Specifies that the interfaces uses the F2 byte (64 Kbps) of the AUG for management traffic.)

8 If the value in Terminate DCC is Path, specify which path (or paths) to carry management traffic. Click the Path DCC Configuration button to display the Path DCC Configuration dialog box.

Figure 2-21 STM-4 Path DCC Configuration Dialog Box

Select the paths on the interface that you want to use to carry management traffic. The paths displayed depend on the value in the VC3 Mode parameter of the interface card (the multiplex structure for VC3 paths for the entire shelf).

Click Done and return to the Config tab on the main screen.


Step Procedure







PM Template: Select from the list of defined performance monitoring templates (of type sdh_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for STM ports.

Alarm Profile: Select from the list of defined alarm profiles (of type sdh_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default sdh_ptp alarm profile.

10 L2 Protocol: Determines the Layer 2 protocol for this port. • PPP (default): Select to make the port a point-to-point protocol. Use

PPP if this port is connected to another Traverse or TE-100 platform.• LAPD: Select to make the protocol for this port link access procedure

D-channel (LAPD). Select LAPD if this port is connected to legacy third-party ADM equipment and this node is used as an OSI DCC gateway node.

LAPD Role: Select the role of this node in the OSI DCC gateway application.• Network• User (default)

DWDM wl supp value: Indicates the DWDM wavelength supplied value.

LAPD Mode: Select the mode of this node in the OSI DCC gateway application.• AITS (Acknowledge information transfer service): Use this value if

the value in L2 Protocol is LAPD.• UITS (Unacknowledge information transfer service) (default): Select

this mode if the L2 Protocol value is PPP.

LAPD MTU: Indicates the multiple transmission unit if the value in L2 Protocol is PPP. The default is 512.

DWDM wl: Select from the list of defined wavelength frequencies.


12 Click Apply.

13 The Configure STM-N Ports procedure is complete.


Step Procedure


Chapter 4Creating a TransAccess 200 Mux

Introduction The TransAccess 200 Mux (TA200) connects to a Traverse shelf. Use the TransNav management system to remotely manage the configuration and status of the TransAccess 200 Mux.

This chapter contains the following information: • Before You Add a TransAccess 200 Mux• Add TransAccess 200 Mux to the User Interface

Before You Add a TransAccess 200 Mux

Review this information before you add a TransAccess 200 Mux to the TransNav management system.

Important: Refer to the TransAccess 200 Mux documentation for explanations and procedures on how to configure this product.

Table 2-17 TransAccess 200 Mux Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Overview”


Hardware

A node must have the following hardware components: • OC-3 interface• TransAccess 200 Mux

Traverse Product Overview Guide, Section 3—Card (Module) Descriptions

Software

Network is discovered. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 2—“Discover the Network”


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentBefore You Add a TransAccess 200 Mux

Timing is configured. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Timing”

Protection groups are configured. Traverse Provisioning Guide, Section 3—Creating Protection Groups

These procedures describe how to add the TransAccess 200 Mux to the graphical user inter-face.

n/a

To monitor performance on a TransAccess 200 Mux, know how to use the performance monitor-ing templates.

TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 1—“Performance Monitoring”.


TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 2—“Alarms”.

For TransAccess 200 Mux alarms to display on the TransNav user interface, set the SNMP infor-mation on the TransAccess 200 Mux using the following values:• Community name: Public• Community IP Address: 0.0.0.0• Community Access: Read-Write• Trap name: Public• Trap IP Address: BP-DCN-IP of the Traverse

node to which this device is connected OR the IP address of the TransNav server if it is not connected to a Traverse node

• Authentication Trap: Yes• T1/E1 Alarms: Detail

TransAccess 200 Mux Operations Manual

Table 2-17 TransAccess 200 Mux Requirements (continued)



Chapter 4 Creating a TransAccess 200 MuxAdd TransAccess 200 Mux to the User Interface

Add TransAccess 200 Mux to the User Interface

The TransAccess 200 Mux is not initially autodiscovered by the TransNav management system. Use this procedure to add a TransAccess 200 Mux to the user interface. See the TransAccess 200 Mux user documentation for information on configuring this product.

Table 2-18 Add TransAccess 200 Mux to the User Interface

Step Procedure

1 Review the information in the procedure, Before You Add a TransAccess 200 Mux, before you start this procedure.

2 In Map View, click the shelf to which this TransAccess 200 Mux is connected. Right-click the shelf, select Attach Sub Shelf, then select TA200.

Figure 2-22 Attach Sub Shelf

3 The Attach TA200 Shelf dialog box appears.

Figure 2-23 Attach TA200 Shelf Dialog Box

4 Configure the following parameters for the TransAccess 200 Mux:• Shelf Name: Type a name for the for the TransAccess 200 Mux. Use

alpha-numeric characters and spaces only. Do not use punctuation or any other special characters in this field.

• IP Address: Enter the IP address for this TransAccess 200 Mux.• Shelf Type: Select if this TransAccess 200 Mux has 12 slots or

16 slots.• Target Node: Select the node to which this TransAccess 200 Mux is

attached. • Advanced: See the TransNav Management System GUI Guide for

explanations of this option.

5 Click Add. The icon for the Traverse node changes to indicate there is a TransAccess 200 Mux shelf attached to this node.

Figure 2-24 TransAccess 200 Mux in Map View

4

5


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentAdd TransAccess 200 Mux to the User Interface

6 Configure the TransAccess 200 Mux parameters.

In Map View, right-click the node with the added TransAccess 200 Mux shelf

Figure 2-25 Sub Shelf Menu

a. Click Sub Shelf.b. On the extended menu, click Launch Sub Shelf, then click the name

of the subshelf. The TransAccess 200 Mux user interface opens. c. Configure the parameters for the TransAccess 200 Mux shelf.

See the TransAccess 200 Mux user documentation for information on configuring this product.

7 Repeat Steps 1 through 6 for each required TransAccess 200 Mux.

8 The Add TransAccess 200 Mux to the User Interface procedure is complete.

Table 2-18 Add TransAccess 200 Mux to the User Interface (continued)

Step Procedure



Chapter 5Creating a TraverseEdge 50

Introduction The TraverseEdge 50 (TE50) connects to a Traverse shelf. Use the TransNav management system to remotely manage the configuration and status of the TE-50.

This chapter contains the following information: • Before You Add a TE-50• Add TE-50 to the User Interface

Before You Add a TE-50

Review this information before you add a TE-50 to the TransNav management system.

Important: Refer to the TraverseEdge 50 User Guide for explanations and procedures on how to configure this product.

Table 2-19 TE-50 Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Overview”.

Ensure the requirements in Before You Start Provisioning Your Network are met.

Hardware

A node must have the following hardware compo-nents: • OC-N interface:

• OC-3• OC-12 interface with VSF4 interface

• TE-50


Software

Network is discovered. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 2—“Discover the Network”


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentBefore You Add a TE-50

Timing is configured. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Timing”

Protection groups are configured. Traverse Provisioning Guide, Section 3—Creating Protection Groups

These procedures describe how to add the TE-50 to the graphical user interface.

n/a

To monitor performance on a TE-50, know how to use the performance monitoring templates.

TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 1—“Performance Monitoring”


TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 2—“Alarms”

For TE-50 alarms to display on the TransNav user interface, set the SNMP information on the TE-50 using the following values:• Community name: Public• Community IP Address: 0.0.0.0 • Community Access: Read-Write• Trap name: Public• Trap IP Address: BP-DCN-IP of the Traverse

node to which this device is connected OR the IP address of the TransNav server if it is not connected to a Traverse node.

• Authentication Trap: Yes• T1/E1 Alarms: Detail

TraverseEdge 50 User Guide

Table 2-19 TE-50 Requirements (continued)



Chapter 5 Creating a TraverseEdge 50Add TE-50 to the User Interface

Add TE-50 to the User Interface

The TE-50 are not initially autodiscovered by the TransNav management system. Use this procedure to add a TE-50 to the user interface. See the TraverseEdge 50 User Guide for information on configuring this product.

Table 2-20 Add TE-50 to the User Interface

Step Procedure

1 Review the information in Before You Add a TE-50, page 2-47 before you start this procedure.

2 In Map View, click the shelf to which this TE-50 is connected. Right-click the shelf, select Attach Sub Shelf, then select TE50.

Figure 2-26 Attach Sub Shelf

3 The Attach TE50 Shelf dialog box appears.

Figure 2-27 Attach TE50 Shelf Dialog Box

4 Configure the following parameters for the TE-50:• Shelf Name: Type a name for the for the TE-50. Use alpha-numeric

characters and spaces only. Do not use punctuation or any other special characters in this field.

• IP Address: Enter the IP address for this TE-50.• Advanced: See TransNav Management System GUI Guide for

explanations of this option.

5 Click Add. The icon for the Traverse node changes to indicate there is a TE-50 shelf attached to this node.

Figure 2-28 TE-50 in Map View

4

5


Traverse Provisioning Guide, Section 2: Configuring TDM EquipmentAdd TE-50 to the User Interface

6 Configure the TE-50 parameters.

In Map View, right-click the node with the added TE-50 shelf

Figure 2-29 Sub Shelf Menu

a. Click Sub Shelf.b. Configure the parameters for the TransAccess 200 Mux shelf.

See the TraverseEdge 50 User Guide for information on configuring this product.

7 Repeat Steps 1 through 6 for each required TE-50.

8 The Add TE-50 to the User Interface procedure is complete.

Table 2-20 Add TE-50 to the User Interface (continued)

Step Procedure


SECTION 3 CREATING PROTECTION GROUPSSECTION 3CREATING PROTECTION GROUPS

Contents

Chapter 1Overview of Protection Groups

1:N Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Optical GbE Port Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Carrier Ethernet Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Link Aggregation with CEPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Line Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

1+1 APS/MSP protection groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Optimized protection switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51+1 path protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5UPSR or SNCP Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Chapter 2Creating a BLSR/MS-SPRing Protection Group

Example of a BLSR/ MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Squelching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Before You Create a BLSR or MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Guidelines to Create a BLSR or MS-SPRing Protection Group . . . . . . . . . . . 3-10Create a BLSR or MS-SPRing Protection Group . . . . . . . . . . . . . . . . . . . . . . 3-11

Chapter 3Creating a UPSR or SNCP Ring Protection Group

Example of a UPSR or an SNCP Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Before You Create a UPSR or SNCP Ring Protection Group. . . . . . . . . . . . . 3-17Guidelines to Create a UPSR or SNCP Ring . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Create a UPSR or SNCP Ring Protection Group . . . . . . . . . . . . . . . . . . . . . . 3-18

Chapter 4Creating Equipment Protection Groups

Before You Configure Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Guidelines to Create an Equipment Protection Group . . . . . . . . . . . . . . . . . . 3-23

Standard TDM Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-241:N Equipment Protection for an Optical TransmuxApplication (STS1-TMX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-241:1 Ethernet Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24


Traverse Provisioning Guide, Section 3 Creating Protection Groups

Create an Equipment Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

Chapter 5Carrier Ethernet Protection

Before You Configure CEPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29Guidelines to Create a CEPP Protection Group . . . . . . . . . . . . . . . . . . . . . . . 3-30Create a CEPP Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

Chapter 6Creating a 1+1 APS/MSP Protection Group

Example of a 1+1 APS/MSP Protection Group . . . . . . . . . . . . . . . . . . . . . . . . 3-35Before You Create a 1+1 APS/MSP Protection Group . . . . . . . . . . . . . . . . . . 3-36Create a 1+1 APS/MSP Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

Chapter 7Creating a 1+1 Path Protection Group

Example of a 1+1 Path Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42Before you Create a 1+1 Path Protection Group. . . . . . . . . . . . . . . . . . . . . . . 3-44Guidelines to Create a 1+1 Path Protection Group . . . . . . . . . . . . . . . . . . . . . 3-45Create a 1+1 Path Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

Chapter 8Creating a 1+1 Optimized Protection Group

Before You Create a 1+1 Optimized Protection Group . . . . . . . . . . . . . . . . . . 3-50Create a 1+1 Optimized Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51


SECTION 3CREATING PROTECTION GROUPS

Chapter 1Overview of Protection Groups

Introduction Depending on the network requirements, the Traverse system supports a selection of methods to protect traffic.

This chapter includes the following topics:• 1:N Equipment Protection, page 3-1• Optical GbE Port Protection, page 3-2• Carrier Ethernet Protection, page 3-2• Line Protection, page 3-4• Path Protection, page 3-5

All system components included are easily accessible and hot-swappable. Additionally, both hardware and software upgrades can be performed in-service without interruption to existing network traffic. This capability allows the transport network to expand gracefully as you add new customers and service requirement.

1:N Equipment Protection

Equipment protection groups use one card to provide redundancy for one or more of equal type. The Traverse supports the following types of equipment protection:• 1:1 equipment protection: One card physically protects an adjacent card (DS1,

DS3, DS3-CC, DS3-TMX, E1, E3-CC, NGE, NGE Plus, EoPDH, or UTMX cards).

Note: VTX/VCX integrated cards are not adjacent.

Note: 1:1 equipment protection between NGE and EoPDH cards is not supported.

NGE, NGE Plus and EoPDH cards using the Ethernet electrical connector module (ECM) provide equipment protection for the electrical ports only. For protection of the optical ports on these cards, see Optical GbE Port Protection, page 3-2.

• 1:2 equipment protection: One card protects up to two adjacent cards (DS3-CC, DS3-TMX, DS1, E1,E3, UTMX-24, UTMX-48, VT/TU 5G Switch, and VTX/VCX integrated cards).

• 1:N equipment protection, where:– One card protects all remaining cards and cards need not be adjacent.

• N = 1 to 2 for VT/TU 5G Switch on ADM shelf • N = 1 to 9 for VT/TU 5G Switch on 384-DCS shelf


Traverse Provisioning Guide, Section 3: Creating Protection GroupsOptical GbE Port Protection

– One card protects all remaining adjacent cards. • N = 1 to 12 for DS3 Transmux protection groups for high-density optical

transmux applications (STS1-TMX)– One card protects all remaining cards.

• N = 1 to 4 for UTMX protection groups for high-density optical transmux applications (STS1-TMX)

To create equipment protection groups, see Chapter 4—“Creating Equipment Protection Groups,” page 3-21.

Optical GbE Port Protection

With an optical coupler/splitter cable, protection extends to the optical (GbE or 10GbE) ports on NGE, NGE Plus, GbE-10, 10GbE, or EoPDHcards in a 1:1 equipment protection group. Use the optical splitter/coupler to bridge the signal from both the working and protecting card (of like type) to provide 1:1 optical equipment protection for these GbE ports.

There is one optical link from the customer premise equipment (CPE) to the coupler/splitter, connecting the CPE to the working card. The splitter sends a copy of the optical signal to both the working and protecting cards in the equipment protection group. The coupler receives a signal from both of the cards, combines them, and sends the composite signal—effectively the signal from the working (active) card—to the CPE.

On the working card of the protection group, the optical transmitters are up (laser on), while on the protecting (standby) card, the optical transmitters are forced down (laser off). Upon an equipment protection switch, when the card transitions from working to protecting or vice versa, its optical ports are automatically brought down or up, as appropriate.

When there is a protection switch from one card in an 1:1 equipment protection group to the other card, services on the optical ports restore as soon as those on the electrical Ethernet ports. Alarms may be raised briefly during the switch while the the optical transmitters are down until they are automatically brought back up.

Optical port protection does not protect against fiber cuts.

For fiber optic specifications and installation instructions, see the Traverse Installation and Commissioning Guide, Section 2—Network Interface Specifications, Chapter 1—“Fiber Optic Interface Cabling Specifications,” page 2-1.

For equipment protection group creation instructions, see Chapter 4—“Creating Equipment Protection Groups,” page 3-21.

Carrier Ethernet Protection

CEP Pair (CEPP) is a logical pairing of either two NGE Plus or two EoPDH cards operating as one Ethernet switch to aggregate the traffic from twice the number of physical ports (40 physical Ethernet ports) as that of a single card. While a CEPP can use all of the physical Ethernet ports of the two cards, on an NGE working card it uses


Chapter 1 Overview of Protection GroupsCarrier Ethernet Protection

only the 64 EOS ports for transport (see Figure 3-1). EoPDH cards have 128 ports available which can be EOS, EOP, or a combination of EOS and EOP. A CEPP can use any of the 128 EOS or EOP ports of the EoPDH working card for transport. CEPPs support Link Aggregation Groups (LAGs) with ports on both cards in the CEPP. See Link Aggregation with CEPP, page 3-3.

NGE Plus or EoPDH cards in a CEPP protection group cannot simultaneously be in a 1:1 equipment protection group; these protection groups are mutually exclusive. NGE Plus or EoPDH cards not in a CEPP function as an NGE card.

Force10 recommends adjacent card configuration, although the cards can be non-adjacent. To create CEPP protection groups, see Chapter 5—“Carrier Ethernet Protection,” page 3-29.

Link Aggregation with CEPP. CEPP supports Link Aggregation for parallel links based on the IEEE 802.3ad standard. A Link Aggregation Group (LAG) with CEPP can contain up to eight port members of the same type (FE or GbE) from the two separate NGE Plus or EoPDH cards. Service providers create a LAG on the working card of the CEPP and include member ports from either card in the CEPP.

Figure 3-1 LAG over CEPP on NGE Plus Cards

LAG5/1

NGE Plus, slot 5:WORKING, ACTIVE

NGE Plus, slot 4:PROTECTION, STANDBY

5/1

5/2

4/1

5/3

4/2

5/18

5/19

5/20

4/18

4/19

4/20

4/3

...

... 5/1

4/1

Ethernetservice

EOS5/1

EOS5/2

EOS5/3

LAG5/1

EOS5/1

EOS5/2

EOS5/3

Ethernetservice

These two NGE Plus cardshave been combined into a

CEPP

TR 00040

PhysicalEthernet

ports


Traverse Provisioning Guide, Section 3: Creating Protection GroupsLine Protection

Line Protection Line protection switching is a traffic protection mechanism based on SONET/SDH line level indications. A line is the transmission medium and the associated equipment that transports information between two network elements: one which originates the line signal and one that terminates it. Line protection switching is a protection mechanism coordinated by the nodes on either side of the failure condition using the protection switching signaling protocol.

1+1 APS/MSP protection groups. The APS/MSP protocol is carried in the K1 and K2 bits in the SONET/SDH signal between nodes in a bi-directional mode. The APS/MSP controllers at the line termination use the channel to exchange requests and acknowledgement for protection switching actions.

1+1 APS/MSP uses both the working and the protect fibers to send traffic simultaneously to the next node. That is, the system duplicates the traffic and sends it over both the working and the protect fibers at the same time.

With this protection mechanism, when the system detects a failure the next node switches to accept traffic from the standby path. The link remains unprotected until service is restored on the working link.

To create a 1+1 APS/MSP protection group, see Chapter 6—“Creating a 1+1 APS/MSP Protection Group,” page 3-35.

Optimized protection switching. The Traverse system also supports 1+1 bi-directional optimized protections switching per ITU-T G.783 Annex B.

To create an optimized protection group, see Chapter 8—“Creating a 1+1 Optimized Protection Group,” page 3-49.

BLSR . Bi-directional Line Switched Ring (BLSR) provides geographically diverse paths for each service using a self-healing closed loop technology to protect against fiber cuts and node failures. Protection switching is performed at the Line layer of the SONET/SDH frame.

MS-SPRing . Multiplex Section Shared Protection Ring (MS-SPRing) provides geographically diverse paths for each service using a self-healing closed loop technology to protect against fiber cuts and node failures. Protection switching is performed at the multiplex section layer of the STM frame.

To create a BLSR or MS-SPRing protection group, see Chapter 2—“Creating a BLSR/MS-SPRing Protection Group,” page 3-7.


Chapter 1 Overview of Protection GroupsPath Protection

Path Protection

Path protection switching is a traffic protection mechanism based on SONET/SDH path level indications. Path protection the logical end-to-end path of traffic through a network.

1+1 path protection. This protection mechanism uses one SONET/SDH of any bandwidth to protect another of the same bandwidth. In a Traverse network, use a 1+1 path protection group to protect the transport of DS1 and VT services.

1+1 path protection uses one STM of any bandwidth to protect another of the same bandwidth. In a Traverse network, use a 1+1 path protection group to protect the transport of E1, VC11, and VC12 services.

To create 1+1 path protection groups, see Chapter 7—“Creating a 1+1 Path Protection Group,” page 3-41.

UPSR or SNCP Ring. This type of protection scheme requires two fibers to carry traffic in opposite directions around a fiber ring. Protection switching is performed at the path level. To provide survivability, traffic from the tributary side is bridged into both the working and protecting channels at the source. Path selection at the destination chooses the best quality signal (working or protecting) before dropping it from the ring.

To create UPSR or SNCP Ring protection groups, see Chapter 3—“Creating a UPSR or SNCP Ring Protection Group,” page 3-15.


Traverse Provisioning Guide, Section 3: Creating Protection GroupsPath Protection



Chapter 2Creating a BLSR/MS-SPRing Protection Group

Introduction A BLSR/MS-SPRing protection group provides geographically diverse paths for each service using a self-healing closed loop technology to protect against fiber cuts and node failures. Protection switching is performed at the line layer of the SONET and the multiplex section of the SDH frame.

The Traverse supports for 2-fiber (2F) BLSR/MS-SPRing. A 2F BLSR/2F MS-SP Ring offers substantial capacity advantages in interoffice and access networks that have distributed mesh traffic patterns because of its ability to reuse bandwidth, as traffic is added and dropped at various locations around the ring.• Example of a BLSR/ MS-SPRing, page 3-8• Squelching, page 3-9• Before You Create a BLSR or MS-SPRing, page 3-9• Guidelines to Create a BLSR or MS-SPRing Protection Group, page 3-10• Create a BLSR or MS-SPRing Protection Group, page 3-11


Traverse Provisioning Guide, Section 3: Creating Protection GroupsExample of a BLSR/ MS-SPRing

Example of a BLSR/ MS-SPRing

A BLSR/MS-SPRing provides the ability to reuse bandwidth. When traffic is dropped at one node in a BLSR/MS-SPRing configuration, the remaining capacity is then available for traffic at that node. The BLSR/MS-SPRing assigns half of the bandwidth to working traffic and the other half is reserved as a protection route.

For example, in an OC-48 BLSR, the first 24 STS-1s carry the working traffic the other 24 STS-1s are assigned as protection.

For example, in an STM-16 MS-SPRing, the first 8 VC-3s carry the working traffic the other 8 VC-3s are assigned as protection.

In the event of a single failure or a failure in a segment in a ring, the Traverse system restores all protected traffic.

Figure 3-2 OC-48/STM-16 2F BLSR/MS-SPRing

25 to 48: Protection

TR-00019

1 to 24: Working

Node 2Node 4

Node 3

Node 1

Tributaries

Tributaries

Tributaries

Tributaries

STS Channels


Chapter 2 Creating a BLSR/MS-SPRing Protection GroupBefore You Create a BLSR or MS-SPRing

Squelching The Traverse supports squelching. Nodes adjacent to a ring failure replace non-restorable traffic with a path layer alarm indication signal (AIS) to notify the far-end node of the interruption in service. The squelching feature automatically generates squelch tables, no manual record keeping is required.

The squelch table first source node ID of the traffic entering the node and the last destination node ID of the traffic exiting the node for each time slot that the node is terminating (adding/dropping) or passing through.

Provisioning a squelch table occurs during the service provisioning.

For information on squelching and the squelch table, see the TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 1—“BLSR and MS-SPRing Protection Groups,” page 4-3.

Before You Create a BLSR or MS-SPRing

Review this information before you create a BLSR or MS-SPRing protection group.

Table 3-1 BLSR/MS-SPRing Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Over-view”.


Hardware

There can be up to 16 nodes in a one ring. n/a

Each node requires at least two cards with inter-faces of the same data rate:• 1-port OC-48/STM-16• OC-192/STM-64• GCM with 1-port OC-48/STM-16 (optical

interface)


You can use an OC-48/STM-16 and a GCM with 1-port OC-48/STM-16 in a BLSR or MS-SP ring protection group.

n/a

The nodes are physically connected. The East card on one node is physically connected to the West card on the next.


Software

Network is discovered Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 2—“Discover the Network,” page 1-9

Timing is configured Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Timing,” page 1-15

There are no line-level alarms (LOS, LOF, AIS-L, SF-BER-L) present on the interfaces you are using to configure the ring.

Click the port, click the Alarms tab and verify no alarms are present.


Traverse Provisioning Guide, Section 3: Creating Protection GroupsGuidelines to Create a BLSR or MS-SPRing Protection Group

Guidelines to Create a BLSR or MS-SPRing Protection Group

A single Traverse 2000 node supports the following numbers of BLSR or MS-SP Ring protection groups:• Up to four on OC-192 or STM-64 rings• Up to nine on OC-48 or STM-16 rings

A single Traverse 1600 node supports the following numbers of BLSR or MS-SP Ring protection groups:• Up to three on OC-192 or STM-64 rings• Up to seven on OC-48 or STM-16 rings

There can be up to 16 nodes in a 2F BLSR or MS-SP Ring.

Note: BLSR cannot be configured on 2-port OC-48 or STM-16 rings.

Ports in a BLSR or MS-SP ring protection group can only be part of that protection group. The ports cannot be part of another protection group.

The East card on one node is physically connected to the West port on the next.

The order of entry of nodes must be from East to West around the ring. That is, there must be a link from the East port of node n to the West port of node n+1 in the list.

The Control Data parameter is Enabled on each interface you are using to configure the ring.

In Shelf View, click the port, click the Config tab, and verify that Control Data is Enabled.

Traverse Provisioning Guide, Section 2—Configuring TDM Equipment, Chapter 3—“Configuring SDH Equipment,” page 2-36

The link is in the Enabled state. If the link is dis-abled (or is preprovisioned), you cannot synchro-nize the ring.

In Map View, click the link, click the Config tab and verify the Operational State is Enabled.

TransNav Management System GUI Guide, Section 3—Network, Chapter 1—“Creating and Deleting Equipment Using Preprovisioning,” page 3-1

These procedures describe the steps to create pro-tection groups only. See the TransNav Manage-ment System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 1—“BLSR and MS-SPRing Protection Groups,” page 4-1

Table 3-1 BLSR/MS-SPRing Requirements



Chapter 2 Creating a BLSR/MS-SPRing Protection GroupCreate a BLSR or MS-SPRing Protection Group

Create a BLSR or MS-SPRing Protection Group

Use this procedure to create a BLSR or MS-SPRing protection group.

Table 3-2 Create a BLSR or MS-SPRing Protection Group

Step Procedure

1 Review the information in Before You Create a BLSR or MS-SPRing, page 3-9 before you start this procedure.

2 In Map View, click the Protection tab to display the Protection Rings screen.

3 From the New list, select BLSR or MSSPRING.

Figure 3-3 Select BLSR or MSSPRING

4 Click Add to display the Protection Group Creation tab, Add Protection Ring screen.

Figure 3-4 Add Protection Ring Screen

Step 4

57

6


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a BLSR or MS-SPRing Protection Group

5 In the Name field, enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation or any other special character in this field.

6 Set the reversion options:• Select the Revertive checkbox to switch traffic back to the working

line when the working line has recovered from the original failure condition or the external command is cleared.

• In the WTR Time field, set a time in minutes that the system will wait after a protection switch before switching back to the working line.Enter a number between 1 and 60; default is 5.

7 Indicate the card type.

Card Type (default is OC-48 on an ANSI node and STM-16 on an ITU node):• Select OC-48 for OC-48 interfaces• Select OC-192 for OC-192 interfaces• Select STM-16 for STM-16 interfaces• Select STM-64 for STM-64 interfaces

Note: BLSR cannot be configured on 2-port OC-48/STM-16 cards.

8 Add nodes to the ring. In Map View, click a node to add it to the ring. The nodes are displayed on the screen as you select them from Map View.

Figure 3-5 West and East Ports for BSLR/MS-SPRing

9 The system automatically assigns IDs consecutively beginning with “0” for the first node assigned to the ring. You can manually assign a node ID by selecting a number (0 through 15) from the ID list. Node IDs are not required to be consecutive, but a node ID can be used only once in a ring.

From the ID list, select a node identification (ID) number.

Table 3-2 Create a BLSR or MS-SPRing Protection Group (continued)

Step Procedure

8 9 1110


Chapter 2 Creating a BLSR/MS-SPRing Protection GroupCreate a BLSR or MS-SPRing Protection Group

10 For each node in the ring (Node column), select a West port from the menu in the West Port column.

The West port of a node is physically connected to the East port of another node.

11 For each node in the ring (Node column), select an East port from the menu in the East Port column.

The East and West ports must be on separate cards in the shelf.

12 On the Add Protection Group screen, click Add.

13 In the Synchronize Protection Group dialog box, click Yes to propagate protection group information to all nodes in the ring.

Figure 3-6 Synchronize Confirmation

14 The protection group is listed in the Protection Rings screen and is assigned a 4-digit Ring ID.

Figure 3-7 Protection Rings Screen

15 The Create a BLSR or MS-SPRing Protection Group procedure is complete.

Table 3-2 Create a BLSR or MS-SPRing Protection Group (continued)

Step Procedure


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a BLSR or MS-SPRing Protection Group



Chapter 3Creating a UPSR or SNCP Ring Protection Group

Introduction A Uni-directional Path Switched Ring (UPSR) is a self-healing closed loop topology that protects against fiber cuts and node failures by providing duplicate, geographically diverse paths for each service.

Subnetwork Connection Protection (SNCP) provides end-to-end path protection in a ring topology.

This chapter contains information on creating an UPSR ring protection group.• Example of a UPSR or an SNCP Ring, page 3-16• Before You Create a UPSR or SNCP Ring Protection Group, page 3-17• Guidelines to Create a UPSR or SNCP Ring, page 3-18• Create a UPSR or SNCP Ring Protection Group, page 3-18


Traverse Provisioning Guide, Section 3: Creating Protection GroupsExample of a UPSR or an SNCP Ring

Example of a UPSR or an SNCP Ring

A UPSR or a SNCP ring is a protection configuration that provides path protection in a unidirectional ring topology. In a ring, there are source nodes (Node 1), destination nodes (Node 4), and intermediate nodes (Node 2 and Node 3). Traffic enters the ring at the source node, travels through the intermediate nodes, and exits the ring at the destination node.

Figure 3-8 Bridging and Selecting Signals in a UPSR or SNCP Ring

In a UPSR or an SNCP ring configuration in a Traverse network, the East card always transmits the working signal clockwise around the ring. The West card always receives the working signal. The East card on one node is physically connected to the West port on the next.

In normal operation, the source node makes a duplicate of the original traffic and bridges it around the ring in opposite directions. The destination node determines the best quality signal based on path layer indications including path layer defects and maintenance signals.

In a failure scenario, the destination node determines the best quality signal and selects traffic from that path. Path protection is single-ended without any type of coordination with, or notification to, the source node. During a fiber failure and before full service is restored, there is no protection on the ring.

Bridging

Node 1

Node 4

Path selection

Node 2

Node 3

TR 00089


Chapter 3 Creating a UPSR or SNCP Ring Protection GroupBefore You Create a UPSR or SNCP Ring Protection Group

Before You Create a UPSR or SNCP Ring Protection Group

Review this information before you create a UPSR or an SNCP protection group.

Table 3-3 UPSR or SNCP Ring Protection Group Requirements




Hardware

Each node requires at least two cards with inter-faces of the same data rate:• OC-3/STM-1• OC-12/STM-4• 1-port OC-48/STM-16• 2-port OC-48/STM-16• OC-192/STM-64• Any GCM with integrated OC-12 or OC-48

interface


You can use the following combination of cards in a protection group:• OC-12/STM-4 and a GCM with 1-port

OC-12/STM-4• OC-48/STM-16 and a GCM with 1-port

OC-48/STM-16

You can use the system cards in a protection group.


Nodes are physically connected. The East card on one node is physically connected to the West port on the next.

Traverse Installation and Commissioning Guide,

Software



There are no path-level alarms (LOS, LOF, AIS-P, SF-BER-P) present on the interfaces you are using to configure the ring.

Click the port, click the Alarms tab, and verify no alarms are present.

These procedures describe the steps to create pro-tection groups only. See TransNav Management System GUI Guide for descriptions of other fields on screen.

TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 2—“UPSR and SNCP Ring Protection Groups,” page 4-9


Traverse Provisioning Guide, Section 3: Creating Protection GroupsGuidelines to Create a UPSR or SNCP Ring

Guidelines to Create a UPSR or SNCP Ring

A single Traverse 2000 node supports the following number of UPSR or SNCP Ring protection groups:• Up to four on OC-192 or STM-64 rings• Up to nine on OC-48 or STM-16 rings

A single Traverse 1600 node supports the following number of UPSR or SNCP Ring protection groups:• Up to three on OC-192 or STM-64 rings• Up to seven on OC-48 or STM-16 rings

There can be up to 16 nodes in a UPSR or SNCP ring.

The East card on one node is physically connected to the West port on the next card.

In a UPSR or SNCP ring configuration, the East card always transmits the working signal clockwise around the ring. The West card always receives the working signal.

For end-to-end UPSR/SNCP protected services, the system automatically assigns the protected path, including the time slots. If you want to assign the protected path, provision a 1+1 path protected service instead.

Create a UPSR or SNCP Ring Protection Group

Use this procedure to create a UPSR or SNCP ring protection group.

Table 3-4 Create a UPSR or SNCP Ring Protection Group

Step Procedure

1 Review the information in Before You Create a UPSR or SNCP Ring Protection Group, page 3-17 before you start this procedure.

2 In Map View, click the Protection tab to display the Protection Rings screen.

3 Add a UPSR or an SNCP Ring protection group. From the New list, select SNCP/UPSR.

Figure 3-9 Select SNCP/UPSR

Step 4


Chapter 3 Creating a UPSR or SNCP Ring Protection GroupCreate a UPSR or SNCP Ring Protection Group

4 Click Add to display the Protection Group Creation tab, Add SNCP/UPSR Ring screen.

Figure 3-10 Add SNCP/UPSR Ring Screen


6 Add nodes to the ring. In Map View, click a node to add it to the ring. The nodes display on the screen as you select them from Map View.

Figure 3-11 West and East Ports for SNCP/UPSR Ring

7 For each node in the ring (Node column), select a West port from the menu in the West Port column.

The West port of a node is physically connected to the East port of another node.

8 For each node in the ring (Node column), select an East port from the menu in the East Port column.

The East and West ports must be on separate cards in the shelf.

Click Add.

Table 3-4 Create a UPSR or SNCP Ring Protection Group (continued)

Step Procedure

5

6 7 8


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a UPSR or SNCP Ring Protection Group

9 In Synchronize Protection Group dialog box, click Yes to propagate protection group information to all nodes in the ring.

Important: If you have multiple servers, you must be on the Primary server to synchronize the nodes.

Figure 3-12 Synchronize Confirmation

10 The protection group is listed in the Protection Rings screen and is assigned a 4-digit Ring ID.

Figure 3-13 Protection Rings Screen

11 The Create a UPSR or SNCP Ring Protection Group procedure is complete.

Table 3-4 Create a UPSR or SNCP Ring Protection Group (continued)

Step Procedure



Chapter 4Creating Equipment Protection Groups

Introduction This chapter provides configuration procedures for network link (trunk) and tributary protection groups in a Traverse network.• Before You Configure Equipment Protection, page 3-21• Guidelines to Create an Equipment Protection Group, page 3-23• Create an Equipment Protection Group, page 3-27

Before You Configure Equipment Protection

Review this information before you create an equipment protection group.

Table 3-5 Equipment Protection Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Overview.”


Hardware


Traverse Provisioning Guide, Section 3: Creating Protection GroupsBefore You Configure Equipment Protection

The Traverse supports equipment protection for the following hardware components:• DS1• DS3 and DS3 Clear Channel (DS3CC)• DS3 Transmux (DS3TMX)• E1• E3 and E3 Clear Channel (E3CC)• GE

• 1-port 10GBE (10GBE)• 10-port GBE (GBE-10)

• NGE• GBE4-FE16-TX• GBE2F-GBE4F-FE16-TX

• NGE Plus• GBE4-FE16-TX / CEP• GBE2F-GBE4F-FE16-TX / CEP

• EoPDH• GBE4-FE16-TX-EoPDH• GBE2T-GBE2F-FE16-TX-EoPDH

• VTX/VCX component of any GCM w/ VCX• VT/TU 5G Switch


The correct ECMs are installed. Traverse Installation and Commissioning Guide, Section 2—Network Interface Specifications, Chapter 2—“ECM Interface Specifications”

The correct optical fiber cables are installed. Traverse Installation and Commissioning Guide, Section 2—Network Interface Specifications, Chapter 1—“Fiber Optic Interface Cabling Speci-fications”

The cards must be in the correct slots. Traverse Installation and Commissioning Guide• Section 11—Node Start-up and

Commissioning Procedures• Section 12—Appendices, Appendix

A—“Card Placement Planning and Guidelines,” page 12-1

Software


Timing is configured Traverse Provisioning Guide Section 1—Configuring the Network, Chapter 4—“Configuring Network Timing,” page 1-15

Table 3-5 Equipment Protection Requirements (continued)



Chapter 4 Creating Equipment Protection GroupsGuidelines to Create an Equipment Protection Group

Guidelines to Create an Equipment Protection Group

Review the following guidelines before you configure an equipment protection group.• Each protection scheme requires the correct ECM. See the Traverse Installation

and Commissioning Guide, Section 2—Network Interface Specifications, Chapter 2—“ECM Interface Specifications,” page 2-15.

• Protection groups can start in any odd or even-numbered slot.• All Ethernet ports on High Capacity 10GE (10GBE) and High Density GE

(GBE-10) cards are optical ports only. There are no electrical ports.• Protection groups on EoPDH cards can be on EOS or EOP ports.• Equipment protection groups on EoPDH cards must be two EoPDH cards. • To plan for an in-service upgrade of an unprotected card (module), use one

physical card and preprovision the second. Preprovision the equipment protection group using the physical card as the working card and the preprovisioned card as the protecting card. At a later date, insert the protecting card into the shelf.

If this is an optical transmux application using 1:N equipment protection, all ports on the DS3TMX cards must be switched to STSTMX format.

Use the CLI command to switch all ports at once.

exec interface switch tmxfmt format ststmx


TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 3—“Equipment Protection Groups,” page 4-15




Traverse Provisioning Guide, Section 3: Creating Protection GroupsGuidelines to Create an Equipment Protection Group

Standard TDM Equipment Protection. •In a 1:1 equipment protection scheme, either card (n or n+1) can be the protecting or working card in the protection group.

• In a 1:2 equipment protection scheme, the middle card (n+1) in a group of three cards protects the adjacent two working cards (n and n+2).

• Traverse supports a mix of old and new DS3 cards in 1:1 protection groups. Traverse supports 1:2 protection groups with new DS3 cards only. There is no support for using the old DS3 card or mixing old and new DS3 cards in 1:2 protection groups. – New cards:

• 12-port DS3/E3/EC-1 (PN: 905-0025-[03 | 13])• 24-port DS3/E3/EC-1 (PN: 905-0077-[03 | 13]) • DS3 Transmux (PN: 905-0001-25]• UTMX-24 (PN: 905-0765-02)• UTMX-48 (PN: 905-0761-02)

– Old cards: • 12-port DS3/EC-1 (PN: 905-0002-xx)• DS3 Transmux (PN: 905-0001-05)

• Traverse does not support a mix of DS3 and E3 cards in a 1:N protection group.

1:N Equipment Protection for an Optical Transmux Application (STS1-TMX).• Force10 recommends using the left-most (nth) card as the protecting card.• All ports on all DS3TMX or UTMX cards must be switched to STSTMX. Use the

CLI command to switch all ports at once (exec interface electrical switch ds3-fmt format ststmx).

• The order in which the cards are added to the protection group determines the order of priority for protection switching. For example, there are DS3TMX cards in slots 1 through 13. The card in slot 1 is the protecting card. If slot 5 is added to the protection group before the card in slot 3, the card in slot 5 has priority over the card in slot 3. If there is a failure on both cards simultaneously, the protecting card will take over for the card in slot 5 until the failure condition clears.

1:1 Ethernet Equipment Protection. •The two cards in the Ethernet protection group can be in any two adjacent slots in the shelf. The lower numbered slot (nth) is the protecting card. The higher numbered slot (n+1) is the working card.

• Create Ethernet protection groups with cards that have similar port configurations. Use any of the following combinations of NGE or NGE Plus cards in a 1:1 Ethernet equipment protection group:

Table 3-6 NGE Card Types for 1:1 Ethernet Equipment Protection

NGE Cards (2 each)

NGE Plus Cards(2 each)

Mixed NGE Cards(1 each)

GBE4-FE16-TX GBE4-FE16-TX / CEP • GBE4-FE16-TX• GBE4-FE16-TX / CEP

GBE2F-GBE2T-FE16-TX GBE2F-GBE2T-FE16-TX / CEP • GBE2F-GBE2T-FE16-TX• GBE2F-GBE2T-FE16-TX / CEP


Chapter 4 Creating Equipment Protection GroupsGuidelines to Create an Equipment Protection Group

– NGE Plus cards in a Carrier Ethernet Protection Pair (CEPP) protection group cannot simultaneously be in a 1:1 Ethernet equipment protection group; these protection groups are mutually exclusive.

– NGE Plus cards not in a CEPP function the same as an NGE card. However, if an operator inserts an NGE Plus card into a pre-Release TR2.1 Traverse node, the node will not recognize the card and raise an “Equipment mismatch” alarm.

• Create Ethernet protection groups on EoPDH cards on EOS and EOP ports. • Use the following combinations of EoPDH cards in a 1:1 Ethernet equipment

protection group:

– EoPDH cards in a Carrier Ethernet Protection Pair (CEPP) protection group cannot simultaneously be in a 1:1 Ethernet equipment protection group; these protection groups are mutually exclusive.

– EoPDH cards not in a CEPP function the same as an NGE card. If an operator inserts an EoPDH card into a pre-Release TR3.2 Traverse node, the node will not recognize the card and raise an “Equipment mismatch” alarm.

• Use any of the following combinations of High Capacity 10GE or High Density GE cards in a 1:1 Ethernet equipment protection group:

• Beginning with Release TR2.1, the 1:1 Ethernet equipment protection also applies to optical GBE ports with the introduction of an optical splitter/coupler. You can either use the optical GBE port on the working card for unprotected traffic or use an optical splitter/coupler to bridge the signal to both cards to provide 1:1 equipment protection for the optical GBE ports.

Important: For pre-Release TR2.1, the 1:1 Ethernet equipment protection group applies only to the electrical ports on the card. All optical GBE ports are disabled (lasers forced OFF) as long as the electrical protection group exists.

• The protecting optical GBE lasers are forced down (lasers off). Upon protection switch, when the NGE, NGE Plus, 10GBE, GBE-10, or EoPDH card transitions from Standby to Active or vice versa, the optical GBE ports are automatically brought up or down, as appropriate.

• Optical GBE port protection does not protect against fiber cuts.

Table 3-7 EoPDH Card Types for 1:1 Ethernet Equipment Protection

EoPDH Cards (2 each)

Mixed EoPDH Cards(1 each)

GBE4-FE16-TX-EoPDH • GBE4-FE16-TX-EoPDH • GBE2F-GBE2T-FE16-TX-EoPDH

GBE2F-GBE2T-FE16-TX-EoPDH

Table 3-8 10GBE and GBE-10 Card Types for 1:1 Equipment Protection

High Capacity 10GE Cards

(2 each)

High Density GE Cards(2 each)

Mixed High Capacity/High Density Cards

(1 each)

10GBE GBE-10 • 10GBE• GBE-10


Traverse Provisioning Guide, Section 3: Creating Protection GroupsGuidelines to Create an Equipment Protection Group

• You cannot create or delete a 1:1 Ethernet equipment protection group if there are any of these conditions on the card:– Activated Ethernet services using ports– Activated members of the EOS ports– Activated members of the EOP ports (EoPDH cards only) – EOS ports, EOP ports, LAGs, or Policers are configured– Ethernet facilities are currently in facility or terminal loopbacks

• 1:1 Ethernet electrical equipment protection:– interworks with all other supported optical (line and path) protection schemes.– does not interwork with 1+1 EOS or EOP port protection.

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.

EOS and EOP port alarms will be raised on the Active card in a 1:1 Protection Group.


Chapter 4 Creating Equipment Protection GroupsCreate an Equipment Protection Group

Create an Equipment Protection Group

Use this procedure to create an equipment protection group.

Table 3-9 Create an Equipment Protection Group

Step Procedure

1 Review the information in Before You Configure Equipment Protection, page 3-21 before you start this procedure.

2 In Shelf View, click the Protection tab to display the Protection Groups screen.

3 From the New list, select 1_for_N equipment.

Figure 3-14 Select a 1:1 Equipment

4 Click Add to display the Protection Group Creation tab, Add Equipment Protection Group screen.

Figure 3-15 Add Equipment Protection Group Screen

4

5 6

7

9


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate an Equipment Protection Group

5 In the Name field, enter the name of the protection group (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation or any other special character in this field.

6 Set the reversion options:• Select the Revertive check box to switch traffic back to the working

card when the working card has recovered from the original failure condition or the external command is cleared.

• In the WTR Time field, set a time in minutes that the system will wait after a protection switch before switching back to the working card.Enter a number between 1 and 60; default is 5.

7 Select the protecting card for the protection group. On the Protecting row, click the Card field and select the protecting card.

Figure 3-16 Select Protecting and Working Cards

8 Select the working cards for the protection group. On each Working row, click the Card field and select the working card.

9 Click Create to create the protection group and return to the Protection Groups screen on the Protection tab.

Figure 3-17 Protection Groups Screen

The system assigns an ID to the new protection group.

10 The Create an Equipment Protection Group procedure is complete.

Table 3-9 Create an Equipment Protection Group (continued)

Step Procedure



Chapter 5Carrier Ethernet Protection

Introduction This chapter provides configuration procedures for Carrier Ethernet Protection Pair (CEPP) protection groups in a Traverse network:• Before You Configure CEPP, page 3-29• Guidelines to Create a CEPP Protection Group, page 3-30• Create a CEPP Protection Group, page 3-32

Before You Configure CEPP

Review this information before you create a CEPP protection group.

Table 3-10 Equipment Protection Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Overview”.


Hardware

The Traverse supports CEPP protection for the following hardware components:

NGE Plus:• GBE4-FE16-TX / CEP• GBE2T-GBE2F-FE16-TX / CEP

EoPDH: • GBE4-FE16-TX-EoPDH• GBE2T-GBE2F-FE16-TX-EoPDH


Verify the correct ECMs are installed. Traverse Installation and Commissioning Guide, Section 8—Network Interface Cabling Proce-dures

Ensure the cards are in the correct slots. Traverse Installation and Commissioning Guide• Section 11—Node Start-up and

Commissioning Procedures• Section 12—Appendices, Appendix A—“Card

Placement Planning and Guidelines,” page 12-1


Traverse Provisioning Guide, Section 3: Creating Protection GroupsGuidelines to Create a CEPP Protection Group

Guidelines to Create a CEPP Protection Group

Review the following guidelines before you configure a CEPP protection group.• Each protection scheme requires the correct ECM. See the Traverse Installation

and Commissioning Guide, Section 2—Network Interface Specifications, Chapter 2—“ECM Interface Specifications,” page 2-15.

• Create Ethernet protection groups with cards that have similar port configurations on the same card type (either NGE Plus or EoPDH). Use either of the following combinations of NGE Plus cards:– two GBE4-FE16-TX / CEP cards– two GBE2T-GBE2F-FE16-TX / CEP cards Or combinations of the following EoPDH cards: – two GBE4-FE16-TX-EoPDH– two GBE2T-GBE2F-FE16-TX-EoPDH

• Protection groups can start in any odd or even-numbered slot.• Force10 recommends adjacent card configuration, although the cards can be

non-adjacent. (Non-adjacent cards require two ECMs.)• NGE Plus or EoPDH cards in a CEPP protection group cannot simultaneously be

in a 1:N equipment protection group; these protection groups are mutually exclusive. NGE Plus or EoPDH cards that are not in a CEPP function the same as an NGE card.

• NGE Plus or EoPDH cards in a Carrier Ethernet Protection Pair (CEPP) protection group cannot simultaneously be in a 1:1 Ethernet equipment protection group; these protection groups are mutually exclusive.

• NGE Plus or EoPDH cards not in a CEPP function the same as an NGE card. However, if an operator inserts an NGE Plus or EoPDH card into a pre-Release TR2.1.x Traverse node, the node will not recognize the card and will raise an “Equipment mismatch” alarm.

Software

Verify the network is discovered. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 2—“Discover the Network,” page 1-9

Ensure the timing is configured. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Timing,” page 1-15


TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 6—“Carrier Ethernet Protection Pair,” page 4-29




Chapter 5 Carrier Ethernet ProtectionGuidelines to Create a CEPP Protection Group

• Beginning with Release TR2.1.x, the 1:1 Ethernet equipment protection now also applies to optical GBE ports with the introduction of an optical splitter/coupler. You can either use the optical GBE port on the working card for unprotected traffic or use an optical splitter/coupler to bridge the signal to both cards to provide 1:1 equipment protection for the optical GBE ports.

Important: For pre-Release TR2.1.x, the 1:1 Ethernet equipment protection group applies only to the electrical ports on the card. All optical GBE ports are disabled (lasers forced OFF) as long as the electrical protection group exists.

• The protecting optical GBE lasers are forced down (lasers off). Upon protection switch, when the NGE, NGE Plus, or EoPDH card transitions from Standby to Active or vice versa, the optical GBE ports are automatically brought up or down, as appropriate.

• Optical GBE port protection does not protect against fiber cuts.• You cannot create or delete a CEPP protection group if there are any of these

conditions on the card:– Activated Ethernet services using ports– Activated members of the EOS or EOP ports– EOS ports, EOP ports, VRBs, LAGs, or Policers are configured– Ethernet facilities are currently in facility or terminal loopbacks

• CEPP protection groups:– interwork with all other supported optical (line and path) protection schemes– do not interwork with 1+1 EOS port protection



Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a CEPP Protection Group

Create a CEPP Protection Group

Use this procedure to create a CEPP protection group.

Table 3-11 Create a CEPP Protection Group

Step Procedure

1 Review the information in Before You Configure CEPP, page 3-29 before you start this procedure.


Figure 3-18 Protection Tab

3 From the New list, select CEPP.

Figure 3-19 Select CEPP

4 Click Add to display the Create Protection Group tab, Carrier Ethernet Protection Pair screen.

Figure 3-20 Carrier Ethernet Protection Pair Screen

56

7

8


Chapter 5 Carrier Ethernet ProtectionCreate a CEPP Protection Group

5 In the Name field, enter the name of the protection group (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation or any other special characters in this field.


card when the working card has recovered from the original failure condition or the external command is cleared.

• In the WTR Time field, set a time in minutes that the system will wait after a protection switch before switching back to the working card.Enter a number between 1 and 60; default is 5.

7 Select the protecting card (NGE Plus or EoPDH only) for the protection group. On the Protecting row, click the Card field and select the protecting card.

Figure 3-21 Select Protecting and Working Cards

8 Select the working cards for the protection group. On the Working row, click the Card field and select the working card.




10 The Create a CEPP Protection Group procedure is complete.

Table 3-11 Create a CEPP Protection Group (continued)

Step Procedure


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a CEPP Protection Group



Chapter 6Creating a 1+1 APS/MSP Protection Group

Introduction Use 1+1 APS/MSP on simple point-to-point and linear chain topologies.

This chapter contains information on creating a 1+1 APS/MSP protection group.• Example of a 1+1 APS/MSP Protection Group, page 3-35• Before You Create a 1+1 APS/MSP Protection Group, page 3-36• Create a 1+1 APS/MSP Protection Group, page 3-37

Example of a 1+1 APS/MSP Protection Group

1+1 APS/MSP uses both the working and the protect fibers to send traffic simultaneously to the next node. That is, the system duplicates the traffic and sends it over both the working and the protect fibers at the same time.

With this protection mechanism, when the system detects a failure, the next node switches to accept traffic from the standby path. The link remains unprotected until service is restored on the working link.

In the following example, a linear chain topology provides direct access to individual eastbound or westbound STS or AU channels at intermediate sites along a fiber route, without unnecessary multiplexing and de-multiplexing of pass-through traffic.

The Traverse platform supports simple point-to-point and linear chain topologies.

Figure 3-23 1+1 APS/MSP in a Linear Chain Topology

Configure 1+1 APS/MSP protection at for each facility connected to the next node. In this example, configure one 1+1 APS/MSP protection group at Node 1 and Node 3. Configure two protection groups at Node 2.

OC-N Links

Node1Tributaries

OC-N Links

Node2 Node 3

TR 00090


Traverse Provisioning Guide, Section 3: Creating Protection GroupsBefore You Create a 1+1 APS/MSP Protection Group

Before You Create a 1+1 APS/MSP Protection Group

Review this information before you create a 1+1APS/MSP group. The Traverse supports 1+1 unidirectional and bi-directional protection switching.

Table 3-12 1+1 APS Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Over-view,” page 1-7.


Hardware

Each node requires at least two cards with interfaces of the same data rate:• OC-3/STM-1• OC-12/STM-4• 1-port OC-48/STM-16• 2-port OC-48/STM-16• OC-192/STM-64• GCM with integrated OC-12 or OC-48

interface

For example, you can use the OC-12 inter-face on the OC-12/STM-4 card in combina-tion with the OC-12 interface on the GCM card.

Traverse Product Overview Guide, Section 3—Card (Module) Descriptions.

Each pair of cards must be in the correct slots.

Traverse Installation and Commissioning Guide• Section 11—Node Start-up and Commissioning

Procedures• Section 12—Appendices, Appendix A—“Card


Software


Timing is configured. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Tim-ing,” page 1-15

No line-level alarms (LOS, LOF, AIS-L, SF-BER-L) are present on the interfaces you are using to configure the protection group.

Click the port, click the Alarms tab, and verify no alarms are present

These procedures describe the steps to create protection groups only. See the TransNav Management System GUI Guide for descrip-tions of other fields on the screen.

TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 4—“1+1 MSP/APS Protection Groups,” page 4-21

When the STM-16 (with integrated 2.5 Gb VT/TU switch) is in a 1+1 MSP protection group and the integrated 2.5G VT/TU switch is in a 1:1 equipment protection group, you can currently activate only 8 VC-4 endpoints of VC grooming types on this STM-16 port using the VCX on this card.

n/a


Chapter 6 Creating a 1+1 APS/MSP Protection GroupCreate a 1+1 APS/MSP Protection Group

Create a 1+1 APS/MSP Protection Group

Use this procedure to create a 1+1 APS/MSP protection group.

Table 3-13 Create a 1+1 APS/MSP Protection Group

Step Procedure

1 Review the information in Before You Create a 1+1 APS/MSP Protection Group, page 3-36 before you start this procedure.


3 Add a 1+1 APS protection group. From the New list, select 1+1 MPS/APS.

Figure 3-24 Select 1+1 MPS/APS

4 Click Add to display the Protection Group Creation tab, Add 1+1 Protection Group screen.

Figure 3-25 Add 1+1 Protection Group Screen

5 In the Name field, enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation or any other special characters in this field.

34

567

8

10


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a 1+1 APS/MSP Protection Group


card when the working port has recovered from the original failure condition or the external command is cleared.

• In the WTR Time field, set a time in minutes that the system will wait after a protection switch occurs before switching back to the working port.Enter a number between 1 and 60; default is 5.

7 In the Switch Mode parameter, set the behavior of the protection switch on the link. • Select Uni-directional to switch traffic from a failed receive direction

to the standby link.• Select Bi-directional to switch both the transmit and receive directions

to the standby link.

8 Select the Protecting Port for this protection group. On the Protecting row, click the Port field and select the protecting port.

Figure 3-26 Select Protecting and Working Ports

9 Repeat Step 8 to select the working port. On the Working row, click the Port field and select the working port.

Table 3-13 Create a 1+1 APS/MSP Protection Group (continued)

Step Procedure


Chapter 6 Creating a 1+1 APS/MSP Protection GroupCreate a 1+1 APS/MSP Protection Group

10 Click Add to return to the Protection Groups screen on the Protection tab.



11 Repeat Steps 1 through 10 at the other end of the fiber link.

12 The Create a 1+1 APS/MSP Protection Group procedure is complete.

Table 3-13 Create a 1+1 APS/MSP Protection Group (continued)

Step Procedure


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a 1+1 APS/MSP Protection Group



Chapter 7Creating a 1+1 Path Protection Group

Introduction 1+1 path protection is a protection mechanism that uses one SONET path of any bandwidth to protect another of the same bandwidth. In a Traverse network, use a 1+1 path protection group to protect the transport of DS1 and VT services.

This chapter contains information on creating a 1+1 path protection group.• Example of a 1+1 Path Protection Group, page 3-42• Before you Create a 1+1 Path Protection Group, page 3-44• Guidelines to Create a 1+1 Path Protection Group, page 3-45• Create a 1+1 Path Protection Group, page 3-45


Traverse Provisioning Guide, Section 3: Creating Protection GroupsExample of a 1+1 Path Protection Group

Example of a 1+1 Path Protection Group

This model uses a 1+1 path protection group to create a protected path across the network. First, provision the required services at each node across the network. Subsequently, add a 1+1 path protection group either immediately, or at a later date.

Using this model, you can protect paths at the following path levels:• STS• High order AU-4• High order VC-3• Low order VC-3

In the following examples, first create and activate the sequence of unprotected services (Steps 1, 2, 3, and 4), and then create the 1+1 path protection group at the Add and Drop nodes (Steps 5 and 6). The pass-through services at the intermediate nodes can be on any available path

Figure 3-28 1+1 Path Protection Group (SONET)

Node 1 (Source node)Slot 1

GCMOC48

Slot 16

GCMOC48

Slot 15

1. Service Type: SONETBandwidth: STSSrc: Node 1/slot-1/all portsDest: Node 1/slot-15/p-1/sts-1Protection Type: Unprotected

UnprotectedOC-48

Node 6 (Drop node)Slot 1

GCMOC48

Slot 16

GCMOC48

Slot 15OC12

4. Service Type: SONETBandwidth: STS-1Src: Node 6/slot 15/p-1/sts-1Dest: Node 6/slot-1/p-3/sts-1Protection Type: Unprotected

6. Path Protection GroupWorking: Node 6/slot-15/p-1/sts-1Protecting: Node 6/slot-16/p-1/sts-1

1 2

2

2

4


Node 4

Node 3

Node 2

PW

33

3Node 5

W P 6

UnprotectedOC-48

5

3. Service Type: SONET (Pass Through)Bandwidth: STS-1Src: Node 2/slot 15/p-1/sts-1Dest: Node 2/slot-16/p-1/sts-1Protection Type: Unprotected


DS1


Chapter 7 Creating a 1+1 Path Protection GroupExample of a 1+1 Path Protection Group

.

Figure 3-29 1+1 Path Protection Group (SDH)


GCMSTM16Slot 16

GCMSTM16Slot 15

1. Service Type: SDHBandwidth: VC3Src: Node 1/slot-1/all portsDest: Node 1/slot-15/p-1/a-1/vc3-1Protection Type: Unprotected

UnprotectedSTM-16


GCMSTM16Slot 16

GCMSTM16Slot 15

STM4

4. Service Type: SDHBandwidth: VC3Src: Node 6/slot 15/p-1/a-1/vc3-1Dest: Node 6/slot-1/p-3/a-1/vc3-1Protection Type: Unprotected

6. Path Protection GroupWorking: Node 6/slot-15/p-1/a-1/vc3-1Protecting: Node 6/slot-16/p-1/a-1/vc3-1

1 2

2

2

4


Node 4

Node 3

Node 2

PW

33

3Node 5

W P 6

UnprotectedSTM-16

5

E1

3. Service Type: SDH (Pass Through)Bandwidth VC3Src: Node 2/slot 15/p-1/a-1/vc3-1Dest: Node 2/slot-16/p-1/a-1/vc3-1Protection Type: Unprotected

2. Service Type: SDH (Pass Through)Bandwidth: VC3Src: Node 2/slot 15/p-1/a-1/vc3-1Dest: Node 2/slot-16/p-1/a-1/vc3-1Protection Type: Unprotected


Traverse Provisioning Guide, Section 3: Creating Protection GroupsBefore you Create a 1+1 Path Protection Group

Before you Create a 1+1 Path Protection Group

Review this information before you create a 1+1 path protection group.

Table 3-14 1+1 Path Requirements




Hardware

Create 1+1 path protection on trunk cards of the same data rate:

Each node requires at least two cards with interfaces of the same data rate:• OC-3/STM-1 • OC-12/STM-4• 1-port OC-48/STM-16• 2-port OC-48/STM-16• OC-192/STM-64• GCM with integrated OC-12/STM-4 or

OC-48/STM-16 interface

For example, you can use the OC-12 inter-face on the OC-12/STM-4 card in combina-tion to with the OC-12/STM-4 interface on the GCM card.


Each pair of cards must be in the correct slots.

Traverse Installation and Commissioning Guide• Section 11—Node Start-up and Commissioning

Procedures• Section 12—Appendices, Appendix A—“Card


Software


Timing is configured Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Tim-ing,” page 1-15

There are no path-level alarms (LOS, LOF, AIS-P, SF-BER-P) present on the interfaces you are using to configure the protection group.


These procedures describe the steps to create a 1+1 path protection group only. See the TransNav Management System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 5—“1+1 Path Protection Groups,” page 4-27


Chapter 7 Creating a 1+1 Path Protection GroupCreate a 1+1 Path Protection Group

Guidelines to Create a 1+1 Path Protection Group

The guidelines to create a 1+1 path protection group are:• Use the 1+1 path protection group model to protect services created at the

following path levels: – STS– High order AU-4– High order VC-3– Low order VC-3

• See Section 5—Creating Service Applications, Chapter 1—“Creating 1+1 Path Protected Services,” page 5-1 for the complete procedure to create end-to-end path protection.

• The network interfaces at the source and drop nodes cannot be part of a 1+1 APS/MSPprotection group, an MS-SP ring, or a BLSR protection group. However, the interfaces can be part of a UPSR/SNCP protection group or unprotected.

• Provision the protection group after the initial service is provisioned. This sequence allows for in-service upgrades of any already activated service.

Create a 1+1 Path Protection Group

Use this procedure to create a 1+1 path protection group.

Table 3-15 Create a 1+1 Path Protection Group

Step Procedure

1 Review the information in Before you Create a 1+1 Path Protection Group, page 3-44 before you start this procedure.


3 Add a 1+1 path protection group. From the New list, select 1+1_path.

Figure 3-30 Select 1+1 Path

Step 4


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a 1+1 Path Protection Group

4 Click Add to display the Protection Group Creation tab, Add 1+1 Protection Group screen.

Figure 3-31 Add 1 Plus 1 Protection Group Screen


6 Select the protecting information.• Select the Protecting Port for this protection group. Click the

Protecting Port field and select the protecting port.• Select the Protection Path for this protection group. Click the

Protection Path field and select the protection path.

7 Select the working information.• Select the Working Port for this protection group. Click the Working

Port field and select the protecting port.• Select the Working Path for this protection group. Click the Working

Path field and select the protection path.

8 Select the bandwidth of the paths. From the Concatenation parameter, select the total bandwidth of the path. If the working and protecting endpoints are SONET endpoints, select from the following options: • 1 (default) for STS-1 paths• 3c for STS-3c• 12c for STS-12c paths (for OC-12 and greater interfaces only)• 48c for STS-48c paths (for OC-48 and greater interfaces only)

If the working and protecting endpoints are STM endpoints, select from the following options: • 1 for HO and LO VC-3 paths (default)• 4c for VC-4-4c paths• 16c for VC-4-16c paths (for STM-4 and greater interfaces only)

Table 3-15 Create a 1+1 Path Protection Group (continued)

Step Procedure

56

7


Chapter 7 Creating a 1+1 Path Protection GroupCreate a 1+1 Path Protection Group




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

Table 3-15 Create a 1+1 Path Protection Group (continued)

Step Procedure


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a 1+1 Path Protection Group



Chapter 8Creating a 1+1 Optimized Protection Group

Introduction 1+1 optimized protection bridges traffic simultaneously over two lines: section 1 and section 2. There is a primary section and a secondary section.

In normal operation, the system selects traffic from the primary section (active traffic). All switch requests (automatic or forced) are from the primary section to the secondary section. Once a switch request clears, the traffic selector stays on the section to which it was switched. That section then becomes the primary section if there are no further switch requests.

If a failure occurs on the secondary section, the traffic selector remains on traffic from the primary section. If a failure occurs on the secondary section during a protection switch, the initial switch request is abandoned.

This chapter contains the following information:• Before You Create a 1+1 Optimized Protection Group, page 3-50• Create a 1+1 Optimized Protection Group, page 3-51


Traverse Provisioning Guide, Section 3: Creating Protection GroupsBefore You Create a 1+1 Optimized Protection Group

Before You Create a 1+1 Optimized Protection Group

Review this information before you create a 1+1 optimized protection group.

The Traverse supports 1+1 bi-directional optimized protection switching.

Table 3-16 1+1 Optimized Protection Requirements



Ensure the requirements in the procedure, Before You Start Provisioning Your Network, page 1-9 are met.

Hardware

Each node requires at least two cards with inter-faces of the same data rate:• OC-3/STM-1• OC-12/STM-4• 1-port OC-48/STM-16• 2-port OC-48/STM-16• OC-192/STM-64• GCM with integrated OC-12/STM-4 or

OC-48/STM-16 interface

For example, you can use the OC-12 interface on the OC-12/STM-4 card in combination to with the OC-12/STM-4 interface on the GCM card.


Each pair of cards must be in the correct slots. Traverse Installation and Commissioning Guide• Section 11—Node Start-up and

Commissioning Procedures • Section 12—Appendices, Appendix

A—“Card Placement Planning and Guidelines,” page 12-1

Software



There are no line-level alarms (LOS, LOF, AIS-L, SF-BER-L) present on the interfaces you are using to configure the protection group.



TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 7—“1+1 Optimized Protection Groups,” page 4-33

When the STM-16 (with integrated 2.5G VT/TU switch) is in a 1+1 optimized protection group and the integrated 2.5G VT/TU switch is in a 1:1 equipment protection group, you can currently activate only 8 VC-4 endpoints of VC grooming types on this STM-16 port using the VCX on this card.

n/a


Chapter 8 Creating a 1+1 Optimized Protection GroupCreate a 1+1 Optimized Protection Group

Create a 1+1 Optimized Protection Group

Use this procedure to create a 1+1 optimized protection group.

Table 3-17 Create a 1+1 Optimized Protection Group

Step Procedure

1 Review the information in Before You Create a 1+1 Optimized Protection Group, page 3-50 before you start this procedure.


3 Add an equipment protection group. From the New list, select 1+1_optimized.

Figure 3-33 Select 1+1 Optimized

4 Click Add to display the Create Protection Group tab, Add 1+1 Protection Group screen

Figure 3-34 Add 1+1 Optimized Protection Group Screen

5 In the Name field, enter the name of the node (maximum 43 characters). Use alphanumeric characters only. Do not use punctuation or any other special character in this field.

6 In the WTR Time field, set the time (in minutes) after a protection switch that the section carrying active traffic becomes the primary section.

Enter a number in the between 1 and 60; default is 5.

Step 4

5 6

7

9


Traverse Provisioning Guide, Section 3: Creating Protection GroupsCreate a 1+1 Optimized Protection Group

7 Select a port for Section 1. On the Section 1 row, click the Port field and select the first working channel.


8 Repeat Step 7 for Section 2. On the Section 2 row, click the Port field and select the port for the second working channel.

9 Click Add to return to the Protection Groups screen on the Protection tab.



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

Table 3-17 Create a 1+1 Optimized Protection Group (continued)

Step Procedure


SECTION 4 CREATING ADM SERVICESSECTION 4CREATING ADM SERVICES

Contents

Chapter 1Service Provisioning Concepts

Traverse Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Supported Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

DS3 Transmux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Bridging and Rolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Multicast Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Optical Transmux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Resource Advisory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2SDH to SONET Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2VT/VC Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Transport Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Traverse Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Service Creation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6End-to-End Services Over Mixed Topologies . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Service Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

1. Add the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72. Configure Service Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73. Select the Service Endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84. Configure Service Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85. Configure Other Service Characteristics. . . . . . . . . . . . . . . . . . . . . . . 4-96. Select the Path for End-to-End Services. . . . . . . . . . . . . . . . . . . . . . . 4-97. Activate the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Before You Start Creating Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Chapter 2Common Procedures for Services

For Strict Services, Configure the Path Through the Network . . . . . . . . . . . . 4-14Activate or Deactivate a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Duplicate a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Chapter 3Creating SONET Services

Examples of SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Other SONET Services and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Cards Required to Create SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Before You Create SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22VT/TU Switch Card Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23VTX/VCX Integrated Card Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23


Traverse Provisioning Guide, Section 4 Creating ADM Services

Guidelines to Provision a SONET VT-Mux Service . . . . . . . . . . . . . . . . . . . . . 4-24Payload Mapping Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Endpoints for STS Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Endpoints for VT1.5 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26Endpoints for SONET VT-MUX Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28Endpoints for SONET Services on EoPDH Cards. . . . . . . . . . . . . . . . . . . . . . 4-28

Endpoints for SONET Services on EoPDH Cards . . . . . . . . . . . . . . . . . . 4-28Starting STS Numbers for SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31Search for Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32Create a SONET Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35

Chapter 4Creating SDH Services

Mixed Payloads with High Order Path Protection . . . . . . . . . . . . . . . . . . . . . . 4-42Low Order Services with Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43Multiplexing Mixed Traffic onto a VC-4 Transport Path . . . . . . . . . . . . . . . . . . 4-44Cards Required to Create SDH Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45Other SDH Services and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45Before You Create SDH Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46VT/TU 5G Switch Card SDH Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47VTX/VCX Integrated Switching Card SDH Guidelines . . . . . . . . . . . . . . . . . . 4-47Guidelines to Provision an SDH VC-Mux Service . . . . . . . . . . . . . . . . . . . . . . 4-48Payload Mapping Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48Endpoints for VC3 and VC4 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49Endpoints for SDH VC-MUX Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50Endpoints for VC11 and VC12 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50Endpoints for SDH Services on EoPDH Cards . . . . . . . . . . . . . . . . . . . . . . . . 4-52Starting AUG1 Numbers for VC-3 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54Starting AUG1 Numbers for VC-4 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54Search for Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55Create an SDH Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58Create an SDH Endpoint or Tunnel Service . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64Create an SDH Transport Path Hop-by-Hop . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70Create an SDH Transport Path End-to-End . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70

Chapter 5Creating 2-Port OC-48/STM-16 Services

Slot-to-Slot Switching Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72Guidelines to Provision Protected Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72Protection Groups using the 2-port OC-48/STM-16 Card . . . . . . . . . . . . . . . . 4-73Protected Services from a 2-port OC-48/STM-16 to a Protected OC-192/ STM-64 Uplink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73Aggregated Services from OC-48 UPSRs to OC-192 Uplinks . . . . . . . . . . . . 4-75Guidelines to Create an Aggregate Service from a Subtended OC-48 UPSR 4-76


SECTION 4CREATING ADM SERVICES

Chapter 1Service Provisioning Concepts

Introduction Creating services in a Traverse network requires that you first identify switching requirements, bandwidth requirements, and service types. This chapter explains the particulars of services on a Traverse platform: • Traverse Services Definition, page 4-1• Supported Features, page 4-1• Transport Capacity, page 4-3• Traverse Service Types, page 4-4• Service Creation Models, page 4-6• End-to-End Services Over Mixed Topologies, page 4-6• Service Creation Process, page 4-7• Before You Start Creating Services, page 4-10

If your system includes 2-port OC-48 cards, see Chapter 5—“Creating 2-Port OC-48/STM-16 Services,” page 4-71 for additional information.

Traverse Services Definition

A service in a TransNav managed network connects traffic from a source to a destination. The source can be a port, subport, channel, or path. The source originates on any card.

The destination of the service varies depending on the connection you are creating. The destination can be a compatible card, port, subport, or another service. Additionally, the destination can be on the same node or on a separate node.

There are three types of services on a Traverse system: regular SONET, Ethernet, or VC-Bundle for transport of Ethernet services.

Supported Features

DS3 Transmux

Transmultiplexing functionality is provided by the Traverse DS3/EC-1 Transmux card. This capability is important in applications where incoming traffic is channelized DS3 and the payload of the outgoing circuit needs to be VT-mapped, such as those that are handed off to the Traverse switch fabric.


Traverse Provisioning Guide, Section 4: Creating ADM ServicesSupported Features

Bridging and Rolling

The Traverse system supports transferring services from one facility to another without dropping traffic. See the Traverse Provisioning Guide, Section 5—Creating Service Applications, Chapter 2—“Bridging and Rolling Services,” page 5-13.

Multicast Connections

Multicast connections are connections made from one source to multiple destinations. The Traverse system supports multicast connections for the following services:• SONET-STS• SONET-VT• Ethernet• SDH-VC4• SDH-VC3

Use multicast connections to create drop-and-continue services in a network of Traverse nodes.

Optical Transmux

The Transmux component also transparently provides this transmux capability when traffic ingresses and egresses the Traverse system using an optical interface. In this case, the Transmux component receives incoming DS1/E1-mapped DS3s from the Traverse backplane and converts the outgoing signal to VT-mapped STS-1s or VC-mapped AU-3s.

Resource Advisory

If this feature is enabled, the system displays only available resources. Ports, paths, endpoints, and other resources assigned to activated services appear in the graphical user interface with an asterisk (*). The system also displays available capabilities for resource limitations, such as [DS1 / VT Capable].

SDH to SONET Interworking

The Traverse platform supports SDH to SONET interworking capabilities. That is, you can connect an SDH signal to a SONET signal.

The Traverse supports the following gateway services:• DS1 over SDH• E1 over SONET• SDH to SONET• SONET to SDH

VT/VC Switching

Force10 offers two options to switch traffic at the VT/VC levels:• VT/TU 5G Switch card• VTX/VCX integrated cards


Chapter 1 Service Provisioning ConceptsTransport Capacity

See the Traverse Product Overview Guide, Section 3—Card (Module) Descriptions, Chapter 7—“VT/VC Switching Cards” for detailed descriptions of these VT/VC switching options.

Transport Capacity

In a TransNav managed network, you can switch traffic at different levels of the optical hierarchy. • In SONET, you can switch traffic at the VT layer, at the STS layer, or at the

concatenated STS layers. • In SDH, you can switch traffic at the low order virtual container (LOVC) layers, at

the high order VC-3, or at the concatenated VC (VC-3-nc or VC-4-nc) layers.

Use the following table as a reference for the transport requirements of each supported service.

Table 4-1 Transport Capacity

PayloadTransport STS-1 OC-3 OC-12 OC-48 OC-192

Mbps 51.84 155.52 622.08 2488.32 9953.28

DS1 or VT 1.5

1.544 28 84 336 1344 5376

DS3 44.736 1 3 12 48 192

E1 or VT 2

2.048 21 63 252 1008 4032

E3 34.368 1 3 12 48 192

VT 1.728 28 84 336 1344 5376

VC-12 2.304 21 63 252 1008 4032

STS-1 48.960 1 3 12 48 192

STS-3c 150.336 — 1 4 16 64

STS-12c 599.040 — — 1 4 16

STS-48c 2,396.160 — — — 1 4

Ethernet 100 or 1000 481 Mbps

1 On a virtually concatenated VC-3 (VC-3-nv), n times 48 but no greater than 1000.

1492 Mbps

2 On a virtually concatenated VC-4 (VC-4-nv), n times 149, but no greater than 1000.

599 Mbps 1000 Mbps 1000 Mbps


Traverse Provisioning Guide, Section 4: Creating ADM ServicesTraverse Service Types

Traverse Service Types

The Traverse supports the following types of services:• ADM Service Types, page 4-4• Ethernet Services, page 4-4

Table 4-2 ADM Service Types

Service Type Definition and Reference

See either of the following references for details on the following service types:• Chapter 4—“Creating SDH Services,” page 4-41• Chapter 3—“Creating SONET Services,” page 4-19

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.

SONET Use this service to transport synchronous traffic through the network. Also, use this service as a regular cross-connect when creating a transport path hop-by-hop through the network.

Table 4-3 Ethernet Services


See the Traverse Provisioning Guide, Section 7—Configuring Ethernet for guidelines and procedures on creating Ethernet services.

Line An Ethernet line service is a forwarding relationship between two endpoints on the same card. Use this service to create a dedicated point-to-point service, a shared point-to-point service, or an internet access application.


Chapter 1 Service Provisioning ConceptsTraverse Service Types

Bridge A bridge service is a forwarding relationship between an arbitrary number of endpoints on the same card. Any of the endpoints can be shared (by VLAN ID) with other services. Within a single bridge service, a packet is forwarded to one endpoint or to all endpoints using standard MAC address forwarding rules. Use this service to create a Virtual LAN Service application in the network.

Aggregation Bridge An aggregation bridge service is a hybrid of a line service and a bridge service. It is a forwarding relationship between a set of endpoints on a card, where one endpoint is considered the aggregation port and the other endpoints are considered ordinary members of the service.

Traffic received on the aggregation port is forwarded just as in a bridge service – to one or more ordinary members based on the destination MAC address. Traffic received on the ordinary members of the service is forwarded directly to the single aggregation port.

Table 4-3 Ethernet Services (continued)



Traverse Provisioning Guide, Section 4: Creating ADM ServicesService Creation Models

Service Creation Models

You can create services in a Traverse network either end-to-end or hop-by-hop. You can create services in a TraverseEdge network hop-by-hop only.

An end-to-end service is a service you can set up between nodes. You select the source of a service on one node and the destination on another. The system sets up the path (including the alternate path if the service is protected) through the domain.

Figure 4-1 End-to-End Services Creation Model

A hop-by-hop service is a service that you configure between two cards or two ports on one node. That is, you select the source and destination endpoints on one node only.

Figure 4-2 Hop-by-Hop Services Creation Model

If you create a transport path end-to-end through the network, you can monitor only the endpoints. If you create a transport path hop-by-hop through the network, you can add or drop traffic at each hop, or monitor performance and alarms.

End-to-End Services Over Mixed Topologies

The TransNav management system supports creating uni- and bi-directional end-to-end services over the following topologies:• up to four single-node interconnected UPSR or SNCP rings• single-node interconnected UPSR and 1+1 APS linear chains• single-node interconnected SNCP rings and 1+1 MSP linear chains• up to three interconnected BLSRs or MS-SPRings• single-node interconnected BLSR and 1+1 MSP linear chains• single-node interconnected MS-SPRings and 1+1 MSP linear chains• single-node interconnected BLSR, UPSR, and 1+1 APS linear chains• single-node interconnected MS-SPRings, SNCP rings, and 1+1 MSP linear chains

See the Traverse Product Overview Guide, Section 5—Planning and Engineering, Chapter 4—“Protected Network Topologies,” page 5-33 for information on network topologies.

Trib

utar

y C

ard

Trun

k C

ard

Trun

k C

ard

Trun

k C

ard

Trun

k C

ard

Trib

utar

y C

ardIntermediate

node(Node 2)

Endpointnode

(Node 1)

Intermediatenode

(Node 3)

Constraints(Loose, Partial-Strict, Strict)Source

1-2 2-1 2-2 3-21-1 43-1

Trib

utar

y C

ard

Trun

k C

ard

Trun

k C

ard

Trun

k C

ard

Trun

k C

ard

Trib

utar

y C

ard

Intermediatenode

Endpointnode

Endpointnode

Source Destination Source Destination Source Destination


Chapter 1 Service Provisioning ConceptsService Creation Process

Service Creation Process

1. Add the Service.

On the Service tab, select the service type and click Add.

2. Configure Service Parameters.

Enter the name of the service and configure other general parameters.

1

2


Traverse Provisioning Guide, Section 4: Creating ADM ServicesService Creation Process

3. Select the Service Endpoints.

Set the endpoints for this service. Click the Source row in the Endpoint column to display the Choose an Endpoint dialog box. Select the source and click Done to close the dialog box.

Click the Destination row, select the endpoint in the dialog box and click Done.

4. Configure Service Protection.

Click the Protection parameter field to display the Protection dialog box. Select the type of protection for the service by clicking on the tabs in the dialog box.

Configure any applicable parameters.

Click Done to close the dialog box and return to the Create Service tab.

3

4


Chapter 1 Service Provisioning ConceptsService Creation Process

5. Configure Other Service Characteristics.

Click the Advanced button to display the Advanced Parameters dialog box.

Configure the characteristics of the service.

If this is an end-to-end service, configure the characteristics of the connection throughout the network.

6. Select the Path for End-to-End Services.

If Strict= , explicitly select the service route between defined endpoints.

Click the plus sign in the Add column to add another hop to the service.

Click the minus sign in the Remove column to remove a hop.

Click Apply to add the provisioned service to the service list and return to the Service tab.

5

6


Traverse Provisioning Guide, Section 4: Creating ADM ServicesBefore You Start Creating Services

Before You Start Creating Services


7. Activate the Service.

On the Service tab, click the service to select it, right-click for the menu, and click Activate.

7



Hardware





Software









Chapter 1 Service Provisioning ConceptsBefore You Start Creating Services



Traverse Provisioning Guide, Section 4: Creating ADM ServicesBefore You Start Creating Services



Chapter 2Common Procedures for Services

Introduction This chapter contains procedures for the following topics:• For Strict Services, Configure the Path Through the Network, page 4-14• Activate or Deactivate a Service, page 4-16• Duplicate a Service, page 4-17

See the TransNav Management System GUI Guide for explanations of each screen.

If your system includes 2-port OC-48 cards, refer to Chapter 5—“Creating 2-Port OC-48/STM-16 Services,” page 4-71 for additional information.


Traverse Provisioning Guide, Section 4: Creating ADM ServicesFor Strict Services, Configure the Path Through the Network

For Strict Services, Configure the Path Through the Network

Use this procedure to specify a path through the network for end-to-end services. This procedure is optional.

Table 4-5 Configure the Path Through the Network

Step Procedure

1 Complete one of the following procedures: • Create an SDH Service, page 4-58• Create a SONET Service, page 4-35

2 On the Create Service tab, select Strict.

Figure 4-3 Configure a Strict Path Through the Network

3 Add additional rows to the Endpoint table for each hop in the network. Click the plus sign (+) in the Add column.• Add one row to specify where the service exits the source node.• Add two rows for each pass-through node (ingress and egress paths).• Add one row to specify the slot and port where the service enters the

destination node.

3

2


Chapter 2 Common Procedures for ServicesFor Strict Services, Configure the Path Through the Network

4 Select the endpoints according to the network plan.

Figure 4-4 Choose the Path Endpoints

a. Click a row in the Endpoint column to display the Choose an Endpoint dialog box.

b. Navigate the tree and select the correct endpoint. c. Click Done to close the dialog box and return to the Create Services

tab on the main screen.d. Repeat for each hop in the network.

5 Click Apply to save this configuration and return to the services list on the Service tab.

6 The Configure the Path Through the Network procedure is complete.

Continue to the procedure Activate or Deactivate a Service, page 4-16.

Table 4-5 Configure the Path Through the Network (continued)

Step Procedure

4a

4b

4c


Traverse Provisioning Guide, Section 4: Creating ADM ServicesActivate or Deactivate a Service

Activate or Deactivate a Service

Use this procedure to activate or deactivate one service or multiple services.

Table 4-6 Activate or Deactivate a Service

Step Procedure

1 Complete the procedure Create a SONET Service, page 35.

2 On the Service tab, complete Step 3 and Step 4.

Figure 4-5 Service Tab—Activate

3 Click a Service from the list.

Hold the Ctrl key and click individual services.

OR

Hold the Shift key and click a range of services.

4 Right-click and select Activate to start the connection carrying traffic.

OR

Right-click and select Deactivate to stop the connection from carrying traffic.

5 The Activate or Deactivate a Service procedure is complete.

34


Chapter 2 Common Procedures for ServicesDuplicate a Service

Duplicate a Service

Use this procedure to create similar services quickly.

Table 4-7 Duplicate a Service

Step Procedure

1 On the Service tab, select a service from the service list.

Figure 4-6 Duplicate a Service

2 Right-click and select Duplicate from the menu to display the Duplicate Service dialog box.

Figure 4-7 Duplicate Service Dialog Box

3 On the Duplicate Service dialog box, click the plus sign in the Add column to add new services to the list.

Add as many rows as you need for new services.

Figure 4-8 Add a New Row for Each New Service

1

2

3

4

6


Traverse Provisioning Guide, Section 4: Creating ADM ServicesDuplicate a Service

4 Click a row in the Service Name column and enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

5 Repeat Step 4 for each new service.

6 Click Apply to save the changes. The Status column changes from Ready to Succeeded.

7 Click Done to close the dialog box and return to the service list on the Service tab.

Figure 4-9 Click Apply and Then Click Done

8 On the Service tab, find and select one of the new services.

9 Right-click and select Edit from the menu.

10 On the Create Service tab, select new endpoints for the service.

11 Click Apply to save the changes and return to the service list on the Service tab.

12 Repeat Steps 8 through 11 for each duplicated service.

13 The Duplicate a Service procedure is complete.

Continue to the procedure Activate or Deactivate a Service, page 4-16 to activate the new services.

Table 4-7 Duplicate a Service (continued)

Step Procedure

7



Chapter 3Creating SONET Services

Introduction This chapter explains how to create the following service types in a Traverse network:• SONET-STS: Use this service to transport synchronous traffic through the

network. Use this service to create a transport path for either synchronous or Ethernet traffic through the network.

• SONET-VT1.5: Use this service to switch individual SONET VT1.5 payloads through the network.

Note: VT services are available on all cards except the GE cards.

This chapter includes the following topics:• Examples of SONET Services, page 4-20• Cards Required to Create SONET Services, page 4-21• Before You Create SONET Services, page 4-22• Endpoints for STS Services, page 4-24• Guidelines to Provision a SONET VT-Mux Service, page 4-24• Payload Mapping Parameter, page 4-24• Endpoints for VT1.5 Services, page 4-26• Endpoints for SONET Services on EoPDH Cards, page 4-28• Starting STS Numbers for SONET Services, page 4-31• Search for Services, page 4-32• Create a SONET Service, page 4-35



Traverse Provisioning Guide, Section 4: Creating ADM ServicesExamples of SONET Services

Examples of SONET Services

Use a combination of service types to create end-to-end SONET services or switch individual VT1.5 payloads in a Traverse network.• SONET-STS: This service transports ATM traffic (STS-3c) from an ATM

multiplexer to an ATM switch on the far end.• DS3-CC: This service connects a clear channel DS3 to a digital cross-connect

system for switching into the network.• DS3-Tmx: This service adapts channelized DS3 traffic into a VT-mapped STS for

transport over a SONET network to a far-end TransAccess 100 Mux.• SONET-STS: This service cross-connects the VT-mapped STS from Node 1 to

Node 3.• SONET-VT 1.5: This service connects a VT (channelized DS3 from Node 1) to an

EC1 port that has a TransAccess 100 Mux connected.• VT-MUX: This service combines incoming channelized VT-mapped payloads into

a single STS-1 container from an EoPDH card to electrical or optical cards on a Traverse node.

Figure 4-10 SONET-STS and SONET-VT Services

Node 1 Node 2 Node 3

OC48 Link OC48 Link

5

OC3 TMXVT

Switch OC12OC48 OC48 OC48 TMXDS3

1. End-to-End (STS-3c)

3

4

2

M13

Slot 2 Slot 3 Slot 6 Slot 8Slot 8Slot 2Slot 14Slot 8Slot 4

ATM MUX

M13

1. Service Type: SONETBandwidth: STS-1Setup Type: LooseSrc: Node 1- slot 4-port 1-OC3-STS 1Dest: Node 3-slot 8-port 1-OC12-STS 1

3. Service Type: SONET (HOP 1)Bandwidth: STS-1Src: Node 1- slot 8-port 6-DS3TMXDest: Node 1-slot 14-port 1-OC48-STS 3

2. Service Type: SONETBandwidth: STS-1Src: Node 1- slot 8-port 9-DS3CCDest: Node 2-slot 8-port 9-DS3CC

4. Service Type: SONET (HOP 2)Bandwidth: STS-1Src: Node 2- slot 2-port 1-OC48-STS 3Dest: Node 2-slot 14-port 1-OC48-STS 3

STS-1/T1 Mux

5. Service Type: SONET (HOP3)Bandwidth: VT1.5Src: slot 2-port 1-OC48-STS 3-VTG1-VT1Dest: slot 6-port 5-EC1-STS 1-VTG5-VT2

OC48Slot 14

TR 00056


Chapter 3 Creating SONET ServicesCards Required to Create SONET Services

Other SONET Services and Applications

Use the procedures in the following chapters to configure other SONET services or applications: • Section 5—Creating Service Applications, Chapter 1—“Creating 1+1 Path

Protected Services,” page 5-1• Section 5—Creating Service Applications, Chapter 3—“Creating

Drop-and-Continue Services,” page 5-19• Section 5—Creating Service Applications, Chapter 5—“Creating Transmux

Services,” page 5-33• Section 5—Creating Service Applications, Chapter 4—“Creating Services over

Interconnected UPSR or SNCP Rings,” page 5-25• Section 5—Creating Service Applications, Chapter 6—“Creating Transparent

Services,” page 5-49• Section 7—Configuring Ethernet, Chapter 4—“Ethernet Over SONET/SDH

(EOS),” page 7-49

Cards Required to Create SONET Services

This table lists the Traverse cards required to create SONET services.

Table 4-8 Cards Required for SONET Services

Service Type Source Cards Destination Cards

SONET DS1DS3/E3/EC1 Clear ChannelDS3/EC1 TransmuxOC-NEC3

DS1DS3/E3/EC1 Clear ChannelDS3/EC1 TransmuxOC-NEC3

STM-NE1

SONET DS1DS3/E3/EC1 Clear ChannelDS3/EC1 TransmuxOC-NEC3

EoPDH (EOP ports only)

Other cards

VT/TU 5G Switch (for VT1.5 services)

n/a n/a

Any card with the VTX/VCX component (for VT1.5 services)


Traverse Provisioning Guide, Section 4: Creating ADM ServicesBefore You Create SONET Services

Before You Create SONET Services

Review the information in this topic before you create any SONET services.

Table 4-9 SONET Service Requirements


Read the information in Section 1—Configuring the Network, Chapter 1—“Traverse Provisioning Over-view,” page 1-7

Hardware

You need a combination of the cards to create SONET services. See Cards Required to Create SONET Services, page 4-21 for a breakdown of required cards for specific services.


Software

Nodes are commissioned. Traverse Installation and Commissioning Guide, Section 11—Node Start-up and Commissioning Pro-cedures, Chapter 1—“Node Start-up and Commis-sioning,” page 11-1




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

Traverse Provisioning Guide, Section 3—Creating Protection Groups

Source (tributary) and destination (transport) interfaces are configured correctly.

Traverse Provisioning Guide, Section 2—Configur-ing TDM Equipment

If a VT/TU 5G Switch card is present in the shelf, review the guidelines.

VT/TU Switch Card Guidelines, page 4-23

If a VTX/VCX integrated component card is present in the shelf, review the guidelines.

VTX/VCX Integrated Card Guidelines, page 4-23

These procedures describe how to create a spe-cific service and change only configurable param-eters. See the TransNav Management System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide, Section 2—Services, Chapter 2—“SONET Ser-vices,” page 2-15

Interworking. Support for ETSI to ANSI inter-working:• SDH to SONET• SONET to SDH

Traverse Provisioning Guide, Section 4—Creating ADM Services, Chapter 3—“Creating SONET Ser-vices,” Cards Required to Create SONET Ser-vices, page 4-21


Chapter 3 Creating SONET ServicesVTX/VCX Integrated Card Guidelines

VT/TU Switch Card Guidelines

Use the following guidelines if the VT/TU 5G Switch card is present in the shelf configuration:• The VT/TU 5G Switch has a termination capacity of 32 OC-3s. It can support up to

1008 bi-directional E1/VC12 services or 1344 bi-directional DS1/VC11 services.• Force10 recommends reserving the equivalent of at least sixteen OC-3s for traffic

leaving the node.• Use the VT/TU 5G Switch if you are mixing low order traffic and high order traffic

on the same AU-4. Specifically, use the VT/TU 5G Switch when at least one of the TUG3s in the AU-4 contains a TUG2 payload.

• If the transport path is carrying low order payloads, configure the container type for VC Grooming.

• If the VT/TU 5G Switch is in an equipment protection group, specify the one which is active.

VTX/VCX Integrated Card Guidelines

Use the following guidelines if a VC cross-connect (VCX) integrated component card is present in the shelf configuration:• The VCX hardware has a termination capacity of 16 STM-1s. It can support up to

504 bi-directional E1/VC12 services or 672 bi-directional DS1/VC11 services.• Force10 recommends reserving the equivalent of at least eight STM-1s for traffic

leaving the node.• Use the VCX card if you are mixing low order traffic and high order traffic on the

same AU-4. Specifically, use the VCX when at least one of the TUG3s in the AU-4 contains a TUG2 payload.


• If the VCX is in an equipment protection group, specify the VCX which is active.

Provisioning model • SONET-STS: end-to-end OR hop-by-hop• SONET-VT1.5: hop-by-hop only

Traverse Provisioning Guide, Section 4—Creating ADM Services, Chapter 1—“Service Provisioning Concepts,” Service Creation Models, page 4-6

Bandwidth requirements• STS-1: 48.960 Mbps• STS-3c: 150.336 Mbps• STS-12c: 599.040 Mbps• STS-48c: 2, 396.160 Mbps• SONET VT: 1.728 Mbps

Traverse Provisioning Guide, Section 4—Creating ADM Services, Chapter 1—“Service Provisioning Concepts,” Transport Capacity, page 4-3

Table 4-9 SONET Service Requirements (continued)



Traverse Provisioning Guide, Section 4: Creating ADM ServicesGuidelines to Provision a SONET VT-Mux Service

Guidelines to Provision a SONET VT-Mux Service

The guidelines to provision a SONET VT-Mux service are:• The source and destination endpoints must be on cards located on the same node.• One end of the service must terminate on an EoPDH card.• For EOP functions, the VT-Mux service must terminate on one of the first 12 STS

endpoints to generate usable endpoints. EoPDH cards restrict low-order connection termination points for use on DS1 cards to reside only in the first 12 STSs of the card’s VOP.

• For EOS functions, the VT-Mux service must terminate on one of the first 24 STS endpoints to generate usable endpoints. This is due to the restriction on EoPDH cards requiring low-order connection termination points to reside only in the first 24 STSs of the card’s VOP.

Payload Mapping Parameter

The Payload Mapping parameter is used on high-order SONET STS services to allow the system to consider the activated service a clear-channel container with no sub-containers.

When the Payload Mapping parameter is set to STS-1 on SONET STS services, the service is considered a clear-channel container with no lower level VT sub-containers. When the parameter is set to VT1.5, Traverse recognizes the low-level VT sub-containers as individual endpoints on the STS-1. The service endpoint on the EoPDH card is treated as 28 VT1.5 endpoints for use in an EOS or EOP port.

Endpoints for STS Services

The following table lists valid sources and destinations for STS services for the following cards: NGE, NGE Plus, 10GbE, and GbE-10. Your network may require creating multiple services at multiple nodes.

Note: For information on the valid sources and destinations for SONET services on EoPDH cards, see Endpoints for SONET Services on EoPDH Cards, page 4-28.


Chapter 3 Creating SONET ServicesEndpoints for STS Services

The Traverse system supports multicast STS connections for 1+1 path-protected and drop-and-continue services.

Table 4-10 Endpoints for STS Services

Sources Destinations

Port Type Mapping Port Type Mapping

OC-N1 node/slot/port/sts STM-N (HO - high order)STM-N (LO - low order)

all ports E1 card

OC-NEC1DS3CCDS3TMXall ports DS1 card

node/slot/port/aug1/node/slot/port/aug1/vc3node/slot/port/aug1/tug3/vc3node/slot

node/slot/port/stsnode/slot/port/stsnode/slot/portnode/slot/portnode/slot/portnode/slot

EC1 node/slot/port STM-N (HO)STM-N (LO)

OC-NEC1DS3CC

node/slot/port/aug1/node/slot/port/aug1/vc3node/slot/port/aug1/tug3/vc3

node/slot/port/stsnode/slot/port/stsnode/slot/portnode/slot/port

DS3CC node/slot/port STM-N (HO)STM-N (LO)

OC-NEC1DS3CC



DS3TMX node/slot/port STM-N (HO)STM-N (LO)

OC-N


node/slot/port/stsnode/slot/port/sts

All ports on a DS1 card

node/slot STM-N (HO)STM-N (LO)

OC-N




Traverse Provisioning Guide, Section 4: Creating ADM ServicesEndpoints for VT1.5 Services

Endpoints for VT1.5 Services

The following table lists valid sources and destinations for VT1.5 services. Your network may require creating multiple services at multiple nodes.

There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create this service.

Note: The maximum switching capacity of NGE and NGE Plus cards is 5 Gbps, however, this is restricted to high order switching. The following restrictions exist for low order switching. • A SONET VT1.5 service cannot be provisioned if the either source or destination

termination point of the service is one of the following VT1.5 connection termination points (CTPs) on an NGE card. Any VT in VTGx or STSy where:x = 3, 4, 5, 6, 7 andy = 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42, 45, 48

SONET port on backplane for EOS ports

node/slot (Ethernet card)/sts

OC-N

Any Ethernet card on a different node

node/slot/port/sts


SONET port on backplane for EOP ports


OC-N node/slot/port/sts

1 For STS services between OC-192 ports, the source STS number and the destination STS number must in the same range when the range is between 1 and 48, or 49 and 192. For example, if the source STS is STS number 12, the destination STS must be between STS number 1 and 48. If the source STS is STS number 105, the destination STS must be between STS number 49 and 192.

Table 4-10 Endpoints for STS Services (continued)




Chapter 3 Creating SONET ServicesEndpoints for VT1.5 Services

• A VT1.5 CTP cannot be added from the OC-48 VOP to an EOS port on the same NE card if the endpoint is one of the following VT1.5 CTPs: Any VT in VTGx or STSy where:x = 3, 4, 5, 6, 7 andy = 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42, 45, 48

Table 4-11 Endpoints for VT1.5 Services



OC-N node/slot/port/sts/vtg/vt STM (HO - high order)1

STM (LO - low order)1

E1

OC-NEC1DS3TMX2

DS1

1 There must be an SDH-Endpoint or SDH-Tunnel service already with a Bandwidth of VC (Grooming) configured on the port.

2 Port is DS1-mapped (DS3 Mapping parameter is DS1).

node/slot/port/aug1/tug3/tug2/vc11node/slot/port/aug1/vc3/tug2/vc11node/slot/port

node/slot/port/sts/vtg/vtnode/slot/port/sts/vtg/vtnode/slot/port/sts-1/vtg/vtnode/slot/port/subportnode/slot/port

EC1 node/slot/port/sts-1/vtg/vt STM (HO)1

STM (LO)1

E1

OC-NEC1DS3TMXDS1


node/slot/port/sts/vtg/vtnode/slot/port/sts-1/vtg/vtnode/slot/port/subportnode/slot/port

DS3TMX2 node/slot/port/subport STM (HO)1

STM (LO)1

E1

OC-NEC1DS3TMX2

DS1

node/slot/port/aug1/tug3/tug2/lo vc3

node/slot/port/aug1/vc3/tug2/lo vc3

node/slot/port


3 lo vc is VC11 or VC12.

DS1 node/slot/port STM (HO)1

STM (LO)1

E1

OC-NEC1DS3TMX2

DS1



node/slot/port



node/slot (Ethernet card)/sts/vtg/vt

OC-N

Any Ethernet card on a different node.

node/slot/port/sts/vtg/vt



Traverse Provisioning Guide, Section 4: Creating ADM ServicesEndpoints for SONET VT-MUX Services

Endpoints for SONET VT-MUX Services

The following table lists the source and destination endpoint requirements to create SONET VT-Mux services.

Endpoints for SONET Services on EoPDH Cards

The tables in the following sections list valid sources and destinations for STS, VT1.5, and EOP bi-directional services on EoPDH cards. The EOP interface for each example is a virtual optical port (VOP). Your network may require creating multiple services at multiple nodes.

Note: An EoPDH card in SONET mode does not support SONET/SDH services to E1/E3 interfaces. Conversely, an EoPDH card in SDH mode does not support SONET/SDH services to DS1/DS3 interfaces.

Endpoints for SONET Services on EoPDH Cards. The following table lists valid sources and destinations for services on EoPDH cards provisioned in SONET mode. The Traverse system supports multicast STS connections for 1+1 path-protected and drop-and-continue services.

Table 4-12 Endpoints for SONET VT-Mux Services

Service Type Source - Endpoint(available range)

Destination Endpoint Type Bandwidth Payload

Mapping Set to

SONET EoPDH - STS(1 to 24)

STS VT-Mux 1 STS Yes VT1.5

EoPDH - STS(1 to 12)

DS3-Tmx DS3-Tmx 1 DS3 No N/A1


DS1 (all ports) DS1-Mux 28 VT No N/A

1 Not applicable

Table 4-13 Endpoints for SONET Services on EoPDH Cards

Interface and Payload Mapping on Source Card SONET Service TypePayload Mapping on EoPDH

Destination Card (all interfaces are VOP)

LinePort Type (Interface

)

Interface CTP type

(CLI)

Payload on Interface

SONET Service

Type (CLI)

SONET Service

Bandwidth

EoPDH CTP Type

Payload on EoPDH CTP

1 DS1 port DS1 DS1 DS1 VT1.51 VT1.5 DS1 in VT1.5

2 VT1.5 VT1.51 VT1.5 DS1 in VT1.5

3 All 28 ports on a DS1 card

CARD-STS All 28 DS1s on DS1 card

DS1-MUX STS STS 28 x (DS1 in VT1.5)


Chapter 3 Creating SONET ServicesEndpoints for SONET Services on EoPDH Cards

4 DS3-CC DS3 DS3 DS3-CC STS2 STS DS3 in STS

5 DS3-TMX TMX_DS1 DS1 structured DS3

DS1 VT1.51 VT1.5 DS1 in VT1.5

6 DS1_TMX VT1.5 VT1.51 VT1.5 DS1 in VT1.5

7 DS3_TMX DS3-TMX STS STS 28 x (DS1 in VT1.5)

8 EC1 VT1.5 DS1 mapped VT1.5 (in STS)

VT1.5 VT1.51 VT1.5 DS1 in VT1.5

9 VT1.5 struc-tured STS

VT1.5 VT1.51 VT1.5 VT1.5

10 STS DS1 mapped VT1.5 (in STS)

VT-MUX STS STS 28 x (DS1 in VT1.5)

11 STS VT1.5 struc-tured STS

VT-MUX STS STS (28 x VT1.5) in STS

12 EC1 DS3 mapped STS

STS STS2 STS DS3 in STS

13 EC1 STS STS STS2 STS STS

14 OC-N VT1.5 DS1 structured DS3 (in STS)

VT1.5 VT1.51 3 VT1.5 DS1 in VT1.5

15 OC-N / VOP4

VT1.5 DS1 mapped VT1.5 (in STS)

VT1.5 VT1.51 VT1.5 DS1 in VT1.5

16 VT1.5 struc-tured STS5

VT1.5 VT1.51 VT1.5 VT1.5

17 STS DS1 mapped VT1.5 (in STS)

VT-MUX STS STS 28 x (DS1 in VT1.5)

18 VT1.5 struc-tured STS

VT-MUX STS STS 28 x VT1.5

19 DS1 mapped VT1.5 (in STS)

STS STS3 STS 28 x (DS1 in VT1.5)

20 DS3 mapped STS

STS STS2 STS DS3 in STS

21 STS5 STS STS2 STS STS

22 STS-3C5 STS STS-3C2 STS STS-3C

1 A VT Switch Module is required in the same chassis.

Table 4-13 Endpoints for SONET Services on EoPDH Cards (continued)




)

Interface CTP type

(CLI)


SONET Service

Type (CLI)

SONET Service

Bandwidth

EoPDH CTP Type



Traverse Provisioning Guide, Section 4: Creating ADM ServicesEndpoints for SONET Services on EoPDH Cards

2 For end-to-end services, the two cards of the service (EoPDH and another card) can be in different nodes.

3 Optical Transmux services require a DS3TMX card in the same chassis with a STS-TMUX port assigned to the service.

4 Source cards with VOP can be EoPDH.

5 Cards with VOP can be NGE, 10GbE, or GbE-10.


Chapter 3 Creating SONET ServicesStarting STS Numbers for SONET Services

Starting STS Numbers for SONET Services

The starting STS number for any SONET service depends on the required bandwidth. For example, an OC-48 interface has a Src. Starting STS range of 1 through 48 if you select STS-1 in the Bandwidth parameter. If you select STS-12c in the Bandwidth parameter, the Source Starting STS can be 1, 13, 25, or 37. The following table lists all of the valid starting STSs. The following table lists all the valid starting STS numbers.

For SONET service between OC-192 ports, the Src. Starting Sts and the Dest. Starting Sts must in the same range when the range is between 1 and 48 or 49 and 192. For example, if the Src. Starting Sts is 12, the Dest. Starting Sts must be between STS number 1 and 48. If the Src. Starting Sts is 105, the Dest. Starting Sts must be between STS number 49 and 192.

Table 4-14 Valid Starting STS

BandwidthStarting STS

EC1 OC-3 OC-12 OC-48 OC-192

STS-1 1 1, 2, 3 1, 2, 3, 4,... 12 1, 2, 3, 4,... 48 1, 2, 3, 4,.. 192

STS-3c — 1 1, 4, 7, 10 1, 4, 7, 10, 16, 19,... 48

1, 4, 7, 10, 16, 19,... 190

STS-12c — — 1 1, 13, 25, 37 1, 13, 25, 37, 49,... 181

STS-48c — — — 1 1, 49, 97, 145


Traverse Provisioning Guide, Section 4: Creating ADM 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 4-15 Search for Services

Step Procedure

1 Review the information in the topic Before You Begin, page 7-137.

2 From Map View or Shelf View, click the Service tab.

Figure 4-11 Select the Service Tab

2

3 45


Chapter 3 Creating SONET ServicesSearch for Services

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 (p0). This refers to the OC-48 interface on the backplane.

• 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

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

Table 4-15 Search for Services (continued)

Step Procedure



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.

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.

Figure 4-12 Service Tab, Page Button

7 The Search for Services procedure is complete.


Step Procedure

6


Chapter 3 Creating SONET ServicesCreate a SONET Service

Create a SONET Service

Use this procedure to create a SONET service.

Table 4-16 Create a SONET Service

Step Procedure

1 Add the SONET service.

Figure 4-13 Service Tab

a. Click the Service tab.b. From the Add button menu, select SONET.c. Click Add to display the Create Service tab.

2 In the Name parameter, enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

Figure 4-14 Create Service Tab

3 From the Bandwidth parameter, select the total bandwidth for the service: • VT1.5 (does not apply to 10GE cards)• STS-1 (default)• STS-3c (default for 10GE cards)• STS-12c (for OC-12 and greater interfaces only)• STS-48c (for OC-48 and greater interfaces only)

1a

1b

1c

2

3

4

5

10 12


Traverse Provisioning Guide, Section 4: Creating ADM ServicesCreate a SONET Service

4 Choose the endpoints for the service.

Refer to Endpoints for STS Services, page 4-24 as required.

Refer to Endpoints for VT1.5 Services, page 4-26 as required.

Figure 4-15 Choose Endpoints for the Service

a. Click the first row in the Endpoint column to display the Choose an Endpoint dialog box.

b. Navigate the tree and select the correct source endpoint. c. Click Done to close the dialog box and return to the Create Service

tab on the main screen.d. Click the Destination row in the Endpoint column.e. Navigate the tree and select the correct destination endpoint.f. Click Done to close the dialog box and return to the Create Service

tab on the main screen.

Table 4-16 Create a SONET Service (continued)

Step Procedure

4a4b

4c



5 Configure the protection attributes for this service. Click the Protection field to display the Protection dialog box.

Figure 4-16 Protection Dialog Box

In the Protection Type parameter, select one of the following options: • Unprotected (default): Select for services that are either unprotected,

1+1 APS protected, protected with an equipment protection group or with a 1+1 Path Protection group.

• Any: The system finds the best effort of protection through the network. There may be some spans of unprotected links, but the system will create the service.

• Full: The system only creates the service if there is full protection on every transport link in the network.

• 1+1 Path Protected: If this service is protected by another service (two services model).

• UPSR Ingress: If the service is a VT1.5 service and is creating a bi-directional path across two interconnected UPSR rings.

6 For services that have a protection type configured, configure the following parameters:• Revertive (default is not selected): Select the check box to switch

traffic back to the original path once the failure condition no longer exists.

• WTR Time (default is 5): Specifies the amount of time (in minutes) for the system to wait before restoring traffic to the original path once the failure condition no longer exists. Specify a value between 1 and 60 minutes.

If this service is protected by a BLSR, go to Step 7.

If this service is protected by another service (two services path protection model), go to Step 8.


Step Procedure

59



7 If the endpoints of the service are on a BLSR or MS-SP ring, click the MS-SP/BLSR tab and configure the following parameters: • Ring Source Node ID: Select the BLSR Node ID where the traffic on

this path enters the ring.• Ring Destination Node ID: Select the BLSR Node ID where the

traffic on this path exits the ring.

8 For services protected by another service, click the 1+1 Path Protected tab and configure the HoldOffTimer parameter. This parameter applies only if there is also a 1+1 APS/MSP protection group. It 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.

9 On the Protection dialog box, click Done to return to the Create Service tab on the main screen.

Figure 4-17 Click Done on the Protection Dialog Box


Step Procedure

9



10 On the Create Service tab, click Advanced to configure more parameters of the service.

Figure 4-18 Advanced Parameters Dialog Box

For specific definitions of these parameters, see the TransNav Management System GUI Guide, Section 2—Services, Chapter 2—“SONET Services,” Configure Protection Parameters, page 2-25.

To provision a VT-MUX service, continue to Step 11.

To complete the service, skip to Step 12.


Step Procedure



11 Configure the Payload Mapping parameter for VT-Mux services if needed.


Select the desired Payload Mapping parameter type. Valid values are: • STS (default): Indicates the service endpoint on the Ethernet card is

treated as an STS-1 connection termination ports for use in EOS or EOP ports.

• VT1.5: Indicates the service endpoint on the Ethernet card is treated as a set of 28 VT1.5 connection termination ports for use in EOS or EOP ports.

• VT2: (Planned for future release.)

12 Click Done to return to the Create Service tab on the main screen.

The Create a SONET Service procedure is complete.

13 If this is a hop-by-hop service, click Apply to save this configuration and return to the Service tab on the main screen.

Continue to the procedure: Activate or Deactivate a Service, page 4-16.

14 If this is an end-to-end service, continue to the procedure: Configure the Path Through the Network, page 4-14.


Step Procedure



Chapter 4Creating SDH Services

Introduction This chapter explains how to create the following service types in a Traverse network:• SDH: Use this service to transport synchronous traffic through the network. Also,

use this service as a regular cross-connect when creating a transport path hop-by-hop through the network.

• SDH Endpoint: Use this service to create a termination point to multiplex low order traffic into the network. Also use this service to create a transport path hop-by-hop through the network.

• SDH Tunnel: Use this service to create a transport path end-to-end through the network.

This chapter includes the following topics:• Mixed Payloads with High Order Path Protection, page 4-42• Low Order Services with Path Protection, page 4-43• Multiplexing Mixed Traffic onto a VC-4 Transport Path, page 4-44• Cards Required to Create SDH Services, page 4-45• Other SDH Services and Applications, page 4-45• Before You Create SDH Services, page 4-46• VT/TU 5G Switch Card SDH Guidelines, page 4-47• Guidelines to Provision an SDH VC-Mux Service, page 4-48• Endpoints for VC11 and VC12 Services, page 4-50• Endpoints for SDH Services on EoPDH Cards, page -4• Starting AUG1 Numbers for VC-3 Services, page 4-54• Search for Services, page 4-55• Create an SDH Service, page 4-58• Create an SDH Endpoint or Tunnel Service, page 4-64• Create an SDH Transport Path Hop-by-Hop, page 4-70• Create an SDH Transport Path End-to-End, page 4-70



Traverse Provisioning Guide, Section 4: Creating ADM ServicesMixed Payloads with High Order Path Protection

Mixed Payloads with High Order Path Protection

The network in the following example is a STM-16 SNCP ring. Each node that is adding or dropping traffic from the network has either a VCX component or a VT/VC switch card. Each low order switching component is configured in an equipment protection group.

The service creation model is based on SNCP Ring protection.

Figure 4-20 Mixed Payloads with High Order Path Protection

Use the SDH-VC4 tunnel service to create a transport path from Node 1 to Node 3. Configure the container type for VC Grooming. Additionally, if the VCX component or a VT/VC switch card is in an equipment protection group, specify the one that is working.

Create the services at Node 1 to add the low order payloads to the network. At Node 3, hand off each low order payload to separate facilities. If the termination point is a STM-N port, it is necessary to create an endpoint service (Services 5, 6, and 7 in the above example).

5GVC/VT

1. Service Type: SDH-TunnelBandwidth: VC4 (Grooming)Source: Node 1/slot-14/port-1/aug1-1VCX card: Slot 14Dest: Node 3/slot-1/port-1/aug1-1VCX card: Slot 4Protection Type: FULL

4. Service Type: SDHBandwidth: VC3Source: Node 1/slot-4/p-1Dest: Node 1/s-14/p-1/a-1/tug3-3/vc3Protection Type: FULL

Node 3

3. Service Type: SONETBandwidth: VT1.5Source: Node 1/slot-4/p-9 DS1Dest: Node 1/slot-14/p-1/a-1/tug3-2/tug2-1/vc11-1Protection Type: FULL

2. Service Type: SDHBandwidth: VC12Source: Node 1/slot-2/port-4 E1Dest: Node 1/slot-14/p-1/a-1/tug3-1/tug2-1/vc12-1Protection Type: FULL

Node 1Slot 2 Slot 4

2

3

4

Node 2

Node 4

Slot 6E1

W E

STM16 STM16 STM4Slot 1 Slot 2 Slot 4

1

E

STM16VCX

Slot 14

W

STM16VCX

Slot 13STM1DS1

18

9

10

10. Service Type: SDHBandwidth: VC3Source: Node 3/slot-1/port-1/tug3-2/vc3Dest: Node 3/slot-8/port-2/tug3-1/vc3Protection Type: FULL

8. Service Type: SDHBandwidth: VC12)Source: Node 3/slot-1/p-1/a-1/tug3-1/tug2-1/vc12-1Dest: Node 3/slot-8/port-1/a-1/tug3-1/tug2-1/vc12-1Protection Type: FULL

9. Service Type: SDHBandwidth: VC11Source: Node 3/slot-1/p-1/a-1/tug3-2/tug2-1/vc11-1Dest: Node 3/slot-8/p-1/a-1/tug3-1/tug2-1/vc11-1Protection Type: FULL

5, 6, and 7. Service Type: SDH-EndpointsBandwidth: VC4 (Grooming)Source: Node 3/slot-6/p-2/aug1-1VCX card: Slot 4Protection Type: FULL

5

6

7

Slot 6


Chapter 4 Creating SDH ServicesLow Order Services with Path Protection

Low Order Services with Path Protection

The network in the following example is a STM-16 ring. Each node that is adding or dropping traffic from the network has either a VCX component or a VT/VC switch card. Each low order switching component is configured in an equipment protection group.

The service creation model is based in creating two services for each low order payload: one unprotected and one path-protected.

Figure 4-21 Low Order Services with Path Protection (SDH)

Use the SDH-Endpoint service to create an transport endpoint at each node that is adding or dropping traffic from the network. Configure the container type for VC Grooming. Additionally, if the VCX component or a VT/VC switch card is in an equipment protection group, specify the one which is working.

Use the two-service creation model to add and drop traffic from the network. In the above example, for each low order payload:• At the node where the traffic is added to the network, create two services:

unprotected and 1+1 path protected. • At a drop node, create the same two services: unprotected and 1+1 path protected.• At any node where traffic is passed through the node to the next, create a pass

through service.

1. Service Type: SDH-Endpoint (x8)Bandwidth: VC-4 (VCGrooming)VCX card: Slot 14

Node 3Slot 6

E

GCMSTM16Slot 14

W

GCMSTM16Slot 13

STM1

Node 1Slot 2 Slot 4

2a

3a

4a

Slot 6E1

E

STM16VCX

Slot 14

W

STM16VCX

Slot 13

2b

3b

4b

DS1 STM1

1

5GVC/VT

5. Service Type: SDH-VC4 EndpointBandwidth: VC-4 (VC-3)Source: Node 3/slot-6/p-2/aug1-1

Slot 2

4a 4b

1

2c3c

E

STM16VCX

Slot 14

W

STM16VCX

Slot 13Slot 2E1

1

2a2b 3c

4c

E

STM16VCX

Slot 14

W

STM16VCX

Slot 13Slot 4DS1

1

3a 3b4c2c

1

1

1

1

5

4c. Service Type: SDH (VC3 bandwidth)Source: s-13/p-1/a-1/tug3-3/vc3Dest: s-14/p-1/a-1/tug3-3/vc3Protection Type: Unprotected

2a. Service Type: SDH (VC12 bandwidth)Source: s-2/p-4 E1Dest: s-13/p-1/a-1/tug3-1/tug2-1/vc12-1Protection Type: Unprotected

2b. Service Type: SDH (VC12 bandwidth)Source: s-2/p-4 E1Dest:/s-14/p-1/a-1/tug3-1/tug2-1/vc12-1Protection Type: 1+1 Path Protected

2c. Service Type: SDH (VC12 bandwidth)Source: s-13/p-1/a-1/tug3-1/tug2-1/vc12-1Dest: s-14/p-1/a-1/tug3-1/tug2-1/vc12-1Protection Type: Unprotected

3a. Service Type: DS1 (VC11 bandwidth)Source: s-4/p-9 DS1Dest: s-13/p-1/a-1/tug3-2/tug2-1/vc11-1Protection Type: Unprotected

3b. Service Type: DS1 (VC11 bandwidth)Source: s-4/p-9 DS1Dest: s-14/p-1/a-1/tug3-2/tug2-1/vc11-1Protection Type: 1+1 Path Protected


4a. Service Type: SDH (VC3 bandwidth)Source: s-6/p-6/a-1/tug3-3/vc3Dest: s-13/p-1/a-1/tug3-3/vc3Protection Type: Unprotected

4b. Service Type: SDH (VC3 bandwidth)Source: s-6/p-6/a-1/tug3-3/vc3Dest: s-14/p-1/a-1/tug3-3/vc3Protection Type: 1+1 Path Protected

Node 2

Node 4


Traverse Provisioning Guide, Section 4: Creating ADM ServicesMultiplexing Mixed Traffic onto a VC-4 Transport Path

Multiplexing Mixed Traffic onto a VC-4 Transport Path

The VC cross-connect (VCX) feature allows you to mix low order traffic and high order traffic on the same AU-4. Specifically, use the VCX when at least one of the TUG3s in the AU-4 contains a TUG2 payload. For example, you can create a protected VC-4 transport path and fill it with a combination of E1, E3, and Ethernet traffic. (Each TUG3 in the VC-4 can carry only one type of traffic.)

The network in the following example is an STM-16 SNCP ring. Each transport interface has the VCX daughter card configured in an equipment protection group.

To configure the services in the following example, create five services at each tributary node (Node 1, Node 2, and Node 3). Create 12 services (four services from three tributary nodes) at the hand-off node (Node 4).

Figure 4-22 Multiplexing Mixed Traffic onto VC-4 Transport Path

At each tributary node, create the following five services:1. Create an SDH-VC4-Tunnel as the transport path from the source node to the

hand-off node and specify that it will carry VC-3 payloads (Container Type is VC-3).

2. Create an E1-Mux service to transport all the traffic from 21 E1 ports on TUG3-1 of the VC-4 tunnel.

3. Create an E3-CC service to transport the E3 traffic on TUG3-2 of the VC-4 tunnel.4. Create an SDH-VC3-Endpoint on TUG3.3 of the VC-4 tunnel and identify the

Ethernet payload (Container Type is Ethernet).5. Create an Ethernet service from an Ethernet port to the VC-3 endpoint.

4. Service Type: SDH-EndpointBandwitdh: VC4 (VC3)Source: Node 1/s-14/p-1/a-1/t3-3/vc3Protection Type: FULL

2. Service Type: SDHBandwitdh: VC3Source: Node 1/ slot-2/all portsDest: Node 1/s-14/p-1/A-1/t3-1/vc3Protection Type: FULL

5. Service Type: EthernetSource: Node 1/slot-8/port-8Dest: Node 1 SDH-Endpoint Service

1. Service Type: SDH-TunnelContainer Type: VC4 (VC-3)Source: Node 1/slot-14/port-1/aug1-1Dest: Node 3/slot-1/port-1/aug1-1Protection Type: FULL

3. Service Type: SDHBandwidth: VC3Source: Node 1/ slot-4/port-1 E3CCDest: Node 1/s-14/p-1/a-1/t3-2/vc3Protection Type: FULL



9. Service Type: EthernetSource: Node 3/slot-6/port-4 - GBEDest: Node 3 SDH-Endpoint Service

Node 1 Node 3

W E

Slot 2

STM16VCX

Slot 1

STM16VCX

6.

7.

9.

STM1Slot 8

W E

STM16VCX

Slot 14

STM16VCX

Slot 13

2.

3.

5.

Slot 2E1

Slot 4E3

Slot 8ETH

4.

8. Service Type: SDH-EndpointBandwidth: VC4 (VC3)Source: Node 1/ s-12/p-1/a-1/t3-3/vc3Protection Type: FULL

Slot 6GBE

8.

Node 2

Node 4


Chapter 4 Creating SDH ServicesOther SDH Services and Applications

At the hand-off node, create the following four services for the traffic arriving from each tributary node:1. Create an SDH-VC3 service to hand-off the E1 traffic to an STM-1.2. Create another SDH-VC3 service to hand-off the E3 traffic to another STM-1.3. Create an SDH-VC3 Endpoint and identify the Ethernet payload.4. Create an Ethernet service to multiplex 10/100 Ethernet traffic to Gigabit Ethernet.

Cards Required to Create SDH Services

This table lists the Traverse cards required to create SDH services.

Other SDH Services and Applications

Use the procedures in the following chapters to configure other SDH services or applications: • Section 5—Creating Service Applications, Chapter 1—“Creating 1+1 Path

Protected Services,” page 5-1• Section 5—Creating Service Applications, Chapter 3—“Creating

Drop-and-Continue Services,” page 5-19• Section 5—Creating Service Applications, Chapter 4—“Creating Services over

Interconnected UPSR or SNCP Rings,” page 5-25• Section 5—Creating Service Applications, Chapter 5—“Creating Transmux

Services,” page 5-33• Section 5—Creating Service Applications, Chapter 6—“Creating Transparent

Services,” page 5-49• Section 7—Configuring Ethernet, Chapter 4—“Ethernet Over SONET/SDH

(EOS),” page 7-49• Section 7—Configuring Ethernet, Chapter 6—“Ethernet Over PDH (EOP),”

page 7-71

Table 4-17 Cards Required for SDH Services

Service Type Source Card Destination Card

SDH STM-NDS3/E3/EC1 Clear ChannelDS3/EC1 TransmuxE1

EC3

STM-NE1

DS1DS3/E3/EC1 Clear ChannelDS3/EC1 TransmuxOC-NEC3

Other cards

VT/TU 5G Switch (for VC11 and VC12 services)

n/a n/a

Any card with the VTX/VCX component (for VC11 and VC12 services)

n/a n/a


Traverse Provisioning Guide, Section 4: Creating ADM ServicesBefore You Create SDH Services

Before You Create SDH Services

Review the information in this topic before you create any SDH services.

Table 4-18 SDH Service Requirements




Hardware

You need a combination of the cards to create SDH services. See Before You Create SDH Ser-vices, page 4-46 for a breakdown of required cards for specific services.


Software




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



Traverse Provisioning Guide, Section 2—Configuring TDM Equipment, Chap-ter 3—“Configuring SDH Equipment,” page 2-27

If a VT/TU 5G Switch card is present in the shelf, review the guidelines.

This chapter, VT/TU 5G Switch Card SDH Guidelines, page 4-47

If a VTX/VCX integrated component card is present in the shelf, review the guidelines.

This chapter, VTX/VCX Integrated Switching Card SDH Guidelines, page 4-47

For low order services, it is necessary to create an SDH endpoint or tunnel service on both the source and destination STM ports before creating a low order service. The Bandwidth of this ser-vice must be VC Grooming.

• This chapter, Low Order Services with Path Protection, page 4-43

• Create an SDH Endpoint or Tunnel Service, page 4-64

These procedures describe how to create a spe-cific service and change only configurable param-eters. See the TransNav Management System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide, Section 6—Services, Chapter 3—“SDH Ser-vices,” page 6-31

Interworking. Support for ETSI to ANSI inter-working:• SDH to SONET• SONET to SDH

Traverse Provisioning Guide, Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,” Before You Create SDH Services, page 4-46


Chapter 4 Creating SDH ServicesVTX/VCX Integrated Switching Card SDH Guidelines

VT/TU 5G Switch Card SDH Guidelines

Use the following guidelines if the VT/TU 5G Switch card is present in the shelf configuration:• The VT/TU 5G Switch has a termination capacity of 32 STM-1s (5 Gbps). It can

support up to 1008 bi-directional VC12 services or 1344 bi-directional VC11 services.

• Force10 recommends to reserve the equivalent of at least 16 STM-1s for traffic leaving the node.

• Use the VT/TU 5G Switch if you are mixing low order traffic and high order traffic on the same AU-4. Specifically, use the VT/TU 5G Switch when at least one of the TUG3s in the AU-4 contains a TUG2 payload.


• If the VT/TU 5G Switch is in an equipment protection group, specify the one which is active.

VTX/VCX Integrated Switching Card SDH Guidelines

Use the following guidelines if the VC cross-connect (VCX) integrating switching component is present in the shelf configuration:• The VCX hardware has a termination capacity of 16 STM-1s. It can support up to

504 bi-directional VC12 services or 672 bi-directional VC11 services.• Force10 recommends to reserve the equivalent of at least eight STM-1s for traffic

leaving the node.• Use the VCX card if you are mixing low order traffic and high order traffic on the

same AU-4. Specifically, use the VCX when at least one of the TUG3s in the AU-4 contains a TUG2 payload.


• If the VCX is in an equipment protection group, specify the active VCX.

Provisioning models• HO SDH: end-to-end OR hop-by-hop• LO SDH: hop-by-hop only• SDH-Tunnel: end-to-end only• SDH-Endpoint: hop-by-hop only


Bandwidth requirements• VC11: 1.728 Mbps• VC12: 2.304 Mbps• VC3: 48.960 Mbps• VC4: 150.336 Mbps


Table 4-18 SDH Service Requirements (continued)



Traverse Provisioning Guide, Section 4: Creating ADM ServicesGuidelines to Provision an SDH VC-Mux Service

Guidelines to Provision an SDH VC-Mux Service

The guidelines to provision an SDH VC-Mux service are:• The source and destination endpoints must be on cards located on the same node.• One end of the service must terminate on an EoPDH card.• For EOP functions, the VC-Mux service must terminate on one of the first 12 VC-3

endpoints to generate usable endpoints. EoPDH cards restrict low-order connection termination points for use on E1 cards to reside only in the first 12 VC-3s of the card’s VOP.

• For EOS functions, the VC-Mux service must terminate on one of the first 24 VC-3 endpoints to generate usable endpoints. This is due to the restriction on EoPDH cards requiring low-order connection termination points to reside only in the first 24 VC-3s of the card’s VOP.

• For SDH services, verify the LO Mapping parameter on the Config tab is set to VC3 HO.

Payload Mapping Parameter

The Payload Mapping parameter is used on high-order SDH VC-3 services to allow the system to consider the activated service a clear-channel container with no sub-containers.

When the Payload Mapping parameter is set to VC-3 on SDH services, the service is considered a clear-channel container with no lower level VC sub-containers. When the parameter is set to VC-11 or VC-12, Traverse recognizes the low-level VC sub-containers as individual endpoints on the VC-3. The service endpoint on the EoPDH card is treated as 28 VC-11 or 21 VC-12 endpoints for use in an EOS or EOP port.


Chapter 4 Creating SDH ServicesEndpoints for VC3 and VC4 Services

Endpoints for VC3 and VC4 Services

The following table lists valid sources and destinations for SDH services. Your network may require creating multiple services at multiple nodes.

The Traverse system supports multicast SDH connections for 1+1 path-protected and drop-and-continue services.

Table 4-19 Endpoints for VC3 and VC4 Services



STM-N1

1 For SDH services between STM-64 ports, the source AUG number and the destination AUG number must inthe same range when the range is between 1 and 32, or between 33 and 64. For example, if the source AUGis AUG number 12, the destination AUG must be between AUG number 1 and 32; if the source AUG is AUG number 51, the destination AUG must be between AUG number 33 and 64.

node/slot/port/aug1/node/slot/port/aug1/tug3/vc3node/slot/port/aug1/vc3

STM-N (HO)STM-N (LO)

E3CCall ports E1 card

OC-NEC3EC1DS3CCDS3TMXall ports DS1 card

node/slot/port/aug1/node/slot/port/aug1/tug3/vc3node/slot/port/aug1/vc3node/slot/portnode/slot


E3CC node/slot/port STM-N (HO)STM-N (LO)E3CC

OC-N EC1DS3CC

node/slot/port/aug1/tug3/vc3node/slot/port/aug1/vc3node/slot/port


All ports on an E1 card


OC-N

node/slot/port/aug1/tug3/vc3node/slot/port/aug1/vc3


Ethernet card for EOS

node/slot (Ethernet card)/aug1



SDH port on back-plane for EOP ports

node/slot (Ethernet card)/aug1 OC-N node/slot/port/aug1


Traverse Provisioning Guide, Section 4: Creating ADM ServicesEndpoints for SDH VC-MUX Services

Endpoints for SDH VC-MUX Services

The following table lists the source and destination endpoint requirements to create SDH VC-MUX services.


The following table lists valid sources and destinations for VC11 and VC12 services. Your network may require creating multiple services at multiple nodes.

There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create these services.

Note: The maximum switching capacity of NGE and NGE Plus cards is 5 Gbps, however, this is restricted to high order switching. The following restrictions exist for low order switching on NGE cards in SDH mode with a provisioned low order mapping of VC-11. • An SDH VC-11 service cannot be provisioned if either the source or destination

termination point of the service is one of the following VC-11 connection termination points (CTPs):Any VC-11 in TUG2-x, VC3-y, or AUGz where:x = 3, 4, 5, 6, 7 andy = 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42, 45, or 48 andz = any value between 1 and 16 inclusive

• A VC-11 CTP cannot be added from the STM-16 VOP to an EOS port on the same NGE card if the endpoint is one of the following VC-11 CTPs: Any VC-11 in TUG2-x, VC3-y, or AUGz where:x = 3, 4, 5, 6, 7 andy = 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42, 45, or 48 andz = any value between 1 and 16 inclusive

Table 4-20 Endpoints for SDH VC-Mux Services



Mapping Set to

SDH EoPDH - VC3 (1 to 24)

VC3 VC-Mux 1 VC3 Yes VC11/ VC12

EoPDH - VC3(1 to 12)

E1 (all ports) E1-Mux E3 No N/A


Chapter 4 Creating SDH ServicesEndpoints for VC11 and VC12 Services

• No restrictions exist for VC-12 connection termination points on NGE cards.




STM-N1


node/slot/port/aug1/tug3/tug2/lovc2

node/slot/port/aug1/vc3/tug2/lovc2


STM (HO)1

STM (LO)1

E1

OC-NEC1DS3TMX3

DS1

3 Port is E1-mapped (DS3 Mapping parameter is E1).


node/slot/port/aug1/vc3/tug2/lo vcc

node/slot/port

node/slot/port/sts/vtg/vtnode/slot/port/sts-1/vtg/vtnode/slot/port/sts-1/vtg/vtnode/slot/port/subportnode/slot/port


STM (LO)1

E1

OC-N EC1DS3TMX3

DS1



node/slot/port


E1 node/slot/port STM (HO)1

STM (LO)1

E1

OC-N EC1DS3TMX3

DS1



node/slot/port


DS1 node/slot/port STM node/slot/port/aug1/tug3/tug2/lo vc2



Traverse Provisioning Guide, Section 4: Creating ADM ServicesEndpoints for SDH Services on EoPDH Cards

Endpoints for SDH Services on EoPDH Cards

The following table lists valid sources and destinations for SDH services on EoPDH cards. The Traverse system supports multicast STM connections for 1+1 path-protected and drop-and-continue services.

Note: An EoPDH card in SDH mode does not support SONET/SDH services to DS1/DS3 interfaces. Conversely, an EoPDH card in SONET mode does not support SONET/SDH services to E1/E3 interfaces.

Table 4-22 Endpoints for SDH Services on EoPDH Cards

Interface and Payload Mapping on Source Card SDH Service TypePayload mapping on

EoPDH Destination Card (all interfaces are VOP)

LIne Port Type (Interface

)

Interface CTP type

(CLI)


SDH Service

Type (CLI)

SDH Service

Bandwidth

EoPDH CTP Type


1 E1 port E1 E1 E1 VC121 VC12 E1 in VC12 (in VC3)

2 All 21 ports on an E1 card

CARD-STM All 21 E1s on card

E1-MUX HO-VC3 VC-3 21 x (E1 in VC12) in VC3

3 E3-CC E3 E3 E3-CC HO-VC32 VC-3 E3 in VC3

4 DS3-TMX E1_TMX E1 structured DS3

E1 VC121 VC12 E1 in VC12 (in VC3)

5 DS3-TMX DS1_TMX_IN_VC12

E1 structured DS3

VC12 VC121 VC12 E1 in VC12 (in VC3)

6 STM-N VC12 E1 structured DS3 in VC3

VC121 3 VC12 E1 in VC12 (in VC3)

7 VC3 E1 structured DS3 in VC3

VC3 HO-VC33 VC3 21 x (E1 in VC12)

8 E1 structured DS3 in VC3

LO-VC334 21 x (E1 in VC12)

9 E3 mapped VC3 LO-VC34 E3 (in VC3)

10 VC36 LO-VC34 VC3


Chapter 4 Creating SDH ServicesEndpoints for SDH Services on EoPDH Cards

11 STM-N / VOP5

VC11 VC11 struc-tured VC36

VC11 VC111 VC11 VC11 (in VC3)

12 VC12 E1 mapped VC12 (in VC3)


13 VC12 struc-tured VC36

VC121 VC12 VC12 (in VC3)

14 VC3 VC11 struc-tured VC3

VC-MUX HO-VC3 VC3 28 x VC-11

15 E1 mapped VC12 (in VC3)

HO-VC3 21 x (E1 in VC12)


HO-VC3 21 X VC-12

17 E3 mapped VC3 VC3 HO-VC32 E3 (in VC3)

18 VC36 HO-VC32 VC3

19 STM-N / VOP5

VC4 VC46 VC4 VC42 VC4 VC4

1 A TU Switch Module must be in the same chassis.



4 LO-VC3 services can be created from VC4-VC3 or VC4-Grooming endpoints on the Source card.


6 Source cards with VOP can be NGE, 10GbE, or GbE-10.

Table 4-22 Endpoints for SDH Services on EoPDH Cards (continued)




)

Interface CTP type

(CLI)


SDH Service

Type (CLI)

SDH Service

Bandwidth

EoPDH CTP Type



Traverse Provisioning Guide, Section 4: Creating ADM ServicesStarting AUG1 Numbers for VC-3 Services

Starting AUG1 Numbers for VC-3 Services

The starting AUG1 number for VC-3 paths depends on the data rate of the interface (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 depend 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 lists all of the valid starting AUG1 numbers for VC-4 services:

Table 4-23 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 4-24 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


Chapter 4 Creating SDH ServicesSearch for Services

Search for Services




Step Procedure




2

3 45






• 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 (p0). This refers to the OC-48 interface on the backplane.









Step Procedure


Chapter 4 Creating SDH ServicesSearch for Services









Step Procedure

6


Traverse Provisioning Guide, Section 4: Creating ADM ServicesCreate an SDH Service

Create an SDH Service

Use this procedure to transport synchronous traffic through the network:

Table 4-26 Create an SDH Service

Step Procedure

1 Add the SDH service.


a. Click the Service tab.b. From the Add button menu, select SDH.c. Click Add to display the Create Service tab.



3 From the Bandwidth parameter, select the total bandwidth for the service: • 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)

1a

1b

1c

23

4

5

10 12


Chapter 4 Creating SDH ServicesCreate an SDH Service




b. Navigate the tree and select the correct source endpoint. c. Click Done to close the dialog box and return to the Create Service

tab on the main screen.d. Click the Destination row in the Endpoint column.e. Navigate the tree and select the correct destination endpoint.f. Click Done to close the dialog box and return to the Create Service


Table 4-26 Create an SDH Service (continued)

Step Procedure

4a

4b

4c





In the Protection Type parameter, select one of the following options: • Unprotected (default): For services that are either unprotected, 1+1

APS/MSP protected, protected with an equipment protection group, or a 1+1 Path Protection group.




• UPSR Ingress: If the service is a LO VC service and is creating a bi-directional path across two interconnected SNCP rings.

6 For services that have a protection type configured, configure the following parameters:• Revertive (default is not selected): Select the check box to switch



If this service is protected by a BLSR or an MS-SPRing, go to Step 7.



Step Procedure

59



7 If the endpoints of the service are on a BLSR or MS-SPRing, click the MSSP/BLSR tab and configure the following parameters: • Ring Source Node ID: Select the BLSR Node ID where the traffic on



8 For services protected by another service, click the 1+1 Path Protected tab and configure the HoldOffTimer parameter. This parameter applies only if there is also a 1+1 APS/MSP protection group. Allows line protection to switch first before the path switches. If the line switches within the specified time period, the path does not switch. The hold-off timer starts when path protection detects a path failure.





Step Procedure

9





For specific definitions of these parameters, see the TransNav Management System GUI Guide, Section 6—Services, Chapter 3—“SDH Services,” Configure Advanced Parameters (Alphabetic Order), page 6-43.

To provision a VT-MUX service, continue to Step 11.

To complete the service, skip to Step 12.


Step Procedure



11 Configure the Payload Mapping parameter for VC-Mux type services if needed.


Select the desired Payload Mapping parameter type. Valid values are: For SDH services:– VC3 (default): Indicates the service endpoint on the Ethernet card

is treated as a VC-3 connection termination ports for use in EOS or EOP ports.

– VC11: Indicates the service endpoint on the Ethernet card will be treated as a set of 28 VC-11 connection termination ports for use in EOS or EOP ports.

– VC12: Indicates the service endpoint on the Ethernet card will be treated as a set of 21 VC-12 connection termination ports for use in EOS or EOP ports.

12 Click Done to return to the Create Service tab on the main screen.

The Create an SDH Service procedure is complete.

13 If this is a hop-by-hop service, click Apply to save this configuration and return to the Service tab on the main screen.

Continue to the procedure: Activate or Deactivate a Service, page 4-16.

14 If this is an end-to-end service, continue to the procedure: Configure the Path Through the Network, page 4-14.


Step Procedure


Traverse Provisioning Guide, Section 4: Creating ADM ServicesCreate an SDH Endpoint or Tunnel Service

Create an SDH Endpoint or Tunnel Service

Use an SDH Tunnel service to create a transport path end-to-end through the network. The endpoints for an SDH Tunnel are the transport cards at the add and drop nodes.

Use an SDH Endpoint service to create a termination point to multiplex low order traffic into the network or to create a transport path hop-by-hop through the network.

Table 4-27 Create an SDH Endpoint or SDH Tunnel Service

Step Procedure

1 Add the SDH Endpoint or SDH Tunnel service.


a. Click the Service tab.b. From the Add button menu, select SDH Endpoint or SDH Tunnel.c. Click Add to display the Create Service tab.

1a

1b

1c


Chapter 4 Creating SDH ServicesCreate an SDH Endpoint or Tunnel Service

2 In the Name field, enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.


3 From the Bandwidth parameter, select the total bandwidth for the service: • VC-3 (Grooming) (default): This path is VC-3 bandwidth and carries

low order payloads.• VC-4 (Grooming): This path is VC-4 bandwidth and carries low order

payloads.• VC-4 (VC-3): This path is VC-4 bandwidth and carries VC-3 payloads

only.

Table 4-27 Create an SDH Endpoint or SDH Tunnel Service (continued)

Step Procedure

23

4

5

10 12




Refer to VT/TU 5G Switch Card SDH Guidelines, page 4-47 as required.



b. Navigate the tree and select the correct source endpoint. If the Bandwidth is (Grooming), ensure to select the correct VCX or VT/TU 5G Switch card.

c. Click Done to close the dialog box and return to the Create Service tab on the main screen.

d. Click the Destination row in the Endpoint column.e. Navigate the tree and select the correct destination endpoint.f. Click Done to close the dialog box and return to the Create Service



Step Procedure

4a4b

4c





In the Protection Group Type field, select one of the following options: • Unprotected (default): Select this option for services that are

unprotected, 1+1 APS/MSP protected, protected with an equipment protection group, or a 1+1 Path Protection group.



• 1+1 Path Protected: Select this option if this service is protected by another service (two services model).

• UPSR Ingress: Select this service if the service is a LO VC service and is creating a bi-directional path across two interconnected SNCP rings.

6 For services that have a protection type configured, configure the following parameters:• Revertive (default is not selected): Select the checkbox to switch


• WTR Time: Specifies the amount of time (in minutes) for the system to wait before restoring traffic to the original path once the failure condition no longer exists. Specify a value between 1 and 60 minutes; default is 5.

If this service is protected by a BLSR or an MS-SPRing, go to Step 7.



Step Procedure

510



7 If the endpoints of the service are on a BLSR or MS-SPRing, click the MS-SP/BLSR tab and configure the following parameters: • Ring Source Node ID: Select the BLSR Node ID where the traffic on



8 For services protected by another service, click the 1+1 Path Protected tab and configure the HoldOffTimer parameter. This parameter applies only if there is also a 1+1 APS/MSP protection group. Allows line protection to switch before the path switches. If the line switches within the specified time period, the path does not switch. The hold-off timer starts when path protection detects a path failure.





Step Procedure

10





a. For specific definitions of these parameters, see the TransNav Management System GUI Guide, Section 6—Services, Chapter 3—“SDH Services,” Configure Advanced Parameters (Alphabetic Order), page 6-43.

b. Click Done to return to the Create Service tab on the main screen.

11 The Create an SDH Endpoint or SDH Tunnel Service procedure is complete.

For SDH Tunnel services, continue to the procedure Configure the Path Through the Network, page 4-14.

For SDH Endpoint services, click Apply to save this configuration and return to the Service tab on the main screen.

Continue to the procedure Activate or Deactivate a Service, page 16.


Step Procedure


Traverse Provisioning Guide, Section 4: Creating ADM ServicesCreate an SDH Transport Path Hop-by-Hop

Create an SDH Transport Path Hop-by-Hop

Use an endpoint service in conjunction with an SDH service to create a transport path hop-by-hop through the network. If you create a transport path hop-by-hop through the network, you can add and drop traffic or monitor performance and alarms at each hop. If you create a transport path end-to-end (tunnel service), you can only monitor each end.

The bandwidth of each service must be the same throughout the path.

Create an SDH Transport Path End-to-End

Use an SDH Tunnel service to create a transport path end-to-end through the network. If you create a path end-to-end, you can only add and drop traffic or monitor each end.

See Create an SDH Endpoint or Tunnel Service, page 4-64 for the procedure to create a tunnel.

Table 4-28 Create a Transport Path Hop-by-Hop

Step Procedure

1 Create an endpoint service at the node that adds the traffic. See the procedure Create an SDH Endpoint or SDH Tunnel Service, page 4-64.

2 Create an endpoint service at the node that drops the traffic. See the procedure Create an SDH Endpoint or SDH Tunnel Service, page 4-64.

3 At each intermediate node:

To be able to add traffic onto the transport path in the future from this node, create an SDH Endpoint service on each trunk card. See the procedure Create an SDH Endpoint or SDH Tunnel Service, page 4-64.

To simply pass traffic through this node, create an SDH service between the ingress and egress trunk cards. See the procedure Create an SDH Service, page 5-62.

4 The Create a Transport Path Hop-by-Hop procedure is complete.



Chapter 5Creating 2-Port OC-48/STM-16 Services

Introduction The Traverse platform distributed switching architecture allows each card (module) a bi-directional switching capacity of up to 2.5 Gbps between each individual slot. This means each slot can switch up to 2.5 Gbps of traffic bi-directionally between any slot and any slot.

This chapter explains how to create bi-directional switching capacity between slots:• Slot-to-Slot Switching Capacity, page 4-72• Guidelines to Provision Protected Services, page 4-72• Protection Groups using the 2-port OC-48/STM-16 Card, page 4-73• Protected Services from a 2-port OC-48/STM-16 to a Protected OC-192/

STM-64 Uplink, page 4-73• Aggregated Services from OC-48 UPSRs to OC-192 Uplinks, page 4-75• Guidelines to Create an Aggregate Service from a Subtended OC-48 UPSR,

page 4-76


Traverse Provisioning Guide, Section 4: Creating ADM ServicesSlot-to-Slot Switching Capacity

Slot-to-Slot Switching Capacity

The slot-to-slot switching architecture is non-blocking for all SONET/SDH cards except the 2-port OC-48/STM-16 card. At full capacity, the 2-port OC-48/STM-16 card supports 96 STS-1 or VC-3 (5 Gbps). It is important to understand how to use the 2-port OC-48/STM-16 card as part of a Force10 solution. You must be careful not to exceed the slot-to-slot bandwidth capacity of 48 STSs (VC-3s) when establishing services between the cards.

Figure 4-38 2.5 Gbps Slot-to-Slot Switching Capacity

Guidelines to Provision Protected Services

The guidelines to provision a protected service are:• For protected configurations, there must be two tributary and two trunk cards on

each node transporting the protected service.• You can use the following interface combinations in a protected service:

– OC-12 tributary and 1-port OC-48 trunks– OC-12 tributary and OC-192 trunks– 1-port OC-48 tributary and OC-192 trunks– 2-port OC-48 tributary and OC-192 trunks– STM-4 tributary and 1-port STM-16 trunks– STM-4 tributary and STM-64 trunks– 1-port STM-16 tributary and STM-64 trunks– 2-port STM-16 tributary and STM-64 trunks

• The Traverse system supports protected services over a OC-192/STM-64, 1-port OC-48/STM-16, or 2-port OC-48/STM-16-16 linear chain.

• There can be no other services provisioned on the tributary port.• The remaining bandwidth on the trunk cards can be used for additional unprotected

or 1+1 path protected services.• The tributary connections and fiber span between the Traverse nodes are

unprotected. The subtending third party equipment provides all protection switching and bandwidth management.

P1P4 P2 P3

W1 W2 W3 W4

R1E

R4E

R2E

R3E

R1W

R2W

R3W

R4W

1+1 APS/MPS

UPSR/SNCP

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

W P

Telecom Bus2.5 Gbps (48 STS-1 or VC-3)


Chapter 5 Creating 2-Port OC-48/STM-16 ServicesProtected Services from a 2-port OC-48/STM-16 to a Protected OC-192/ STM-64 Uplink

Protection Groups using the 2-port OC-48/STM-16 Card

Force10 supports using the 2-port OC-48/STM-16 card in a 1+1 APS/MSP protection group and a UPSR/SNCP protection group. Stagger the ports in the protection groups as illustrated to distribute cross-connects from the 2-port OC-48/STM-16 card without oversubscribing the 48 STS (2.5 Gbps) slot-to-slot bandwidth limitation in the case of a protection switch. The following figure illustrates staggered protection groups for a series of 2-port OC-48/STM-16 cards in one shelf.

Figure 4-39 Protection Groups on a Series of 2-port OC-48/STM-16 Cards

For 1+1 APS/MSP protection groups: Configure the 1+1 APS/MSP protection groups on the 2-port OC-48/STM-16 cards using port 2 of the first card and port 1 of the next. On the fourth protection group, use port 2 of the last card and port 1 of the first card.

For UPSR/SNCP protection groups: Configure the OC-48/STM-16 UPSR/SNCP protection groups on the 2-port OC-48/STM-16 cards using port 2 of one card as the West port and port 1 of the next card as the East port. For Ring 4, pair port 2 of the last card with port 1 of the first card. That is, port 2 of the last card is the West port of the protection group and port 1 of the first card is the East port in the protection group.

Protected Services from a 2-port OC-48/STM-16 to a Protected OC-192/ STM-64 Uplink

In protected configurations, the system creates four cross-connects for each service (a working and protecting cross-connect from each OC-48/STM-16 port to each OC-192/STM-64 port). In general, all services from one 2-port OC-48/STM-16 protection group must use a contiguous set of 48 STS (VC-3) paths on the OC-192/STM-64 card. On the 2-slot OC-192/STM-64 card, STS-1 to STS-96 are available in the lower-numbered slot and STS-97 to STS-192 are available in the higher-numbered slot.

W P

Telecom Bus2.5 Gbps (48 STS-1 or VC-3) 1+1 APS/MSP

UPSR/SNCP

P3

W4

P2

W3

P1

W2

P4

W1

R3E

R4W

R2E

R3W

R1E

R2W

R4E

R1W


Traverse Provisioning Guide, Section 4: Creating ADM ServicesProtected Services from a 2-port OC-48/STM-16 to a Protected OC-192/ STM-64 Uplink

This diagram illustrates the cross-connects the system creates for a protected service between ports on the 2-port OC-48/STM-16 and OC-192/STM-64 cards.

Figure 4-40 Created Cross-Connects on a Protected Configuration

The system creates two cross-connects from s-11/p-2 to the protection group on the OC-192/STM-64 cards. As part of the OC-48/STM-16 protection group, the system creates two more cross-connects from s-12/p1 to the protection group on the OC-192/STM-64 cards.

P2

W1

P1

W2

P4

W3

P3

W4

W P

(W) STS-49 to STS-96

(P) STS-97 to STS-144(W) STS-145 to STS-192

(W) STS-1 to STS-48(P) STS-1 to STS-48

(W) STS-97 to STS-144

(P) STS-49 to STS-96

(P) STS-145 to STS-192

STS-1 toSTS-96

STS-97 toSTS-192

STS-1 toSTS-96

STS-97 toSTS-192



(P) STS-49 to STS-96(W) STS-49 to STS-96


Slot-11 Slot-12 Slot-13 Slot-14 Slot-15 Slot-16 Slot-17 Slot-18


Chapter 5 Creating 2-Port OC-48/STM-16 ServicesAggregated Services from OC-48 UPSRs to OC-192 Uplinks

Aggregated Services from OC-48 UPSRs to OC-192 Uplinks

The Traverse platform supports aggregating services between any port on any node of a subtended OC-48/STM-16 UPSR-protected ring and the OC-192/STM-64 uplink using the 2-port OC-48/STM-16 card to reduce cost. Use this application to aggregate traffic from the subtended rings into a core network.

Figure 4-41 End-to-End Services from Subtended OC-48 UPSR using 2-port OC-48 Cards

In this example, assume that the subtended rings use slots 14 and 15 as the West and East ports in the configuration. On the uplink node, combine four 2-port OC-48/STM-16 cards in a series of subtended OC-48/STM-16 UPSR protected rings. Two OC-192/STM-64 cards in a 1+1 APS/MSP protection group link into the core network. Create the end-to-end services from nodes in the subtending ring to the OC-192/STM-64 uplink using the strict routing feature and choosing the working path.

In this application, creating services directly between subtending rings or between nodes on one ring is not supported. Such services would require cross-connects between the OC-48/STM-16 cards and that would oversubscribe the STS-48 (2.5 Gbps) slot-to-slot bandwidth restriction.

Slot 1OC48

R1E

OC48

R4E

OC48

R2E

OC48

R3E

Slot 2 Slot 3 Slot 4

OC192

W5

OC192

P5

R1W

R2W

R3W

R4W

Slot 11 Slot 13

Services

PG5 (1+1 APS)

UPSR/SNCPRing 1

UPSR/SNCPRing 2

OC-48 UPSRRing 3

OC-48 UPSRRing 4

Uplink Node

Services from Ring 1 must use STS-1 to STS-48 on the OC-192.Services from Ring 2 must use STS-97 to STS-144 on the OC-192.Servcies from Ring 3 must use STS-49 to STS-96 on the OC-192.Services from Ring 4 must use STS-145 to STS-192 on the OC-192.

Example End-to-End Services from Ring 1

R1E

R4E

R2E

R3E

R1W

R2W

R3W

R4W

Node 1

Node 3

Node 2

XX

Service Type: SONET (End-to-end Strict)Bandwidth: STS-1, STS-3c, STS-12c, or STS-48cStrict:Protection: AnyDescription EndpointSource Node 1/s-5/p-1/sts-1Pass-Through Node 1/s-15/p-1/sts-1Pass-Through Node 3/s-14/p-1/sts-1Pass-Through Node 3/s-15/p-1/sts-1Pass-Through Uplink Node/s-1/p-2/sts-1Destination Uplink Node/s-11/p-1/sts-1


Traverse Provisioning Guide, Section 4: Creating ADM ServicesGuidelines to Create an Aggregate Service from a Subtended OC-48 UPSR

Guidelines to Create an Aggregate Service from a Subtended OC-48 UPSR

Subtended UPSR protected rings. On the uplink node, configure the OC-48/STM-16 UPSR protection groups on the 2-port OC-48/STM-16 cards using port 2 of one card as the West port and port 1 of the next card as the East port. For Ring 4, pair port 2 of the last card with port 1 of the first card. That is, port 2 of the last card is the West port of the protection group and port 1 of the first card is the East port in the protection group.

Stagger the protection groups as described to distribute the cross-connects from the 2-port OC-48/STM-16 card to the 2-slot OC-192/STM-64 card without oversubscribing the 48 STS (2.5 Gbps) slot-to-slot bandwidth limitation. In this protected configuration, the system creates four cross-connects (one from each direction in the ring to each OC-192/STM-64 port).

OC-192 Card. On the 2-slot OC-192 card, STS-1 to STS-96 are available in the lower-numbered slot. STS-97 to STS-192 are available in the higher-numbered slot. In general, all services from one OC-48/STM-16 ring must use a contiguous set of 48 STS paths on the OC-192/STM-64 card. With these references in mind, configure services from each ring with the following guidelines:• Services from Ring 1 must use STS-1 to STS-48 on the OC-192/STM-64 card• Services from Ring 2 must use STS-97 to STS-144 on the OC-192/STM-64 card• Services from Ring 3 must use STS-49 to STS-96 on the OC-192/STM-64 card• Services from Ring 4 must use STS-145 to STS-192 on the OC-192/STM-64 card

The following services are not supported. Each would require bandwidth between the 2-port OC-48/STM-16 cards that would essentially oversubscribe the STS-48 (2.5 Gbps) slot-to-slot bandwidth restriction.• Services between rings are not supported• Services between nodes on one ring are not supported in this release

Activate the services in the following order:1. Services from Ring 1: STS-1 to STS-482. Services from Ring 2: STS-97 to STS-1443. Services from Ring 4: STS-145 to STS-1924. Services from Ring 3: STS-49 to STS-96


SECTION 5 CREATING SERVICE APPLICATIONSSECTION 5CREATING SERVICE APPLICATIONS

Contents

Chapter 1Creating 1+1 Path Protected Services

Path Protection Group Model (SONET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Path Protection Group Model (SDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3High Order Services with Path Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Low Order Services with Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Path Protection over APS-Protected Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Path Protection over MSP-Protected Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Before You Create 1+1 Path Protected Services . . . . . . . . . . . . . . . . . . . . . . 5-8Guidelines to Provision 1+1 Path Protected Services. . . . . . . . . . . . . . . . . . . 5-9Procedures Required to Create a 1+1 Path Protected Service. . . . . . . . . . . . 5-9Bookend Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Guidelines to Create a Bookend Application. . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Procedures Required to Create a Bookend Application . . . . . . . . . . . . . . . . . 5-11

Chapter 2Bridging and Rolling Services

Bridging and Rolling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Bridge and Roll in a UPSR/SNCP Protection Group. . . . . . . . . . . . . . . . . . . . 5-14Bridge and Roll in a Single 1+1 APS/MPS Protection Group . . . . . . . . . . . . . 5-15Guidelines to Create Bridge and Roll Services . . . . . . . . . . . . . . . . . . . . . . . . 5-16Procedures Required to Bridge and Roll Services . . . . . . . . . . . . . . . . . . . . . 5-16Bridge and Roll Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Create a Persistent Bridge Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Chapter 3Creating Drop-and-Continue Services

Drop and Continue Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Example of a Drop and Continue Service (SONET) . . . . . . . . . . . . . . . . . . . . 5-20Example of a Drop and Continue Service (SDH) . . . . . . . . . . . . . . . . . . . . . . 5-21Ethernet Services and Drop and Continue Applications . . . . . . . . . . . . . . . . . 5-22Cards Required to Create Drop and Continue Service . . . . . . . . . . . . . . . . . . 5-22Before You Create a Drop and Continue Service . . . . . . . . . . . . . . . . . . . . . . 5-22Guidelines to Provision Drop and Continue Services . . . . . . . . . . . . . . . . . . . 5-23Procedures Required to Provision a Drop and Continue Service . . . . . . . . . . 5-23Parameters Required to Provision Drop and Continue Services . . . . . . . . . . 5-24

Chapter 4Creating Services over Interconnected UPSR or SNCP Rings

Services over Interconnected UPSR or SNCP Rings . . . . . . . . . . . . . . . . . . . 5-25


Traverse Provisioning Guide, Section 5 Creating Service Applications

Example of a SONET Bi-directional Protected Path . . . . . . . . . . . . . . . . . . . . 5-26Example of an SDH Bi-directional Protected Path. . . . . . . . . . . . . . . . . . . . . . 5-27Example of Bi-directional Protected DS1 and VT1.5 Services . . . . . . . . . . . . 5-28Example of Bi-directional Protected E1 and VT Services . . . . . . . . . . . . . . . . 5-29Cards Required at Interconnecting Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Before You Create Services over Interconnected Rings . . . . . . . . . . . . . . . . . 5-30Guidelines to Provision Services over Interconnected Rings . . . . . . . . . . . . . 5-31Procedures Required to Provision Services over Interconnected Rings . . . . . 5-31

Chapter 5Creating Transmux Services

G.747 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Switching DS1s Inside a Channelized DS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35Switching E1s Inside a Channelized DS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36Cards Required to Create a Transmux Service. . . . . . . . . . . . . . . . . . . . . . . . 5-37Before You Create a Transmux Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40Guidelines to Provision an Optical Transmux Service. . . . . . . . . . . . . . . . . . . 5-41Procedures Required to Provision an Optical Transmux Service . . . . . . . . . . 5-42Assign and Configure Transmux Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43Configure an Optical Transmux Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46

Chapter 6Creating Transparent Services

Example of SONET Transparent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50Example of SDH Transparent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51Cards Required to Create a Transparent Service . . . . . . . . . . . . . . . . . . . . . . 5-52Before You Create a Transparent Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Guidelines to Provision Transparent Services. . . . . . . . . . . . . . . . . . . . . . . . . 5-53Procedures Required to Create a Transparent Service. . . . . . . . . . . . . . . . . . 5-54Disable Control Data Parameter on Nodes Linked to Third-Party Equipment. 5-54Provision the Transparent Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55


SECTION 5CREATING SERVICE APPLICATIONS

Chapter 1Creating 1+1 Path Protected Services

Introduction 1+1 path protected services protect the entire path of one service through a network. This feature is designed to protect paths in a mesh network. You can also use 1+1 path protection to protect traffic traveling over unprotected facilities.

This chapter explains how to create 1+1 path protection groups and 1+1 path protected services through a Traverse network:• Path Protection Group Model (SONET), page 5-2• Path Protection Group Model (SDH), page 5-3• High Order Services with Path Protection, page 5-4• Low Order Services with Path Protection, page 5-5• Path Protection over APS-Protected Links, page 5-6• Path Protection over MSP-Protected Links, page 5-7• Before You Create 1+1 Path Protected Services, page 5-8• Guidelines to Provision 1+1 Path Protected Services, page 5-9• Procedures Required to Create a 1+1 Path Protected Service, page 5-9• Bookend Application, page 5-10• Guidelines to Create a Bookend Application, page 5-11• Procedures Required to Create a Bookend Application, page 5-11

If your system includes 2-port OC-48 or STM-16 cards, see Section 4—Creating ADM Services, Chapter 5—“Creating 2-Port OC-48/STM-16 Services,” page 4-71 for additional information.


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsPath Protection Group Model (SONET)

Path Protection Group Model (SONET)

This model uses a 1+1 path protection group to create a protected STS path across the network. First, provision the required services at each node across the network. Subsequently, add a 1+1 path protection group either immediately or at a later date.

In the following examples, first create and activate the sequence of unprotected services (Steps 1, 2, 3, and 4). Next, create the 1+1 path protection group at the Add and Drop nodes (Steps 5 and 6). The pass through services at the intermediate nodes can be on any available path.

Figure 5-1 1+1 Path Protection Group (SONET)


GCMOC48

Slot 16

GCMOC48

Slot 15

1. Service Type: SONETBandwidth: STSSrc: Node 1/slot-1/all portsDest: Node 1/slot-15/p-1/sts-1Protection Type: Unprotected

UnprotectedOC-48


GCMOC48

Slot 16

GCMOC48

Slot 15OC12

4. Service Type: SONETBandwidth: STS-1Src: Node 6/slot 15/p-1/sts-1Dest: Node 6/slot-1/p-3/sts-1Protection Type: Unprotected


1 2

2

2

4


Node 4

Node 3

Node 2

PW

33

3Node 5

W P 6

UnprotectedOC-48

5



DS1


Chapter 1 Creating 1+1 Path Protected ServicesPath Protection Group Model (SDH)

Path Protection Group Model (SDH)

This model uses a 1+1 path protection group to create a protected path across the network. First, provision the required services at each node across the network. Subsequently, add a 1+1 path protection group either immediately or at a later date.

Using this model, you can protect paths at the following path levels:• High order AU-4• High order VC-3• Low order VC-3

In the following examples, first create and activate the sequence of unprotected services (Steps 1, 2, 3, and 4). Then create the 1+1 path protection group at the Add and Drop nodes (Steps 5 and 6). The pass-through services at the intermediate nodes can be on any available path.

Figure 5-2 1+1 Path Protection Group (SDH)


GCMSTM16Slot 16

GCMSTM16Slot 15


UnprotectedSTM-16


GCMSTM16Slot 16

GCMSTM16Slot 15

STM4



1 2

2

2

4


Node 4

Node 3

Node 2

PW

33

3Node 5

W P 6

UnprotectedSTM-16

5

E1

3. Service Type: SDH (Pass Through)Bandwidth VC3Src: Node 2/slot 15/p-1/a-1/vc3-1Dest: Node 2/slot-16/p-1/a-1/vc3-1Protection Type: Unprotected

2. Service Type: SDH (Pass Through)Bandwidth: VC3Src: Node 2/slot 15/p-1/a-1/vc3-1Dest: Node 2/slot-16/p-1/a-1/vc3-1Protection Type: Unprotected


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsHigh Order Services with Path Protection

High Order Services with Path Protection

This model uses two services to create a protected service across a Traverse network. First provision an unprotected end-to-end service. Subsequently add a protected service either immediately or at a later date.

In the following example, first provision an unprotected end-to-end service. Activate the unprotected service, then provision the protecting service to create a protecting path.

Notice that at the Node 1, the source for both services is identical. At the Node 4, the destination for both services is identical. You can choose the paths at each intermediate node using the Constraints screen of the service creation.

Figure 5-3 Creating 1+1 Path Protection with Two Services

The network interfaces at the Source and Drop nodes cannot be part of a 1+1 APS/MSP, BLSR, or MS-SP ring protection group. However, the interfaces can be part of a UPSR, SNCP ring, or unprotected. Activate provisioned services in any order; the first service you activate carries the active traffic.

Node 1 (Source node)

OC12/STM4Slot 1

OC48/STM16Slot 16

OC48/STM16Slot 15

2. Service Type: SONET-STSSrc: Node 1/slot-1/port-1/sts-1Dest: Node 4/slot-8/port-1/sts-24Protection Type = 1+1 Path Protected

1. Service Type: SONET-STSSrc: Node 1/slot 1/port-1/sts-1Dest: Node 4/slot-8/port-1/sts-24Protection Type = Unprotected

Node 6 (Drop node)

UnprotectedOC-48/STM-16

UnprotectedOC-48/STM-16

2. Service Type: SDHSrc: Node 1/slot-1/port-1/aug-1/vc3-1Dest: Node 4/slot-8/port-1/aug-1/vc3-1Protection Type = 1+1 Path Protected

1. Service Type: SDHSrc: Node 1/slot 1/port-1/aug-1/vc3-1Dest: Node 4/slot-8/port-1/aug-1/vc3-1Protection Type = Unprotected

OR

OR

OC12/STM4Slot 1

OC48/STM16Slot 16

OC48/STM16Slot 15


Chapter 1 Creating 1+1 Path Protected ServicesLow Order Services with Path Protection


Low Order Services with Path Protection

This model uses two services to create a protected service across a Traverse network. First provision an unprotected service. Subsequently add a protected service either immediately or at a later date.

The network in the following example is a STM-16 ring. Each node that is adding or dropping traffic from the network has either a VCX component or a VT/VC switch card. Each low order switching component is configured in an equipment protection group.

The service creation model is based in creating two services for each low order payload: one unprotected and one path-protected.

Figure 5-4 Low Order Services with Path Protection (SDH)

Use the SDH-Endpoint service to create an transport endpoint at each node that is adding or dropping traffic from the network. Configure the container type for VC Grooming. Additionally, if the VCX component or a VT/VC switch card is in an equipment protection group, specify the one which is working.

Use the two-service creation model to add and drop traffic from the network. In the above example, for each low order payload:• At the node where the traffic is added to the network, create two services:

unprotected and 1+1 path protected. • At a drop node, create the same two services: unprotected and 1+1 path protected.• At any node where traffic is passed through the node to the next, create a pass

through service.

1. Service Type: SDH-Endpoint (x8)Bandwidth: VC-4 (VCGrooming)VCX card: Slot 14

Node 3Slot 6

E

GCMSTM16Slot 14

W

GCMSTM16Slot 13

STM1

Node 1Slot 2 Slot 4

2a

3a

4a

Slot 6E1

E

STM16VCX

Slot 14

W

STM16VCX

Slot 13

2b

3b

4b

DS1 STM1

1

5GVC/VT

5. Service Type: SDH-VC4 EndpointBandwidth: VC-4 (VC-3)Source: Node 3/slot-6/p-2/aug1-1

Slot 2

4a 4b

1

2c3c

E

STM16VCX

Slot 14

W

STM16VCX

Slot 13Slot 2E1

1

2a2b 3c

4c

E

STM16VCX

Slot 14

W

STM16VCX

Slot 13Slot 4DS1

1

3a 3b4c2c

1

1

1

1

5

4c. Service Type: SDH (VC3 bandwidth)Source: s-13/p-1/a-1/tug3-3/vc3Dest: s-14/p-1/a-1/tug3-3/vc3Protection Type: Unprotected

2a. Service Type: SDH (VC12 bandwidth)Source: s-2/p-4 E1Dest: s-13/p-1/a-1/tug3-1/tug2-1/vc12-1Protection Type: Unprotected

2b. Service Type: SDH (VC12 bandwidth)Source: s-2/p-4 E1Dest:/s-14/p-1/a-1/tug3-1/tug2-1/vc12-1Protection Type: 1+1 Path Protected


3a. Service Type: DS1 (VC11 bandwidth)Source: s-4/p-9 DS1Dest: s-13/p-1/a-1/tug3-2/tug2-1/vc11-1Protection Type: Unprotected

3b. Service Type: DS1 (VC11 bandwidth)Source: s-4/p-9 DS1Dest: s-14/p-1/a-1/tug3-2/tug2-1/vc11-1Protection Type: 1+1 Path Protected


4a. Service Type: SDH (VC3 bandwidth)Source: s-6/p-6/a-1/tug3-3/vc3Dest: s-13/p-1/a-1/tug3-3/vc3Protection Type: Unprotected

4b. Service Type: SDH (VC3 bandwidth)Source: s-6/p-6/a-1/tug3-3/vc3Dest: s-14/p-1/a-1/tug3-3/vc3Protection Type: 1+1 Path Protected

Node 2

Node 4

Traverse Provisioning Guide, Section 5: Creating Service ApplicationsPath Protection over APS-Protected Links

Path Protection over APS-Protected Links

The Traverse supports 1+1 path protection over a fiber span using 1+1 APS protection. There can be any combination of protection groups on up to four links. This example shows two nodes connected by two fiber spans: OC-12 and OC-48. Each span is in a 1+1 APS protection group.

Figure 5-5 Path Protection over 1+1 APS-Protected Links

This feature requires the user to create services using the two service model. In the event of a protection switch, Node 2 has an option of four different signals it can drop to the OC-12 card in slot 13 (two working, two protecting from the APS-protected links). However, path protection considers only the path from each active (working) APS-protected facility for protection switching purposes.

To prevent unnecessary path protection switches, path protection does not immediately detect a path failure in the event of an APS protection switch. The configurable hold-off timer determines the amount of time path protection waits before switching to the active path from the second protection group. The hold-off timer starts when path protection detects a path failure.

If the APS protection switch occurs and selects traffic from the protecting port, the path protection selector continues to select traffic from that APS protection group.

If the hold-off timer expires before the APS protection switch clears, path protection switches to the alternate path (from the second APS protection group).

Node 1Slot 1

GCMOC48

Slot 16

GCMOC48

Slot 15

5. Service Type: SONETBandwidth: ST1Src: Node 1/slot-1/all portsDest: Node 1/slot-9/p-1/sts-1Protection Type: Unprotected

Node 2

OC48

Slot 10OC48

Slot 9

7. Service Type: SONETBandwidth: ST1Src: Node 2/slot 10/p-1/sts-1Dest: Node 2/slot-3/p-3/sts-1Protection Type: Unprotected

3

E1

4

6. Service Type: SONETBandwidth: ST1Src: Node 1/slot-1/all portsDest: Node 1/slot-15/p-1/sts-1Protection Type: 1+1 Path Protected

8. Service Type: SONETBandwidth: ST1Src: Node 2/slot-2/p-1/sts-1Dest: Node 2/slot-13/p-3/sts-1Protection Type: 1+1 Path Protected

OC12 OC12 OC12 OC12 OC12

Slot 1Slot 10Slot 9 Slot 2

W P W P P P

5

6

W W

7

8

Slot 13

2. Protection Group 21+1 APS OC48

3. Protection Group 31+1 APS OC-12


1 2 3 4



Chapter 1 Creating 1+1 Path Protected ServicesPath Protection over MSP-Protected Links

Path Protection over MSP-Protected Links

The Traverse supports 1+1 path protection over a fiber span using 1+1 MSP or 1+1 optimized facility protection. There can be any combination of protection groups up to four links. This example shows two nodes connected by two fiber spans: STM-4 and STM-16. Each span is in a 1+1 MSP protection group.

Figure 5-6 Path Protection over 1+1 MSP-Protected Links

This feature requires the user to create services using the two service model. In the event of a protection switch, Node 2 has an option of four different signals it can drop to the STM-4 card in slot 13 (two working, two protecting from the MSP-protected links). However, path protection considers only the path from each active (working) MSP-protected facility for protection switching purposes.

To prevent unnecessary path protection switches, path protection does not immediately detect a path failure in the event of an MSP protection switch. The configurable hold-off timer determines the amount of time path protection waits before switching to the active path from the second protection group. The hold-off timer starts when path protection detects a path failure.

If the MSP protection switch occurs and selects traffic from the protecting port, the path protection selector continues to select traffic from that MSP protection group.

If the hold-off timer expires before the MSP protection switch clears, path protection switches to the alternate path (from the second MSP protection group).

Node 1Slot 1

GCMSTM16Slot 16

GCMSTM16Slot 15


Node 2

STM16Slot 10

STM16Slot 9


3

E1

4

6. Service Type: SDHBandwidth: VC3Src: Node 1/slot-1/all portsDest: Node 1/slot-15/p-1/a-1/vc3-1Protection Type: 1+1 Path Protected

8. Service Type: SDHBandwidth: VC3Src: Node 2/slot-2/p-1/a-1/vc3-1Dest: Node 2/slot-13/p-3/a-1/vc3-1Protection Type: 1+1 Path Protected

STM4 STM4 STM4 STM4 STM4

Slot 1Slot 10Slot 9 Slot 2

W P W P P P

5

6

W W

7

8

Slot 13

1. Protection Group 11+1 MSP STM-4




1 2 3 4


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsBefore You Create 1+1 Path Protected Services

Before You Create 1+1 Path Protected Services

Review the information in this topic before you create a 1+1 path protected service.

Table 5-1 1+1 Path Protected Service Requirements




Hardware

The hardware depends on the services you are creating. See the appropriate chapter in this docu-ment to determine the correct hardware for each service type.


Traverse Provisioning Guide, Section 4—Creating ADM Services

Software





This chapter describes how to create path-pro-tected services in a Traverse network. See Section 4—Creating ADM Services for detailed procedures on creating services.


Provisioning models • SONET-STS: end-to-end OR hop-by-hop• SONET-VT1.5: hop-by-hop only• HO SDH: end-to-end OR hop-by-hop• LO SDH: hop-by-hop only• SDH-Tunnel: end-to-end only• SDH-Endpoint: hop-by-hop only



Chapter 1 Creating 1+1 Path Protected ServicesProcedures Required to Create a 1+1 Path Protected Service

Guidelines to Provision 1+1 Path Protected Services

The guidelines to provision a 1+1 path protected service are:• Use the 1+1 path protection group model to protect services created at the

following path levels: – High order AU-4– High order VC-3– Low order VC-3– STS

• Use the two services model to protect services of any bandwidth. • The network interfaces at the source and drop nodes cannot be part of an MS-SP

ring or a BLSR protection group. However, the interfaces can be part of an SNCP/UPSR protection group, a 1+1 APS protection group, a 1+1 MSP protection group, or unprotected.

• Provision the unprotected services first.• Provision the path-protected service or the protection group second.• At the intermediate nodes, the path numbers can be different.• If any part of the network has another type of protection, you must make the

cross-connection to the working facility.• Activate the services in any order, however, the service you activate first carries the

active traffic.• If end-to-end services are created for the unprotected services, Force10

recommends using end-to-end services for the protecting services. That is, Force10 recommends not to use a hop-by-hop service to protect end-to-end services or vice versa.

• To perform a manual switch on an end-to-end service protected by a hop-by-hop service, perform the manual switch on the protecting hop-by-hop service.

Procedures Required to Create a 1+1 Path Protected Service

Use the following procedures to help you provision 1+1 path protected services on a Traverse system:1. Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,”

page 4-412. Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services,”

page 4-19 3. Section 3—Creating Protection Groups, Chapter 7—“Creating a 1+1 Path

Protection Group,” page 3-414. Section 4—Creating ADM Services, Chapter 2—“Common Procedures for

Services,” Activate or Deactivate a Service, page 4-16


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsBookend Application

Bookend Application

The Traverse platform supports STS-12c/VC-4-4c end-to-end services over 1+1 APS/MSP protected OC-48/STM-16 links using the 2-port OC-48/STM-16 card in a bookend application. Use the 2-port OC-48/STM-16 card as a transport card. Use the extra transport bandwidth for other services on the node.

The bookend application also uses the following additional services:• STS-1• STS-3c• LO VC-3• HO VC-3• VC-4• SNCP ring• UPSR ring

Figure 5-7 Bookend Application (SONET)

Create the end-to-end STS-12c (VC4-4c) services from the OC-12 (STM-4) ports. Remember to create services without oversubscribing the 48 STS (VC-3) (2.5 Gbps) slot-to-slot bandwidth limitations.


Chapter 1 Creating 1+1 Path Protected ServicesProcedures Required to Create a Bookend Application

Guidelines to Create a Bookend Application

The guidelines to provision a bookend application are:• Configure the 1+1 APS/MSP protection groups on the 2-port OC-48 (STM-16)

cards using port 2 of one card as the working port and port 1 of the other card as the protecting port.

• When engineering other services using the rest of the transport bandwidth from the 2-port OC-48 (STM-16) card, plan for the 48 STS (VC-3) (2.5 Gbps) slot-to-slot bandwidth limitation.

Procedures Required to Create a Bookend Application

Use the following procedures to help you create a bookend application on 1+1 path-protected services on a Traverse system:1. Section 3—Creating Protection Groups, Chapter 6—“Creating a 1+1 APS/MSP

Protection Group,” page 3-352. Section 4—Creating ADM Services, Chapter 1—“Service Provisioning Concepts,”

page 4-13. Section 4—Creating ADM Services, Chapter 2—“Common Procedures for

Services,” page 4-134. Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,”


page 4-19


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsProcedures Required to Create a Bookend Application



Chapter 2Bridging and Rolling Services

Introduction This chapter includes the following topics:• Bridging and Rolling Services, page 5-13• Bridge and Roll in a UPSR/SNCP Protection Group, page 5-14• Bridge and Roll in a Single 1+1 APS/MPS Protection Group, page 5-15• Guidelines to Create Bridge and Roll Services, page 5-16• Procedures Required to Bridge and Roll Services, page 5-16• Bridge and Roll Services, page 5-17• Create a Persistent Bridge Service, page 5-18

If your system includes 2-port OC-48 cards, see Section 4—Creating ADM Services, Chapter 5—“Creating 2-Port OC-48/STM-16 Services,” page 4-71 for additional information.

Bridging and Rolling Services

The Traverse system supports a bridge and roll feature that allows an operator to transfer services from one facility to another without dropping traffic. In-service transition allows one or more cross-connects to be moved from one facility to another without interrupting traffic. This operation is non-service affecting (less than 2 ms). This operation takes less time than a protection switch event.


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsBridge and Roll in a UPSR/SNCP Protection Group

Bridge and Roll in a UPSR/SNCP Protection Group

In this example, two Traverse nodes are connected to a network cloud using a UPSR/SNCP protection group. Create a primary service from the port to the working port of the protection group. Create a bridge service that originates on the same source, but terminates on a separate facility. Activate the bridge service.

Subsequently, roll the traffic from the original service to the bridge service either immediately or at a later date. At any given time, an operator can use the multiple select feature (Ctrl+click) to select all bridge services in the service list and roll the services. The roll operation essentially changes the selector for the service to the bridge service. Perform the roll operation at both ends of the network.

Figure 5-8 Bridging and Rolling Services, UPSR/SNCP Protection Groups

SONET

Destination NodeSource NodeSlot 1TMX

Slot 16

W

GCMOC48Slot 15

OC48 OC48Slot 14Slot 13

1. Original ServiceSource: Node 1/s-1/p-1/sts-1Dest: Node 1/s-16/p-1/sts-1

2. Bridge and Roll ServiceSource: Node 1/s-1/p-1/sts-1Dest: Node 1/s-14/p-1/sts-1Bridge and Roll:

2 1

1. Original ServiceSource: Node 1/s-1/p-1/aug-1/vc3-1Dest: Node 1/s-16/p-1/aug-1/vc3-1

2. Bridge and Roll ServiceSource: Node 1/s-1/p-1/aug-1/vc3-1Dest: Node 1/s-14/p-1/aug-1/vc3-1Bridge and Roll:

OR

Node 4

Node 3

Slot 1

E

GCMOC48 TMX

E

GCMOC48Slot 16

W

GCMOC48Slot 15

OC48Slot 13

2 1

OC48Slot 14

SDH


Chapter 2 Bridging and Rolling ServicesBridge and Roll in a Single 1+1 APS/MPS Protection Group

Bridge and Roll in a Single 1+1 APS/MPS Protection Group

Bridge and roll services are also supported in a 1+1 APS/MPS protection group. Unlike the UPSR/SNCP protection group, the created bridge service for the originates on the same source endpoint but uses a different path.

In this example, two Traverse nodes are connected to a network cloud using 1+1 APS protection groups. Create a primary SONET service from the DS3 port to the working port of the protection group. Subsequently, create a bridge service using the same source endpoint to the working port, but a different path. For example, use STS-1 for the primary service and STS-2 for the alternative service. The STS paths would be diversely routed within the network cloud. Once all the services are activated, the same signal is being transmitted over two diversely routed paths.

At any given time, an operator can use the multiple select feature (Ctrl+click) to select all bridge services in the service list and roll the services. The roll operation essentially changes the selector for the DS3 service to select the signal from the alternative path (in this example, STS-2). Perform the roll operation at both ends of the network.

Figure 5-9 Bridging and Rolling Services, 1+1 APS/MSP Protection Groups

SONET

Destination NodeSource NodeSlot 1TMX

Slot 16

GCMOC48

W

Slot 15OC48 OC48

Slot 14Slot 13

1. Original ServiceSource: Node 1/s-1/p-1/sts-1Dest: Node 1/s-14/p-1/sts-1

2. Bridge and Roll ServiceSource: Node 1/s-1/p-1/sts-1Dest: Node 1/s-16/p-1/sts-1Bridge and Roll:

2 1

1. Original ServiceSource: Node 1/s-1/p-1/aug-1/vc3-1Dest: Node 1/s-14/p-1/aug-1/vc3-1

2. Bridge and Roll ServiceSource: Node 1/s-1/p-1/aug-1/vc3-1Dest: Node 1/s-16/p-1/aug-1/vc3-1Bridge and Roll:

OR

Node 4

Node 3

Slot 1

GCMOC48 TMX

GCMOC48Slot 16

GCMOC48

W

Slot 15OC48Slot 13

2 1

OC48Slot 14

E

SDH

E


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsGuidelines to Create Bridge and Roll Services

Guidelines to Create Bridge and Roll Services

The Traverse system supports bridge and roll services for the following bandwidths of services:• VT1.5• STS-1• STS-3c• STS-12c• STS-48c• HO VC-3• VC-4• VC-4-4c• VC-4-16c

The destination of the bridge service can be on a separate transport card. For example, the working card of a second protection group. See Bridge and Roll Services, page 5-17 for the related procedure.

The destination of the bridge service can be on a separate path of the same working transport card of the original service. In this case, the separate path would be an alternative route through the network. See Create a Persistent Bridge Service, page 5-18 for the related procedure.

You can roll and unroll traffic as often as required without using the commit function. The commit function transforms the bridge service to a regular service by removing the Bridge and Roll attribute.

Procedures Required to Bridge and Roll Services

Use the following procedures to help you bridge and roll services on a Traverse system.1. Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services,”

Create a SONET Service, page 4-352. Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,” Create

an SDH Service, page 4-583. Section 4—Creating ADM Services, Chapter 2—“Common Procedures for



Chapter 2 Bridging and Rolling ServicesBridge and Roll Services

Bridge and Roll Services

Use this procedure to transfer traffic from one facility to another without interrupting service. Create all the bridge services individually first, then roll and commit multiple services.

Table 5-2 Bridge and Roll Services

Step Procedure

1 At the Source node in the network, use the appropriate procedure to create the original service: • Create a SONET Service, page 4-35 • Create an SDH Service, page 4-58

2 Use the appropriate procedure to create the bridge service: • Create a SONET Service, page 4-35 • Create an SDH Service, page 4-58

The Source endpoint must be the same as the original service from Step 1.

The Destination endpoint should be on a separate working card of another protection group.

When configuring the Advanced dialog box, select the Bridge and Roll parameter for the service.

3 Activate all bridged (new) services:a. On the service list, find and select all the bridged services. b. Right-click and select Activate.

4 Perform Steps 1 to Step 3 at the Destination node in the network.

5 At the Source node, roll the traffic from the original service to the bridged service:a. On the service list, find and select all the bridged services. b. Right-click and select Roll.

6 Deactivate the original services:a. On the service list, find and select all the original services from Step 1. b. Right-click and select Deactivate.

7 Delete the original services from the service list:a. Find and select the original services on the service list. b. Right-click and select Delete.

8 Commit the bridged services to stop traffic on the original service.a. Select the bridged services in the service list.b. Right-click and select Commit.

9 Perform Steps 5 through 8 at the Destination node in the network.

10 The Bridge and Roll Services procedure is complete.


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsCreate a Persistent Bridge Service

Create a Persistent Bridge Service

Use this procedure to transfer traffic from one path to another diversely routed path without interrupting service. Create all the bridge services individually first. Subsequently (either immediately or at a later time) roll and unroll multiple services to transfer traffic.

Table 5-3 Create a Persistent Bridge Service

Step Procedure

1 At the Source node in the network, use the appropriate procedure to create the original service: • Create a SONET Service, page 4-35 • Create an SDH Service, page 4-58

2 Use the appropriate procedure to create the bridge service: • Create a SONET Service, page 4-35 • Create an SDH Service, page 4-58

The Source endpoint must be the same as the original service from Step 1.

The Destination endpoint should be on a separate path of the same working card of the same protection group.

When configuring the Advanced dialog box, select the Bridge and Roll parameter for the service.

3 Activate all bridged (new) services.a. On the service list, find and select all the bridged services. b. Right-click and select Activate.

4 Perform Steps 1 to Step 3 at the Destination node in the network.

5 When required, roll the traffic from the original service to the bridge service. Perform the roll operation at both nodes (C nodes).a. On the service list, find and select all the bridge services. Use the

multiple select option (Ctrl + click) to select multiple services.b. Right-click and select Roll.

6 When required, unroll the traffic from the bridge service to the original service. Perform the unroll operation at both nodes (VL nodes).a. On the service list, find and select all the bridged services. Use the

multiple select option (Ctrl + click) to select multiple services.b. Right-click and select Unroll.

7 The Create a Persistent Bridge Service procedure is complete.




Chapter 3Creating Drop-and-Continue Services

Introduction This chapter explains how to create a drop-and-continue service in a Traverse network. • Drop and Continue Services, page 5-19• Example of a Drop and Continue Service (SONET), page 5-20• Ethernet Services and Drop and Continue Applications, page 5-22• Cards Required to Create Drop and Continue Service, page 5-22• Before You Create a Drop and Continue Service, page 5-22• Guidelines to Provision Drop and Continue Services, page 5-23• Procedures Required to Provision a Drop and Continue Service, page 5-23• Parameters Required to Provision Drop and Continue Services, page 5-24


Drop and Continue Services

Drop-and-continue applications allow you to add traffic to a UPSR or SNCP ring, drop traffic at one location, and continue the signal to another destination around the ring. To provision a drop-and-continue service, you need to provision a combination of three types of services at different nodes in the network.1. Add Service: This service adds the traffic to the ring. You provision this service at

the node where the traffic enters the ring. The source of this service is a tributary port. The destination is either trunk port (East or West) of the ring. You create this add service as FULL or ANY protected; the system creates both the working and protection paths around the ring

2. Drop Service: This service drops traffic from the ring. You provision this service at any node for traffic traveling in either direction around the ring. The source of this service is the trunk port (East or West) that receives the added traffic from the ring. The destination is the port which drops the added traffic from the ring.

3. Continue Service: This service carries the traffic around the ring. After you have dropped traffic at one node, you continue the path around the network. You provision one unidirectional continue service at any node for traffic traveling in both directions around the ring. The source of this service is the trunk port (East or West) that receives the added traffic from the ring. The destination is the other trunk card on the node.

Provision all required services on one node before you move to the next. That is, configure the services hop-by-hop through the network. Provision and activate the drop service before you provision the continue service.

Traverse Provisioning Guide, Section 5: Creating Service ApplicationsExample of a Drop and Continue Service (SONET)

Example of a Drop and Continue Service (SONET)

The following example an OC-48 UPSR is already connected and configured. The West Ports are Slot 15 on all the nodes. The East Ports are Slot 16. Traffic enters the ring at Node and is bridged in both directions around the ring. In a UPSR configuration in a Traverse network, the East card always transmits the working signal clockwise around the ring. The West card always receives the working signal.

This example shows ONLY the services you need to create at each node to drop and continue traffic around the ring.

Figure 5-10 Drop-and-Continue Service

In this example, traffic added at Node 1 is bridged around the ring. On the Traverse system, when you create the Add Service, you can use either the East or West port as the destination; the system creates the second connection to the other port of the ring. For any service that has Protection Type = UPSR, the system creates the second connection from the signal traveling in the opposite direction around the ring.

9. Service Type: SONET-STS(Continue)Src: Node 2 - slot 15 - port 1- sts4Dest: Node 2 - slot 16 - port 1 - sts4Directionality = UnidirectionalProtection Type = Unprotected

ALL SERVICESHop-by-hopBandwidth = STS-3c

1. Service Type: SONET-STS (Add)Src: Node 1 - slot 2 - port 1 - sts4Dest: Node1 - slot 16 - port 1 - sts4Directionality = UnidirectionalProtection Type = FULL

2. Service Type: SONET-STS (Continue)Src: Node 3 - slot 15 - port 1 - sts4Dest: Node 3 - slot 16 - port 1 - sts4Directionality = UnidirectionalProtection Type = UnprotectedVideo Server

6. Service Type: SONET-STS (Continue)Src: Node 3 - slot 15 - port 1 - sts4Dest: Node 3 - slot 16 - port 1 - sts4Directionality = UnidirectionalProtection Type = Unprotected

5. Service Type: SONET-STS (Continue)Src: Node 2 - slot 16 - port 1- sts 4Dest: Node 2 - slot 15 - port 1 - sts 4Directionality = UnidirectionalProtection Type = UnprotectedVideo Client 3

EW

Node 3

Slot 16OC12Slot 2 Slot 15

OC48OC48

8

EW

Node 4


OC48OC48

6

5

8. Service Type: SONET-STS (Continue)Src: Node 3 - slot 15 - port 1 - sts4Dest: Node 3 - slot 16 - port 1 - sts4Directionality = BidirectionalProtection Type = Unprotected

W E


OC48OC48

1

Node 1

EW

Node 6


OC48OC48

2

Node 2

W

OC48Slot 15Slot 2

E

OC48Slot 16

OC12

9

10

Node 5

W

OC48Slot 15Slot 2

E

OC48Slot 16

OC12

3. Service Type: SONET-STS (Continue)Src: Node 3 - slot 15 - port 1 - sts4Dest: Node 3 - slot 16 - port 1 - sts4Directionality = UnidirectionalProtection Type = Unprotected

OC-48 UPSRWest Ports = Slot 15East Ports = Slot 16

10. Service Type: SONET-STS(Drop)Src: Node 2 - slot 15 - port 1 - sts4Dest: Node 2 - slot 2 - port 1 - sts4Directionality = UnidirectionalProtection Type = FULL

7. Service Type: SONET-STS (Drop)Src: Node 4 - slot 15 - port 1 - sts4Dest: Node 4 - slot 2 - port 1 - sts4Directionality = UnidirectionalProtection Type = FULL

7

4. Service Type: SONET-STS (Drop)Src: Node 4 - slot 15 - port 1 - sts4Dest: Node 4 - slot 2 - port 1 - sts4Directionality = UnidirectionalProtection Type = FULL

4

Video Client 1

3

Video Client 2


Chapter 3 Creating Drop-and-Continue ServicesExample of a Drop and Continue Service (SDH)

Example of a Drop and Continue Service (SDH)

The following example an STM-16 SNCP ring is already connected and configured. The West Ports are Slot 15 on all the nodes. The East Ports are Slot 16. Traffic enters the ring at Node and is bridged in both directions around the ring. In an SNCP ring configuration in a Traverse network, the East card always transmits the working signal clockwise around the ring. The West card always receives the working signal.

This example shows ONLY the services you need to create at each node to drop and continue traffic around the ring.

Figure 5-11 Drop-and-Continue Service

In this example, traffic added at Node 1 is bridged around the ring. On the Traverse system, when you create the Add Service, you can use either the East or West port as the destination; the system creates the second connection to the other port of the ring. For any service that has Protection Type =UPSR/SNCP, the system creates the second connection from the signal traveling in the opposite direction around the ring.

EW

W E

9. Continue Service: SDH-VC4Src: Node 6/slot-15/port-1/aug1-1Dest: Node 6/slot-16/port-1/aug1-1Directionality = UnidirectionalProtection Type = Unprotected

ALL SERVICESHop-by-hopBandwidth = VC-4

1. Service Type: SDH-VC4 (Add)Src: Node 1/slot-2/port-1/aug1-1Dest: Node1/slot-16/port-1/aug1-1Directionality = UnidirectionalProtection Type = FULL

2. Service Type: SDH-VC4 (Continue)Src: Node 2/slot-15/port-1/aug1-1Dest: Node 2/slot-16/port-1/aug1-1Directionality = UnidirectionalProtection Type = UnprotectedVideo Server

EW

Node 5

Slot 16STM4Slot 2 Slot 15

8

EW

Node 4


8. Service Type: SDH-VC4 (Continue)Src: Node 5/slot-15/port-1/aug1-1Dest: Node 5/slot-16/port-1/aug1-1Directionality = BidirectionalProtection Type = Unprotected


1

Node 1

EW

Node 2

Slot 16STM4

Slot 2 Slot 15

GCMSTM16

Node 6

Slot 15Slot 2 Slot 16STM4

910

Node 3

Slot 15Slot 2 Slot 16

STM4

3. Service Type: SDH-VC4 (Continue)Src: Node 3/slot-15/port-1/aug1-1Dest: Node 3/slot-16/port-1/aug1-1Directionality = UnidirectionalProtection Type = Unprotected

STM-16 SNCPWest Ports = Slot 15East Ports = Slot 16

7. Service Type: SDH-VC4 (Drop)Src: Node 4/slot-15/port-1/aug1-1Dest: Node 4/slot-1/port-1/aug1-1Directionality = UnidirectionalProtection Type = FULL

7

4

32

6

5


Video Client 2


4. Service Type: SDH-VC4 (Drop)Src: Node 3/slot-15/port-1/aug1-1Dest: Node 3/slot-2/port-1/aug1-1Directionality = UnidirectionalProtection Type = FULL Video Client 3

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

10. Service Type: SDH-VC4 (Drop)Src: Node 6/slot-15/port-1/aug1-1Dest: Node 6/slot-2/port-1/aug1-1Directionality = UnidirectionalProtection Type = FULL Video Client 1


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsEthernet Services and Drop and Continue Applications

Ethernet Services and Drop and Continue Applications

To create Ethernet services in a drop-and-continue application (such as video broadcast), use the same example (Figure 5-10 Drop-and-Continue Service, page 5-20). However, the Add service would originate on an Ethernet card. The Drop service would terminate on an Ethernet card.

Cards Required to Create Drop and Continue Service

This table lists the Traverse cards required to create a drop-and-continue services.

Before You Create a Drop and Continue Service

Review the information in this topic before you create a drop-and-continue service.

Table 5-4 Cards Required for Drop-and-Continue Services


SDH STM-NAny Ethernet card

STM-NAny Ethernet card

SONET OC-NEC3Any Ethernet card

OC-NEC3Any Ethernet card

Table 5-5 Drop-and-Continue Service Requirements




Hardware

See Cards Required to Create Drop and Con-tinue Service, page 5-22.

The hardware depends on the services you are creating. See the appropriate chapter in this docu-ment to determine the correct hardware for each service type.



Software






Chapter 3 Creating Drop-and-Continue ServicesProcedures Required to Provision a Drop and Continue Service

Guidelines to Provision Drop and Continue Services

The guidelines to provision a drop and continue service are:• The UPSR or SNCP ring must be connected and provisioned. See

Section 3—Creating Protection Groups, Chapter 3—“Creating a UPSR or SNCP Ring Protection Group,” page 3-15.

• Provision the required service (Source, Drop, or Continue) at each hop in the network.

• Provision all required services on one node before you move to the next.• Provision and activate the drop service before you provision the continue service.• The working and protect path numbers around the ring must match. That is, if you

add SONET service onto STS number 4 at the first node, you must use STS number 4 at each node to transport that service around the ring. Respectively, if you add an SDH-VC-4 service onto STS number 4 (a-4) at the first node, you must use STS number 4 at each node to transport that service around the ring.

• For Ethernet drop-and-continue service applications, ensure that LCAS is not enabled on any of the EOS ports. Otherwise, because LCAS is effectively a bidirectional feature, the TransNav management system raises a TLCT alarm on the source EOS port and a TLCR alarm on the subscriber EOS port due to the incorrect provisioning.

Procedures Required to Provision a Drop and Continue Service

To fully provision a drop-and-continue service, you must provision a combination of three types of services at different points in your network. Use the following procedures to help you provision drop-and-continue services on a Traverse system.1. Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services,”

Create a SONET Service, page 4-352. Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,” Create

an SDH Service, page 4-583. Section 4—Creating ADM Services, Chapter 2—“Common Procedures for


These procedures describe how to create a spe-cific service and change relevant parameters only. See the TransNav Management System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide• Section 6—Services, Chapter 3—“SDH

Services,” page 6-31• Section 2—Services, Chapter 2—“SONET

Services,” page 2-15

Provisioning model • Hop-by-hop only


Bandwidth requirements • SDH-VC3: 48.960 Mbps• SDH-VC4: 150.336 Mbps• SONET-STS: 48.960 Mbps


Table 5-5 Drop-and-Continue Service Requirements (continued)



Traverse Provisioning Guide, Section 5: Creating Service ApplicationsParameters Required to Provision Drop and Continue Services

Parameters Required to Provision Drop and Continue Services

Use the information in the following table to help you provision drop-and-continue services on a UPSR or an SNCP ring.

Table 5-6 Required Parameters for Drop-and-Continue Services

Service Parameter Value

ALL SERVICES

Service Tab Service Type • SDH• SONET-STS

Add Service

Endpoints Source Port Tributary port

Destination Port Trunk (East or West) port on ring

Dest. Starting Path Must match on all nodes in ring

Attributes Directionality Uni-Directional

Protection Type FULL

Drop Service

Endpoints Source Port Trunk (East or West) port on ring

Src. Starting Path Must match Dest. Starting Sts from Source Service.

Destination Port Drop port (tributary)

Dest. Starting Path Any available starting STS num-ber

Attributes Directionality Uni-Directional

Protection Type FULL

Continue Service

Endpoints Source Port Trunk (East or West) port on ring

Src. Starting Path Must match Dest. Starting Path from Source Service.

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

Dest. Starting Path Must match Dest. Starting Path from Source Service.

Attributes Directionality Uni-Directional on drop nodes.

Bi-directional on intermediate nodes.

Protection Type Unprotected (protected by physi-cal ring)



Chapter 4Creating Services over Interconnected UPSR or SNCP Rings

Introduction This chapter explains how to create path-protected bidirectional services in a 2-node interconnected ring configuration. • Services over Interconnected UPSR or SNCP Rings, page 5-25• Example of a SONET Bi-directional Protected Path, page 5-26• Example of Bi-directional Protected E1 and VT Services, page 5-29• Cards Required at Interconnecting Nodes, page 5-30• Before You Create Services over Interconnected Rings, page 5-30• Guidelines to Provision Services over Interconnected Rings, page 5-31• Procedures Required to Provision Services over Interconnected Rings,

page 5-31

If your system includes 2-port OC-48 or STM-16 cards, see Section 4—Creating ADM Services, Chapter 5—“Creating 2-Port OC-48/STM-16 Services,” page 4-71 for additional information.

Services over Interconnected UPSR or SNCP Rings

Interconnected ring configurations use the same two or more nodes in separate ring topologies.

To provision services in an interconnected ring configuration, create a combination of the following services at different nodes in the network:• Add Service: This service can be any one of the supported service types. Create

this service at each node that adds traffic to both of the interconnected rings.• Pass Through Service: This service is a SONET or SDH service that passes the

traffic though the node. Create this type of service at all intermediate nodes in the interconnected ring configuration that do not add or drop traffic.

• Drop Service: This service drops traffic from one ring to the other. Create this service at each interconnecting node (a node that is a member of both ring configurations).

• Continue Service: This service carries the traffic to the next interconnecting node. After you have dropped traffic at the first interconnecting node, continue the signal around to the next interconnecting node to create an alternative path for the traffic. Create this service at each interconnecting node.


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsExample of a SONET Bi-directional Protected Path

Example of a SONET Bi-directional Protected Path

To create a protected bi-directional STS path across two interconnected rings, create a series of SONET services at each node. In the following example, traffic enters each ring at Node A and Node D and is bridged in both directions around each ring.

On a ring configuration in a Traverse network, the East card always transmits the working signal clockwise around the ring. The West card always receives the working signal.

In this example, the traffic from Node A (working) travels to the interconnecting node (INCT Node 1) in the clockwise direction. The traffic added at Node D also travels in the clockwise direction to INCT Node 2.

Figure 5-12 Bi-directional Protected STS Paths over Interconnected UPSRs

In this example, use a series of SONET-STS services at each node to create a bidirectional protected path for STS traffic across both rings.

At Node A and Node D, create a service that adds traffic to both rings. Tag the services as FULL protected to bridge the signal in both directions around the ring.

At every intermediate node, create a pass-through service that simply passes the traffic through the node.

At each of the interconnecting nodes, create a series of unidirectional services to drop the traffic from one ring to the other. Bridge each signal (forward working and forward protect) to both the East and West ports of the other ring to create alternate paths.

W

Slot 2Slot 1

E

OC48OC48

Slot 16Slot 15

W E

GCMOC48

GCMOC48

W

INCT Node 1Slot 2Slot 1

E

OC48OC48

Slot 16Slot 15

W E

GCMOC48

GCMOC48

56

10

9

INCT Node 2

161314

Node A

Node B Node D

Node C

1

3 2

4Working

Protect Working

Protect

78

1112

15

At Node B (3) and Node C (4)Service Type: SONET-STS (Pass Through)Directionality: BidirectionalProtection Type: Unprotected

At Node A (1) and Node D (2):Service Type: SONET-STS (Add)Directionality: BidirectionalProtection Type: FULL

At INCT Node 1 (9 and 10)Service Type: SONET-STS (Continue)Resource Advisory: OFFDirectionality: UnidirectionalProtection Type: 1+1 Path Protected

At INCT Node 1 (5, 6, 7, and 8)5. Service Type: SONET-STS (Drop)Resource Advisory: OFFDirectionality: UnidirectionalProtection Type: Unprotected

At INCT Node 2 (15 and 16)Service Type: SONET-STS (Continue)Resource Advisory: OFFDirectionality: UnidirectionalProtection Type: 1+1 Path Protected

At INCT Node 2 (11, 12, 13, and 14)5. Service Type: SONET-STS (Drop)Resource Advisory: OFFDirectionality: UnidirectionalProtection Type: Unprotected

E

W

W

E

E

W

E

W

W

W

W

E

E

E

W

E

Ring 1OC-48 UPSR

Ring 2OC-48 UPSR


Chapter 4 Creating Services over Interconnected UPSR or SNCP RingsExample of an SDH Bi-directional Protected Path

Example of an SDH Bi-directional Protected Path

To create a protected bi-directional VC4 path across two interconnected rings, create a series of SDH services at each node. In the following example, traffic enters each ring at Node A and Node D and is bridged in both directions around each ring.

On a ring configuration in a Traverse network, the East card always transmits the working signal clockwise around the ring. The West card always receives the working signal.

In this example, the traffic from Node A (working) travels to the interconnecting node (INCT Node 1) in the clockwise direction. The traffic added at Node D also travels in the clockwise direction to INCT Node 2.

Figure 5-13 Bi-directional Protected VC4 Paths over Interconnected SNCP Rings

In this example, use a series of SDH-VC4 services at each node to create a bidirectional protected path for STS traffic across both rings.

At Node A and Node D, create a service that adds traffic to both rings. Tag the services as FULL protected to bridge the signal in both directions around the ring.


At each of the interconnecting nodes, create a series of unidirectional services to drop the traffic from one ring to the other. Bridge each signal (forward working and forward protect) to both the East and West ports of the other ring to create alternate paths.

W

Slot 2Slot 1

E

STM16STM16

Slot 16Slot 15

W E

GCMSTM16

GCMSTM16

W


E

STM16STM16Slot 16Slot 15

W E

GCMSTM16

GCMSTM16

56

10

9

INCT Node 2

161314

Node A

Node B Node D

Node C

1

3 2

4Working

Protect Working

Protect

78

1112

15

At Node B (3) and Node C (4)Service Type: SDH-VC4 (Pass Through)Directionality: BidirectionalProtection Type: Unprotected

At Node A (1) and Node D (2):Service Type: SDH-VC4 (Add)Directionality: BidirectionalProtection Type: FULL

At INCT Node 1 (9 and 10)Service Type: SDH-VC4 (Continue)Directionality: UnidirectionalProtection Type: 1+1 Path Protected

At INCT Node 1 (5, 6, 7, and 8)5. Service Type: SDH-VC4 (Drop)Directionality: UnidirectionalProtection Type: Unprotected

At INCT Node 2 (15 and 16)Service Type: SDH-VC4 (Continue)Directionality: UnidirectionalProtection Type: 1+1 Path Protected

At INCT Node 2 (11, 12, 13, and 14)5. Service Type: SDH-VC4 (Drop)Directionality: UnidirectionalProtection Type: Unprotected

E

W

W

E

E

W

E

W

W

W

W

E

E

E

W

E

Ring 1STM-16 SNCP

Ring 2STM-16 SNCP


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsExample of Bi-directional Protected DS1 and VT1.5 Services

Example of Bi-directional Protected DS1 and VT1.5 Services

In the following example, DS1 traffic enters each ring at Node A and Node D and is bridged in both directions around each ring. The traffic from Node A (working) travels to INCT Node 1 in the clockwise direction. The traffic added at Node D travels in the clockwise direction to INCT Node 2.

Figure 5-14 Bi-directional DS1 and VT1.5 Services over Interconnected UPSR

In this example, create a combination of services: SONET-STS services and SONET-VT services to create a bi-directional path for DS1 channels across the rings. At Node A and Node D, create a service that adds traffic to both rings. Tag the services as FULL protected to bridge the signal in both directions around the ring.


At each of the interconnecting nodes, create a series of unidirectional services to drop the traffic from one ring to the other. The incoming signal is a VT-mapped STS. Use a SONET-VT service to drop VTs to the second ring. Use a SONET-STS service to continue the VT-mapped STS to the next node to create an alternate path for the DS1 traffic.

5GVC/VT

5GVC/VT

5GVC/VT

5GVC/VT

W

W

Node A

Node B

Node C

Node D


EW

OC12OC12Slot 16Slot 15

W E

GCMOC48

GCMOC48

Slot 10Slot 9


E

OC12OC12Slot 16Slot 15

W E

GCMOC48

GCMOC48

Slot 10Slot 9

5

10

15

14

3

4Working

Protect Working

Protect

7

8

13

1

69

16

1211

2

At Node A (1) and Node D (2):Service Type: DS1-Mux-VT (Add)Directionality: BidirectionalProtection Type: UPSR Protected

At INCT Node 1 (5, 6, 7, and 8)Service Type: SONET-VT (x 28) (Drop)Resource Advisory: OFFDirectionality: UnidirectionalProtection Type: UPSR Ingress

At Node B (3) and Node C (4):Service Type: SONET-STS (Pass Through)Directionality: BidirectionalProtection Type: Unprotected

At INCT Node 1 (9 and 10):Service Type: SONET-STS (Continue)Resource Advisory: OFFDirectionality: UnidirectionalProtection Type: Unprotected

At INCT Node 2 (11, 12, 13, and 14)Service Type: SONET-VT (x 28) (Drop)Resource Advisory: OFFDirectionality: UnidirectionalProtection Type: UPSR Ingress

At INCT Node 2 (15 and 16):Service Type: SONET-STS (Continue)Resource Advisory: OFFDirectionality: UnidirectionalProtection Type: Unprotected

E

W

W

E

E

W

E

W

W

W

E

E

EW

E

Ring 1OC-48 UPSR

Ring 2OC-48 UPSR


Chapter 4 Creating Services over Interconnected UPSR or SNCP RingsExample of Bi-directional Protected E1 and VT Services

Example of Bi-directional Protected E1 and VT Services

In the following example, E1 traffic enters each ring at Node A and Node D and is bridged in both directions around each ring. The traffic from Node A (working) travels to INCT Node 1 in the clockwise direction. The traffic added at Node D travels in the clockwise direction to INCT Node 2.

Figure 5-15 Bi-directional E1 and VC-12 Services over Interconnected SNCP Rings

In this example, create a combination of services: SDH-VC3 services and SDH-VC12 services to create a bi-directional path for E1 channels across the rings. At Node A and Node D, create a service that adds traffic to both rings. Tag the services as FULL protected to bridge the signal in both directions around the ring.


At each of the interconnecting nodes, create a series of unidirectional services to drop the traffic from one ring to the other. The incoming signal is a VC12-mapped-VC3. Use an SDH-VC12 service to drop VTs to the second ring. Use an SDH-VC3 service to continue the VC12-mapped-VC3 to the next node to create an alternate path for the DS1 traffic.

5GVC/VT

5GVC/VT

5GVC/VT

5GVC/VT

W

W

Node A

Node B

Node C

Node D


EW

Slot 16Slot 15

W E

Slot 10Slot 9


E

Slot 16Slot 15

W E

Slot 10Slot 9

5

10

15

14

3

4Working

Protect Working

Protect

7

8

13

1

69

16

1211

2

At Node A (1) and Node D (2):Service Type: SDH-VC3 (Add)Directionality: BidirectionalProtection Type: FULL

At INCT Node 1 (5, 6, 7, and 8)Service Type: SDH-VC12 (x 21) (Drop)Directionality: UnidirectionalProtection Type: UPSR Ingress

At Node B (3) and Node C (4):Service Type: SDH-VC3 (Pass Through)Directionality: BidirectionalProtection Type: Unprotected

At INCT Node 1 (9 and 10):Service Type: SDH-VC3 (Continue)Directionality: UnidirectionalProtection Type: Unprotected

At INCT Node 2 (11, 12, 13, and 14)Service Type: SDH-VC12 (x 21) (Drop)Directionality: UnidirectionalProtection Type: UPSR Ingress

At INCT Node 2 (15 and 16):Service Type: SDH-VC3 (Continue)Directionality: UnidirectionalProtection Type: Unprotected

E

W

W

E

E

W

E

W

W

W

E

E

EW

E

Ring 1STM-16 SNCP

Ring 2STM-16 SNCP

GCMSTM16

GCMSTM16

GCMSTM16

GCMSTM16

STM16 STM16

STM16 STM16


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsCards Required at Interconnecting Nodes

Cards Required at Interconnecting Nodes

This table lists the Traverse cards required at the interconnecting nodes. Other nodes require cards depending on tributary services.

Before You Create Services over Interconnected Rings

Review the information in this topic before you create services over interconnected UPSR or SNCP rings.

Table 5-7 Cards Required at the Interconnecting Nodes


SDH STM-N STM-N

SONET OC-N OC-N

Other cards

VT/TU 5G Switch (for low order and SONET-VT services only)

n/a n/a

Table 5-8 Protected Ring Interconnection Requirements




Hardware

See Cards Required at Interconnecting Nodes, page 5-30.


Hardware is installed in an interconnected ring configuration.

n/a

Software



Protection groups are configured.• Each ring in the configuration is configured as a

UPSR or SNCP ring.• Electrical tributary cards are configured in an

equipment protection group.• VT/TU 5G Switch cards are configured in an

equipment protection group.• Tributary facilities are configured in a 1+1

APS/MSP protection group.



Chapter 4 Creating Services over Interconnected UPSR or SNCP RingsProcedures Required to Provision Services over Interconnected Rings

Guidelines to Provision Services over Interconnected Rings

The guidelines to create services in an interconnected UPSR or SNCP ring configuration are:• Create and activate all services on one node before you move to the next service.• At the interconnecting nodes, create the Drop services first, then create the

Continue services.• Force10 recommends that the bi-directional path use the same path number at each

node in both rings.

Procedures Required to Provision Services over Interconnected Rings

To provision services across interconnected rings, you must create a combination of service at different nodes in the network. Use the following procedures to help you provision services in an interconnected ring configuration:1. Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services,”

Create a SONET Service, page 4-35.2. Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,” Create

an SDH Service, page 4-58.3. Section 4—Creating ADM Services, Chapter 2—“Common Procedures for

Services,” Activate or Deactivate a Service, page 4-16.

All source and destination interfaces are config-ured correctly.


These procedures describe how to create bi-direc-tional paths over interconnected rings. These pro-cedures include relevant parameters only.

See Traverse Provisioning Guide, Section 4—Creating ADM Services for detailed pro-cedures on all service types

See TransNav Management System GUI Guide, Section 6—Services for descriptions of other fields on screen

Provisioning model • Hop-by-hop only


Table 5-8 Protected Ring Interconnection Requirements (continued)



Traverse Provisioning Guide, Section 5: Creating Service ApplicationsProcedures Required to Provision Services over Interconnected Rings



Chapter 5Creating Transmux Services

Introduction The optical transmux feature transforms incoming channelized DS3 signals to VC- or VT-mapped payloads on one node. Use this feature together with the VTX/VCX component or the VT/TU 5G Switch card to switch these payloads on the same node.

This chapter explains how to create an optical transmux service in a Traverse network. • G.747 Services, page 5-34• Switching DS1s Inside a Channelized DS3, page 5-35• Switching E1s Inside a Channelized DS3, page 5-36• Cards Required to Create a Transmux Service, page 5-37• Before You Create a Transmux Service, page 5-40• Guidelines to Provision an Optical Transmux Service, page 5-41• Procedures Required to Provision an Optical Transmux Service, page 5-42• Assign and Configure Transmux Resources, page 5-43• Configure an Optical Transmux Service, page 5-46



Traverse Provisioning Guide, Section 5: Creating Service ApplicationsG.747 Services

G.747 Services The Traverse and TE-100 system supports the ITU standard G.747: Second Order Digital Multiplex Equipment operating at 6312 kbit/s and Multiplexing Three Tributaries at 2048 kbit/s. Specifically, the system can multiplex either 28 DS1 signals or 21 E1 signals into a channelized DS3 signal. The system uses this standard in the transmux application.

The following hierarchy shows E1 or DS1 payloads multiplexed into a SONET signal. Each path shows a valid source or destination for an optical transmux service.

Figure 5-16 E1 and DS1 Payloads on SONET

The following hierarchy shows E1 and DS1 payloads multiplexed into an STM signal. Each path shows a valid source or destination for an optical transmux service.

Figure 5-17 E1 and DS1 Payloads on STM

OC-N

E1

STS

VT2

DS1

DS3

DS1

VT1.5DS3

E1

STM-N

DS1 E1

AU4

VC11 VC12VC3

DS1 E1

AU3

VC11 VC12DS3

DS1 E1

DS3

DS3

DS1 E1

DS3


Chapter 5 Creating Transmux ServicesSwitching DS1s Inside a Channelized DS3

Switching DS1s Inside a Channelized DS3

In the following example, create a series of services at different nodes to be able to switch the DS1 traffic inside a channelized DS3 signal.1. At Node 1, create a DS3-CC service and bridge it around the ring.2. At Node 2, create a service that passes the traffic through the node. 3. At Node 3, use the optical transmux feature to convert the channelized DS3 signal

into a VT-mapped STS. Create a SONET-VT service and indicate that the incoming and outgoing signals are transformed to a VT-mapped STS. Use the VT Switch capabilities to switch traffic at the VT layer.

4. At Node 4, create another pass-through service. 5. At Node 5, create a DS3-CC service to connect the traffic to the M13.

Figure 5-18 Switching DS1 Signals Inside a Channelized DS3

In the above example, if a TransAccess 100 Mux were connected to Node 5 instead of the M13, you would only need to transform the source signal at Node 3 (Source DS1 Mapping parameter). At Node 5, you would create a SONET-STS service to the EC1 port connected to the TransAccess 100 Mux.

4. Service Type: SONET-VT (x 28)Source: Node 3/slot-1/port-1/sts-1/VTG1-VT1Source DS1 Mapping:Dest: Node 3/slot-16/port-1/sts-1/VTG4-VT3Dest DS1 Mapping:Protection Type: FULL

1. Service Type: DS3-CCSource: Node 1/slot-2/port-3 DS3CCDest: Node1/slot-16/port-1/sts-1/Protection Type: FULL

3. Node 3/slot-6/port-1 STSTMXNode 3/slot-6/port-2 STSTMX

6. Service Type: DS3-CCSource: Node 5/slot-2/port-3 DS3CCDest: Node 5/slot-15/port-1/sts-1Protection Type: FULL

Node 1

W E

GCMOC48

Slot 16

GCMOC48

Slot 15Slot 1DS3 DS3

Slot 2

Node 5

W E

GCMOC48

Slot 16

GCMOC48

Slot 15Slot 1DS3 DS3

Slot 2

OC-48 UPSR

OC-48 UPSR

W E

OC48Slot 1

Node 3

W E

GCMOC48

Slot 16

GCMOC48

Slot 15Slot 2 Slot 5TMX TMX VT VTOC48

Slot 6 Slot 7 Slot 8

1.

M13

3.

M13

4.

6.

Node 2

Node 4

2. Service Type: SONET-STSSource: Node 2/slot-15/port-1/sts-1Dest: Node 2/slot-16/port-1/sts-1Directionality: Bi-directional

5. Service Type: SONET-STSSource: Node 4/slot-15/port-1/sts-1Dest: Node 4/slot-16/port-1/sts-1Directionality: Bi-directional

3.


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsSwitching E1s Inside a Channelized DS3

Switching E1s Inside a Channelized DS3

In the following example, create a series of services at different nodes to be able to switch the E1 traffic inside a channelized DS3 signal.1. At Node 1, create an SDH Tunnel to transport traffic from Node 1 to Node 3. 2. At Node 1, create a SDH (VC3) service and bridge it around the ring.3. At Node 2, create a service that passes the traffic through the node. 4. At Node 3, create another SDH Tunnel to transport the low order traffic from

Node 3 to Node 5 [Bandwidth = VC-4 (Grooming)]. Then use the optical transmux feature to convert the channelized DS3 signal to a VC-structured STM and bridge it onto the second ring. Create a series of VC12 services and indicate that the source signal is a channelized DS3. Use the VT/TU 5G Switch capabilities to switch traffic at the VC layer.

5. At Node 4, create another pass through service. 6. At Node 5, create another SDH service to connect the traffic to the M13.

Figure 5-19 Switching E1 Signals Inside a Channelized DS3

5

5

5GVC/VT

5GVC/VT

6. Service Type: SDH-VC12 (x 21)Source: Node 3/s-1/p-1/a1-1/tug3-1/tug2-1/vc12-2Dest: Node 3/s-16/p-1/a1-1/tug3-1/tug2-1/vc12-2Protection Type: FULLSource E1 Mapping: (TMX port s-5/p-1)Dest E1 Mapping: (TMX port s-5/p-2)

5. Node 3/slot-6/port-1 and port 2: STSTMXLine Format: CBITDS3 Mapping: E1

STM-16SNCP Ring

W E

STM16Slot 1

Node 3

W E

GCMSTM16Slot 16

GCMSTM16Slot 15Slot 2 Slot 5

TMX TMXSTM16Slot 6 Slot 7 Slot 8

6

Node 2

Node 4

3. Service Type: SDHBandwidth: VC3Source: Node 2/s-15/p-1/a1-1/tug3-1/vc3Dest: Node 2/slot-16/p-1/a1-1/tug3-1/vc3Directionality: Bi-directional

1 4

STM-16SNCP Ring

4. Service Type: SDH-TunnelBandwidth: VC4 (Grooming)Source: Node 3/s-16/a1-1Dest: Node 5/s-15/p-1/a1-1Protection Type: FULL

7. Service Type: SDHBandwidth: VC3Source: Node 4/s-15/p-1/a1-1/tug3-1/vc3Dest: Node 4/slot-16/p-1/a1-1/tug3-1/vc3Directionality: Bi-directional

Node 1

W E

GCMSTM16Slot 16

GCMSTM16Slot 15Slot 1

DS3 DS3Slot 2

2

M13

11. Service Type: SDH-TunnelBandwidth: VC4 (VC3)Source: Node 1/s-16/a1-1Dest: Node 3/s-1/p-1/a1-1Protection Type: FULL

2. Service Type: SDHBandwidth: VC3Source: Node 1/s-2/port-3 DS3CCDest: Node1/s-16/p-1/a1-1/tug3-1/vc3Protection Type: FULL

Node 5

W E

GCMSTM16Slot 16

GCMSTM16Slot 15Slot 1

DS3 DS3Slot 2

8

M13

4

DS3

8. Service Type: SDHBandwidth: VC3Source: Node 1/s-2/port-3 DS3CCDest: Node1/s-16/p-1/a1-1/tug3-1/vc3Protection Type: FULL

DS3

DS3

TR 00063


Chapter 5 Creating Transmux ServicesCards Required to Create a Transmux Service

Cards Required to Create a Transmux Service

The following tables lists the Traverse SONET and SDH cards required to create a transmux service.

Table 5-9 SONET Cards Required for a Transmux Service

Source Card Destination Card

OC-N STM-NOC-NDS3CC (EC1 mode)1

E31

DS3TMXDS3TMX (EC1 mode)DS1E1UTMX-24UTMX-48

EC1 STM-NOC-NEC1DS3CC1 E31

DS3TMX2

UTMX-242

UTMX-482

DS1E1

DS3-CC1

E31STM-NOC-NEC1DS3CCE3

DS1 E1 DS3TMX UTMX-24UTMX-48

STM-NOC-NEC1 2

DS3TMX2

UTMX-242

UTMX-482

DS12

E12

EoPDH STM-NOC-NDS3CC1

E31

EC1DS3TMXE3UTMX-242

UTMX-482 DS1E1EoPDH


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsCards Required to Create a Transmux Service

Other cards

DS3TMX, UTMX-24, UTMX-48 One optical transmux resource (one STSTMX port) is required for each STM-0 or STS (ingress or egress) carrying a channelized DS3.

VT/TU 5G Switch card Required to create VT1.5, VC11, and VC12 services only.

1 For STS switched services only

2 For VT1.5 switched services only

Table 5-10 SDH Cards Required for a Transmux Service


STM-NOC-N

STM-NOC-NDS3CC (EC1 mode)1

E31

DS3TMX DS3TMX (EC1 mode)DS1E1UTMX-24UTMX-48

EC1 STM-NOC-NEC1DS3TMX2 DS3CC1

E31 UTMX-242

UTMX-482

DS12

E12

DS3CC1

E31STM-NOC-NEC1DS3CCE3

DS1 E1 DS3TMX UTMX-24UTMX-48

STM-NOC-NEC12

DS3TMX2 UTMX-242

UTMX-482

E12

Table 5-9 SONET Cards Required for a Transmux Service (continued)



Chapter 5 Creating Transmux ServicesCards Required to Create a Transmux Service

EoPDH STM-NOC-NEC1DS3CC1

E31

DS3TMXE3UTMX-24UTMX-48DS1E1EoPDH

Other cards

DS3TMXUTMX-24UTMX-48

One optical transmux resource (one STSTMX port) is required for each STM-0 or STS (ingress or egress) carrying a channelized DS3.

VT/TU 5G Switch card Required to create VC11 and VC12 services only.

1 For VC-3 and VC-4 switched services only.

2 For VC-11 and VC-12 switched services only.

Table 5-10 SDH Cards Required for a Transmux Service (continued)



Traverse Provisioning Guide, Section 5: Creating Service ApplicationsBefore You Create a Transmux Service

Before You Create a Transmux Service

Review the information in this topic before you create a transmux service.

Table 5-11 Transmux Service Requirements




Hardware

See Cards Required to Create a Transmux Ser-vice, page 5-37



Software



Protection groups are configured for the follow-ing cards:• SDH or SONET facilities• DS3TMX cards• VT/TU 5G Switch card• UTMX cards


Source and destination interfaces are configured correctly.

Traverse Provisioning Guide, Section 2—Configuring TDM Equipment, Chapter 2—“Configuring SONET Equipment,” page 2-3


TransNav Management System GUI Guide• Section 6—Services, Chapter 3—“SDH

Services,” page 6-31• Section 2—Services, Chapter 2—“SONET


Provisioning model

Hop-by-hop only


SDH to SONET Interworking. You can create an optical transmux service between a SONET interface and an SDH interface. The interfaces can be the same or different types.

n/a


Chapter 5 Creating Transmux ServicesGuidelines to Provision an Optical Transmux Service

Guidelines to Provision an Optical Transmux Service

The guidelines to provision an optical transmux service are:• There must be at least one DS3TMX or UTMX card in the same node. This card

can be in an equipment protection group. See Section 3—Creating Protection Groups, Chapter 4—“Creating Equipment Protection Groups,” page 3-21 for detailed guidelines and procedures to create the equipment protection group.

• Reserve one transmux resource (STSTMX port) for each STM-0 or STS that is:– Carrying a channelized DS3 that needs to be converted to a VC- or

VT-structured payload.– Carrying a channelized DS3 and switching occurs for the individual channels.

• To switch DS1s or E1s inside the channelized DS3, there must be at least one VT/TU 5G switch card or a VTX component in the same node.

• Only one endpoint of the service must be either an STS or an STM path. The Traverse supports OC-N, EC3, STM-N, DS1, E1, and DS3TMX subports as the other endpoint.

• EC1 endpoints can be used only for VT-switched services.• Each DS3TMX card can support up to 12 transmux instances (one STM-0 or one

STS per TMX port). • Each UTMX card must have at least one optical resource (one STSTMX port) on

the same node.• Each UTMX-24 card can support up to 24 transmux instances (one STM-0 or one

STS per TMX port).• Each UTMX-48 card can support up to 48 transmux instances (one STM-0 or one

STS per TMX port). • On the UTMX-48 card, ports 25 through 48 are logical ports. Only STS1-TMX is

supported. In a DCS system, all 48 ports can be used as STS1-TMX.


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsProcedures Required to Provision an Optical Transmux Service

Procedures Required to Provision an Optical Transmux Service

To provision a transmux service, you must provision a combination of services at different points in your network. Use the following procedures to help you provision an optical transmux feature on a Traverse system.1. Section 5—Creating Service Applications, Chapter 5—“Creating Transmux

Services,” Assign and Configure Transmux Resources, page 5-432. Section 5—Creating Service Applications, Chapter 5—“Creating Transmux

Services,” Configure an Optical Transmux Service, page 5-463. Section 4—Creating ADM Services, Chapter 2—“Common Procedures for


These procedures reference required parameters only. Use the following procedures to reference all configurable parameters for each service type:1. Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,”


page 4-19


Chapter 5 Creating Transmux ServicesAssign and Configure Transmux Resources

Assign and Configure Transmux Resources

Use this procedure to assign and configure transmux resources on the DS3TMX and UTMX cards.

Important: Use the CLI command exec interface switch tmxfmt format ststmx to change all TMX ports in one node.

Table 5-12 Assign and Configure Transmux Resources

Step Procedure

1 Review this topic in Before You Create a Transmux Service, page 5-40.

2 In Map View, double click the node that is performing the optical transmux functions.

3 In Shelf View, assign transmux resources for each STS requiring transformation.

Figure 5-20 Click a TMX Port, Click the Config Tab

a. Click a TMX port on a DS3TMX or UTMX card.b. Click the Config tab.

4

5


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsAssign and Configure Transmux Resources

4 Select STS1TMX, then click Switch.

Figure 5-21 Switch to STS1TMX Port Type

5 In the Confirm Switch dialog box, click Yes to confirm the change.

Figure 5-22 Confirm Switch Dialog Box

Table 5-12 Assign and Configure Transmux Resources (continued)

Step Procedure


Chapter 5 Creating Transmux ServicesAssign and Configure Transmux Resources

6 Configure the interface parameters for the STS1TMX port type:

Line Format: Select one of the following:• M23 (default): Seven DS2 signals asynchronously multiplexed into

the DS3 signal.• CBIT: 28 DS-1 signals are multiplexed into the DS3 signal with the

C-bit used as control bit.

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 the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 2—“SONET Equipment,” Table 5-1 GR-253 and Sequential VT Mapping Formats, page 5-7 for the list of mapping formats. Select one of the following values: • Non-Sequential (default)• Sequential

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


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 control bit position.


Subport Mapping: Select the payload of the DS1 channels. Configurable only if DS3 Mapping is DS1.• VT1.5/VC11 (default): The DS1 channel is carried in a VT1.5 or

VC11 payload. All 28 subports are available.• VT2/VC12: The DS1 channel is carried in a VT2 or VC12 payloads.

Only the first 21 subports are available.

7 Repeat Steps 3 through 6 for each STM-0 or STS carrying a channelized DS3 payload.

8 The Assign and Configure Transmux Resources procedure is complete.

Continue to the next procedure, Configure Transmux Services, page 5-46.

Table 5-12 Assign and Configure Transmux Resources (continued)

Step Procedure


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsConfigure an Optical Transmux Service

Configure an Optical Transmux Service

Use this procedure to configure the optical transmux attributes of a service. This procedure references required parameters only.

Use the following procedures to reference all configurable parameters for each service type:• Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,”

page 4-41• Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services,”

page 4-19

Table 5-13 Configure Transmux Services

Step Procedure

1 Complete the procedure Assign and Configure Transmux Resources, page 5-43.

2 In Map View, double click the node that is performing optical transmux functions.

3 Use the following procedures to create a SONET or SDH service. • Create an SDH Service, page 4-58• Create a SONET Service, page 4-35


Chapter 5 Creating Transmux ServicesConfigure an Optical Transmux Service

4 If this is an SDH-VC3 or a SONET-STS service, enter the transmux information for the service. On the Create Service tab, click the Advanced button to display the Advanced Parameters dialog box.

Figure 5-23 Configure Transmux Parameters

• Source DS3 Mapping: Select this parameter if the source signal carries a channelized DS3 payload.As soon as you check this parameter, the Choose a TMX Port dialog box appears. Select the port you designated as the STS1TMX resource.

• Destination DS3 Mapping: Select this parameter if the destination signal carries a channelized DS3 payload.As soon as you check this parameter, the Choose a TMX Port dialog box appears. Select the port you designated as the STS1TMX resource.

5 If this is a VC11, VC12, or SONET-VT service, enter the transmux information for the service. On the Create Service tab, click the Advanced button.• Source DS1 Mapping: Select this parameter if the source signal

carries a channelized DS3 payload.As soon as you check this parameter, the Choose a TMX Port dialog box appears. Select the port you designated as the STS1TMX resource.

• Destination DS1 Mapping: Select this parameter if the destination signal carries a channelized DS3 payload.As soon as you check this parameter, the Choose a TMX Port dialog box appears. Select the port you designated as the STS1TMX resource.

6 Repeat Steps 2 through 5 for each transmux service

7 Complete the procedure Activate or Deactivate a Service, page 4-16 to activate the services.

8 The Configure Transmux Services procedure is complete.

Table 5-13 Configure Transmux Services (continued)

Step Procedure


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsConfigure an Optical Transmux Service



Chapter 6Creating Transparent Services

Introduction This chapter explains how to create a transparent service in a Traverse network. • Example of SONET Transparent Services, page 5-50• Example of SDH Transparent Services, page 5-51• Cards Required to Create a Transparent Service, page 5-52• Before You Create a Transparent Service, page 5-52• Guidelines to Provision Transparent Services, page 5-53• Procedures Required to Create a Transparent Service, page 5-54• Disable Control Data Parameter on Nodes Linked to Third-Party Equipment,

page 5-54• Provision the Transparent Service, page 5-55



Traverse Provisioning Guide, Section 5: Creating Service ApplicationsExample of SONET Transparent Services

Example of SONET Transparent Services

A transparent service transports the data (payload and overhead) of an entire incoming link from the tributary equipment and carries it over a network of higher bandwidth trunks, creating a virtual trunk. In the transparent multiplexing application, the tributary connections and fiber span between the Traverse nodes are unprotected. The subtending third-party vendor equipment provides all protection switching and bandwidth management.

Figure 5-24 Transparent SONET Service

In the above example, create a series of SONET services, two at each node. The Control Data parameter is disabled at any SONET port connected to third-party equipment. The transparency flag is turned ON for each SONET service. The remaining bandwidth on the OC-192 can be used for additional unprotected or 1+1 path protected tributary services.

In addition to carrying regular traffic, the transparency service:• Forwards the overhead bytes contained in the first three STS-1s on the tributary

equipment. The overhead bytes can be configured in one of the following ways:– D1-D12, K1, K2, E1, and J0– D1-D12, K1, K2, E1, and F1

• Propagates AIS-L when B1-B2 errors are occurring at a high enough rate for an alarm to be declared.

• Duplicates STS formatting seen on the incoming link across the transparent service. In this respect, the bandwidth selection that was made when creating the service is irrelevant—it does not mean that a STS-48c will be formatted on the link. It simply is a way of ensuring no additional services will be created on the link.

3rd party vendor equipmentOC-48 (working)

3rd party vendor equipmentOC-48 (protecting)

3rd party vendor equipmentOC-48 (working)

3rd party vendor equipmentOC-48 (protecting)

Slot 1 Slot 11Slot 3 Slot 13

Node 1Slot 13

OC48Slot 2

OC48Slot 1 Slot 11

1

Node 2Slot 1

OC48Slot 13Slot 3

OC48Slot 14

6

Control Data = DisabledControl Data = Disabled

OC192 OC192 OC192 OC192OC192OC192 OC192 OC192

2 43 5

1. Service Type = SONET-STSSrc: Node 1/slot-2/port-1/sts-1Dest: Node 1/slot-11/port-1/sts-1Bandwidth = 48cTransparency = ON






Node 3

Transparent ServiceTributarydata

Tributarydata


Chapter 6 Creating Transparent ServicesExample of SDH Transparent Services

Example of SDH Transparent Services

A transparent service transports the data (payload and overhead) of an entire incoming link from the tributary equipment and carries it over a network of higher bandwidth trunks, creating a virtual trunk. In the transparent multiplexing application, the tributary connections and fiber span between the Traverse nodes are unprotected. The subtending third-party vendor equipment provides all protection switching and bandwidth management.

Figure 5-25 Transparent SDH Service

In the above example, create a series of SDH services, two at each node. The Control Data parameter is disabled at any SDH port connected to third-party equipment. The transparency flag is turned ON for each SDH service. The remaining bandwidth on the STM-64 can be used for additional unprotected or 1+1 path protected tributary services.

In addition to carrying regular traffic, the transparency service:• Forwards the overhead bytes contained in the first three STS-1s on the tributary

equipment. The overhead bytes can be configured in one of the following ways:– D1-D12, K1, K2, E1, and J0– D1-D12, K1, K2, and F1

• Propagates AIS-L when B1-B2 errors are occurring at a high enough rate for an alarm to be declared.

• Duplicates STM formatting seen on the incoming link across the transparent service. In this respect, the bandwidth selection that was made when creating the service is irrelevant—it does not mean that a VC-4-16c will be formatted on the link; it simply is a way of ensuring no additional services will be created on the link.

3rd party vendor equipmentSTM-16 (working)

3rd party vendor equipmentSTM-16 (protecting)

3rd party vendor equipmentSTM-16 (working)

3rd party vendor equipmentSTM-16 (protecting)

Slot 1 Slot 11Slot 3 Slot 13

Node 1Slot 13

STM16Slot 2

STM16Slot 1 Slot 11

1

Node 3Slot 1

STM16Slot 13Slot 3

STM16Slot 14

6

Control Data = DisabledControl Data = Disabled

STM64 STM64 STM64 STM64STM64STM64 STM64 STM64

2 43 5

1. Service Type = SDH-VC4Src: Node 1/slot-2/port-1/aug1-1Dest: Node 1/slot-11/port-1/aug1-1Bandwidth = VC-4-16cTransparency = ON






Node 2

Transparent ServiceTributarydata

Tributarydata


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsCards Required to Create a Transparent Service

Cards Required to Create a Transparent Service

This table lists the Traverse cards required to create transparent services:

Before You Create a Transparent Service

Review the information in this topic before you create a transparent service.

Table 5-14 Cards Required to Create the Services


SONET-STS OC-12 OC-48 (1-port)

OC-12 OC-192

OC-48 (1- or 2-port) OC-192

SDH-VC4 STM-4 STM-16 (1-port)

STM-4 STM-64

STM-16 (1- or 2-port) STM-64

Table 5-15 Transparent Service Requirements


Read the information in Section 4—Creating ADM Services, Chapter 1—“Service Provisioning Concepts,” page 4-1.

Ensure the procedure requirements are met, Before You Start Provisioning Your Network, page 1-9.

Hardware

See Cards Required to Create a Transpar-ent Service, page 5-52



Software


Timing is configured. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Tim-ing,” page 1-15




TransNav Management System GUI Guide• Section 6—Services, Chapter 3—“SDH Services,”

page 6-31• Section 2—Services, Chapter 2—“SONET


Provisioning model• Hop-by-hop only


Guidelines See the procedure, Guidelines to Provision Transpar-ent Services, page 5-53, in this chapter


Chapter 6 Creating Transparent ServicesGuidelines to Provision Transparent Services

Guidelines to Provision Transparent Services

The guidelines to provision a transparent service are:• For protected configurations, there must be two tributary and two trunk cards on

each node transporting the transparent service.• You can use the following combinations of interfaces in a transparent service:

– STM-4 tributary and 1-port STM-16 trunks– STM-4 tributary and STM-64 trunks– 1-port STM-16 tributary and STM-64 trunks– 2-port STM-16 tributary and STM-64 trunks– OC-12 tributary and 1-port OC-48 trunks– OC-12 tributary and OC-192 trunks– 1-port OC-48 tributary and OC-192 trunks– 2-port OC-48 tributary and OC-192 trunks

• The Traverse system supports transparent services over an OC-192/STM-64 or 1-port OC-48/STM-16 linear chain.

• There can be no other services provisioned on the tributary port.• The remaining bandwidth on the trunk cards can be used for additional unprotected

or 1+1 path protected services.• The tributary connections and fiber span between the Traverse nodes are

unprotected. The subtending third-party equipment provides all protection switching and bandwidth management.

For 2-port OC-48 cards, the following guidelines also apply:• All services from one 2-port OC-48 card must use a contiguous set of 48 STS paths

on the OC-192 card. On the 2-slot OC-192 card, STS-1 to STS-96 are available in the lower-numbered slot. STS-97 to STS-192 are available in the higher-numbered slot.

• The slot-to-slot switching architecture is non-blocking for all SONET cards except the 2-port OC-48 card. Do not exceed the slot-to-slot bandwidth capacity of 48 STSs when establishing services between the cards.

• Force10 does not support the use of 2-port OC-48 cards for carrying OC-12 transparency services.

For information on creating services using 2-port OC-48 or STM-16 cards, see Section 4—Creating ADM Services, Chapter 5—“Creating 2-Port OC-48/STM-16 Services,” page 4-71.


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsProcedures Required to Create a Transparent Service

Procedures Required to Create a Transparent Service

Use the following procedures to help you provision transparent services on a Traverse system.1. Disable Control Data Parameter on Nodes Linked to Third-Party Equipment,

page 5-542. Provision the Transparent Service, page 5-553. Activate or Deactivate a Service, page 4-16

These procedures reference required parameters only. Use the following procedures to reference all configurable parameters for each service type:1. Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services,”

Create a SONET Service.2. Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,” Create

an SDH Service.

Disable Control Data Parameter on Nodes Linked to Third-Party Equipment

Use the following procedure to disable the Control Data parameter on the nodes connected to third-party equipment.

Table 5-16 Disable the Control Data Parameter on Nodes Connected to Third-Party Equipment

Step Procedure

1 Double-click the first node to display Shelf View.

2 Click the port that is connected to third-party equipment, then click the Config tab to display the Port Configuration dialog box.

3 From the Control Data parameter, select Disabled.


5 Repeat Steps 1 through 4 at the second node connected to the third-party equipment.

6 The Disable the Control Data Parameter on Nodes Connected to Third-Party Equipment procedure is complete.

Continue to the next procedure, Provision the Transparent Service.


Chapter 6 Creating Transparent ServicesProvision the Transparent Service

Provision the Transparent Service

Use this procedure to provision a transparent service.

Table 5-17 Provision the Transparent Service

Step Procedure

1 Complete the procedure, Disable the Control Data Parameter on Nodes Connected to Third-Party Equipment, page 5-54.

2 Use the procedure: Create a SONET Service, page 4-35 to create a SONET service with the following characteristics:

From the Bandwidth parameter:• Select STS-12c if this is an OC-12 interface• Select STS-48c if this is an OC-48 interface

Note: Be careful not to exceed the slot-to-slot bandwidth capacity of 48 STSs for 2-port OC-48 cards when establishing services between the cards.

Choose the Endpoints for the service: • For the Source Endpoint, choose the port that is connected to the

third-party equipment.• For the Destination Endpoint, choose the correct trunk card on the

same node.

3 On the Create Service tab, click Advanced to configure the advanced parameters.

Note: To activate the Advanced button, you must enter a name on the Create Service tab.

4 Configure the transparency parameter for the service.


a. Select Transparency to turn on the transparency flag.b. Click Done to return to the Create Service tab on the main screen.

5 On the Create Service tab, click Apply to provision this service and return to the service list on the Service tab.


Traverse Provisioning Guide, Section 5: Creating Service ApplicationsProvision the Transparent Service

6 Repeat Steps 1 through 5 for each service in the application.

7 The Provision the Transparent Service procedure is complete.

Continue to the procedure Activate or Deactivate a Service, page 4-16 to activate the service.

Table 5-17 Provision the Transparent Service (continued)

Step Procedure


SECTION 6 CREATING DCS APPLICATIONSSECTION 6CREATING DCS APPLICATIONS

SECTION 6CREATING DCS APPLICATIONS

Contents

Chapter 1DCS Application Overview

Multi-Shelf DCS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2DCS-384 Matrix Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3DCS-IO Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Single-Shelf DCS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5DCS-96 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6DCS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7MSAID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7MSAID Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7MSAID Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7MSAID Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8DCS Service Search, Filter, Scroll, and Sort Functions . . . . . . . . . . . . . . . . . 6-9

Search and Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Page Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Chapter 2Creating a Multi-Shelf Application

Multi-Shelf DCS Network Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Shelf Views of a Multi-Shelf DCS Application . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Guidelines to Create a Multi-Shelf DCS Application . . . . . . . . . . . . . . . . . . . . 6-14Procedure to Create a Multi-Shelf DCS Application . . . . . . . . . . . . . . . . . . . . 6-16Allocate MSAID Ranges on DCS-IO Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17Assign MSAID Number to STS- Equivalents on DCS-IO Shelf. . . . . . . . . . . . 6-19Activate MSAID Assignments on DCS-IO Shelf . . . . . . . . . . . . . . . . . . . . . . . 6-23Create DCS Services on the DCS-384 Matrix Shelf . . . . . . . . . . . . . . . . . . . . 6-24Activate DCS-384 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28

Chapter 3Creating a Single-Shelf DCS Application

Single-Shelf DCS Network Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30Shelf View of a Single-Shelf DCS-96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31Guidelines to Create a DCS-96 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31


Traverse Provisioning Guide, Section 6 Creating DCS Applications

Procedure to Create a Single-Shelf DCS Application . . . . . . . . . . . . . . . . . . . 6-32Assign MSAID Numbers to STS- Equivalents on DCS-96 Shelf . . . . . . . . . . . 6-33Create DCS Services on the DCS-96 Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36Activate DCS-96 DCS Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42

Chapter 4Upgrade a Single-Shelf DCS to a Multi-Shelf DCS

Procedure to Upgrade a Single-Shelf DCS to a Multi-Shelf DCS . . . . . . . . . . 6-44Install, Commission, and Create DCS Services on the DCS-384 Shelf . . . . . 6-45Upgrade the Hardware in the DCS-96 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46Change the DCS-96 Shelf to a DCS-IO Shelf . . . . . . . . . . . . . . . . . . . . . . . . . 6-47



Chapter 1DCS Application Overview

Introduction This chapter introduces the following Traverse DCS application terminology: • Multi-Shelf DCS Application, page 6-2• DCS-384 Matrix Shelf, page 6-3• DCS-IO Shelf, page 6-4• Single-Shelf DCS Application, page 6-5• DCS-96 Shelf, page 6-6• DCS Services, page 6-7• MSAID, page 6-7• MSAID Allocation, page 6-7• MSAID Assignments, page 6-7• MSAID Formats, page 6-8• DCS Service Search, Filter, Scroll, and Sort Functions, page 6-9


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsMulti-Shelf DCS Application

Multi-Shelf DCS Application

A multi-shelf Traverse DCS application consists of a DCS-384 matrix shelf and one or more DCS-IO shelves. In this example, Node1 is the management gateway node and is also a DCS-384 matrix shelf in a multi-shelf DCS application. The server communicates to the other nodes in-band using the DCC.

Figure 6-1 Multi-Shelf DCS Application

Node2 and Node3 are DCS-IO shelves. Node2 is connected to other Traverse ADM nodes in a UPSR ring. Node3 is a fully-equipped optical transmux shelf transmultiplexing DS3-mapped STS to the matrix shelf to be switched at the VT level.

See Section 6—Creating DCS Applications, Chapter 2—“Creating a Multi-Shelf Application,” page 6-11 for detailed procedures to create a multi-shelf DCS application.

See DCS-384 Matrix Shelf, page 6-3 for a description of the DCS-384 matrix shelf.

See DCS-IO Shelf, page 6-4 for a description of the DCS-IO shelf.

Node1DCS-384Matrix Shelf

OC481+1 APS

UPSR

DCSApplication

OC481+1 APS

Another vendor's network. Connectedelectrically or optically to the

DCS-IO shelf.

Node2DCS-IOShelf

Node3DCS-IOShelf

EMSServer

Node4ADM node

Node5ADM node


Chapter 1 DCS Application OverviewDCS-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 6-2 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

See the TransNav Management System GUI Guide, Section 7—DCS Applications, Chapter 1—“DCS-384 Matrix Shelf,” page 7-1 for detailed descriptions of the commissioned hardware configuration, the MSAID assignments, and the MSAID allocations on the DCS-384 matrix shelf.

See this document, Section 6—Creating DCS Applications, Chapter 2—“Creating a Multi-Shelf Application,” page 6-11 for detailed procedures on creating a multi-shelf DCS application.

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


Traverse Provisioning Guide, Section 6: Creating 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 6-3 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.

See TransNav Management System GUI Guide, Section 7—DCS Applications, Chapter 2—“DCS-IO Shelf,” page 7-17 for a detailed description of the DCS-IO shelf.

See this document, Section 6—Creating DCS Applications, Chapter 2—“Creating a Multi-Shelf Application,” page 6-11 for detailed procedures on creating a multi-shelf DCS application.

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 1 DCS Application OverviewSingle-Shelf DCS Application

Single-Shelf DCS Application

A single-shelf application requires only one Traverse node commissioned as a DCS-96 shelf. Use this single-shelf DCS application as the first step to building a multi-shelf DCS application. A single-shelf DCS can be easily upgraded to a multi-shelf application.

Figure 6-4 Single-Shelf DCS Application

In this network application example, Node1 is not only the management gateway node, but also a DCS-96 shelf. It is switching VT1.5 services aggregated from the subtending nodes. Node2 and Node3 are regular ADM nodes.

See Section 6—Creating DCS Applications, Chapter 3—“Creating a Single-Shelf DCS Application,” page 6-29 for detailed procedures on creating a single-shelf DCS application.

TA100-1

EMSServer

UPSR

Node1DCS-96 Shelf

Node3ADM node

Node2ADM node


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsDCS-96 Shelf

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 6-5 Single-Shelf DCS-96 Application

This example of a 96 STS-equivalent VT matrix shelf has the following configuration:• 1:1 protected GCM and VT/TU 5G Switch cards• 1:2 protected DS1 and DS3/EC-1 ports• 1+1 APS OC-3 and OCS-12 ports

Two slots (slots 17 and 18) are reserved for expansion to a multi-shelf DCS application.

See TransNav Management System GUI Guide, Section 7—, Chapter 3—“DCS-96 Shelf,” page 7-25 for a detailed description of a DCS-96 shelf.

See this document, Section 6—Creating DCS Applications, Chapter 3—“Creating a Single-Shelf DCS Application,” page 6-29 for detailed procedures on creating a single-shelf DCS 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


Chapter 1 DCS Application OverviewMSAID Assignments

DCS Services DCS services are the cross-connects that switch the VT1.5 signals on the DCS switching shelves: DCS-384 and DCS-96.

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.

See TransNav Management System GUI Guide, Section 7—DCS Applications, Chapter 1—“DCS-384 Matrix Shelf,” page 7-1 for detailed descriptions of the MSAID assignments and the MSAID allocations on the DCS-384 matrix shelf.

MSAID Allocation

On the DCS-IO shelf, a user must allocate an MSAID range to the OC-48 interfaces connected to the DCS-384 shelf. Because MSAIDs are automatically provisioned on the DCS-384 shelf, the MSAIDs on the links of the DCS-IO shelf must match the allocation of the corresponding links on the DCS-384 shelf.

During an upgrade from a DCS-96 shelf to a DCS-IO shelf, MSAID numbers are automatically allocated to slots 17 and 18.

See this document, Section 6—Creating DCS Applications, Chapter 2—“Creating a Multi-Shelf Application,” Allocate MSAID Ranges on DCS-IO Shelf, page 6-17 for a detailed procedure.

MSAID Assignments

On the DCS-IO shelf, a user must assign an STS-equivalent to an allocated MSAID.

See this document, Section 6—Creating DCS Applications, Chapter 2—“Creating a Multi-Shelf Application,” Assign MSAID Number to STS- Equivalents on DCS-IO Shelf, page 6-19 for a detailed procedure.


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsMSAID Formats

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 6-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



























Chapter 1 DCS Application OverviewDCS Service Search, Filter, Scroll, and Sort Functions

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 6-6 Service Filter Search

Page Scrolling. The TransNav system provides 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 3—“TransNav User Preferences,” Customize System Options, page 2-17).

Figure 6-7 Scrolling Services Page Screen Buttons



Table 6-1 MSAID Formats

DS1 Channel

MSAID-VT-Seq MSAID-VT-GR253 MSAID-VTG-VT

Payload Mapping

Payload Mapping

User Interface

User Interface User Interface


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsDCS Service Search, Filter, Scroll, and Sort Functions

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 6-8 Column Sort Icon



Chapter 2Creating a Multi-Shelf Application

Introduction This chapter includes the following topics:• Multi-Shelf DCS Network Example, page 6-12• Shelf Views of a Multi-Shelf DCS Application, page 6-13• Guidelines to Create a Multi-Shelf DCS Application, page 6-14• Procedure to Create a Multi-Shelf DCS Application, page 6-16• Allocate MSAID Ranges on DCS-IO Shelf, page 6-17• Assign MSAID Number to STS- Equivalents on DCS-IO Shelf, page 6-19• Activate MSAID Assignments on DCS-IO Shelf, page 6-23• Create DCS Services on the DCS-384 Matrix Shelf, page 6-24• Activate DCS-384 Services, page 6-28


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsMulti-Shelf DCS Network Example

Multi-Shelf DCS Network Example

In this example, the management server (EMS server) is connected to a router. In turn, the router is connected to the management gateway node (Node1). Node1 is also a DCS-384 matrix shelf in a multi-shelf DCS application. The server communicates to the other nodes in-band using the DCC.

For information on planning IP addresses for a Traverse network, see Traverse Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” page 2-11.

Figure 6-9 Multi-Shelf DCS Application Managed In-band With Router

In this example, Node2 and Node3 are DCS-IO shelves. Node2 is connected to other Traverse ADM nodes in a UPSR ring. Node3 is a fully-equipped optical transmux shelf transmultiplexing DS3-mapped STS to the matrix shelf to be switched at the VT level.

All nodes are commissioned as a specific type of network element: DCS-384, DCS-IO, or regular ADM. Each DCS shelf also has an additional commissioning parameter for MSAID formats. All MSAID formats in the DCS application must match.

Add routes for each node-ip to router.<node-ip> <mask> <Node1 bp-dcn-ip>10.100.100.1 255.255.255.0 172.168.0.210.100.100.2 255.255.255.0 172.168.0.210.100.100.3 255.255.255.0 172.168.0.210.100.100.4 255.255.255.0 172.168.0.210.100.100.5 255.255.255.0 172.168.0.2

EMS ServerIPGatewayMask

172.169.0.10172.169.0.1

255.255.255.0

Port IP A172.169.0.1

Port IP B172.168.0.1

Add routes for each node-ip to EMS server.<node-ip> <mask> <Router Port IP A>10.100.100.1 255.255.255.0 172.169.0.110.100.100.2 255.255.255.0 172.169.0.110.100.100.3 255.255.255.0 172.169.0.110.100.100.4 255.255.255.0 172.169.0.110.100.100.5 255.255.255.0 172.169.0.1

OC481+1 APS

UPSR

DCSApplication

node-idnode-ip10.100.100.2

dcs-iomsaid-vt-seq

Node2

oper-modemsaid-format

node-ip

ems-ipems-gw-ipems-mask

node-id10.100.100.1

172.169.0.10172.168.0.1

255.255.255.0

Node1

bp-dcn-ipbp-dcn-gw-ipbp-dcn-mask

172.168.0.2172.168.0.1

255.255.255.0

dcs-384

msaid-vt-seq

oper-mode

msaid-format

OC481+1 APS

10.100.100.3dcs-io

msaid-vt-seq

Node3 node-idnode-ipoper-modemsaid-format

Another vendor's network. Connectedelectrically or optically to the

DCS-IO shelf.

10.100.100.4adm

Node4 node-idnode-ipoper-mode

10.100.100.5adm

Node5 node-idnode-ipoper-mode

TN 00170


Chapter 2 Creating a Multi-Shelf ApplicationShelf Views of a Multi-Shelf DCS Application

Shelf Views of a Multi-Shelf DCS Application

In a commissioned DCS-384 matrix shelf, 20 cards are preprovisioned in the shelf in the following order:• Slots 1 to 10 are preprovisioned with VT/TU Switch cards, with slot 10 protecting

the cards in slots 1 through 9. The physical provisioning of the VT/TU Switch cards must be made left to right, beginning with slot 1.

• Slots 11 to 18 are preprovisioned with 2-port OC-48 cards.• The GCM slots are empty in a preprovisioned shelf, but will show the correct card

if the hardware is present.

Figure 6-10 Shelf Views of a Multi-Shelf DCS Application

This example shows two DCS-IO shelves. Node2 is a DCS-IO shelf that was upgraded from a DCS-96 shelf. Slots 15 and 16 contained two VT/TU 5G Switch cards that were redeployed to the DCS-384 matrix shelf after the upgrade.

Node3 is a transmux node that is optically transmultiplexing 96 DS3-mapped STSs then switching VT-mapped STSs to the DCS-384 matrix shelf. The OC-48 interfaces in slot 18 are protected by the OC-48 interfaces on the GCM cards.

Important: If the physical configuration of your DCS-384 has empty VT/TU Switch card slots, then provision a protection group Lockout on these pre-provisioned and unpopulated cards from the VT Protection Equipment tab.

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

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)

12P

DS3TMX

P

12P

DS3TMX

W

12P

DS3TMX

W

12P

DS3TMX

W

12P

DS3TMX

W

1P

OC48

1P

OC48

1P

OC48

1P

OC48

12P

DS3TMX

W

12P

DS3TMX

W

12P

DS3TMX

W

12P

DS3TMX

W

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

GCM+OC48

GCM+OC48

2P

OC48

2P

OC48

2P

OC48

Node3 (DCS-IO)

OC-12 UPSR OC-48 UPSRs


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsGuidelines to Create a Multi-Shelf DCS Application

Guidelines to Create a Multi-Shelf DCS Application

The guidelines to create a multi-shelf DCS application are: • A multi-shelf DCS application requires at least two Traverse nodes: a DCS-384

matrix shelf and a DCS-IO shelf.• A commissioned DCS-384 matrix shelf has all eighteen cards preprovisioned.

However, the minimum hardware configuration for a DCS-384 matrix shelf is:– Three VT/TU 5G Switch cards: two working (slot 1 and slot 2) and one protect

(slot 10)

Note: Remember: the physical provisioning of the VT/TU Switch cards must be made left to right, beginning with slot 1.

– Two 2-port OC-48 cards inserted in slots 11 and 12 (in a 1+1 APS protection group)

– Two GCM cards• Expanding the minimum hardware configuration, the DCS-384 matrix shelf

requires one VT/TU 5G Switch card for each working OC-48 interface.• Specify the MSAID format during node commissioning. MSAID-VTG-VT is the

default 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 OC-48 interfaces on the DCS-IO shelf must be in a 1+1 APS protection group.Protection groups are preprovisioned on the DCS-384 matrix shelf. Connect the working links on the DCS-IO shelf the working links on to the working links on the DCS-384 matrix shelf. Connect the protecting links on the DCS-IO shelf to the protecting links on the DCS-384 matrix shelf.

• In a DCS-384 node, the protection groups are pre-provisioned for the 2-port OC-48 cards using the scheme that for each pair of cards, the working port is port 1 and the protecting port is port 2 of the adjacent card.

Important: If the physical configuration of your DCS-384 has empty VT/TU Switch card slots, then provision a protection group Lockout on these pre-provisioned and unpopulated cards from the VT Protection Equipment tab.

Table 6-2 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







Chapter 2 Creating a Multi-Shelf ApplicationGuidelines to Create a Multi-Shelf DCS Application



Table 6-2 1+1 APS Protection Groups on a DCS-384 Node

Protection Group Working Port Protecting Port


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsProcedure to Create a Multi-Shelf DCS Application

Procedure to Create a Multi-Shelf DCS Application

Use this procedure as a guideline to create a multi-shelf DCS application.

Table 6-3 Create a Multi-Shelf DCS Application

Step Procedure

1 Install and commission a DCS-384 matrix shelf. See Traverse Installation and Commissioning Guide for detailed procedures.

2 Install and commission a DCS-IO shelf. See Traverse Installation and Commissioning Guide for detailed procedures.

3 Create bi-directional 1+1 APS protection groups on the DCS-IO shelf to match the far end protection groups on the DCS-384 matrix shelf. See this document, Section 3—Creating Protection Groups, Chapter 6—“Creating a 1+1 APS/MSP Protection Group,” page 3-35.

4 Complete the procedure: Allocate MSAID Ranges on DCS-IO Shelf, page 6-17.

5 Complete the procedure: Assign MSAID Numbers on DCS-IO Shelf, page 6-19.

6 Complete the procedure: Activate MSAID Assignments on DCS-IO Shelf, page 6-23.

7 Complete the procedure: Create DCS Services on the DCS-384 Matrix Shelf, page 6-24.

8 Complete the procedure: Activate DCS Services on a DCS-384 Matrix Shelf, page 6-28.

9 The procedure Create a Multi-Shelf DCS Application is complete.


Chapter 2 Creating a Multi-Shelf ApplicationAllocate MSAID Ranges on DCS-IO Shelf

Allocate MSAID Ranges on DCS-IO Shelf

Use this procedure to allocate ranges of MSAID numbers to the transport links on the DCS-IO shelf.

Table 6-4 Allocate MSAID Ranges on DCS-IO Shelf

Step Procedure

1 Complete Step 1, Step 2, and Step 3 in the Create a Multi-Shelf DCS Application, page 6-16.

2 In Shelf View of the DCS-IO shelf, click the DCS tab.

Figure 6-11 Allocate MSAIDs on the DCS-IO Shelf

3 Click the Allocation subtab.

2

3 4

5

6


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsAllocate MSAID Ranges on DCS-IO Shelf

4 Click a row in the Port column to display the Choose a Port dialog box.

Figure 6-12 Choose A Port Dialog Box

a. Select the working port in the protection group. b. Click Done to close the box and return to the DCS tab on the main

screen.

5 On the DCS tab in the main screen, in the MSAID Range column, click a row to select an MSAID range.

Important: This range must match the MSAID range allocated to the far end of the link on the DCS-384 matrix shelf.

Figure 6-13 Allocate MSAID Range to Working Link


7 The Allocate MSAID Ranges on DCS-IO Shelf procedure is complete.

Continue to the next procedure: Assign MSAID Numbers on DCS-IO Shelf, page 6-19.

Table 6-4 Allocate MSAID Ranges on DCS-IO Shelf (continued)

Step Procedure

4a

4b


Chapter 2 Creating a Multi-Shelf ApplicationAssign MSAID Number to STS- Equivalents on DCS-IO Shelf

Assign MSAID Number to STS- Equivalents on DCS-IO Shelf

Use this procedure to assign MSAID numbers to STS-1 equivalents on the DCS-IO shelf.

Table 6-5 Assign MSAID Numbers on DCS-IO Shelf

Step Procedure

1 Complete the procedure: Allocate MSAID Ranges on DCS-IO Shelf, page 6-17.


Figure 6-14 Assign MSAID Numbers on the DCS-IO Shelf

3 Click the Assignment subtab.

2

3

4


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsAssign MSAID Number to STS- Equivalents on DCS-IO Shelf

4 Click Add to display the Assignment Details dialog box.

Figure 6-15 Assignment Details Dialog Box.

5 In the Assignment Details dialog box, click the Endpoint field to display the Choose an Endpoint dialog box.

Figure 6-16 Choose an Endpoint

a. In the navigation tree, click the correct port.b. Click Done to return to the Assignment Details dialog box.

Table 6-5 Assign MSAID Numbers on DCS-IO Shelf (continued)

Step Procedure

567

910

8

5

5a

5b


Chapter 2 Creating a Multi-Shelf ApplicationAssign MSAID Number to STS- Equivalents on DCS-IO Shelf

6 In the Assignment Details dialog box, select an MSAID from the drop-down menu.

Figure 6-17 MSAID Number Assignments

7 In the Description field, enter alphanumeric characters to describe this assignment in the DCS application.

8 If this service is an optical transmux service, configure the transmux parameters.

Figure 6-18 Configure Transmux Parameters

a. Select the Transmuxed check box. The Choose a TMX Port dialog box displays.

b. Navigate the tree and select the resource STSTMX port.c. Click Done to return to the Assignment Details dialog box.

9 In the Protection field, Unprotected is the default for this service.


Step Procedure

8a

8b

8c


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsAssign MSAID Number to STS- Equivalents on DCS-IO Shelf

10 Click Apply to save the changes and return to the DCS tab on the main screen.

Figure 6-19 MSAID Assignment List

11 The Assign MSAID Numbers on DCS-IO Shelf procedure is complete.

Continue to the next procedure: Activate MSAID Assignments on DCS-IO Shelf, page 6-23.


Step Procedure


Chapter 2 Creating a Multi-Shelf ApplicationActivate MSAID Assignments on DCS-IO Shelf

Activate MSAID Assignments on DCS-IO Shelf

Use this procedure to activate MSAID assignments on the DCS-IO shelf.

Table 6-6 Activate MSAID Assignments on DCS-IO Shelf

Step Procedure

1 Complete the procedure: Assign MSAID Numbers on DCS-IO Shelf, page 6-19.


Figure 6-20 DCS Tab, Assignment Subtab, Assignment List


4 Press the Shift key and select all the assignments in the Assignment List

5 Click the (De)Activate command button to activate all the selected services.

6 The Activate MSAID Assignments on DCS-IO Shelf procedure is complete.

Continue to the next procedure: Create DCS Services on the DCS-384 Matrix Shelf, page 6-24.

2

34

5


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsCreate DCS Services on the DCS-384 Matrix Shelf

Create DCS Services on the DCS-384 Matrix Shelf

Use this procedure to create DCS services on the DCS-384 matrix shelf.

Table 6-7 Create DCS Services on the DCS-384 Matrix Shelf

Step Procedure

1 Complete the procedure: Activate MSAID Assignments on DCS-IO Shelf, page 6-23.

2 In Shelf View of the DCS-384 matrix shelf, click the DCS tab.

Figure 6-21 DCS-384 DCS Tab, Services Subtab

3 Click the Services subtab.

4 Click Add to display the Create DCS Services tab.

Figure 6-22 Create DCS Services Tab

2

3

4

56

7

9 10

8


Chapter 2 Creating a Multi-Shelf ApplicationCreate DCS Services on the DCS-384 Matrix Shelf


6 In the Bandwidth parameter, select the bandwidth for the service:• VT1.5 (default)• STS-1

7 Click a row in the Endpoint column to display the Choose an Endpoint dialog box.

Figure 6-23 Choose an MSAID Endpoint on DCS-384 matrix shelf

a. Navigate the tree and select the correct endpoint. If this is an STS-1 service, the list will display only MSAID numbers. If this is a VT1.5 service, the list will display MSAID numbers, VT groups, and individual VTs.

b. Click Done to close the dialog box and return to the Create DCS Services tab on the main screen.

8 In the Protection parameter, select Unprotected.

Table 6-7 Create DCS Services on the DCS-384 Matrix Shelf (continued)

Step Procedure

7

7a

7b


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsCreate DCS Services on the DCS-384 Matrix Shelf

9 On the Create DCS Services tab, click Advanced to configure more parameters of the service.


a. For specific definitions of these parameters, see the TransNav Management System GUI Guide, Section 2—Services, Chapter 2—“SONET Services,” Configure Protection Parameters, page 2-25.

b. Click Done to return to the Create DCS Services tab on the main screen.


Step Procedure


Chapter 2 Creating a Multi-Shelf ApplicationCreate DCS Services on the DCS-384 Matrix Shelf

10 Click Apply to save this configuration and return to the DCS services list.

Figure 6-25 DCS-384 Service List

11 The Create DCS Services on the DCS-384 Matrix Shelf procedure is complete.

Continue the next procedure: Activate DCS Services on a DCS-384 Matrix Shelf, page 6-28.


Step Procedure


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsActivate DCS-384 Services

Activate DCS-384 Services

Use this procedure to activate DCS services on the DCS-384 matrix shelf.

Table 6-8 Activate DCS Services on a DCS-384 Matrix Shelf

Step Procedure

1 Complete the procedure: Create DCS Services on the DCS-384 Matrix Shelf, page 6-24.

2 In Shelf View of the DCS-384 matrix shelf, click the DCS tab.


3 Press the Shift key and select all the provisioned DCS services.

4 Right-click on the service list and select Activate from the menu.

5 The Activate DCS Services on a DCS-384 Matrix Shelf procedure is complete.

2

3

4



Chapter 3Creating a Single-Shelf DCS Application

Introduction This chapter includes the following topics:• Single-Shelf DCS Network Example, page 6-30• Shelf View of a Single-Shelf DCS-96, page 6-31• Guidelines to Create a DCS-96 Application, page 6-31• Procedure to Create a Single-Shelf DCS Application, page 6-32• Assign MSAID Numbers to STS- Equivalents on DCS-96 Shelf, page 6-33• Create DCS Services on the DCS-96 Shelf, page 6-36• Activate DCS-96 DCS Services, page 6-42


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsSingle-Shelf DCS Network Example

Single-Shelf DCS Network Example

In this example, the management server (EMS server) is connected directly to the management gateway node (Node1). The server communicates to the other nodes in-band using the DCC.

For information on planning IP addresses for a Traverse network, see the Traverse Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” page 2-11.

Figure 6-27 Single-Shelf DCS Application Managed Inband

In this network application example, Node1 is not only the management gateway node, but also a DCS-96 shelf. It has an additional node commissioning parameter to configure MSAID formats. It is switching VT1.5 services aggregated from the subtending nodes. Node2 and Node3 are regular ADM nodes.

node-ipbp-dcn-ipbp-dcn-gw-ipbp-dcn-mask

node-id

node-id

bp-dcn-ipbp-dcn-gw-ipbp-dcn-mask

node-ip

IP

MaskTrap-1

NameTA100-1

Gateway

Optional

10.100.100.2172.168.1.1172.168.1.2

Node2

10.100.100.1172.168.0.2172.168.0.1

255.255.255.0

Node1

172.168.1.2172.168.1.1

255.255.255.010.100.100.2

TA100-1

node-idnode-ip 10.100.100.3

Node3

Add routes to EMS server for each node-ip.<node-ip> <mask> <bp-dcn-ip of Node1>10.100.100.1 255.255.255.0 172.168.0.210.100.100.2 255.255.255.0 172.168.0.210.100.100.3 255.255.255.0 172.168.0.2

EMSServer

oper-modemsaid-format

admoper-mode

adm oper-mode

dcs-96msaid-vt-seq

255.255.255.0

IPGatewayMask

172.169.0.10

255.255.255.0172.168.0.2


Chapter 3 Creating a Single-Shelf DCS ApplicationGuidelines to Create a DCS-96 Application

Shelf View of a Single-Shelf DCS-96

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 6-28 Single-Shelf DCS-96 Application

This example of a 96 STS-equivalent VT matrix shelf has the following configuration:• 1:1 protected GCM and VT/TU 5G Switch cards• 1:2 protected DS1 and DS3/EC-1 ports• 1+1 APS OC-3 and OCS-12 ports

Two slots (slots 17 and 18) are reserved for expansion to a multi-shelf DCS application.

Guidelines to Create a DCS-96 Application

The guidelines to create a single-shelf DCS application are: • A single-shelf application requires only one Traverse node commissioned as a

DCS-96 shelf. • A DCS-96 shelf has a protected 96 STS-1 capacity.• Only the VT/TU 5G Switch card can be used for VT1.5 switching in a DCS

application. • Reserve slot 17 and slot 18 for scaling to a multi-shelf DCS application.• 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 totalling the equivalent of 96 STSs.

– Two VT/TU 5G Switch cards.– Two GCM cards with or without the integrated OC-12/48 ports.

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

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


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsProcedure to Create a Single-Shelf DCS Application

Procedure to Create a Single-Shelf DCS Application

Use this procedure as a guideline to create a single-shelf application.

Table 6-9 Create a Single-Shelf DCS Application

Step Procedure

1 Install and commission a DCS-96 shelf. See the Traverse Installation and Commissioning Guide for detailed procedures.

2 Insert the cards according to the network plan.

3 Create the appropriate protection groups for the equipment on the node. See this document, Section 3—Creating Protection Groups, Chapter 6—“Creating a 1+1 APS/MSP Protection Group,” page 3-35.

4 Complete the procedure: Assign MSAID Numbers on DCS-96 Shelf, page 6-33.

5 Complete the procedure: Create DCS Services on the DCS-96 Shelf, page 6-36.

6 Complete the procedure: Activate DCS Services on a DCS-96 Shelf, page 6-42.


Chapter 3 Creating a Single-Shelf DCS ApplicationAssign MSAID Numbers to STS- Equivalents on DCS-96 Shelf

Assign MSAID Numbers to STS- Equivalents on DCS-96 Shelf

Use this procedure to assign MSAID numbers to STS-equivalents on the DCS-96 shelf.

Table 6-10 Assign MSAID Numbers on DCS-96 Shelf

Step Procedure

1 Complete Step 1, Step 2, and Step 3 in the Create a Single-Shelf DCS Application, page 6-32.

2 In Shelf View of the DCS-96 shelf, click the DCS tab.

Figure 6-29 Assign MSAID Numbers on the DCS-IO Shelf


4 Click Add to display the Assignment Details dialog box.

23

4


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsAssign MSAID Numbers to STS- Equivalents on DCS-96 Shelf

5 In the Assignment Details dialog box, click the Endpoint field to display the Choose an Endpoint dialog box.

Figure 6-30 Choose an Endpoint

a. In the navigation tree, click the correct port.b. Click Done to return to the Assignment Details dialog box.

6 In the Assignment Details dialog box, select an MSAID from the drop-down menu.

Figure 6-31 MSAID Number Assignments

7 In the Description field, enter alphanumeric characters to describe this assignment in the DCS application.

Table 6-10 Assign MSAID Numbers on DCS-96 Shelf (continued)

Step Procedure

5

5a

5b

6

7


Chapter 3 Creating a Single-Shelf DCS ApplicationAssign MSAID Numbers to STS- Equivalents on DCS-96 Shelf

8 Click Apply to save the changes and return to the DCS tab on the main screen.

Figure 6-32 MSAID Assignment List

9 The Assign MSAID Numbers on DCS-96 Shelf procedure is complete.

Continue to the next procedure: Create DCS Services on the DCS-96 Shelf, page 6-36.

Table 6-10 Assign MSAID Numbers on DCS-96 Shelf (continued)

Step Procedure


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsCreate DCS Services on the DCS-96 Shelf

Create DCS Services on the DCS-96 Shelf

Use this procedure to create DCS services on the DCS-96 shelf.

Table 6-11 Create DCS Services on the DCS-96 Shelf

Step Procedure

1 Complete the procedure: Create a Single-Shelf DCS Application, page 6-32.




4 Click Add to display the Create DCS Services tab.

2

3

4


Chapter 3 Creating a Single-Shelf DCS ApplicationCreate DCS Services on the DCS-96 Shelf


Figure 6-34 Create DCS Services Tab

6 Click a row in the Endpoint column to display the Choose an Endpoint dialog box.

Figure 6-35 Choose an Endpoint on the DCS-96 Shelf

a. In the navigation tree, select the correct endpoint. b. Click Done to close the dialog box and return to the Create DCS

Services tab on the main screen.

Table 6-11 Create DCS Services on the DCS-96 Shelf (continued)

Step Procedure

5

6

8 9

7

6

6a

6b

6a





In the Protection Type parameter, select one of the following options: • Unprotected (default): Used for services that are either unprotected,

1+1 APS/MSP protected, protected with an equipment protection group, or a 1+1 Path Protection group.


• Full: The system only create the service if there is full protection on every transport link in the network.


• UPSR Ingress: If the service is a SONET-VT service and is creating a bidirectional path across two interconnected UPSRs.

8 For services that have a protection type configured, configure the following parameters.• Revertive (default is not selected): Select the check box to switch



If this service is protected by a BLSR or an MS-SP ring, go to Step 9.



Step Procedure

510



9 If the endpoints of the service are on a BLSR or MS-SP ring, click the MS-SP/BLSR tab and configure the following parameters. • Ring Source Node ID: Select the BLSR Node ID where the traffic on



10 For services protected by another service. Click the 1+1 Path Protected tab and configure the HoldOffTimer parameter. This parameter applies only if there is also a 1+1 APS/MSP protection group. Allows line protection to switch first before the path switches. If the line switches within the specified time period, the path does not switch. The hold-off timer starts when path protection detects a path failure.





Step Procedure

9



12 On the Create DCS Services tab, click Advanced to configure more parameters of the service.



b. Click Done to return to the Create DCS Services tab on the main screen.


Step Procedure



13 Click Apply to save this configuration and return to the DCS services list.

Figure 6-39 DCS-96 Service List

14 The Create DCS Services on the DCS-96 Shelf procedure is complete.

Continue the next procedure: Activate DCS Services on a DCS-96 Shelf, page 6-42.


Step Procedure


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsActivate DCS-96 DCS Services

Activate DCS-96 DCS Services

Use this procedure to activate DCS services on the DCS-96 shelf.

Table 6-12 Activate DCS Services on a DCS-96 Shelf

Step Procedure

1 Complete the procedure: Create DCS Services on the DCS-96 Shelf, page 6-36.




4 Press the Shift key and select all the provisioned DCS services.

5 Right-click on the service list and select Activate from the menu.

6 The Activate DCS Services on a DCS-96 Shelf procedure is complete.

2

3 4

5



Chapter 4Upgrade a Single-Shelf DCS to a Multi-Shelf DCS

Introduction A Traverse single-shelf DCS application consists of a DCS-96 shelf. A Traverse multi-shelf application consists of one DCS-384 matrix shelf and one or more DCS-IO shelves.

To upgrade from a single-shelf DCS application to multi-shelf DCS application, you must add the DCS-384 matrix shelf and convert the DCS-96 shelf to a DCS-IO shelf.

This chapter includes the following topics:• Procedure to Upgrade a Single-Shelf DCS to a Multi-Shelf DCS, page 6-44• Install, Commission, and Create DCS Services on the DCS-384 Shelf,

page 6-45• Upgrade the Hardware in the DCS-96 Shelf, page 6-46• Change the DCS-96 Shelf to a DCS-IO Shelf, page 6-47


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsProcedure to Upgrade a Single-Shelf DCS to a Multi-Shelf DCS

Procedure to Upgrade a Single-Shelf DCS to a Multi-Shelf DCS

Use this procedure as a guideline to upgrade a single-shelf DCS to a multi-shelf DCS.

Table 6-13 Upgrade a Single-Shelf DCS to a Multi-Shelf DCS Application

Step Procedure

1 Complete the procedure: Install, Commission, and Create Services on the Matrix Shelf.

2 Complete the procedure: Upgrade the Hardware in the DCS-96 Shelf.

3 Create the bi-directional 1+1 APS protection groups on the DCS-IO shelf. See this document, Section 3—Creating Protection Groups, Chapter 6—“Creating a 1+1 APS/MSP Protection Group”.

The working ports are port 1 of each OC-48 card. The protecting port for port 1 is port 2 of the adjacent card.

Figure 6-41 New 1+1 APS Protection Groups on DCS-96 Shelf

4 Complete the procedure: Change the DCS-96 Shelf to a DCS-IO Shelf.

5 The Upgrade a Single-Shelf DCS to a Multi-Shelf DCS Application procedure is complete.


Chapter 4 Upgrade a Single-Shelf DCS to a Multi-Shelf DCSInstall, Commission, and Create DCS Services on the DCS-384 Shelf

Install, Commission, and Create DCS Services on the DCS-384 Shelf

Use this procedure as a guideline to install, commission, and create DCS services on a DCS-384 matrix shelf.

Table 6-14 Install, Commission, and Create Services on the Matrix Shelf

Step Procedure

1 Install and commission a DCS-384 matrix shelf. See the Traverse Installation and Commissioning Guide for detailed procedures.

2 Create the DCS services from the DCS-96 shelf to the DCS-384 matrix shelf.

For a script to copy all the DCS services, contact the Force10 Networks Technical Assistance Center (TAC).

3 Activate all the DCS services on the DCS-384 matrix shelf. See this document, Section 6—Creating DCS Applications, Chapter 2—“Creating a Multi-Shelf Application,” Activate DCS-384 Services.

4 The Install, Commission, and Create Services on the Matrix Shelf procedure is complete.

Continue to the procedure: Upgrade the Hardware in the DCS-96 Shelf.


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsUpgrade the Hardware in the DCS-96 Shelf

Upgrade the Hardware in the DCS-96 Shelf

Use this procedure to upgrade the hardware in a DCS-96 shelf.

Table 6-15 Upgrade the Hardware in the DCS-96 Shelf

Step Procedure

1 Complete the procedure: Install, Commission, and Create Services on the Matrix Shelf.

2 In the DCS-96 shelf, insert the 2-port OC-48 cards in the slots 17 and 18 (these slots should be reserved for this expansion). See the Traverse Installation and Commissioning Guide, Section 6—Precautions and Common Procedures, Chapter 3—“Inserting and Removing Cards.”

3 Connect the fibers between the DCS-IO shelf and the DCS-384 matrix shelf.

There are preprovisioned 1+1 APS protection groups configured on the DCS-384. Connect the working ports on the DCS-IO shelf to the working ports on the DCS-384 matrix shelf. Connect the protecting ports on the DCS-IO shelf to the protecting ports on the DCS-384 matrix shelf.

Force10 recommends to connect the fibers in the following order:• DCS-96/slot-17/port-1 to DCS-384/slot-11/port-1• DCS-96/slot-17/port-2 to DCS-384/slot-12/port-2• DCS-96/slot-18/port-1 to DCS-384/slot-12/port-1• DCS-96/slot-18/port-2 to DCS-384/slot-11/port-2

4 The Upgrade the Hardware in the DCS-96 Shelf procedure is complete.

Continue with Step 3 the procedure: Upgrade a Single-Shelf DCS to a Multi-Shelf DCS Application.


Chapter 4 Upgrade a Single-Shelf DCS to a Multi-Shelf DCSChange the DCS-96 Shelf to a DCS-IO Shelf

Change the DCS-96 Shelf to a DCS-IO Shelf

Use this procedure to change the DCS-96 shelf to a DCS-IO shelf.

Table 6-16 Change the DCS-96 Shelf to a DCS-IO Shelf

Step Procedure

1 Ensure the 1+1 APS protection groups are created on this node.

The working ports are port 1 of each OC-48 card. The protecting port for port 1 is port 2 of the adjacent card.

Figure 6-42 New 1+1 APS Protection Groups on DCS-96 Shelf

2 Open a telnet session to the management server. See the procedure in the TransNav Management System CLI Guide, Section 1—Overview and Quick Reference, Chapter 1—“CLI Overview,” Connect to the Domain-Level CLI, page 1-4.

3 At the domain prompt, enter

node NodeName

where:

NodeName is the name of the DCS-96 shelf.


Traverse Provisioning Guide, Section 6: Creating DCS ApplicationsChange the DCS-96 Shelf to a DCS-IO Shelf

4 Start the upgrade procedure. At the node prompt, enter

exec dcs upgrade start slot x slot y

where:

slot x is the first slot that was reserved for 2-port OC-48 transport card (typically slot 17).slot y is the second slot reserved for the second 2-port OC-48 transport card (typically slot 18).

5 Roll the MSAID assignments on the DCS-96 shelf to the new transport cards. At the node prompt, enter:

exec dcs msaid assignment roll

MSAIDs 1 to 48 are automatically allocated to the slot x (specified in Step 4), port 1.

MSAIDs 49 to 96 are automatically allocated to slot y (specified in Step 4), port 1.

6 Finish the DCS upgrade process. At the node prompt, enter:

exec dcs upgrade finish

7 Verify the node commissioning parameter oper-mode is changed from DCS-96 to DCS-IO. At the node prompt, enter:

show node commission

8 The Change the DCS-96 Shelf to a DCS-IO Shelf procedure is complete.

Table 6-16 Change the DCS-96 Shelf to a DCS-IO Shelf (continued)

Step Procedure


SECTION 7 CONFIGURING ETHERNET SECTION 7CONFIGURING ETHERNET

Contents

Chapter 1Configuring Ethernet Overview

Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Link Integrity Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Ethernet Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Ethernet Configuration Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Configuring CPE to Ethernet Information Flow . . . . . . . . . . . . . . . . . . . . . . . . 7-6Configuring CPE to Ethernet Services Procedure. . . . . . . . . . . . . . . . . . . . . . 7-7

Chapter 2Configuring Ethernet Equipment

Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9VLAN Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Port Tagged. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Customer Tagged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10VLAN Bundling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Service Provider Tagged. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Untagged Ethernet Frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12VLAN Tagging on Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13VLAN Tagging Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15Configure Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16Configure Ethernet Port Parameter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18Auto Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24Configure Auto Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25View VLAN Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30View the Negotiated Status of the Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32View or Edit the MAC Address Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33

Chapter 3Link Aggregation

Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37Guidelines to Configure Link Aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38

Carrier Ethernet Protection Pair (CEPP) . . . . . . . . . . . . . . . . . . . . . . . . . 7-38LAG Capacity Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39Create a Link Aggregation Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41

Chapter 4Ethernet Over SONET/SDH (EOS)

Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49


Traverse Provisioning Guide, Section 7 Configuring Ethernet

Ethernet over SONET/SDH (EOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50Virtual Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51Guidelines to Configure EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51

EOS Port Members (SONET or SDH Services) . . . . . . . . . . . . . . . . . . . 7-51Virtual Concatenation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54Configure EOS Port Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55Configure Service Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56Creating EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58

Chapter 5EOS Port Protection

Ethernet Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65Example of EOS Port Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66Guidelines to Configure EOS Port Protection . . . . . . . . . . . . . . . . . . . . . . . . . 7-67Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67Create a 1+1 EOS Port Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69

Chapter 6Ethernet Over PDH (EOP)

Ethernet over PDH (EOP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-71Virtual Concatenation of PDH Circuits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72Guidelines to Configure EOS and EOP Ports on EOPDH Cards . . . . . . . . . . 7-73

EOP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73EOP Port Members (SONET or SDH Services) . . . . . . . . . . . . . . . . . . . 7-73Virtual Concatenation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75Creating EOP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76Managing EOP Port Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82

Chapter 7EoPDH Services and Applications

Ethernet over PDH Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85EoPDH Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85Configuring CPE to Ethernet Information Flow . . . . . . . . . . . . . . . . . . . . . . . . 7-86Configuring CPE to EoPDH Services Procedure. . . . . . . . . . . . . . . . . . . . . . . 7-87Managing Traffic on EOP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88

Chapter 8Link Capacity Adjustment Scheme

Ethernet Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-89LCAS Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90

Failed or Deleted Members on EOS Ports. . . . . . . . . . . . . . . . . . . . . . . . 7-90Restored or Added Members on EOS ports . . . . . . . . . . . . . . . . . . . . . . 7-90Failed or Deleted Members on EOP Ports. . . . . . . . . . . . . . . . . . . . . . . . 7-91EOS Port Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-91Example 1: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-91



Example 2:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-91LCAS and Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-92Asymmetric LCAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-92LCAS Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-92Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-94Guidelines to Configure LCAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-96Guidelines to Removing LCAS EOS Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-96Configure LCAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97

Chapter 9Rapid Spanning Tree Protocol

Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-103What is RSTP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-104Supported RSTP Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-105RSTP Bridge Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106RSTP Port Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106Guidelines to Configure RSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-107

Spanning Tree BPDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-108Virtual RSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-109Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-110Configure RSTP on an EOS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-111View RSTP Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-113Configure Virtual RSTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-115

Chapter 10Ethernet Services

Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-119Ethernet Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-119Line Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-120Bridge Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-121

Adding and Removing Endpoints to a Bridge Service. . . . . . . . . . . . . . . 7-121Aggregation Bridge Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-122

Aggregation Bridge Service with an Active/Standby CPE. . . . . . . . . . . . 7-122Hub Forwarding via a Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-122

Multipoint ECC Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-123Ethernet Services and VLAN Tagging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-125Determining Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-126

Packets Arriving on Ports Tagged Port-Based . . . . . . . . . . . . . . . . . . . . 7-127Packets Arriving on Ports Tagged Customer-Tagged. . . . . . . . . . . . . . . 7-127Packets Arriving on Ports Tagged Service-Tagged. . . . . . . . . . . . . . . . . 7-127

All Ports in Service are Port-based . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-128Mix of Port-based and Service-tagged Ports in Service . . . . . . . . . . . . . . . . . 7-128All Ports in Service are Customer- tagged . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-129Mix of Customer- tagged and Service-tagged Ports in Service. . . . . . . . . . . . 7-132All Ports in Service Tagged as Service- tagged . . . . . . . . . . . . . . . . . . . . . . . 7-134VLAN Tagging Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-135Guidelines to Configure Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-135

Line Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-135



Bridge Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-136Aggregate Bridge Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-136Multiport ECC Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-136Setting Up EOS Ports on 10GbE or GbE-10 Cards. . . . . . . . . . . . . . . . . 7-137

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-138Search for Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-139Configure Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-142

Chapter 11Ethernet Traffic Management

Supported Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-149Ingress Traffic Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-150Egress Traffic Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-151Ethernet Traffic Management Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-152Managing Traffic on EOP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-154Maximum Information Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-154Pause Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-154

On Sending PAUSE frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-154On Receiving PAUSE Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-155

Queuing Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-155FIFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-156Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-156Weighted Fair Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-156Queuing Policy and Spanning Tree BPDUs . . . . . . . . . . . . . . . . . . . . . . . . . . 7-157

If Queuing Policy is either FIFO or PQ. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-157If Queuing Policy is WFQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-158

Marking Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-158Configure Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-159

Chapter 12Classifying and Prioritizing Packets

Class of Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-161Initial Drop Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-162Default Classifier Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-162Priority-based CoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-162Port-Based CoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-163Untagged Packets and Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-163Queuing Policy and Class of Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-164Classifier Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-164Create Classifier Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-165

Chapter 13Policing

Policing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-167Bandwidth Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-168Default Bandwidth Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-168Example Bandwidth Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-168Create a Bandwidth Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-170Policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-171



Policing Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-172Bandwidth Profiles and Policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-173Guidelines to Create a Policer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-173Create Policers on the Ethernet Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-174

Chapter 14RED Congestion Control

Random Early Discard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-177Traverse RED Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-178System Defaults for RED Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-179Customize RED Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-180View Current System RED Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-183

Release TR3.2.2 Force10 Networks Page v


Page vi Force10 Networks Release TR3.2.2

SECTION 7CONFIGURING ETHERNET

Chapter 1Configuring Ethernet Overview

Introduction This chapter contains the following topics:• Ethernet Cards, page 7-1• Link Integrity Feature, page 7-2• Ethernet Configuration Process, page 7-3• Ethernet Configuration Procedure, page 7-4

Ethernet Cards

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

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

10GBE Card 10GbE Not applicable

GBE-10 Card GbE-10 Not applicable

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


Traverse Provisioning Guide, Section 7: Configuring EthernetLink Integrity Feature

Link Integrity Feature

Link integrity is a feature in which the system provides a reliable point-to-point link between Ethernet ports on two different systems joined by a network transport connection. This is an attribute of a relationship between ports, not on a port itself. Link integrity communicates a failure anywhere in the end-to-end data path to both ports as follows:• If a local Ethernet port fails, the local system informs the remote system of the

failure.• When the local system learns of a remote Ethernet port failure, the local system

disables the transmitter of the local Ethernet port so the local Ethernet port’s link partner will consider the link to be down.

• If the transport connection between the Ethernet ports fails, each of the two end systems will disable the transmitter of its local Ethernet port.

Enable the link integrity feature on Ethernet line services using the Link Integrity parameter. Configure link integrity on two line services that use exactly one Ethernet port and one EOS port on the ingress and egress nodes of the network. Neither the Ethernet port nor the EOS port can be in any other activated service.

Link integrity is not supported on an EOP port on the EoPDH card.

See Chapter 10—“Ethernet Services,” page 7-119 for information on configuring this feature.


Chapter 1 Configuring Ethernet OverviewEthernet Configuration Process

Ethernet Configuration Process

Use this flow chart as a guideline to configure Ethernet in a Traverse system.

Figure 7-1 Ethernet Provisioning Flow Chart

Create Ethernet Services

Configure Ethernet TrafficManagement

End

TR-00001

Optionally, configure EOS features:RSTPLCAS

1+1 EOS port protection

Create and activateEOS members on EOS ports and

EOP members on EOP ports (Use service groups or SONET and

SDH services with endpoints onEthernet cards)

Create EOS portsCreate EOP ports (EoPDH cards only)

Optionally, configure EOP features:LCAS

1+1 EOP port protection

Start:The equipment is installed and

connected

Provision and activateSONET / SDH

path services with endpoints onEthernet cards

Optionally, configure optical andelectrical protection groups

and equipment(card and port parameters)

Optionally configure Ethernet features:Link Aggregation Groups

Auto-negotiation


Traverse Provisioning Guide, Section 7: Configuring EthernetEthernet Configuration Procedure

Ethernet Configuration Procedure

Use this procedure as a guideline to configure Ethernet services on a Traverse system.

Table 7-1 Traverse Ethernet Configuration Process and References


1 The equipment is installed and connected according to the net-work plan


Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 2—“Discover the Network,” page 1-9

2 Configure optical and Ethernet electrical protection groups according to the network plan

Traverse Provisioning Guide, Section 3—Creating Pro-tection Groups

3 Configure optical and Ethernet equipment (cards and ports)

Traverse Provisioning Guide • Section 2—Configuring Equipment• Section 7—Configuring Ethernet, Chapter

2—“Configuring Ethernet Equipment,” page 7-9

4 Optionally, configure Ethernet fea-tures

Traverse Provisioning Guide• Section 7—Configuring Ethernet, Chapter

2—“Configuring Ethernet Equipment,” Auto Negotiation, page 7-24

• Section 7—Configuring Ethernet, Chapter 3—“Link Aggregation,” page 7-37

5 Create and activate EOS port members

Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 4—“Ethernet Over SONET/SDH (EOS),” page 7-49

6 Create EOS ports Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 4—“Ethernet Over SONET/SDH (EOS),” page 7-49

7 Optionally, configure EOS fea-tures

Traverse Provisioning Guide• Section 7—Configuring Ethernet, Chapter 8—“Link

Capacity Adjustment Scheme,” page 7-89• Section 7—Configuring Ethernet, Chapter 9—“Rapid

Spanning Tree Protocol,” page 7-103• Section 7—Configuring Ethernet, Chapter 5—“EOS

Port Protection,” page 7-65

8 Configure Ethernet services Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 10—“Ethernet Services,” page 7-119

9 Optionally, create and activate EOP port members (EoPDH cards only)

Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 6—“Ethernet Over PDH (EOP),” page 7-71

10 Optionally, create EOP ports (EoPDH cards only)


11 Optionally, configure EOP fea-tures (EoPDH cards only)

Traverse Provisioning Guide• Section 7—Configuring Ethernet, Chapter 8—“Link

Capacity Adjustment Scheme,” page 7-89

12 Configure Ethernet traffic manage-ment

Section 7—Configuring Ethernet, Chapter 11—“Ether-net Traffic Management”


Chapter 1 Configuring Ethernet OverviewEthernet Configuration Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetConfiguring CPE to Ethernet Information Flow

Configuring CPE to Ethernet Information Flow

Use this flow chart as a guideline to configure the flow of information from a CPE device to Ethernet services in a Traverse system.

Figure 7-2 Ethernet Provisioning Flow Chart

Configure Ethernet traffic managementfor EOP ports

End

TR-00055

Create EOP portsand activate EOP members

(EoPDH cards only)


connected

Optionally, configure optical andelectrical equipment

(card and port parameters)

Create Ethernet MultipointECC services


Chapter 1 Configuring Ethernet OverviewConfiguring CPE to Ethernet Services Procedure

Configuring CPE to Ethernet Services Procedure

Use this procedure as a guideline to configure CPE devices to Ethernet services on a Traverse system.

Table 7-2 Configuring CPE Devices to Ethernet Services












5 Configure Ethernet multipoint ECC services

Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 10—“Ethernet Services,” page 7-119

6 Configure Ethernet traffic manage-ment

Section 7—Configuring Ethernet, Chapter 11—“Ether-net Traffic Management”


Traverse Provisioning Guide, Section 7: Configuring EthernetConfiguring CPE to Ethernet Services Procedure



Chapter 2Configuring Ethernet Equipment

Introduction This chapter contains the following topics:• Ethernet Cards, page 7-9• VLAN Tags, page 7-10

– Port Tagged, page 7-10– Customer Tagged, page 7-10– VLAN Bundling, page 7-11– Service Provider Tagged, page 7-12– Untagged Ethernet Frames, page 7-12

• VLAN Tagging Guidelines, page 7-14• Before You Begin, page 7-15• Configure Ethernet Cards, page 7-16• Configure Ethernet Port Parameter Values, page 7-18• Auto Negotiation, page 7-24• Configure Auto Negotiation, page 7-25• View or Edit the MAC Address Table, page 7-33

These procedures describe how to change configurable parameters only. See the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 2—“SONET Equipment,” page 5-5 and Section 5—Equipment, Chapter 3—“SDH Equipment,” page 5-29 for explanations of all the parameters and fields on each card (module).

Ethernet Cards


Cards Card Types




Traverse Provisioning Guide, Section 7: Configuring EthernetVLAN Tags

VLAN Tags Ethernet standards define VLAN tags as a mechanism to create multiple virtual LANs out of one physical LAN. That virtual LAN defines a forwarding domain and packets move between the physical ports that belong to the same virtual LAN. Packets tagged with the same VLAN tag belong to the same virtual LAN.

The Traverse system supports the following types of VLAN tagging models:• Port Tagged, page 7-10• Customer Tagged, page 7-10• VLAN Bundling, page 7-11• Service Provider Tagged, page 7-12• Untagged Ethernet Frames, page 7-12

Port Tagged In a service provider’s VLAN network, the Port tagging type identifies that every packet on a port belongs to the same service, regardless of whether or not the packet has a customer VLAN tag.

Customer Tagged

In a customer’s VLAN network, on the customer-facing ports, the Traverse can send and receive packets tagged with the customer VLAN tag.

Figure 7-3 Customer-Tagged Ethernet Frame

The 802.1Q VLAN tag contains the customer VLAN ID and the customer priority bits (priority field).

The customer VLAN ID has 12 bits that allows for identification of up to 4096 VLANs. Of the 4096 possible VLAN values, values 1 through 4093 are valid VLAN IDs. The value 0 identifies priority frames meaning the packet contains priority information, but no VLAN ID. Values 4094 and 4095 are reserved for system use.




Cards Card Types

Length/Type

MAC Client Data

Pad

Frame Check Sequence

802.1Q VLAN Tag

Source MAC Address

Destination MAC Address

Bytes

6

6

2

2

4

802.1p Priority Field (3 bits)VLAN ID (12 bits)

0-n

Preamble andStart Frame Delimiter 8

Ethertype 2


Chapter 2 Configuring Ethernet EquipmentVLAN Bundling

With Release TR3.2, VLAN IDs on customer-tagged ports can be bundled allowing users to provision a list of VLAN IDs to be mapped to a service for increased traffic. See VLAN Bundling, page 7-11.

The customer VLAN tag is also used to identify the Traverse Ethernet service to which this packet belongs. See Chapter 10—“Ethernet Services,” page 7-119.

The customer uses the 3-bit priority field to indicate the quality of service the packet receives in relation to other packets on the same data stream. These priority bits are used to set the internal class of service and the initial drop precedence for this packet. See Chapter 12—“Classifying and Prioritizing Packets,” page 7-159.

VLAN Bundling For Release TR3.2 and later, service providers can use the new VLAN Bundling feature. VLAN bundling is an important and commonly used MEF-compliant feature among Enterprise and Service provider customers. In the case of a service provider, this feature helps to conserve issuing service-VLAN (S-VLAN) IDs and offers flexibility to transport multiple “like” customers over the same link by enabling multiple customer-VLAN (C-VLAN) IDs to map to a single S-VLAN tag.

Important: For pre-TR3.2 releases, the tagging feature model remains intact and provides an Ethernet card configuration mapping of one C-VLAN ID to a S-VLAN ID. For TR3.2 and later releases, subscriber support is made available where multiple C-VLAN IDs map to a single service S-VLAN ID for application, such as Voice over IP (VoIP) or internet access. Users can reconfigure their system to utilize the new VLAN Bundling feature model as appropriate for their network configuration.

The VLAN Bundling feature offers support for a minimum of 100 C-VLAN IDs in an S-VLAN ID and configuration capability via the TransNav GUI or CLI.

Figure 7-4 Assign One Service Tag to Multiple Customer Tags

See Chapter 10—“Ethernet Services,” page 7-119 for information on configuring this feature.

TraverseEthernet

1

TraverseEthernet

2

TraverseEthernet

3

Ingress Frames:Tagged VLAN IDs: 1, 2, 3, 4, 5, 6, 7

Tagged VLAN IDs: 1, 2, 3, 4, 5, 6, 7

Egress Frames:

FE orGEport

Legend:CT - Customer tagST - Service tag CTs 4, 5, 6, 7 are

mapped into thesame ST

CTs 1, 2, 3 aremapped into the

same ST

EOS2

EOS1

Create one Ethernet service per EOS forall CTs in the EOS

Egress Frames:Tagged VLAN IDs: 1, 2, 3

IngressFrames:

Tagged VLAN IDs: 1, 2, 3

Egress Frames:Tagged VLAN IDs: 4, 5, 6, 7

IngressFrames:

Tagged VLAN IDs: 4, 5, 6, 7

FE orGEport

FE orGEport


Traverse Provisioning Guide, Section 7: Configuring EthernetService Provider Tagged

Service Provider Tagged

In a service provider’s VLAN network, the service provider VLAN tag identifies a particular customer’s flow within the service provider network. Values 1 through 4093 are valid service VLAN IDs. The service provider VLAN tag carries packet class of service and drop precedence information used within the service provider network.

The service provider VLAN tag can be used to multiplex traffic on ports that are within the service provider network. The customer VLAN tags, if any, on the customer’s packets are carried along as just data.

Figure 7-5 Service Provider-Tagged Ethernet Frame

If there is already a VLAN tag on the frame when it arrived on the port, the system adds a second tag before the customer VLAN tag in the header of the Ethernet frame. This process is called double-tagging, VLAN stacking, or Q-in-Q.

If the packet arrives untagged, the system adds the service provider VLAN tag.

Untagged Ethernet Frames

An untagged Ethernet frame is an Ethernet frame that does not have an 802.1Q VLAN tag in the header.

Figure 7-6 Untagged Ethernet Frame

Length/Type

MAC Client Data

Pad


802.1Q VLAN Tag

Ethertype

2

2

2

2

4

Source MAC Address


Bytes

6

6

802.1Q VLAN Tag802.1p Priority Field (3 bits)VLAN ID (12 bits)

Service Provider VLAN tag

Customer VLAN tag

0-n

PreambleStart Frame Delimiter 8

Ethertype 2

802.1p Priority Field (3 bits)VLAN ID (12 bits)

MAC Client Data

Pad


Length/Type

Source MAC Address


Bytes

6

6

2

0-n

4

Preamble andStart Frame Delimiter 8


Chapter 2 Configuring Ethernet EquipmentVLAN Tagging on Ethernet Ports

The Traverse system processes untagged Ethernet frames arriving on Port-based and Customer-tagged ports, and drops them if they arrive on Service-tagged ports. See the following topics for information on how the system processes untagged packets:• Chapter 10—“Ethernet Services,” Mix of Port-based and Service-tagged Ports

in Service, page 7-128• Chapter 10—“Ethernet Services,” All Ports in Service are Customer- tagged,

page 7-129• Chapter 10—“Ethernet Services,” Mix of Customer- tagged and Service-tagged

Ports in Service, page 7-131• Chapter 10—“Ethernet Services,” All Ports in Service Tagged as Service-

tagged, page 7-133

VLAN Tagging on Ethernet Ports

The Traverse Ethernet provisioning model supports multiple services sharing the same Ethernet port, Ethernet-over-SONET/SDH (EOS) port, Ethernet-over-PDH (EOP) port, or link aggregation group (LAG) by using the Tagging parameter. The selection in the Tagging parameter can be one of the following values: • 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. This VLAN tag 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.Untagged packets are treated, for service identification, as though they have a “0” VLAN tag.

• Bundled Customer-tagged. Multiple customer tags map to a single service tag.• Service-tagged. Every packet on this port is assumed to have a service provider

VLAN tag that identifies its Ethernet service within the service provider network. Service provider VLAN tags are used within the service provider network and are never used on customer-facing ports. The service 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.

When ports with different Tagging types are combined in the same service, the system performs some VLAN tag manipulation – adding or removing tags – as packets are


Traverse Provisioning Guide, Section 7: Configuring EthernetVLAN Tagging Guidelines

forwarded among service ports. This table summarizes system behavior regarding the Tagging parameter and Ethernet service ports.

See Chapter 10—“Ethernet Services,” Ethernet Services and VLAN Tagging, page 7-125 for more information on VLAN tagging and Ethernet services.

VLAN Tagging Guidelines

You cannot change the Tagging parameter of a port if one or more services are activated on that port.

An Ethernet service cannot have a mix of Customer-tagged and Port-based ports in the same service. You cannot add a port to an activated Ethernet service if adding that port results in a mix of Customer-tagged and Port-based ports in that service.

An Ethernet service can have a mix of Service-tagged ports and either other type of tagged port.

A port using Port-based tagging can only have one Ethernet service using that port.

A port using Customer-tagged or Service-tagged tagging can have more than one Ethernet service using that port.

No two activated services can use the same C-VLAN ID on the same Customer-tagged port.

A port using Customer-tagged tagging can have one service that allows untagged or priority-tagged packets, thus allowing the system to know which service to associate the untagged or priority-tagged packets. Priority-tagged packets are tagged with a priority tag that has a VLAN ID of 0 and a specific value of priority bits.

NGE, NGE Plus, and EoPDH cards support any number of concurrent port-VLAN IDs up to 3,000. The 10GbE and GbE-10 cards support any number of concurrent port-VLAN IDs up to 32,768.

Table 7-3 VLAN Tag Modification

Ingress Port

Egress Port

Port-Based Customer-Tagged

Bundled Customer-tagged (with C-VLAN ID

Preservation enabled)

Service-Tagged

Port-based No change Not supported Not supported Add tag

Customer-tagged Not supported Swap VLAN ID Supported Add tag

Bundled Cus-tomer-tagged

Not supported Supported(maintain original C-VLAN tagging)

Supported Supported

Service-tagged Strip tag Strip tag Supported Swap VLAN ID


Chapter 2 Configuring Ethernet EquipmentBefore You Begin

Before You Begin

Review the information in this topic before you configure the following Traverse equipment: NGE, NGE Plus, 10GbE, GbE-10, EoPDH:

Table 7-4 Ethernet Equipment Requirements




Hardware

The information in this section strictly pertains to the following Ethernet cards:

NGE• GBE4-FE16-TX• GBE2T-GBE2F-FE16-TX

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

Gigabit Ethernet• 10GBE• GBE-10

EoPDH • GBE4-FE16-TX-EoPDH• GBE2T-GBE2F-FE16-TX-EoPDH


The correct ECMs are installed. Traverse Installation and Commissioning Guide, Section 2—Network Interface Specifications, Chapter 5—“Ethernet (Electrical) Interface Cabling Specifications,” page 2-43

The physical network is connected. Traverse Installation and Commissioning Guide

Software



Optical protection groups are configured. Traverse Provisioning Guide, Section 3—Creating Protection Groups

If this card is part of a 1:1 Ethernet electrical pro-tection group, the protection groups must be con-figured.

Configure the card or ports of the working card.

Traverse Provisioning Guide, Section 3—Creating Protection Groups, Chapter 4—“Creating Equip-ment Protection Groups,” page 3-21


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Ethernet Cards

Configure Ethernet Cards

Use this procedure to customize behavior of an Ethernet card.

Table 7-5 Configure Ethernet Cards

Step Procedure

1 Read the information in the topic Before You Begin, page 7-15.

2 In 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.

Figure 7-7 Ethernet Card, Configuration Tab

3 Customer Tag: Enter an alphanumeric character string to identify the card to a customer.

4 Configure the following attributes for all EOS and EOP ports on this card:

Standard: Select the technology standard for the EOS and EOP ports on this card. (Note: To change the technology standard, you must switch the card type using the Switch to SONET/SDH button.):

ANSI: For North American operation.

ITU: For operations outside of North America.

LO Mapping (NGE and EoPDH cards only): Indicates the LO mapping for the EOS and EOP port members on this card.

If the value in the Standard parameter is ANSI, the only available LO mapping for EOS and EOP ports is VT1.5.

If the value in the Standard parameter is ITU, the default value can be changed. Select one of the following values:• Select VT15/VC11 to multiplex the data into a VC11 • Select VT2/VC12 (default) to multiplex the data into VC12

See Chapter 4—“Ethernet Over SONET/SDH (EOS),” page 7-49 for more information on EOS ports.

See Chapter 6—“Ethernet Over PDH (EOP),” page 7-71 for more information on EOP ports.

3

4

5

2


Chapter 2 Configuring Ethernet EquipmentConfigure Ethernet Cards

5 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, NGE Plus, and EoPDH cards, the alternate value is used in all VLAN tags in a packet. On EoPDH cards, this is used for both EOS and EOP ports.

On 10GbE or GbE-10 cards, the system distinguishes between incoming (customer) and outgoing (service) tags. If the corresponding port Ethertype parameter is disabled, then incoming tags must have 0x8100 Ethertype. If the corresponding port Ethertype parameter is enabled, then outgoing tags must match the setting of this card parameter. For example, if 0x9100 is selected, then only service tags with 0x9100 will be recognized. If only one tag exists, it is the outgoing tag and statements made for service tag apply.• 8100 (default): The system uses this standard Ethertype value.• 9100: The system manages packets with the Ethertype value of 9100

in the VLAN tag.

6 The Configure Ethernet Cards procedure is complete.

To configure the RSTP parameters, see Chapter 9—“Rapid Spanning Tree Protocol,” page 7-103.

To configure on LCAS parameters, see Chapter 8—“Link Capacity Adjustment Scheme,” page 7-89.

Continue to the procedure Configure Ethernet Port Parameter Values, page 7-18.

Table 7-5 Configure Ethernet Cards

Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Ethernet Port Parameter Values

Configure Ethernet Port Parameter Values

Use this procedure to customize behavior of an Ethernet interface.

Table 7-6 Configure Ethernet Port Parameter Values

Step Procedure

1 Review the information in Before You Begin, page 7-15.

2 In Shelf View, click an Ethernet port. If this card is in a 1:1 equipment protection group, click the port on the working card.

3 Click the Config tab to display the Ethernet Port Configuration screen.

Figure 7-8 Ethernet Port Configuration Screen

4 Transmitter State (GBE and 10GbE ports only): Determines if the laser on a GBE or 10GbE port is turned on or off. • On (default): The laser is on.• Off: Select to turn off the laser.

5 76

4

8


Chapter 2 Configuring Ethernet EquipmentConfigure Ethernet Port Parameter Values

5 If this is an optical Ethernet port, optionally enable the automatic laser shut down (ALS) feature on this port.

Transmitter Auto Shutdown: Automatically shuts 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 (automatic laser shutdown) alarm against the optical facility when the transmitter has been turned off automatically.• Disabled (default): The ALS feature is turned off.• Manual: The operator initiates a single laser pulse from the transmitter

for the amount of time specified in the Recovery Pulse Width parameter. To send the single laser pulse, click Current Transmitter State, then click Manual Restart.

• Automatic: The system turns off the transmit laser for a random time between 100 and 300 seconds. The transmit laser turns on if one of the following conditions occur:– The user manually sends a single laser pulse (click Current

Transmitter State). – If the system receives a valid signal for more than 800 ms.– After the random timer expires, the system sends periodic laser

pulses from the transmitter for the amount of time specified in the Recovery Pulse Width parameter.

Recovery Pulse Width (sec) (GBE and 10GBE ports only): The system enables the transmitter for the amount of time, in seconds, specified in this parameter. Valid only if the Transmitter Auto Shutdown parameter value is Manual or Automatic. Enter a time between 2 and 10 seconds; default is 5 seconds.

6 Change any of the following parameters for any Ethernet interface:

Jumbo Frame Support: 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): Enter the jumbo frame size (available only when Jumbo Frame Support is Enabled). Range is 1522 to 9600 bytes; default is 9600 bytes.

Table 7-6 Configure Ethernet Port Parameter Values (continued)

Step Procedure



7 Configure the Tagging parameter for this port:• 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. This VLAN tag is termed the customer VLAN tag and is significant for Traverse Ethernet service definition. Customer-tagged ports use the customer VLAN tag (to associate the packet with a particular service).

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

8 Change any of the following general parameters for the interface:• Customer: Select from the list of defined customers. • Customer Tag: Enter an alphanumeric character string to identify the

port to a customer.• PM Template: Select from the list of defined performance monitoring

templates (of type ethernet_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for Ethernet ports.

• Alarm Profile: Select from the list of defined alarm profiles (of type ethernet_ptp) to customize service-affecting and non-service-affecting alarm severities. Default value is default, which is the default ethernet_ptp alarm profile.


Step Procedure



9 Click Advanced to display the Advanced Configuration dialog box.

Max Info Rate (Mbps) (MIR) (NGE, NGE Plus, and EoPDH cards only): Specify the maximum ingress data rate (in Mbps) allowed for this port. Incoming packets above this rate are discarded.

Manual Pause: Indicates if a PAUSE frame should be sent when the ingress rate matches the rate specified in the Max Info Rate (Mbps) parameter. The link partner should limit its rate of transmission to the value specified in this parameter. The incoming packets above this rate are discarded. Select one of the following valid values:• Disabled: Select to disable the PAUSE feature for this port. If

disabled, the link partner’s transmission may exceed MIR. • Enabled: Select to send a PAUSE frame when the ingress rate matches

the rate specified in the Max Info Rate (Mbps) parameter.• RxOnly: The system commits to stop transmitting on the link when it

receives a PAUSE frame from the link partner. • TxOnly (default): The system sends a PAUSE frame to the link partner

in times of upstream congestion or if the port is receiving traffic over the value specified in the Max Info Rate (Mbps) parameter.

10 Insert Alternate VLAN Ethertype: Select the check box 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, NGE Plus, and EoPDH cards, the alternate value is used in all VLAN tags in a packet. On EoPDH cards, this is used for both EOS and EOP ports.

On 10GbE or GbE-10 cards, the system distinguishes between incoming (customer) and outgoing (service) tags. If the corresponding port Ethertype parameter is disabled, then incoming tags must have 0x8100 Ethertype. If the corresponding port Ethertype parameter is enabled, then outgoing tags must match the setting of this card parameter. For example, if 0x9100 is selected, then only service tags with 0x9100 will be recognized. If only one tag exists, it is the outgoing tag and statements made for service tag apply.• 8100 (default): The system uses this standard Ethertype value. • 9100: The system manages packets with the Ethertype value of 9100

in the VLAN tag.


Step Procedure



11 In the Queuing Policy parameter, specify how the queues are managed. Select one of the following values: • FIFO (default): First-in-first-out. Select this queuing policy to

schedule all packets for transmission based on the FIFO algorithm. All traffic uses CoS1. Optionally, configure whether shaping should be employed using the FIFO Shaping Enable and the FIFO Shape Rate parameters. Go to Step 12.

• Priority: Select this queuing policy to schedule all packets for transmission based on strict priority, using three classes of service. There are three priorities: highest priority traffic uses CoS1, medium priority traffic uses CoS2, and low priority traffic uses CoS3.

• WFQ: Weighted fair queuing. Select this queuing policy to guarantee a specific amount of the port’s bandwidth when there is congestion on the port. WFQ uses 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. Go to Step 13.

12 If FIFO is the value in the Queuing Priority parameter, configure the following parameters:• FIFO Shape Enable: Specify if the system will use the number in the

FIFO Shaping Rate parameter to shape the traffic being transmitted onto the port; default is Disabled.

• FIFO Shaping Rate: If the FIFO Shaping Rate is enabled, for GbE ports specify a number between 1 and 1000 Mbps; default is 1000. For 10GbE or GbE-10 ports, specify a number between 1 and 10,000 Mbps; the default for the 10GbE card (1-port 10GbE) is 10000, the default for each port on the GbE-10 card (10-port GbE) is 1000.


Step Procedure



13 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 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 is 1 which means packets with the CoS2 have no priority in relation to the other classes of service.



14 Click Done to save your changes, close the Advanced Parameters dialog box and return to the Ethernet Port Configuration screen.

15 Click the Lock icon , located in the lower left corner of the screen, to unlock the port and be able to monitor potential problems.


17 The Configure Ethernet Port Parameter Values procedure is complete.

Continue to any of the following procedures according to your network plan:• Chapter 3—“Link Aggregation,” page 7-37• Chapter 11—“Ethernet Traffic Management,” page 7-147


Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetAuto Negotiation

Auto Negotiation

Auto-negotiation is a process described in IEEE standard 802.3 that allows two devices on an Ethernet segment (link partners) to determine mutually agreeable settings for speed, duplex, and pause flow control.

When auto-negotiation is enabled for a port, the system initiates auto-negotiation whenever:• the port receives a signal when there had previously been no signal.• a link partner initiates auto-negotiation.• the operator makes any change to the advertisement parameters for the port.• the operator changes the value in the Auto-negotiation parameter to ON.• the operator requests that auto-negotiation be restarted immediately on a specified

port.

The auto-negotiation process completes in approximately three seconds.

The link is considered down and a Link Fail alarm appears when one of the following instances occur:• The link partners are unable to resolve to a common mode of operation for any

negotiated parameter.• One or more link partners does not advertise any parameters.• If the detected speed and assumed duplex of the link partner are not compatible

with the Traverse.

If auto-negotiation is enabled for an FE port but the link partner does not negotiate, the system assumes that the link partner is operating in half duplex mode.

GbE-10 card GbE TX ports have auto-negotiation “forced” with speed set to 10 Gbps and duplex set to FULL DUPLEX. Manual Pause, Advertise 1000M Full Duplex, and Advertised PAUSE RX are provisionable. Through the Manual Pause parameter, Forced Pause Receive is provisionable and Forced Pause Transmit is disabled. Advertised PAUSE TX is disabled.

To enable auto-negotiation between the Traverse system and a TransAccess 200 Mux, ensure the Traverse BP DCN connection is either static 100/half duplex or auto-negotiation Advertise 100M Half Duplex. However, if the BP DCN connection is set at auto-negotiation Advertise 100M Half Duplex., the far-end must advertise 100/half duplex.

Important: By default, the Auto-negotiation feature is enabled with the exception of 10GBE and EOP ports, where auto-negotiation and pause functionality are unavailable. For GBE-10 TX ports, auto-negotiation is “forced” with speed set to 10 Gbps and duplex set to FULL_DUPLEX. However, the Traverse allows the operator to disable auto-negotiation for both ETH100TX and optical GbE ports, but always performs auto-negotiation on copper GbE TX ports.

Force10 recommends that if the peer device is 802.3 compliant, the operator leave the Auto-negotiation feature enabled.


Chapter 2 Configuring Ethernet EquipmentConfigure Auto Negotiation

Configure Auto Negotiation

Use the following procedure to help you configure Auto-negotiation on a port.

Table 7-7 Configure Auto-negotiation

Step Procedure

1 In Shelf View, click an Ethernet port, then click the Config tab to display the Ethernet Port Configuration screen. If this card is in a 1:1 equipment protection group, click the port on the working card.

Figure 7-9 Ethernet Port Configuration

2 In the Auto-negotiation parameter, select one of the following values: • On (default for all port types): Negotiate the speed, duplex attributes,

and pause flow control of the link based on the values in the Advertise parameters (as applicable to the port type). – For ETH100TX ports, go to Step 3.– For GBE ports, go to Step 4.– For GBETX ports, go to Step 5.

• Off: Available for ETH100TX and optical GBE ports only. The link starts up and initializes with the values in the Manual Speed, Manual Duplex, and Manual PAUSE fields (as applicable to the port type). – For ETH100TX ports, go to Step 6.– For GBE ports, go to Step 7.


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Auto Negotiation

3 Click an ETH100TX port, then click Advanced to display the list of Advanced parameters for this port.

Figure 7-10 ETH100TX Port Auto-negotiation Parameters

If Auto-negotiation is turned on for this port, ETH100TX ports can adver-tise that the port is capable of operating as specified in the following parameters:• Advertise 10M Half Duplex: Enabled (default) or Disabled.

Advertise half duplex and 10 Mbps speed when Auto-negotiation is turned ON. Disable this parameter to specify this port not operate in this mode.

• Advertise 10M Full Duplex: Enabled (default) or Disabled. Advertise full duplex and 10 Mbps speed when Auto-negotiation is turned ON. Disable this parameter to specify this port not operate in this mode.

• Advertise 100M Half Duplex: Enabled (default) or Disabled. Advertise half duplex and 100 Mbps speed when Auto-negotiation is turned ON. Disable this parameter to specify this port not operate in this mode.

• Advertise 100M Full Duplex: Enabled (default) or Disabled. Advertise full duplex and 100 Mbps speed when Auto-negotiation is turned ON. Disable this parameter to specify this port not operate in this mode.

• Advertise PAUSE: Enabled (default) or Disabled. Select Enabled so the system transmits a PAUSE frame when the incoming traffic exceeds MIR. Select Disabled so the system does not transmit a PAUSE frame.When Enabled, the system responds to a received PAUSE frame by suspending transmission of traffic. When Disabled, the system does not suspend transmission of traffic when it receives a PAUSE frame.

Table 7-7 Configure Auto-negotiation (continued)

Step Procedure



4 Click a GBE port, then click Advanced to display the list of Advanced parameters for this port.

Figure 7-11 GBE Port Auto-negotiation Parameters

If Auto-negotiation is turned on for this port, GBE ports can advertise one or more of the following parameters:• Advertise 1000M Full Duplex: Enabled (default) or Disabled.

Advertise full duplex and 1000 Mbps (1 Gbps) speed. • Advertise 1000M Half Duplex (TE-100 only): Enabled (default) or

Disabled. Advertise half duplex and 1000 Mbps (1 Gbps) speed. • Advertise PAUSE RX: Enabled (default) or Disabled. The system

commits to stop transmitting on the link when it receives a PAUSE frame from the link partner. Read-only for optical GBE ports when Auto-negotiation is turned ON. Configurable when Auto-negotiation is turned OFF.

• Advertise PAUSE TX: Enabled (default) or Disabled. The system sends a PAUSE frame to the link partner in times of upstream congestion or if the Traverse detects that this port is receiving traffic over the value specified in the Maximum Information Rate parameter.


Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Auto Negotiation

5 Click a GBETX port, then click Advanced to display the list of advanced parameters for this port.

Figure 7-12 GBETX Port Auto-negotiation 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 the Traverse detects that this port is receiving traffic over the value specified in the Maximum Information Rate parameter.

6 If Auto-negotiation is turned OFF for this ETH100TX port, set the follow-ing parameters:• Manual Duplex: Indicates the mode of operation for this port based

on IEEE standard 802.3.– Full (default): The port operates in full duplex mode and allows

simultaneous transmissions on the link.– Half: The port operates in half-duplex mode and uses CSMA/CD

to share access to the link.• Manual Speed: Configure the data rate of the link:

– 10 Mbps– 100 Mbps (default)

• Manual Pause: Configure if the system will send a PAUSE frame to the link partner in times of upstream congestion or if the traffic on this port is bursting over the value specified in the Maximum Information Rate parameter.

• Crossover: Controls the MDI/MDIX configuration of this port. – Enabled. Select to reverse the transmit and receive on this port.

Turns a straight-through cable into a crossover cable.– Disabled (default)


Step Procedure



7 When Auto-negotiation is turned OFF for this optical GBE port, set the following parameters:• Manual Duplex: Indicates the mode of operation for this port based

on IEEE standard 802.3.– Full (default): The port operates in full duplex mode and allows

simultaneous transmissions on the link.– Half: The port operates in half-duplex mode and uses CSMA/CD

to share access to the link.• Manual Speed (Read only): 1000 Mbps (1 Gbps)• Manual PAUSE:

– Enabled. The system will send a PAUSE frame and commit to stopping traffic if it receives a PAUSE frame.

– Disabled. The system does not send or receive PAUSE frames.– TX Only (default). The system will send a PAUSE frame to the

link partner in times of upstream congestion or if the Traverse detects that this port is receiving traffic over the value specified in the Maximum Information Rate parameter.

– RX only. The Traverse commits to stop transmitting on the link when it receives a PAUSE frame from the link partner.

8 The Configure Auto-negotiation procedure is complete.


Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetView VLAN Usage

View VLAN Usage

Use this procedure to view VLAN Usage statistics.

Table 7-8 View the VLAN Usage

Step Procedure

1 In Shelf View, click an Ethernet port, then click the Config tab. If this card is in a 1:1 equipment protection group, click the port on the working card.


2 On the Ethernet Port Configuration screen, click the VLAN Usage button to display the VLAN Usage dialog box.

Figure 7-14 VLAN Usage Dialog Box

Port: Displays the port.

Tagging: Displays the port tagging type.

Three options are available for viewing:• Show all VLAN: Shows all VLAN Usage (used and available) for this

port.• Show VLAN in use: Shows VLAN currently in use for this port.• Show available VLAN: Shows VLAN currently available to this port.

2


Chapter 2 Configuring Ethernet EquipmentView VLAN Usage

3 Click Refresh to retrieve the current data.

Click Done to save the changes, close the dialog box, and return to the main screen.

4 The View the Negotiated Status of a Link procedure is complete.

Table 7-8 View the VLAN Usage (continued)

Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetView the Negotiated Status of the Link

View the Negotiated Status of the Link

Use this procedure to view the negotiated status of the link.

Table 7-9 View the Negotiated Status of a Link

Step Procedure

1 In Shelf View, click an Ethernet port, then click the Config tab. If this card is in a 1:1 equipment protection group, click the port on the working card.


2 On the Ethernet Port Configuration screen, click the Status button to display the Ethernet Port Status dialog box.

Figure 7-16 Ethernet Port Status Dialog Box

Auto-negotiation: Displays the configured value from the Auto-negotiation parameter.

Configuration Pause: Displays the configured value from the PAUSE parameter.

Configuration Duplex: Displays the configured value from the Duplex parameter.

Configuration Speed: Displays the configured value from the Speed parameter.

System Link Status: Displays the current status of the link. Valid values are:• Up: Indicates the link is active.• Down: Indicates the link is not working.

System Pause: Displays the current status of the PAUSE parameter.

System Duplex: Displays the current status of the Duplex parameter.

System Speed: Displays the current speed of the link.

2


Chapter 2 Configuring Ethernet EquipmentView or Edit the MAC Address Table

View or Edit the MAC Address TableMAC learning is the process the system uses to associate a MAC address with a specific port, based on having received a packet at that port with that MAC address as its Source MAC address. Future packets addressed to that MAC address are forwarded to that single port instead of being “flooded” to all ports. Learning, re-learning, aging, and clearing are all standard MAC table functions.

MAC forwarding in a bridge service follows well-documented rules for determining the set of output ports for a packet based on the destination MAC address in its header.

The Traverse learns MAC addresses in either of the following ways:• The Traverse automatically learns MAC addresses on a port and service. If a port is

in multiple bridge services, any MAC address received on that port is learned just in that service. When the operator views the table of learned MAC addresses on a card, the system identifies the service in which the address was learned on the port.

• The operator can manually add MAC addresses to the MAC Address table for any service and port (See the procedure Configure Ethernet Cards, page 7-16, MAC Address parameter). This information is part of service provisioning and can be changed while the service is activated. Manually-added MAC addresses work exactly as learned addresses, but do not age.

Each Ethernet card can learn up to 32,000 MAC addresses, however, only the EoPDH cards have 300 factory-assigned MAC addresses.

3 Click Refresh to retrieve the current data.

Click Done to save the changes, close the dialog box, and return to the main screen.

4 The View the Negotiated Status of a Link procedure is complete.

Table 7-9 View the Negotiated Status of a Link (continued)

Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetView or Edit the MAC Address Table

Use this procedure to view or modify the MAC Address table in the system.

Table 7-10 View or Edit the MAC Address Table

Step Procedure

1 In Shelf View, click an Ethernet card, then click the Config tab.

2 Click the MAC Address table button to display the MAC Address Queries dialog box. The MAC Address Queries dialog box allows a user to query all MAC addresses in the system.

Figure 7-17 MAC Address Queries Dialog Box

3 Filter the MAC addresses using all or any of the following options:

MAC Address:• ALL (default) • Define: Enter a specific MAC address

Service: Select a service identification number (SID). The valid values are: • ALL (default): Query all services• Define: Enter a specific SID

Port Id: Select the port number from the drop-down menu. Available when the Port Type value is EOS, ETH, GBE, LAG, or EOP; default is ALL.

Port Type: Select one of the following values to filter the list based on the type of port:• None (default)• ETH: ETH100TX interfaces• GBE: GBE ports• 10GBE: 10GbE ports• EOS: EOS ports • LAG: Link aggregation group ports• EOP: Ethernet over PDH port (EoPDH cards only)


Chapter 2 Configuring Ethernet EquipmentView or Edit the MAC Address Table

4 Count: Click to count all the MAC addresses learned on this card.

5 Delete All: Click to remove all MAC addresses recorded in the forwarding table.

6 Query: Click to query the MAC addresses if any of the filters were used in Step 3.

7 Delete: Delete the MAC addresses highlighted in the MAC Address list.

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

9 The View or Edit the MAC Address Table procedure is complete.

Table 7-10 View or Edit the MAC Address Table (continued)

Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetView or Edit the MAC Address Table



Chapter 3Link Aggregation

Introduction This chapter contains the following topics:• Ethernet Cards, page 7-37• Link Aggregation, page 7-37• Guidelines to Configure Link Aggregation, page 7-38• LAG Capacity Changes, page 7-39• Before You Begin, page 7-39• Create a Link Aggregation Group, page 7-41

Ethernet Cards

Link Aggregation

Clause 43 in IEEE 802.3 defines a link aggregation group (LAG) as Ethernet links grouped together to appear as if they were a single logical link. On the Traverse system, each logical link can consist of up to eight customer-facing Ethernet ports of full duplex point-to-point links operating at the same data rate.

Use a LAG (also known as an Etherchannel) on an Ethernet service in the same manner as an Ethernet port. However, a LAG has more capacity and availability than a regular Ethernet port. A LAG can carry more data than an individual port and will continue to operate at reduced capacity when individual ports fail. Configure a service-related attribute of LAG in a service (such as Classifier or Policer) in the same manner as you would configure service-related attributes of an Ethernet port.


Cards Card Types







Traverse Provisioning Guide, Section 7: Configuring EthernetGuidelines to Configure Link Aggregation

Link Aggregation, in accordance with the standard, assures that all frames in the same ‘conversation’ are sent out the same link to minimize packet reordering. For the Traverse Ethernet cards, ‘conversation’ is defined as “all frames that share the same source MAC address, destination MAC address, and (if the frame contains an IP packet) source IP address and destination IP address.”

When any of the links in the LAG fails, the system transfers the traffic from the failed link to another link that is still in operation. This adjustment is automatic and does not require operator action.

The operator configures a LAG on an Ethernet card. The system propagates the values in the LAG parameters to the member ports in the LAG. The individual Ethernet ports in the LAG cannot be used as separate ports. If a LAG on an activated Ethernet service has no members, an error message displays.

Guidelines to Configure Link Aggregation

Before you configure a LAG, consider the following guidelines:• Up to 8 ports in one LAG on an NGE, GbE-10, or EoPDH card; only 1 port on a

10GbE card. One port is termed a member of the LAG.• Only 1 LAG on the same 10GbE card, up to 10 LAGs on the same GbE-10 card, or

up to 20 LAGs on the same NGE or EoPDH card. • Member ports must of the same type: either ETH100TX or GBE. Optical and

electrical GBE ports can be in the same LAG. • GbE-10 cards have different numbers of physical ports and will have

correspondingly different numbers of LAGs.• Ports can be dynamically added to or removed from a LAG.• Configured LAG member parameters are propagated to the individual ports. The

system propagates a configured LAG member attribute to all of the individual ports in the LAG. These attributes cannot be changed or configured directly while the port is in a LAG.

• All ports in the LAG must be full duplex.• An Ethernet port already in an activated Ethernet service or with a terminal

loopback on the port cannot be a member of a LAG. • A service will not activate if one member (Ethernet port) is already in a LAG. • A LAG cannot be deleted if it is currently in an activated Ethernet service.• When the forwarding rules for a service cause a packet to be forwarded to a LAG

and when that LAG is in an alarm condition, then the system drops the packet.• If the link partner of a LAG is connected to third-party equipment, the link partners

must be configured to the equivalent of a LAG using the same set of ports.

Carrier Ethernet Protection Pair (CEPP). CEPP supports Link Aggregation for parallel links based on the IEEE 802.3ad standard. A Link Aggregation Group (LAG) with CEPP can contain up to eight port members of the same type (FE or GbE) from the two separate NGE Plus or EoPDH cards. Service providers create a LAG on the working card of the CEPP and include member ports from either card in the CEPP.

To create CEPP protection groups, see Section 3—Creating Protection Groups, Chapter 5—“Carrier Ethernet Protection,” page 3-29.


Chapter 3 Link AggregationBefore You Begin

LAG Capacity Changes

In cases where the capacity of the LAG is reduced while the LAG is in service, the system automatically adjusts its selection process such that conversations that had been directed to the failed port are directed to another port in the LAG.

Activated Ethernet services on a LAG may experience a short period of packet loss while the system adjusts the distribution mechanism to exclude a failed or removed port.

In cases in which the capacity of the LAG is increased while the LAG is in service (due to port recovery or manual addition) the system automatically adjusts its selection process such that the recovered or newly-added port is eligible to be used for some conversations

Recovery of a previously-failed port in a LAG, and addition of a new port to a LAG, does not cause packet loss on any activated service using the LAG.

Before You Begin

Review the information in this topic before you configure link aggregation groups on the following Ethernet cards: NGE, NGE Plus, 10GbE, GbE-10, and EoPDH.

Table 7-11 Link Aggregation Requirements




Hardware


NGE• GBE4-FE16-TX• GBE2T-GBE2F-FE16-TX

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

Gigabit Ethernet• 10GbE • GbE-10


Traverse Product Overview Guide, Section 3—Card (Module) Descriptions.

The correct ECMs are installed. Traverse Installation and Commissioning Guide, Section 2—Network Interface Specifications, Chapter 5—“Ethernet (Electrical) Interface Cabling Specifications,” page 2-43.


Software


Traverse Provisioning Guide, Section 7: Configuring EthernetBefore You Begin

Verify the network is discovered. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 2—“Discover the Network,” page 1-9.

Ensure the timing is configured. Traverse Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Configuring Network Timing,” page 1-15.

Ensure the optical protection groups are config-ured.

Traverse Provisioning Guide, Section 3—Creating Protection Groups.

If this card is part of a 1:1 Ethernet electrical pro-tection group or a Carrier Ethernet Protection Pair, the protection groups must be configured.

Configure the LAG on the working card.

Traverse Provisioning Guide, Section 3—Creating Protection Groups, Chapter 4—“Creating Equip-ment Protection Groups,” page 3-21.

Ethernet cards and interfaces are configured. Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 2—“Configuring Ethernet Equipment,” page 7-9.

Table 7-11 Link Aggregation Requirements (continued)



Chapter 3 Link AggregationCreate a Link Aggregation Group

Create a Link Aggregation Group

Use this procedure to create a link aggregation group (LAG) of customer-facing Ethernet ports.

Note: On 10GbE cards, only one LAG can be created. On GbE-10 cards, create up to 10 LAGs per card.

Table 7-12 Create a Link Aggregation Group

Step Procedure

1 Read the information in Before You Begin, page 7-39.

2 In Shelf View, create a link aggregation group.

Figure 7-18 Ethernet Tab, LAG Subtab

a. Click the Ethernet tab.b. Click the LAG subtab.c. Click the Add button to display the Create LAG tab.

Figure 7-19 Create LAG Tab

2a

2b

2c

3

512 13

4


Traverse Provisioning Guide, Section 7: Configuring EthernetCreate a Link Aggregation Group

3 Configure the attributes of the LAG:• 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.

• Customer: Select from a list of defined customers.• Link Type (Read-only for 10GbE and GbE-10 cards): Select the types

of ports to be included in this LAG. Member ports must of the same type.– FE (default for NGE and EoPDH cards). Select FE to create a

LAG of FE ports.– GbE (default for 10GbE and GbE-10 cards). Select GbE to create

a LAG of GbE ports.

Table 7-12 Create a Link Aggregation Group (continued)

Step Procedure



4 Choose the Ethernet ports to be members of this LAG.

Figure 7-20 Choose Ports for this LAG


b. Navigate the tree and select the correct source endpoint. c. Click Done to close the dialog box and return to the Create LAG tab

on the main screen.d. Type a unique number in the Member# column.e. Add extra rows to the endpoint table. Click the plus sign in the Add

column. Add as many rows as required for this LAG.f. Repeat substeps a. to e. for each required port.


Step Procedure

5a

5b

5d

5c

5e



5 Configure the attributes of the LAG members. Click the Advanced button to display the LAG Advanced Parameters dialog box.

Configure the Tagging type for this port:• Port-based: Every packet on this port is considered to belong to the


• Customer-tagged: Every packet on this port is assumed to have a VLAN tag that identifies its service in the customer network. This VLAN tag 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.


6 Configure the Part Loss Threshold value for this port: • 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 for NGE and EoPDH; enter 1 for GbE-10 cards, and a number between 1 and 10 for a 10GbE card.

• The default is 0 which means the corresponding alarm is never raised.


Step Procedure



7 In the Queuing Policy parameter, specify how the queues are managed. Select one of the following values.

Note: Setting the Queuing Policy for EoPDH cards can greatly affect traffic management on EOP ports. For more information, see Chapter 11—“Ethernet Traffic Management,” Managing Traffic on EOP Ports, page 7-152.• FIFO (default): First-in-first-out. Select this queuing policy to


• Priority: Select this queuing policy to schedule all packets for transmission based on strict priority, using three classes of service. There are three priorities: Highest priority traffic uses CoS1, medium priority traffic uses CoS2, and low priority traffic uses CoS3.



FIFO Shaping Rate parameter to shape the traffic being transmitted onto the port. Valid values are Disabled (default) and Enabled.

• FIFO Shaping Rate: If the FIFO Shaping Rate is enabled, specify a number between 1 and 1000 Mbps for NGE cards. For 10GbE and GbE-10 cards, specify a number between 1 and 10,000 Mbps; default for 10GbE is 10000, default for GbE-10 is 1000.


Step Procedure




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.



10 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, it is the outer tag and statements made for service tag 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.

11 Max Info Rate (Mbps) (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.


Step Procedure



12 Click Done to close the Advanced Parameters tab and return to the main screen.

13 Click the Lock icon , located in the lower left corner of the screen, to unlock the port and be able to monitor potential problems.


15 The Create a Link Aggregation Group procedure is complete.

Configure the traffic management characteristics of this LAG. See Chapter 11—“Ethernet Traffic Management,” page 7-147.


Step Procedure



Chapter 4Ethernet Over SONET/SDH (EOS)

Introduction This chapter contains the following topics:• Ethernet over SONET/SDH (EOS), page 7-50• EOS Ports, page 7-50• Virtual Concatenation, page 7-51• Before You Begin, page 7-54• Guidelines to Configure EOS Ports, page 7-51• Configure EOS Port Members, page 7-55• Configure Service Groups, page 7-56• Creating EOS Ports, page 7-58

Ethernet Cards


Cards Card Types







Traverse Provisioning Guide, Section 7: Configuring EthernetEthernet over SONET/SDH (EOS)

Ethernet over SONET/SDH (EOS)

Ethernet traffic travels over SONET or SDH connections. Creating Ethernet over SONET/SDH (EOS) connections require two components:• EOS ports. On a Traverse system, an EOS port is a port-like abstraction

representing the adaptation point between Ethernet and SONET/SDH. This EOS port can be thought of as an Ethernet WAN interface, compared to physical Ethernet ports which are Ethernet LAN interfaces.

• Transport connections. Create a regular SONET or SDH service. For end-to-end services, the endpoints of the service are Ethernet cards (virtual SONET and STM ports on the backplane). For hop-by-hop services, one endpoint is the virtual SONET or STM port on the backplane of the Ethernet card; the second endpoint is a SONET or STM port.

EOS Ports An EOS port is a port-like abstraction representing the adaptation point between Ethernet and SONET/SDH.

The following Traverse cards support EOS ports: NGE, NGE Plus, 10GbE, GbE-10, and EoPDH.

The following functions take place at an EOS port:• Encapsulation. The cards use frame-mapped GFP, according to ITU-T G.7041, to

encapsulate Ethernet frames for transmission over SONET/SDH transport connections represented by EOS ports.

• Termination. Members of an EOS port are the endpoints of SONET or SDH services.

• Inverse Multiplexing. EOS ports support contiguous concatenation (no fragmentation) and both high and low order virtual concatenation.

• Other features such as MAC learning, LCAS, and RSTP.

The EOS port raises alarms and collects performance monitoring data the same way as a physical Ethernet port. It is also a valid endpoint in an Ethernet service.

Multiple members in an EOS port create a virtual concatenation group (VCG).

An operator creates and activates the SONET or SDH services, then creates the EOS ports on the card.

It is possible to have an EOS port with activated SONET or SDH services yet no Ethernet service connected to the EOS port. In this case, the SONET or SDH services and the EOS port will be operating fine but there is no Ethernet data to send. Any Ethernet data the EOS port receives from the transport network gets dropped.

If an operator creates an EOS port with no members, the system generates a “No Provisioned Members” alarm on that EOS port.


Chapter 4 Ethernet Over SONET/SDH (EOS)Guidelines to Configure EOS Ports

Virtual Concatenation

Virtual concatenation (VCAT) is an inverse multiplexing technique, based on ITU-T G.707/Y.1322 and G.783 standards, that supports the bundling of multiple independent lower-rate channels into a higher rate channel. VCAT enables efficient mapping of encapsulated Ethernet frames directly into a payload of separate path signals, known as a virtual concatenation group (VCG).

For example, in SDH standards, a VC-3-6v is a virtually concatenated path multiplexed onto six VC-3 paths. Its bandwidth is six times that of a VC-3.

In SONET standards, an STS-1-6c is a virtually concatenated path multiplexed onto six STS-1 paths. Its bandwidth is six times that of an STS-1.

This mapping technique eliminates the rigid hierarchies of the common SONET and SDH containers, enabling service providers to provision and transport data services more efficiently.

To create a virtual concatenated group (VCG) for a SONET or SDH circuit on the Traverse system, create an EOS port.

Guidelines to Configure EOS Ports

These procedures require the NGE, NGE Plus, 10GbE, GbE-10, or EoPDH cards AND the underlying SONET or STM cards to be connected and configured in a transport topology.

Each NGE or EoPDH Ethernet card has one virtual OC-48 / STM-16 port. Each 10GbE or GbE-10 card has one virtual OC-192 / STM-64 port. These are called virtual optical ports or VOPs. In all cases, the virtual port is termed port 0 in the user interface. All ports on the 10GbE or GbE-10 cards are considered optical ports.

EOS Port Members (SONET or SDH Services). Each Ethernet card supports termination functions for either SONET or SDH, but not both. If provisioned for SDH termination, the Ethernet cards can terminate either VC-11 or VC-12, but not both at the same time.

When the virtual port is in SONET mode, the operator can channelize into any or a combination of the following SONET bandwidths: • STS-3c• STS-1• VT1.5 (NGE and EoPDH cards only)

See Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services,” page 4-19 to create SONET services.

When the virtual port is in SDH mode, the following table indicates the SDH bandwidths available for each card:


Traverse Provisioning Guide, Section 7: Configuring EthernetGuidelines to Configure EOS Ports

ive

Table 7-13 SDH Bandwidths Available by Ethernet Card Type

See Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,” page 4-41 to create SDH services.

The SONET/SDH services can be either unidirectional or bidirectional. It is possible to add the transmit direction of an endpoint to one EOS port, and the receive direction of the same endpoint to a different EOS port.

It is also possible to add the same endpoint to an EOS port twice, once as unidirectional in the transmit direction and once as unidirectional in the receive direction. Use this method to set up an asymmetric virtual concatenation group.

It is possible to add or remove endpoints dynamically to an EOS port.

Virtual Concatenation. All members of an EOS port (Concatenation Type = Virtual) must be of the same bandwidth.

The system supports a maximum differential delay of 64 milliseconds on NGE cards and 128 milliseconds on 10GbE, GbE-10, and EoPDH cards.

The Traverse supports asymmetric virtual concatenated groups. That is, the system supports a different number of SONET or SDH services in the transmit direction than in the receive direction.

EOS members can have protected and unprotected paths.

EOS Ports. Each NGE card supports up to 64 EOS ports. Each 10GbE, GbE-10, or EoPDH card supports up to 128 EOS ports. On EoPDH cards, the ports can be EOS, EOP, or any combination of EOS and EOP ports totalling 128. For more information on EOP ports, see Chapter 6—“Ethernet Over PDH (EOP),” page 7-71.

You cannot delete any EOS port that is being used in an activated Ethernet service.

Additionally, for NGE cards only: • If you delete an EOS port that contains members, you must delete the EOS port

from both the local and remote NGE cards. • It is possible to add or remove members dynamically to an EOS port. Remove

members in both the local and the remote EOS ports.

NGE Cards 10GbE and GbE-10 Cards EoPDH

AU-4 / VC-4 AU-4 / VC-4 AU-4 / VC-4

AU-3 / VC-3 AU-3 / VC-3 AU-3 / VC-3

AU-3 / VC-3 / TUG-2 / VC-11 AU-3 / VC-3 / TUG-2 / VC-11

AU-3 / VC-3 / TUG-2 / VC-12 AU-3 / VC-3 / TUG-2 / VC-12

NGE 10GbE and GbE-10 EoPDH

Concatenation Size Transmit Receive Transmit Receive Transmit Rece

STS-3C, VC-4 8 8 64 64 8 8

STS-1, VC3 24 24 192 192 24 24

VT1.5, VC-11, VC-3 64 64 N/A N/A 64 64


Chapter 4 Ethernet Over SONET/SDH (EOS)Guidelines to Configure EOS Ports

• Use a 1+1 EOS port protection group to protect Ethernet traffic leaving the Ethernet card. For details, see Chapter 5—“EOS Port Protection,” page 7-65.



Before You Begin

Review the information in this topic before you configure EOS ports on the following cards: NGE, NGE Plus, 10GbE, GbE-10, or EoPDH.

Table 7-14 EOS Port Requirements




Hardware


NGE: GBE4-FE16-TX GBE2T-GBE2F-FE16-TX

NGE Plus: GBE4-FE16-TX / CEPGBE2T-GBE2F-FE16-TX / CEP

Gigabit Ethernet: 10GbEGbE-10

EoPDH: GBE4-FE16-TX-EoPDH GBE2T-GBE2F-FE16-TX-EoPDH




Software







Ethernet cards and interfaces are configured. Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 2—“Configuring Ethernet Equipment,” page 7-9


Chapter 4 Ethernet Over SONET/SDH (EOS)Configure EOS Port Members

Configure EOS Port Members

Configure an EOS member using Service Groups to create a number of SONET/SDH services at one time. See Configure Service Groups, page 7-56. The endpoints for these services can only be NGE, NGE Plus, 10GbE, GbE-10, or EOPDH cards on separate nodes.

Or, use the following procedures to create SONET or SDH services using endpoints in the Ethernet cards:• See Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services,”

page 4-19 to create SONET services.• See Section 4—Creating ADM Services, Chapter 4—“Creating SDH Services,”

page 4-41 to create SDH services.


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Service Groups

Configure Service Groups

Use service groups to create multiple end-to-end SONET or SDH services at one time.

Table 7-15 Configure Service Groups

Step Procedure

1 Click the Service Group tab, then click Add.

2 In the Create Service Group screen, enter the general information for this group of services:• Name: Alphanumeric character string to name the group.• Description: Alphanumeric character string to describe the group of

services.

Figure 7-21 Create Service Group Screen

3 Select the bandwidth of the services from the Concat. Size field.• STS-1• STS-3C• VC3-HO• VC-4

4 Select the type of Protection for this service group. (Planned for future release.) Values are:

Co-route (default): Indicates all members follow the same route.

5 In the Service Count field, enter the number of consecutive services you want to create in the system. This number depends on the value in the Concat. Size field in Step 3.

For NGE and EoPDH cards:• If the value is STS-1 or VC3-HO, enter a number between 1 and 48.• If the value is STS-3C or VC-4, enter a number between 1 and 16.

For 10GbE and GbE-10 cards:• If the value is STS-1 or VC3-HO, enter a number between 1 and 64.• If the value is STS-3C or VC-4, enter a number between 1 and 192.

6 Select the source and destination endpoints of the service. The endpoints can only be NGE, NGE Plus, 10GbE, GbE-10, or EOPDH cards on separate nodes.


Chapter 4 Ethernet Over SONET/SDH (EOS)Configure Service Groups

7 On the Create Services screen, click Advanced to configure more parameters of the service.

Figure 7-22 Service Group Advanced Parameters Dialog Box


b. Click Done to return to the Create Service Groups screen.

8 Click Apply to create the service group and return to the Service Group screen.

9 On the Service Group screen, locate the new service group. Right-click and select Synchronize to synchronize the services and create the services through the network.

10 On the Service Group screen, locate the new service group. Right-click and select Activate.

11 The Configure Service Groups procedure is complete.

Continue to the procedure Creating EOS Ports, page 7-58

Table 7-15 Configure Service Groups (continued)

Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetCreating EOS Ports

Creating EOS Ports

Use this procedure to create and configure EOS ports.

Table 7-16 Creating EOS Ports

Step Procedure

1 Read the information in Before You Begin, page 7-54 before you start this procedure.

2 In Shelf View, click the Ethernet tab, then click Add. The Create EOS tab appears.

3 On the Create EOS tab, configure the parameters for the EOS port.

Figure 7-23 Create EOS Tab

Slot: Select the correct slot number from the drop-down menu.

EOS Port ID: Enter a number to identify this EOS port in the system. (This number appears with the slot number in the Slot/ID field on the Ethernet tab, EOS subtab.)

Description: Enter an alphanumeric character string to identify this EOS port in the EOS port list on the EOS subtab.

Service Group: Select a service group ID number if this EOS port will use EOS services created from a Service Group.

Concatenation Type: Indicates if this EOS port uses contiguous concatenation or virtual concatenation.• Virtual: This EOS port contains multiple endpoints of the same size

creating a virtual concatenation group. • Contiguous: The EOS port contains a single endpoint.


Chapter 4 Ethernet Over SONET/SDH (EOS)Creating EOS Ports

Concatenation Size: Select the bandwidth of the transport paths that are members of this EOS port: • VT1.5 (NGE, NGE Plus, and EoPDH only)• STS-1• STS-3C• VC-11 (NGE, NGE Plus, and EoPDH only)• VC-12 (NGE, NGE Plus, and EoPDH only)• VC3-HO• VC-4

Tagging: Select one of the following tagging parameters: • Port-based: Every packet on this port is considered to belong to the


• Customer-tagged: Every packet on this port is assumed to have a VLAN tag that identifies its service in the customer network. This VLAN tag 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, each identified by a separate customer VLAN ID.


RSTP: Click the check box to enable RSTP (Rapid Spanning Tree Protocol).

Note: If you are setting up Virtual RSTP, you should first set up the Virtual RSTP Bridges (VRBs). See Chapter 9—“Rapid Spanning Tree Protocol,” Configure Virtual RSTP, page 7-115 for more information.

VRB: If you are setting up VRSTP and have already set up your VRBs, click this field and select the VRB number from the drop-down menu for this EOS port. Valid values are 1 through 20; default is 1.

Table 7-16 Creating EOS Ports (continued)

Step Procedure



4 Add the endpoints of the EOS port to the endpoint table.

Figure 7-24 Add Endpoints to the EOS Port


b. Navigate the tree and select the desired endpoint. The endpoint must be in the same slot as the slot identified in parameter Slot.

c. Click Done to close the dialog box and return to the Create EOS tab on the main screen.

d. Type a unique number from 1 through 255 in the Member# column. e. Add extra rows to the endpoint table by clicking the plus sign in the

Add column. Add as many rows as required for this EOS port.f. Repeat Steps a. through e. for each required endpoint.


Step Procedure

4a

4b

4d

4c

4e



5 Configure the attributes of each EOS port member.

Direction: Select the direction the traffic travels on the EOS port member. This parameter must match the direction of the EOS port member SONET/SDH service. • Receive: Unidirectional in the receive direction only• Transmit: Unidirectional in the transmit direction only• Bidirectional: Traffic travels in both directions

Admin State: Select to control the suppression of alarms on the EOS port member.• Unlock (default)• Locked

Alarm Profile: Assign an alarm profile to the EOS port member. Select one of the following values:• useParent (default): The member inherits the alarm profile of the EOS

port. • default: Uses the default alarm profile (of type eos_ctp or

sdh_eos_ctp) for the selected endpoint.

6 Click Advanced to set the advanced attributes of the EOS port.

Alarm Profile: Assign an alarm profile to this EOS port. By default, the alarm profile is of type eos or sdh_eos.

PM Template: Assign a PM template to this EOS port. By default, the PM template is of type eos_pm.

GFP FCS Insert: Indicates whether or not the system inserts GFP Payload FCS (frame check sequence) into each frame sent over this EOS port. Payload FCS should be used only when interoperating with other vendors’ systems that require it. Normally it is not used on Traverse systems.• Enabled: The system adds Payload FCS to each frame.• Disabled (default): The system does not add Payload FCS to any

frame.


Step Procedure




7 Insert Alternate VLAN Ethertype: If this parameter is enabled, this EOS port will use the Alternate VLAN Ethertype value when a VLAN swap or add operation is performed on a packet being sent out this port. 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, it is the outer tag and statements made for service tag apply.

8 In the Queuing Policy parameter, specify how the queues are managed. Select one of the following values: • FIFO (default): First-in, first-out. Select this queuing policy to





FIFO Shaping Rate parameter to shape the traffic being transmitted onto the port.

• FIFO Shaping Rate: If the FIFO Shaping Rate is enabled, enter a number between 1 and 1000 Mbps on NGE cards. For 10GbE and GbE-10 cards, specify a number between 1 and 10,000 Mbps; default for 10GbE is 10,000, default for GbE10 is 1000.


Step Procedure







11 Click Done to close the Advanced Parameters dialog box and return to the main screen.

12 Click Apply to create this EOS port and return to the Ethernet tab, EOS port subtab.

13 The Creating EOS Ports procedure is complete. Continue to any of the following procedures according to your network plan.• Configure EOS port protection. See Chapter 5—“EOS Port

Protection,” page 7-65• Configure EOP ports. See Chapter 6—“Ethernet Over PDH (EOP),”

page 7-71 (Not available on TE-100)• Configure RSTP or Virtual RSTP. See Chapter 9—“Rapid Spanning

Tree Protocol,” page 7-103• Configure LCAS. Chapter 8—“Link Capacity Adjustment Scheme,”

page 7-89


Step Procedure


SECTION 7SECTION 7CONFIGURING ETHERNET

Chapter 5EOS Port Protection

Introduction This chapter contains the following topics:• Example of EOS Port Protection, page 7-66• Guidelines to Configure EOS Port Protection, page 7-67• Before You Begin, page 7-67• Create a 1+1 EOS Port Protection Group, page 7-69

Ethernet Cards

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

Cards Card Types



EoPDH Card GBE4-FE16-TX-EoPDH GBE2T-GBE2F-FE16-TX-EoPDH


Traverse Provisioning Guide, Section 7: Configuring EthernetExample of EOS Port Protection

Example of EOS Port Protection

1+1 EOS port protection protects the Ethernet signal on the customer side of the Traverse by providing a duplicate Ethernet connection for transport. Failure on either Ethernet link does not prevent service.

Figure 7-25 1+1 EOS Port Protection Group

1+1 EOS port protection ensures all the transport (SONET or SDH) paths that are members of an EOS port switch at once whenever there is a protection-switching trigger. Triggers are automatic (defined in terms of the health of the EOS ports’ associated Ethernet ports) and external commands (same as 1+1 APS/MSP protection groups).

1+1 EOS port protection groups interwork with all other supported types of protection switching. However, the system only interworks with 1+1 path protection groups not 1+1 path protection created by the two services model.

Node 1

GBE/FETXSlot 1

.

..

.

..GBE/FETXSlot 2

.

..

.

..

Slot 11

W

OC192/STM64

Slot 13

E

OC192/STM64

Video Codec 1

PWR

OK

WIC0ACT/CH0

ACT/CH1

WIC0ACT/CH0

ACT/CH1

ETHACT

COL

Video Codec 2

OC-192/STM-64UPSR/SNCP

PWR

OK

WIC0ACT/CH0

ACT/CH1

WIC0ACT/CH0

ACT/CH1

ETHACT

COL

1+1 EOS Port Protection GroupProtecting: slot 1-id1Working: slot 2-id 1Unidirectional

TR 00035


Chapter 5 EOS Port ProtectionBefore You Begin

Guidelines to Configure EOS Port Protection

Review the following guidelines before you configure a 1+1 EOS port protection group:• Requirements: Depends on two separate Ethernet cards receiving the same signal. • The system supports up to 20 EOS port protection groups per Ethernet card. That

is, on any card, up to 20 of its EOS ports can simultaneously participate in 20 separate EOS port protection groups.

• An EOS port can be in only one 1+1 EOS port protection group at a time.• Each EOS port must have a provisioned member size of STS-1, STS-3c, VC-3, or

VC-4. • The system supports up to 64 EOS port protection groups per node for NGE cards. • An EOS port protection group contain exactly two EOS ports. The operator

designates one as Working and the other as Protecting.• Use 1+1 EOS port protection only with one Ethernet line service. • The Ethernet line that is using the 1+1 EOS port protection can not have link

integrity enabled. • The switching for an EOS port protection group is always unidirectional.


Before You Begin

Review the information in this topic before you configure EOS port protection on the following Traverse cards: NGE, NGE Plus, EoPDH.

Table 7-17 Link Aggregation Requirements




Hardware


NGE: GBE4-FE16-TX, GBE2T-GBE2F-FE16-TX


EoPDH: GBE4-FE16-TX-EoPDHGBE2T-GBE2F-FE16-TX-EoPDH






Software







EOS ports are correctly configured. Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 4—“Ethernet Over SONET/SDH (EOS),” page 7-49

Table 7-17 Link Aggregation Requirements (continued)



Chapter 5 EOS Port ProtectionCreate a 1+1 EOS Port Protection Group

Create a 1+1 EOS Port Protection Group

Use this procedure to create a 1+1 EOS port protection group.

Table 7-18 Create a 1+1 EOS Port Protection Group

Step Procedure

1 Review the information in Before You Begin, page 7-67 before you start this procedure.

2 In Shelf View, add a 1+1 EOS protection group.

Figure 7-26 Select 1+1 EOS

a. Click the Protection tab to display the Protection Groups screen.b. From the New list, select 1+1 EOS.c. Click Add to display the Create EOS tab.

3 On the 1+1 EOS Protection Group screen, enter the attributes of the protection group.

Figure 7-27 Add 1+1 Protection Group Screen

In the Name field, enter the name of the node (maximum 43 characters). Use alphanumeric characters only. Do not use punctuation or any special characters in this field.


card when the working port has recovered from the original failure condition or the external command is cleared.

• In the WTR Time field, set a time in minutes that the system will wait after a protection switch before switching back to the working port.Enter a number between 1 and 60; default is 5.

3a

3b3c

45

6


Traverse Provisioning Guide, Section 7: Configuring EthernetCreate a 1+1 EOS Port Protection Group

5 Select the working and protecting EOS ports for this protection group.


a. On the Protecting Port row, select the protecting port.b. On the Working Port row, select the working port.

6 Click Create to return to the Protection Groups screen on the Protection tab.



7 The Create a 1+1 EOS Port Protection Group procedure is complete.

Table 7-18 Create a 1+1 EOS Port Protection Group (continued)

Step Procedure

7



Chapter 6Ethernet Over PDH (EOP)

Introduction In a Traverse system, EoPDH is an access technology used to bring Ethernet frames to a Traverse node for switching and forwarding to nodes within the system on a transport network. Most EoPDH applications will use a combination of EOS and EOP ports. The PDH circuits containing Ethernet frames arrive at an EoPDH card where they are extracted from the EoPDH link. The extracted frames are then forwarded within the Traverse network over an EOS link which acts as a network-to-network interface.

The information in this chapter strictly pertains to the Traverse Ethernet over PDH (EoPDH) cards (GBE4-FE16-TX-EoPDH and GBE2T-GBE2F-FE16-TX-EoPDH). It contains the following topics:• Ethernet over PDH (EOP), page 7-71• Virtual Concatenation of PDH Circuits, page 7-72 • Guidelines to Configure EOS and EOP Ports on EOPDH Cards, page 7-73• Before You Begin, page 7-75• Creating EOP Ports, page 7-76• Managing EOP Port Traffic, page 7-82

Ethernet over PDH (EOP)

On EoPDH cards, in addition to SONET or SDH connections, traffic can also travel over PDH connections. However, because they are used for access not transport, EOP ports are more like Ethernet ports than EOS ports. For more information on EOS ports, refer to Chapter 4—“Ethernet Over SONET/SDH (EOS),” page 7-49 in this section.

Physical PDH ports have Administrative and Operational states. EOP port members, like EOS port members, have only an Administrative state.

Creating Ethernet over PDH (EOP) connections requires three components:• EOP ports: On the Traverse system, an EOP port is a port-like abstraction

representing the adaptation point between Ethernet and PDH. This EOP port can be thought of as an Ethernet WAN interface, compared to physical Ethernet ports which are Ethernet LAN interfaces.

• EOS ports: On the Traverse system, an EOS port is a port-like abstraction representing the adaptation point between Ethernet and SONET/SDH.


Traverse Provisioning Guide, Section 7: Configuring EthernetVirtual Concatenation of PDH Circuits

• Transport connections: Create a regular service. For end-to-end services, the endpoints of the service are Ethernet cards (virtual SONET and STM ports on the backplane). For hop-by-hop services, one endpoint is the virtual SONET or STM port on the backplane of the Ethernet card; the second endpoint is a SONET or STM port.

Virtual Concatenation of PDH Circuits

Virtual concatenation (VCAT) of PDH circuits, as defined in ITU-T standard G.7043 “Virtual concatenation of plesiochronous digital hierarchy (PDH) signals,” is nearly identical to virtual concatenation of SONET/SDH circuits. Similar to SONET/SDH virtual concatenation, VCAT on EoPDH cards supports bundling of multiple independent lower-rate channels into a higher rate channel, enabling efficient mapping of encapsulated PDH frames. Unlike SONET/SDH virtual concatenation, however, virtual concatenation on PDH circuits supports more low-order connection termination types with different placements. See Chapter 4—“Ethernet Over SONET/SDH (EOS),” Virtual Concatenation, page 7-51 for information on virtual concatenation on SONET/SDH circuits.

On PDH circuits, four types of EOP port members are available: DS1, DS3, E1, and E3. The following table defines the virtual concatenation requirements for each PDH Member Type:

Table 7-19 PDH Virtual Concatenation Requirements

PDH Member Type

Line Framing Selected Concatenation Type Virtual Concatenation

Allowed Y/N

DS1 (VT1.5) ESF (default) Virtual or Contiguous Yes

SF Contiguous No. Not supported due to smaller frame size.

E1 (VC-12) Multiframe (default) Virtual or Contiguous Yes

Basic Frame Contiguous No

DS3 (STS-1) CBIT (read-only) Virtual or Contiguous Yes

E3 (VC-3) G.832 Virtual or Contiguous Yes


Chapter 6 Ethernet Over PDH (EOP)Guidelines to Configure EOS and EOP Ports on EOPDH Cards

Guidelines to Configure EOS and EOP Ports on EOPDH Cards

These procedures require the EoPDH cards AND the underlying SONET or STM cards to be connected and configured in a transport topology. The guidelines for configuring EOP ports are similar to configuring EOS ports. For information on configuring EOS ports, see Chapter 4—“Ethernet Over SONET/SDH (EOS),” page 7-49.

Each EoPDH card has one virtual OC-48 / STM-16 port called a virtual optical port (VOP). The virtual port is port 0 in the user interface.

EOP Ports. Each EoPDH card supports both EOS and EOP (Ethernet over PDH) ports. The EoPDH card can support 128 EOP, 128 EOS, or any combination of EOP and EOS ports that total 128. For information on EOS ports, see Chapter 4—“Ethernet Over SONET/SDH (EOS),” page 7-49.

EOP ports are virtual ports used to send and receive Ethernet frames. They are similar to EOS ports in that they contain multiple members that are virtually concatenated to form a higher-capacity channel using frame-based GFP to encapsulate the Ethernet frames. Both EOS and EOP ports can also be used as endpoints in Ethernet services, raise alarms, and collect PM data.

EOP Port Members (SONET or SDH Services). Each Ethernet card supports termination functions for either SONET or SDH, but not both. If provisioned for SDH termination, the Ethernet cards can terminate either VC-11 or VC-12, but not both at the same time. However, VC-11 and VC-12 can both coexist with VC-3. The following table describes the termination points and maximum connection termination points for each combination of port type and bandwidth.

Note: On EoPDH cards, low-order connection termination points can reside only in the first 24 STSs or VC-3s of the card’s VOP.

Table 7-20 EOS and EOP Bandwidth and Termination Requirements

Port Type BandwidthSONET(STS)

Termination Points

SDHTermination Points1 Maximum CTPs

EOP DS1 1 through 12 Not supported 336

E1 Not supported 1 through 12 252

EOS VC-11 Not applicable 1 through 24 672

VC-12 Not applicable 1 through 24 504

VT1.5 1 through 24 Not applicable 672

EOP DS3 1 through 48 Not supported 48

E3 Not supported 1 through 48 48

EOS STS 1 through 48 1 through 48 48

VC3 Not applicable 1 through 48 48

VC4 Not applicable 1 through 16 16

1 All SDH Termination Points are VC3 except EOS VC4 which is AU4.


Traverse Provisioning Guide, Section 7: Configuring EthernetGuidelines to Configure EOS and EOP Ports on EOPDH Cards

On the EoPDH card’s OC-48 VOP, operators can provision the VT1.5 connection termination points in STS 1 through 12. Within those 12 STS’s, the operator can provision up to a total of 336 VT1.5 connection termination points.

When the EoPDH virtual port is in SDH mode, and the LO Mapping is VC-11, the operator can provision VC-11 connection termination points only in the 12 VC-3s contained in the first 12 AU-3s in the card’s STM-16 VOP. Within those 12 VC-3s, the operator can provision up to a total of 672 VC-11 connection termination points.

When the EoPDH virtual port is in SDH mode, and the LO Mapping is VC-12, the operator can provision VC-12 connection termination points only in the 12 VC-3s contained in the first 12 AU-3s in the card’s STM-16 VOP. Within those 12 VC-3s, the operator can provision up to a total of 504 VC-11 connection termination points.

The remaining SONET bandwidth (STS / VTG / VT) and SDH bandwidth (AUG / VC-3 / TUG-2 / VC) are available for provisioning high-order connection termination points, as long as they do not exceed the virtual port limits.

The SONET and SDH services on EoPDH cards are bidirectional only.

On EoPDH cards and ports, operators can cross-connect between the following service types when the Ethernet card VOP is the source, the destination, or the source and destination:• Ethernet card VOP • HO (STS-3c, STS-1, VC-4, VC-3) or LO (VT1.5, VC-12, VC-11) CTPs on OC-N /

STM-N cards, DS3 / EC-1 Transmux cards (EC-1 ports only), or Ethernet card VOP.

• VC12 service to E1 inside DS3 inside VC3 • Optical Transmux

For additional information on the Ethernet services available on EoPDH cards, see Section 4—Creating ADM Services, Chapter 3—“Creating SONET Services” and Chapter 4—“Creating SDH Services.”

It is possible to add or remove endpoints dynamically to an EOP port.

Any EOP port being used in an activated Ethernet service cannot be deleted.

Virtual Concatenation. All members of a virtual EOP port must be of the same bandwidth. The EOP PDH Member Type defines the EOP port members as DS1 or DS3 for SONET, and E1 or E3 for SDH. DS1 and E1 PDH Member Types can transmit and receive up to 16 source members, while DS3 and E3 PDH Member Types can transmit and receive up to 8 source members.

The system supports a maximum differential delay of 128 milliseconds on EoPDH cards.

The Traverse supports asymmetric virtual concatenated groups. That is, the system supports a different number of SONET or SDH services in the transmit direction than in the receive direction. If a virtually concatenated group on an EoPDH card is provisioned LCAS Enabled at the transmit end but the receive end is not using LCAS, the system will produce a LCAS Inactive alarm as specified in ITU-T standard G.806, sections 10.1.1.1 and 10.1.1.2.

The system supports a mix of protected and unprotected members in the same virtually concatenated group.


Chapter 6 Ethernet Over PDH (EOP)Before You Begin

An operator can dynamically add or remove protection for an EOP port member.

Before You Begin

Review the information in this topic before you configure EOP ports on EoPDH cards.

Table 7-21 EOP Port Requirements




Hardware


EoPDH: • GBE4-FE16-TX-EoPDH• GBE2T-GBE2F-FE16-TX-EoPDH




Software









Traverse Provisioning Guide, Section 7: Configuring EthernetCreating EOP Ports

Creating EOP Ports

Use this procedure to create and configure EOP ports.

Table 7-22 Creating EOP Ports

Step Procedure

1 Read the information in Before You Begin, page 7-54 before you start this procedure.

2 In Shelf View, select the EoPDH card on which the port is being created, then click the Config tab. The Card Configuration screen displays.

3 Set the type of LO Mapping for the card. The valid values are:• for SONET: VT15/VC11 • for SDH:

– VT2/VC12 (default)– VT15/VC11

Click Apply.

4 Next, click the Ethernet tab, click the EOP subtab, then click Add. The Create EOP tab appears.

5 On the Create EOP tab, configure the parameters for the EOP port.

Figure 7-30 Create EOP Tab

Slot: Select the correct slot number from the drop-down menu.

EOP Port ID: Enter a number from 1 to 128 to identify this EOP port in the system. (This number displays with the slot number in the Slot/ID field on the Ethernet tab, EOP subtab.)

Description: Enter an alphanumeric character string to identify this EOP port in the EOP port list on the EOP subtab.


Chapter 6 Ethernet Over PDH (EOP)Creating EOP Ports

Tagging: Select one of the following tagging parameters: • Port-based: Every packet on this port is considered to belong to the


• Customer-tagged: Every packet on this port is assumed to have a VLAN tag that identifies its service in the customer network. This VLAN tag 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, each identified by a separate customer VLAN ID.

Note: If you are creating a multipoint ECC service, the EOP port must be Customer-tagged.


Concatenation Type: Specify if this EOP port uses contiguous concatenation or virtual concatenation.

– Virtual (default): This EOP port contains multiple endpoints of the same size creating a virtual concatenation group.

– Contiguous: The EOP port contains a single endpoint.

PDH Member Type: Select the bandwidth of the transport paths that are members of this EOP port. Valid values for SONET are:

– DS1 (SONET default)– DS3Valid values for SDH are:– E1: Default if VC-12 LO Mapping is selected– E3: Default if VC-11 LO Mapping is selected

Line Framing: Indicates the timing output of the selected PDH Member Type based on the selected Concatenation Type. Valid values are:

– ESF (Default for PDH Member Type DS1): Extended super frame format.

– CBIT (Default for PDH Member Type DS3): 28 DS-1 signals are multiplexed into the DS3 signal, with the C-bit used as control bit.

Table 7-22 Creating EOP Ports (continued)

Step Procedure



– Multiframe (Default for PDH Member Type E1): When selected, the timing interface detects and generates CRC-4 multi-frame format per ITU-T Rec G.706/4.2.

– G.832 (Default for PDH Member Type E3): Indicates the ITU-T G.703 industry standard.

AIS Format: Displays the Alarm Indication Signal format. Valid values are:

– ONES– NAS

Member PDH PM Template: Assign a PDH PM template to this EOP port. The template must match the PDH Member Type selected (DS1, DS3, E1, or E3).

6 Add the endpoints of the EOP port to the endpoint table.

Figure 7-31 Add Endpoints to the EOP Port

a. Enter a Member# for this EOP member. DS1 and E1 PDH Member Types can have up to 16 members; DS3 or E1 PDH Member Types can have up to 8 members.

b. Click the first row in the Endpoint column to display the Choose an Endpoint dialog box.

c. Navigate the tree and select the desired endpoint. The endpoint must be in the same slot as the slot identified in the Slot parameter.

Note: Of the 24 available endpoints, the first 12 endpoints can be used for either EOS or EOP ports. The second 12 endpoints can be used only for EOS ports.


Step Procedure

4a

4b

4d

4c

4e



d. Click Done to close the dialog box and return to the Create EOP tab on the main screen.

e. Type a unique number from 1 through 255 in the Member# column. This member sequence corresponds to the VCAT member sequence when LCAS is disabled. The member sequence must be the same at both ends of the EOP transport link.

f. Add extra rows to the endpoint table by clicking the plus sign in the Add column. Add as many rows as required for this EOP port.

g. Repeat Steps b through f for each required endpoint.

7 Configure the attributes of each EOP port member.

Direction: Select the direction the traffic travels on the EOP port member. This parameter must match the direction of the EOP port member SONET/SDH service. • Receive: Unidirectional in the receive direction only• Transmit: Unidirectional in the transmit direction only• Bidirectional: Traffic travels in both directions

Admin State: Select Lock to suppress the collection of alarm and PM data on the EOP port member. To place an EOP port into any Loopback mode, the Admin State must be Unlock.• Unlock (default)• Lock

Alarm Profile: Assign an alarm profile to the EOP port member. Select one of the following values:• useParent (default): The member inherits the alarm profile of the EOP

port. • default: Uses the default alarm profile (of type eop_ctp) for the

selected endpoint.

Loopback: Click the row in the Loopback column to select the type of loopback function for this EOP port. Valid values are:• Clear (default) • Facility • Far-End


Step Procedure



8 Click the Advanced button to set the advanced attributes of the EOP port.

Figure 7-32 EOP Advanced Parameters Dialog Box

Alarm Profile: Assign an alarm profile to this EOP port. By default, the alarm profile is of type eop or eop_ctp.

PM Template: Assign a PM template to this EOP port. By default, the PM template is of type eop_pm.

GFP FCS insert: Indicates whether or not the system inserts GFP Payload FCS (frame check sequence) into each frame sent over this EOP 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.

9 Insert Alternate VLAN Ethertype: If this parameter is enabled, this EOP port will use the Alternate VLAN Ethertype value when a VLAN swap or add operation is performed on a packet being sent out this port. 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 EoPDH cards, the alternate value is used in all VLAN tags in a packet.


Step Procedure



10 In the Queuing Policy parameter, specify how the queues are managed.

Note: Transmission times on EOP ports are slower than Ethernet links. EOP links could become severely congested if traffic on the Ethernet links overrun the port. For recommended set up information, see Managing EOP Port Traffic, page 7-82.

Select one of the following values: • FIFO (default): First-in, first-out. Select this queuing policy to




11 If FIFO is the value in the Queuing Priority parameter, configure the following parameters:• FIFO Shape: Select Enabled to specify if the system will use the

number in the FIFO Shaping Rate parameter to shape the traffic being transmitted onto the port. Default is Disabled.

• FIFO Shaping Rate: If the FIFO Shaping parameter is enabled, enter a number between 1 and 1000 Mbps on EoPDH cards.


Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetManaging EOP Port Traffic

Managing EOP Port Traffic

Transmission times on EOP ports are much slower than other types of Ethernet links. This could cause EOP links to easily become severely congested if traffic on the other types Ethernet links increases significantly.

The default port and service values on the Traverse system cause all traffic to compete for the same bandwidth. The defaults cause the outbound EOP traffic (from the Traverse network to the EOP link) to congest the egress queues of the EOP link. (Drops in traffic will appear on a service PM report in the TX RED DISCARDS counter.)

If low bandwidth, VOIP, or in-band management (i.e., multipoint-ECC) traffic is to occur on an EOP link that is vulnerable to congestion, Force10 recommends applying non-default traffic management to avoid unacceptable loss rates during congestion.






13 Click Done to close the Advanced Parameters dialog box and return to the main screen.

14 Click Apply to create this EOP port and return to the Ethernet tab, EOP subtab.

15 The Creating EOP Ports procedure is complete. Continue to any of the following procedures according to your network plan:• Configure EOS port protection. See Chapter 5—“EOS Port

Protection,” page 7-65• Configure LCAS. Chapter 8—“Link Capacity Adjustment Scheme,”

page 7-89


Step Procedure


Chapter 6 Ethernet Over PDH (EOP)Managing EOP Port Traffic

To manage traffic congestion on the EOP port congestion, Force10 recommends using the following steps:• Change the port per hop behavior to WFQ or PRIORITY. The default of FIFO only

supports the default service COS of 1.• Classify Ethernet services that carry loss sensitive traffic (such as VOIP) as COS 1

or 2. In band management traffic is fixed at COS 1.• Classify all other Ethernet services at lower COS levels, such as COS 3 or 4.


Traverse Provisioning Guide, Section 7: Configuring EthernetManaging EOP Port Traffic




Chapter 7EoPDH Services and Applications

Introduction This chapter contains information on unique features of the EoPDH cards in the following topics:• Ethernet over PDH Cards, page 7-85• EoPDH Applications, page 7-85• Configuring CPE to Ethernet Information Flow, page 7-86• Configuring CPE to EoPDH Services Procedure, page 7-87• Managing Traffic on EOP Ports, page 7-88

Ethernet over PDH Cards

EoPDH Applications

EoPDH cards can be configured to handle traffic from subtended CPE devices to a Traverse node for switching and forwarding over the system. As such, the EoPDH is an access technology, not a transport technology. Frames from the CPE devices arrive at the Traverse on bonded PDH links, such as DS1s. Bonded PDH links are set up between the DS1s and EOP ports on EoPDH cards. From the EOP ports, the traffic is forwarded over the system using Traverse Ethernet services.

Multiple CPEs can be managed in groups from a single EoPDH card. Each group is a single IP subnet; each subnet is supported by an IP interface on the Traverse. The IP interface uses an Ethernet control channel (ECC) and a multiport aggregate bridge service on the EoPDH card to transport the IP packets between the CPE devices and the node. The ECC is an inter-node control channel that runs over Ethernet links and operates as a DCC.

The IP interface (called an ECC Interface or “ECCI”) is a numbered IP interface with one or more member ports. It must be configured on the Traverse.

Important: The information in this section strictly pertains to Ethernet over PDH (EoPDH) cards:

Cards Card Types


Traverse Provisioning Guide, Section 7: Configuring EthernetConfiguring CPE to Ethernet Information Flow


Operators can configure a multi-port ECC service which uses a specific VLAN ID and IP address to allow in-band management of the IP traffic. Each EoPDH card can support 4 multipoint-ECC services and each node can support 16 multipoint ECC services.

For information on multipoint ECC services, see Chapter 10—“Ethernet Services,” Ethernet Services Definition, page 7-119.

Configuring CPE to Ethernet Information Flow

Use this flowchart as a guideline to configure the flow of IP packets from a CPE device to Ethernet services via an EoPDH card in a Traverse system.

Figure 7-33 Provisioning IP Packets from CPE Devices to Traverse

Configure Ethernet traffic managementfor EOP ports

End

TR-00055

Create EOP portsand activate EOP members

(EoPDH cards only)


connected

Optionally, configure optical andelectrical equipment

(card and port parameters)

Create Ethernet MultipointECC services

Chapter 7 EoPDH Services and ApplicationsConfiguring CPE to EoPDH Services Procedure


Configuring CPE to EoPDH Services Procedure

Use this procedure as a guideline to configure CPE devices to Ethernet services on a Traverse system.

Table 7-23 Configuring CPE Devices to Ethernet Services








3 Configure SONET / SDH path VT-MUX services with endpoints on Ethernet cards according to net-work plan

Traverse Provisioning Guide • Section 4—Creating ADM Services, Chapter

3—“Creating SONET Services,” page 4-19• Section 4—Creating ADM Services, Chapter

4—“Creating SDH Services,” page 4-41

4 Configure Ethernet services Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 10—“Ethernet Services,” page 7-119





7 Optionally, configure EOP fea-tures (EoPDH cards only)


8 Configure Ethernet traffic manage-ment for EOP ports

Traverse Provisioning Guide, Section 7—Configuring Ethernet, Chapter 11—“Ethernet Traffic Management,” , page 7-147

Traverse Provisioning Guide, Section 7: Configuring EthernetManaging Traffic on EOP Ports


Managing Traffic on EOP Ports

Transmission times on EOP ports are slower than Ethernet links. This could cause EOP links to become severely congested if traffic on the Ethernet links overruns the port.

If low bandwidth, VOIP, or in band management is used on an EOP link, the port and services defaults will cause all traffic to compete for the same bandwidth. This, in turn, will cause the outbound EOP traffic (from the Traverse network to the EOP link) to congest the egress queues of the EOP link. (Drops in traffic will appear on a service PM report in the TX RED DISCARDS counter.)


supports the default service COS of 1.• Classify time critical traffic (such as VOIP) as COS 1 or 2. In band management

traffic is fixed at COS 1.• Classify all other traffic at lower COS levels such as 3 or 4.


Chapter 8Link Capacity Adjustment Scheme

Introduction Link capacity adjustment scheme (LCAS) is a protocol defined in ITU G.7042, “Link capacity adjustment scheme (LCAS) for virtual concatenated signals.” Nodes at the ends of a virtually concatenated group (VCG) use this protocol to manage the group of concatenated SONET or SDH services. On EoPDH cards, this also applies to PDH services. Specifically, a system can adjust the group membership in response to autonomic events (member fail or recover) or operator requests (manually add or remove member). LCAS signaling between peers is carried in the SONET/SDH/PDH path overhead as outlined in G.7042 and G.707.

See the following topics for a complete description of LCAS capabilities on the Traverse system.• LCAS Operation, page 7-90• LCAS and Protection Groups, page 7-93• Asymmetric LCAS, page 7-93• LCAS Interworking, page 7-93• Before You Begin, page 7-95• Guidelines to Configure LCAS, page 7-96• Configure LCAS, page 7-97

Ethernet Cards


Cards Card Types







Traverse Provisioning Guide, Section 7: Configuring EthernetLCAS Operation

LCAS Operation

On the Traverse system, LCAS operates on the members of an EOS or EOP port that are in a virtual concatenation group (VCG). The system can adjust the capacity of the VCG membership in response to autonomic events (member fail or recover) or operator requests (manually add or delete).

The Traverse considers a member (unprotected or protected) to be failed if there is a critical alarm associated with that member. The Traverse considers a failed member to have recovered when the critical alarm has cleared.

The system generates an LCAS event whenever a member fails or recovers. Also, if a member is added or deleted to the VCG, the event identifies the EOS or EOP port, the event type (failure or recovery), and the number of currently active members on the port.

On NGE and NGE Plus cards, LCAS-enabled EOS ports must face LCAS-enabled EOS ports on the far-end. If an LCAS-enabled EOS port on an NGE card faces a non-LCAS EOS port on the far end, unexpected behavior may occur.

Due to differences between SONET/SDH conditions and PDH conditions, some differences exist in how LCAS handles failed/deleted members on EOP ports. These differences are discussed separately below.

Failed or Deleted Members on EOS Ports. If a member of an LCAS-enabled VCG fails or is manually deleted, the system automatically removes the member from the VCG. However, the VGG continues to transfer data on the remaining members of the group. There will be a short period during which data being transmitted or received on the VCG is discarded.

When a member fails and the LCAS {LO | HO} Holdoff Timer is enabled on the EOS port, the system does not remove the member until the timer expires. If the SONET/SDH protection mechanism restores the member path, then the period during which data is discarded can be minimized. If the protection mechanism is not successful in restoring the member path, then the period during which data is discarded will be extended while LCAS removes the member from the group.

The system raises a path alarm when a member fails, identifying both the failure and the slot-port-path. The system clears the path alarm when the member recovers.

If LCAS has removed failed members, as long as at least one member remains Ethernet data continues to flow on any activated services that are using the VCG. However, the remaining bandwidth may be insufficient to satisfy the service bandwidth needs.

The system raises a total loss of capacity alarms (TCLT, TCLR) for the VCG as well as path alarms for the individual members when there are no members left in the group. The alarms clear when at least one member returns to health and is added back to the operating VCG. The system also generates partial loss of capacity alarms (PLCT, PLCR) depending on the provisioned thresholds.

If an operator removes the only member from an LCAS-enabled EOS port, the port will fail and the system will generate a “No Provisioned Members” alarm.

Restored or Added Members on EOS ports. When a previously failed member recovers, the system automatically uses LCAS to add the member to the VCG. No data drops when the member is added into the VCG. However, data is lost when an operator manually adds or removes another member to the group.


Chapter 8 Link Capacity Adjustment SchemeLCAS Operation

If the LCAS {LO | HO} WTR timer is enabled on the EOS port, the system does not restore a failed member until the timer expires.

Failed or Deleted Members on EOP Ports. If an EOP member of an LCAS-enabled VCG fails due to an LOF, AIS, or LOM alarm, the system automatically removes the failed member from the VCAT group while the fault is present.

If an active EOP port member is in an IDLE fault condition, the member stays in the group, however, the system is unable to recover incoming frames resulting in a GFP fault.

Removing an LCAS on a PDH member occurs even if the administrative state of the member has been locked.

EOP port members provide a Loopback option. If an EOP port member is provisioned with Facility Loopback, the system cannot send a source signal on the looped-back member. The system removes the member from the VCAT group even if the member has been locked.

EOS Port Thresholds. To receive a loss of capacity alarm for an EOS port, the operator can set the threshold limits for the PLCR Threshold (Partial Loss of Capacity, Receive) and PLCT Threshold (Partial Loss of Capacity, Transmit) fields on the Advanced Parameters tab. The thresholds are based on ITU-T standard G.806. If set to zero (the default), the system generates a total loss of capacity (TLCR or TLCT) alarm. The following examples show how these thresholds can be used:

Example 1:

An LCAS-enabled EOS port in your system is configured on which you expect to send and receive up to 1 Gbps of Ethernet data. It is provisioned as an STS-1-21v. In order to carry a gigabit, every one of those 21 members must be up. If some (but not all) of the members go down, the EOS port is still carrying traffic but at a reduced capacity that does not meet your performance goals. In this example, you would set the PLCT and PLCR Thresholds to 21. This setting will cause a PLCT or PLCR alarm that would notify the operator if the number of correctly-operating members ever falls below 21. If the number ever goes to zero, the Traverse system sends a TLCT or TLCR (Total Loss of Capacity, Transmit/Receive) alarm instead of a PLCT/PLCR alarm.

Example 2:

An LCAS-enabled EOS port in your system is configured on which you expect to send and receive up to 220 Mbps of Ethernet data. For that amount of traffic, 5 STSs are needed. You decide to provision the EOS port with 10 members (STS-1-10v), using strict routing to send 5 members on one route through the network and 5 members on a different route. Any single point of failure in your network will only take down 5 members, leaving you with a sufficient number to carry the required 220 Mbps of traffic. In this example, you would set the PLCT and PLCR Thresholds to 5. If the number of correctly-operating members falls below 10 but is still at least 5, your traffic is okay and an alarm is not generated. However, if the number of correctly-operating members ever falls below 5, the system will fall below your required capacity and generate a PLCR or PLCT alarm. Note that when all 10 members are up, you are actually able to send well over the required 220 Mbps of Ethernet traffic. Anything above 220 Mbps is “extra traffic” that you would be willing to lose during a network fault.


Traverse Provisioning Guide, Section 7: Configuring EthernetLCAS Operation


Chapter 8 Link Capacity Adjustment SchemeLCAS Interworking

LCAS and Protection Groups

Members of a VCG can be part of a protection group or 1+1 path protected. An unprotected member has a single transport path. A protected member has two transport paths that operate as a path protection group.

When a member is protected, failure of one path will not cause a critical alarm; failure of both paths will. When both paths are failed, the recovery of one path removes the critical alarm.

The LCAS {LO | HO} Holdoff Timer should always be enabled when the VCG members are protected and always be disabled when VCG members are unprotected.

Asymmetric LCAS

Asymmetric LCAS arises when an LCAS-enabled VCG is configured with different bandwidth in each direction. However, there must be at least one path in each direction for LCAS to work. For example, you can configure three uni-directional paths from Node1 to Node2 using STS1, STS2, STS3, and one uni-directional path from Node2 to Node1 using STS10.

The Traverse system correctly transmits and receives Ethernet data when some (but not all) of the members of the VCG are uni-directional paths.

In addition, the Traverse system correctly transmits and receives Ethernet data when some (but not all) of the members of the VCG are bi-directional paths that have failed in only one direction.

LCAS Interworking

When two nodes use virtual concatenation for a network connection, it is possible that one side is configured to use LCAS on the connection and the other side is not (or does not support LCAS). That is, when a node is using LCAS it sends LCAS control messages. If a Traverse node does not receive any LCAS control messages, it assumes that the peer is not using LCAS.


Traverse Provisioning Guide, Section 7: Configuring EthernetLCAS Interworking

This table describes system behavior in interworking scenarios.

Table 7-24 LCAS Interworking and System Behavior

Traverse Peer Node System Behavior

Disabled Disabled If a member of a group fails, the entire group stops carrying traffic.

The system raises the total loss of capacity (TLCT and TCLR) alarms for the EOS port in addition to a SONET/SDH path alarm for the individual member.

The alarms clear when all members are restored and the EOS port starts to carry traffic again.

Enabled Disabled On NGE, 10GbE, and GbE-10 cards:• No traffic passes and the system raises a No

Remote LCAS alarm.• Traffic passes in a non-LCAS mode and raises an

LCAS_Inactive alarm.

On EoPDH cards:• Traffic passes in a non-LCAS mode and raises an

LCAS_Inactive alarm.

Disabled Enabled No traffic passes. The system raises the TLCT and TCLR alarms.

Enabled Enabled If a member of a group fails, the group continues to operate at reduced capacity.

The system removes the failed member from the group until it is able to carry traffic again.

When the member is restored, the system automatically adds it to the group again and increases the capacity.


Chapter 8 Link Capacity Adjustment SchemeBefore You Begin

Before You Begin

Review the information in this topic before you configure the LCAS on the following cards: NGE, NGE Plus, 10GbE, GbE-10, or EOPDH.

Table 7-25 LCAS Requirements




Hardware


NGE: • GBE4-FE16-TX • GBE2T-GBE2F-FE16-TX

NGE Plus: • GBE4-FE16-TX / CEP• GBE2T-GBE2F-FE16-TX / CEP

Gigabit Ethernet:• 10GbE• GBE-10





Software





Traverse Provisioning Guide, Section 3—Creating Protection Groups, Chapter 4—“Creating Equip-ment Protection Groups,” page 3-21.



Traverse Provisioning Guide, Section 7: Configuring EthernetGuidelines to Configure LCAS

Guidelines to Configure LCAS

The Concatenation Type parameter of the EOS or EOP port must be Virtual. See Chapter 4—“Ethernet Over SONET/SDH (EOS),” page 7-49 for detailed information on EOS ports. See Chapter 6—“Ethernet Over PDH (EOP),” page 7-71 for information on EOP ports.

Guidelines to Removing LCAS EOS Links

When removing a member from an LCAS EOS link on an NGE card, you must remove the member on both sides of the EOS link before attempting to re-add the same member to that LCAS EOS link. Failure to delete the member from both sides of the link will result in an error message when an attempt is made to re-add the same member.

Before removing an LCAS-enabled EOS port that has members using hop-by-hop SONET/SDH services terminating at an NGE card on either end of the EOS link, you must remove the member on both sides of the EOS link. This prevents another member of the EOS port from accidentally being removed by LCAS.

Removing an LCAS-enabled EOS port from a 10GbE, GbE-10, or EoPDH card requires terminating services on only one end of the link. To remove a member from an LCAS EOP link on an EoPDH card also requires terminating services on only one end of the link.

If another member of the EOS port is accidentally removed by LCAS, users can repair the error by either reactivating the service, removing the remote EOS member, or re-adding the local EOS member.


Chapter 8 Link Capacity Adjustment SchemeConfigure LCAS

Configure LCAS

Use this procedure to configure LCAS on an EOS or EOP port.

Note: EOP ports are only available on EOPDH cards.

Table 7-26 Configure LCAS

Step Procedure

1 In Shelf View, click an Ethernet card, then click the Config tab.

Figure 7-34 Ethernet Card, Configuration Tab

2 Configure the LCAS timers for EOS ports on this NGE, 10GbE, GbE-10 or EoPDH card. Configure the LCAS timers for EOP ports on this EoPDH card.

When LCAS detects that an Active EOS or EOP port member has failed, it will wait for a period defined by the hold-off timer parameters before removing that member from its fragmentation / reassembly processes (declares it “not Active”). • LCAS LO Holdoff (100 ms) (NGE, NGE Plus, and EoPDH 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; default is 1 (100 milliseconds).

• LCAS HO Holdoff (100 ms): The time in milliseconds LCAS waits before removing a member from the HO VCAT groups on the card. Enter a value between 0 to 10 seconds, in increments of 100 milliseconds; default is 1 (100 milliseconds).

2 3


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure LCAS

3 Configure the LCAS wait-to-restore times for the EOS or EOP ports on this card (Traverse only).

When LCAS detects that a member has recovered from a failure, it will wait for a period defined by the Wait-to-Restore (WTR) timer before it includes that member back in its fragmentation / reassembly processes (declares it “Active”).• LCAS LO WTR (min) (NGE, NGE Plus, and EoPDH 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.

4 In Shelf View, edit the EOS or EOP port to enable LCAS.

Figure 7-35 EOS List on EOS Subtab

a. Click the Ethernet tab.b. Click the EOS or EOP subtab.c. Select the correct EOS or EOP port from the EOS or EOP port list.d. Click Edit to edit the EOS or EOP port configuration parameters.

To enable LCAS on an EOS port, go to Step 5.

To enable LCAS on an EOP port, go to Step 6.

Table 7-26 Configure LCAS (continued)

Step Procedure

4d

4a4b

4c



5 On the Edit EOS tab, click Advanced to display the EOS Port Advanced Parameters dialog box.

Figure 7-36 Edit EOS Tab

The EOS Port Advanced Parameters dialog box displays.

Figure 7-37 EOS Advanced Parameters Dialog Box


Step Procedure

5



6 On the Edit EOP tab, click Advanced to display the EOP Port Advanced Parameters dialog box.

Figure 7-38 Edit EOP Tab

The EOP Port Advanced Parameters dialog box displays.

Figure 7-39 EOP Advanced Parameters Dialog Box


Step Procedure

7



7 Find and configure the following LCAS parameters for this EOS or EOP port:

LCAS: Enables or disables LCAS operations for this EOS or EOP port.• Select (default): Select the checkbox to enable LCAS to manage VCG

membership on this port. The system can remove any failed members from this service and continue to use this EOS or EOP port at a reduced capacity.

• Unselect (clear the checkbox): VCG membership is statically configured. The system stops carrying any traffic if a member fails or is removed from the VCG.

Apply LCAS WTR (Traverse only): Select the checkbox to apply the LCAS wait-to-restore value to this port.• Select: Use the value specified in the LCAS {LO | HO} WTR timer

(Step 3).• Unselect (default): Do not use the wait-to-restore value.

Apply LCAS Hold Off:• Select: Use the value specified in the LCAS {LO | HO} Holdoff

(100ms) timer (Step 2).• Unselect (default)

PLCT Threshold: Partial Loss of Capacity, Transmit (PLCT) Threshold. Indicates the number of provisioned EOS or EOP port source (transmit) members that should be operating correctly in order for the EOS or EOP port to carry its expected throughput. Whenever the number of correctly-operating source members falls below this threshold, the system will raise a PLCT alarm on the EOS or EOP port. Used only when the EOS or EOP port has LCAS enabled and has at least one provisioned member. Enter a number between 0 and 64 for NGE and EoPDH cards or 192 for 10GbE and GbE-10 cards. The default is 0, which means that the PLCT alarm will not be raised on this EOS or EOP port.

PLCR Threshold: Partial Loss of Capacity, Receive (PLCR) Threshold. Indicates the number of provisioned EOS or EOP port source (receive) members that should be operating correctly in order for the EOS or EOP port to carry its expected throughput. Whenever the number of correctly-operating source members falls below this threshold, the system will raise a PLCR alarm on the EOS or EOP port. Used only when the EOS or EOP port has LCAS enabled and has at least one provisioned member. Enter a number between 0 and 64 for NGE and EoPDH cards or 192 for 10GbE and GbE-10 cards. The default is 0, which means that the PLCT alarm will not be raised on this EOS or EOP port.

LCAS Compatibility Mode: Enable (select) this parameter only if this EOS or EOP 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


Step Procedure


members. The system adds the removed member to the end of the VCG sequence and restores the member when the path clears.


8 Repeat Steps 1 through 7 at the other end of the transport link.

9 The Configure LCAS procedure is complete.


Step Procedure



Chapter 9Rapid Spanning Tree Protocol

Introduction This chapter contains the following topics:• What is RSTP?, page 7-104• Supported RSTP Topologies, page 7-105• RSTP Bridge Management, page 7-106• RSTP Port Management, page 7-106• Guidelines to Configure RSTP, page 7-107• Virtual RSTP, page 7-109• Before You Begin, page 7-110• Configure RSTP on an EOS Port, page 7-111• View RSTP Port Status, page 7-113• Configure Virtual RSTP, page 7-115

Ethernet Cards


Cards Card Types







Traverse Provisioning Guide, Section 7: Configuring EthernetWhat is RSTP?

What is RSTP? Spanning Tree Protocol (STP), defined in the IEEE 802.1D standard, is a widely used technique for eliminating loops and providing path redundancy in a Layer 2 packet-switched network. Fundamentally, STP provides an algorithm that enables a switch to identify the most efficient data transmission path to use when faced with multiple paths. In the event that the best path fails, the algorithm recalculates and finds the next most efficient path.

Although effective, the protocol faces one significant drawback that limits its applicability in networks carrying delay-sensitive voice and video traffic: STP has lengthy fail-over and recovery times. Depending upon the complexity of the network topology, STP can take as long as 30 to 60 seconds to detect the change and reconverge after a link failure.

Rapid Reconfiguration of Spanning Tree (RSTP - IEEE 802.1w) is an amendment to the original IEEE 802.1D standard and specifically addresses these limitations for applications in carrier-class networks requiring high levels of resiliency and availability. RSTP reduces the time it takes to reconfigure and restore services after a link failure to sub-second levels, while retaining compatibility with existing STP equipment.

RSTP is a transport technology based on a distributed algorithm that selects a single switch in the network topology to act as the root of the spanning tree. The algorithm assigns port roles to individual ports on each switch. Port roles determine whether the port is to be part of the active topology connecting the bridge or switch to the root bridge (a root port), or connecting a LAN through the switch to the root bridge (a designated port).

Regardless of their roles, ports can serve as alternate or redundant ports that provide connectivity in the event of a failure. For example, when bridges, switches, bridge ports, or entire LANs fail or disappear.


Chapter 9 Rapid Spanning Tree ProtocolSupported RSTP Topologies

Supported RSTP Topologies

In Traverse Ethernet applications, enable RSTP among Traverse nodes that participate in bridge services to ensure that the Ethernet topology used to forward packets among the nodes is loop free. The Traverse supports both ring and mesh RSTP topologies.

This diagram illustrates how RSTP might create a spanning tree out of an Ethernet ring. In this example, each Ethernet card (module) is in a separate Traverse node.

The lines between cards represent the point-to-point links that connect the RSTP bridges. These links are SONET/SDH connections that can be either contiguous concatenation paths or virtual concatenation groups. The dashed lines represent customer Ethernet ports.

Figure 7-40 Supported RSTP Topology

IEEE 802.1w defines an RSTP port to have one of the following roles:• Root (R) ports forward Ethernet frames. The system has decided to use this port to

reach the Root Bridge.• Designated (D) ports also forward Ethernet frames. • Alternate (A) ports are blocked but can quickly become forwarding ports when the

topology is reconfigured. In this diagram, one of the links is blocked (heavy line) at one node. The node that has blocked the link does not send or receive any packets on that link. This blockage prevents packets from looping around the ring.

• Edge (E) ports are those that have no further bridges downstream. RSTP does not run on these ports.

ETH

ETH

ETH

ETH

R: Root PortD: Designated portA: Alternate portE: Edge portRoot: Root Bridge of network

R

D

D

Root

D

R

DR D

R DD

RD

R

R

A

EE

ETH

ETH

E

E

E

E

E

E

ETH ETH


Traverse Provisioning Guide, Section 7: Configuring EthernetRSTP Bridge Management

RSTP Bridge Management

An RSTP bridge is a network element that carries out Layer 2 Ethernet processing (maintaining forwarding tables, making forwarding decisions, and flooding packets). On the Traverse system, an RSTP bridge is represented by the Ethernet card itself.

The Traverse system has one RSTP bridge per Ethernet card. The RSTP bridge attributes are viewable on the Config tab of the Ethernet card.

Note: With Release TR2.1, up to 20 virtual copies of RSTP (V-RSTP) can be run on the same Ethernet card. For more information, see Virtual RSTP, page 7-109.• RSTP Bridge ID (Read-only): An identifier for this card used in the RSTP

protocol. Displayed in the following hexidecimal format: <BridgePriority>000-<MAC address>. Example: 8000-1b2000c144d8. When two cards are in a 1:1 equipment protection group, each card has a different RSTP Bridge ID, even though only one of the cards is included in the spanning tree topology at any time.

• RSTP Bridge Priority: Enter an integer between 0 and 15; default is 8. The bridge card with the lowest Bridge Priority in the spanning tree topology will be selected as the Root Bridge. If the lowest Bridge Priority is shared by multiple bridges, the one with the smallest numerical MAC address will be selected as the Root Bridge. If you do not change the Bridge Priority of any card from its default of 8, this means that the card in the RSTP topology with the lowest MAC address becomes the Root Bridge. When two cards are in a 1:1 equipment protection group, this value applies to both cards.

• RSTP Root Port ID (Read-only): The EOS port on this card that currently provides the lowest cost path to the root bridge.

• RSTP Root Bridge ID (Read-only): The Bridge ID of the card that is currently selected as Root Bridge for the spanning tree topology. If the current Root Bridge is the Active card in a 1:1 equipment protection group, and there is a protection switch that moves operation from that card to the other card in the protection group, then the spanning tree topology will select a new Root Bridge, which may or may not be the other card in the protection group.

RSTP Port Management

An RSTP port is the endpoint of a link that sends and receives packets. On the Traverse system, an RSTP port is represented by the EOS port type.

On an EOS port, configure the following parameters to enable RSTP on the EOS port:• RSTP: Enables or disables RSTP for Bridge services.

– Select Enabled to enable RSTP on this EOS port for bridge services.– Select Disabled to disable RSTP for bridge services.

• RSTP Path Cost: Set the path cost of this link. The total cost of a path between any card and the root bridge is the sum of the costs of all the links in the path. Lower values of this parameter mean that this port is more likely to be included in the lowest cost (more desirable) path from this or any other card to the root bridge. Enter an integer between 1 and 16; default is 1.

• RSTP Port Priority: Used when the spanning tree algorithm has determined that several ports on the card provide paths of equal total cost to the root bridge. The port with the lowest Port Priority is chosen as the Root Port. If several ports have the same lowest Port Priority, then the port with the lowest EOS Port ID is chosen as the Root Port. Enter an integer between 1 and 15; default is 8.


Chapter 9 Rapid Spanning Tree ProtocolGuidelines to Configure RSTP

See View RSTP Port Status, page 7-113 to view the status of the RSTP port. RSTP port state parameters are as follows: • RSTP Port State (Read-only): Indicates the status of the selected port.

– Disabled: This EOS port is not forwarding packets and is not participating in the RSTP operation.

– Listening: This EOS port is preparing to forward packets. It is temporarily disabled to prevent loops which may occur as the active topology of the LAN changes. Learning is disabled since changes in active topology can lead to incorrect information when the topology becomes stable.

– Learning: This EOS port is preparing to forward packets. It is temporarily disabled to prevent loops which may occur as the active topology of the LAN changes. Learning is enabled to collect information prior to forwarding, in order to reduce the number of frames unnecessarily forwarded.

– Forwarding: This EOS port is forwarding packets.– Blocking: This EOS port is not forwarding packets. It is preventing packets

from looping in the active topology.– Undefined: This EOS port is not using RSTP at all. Either this EOS port does

not have RSTP configured or there is no activated bridge service using this EOS port.

• RSTP Port Role (Read-only): This field reads one of the following values.– Alternate: Ports are blocked but can quickly become forwarding ports when

the topology is reconfigured. The node that has blocked the link does not send or receive any packets on that link. This blockage prevents packets from looping around the ring.

– Designated: This EOS port forwards Ethernet frames. – Disabled: RSTP is not enabled for this EOS port.– Root: The system has decided to use this port to reach the Root Bridge. This

port also forwards Ethernet frames.

Guidelines to Configure RSTP

Before you create an EOS port with RSTP enabled for a bridge service, review the following guidelines:• Multiple Ethernet cards in the same node can participate in the same RSTP ring.

That is, an RSTP network can contain multiple RSTP bridges in the same Traverse node.

• The Traverse RSTP implementation is intended only to operate within the Traverse network. The Traverse implementation of RSTP runs on EOS ports and does not run on any physical Ethernet ports.

• Enable RSTP in the Advanced Parameters dialog box of an EOS port. • All EOS port members must be bi-directional links for RSTP to be enabled.• The EOS port must be an endpoint in one or more bridge services. By enabling

RSTP on an EOS port, the port broadcasts that it will forward (based on the MAC address) any packets sent to it. However, when an EOS port doesn’t participate in any Bridge service, it does not perform MAC forwarding at all.

• RSTP supports any Ethernet topology (“RSTP network”) that consists of a set of Ethernet cards (“RSTP bridges”) interconnected by SONET/SDH transport connections (“RSTP links”) where:


Traverse Provisioning Guide, Section 7: Configuring EthernetGuidelines to Configure RSTP

– The number of RSTP links supported by a single RSTP bridge is up to at least 64 (all 64 EOS ports).

– The number of RSTP bridges in the more complex (mesh) topology is any number up to at least 200.

– The number of card-to-card hops between RSTP bridges is up to at least 32.• The Traverse platform supports both ring and mesh RSTP topologies. • There can be up to 200 Ethernet cards in an RSTP topology, but there cannot be

more than 32 hops to the RSTP Root Bridge.• There can be up to 32 Ethernet cards in a ring topology.• On average, RSTP may take up to three seconds to reconverge whenever there is a

topology change in a ring topology network. On average, RSTP may take between 15 and 45 seconds to reconverge on a mesh topology. A topology change includes the addition, removal, failure, or recovery of Ethernet cards or links participating in the RSTP network.

• If a customer uses 802.1d Spanning Tree Protocol (STP) within their own topology, the Traverse network is completely transparent to any such STP or RSTP implementation. That is, it looks like a multipoint LAN to which the customer’s devices are connected.

Spanning Tree BPDUs. If the Queuing Policy for this EOS port is WFQ, then all service data sent to the EOS port is queued on one of four service data queues. However, there is no separate system queue available for exclusive use of RSTP packets. The system uses CoS4 (queue 4).

Using CoS4 poses the following limitations:• BPDU (bridge protocol data unit) packets may get queued behind lots of CoS 4

service packets, leading to undesirably long delays.• If CoS 4 is assigned a Weight of 1, then packets of this CoS are transmitted only

when other CoSs with Weights other than one are not using their weighted proportion of the available bandwidth. If other CoS’s on this EOS port are using all of their weighted proportion, the scheduler for this EOS port will always select packets from those CoS’s, leading to undesirably long delays for CoS 4 packets, including RSTP.

Therefore, if WFQ is the Queuing Policy and RSTP is enabled for this EOS port in an activated bridge service, use the following guidelines:• Ensure that the WFQ Weight CoS 4 parameter has a weight of more than one.

Force10 recommends setting weights on the EOS port such that value in the WFQ Weight CoS4 parameter is at least 5% of the total.

• Ensure that the amount of CoS 4 service data queued for the EOS port is always small (one). For example, use Classifiers on the service-ports of the bridge service that do NOT classify packets into CoS4, or configure very small RED thresholds for the CoS 4 queues. (BPDUs are always queued without regard to RED thresholds, so setting small or even zero RED thresholds will not impede the transmission of BPDUs.)


Chapter 9 Rapid Spanning Tree ProtocolVirtual RSTP

Virtual RSTP On the Traverse system, up to 20 virtual copies of RSTP (V-RSTP) can be run on the same Ethernet card. Each copy, called a Virtual RSTP Bridge (VRB), uses an exclusive set of EOS ports that terminate on the card. Different EOS ports on each node can be assigned to VRBs to form completely separate spanning trees for individual customers; each bridge service can be in a different spanning tree.

After the SONET/SDH services are set up and the bandwidths are determined, Force10 recommends first setting up the VRB structure, then creating the EOS ports, assigning a VRB number to each link of the bridge service, enabling RSTP on each EOS port, and finally, creating the EOS and bridge services on each node.

Configure the following parameters to set up the VRB structure on the Ethernet tab of each Ethernet card:

VRB: Indicates a number to identify the virtual RSTP bridge being created. Valid values are 1 to 20; default is 1.

Bridge Priority: Indicates a number from 1 to 8 to indicate the priority of this bridge; default is 8. The bridge with the lowest Bridge Priority in the spanning tree topology will be selected as the Root Bridge. If the lowest Bridge Priority is shared by multiple bridges, the bridge with the smallest numerical MAC address will be selected as the Root Bridge. When two cards are in a 1:1 equipment protection group, this value applies to both cards.

Name: Indicates the name for this VRB. Names are case sensitive. They must be 2 to 32 characters in length, be alphanumeric, and contain no special characters. Hyphens (-) and spaces are allowed.



Before You Begin

Review the information in this topic before you configure RSTP or VRSTP on NGE, NGE Plus, 10GbE, GbE-10, or EoPDH cards.

Table 7-27 RSTP Requirements




Hardware

The information in this section strictly pertains to the following Ethernet cards (cards):

NGE: GBE4-FE16-TX GBE2T-GBE2F-FE16-TX


Gigabit Ethernet: 10GbEGbE-10

EoPDH (EOS ports only) GBE4-FE16-TX-EoPDHGBE2T-GBE2F-FE16-TX-EoPDH


The correct Electrical Connector Modules (ECMs) are installed.

Traverse Installation and Commissioning Guide, Section 2—Network Interface Specifications, Chapter 5—“Ethernet (Electrical) Interface Cabling Specifications,” page 2-43


Software








Chapter 9 Rapid Spanning Tree ProtocolConfigure RSTP on an EOS Port

Configure RSTP on an EOS Port

Use this procedure to help configure RSTP on an EOS port of an NGE, NGE Plus, 10GbE, GbE-10, or EoPDH card. RSTP is not supported on EOP ports.

Table 7-28 Configure RSTP on an EOS Port

Step Procedure

1 Complete the procedure Creating EOS Ports, page 7-58.

2 In Shelf View, click an NGE, NGE Plus, 10GbE, GbE-10, or EoPDH Ethernet card, then click the Ethernet tab.

Figure 7-41 Ethernet Card, Ethernet Configuration Tab

3 Edit the EOS port.

Figure 7-42 Ethernet Tab, EOS Subtab

a. Click the EOS subtab.b. Click the EOS port on the card to edit.c. Click the Edit button.

4 On the Edit EOS tab, click the Advanced button.

Figure 7-43 Click Advanced on the Edit EOS Tab

3a

3c

4


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure RSTP on an EOS Port

5 On the Advanced Parameters dialog box, set the RSTP Path Cost and RSTP Port Priority parameters for this EOS port.

Figure 7-44 RSTP Parameters for EOS Port

RSTP Config: Enables or disables RSTP for bridge services. If RSTP was not enabled on the previous screen, select RSTP Config to enable it.• Select to enable RSTP on this EOS port for bridge services.• Unselected (default). Disables RSTP for bridge services.

RSTP Path Cost: Set the path cost of this link. The total cost of a path between any card and the root bridge is the sum of the costs of all the links in the path. Lower values of this parameter mean that this port is more likely to be included in the lowest cost (more desirable) path from this or any other card to the root bridge. Enter a number between 1 and 16; default is 1.

RSTP Port Priority: Used when the spanning tree algorithm has determined that several ports on the card provide paths of equal total cost to the root bridge. The port with the lowest Port Priority is chosen as the Root Port. If several ports have the same lowest Port Priority, then the port with the lowest EOS Port ID is chosen as the Root Port. Enter a number between 1 and 15; default is 8.

When two cards are in a 1:1 equipment protection group, this value applies to both cards.

6 Click Done to save the changes, close the Advanced Parameters dialog box, and return to the Edit EOS tab.

7 On the Edit EOS tab, click Apply to save the changes and return to the EOS list on the EOS subtab.

8 The Configure RSTP on an EOS Port procedure is complete.

Table 7-28 Configure RSTP on an EOS Port (continued)

Step Procedure


Chapter 9 Rapid Spanning Tree ProtocolView RSTP Port Status

View RSTP Port Status

Use this procedure to view the status of RSTP on an NGE, NGE Plus, 10GbE, or GbE-10 Ethernet card.

Table 7-29 View RSTP Port Status

Step Procedure

1 Complete the procedure Creating EOS Ports, page 7-58.

2 Complete the procedure Configure RSTP on an EOS Port, page 7-111

3 In Shelf View, click an Ethernet card, then click the Ethernet tab.

Figure 7-45 Ethernet Tab, EOS Subtab

a. Click the EOS subtab.b. Click the EOS port to edit or review the status. Verify the RSTP check

box is selected.c. Click the Edit button.

4 On the Edit EOS tab, click the Status button.

Figure 7-46 Click Status on the Edit EOS Tab

3b3a

3c

4


Traverse Provisioning Guide, Section 7: Configuring EthernetView RSTP Port Status

5 On the EOS Port Status dialog box, view the RSTP port status.

Figure 7-47 RSTP Parameters for EOS Port

See RSTP Port Management, page 7-106 for explanations of these parameters.• RSTP Port State • RSTP Port Role

6 Click Refresh to retrieve the current data for the EOS port.

Click Done to close the EOS Port Status dialog box.

7 On the Edit EOS tab, click Cancel to return to the EOS list on the EOS subtab.

8 The View RSTP Port Status procedure is complete.

Table 7-29 View RSTP Port Status (continued)

Step Procedure


Chapter 9 Rapid Spanning Tree ProtocolConfigure Virtual RSTP

Configure Virtual RSTP

Use this procedure to configure up to 20 copies of virtual RSTP on an NGE, NGE Plus, 10GbE, or GbE-10 Ethernet card.

Table 7-30 Configure Virtual RSTP

Step Procedure

1 In Shelf View, click the Ethernet tab, then click the VRSTP subtab.

Figure 7-48 Ethernet Card, Ethernet Tab

2 Set up the virtual RSTP bridges (VRBs).

Figure 7-49 VRB Add Dialog Box

a. From the VRSTP screen, click the Add button. The VRB Add dialog box displays. Configure the following fields:Card: Indicates the slot and card type on which the VRB is being set up. Select the card on which to create the VRB.VRB: Enter the number of the VRB being added. Valid values are 2 through 20; default is 1. The default is static; it cannot be deleted.Bridge Priority: Enter the priority of the RSTP bridge for this VRB. Valid values are 1 (high) through 15 (low); default is 8.The bridge (card) with the lowest Bridge Priority in the spanning tree topology will be selected as the Root Bridge. If the lowest Bridge Priority is shared by multiple bridges, the one with the smallest numerical MAC address will be selected as the Root Bridge. If the Bridge Priority of any card is not changed from its default, the card in the RSTP topology with the lowest MAC address becomes the Root Bridge.Name (optional): Enter a name for the virtual RSTP bridge you are creating. The name must be 2 to 32 characters in length, be alphanumeric, and contain no special characters. Hyphens (-) and spaces are allowed.


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Virtual RSTP

b. Click Apply to save the changes, close the VRB Add dialog box, and return to the VRSTP screen.

c. Repeat Steps a and b for each virtual RSTP bridge needed at this node.

3 Create the EOS ports for each VRB. Follow the procedure Creating EOS Ports, page 7-58.

4 Link the EOS ports to the VRBs that are set up. a. On the EOS subtab, select the row of the EOS port on which to enable

VRSTP.b. Click the RSTP check box to enable RSTP.c. Click the VRB field. Select a VRB number from the drop-down menu.

Valid values are 1 through 20; default is 1. d. Repeat Steps a through d to enable RSTP and VRB for each EOS port.

Figure 7-50 EOS Subtab, Linking VRBs

Table 7-30 Configure Virtual RSTP (continued)

Step Procedure


Chapter 9 Rapid Spanning Tree ProtocolConfigure Virtual RSTP

5 To view the link detail and EOS port information for a specific VRB:a. Click the VRSTP subtab. b. Click the VRB row for which to review the detail.

Figure 7-51 VRSTP Subtab, VRB Detail

c. Click Refresh. Detail information for the selected VRB appears in the fields at the bottom of the VRSTP screen. Only EOS ports with VRB enabled will display.VRB (Read-only): The VRB number assigned to this row number.Last Query (Read-only): Indicates the date and time of the last time this item was queried.Bridge ID (Read-only): Indicates the RSTP Bridge ID of this virtual RSTP bridge. Used in the RSTP protocol and displayed in the following hexidecimal format: <BridgePriority>000-MAC address>. Example: 8000-1b2000c144d8. When two cards are in a 1:1 equipment protection group, each card has a different Bridge ID, even though only one of the cards is included in the spanning tree topology at any time.Root ID (Read-only): Indicates the RSTP Root Bridge ID for this VRB.Root Port (Read-only): The RSTP Root Port ID. The EOS port on the card that provides the lowest cost to the root bridge.EOS (Read-only): The EOS Port ID assigned to this VRB.Port Priority (Read-only): The RSTP port priority. The EOS port with the lowest port priority is chosen as the root port. If several ports have the same lowest Port Priority, the port with the lowest EOS Port ID becomes the root port. Valid values are 1 through 15; default is 8.


Step Procedure

5b

5c


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Virtual RSTP

Path Cost (Read-only): The RSTP path cost of this link. The total cost of a path between any card and the root bridge; the sum of the costs of all links in the path. Lower values of this parameter indicate the port is more likely to be included in the lower cost path from this or any other card to the root bridge. Valid values are 1 through 16; default is 1.Port Role (Read-only): The RSTP port role for this link. Valid values are:– Alternate: Ports are blocked but can quickly become forwarding

ports when the topology is reconfigured. The node that has blocked the link does not send or receive any packs on that link. This blockage prevents packets from looping around the ring.

– Designated: This EOS port forwards Ethernet frames.– Disabled: RSTP is not enabled for this EOS port.Port State (Read-only): The RSTP Port State of this link. Valid values are:– Disabled: This EOS port is not participating in the RSTP

operation.– Listening: This EOS port is preparing to forward packets. It is

temporarily disabled to prevent loops which may occur as the active topology of the LAN changes. Learning is disabled since changes in active topology can lead to incorrect information when the topology becomes stable.

– Learning: This EOS port is preparing to forward packets. It is temporarily disabled to prevent loops which may occur as the active topology of the LAN changes. Learning is enabled to collect information prior to forwarding in order to reduce the number of frames unnecessarily forwarded.

– Forwarding: This EOS port is forwarding packets.– Blocking: This EOS port is not forwarding packets. It is

preventing packets from looping in the active topology.– Undefined: This EOS port is not using RSTP at all. Either this

port does not have RSTP configured or there is no activated bridge service using this EOS port.

6 The Configure Virtual RSTP procedure is complete.


Step Procedure



Chapter 10Ethernet Services

Introduction This chapter contains the following topics:• Ethernet Services Definition, page 7-119• Ethernet Services and VLAN Tagging, page 7-125• Determining Services, page 7-126• Guidelines to Configure Ethernet Services, page 7-134• VLAN Tagging Guidelines, page 7-134• Before You Begin, page 7-137• Search for Services, page 7-138• Configure Ethernet Services, page 7-141

Ethernet Cards

Ethernet Services Definition

Ethernet service is a card-level packet forwarding relationship, optionally restricted by VLAN ID, between Ethernet termination points on the same card.

The endpoints in an Ethernet service can be a mix of the following types: • 10GbE• GBE • GBETX • ETH100TX


Cards Card Types







Traverse Provisioning Guide, Section 7: Configuring EthernetLine Services

• EOS port: Ethernet-over-SONET/SDH transport connections• EOP port: Ethernet over PDH transport connections• LAG: virtual Ethernet ports built out of sets of physical Ethernet ports

There are four types of Ethernet services on a Traverse platform: • Line Services, page 7-120• Bridge Services, page 7-121• Aggregation Bridge Services, page 7-122• Multipoint ECC Services, page 7-123

Line Services An Ethernet line service is a forwarding relationship between two endpoints on the same card. Use this service to create a dedicated point-to-point service, a shared point-to-point service, or an internet access application.

Figure 7-52 Line Service

An Ethernet line service transfers packets from one port to another. The set of arriving packets on a port that belong to a particular line service may be (a) all packets, or (b) a subset identified by VLAN. Once identified to a service, the system forwards the packets to, and only to, the other port in the service. Services can share (by VLAN ID) any of the endpoints with other services.

The system does not learn the source MAC addresses on any port in a line service and forwards packets without regard to the destination MAC addresses.

Under some circumstances, the system can modify the VLAN information on the packet (see Ethernet Services and VLAN Tagging, page 7-125). The forwarding mechanism is subject to traffic management, which may end up dropping some of the packets.


Chapter 10 Ethernet ServicesBridge Services

Bridge Services

A bridge service is a forwarding relationship between an arbitrary number of endpoints on the same card. Any of the endpoints can be shared (by VLAN ID) with other services. Within a single bridge service, a packet is forwarded to one endpoint or to all endpoints using standard MAC address forwarding rules. Use this service to create a Virtual LAN Service application in the network.

Figure 7-53 Bridge Service

On NGE cards, there can be up to 20 Ethernet ports and up to 64 EOS ports in a single bridge service. On 10GbE cards, there is one Ethernet port; on GbE-10 cards, there can be up to 10 Ethernet ports. Both 10GbE and GbE-10 cards can have up to 128 EOS ports in a single bridge service and support up to 256 activated bridge services. EoPDH cards can support up to 128 ports which can be EOS, EOP, or a combination of EOS and EOP ports.

The system learns the source MAC addresses from packets that arrive on any port in a bridge service. The system forwards packets to other ports in the same service based strictly on the destination MAC address.

Adding and Removing Endpoints to a Bridge Service. You can add or remove endpoints to and from an activated bridge service. If, during a transition, the membership of the bridge service is less than two, the system will suspend forwarding packets and will resume forwarding when another member is added.


Traverse Provisioning Guide, Section 7: Configuring EthernetAggregation Bridge Services

Aggregation Bridge Services

An aggregation bridge service is a hybrid of a line service and a bridge service. It is a forwarding relationship between a set of endpoints on a card, where one endpoint is considered the aggregation port and the other endpoints are considered ordinary members of the service.

Traffic received on the aggregation port is forwarded just as in a bridge service – to one or more ordinary members based on the destination MAC address. Traffic received on the ordinary members of the service is forwarded directly to the single aggregation port.

Figure 7-54 Aggregated Bridge Service

The system learns MAC addresses only on the non-aggregation members. Learned MAC addresses are needed to determine forwarding from the aggregation port to the other ports.

Aggregation Bridge Service with an Active/Standby CPE. In this scenario, the aggregation port is an EOS port. The other endpoints are Ethernet ports that connect to different line cards (one Active, one Standby) in a CPE (customer premise equipment) device. The CPE sends and receives on one of the Ethernet ports at a time. The Traverse forwards traffic from both CPE ports to the EOS port. In the other direction, the Traverse forwards traffic from the EOS port to whichever Ethernet port the MAC address has been learned on. Packets addressed to unknown or broadcast MAC addresses are flooded to both Ethernet ports. The CPE device accepts the packets from the active port and ignores packets from the standby port.

Hub Forwarding via a Router. In this scenario, the aggregation port is an Ethernet port connected to a router at a customer’s hub location. The ordinary members are EOS ports that connect to remote Traverse or TraverseEdge at customer branch locations. The customer wants all branch-to-branch traffic to go through the router security and traffic pattern tracking reasons. Traffic arriving from any EOS port goes directly to the router port. Traffic arriving from the router port is forwarded to the correct branch location(s), based on MAC forwarding.


Chapter 10 Ethernet ServicesMultipoint ECC Services

Multipoint ECC Services

A multipoint ECC (Ethernet Control Channel) service uses a bonded set of PDH links, such as DS1s, to provide IP management connectivity between remote CPE (customer premise equipment) devices and the provider’s management network.

The CPE device is managed using IP frames over a designated management VLAN on the Ethernet link that runs over the bonded PDH link (an EOP link). The frames are tagged with a customer VLAN ID corresponding with the management VLAN of the CPE device. The EOP links terminate on the EoPDH card at EOP ports. The Traverse node then carries the IP traffic over the DCC network to the Traverse node that has its DCN port connected to the provider’s management network.

CPEs connected to a single EoPDH card can be placed in one or more groups. Each group has a separate unique IP subnet supported by a unique IP interface on the Traverse. The IP interface is the gateway to an IP subnet in the provider’s management network; both the IP address and subnet mask of the IP interface are unique. To the CPE, the multipoint ECC appears as an IP gateway on a router.

Figure 7-55 IP Connectivity on a Multipoint ECC Service

Each EoPDH card supports a maximum of four multipoint ECC services; each Traverse shelf supports a maximum of 16 such ECC services.

The Ethernet Control Channel (ECC):• Is the name for the management channel that runs between a CPE and its attached

Traverse node.• Provides the same basic capability as DCC of transporting packets (normally IP)

between the CPEs and the Traverse system.• Uses a unique VLAN ID on the Ethernet link between two nodes to differentiate

the ECC frames from non-management frames.

A multipoint ECC Interface (ECCI) service:• Is a service that provides an IP interface on a single node to which zero or more

ECCs are connected. • Must be created by the operator.


Traverse Provisioning Guide, Section 7: Configuring EthernetMultipoint ECC Services

• One or more can be configured on an EoPDH card.• Has zero or more member ports. A member port is an EOP port set up on an

EoPDH card.

Each multipoint ECCI port member must have a defined VLAN ID that matches the VLAN ID of the ECC over the attached links. The multipoint ECCI service uses ARP and MAC forwarding to support multiple CPEs from the single IP interface.

The multipoint ECCI service uses MAC learning to determine on which ECC to reach a CPE. When a management packet is set from the Traverse system, the ECC Interface uses ARP and MAC forwarding to select one or more member EOP ports. When a management packet is sent from a CPE, the multipoint ECC directs it onto the inter-Traverse IP network. Security features ensure the packets are not sent to other CPEs on the same subnet over the network.

Each ECCI port member must have a defined VLAN ID that matches the VLAN ID of the ECC over the attached links. CPE devices are managed by an ECC that runs over a UNI (ECC-UNI). The Traverse system supports multiple CPEs from a single IP interface using a multi-port ECCI.


Chapter 10 Ethernet ServicesEthernet Services and VLAN Tagging

Ethernet Services and VLAN Tagging

This table summarizes system behavior between incoming packets (ingress) and outgoing packets (egress) based on the Tagging parameter.

See Chapter 2—“Configuring Ethernet Equipment,” VLAN Tags, page 7-10 for description of the port Tagging parameters.

Table 7-31 VLAN Tag Modification

Ingress Port

Egress Port

Port-Based Customer-Tagged

Bundled Customer-tagged(with C-VLAN ID

Preservation enabled)

Service-Tagged

Port-based No change

See All Ports in Service are Port-based, page 7-128

Not supported Not supported Add service tag

Mix of Port-based and Service-tagged Ports in Service, page 7-128

Customer-tagged Not supported Pass unchanged, strip, or swap VLAN ID

All Ports in Service are Customer- tagged, page 7-129

Pass customer tags unchanged


Add service tag

Mix of Customer- tagged and Service-tagged Ports in Service, page 7-131

Bundled Cus-tomer-tagged(with C-VLAN ID Preservation enabled)

Not supported Pass customer tags unchanged




Add service tag


Service-tagged Remove service tag

Mix of Port-based and Service-tagged Ports in Service, page 7-128

Remove service tag


Remove service tag



Pass unchanged or swap VLAN ID

All Ports in Service Tagged as Service- tagged, page 7-133


Traverse Provisioning Guide, Section 7: Configuring EthernetDetermining Services

Determining Services

For each Customer-tagged, Bundled Customer-tagged, and Service-tagged port in a service, it is necessary to specify which VLAN ID(s) on that port is (are) associated with which service. The system directs packets on the port with the VLAN ID to the service and ensures that packets sent by the service on the port have an associated VLAN ID.

For release TR3.2 and later, on the VLAN Configuration portion of the Creating Ethernet Service screen, there are two new parameters to identify a multiple (“bundled”) or single (“not bundled”) VLAN ID association with a service.

Important: If this is an existing service created before release TR3.2, the Single VLAN ID value will be set by default to preserve the existing VLAN configuration. Otherwise, the user can (but is not required to) manually change from single to multiple VLAN Provisioning mode regardless of the service’s activation state.• Multiple VLAN Provisioning mode—Multiple C-VLAN IDs on a

Customer-tagged port map to a service. (Enabled by default on services created in release TR3.2 and Disabled for services that existed prior to release TR3.2 upgrade.)

Note: The Traverse system supports a mix of Ethernet services activated on a port where the new VLAN provisioning option is selected on some services that use that port, and is not selected on other services that use that port.

The parameter group used to associate (multiple) VLAN IDs with each Customer-tagged port in a service are:

– C-VLAN ID Preservation—Preserves VLAN IDs for a range of customer-tagged port members (Enabled by default)• C-VLAN ID for all Customer-tagged Ports—Create a set of C-VLAN

IDs for bundling. The user can add or remove C-VLAN IDs without interruption on an active service. 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: If a set of C-VLAN IDs are defined, the system prevents the deselection of the C-VLAN ID Preservation parameter.

Note: The Traverse system prohibits changing the C-VLAN ID Preservation from Disabled to Enabled, if the service currently contains more than one C-tagged port, and if different C-tagged ports are provisioned to use different C-VLAN IDs.

The parameter group used to associate S-VLAN IDs with each Service-tagged port in a service are:

– Use the same S-VLAN ID on all S-Tagged ports—Use the same VLAN ID for all Service-tagged ports (i.e., do not swap S-VLAN IDs).• S-VLAN ID for all S-Tagged Ports—Identify an S-VLAN ID.

To preserve an existing (pre-release TR3.2) VLAN configuration of one C-VLAN ID per service, use:• Single VLAN ID—One C-VLAN ID on a port maps to a service (no bundling)


Chapter 10 Ethernet ServicesDetermining Services

The parameter group used to associate a single VLAN ID with each Customer-tagged or Service-tagged port in a service are:

– Service VLAN ID—Advanced parameters on an Ethernet service– Override VLAN ID—Advanced parameters on a service-port, i.e., a port’s

role as an endpoint in a service

For pre-TR3.2 releases where the C-VLAN ID Preservation parameter is disabled, the Ethernet service Service VLAN ID is associated with all Customer-tagged and Service-tagged service-ports in the service, except for any service-ports that have an Override VLAN ID provisioned. In that case, the system uses the Override VLAN ID associated just with that one service-port.

A Service VLAN ID for a service, all of whose service-ports are tagged Port-based, is ignored. However, if a bridge or aggregation bridge service contains only Port-based ports, it is possible that at some future time the operator could add another port (tagged Service-tagged) to that service. At that time, the Service VLAN ID would be automatically associated with that new Service-tagged port (unless the new port is configured with its own Override VLAN ID).

Packets Arriving on Ports Tagged Port-Based. When a packet arrives on a port tagged Port-based that is a member of an activated Ethernet service, the system considers that the packet belongs to that service without reference to the VLAN ID field or to any VLAN tag in the packet.

See the following topics for the forwarding rules for packets arriving on ports tagged Port-based:• All Ports in Service are Port-based, page 7-128• Mix of Port-based and Service-tagged Ports in Service, page 7-128

Packets Arriving on Ports Tagged Customer-Tagged. When a packet arrives on a port that is Customer-tagged and that packet already has a VLAN tag, the system uses the VLAN ID in the VLAN tag to determine which service the packet belongs to according to the following ordered rules:• If the VLAN ID is 0, system treats the packet as a priority-tagged packet. • The VLAN ID of the packet must be in the range of the VLAN IDs associated with

that customer-tagged service port.

When a packet arrives on a port that is Customer-tagged and that packet does not have a VLAN tag, the system considers the packet has a VLAN ID of 0 and determines the appropriate service according to the rules listed above.

The system allows a Customer-tagged port to carry a mix of tagged and untagged packets.

See the following topics for the forwarding rules for packets arriving on ports tagged Customer-tagged:• All Ports in Service are Customer- tagged, page 7-129• Mix of Customer- tagged and Service-tagged Ports in Service, page 7-131

Packets Arriving on Ports Tagged Service-Tagged. When a packet arrives on a Service-tagged port and that packet has one or more VLAN tags, the system treats the first (outermost) VLAN tag as a service provider VLAN tag. The VLAN ID in the service provider VLAN tag is used to determine which service the packet belongs to, irrespective of whether or not the packet also contains a customer VLAN tag according to the following ordered rules:


Traverse Provisioning Guide, Section 7: Configuring EthernetAll Ports in Service are Port-based

• If the VLAN ID matches the VLAN ID field of this port in an activated Ethernet service, then the packet belongs to that service.

• If the service VLAN ID does not match any service according to the preceding rules, the system drops the packet.

When a packet arrives on a Service-tagged port and that packet does not have a VLAN tag, the system drops the packet.

See the following topics for the forwarding rules for packets arriving on ports tagged Service-tagged:• Mix of Port-based and Service-tagged Ports in Service, page 7-128• Mix of Customer- tagged and Service-tagged Ports in Service, page 7-131• All Ports in Service Tagged as Service- tagged, page 7-133

All Ports in Service are Port-based

When a packet arrives on a port tagged Port-based and that port is a member of an activated Ethernet service, then the system considers that the packet belongs to that service without reference to the VLAN ID field or to any VLAN tag in the packet.

When all ports in a service have Port-based in the Tagging parameter, the system forwards packets among the ports in the service without processing the VLAN tags. The packets may have VLAN tags that originated from the customer premise equipment (CPE), but the forwarding process does not use those tags.

On Port-based ports, the system ignores the an existing VLAN tag. Packets may be either tagged or untagged. If there is a VLAN tag in the packet, it is treated as a customer VLAN tag and forwarded transparently to the egress port. Depending on how the operator provisions the service, the system could examine the priority bits in the customer VLAN tag, if it has one, for classification purposes.

In a line service, the system forwards all packets from service port A to service port B and vice versa. In a bridge service, the system forwards packets received on any port to one or more other ports based entirely on the destination MAC address. The system does not add or remove VLAN tags in the forwarding process.

Some examples of applications supported this way: • Line service between two Ethernet ports on the same card. The system forwards all

packets received from one port unmodified (regardless of VLAN tag) to the other port.

• Line service between an Ethernet port and a transport link. The system forwards all packets received from the port unmodified to the transport link (such as the EOS port) and vice versa.

• Bridge service between any number of Ethernet ports on the same card. The system forwards all packets received from one port unmodified on the destination port(s).

Mix of Port-based and Service-tagged Ports in Service

If a service has a mix of Port-based and Service-tagged ports, the system manipulates the VLAN tag before moving data among the ports. In this application, the VLAN ID identifies the service provider VLAN tag used on the Service-tagged ports. It has no meaning for the Port-based ports.

When a packet arrives from a Port-based port, it may or may not already have a VLAN tag. If the packet contains a VLAN tag, this tag is termed a customer VLAN tag. When the packet is forwarded to a Service-tagged port, the system adds a second VLAN tag to the packet. The second VLAN tag is termed the service provider VLAN tag and is added before the customer VLAN tag in the header of the packet. This process is called double-tagging, VLAN stacking, or Q-in-Q.


Chapter 10 Ethernet ServicesAll Ports in Service are Customer- tagged

The service provider VLAN tag belongs to the provider to multiplex several independent customer’s virtual LANS onto the same set of transport links.

If a service receives a packet from a Service-tagged port and forwards it to a Port-based port, the system removes the service provider VLAN tag and does not otherwise modify the packet.

All Ports in Service are Customer- tagged

When a packet arrives on a Customer-tagged port and the VLAN ID in its VLAN tag matches the VLAN ID of the service, the packet is then forwarded to another port in the same service based on the forwarding rules of that service.

However, this type of application can add customer VLAN tags to untagged packets, remove customer VLAN tags to produce untagged packets, or replace one VLAN ID for another.

If a service receives a packet from a Customer-tagged port and forwards it to another Customer-tagged port with C-VLAN ID Preservation enabled, the system processes the packet as follows:

If a service receives a packet from a Customer-tagged port and forwards it to another Customer-tagged port with C-VLAN ID Preservation disabled, the system processes the packet as follows:

Table 7-32 C-VLAN ID Preservation is enabled (CT to CT)

Ingress Port Tagging Type

Ingress CT Frame Format

Egress Port Tagging Type

Action when C-VLAN

Preservation is “Yes”

Customer-tagged (CT)

Tagged CT No change to CT

CT Priority-tagged CT No change to CT (i.e., send prior-ity-tagged frame)

CT Untagged CT No change to CT (i.e., send untagged frame)

Table 7-33 C-VLAN ID Preservation is disabled (CT to CT)

Ingress Port Tagging

Type



C-VLAN ID (C-VID)

Provisioned for Egress Port

Action when C-VLAN

Preservation is “No”


Tagged CT Valid C-VID (1–4093)

Swap C-VID in CT to match egress port’s C-VID

CT Tagged CT 0 (Untagged/priority tagged)

Strip CT (i.e., send an untagged frame)


Traverse Provisioning Guide, Section 7: Configuring EthernetAll Ports in Service are Customer- tagged

Packets arriving on Customer-tagged ports and forwarded to other Customer-tagged ports support the following applications:• Internet access service. An Ethernet line service between the Customer-tagged

Ethernet port and Customer-tagged EOS or EOP port, where packets arrive and depart on the Ethernet port with valid VLAN tags. There is no change to the customer VLAN tag as the packet moves between the Ethernet port and EOS or EOP port.

• Internet access service (IAS) with untagged packets. An Ethernet line service between a Customer-tagged Ethernet port and a Customer-tagged EOS or EOP port, where packets arrive and depart on the Ethernet port with untagged packets. The system adds a customer VLAN tag (via Service VLAN ID) when the packet is forwarded from the Ethernet port to the EOS or EOP port. The system removes the customer VLAN tags from the packet in the reverse direction. In this scenario, configure the Ethernet port with an Override VLAN ID of 0 (untagged packets).

• There can be a mix of tagged and untagged packets on a Customer-tagged Ethernet port. Tagged packets will be assigned to services according to their existing customer VLAN tags. Untagged packets will get assigned to another service that has a VLAN ID of 0 for that service port.

• Multiple line services that use the same Customer-tagged Ethernet port can send packets to the same EOS or EOP port, different EOS or EOP port, or other Ethernet ports on the same card. This application allows a true any VLAN cross-connect.

• Services of different service types can use the same Customer-tagged Ethernet port. The customer VLAN tag identifies the service. The type of service (line, bridge, or aggregation bridge) determines whether packets are forwarded strictly to one other port or to various other ports according to MAC forwarding rules. This allows a service provider to configure an Ethernet Virtual LAN service and an Ethernet Private Line application on the same customer port.

• Multiple bridge services can use the same Customer-tagged Ethernet port. A service provider can provision multiple Ethernet virtual LAN services on the same customer port, where the different services are identified by different customer VLAN tag values.

CT Priority-tagged CT Valid C-VID (1–4093)

Swap C-VID in CT to match egress port’s C-VID

CT Priority-tagged CT 0 (Untagged/priority tagged)

Strip CT (i.e., send an untagged frame)

CT Untagged CT Valid C-VID (1–4093)

Add CT containing egress port’s C-VID and priority

CT Untagged CT 0 (Untagged/priority tagged)

No change to CT (i.e., send untagged frame)

Table 7-33 C-VLAN ID Preservation is disabled (CT to CT) (continued)


Type



C-VLAN ID (C-VID)


Action when C-VLAN



Chapter 10 Ethernet ServicesMix of Customer- tagged and Service-tagged Ports in Service

Mix of Customer- tagged and Service-tagged Ports in Service

The system adds a service provider VLAN tag to a packet arriving on a Customer-tagged port that is forwarded to a Service-tagged port, then processes the packet as follows:

Table 7-34 C-VLAN ID Preservation is disabled (CT to ST)

Ingress Port Tagging Type



Action when C-VLAN Preservation is “No”

CT Untagged ST Add CT containing C-VID=0 and priority (Default Priority Bit in the Classifier of the ingress port) and add ST con-taining egress port’s (i.e., ser-vice provider’s network) S-VID and priority (according to the classification and policing oper-ations)1

1 The untagged packet changes into a customer VLAN-tagged packet before the system adds the service provider VLAN tag. The customer VLAN tag carries no customer VLAN ID, only a provisioned priority for untagged packets (what IEEE calls a “priority tagged” packet). If the eventual consumer of the service provider VLAN tag is another Ethernet card in the Traverse network, the system can process both tags. For other cases (e.g., if the eventual consumer is a non-Traverse node), the service provider must decide how to process the two tags.

CT Priority-tagged ST No change to CT (i.e., send untagged frame) and add ST containing egress port’s S-VID and priority (according to the classification and policing oper-ations)

Customer-tagged (CT) Tagged Service tagged (ST) No change to CT (i.e., send untagged frame) and add ST containing egress port’s S-VID and priority (according to the classification and policing oper-ations)


Traverse Provisioning Guide, Section 7: Configuring EthernetMix of Customer- tagged and Service-tagged Ports in Service

The system removes a service provider VLAN tag to a packet arriving on a Service-tagged port that is forwarded to a Customer-tagged port exposing the customer VLAN tag to the customer premise equipment, then processes the packet as follows:

Table 7-35 C-VLAN ID Preservation is disabled (ST to CT)


Type



C-VLAN ID (C-VID)


Action when C-VLAN


Service-tagged (ST)

Tagged CT Valid C-VID (1–4093)

Strip S-tag. Swap C-VID in CT to match egress port’s C-VID

ST Tagged CT 0 (Untagged/priority tagged)

Strip S-tag. Strip CT (i.e., send an untagged frame)

ST Priority-tagged CT Valid C-VID (1–4093)

Strip S-tag. Swap C-VID in CT to match egress port’s C-VID

ST Priority-tagged CT 0 (Untagged/priority tagged)

Strip S-tag. Strip CT (i.e., send an untagged frame)

ST Untagged CT Valid C-VID (1–4093)

Strip S-tag. Add CT containing egress port’s C-VID and priority

ST Untagged CT 0 (Untagged/priority tagged)

Strip S-tag. No change to CT (i.e., send untagged frame)


Chapter 10 Ethernet ServicesAll Ports in Service Tagged as Service- tagged

The system removes a service provider VLAN tag to a packet arriving on a Service-tagged port that is forwarded to a Customer-tagged port exposing the customer VLAN tag to the customer premise equipment, then processes the packet as follows:

The most common instance of this application will mix Customer-tagged Ethernet ports in a service with Service-tagged EOS or EOP ports. For example, the system adds the service provider VLAN tag to identify the Ethernet service on a shared transport service within the service provider network. At the other end of the network, the system strips the service provider VLAN tag and forwards the packet using the customer VLAN tag. Additionally, the service provider can use the service provider VLAN tag to carry policing data along with the packets in the service provider network in order to manage congestion that occurs at downstream nodes.

All Ports in Service Tagged as Service- tagged

The Traverse system also supports applications in which all service ports are tagged Service-tagged. These applications include hairpinning and LO to HO switching. In a hairpinning application, all Ethernet traffic is backhauled from access nodes to an Ethernet hub that switches VLANs to other access nodes. In a LO to HO switching application, VLAN traffic is aggregated from small tunnels on an access ring to larger tunnels on a metro ring.

Packets arriving on a Service-tagged port and forwarded to another Service-tagged means that the service provider VLAN tag remains on the packet.

Specifically, if a service receives a packet from a Service-tagged port and forwards it to another Service-tagged port, the system processes the packet as follows:• If the arriving packet is tagged with appropriate VLAN ID of this service, the

system does not remove the tag (a service provider VLAN tag). The system replaces the service VLAN ID in the service provider VLAN tag in with the VLAN ID associated with the egress port. This replacement occurs whether or not the two VLAN IDs are the same. The system modifies the priority bits in the service provider VLAN tag according to the classification and policing operations.

Table 7-36 C-VLAN ID Preservation is enabled (CT to ST)


Type



Action when C-VLAN Preservation is “Yes”


Tagged ST No change to C-tag. Add S-tag contain-ing egress port’s S-VID and priority.

CT Priority-tagged ST No change to C-tag. Add S-tag contain-ing egress port’s S-VID and priority.

CT Untagged ST No change to C-tag (i.e., in this case, do not add C-tag). Add S-tag containing egress port’s S-VID and priority.


Traverse Provisioning Guide, Section 7: Configuring EthernetVLAN Tagging Guidelines

Supported applications of this tagging model are as follows: • A virtual private LAN application. Packets enter the network at a Ethernet port on

Node A are switched (through Ethernet bridge services) on some intermediate Nodes B, C, and D before they leave the network at an Ethernet port on Node E. On the intermediate nodes, a packet can be forwarded from one Service-tagged port (EOS or EOP port) to another, as well as to local Ethernet ports.

• An “EtherDACS” application. Packets that enter the network at access nodes travel through small tunnels on access rings. They are aggregated into larger tunnels on metro or core rings before reaching their egress point at some head-end node. The intermediate aggregation nodes forward packets from one Service-tagged EOS or EOP port terminating a low-order VCG to another EOS or EOP port terminating a high-order VCG.

VLAN Tagging Guidelines

You cannot change the Tagging parameter of a port if one or more services are activated on that port.

An Ethernet service cannot have a mix of Customer-tagged and Port-based ports in the same service. You cannot add a port to an activated Ethernet service if adding that port results in a mix of Customer-tagged and Port-based ports in that service.

An Ethernet service can have a mix of Service-tagged ports and either other type of tagged port.

A port using Port-based tagging can only have one Ethernet service using that port.

A port using Customer-tagged or Service-tagged tagging can have more than one Ethernet service using that port.

No two activated services can use the same C-VLAN ID on the same Customer-tagged port.

A port using Customer-tagged tagging can have one service that allows untagged or priority-tagged packets, thus allowing the system to know which service to associate the untagged or priority-tagged packets. Priority-tagged packets are tagged with a priority tag that has a VLAN ID of 0 and a specific value of priority bits.

NGE, NGE Plus, and EoPDH cards support any number of concurrent port-VLAN IDs up to 3,000. The 10GbE and GbE-10 cards support any number of concurrent port-VLAN IDs up to 32,768.

Guidelines to Configure Ethernet Services

Line Services. A line service has only two members. You cannot remove any member from an activated service.

Enable the link integrity feature on Ethernet line services using the Link Integrity parameter. Configure link integrity on a line service that uses exactly one Ethernet port and one EOS port on the ingress and egress nodes of the network.


Chapter 10 Ethernet ServicesGuidelines to Configure Ethernet Services

Bridge Services. A bridge service forwards packets among the number of ports on a card. See the following table for information on the number of bridge services available on each Ethernet card (NGE, NGE Plus, 10GbE, GbE-10, and EoPDH):

You can add or remove members from an activated bridge service. If, during a transition, the membership of the bridge service is less than two, the system suspends forwarding packets and resumes forwarding when another member is added.

Aggregate Bridge Services. An aggregate bridge service must have exactly one aggregate port which cannot be removed or replaced while the service is activated.

An aggregate bridge service can have anywhere from 0 to 83 non-aggregate ports (other members) on an NGE or NGE Plus card; from 0 to 128 non-aggregate ports on a 10GbE card; from 0 to 137 non-aggregate ports on a GbE-10 card; from 0 to 147 non-aggregate ports on an EoPDH card. Any of these members can be added to or removed from an activated service at any time.

Multiport ECC Services. A multiport ECC (Ethernet Control Channel) service links the Traverse system and external CPE devices for forwarding IP packets across the network. Each EoPDH card supports up to four ECCs via an EOP port; each Traverse shelf supports a maximum of 16 ECCs.

Individual IP addresses must be set for each ECC and the CPE device, and they must be in the same subnet mask range. The IP address of the ECC interface is used as the default IP gateway, allowing the traffic to pass through the CPE to the ECC into the inter-Traverse management network. The CPE must be configured to transfer management traffic over one of its EOP links using a management VLAN ID.

Each EOP member used by a multiport ECC service must be in customer-tagged service mode.

VLAN IDs assigned to EOP members must be unique to the ECC; they must be different from VLAN IDs assigned to normal traffic. EOP members in the ECC may use identical or different VLAN IDs.

Table 7-37 Bridge Services Available on Ethernet Cards

NGE / NGE Plus 10GbE GbE-10 EoPDH

Number of physical ports

20 1 10 20

Number of EOS ports

64 128 128 1281

1 On EoPDH cards, the total number of available EOS and EOP ports is 128. These can be all EOS, all EOP, or a combination of EOS and EOP ports totalling 128.

Possible service ports available on single service

84 129 138 148

Number of acti-vated bridge ser-vices supported

20 minimum 256 minimum 256 minimum 20 minimum


Traverse Provisioning Guide, Section 7: Configuring EthernetGuidelines to Configure Ethernet Services

Setting Up EOS Ports on 10GbE or GbE-10 Cards. To forward Ethernet data from one 10GbE or GbE-10 card to another 10GbE or GbE-10 card in the same chassis, first set up card-to-card SONET/SDH (STS/VC-3) services between the virtual optical port (port 0) on one 10GbE or GbE-10 card and the virtual optical ports on the second 10GbE or GbE-10 card. Next, add the members to the EOS ports on each card. Ethernet services on the two 10GbE or GbE-10 cards can exchange Ethernet frames over the backplane by sending and receiving frames on their local EOS ports. This can be useful to forward frames from the 10Gbps Ethernet port on a 1-port 10GbE card to one or more GbE ports on a 10-port GbE-10 card in the same chassis.

The Traverse backplane can connect no more than 48 STSs/VC-3s between any single pair of slots. The slot-to-slot restriction also pertains to the 2-port OC-48/STM-16 card. For more information on the restriction for the 2-port OC-48/STM-16 cards, see Section 4—Creating ADM Services, Chapter 5—“Creating 2-Port OC-48/STM-16 Services,” Guidelines to Create an Aggregate Service from a Subtended OC-48 UPSR, page 4-76.

The two-slot 10GbE or GbE-10 cards have a total backplane capacity of 192 STSs/VC-3s. On the two-slot 10GbE or GbE-10 cards, STS-1 to STS-96 are available in the lower-numbered slot. STS-97 to STS-192 are available in the higher-numbered slot. This is the same STS-to-slot assignment used on the two-slot OC-192 card described in Section 4—Creating ADM Services, Chapter 5—“Creating 2-Port OC-48/STM-16 Services,” Guidelines to Create an Aggregate Service from a Subtended OC-48 UPSR, page 4-76.

To connect all 192 STSs between the two 10GbE or GbE-10 cards, use the following set of cross-connects:

This cross-connect set results in 48 slot-to-slot STS connections between any pair of slots on the two-slot cards. Any equivalent set of services that does not exceed 48 slot-to-slot STS connections will work equally well.

When cross-connecting STSs between a two-slot, 1-port 10GbE card (or 10-port GbE-10 card) and a two-slot OC-192 card, the 48 slot-to-slot restriction does not apply. The OC-192 cards have specialized hardware to allow connecting more than 48 STSs per slot. You can connect any STS on a 10GbE or GbE-10 card to any STS on an OC-192 card.

Table 7-38 Cross-connecting Services on 10GbE or GbE-10 Cards

Services Connect STSs from Connect STSs to

STS-1 or STS-3c slot 3 / STS 1-48 slot 5 / STS 1-48


STS-1 or STS-3c slot 3 / STS-97-144 slot 5 / STS 49-96



Chapter 10 Ethernet ServicesBefore You Begin

Before You Begin

Review the information in this topic before you configure the Ethernet services using the following cards: NGE, NGE Plus, 10GbE, GbE-10, or EOPDH.


Table 7-39 Ethernet Service Requirements


Read the information in Section 7—Configuring Ethernet, Chapter 2—“Configuring Ethernet Equip-ment,” page 7-9.


Hardware

The information in this section strictly pertains to the following Ethernet cards:NGE• GBE4-FE16-TX• GBE2T-GBE2F-FE16-TX

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

Gigabit Ethernet • 10GbE• GBE-10

EOPDH • GBE4-FE16-TX-EoPDH• GBE2T-GBE2F-FE16-TX-EoPDH




Software





Traverse Provisioning Guide, Section 3—Creating Protection Groups, Chap-ter 4—“Creating Equipment Protection Groups,” page 3-21


Traverse Provisioning Guide, Section 7: Configuring EthernetSearch for Services

Search for Services




Read the Ethernet Services definitions in this chapter. Know the endpoints and attributes of each service.

• Line Services, page 7-120• Bridge Services, page 7-121• Aggregation Bridge Services, page 7-122

Table 7-39 Ethernet Service Requirements (continued)



Step Procedure




2

3 45


Chapter 10 Ethernet ServicesSearch for Services




• 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 (p0). This refers to the OC-48 interface on the backplane.









Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetSearch for Services









Step Procedure

6


Chapter 10 Ethernet ServicesConfigure Ethernet Services

Configure Ethernet Services

Use the following procedure to help create Ethernet services.

Table 7-41 Configure Ethernet Services

Step Procedure


2 In Shelf View, add the Ethernet service.

Figure 7-58 Select Ethernet on the Service Tab

a. Click the Service tab and select Ethernet.b. Click Add to display the Creating Ethernet Service dialog box.

2a


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Ethernet Services

3 On the Creating Ethernet Service dialog box, enter the general information for this service.

Figure 7-59 Create Ethernet Line Services

• Name: Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

• Description: Enter the description of the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

• Customer: Select a customer name from the drop-down list box.

4 In the Type parameter, select the type of Ethernet service:• Bridge• Line • Aggregate Bridge • Multipoint ECC (use only with EOP ports)

If you selected Bridge, Line or Aggregate Bridge for the type of Ethernet service, continue to Step 5. If you selected Multipoint ECC for the type of Ethernet service, skip to Step 7.

Table 7-41 Configure Ethernet Services (continued)

Step Procedure

3

5

4



5 Select the VLAN configuration type for the port types on this service.

Figure 7-60 VLAN Configuration

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.

Note: The Untagged and Priority tagged packets can be included as part of the CE-VLAN list by using VLAN ID 0.This can be entered as VLAN IDs (0, 1-15, 18, 21-24, 19).

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


Step Procedure



6 In the Port Configuration table, select the correct endpoints for the port members in this service. The endpoints must be on the same Ethernet card. If C-VLAN ID Preservation was not selected (see previous step), enter different VLAN IDs for each customer-tagged port member.

If Use same S-VLAN ID was not selected (see previous step), enter different VLAN IDs for each service-tagged port member.

7 Enter the IP address and subnet mask IP address of the Ethernet Control Channel (ECC) being created.

Figure 7-61 Create Multipoint ECC Ethernet Service

IP address: Enter the IP address of the Traverse interface that directs IP packets to and from the CPE device.

Subnet mask: Enter the subnet mask for your system. When used with the IP address entered in the IP address field, a direct connection is created that is advertised to all nodes in the Traverse system with OSPF over DCC.

Note: The ECC and IP address for the CPE must be in the same subnet range. The IP address must be unique; it cannot match the IP address of the CPE.

Member port priority: Indicates the value of the 802.1Q priority bit field of each packet sent from the multipoint ECCI to a CPE.

Card: Select the EoPDH card to associate with the ECC.


Step Procedure



8 If required, assign a configured classifier or a policer to each service port.A single policer can be assigned to multiple service ports. All flows on those service ports will be policed together and will compete for the bandwidth being policed. • Classifier: Select a classifier for this service port. See

Section 7—Configuring Ethernet, Chapter 12—“Classifying and Prioritizing Packets,” page 7-159 for more information on classifiers.

• Policer: Select a policer for this service port. See Section 7—Configuring Ethernet, Chapter 13—“Policing,” page 7-165 for more information on policers.

9 Configure the Advanced parameters of each service port. Click the Advanced column in the Endpoint table for this service port.

Figure 7-62 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: If this port is Service-tagged, specify the system behavior regarding the priority field on packets being transmitted out this port.– Mark (default): The system sets the priority field in the VLAN tag

as a result of the classifying and policing functions.– Copy: The system copies the priority value in the customer VLAN

tag to the priority field in the service provider VLAN tag if the transmit. If the packet was untagged, the system uses the value specified in the Default Priority Bit parameter.

• MAC Addresses: 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.

• Service Port PM: Select the performance monitoring template to be used. The default is default.

10 Click Done to close the Advanced Parameters dialog box.


Step Procedure



11 Click Apply to create the service and return to the services list on the Service tab in the main screen.

12 The Configure Ethernet Services procedure is complete. Continue to Section 4—Creating ADM Services, Chapter 2—“Common Procedures for Services,” page 4-13.


Step Procedure



Chapter 11Ethernet Traffic Management

Introduction This chapter contains the following topics:• Supported Ethernet Cards, page 7-147• Ingress Traffic Flow, page 7-148• Egress Traffic Flow, page 7-149• Ethernet Traffic Management Description, page 7-150• Managing Traffic on EOP Ports, page 7-152• Maximum Information Rate, page 7-152• Pause Control, page 7-152• Queuing Policy, page 7-153• Queuing Policy and Spanning Tree BPDUs, page 7-155• Marking Packets, page 7-156• Configure Marking, page 7-157

Supported Ethernet Cards


Cards Card Types







Traverse Provisioning Guide, Section 7: Configuring EthernetIngress Traffic Flow


Ingress Traffic Flow

This flow chart describes system traffic management behavior once it has received an Ethernet frame. The ingress Ethernet frame can be a physical port or an EOS port based on the flow of traffic. If a classifier is applied to a physical port, the traffic is classified before being put on the network. Similarly, if a classifier is applied to an EOS port the traffic will be classified before being sent to the physical port.

Figure 7-63 Ingress Traffic Flow

N

Y

N Green orYellowPackets

TR-00008

Forwarded basedon forwarding

rules of service

Policer forservice?

Conform tobandwidth

profile?

Packet dropped

EgressPort(s)

Y

Red Packets

Forwarded to one or moreports based on service type

Determine priority(VLAN tag or

configured priorityfor untagged

packets)

Classify packet.Determine CoS and

IDP

Packet DroppedSend PAUSE

Frame

Packet Received

Well-FormedPacket?

Excess PacketsDropped

Y Y

N

Determine servicebased on Tagging

type of ingressport and VLAN tag

Is arrival rate> MIR and is PAUSE

enabled?(NGE, NGE Plus, EoPDH

only)

N

Chapter 11 Ethernet Traffic ManagementEgress Traffic Flow

Egress Traffic Flow

This flow chart describes system traffic management behavior before it transmits the packet.

Figure 7-64 Egress Traffic Flow

From ingressport

Is this a Service-tagged port? Marking

RandomEarly

Discard?Packet dropped

Shaping

Scheduling

PacketTransmitted

For every egress portselected by theforwarding step

TR-00009


Traverse Provisioning Guide, Section 7: Configuring EthernetEthernet Traffic Management Description

Ethernet Traffic Management Description

The steps in this table describe system traffic management behavior and reference the following flow charts:• Ingress Traffic Flow, page 7-148• Egress Traffic Flow, page 7-149

Traffic management on EOP ports can easily become congested. For information on effectively manage traffic on EOP ports, see Managing Traffic on EOP Ports, page 7-152.

Table 7-42 Ethernet Traffic Management Flow

Step Reference

1 Receiving and Checking. A packet is received from a physical Ethernet port, an EOS port, or an EOP port.

The system performs a Layer 2 check (CRC check, frame size, etc.). Bad packets are counted and dropped. Good packets are counted.

n/a

2 Ingress shaping. The system calculates the current arrival rate for this port. If it exceeds the configured maximum allowed arrival rate for the ingress port, send a PAUSE frame.

Maximum Information Rate, page 7-152

3 Determine Service. The system references the Tagging parameter of the ingress port. Based on Tagging parameter and the presence (or absence) of VLAN tag in the packet, the system determines to which service the packet belongs.

If the service type is in a bridge service, perform MAC learning on the packet’s Source MAC address for this port and service.

Section 7—Configuring Ethernet, Chapter 2—“Configuring Ethernet Equipment,” page 7-9

Section 7—Configuring Ethernet, Chapter 10—“Ethernet Services,” page 7-119

4 Classifying Packets. The system references the classifier for this ingress port for the service to which the packet belongs. Then, the system pro-cesses the Priority in the packet field using the clas-sifier to set class of service (CoS) and initial drop precedence (IDP).

Chapter 12—“Classifying and Prioritizing Packets,” page 7-159

5 Policing Packets. The system references the policer for this ingress port in this service (if any) and uses the CoS (determined in Step 4) to deter-mine if the packet conforms to the set bandwidth profile.

The system determines the final drop precedence: green, yellow, or red. The system immediately drops red packets (out-of-profile) and forwards green and yellow.

Chapter 13—“Policing,” page 7-165

6 Forwarding Packets. The system selects one or more egress ports based on the service type, a list of ports in the service, and possibly the packet’s Desti-nation MAC address.



Chapter 11 Ethernet Traffic ManagementEthernet Traffic Management Description

7 Modifying Packets. The system references the Tagging parameter of the egress port. Based on Tagging parameter and the presence or absence of VLAN tag in the packet, the system performs VLAN modification if necessary.


8 Marking Packets. If the egress port is Ser-vice-tagged, the system encodes the class of service and final drop precedence into the Priority field of the service provider tag.

Marking Packets, page 7-156

9 Dropping Packets (or Random Early Discard). The system uses the queuing policy and the class of service to select an output queue for the packet on the egress port.

Based on that queue’s RED curve, current length, and the packet’s final drop precedence, the system either queues or drops the packet.

Chapter 14—“RED Congestion Control,” page 7-175

10 Shaping Traffic. If the Queuing Policy of the egress port is FIFO and FIFO Shaping is enabled, use the Shaping Rate to delay the packet until its time.

If the Queuing Policy is WFQ, shape the traffic according to the provisioned weights for the queues.

Queuing Policy, page 7-153

11 Scheduling Packets. When the packet reaches the front of the correct output queue, the port has band-width to transmit a packet, and the Queuing Policy for the egress port says the next packet should come from this output queue, the system transmits the packet.

Queuing Policy, page 7-153

12 The system transmits the packet based on the for-warding rules of the service.


Table 7-42 Ethernet Traffic Management Flow (continued)

Step Reference


Traverse Provisioning Guide, Section 7: Configuring EthernetManaging Traffic on EOP Ports

Managing Traffic on EOP Ports

Transmission times on EOP ports are much slower than other types of Ethernet links. This could cause EOP links to easily become severely congested if traffic on the other types Ethernet links increases significantly.

The default port and service values on the Traverse system cause all traffic to compete for the same bandwidth. The defaults cause the outbound EOP traffic (from the Traverse network to the EOP link) to congest the egress queues of the EOP link. (Drops in traffic will appear on a service PM report in the TX RED DISCARDS counter.)

If low bandwidth, VOIP, or in-band management (i.e., multipoint-ECC) traffic is to occur on an EOP link that is vulnerable to congestion, Force10 recommends applying non-default traffic management to avoid unacceptable loss rates during congestion.


supports the default service COS of 1.• Classify Ethernet services that carry loss sensitive traffic (such as VOIP) as COS 1

or 2. In band management traffic is fixed at COS 1.• Classify all other Ethernet services at lower COS levels, such as COS 3 or 4.

Maximum Information Rate

Use the Max Info Rate (Mbps) parameter on each NGE, NGE Plus, or EoPDH Ethernet port or ports in a link aggregation group to specify the maximum ingress data rate (in Mbps) allowed for that port.

To configure the Max Info Rate parameter, see Section 7—Configuring Ethernet, Chapter 2—“Configuring Ethernet Equipment,” Configure Ethernet Port Parameter Values, page 7-18.

If the PAUSE control 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 control 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.

Pause Control Auto-negotiation is a process described in IEEE 802.3 that allows two devices on an Ethernet segment (link partners) to determine mutually agreeable settings for speed, duplex, and flow control. The Traverse supports auto-negotiation for optical GBE, electrical GBE, and Fast Ethernet ports on NGE, NGE Plus, and EoPDH cards. By default, the auto-negotiation feature is always enabled.

The following sections detail how the system sends and receives PAUSE frames.

On Sending PAUSE frames. Whenever the Traverse receives a PAUSE frame from an Ethernet port, it responds by suspending its transmission of packets on that port for a short period. Transmitting a PAUSE frame transmission mechanism is a means for ingress shaping or limiting the incoming flow of traffic from CPE devices to a provisioned rate on the port.


Chapter 11 Ethernet Traffic ManagementQueuing Policy

The Traverse generates a PAUSE frame only when the rate of incoming traffic exceeds the maximum information rate (MIR) limit configured for the port. The MIR is a data rate limit assigned to a physical port.

The system sends an IEEE 802.3 PAUSE frame with a timer on an Ethernet port whenever the rate at which packets arrive on the port exceed the ports’ configured MIR. If a large burst arrives which would exceed the configured MIR, the system sends a PAUSE frame during the burst, reducing the packet arrival rate back down to the configured rate.

The default value for the MIR on each port type is the maximum data rate for that port. For example, ETH100TX port has a default MIR of 100 Mbps. A GBE port has a default value of 1000 Mbps.

The system invokes flow control early enough so there is sufficient buffer space to hold packets that may arrive from the Ethernet port prior to the link partner’s having responded to the PAUSE frame. For purposes of buffer space calculation, the system assumes the link partner operates according to IEEE 802.3, section 31B.3.7.

If the system drops packets because of no buffer space in spite of having invoked flow control, it counts those packets in the RX DISCARD counter of the port on which the packet arrived.

Flow control operates independently for all Ethernet ports. That is, invoking flow control on one Ethernet port has no effect on the flow of traffic on any other Ethernet port.

To remove flow control, the system sends an IEEE 802.3 PAUSE frame with a timer set to zero.

On Receiving PAUSE Frames. If pause control is enabled for the port and the system receives a PAUSE frame on the port, the system does not transmit another packet to the port until it receives a PAUSE frame with a timer of zero on that port. However, the system finishes transmitting any packet being transmitted on a port when a PAUSE frame is received on that port.

When pause control is disabled on a port, the system simply removes the PAUSE frame from the data stream and continues to transmit packets accordingly.

Queuing Policy Queuing policy is a mechanism for specifying the treatment of packets that are queued to be transmitted on an egress port. The NGE, NGE Plus, 10GbE, GbE-10, and EoPDH cards support up to four queues that correspond directly to classes of service (CoS1, CoS2, CoS3, CoS4). Packets of the same CoS are queued on the same queue.

Queuing policy for an Ethernet port, a link aggregation group (LAG), an EOS port, or an EOP port is determined by the Queuing Policy parameter. Configure the Queuing Policy of an Ethernet port, LAG, EOS port, or EOP port during the configuration process.

Note: Use caution when setting the queueing policy on EoPDH cards to avoid traffic management problems. For more information, see Managing Traffic on EOP Ports, page 7-152.

• Section 7—Configuring Ethernet, Chapter 2—“Configuring Ethernet Equipment,” Configure Ethernet Port Parameter Values, page 7-18


Traverse Provisioning Guide, Section 7: Configuring EthernetFIFO

• Section 7—Configuring Ethernet, Chapter 3—“Link Aggregation,” Create a Link Aggregation Group, page 7-41

• Section 7—Configuring Ethernet, Chapter 4—“Ethernet Over SONET/SDH (EOS),” Creating EOS Ports, page 7-58

• Section 7—Configuring Ethernet, Chapter 11—“Ethernet Traffic Management,” Managing Traffic on EOP Ports, page 7-152

In the Queuing Policy parameter, specify how the queues are managed. Use one of the following policies: • FIFO, page 7-154• Priority, page 7-154• Weighted Fair Queuing, page 7-154

FIFO First-in-first-out. Use this queuing policy to schedule all packets for transmission based on the FIFO algorithm. All traffic uses CoS1 or queue 1. Optionally, configure whether shaping should be employed using the following parameters.

Note: On EoPDH cards, Force10 recommends using WFQ or PRIORITY for the Queueing Policy to avoid traffic management problems under some conditions. For more information, see Managing Traffic on EOP Ports, page 7-152.

• FIFO Shape Enable. If the value in Queuing Policy is FIFO, specify if the system will use the number in the FIFO Shaping Rate parameter to shape the traffic being transmitted onto the port.

• FIFO Shaping Rate. If the FIFO Shaping Rate is enabled, specify a number between 1 and 1,000 Mbps for NGE, NGE Plus, and EoPDH cards. For 10GbE and GbE-10 cards, specify a number between 1 and 10,000 Mbps; the default for the 10GbE is 10,000, the default for the GbE-10 is 1,000.

Priority Use this queuing policy to schedule all packets for transmission based on strict priority, using three priorities: high, medium, low. Highest priority traffic uses CoS1 (queue 1). Medium priority traffic uses CoS2 (queue 2). Low priority traffic uses CoS3 (queue 3).

Note: Force10 recommends using this queueing policy on EoPDH cards to avoid traffic management problems on EOP ports. For more information, see Managing Traffic on EOP Ports, page 7-152.

Higher priority queues always send queued packets. Only when all higher priority queues are empty does the scheduler look for a packet on a lower priority queue. Typical application is voice vs. data: voice requires low latency and should get absolute priority over data, i.e., whenever there is a voice packet, the system picks it over a data packet. Note that lower priorities can be starved (i.e., if voice traffic completely fills the output port, data traffic is never transmitted).

There are no additional parameters to configure to use with Priority queuing.

Weighted Fair Queuing

Use 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 (four queues) and the


Chapter 11 Ethernet Traffic ManagementQueuing Policy and Spanning Tree BPDUs

guarantees are specified as weights. If the value in Queuing Policy parameter is WFQ, specify the weights in the four WFQ CoS Weight {1 | 2 | 3 | 4} parameters.

Note: Force10 recommends using this queueing policy on EoPDH cards to avoid traffic management problems on EOP ports. For more information, see Managing Traffic on EOP Ports, page 7-152.

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




The scheduler uses these weights to allocate bandwidth on the port to each class of service. When there is no congestion, every CoS sends all queued packets. For example: weights 5, 25, 10, 1. (41 units). In times of congestion, CoS 1 traffic is guaranteed to get at least 12.2% (5/41) of bandwidth on the port. CoS 2 is guaranteed 62.5% (25/40). CoS 3 is guaranteed 25% (10/40). CoS 4 is guaranteed 2.5% (1/40).

Any bandwidth that is guaranteed for a queue but not actually needed by that queue is available for any other queue to use. For example, CoS 3, though guaranteed an allocation of 25%, is only transmitting enough data to use up 5%. That leaves 20% of the bandwidth of the port available for other queues to use. In this case, the scheduler distributes that unclaimed 20% approximately evenly among any queues that are already using up their entire guarantee. In particular, CoS 4, which has no guarantee, gets some of the unclaimed bandwidth from CoS 3.

Queuing Policy and Spanning Tree BPDUs

Spanning tree BPDUs (bridge protocol data units) prevent loops in network topologies used for Private LAN and Virtual Private LAN applications. When RSTP is enabled on an EOS port and there are activated bridge services using that EOS port, the system sends BPDUs on that port.

Therefore, BPDUs require being queued on the queues for that EOS port. The Queuing Policy parameter of the EOS port determines how they are queued.

If Queuing Policy is either FIFO or PQ. If the Queuing Policy for this EOS port is either FIFO or PQ, there is a separate, high-priority queue for BPDUs that is not used for customer packets. The scheduler sends spanning tree BPDUs on the port before service data. There is no contention between the BPDUs and the service data queued on that EOS port.


Traverse Provisioning Guide, Section 7: Configuring EthernetMarking Packets

If Queuing Policy is WFQ. If the Queuing Policy for this EOS is WFQ, then all service data sent to the EOS is queued on one of four service data queues. However, there is no separate system queue available for exclusive use of RSTP packets. The system uses CoS4 (queue 4).

Using CoS4 poses the following limitations:• BDPU packets may get queued behind lots of CoS 4 service packets, leading to

undesirably long delay.• If CoS 4 is assigned a Weight of 1, then packets of this CoS are transmitted only

when other CoSs with weights other than one are not using their weighted proportion of the available bandwidth. If other CoSs on this EOS port are using all of their weighted proportion, the scheduler for this EOS port will always select packets from those CoSs, leading to undesirably long delay for CoS 4 packets, including RSTP.

Therefore, if WFQ is the Queuing Policy and RSTP is enabled for this EOS port in an activated bridge service, use the following guidelines:• Ensure that the WFQ Weight CoS 4 parameter has a weight of more than one.

Force10 recommends setting weights on the EOS port such that the value in the WFQ Weight CoS4 parameter is at least 5% of the total.

• Ensure that the amount of CoS 4 service data queued for the EOS port is always small (or one). For example, use Classifiers on the service ports of the bridge service that do NOT classify packets into CoS4. Or, configure very small RED thresholds for the CoS 4 queues. (BPDUs are always queued without regard to RED thresholds, so setting small RED thresholds will not impede the transmission of BPDUs.)

Marking Packets

Marking is used to convey the results of a policing operation on a packet to other Ethernet cards that will process the same packet in the service provider’s network. Marking uses the 802.1p bits in the service provider VLAN tag. Specifically, the system uses the two most significant bits of the Priority field to encode the CoS and the least significant bit of the Priority field to encode the color.

Marking allows traffic to be classified and policed at the ingress node of a service provider’s network. Then, the results of those steps (CoS and color) are carried along as the packet goes through the service provider network. Marking allows traffic originally colored yellow at its ingress node to be the first candidate for dropping at subsequent aggregation points.

The system only marks packets if they transmit on a Service-tagged port. The system will always mark those packets in a way that reflects the results of the classification and policing steps. The system does not mark packets transmitting on a Port-based or Customer-tagged port.


Chapter 11 Ethernet Traffic ManagementConfigure Marking

Whenever the system sends a packet on a Service-tagged port, the system encodes the results of the policing step into the 802.1p field of the packet’s service provider VLAN tag, according to the following table.

The system sets the Priority bits in the VLAN tag as a result of the classifying and policing functions when the transmit port is Service-tagged and the Marking Bit parameter is set to Mark.

The system copies the priority value in the customer VLAN tag to the priority bits in the service provider VLAN tag if the transmit port is Service-tagged and the Marking Bit parameter is set to copy.

If the packet arrives with no VLAN tag (untagged), the system uses the provisioned values for untagged packets in the priority field of the service provider VLAN tag.

Configure Marking

Use the Marking Bit of the service port member to configure marking.

See Section 7—Configuring Ethernet, Chapter 10—“Ethernet Services,” Configure Ethernet Services, page 7-141.

Table 7-43 System Marking Service-tagged Ports

Policed CoS Policed Drop Precedence Resulting 802.1p

1 Green 0

1 Yellow 1

2 Green 2

2 Yellow 3

3 Green 4

3 Yellow 5

4 Green 6

4 Yellow 7


Traverse Provisioning Guide, Section 7: Configuring EthernetConfigure Marking



Chapter 12Classifying and Prioritizing Packets

Introduction The classification process establishes two things about a packet: its class of service (CoS) and its initial drop precedence (IDP).

This chapter contains the following topics:• Class of Service, page 7-159• Initial Drop Precedence, page 7-160• Default Classifier Template, page 7-160• Priority-based CoS, page 7-160• Port-Based CoS, page 7-161• Untagged Packets and Classification, page 7-161• Queuing Policy and Class of Service, page 7-162• Classifier Guidelines, page 7-162• Create Classifier Templates, page 7-163

Class of Service

Ethernet class of service refers to three bits within a four byte IEEE 802.1Q (VLAN) header used to indicate the priority of the Ethernet frame as it passes through a switched network. The priority bits in the IEEE 802.1Q header are referred to as the IEEE 802.1p bits. These three priority bits allow for eight classes (four classes with two colors for each class).

The purpose of classifying traffic into different classes is to control how traffic is managed when there is congestion on an egress port. There is a relationship between the classification step, which takes place at ingress ports, and the RED and Queuing steps, which take place at egress ports. The service provider must carefully coordinate the configuration of the mechanisms that manage these steps and design and implement a coherent class of service policy for the network.

Upon arrival, the system looks at the 802.1p bits in the packet’s VLAN tag to assign both a class of service and an initial drop precedence to the packet. If the packet is untagged, it receives a default class of service and initial drop precedence.

On the Traverse system, there are four possible classes of service that map directly to four queues. See Chapter 11—“Ethernet Traffic Management,” Queuing Policy, page 7-153 for the details on queuing and queuing policies.


Traverse Provisioning Guide, Section 7: Configuring EthernetInitial Drop Precedence

Initial Drop Precedence

It is possible that when a packet arrives at an ingress port, the customer equipment has already prioritized it to indicate some level of conformance within the customer’s own network. That is, the customer has encoded information about the packet’s conformance into the priority (802.1p) field. If the packet arrives on the port already with a priority, then the service provider should take that into consideration when the packet passes through the service provider’s bandwidth profile. That is, if the customer has already marked a packet yellow (high drop precedence), then even if the packet appears to conform to the service provider’s bandwidth profile, the packet should still be a candidate for dropping if there is congestion.

The term initial drop precedence (IDP) refers to this pre-prioritizing. The classification step reads the packet’s markings to set its IDP. The policing step (actually running the packet through the Traverse bandwidth profile) can modify that IDP to come up with a final drop precedence value.

Default Classifier Template

Defining a classifier template requires knowing the Queuing Policy of the egress port. See Chapter 11—“Ethernet Traffic Management,” Queuing Policy, page 7-153 for information on queuing policies.

Create a classifier on the TransNav server using a combination of classes of service (queues) and the initial drop precedence of the packet as it arrives on the port.

Priority-based CoS

You can configure Ethernet services on the Traverse system for a priority-based class of service. For example, a service purchased by Company A transports packets from several departments (Legal and Finance) within the company. The service provider and Company A agree that the Legal department’s traffic requires better service—more of the available bandwidth when there is congestion—than the Finance department’s traffic. The Legal and Finance departments would have different classes of service.

In another example, Company B might design a service where mixed voice and data traffic arrives on the same port. The voice traffic should be handled in one way (small throughput but with low latency and jitter), and the data traffic another (high throughput but with higher acceptable latency and jitter). Voice and data would have different classes of services.

Table 7-44 Default Classifier Template

Priority Bits Class of Service IDP

Priority 0 1 Green

Priority 1 1 Green

Priority 2 1 Green

Priority 3 1 Green

Priority 4 1 Green

Priority 5 1 Green

Priority 6 1 Green

Priority 7 1 Green


Chapter 12 Classifying and Prioritizing PacketsUntagged Packets and Classification

Both Company A and Company B would mark every packet’s traffic class by assigning a specific value to the Priority field (also called “802.1p bits”) in each Ethernet frame’s header. That is, Company A would use the Priority field to identify the department that generated the traffic. Company B would use the Priority field to identify the type of application (voice or data) that generated the traffic. In each case, the service provider would use a classifier to look at the priority value on each arriving packet and map that to a CoS.

Port-Based CoS

You can also configure Ethernet services using a port-based class of service. A service provider may have two customers –Company C and Company D – whose traffic arrives on different ports and is carried over the network on the same transport connection. Perhaps Company C pays more for its service, so Company C packets should get more of the shared transport capacity than packets belong to Company D. Each company would have different CoS defined for their traffic.

In this case, the service provider could use different classifiers on the two customers’ ports. The classifier on the Company C port assigns all packets to one CoS. The classifier on Company D port assigns all packets to a different CoS. This classifier would not interpret the Priority field of the packet at all.

Untagged Packets and Classification

Untagged packets do not have VLAN tags and therefore contain no 802.1p bits. However, these packets can still be assigned a CoS and IDP because they may end up competing for resources on a congested output port.

Use the Default Priority Bit parameter on an Ethernet service member to assign a priority to untagged Ethernet frames arriving on a member port. By default, the system assigns an 802.1p value for untagged packets of priority 1. See Section 7—Configuring Ethernet, Chapter 10—“Ethernet Services,” Configure Ethernet Services, page 7-141 to configure this parameter.

See the following topics for information on how the system processes untagged packets:• Chapter 10—“Ethernet Services,” Mix of Port-based and Service-tagged Ports

in Service, page 7-128• Chapter 10—“Ethernet Services,” All Ports in Service are Customer- tagged,

page 7-129• Chapter 10—“Ethernet Services,” Mix of Customer- tagged and Service-tagged

Ports in Service, page 7-131• Chapter 10—“Ethernet Services,” All Ports in Service Tagged as Service-

tagged, page 7-133


Traverse Provisioning Guide, Section 7: Configuring EthernetQueuing Policy and Class of Service

Queuing Policy and Class of Service

Every egress port has a Queuing Policy that determines how many classes of services the port can differentiate, and how those classes are treated with respect to each other. Depending on the egress port’s Queuing Policy, the Traverse supports different numbers of Classes of Service: • FIFO: one class• Priority Queuing: up to three classes• Weighted Fair Queuing: up to four classes

See Chapter 11—“Ethernet Traffic Management,” Queuing Policy, page 7-153 for discussion about queuing policy.

Classifier Guidelines

Create a classifier on the TransNav server (classifier templates). The TransNav management system supports up to 12 classifier templates.

Each classifier template maps each possible 802.1p value (0 through 7) to a class of service and initial drop precedence pair. The default classifier template maps every 802.1p value to CoS=1, IDP=green. See Default Classifier Template, page 7-160.

Defining a classifier template requires knowing the Queuing Policy of the egress port. See Chapter 11—“Ethernet Traffic Management,” Queuing Policy, page 7-153 for information on queuing policies.

It is possible to assign different classifier templates to different ports in the same service for NGE and EoPDH cards. On 10GbE and GbE-10 cards, assign the same classifier template to all service ports that share a port.

It is possible to change the assignment of classifier template to a port in a service, while that service is activated. The new template takes effect with no interruption to the service.

It is possible to edit a classifier template to change the mapping of 802.1p values to (CoS, IDP), and to synchronize the edited template. The new values takes effect with no interruption to any activated services that use the template.

You cannot delete a classifier template if there are any provisioned or activated Ethernet services that currently use or are provisioned with that classifier template.


Chapter 12 Classifying and Prioritizing PacketsCreate Classifier Templates

Create Classifier Templates

Use this procedure to help create a classifier template on the TransNav server.

Table 7-45 Create a Classifier Template

Step Procedure

1 From the Admin menu, click Classifiers. The Classifiers dialog box appears.

Figure 7-65 Classifiers Dialog Box

2 Click Add to add a new classifier to the classifier list. The Classifier Configuration dialog box appears.

Figure 7-66 Classifier Configuration Dialog Box

3 Enter a name for the classifier in the Name field. Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.


Traverse Provisioning Guide, Section 7: Configuring EthernetCreate Classifier Templates

4 Configure the class of service (CoS) and initial drop precedence (IDP) for each priority level.

Priority {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

5 Click OK to close the dialog box and return to the Classifiers dialog box.

6 In Synchronize Template dialog box, click Yes to propagate new classifier template information to all nodes in the network.

Figure 7-67 Synchronize Template Dialog Box

7 Click Done to close the Classifier dialog box and return to the main GUI screen.

8 The Create a Classifier Template procedure is complete.

To assign a classifier to a service port, see Section 7—Configuring Ethernet, Chapter 10—“Ethernet Services,” Configure Ethernet Services, page 7-141.

Table 7-45 Create a Classifier Template (continued)

Step Procedure



Chapter 13Policing

Introduction This chapter contains the following topics:• Policing Packets, page 7-165• Bandwidth Profiles, page 7-166• Default Bandwidth Profiles, page 7-166• Example Bandwidth Profiles, page 7-166• Policers, page 7-169• Policing Algorithm, page 7-170• Guidelines to Create a Policer, page 7-171• Create Policers on the Ethernet Card, page 7-172

Policing Packets

Policing is the process of measuring a stream of traffic against a bandwidth profile to determine conformance of each packet with that profile. By the time a packet is presented to the Policer, it has already been assigned an initial drop precedence value, as described in the Classification section. The result of policing will be to assign to each packet a final drop precedence value. This value represents the conformance of the packet to the profile.

Drop precedence, or conformance, is used in the random early discard (RED) queuing step. When there is congestion on an output port (packets are forwarded to a port at a rate that exceeds the transmission rate of the port), then packets start to back up on the queues for that port. RED decides whether each individual packet should be queued or dropped, depending on the drop precedence value. Packets that do not conform to CIR but conform to PIR (yellow, or high drop precedence) should be dropped before the packets that conform to CIR (green, or low drop precedence).

Policing uses a variant of an algorithm called “two rate three color marker” and is implemented through two mechanisms: policers and bandwidth profiles. • Bandwidth Profiles, page 7-166. A bandwidth profile is a set of values that define

the rate and size of a pair of token buckets. • Policers, page 7-169. A policer is a pair of token buckets.

A bandwidth profile is a sort of template for making a pair of buckets. A policer as the actual bucket pair that results from following the instructions. The distinction is important, since the two types of objects are constructed and used in very different ways.


Traverse Provisioning Guide, Section 7: Configuring EthernetBandwidth Profiles

Bandwidth Profiles

A bandwidth profile has four values:• Committed Information Rate (CIR). The average rate (in Mbps) up to which

Traverse will consider ingress frames to have low drop precedence (green).• Committed Burst Size (CBS). The size (in KB) that limits the maximum number of

bytes available for a burst of ingress frames to conform to CIR.• Peak Information Rate (PIR). The average rate (in Mbps) up to which Traverse will

consider ingress frames to have high drop precedence (yellow), and above which Traverse will automatically drop ingress frames.

• Peak Burst Size (PBS). The size (in KB) that limits the maximum number of bytes available for a burst of ingress frames to conform to PIR.

A service provider can use the bandwidth profile as part of building a service level agreement. For example, you can overprovision an egress port by admitting more CIR-compliant traffic than the egress port can actually carry, counting on statistical multiplexing (not all ingress sources will send at the CIR at the same time) to get more efficient use of the egress port bandwidth.

Default Bandwidth Profiles

Bandwidth Profiles are built and distributed using templates in the user interface. From Map View or Shelf View, click the Admin menu, then click Bandwidth Profiles.

The minimum value for each parameter is 0 Mbps. However, for the following cards NGE, NGE Plus, 10GbE, GbE-10, and EoPDH, the maximum Committed and Peak Burst Size parameters of the bandwidth profiles depend on the associated Committed or Peak Information Rates shown in the table below. The effect of using this bandwidth profile for a traffic flow would be to consider that all packets conform to CIR (green). That has the same effect as doing no policing at all. The maximum number of bandwidth profiles is 116.

Example Bandwidth Profiles

Each bandwidth profile can be used many times to create many different policers. Typically, a service provider will define a set of service offerings, create a bandwidth profile for each, and then sell those service offerings to many customers. The following table contains a set of service offerings. Only the rates are shown (burst sizes will be provisioned too):

Table 7-46 Sample Bandwidth Profiles

Package Name CIR PIR

Gold 100 100 Mbps 100 Mbps



Silver 50 50 Mbps 500 Mbps




Chapter 13 PolicingExample Bandwidth Profiles

The Gold packages have the same value for CIR and PIR. Everything up to CIR is colored green. Because CIR and PIR are the same, this bandwidth profile does not color anything yellow. Green packets are more likely to be queued for the egress port than yellow packets that may be submitted by a service running a different bandwidth profile. In a Gold package, any arriving traffic that exceeds the PIR is unconditionally dropped, whether or not there is available bandwidth on the egress port.

The Silver packages have smaller committed rates, but larger excess rates. Silver traffic that conforms to the CIR (green) is treated just like traffic from the Gold packages. Silver traffic that conforms to PIR (yellow) is accepted, but may be dropped if the queue is backed up. If the egress port is free or only slightly backed up at the moment, the yellow traffic will be queued along with the green. When the egress port is lightly loaded, a “Silver 50” customer can get up to 200 Mbps. As the egress port’s use increases, yellow traffic is increasingly dropped instead of queued. When the egress port is saturated, all of the yellow traffic will be dropped and the “Silver 50” customer will be getting only 50 Mbps.

The Best Effort packages have no committed rate. In Best Effort Small, up to 50 Mbps of the customer’s traffic is colored yellow and anything over 50 Mbps is dropped. Yellow traffic gets through only if there is available bandwidth. If there is enough green traffic to fill up the egress port, all of the yellow traffic will get dropped. Best Effort Large is similar except that 1,000 Mbps of the customer’s traffic – up to full line rate on a GbE port – is conditionally accepted (yellow). Sometimes all of this customer’s traffic will get through; sometimes all of it will be dropped.

Best Effort Small 0 Mbps 50 Mbps

Best Effort Large 0 Mbps 1000 Mbps

Table 7-46 Sample Bandwidth Profiles (continued)

Package Name CIR PIR


Traverse Provisioning Guide, Section 7: Configuring EthernetCreate a Bandwidth Profile

Create a Bandwidth Profile

Use this procedure to create a bandwidth profile on the TransNav server.

Table 7-47 Create a Bandwidth Profile

Step Procedure

1 From the Admin menu, click Bandwidth Profiles. The Bandwidth Profiles dialog box appears.

Figure 7-68 Bandwidth Profiles Dialog Box

2 Click Add to add a new bandwidth profile to the bandwidth profile list. The Bandwidth Profile Configuration dialog box appears.

Figure 7-69 Bandwidth Profiles Configuration

3 Enter a name for the classifier in the Name field. Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

4 Enter the following rates and burst sizes:• CIR. Committed information rate. For NGE and EoPDH cards, enter a

value between 0 and 1000 Mbps; for 10GbE and GbE-10 cards, enter a value between 0 and 10,000 Mpbs. The default value is 1000 Mbps. Provisionable in increments of 1 Mbps.

• CBS. Committed burst size. For NGE and EoPDH cards, enter a value between 0 and 1,000 KB. For 10GbE and GbE-10 cards, enter a value between 0 and 16,000 KB. The default value is 256 KB. Provisionable in increments of 1 KB.


Chapter 13 PolicingPolicers


Policers Policing is the act of measuring a flow of packets, coloring packets green or yellow (or dropping them) in accordance with a bandwidth profile.

Policing is optional. By default, when you add a port to a service, the flow of packets on that service-port is not policed. That means that the color that was set for a packet by the service port’s classifier (by default, this is green) is preserved.

Traverse performs policing by class of service. When packets arrive at a policer, each one has already been assigned a class of service. Each packet is policed according to the bandwidth profile for its class of service.

Note that this means that it is not possible to classify traffic into two classes—one for voice and one for data—and then police the aggregate of the two classes. To queue voice and data separately, which will be a common application, police them separately. A single policer can be assigned to multiple service ports. All flows on those service ports will be policed together and will compete for the bandwidth being policed.

5 In Synchronize Template dialog box, click Yes to propagate new bandwidth profile template information to all nodes in the network.

Figure 7-70 Synchronize Template Dialog Box

6 Click Done to close the Classifier dialog box and return to the main screen.

7 Repeat Steps 1 to 6 for as many bandwidth profiles are required in the network.

8 The Create a Bandwidth Profile procedure is complete.

Table 7-47 Create a Bandwidth Profile (continued)

Step Procedure

Traverse Provisioning Guide, Section 7: Configuring EthernetPolicing Algorithm

Policing Algorithm

The system uses a version of the classic “two-rate three color marker” algorithm described in RFC 2698. In this algorithm, a policer is a set of two token buckets, each defined by a rate (token arrival rate) and a burst size (bucket depth).

The building block of a policer is a pair of token buckets as illustrated below.

Figure 7-71 Dual Token Bucket Policing

There are two token buckets for metering CIR / CBS and PIR / PBS respectively. The buckets hold tokens, where each token can be thought of as permission for one byte. The sizes of the buckets correspond to the burst rates. For example, a PBS of 128 MB (megabytes) would be modeled by a bucket capable of holding 128 million tokens.

Nonconforming packets of the either bucket are the overflow packets and are dropped or marked according to the policer definition. Policers are configured on the Ethernet card using the combination of created bandwidth profiles and queues.

Initially, both buckets are full of tokens. The system adds tokens to each bucket at a rate corresponding to the appropriate information rate, according to the following formula:

token arrival rate = ((Information Rate) / 8) per second

For a CIR of 80 Mbps (which is 10 megabytes per second), the token arrival rate at the CIR bucket is 10 million tokens per second.

The system actually adds a token every 0.1 microsecond (that is, 10 million times per second). So it would be more accurate to say that for a CIR of 80 Mbps, the token arrival rate at the CIR bucket is one token every 0.1 microsecond. For numbers that are not as even, the system adds fractional tokens as necessary to implement the specified information rate.

CIR Bucket

PIR Bucket

CBS

PBS

Add tokens at the ratecorresponding to CIR

Remove tokens basedon packet size

Add tokens at ratecorresponding to PIR

Remove tokens basedon packet size

TR 00006


Chapter 13 PolicingGuidelines to Create a Policer

If either bucket is already full of tokens when new tokens arrive, the new ones are simply discarded. When a packet is presented to this dual-bucket policer, the system assigns a final drop precedence to the packet for traffic management at subsequent nodes in the provider network. The final drop precedence will be one of the following colors: • Green: classifier-assigned green and in profile for corresponding CoS.• Yellow: classifier-assigned green and out of profile or classifier-assigned yellow

and in profile for corresponding CoS.• Red: green or yellow and out of profile.

At the conclusion of the policing step, every packet has a final drop precedence of red, yellow, or green, recording its conformance to the bandwidth profile for its CoS. Red packets are automatically dropped. Yellow and green packets proceed to the queuing step.

Bandwidth Profiles and Policers

Bandwidth profiles and policers are related features. A bandwidth profile is like a recipe for making a pair of token buckets and is configured using templates in the TransNav management server. The TransNav management system supports a small number of network-wide recipes.

A policer is an actual set of token bucket pairs, one pair per CoS per port (Ethernet, EOS, or EOP). Policers are configured on an Ethernet card. Many policers can use the same recipe but still operate completely independently. Traffic flowing through Policer A can never affect the coloring of traffic flowing through Policer B, even if both policers use the same bandwidth profiles.

Guidelines to Create a Policer

There are no policers on a card until the service provider creates them. Policers can be selected by Policer ID or by the corresponding User tag for that Policer ID.

Each Ethernet card supports up to 1,024 policers. However, it will be more common to have just a few.

Important: Multiple services using the same policer share the total policer bandwidth. If you need the total policer bandwidth for each service, then create and assign a separate policer per service.

A policer has a separate bandwidth profile template for every class of service. When you create a policer, its default configuration is to use the bandwidth profile named “default” for every class. The default configuration for a newly-created policer is described in the following table.

Table 7-48 Default Policer

Class of Service Bandwidth Profile

1 Default

2 Default

3 Default

4 Default


Traverse Provisioning Guide, Section 7: Configuring EthernetCreate Policers on the Ethernet Card

Create Policers on the Ethernet Card

Use the following procedure to create a policer on an Ethernet card.

Table 7-49 Create Traffic Policers on the Ethernet Card

Step Procedure

1 Complete the Create a Bandwidth Profile, page 7-168 procedure for as many bandwidth profiles as are required in the network.

2 In Shelf View, click the Ethernet tab, then click the Policer subtab.

Figure 7-72 Ethernet Tab, Policer Subtab

3 Click Add to display the Create Policer tab.

Figure 7-73 Create Policer Tab

4 Policer ID. Enter an integer between 1 and 1024.

Card. Select the card in the shelf on which to configure the policer.

User tag (default is blank): Enter a 16-character user-defined name for this Policer ID. The Policer ID and User tag combination are unique for this card.

In the Bandwidth Profile column, select the correct bandwidth profile for the corresponding class of service (queue).

5 Click Apply to create the Policer and return to the Policer subtab.


Chapter 13 PolicingCreate Policers on the Ethernet Card

6 Repeat Steps 2 through 5 for each Policer required on this node.

7 The Create Traffic Policers on the Ethernet Card procedure is complete. To assign a policer to a service port, see Section 7—Configuring Ethernet, Chapter 10—“Ethernet Services,” Configure Ethernet Services, page 7-141.

Table 7-49 Create Traffic Policers on the Ethernet Card (continued)

Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetCreate Policers on the Ethernet Card



Chapter 14RED Congestion Control

Introduction This chapter contains the following topics:• Random Early Discard, page 7-175• System Defaults for RED Thresholds, page 7-177• Customize RED Thresholds, page 7-178• View Current System RED Thresholds, page 7-181

Random Early Discard

Random early discard (RED) manages congestion on the egress port. Packets are queued because the egress port is already transmitting a packet. RED manages two queuing issues: • Buffer usage. Instead of letting queued packets pile up indefinitely, potentially

using up all the buffers, there is limit on queue buffer consumption. This means some packets sent to the queue have to get dropped.

• Latency. The longer the queue gets, the more packets are delayed before they finally are transmitted. Different applications have different amount of delay tolerance. For example, better to drop voice packets than hold them back for a long time. So, RED drops packets.

The simplest form of dropping packets from the end of a full queue. A queue has a fixed length. The queue is considered full when the queue reaches that length. All packets that arrive after the queue is full are dropped.

The Traverse system uses a probabilistic drop mechanism instead of a fixed length queue. At a given queue length, some packets are dropped and others are queued. Below some length all packets are queued, then there is a range within which packets are dropped with probability that increases linearly from 0 to 100. Then, all packets are dropped. The specification of these lengths is called a RED curve.


Traverse Provisioning Guide, Section 7: Configuring EthernetTraverse RED Curves


Traverse RED Curves

The RED curve on the Traverse system is weighted by packet color: one RED curve for green packets and another for yellow packets. The system starts dropping yellow packets before the green packets. When a port reaches a certain length, the system randomly drops some yellow packets and queues other yellow packets, while still queuing all green. As the length of the queue increases, the system drops a higher percentage of yellow packets, but still accepts all green packets.

At some point, the system drops all yellow packets, but still accepts all green packets. Then, as the queue length continues to increase, the system continues to drop all yellow, but also randomly drops some green while queuing other green. Finally, when the queue is completely full, the system drops all packets regardless of color.

The probability of drop for a packet color rises linearly with queue length, from 0% to 100%. The following figure shows the RED curves of one queue for yellow and green packets.

Figure 7-74 Example RED Curves for Output Queue

Each output queue on a port has a RED curve described by the following set of threshold parameters.• Minimum Yellow. The queue length at which the system starts to randomly drop

packets with drop precedence yellow. Below this queue length, the system queues all yellow packets (probability of drop is zero).

• Maximum Yellow. The queue length at which the system drops all packets with drop precedence yellow (probability of drop is 100%).

• Minimum Green. The queue length at which the system starts to randomly drop packets with drop precedence green. Below this queue length, the system queues all green packets.

• Maximum Green. The queue length at which the system drops all packets with drop precedence green.

RED configuration allows the service provider fine-tune the behavior of the system when there is congestion. By default, the system manages the RED curves for output queues. However, the operator is able to override the default RED choices at any time.

There are system default RED profiles based on the window within which the link speed of the port falls. If the port’s link speed changes to a different window (for example, EOS ports to which members are added / deleted), the system automatically adjusts the default RED profiles to match the new window. If the operator chooses to override the system’s RED defaults, the system uses the manually entered settings no matter what happens to the speed of the port.

Probabilityof Drop

32Min

Yellow

96Max

Yellow

128Min

Green

256Max

Green

0

100

Queue Length in KB

Chapter 14 RED Congestion ControlSystem Defaults for RED Thresholds

System Defaults for RED Thresholds

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:

The total amount of buffer space on NGE, NGE Plus and EoPDH cards is 16 MB; for 10GbE and GbE-10 cards, the total amount of buffer space is 72 MB. These system defaults keep all ports active within this buffer limit.

Table 7-50 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


Traverse Provisioning Guide, Section 7: Configuring EthernetCustomize RED Thresholds

Customize RED Thresholds

Use the following procedure to help you customize RED thresholds for an Ethernet, EOS, or EOP port.

Table 7-51 Customize RED Thresholds for a Port

Step Procedure

1 To customize an Ethernet port, in Shelf View, click an Ethernet port, then click the Config tab. To customize an EOS port or EOP port, from Shelf View, click the Ethernet tab, then the EOS or EOP subtab. Double-click the desired Slot/ID member.


2 Click the Advanced button to display the Advanced Configuration dialog box.

Figure 7-76 Advanced Configuration—RED Thresholds


Chapter 14 RED Congestion ControlCustomize RED Thresholds

3 Customer RED CoS1. Select to configure the following RED thresholds for CoS1 (queue 1).• RED CoS1 Yellow Min (KB). Enter a number between 0 KB and

8,000 KB, in increments of 1 KB. There is no default.• RED CoS1 Yellow Max (KB). Enter a number between 0 KB and

8,000 KB, in increments of 1 KB. There is no default.• RED CoS1 Green Min (KB). Enter a number between 0 KB and

8,000 KB, in increments of 1 KB. There is no default.• RED CoS1 Green Max (KB). Enter a number between 0 KB and

8,000 KB, in increments of 1 KB. There is no default.
















Table 7-51 Customize RED Thresholds for a Port (continued)

Step Procedure


Traverse Provisioning Guide, Section 7: Configuring EthernetCustomize RED Thresholds

7 Click Done to close the dialog box and return to the main screen.

8 The Customize RED Thresholds for a Port procedure is complete.

Table 7-51 Customize RED Thresholds for a Port (continued)

Step Procedure


Chapter 14 RED Congestion ControlView Current System RED Thresholds

View Current System RED Thresholds

Use the following procedure to view the current RED thresholds on a port.

Table 7-52 View Current System RED Thresholds

Step Procedure

1 To customize an Ethernet port, in Shelf View, click an Ethernet port, then click the Config tab. To customize an EOS or EOP port, from Shelf View, click the Ethernet tab, then the EOS or EOP subtab. Double-click the desired EOS or EOP Slot/ID member.


2 For an Ethernet port, click the Queue button to display the Queue Status dialog box. For an EOS or EOP port, click the Queues button.

Figure 7-78 Queue Status—RED Thresholds

3 Click Refresh to refresh the data.

4 Click Done to close the dialog box and return to the main screen.

5 The View Current System RED Thresholds procedure is complete.


Traverse Provisioning Guide, Section 7: Configuring EthernetView Current System RED Thresholds


SECTION 8 CHANGING NETWORK CONFIGURATIONSSECTION 9CHANGING NETWORK CONFIGURATIONS

Contents

Chapter 1Adding a Node to a Protected Ring Configuration

Diagram of Topology Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Before You Update the Topology (Add a Node) . . . . . . . . . . . . . . . . . . . . . . . 8-2Add a Node to the Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Add a New Node to the Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7


Traverse Provisioning Guide, Section 8 Changing Network Configurations


SECTION 8CHANGING NETWORK CONFIGURATIONS

Chapter 1Adding a Node to a Protected Ring Configuration

Introduction This chapter explains how to make a topology update, i.e., add a node to a protected ring configuration.• Diagram of Topology Update, page 8-3• Before You Update the Topology (Add a Node), page 8-4• Add a Node to the Ring, page 8-5• Add a New Node to the Protection Group, page 8-9

Diagram of Topology Update

This example shows a basic three-node ring configuration. The fourth node will be added to the ring between Node 1 and Node 3.

Figure 8-1 Topology Update UPSR/SNCP Ring or BLSR/MS-SP Ring

Node 2

Node 3Node 1

Node 4

Span 1 Span 2

Span 3

TR 00094


Traverse Provisioning Guide, Section 8: Changing Network ConfigurationsBefore You Update the Topology (Add a Node)

Before You Update the Topology (Add a Node)

Review this information before you add a node to a protected ring configuration.

Table 8-1 Add Node Requirements


Hardware

New node is installed and commissioned. However, the fibers ARE NOT yet connected to the other nodes in the existing network.

Traverse Installation and Commissioning Guide, Section 11—Node Start-up and Commissioning Procedures

All nodes in the ring have the same version of software.

If upgrades are required, contact your Force10 customer representative.

n/a

Software

Timing is configured for the new node.

Traverse Provisioning Guide, Chapter 4—“Configuring Network Timing,” page 1-15

For hop-by-hop services, preprovision the pass-through services on the new node.

Traverse Provisioning Guide, Chapter 3—“Creating SONET Services,” page 4-19 or Chapter 4—“Creating SDH Services,” page 4-41


Chapter 1 Adding a Node to a Protected Ring ConfigurationAdd a Node to the Ring

Add a Node to the Ring

Use this procedure as a guideline to update a topology (add a new node to the ring).

Important: When adding a node to a UPSR ring with end-to-end provisioning, make sure there are no LOS conditions through the network when the node is added. Existing LOS conditions will result in an Add Node refresh failure or refresh in progress state. If this interim Add Node state exists, stop any further span provisioning tasks and contact the Force10 Technical Assistance Center..

After the new node has been added to the ring, replace the source or destination endpoint from the original service with the source or destination endpoint of the added node. For example, a service exists between Node A and Node B and the source endpoint is on Node A Slot 1. If Node C is added between Node A and Node B, the source endpoint must be changed from Node A Slot 1 to Node C Slot 3.

From:Node A (s1) <----> (s2) Node B

To:Node A (s1) <----> (s3) Node C

Table 8-2 Add a Node to the Ring

Step Procedure

1 Read the guidelines in the topic Before You Update the Topology (Add a Node), page 8-4.

2 Force switch the traffic off both the near end and the far end of the fiber span that will be disconnected to add the new node. (Span 3 in the example Topology Update UPSR/SNCP Ring or BLSR/MS-SP Ring, page 8-3).

For a BLSR/MS-SP Ring, go to Step 3.

For a UPSR/SNCP Ring, go to Step 4.

3 Force-switch the traffic off a span in a BLSR/MS-SP Ring:a. In Map View, click the Protection tab.b. Click the protection group to select it and click Edit.c. Select the near end port. Right-click and select Forced (FS-R).d. Select the far end port. Right-click and select Forced (FS-R).e. Go to Step 5.


Traverse Provisioning Guide, Section 8: Changing Network ConfigurationsAdd a Node to the Ring

4 Force all the traffic off the fiber span in a UPSR/SNCP Ring. If adding a node to a UPSR ring, verify there are no LOS conditions in the network during the Add Node process (except during Step 6). At each node in the ring that is adding or dropping traffic that is using that span, perform the following steps:a. In Map View, click the link that will be disconnected to add the new

node, then click the Services tab. b. Right-click a service and select Show TxRx Path. c. In the Xconn Conf column, click the selector for the service. d. Click the Switch tab.e. From the Path menu, select the path on the affected span.f. From the Command menu, select Force.g. Repeat substeps a. to f. for each service on the span.

Important: When adding a node to a UPSR ring with end-to-end provisioning, make sure there are no LOS conditions through the network when the node is added. Existing LOS conditions will result in an Add Node refresh failure or refresh in progress state. If this interim Add Node state exists, stop any further span provisioning tasks and contact the Force10 Technical Assistance Center.

5 Stop the system from signalling end-to-end services. a. In Map View, click the Config tab. b. Click the link, then click the Services button.

Figure 8-2 Stopping End-to-End Services

c. Use the Shift key and the mouse to select all the services on the span.d. Click Topological Update and select Start to start the node addition

process and stop the end-to-end signaling. The Upgrade State for each service changes to Refresh-Stopped. This will take a few minutes.

6 Connect the fibers of the new node according to the network plan. This will cause an expected LOS.

Note: Do not delete the link at this time. Although the link is now disabled, it will be used in Step 9.

Table 8-2 Add a Node to the Ring (continued)

Step Procedure


Chapter 1 Adding a Node to a Protected Ring ConfigurationAdd a Node to the Ring

7 Discover the new node. See the procedure: Discover the Network.

8 Add the new node to the protection group. See the procedure: Select the Node to Add to the Ring.

9 For end-to-end services, complete the topological update.a. In Map View, click the Config tab. b. Click the link, then click the Services button. c. Use the Shift key and the mouse to select all the services on the span.d. Click Topological Update and select Complete which completes the

node addition process and restarts end-to-end services signalling. e. A confirmation dialog box appears to complete the topology update.

Click Yes. f. The Add Span - Resume Refresh dialog box displays. In the Added

Node field, select the newly added node. Click Resume.

Note: When adding a node to a UPSR ring with end-to-end provisioning, you must change the value in the Added Node field to reflect the new node that was added.

Figure 8-3 Select the Node to Add to the Ring

g. All services should transition first to the Refresh-In-Progress and then to the Refresh-OK state.

h. Click Done.i. Go to Step 11.

Important: If refresh failures occur or if the services fail to refresh, contact the Force10 Technical Assistance Center.

10 For hop-by-hop services, activate the pre-provisioned pass-through services at the new node. See the procedure Activate or Deactivate a Service, page 4-16.

11 Clear the Forced-Switch command on all services.


For a UPSR/SNCP ring, go to Step 13.


Step Procedure


Traverse Provisioning Guide, Section 8: Changing Network ConfigurationsAdd a Node to the Ring

12 Clear all the Forced-Switched commands on the span in BLSR/MS-SP Ring:a. In Map View, click the Protection tab.b. Select the protection group and click Edit.c. Select the working port. Right-click and select Clear.d. Go to Step 16.

13 Clear all the Forced-Switched commands on the span in the UPSR or SNCP ring:a. In Map View, click the new link, then click the Services tab. b. Right-click a service and select Show TxRx Path. c. In the Xconn Conf column, click the selector for the service. d. Click the Switch tab.e. From the Path menu, select the path that is on the affected span.f. From the Command menu, select Clear.g. Repeat substeps a. to f. for each service on the span.

14 Delete the disabled link.

15 Connect the source or destination endpoint of the disabled service to the source or destination endpoint on the new node.

16 The Add a Node to the Ring procedure is complete.


Step Procedure


Chapter 1 Adding a Node to a Protected Ring ConfigurationAdd a New Node to the Protection Group

Add a New Node to the Protection Group

Use this procedure to add a new node to a UPSR/SNCP Ring or BLSR/MS-SP Ring protection group.

Table 8-3 Add the New Node to the Protection Group

Step Procedure

1 Complete steps Steps 1 through 7 in the procedure Add a Node to the Ring, page 8-5.

2 In Map View, click the Protection tab.

Figure 8-4 Map View, Protection Tab

3 Click the protection group to which you want to add the node.

4 Click Edit to display the Protection Group Creation tab.

2

3


Traverse Provisioning Guide, Section 8: Changing Network ConfigurationsAdd a New Node to the Protection Group

5 Click Add Node.

Figure 8-5 Protection Group Creation Tab

For a UPSR/SNCP Ring, go to Step 6.


6 In the Add Node dialog box, select the added node and set the West and East ports of the ring.

Figure 8-6 Add Node to UPSR/SNCP Ring

Remember that the West port on one node is physically connected to the East port on the next.

Click Add to return to the main screen.

Go to Step 8.

Table 8-3 Add the New Node to the Protection Group (continued)

Step Procedure

4


Chapter 1 Adding a Node to a Protected Ring ConfigurationAdd a New Node to the Protection Group

7 In the Add Node dialog box, set the BLSR/MS-SP Ring parameters.

Figure 8-7 Add Node to BLSR/MS-SP Ring

• Node: Select the node to add to the ring.• Node Position: Select a number to determine the position of this node

in the BLSR/MS-SP Ring. • Node ID: Identification number of the node in the ring. Select 0 to 15.

Default is the sequential order. This ID is used to squelch services in the ring.

• West Port: Select the West port of the ring.• East Port: Select the East port of the ring.

Remember that the West port on one node is physically connected to the East port on the next node.

Click Add to close the dialog box and return to the main screen.

8 Click Apply to return to the protection group list on the protection tab.

Figure 8-8 Protection Group Creation Tab After Node is Added


Step Procedure


Traverse Provisioning Guide, Section 8: Changing Network ConfigurationsAdd a New Node to the Protection Group

9 On the Protection tab, synchronize the protection group.

Figure 8-9 Protection Group List on Protection Tab

• Click the protection group to select it.• Right-click and select Synchronize to synchronize the ring.

10 The Add the New Node to the Protection Group procedure is complete.

Return to Step 8 of the procedure Add a Node to the Ring, page 8-5.


Step Procedure


SECTION 9 APPENDICESSECTION 9APPENDICES

Contents

Appendix AProvisioning Checklists

Before You Start Provisioning Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Node and Timing Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Card Configuration Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4Protection Group Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5Port Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Service Creation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

Appendix BService Endpoints

Endpoints for STS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10Endpoints for VT1.5 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11Endpoints for SONET VT-MUX Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13Endpoints for SONET Services on EoPDH Cards . . . . . . . . . . . . . . . . . . . . . 9-13Endpoints for SONET Services on EoPDH Cards . . . . . . . . . . . . . . . . . . . . . 9-13Endpoints for VC3 and VC4 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16Endpoints for SDH VC-MUX Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17Endpoints for VC11 and VC12 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17Endpoints for SDH Services on EoPDH Cards . . . . . . . . . . . . . . . . . . . . . . . . 9-19


Traverse Provisioning Guide, Section 9 Appendices


SECTION 0APPENDICES

Appendix AProvisioning Checklists

Introduction Use the checklists in this Appendix to bring a Traverse network into service and to create services for transport over the network using the TransNav management system graphical user interface (GUI). • Before You Start Provisioning Procedures, page 0-2• Node and Timing Configuration Checklist, page 0-3• Card Configuration Checklist, page 0-4• Protection Group Configuration Checklist, page 0-5• Port Configuration Checklist, page 0-6• Service Creation Checklist, page 0-7

Successfully completing each checklist assumes that the tasks in the previous checklist are complete.

Each step references the related detail-level procedure for additional information. All provisioning detail-level procedure references are to the Traverse Provisioning Guide.


Traverse Provisioning Guide, Section 0: AppendicesBefore You Start Provisioning Procedures

Before You Start Provisioning Procedures





Hardware





Software









Appendix A Provisioning ChecklistsNode and Timing Configuration Checklist

Node and Timing Configuration Checklist

Use this checklist as a guide to more detailed procedures. Each step refers to the relevant detailed procedure.

Table 0-2 Node and Timing Configuration Checklist

Step Description and Procedure Reference Mark Complete

1 Review the information in Before You Start Provisioning Procedures, page 0-2 before you start with this checklist.

2 Arrange Node(s) in Map View. The GUI opens in Map View. Traverse node(s) and optical links are autodiscovered and displayed in the upper left corner of Map View. Click and drag the node(s) to the correct area(s) on the map to best represent your network.

From the File menu, click Save User Preferences.

3 Go to Shelf View. Double-click a node to go to Shelf View. The GUI auto discovers all cards. Shelf View displays the node and cards exactly like the physical installation in the central office.

The node is already commissioned.

4 Configure the Node. In Shelf View, click the Config tab to display the Node Configuration dialog box.

See Configure Node Parameters, page 1-11.

5 Configure External Timing. Set the BITS interface sources for the head-end node.

See Configure External Timing, page 1-19.

6 Configure Line Timing. Set the timing options in other network nodes.

See Configure Line Timing, page 1-22.

7 Configure Derived References (optional). Provide a timing reference from a line interface and send it to an external clock.

See Configure Derived References, page 1-23.

8 Repeat Steps 3 to Steps 7 for each node in the network.

9 All Node and Timing Configuration Checklist steps are complete.

Continue to the Card Configuration Checklist, page 4 checklist.


Traverse Provisioning Guide, Section 0: AppendicesCard Configuration Checklist

Card Configuration Checklist

Use this checklist as a guide to more detailed procedures. Each step refers to the relevant detailed procedure.

Table 0-3 Card Configuration Checklist


1 Complete the Node and Timing Configuration Checklist, page 3.

2 Go to Shelf View and Select a Card. Double-click a node to go to Shelf View. The GUI auto discovers all cards. Shelf View displays the node and cards exactly like the physical installation in the central office. Click a card from Shelf View.

3 Configure the Card. In Shelf View, click the card, then click the Config tab to display the Card Configuration screen.

See Section 2—Configuring TDM Equipment for details on specific cards.

4 Repeat Step 3 for each card in the node.

5 Repeat Steps 2 and 4 for each node in the network.

6 All Card Configuration Checklist steps are complete.

Continue to the Protection Group Configuration Checklist, page 5.


Appendix A Provisioning ChecklistsProtection Group Configuration Checklist

Protection Group Configuration Checklist

Use this checklist as a guide to more detailed procedures. Each step refers to the relevant detailed procedure. Complete each item as required for your network configuration.

Table 0-4 Protection Group Configuration Checklist


1 Complete the Card Configuration Checklist, page 4.

2 Create Equipment Protection Groups for Tributary Cards. For each tributary card, create an equipment protection group.

See Create an Equipment Protection Group, page 3-27.

3 Create 1:1 Equipment Protection Group for VCX Hardware. If you have a card with a VCX component, create a protection group for the VCX hardware.

See Create an Equipment Protection Group, page 3-27.

4 Create 1+1 MSP Groups for Tributary STM-N Cards. For each tributary STM-N port, create a facility protection group.

See Create a 1+1 APS/MSP Protection Group, page 3-37.

5 Create 1+1 APS Groups for Tributary OC-N Cards. For each tributary OC-N port, create a facility protection group.


6 Create 1+1 Protection Group for Trunk Cards. For a point-to-point network, create a 1+1 MSP/APS protection groups for trunk links.


7 Create UPSR Ring Topology. For a path-protected ring network, create a UPSR ring topology.

See Create a UPSR or SNCP Ring Protection Group, page 3-18.

8 Create a BLSR Topology. For a line-protected ring network, create a BLSR topology.

See Create a BLSR or MS-SPRing Protection Group, page 3-11

9 All Protection Group Configuration Checklist steps are complete.

Continue to Port Configuration Checklist, page 6.


Traverse Provisioning Guide, Section 0: AppendicesPort Configuration Checklist

Port Configuration Checklist

Use this checklist as a guide to more detailed procedures. Each step refers to the relevant detailed procedure. Complete the steps as required based on the cards installed in the shelf.

Table 0-5 Port Configuration Checklist


1 Complete the Protection Group Configuration Checklist, page 5.

2 In Shelf View, click any port, then click the Config tab.

3 On the Port Configuration screen, change any default values for any configurable parameters.

See Section 2—Configuring TDM Equipment for details on all configurable port parameters.

SDH or SONET Interfaces:

If this is an SDH or SONET interface, configure parameters only on the working port if the port is part of a protection group. Parameters on a protecting port are automatically set to the same values as the working port.

Electrical Interfaces:

If this is an electrical interface, configure parameters only on working cards if a card is configured as part of a protection group. Parameters on a protecting card are automatically set to the same values as the working card.

4 Click the Lock icon, which is located in the lower left corner of the screen, to unlock the port and monitor potential problems.


6 Repeat Steps 1 to 5 for each node in the network.

7 All Port Configuration Checklist steps are complete.

Continue to Service Creation Checklist, page 7.


Appendix A Provisioning ChecklistsService Creation Checklist

Service Creation Checklist

Configuring services on a node or through a network is a process of provisioning attributes of the service in four screens then activating the service. The Traverse supports a number of service types.

See Section 4—Creating ADM Services for detailed information on creating specific services.

Table 0-6 Service Creation Checklist


1 Add the Service. On the Service tab, select the service type and click Add

2 Configure Service Parameters. Enter the name of the service and configure other general parameters.

3 Select the Service Endpoints. Set the endpoints for this service. Click the Source row in the Endpoint column to display the Choose an Endpoint dialog box. Select the source and click Done to close the dialog box.

Click the Destination row, select the endpoint in the dialog box and click Done.

4 Configure Service Protection. Click the Protection parameter field to display the Protection dialog box. Select the type of protection for the service by clicking on the tabs in the dialog box.

Configure any applicable parameters.

Click Done to close the dialog box and return to the Create Service tab.

5 Configure Other Service Characteristics. Click the Advanced button to display the Advanced Parameters dialog box.

Configure the characteristics of the service.

If this is an end-to-end service, configure the characteristics of the connection throughout the network.


Traverse Provisioning Guide, Section 0: AppendicesService Creation Checklist

6 Select the Path for End-to-End Services. If Strict= , explicitly select the service route between defined endpoints.

If using Partial-Strict constraints, select the initial source ingress and egress points, a secondary source ingress point, and the destination ingress point.

If using Loose constraints, select the initial source ingress point and the desination ingress point.

Click the plus sign in the Add column to add another hop to the service.

Click the minus sign in the Remove column to remove a hop.

Click Apply to add the provisioned service to the service list and return to the Service tab.

7 Activate the Service. On the Service tab, click the service to select it, right-click for the menu, and click Activate.

Table 0-6 Service Creation Checklist (continued)



SECTION 0APPENDICES

Appendix BService Endpoints

Introduction This appendix summarizes the valid source and destination information for each supported service type on the Traverse:• Endpoints for STS Services• Endpoints for VT1.5 Services• Endpoints for SONET VT-MUX Services• Endpoints for SONET Services on EoPDH Cards• Endpoints for VC3 and VC4 Services• Endpoints for SDH VC-MUX Services• Endpoints for VC11 and VC12 Services• Endpoints for SDH Services on EoPDH Cards


Traverse Provisioning Guide, Section 0: AppendicesEndpoints for STS Services

Endpoints for STS Services

The following table lists valid sources and destinations for STS services for the following cards: NGE, NGE Plus, 10GbE, and GbE-10. Your network may require creating multiple services at multiple nodes.

Note: For information on the valid sources and destinations for SONET services on EoPDH cards, see Endpoints for SONET Services on EoPDH Cards, page 0-13.

The Traverse system supports multicast STS connections for 1+1 path-protected and drop-and-continue services.




OC-N1 node/slot/port/sts

STM-N (HO - high order)STM-N (LO - low order)

all ports E1 card

OC-NEC1DS3CCDS3TMXall ports DS1 card

node/slot/port/aug1/node/slot/port/aug1/vc3node/slot/port/aug1/tug3/vc3node/slot


EC1 node/slot/port


OC-NEC1DS3CC



DS3CC node/slot/port


OC-NEC1DS3CC



DS3TMX node/slot/port


OC-N




Appendix B Service EndpointsEndpoints for VT1.5 Services

Endpoints for VT1.5 Services

The following table lists valid sources and destinations for VT1.5 services. Your network may require creating multiple services at multiple nodes.

There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create this service.

Note: The maximum switching capacity of NGE and NGE Plus cards is 5 Gbps, however, this is restricted to high order switching. The following restrictions exist for low order switching. ∞ A SONET VT1.5 service cannot be provisioned if the either source or destination

termination point of the service is one of the following VT1.5 connection termination points (CTPs) on an NGE card. Any VT in VTGx or STSy where:x = 3, 4, 5, 6, 7 andy = 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42, 45, 48

All ports on a DS1 card node/slot


OC-N





OC-N


node/slot/port/sts


SONET port on backplane for EOP ports

node/slot (Ethernet card)/sts OC-N node/slot/port/sts

1 For STS services between OC-192 ports, the source STS number and the destination STS number must in the same range when the range is between 1 and 48, or 49 and 192. For example, if the source STS is STS number 12, the destination STS must be between STS number 1 and 48. If the source STS is STS number 105, the destination STS must be between STS number 49 and 192.





Traverse Provisioning Guide, Section 0: AppendicesEndpoints for VT1.5 Services

∞ A VT1.5 CTP cannot be added from the OC-48 VOP to an EOS port on the same NE card if the endpoint is one of the following VT1.5 CTPs: Any VT in VTGx or STSy where:x = 3, 4, 5, 6, 7 andy = 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42, 45, 48

Table 0-8 Endpoints for VT1.5 Services



OC-N node/slot/port/sts/vtg/vt

STM (HO - high order)1

STM (LO - low order)1

E1

OC-NEC1DS3TMX2

DS1


2 Port is DS1-mapped (DS3 Mapping parameter is DS1).



EC1 node/slot/port/sts-1/vtg/vt

STM (HO)1

STM (LO)1

E1

OC-NEC1DS3TMXDS1



DS3TMX2 node/slot/port/subport

STM (HO)1

STM (LO)1

E1

OC-NEC1DS3TMX2

DS1



node/slot/port


DS1 node/slot/port

STM (HO)1

STM (LO)1

E1

OC-NEC1DS3TMX2

DS1



node/slot/port



node/slot (Ethernet card)/sts/vtg/vt

OC-N

Any Ethernet card on a different node.

node/slot/port/sts/vtg/vt



Appendix B Service EndpointsEndpoints for SONET Services on EoPDH Cards

Endpoints for SONET VT-MUX Services

The following table lists the source and destination endpoint requirements to create SONET VT-Mux services.


The tables in the following sections list valid sources and destinations for STS, VT1.5, and EOP bi-directional services on EoPDH cards. The EOP interface for each example is a virtual optical port (VOP). Your network may require creating multiple services at multiple nodes.



The following table lists valid sources and destinations for services on EoPDH cards provisioned in SONET mode. The Traverse system supports multicast STS connections for 1+1 path-protected and drop-and-continue services.


Table 0-9 Endpoints for SONET VT-Mux Services



Mapping Set to

SONET EoPDH - STS(1 to 24)

STS VT-Mux 1 STS Yes VT1.5


DS3-Tmx DS3-Tmx 1 DS3 No N/A1


DS1 (all ports) DS1-Mux 28 VT No N/A

1 Not applicable





)

Interface CTP type

(CLI)


SONET Service

Type (CLI)

SONET Service

Bandwidth

EoPDH CTP Type


1DS1 port DS1 DS1


2 VT1.5 VT1.51 VT1.5 DS1 in VT1.5


Traverse Provisioning Guide, Section 0: AppendicesEndpoints for SONET Services on EoPDH Cards

3All 28 ports on a DS1 card

CARD-STS All 28 DS1s on DS1 card DS1-MUX STS STS 28 x (DS1 in VT1.5)

4 DS3-CC DS3 DS3 DS3-CC STS2 STS DS3 in STS

5

DS3-TMX

TMX_DS1DS1 structured DS3


6 DS1_TMX VT1.5 VT1.51 VT1.5 DS1 in VT1.5

7 DS3_TMX DS3-TMX STS STS 28 x (DS1 in VT1.5)

8

EC1

VT1.5

DS1 mapped VT1.5 (in STS) VT1.5 VT1.51 VT1.5 DS1 in VT1.5

9 VT1.5 structured STS VT1.5 VT1.51 VT1.5 VT1.5

10 STS DS1 mapped VT1.5 (in STS) VT-MUX STS STS 28 x (DS1 in VT1.5)

11 STS VT1.5 structured STS VT-MUX STS STS (28 x VT1.5) in STS

12 EC1 DS3 mapped STS STS STS2 STS DS3 in STS

13 EC1 STS STS STS2 STS STS

14 OC-N VT1.5 DS1 structured DS3 (in STS) VT1.5 VT1.51 3 VT1.5 DS1 in VT1.5

15

OC-N / VOP4

VT1.5

DS1 mapped VT1.5 (in STS) VT1.5 VT1.51 VT1.5 DS1 in VT1.5

16 VT1.5 structured STS5 VT1.5 VT1.51 VT1.5 VT1.5

17

STS

DS1 mapped VT1.5 (in STS) VT-MUX STS STS 28 x (DS1 in VT1.5)

18 VT1.5 structured STS VT-MUX STS STS 28 x VT1.5

19 DS1 mapped VT1.5 (in STS) STS STS3 STS 28 x (DS1 in VT1.5)

20 DS3 mapped STS STS STS2 STS DS3 in STS

21 STS5 STS STS2 STS STS

22 STS-3C5 STS STS-3C2 STS STS-3C





)

Interface CTP type

(CLI)


SONET Service

Type (CLI)

SONET Service

Bandwidth

EoPDH CTP Type



Appendix B Service EndpointsEndpoints for SONET Services on EoPDH Cards

1 A VT Switch Module is required in the same chassis.




5 Cards with VOP can be NGE, 10GbE, or GbE-10.


Traverse Provisioning Guide, Section 0: AppendicesEndpoints for VC3 and VC4 Services


The following table lists valid sources and destinations for SDH services. Your network may require creating multiple services at multiple nodes.

The Traverse system supports multicast SDH connections for 1+1 path-protected and drop-and-continue services.




STM-N1

1 For SDH services between STM-64 ports, the source AUG number and the destination AUG number must inthe same range when the range is between 1 and 32, or between 33 and 64. For example, if the source AUGis AUG number 12, the destination AUG must be between AUG number 1 and 32; if the source AUG is AUG number 51, the destination AUG must be between AUG number 33 and 64.

node/slot/port/aug1/node/slot/port/aug1/tug3/vc3node/slot/port/aug1/vc3


E3CCall ports E1 card

OC-NEC3EC1DS3CCDS3TMXall ports DS1 card

node/slot/port/aug1/node/slot/port/aug1/tug3/vc3node/slot/port/aug1/vc3node/slot/portnode/slot


E3CC node/slot/port STM-N (HO)STM-N (LO)E3CC

OC-N EC1DS3CC

node/slot/port/aug1/tug3/vc3node/slot/port/aug1/vc3node/slot/port


All ports on an E1 card


OC-N

node/slot/port/aug1/tug3/vc3node/slot/port/aug1/vc3


Ethernet card for EOS




SDH port on back-plane for EOP ports

node/slot (Ethernet card)/aug1 OC-N node/slot/port/aug1


Appendix B Service EndpointsEndpoints for VC11 and VC12 Services

Endpoints for SDH VC-MUX Services

The following table lists the source and destination endpoint requirements to create SDH VC-MUX services.


The following table lists valid sources and destinations for VC11 and VC12 services. Your network may require creating multiple services at multiple nodes.

There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create these services.

Note: The maximum switching capacity of NGE and NGE Plus cards is 5 Gbps, however, this is restricted to high order switching. The following restrictions exist for low order switching on NGE cards in SDH mode with a provisioned low order mapping of VC-11. • An SDH VC-11 service cannot be provisioned if either the source or destination

termination point of the service is one of the following VC-11 connection termination points (CTPs):Any VC-11 in TUG2-x, VC3-y, or AUGz where:x = 3, 4, 5, 6, 7 andy = 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42, 45, or 48 andz = any value between 1 and 16 inclusive

• A VC-11 CTP cannot be added from the STM-16 VOP to an EOS port on the same NGE card if the endpoint is one of the following VC-11 CTPs: Any VC-11 in TUG2-x, VC3-y, or AUGz where:x = 3, 4, 5, 6, 7 andy = 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42, 45, or 48 andz = any value between 1 and 16 inclusive

Table 0-12 Endpoints for SDH VC-Mux Services



Mapping Set to

SDH EoPDH - VC3 (1 to 24)

VC3 VC-Mux 1 VC3 Yes VC11/ VC12

EoPDH - VC3(1 to 12)

E1 (all ports) E1-Mux E3 No N/A


Traverse Provisioning Guide, Section 0: AppendicesEndpoints for VC11 and VC12 Services

• No restrictions exist for VC-12 connection termination points on NGE cards.




STM-N1


node/slot/port/aug1/tug3/tug2/lovc2

node/slot/port/aug1/vc3/tug2/lovc2


STM (HO)1

STM (LO)1

E1

OC-NEC1DS3TMX3

DS1

3 Port is E1-mapped (DS3 Mapping parameter is E1).


node/slot/port/aug1/vc3/tug2/lo vcc

node/slot/port

node/slot/port/sts/vtg/vtnode/slot/port/sts-1/vtg/vtnode/slot/port/sts-1/vtg/vtnode/slot/port/subportnode/slot/port


STM (LO)1

E1

OC-N EC1DS3TMX3

DS1



node/slot/port


E1 node/slot/port STM (HO)1

STM (LO)1

E1

OC-N EC1DS3TMX3

DS1



node/slot/port


DS1 node/slot/port STM node/slot/port/aug1/tug3/tug2/lo vc2



Appendix B Service EndpointsEndpoints for SDH Services on EoPDH Cards

Endpoints for SDH Services on EoPDH Cards

The following table lists valid sources and destinations for SDH services on EoPDH cards. The Traverse system supports multicast STM connections for 1+1 path-protected and drop-and-continue services.

Note: An EoPDH card in SDH mode does not support SONET/SDH services to DS1/DS3 interfaces. Conversely, an EoPDH card in SONET mode does not support SONET/SDH services to E1/E3 interfaces.

Table 0-14 Endpoints for SDH Services on EoPDH Cards




)

Interface CTP type

(CLI)


SDH Service

Type (CLI)

SDH Service

Bandwidth

EoPDH CTP Type


1 E1 port E1 E1 E1 VC121 VC12 E1 in VC12 (in VC3)

2 All 21 ports on an E1 card

CARD-STM All 21 E1s on card

E1-MUX HO-VC3 VC-3 21 x (E1 in VC12) in VC3

3 E3-CC E3 E3 E3-CC HO-VC32 VC-3 E3 in VC3

4 DS3-TMX E1_TMX E1 structured DS3

E1 VC121 VC12 E1 in VC12 (in VC3)

5 DS3-TMX DS1_TMX_IN_VC12

E1 structured DS3


6 STM-N VC12 E1 structured DS3 in VC3

VC121 3 VC12 E1 in VC12 (in VC3)

7 VC3 E1 structured DS3 in VC3

VC3 HO-VC33 VC3 21 x (E1 in VC12)

8 E1 structured DS3 in VC3

LO-VC334 21 x (E1 in VC12)

9 E3 mapped VC3 LO-VC34 E3 (in VC3)

10 VC36 LO-VC34 VC3


Traverse Provisioning Guide, Section 0: AppendicesEndpoints for SDH Services on EoPDH Cards

11 STM-N / VOP5

VC11 VC11 struc-tured VC36

VC11 VC111 VC11 VC11 (in VC3)

12 VC12 E1 mapped VC12 (in VC3)



VC121 VC12 VC12 (in VC3)

14 VC3 VC11 struc-tured VC3

VC-MUX HO-VC3 VC3 28 x VC-11

15 E1 mapped VC12 (in VC3)

HO-VC3 21 x (E1 in VC12)


HO-VC3 21 X VC-12

17 E3 mapped VC3 VC3 HO-VC32 E3 (in VC3)

18 VC36 HO-VC32 VC3

19 STM-N / VOP5

VC4 VC46 VC4 VC42 VC4 VC4

1 A TU Switch Module must be in the same chassis.



4 LO-VC3 services can be created from VC4-VC3 or VC4-Grooming endpoints on the Source card.


6 Source cards with VOP can be NGE, 10GbE, or GbE-10.

Table 0-14 Endpoints for SDH Services on EoPDH Cards (continued)




)

Interface CTP type

(CLI)


SDH Service

Type (CLI)

SDH Service

Bandwidth

EoPDH CTP Type



INDEX

Numerics1+1 APS/MSP

2-port OC-48/SMT-16protection group, 4-73

1+1 path protectionbookend application, 5-10create service, 5-8requirements

bookend application, 5-11procedures, 5-9service, 5-8

AAccess

systemmethods, 1-8

Addnode

to ring, 8-3AIS

formatDS3 port, 2-9DS3TMX port, 2-12STS1TMX port, 2-12, 5-45

insertionE1 port, 2-31

maskDS1 port, 2-7DS3 port, 2-9DS3TMX port, 2-12E1 port, 2-31E3 port, 2-32EC1 port, 2-17SDH port, 2-37SONET port, 2-22STS1TMX port, 2-12, 5-45

Alarmsprofile

DS1 port, 2-7DS3 port, 2-10DS3TMX port, 2-13E1 port, 2-31E3 port, 2-33EC1 port, 2-18Ethernet port, 7-20SDH port, 2-41SONET port, 2-26subport, 2-15

Alternate VLAN ethertype see Ethernet module

Automatic laser shutdown see Transmitter auto shutdown

Auto-negotiationdescription, 7-24parameters

advertise 1000M full duplex, 7-27, 7-28advertise 1000M half duplex, 7-27, 7-28advertise 100M full duplex, 7-26advertise 100M half duplex, 7-26advertise 10M full duplex, 7-26advertise 10M half duplex, 7-26advertise GBE RX PAUSE, 7-28advertise GBE TX PAUSE, 7-28advertise PAUSE, 7-26advertise PAUSE RX, 7-27advertise PAUSE TX, 7-27setting, 7-25

BBandwidth

portvirtual, 7-51

profilecreate, 7-168defaults, 7-166examples, 7-166policer, 7-171values, 7-166

Bi-directional switchingcreating, 4-71

Bookend application, 5-10Bundling

VLAN, 7-11Bytes

forwardedtransparent services, 5-50, 5-51

CCard

configuration checklist, 9-4parameters

change, 2-2Carrier Ethernet Protection Pair

definition, 3-2guidelines, 3-30link aggregation, 3-3, 7-38protection group

create, 3-32requirements, 3-29with LAG, 3-3

Release TR3.2.2 Force10 Networks Index-1

Index

ChangeBER thresholds, 2-19card parameters, 2-2DCC tunnel, 1-17DS1 port parameters, 1-16

Checklistcard configuration, 9-4node and timing configuration, 9-3port configuration, 9-6protection group configuration, 9-5provisioning, 9-1service creation, 9-7

Configurationderived references, 1-23external timing, 1-19line timing, 1-22network timing guidelines, 1-18node parameters, 1-11timing options global, 1-18

Connectionstiming

inputs and outputs, 1-18Control data

disableSONET, 1-19third-party equipment, 5-54

SDH port, 2-39SONET port, 2-24

Createservice

1+1 path protection, 5-8Cross-connect

ADM service types, 4-4Current transmitter state

STMport, 2-38

CustomerDS1 port, 2-7DS3 port, 2-10DS3TMX port, 2-13E1 port, 2-31E3 port, 2-33EC1 port, 2-18Ethernet port, 7-20premise equipment, 7-123SDH port, 2-41SONET port, 2-26STS1TMX port, 2-13tag

DS1 port, 2-7DS3 port, 2-10DS3TMX port, 2-13E3 port, 2-33EC1 port, 2-18

Ethernet, 7-16SDH port, 2-41SONET port, 2-26STS1TMX port, 2-13

taggedEthernet port, 7-20

DDaylight Saving Time

support, 1-15DCC tunnel

change, 1-17configuration, 1-20example, 1-16requirements, 1-17

DCSapplication

creating multi-shelf, 6-14DCS-384 matrix shelf definition, 6-3DCS-96 shelf definition, 6-6, 6-31DCS-IO shelf definition, 6-4multi-shelf example, 6-12multi-shelf, DCS-384 matrix shelf, 6-3multi-shelf, DCS-IO shelf, 6-4single-shelf definition, 6-5single-shelf, DCS-96 shelf, 6-6, 6-31

DCS-384activate services, 6-28creating services, 6-24

DCS-IOallocate MSAID ranges, 6-17

servicesearch, 6-9

Derivedreferences configuration, 1-23timing, 1-18

Do not use for synchronization see DUS

Drop and continue serviceEthernet, 5-22guidelines, 5-23interconnected rings

guidelines, 5-31required parameters, 5-24required procedures, 5-23requirements, 5-22video broadcast, 5-22

DS1mapping

change formats, 2-5port

change parameters, 2-4requirements, 2-4

Index-2 Force10 Networks Release TR3.2.2

Index

DS1 portAIS mask, 2-7alarm profile, 2-7card configuration, 2-5change parameters, 1-16customer, 2-7customer tag, 2-7line build out, 2-7line coding, 2-7line format, 2-7performance monitoring template, 2-7

DS3line format

port, 2-9port

AIS format, 2-9AIS mask, 2-9alarm profile, 2-10customer, 2-10customer tag, 2-10in band loopback, 2-9line build out, 2-9performance monitoring template, 2-10

remote defect indicator, 2-32DS3 mapping

DS3TMX port, 2-12STS1TMX port, 2-12, 5-45

DS3TMXport

AIS format, 2-12AIS mask, 2-12alarm profile, 2-13customer, 2-13customer tag, 2-13DS3 mapping, 2-12line build out, 2-12line format, 2-12PM template, 2-13subport numbering, 2-12

subportline format, 2-14, 2-15PM template, 2-15

DUSSDH port, 2-37SONET port, 2-22

EE1

portAIS insertion, 2-31AIS mask, 2-31alarm profile, 2-31configure, 2-30

customer, 2-31line build out, 2-31line format, 2-31performance monitoring template, 2-31

E3port

AIS mask, 2-32alarm profile, 2-33customer, 2-33customer tag, 2-33line build out, 2-32line format, 2-32performance monitoring template, 2-33

EC1port

AIS mask, 2-17alarm profile, 2-18change parameters, 2-15customer, 2-18customer tag, 2-18line build out, 2-17parameters,change, 2-15performance monitoring template, 2-18SD BER, 2-17SF BER, 2-17

ECC, see Multipoint ECCEndpoint

resource advisory, 4-2SDH, 4-49, 9-16services

EOP on EoPDH cards, 4-28, 9-13SDH on EoPDH cards, 4-52, 9-19STS on EoPDH cards, 4-28, 9-13VT1.5 on EoPDH cards, 4-28, 9-13

summary, 9-9EOP

connection requirements, 7-71EoPDH, 7-73

port member, 7-73port

create, 7-76traffic congestion management, 7-82, 7-152

EoPDHbandwidth

requirements, 7-73customer

premise equipment, 7-123definition, 7-71endpoints

EOP, 4-28, 9-13SDH services, 4-52, 9-19STS, 4-28, 9-13VT1.5, 4-28, 9-13


Index

EOPavailable port membersconnection requirements, 7-71

portcreate, 7-76EOP, 7-73members, 7-73virtual, 7-73

servicemultipoint, 7-123SDH restrictions, 4-52, 9-19SONET restrictions, 4-28, 9-13SONET/SDH restrictions, 7-137

termination points, 7-73VCAT

requirementsEOS

bandwidthsvirtual ports, 7-51

definition, 7-50links

removing LCAS-enabled, 7-96port

LO mapping, 7-16standard, 7-16threshold, 7-101

ETH100TX portcrossover, 7-28manual duplex, 7-28manual pause, 7-28manual speed, 7-28

Etherchannel, see LAGEthernet

alternate VLAN ethertypeinsert, 7-17

cardalternate VLAN ethertype, 7-21customer tag, 7-16

Carrier Ethernet Protection Paircreate, 3-32definition, 3-2

control channelservices, 7-123

control channel interfaceport member, 7-123use of, 7-123

EoPDHport, 7-73port member, 7-73

featuresLCAS, 7-89RSTP, 7-104video broadcast, 5-22virtual concatenation, 7-51

line service, 7-120link aggregation

capacity changes, 7-39Carrier Ethernet Protection Pair, 3-3, 7-38description, 7-37guidelines, 7-38

modulealternate VLAN ethertype, 7-17

over SONET/SDHrequired connections, 7-50

portalarm profile, 7-20configure FIFO shaping rate, 7-22configure parameters, 7-18configure WFQ, 7-23customer, 7-20FIFO queuing policy, 7-22FIFO shape enable, 7-22insert alternate VLAN ethertype, 7-21jumbo frame, 7-19link integrity, 7-2manual duplex, 7-29manual pause, 7-29manual speed, 7-29performance monitoring template, 7-20queuing policy, 7-22recovery pulse width, 7-19tagging, 7-20transmitter auto shutdown, 7-19transmitter state, 7-18WFQ queuing policy, 7-22

see also Carrier Ethernet Protection Pairvirtual port

EoPDH, 7-73External

timingconfiguration, 1-19

FFIFO

queuing policyEthernet port, 7-22

shape enableEthernet port, 7-22

shaping rateEthernet port, 7-22

Forwardsection trace


section trace formatSDH port, 2-39SONET port, 2-24


Index

GG.747

servicesstandard, 5-34

HHop-by-hop

service, 4-6

IIn band loopback, 2-9IP address

node-ip, 1-16IP QoS, 1-15

access control list, 1-19configuring, 1-17static classifiers, 1-18

JJumbo frame

Ethernet port, 7-19

LLAG

capacity changes, 7-39create, 7-41description, 7-37guidelines, 7-38

LCASEOS links

removal guidelines, 7-96feature description, 7-89

Linebuild out

DS1 port, 2-7DS3 port, 2-9DS3TMX port, 2-12E1 port, 2-31E3 port, 2-32EC1 port, 2-17

codingDS1 port, 2-7

formatDS1 port, 2-7DS3 port, 2-9DS3TMX port, 2-12DS3TMX subport, 2-14, 2-15E1 port, 2-31E3 port, 2-32STS1TMX port, 2-12, 5-45STS1TMX subport, 2-14, 2-15

protectionCarrier Ethernet Protection Pair, 3-4

servicedefinition, 7-120

timingconfiguration, 1-22

Linkintegrity

overview, 7-2LO mapping

EOS ports, 7-16

MMAC address

forwardingmultipoint service, 7-123

tableview or edit, 7-33

Mapping formatsDS1

change parameters, 2-5MSAID

allocateDCS-IO shelf, 6-17

allocating, 6-7assigning

DCS-IO, 6-19DCS-IO

assignments, activating, 6-23definition, 6-7supported formats, 6-8

Multipoint ECCservice

description, 7-123services

configuration guidelines, 7-135

NNetwork

configuration process, 1-7Time Protocol, 1-12timing configuration

guidelines, 1-18Node

ID, 1-16IP, 1-16IP address, 1-16parameters

configure, 1-11SNMP

agent port, 1-16timing configuration checklist, 9-3


Index

NTP IP, see Network Time Protocol

OOC-192

uplinksprotected services, 4-73

OC-482-port

protection groups, 4-73OC-48/STM-16

2-port1+1 APS/MSP protection group, 4-73UPSR/SNCP protection group, 4-73

Optical transmux, 5-33guidelines, 5-41service

required procedures, 5-42requirements, 5-40

PParameters

drop and continue service, 5-24Path

protectionCarrier Ethernet Protection Pair, 3-5over MSP-protected links, 5-6, 5-7

Payload mappinghigh order services

SDH, 4-48SONET, 4-24

Performance monitoring templateDS1 port, 2-7DS3 port, 2-10DS3TMX

subport, 2-15DS3TMX port, 2-13E1 port, 2-31E3 port, 2-33EC1 port, 2-18Ethernet port, 7-20SDH port, 2-41SONET port, 2-26STS1TMX

subport, 2-15PLCT Threshold

EOS portadvanced, 7-101

Policersalgorithm, 7-170bandwidth profiles, 7-171create

Ethernet cards, 7-172

guidelines, 7-171description, 7-169

Portconfiguration

checklist, 9-6number

TransAccess 200 Mux, 1-17virtual

bandwidth, 7-51Port-based tagging

Ethernetport, 7-20

Primary reference, 1-18Protected services

create, 4-71guidelines, 4-72

ProtectionCarrier Ethernet Protection Pair

line, 3-4path, 3-5

groupCarrier Ethernet Protection Pair, 3-32

Protection groups1+1 APS/MSP

2-port OC-48/STM-16, 4-732-port OC-48, 4-73configuration

checklist, 9-5UPSR/SNCP

2-port OC-48/STM-16, 4-73Provisioning

checklists, 9-1

QQueuing policy

Ethernet port, 7-22traffic

management, 7-153

RRandom early discard

configurationdefaults, 7-177

description, 7-175thresholds

customize, 7-178view, 7-181

weightcurve, 7-176

RDI, see Remote defect indicatorRead community

TransAccess 200 Mux, 1-17


Index

Recovery pulse widthEthernet port, 7-19STM port, 2-38

RED, see Random early discardRemote defect indicator

DS3, 2-32Requirements

drop and continue service, 5-22optical transmux service, 5-40

Resource advisorydefinition, 4-2

Reversesection trace


section trace formatSDH port, 2-39SONET port, 2-24

RSTPfeature description, 7-104virtual

bridge, 7-109description, 7-109multiple copies

SSD BER

EC1 port, 2-17line, 2-22SONET port, 2-22

SDHequipment requirements, 2-28port

AIS mask, 2-37alarm profile, 2-41control data, 2-39customer, 2-41customer tag, 2-41DUS, 2-37forward section trace, 2-39forward section trace format, 2-39performance monitoring template, 2-41reverse section trace, 2-39reverse section trace format, 2-39SF BER

line, 2-37terminate DCC, 2-40transmitter state, 2-37

serviceendpoints, 4-49, 9-16

Serviceaggregate

guidelines, 4-76OC-48 UPSR, 4-75

creation checklist, 9-7deactivating

EOS links with LCAS, 7-96drop-and-continue services, 5-19endpoints

summary, 9-9Ethernet

port PM, 7-145high order

payload mapping, 4-24, 4-48hop-by-hop, 4-6protected uplinks, 4-73SDH

endpoints, 4-49, 9-16switch

DS1, 5-35DS1 traffic, 5-47E1, 5-36

transparentSDH example, 5-51SONET example, 5-50

VC-MUXprovisioning, 4-48

VT MUXendpoint requirements, 4-28, 9-13SDH endpoints, 4-50, 9-17

VT-MUXprovisioning SONET, 4-24

ServicesEoPDH

restrictions, 4-28, 4-52, 7-137, 9-13, 9-19Ethernet

configuration guidelines, 7-134determining, 7-126MAC address forwarding, 7-123multipoint control channel, 7-123

multipoint, 7-123search

filters, 4-32, 4-55, 7-138Service-tagged

Ethernetport, 7-20

SF BEREC1 port, 2-17line, 2-22, 2-37SDH port, 2-37SONET port, 2-22

SNMPnode

agent port, 1-16configuration, 1-16


Index

counters, 1-15direct node support, 1-15ems.mib, 1-17MIB, 1-17northbound interface, 1-15proprietary MIB, 1-15SNMP v1/v2c, 1-15

SONETport

AIS mask, 2-22alarm profile, 2-26change parameters, 2-21control data, 2-24customer, 2-26customer tag, 2-26DUS, 2-22forward section trace, 2-24forward section trace format, 2-24performance monitoring template, 2-26reverse section trace, 2-24reverse section trace format, 2-24SD BER line, 2-22SF BER line, 2-22SS bit transmit, 2-24terminate DCC, 2-25transmitter auto shutdown, 2-23transmitter state, 2-22

SS bit transmitSONET port, 2-24

StandardEOS ports, 7-16

Starting AUG1 numbersVC3 paths, 4-54VC4 paths, 4-54

STMport

current transmitter state, 2-38recovery pulse width, 2-38transmit auto shutdown, 2-38

STM-64uplinks

protected services, 4-73STS1TMX

portAIS format, 2-12, 5-45AIS mask, 2-12, 5-45customer, 2-13customer tag, 2-13DS3 mapping, 2-12, 5-45line format, 2-12, 5-45subport mapping, 5-45subport numbering, 2-12, 5-45

subport

line format, 2-14, 2-15PM template, 2-15

Subportalarm

profile, 2-15mapping

STS1TMX port, 5-45numbering

DS3TMX port, 2-12STS1TMX port, 2-12, 5-45

Switchingbi-directional, 4-71capacity

slot-to-slot, 4-72System access methods, 1-8

TTagging

Ethernet port, 7-20Terminate DCC


Third-party equipmentdisable control data, 5-54

Timingconnections, 1-18example, 1-17global option, 1-18

Topologyupdate

add note to ring, 8-5diagram, 8-3

Trafficcongestion

EOP port, 7-82, 7-152management

auto-negotiation, 7-152description, 7-150marking packets, 7-156maximum information rate, 7-152pause control, 7-152policer description, 7-169policing description, 7-165preventing network loops, 7-155queuing policy, 7-153queuing priority, 7-154queuing schedule, 7-154reception behavior, 7-148setting bandwidth, 7-154transmission behavior, 7-149

TransAccess 200 Muxport number, 1-17read community, 1-17


Index

write community, 1-17Transmitter

auto shutdownEthernet port, 7-19STM-N port, 2-38

current stateSTM port, 2-38

stateEthernet port, 7-18SDH port, 2-37SONET port, 2-22

Transmuxservice

cards required, 5-37configure, 5-43configure optical attributes, 5-46provision guidelines, 5-41required procedures, 5-42

standardG.747 services, 5-34

Transparentservice

disable control data parameter, 5-54Transparent service

bytes forwarded, 5-50, 5-51cards required, 5-52create, 5-49, 5-52guidelines, 5-53provision, 5-55SDH example, 5-51SONET example, 5-50

Typologyupdate

add node to protection group, 8-9

UUplinks

protected services, 4-73UPSR/SNCP

2-port OC-48/STM-16protection group, 4-73

VVC3 paths, 4-54VC4 paths, 4-54VCAT see Virtual concatenationVideo broadcast

configuration, 5-22Virtual

concatenationdescriptionPDH circuits

RSTPdescription, 7-109

VLANbundling

description, 7-11determining service, 7-126

VRB, see Virtual RSTPVT MUX

serviceendpoint requirements, 4-28, 9-13SDH endpoints, 4-50, 9-17

WWFQ

CoS 1 to 4Ethernet port, 7-23

queuing policyEthernet port, 7-22

Write communityTransAccess 200 Mux, 1-17


Index


Visit our website at:www.force10networks.com

Release TR3.2.2 Traverse System Documentation800-0003-TR322

www.turinnetworks.com

Traverse Provisioning Guide - Force10...Release TR3.2.2 Force10 Networks Page 1-7 SECTION...

Documents

Transcript of Traverse Provisioning Guide - Force10...Release TR3.2.2 Force10 Networks Page 1-7 SECTION...