Lucent Technologies DMX Access Multiplexer Applications and Planning Guide

C-4 Redundant Routes with the Level 2 Subdomain

Assigning Areas

C-3 Assigning Subdomains

C-6

Recommended Area Assignments

C-7

C-8

C-9

Level 2 Router Assignments on an OSI LAN

C-10 OSI LAN Redundancy

D Physical, Electrical, and Thermal Compatability Requirements for ODP Applications

D-1 DMX Shelf Side/Front View with Mounting Bracket

D-2 DMXtend Shelf Side/Front View with Mounting Bracket

D-3 DMXplore Wall-mount Shelf Side/Front View with

Mounting Bracket

D-4 DMXplore Rack-mount Side/Front View with

Mounting Bracket

D-5 Mounting Bracket Positions on DMX Shelf

365-372-300

Issue 8.0 September 2006

F I G U R E S x x i

F I G U R E S x x i i

365-372-300

Issue 8.0 September 2006

List of Tables

1 System Overview

1-1 Interface Densities

4 Product Description

4-1 Interface Densities

4-2 Circuit Packs in DMX Shelf

4-3 Main packs that allow portless LNW20 operation

4-4 DMX 30 Amp High Capacity Shelf Power

4-5 DMX 20 Amp High Capacity Shelf Power

4-6 High-capacity Shelf Current Drains

4-7 Bay Current Drains

4-8 High-capacity Shelf Heat Dissipation

4-9 Cables

5 System Planning and Engineering

5-1 Circuit packs with medium sized switch fabric

5-2 0x1 compatible combinations

5-3 Ethernet Circuit Pack Capacities Summary Part 1

5-4 Ethernet Circuit Pack Capacities Summary Part 2

5-5 Ethernet Circuit Pack Capacities for Ring Configuration

5-6 All Allowable UPSR Add-drop Cross-connections

5-7 All Allowable 1+1 Add-drop Cross-connections

365-372-300

Issue 8.0 September 2006

T A B L E S x x i i i

5-8 All Allowable BLSR Add-drop Cross-connections

5-9 All Allowable Hairpin Cross-connections

5-10 Sync Messages with the S1 Byte

6 Operations, Administration, Maintenance, and Provisioning

6-1 SYSCTL Faceplate Indicators and Functions

6-2 IAO LAN Compatibility

6-3 DMX OI Compatibility Summary

6-4 DCC Protection Modes1

6-5 DCC Compatibility

6-6 Remote Software Download Compatibility

6-7 STS-1 Test Access

6-8 VT1.5 Test Access

6-9 Provisionable PM Parameters

6-10 DMX Time and Date Synchronization Compatibility

6-11 Remote NE Status Compatibility

6-12 Characters NOT Allowed in a WaveStar

CIT Password

6-13 Characters Allowed in a WaveStar

CIT Password

6-14 Characters NOT Allowed in a DMX Password and User ID 6-128

6-15 Characters Allowed in a DMX Password and User ID

7 Ordering

7-1 Orderable Software

7-2 Orderable Documentation

7-3 Lightguide Build-outs and Accessories

7-4 PTM Optics for LNW37/45/49/59/62/63/64/70/73/73C/74/78 7-9

7-5 Miscellaneous Accessories

T A B L E S x x i v

365-372-300

Issue 8.0 September 2006

10 Technical Specifications

10-1 Transmission Interface Standards

10-2 PTM Optics for LNW37

10-3 PTM Optics for LNW45

10-4 PTM Optics for LNW49

10-5 SONET Optical System Specifications

10-6 SONET Optical Transmitter Information

10-7 SONET Optical Receiver Information

10-8 SONET Optical Specifications and Link Budgets

10-9 SONET Optical System Specifications

10-10 SONET Optical Transmitter Information

10-11 SONET Optical Receiver Information

10-12 SONET Optical Specifications and Link Budgets

10-13 SONET Optical System Specifications

10-14 SONET Optical Transmitter Information

10-15 SONET Optical Receiver Information

10-16 SONET Optical Specifications and Link Budgets

10-17 SONET Optical System Specifications

10-18 SONET Optical Transmitter Information

10-19 SONET Optical Receiver Information

10-20 SONET Optical Specifications and Link Budgets

10-21 SONET Optical System Specifications

10-22 SONET Optical Transmitter Information

10-23 SONET Optical Receiver Information

10-24 SONET Optical Specifications and Link Budgets

10-25 PTM Optics for LNW62

10-26 SONET Optical System Specifications

10-27 SONET Optical Transmitter Information

10-28 SONET Optical Receiver Information

365-372-300

Issue 8.0 September 2006

T A B L E S x x v

10-29 SONET Optical Specifications and Link Budgets

10-30 SONET Optical System Specifications

10-31 SONET Optical Transmitter Information

10-32 SONET Optical Receiver Information

10-33 SONET Optical Specifications and Link Budgets

10-34 SONET Optical System Specifications

10-35 SONET Optical Transmitter Information

10-36 SONET Optical Receiver Information

10-37 Optical Specifications and Link Budgets

10-38 SONET Optical System Specifications

10-39 SONET Optical Transmitter Information

10-40 SONET Optical Receiver Information

10-41 OC-48 DWDM OLIUs Wavelength Plan

10-42 Optical Requirements and Link Budgets for the

OC-48 DWDM OLIUs

10-43 PTM Optics for LNW59

10-44 SONET Optical System Specifications

10-45 SONET Optical Transmitter Information

10-46 SONET Optical Receiver Information

10-47 Optical Specifications and Link Budgets

10-48 SONET Optical System Specifications

10-49 SONET Optical Transmitter Information

10-50 SONET Optical Receiver Information

10-51 Optical Specifications and Link Budgets

10-52 SONET Optical System Specifications

10-53 SONET Optical Transmitter Information

10-54 SONET Optical Receiver Information

10-55 Optical Specifications and Link Budgets

10-56 SONET Optical System Specifications

10-57 SONET Optical Transmitter Information 10-87

10-58 SONET Optical Receiver Information 10-87

10-59 OC-192 DWDM OLIUs Wavelength Plan

T A B L E S x x v i

365-372-300

Issue 8.0 September 2006

10-60 Optical Specifications and Link Budgets

10-61 PTM Optics for LNW63/64/70/73/73C/74/78

10-62 1000BASE-SX Operating Range Over Each

Optical Fiber Type

10-63 1000BASE-SX Transmit Specifications

10-64 1000BASE-SX Receive Specifications

10-65 1000BASE-SX Link Budgets and Penalties

10-66 1000BASE-LX Operating Range

10-67 1000BASE-LX Transmit Specifications

10-68 1000BASE-LX Receive Specifications

10-69 1000BASE-LX Link Budgets and Penalties

10-70 1000BASE-ZX Operating Range

10-71 1000BASE-ZX Transmit Specifications

10-72 1000BASE-ZX Receive Specifications

10-73 1000BASE-ZX Link Budgets and Penalties

10-74 100BASE-LX Operating Range Single-Mode Fiber

10-75 100BASE-LX Transmit Specifications

10-76 100BASE-LX Receive Specifications

10-77 100BASE-LX Link Budgets and Penalties

10-78 ESCON Optics Operating Range Multi-Mode Fiber

10-79 ESCON Transmit Specifications

10-80 ESCON Receive Specifications

10-81 ESCON Maximum Link Loss

10-82 Transmission Delay in Microseconds

10-83 DMX 30 Amp High Capacity Shelf Power

10-84 DMX 20 Amp High Capacity Shelf Power

10-85 High-capacity Shelf Current Drains

10-86 Bay Current Drains

10-87 High-capacity Shelf Heat Dissipation

10-88 Optical specifications

365-372-300

Issue 8.0 September 2006

T A B L E S x x v i i

A Ethernet/SAN

A-1 1way Cross-Connection Support

A-2 Allowed Traffic Management Modes per Port Type

A-3 Handling of Untagged or Unprovisioned service at

Boundary Ports

A-4 Default mapping of User Priority to CoS

A-4 Default mapping of DSCP to CoS

A-5 Combination of VLAN Tagging and

Traffic Management Modes

A-6 Ethernet Private Line Services

A-7 Ethernet Packet Ring Services

A-8 VCGs Available on Ethernet Circuit Packs

A-9 Supported Ethernet Services

A-10 Typical Ethernet Service Configurations

B Performance Monitoring

B-1 Data Registers

B-2 SONET OC-N Performance Parameters

B-3 SONET EC-1 Performance Parameters

B-4 SONET E1 Performance Parameters

B-5 SONET STS-N Performance Parameters

B-6 SONET VT1.5 Performance Parameters

B-7 SONET VC-12 Performance Parameters

B-8 DS3 Performance Parameters

B-9 DS3 Signal formats, PM signal formats, and VM modes

B-10 DS1 Performance Parameters

B-11 CV-PFE parameter increments

B-12 Ethernet Performance Parameters

T A B L E S x x v i i i

365-372-300

Issue 8.0 September 2006

C IS-IS Level 2 Routing Guidelines

C-1 Area Addresses

D Physical, Electrical, and Thermal Compatability Requirements for OSP Applications

D-1 Metropolis

Dimensions and Weight

D-2 DMX Shelf Power Supply Requirements

D-3 DMX 20 Amp High Capacity Shelf Power

D-4 DMX Shelf Current Drains

D-5 DMX Power Supply Requirements

D-6 DMXtend Shelf Current Drains

D-7 DMXplore Power Supply Requirements

D-8 DMXplore Shelf Current Drains

365-372-300

Issue 8.0 September 2006

T A B L E S x x i x

T A B L E S x x x

365-372-300

Issue 8.0 September 2006

About this information product

Purpose

This applications and planning guide (APG) provides the following information for the Metropolis

DMX Access Multiplexer:

• Features

• Applications

• Operation

• Engineering

• Support

• Specifications

• Ordering

Reason for reissue

Issue 8.0 of this document details features associated with Release 7.0 of DMX. Release 7.0 includes software enhancements and introduces new hardware to support the R7.0 features detailed herein.

365-372-300

Issue 8.0 September 2006 x x v

Safety labels

This document may contain safety labels in the form of

DANGERS

WARNINGS

, and

CAUTIONS

These admonishments have the following definitions:

•

DANGER

shows the presence of a hazard that will cause death or severe personal injury if the hazard is not avoided.

•

WARNING

shows the presence of a hazard that can cause death or severe personal injury if the hazard is not avoided.

•

CAUTION

shows the presence of a hazard that will or can cause minor personal injury or property damage if the hazard is not avoided. Caution is also used for property-damage-only accidents.

This includes equipment damage, loss of software, or service interruption.

The alert symbol appears throughout this document to alert the user to these safety labels.

Intended audience

This applications and planning guide is intended for network planners and engineers. However, it is also for anyone who needs specific information regarding the features, applications, operation, engineering, and ordering of the DMX Access Multiplexer.

How to use this information product

The following is a brief description of the contents of each chapter in this document:

•

“About This Document”

describes the purpose, intended audience, reason for reissue, and organization of this document. This section references related documentation and explains how to order, make comments, or recommend changes to this document.

• Chapter 1,

“System Overview,”

describes the DMX Access

Multiplexer. This introductory section also lists the features included in the releases covered by this document.

• Chapter 2,

“Features,”

briefly describes the features listed in

Chapter 1. These features are described in more detail in Chapter

3, “Network Topologies,” Chapter 4, “Product Description,” and

Chapter 6, “Operations, Administration, Maintenance, and

Provisioning.”

• Chapter 3,

“Applications and Configurations,”

describes how the

DMX Access Multiplexer shelf serves diverse needs such as embedded network evolution, access transport for voice and private line services, interoffice transport, broadband business data access, DSLAM access, IP network infrastructure, enterprise

x x v i

365-372-300

Issue 8.0 September 2006

LAN interconnect and transport, ISP carrier access, and cable access to internet applications through configurations such as path switched ring, linear optical extensions, homing, and hubbing.

• Chapter 4,

“Product Description,”

describes the DMX Access

Multiplexer hardware, including the shelf, circuit packs, cables, and power.

• Chapter 5,

“System Planning and Engineering,”

summarizes physical arrangement, cross-connection, and synchronization information to help you plan procurement and deployment of the

DMX Access Multiplexer.

• Chapter 6,

“Operations, Administration, Maintenance, and

Provisioning,”

defines the “maintenance philosophy,” outlining the various features available to monitor and maintain the DMX

Access Multiplexer.

• Chapter 7,

“Ordering,”

provides equipment ordering information for the DMX Access Multiplexer.

• Chapter 8,

“Product Support,”

describes how Lucent Technologies supports the DMX Access Multiplexer. This chapter includes information about engineering and installation services, technical support, documentation support, and training available from

Lucent Technologies.

• Chapter 9,

“Reliability and Quality,”

provides the Lucent

Technologies quality policy and describes the reliability program.

• Chapter 10,

“Technical Specifications,”

lists the technical specifications for the Metropolis

DMX Access Multiplexer.

• Appendix A,

“Ethernet/SAN,”

details all Ethernet/SAN specific equipment and specifications relevant to the Metropolis

DMX

Access Multiplexer.

• Appendix B,

“Performance Monitoring,”

primarily lists the performance monitoring parameters for the Metropolis

DMX

Access Multiplexer.

• Appendix C,

“IS-IS Level 2 Routing Guidelines,”

provides guidelines for L2 routing on the Metropolis

DMX Access

Multiplexer.

• Appendix D,

“Physical, Electrical, and Thermal Compatibility

Requirements for OSP Applications”

provides guidelines for the installation of the DMX, DMXtend, and DMXplore in OSP cabinet applications.

365-372-300

Issue 8.0 September 2006 x x v i i

• Glossary provides definitions for telecommunication acronyms and terms.

• Index supplies users with specific subjects and corresponding page numbers to find necessary information.

Conventions used

Bold

typeface signifies emphasis.

Italic typeface denotes a particular product line or information product.

Bold Courier

typeface signifies a command.

For the remainder of this information product, “DMX” is used in place of Metropolis

DMX Access Multiplexer in most cases.

Electronic documentation

Documentation for the DMX Access Multiplexer is now available in electronic form, on compact disk read only memory (CD-ROM). CD-

ROM has many advantages over traditional paper documentation, including cost savings and search and retrieve capability.

Ordering information

CD-ROM documentation is available by annual subscription (on standing order). To order, call your Technical Information Resource

Manager, your Lucent Technologies Account Executive, or the Lucent

Technologies Customer Information Center (

1-888-582-3688

Pricing information

For pricing information or a list of all documents that are available on

CD-ROM, contact your Lucent Technologies Network Systems

Account Executive or the Lucent Technologies Customer Education and Training hotline (

1-800-334-0404

Technical information

For technical information, call Lucent Technologies Documentation

Support (

1-888-LTINFO6

How to comment Fax

Fax comments to

(407) 767-2760

Phone

You may also report errors or request changes to this document by calling the toll-free number,

1-888-LTINFO6 (1-888-584-6366)

. When calling, be sure to have the nine-digit document number ready.

x x v i i i

365-372-300

Issue 8.0 September 2006

Email

Comments may be sent via email to

[email protected]

World Wide Web

Comments may also be sent by filling out a web-based form at

www.lucent-info.com

How to order

To order additional copies of this document or to request placement on the standing order list, refer to the information below.

Commercial customers

A check, money order, purchase order number, or charge card number is required with all orders. Make checks payable to Lucent

Technologies. Lucent Technologies entities should use Form 1-80.80

FA, available through the Customer Information Center (CIC). RBOC/

BOC customers should process orders through your Company

Documentation Coordinator.

Internet orders

Hardware, software, and documentation may be ordered on the world wide web. For more information, visit Lucent on the web at

www.lucentdocs.com

From Canada: email orders to [email protected].

Mail orders

To order documentation by mail, send correspondence to the address below:

Lucent Technologies

Customer Information Center

Attention: Order Entry Section

2855 North Franklin Road

P.O. Box 19901

Indianapolis, IN 46219

Telephone orders

Within US: 1-888-LUCENT-8 (1-888-582-3688)

From Caribbean, Latin America, and Canada: (Toll) 1-317-322-6616

From Europe, Middle East, and Africa: (Toll) 1-317-322-6416

From Asia/Pacific Region, China, Australia, and New Zealand:

(Toll) 1-317-322-6411

FAX orders

Within US (24 hrs/day, toll free): 1-800-566-9568

365-372-300

Issue 8.0 September 2006 x x i x

International: 1-317-322-6699

x x x

365-372-300

Issue 8.0 September 2006

1 System Overview

Overview

Purpose

This chapter introduces the Metropolis

DMX Access Multiplexer system.

Contents

The following topics are included in this chapter:

Overview of the Metropolis

Portfolio

Metropolis

Metro Access Solutions

Metropolis

DMXplore Access Multiplexer

Metropolis

DMXtend Access Multiplexer

Introduction to the DMX Access Multiplexer

Feature Release Plan

365-372-300

Issue 8.0, September 2006

1 - 1

System Overview

Overview of the Metropolis

Portfolio

Purpose

Metropolitan, "metro," networks are the communications networks that link homes and businesses to larger, long-distance core networks.

These networks are complex because they are filled with both old and new networking equipment and must carry all types of service traffic, including voice, data and video.

Driven by the exponential growth of the Internet, requirements for metropolitan optical transport networks are changing quickly from pure circuit networks to hybrid networks. This evolution requires metro access networks to aggregate the local loop or last-mile bandwidth in order to integrate with the high-speed core/backbone networks. These requirements are driving metropolitan network evolution from traditional SONET multiplexers into more flexible, higher-speed, dataaware platforms—a necessity for optical edge solutions.

Solution

Lucent Technologies is helping service providers to cost-effectively deploy solutions that can accommodate a multitude of services, such as voice, private line, Ethernet, IP, frame relay, and ATM. The Metropolis

portfolio offers a seamless evolution to next-generation metro solutions that can eliminate the bottleneck in the metropolitan network, allowing service providers to deliver new high-speed, revenue-generating services such as gigabit Ethernet, virtual private networks (VPN), storage area networks and digital subscriber lines (DSL).

1 - 2

365-372-300

Issue 8.0, September 2006

Overview of the Metropolis® Portfolio

System Overview

Portfolio

Lucent designed its Metropolis

portfolio so customers can choose the solution that best accommodates their existing networks, allowing them to bring new services to market quickly and cost effectively.

Metropolis

includes two categories of next-generation products based on the most common types of metro networks:

• Next-Generation SONET—Metropolis DMX, DMXtend,

DMXpress, and DMXplore Access Multiplexers— which leverages existing optical equipment while providing a solid foundation for future bandwidth, gigabit Ethernet (GbE) and IP services growth.

• MetroWDM—Metropolis EON (Enhanced Optical Networking),

Lambda Unite, and Metropolis WSM, metro core DWDM solutions for regional traffic.

Each of the Metropolis

solutions can fuse with Lucent’s new multiservice data switches and existing IP and ATM equipment to provide an end-to-end broadband network that links to long-distance or other metro networks.

Low Cost Access

Metropolis

DMX

tend

Metropolis

DMX

plore

Metropolis

DMX

plore

SONET/SDH Metropolitan Access/

DSLAM Access Transport

(Stinger)

Globe Aggregation and Transport

(Optical Edge Service)

Multiservice TDM

Bulk Carrier/to carrier

Interconnect

(Wavelength Service)

Digital Video Services

(WaveStar

DVS)

Metropolis

DMX/ADM

TDM to IP Services Migration

High Margin Ethernet Services

High Security Multiservices

Access (PSAX, Stinger,

GX SSQ, Springtide)

Low Cost Last Mile Aggregation

Scaleability from 2.5G to

10G to 40G and Beyond

GX 550

WaveStar

TDM 2.5G/10G

Metro EON

(40G/80G)

Lambda Unite

Metropolis WSM

WaveStar

OLS 1.6T

Metropolitan Core

WaveStar

OLS 1.6T

WaveStar

OLS 1.6T

Multiservice

Edge Node

Optical Core - Long Haul

2.5G = WaveStar TDM 2.5G (OC-48) 2F

10G = WaveStar TDM 10G (OC-192) 2F

DMX = Metropolis DMX Access Multiplexer

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

DMX

plore

= Metropolis DMX plore Access Multiplexer

ADM = Metropolis ADD/Drop Multiplexer nc-dmx-111

WSM= Metropolis WaveLength Services Manager

365-372-300

Issue 8.0, September 2006

1 - 3

System Overview

Metropolis

Metro Access Solutions

Overview

This section provides a brief description of each of the following products which comprise the Metropolis portfolio:

• Metropolis

DMXplore Access Multiplexer

• Metropolis

DMXtend Access Multiplexer

• Metropolis

DMX Access Multiplexer

1 - 4

365-372-300

Issue 8.0, September 2006

System Overview

Metropolis

DMXplore Access Multiplexer

Overview

DMXplore is ideal for Fiber-to-the-Business (FTTB) and end-user access applications. It has been designed with an extremely small footprint to enable seamless integration as a piece of customer premise equipment (CPE). Supporting OC-3/12 high-speed, DS1/DS3, and 10/

100 Mbps Ethernet tributary interfaces, DMXplore is an ideal nextgeneration CPE for its ability to provide voice and data devices to a variable number of end-users.

DMXplore is designed with a modular architecture to support protected or unprotected DS1 and DS3 transport applications using OC-3/12 high-speed interfaces. This modular architecture supports separate working and protection circuit packs, thus allowing the continuation of service in the event of failures.

DMXplore features combo cards supporting OC-3/12 high-speed interfaces as well as the switch fabric servicing the DS1/DS3 ports.

The DMXplore is optimized for low-cost, small footprint entry into end-user environments. The DMXplore can be placed in an office building, medical facility, hotel, college dormitory, or any building housing a moderate amount of multiple end users. In its ability to provide a flexible mix of DS1, DS3, and 10/100 Mbps interfaces, the

DMXplore is ideal as a collection point for multiple lines within a diverse MTU (Multi-Tenant Unit), providing a variety of both voice and data services.

Figure 1-1 DMXplore providing enterprise access

DMX

plore

- DS1/-3 provides:

- 10/100 Mbp Ethernet

DMX

plore

DMX

plore

Metropolis

DMX

tend

OC-12

Metropolis

DMX

UPSR

Metropolis

DMX

tend

OC-3 UPSR/1+1

DMX

plore

OC-3

UPSR

DMX

plore

Metropolis

DMX

Metropolis

DMX

press

OC-48/192 UPSR

Metropolis

DMX

Metro Core

DMX = Metropolis

DMX Access Multiplexer

DMX

tend

= Metropolis

DMX

tend

Access Multiplexer

DMX

plore

= Metropolis

DMX

plore

Access Multiplexer

MA-DMXplore-11

365-372-300

Issue 8.0, September 2006

1 - 5

System Overview

Metropolis

DMXtend Access Multiplexer

Introduction to DMXtend

The DMXtend Access Multiplexer is a single-shelf network multiplexer designed primarily for access transport, business access, and regional interoffice applications transporting voice, data, and SAN traffic at the OC-3/12/48/192 level via 1+1, or unidirectional path switched ring (UPSR) protected lines.

DMXtend supports a wide array of wideband and broadband transport, including traditional SONET transport of DS1, E1, DS3, EC-1,

TransMUX, OC-3, OC-12, OC-48, OC-192 as well as 10/100/1000

Mbps LAN, Resilient Packet Ring (RPR), and FICON/ESCON/Fibre-

Channel SAN transport. The shelf can be equipped to serve many diverse network applications and supports a variety of operations interfaces for current and evolving network operations needs.

The figure below shows the DMXtend providing loop access for the various interfaces listed above, and interworking with DDM and

FT-2000 to enable a network transition to next-generation, higher capacity services, and shows how the DMXtend can interwork with embedded, legacy equipment.

Figure 1-2 Next-generation Loop Access with DMXtend

Access Loop

DS1/3

10/100/1000

MbPS

Metropolis

DMX tend

Metropolis

DMX tend

DS1/3

Fiber

Reach

DS1/3

Metropolis

DMX tend

For TR-008 DLC

DS1/3

10/100/1000

MbPS

Metropolis

DMX tend

DDM

OC-48

OC-3

Central

Office

DS1s

DCS

STS-1

OC-3

Sx:x

LNW67

1G SX

LUCENT

BRK A 20A

LNW26

OC-48 Sx:x 1310 LR

LUCENT

LNW1

SYSCTL Sx:x

LUCENT

BRK B 20A

177D

BLANK Sx:x

LUCENT

LNW26

OC-48 Sx:x 1310 LR

LUCENT

LNW36

OC-3 Sx:x

LUCENT

LNW36

OC-3 Sx:x

LUCENT

Sx:x

LNW46

LUCENT

OC-12 1310LR

Sx:x

LNW46

LUCENT

OC-12 1310LR

LNW6

28DS1 Sx:x

LUCENT

LNW6

28DS1 Sx:x

LUCENT

LNW16

12DS3/EC1 Sx:x

LUCENT

LNW16

12DS3/EC1 Sx:x

LUCENT

FAULT

ACTIVE

28DS1

FAULT

ACTIVE

28DS1

FAULT

ACTIVE

FAULT

ACTIVE

12DS3/

EC1

12DS3/

EC1

1G SX

FAULT

ACTIVE

OUT IN

FAULT

ACTIVE

OC-48

OLIU

OUT IN

SEL

UPD/

INT

LAN

CIT

232

FAULT

ABN

ACO

TEST

IND

177D

BLANK

FAULT

ACTIVE

OC-48

OLIU

OUT IN

FAULT

ACTIVE

OC-3

OLIU

FAULT

ACTIVE

OC-3

OLIU

OUT IN OUT IN

FAULT

ACTIVE

OC-12

OLIU

FAULT

ACTIVE

OC-12

OLIU

1 1 OUT IN OUT IN

1 1

2 2

4 4

A1 A2 B1 B2 G1 M1 CTL G2 M2

DMX

C1 C2 D1 D2

DS3,OC-3

For TR-303 DLC

FR/ATM

Edge

Class 5

Switch

"5ESS"

Switch (es)

OC-12

DDM

DS1/3

10/100 MbPS

OC-3

Metropolis

DMX tend

DMX = Metropolis

DMX Access Multiplexer

DMX tend

= Metropolis DMX tend Access Multiplexer

DDM

NC-DMXtend-002

1 - 6

365-372-300

Issue 8.0, September 2006

System Overview

Introduction to the DMX Access Multiplexer

Overview

The DMX Access Multiplexer is a single-shelf network multiplexer designed primarily for access transport, business access, and regional interoffice applications transporting voice and data at the

OC-12/OC-48/OC-192 level via a UPSR, BLSR, or 1+1 linear optical extension.

Lucent’s rich history of SONET multiplexers provides the foundation for the DMX. The DMX builds on that tradition by providing the tools necessary for the new generation of access networks: greater capacity, increased network flexibility, diverse functionality, and reliable service.

DMX, a SONET line terminating network element, supports a wide array of wideband and broadband transport, including traditional

SONET transport of DS1, E1, DS3, EC-1, TransMUX, OC-3, OC-12,

OC-48, and OC-192 signals, as well as 10/100/1000 Mbps LAN,

Resilient Packet Ring (RPR) and FICON/ESCON/Fibre-channel SAN transport. The shelf can be equipped to serve many diverse network applications and supports a variety of operations interfaces for current and evolving network operations needs.

Functionality

There are 13 circuit pack slots in each shelf, consisting of the following:

• 1 Control slot (CTL) for the SYSCTL (LNW1 or LNW2)

• 2 Main slots (M1, M2) for high-speed optical line interface units

(OC-12, OC-48, or OC-192) or the Main Switch Pack (LNW80)

• 8 multipurpose Function Unit slots (A through D) for DS1, DS3,

E1, TransMUX, EC-1, OC-3, OC-12, OC-48, 10/100BASE-TX/

LX and 10/100BASE-TX/LX Private Line, 1000BASE-SX,

1000BASE-LX, RPR, ESCON, FICON, and Fibre-Channel service

• 2 Growth slots (G1, G2) for OC-3, OC-12, OC-48,

1000BASE-X SX/LX, optical 100BASE-LX, RPR, ESCON,

FICON, and Fibre-Channel service. In R7.0, Growth slots can also host the LNW20 TransMUX card in portless DS3 mode.

The Growth slots are regarded as Function Unit slots in Release

7.0, but in the future may also be used for additional features.

365-372-300

Issue 8.0, September 2006

1 - 7

Introduction to the DMX Access Multiplexer

System Overview

Release 7.0 supports the following circuit packs:

• System Controller (LNW2)

• 28DS1 (LNW6)

• 28DS1PM (LNW7)

• 56DS1/E1 (LNW8)

• 12-port DS3 TransMUX (LNW18)

• 48TMUXDS3EC1 (LNW20)

• 12DS3/EC1 (LNW16)

• 48DS3/EC1 (LNW19)

• 48DS3/EC1 with terminal loopbacks (LNW19B)

• Quad OC-3 OLIU (LNW36)

• Eight-port OC-3 PTM OLIU (LNW45)

• Quad OC-3 PTM OLIU (LNW37)

• Dual OC-12 OLIU (LNW46)

• OC-12 OLIU (LNW48)

• Quad OC-12 PTM OLIU (LNW49)

• OC-12 OLIU (LNW50)

• OC-12 OLIU (LNW54)

• Quad OC-48 PTM OLIU (LNW62)

• OC-48 OLIU (LNW26B)

• OC-48 OLIU (LNW27)

• OC-48 OLIU (LNW28)

• OC-48 OLIU (LNW29)

• OC-48 OLIU (LNW76)

• OC-48 OLIU (LNW77)

• OC-48 OLIU (LNW31)

• OC-48 OLIU (LNW32)

• OC-48 DWDM OLIUs (LNW421-459, LNW221-259, and

LNW121B-159B) (32 wavelengths for both network and tributary interfaces)

• OC-192 OLIU (LNW56)

• OC-192 OLIU with Tone Circuitry (LNW57)

1 - 8

365-372-300

Issue 8.0, September 2006

Introduction to the DMX Access Multiplexer

System Overview

• OC-192 OLIU with Tone Circuitry and on-board amplifier

(LNW60)

• OC-192 OLIU (LNW58)

• Dual OC-192 OLIU (LNW59)

• OC-192 OLIU (LNW523— DWDM, 4-color tunable)

• OC-192 OLIU (LNW527— DWDM, 4-color tunable)

• OC-192 OLIU (LNW554— DWDM, 4-color tunable)

• OC-192 OLIU (LNW555)

• 1G SX/LX Private Line (4— 1000BASE-LX/SX ports) (LNW63)

• Octal 1GbE Private Line (8 —1000BASE-SX/LX/ZX optical and/ or electrical 1000BASE-TX) (LNW64)

• 10/100Mbps (24 100BASE-TX ports) (LNW66)

• 1G SX (2— 1000BASE-SX ports) (LNW67)

• 1G LX (2— 1000BASE-LX ports) (LNW68)

• 100/1000 Mbps (4— 100BASE-LX and

4— 1000 BASE-X ports) (LNW70)

• 10/100Mbps Private Line (24— 100BASE-TX ports) (LNW71)

• SAN circuit pack (FC-DATA) with choice of FICON/ESCON/

Fibre-channel interfaces using PTM optics (LNW73)

• SAN circuit pack with compression, choice of FICON/ESCON/

Fibre-channel interfaces using PTM optics (LNW73C)

• 10/100Mbps Private Line (8— 100BASE-X and

16 100BASE-TX ports) (LNW74)

• 10/100Mbps RPR (4— 100BASE-X and 2 1000BASE-X ports)

(LNW78)

• Electric Continuity Test Tool (for DS1/DS3/Ethernet Cabling)

(LNW94 and LNW93)

• Main Switch Pack— no optics (LNW80)

Important!

DS1, DS3, EC-1, E1, TransMUX, and 10/100-TX functionality is not supported in the Growth slots. 100 BASE-LX

(optical Fast Ethernet) functionality is supported in Growth Slots.

365-372-300

Issue 8.0, September 2006

1 - 9

Introduction to the DMX Access Multiplexer

System Overview

Interface Density

DMX provides a VT1.5 and STS-1 cross-connect fabric. DMX’s main switch fabric is contained in each of the high-speed (network-side interface) circuit packs, located in the MAIN slots. The MAIN slots house OC-12, OC-48, and OC-192 high-speed interfaces. They can also house the LNW80 switch pack. The LNW59 VLF Main enables

0x1 Fn/Growth slot equipage beginning in R7.0. In many cases, this doubles the overall capacity of the shelf.

The table below details the maximum number of signals that DMX can transport if all Function Unit (and Growth Slots where applicable) groups are equipped with a particular circuit pack (for example, 80

1000BASE-SX/LX/ZX ports if both slots in all four Function Unit and

Growth groups are equipped with the LNW64 circuit packs (this 0x1 configuration requires VLF Main packs).

Table 1-1 Interface Densities

Interface Type

DS1/E1

DS3/EC-1

TransMUX

OC-3

OC-12

OC-48

OC-192

100BASE-TX

100BASE-LX (optical)

1000BASE-SX/LX/ZX

1000BASE-TX

FICON/ESCON/

Fibre-Channel

192

Capacity/Main Switch

VLF

(0x1 equipped)

Large/

Medium

Fabric

224

192

224

192

Comments

Electrical TDM packs, and other packs that require rear access, do not support true 0x1, hence, overall capacity does not increase with VLF Mains

192 capacity requires the 48 port LNW20

80 unprotected, 40 protected

40 unprotected, 20 protected

40 capacity requires LNW62, only supported on VLF equipped shelves. 40/10 unprotected, 20/5 protected

4 capacity requires LNW59. LNW59 provides 2 OC-192 ports. 4 unprotected with LNW59 only, 2/1 protected

Larger capacities associated with VLF Mains require 0x1 equipage in all slots, only supported in R7.0 and later releases.

1 - 1 0

365-372-300

Issue 8.0, September 2006

Introduction to the DMX Access Multiplexer

System Overview

DMX also provides STS-1 virtual concatenation. STS-1 VCAT increases flexibility when managing Ethernet services. Each

10/100BASE-TX/PL and 1000BASE-SX/LX/ZX Ethernet service can be provisioned to any number of STS-1s (up to 21 STS-1s per VCG).

This is true for all Ethernet packs except LNW71. The LNW71 and

LNW74 can accept 1 or 2 STS-1s or a single STS-3c per port (the

LNW74 also supports VT1.5 VCAT). The LNW73/73C provides STS-

1 and STS-3c virtual concatenation.

Shelf size

The High-Capacity shelf has the following characteristics (includes integral fan unit):

• Width: 17.6 inches

• Height: 19 inches (includes integral fan unit)

• Depth (front to back): 13.75 inches (all optical applications only: without back cover and interface connectors*)

• Weight (with circuit packs): 57 pounds

• Weight (without circuit packs): 38 pounds

Important!

*: 15 inches with interface connectors, 16 inches with connectors and cover.

365-372-300

Issue 8.0, September 2006

1 - 1 1

Introduction to the DMX Access Multiplexer

System Overview

Operations

The DMX is representative of ten years of Lucent’s innovation and experience in network operations, control, and maintenance. Utilizing

Level 1 and Level 2 Target Identifier (TID) Address Resolution

Protocol (TARP), a consistent and standard form of address resolution is in place, enabling the DMX network to be easily monitored and maintained.

DMX also supports standard interworking using the Open Systems

Interconnection (OSI) seven-layer protocol stack or IP over the DCC.

The OSI seven-layer protocol stack refers to the OSI reference model, a logical framework for network operations standardized by the ISO.

This provides for large networks up to 1000 NEs via level 1 area provisioning and level 2 routing.

The DMX is designed for easy installation and operation. Centralized operation is supported by a full set of single-ended operations (SEO), control, and maintenance features. Integrated test capabilities and default provisioning simplifies installation.

Basic maintenance tasks can be performed using faceplate LED displays and controls, while a craft interface terminal (CIT) or a remote

OS gives access to sophisticated maintenance, provisioning, and reporting features.

Built-in maintenance capabilities support both installation and system operation. A DMX can be tested and installed without external test equipment.

1 - 1 2

365-372-300

Issue 8.0, September 2006

System Overview

Feature Release Plan

Overview

This section outlines the major features of Releases 7.0. The feature release plan will be updated for each future release of the system.

A list of important features from past releases can be found directly following the R7.0 Features.

Release 7.0 Features

Listed below are the Release 7.0 features.

•

Dual OC-192 VLF optical interface (LNW59)

Dual OC-192 Very Large Fabric (VLF) Mains (LNW59) support

OC-192 add/drop, UPSR, and BLSR configurations, single- and dual-homing, revertive or non-revertive linear 1+1 protection switching. The LNW59 provides 2 XFP ports capable of supporting 1.3SR1, 1.5IR2, and 1.5LR2 XFPs. It can also function as a headless main, similar to the LNW80 (i.e. with no optics).

For overall capacity, the LNW59 boasts a 20G optical main with a

240G centralized STS switch fabric, 30G centralized VT termination capacity, and 40G VT switch fabric. When DMX is equipped with the LNW59 VLF Main, all switching takes place on the LNW59. The switch fabrics on the low-speed, tributary optical circuit packs are disabled. The LNW59 further upgrades the shelf’s overall capacity by enabling the Function and Growth slots with 10G of bandwidth.

The LNW59 also enables true 0x1 operation amongst the tributary slots by supporting hairpin cross-connections between unprotected

0x1 interfaces located in the same function or growth unit.

LNW59 supports STS-1, STS-3c, STS-12c, and STS-48c signal transport. It can cross-connect VTs in any of 192 STS-1s.

LNW59s may occupy Main slots 1 and 2.

All tributary circuit packs, with the exception of the LNW6 and

LNW7, are supported by the LNW59.

365-372-300

Issue 8.0, September 2006

1 - 1 3

Feature Release Plan

System Overview

•

Quad OC-48 optical interface (LNW62)

Quad OC-48 (LNW62) circuit packs support add/drop, UPSR, and

BLSR configurations, single- and dual-homing, revertive or nonrevertive linear 1+1 protection switching and 0x1 operation. A maximum of 15 BLSRs (between low-speed and high-speed slots) are supported per shelf.

The LNW62 provides 4 PTM (also known as SFP) ports capable of supporting 1.3LR1 and 1.5LR2 PTMs.

As an R7.0 circuit pack, the LNW62 does not have an on-board switch fabric and therefore can only be used with the LNW59 packs in the Main slots. All switching functions are performed on the VLF Main packs (LNW59).

LNW62 supports STS-1, STS-3c, STS-12c, and STS-48c signal transport. The LNW62 boasts a 10G backplane interface capacity and may occupy both Function and Growth slots, providing a total port density of 20 OC-48 ports per shelf if every Function and

Growth slot is equipped with an LNW62.

•

8-port optical/electrical GbE private line interface

(8 optical 1000BASE-SX/LX/ZX or electrical 1000BASE-TX ports)

(LNW64)

The LNW64 provides 8 private line, PTM (also known as SFP)

GbE ports. The ports can be equipped with 8 1000BASE-SX/LX/

ZX PTMs or 8 1000BASE-TX electrical PTMs. LNW64 can also support a mix of 4 electrical and 4 optical PTMs. The LNW64 contains 8 internal VCG ports supporting enhanced private line services such as virtual concatenation (VCAT) and Link Capacity

Adjustment Scheme (LCAS). LNW64 is OSP hardened and can only be used with VLF Mains (LNW59).

LNW64 supports STS-1 and STS-3c cross-connections with or without VCAT, and STS-12c cross-connections without VCAT.

All ports are capable of transmitting at wire speed (1000 Mbps) simultaneously, making full capacity of the pack 168 STS-1s.

With VLF Mains, LNW64 can occupy both slots 1 and 2 of a function/growth unit, making the total capacity of a system fully populated with LNW64s, 80 GbE private line ports.

1 - 1 4

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

•

48-port DS3/EC1/TransMUX/Portless TMUX circuit pack (LNW20)

The LNW20 will be available in R7.0.1 (03/07). It provides 48 ports supporting DS3, EC1, and TMUX functionality on a portby-port basis. Each port can be individually provisioned as DS3 or

EC1 (unchannelized), or as TransMUX (channelized DS3s). With the LNW20, one high-density pack can be used for all DS3, EC1, and/or TransMUX applications.

The LNW20 can also function in portless mode. Portless mode does not utilize physical ports on the pack (those provisioned for portless that is). When operating in portless mode, LNW20 pulls

DS1s from channelized DS3 signals that enter DMX on a SONET

STS-1 interface on another pack (at least one side of the crossconnect is OCn/EC1) and converts them to VT mapped STS-1s.

This VT-mapped STS-1 is cross-connected at the VT level in the

Main packs to any interface that supports the signal structure today (DS1, channelized DS3, EC1, optical). Portless mode can be provisioned on a per-port basis when VLF Mains are used. When non-VLF Mains are used, odd numbered ports can be configured as portless and the corresponding even-numbered port will be unavailable for service.

LNW20 can be 1x1 protected or function in 0x1 unprotected mode. It supports hairpins to other packs in the shelf, and between ports on the same pack. LNW20 can occupy slots A1/A2 through

G1/G2 when the LNW59 VLF Main is used. LNW20 only functions in portless mode in G1/G2. Portless mode is only supported with certain Main packs, when the shelf is equipped with Main packs that don’t support portless mode, it can not occupy G1/G2 (see

Main packs that allow portless LNW20 operation

•

4-port optical SAN interface with Compression

—

FICON/ESCON/

Fibre-Channel (LNW73C)

The LNW73C is a Storage Area Networking (SAN) interface card designed to facilitate SAN distance extensions via the DMX platform using GFP-T (G.7041). The LNW73C differs from the

LNW73 in that it enables compression of SAN traffic. The

LNW73C is able to conserve up to 50% of bandwidth versus uncompressed SAN traffic in typical applications.

Like the LNW73, it utilizes PTM optics to provide the option of

FICON, ESCON, or Fibre-channel interfaces natively on the

DMX shelf. Each pack must be equipped to provide only one type of service (FICON/FC or ESCON) and can be housed in Slot A1,

B1, C1, D1, or G1. The LNW73C can operate at 1 Gbps or 2 Gbps

365-372-300

Issue 8.0, September 2006

1 - 1 5

Feature Release Plan

System Overview

and in either Asynchronous or Synchronous transmission modes.

When operating in async Fibre Channel (FC) mode, 2 ports are available at 2Gbps FC, or 4 ports at 1Gbps FC, or 1 port at 2Gbps

FC and 2 ports of 1Gbps FC. When operating in synchronous FC mode, 1 port is available at 2Gbps FC, or 2 at 1Gbps FC. So, the total number of SA N interfaces on a DMX shelf is 20 when the

LNW73C is operating at 1G FC/FICON or ESCON, and 10 when it is set to 2G FC/FICON.

The R7.0 implementation of SAN compression enables a high throughput of up to four full-line rate FC-2G interfaces in a single pack.

•

Data Compression for SAN traffic

Release 7.0 supports data compression on new LNW73C SAN packs. The LNW73C is able to compress asynchronous Fibre

Channel traffic and conserve up to 50% of bandwidth versus uncompressed asynchronous FC traffic in typical applications.

Compression for asynchronous FC traffic is pre-standard and will be standardized by FC-BB-4. The R7.0 implementation of SAN compression enables a high throughput of up to two full-line rate

FC-2G interfaces in a single pack.

•

True 0x1

With the introduction of the VLF Main pack (LNW59) in R7.0,

DMX allows true 0x1 unprotected circuit packs. That means that any slot can be equipped with any pack (some restrictions apply).

For example, an LNW70 could be used to provide switched

Ethernet services in slot A1, while slot A2 could be equipped with another pack, like an LNW62. Two of the same circuit pack can also populate adjacent slots in the same group, yet certain restrictions apply. For more information on 0x1, including circuit pack/slot equipage restrictions, refer to Chapter 5.

The 0x1 OCn application replaces 0x1Sn functionality when VLF

Mains are used. 0x1Sn will still be supported when the shelf is equipped with non-VLF Mains. 0x1 is only available on the lowspeed/tributary packs, not on the Main (M1/M2) interfaces. When all lines on an OCn pack are set to 0x1, the pack becomes unprotected and the companion slot can be equipped with a different pack.

1 - 1 6

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

•

Line timing from optical tributary packs

DMX can derive timing references from low-speed/tributary optical interfaces beginning in R7.0. Prior to R7.0, line timing references could only be derived from the signals entering the

Main circuit packs. DMX can now derive timing references form any optical line entering Main, Function Unit, or Growth slots.

All optical circuit packs can derive a 6.48MHz timing signal from an incoming optical line.

•

Link Aggregation on LNW70 LAN ports

DMX supports link aggregation on any two LNW70 LAN ports of the same rate (i.e. 100 or 1000 Mbps) operating in switched mode.

The ports must be located on the same pack and DMX supports a maximum of 8 Link Aggregation Groups (LAGs) per function unit/growth group.

Link aggregation can be used to enable bandwidth increases/ decreases and facility protection on LNW70 LAN ports.

Ordinarily, multiple Ethernet links between two bridges form loops (unless a spanning tree blocks all but one) so they can’t be used to increase bandwidth. Link Aggregation causes defined groups of links to be treated as a single logical link, making multiple LAN ports appear as one. In this way, bandwidth can be increased without requiring an upgrade to a higher rate link.

Link aggregation can also remove failed links automatically, thereby providing a means of facility protection. When a link fails, traffic is shifted to the remaining links in that LAG. More links than are needed can be added to the group and each is active until it fails (similar to utilizing LCAS protection for SONET tributaries).

•

QoS on EoS VCGs

Quality of service (QoS) on Ethernet over SONET (EoS) VCGs is designed to enable aggregation of diverse data streams in multiple topologies amongst LNW70 and LNW78 circuit packs. These topologies include packet rings, hub-and-spoke with LNW70 at the hub, and hybrid ring/hub-and-spoke with LNW70/LNW78 at the hub.

365-372-300

Issue 8.0, September 2006

1 - 1 7

Feature Release Plan

System Overview

QoS on EoS VCGs functions by giving EoS VCG ports the same classification options for incoming packets, rate control capabilities for Ethernet services (PIR, CIR), queuing/scheduling capabilities for outgoing, and the same packet transformation functions as on 802.3 LAN ports.

•

MAC address locking

DMX allows MAC locking on the LNW70. MAC locking prevents unauthorized users from gaining access to the network through an Ethernet port, thereby providing a level of security against intrusion attempts. MAC locking restricts access to a bridged Ethernet network by requiring that the source address of traffic entering a locked port be registered with that port. Any number of ports, LANs, VCG, or link aggregation groups (LAGs) can be locked. DMX permits registering of multiple addresses with a single entity.

•

Ethernet facility loopbacks

DMX supports facility loopbacks on the LNW70 and LNW78.

Facility loopbacks are used to test the integrity of the customer to provider network link by looping the signals back at the far end and comparing counts of sent and received frames.

Facility loopbacks are supported on both individual ports and

LAGs. Loopbacks on LAGs are permitted simultaneously for both ports in the group because they are treated as failed members allowing transmission on unlooped members. If a facility loopback is set up on a LAG, alarms are suppressed on both the member ports and the LAG.

•

Locked VT Cross-connections (aka VT locked bandwidth)

In the “locked” mode, DMX does not select the best signal from both rotations of a UPSR. Instead, traffic is added and dropped

(locked) from one rotation of the ring only (provisionable). The main advantage of locked VT cross-connections is the lack of

UPSR switching which results in the ability to reuse timeslots around a UPSR.

The ability to mix locked, unlocked, and pass-through VT1.5s within the same STS-1 was added in R6.0.2.

1 - 1 8

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

•

Linear/Unprotected UPSR

In R7.0, DMX also allows both rotations of a ring to be used simultaneously. Prior to 7.0, if a 1WAY (as opposed to a pathprotected 1WAYPR) cross-connection was established with the source from a UPSR ring, the other side became unusable as the source (1WAY) or destination of a cross-connection (1WAY or

1WAYPR), except for pass-through cross-connections. This feature removes those restrictions.

DMX permits simultaneous 1WAY cross-connections sourced from the 2 associated ring channels in a UPSR application, simultaneous 1WAY cross-connection sourced from a ring channel, and 1WAY or 1WAYPR destined to the associated ring channel.

This feature removes the need for unswitched cross-connections on Ethernet/Data packs which don’t require VCG pairing, yet they will still be supported to ensure backwards compatibility.

•

Electrical 100/1000BASE-TX PTMs on LNW78 and LNW63

DMX supports 100BASE-TX and 1000BASE-TX electrical

PTMs (also known as SFPs) on the LNW78 and LNW63 circuit packs. Certain port/PTM equipage restrictions apply.

•

LNW78 RPR enhancements for R7.0

In addition to the various Ethernet networking capabilities detailed above for R7.0, the LNW78 RPR pack has been upgraded to support the following capabilities:

– VCG ports 17-22 are now available to provide EoS service.

This feature enables EoS port connectivity to RPR ring interfaces via the LNW78 faceplate and/or hairpin crossconnections.

– Standards-based LCAS

– Interconnection of multiple RPR rings on the same shelf or separate shelf using EoS VCGs.

– EOS private line support: adds EoS private line support to an

RPR core ring. Traffic can be managed with QoS support on

EoS VCGs.

– Support of Basic RPR Bridging. In past Releases, DMX only supported enhanced RPR bridging.

Highlighted Features From

Past Releases

Listed below are important features from past releases of the DMX:

New System Controller (LNW2)

365-372-300

Issue 8.0, September 2006

1 - 1 9

Feature Release Plan

System Overview

The LNW2 contains a memory upgrade to support the enhanced feature sets of R6.0 and later releases.

The System Controller (SYSCTL) supports all DMX operations interfaces, including IAO LAN (OSI or TCP/IP), TL1, PC-CIT, office alarms, and miscellaneous discretes. The SYSCTL also supports DCC terminations for each optical line interface.

The SYSCTL circuit pack provides a microprocessor, nonvolatile memory to store the generic program software and provisioning database, and additional memory for system operation.

The new SYSCTL (LNW2) will continue to provide PC-CIT front access to the DMX via the IAO LAN and a serial RS-232 port (it also provides access via the LAN and serial ports located on the back of the

DMX shelf).

High Speed (network side) Service Interfaces

•

OC-192 HS Long-reach optical interface with on-board amplifier

(LNW60)

The LNW60 is an OC-192 long-reach OLIU with tone circuitry and an on-board, integrated amplifier. The LNW60 also includes an integrated, on-board amplifier capable of transmitting signals across spans as great as 127 km.

•

1-port OC-12 High-speed interface (LNW54)

•

OC-192 HS Long-reach optical interface (80 km)

DMX OC-192 Long-reach OLIUs (LNW555) are 1533.47 nm port units supporting OC-192 add/drop and UPSR and BLSR configurations, single- and dual-homing, non-revertive linear 1+1

(1+1 on OC-192 in R4.0) protection switching, and STS-1, STS-

3c, STS-12c, and STS-48c signal transport. The OC-192 OLIU can cross-connect VTs in any 48 STS-1s. LNW555s may occupy

Main slots 1 and 2.

•

OC-192 HS Long-reach optical interface

DMX OC-192 Long-reach OLIUs with tone circuitry (LNW57) are 1533.47 nm port units supporting OC-192 add/drop, UPSR and BLSR configurations, single- and dual-homing, non-revertive linear 1+1 protection switching, and VT1.5, STS-1, STS-3c, STS-

12c, and STS-48c signal transport. LNW57s may occupy Main slots 1 and 2.

•

OC-192 HS DWDM optical interface

1 - 2 0

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

DMX OC-192 DWDM OLIUs (LNW523, LNW527 and

LNW554) are 1550 nm (see Table 10-36 for a list of tunable frequencies) port units supporting OC-192 add/drop and UPSR and BLSR configurations, single- and dual-homing, non-revertive linear 1+1 protection switching, and VT1.5, STS-1, STS-3c, STS-

12c, and STS-48c signal transport. These circuit packs may occupy Main slots 1 and 2.

•

OC-48 long-reach high-speed optical interface

The LNW32 high-speed circuit pack is a long-reach OC-48, 1310 nm optical line interface unit. The LNW32 supports OC-48 add/ drop, BLSR and UPSR configurations, single- and dual-homing, non-revertive linear 1+1 protection switching, and VT1.5, STS-1,

STS-3c, STS-12c, and STS-48c signal transport. The LNW32 contains a 48 STS-1 VT switch fabric and is OSP hardened.

•

OC-48 HS DWDM optical interface (passive optics)

(LNW221-259 and LNW121-159B)

DMX OC-48 High-speed DWDM OLIUs are passive optical port units, available in 32 different wavelengths. By using the DWDM port units and the Passive Optic Units (POUs), you are able to increase fiber capacity by a factor of 16 or 32. The OC-48 HS

DWDM OLIUs may occupy Main slots 1 and 2.

•

OC-12 High-speed optical interface

The OC-12 OLIUs are intermediate- (LNW48) or long- (LNW50) reach 1310 nm optical line interface unit.

•

20 Amp version of the High Capacity Shelf

The 20 Amp version of the high-capacity shelf contains all of the functionality of the standard DMX high-capacity shelf, but it is designed to function with a 20 Amp power supply.

•

Main Switch Pack (No optics, 96 STS-1 VT fabric)

The LNW80 may occupy Main slots 1 and 2 and contains NO interfaces on the faceplate of the pack. The LNW80 high-speed circuit pack is designed to save cost in CO hub applications where there is no need to transmit traffic over network-side interfaces.

LNW80 is best used in a DCS type of application. It can crossconnect signals amongst multiple low-speed tributary interfaces and perform VT mapping into OC-3/12/48 tributaries.

365-372-300

Issue 8.0, September 2006

1 - 2 1

Feature Release Plan

System Overview

Low Speed (tributary side) TDM and Ethernet Service Interfaces

•

OC-48 low-speed optical interface

Capacity of 10 low-speed OC-48 ports when all Function Unit groups (including Growth slots) are equipped with OC-48 OLIU circuit packs (1 bidirectional port per pack). Capacity of 5 OC-48 rings when ports are protected.

•

OC-48 LS DWDM optical interface (passive optics)

DMX OC-48 Low-speed DWDM OLIUs are optical port units, available in 32 different wavelengths. By using the DWDM port units and the Passive Optic Shelves, you are able to increase fiber capacity by a factor of 8, 16, or 32. The OC-48 LS DWDM OLIUs may occupy both the Function and Growth slots.

•

Dual OC-12 low-speed optical interface

Twenty OC-12 capacity when all Function Unit groups (including

Growth slots) are equipped with OC-12 OLIU circuit packs (2 ports per pack). 10 OC-12 capacity when signals are protected.

•

Quad OC-12 low-speed optical interface (48 STS-1 VT fabric)

Provides forty ports at OC-12 when all Function Unit groups

(including Growth slots) are equipped with LNW49 OC-12 OLIU circuit packs (4 ports per pack). These packs provide 20 OC-12 interfaces when signals are protected.

•

8-port OC-3 low-speed optical interface (48 STS-1 VT fabric)

(LNW45)

Provides eight OC-3 ports per pack, equaling a total interface density of 80 OC-3 ports when all Function Unit groups

(including Growth slots) are equipped with OC-3 circuit packs.

These packs provide forty ports of OC-3 capacity when signals are protected. The LNW45 utilizes PTM optics, allowing you to equip additional ports as necessary. It also contains a 48 STS-1s VT switch fabric that allows usage of all ports at full capacity for add/ drop, hairpinning, and/or VT ring closure applications.

•

Quad OC-3 low-speed optical interface (12 STS-1 VT fabric)

Provides forty ports at OC-3 when all Function Unit groups

(including Growth slots) are equipped with OC-3 OLIU circuit packs (4 ports per pack). These packs provide 20 OC-3 capacity when signals are protected.

•

56 Port E1 service support

1 - 2 2

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

DMX supports 56 E1 signals on the LNW8 circuit pack. E1 signals are SDH/PDH signals at 2.048 Mbps. DMX supports performance monitoring on E1 signals.

•

48 port DS3/EC1 interface with DS3 loopbacks (LNW19B)

192 DS3/EC1 drop capacity when four Function Unit groups are equipped with LNW19B circuit packs (48 ports per pack, 1x1 hardware protected). The difference between the LNW19B and the previously released LNW19, is that the LNW19B provides the capability for DS3 terminal loopbacks that aid in testing, troubleshooting, and installation procedures.

•

56 port DS1 interface (LNW8)

224 DS1 drop capacity when four Function Unit groups are equipped with LNW8 circuit packs (56 ports per pack, 1x1 hardware protected).

•

48 port DS3/EC1 interface (LNW19)

192 DS3/EC1 drop capacity when four Function Unit groups are equipped with LNW19 circuit packs (48 ports per pack, 1x1 hardware protected).

•

Port-provisionable 12DS3/EC1 circuit pack

In early releases the 12DS3/EC1 circuit pack was switch selectable for DS3 or EC-1 service on a per-pack basis. DS3 or

EC-1 service can be provisioned on a per-port basis.

•

12-port DS1/DS3 TransMux circuit pack

DMX supports a 12-port Trans/MUX card that can collect various

DS1 signals from around a ring and combine them into a channelized DS3 signal.

•

6-port optical RPR Ethernet interface (two 1000BASE-X and four 100BASE-X ports) with PTM optics (LNW78)

The LNW78 provides two 1000BASE-X ports for GbE LAN applications and four 100BASE-X ports for fast Ethernet LAN applications at 100 Mbps. The first two ports (1-2) are for the GbE traffic. Ports 5-8 are for FE traffic, and ports 3 and 4 are not available until a later release. The LNW78 supports similar port, switching, and traffic management capabilities as the LNW70.

The LNW78 also provides standards compliant RPR switching per IEEE 802.17. LNW78 will support one RPR instance in R7.0 and two in the future. The LNW78 provides two internal Virtual

365-372-300

Issue 8.0, September 2006

1 - 2 3

Feature Release Plan

System Overview

Concatenation Group (VCG) WAN ports (will support 4 in the future) with a total capacity of 2.5 Gbps capacity for Ethernet RPR traffic (24 STS-1s in each direction).

DMX supports a total add/drop capacity of 10 RPR GbE ports and

20 RPR FE ports if all slots are equipped with LNW78 circuit packs.

•

GbE (1000 Mbps) Private Line circuit pack (LNW63)

The LNW63 enables support of GbE private line on DMX. The

LNW63 provides 4 PTM ports that can be equipped with longreach (1000 BASE-LX) 1310 nm and/or short-reach (1000 BASE-

SX) 850 nm single mode PTMs.

•

8-port optical Ethernet interface (four 1000BASE-X and four 100BASE-LX ports) (LNW70)

The LNW70 supports all R4.0 and R5.0 Ethernet enhancements

(see descriptions below), provides 32 internal Virtual

Concatenation Group (VCG) WAN ports with a total capacity of

2.5 Gbps with SONET protection and 5 Gbps without SONET protection. The LNW70 has a total Ethernet switching capacity of

9 gigabits per second (Gbps).

•

4-port optical SAN interface

—

FICON/ESCON/Fibre-Channel

(LNW73)

The LNW73 is a Storage Area Networking (SAN) interface card designed to facilitate SAN distance extensions via the DMX platform using GFP-T (G.7041). It utilizes PTM optics to provide the option of FICON, ESCON, or Fibre-channel interfaces natively on the DMX shelf.

•

24 port 100BASE-TX (10/100Mbps) Private Line Ethernet interface

(LNW71)

Enhanced 10/100 Mbps Ethernet interface designed to enable Fast

Ethernet Private Line services. 96 10/100 Mbps drop capacity when four Function Unit groups are equipped with 10/100 Mbps circuit packs (24 ports per pack).

•

24-port optical/electrical Fast Ethernet private line interface

(8 optical 100BASE-LX and 16 electrical 100BASE-TX ports) with

R5.0 Ethernet enhancements (LNW74)

The LNW74 provides 8 100BASE-LX optical ports with front

(faceplate) access and 16 electrical 100BASE-TX ports with rear access at 10/100 Mbps for enhanced fast Ethernet private line applications. The LNW74 contains 24 internal 100 Mbps WAN

1 - 2 4

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

ports supporting enhanced private line services such as low-order virtual concatenation (VT1.5) and Link Capacity Adjustment

Scheme (LCAS). LNW74 is OSP hardened.

•

100BASE-TX (10/100T) Ethernet interface

Ninety-six 100BASE-TX drop capacity when four Function Unit groups are equipped with 10/100T circuit packs (24 ports per pack).

•

1000BASE-SX/LX (1G SX/LX) optical Ethernet interfaces

Ten 1000BASE-SX/LX drop capacity when all Function Unit groups (including Growth slots) are equipped with 1G SX and/or

1G LX circuit packs (2 ports per pack).

•

Electrical Fast Ethernet/GbE PTM for LNW70

•

Pluggable Transmission Module (PTM) optics

The Pluggable Transmission Module (PTM) optics, also known as

SFP optics, are used on the LNW37, LNW49. LNW45, LNW63,

LNW70, LNW73, LNW74, and LNW78 packs. PTM optics are

“pluggable” optics. PTM optics also allow one pack to support various span lengths (short/intermediate, and long-reach).

•

Fiber Management Brackets

In the interest of helping customers organize the physical networking in their offices, DMX provides a fiber management bracket that mounts to the apparatus blanks used in the unoccupied slots of the shelf. This bracket has 8 hooks where fibers can be set until the pack to which they will be attached are installed.

•

Detectable Blank Circuit Packs

DMX supports detectable blank circuit packs: LNW98 in unequipped Function and Growth slots, LNW97 in an unequipped

M2.

•

In-service Electric Continuity Test Tool

The In-service Electrical Continuity Test Tool (LNW93) is very similar to the LNW94 test tool except that it has no backplane connectors for DS1 ports #1-28 or for DS3 ports #1-24. When the

LNW93 is plugged in, it makes no contact with the wires on the backplane for those lower ports. Since there is no physical connection, the LNW93 does not interfere with the service of the pack in the other slot of the function unit.

•

Electric Continuity Test Tool

365-372-300

Issue 8.0, September 2006

1 - 2 5

Feature Release Plan

System Overview

The Electrical Continuity Test Tool (LNW94) can be placed in any Function slot on the DMX shelf. It is used to test the cables which will be connected to DS1, DS3, or Ethernet electrical interfaces. LNW94 tests the integrity of electrical cables to both identify where trouble exists and which cables or DSX panels are faulty prior to installation and turn up.

•

Optical Amplifiers

External amplifiers, enabling transmission for OC-48/192 spans of up to 140 km.

In-service upgrades

•

In-service upgrade from LNW1 to LNW2

DMX supports an in-service upgrade from the LNW1 to LNW2

SYSCTL on shelves equipped with software Release 5.x. Use of the LNW2 SYSCTL requires that the shelf be equipped with R6.0 or later software.

•

OC-48 to OC-192 HS BLSR and UPSR in-service upgrade

DMX supports in-service upgrades, from OC-48 to OC-192

UPSRs and from OC-48 to OC-192 BLSRs (in-service OC-48 to

OC-192 upgrades are currently supported only when using OC-

192 packs released prior to R7.0.

•

OC-12 to OC-48 HS UPSR in-service upgrade

DMX supports in-service upgrades, from OC-12 to OC-48 (small fabric packs) UPSRs.

•

In-service upgrade from low-density to high-density electrical interface circuit packs

DMX allows an in-service upgrade from either the LNW16 to the

LNW19/19B or the LNW6 and LNW7 to LNW8.

•

In-service upgrade from low-density (LNW16) to high-density

(LNW19/19B) electrical interface circuit packs

DMX allows an in-service upgrade from the LNW16 (12 DS3 ports) to the LNW19 or LNW19B (48 DS3/EC-1 ports) circuit packs.

1 - 2 6

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

Network Configurations/Capabilities

•

OC-192/48/12 HS linear optical extension

The DMX supports point-to-point, 1+1 protected linear optical extension from the circuit packs in the MAIN slots.

•

OC-192/48/12 HS unidirectional path switched ring (UPSR)

•

OC-48/192 HS Bidirectional line switched ring (BLSR)

with VT support

The DMX supports OC-48/192 BLSR at VT1.5, STS-1, STS-3c,

STS-12c, and STS-48c (OC-48 BLSRs do not support STS-48c) level. DMX OC-48/192 BLSRs also support VT grooming and squelching.

•

Low-speed OC-48 UPSR

•

1+1 protected low-speed linear optical extensions (OC-3/12/48)

•

Bidirectional Optimized 1+1 Linear Protection Switching per ITU-T

G.841 Annex B

DMX supports this feature on all OC-n interfaces. Bidirectional optimized 1+1 is designed to enable interoperability between

DMX and SDH equipment. It is a separate switching scheme from standard 1+1 bidirectional and does not work with standard 1+1.

•

Bidirectional 1+1 Protection Switching

DMX supports revertive and non-revertive bidirectional 1+1 protection switching in all OC-n interfaces in addition to linear

1+1 protection switching.

•

Support of Resilient Packet Ring (RPR) per IEEE 802.17

•

GbE Private Line

Allows DMX to provide dedicated bandwidth (up to 1000Mbps) for individual customers.

•

0x1Sn unprotected interfaces

DMX supports 0x1 provisioning of an optical port in 1 slot of a low-speed (function unit) pair. 0x1Sn is not supported on HS interfaces. The companion port to the one provisioned for 0x1Sn is inactive. 0x1Sn is provisionable on per port/port pair basis.

•

Locked DS1/DS3 Cross-connections

In the “locked” mode, DMX does not select the best signal from both rotations of a UPSR. Instead, traffic is added and dropped

(locked) from one rotation of the ring only (provisionable). The

365-372-300

Issue 8.0, September 2006

1 - 2 7

Feature Release Plan

System Overview

main advantage of locked DS1/DS3 cross-connections is the lack of UPSR switching which results in the ability to reuse timeslots around a UPSR.

•

DS1s 1x1 protected

DS1s are 1x1 equipment protected at the pack level. The LNW8

56DS1 pack provides support for up to 224 DS1s.

•

DS3s 1x1 protected

DS3s are 1x1 equipment protected at the pack level. The LNW19/

LNW19B 48 DS3 packs provides support for up to 192 DS3s

•

VT1.5 granularity

Fully-flexible VT1.5 granularity across up to 48 STS-1s. The number of VTs supported varies on a per-pack basis.

•

VT and Ethernet Hairpinning

•

Ethernet Enhancements for R4.0

•

Ethernet Enhancements for R5.0

•

Utilization of Simple Network Management Protocol (SNMP)

DMX allows SNMP to be used for monitoring alarms and traps relative to the Ethernet circuit packs.

•

Utilization of Simple Network Management Protocol (SNMP) for

TDM interfaces

DMX allows SNMP to be used monitoring alarms, traps, and performance monitoring parameters relative to the DS1/E1 and

DS3/EC-1 circuit packs.

•

R5.1 Ethernet Enhancements (supported by LNW70)

– Committed and Peak rate controls (CIR and PIR)

– 4 classes of services

– 4 1000BASE-X and 4 100BASE-LX port density with PTM optics (simultaneously)

– Larger MAC tables

– 32 VCGs (star configuration) per G.707

– 16 virtual switches with independent VLAN space per virtual switch

• DMX

Ethernet interworking with DDM-2000

The DDM-2000 circuit pack can interwork with the LNW71 and

LNW74 circuit packs.

•

VLAN Transparency

1 - 2 8

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

•

1 Mbps Ethernet rate shaping

•

IP DiffSrv packet priority for VoIP applications

R6.0 allows DMX to use an IP DiffSrv Code Point (DSCP) in the header of IP packets to enable differentiated levels of services for individual customers and their data streams.

•

Performance monitoring (PM) on VLANs

DMX can provide PM on UPSR VT1.5, STS-n pass-throughs, and

BLSR STS-n pass-throughs.

•

Support of 4093 Virtual Local Area Networks (VLANs) and stacked

VLANs per Ethernet circuit pack

•

Pipe-mode (adaptive rate) cross-connections

Pipe mode is a fault and PM feature whereby fault and PM are reported independently for each constituent signal within a crossconnection rather than simply at the xc rate.

•

Increased number of OSI associations

The maximum number of OSI associations per TCP connection has been increased from 64 to 300. The maximum number of OSI associations for TL1 per GNE has been increased from 200 to 300.

•

250 NEs in a Level 1 routing area

The maximum number of NEs per OSI Level 1 routing area has been increased from 50 to 250.

•

Alarm Severity Assignment Profiles (ASAPs)

•

Revertive Unidirectional and Bidirectional 1+1

DMX now supports revertive and non-revertive unidirectional and bidirectional 1+1.

•

VT grooming on Low-speed Interfaces (LNW45 and 49)

•

WaveStar BandWidth Manager, FT-2000, LambdaUnite, and 2.5G/

10G interworking over OC-48 BLSRs

•

Single- and dual-homed 0x1 ring tributaries

: OC-3, OC-12, OC-48

•

BLSR auto ring discovery for BLSR interworking

•

FTP/FTAM Gateway

Also referred to as FTTD (File Transfer Translation Device), the

FTTD allows DMX to function as a Gateway Network Element

(GNE) that can facilitate the download of files located at FTP servers to remote NEs connected to the DMX.

•

UPSR and BLSR bridge and roll cross-connections

365-372-300

Issue 8.0, September 2006

1 - 2 9

Feature Release Plan

System Overview

Allows DMX to move cross-connections within or between an

OC-n with minimal hits to traffic.

•

OC-12/48/192 Facility Loopbacks

•

OC-3 Facility Loopbacks

With the release of LNW37, DMX supports OC-3 facility loopbacks in addition to the OC-12/48/192 facility loopbacks supported in previous releases.

•

UPSR Dual Ring Interworking (DRI)

ANSI/Bellcore compliant DRI (through drop and continue method) with interconnected rings (OC-3/12/48/192 interfaces)

•

Non-preemptible Unprotected Traffic (NUT)

DMX allows the manual provisioning of NUT on BLSRs. NUT allows the DMX to host packet rings over BLSRs.

•

SS bits per pack

By default DMX transmits 00 in the outgoing SS pointer bits for compatibility with SONET interfaces. DMX provides the ability to set the outgoing SS bits to 10 on a LS optical pack basis for compatibility with older SDH equipment. DMX is provisionable to support SS bits on a per pack basis. This prevents LOP defects and allows SONET/SDH interworking.

•

IP communications over DCC channel

Synchronization

•

Embedded Stratum 3 Timing Generator

The OC-12/48/192 high-speed circuit packs contain an embedded

Stratum 3 timing generator. This timing generator is used when the DMX is configured in a free running mode.

•

DS1 Timing Output

DMX can generate a DS1 timing output to time other externallytimed systems. The DS1 output is derived from a line reference.

•

S1 Byte Synchronization Messaging

DMX uses the S1 byte of the SONET overhead to pass timing status information to different nodes in an access transport network.

•

Network Time Protocol (NTP)

NTP assures accurate time keeping with reference to radio and atomic clocks located on the Internet.

1 - 3 0

365-372-300

Issue 8.0, September 2006

Feature Release Plan

System Overview

Operations

•

Telcordia support of LCAS, VCAT, and diverse routing

•

Navis

™

Optical Management System (OMS) R3.1 support

Navis™ OMS R3.1 can be used to manage operations on DMX

R5.0.

•

TIRKS (R20.0)/NMA (R14.0)/TRANSPORT (R3.2)

DMX is supported by Telcordia OSs TIRKS, NMA, and

TRANSPORT.

•

Target ID Address Resolution Protocol (TARP)

DMX is compatible with any other-vendor NEs that support

TARP, OSI, IAO LAN, and TL1/X.25 as specified in Telcordia

Technologies GR-253.

•

Transmission Control Protocol/Internet Protocol (TCP/IP)

Provides access to Navis ™ Optical EMS or PC-CIT over TCP/IP

LAN to a DMX and subtending DMX, DDM-2000, and other NEs that support DMX operations interworking.

TCP/IP also enable software downloads via FTP through the LAN

CIT and RS232 CIT ports located at the front of the high-speed

(network side) circuit packs in the MAIN slots of the DMX shelf.

•

Level 1 Area Provisioning

•

Level 2 Routing

•

OSI seven-layer protocol stack

Provides interworking using the standard Open Systems

Interconnection (OSI) seven-layer protocol stack over the data communications channel (DCC).

•

WaveStar CIT

The CIT manages the DMX system through the LAN/Serial ports, providing TL1 messaging, software download, and full operations, maintenance, and provisioning functions through a

Graphic User Interface (GUI).

•

Product family 2000 and WaveStar product family Operations interworking (OI)

OI compatibility with Product Family 2000 (DDM-2000 and FT-

2000), and WaveStar Product Family.

•

Multivendor Operations interworking (OI)

DMX supports interoperability with many other vendors. Ask your account representative for more information.

365-372-300

Issue 8.0, September 2006

1 - 3 1

Feature Release Plan

System Overview

•

Utilization of Simple Network Management Protocol (SNMP)

DMX allows SNMP to be used in monitoring alarms and traps relative to the Ethernet circuit packs.

•

Test Access

1 channel as it passes through the system and routes it to an external testing device. The more intrusive mode splits the VT1.5/

STS-1 from the incoming signal and sends it to an external testing device. Test access facilitates DMX functioning in a DCS application.

•

Proxy Address Resolution Protocol (ARP)

•

Office Alarm support

•

IAO-LAN support (front and rear)

•

In-service node additions

•

Remote alarm support

•

EIA-RS-232 PC-CIT (serial port front and rear access)

•

Local and Remote Software Download capability

•

AITS support

•

Ring Circuit Audits

•

Auto-generated Squelch Map

Environmental and Packaging

•

EMC, UL 605950, NEBS Level 3, CSA

1 - 3 2

365-372-300

Issue 8.0, September 2006

2 Features

Overview

Purpose

This chapter briefly highlights the features of the DMX Access

Multiplexer. These features are more thoroughly described in Chapter

3, “Network Topologies,” Chapter 4, “Product Description,” Chapter 5,

“System Planning and Engineering”, and Chapter 6, “Operations,

Administration, Maintenance, and Provisioning,” as applicable.

Contents

The following topics are included in this chapter:

Hardware Features

In-service Upgrades

Topologies

Networking Capabilities

Cross-connection Types

Operations Features

Synchronization

365-372-300

Issue 8.0, September 2006

2 - 1

Features

Hardware Features

Overview

This section briefly describes the major hardware related features supported through Release 7.0 of the Metropolis

DMX Access

Multiplexer.

Below is a list of the sections included in Hardware Features:

• DMX High Capacity Shelf

• Network interface circuit packs (those housed in the MAIN slots of the DMX shelf)

• Optical, tributary interface circuit packs

• Electrical, tributary interface circuit packs

• Ethernet circuit packs

• Other hardware features

Important!

For more detailed information on the capabilities of these circuit packs, refer to the sections entitled “Circuit Packs” in

Chapter 4. For technical specifications refer to Chapter 10.

DMX High Capacity Shelf

The high capacity shelf is not software dependent. This design incorporates additional DS1/E1 and DS3/EC-1 interfaces that enable the DMX to support 224 DS1s/E1s or 192 DS3s/EC-1s. In order to support this amount of traffic, the DMX high capacity shelf must be equipped with high density DS1 and DS3 circuit packs.

This shelf is available in both 20 Amp and 30 Amp versions. The 20

Amp version has no restrictions as to circuit pack slot equipage through

R7.0. The 30 Amp version of the shelf is intended to provide “future proofing”.

2 - 2

365-372-300

Issue 8.0, September 2006

Hardware Features

System Controller-

SYSCTL (No Network

Interfaces)

Features

The DMX supports two SYSCTLs:

• LNW1— The SYSCTL provides communication with other circuit packs on the DMX shelf. The SYSCTL supports all DMX operations interfaces, including IAO LAN (OSI or TCP/IP), TL1,

PC-CIT, office alarms, and miscellaneous discretes. The SYSCTL also supports DCC terminations for each optical line interface.

The LNW1 will work with any software release prior to R6.0, but the LNW2 must be used with R6.0 and later Releases.

• LNW2 — This version of the SYSCTL contains a memory upgrade to support the enhanced feature sets of R6.0 and upcoming releases.

Network Interface Circuit

Packs

This section briefly details the network interface circuit packs available through Release 7.0 of the DMX. “Network Interface” is used to refer to the high-speed circuit packs, housed in the MAIN slots of the DMX shelf, and used to provide the connection to the core-side of the network.

Main Switch Circuit Pack (No Network Interfaces)

The DMX supports the following main switch cards:

• LNW80— headless pack to facilitate switching amongst multiple tributary interfaces, resides in Main slots, provides no high speed or network side optics, VT mapping in 96 STS-1s, OSP hardened

VLF Main Circuit Pack (LNW59) (R7.0)

In R7.0, DMX introduces the LNW59 OC-192 Very Large Fabric

(VLF) Main circuit pack. LNW59 drastically increases the overall switch fabric capacity of DMX. It also provides two ports that can host

PTMs (also known as XFPs). LNW59 can support 1.3SR1, 1.5IR2, and

1.5LR2 pluggable optics. It can also function in headless mode, providing switching and synchronization functionality without being equipped with optics.

For overall capacity, the LNW59 boasts a 20G optical main with a

240G centralized STS switch fabric, 30G centralized VT termination capacity, and 40G VT switch fabric. When DMX is equipped with the

LNW59 VLF Main, all switching takes place on the LNW59. The switch fabrics on the low-speed, tributary optical circuit packs are disabled. The LNW59 further upgrades the shelf’s overall capacity by enabling the Function and Growth slots to house circuit packs with up to 10G bandwidth.

365-372-300

Issue 8.0, September 2006

2 - 3

Hardware Features

Features

The LNW59 also enables true 0x1 operation amongst the tributary slots by supporting hairpin cross-connections between unprotected 0x1 interfaces located in the same function or growth unit.

All tributary circuit packs, with the exception of the LNW6 and LNW7 are supported by the LNW59.

OC-192 Network Interface Circuit Packs

The DMX supports the following OC-192 network interface cards:

• LNW56— (1550nm, intermediate-reach, VT mapping across 48

STS-1s)

• LNW57— (1533.47 nm, long-reach, VT mapping across 48

STS-1s, 80 km reach, with SBS tone circuitry)

• LNW58— (1310nm, short-reach, VT mapping across 48 STS-1s)

• LNW59— (4 ports, 1.3SR1, 1.5IR2, and 1.5LR2 PTM optics,

240G centralized STS switch fabric, 30G centralized VT termination capacity, and 40G VT switch fabric)

• LNW60— (1533.47 nm, long-reach, VT mapping across 48

STS-1s, with SBS tone circuitry, and on-board optical amplifier)

• LNW523, LNW527 and LNW554— (DWDM, full VT access,

4-frequency tunable laser. The LNW523 is being DA’d and will no longer be available as of 6/30/07.)

• LNW555— (1550nm, long-reach, VT mapping across 48 STS-1s,

80 km reach)

OC-48 Network Interface Circuit Packs

The DMX supports the following OC-48 network interface cards:

• LNW26B— (1310nm, long-reach, VT mapping across 12

STS-1s)

• LNW27— (1310nm, long-reach, VT mapping across 48 STS-1s)

• LNW28— (1310nm, long-reach, VT mapping across 12 STS-1s,

OSP hardened). The LNW28 will no longer be available as of

5/28/06.

• LNW29— (1550nm, long-reach, VT mapping across 48 STS-1s)

• LNW32— (1310nm, long-reach, VT mapping across 48 STS-1s,

OSP hardened)

• LNW76— (1310nm, short-reach, VT mapping across 48 STS-1s)

• LNW77— (1310nm, intermediate-reach, VT mapping across 12

STS-1s)

2 - 4

365-372-300

Issue 8.0, September 2006

Hardware Features

Features

• LNW121B-159B— (DWDM, VT mapping across 12 STS-1s, the

LNW121B, 123B, 131B, 135B, 137B, 143B, 145B, 147B, 149B,

157B, and 159B packs are no longer available. All other 100 series packs are still be available.

• LNW221-259— (high-speed, DWDM, 1550nm, long-reach, VT mapping across 48 STS-1s, the LNW221, 243, and 257 packs are no longer available. All other 200 series packs will still be available.)

OC-12 Network Interface Circuit Packs

The DMX supports the following OC-12 network interface card:

• LNW48— (1310nm, intermediate-reach, VT mapping across 12

STS-1s, OSP Hardened)

• LNW50— (1310nm, long-reach, VT mapping across 12 STS-1s,

OSP Hardened)

• LNW54— (1550nm, long-reach, VT mapping across 12 STS-1s,

OSP Hardened)

Optical, Tributary Interface

Circuit Packs

DMX supports the following optical, tributary interface circuit packs:

• OC-3— LNW36 (1310nm, long-reach, 12 STS-1 VT fabric

OSP hardened, 4 ports. The LNW36 is being DA’d and will no longer be available as of 12/31/07.)

• OC-3— LNW45 (PTM optics, OSP hardened, 8 ports,

VT mapping across 48 STS-1s)

• OC-3— LNW37 (PTM optics, OSP hardened, 4 ports,

VT mapping across 12 STS-1s)

• OC-12— LNW46 (1310nm, long-reach, 12 STS-1 VT fabric, OSP hardened, 2 ports. The LNW46 is being DA’d and will no longer be available as of 12/31/07.)

• OC-12— LNW49 (PTM optics, 48 STS-1 VT fabric, 4 ports,

OSP)

• OC-48— LNW31 (1310nm, intermediate-reach, 1 port,

VT mapping across 12 STS-1s)

• OC-48— LNW62 (R7.0) (1.3LR1 and 1.5LR2 PTM optics, 4 ports, requires VLF Main- LNW59)

• OC-48— LNW421-459 (low-speed, DWDM, 1550nm, long-reach, VT mapping across 12 STS-1s, the LNW421, 423,

431, 433, 435, 437, 443, 445, 457 packs are no longer available.

All other 400 series packs are still be available.)

365-372-300

Issue 8.0, September 2006

2 - 5

Hardware Features

Features

Electrical, Tributary

Interface Circuit Packs

DMX supports the following electrical, tributary interface circuit packs:

• 28DS1— LNW6 (28 ports, OSP hardened, not supported on shelves equipped with LNW59 VLF Mains)

• 28DS1PM— LNW7 (28 ports, enables PM functionality on DS1 interfaces, OSP hardened, not supported on shelves equipped with

LNW59 VLF Mains)

• 56DS1/E1 — LNW8 (56 ports, enables PM functionality on DS1 and E1 interfaces— E1 functionality provisionable on a per pack basis, OSP hardened)

• 12DS3/EC1— LNW16 (12 ports, DS3 or EC-1 service is provisionable on a per-port basis)

• 48DS3/EC1— LNW19 (48 ports, DS3 or EC-1 service is provisionable on a per-port basis, OSP hardened)

• 48DS3/EC1— LNW19B (48 ports, DS3 or EC-1 service is provisionable on a per-port basis, supports DS3 loopbacks, OSP hardened)

• DS1/DS3 TransMUX — LNW18 (12-port, capable of collecting various DS1 signals from around a ring and combining them into channelized DS3 signals, OSP hardened)

• DS1/DS3 TransMUX/Portless — LNW20 (R7.0) (48-port, DS3,

EC1, and TMUX functionality on a port-by-port basis, supports channelized or unchannelized DS-3s, also offers a portless mode wherein the pack pulls DS1s from channelized DS3 signals that enter DMX on a SONET STS-1 interface (on another pack) and then converts them to a VT mapped STS-1, OSP hardened)

Ethernet/ Interface Circuit

Packs

DMX supports the following Ethernet interface circuit packs:

• Fast Ethernet— LNW66 (24 ports, 10/100 Mbps)

• Fast Ethernet— LNW71 (24 ports, 10/100 Mbps, enhancements to enable Ethernet private line services, The LNW71 is being DA’d and will no longer be available as of 3/1/08.)

• 24-port Optical/Electrical Fast Ethernet Private Line— LNW74 (8 optical 100BASE-FX with front, faceplate access and 16 electrical

100BASE-TX ports with rear access, supports R5.0 and 5.1

Ethernet enhancements and PTM optics)

2 - 6

365-372-300

Issue 8.0, September 2006

Hardware Features

Features

• 8-port Optical/Electrical Gigabit Ethernet Private Line— (R7.0)

LNW64 (8 optical 1000BASE-SX/LX/ZX or 8 electrical

1000BASE-TX PTMs, also supports a mix of 4 optical and 4 electrical PTMs, OSP hardened, 168 STS-1 capacity, requires

VLF Mains- LNW59)

• Gigabit Ethernet (GbE)— LNW67 (2 ports, 1 gigabit each, short reach. The LNW67 is being DA’d and will no longer be available as of 3/1/08.)

• GbE— LNW68 (2 ports, 1 gigabit each, long reach, The LNW68 is being DA’d and will no longer be available as of 3/1/08.)

• Gigabit Ethernet (GbE)/Fast Ethernet (10/100 Mbps)— LNW70

(four 1000BASE-X or 10/100/1000BASE-T and four

100BASE-FX ports) with R5.0 and 5.1 Ethernet enhancements and PTM optics

• FC-DATA— LNW73 (4 ports, support of FICON, ESCON, or

Fibre-Channel interfaces using PTM optics) Pack must be equipped with only one type of PTM: either FICON/FC or

ESCON.

• FC-DATA (R7.0)— LNW73C (4 ports, support of FICON,

ESCON, or Fibre-Channel interfaces with compression) Identical to the LNW73, except that is supports compression of SAN traffic, resulting in an increase of bandwidth efficiency to the order of 100%.

• 4-port Optical Gigabit Ethernet Private Line— LNW63 (4 optical

1000BASE-X ports), supports R5.0 and 5.1 Ethernet enhancements and PTM optics. Can be equipped with long-reach

(1000 BASE-LX) 1310 nm and/or short-reach (1000 BASE-SX)

850 nm single mode PTMs.

• RPR Pack— LNW78 (two 1000BASE-X and four 100BASE-FX ports) supports GbE and FE interfaces via PTM optics. Similar switching and traffic management capabilities to the LNW70, added support of standards compliant RPR (IEEE802.17)

365-372-300

Issue 8.0, September 2006

2 - 7

Hardware Features

Features

Other Hardware Features

DMX also supports the following hardware:

External Optical Amplifiers

For OC-48/192 spans of up to 140km, Lucent Technologies offers external optical amplifiers. The external optical amplifier is a stand-alone shelf and can be used with both OC-48 and OC-192 optics.

External optical amplifiers consist of one booster and one pre-amplifier part. The booster part is connected via a Dispersion Compensation

Module (DCM) to the transmit interface of the respective OC-192 or

OC-48 port unit. The pre-amplifier part is connected by means of a

DCM to the receive interface of the associated port unit.

Passive Optics Units (POUs)

The Lucent Passive Optics Units (POUs) are a lower-cost solution to using DWDM for transmitting large amounts of traffic on one fiber.

This module fits into a bay frame, but reduces the number of DMX shelves in a bay to three. The box does not require any electrical powering.

POU shelves are available to support the following applications:

• Optical add-drop module (OADM): 1, 2, or 4 wavelengths

• Optical add-drop module (OADM): one 1310 nm port and four

1550 nm ports

• 16 unidirectional/bidirectional wavelengths (2 versions):

MUX/DMUX

• 32 wavelengths; 16 unidirectional/bidirectional wavelengths with a wavelength interleaver used to add another 16 wavelengths:

MUXINT/DMUXINT

Pluggable Transmission Modules (PTMs)

PTMs, also known as SFPs and XFPs (LNW59 only), are used on the

LNW37/45/49/59/62/63/64/70/73/73c/74/78 packs. PTM optics are

“pluggable” optics. This means that the circuit pack does not come equipped with optics. The customer orders the number and type of optics required at the time of installation. Additional optics can be ordered as new services are required. Thus DMX interface density is made more scalable to meet the unique needs of each customer.

The PTM optics also allow for some versatility in the span lengths and rates that can be covered by the same pack.

2 - 8

365-372-300

Issue 8.0, September 2006

Hardware Features

Features

Electrical Fast Ethernet/GbE PTM

The LNW64/70/78 now supports a dual function electrical Pluggable

Transmission Module (PTM) that is provisionable for 100 or 1000

Mbps (electrical FE or GbE) traffic. It conforms to the IEEE802.3 standards for 100BASE-T and 1000BASE-T in its respective settings

(IEEE802.3z and IEE802.3ab). Connectivity is provided for an RJ-45

Cat 5 cable and the PTM has a maximum span length of 100 meters.

This provisionable PTM can occupy ports 1-4 on the LNW64 and

LNW70. Ports 5 through 8 on both packs are always reserved for optical Fast Ethernet PTMs. This PTM can occupy ports 5-8 on the

LNW78. Ports 1 and 2 are reserved for optical GbE and port 3 and 4 are not usable at this time.

High-capacity 20 Amp Shelf

The 20 Amp version of the high-capacity shelf contains all of the functionality of the 30 Amp DMX high-capacity shelf, but it is designed to function with a 20 Amp power supply. This can save customers considerable investment in power cables. There are no restrictions through R6.0 resulting from the lower amperage given the circuit packs that are currently available through R6.0.

Important!

With the LNW59 VLF Main pack, available in

R7.0, overload and overheating in the 20A Standard Shelf is a possibility given certain combinations of circuit packs in the tributary slots. The LNW59 is not necessarily precluded from use in the 20 Amp shelf, but guidelines provided later in this document must be followed to ensure proper functioning of the 20

Amp shelf when it is equipped with the LNW59.

The power density of certain system configurations may also preclude the use of more than two DMX shelves per frame in

NEBS environments. See the section entitled

Power Specifications

for more information.

365-372-300

Issue 8.0, September 2006

2 - 9

Hardware Features

Features

Cable Management Bracket

The bracket is designed to facilitate the organization and storage of prewired fibers that are expected to carry service to the shelf in the future. These brackets attach to the apparatus blanks via PEM nuts on the faceplate. PEM Nuts or PEM Fasteners are mounted flush on the faceplate. They provide a fixed receptacle to which the bracket can be screwed in.

This feature is available on both the standard and detectable apparatus blanks and also allows visibility via the CIT.

Electrical Continuity Test Tool (LNW94)

DMX supports a circuit pack designed to aid technicians in the installation and maintenance of Electrical interfaces and cables. The

Electrical Continuity Test Tool (LNW94) can be placed in any

Function Unit slot (A, B, C, and D) on the DMX shelf. It is used to test the cables which will be connected to DS1, DS3, or Ethernet electrical interfaces. LNW94 tests the integrity of electrical cables to both identify where trouble exists and which cables or DSX panels are faulty prior to installation and turn up.

2 - 1 0

365-372-300

Issue 8.0, September 2006

Hardware Features

Features

In-service Electric Continuity Test Tool (LNW93)

The In-service Electrical Continuity Test Tool (LNW93) test circuit pack is used for upgrades in the DMX high capacity shelf. An in-service shelf might have a function unit with low capacity DS1

(LNW6 or 7) or DS3 (LNW16) packs. When these packs are upgraded with higher capacity packs (DS1, LNW8; DS3, LNW19/19B), as part of the upgrade procedure, new DS1 or DS3 connectorized cables are added to the DSX cross-connect frames and to the DMX shelf. The

LNW93 pack is used to test out the new wiring without disrupting traffic on the in-service pack.

The LNW93 is very similar to the LNW94 test tool except that it has no backplane connectors for DS1 ports #1-28 or for DS3 ports #1-12.

When the LNW93 is plugged in, it makes no contact with the wires on the backplane for those lower ports. Since there is no physical connection, the LNW93 does not interfere with the service of the pack in the other slot of the function unit. The LNW93 tests the integrity of electrical cables to both identify where trouble exists and which cables or DSX panels are faulty prior to installation and turn up of a high density DS1 or DS3 circuit pack.

Detectable blank circuit packs

DMX supports detectable blank circuit packs: LNW98 in unequipped

Function and Growth slots, LNW97 in an unequipped M2.

The WaveStar

CIT reports the presence of a detectable blank in a slot by displaying a blank faceplate graphic instead of an empty slot graphic. No alarms are associated with the insertion or removal of the detectable blank.

365-372-300

Issue 8.0, September 2006

2 - 1 1

Features

In-service Upgrades

Overview

This section briefly describes the in-service upgrades supported through Release 7.0 of the Metropolis

DMX Access Multiplexer. All features associated with Release 7.0 display the release number next to the feature title. If no release number is specified, the feature was part of a previous release of DMX.

LNW1 to LNW2 in-service upgrade

DMX supports an in-service upgrade from the LNW1 to LNW2 circuit packs on any shelf that is running Release 5.x software. The LNW1 functions with every software Release prior to R6.0, but the LNW2 must be used with R6.0 software (or that of a later Release).

OC-48 UPSR to OC-192

UPSR in-service upgrade

DMX supports an in-service upgrade, enabling you to increase UPSR network capacity from OC-48 to OC-192 without affecting service. No in-service upgrades to the LNW59 are currently supported.

OC-12 UPSR to OC-48

UPSR in-service upgrade

DMX supports an in-service upgrade, enabling you to increase UPSR network capacity from OC-12 to OC-48 (small, 12 STS-1 fabric packs) without affecting service. No in-service upgrades to the LNW59 are currently supported.

OC-48 BLSR to OC-192

BLSR in-service upgrade

DMX supports an in-service upgrade, enabling you to increase BLSR network capacity from OC-48 to OC-192 without affecting service. No in-service upgrades to the LNW59 are currently supported.

In-service electrical upgrade from low to high-density DS1/DS3 circuit packs

DMX supports an in-service electrical upgrade on the High-capacity shelf, enabling you to increase DS1/DS3 capacity without affecting service. There is an outage of 100 to 200 milliseconds when upgrading

DS1 circuit packs. Total DS1 capacity can be increased from 112 to

224 DS1 interfaces per shelf. Total DS3/EC1 capacity can be increased from 48 to 192. Electrical in-service upgrades can be performed on shelves hosting a mix of DS1 and DS3/EC1 circuit packs without affecting service. The DMX High-Capacity shelf is required when using high-density DS1/DS3 circuit packs.

Important!

DMX also supports an in-service electrical upgrade from the LNW16 to the LNW19 or 19B (the LNW19B is available beginning in R5.0). No in-service upgrades to the LNW20 are currently supported.

2 - 1 2

365-372-300

Issue 8.0, September 2006

In-service Upgrades

Features

LNW6/7 Upgrade Rules

Whenever upgrading LNW6 to LNW7 circuit packs, it is necessary to first install an LNW8 circuit pack to ensure that the upgrade is completed without loss of service. The LNW6 and LNW7 are not allowed in a DMX system equipped with LNW59 VLF Mains.

365-372-300

Issue 8.0, September 2006

2 - 1 3

Features

Topologies

Overview

This section briefly describes the major topologies supported through

Release 7.0 of the Metropolis

High-speed (Network interface) OC-192/48/12

UPSR for STS-n/VT1.5

DMX supports Unidirectional Path Switched Rings (UPSR) at the

STS-n and VT1.5 level. When both Main slots are equipped with

OC-192/48/12 VLF or large VT fabric circuit packs, an STS-1/VT1.5 switching fabric (STS-1, STS-3c, STS-12c, and STS-48c) supports the low-speed interfaces. OC-48/12 medium VT fabric cards, supporting

STS-1, STS-3c, STS-12c, and STS-48c are also available. Each circuit pack establishes both an east-to-west and a west-to-east rotation on the ring. A UPSR ring provides a very valuable and reliable foundation for services protecting against fiber cuts and node failures.

High-speed (Network interface) OC-192/48 BLSR for STS-1/VT1.5

The DMX system supports an OC-192/48 Bidirectional Line Switched

Ring (BLSR). When both Main slots are equipped with OC-192/48

OLIU circuit packs, an STS-1 switch fabric supports the low-speed interfaces (STS-1, STS-3c, STS-12c, and STS-48c). A 2-fiber bidirectional line-switched ring (BLSR) is a self-healing ring configuration in which bidirectional traffic travels over the same set of nodes in each direction. Bidirectional switching makes use of redundant (protection) bandwidth on the bidirectional lines that interconnect the nodes in the ring to provide protection for traffic carried on the working bandwidth. Because the traffic is bidirectional, a single circuit does not necessarily consume bandwidth on every span in the ring. This leaves the spans between other nodes available for additional traffic. Therefore, with distributed switching patterns, a

BLSR can carry more traffic than the same facilities could carry if configured for a unidirectional path-switched ring. In BLSR configurations, the VT switch fabric located in the MAIN packs is used only for Function Unit or Growth Slot hairpins.

DMX supports VT BLSRs on all high speed OC-192 interfaces and on high-speed OC-48 interfaces that have a 48 STS-1 VT fabric (LNW29,

LNW27, LNW32, LNW76, LNW221-259).

2 - 1 4

365-372-300

Issue 8.0, September 2006

Topologies

Features

Multiple BLSRs

DMX supports multiple BLSRs on the low-speed interfaces. Including the MAIN, high-speed interfaces, a total of 4 BLSRs can be supported in R6.0. With the VLF Main LNW59, available in R7.0, DMX can support a total of 5 BLSRs when the shelf is equipped with single-port circuit packs. LNW59 provides 4 OC-192 ports, thereby allowing two,

2-fiber BLSRs on the Main interface. When the LNW62 (R7.0) is equipped in all slots of the shelf, DMX can support a maximum of 16

BLSRs.

True 0x1 (R7.0)

LNW70 could be used to provide switched Ethernet services in slot A1, while slot A2 could be equipped with another pack, like an LNW62.

Two of the same circuit pack can also populate adjacent slots in the same group, yet certain restrictions apply. For more information on

0x1, including circuit pack/slot equipage restrictions, refer to Chapter

The 0x1 OCn application replaces 0x1Sn functionality when VLF

Mains are used. 0x1Sn will still be supported when the shelf is equipped with non-VLF Mains. 0x1 is only available on the low-speed/tributary packs, not on the Main (M1/M2) interfaces. When all lines on an OCn pack are set to 0x1, the pack becomes unprotected and the companion slot can be equipped with a different pack.

VT Grooming and

Squelching

DMX supports GR-1230 compliant VT grooming and squelching on

OC-48/192 BLSRs. DMX also support the automatic generation of VT squelch maps.

High-speed (Network interface) OC-192/48/12

Linear optical extensions

DMX supports 1+1 protected linear optical extensions. The high-speed linear optical extension may connect the DMX shelf, by way of

OC-12/48/192 network interfaces in the MAIN slots, to an

OC-12/48/192 node. This feature performs true linear switching based on line layer defects.

R6.0 and later Releases support revertive unidirectional and bidirectional 1+1 (as opposed to just non-revertive).

365-372-300

Issue 8.0, September 2006

2 - 1 5

Topologies

Features

Low-speed UPSRs (for

STS-1 termination and VT

Ring Closure)

The DMX can host multiple rings on the low-speed interfaces of the

DMX shelf. Each circuit pack establishes both an east-to-west and a west-to-east rotation on the ring. A UPSR ring provides a very valuable and reliable foundation for services protecting against fiber cuts and node failures.

DMX supports UPSRs on all lines of all slots equipped with OLIUs.

Low-speed (Tributary interface) Linear optical extensions

DMX supports 1+1 protected linear optical extensions for data transport originating at a data device. The low-speed linear optical extension may connect the DMX shelf, by way of OC-3/12/48 tributary interfaces in the Function and/or Growth slots, to an OC-3, OC-12, as well as an OC-48 node.

Single- and dual-homed ring extensions

The DMX supports low-speed OC-3/12/48 0x1 protected broadband tributaries, including single- and dual- homed ring extensions. A

DDM-2000 OC-3, OC-12, FiberReach, DMXpress, DMXtend, or

DMXplore may be the add/drop multiplexer on the lower-speed ring.

Hairpinning

In “hairpinning” topologies prior to R7.0, low-speed tributary traffic was routed into the system and back out without ever being placed on the high-speed (OC-12, OC-48 or OC-192) interfaces. If the VLF Main pack (LNW59) available in R7.0 is used, all cross-connects use the switch fabric located on these packs. Any switch fabrics located on low-speed, tributary packs are disabled when VLF Mains are used.

2 - 1 6

365-372-300

Issue 8.0, September 2006

Topologies

Features

Dual Ring Interworking

DMX supports UPSR DRI. DMX dual node ring interworking (DRI) cross-connections comply with Telcordia GR-1400 (which refers to

GR-253-CORE) standards. A service selector exists for each STS-N tributary provisioned for DRI.

GbE Private Line

DMX GbE private lines (1000 Mbps) enable premium data transport services offering GbE transport with optional bandwidth provisioning up to full line-rate. GbE private lines provide the user the ability to transport frames completely transparently between two DMX NEs. No

VLAN knowledge or packet-layer provisioning is required by the user in this application. Simple, SONET cross-connect provisioning is all that is required when using “private line” or “no tag” mode. These GbE capabilities allow the DMX to provide dedicated bandwidth for individual customers and fast SONET-layer restoration.

Fast Ethernet Private Line

DMX Fast Ethernet (10/100 Mbps) private lines enable premium data transport services offering 10/100 Mbps transport with optional bandwidth provisioning up to 100Mbps (variable bandwidth provisioning of 1, 2, or 3 STS1s. Fast Ethernet private lines provide the user the ability to transport frames completely transparently between two DMX NEs. No VLAN knowledge or packet-layer provisioning is required by the user in this application. Simple, SONET cross-connect provisioning is all that is required. These Fast Ethernet capabilities allow the DMX to provide dedicated bandwidth for individual customers and fast SONET-layer restoration. LNW71 or LNW74 must be used to enable Fast Ethernet private lines.

365-372-300

Issue 8.0, September 2006

2 - 1 7

Topologies

Features

GbE Packet Rings

DMX supports Gigabit Ethernet (GbE) packet rings that enable cost-effective Internet access and business-to-business LAN services.

GbE packet rings allow interworking among 10/100 Mbps and 1000

Mbps (GbE) Ethernet lines while VLAN tagging ensures individual customer privacy. These GbE capabilities allow the DMX to support various Quality of Service (QoS) features, including fast packet-layer restoration.

4093 VLANs

DMX allows the provisioning of up to 4093 separate IEEE 802.1q

VLANs. VLANs are a way in which LAN users at the enterprise level, located on physically separated LAN networks, are assigned priority access privileges across a WAN backbone. Although they are in different locations, they appear to be on the same physical segment of an enterprise-level LAN. Thus, VLANs are logical groupings of various users, regardless of their physical location on the network.

Stacked VLANs (VLAN Transparency)

DMX allows customer traffic to be identified and segregated using

“stacked” IEEE 802.1q VLAN tags. VLAN tags enable the formation of Virtual Private Networks (VPNs) by segregating various units of traffic and isolating different end-customers. This allows data from different customers to efficiently share common bandwidth while simultaneously ensuring a basic level of security for each customer

(hence VPN).

The notion of VLAN “transparency” comes from the fact that individual customer packets are tagged using a second tag, a default port tag (default port tag is provided by customer equipment). There is no need to coordinate VLAN tags between the customer and service provider. Therefore, customer packets are transmitted through a service provider’s network “transparently”.

2 - 1 8

365-372-300

Issue 8.0, September 2006

Topologies

Features

Resilient Packet Ring

(RPR) Ethernet Protection

DMX supports Resilient Packet Ring (RPR) Ethernet transport compliant with IEEE 802.17. RPR is intended to optimize

Ethernet-based metro ring networks for packet transport with resiliency equivalent to that of SONET rings. It could be used to carry voice and

DMX’s RPR implementation uses enhanced Ethernet bridging as opposed to basic Ethernet bridging. Basic bridging may be supported in a future release.

RPR is supported through the use of the LNW78. LNW78 supports one

RPR instance in R7.0 and two in the future. The LNW78 provides two internal Virtual Concatenation Group (VCG) WAN ports (will support

4 in the future) with a total capacity of 2.5 Gbps capacity for Ethernet

RPR traffic.

Dense Wave Division

Multiplexing (DWDM)

DMX supports DWDM on OC-48 high-speed and low-speed and

OC-192 high-speed interfaces. DWDM enables you to combine multiple OC-48/192 wavelengths on the same fiber. With DWDM and passive filter components, fiber capacity can be increased by a factor as great as 32.

Non-preemptable

Unprotected Traffic

DMX allows the manual provisioning of non-preemptable unprotected traffic (NUT). NUT can be used on both high-speed and low-speed

BLSRs.

NUT ensures that data transmission over SONET BLSR topologies runs smoothly. When using multi-point cross-connections through a

BLSR, packets do not receive standard BLSR protection due to the necessary functioning of NUT. Yet, protection on all data packets is provided for with rapid spanning tree protocol (IEEE 802.1w). Thus,

NUT enables protected packet rings without utilizing SONET layer protection.

365-372-300

Issue 8.0, September 2006

2 - 1 9

Features

Networking Capabilities

Overview

This section briefly describes the major networking capabilities supported through Release 7.0 of the Metropolis

DMX Access

Multiplexer. All features associated with Release 7.0 display the release number next to the feature title. If no release number is specified, the feature was part of a previous release of the DMX.

1+1 Non-revertive

Bidirectional Protection

Switching

DMX now supports non-revertive bidirectional protection switching for all OC-n interfaces in addition to non-revertive unidirectional protection switching.

1+1 revertive unidirectional and bidirectional

Protection Switching

R6.0 and later Releases support revertive unidirectional and bidirectional protection switching.

SAN Networking via DMX

With the LNW73 DMX supports native SAN interfaces integrated into the DMX shelf. The LNW73 is a Storage Area Networking (SAN) interface card designed to facilitate SAN distance extensions via the use of GFP-T (G.7041) to encapsulate SAN traffic and transport it over

SONET networks. It utilizes PTM optics to provide the option of

FICON, ESCON, or Fibre-channel interfaces natively on the DMX shelf. Each pack must be equipped with only one type of PTM (either

FICON/FC or ESCON) and can be housed in Slot A1, B1, C1, D1, or

G1. The LNW73 can operate at 1 Gbps or 2 Gbps. When the pack is operating at 2 Gbps only every other port may be used. So, the total number of SAN interfaces on a DMX shelf is 20 when the LNW73 is operating at 1G FC/FICON or ESCON, and 10 when it is set to 2G

FC/FICON.

DMX is pursuing interoperability certification with established storage hardware vendors such as IBM and EMC. Interoperability testing is currently underway with EMC, with a target date of the end of 2006.

To achieve EMC certification, DMX has been tested with various

FC/FICON switches used with EMC storage equipment. Presently,

DMX has completed testing with the Brocade Silkworm 3800 and

2250, the McData Sphereon 4500, and Cisco MDS 9120 and MDS

9126. This testing has yielded some simple guidelines that need to be followed to ensure smooth interworking between DMX and the

FC/FICON switches listed above. For more information on these

guidelines, refer to General FC/FICON Equipment port configuration for connection to DMX/DMXtend (A-132).

2 - 2 0

365-372-300

Issue 8.0, September 2006

Networking Capabilities

Features

Data Compression for SAN

Traffic (R7.0)

The R7.0 implementation of SAN compression enables a high throughput of up to two full-line rate FC-2G interfaces in a single pack.

Release 7.0 supports data compression on new LNW73C SAN packs.

The LNW73C is able to compress asychronous Fibre Channel traffic and conserve up to 50% of bandwidth versus uncompressed asynchronous FC traffic in typical applications.

Compression for asynchronous FC traffic is pre-standard and will be standardized by FC-BB-4.

Ethernet Interworking with

DDM-2000

To facilitate affordable and more immediate delivery of Ethernet services on SONET networks, DMX now interworks with new

Ethernet circuit packs available for the DDM-2000.

DDM-2000 now supports a circuit pack providing one 100BASE-LX

(100 Mbps p/s) and four 10/100 BASE-TX ports with data transport at the rate of 10/100 Mbps using standard Ethernet switching (IEEE

802.1), standard encapsulation according to ITU G.7041 for Generic

Framing Procedure (GFP), ITU G.707 for Virtual Concatenation

(VCAT). The DDM-2000 can transmit Ethernet signals across spans as long as 100 meters. The DDM-2000 circuit pack is designed specifically to support Fast Ethernet Private Line applications. Each circuit pack can support 4 private lines. The pack supports VT1.5,

STS-1, and STS-3c cross-connections.

The DDM-2000 circuit pack can interwork with the LNW71 and

LNW74 circuit packs.

1 Mbps Rate Limiting

DMX supports rate shaping at the level of 1 Mbps for Ethernet interfaces. This means that DMX can automatically establish Ethernet transmission channels to fit the need of the user upon connection. For each connection, the DMX will create a virtual channel of the appropriate size (in 1 Mbps intervals) to facilitate the desired Service

Level Agreement (SLA). Rate limiting at the 1Mbps level provides a transmission ceiling for highly efficient allocation of shared bandwidth for data communications.

High-speed VT1.5

granularity

VT1.5 granularity is provided across any 12 STS-1 signals within the

OC-48 OLIU (LNW26B, LNW77, LNW28, and LNW121B-159B) providing a fully-flexible assignment of VT1.5 timeslots across any 12

STS-1s. VT1.5 granularity is provided across 48 STS-1 signals within the OC-48 OLIUs (LNW27, LNW29, LNW32, LNW76, and

LNW221-259). VT1.5 granularity is provided across 48 STS-1 signals within the OC-192 OLIUs (LNW58, LNW56, LNW57, LNW523,

365-372-300

Issue 8.0, September 2006

2 - 2 1

Networking Capabilities

Features

LNW527, LNW554, and LNW555). The LNW59 boasts a 40G VT fabric.

VT1.5 granularity is provided across 96 STS-1s on the LNW80 (Main

Switch Pack).

For the VT granularity of the tributary (low-speed) packs, refer to the section above entitled

Optical, Tributary Interface Circuit Packs

Automatic Ring Discovery for BLSR Interworking

DMX supports automatic ring discovery to better facilitate BLSR interworking with Lucent’s FT-2000, WaveStar BandWidth Manager,

Lambda Unite, and WaveStar 2.5G/10G.

Non-preemptable

Unprotected Traffic

DMX allows the manual provisioning of non-preemptable unprotected traffic (NUT) for multi-point Ethernet and 0x1 cross-connections on service tributaries. Though this traffic is unprotected, its transmission priority will not be preempted by other service or protection traffic.

DMX/Lambda UNITE bay configuration

The compact size of the DMX allows you to place two DMX shelves and one Lambda UNITE in the same bay. As the needs of an access site grow to the point where equipment is required to hub more than 6

OC-48 rings, it becomes advantageous to upgrade a DMX shelf to a

Lambda UNITE. The Short Reach (SR) OC-48 and OC-192 optics supported by the DMX are designed for such an application. Once the

Lambda UNITE is installed as the hub-node, the Unite node can hub 64

OC-48 rings or 16 OC-192 rings while simultaneously using the original DMX as a drop node or mini-DCS.

Multicast Ethernet Packets

DMX supports multicast Ethernet packets in all releases. A multicast packet is identified by the first bit in the MAC destination address.

Such a MAC address will never appear as a source address, and so multicast destination addresses (TIDs) are not learned. Since unknown source addresses a treated as broadcast, multicast packets/frames are sent to ALL ports in the VLAN (IEEE 802.1Q) or Transparent LAN

(customer/port tag) for that packet.

Optical Terminal and

Facility Loopbacks

DMX supports facility loopbacks on all OC-192/48/12 high speed

(network side) interfaces. DMX also supports OC-3/12/48 low speed

(tributary side) facility loopbacks as well as low speed OC-3/12/48 terminal loopbacks. Terminal and facility loopbacks are used for installation and maintenance procedures to test the integrity of near and far- end interfaces as well as fibers and system circuitry. OC-3 facility loopbacks are only supported on the LNW37/45 circuit packs.

2 - 2 2

365-372-300

Issue 8.0, September 2006

Networking Capabilities

Features

DS3 Terminal Loopbacks

DMX supports terminal loopbacks on DS3 interfaces.

Ethernet Terminal

Loopbacks

DMX supports terminal loopbacks on all Ethernet interfaces. Ethernet loopbacks may be used during installation and maintenance procedures to test the integrity of near and far- end interfaces as well as fibers and system circuitry.

Ethernet Facility

Loopbacks (R7.0)

DMX supports facility loopbacks on the LNW70 and LNW78. Facility loopbacks are used to test the integrity of the customer to provider network link by looping the signals back at the far end and comparing counts of sent and received frames.

Facility loopbacks are supported on both individual ports and Link

Aggregation Groups (LAGs). Loopbacks on LAGs are permitted simultaneously for both ports in the group because they are treated as failed members allowing transmission on unlooped members. If a facility loopback is set up on a LAG, alarms are suppressed on both the member ports and the LAG.

MAC Address Locking

(R7.0)

DMX allows MAC locking on the LNW70. MAC locking prevents unauthorized users from gaining access to the network through an

Ethernet port, thereby providing a level of security against intrusion attempts. MAC locking restricts access to a bridged Ethernet network by requiring that the source address of traffic entering a locked port be registered with that port. Any number of ports, LANs, VCG, or link aggregation groups (LAGs) can be locked. DMX permits registering of multiple addresses with a single entity.

365-372-300

Issue 8.0, September 2006

2 - 2 3

Networking Capabilities

Features

Fast Spanning Tree/

IEEE802.1w Rapid

Reconfiguration

Ethernet requires a network with a tree structure in order to work effectively. Ethernet bridges and switches build tables that define the paths to specific devices. A MAC bridge, for example, will have a filtering database that defines where to send any packets addressed to a specific MAC within the network. The tables are built based on input from devices within the network. DMX supports an improved/faster spanning tree algorithm, documented in IEEE 802.1w Rapid

Reconfiguration.

R6.0 added support of spanning tree on LAN ports on the LNW70 in addition to VCG ports that were supported in previous releases.

If there is a loop in the network, that is, if there is more than one way to get to a destination device, two problems can result:

Frames may be duplicated in the network.

• That is, the same frame may be sent to a node via two different paths.

The address information will be changed as packets from that device are received across different paths. In a meshed network, the reconfiguration of the filtering database can begin to use up all the network resources, so that little bandwidth is left for data traffic.

The spanning tree accomplishes two important functions:

• It removes loops from the bridged network

• It allows Ethernet layer reconfiguration if a link fails.

Important!

DMX has been designed with multi-vendor interoperability in mind. As many vendors’ equipment (including legacy equipment) may not be able to use IEEE802.1w, DMX can automatically fall back on IEEE802.1d in the event that other NEs in the network are running standard spanning tree protocol.

However DMX employs IEEE 802.1w as a default spanning tree protocol.

SS Bits Per Pack

By default DMX transmits 00 in the outgoing SS pointer bits for compatibility with SONET interfaces. DMX provides the ability to set the outgoing SS bits to 10 on a LS optical pack basis for compatibility with older SDH equipment. DMX ignores incoming SS bits regardless of the outgoing SS bit provisioning. Most SONET equipment ignores

SS bits. DMX is provisionable to support SS bits on a per pack basis.

This prevents LOP defects and allows SONET/SDH interworking.

2 - 2 4

365-372-300

Issue 8.0, September 2006

Networking Capabilities

Features

E1 Service Support

DMX supports 56 E1 signals on the LNW8 circuit pack. E1 signals are

SDH/PDH signals at 2.048 Mbps. DMX supports performance monitoring on E1 signals.

R4.0 Ethernet

Enhancements

Release 4.0 contains many software-based enhancements to the functionality of DMX Ethernet circuit packs. Again, these are software-based enhancements and require no changes to DMX hardware.

• Ethernet Latency improvements

• Ethernet auto-negotiation provisioning

• Automatic MDI/MDIX crossover capability on LNW71

• TCAs on Ethernet PM error counts

• Ethernet MAC address table search and report (with support for static entries)

• Ethernet loopbacks

• Admin-down capability for Ethernet ports

• QinQ stacked VLAN tags

• Extension of 1-way cross-connections for video broadcast to

BLSR rings

365-372-300

Issue 8.0, September 2006

2 - 2 5

Networking Capabilities

Features

R5.0/5.1 Ethernet

Enhancements

Release 5.0 and 5.1 contain many hardware and software-based enhancements to the functionality of DMX Ethernet circuit packs. As these are hardware-based enhancements, they require the use of the

LNW70 and LNW74 circuit packs. The features with a circuit pack listed in parenthesis are available only with the use of that pack and not both. The features associated with the LNW70 circuit pack are available beginning in R5.1.

• Committed and Peak rate controls (CIR and PIR) (LNW70)

• 4 classes of services (LNW70)

• 4xGbE density with PTM optics (LNW70)

• Larger MAC tables (LNW70)

• 32 VCGs (star configuration) per G.707 (LNW70)

• 16 virtual switches with independent VLAN space per virtual switch (LNW70)

•

Jumbo Frames (refer to Packet size in different tagging modes (A-86)

• Link Capacity Adjustment Scheme (LCAS) per ITU G.7042

• Generic Framing Procedure (GFP) per ITU G.7041

• Client Signal Fail

• 100BASE-FX optical, fast Ethernet ports

• VT1.5 VCAT (LNW74 only)

LNW78 RPR

Enhancements (R7.0)

In addition to the various Ethernet networking capabilities detailed above for R7.0, the LNW78 RPR pack has been upgrades to support the following capabilities:

• VCG ports 17-22 are now available to provide EoS connectivity.

This feature allows EoS port connectivity to RPR ring interfaces via the faceplate of the LNW78 and/or hairpin cross-connects.

• Standards-based LCAS

• Interconnection of multiple RPR rings on the same shelf or separate shelf using EoS VCGs.

• EoS traffic can be managed with QoS support on EoS VCGs.

• Support of Basic RPR Bridging. In past Releases, DMX only supported enhanced RPR bridging.

2 - 2 6

365-372-300

Issue 8.0, September 2006

Networking Capabilities

Features

QoS on EoS VCGs (R7.0)

QoS on EoS VCGs functions by giving EoS VCG ports the same classification options for incoming packets, rate control capabilities for

Ethernet services (PIR, CIR), queuing/scheduling capabilities for outgoing, and the same packet transformation functions as on 802.3

LAN ports.

Link Aggregation on

LNW70 LAN Ports (R7.0)

DMX supports link aggregation on any two LNW70 LAN ports of the same rate (i.e. 100 or 100 Mbps) operating in switched mode. The ports must be located on the same pack and DMX supports a maximum of 8

Link Aggregation Groups (LAGs) per function unit/growth group.

Link aggregation can be used to enable hitless bandwidth increases and both facility and equipment protection on LNW70 LAN ports.

Ordinarily, multiple Ethernet links between two bridges form loops

(unless a spanning tree blocks all but one) so they can’t be used to increase bandwidth. Link Aggregation causes defined groups of links to be treated as a single logical link, making multiple LAN ports appear as one. In this way, Bandwidth can be increased without requiring an upgrade to a higher rate link.

Link aggregation can also remove failed links automatically, thereby providing a means of facility protection. More links than are needed can be added to the group and each is active until it fails (similar to utilizing LCAS protection for SONET).

365-372-300

Issue 8.0, September 2006

2 - 2 7

Features

Cross-connection Types

All allowable crossconnections

This section details the types of cross-connections supported by the last few releases of DMX. Thus, this represents only a fraction of the total allowable cross-connections. For an in depth look at cross-connections supported by the DMX, refer to the section entitled

“Cross-connections” in Chapter 5 of this document.

Atomic cross-connections

Beginning in R6.0, DMX employs atomic cross-connections for all cross-connect provisioning. The introduction of atomic cross-connections simplifies cross-connection provisioning and lays the ground work for the support of additional applications and combinations of cross-connections in future releases. Atomic cross-connections are one-way cross-connections between logical ring channels which can be set up and taken down by a single command, and which cannot be broken down into smaller parts. Logical ring channels are the tributaries of a port or port protection group used for transmission in the absence of any line or equipment protection.

Atomic cross-connections are more flexible than the cross-connect provisioning structure employed previously. They allow for the support of more detailed applications because multiple atomic cross-connections can be provisioned to construct the desired cross-connection application.

The difference is that you are provisioning each portion of the 2way cross-connect (as in legacy releases) as 1way cross-connects. This provides increased flexibility in provisioning all cross-connects.

For customers who use the WaveStar PC-CIT, Telcordia Operating

Systems (OS), and Navis INC this change will be transparent. In order to support atomic cross-connections for the first time, customers employing proprietary OS solutions will need to adjust their cross-connection provisioning procedures.

2 - 2 8

365-372-300

Issue 8.0, September 2006

Cross-connection Types

Features

Hairpinning cross-connections

Prior to R7.0, and when VLF Mains are not used, DMX is capable of connecting any input on a circuit pack in a function or growth slot to any output on a circuit pack in a different function or growth slot in the same shelf. With the VLF Mains available in R7.0, DMX can cross-connect any input on a circuit pack in a function or growth slot to any output on a circuit pack in the same or different function or growth slot. This is because R7.0 enables true 0x1 configurations where both slots in a function group can be provisioned independently for working traffic, wether they are the same or different packs (certain restrictions

apply, refer to Very Large Fabric (VLF) Engineering Rules (5-15)).

These flexible cross-connect capabilities allow you to use a combination of add/drop and hairpinning of compatible payloads through a variety of interfaces. You can bring traffic in from one remote site and cross-connect it at the VT1.5, STS-1, STS-3c, STS-12c, or STS-48c level back out to other remote sites without consuming any capacity on the ring/line interface.

If hairpinning cross-connections are being provisioned between any interface and a 0x1 unprotected interface, 1-way cross-connections must be used. 1-waypr cross-connections are not allowed in 0x1 unprotected scenarios.

Bridge and Roll cross-connections

Bridge and roll cross-connections are coordinated activity between two

NEs designed to move traffic from one facility to another, affecting service by a maximum of 10 milliseconds.

Bridged Cross-connections

Bridging of an existing cross-connection consists of adding a one-way cross-connection with the same input tributary as that of an existing cross-connection, resulting in a 1x2 multicast from an input tributary to two output tributaries. DMX supports bridging for each of the supported SONET cross-connection rates. You can bridge any existing cross-connection to a second output port without impairing the existing signal. Conversely, either half of a bridged signal can be taken down without impairing the remaining cross-connected signal.

365-372-300

Issue 8.0, September 2006

2 - 2 9

Cross-connection Types

Features

Rolling a bridged cross-connection

The DMX provides the capability to change the location or source of the input tributary of a given cross-connection. The DMX supports facility rolling for all supported signal rates as follows:

• Disconnection of the circuit cross-connecting input tributary to output tributary

• Cross-connection of either a new input tributary to the corresponding input tributary

Locked DS1/DS3 Cross

Connections

In the “locked” mode, DMX does not select the best signal from both rotations of a UPSR. Instead, traffic is added and dropped (locked) from one rotation of the ring only (provisionable). The main advantage of locked DS1/DS3 cross-connections is the lack of UPSR switching.

Locked VT Cross

Connections (R7.0)

In the “locked” mode, DMX does not select the best signal from both rotations of a UPSR. Instead, traffic is added and dropped (locked) from one rotation of the ring only (provisionable). The main advantage of locked VT cross-connections is the lack of UPSR switching which results in the ability to reuse timeslots around a UPSR.

The ability to mix locked, unlocked, and pass-through VT1.5s within the same STS-1 was added in R6.0.2. In R7.0, DMX also allows both rotations of a ring to be used simultaneously.

Linear/Unprotected UPSR

(R7.0)

In R7.0, DMX also allows both rotations of a ring to be used simultaneously. Prior to 7.0, if a 1WAY (as opposed to a path-protected

1WAYPR) cross-connection was established with the source from a

UPSR ring, the other side became unusable as the source (1WAY) or destination of a cross-connection (1WAY or 1WAYPR), except for pass-through cross-connections. This feature removes those restrictions.

DMX permits simultaneous 1WAY cross-connections sourced from the

2 associated ring channels in a UPSR application, simultaneous 1WAY cross-connection sourced from a ring channel, and 1WAY or

1WAYPR destined to the associated ring channel.

This feature removes the need for unswitched cross-connections on

Ethernet/Data packs which don’t require VCG pairing, yet they will still be supported to ensure backwards compatibility.

2 - 3 0

365-372-300

Issue 8.0, September 2006

Features

Operations Features

Overview

This section details the operations features available with Release 7.0 of the Metropolis

DMX PC-CIT with GUI

The PC-CIT manages the DMX system through the TL1/CIT port, providing TL1 messaging, software download, and full operations and provisioning capability via a Graphic User Interface (GUI) or TL1 command builder. The PC-CIT can run a full-featured GUI or TL1 scripts. Using the GUI, a crafts person can access all DMX software functions and context-sensitive help. The TL1 command builder, also known as the TL1 Translation Device (T-TD), is a flexible TL1 command instructor that supports full TL1 management through

TCP/IP or RS-232 interfaces.

The PC-CIT is not used to download release software to the system (the

PC is used, but not the CIT software). Release software can be copied to other NEs remotely, provided the initial download of DMX release software has occurred on each system.

Performance monitoring

Performance monitoring (PM) data will be reported on the VT1.5,

VC12, STS-1, STS-3c, STS-12c, STS-48c, DS1, E1, DS3, EC-1,

Ethernet (LAN and VCG ports), SAN, OC-3, OC-12, OC-48 and

OC-192 levels.

Alarm Severity Assignment

Profiles (ASAPs)

DMX supports adjustable ASAPs. With ASAPs, alarms are grouped into categories called “Profile Types”. Each Profile Type can have multiple views (ASAPs). These views include the default view and various user created/provisioned profiles. Each ASAP within a profile type has the same alarms, but alarm severity levels are user provisionable. The user can then assign ASAPs to entities within the shelf.

With legacy releases, many alarm severity levels are hardcoded and are not adjustable. R6.0 and later Releases make it possible to assign different alarm severity levels for all alarms. This feature also allows the user to assign different alarm severity levels for the same probable cause to different entities within the shelf. Once alarm severity levels

365-372-300

Issue 8.0, September 2006

2 - 3 1

Operations Features

Features

Pipe-mode (adaptive-rate) cross-connections

Proxy ARP

are set, the user can assign the same level to different entities without reprovisioning the level itself.

These capabilities give the user greater control over alarm reporting.

Pipe mode is a fault and PM feature whereby fault and PM are reported independently for each constituent signal within a cross-connection rather than simply at the xc rate.

In normal ARP usage for an Ethernet LAN, the sending system broadcasts an ARP request on the physical LAN. The ARP request contains the target IP address and asks the system with this IP address to respond with its physical Ethernet address. All systems on the LAN receive the request, but only the system which recognizes the target IP address as its own will send a point-to-point ARP reply to the sending system. The broadcast ARP request on a physical LAN only reaches systems which are attached to this physical LAN. If the sending system and the target system are on different physical networks, the target system will not receive the ARP request and thus can not respond to it.

Proxy ARP lets a system, called ARP subnet gateway, answer ARP requests received from one of its physical (LAN) networks for a target system which is not attached to this physical network.

To allow SNMP manager/NTP server located in the IP-based access

Data Communication Network (DCN) to communicate with NEs located in the OSI-based DCN, DMX supports IP tunneling solution to encapsulate and route IP packets over OSI-based embedded DCN. The provisioning of static routes on the external router(s) is required to route the IP packets from the access DCN to the embedded DCN. The

Proxy ARP support on the Gateway Network Element (GNE) will eliminate this need of static routes on the external router(s).

Support of Simple Network

Management Protocol

DMX makes use of Simple Network Management Protocol (SNMP).

SNMP is the most common protocol used by data network management applications to query a management agent using a supported Management Information Base (MIB). SNMP operates at the

OSI Application layer. The IP-based SNMP is the basis of most network management software, to the extent that today the phrase

“managed device” implies SNMP compliance. The DMX provides

SNMP support of certain reports and traps for all Ethernet interfaces.

For more information, see the section entitled “SNMP Parameters and

Traps” in Chapter 6 of this document.

DMX supports SNMP on DS1/E1 and DS3/EC-1 interfaces. SNMP support of these TDM interfaces includes traps and performance monitoring parameters.

2 - 3 2

365-372-300

Issue 8.0, September 2006

Operations Features

Features

Test Access

Test access, a traditional DCS function, allows the user visibility into any DS1/DS3 signal in the network. Test access aids users in turning up connections and in identifying faults in existing service connections.

DMX supports two different types of test access. The non-intrusive method simply taps the DS1 channel as it passes through the system and routes it to an external testing device. The more intrusive mode splits the DS1 or DS3 from the incoming signal and sends it to an external testing device. Test access facilitates DMX functioning in a

DCS application.

PRBS generation/detection

Test access using PRBS generation/detection via the internal test head on the VLF Main allows the user to test network, NE, and facility performance/integrity without an external test head. The VLF Mains introduced in R7.0 contain an internal test head that can generate and detect errors in Pseudo Random Bit Sequences (PRBSs). This capability is not meant to wholly eliminate the use of external equipment for tests, but can be used for expediency, less complicated tests, and where non-manual set-up is advantageous. PRBS enabled test access involves initiating test access, inserting a test signal (i.e. a

PRBS) generated internal to the NE, and/or monitoring a received test signal internal to the NE. PRBS generation/detection is supported on

STS1 and STS3c tributaries.

DMX allows up to 12 test access sessions at a time and for a mix of the old style test access sessions described on the previous pages

(specifying tatrib(s)) or the new-style session (to the internal test head) within the 12 allowed sessions. The internal test head hardware supports signal generation on up to 12 STS1s, and signal detection on up to 12 STS1s. Test access for STS3c rates is new in R7.0. Only internal test access is supported on STS3c signals; requests using the tatrib parameter(s) will be denied. It’s important to note that when a generator or detector is allocated to an STS3c session, it uses 3 of the

12-STS1 capacity, and that 3 generators or detectors on the STS3c boundary must be available.

TL1 management

TL1 messaging is supported via the Serial and IAO LAN interfaces.

The DMX PC-CIT, when used in conjunction with the TL1 command builder, provides full TL1 management through TCP/IP to OSI interfaces.

365-372-300

Issue 8.0, September 2006

2 - 3 3

Operations Features

Features

TL1 management via

TCP/IP

TL1 message exchange is supported over TCP/IP via IAO LAN, OSI

LAN, and PC-CIT interfaces. IAO LAN supports TCP/IP protocol and

OSI protocol. These provide a communication link from a DMX to a local node that may serve as a gateway to the network.

Integrated TCP/IP

Management Interface

The DMX supports two types of IP Access. In one case, the DMX can serve as a TL1 Translation Device (T-TD) by being a gateway network element that allows a Navis EMS and/or PC-CIT to communicate to other network elements (NEs) on an OSI network through an IP access network. In the second instance, the DMX can functionally encapsulate

IP packets within OSI packets to be transmitted through the OSI network to the proper NE. This capability is called IP tunneling.

TL1 Translation

The DMX can copy the application information within an IP packet into an OSI packet. Thus, all IP protocol information is lost. This translation is performed at the application layer. Separate gateways can be provided by a single DMX.

IP Tunneling

IP tunneling allows for file transfer through an IP access network. IP tunneling is used to perform end-to-end FTP through the OSI portion of the IP access network. In this instance the DMX serves as a gateway network element (GNE) that encapsulates an IP packet within an OSI packet. When the final destination of the file is reached, the IP packet is removed from within the OSI packet and processed by the TCP/IP stack. Thus, IP tunneling allows an Navis EMS and/or CIT to reach

NEs in an OSI based DCN network with FTP over IP. In this case, the end points of the IP tunnel are the actual terminating points for the IP traffic.

FTP/FTAM Gateway for remote software download

Also referred to as FTTD (File Transfer Translation Device), the FTTD allows DMX to function as a Gateway Network Element (GNE) that can facilitate the download of files located at FTP servers to remote

NEs connected to the DMX.

Software download over

DCC

This feature enables software (upgrade) to be downloaded to remote

NEs from a central office site via the data communications channel

(DCC).

2 - 3 4

365-372-300

Issue 8.0, September 2006

Operations Features

Features

Increased OSI associations

The maximum number of OSI associations per TCP connection has been increased from 64 to 300. The maximum number of OSI associations for TL1 per GNE has been increased from 200 to 300.

250 NEs in a Level 1 area

The maximum number of NEs per OSI Level 1 routing area has been increased from 50 to 250.

OSI seven-layer protocol stack

This feature provides interworking using the Open Systems

Interconnection (OSI) seven-layer protocol stack over the data communications channel (DCC). The OSI seven-layer protocol stack refers to the OSI reference model, a logical structure for network operations standardized by the International Standards Organization

(ISO).

Remote NE Status

This feature partitions a subnetwork into maintenance domains (alarm groups). An Alarm Group is a set of NEs that share status information.

Alarm groups can be nodes in a ring or any other logical grouping such as a maintenance or geographical group. Each Level 1 area can be identified as a separate Alarm Group, as long as it does not exceed 50 nodes. You must provision one NE in an Alarm Group as an alarm gateway NE (AGNE) to support office alarms and a summary alarm information of remote NEs in the local alarm report. More than one

AGNE can be provisioned per alarm group, but this is not recommended.

Security

Security features include 1-999 day password aging, customized login proprietary messages, and 150 users.

TARP

DMX is compatible with any other-vendor NEs that support Target ID

Address Resolution Protocol (TARP), OSI, IAO LAN, and TL1 as specified in Telcordia Technologies GR-253.

SONET

Many of the traditional SONET maintenance, provisioning, operations, control, and synchronization features are included in the DMX. The flexible SONET standard provides a formidable foundation for the

DMX to build upon.

TIRKS/NMA/Transport compatibility

Multivendor Operations

Interworking

DMX is supported by Telcordia OSs: TIRKS, NMA, and Transport.

DMX supports interoperability with many vendors’ equipment.

365-372-300

Issue 8.0, September 2006

2 - 3 5

Operations Features

Features

Product Family

2000/WaveStar Product

Family Interworking

DMX supports TARP interoperability with Product Family 2000 nodes such as the FT-2000 OC-48 Lightwave System, the DDM-2000

OC-3/OC-12 Multiplexer, and the DDM-2000 FiberReach Multiplexer.

DMX also provides interoperability with all WaveStar Product Family nodes supporting TARP over both UPSR and BLSR applications.

DMX provides interoperability with WaveStar BandWidth Manager nodes supporting TARP over both OC-48 and OC-192 BLSRs.

Navis

Operations Support

DMX supports operations via Lucent’s Navis™ Optical OMS and

Navis™ Optical INC.

Network Time Protocol

Network Time Protocol (NTP) assures accurate synchronization of the

DMX with reference to radio and/or atomic clocks located on the

Internet.

2 - 3 6

365-372-300

Issue 8.0, September 2006

Features

Synchronization

Embedded Stratum 3 timing generator

The OC-12/48/192 high-speed circuit packs (as well as LNW80) contain an embedded Stratum 3 timing generator. This timing generator is used when the DMX is configured in a free running mode.

Line timing and external timing are also supported by DMX. Line timing is derived from an incoming MAIN or tributary OC-12/48/192 line, while external timing is derived from an external timing source.

Line timing from tributary optical interfaces is supported beginning in

R7.0.

DS1 timing output

DMX can generate a DS1 timing output to time other externally-timed systems. The DS1 output is derived from a line reference.

S1 byte synchronization messaging

DMX uses the S1 byte of the SONET overhead to pass timing status information to different nodes in an access transport network.

Line Timing from Optical

Tributary Packs (R7.0)

DMX can derive timing references from low-speed/tributary optical interfaces beginning in R7.0. Prior to R7.0, line timing references could only be derived from the signals entering the Main circuit packs. DMX can now derive timing references form any optical line entering Main,

Function Unit, or Growth slots.

All optical circuit packs can derive a 6.48MHz timing signal from an incoming optical line.

365-372-300

Issue 8.0, September 2006

2 - 3 7

Synchronization

Features

2 - 3 8

365-372-300

Issue 8.0, September 2006

3 Applications and Configurations

Overview

Purpose

The DMX Access Multiplexer supports a wide range of service applications and a variety of network configurations economically and efficiently.

Because DMX is very flexible, most of the applications described in this section can be served over many of the available network topologies. The product configuration deployed depends on many factors such as fiber layout location, mix of services offered, and interconnections to other networks.

The first section of this chapter describes service applications. The second section explains the network topologies supported.

The following sections are included in this chapter:

Service Applications

Network Configurations

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 1

Applications and Configurations

Service Applications

Overview

Purpose

The DMX Access Multiplexer provides a wide range of service applications transporting voice and data from the access edge of the network to the core of the network. These applications range from traditional SONET applications to advanced data transport applications.

Features

DMX provides the following features for the service applications described in this section:

• DS1 transport and switching

• DS3 transport and switching

• E1 transport

• EC-1 transport and switching

• OC-3 transport and switching

• OC-12 transport and switching

• OC-48 transport and switching

• OC-192 transport and switching

• 100BASE-TX/FX transport and switching

• 1000BASE-SX/LX transport and switching

• SAN (FICON/ESCON/Fibre-Channel) transport

• Synchronization distribution (DS1 timing inputs and outputs)

• Single-ended or independent operations

• Long reach single-mode fiber spans for OC-3, OC-12, OC-48, and

OC-192 optics

• Passive wavelength division multiplexing (DWDM)-compatible optics.

3 - 2

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Overview

Applications and Configurations

The figure below shows how the DMX fits into Lucent’s metropolitan optical networking solution.

Figure 3-1 Multiservice Optical Access Network

Large

Business

PBX/Switch

Router

- Voice

- Broadband Data

- 100/1000 Ethernet

Metropolis

DMX

DOS

Metropolis

DMX

OC-48/192 UPSR

Metropolis

DMX

Medium

Business

Switch

Router

OC-48

Metropolis

DMX

PSR

Metropolis

DMX

FR/ATM

Edge

Switches

Broadband

(ATM,TDM)

Ethernet

DSLAM CMTS

- Voice

- Wideband Data (TDM,

ATM, FR,PPP)

- 10/100 Ethernet xDSL

Residential/SOHO

Customer

ATM

Concentrator

Access Node

DMX = Metropolis DMX Access Multiplexer

HFC

Voice

Switch

Access

Routers

LAN

Application

Services

Core

Router(s)

Access

Routers

ATM

Core

Switch

Service Node/CO

PSTN

Internet

ATM nc-dmx2-029

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 3

Overview

Applications and Configurations

Contents

Service applications described in this section include:

Established Network Evolution

Access Transport for Voice and TDM Private Line Services

Interoffice Transport

Ethernet Private Line

Multi-point Ethernet Private Line

Ethernet Rate Shaping Services

Hitless Bandwidth Provisioning with LCAS

Link Aggregation (LNW70 LAN ports)

Virtual LAN Services

Transparent LAN Services

Best Effort Ethernet Service

Ethernet/TDM Access to Frame Relay and/or ATM Service

Ethernet/TDM Access to IP Network

DMX as an Ethernet Hub using LNW70

DMX as an Ethernet Hub using LNW78

Ethernet Transport via RPR

SAN Distance Extensions with DMX

Converged Service Delivery via Metropolis

DMX Product

Family

DSLAM Access

TransMUX Functionality with LNW18/20

Enhanced TransMUX Functionality with LNW20

3 - 4

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Established Network Evolution

Overview

The DMX offers a capacity upgrade from an OC-3 or OC-12 network to an OC-12/48/192 network. Implementing a DMX ring at the edge of the network, in combination with pre-existing OC-3 and OC-12 rings, provides increased network capacity and flexibility with the opportunity to interwork with or replace current-generation access multiplexers.

Description

The DMX can interwork with existing Lucent and other-vendor

SONET network elements to support all of the applications and topologies described in this section. The figures below show the network evolving from an OC-3/OC-12 network to an OC-48/192

network. Figure 3-2 (3-5) shows the original network, while Figure 3-3

(3-6) shows the network evolution when once DMX is deployed.

Figure 3-2 Established Network

WBDCS/

DMX

WaveStar

2.5G/10G,

BWM

CO/POP

OC3/12

DDM

OC3/12

DS1,DS3, OC-3c

Customer

Location

DDM

FiberReach

Customer

Location nc-dmx-157

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 5

Established Network Evolution

Figure 3-3 Established Network Evolution

Applications and Configurations

WBDCS/

DMX

DS1,DS3,

OC-3/12/48

Metropolis

DMX

OC-12/48/192 UPSR

WaveStar

2.5G/10G,

BWM

DDM

OC3/12

DS1,DS3, OC-3c

CO/POP

Metropolis

DMX

Hub/RT

DS1,DS3

Metropolis

DMX

OC-3/12

& rings

Customer

Location

Customer

Location

DDM

FiberReach nc-dmx-015

Application advantage

As greater capacity is needed, the DMX provides customers a graceful upgrade path from smaller capacity OC-3/12 networks to

OC-12/48/192 DMX networks capable of enhanced applications, topologies, and capacities. The features of the DMX enable it to cost-effectively serve your needs now while protecting your networking future.

3 - 6

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Access Transport for Voice and TDM Private Line Services

Overview

The DMX supports a full set of interfaces, topologies, and operations to provide the flexibility, upgradability, and ease of operation required to meet the dynamic requirements of the access transport environment. A

DMX OC-12/48/192 path switched ring for TDM transport of voice and private line services is a reliable infrastructure for residential or small business voice services.

Description

DMX is particularly suited to the evolving needs of voice and private line access transport applications due to its compact size, environmental hardening, and capacity growth potential. The DMX’s flexibility allows the infrastructure to be optimized for a particular fiber topology, service mix, and growth forecast. DMX can simultaneously support wideband and broadband private line services for DS1, DS3,

E1, EC-1, OC-3, OC-12, and OC-48 client interfaces.

The figure below shows a path switched ring transporting low-speed

DS1 signals that are carrying voice services from a PBX or a digital loop carrier (DLC) system over an OC-48 or OC-192 ring. In this application, DMX hands off these voice circuits to the voice switch in the central office using a very cost-effective DS1/EC-1 interface.

Figure 3-4 Voice and Private Line Access Application

Customer

Location

Voice

Switch

DS1/

EC-1

Metropolis

DMX

DS1,DS3,

OC-3(c)/

12(c)/48(c)

OC-12/48/192

Metropolis

DMX

Metropolis

DMX

Cabinet

DS1 DLC or

PBX

DS1,DS3,

OC-3(c)/

12(c)/48(c) nc-dmx-007

Application advantage

The access transport application provides low-cost transport of revenue-generating voice and private line wideband and broadband services in a single multiplexer.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 7

Applications and Configurations

Interoffice Transport

Overview

The DMX provides the features necessary for interoffice transport in a greater metropolitan area, including long-span optics, easy capacity upgrades, and add/drop interfaces to other CO equipment. A

VT1.5/STS-1 OC-48 path switched ring is a very effective self-healing network configuration for large cross-section interoffice networks.

Description

The DMX is ideal for metropolitan interoffice transport applications due to its large capacity and mixture of voice, data, and Ethernet services. An OC-12/48/192 UPSR/BLSR ring provides fast and reliable transport of DS1, E1, DS3, EC-1, OC-3(c), OC-12(c), OC-48(c), and

10/100/1000 Mbps Ethernet services.

The figure below shows a sample interoffice transport configuration.

Figure 3-5 Interoffice Transport

Central Office

DMX

OC-48/192

Central Office

DMX

OC-48/192

Central Office

DMX

DS1, DS3, E1, EC-1,

OC-3, OC-12, OC-48

10/100/1000 Mb/s

Ethernet

DS1, Ds3, E1, EC-1,

OC-3, OC-12, OC-48

10/100/1000 Mb/s

Ethernet

OC-48/192

Central Office

DMX

OC-48/192

DS1, Ds3, E1, EC-1,

OC-3, OC-12, OC-48

10/100/1000 Mb/s

Ethernet

VT1.5/STS-1 cross-connect

DS1, DS3, E1, EC-1,

OC-3, OC-12, OC-48

10/100/1000 Mb/s

Ethernet nc-dmx2-030

Application advantage

DMX’s interoffice transport applications provide low-cost, self-healing voice, Ethernet, asynchronous transfer mode (ATM), and frame relay

(FR) transport on a single multiplexer.

3 - 8

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Ethernet Private Line

Overview

Ethernet private lines provide the user the ability to transport frames completely transparently between two DMX NEs. No VLAN knowledge or packet-layer provisioning is required by the user in this application. Simple, SONET STS-1 cross-connect provisioning is all that is required. These private line capabilities allow the DMX to provide dedicated bandwidth for individual customers and fast

SONET-layer restoration in the event of a facility-based failure.

Ethernet Private Line

(point-to-point Ethernet) for

Enterprise LAN transport

DMX utilizes standard STS-1 (STS-3(c) can also be used) with virtual concatenation (ITU G.707) to transport 10/100 Mbps or 1000 Mbps

Ethernet services over a SONET OC-12/48/192 UPSR/BLSR ring. In this configuration, Ethernet traffic from an end customer may be fed to a core router in the central office (CO), while voice traffic is fed from the same ring to a voice switch in the CO. In private line LAN transport configurations, standard SONET UPSRs/BLSRs provide restoration of service within 50 milliseconds.

Figure 3-6 Ethernet Private Line Transport Application

Customer A Customer B

Server Farm

Switch/

Router

10/100Mbps

GbE

Local

Branch office

Main campus

Switch/Router

1000Mbps

GbE

Metropolis

DMX

Customer A

Metropolis

DMX

OC-192

10/100Mbps

GbE

Local

Branch office

Switch/Router

Metropolis

DMX

1000Mbps

GbE

OC-12/48

Metropolis

DMX

Regional

POP

Customer B

Main Office nc-dmx2-018

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 9

Ethernet Private Line

Applications and Configurations

Application advantage

Ethernet Private Lines simplify networks by eliminating intermediate

WAN protocols, such as frame relay or ATM while providing service providers an ideal migration path from traditional private line, circuit-based services.

Ethernet Private Lines also provide dedicated bandwidth and absolute

QoS for business critical data transport applications. Private lines are protected by SONET layer protection switching with a guaranteed restoration time of less than 50 milliseconds.

3 - 1 0

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Multi-point Ethernet Private Line

Overview

This section is meant to supplement the previous section (Ethernet

Private Line) and aims at better describing the Multipoint Ethernet cross connection functionality of private lines.

Multi-point Ethernet Private

Line for Enterprise LAN transport

Similar to the figure discussed in the previous section, the figure below shows a customer (Customer 1) with a private line connecting multiple sites. In such applications, multi-point connectivity enables simultaneous connectivity to all sites serviced by the private line at all times. Ethernet private line links are sized independently and are configured for 802.1q or Transparent VLAN mode, and VT Virtual

Concatenation in R5.0. Finally, in multi-point ethernet applications, the intermediate nodes (the DMX at the bottom of the ring in the figure below) provide a simple bridging function, passing-through all

Ethernet traffic on the private line. As such, the intermediate nodes do no require Ethernet functionality.

Figure 3-7 Multi-point Ethernet Private Line Application

SONET-protected

Link A

Customer 1

Metropolis

DMX

SONET-protected

Link B

Customer 1

Metropolis

DMX

OC12/48/192

UPSR

Metropolis

DMX

Customer 1

Metropolis

DMX

DMX = Metropolis DMX Access Multiplexer

Through Nodes do not require

Ethernet functionality nc-dmx2-034

Multicast Ethernet Packets

Multicast Ethernet packets/transmission can be used to facilitate certain private line applications. Yet, Ethernet private line can be implemented using a variety of Ethernet cross-connection types. For more information about Ethernet cross-connection types, refer to the section entitled “Cross-connections” in Chapter 5 of this document.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 1 1

Multi-point Ethernet Private Line

Applications and Configurations

Multicast Ethernet can also be used to facilitate video distribution, webcasting, and any other application in which multipoint Ethernet cross-connections are used. For more information on the functionality of multicast Ethernet in the DMX, refer to the section entitled

“Networking Capabilities” in Chapter 2 of this document.

Application advantage

Multi-point Ethernet Private Lines eliminate the need for an adjunct data switch and further simplify networks by eliminating intermediate

WAN protocols, such as frame relay or ATM while giving service providers an ideal migration path from traditional private line, circuit-based services.

Multi-point Ethernet Private Lines also provide absolute QoS and security for data transport applications with dedicated bandwidth and

SONET layer protection switching (less than 50 millisecond restoration time).

3 - 1 2

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Ethernet Rate Shaping Services

Overview

Rate-shaped services offer a statistical multiplexing model that makes efficient use of shared bandwidth. DMX currently supports two of the primary forms of rate shaping. The two primary forms of rate shaping are rate limiting, and guaranteed rate services (plus various combinations of both).

Rate limiting is achieved using Peak Information Rate (PIR) provisioning. Guaranteed rate service is achieved using Committed

Information Rate (CIR) provisioning. PIR institutes a limit, or

“ceiling”, of maximum bandwidth to be allocated to a particular customer at any time. CIR, on the other hand, provides a guaranteed minimum, or “floor” throughput even during periods of high congestion. DMX provides support of CIR in R5.0.

PIR

Burstable Bandwidth

CIR

Guaranteed Bandwidth nc-dmx2-032

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 1 3

Ethernet Rate Shaping Services

Applications and Configurations

How it Works

The figure above demonstrates the relationship between CIR and PIR services for a single customer’s bursty data stream. Again, PIR represents the maximum bandwidth a particular customer will be allocated at any time, while CIR is guaranteed minimum bandwidth that insures a constant level of service even during periods of high congestion.

As the figure above suggests, if the maximum bandwidth for a customer (PIR) is exceeded, surplus packets may be dropped. Rate guarantees can be changed in-service and are provisionable at sub-rate levels (1 Mbps).

Policing takes place first in order to ensure that a customer meets the

CIR/PIR stipulations of their contract. The priority queuing relative to other customer’s traffic then occurs providing another QoS capability.

Figure 3-8 Bandwidth Allocation within Ethernet circuit packs

Eth ports

Policing is done here, inside the Ethernet card.

PIR

Policing

Priority

Queues

(WRR)

To Ethernet switch fabric

Discarded non-

Conforming packets nc-dmx2-030

Application advantage

Rate shaping provides the capability to offer a maximum “ceiling” throughput at all times (PIR). It also supports commitments to minimum bandwidth availability (CIR). This combination of CIR and

PIR rate shaping enables DMX to both help service providers meet detailed service level agreements (SLAs) and to ensure adequate capacity for end-users at all times. SLAs also can be offered with sub-rate guarantees. Rate shaping can enable oversubscription with increased revenue potential. Finally, all private line traffic is protected by time-tested SONET layer protection (1+1, UPSR, and BLSR).

3 - 1 4

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Hitless Bandwidth Provisioning with LCAS

Overview

Link Capacity Adjustment Scheme (LCAS) enables in-service (or non-service affecting) bandwidth increases/decreases for Ethernet links.

Description

DMX supports standard LCAS per ITU G.7041. Bandwidth changes to

Ethernet links are done one span at a time. Without LCAS, provisioning a bandwidth change on the first span of a packet ring takes down Ethernet service around the rest of the ring until the entire ring is set to operate at the same capacity.

With LCAS, planned increases and/or decreases of bandwidth are hitless (that is, they do not affect service). As the figure below illustrates, when capacity changes to each span around the packet ring are provisioned, service is not interrupted. While the span between nodes A&B is set to 15 STS-1s, the remaining spans continue to function at 10 STS-1s.

Figure 3-9 Hitless Bandwidth Provisioning: 1st Span

Central Office

TDM

Capacity of span one changed to 15 STS-1s in-service. The rest of the packet ring continues to function.

Metropolis

DMX

15 STS-1s

OC12/48/192

Metropolis

DMX

Ethernet

10 STS-1s

Metropolis

DMX

10 STS-1s

Metropolis

DMX

JK-E-10.eps

Application Advantages

As the global market for communication services is in continuous flux, both advances in technology and changes in state, regional, and national economies exert various pressures on your network.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 1 5

Hitless Bandwidth Provisioning with LCAS

Applications and Configurations

Accordingly, capacity changes to your network are necessary on a regular basis.

LCAS enables you to meet the challenges of today’s market without affecting service. With LCAS, you are not in danger of violating stringent Enterprise customer SLAs. You can also deploy you SONET network according to long-term growth forecasts, and get the most out of the ability to adjust private line and packet ring capacity within your

SONET lines.

3 - 1 6

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Link Aggregation (LNW70 LAN ports)

Overview

DMX supports link aggregation on any two LNW70 LAN ports of the same rate (i.e. 100 or 1000 Mbps), operating in switched mode. In

R7.0, the two ports comprising a LAG must be located on the same pack.

Link aggregation can also provide facility protection on LNW70 LAN ports.

Description

Ordinarily, multiple Ethernet links between two bridges form loops

(unless a spanning tree blocks all but one) so they can’t be used to increase bandwidth. Link Aggregation causes defined groups of links to be treated as a single logical link, making multiple LAN ports appear as one. In this way, Bandwidth may be increased without requiring an upgrade to a higher rate link.

More links than are needed can be added to the group and each is active until it fails (similar to utilizing LCAS protection for SONET tributaries).

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 1 7

Link Aggregation (LNW70 LAN ports)

Applications and Configurations

Link Aggregation Example

The figure below depicts link aggregation on two LNW70 LAN ports functioning at 100Mbps. The top portion of the figure shows two ports receiving separate 100 Mbps inbound flows. The bottom portion depicts the same two flows being equally split across the two outbound ports in the LAG. In this example, no failure has occurred and both ports comprising the LAG are in-service.

Traffic entering incoming ports is aggregated into a LAG. While both ports are in-service, outgoing traffic is split between working ports.

Figure 3-10 Link aggregation at 100 Mbps

(all ports in-service)

Link Aggregation Group (LAG)

100 Mb

Up to

200 Mbps

LNW70

Link Aggregation Group (LAG)

LNW70

100 Mb

200 Mbps per conversation

MA-DMXAPG-044

The instance pictured above represents the ideal case, in which there are at least 2 flows, each a maximum of 100Mbps. In this case they can be equally split over the two ports comprising the LAG. The ability to split the two flows across multiple ports also depends on the distribution of MAC/IP addresses.

Link aggregation employs an algorithm that assigns traffic to member ports to prevent misreading. A given flow can be assigned to only one port and cannot be split across multiple ports in the same LAG. To increase flexibility, DMX allows a flow to be defined by either a MAC source and destination address pair or an IP source and address pair.

The algorithm uses the XOR of the least significant bits of the address pairs to assign a port/link. Therefore, the actual load balancing achieved depends on the distribution of MAC/IP addresses.

3 - 1 8

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Link Aggregation (LNW70 LAN ports)

Applications and Configurations

Application advantage

Link Aggregation provides a means of supporting facility protection and bandwidth increases/decreases on LNW70 LAN ports. Link

Aggregation causes defined groups of links to be treated as a single logical link and removes failed links automatically, thereby enabling bandwidth changes and facility protection on 2 paired links comprising a LAG.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 1 9

Applications and Configurations

Virtual LAN Services

Overview

The Virtual LAN (VLAN) Service application provides a packet-based

Ethernet connection via a shared packet over SONET connection.

Description

VLAN Service applications can be utilized by multiple customers over a shared ring for improved bandwidth efficiency. DMX uses VLANs and allows bandwidth to be shared among customers. Up to 4093

VLANs can be assigned to guarantee privacy among various customers.

Multiple customers can use the VLAN interconnect (multipoint LAN) capability of DMX at multiple sites.

The figure below shows DMX’s varied VLAN capabilities.

Figure 3-11 VLAN Service Application

DMX 100/1000M

Ethernet

Switch/

Router

Switch/

Router

100/1000M

Ethernet

DMX

OC-48/192

DMX

OC-48

CO/Regional

Hub

DMX

ISP

Router

Ethernet

OC-48

DMX

10/100/1000M bps Ethernet

Application

Server

Switch/

Router nc-dmx2-014

Application advantage

DMX Ethernet services extend packet switching from the LAN to the

WAN. In doing so, enterprise interconnect locations in metropolitan areas can transport traffic much more efficiently over shared and/or provisionable access bandwidth. ISP carrier access applications can use spanning tree protection and flexible bandwidth allocation (using

STS-1 virtual concatenation) in the WAN.

3 - 2 0

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Transparent LAN Services

Overview

The enterprise LAN (local area network) interconnect and transport applications provide business-to-business networking of routers and data switches. Transparent LAN service is similar to VLAN service, except that Transparent LANs can be deployed using rate shaping OR on a best effort basis.

Enterprise LAN interconnect (multipoint

Ethernet) description

The multipoint LAN interconnect capability of DMX allows data to be transported across a DMX network from any point to any other point.

Protection is provided via the standard spanning tree algorithm. The

DMX software determines which DMX NE is the “root” of the data network. The data spans out from that DMX NE, enabling the customer to extend its enterprise network into the WAN as a virtual private LAN.

The figure below depicts two high-speed DMX path switched rings transporting data in either a point-to-point or multipoint configuration between DMX clients through multiple nodes and switching points.

Figure 3-12 Transparent LAN Services

Customer 2

Customer 3

Metropolis

DMX

Services:

Point-to-Point

Multi-Point Broadcast

Aggregation

Customer 2

Metropolis

DMX

Customer 1

OC-12/48/192

UPSR or

BLSR

Metropolis

DMX

Customer 3

Customer 1

1GbE

Customer 2

FE = Fast Ethernet (10/100 Mbps)

GbE = Gigabit Ethernet (1000 Mbps)

Metropolis

DMX

1GbE

Customer 1 nc-dmx2-012

Multicast Ethernet Packets

Multicast Ethernet packets/transmission can be used to facilitate certain

Transparent LAN applications. Yet, Transparent LANs can be implemented using a variety of Ethernet cross-connection types. For more information about Ethernet cross-connection types, refer to the

section entitled Cross-connections (5-26).

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 2 1

Transparent LAN Services

Applications and Configurations

“Networking Capabilities” in Chapter 2 of this document.

Application advantage

The Transparent LAN application supports fast, packet-layer protection throughout the WAN, as well as the ability to offer both dedicated and shared bandwidth transport services with improved efficiency and flexible quality of service (QoS).

3 - 2 2

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Best Effort Ethernet Service

Overview

Best effort Ethernet Services is an over-subscription service model that functions without Rate Shaping. Ideal for broadband Internet access within a metro area, Best Effort Ethernet Service enables service providers/carriers to offer an economy-class of service that maximizes revenue potential of a fixed amount of bandwidth.

Description

In the Best Effort service model customers share common bandwidth and are given no quality of service (QoS) or throughput rate guarantees.

Thus best effort applications function without rate shaping services and provide customers with throughput relative to available bandwidth only.

If customers require that their traffic be separated from common network traffic (for security purposes), this can be achieved by VLAN tagging (IEEE 802.1q) or Transparent VLANs (see the sections above).

Traffic in best effort applications may also be prioritized via IEEE

802.1p tags.

Protection in this application is provided by both standard SONET layer switching within the WAN and Rapid Spanning Tree protocol

(IEEE 802.1w) in the Ethernet environment.

Application Advantages

Best effort services are ideal for providing Internet access. This application enables service providers to offer economy-class service facilitated by over-subscribing bandwidth shared by numerous customers. Thus best effort services enable service providers/carriers to maximize the revenue potential of a fixed amount of bandwidth.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 2 3

Applications and Configurations

Ethernet/TDM Access to Frame Relay and/or ATM Service

Overview

The DMX supports business data access applications for a variety of broadband service interfaces. These services can cost-effectively reach remote data aggregation switches at collocated sites and business premises.

Description

In this application, DMX transports DS1, DS3, OC-3, OC-12, and

OC-48 (c) signals from an edge aggregator (Figure 3-13 (3-24)) to the

core switch. It also provides DS1 and DS3 (TDM) low-cost backhaul of frame relay and ATM to the hub multiservice switch. This application also provides 10/100/1000 Mbps Ethernet transport and switching.

Figure 3-13 DMX Providing Access to Frame Relay and/or ATM

Network

METRO

POP

ISP Edge

Switch/Router

FR/ATM

TDM access

LAN

10/100/1000

Mbps and or

TDM

FR/ATM

UNIT

FR/ATM

UNIT

LAN

Ethernet access

Metropolis

DMX

DS1/DS3

GbE Packet Ring

(Flexible nx STS1 statistical pipes) Metropolis

DMX

Application advantage

PVC

FR/ATM

Network

FR/ATM

UNIT nc-dmx2-017

DMX satisfies evolving data service delivery requirements for business customers through its flexible, scalable access network infrastructure, offering a next-generation infrastructure that is stable against the churn of data technology.

DMX simplifies data service delivery by enabling access to existing

ATM and Frame Relay networks through Ethernet and/or TDM interfaces. Thus, traffic originating at Frame Relay or ATM equipment can enter the DMX through a 10/100/1000 Mbps Ethernet or DS1/DS3

TDM interface to be transmitted across SONET networks to its final destination (be it a Frame Relay/ATM based network or an Ethernet

LAN).

3 - 2 4

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Ethernet/TDM Access to IP Network

Overview

DMX provides access to the IP service delivering platforms, which enable such capabilities as virtual routing services, Layer 3 VPNs, firewalling, and IPsec Tunnels. These enhanced IP services allow service providers to offer customers state-of-the-art networking capabilities such as network based VPNs, built-in QoS, bullet-proof security, multi-tenant Internet access, voice/data convergence, and other next generation applications.

Description

While DMX single-handedly enables such things as voice/data convergence, it is important to state that the majority of the services listed above are supported by various IP Services platforms (Lucent’s

Access Point

Routers, and Brick Firewall Family for example). The

DMX, however provides an efficient and crucial link between metro area networks and these IP Services platforms located in the network core.

In the figure below the DMX is hosting an OC-48/192 metro ring connected to an OC-12/48 access ring on one end, and the metro core on the other. On the access ring side, DMX provides a link to CPE sized multiplexers (which are in turn connected to routers or firewalling platforms) or directly to IP routers (over 10/100/1000 Mbps

Ethernet interfaces).

On the other side of the metro ring, the DMX is connected to an IP

Services switch (both TDM and Ethernet interfaces supported by some

IP switches). IP services switches can then provide a range of enhanced

IP services.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 2 5

Ethernet/TDM Access to IP Network

Applications and Configurations

Figure 3-14 DMX providing Ethernet/TDM access to the Internet

802.1q VLAN or Transparent VLAN IP/IP-Sec

MPLS VPN

Main Service Node

Gx550

Class 5

Switch

10/100 Mbps

No Firewall

VLAN

Metropolis

DMX press

LAN traffic over right sized

STS1-xv

Hub

Node

OC-12/48

Access Ring

Metropolis

DMX

Metropolis

DMX press

GbE

VPN Bricks

(Firewall),

SuperPipe

(VPN router)

OC-48/92

Access Ring

Metropolis

DMX

10/100 Mbps and or GbE

IP VPN to the

Internet

FR/ATM

UNIT nc-dmx2-016

Application Advantages

DMX allows service provider’s access networks to support today’s enterprise customer needs with TDM to IP services migration, access to high-security multiservice platforms (i.e. SpringTide

), and efficient aggregation of last-mile voice and data services.

3 - 2 6

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

DMX as an Ethernet Hub using LNW70

Metropolis

DMX

Overview

Description

When DMX is equipped with the LNW70 and used as a metro Ethernet hub, it presents many advantages over other next-generation and non next-generation metro ADMs.

At the metro edge, the Metropolis

Portfolio provides integrated

CPE/MSPP functionality. With Ethernet over SONET (EoS), the

Metropolis

Portfolio supports full- or sub-rate GbE packet rings. It supports Transparent (802.1q) or Stacked VLANs and can provide

802.1w rapid spanning tree restoration (802.1d also supported) whether functioning in Private Line or Packet Ring mode.

Figure 3-15 DMX as an Ethernet Hub

Single DMX for Metro Hub

OC-12/48/192

Metropolis

DMX

Metropolis

DMX

tend

10/100/1000 Mbps

Ethernet, plus TDM

Metropolis

DMX

plore

OC-3/12/48

OC-12/48/192

OC-3/12/48

LNW70

DMX = Metropolis DMX Access Multiplexer

DMX

plore

= Metropolis DMX

plore

Access Multiplexer

DMX

press

= Metropolis

DMX

press

Access Multiplexer

DMX

tend

= Metropolis

DMX

tend

Access Multiplexer

MA-DMX-409

As shown in the figure above, the LNW70 contains enough capacity and external ports to aggregate and transmit 2.5 Gigabits per second of

Ethernet traffic. The integrated packet switch can connect multiple packet rings and/or point-to-point “spokes”. DMX also supports optical/Ethernet hairpinning at full-rate GbE line speed. Finally, with the LNW70, DMX provides optical 100BASE-X and 1000BASE-X, along with electrical 10/100BASE-T and 1000BASE-T ports on one

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 2 7

DMX as an Ethernet Hub using LNW70

Applications and Configurations

card for data traffic aggregation at the metro edge or data traffic hand-off at the metro core.

Application Advantages

DMX provides superior Ethernet aggregation and switch capacity with the LNW70. Each LNW70 supports an industry leading, single circuit pack capacity of 2.5Gbps. It supports both optical 100BASE-X and

1000BASE-X, along with electrical 10/100BASE-T and 1000BASE-T optical ports on the same pack, allowing you to provision the most appropriate and rate-specific data cross-connections for your network.

This helps you to get the most out of your investment in both metro edge and data core NEs.

With an array of Ethernet topologies to choose from, DMX allows you to deploy the most appropriate network for your customers’ needs.

Support of industry standard Private Lines and Packet rings, with both

SONET and spanning tree protection schemes, ensures your ability to interwork with CPE networks and provide your customers with the highest level of reliability possible. R5.1 also makes such billable services as CIR and PIR available in structuring Enterprise SLAs.

Meeting the reliability requirements of stringent SLAs is easier given

R5.1’s support of LCAS, which enables hitless bandwidth provisioning.

DMX provides all of these capabilities within an industry leading TDM

NE that scales from DS1/E1 to OC-192 in the same, compact unit. This makes DMX capable of aggregating both Ethernet and SONET traffic with the highest levels of speed, security, and sophistication possible.

3 - 2 8

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

DMX as an Ethernet Hub using LNW78

Overview

The LNW78 support both RPR and EoS services on a single card. The

LNW78 also supports CoS features on EoS VCGs, including the same classification options for incoming packets, queuing/scheduling capabilities for outgoing packets, and CIR/PIR rate shaping functionality as were previously supported only on 802.3 LAN ports.

This increased functionality allows DMX to offer hybrid

RPR/hub-and-spoke functionality where the LNW78 acts as a point of both aggregation for remote LAN ports (or customer ports) and interconnection, linking remote LAN ports to an RPR ring.

Hybrid hub-and-spoke/RPR interconnect

As the figure below demonstrates, employing the LNW78 at a hub node enables DMX to support hub-and-spoke configurations similar to the hubbing application using the LNW70 described in the previous section. As the LNW78 also supports RPR, it can aggregate remote

LAN ports and connect their traffic to an RPR ring.

Figure 3-16 Hybrid hub-and-spoke/RPR interconnect with LNW78

SONET

6 Eos VCG

With Rate Controls

Metropolis

DMX

plore

VLNC15

Metropolis

DMX

plore

VLNC15

LNW78

RPR Port Unit

RPR Ring

RPR VCG

LNW78

RPR Port Unit

RPR VCG

LNW78

RPR Port Unit

Metropolis

DMX

LNW70

LNW78

RPR Port Unit

Metropolis

DMX

tend

LNW74

Metropolis

DMX

tend

LNW74

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 2 9

DMX as an Ethernet Hub using LNW78

Ne-local LAN port aggregation/interconnect

Applications and Configurations

The NE-local LAN ports aggregation/interconnect configuration below functions similar to the application described above except that the connections to Ethernet pack(s) providing LAN ports is via backplane hairpin(s).

The figure below shows more benefits enabled by EoS functionality on the LNW78. Both private lines dropped from an optical ring and local

Ethernet LAN ports (LNW70 and LNW74 in the figure below) can be hairpinned through the shelf backplane and added to the RPR ring. If a shelf is equipped with both LNW70 and LNW78 packs, the Ethernet switch on the LNW70 can be used to aggregate traffic from multiple ports into a single point-to-point connection to an LNW78 EoS VCG.

Figure 3-17 DMX as an Ethernet Hub

MAIN MAIN

Aggregated Traffic

From a SW Port Card

RPR VCG

EoS VCG

OC-3/12/48

LNW78 LNW74 LNW70

Local LNW78 Ports

Remote Private Line via

Optical Ring

OC-n

Local 10/100

Ports

Local 100/1000

Mbps Ports

Additional Local LAN

Ports to RPR

MA-DMXAPG-050

Application Advantages

This application allows lower cost edge ports that may not have the sophistication of DMX’s Ethernet capabilities to be rate controlled with

CIR/PIR rate shaping. It also provides that added benefit of RPR/LAN port interconnect without requiring the use of physical LAN ports, additional Ethernet circuit packs, PTMs (SFPs), and associated cabling and craft personnel time needed to establish the interconnect.

3 - 3 0

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Ethernet Transport via RPR

Overview

DMX supports Resilient Packet Ring (RPR) Ethernet transport compliant with IEEE 802.17. RPR is intended to optimize

Ethernet-based metro ring networks for packet transport with resiliency equivalent to that of SONET rings. It could be used to carry voice and

TDM traffic with the QoS of SONET and ATM combined, while supporting LAN traffic with the efficiency of Ethernet. It also employs a fairness algorithm to allow equal access to opportunistic bandwidth regardless of a node’s position around the ring. RPR is a useful alternative to Ethernet over Fiber for carriers, cable operators, large enterprise networks, and municipal utilities-owned networks.

Bridging in RPR

DMX’s RPR implementation uses enhanced Ethernet bridging as well as basic Ethernet bridging. As shown in the figure below, basic bridging is much different than enhanced bridging. Chief among their differences is that enhanced bridging allows for spatial reuse, meaning that other nodes around the ring can reuse opportunistic bandwidth.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 3 1

Ethernet Transport via RPR

Applications and Configurations

Basic Bridging

With basic bridging (side “a” of the figure below), packets that originate at any node on the ring are flooded. Flooding means they are sent to every node around the ring, regardless of their destination. With basic bridging, all nodes see all packets, making it a simple form of reliable transport. The downside of flooding packets with basic bridging is that it negates the possibility of spatial reuse, one of the great benefits of RPR.

Figure 3-18 Basic vs. Enhanced Bridging

1 1

Y Y

8 2 8 2

3 7

6 4

Basic with Unidirectional Flooding

6 4

Enhanced with Spatial Reuse

MA-DMXplore-061

Enhanced Bridging

Enhanced bridging is a more efficient form of RPR transport that allows for the possibility of spatial reuse. As shown in side “b” of the figure above, enhanced bridging allows the nodes to learn the location of the node to which the destination address belongs. All subsequent transmissions for that data stream are unicast by the shortest path. This means that packets are not flooded around the ring, but are sent directly to the destination node. This leaves the unused bandwidth around the rest of the ring open for additional traffic.

3 - 3 2

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Ethernet Transport via RPR

Applications and Configurations

Steering Protection

DMX uses steering protection to recover from failures in RPR. As shown in the figure below, all the nodes around the RPR ring learn of a failure through topology messaging. The nodes then redirect transmission to reach destination addresses. RPR steering provides <50 msec recovery time (similar to SONET) and is revertive.

Steering with Enhanced Bridging

The figure below depicts steering protection as it would function with

Enhanced RPR bridging. Again, with enhanced bridging all nodes learn the location to which the destination address belongs and transmit packets one-way (unicast), directly toward the destination node. If packets are originating at node “x” and their destination is node “y”, and a failure occurs in the shortest path, the “x” node will perform the steering function to send packets back around the ring in the other direction. With enhanced bridging, the post-failure transmissions will also be unicast.

Figure 3-19 Steering Protection with Enhanced Bridging

Enhanced Bridging

1 1

Y Y

8 2 8 2

Before Steering

3 7

After Steering

MA-DMXplore-063

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 3 3

Ethernet Transport via RPR

Applications and Configurations

Steering with Basic Bridging

The figure below depicts steering protection with basic bridging. Basic bridging functions using unidirectional flooding (see the graphic on the left of the figure below). If the RPR ring is set to use basic bridging with unidirectional flooding, steering will force it into bidirectional flooding as pictured on the right side of the figure below.

Figure 3-20 Steering Protection with Basic Bridging

Basic Bridging

1 1

Y Y

8 2 8 2

3 7

6 4

Before Steering

(Unidirectional Flooding)

Cleave point - Based on

Failed Span

After Steering

(Bidirectional Flooding)

MA-DMXplore-064

As is the case with enhanced bridging, steering directs traffic away from the failure point. With basic bridging, the steering function will change the cleave point in the RPR ring to the point of failure. All traffic will still be broadcast in both directions, around the entire ring.

3 - 3 4

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Ethernet Transport via RPR

Applications and Configurations

Fairness and Spatial reuse Spatial Reuse

RPR provides support for spatial reuse, whereby unused bandwidth around the ring can be used to facilitate transport of additional traffic.

Spatial reuse is supported only in enhanced bridging scenarios where the unused portion of the ring is left open to additional traffic (See

Basic vs. Enhanced Bridging

With enhanced bridging (as in Figure 3-18), Node 1 can transmit traffic

to Node 2 at the full ring rate, while Node 2 can transmit traffic to Node

3 at the full ring rate. The same capability is enabled at the other nodes around the ring because the traffic originating at each node stops at its destination node.

Fairness

Fairness is accomplished by way of an algorithm that functionally throttles the access to this unused bandwidth at each node around the ring in an effort to provide equal access for all best-effort traffic.

Fairness allows best-effort users (Class C users, or Class B users that are transmitting traffic at a rate higher than their specified CIR) equal access to any available, unreserved bandwidth. Bandwidth reserved for

Class A users can’t be used by any other class. The unreserved bandwidth is the difference between the maximum ring rate and the reserved bandwidth (what is left over). The fairness algorithm then prevents any one node from having greater access to unreserved bandwidth than the other nodes around the ring.

Figure 3-21 Fairness in RPR

250 Mb

200 Mb

700 Mb available

6 4

300 Mb

(offered)

Initial Condition

300 Mb

(offered)

Steady State

MA-DMXplore-066

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 3 5

Ethernet Transport via RPR

Applications and Configurations

The figure above depicts a typical RPR ring where a total of 700 Mbps is unreserved. If there is only one best-effort user on the ring, that user can send a maximum of 700 Mbps. If there is another best-effort user at another node transmitting traffic, the first node is throttled back to allow the second equal access to bandwidth.

On the left side of the figure above, both Node 5 and 6 have 300 Mb to transmit to Node 8. If they were the only best-effort users on the ring transmitting traffic at this time, there would be no problem. Yet, Node 7 is also trying to transmit 200 Mb of traffic to Node 1. Initially, because there is already 600 Mb of traffic (from Nodes 5 and 6) in route, Node 7 can only get 100 Mb of traffic through to Node 1.

As a result, it sends a message to Node 6 (shown as the black arrows inside the ring), informing it that it can only send 100 Mb of its total payload. Node 6 immediately reduces its transmit rate to 100 Mbps and sends a similar fairness message to Node 5. Node 5 then responds in a similar fashion to Node 6.

With this feedback control system, the transmit rates and fairness messages adjust to converge on a steady state average of 250 Mb for

Nodes 5 and 6, and 200 Mb for Node 7. The reason that the rates aren’t all equal is because Node 7 only needs to send 200 Mb to start with.

In this example fairness ensures that all nodes with best-effort users share unreserved bandwidth equally. Node 7 is allowed to transmit its entire payload only because the capacity is less than the capacity that can be allocated to each of the other two nodes hosting best-effort users.

3 - 3 6

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Ethernet Transport via RPR

Applications and Configurations

RPR interconnect with

LNW78 EoS functionality

The figure below shows two RPR rings connected via an EoS link. The rings are linked together through EoS VCGs LNW78 located on different shelves. The Eos ports on the LNW78(s) connect the Ethernet switches located on the packs, thereby providing a bridge between the two RPR rings. This eliminates the need to use physical LAN ports, additional Ethernet circuit packs, PTMs (SFPs), and associated cabling to establish the interconnect. On each shelf shown below traffic is mapped to EoS ports. The EoS ports are then connected to an optical interface, in this case, via a hairpin connection. The two shelves are connected by an optical ring (or 1+1). Ethernet traffic can now flow between RPR rings.

Figure 3-22 RPR Packet Ring interconnect via EOS VCG with

LNW78 (multi-node interconnect)

RPR Ring 1

Metropolis

DMX

LNW78

Metropolis

DMX

LNW78

OC-n

LNW78

Metropolis

DMX

LNW78

Local Hairpin – LNW78 to

Optical Port Unit

OC-n

Optical Shelf

Interconnect

Local Hairpin – LNW78 to

Optical Port Unit

LNW78

Metropolis

DMX

LNW78

OC-n

Metropolis

DMX

LNW78

Metropolis

DMX

LNW78

RPR Ring 2

MA-DMXAPG-051

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 3 7

Ethernet Transport via RPR

Applications and Configurations

Metropolis

DMX

LNW78

As the figure below shows, the link between the two rings can be established using LNW78s located on the same shelf. In this example, the two RPR rings reside on a single shelf. As in the multi-NE shelf example, Ethernet traffic is mapped to EoS ports. The difference in this figure is that the EoS ports on each card are connected to each other via an internal hairpin.

Figure 3-23 RPR Packet Ring interconnect via EOS VCG with

LNW78 (single-node interconnect)

RPR Ring 1

Metropolis

DMX

LNW78

OC-n

LNW78

Local Hairpin –

LNW78 to LNW78

Metropolis

DMX

LNW78

Metropolis

DMX

LNW78

OC-n

Metropolis

DMX

LNW78

RPR Ring 2

DMX = Metropolis DMX Access Multiplexer

MA-DMXAPG-052

RPR ring interconnect via EoS connects multiple rings without making them the same ring. This is advantageous because all functions of the rings remain separate, including node-based bandwidth allocation around the RPR as governed by the fairness algorithm.

3 - 3 8

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Ethernet Transport via RPR

Applications and Configurations

Application Advantages

RPR can offer the following advantages over Ethernet over Fiber and

SONET transport for data traffic.

• Optimizes SONET rings for Ethernet transport with <50 msec restoration.

• Could be used to transport voice, TDM, and data traffic with the efficiency of Ethernet

• RPR offers efficient allocation of SONET timeslots for leased line data services.

• RPR can be oversubscribed, with equal access to opportunistic bandwidth.

• Best-effort classes of service use opportunistic, unreserved bandwidth. RPR does not reserve protection bandwidth. It doesn’t have unused links as with the Spanning Tree protocol.

• Enhanced bridging only uses the direct path between source and destination, allowing for spatial reuse.

• RPR supports a fairness algorithm used to distribute access to opportunistic bandwidth around the ring. Even when two RPR rings are connected via EoS VCGs on the LNW78, all ring functionality remains separate. This allows fairness to function independently relative to each ring.

• RPR supports 3 classes of service:

– Class A: CIR= PIR (used for voice, video, and circuit emulation)

– Class B: CIR and PIR (guaranteed bandwidth, everything above the CIR and below the PIR has best-effort, fairness controlled access to opportunistic bandwidth)

– Class C: CIR=0 (all traffic is best-effort, fairness controlled)

• CoS functionality on EoS VCGs extends the same classification options for incoming packets, queuing/scheduling capabilities for outgoing packets, and CIR/PIR rate shaping functionality as were previously supported only on 802.3 LAN ports. Therefore traffic originating on low-cost remote LAN/customer ports that may not have the advanced Ethernet capabilities of DMX can be managed with QoS support available on EoS VCGs.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 3 9

Applications and Configurations

SAN Distance Extensions with DMX

Overview

Description

With today’s increasing regulations and heightened concern with

Business Continuity and Disaster Recovery, both large and small businesses must consider alternate storage architectures for distance extensions. DMX can provide a ubiquitous, flexible, highly reliable platform for both TDM and data-based transport, including voice, DSn private line, Ethernet, and storage (SAN) traffic.

When SAN deployments began in corporations and colleges, it was to serve the needs of various, unique departments within a larger organization. The resulting situation, depicted in the figure below, is one of multiple SAN Islands made up of disparate technology with various management and transport requirements.

Figure 3-24 SAN Islands Today

There are three options available to connect SAN islands: IP, WDM, and SONET. IP is attractive due to its high availability, but it is non-deterministic and prone to packet loss. This makes IP incapable of providing both the capacity and reliability necessitated by enterprise requirements. WDM is not widely available for enterprises today, but is a good choice for large data center connectivity and those enterprises that require many storage ports.

SONET, on the other hand, is ubiquitously available and accepted as a data transport platform by business customers. It provides the most attractive balance of QoS and capacity for small to large-sized

Enterprises running both synchronous (disk mirroring) and asynchronous (data replication/backup) applications. With new technology such as GFP, VCAT, and LCAS, SAN over SONET enables simple deployment and traffic engineering for carriers, while ensuring efficient transport by way of low overhead byte count and flexible framing. Due to SONET’s advanced protection capabilities it can guarantee little or no packet loss for SAN transport. Plus, given

3 - 4 0

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

SAN Distance Extensions with DMX

Applications and Configurations

Ethernet’s incorporation into SONET platforms, SAN management can be easily centralized and performed over IP. For reliability, capacity, and ease of deployment/management SONET is the clear choice when considering the creation of corporate and campus SAN extensions.

Application Advantages

In addition to GFP, VCAT, and LCAS, Metropolis DMX products incorporate a full array of SAN interfaces on a single card to enable efficient SAN transport over SONET. The DMX SAN card uses PTM

(Pluggable Transmission Module) optics, also known as SFP optics, to provide FICON, ESCON, and Fibre-channel interfaces. The same card can be used on both the Metropolis DMX and DMXtend, enabling rollout of new services from the metro core to edge, where and when they are requested. It can be equipped with four 200Mbps ESCON ports or four 1Gbs, two 2Gbs, or a mix of one 2Gbs and two 1Gbs

FICON/FC ports. The Metropolis SAN implementation offers standards-based buffer-to-buffer credit management for long distance operations, sub-rate allocation of asynchronous FC traffic, and provisionable bandwidth levels.

The Metropolis DMX and DMXtend are the ideal platforms for

SAN/SONET connectivity. They can easily connect various enterprise

SAN islands no matter what protocol is used. The figure below is a network view of multiple SANs connected within the same building or business park, across a region and nation-wide.

Figure 3-25 Metropolis

DMX Product Family SAN Transport

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 4 1

Applications and Configurations

Converged Service Delivery via Metropolis

DMX Product Family

Overview

Description

Modern Ethernet/SONET MSPPs like DMX have made it simple for a single provider to offer voice, data, and video on a common, easy-to-manage platform. The hybrid Ethernet/SONET nature of DMX has made it an integral part of the top Service Provider (SP) networks moving toward converged offerings. In addition to convergence, there are a host of new service opportunities that demand intelligent access solutions. These include services like Storage Area Network (SAN) distance extensions, secure VPNs, and VoIP; all of which are receiving great attention from industry media and promise high market demand in the future.

The Metropolis

DMX, DMXplore and DMXtend offer high bandwidth optical access at the OC-3/12/48 level in conjunction with

DS1/3 interfaces for voice traffic, Fast Ethernet (10/100 Mbps) and

Gigabit Ethernet (1000Mbps) for integrated data transport, and on

DMX and DMXtend, native SAN interfaces

(FICON/ESCON/Fibre-Channel) all in one compact, low-cost unit.

These characteristics make the DMX family ideal next-generation converged platforms for their ability to address the concerns of both

SPs and end-users alike.

Figure 3-26 Metropolis

DMX Family Providing Converged

Service

Metropolis DMX/ DMX

tend/

DMX

plore

DS1/DS3

Voice

10/100/

1000 Mbps

Ethernet

SAN

FICON/

ESCON/FC

SONET

OC-3/12/48

Voice

DATA/

Ethernet

SAN

OC-3/12/48/192 high-speed lines provide connections with enough bandwidth to service even very high-bandwidth FTTB and FTTH applications. The rich feature set of the Metropolis

DMX family includes support of Ethernet QoS protocols that rival offerings from other industry vendors and, combined with the legendary reliability of

3 - 4 2

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Converged Service Delivery via Metropolis® DMX Product Family

Applications and Configurations

SONET, provides an extremely resilient platform ensuring low-latency and fast restoration in the event of failures. Finally, because the

Metropolis

DMX Family is SONET-based and provides fully integrated interfaces for data transport, they can enable SPs and

Enterprises alike to preserve their investment in existing network assets.

Application Advantages

With a metro platform that provides integrated multi-service access,

Enterprises can continue to employ their entire data infrastructure, simply connecting to the DMX/DMXplore/DMXtend at the point of transport. In addition to protecting their existing investments in hardware, this approach also enables the continued use of platforms and procedures used to manage their internal LAN. On the SP side, integrated access amounts to enabling converged service offerings with similar advantages. SPs can deliver more revenue generating services without the use of multiple CPEs/CO access devices. This is both an attractive prospect for enterprises, and allows SPs to keep OPEX under control. As SONET-based platforms, the Metropolis

DMX Family can interoperate with SP management systems and be easily integrated into their network.

Across the board, industry analysts agree that OPEX and CAPEX reductions are the compelling force for upgrading to next-generation network elements. And with a small footprint, great scalability, and fully integrated multi-service interfaces, DMXplore and DMXtend simultaneously make the case for a next-generation CPE and fulfill the need.

Figure 3-27 Metropolis

DMX Family Converged Service

Application

DMX

plore

10/100 Mbps and/or

TDM

METRO

CO/POP

DMX

plore

OC-3/12

1+1/

UPSR

Metropolis

DMX

tend

OC-3/12/48

UPSR/ 1+1

Metropolis

DMX

plore

= Metropolis

DMX

plore

Access Multiplexer

DMX = Metropolis DMX Access Multiplexer

DMX

tend

= Metropolis

DMX

tend

Access Multiplexer

MA-DMXplore-019

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 4 3

Applications and Configurations

DSLAM Access

Overview

The DMX provides a cost-effective aggregation and transport vehicle for digital subscriber line (DSL) or remote digital subscriber line access multiplexer (DSLAM) gateways.

Description

Application advantage

In the figure below DMX is located at a central office where it collects

DS3 and/or OC-3/OC-12/GbE signals from multiple DSLAMs, multiplexes them to the OC-48/192 line rate, and sends them out on the

OC-48/192 ring for back-haul to centrally located ATM switches that can be used more cost-effectively than distributed ATM switches.

Figure 3-28 DSLAM Application

DSLAM

DS3, OC-3,

OC-12 (A

TM)

DS3, OC-3,

OC-12 (ATM)

DSLAM

(Ether

Edge POP

Metropolis

DMX

Metropolis

DMX

OC-48/OC-192 UPSR

Voice

Switch

Data Hub

Metropolis

DMX

DS3,

OC-3/12

(high-fill)

Core

Switch

DS3,

OC-3

(low-fill)

Edge

Switch

OC-12

DSI/

Voice

Multiservice

DSLAM

DS3, OC-3,

OC-12 (ATM)

DSLAM nc-dmx-012

A DMX offers a cost-effective, scalable access network infrastructure for DSL access transport.

3 - 4 4

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

TransMUX Functionality with LNW18/20

Overview

The DMX provides a cost-effective/ bandwidth preserving aggregation and transport vehicle for DS1 signals. Using the LNW18 (12 ports) or

LNW20 (48 ports), DMX can combine multiple DS1 signals into a channelized DS3 for more efficient transport through/to the core network.

Description

In the figure below DMX is pictured collecting multiple DS1s around the UPSR and, in the node at the far right of the figure, transmitting them within a channelized DS3 signal back to the core network. This

TransMUX capability is provided by the TransMUX circuit packs located in the DMX at the far right of the picture.

Figure 3-29 TransMUX Application

7 DS1s on

STS-1 #1 to IEC

Metropolis

DMX

Metropolis

DMX

OC48/192

UPSR

Metropolis

DMX

1 DS3 to IEC

Transmux CPs are only required here

10 DS1s on

STS-1 #2 to IEC

Metropolis

DMX

10 DS1s on

STS-1 #3 to IEC nc-dmx2-035

Application advantage

TransMUX functionality enables the DMX to:

• Groom DS1s for channelized DS3s

• Eliminate the need for separate M-13 MUXs at the DS1 aggregation site

• Pack DS3s with multiple DS1s to use bandwidth back to the network core most efficiently

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 4 5

Applications and Configurations

Enhanced TransMUX Functionality with LNW20

Overview

The LNW20 enhances DMX TransMUX functionality by increasing capacity and supporting new configurations. LNW20 provides 48 ports supporting DS3, EC1, and TMUX services provisionable on a port-by-port basis. Each port can be individually provisioned as DS3 or

EC1 (unchannelized), or as TransMUX (channelized DS3s). With the

LNW20, one high-density pack can be used for all DS3, EC1, and/or

TransMUX applications.

Description

The figure below shows the various capabilities of the LNW20. Notice that the brackets and text at the right of the figure differentiate between legacy features and new capabilities enabled only by the LNW20.

Figure 3-30 LNW20 Capabilities

DS-3

EC-1

(VT1.5/DS-1)

EC-1

(VT1.5/DS-1)

STS-1(VT1.5/DS-1)

STS-1(DS-3/DS-1)

STS-1(VT1.5)

LNW18 TMUX

LNW16/LNW19

Existing

Capability

STS-1(DS-3/DS-1)

Added

Functionality via LNW20

External Internal

STS-1(VT1.5/DS-1)

STS-1 OC-n Main

STS-1 to OC-n Hairpin

STS-1 Main Fabric

VT1.5 to DS-1 Drop

VT1.5 Groomed to Multiple Interfaces

Portless

Transmux

MA-DMXAPG-054

Before the LNW20 was introduced, DMX could support TransMUX functionality on DS3 signals using the LNW18. It could also support

EC-1 signals using the LNW16/19/19B.

3 - 4 6

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Enhanced TransMUX Functionality with LNW20

Applications and Configurations

With the LNW20, DMX can support DS3, EC-1 TransMUX using a single card. As the figure shows, it also supports a portless mode that supports TransMUX functionality without using any of the physical interfaces on the pack (for those ports in portless mode that is).

When operating in portless mode, LNW20 pulls DS1s from channelized DS3 signals that enter DMX on a SONET STS-1 interface on another pack (at least one side of the cross-connect is OCn/EC1) and converts them to VT mapped STS-1s. This VT-mapped STS-1 is cross-connected at the VT level in the Main packs to any interface that supports the signal structure today (DS1, channelized DS3, EC1, optical).

Application advantage

Enhanced TransMUX functionality with the LNW20 enables DMX to:

• Upgrade density for TransMUX to 48 ports per pack

• Support DS3, EC-1 and TransMUX on a single pack

• Portless functionality allows DMX to cross-connect any channelized DS3 entering the shelf to any port that accepts

VT-mapped STS-1s without using the electrical interfaces on the

LNW20 itself.

• Groom DS1s for channelized DS3s

• Eliminate the need for separate M-13 MUXs at the DS1 aggregation site

• Pack DS3s with multiple DS1s to use bandwidth back to the network core most efficiently

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 4 7

Applications and Configurations

Network Configurations

Overview

Purpose

DMX provides the flexibility required for operation in today’s changing telecommunications networks. With topology and capacity upgrades, a DMX network can be installed with minimum first cost and then easily grown to add new sites and services.

Network flexibility

The following sections describe some of the network topologies in which DMX can be used. Many other combinations of these network configurations can be used to meet specific network and fiber topologies.

3 - 4 8

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Overview

Contents

Applications and Configurations

Network topologies discussed in this section include:

Increased Span Length: External DWDM Optical Amplifiers

(OAs)

Dual Node Ring Interworking

Single and Dual-Homing

Hairpinning

Linear Optical Extensions

Hubbing

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 4 9

Applications and Configurations

Path Switched Rings

Overview

This section describes the unidirectional path switched ring configuration available with the DMX.

Purpose of path switched rings

The need to prevent service outage caused by network failure has created path switched ring applications. The path switched rings configuration provided by DMX is a self-healing network that automatically protects against service outages caused by cable cuts and equipment failures, which in turn protects customer traffic and increases revenue opportunity.

DMX path switched rings operate in an easily-managed, integrated, single-ended fashion. Restoration is fast and reliable. Complex network-level coordination is not necessary to restore traffic.

Furthermore, bandwidth administration and network reconfigurations

(for example, adding or deleting nodes) are simple because path switching does not require special time slot assignment rules.

Typical path switched ring application

A network that requires the majority of its traffic to be dropped at a single node is an ideal application for path switched rings. A typical access network, where most traffic is between the customer locations and a point-of-presence (POP) or end office, fits this mold. Such an application calls for reliable delivery between customers and POPs. In cases where a mixture of wideband and broadband services is required, a DMX path switched ring is ideal.

OC-3/12/48/192 path switched rings

The OC-12/48/192 path switched ring allows several remote sites to share the two-fiber ring facility back to the CO. DMX interfaces to the ring through the Main slots at the OC-12/48/192 rate and uses its programmable VT1.5/STS-1/STS-3c/STS-12c/STS-48c cross-connect capability. Path switching can be done on VT1.5, STS-1, STS-3c,

STS-12c, or STS-48c paths, or a mixture of these, and all can be added/dropped from the DMX path switched ring at any node. Using the ring’s path protection scheme, time slots are reserved all the way around the ring. Cross-connections offer full flexibility in assigning signals between low-speed ports and the high-speed interface at each node. DMX can easily adapt to unpredicted growth at a ring node.

OC-3/12/48 UPSRs are supported on the low speed (tributary) interfaces with the same characteristics as the high speed UPSRs

3 - 5 0

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Path Switched Rings

Applications and Configurations

described above. DMX supports path switching on STS-1, STS-3c,

STS-12c, STS-48c, and VT1.5 paths only.

Ring topology

The ring topology routes traffic between a CO site and a set of remote sites, or between multiple COs, while providing complete protection. In addition, only two OLIUs are needed per DMX, which provides a cost savings. Traffic can also be routed between remote nodes. The ring can start with as few as two nodes and grow to support many nodes through in-service node additions.

For protection against a CO failure, it may be desirable to include a second CO node in the ring. DMX’s support for dual homing architectures allows all services to be routed to the alternate CO while the first CO is out of service.

Operation

The DMX OC-3/12/48/192 path switched ring operates as shown in

Figure 3-31 (3-52). Traffic entering a path switched ring node is sent

onto both rotations of the ring. At the receiving node, the signal having the highest integrity (based on SONET path information) is selected and dropped as outgoing traffic. At intermediate nodes, the traffic is

“passed-through” without changing the SONET path information. The

DMX VT1.5/STS-1/STS-3c/STS-12c/STS-48c cross-connect capabilities make the provisioning of add/drop and pass-through traffic quick and easy.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 5 1

Path Switched Rings

Applications and Configurations

The self-healing nature of the path switched ring is shown in Figure

3-31 (3-52) (b). In this case, the fiber failure between nodes C and D

causes node C to switch from the counterclockwise ring to the clockwise ring, thus maintaining service between all nodes on the ring.

Figure 3-31 Path Switched Rings

AC CA AC CA

Node A

Node D Node B

Node C

Node A

Node D Node B

Node C

Switch

Made

AC CA AC CA nc-dmx2-028

Configuration advantage

Path switched rings are the industry standard for self-healing networks, providing reliable transport for access networks while accommodating almost any type of application.

3 - 5 2

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

2-Fiber BLSRs

Overview

Traffic capacity

A 2-fiber bidirectional line-switched ring (BLSR) is a self-healing ring configuration in which bidirectional traffic travels over the same set of nodes in each direction. Bidirectional switching makes use of redundant (protection) bandwidth on the bidirectional lines that interconnect the nodes in the ring to provide protection for traffic carried on the working bandwidth. Because the traffic is bidirectional, a single circuit does not necessarily consume bandwidth on every span in the ring. This leaves the spans between other nodes available for additional traffic. Therefore, with distributed switching patterns, a

BLSR can carry more traffic than the same facilities could carry if configured for a unidirectional path-switched ring.

The DMX supports one high-speed OC-48 2-fiber BLSR or two high-speed OC-192 2-fiber BLSR and 14 low-speed OC-48 BLSRs. In the latter application, the low-speed OC-48 BLSR(s) is hosted by

OC-48 circuit packs housed in the Function slots and can add and drop traffic with the high-speed OC-192/48 circuit packs housed in the Main slots. Low-speed OC-48 BLSRs can also add and drop traffic with interfaces in other tributary (low-speed) slots (includes both Function

Units and Growth slots).

The following figure shows working and protection traffic capacities in an OC-192 2-fiber BLSR. The OC-48 2-fiber BLSR operates in the same way, but has 48 STS-1 timeslots in each direction, 24 for working traffic and 24 for protection.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 5 3

2-Fiber BLSRs

Applications and Configurations

Figure 3-32 Traffic Capacity in an OC-192 2-Fiber BLSR

Working 1

Protection 2

Working 2

Fiber 1

Timeslots 1-96

Timeslots 97-192

Protection 1

Timeslots 97-192

Fiber 2

Metropolis

DMX

Metropolis

DMX

Protection 2

Working 1

Protection 1

Working 2

Fiber 2

Timeslots 97-192

Timeslots 1-96

Timeslots 97-192

Timeslots 1-96

Fiber 1 nc-dmx-109

Self-healing rings

DMX 2-fiber BLSRs are self-healing in that transport is automatically restored after node or fiber failures. Each OC-192 line carries 96 STS-1 equivalent timeslots of working capacity plus 96 STS-1 equivalent timeslots of protection capacity. Each OC-48 line carries 24 STS-1 equivalent timeslots of working capacity plus 24 STS-1 equivalent timeslots of protection capacity. In the event of a fiber or node failure, service is restored by switching traffic from the working capacity of the failed line to the protection capacity in the opposite direction around the ring (see the figure below and the figure on the following page.). In the event of a node failure, traffic added and dropped from the failed node is not protected by line switching.

3 - 5 4

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

2-Fiber BLSRs

Applications and Configurations

2-fiber BLSR traffic flow

The figure below shows normal (non-protection-switched) traffic flow on a 2-fiber BLSR.

Figure 3-33 Normal Traffic Flow in a 2-Fiber BLSR

Working 1

Protection 2

Working 2

Protection 1

Node B

DMX

Node A Node C

DMX DMX

DMX

Node E

DMX

Node D

Protection switching

When a line failure triggers a protection switch, the nodes adjacent to the failure switch traffic on to protection capacity. Traffic heading toward the failure is looped back on to the protection capacity traveling away from the failure to reach its destination by traveling the opposite way around the ring (see the figure below). Service is reestablished on the protection capacity in

≤

50 milliseconds after detection of the failure

(for catastrophic failures in rings without existing protection switches or extra traffic).

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 5 5

2-Fiber BLSRs

Applications and Configurations

Fiber cut example

The figure below illustrates a 2-fiber BLSR protection switch that results from a fiber cut.

Figure 3-34 Loopback Protection Switch in a 2-Fiber BLSR

Working 1

Protection 2

Working 2

Protection 1

Node B

DMX

Node A Node C

DMX DMX

Protection traffic flow

DMX

Node E

DMX

Node D

Fiber Cut nc-dmx-113

In the figure above, traffic going from Node A to Node C that normally passes through Node E and Node D on “working 2” capacity is switched at Node E on to the “protection 2” capacity of the line leaving

Node E in the direction of Node A. The traffic passes through Nodes A,

B, and C on the protection bandwidth to Node D where it is looped back to Node C. Similarly, traffic going from Node C to Node A that normally passes through Node D and Node E on “working 1” capacity is switched at Node D on to the “protection 1” capacity of the line leaving Node D in the direction of Node C. The traffic passes through

Nodes C, B, and A on the protection bandwidth to Node E where it is looped back to Node A. Note that only the nodes adjacent to the failure perform loopback protection switches. The same approach is used for a node failure. For example, if Node D fails, Nodes C and E perform loopback protection switches to provide an alternate route for ring traffic. However, traffic that is added and dropped at the failed node,

Node D, cannot be protected by ring switching and is therefore squelched at the switching nodes.

3 - 5 6

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Packet Rings

Overview

Packet Ring configurations provide business-to-business networking of routers and data switches using Ethernet transport over a reliable, low-cost multiservice network. The DMX provides the unique capability for a packet ring to span multiple ring topologies. As shown in the figure below packet rings hosted by the DMX can span multiple

OC-192, OC-48, OC-12, OC-3 ring configurations (UPSRs or BLSRs).

Additionally, packet rings hosted by the DMX can reach into areas serviced by dual and single-homed ring extensions (see the figure below).

Ethernet over SONET

A Packet Ring is a set of packet switches connected in a ring topology that use the inherent redundancy of the ring configuration to provide durability and fast restoration in the event of failures.

Packet rings can be used with or without SONET layer protection. At the packet layer, the rapid spanning tree protocol (as defined in IEEE

802.1) is used to provide protection.

Figure 3-35 Packet Rings

DMX

100/1000M

Ethernet

Switch/

Router

Switch/

Router

100/1000M

Ethernet

DMX

OC-48/192

DMX

OC-48

CO/Regional

Hub

DMX

ISP

Router

Ethernet

OC-48

DMX

10/100/1000M bps Ethernet

Application

Server

Switch/

Router

DMX = Metropolis DMX Access Multiplexer nc-dmx2-014

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 5 7

Packet Rings

Applications and Configurations

DMX uses standard Generic Framing Procedure (GFP) encapsulation

(ITU G.7041) for Ethernet over SONET mapping. Packet rings provide efficient aggregation and transport for Ethernet traffic. DMX’s virtual concatenation capability (ITU G.707) provides flexible bandwidth granularity in the wide area network (WAN), which can grow with your service demand.

Packet Rings over a BLSR

DMX allows the manual provisioning of non-preemptable unprotected traffic (NUT) for multi-point Ethernet cross-connections that originate on low-speed (tributary) interfaces and share bandwidth on the high-speed (Network side) BLSR ring.

When using multi-point cross-connections through a BLSR, packets do not receive standard BLSR protection due to the necessary functioning of NUT. Yet, protection on all data packets is provided for with rapid spanning tree protocol (IEEE 803.1w).

Packet Ring Capacity

DMX supports the following number of packet rings per Ethernet interface circuit pack:

• 1 packet ring on each 10/100 Mbps Fast Ethernet circuit pack

(LNW66, LNW71, and LNW74)

• 2 packet rings on each 1000 Mbps GbE circuit pack (LNW67 and

LNW68)

• 16 packet rings on each 10/100/1000 Mbps GbE circuit pack

(LNW70)

• 2 packet rings on each RPR circuit pack (LNW78)

Specific Applications

Supported

DMX supports the following enterprise LAN (local area network) interconnect and transport applications:

• Ethernet Private Line

• Ethernet Rate Shaping Services

• Virtual LAN Services

• Transparent LAN Services

• Best Effort Service

• Ethernet/TDM Access to Frame Relay or ATM Network

• Ethernet/TDM Access to IP Network

• DSLAM Access

Each of these packet ring applications are detailed in the “Service

Applications” section of this chapter.

3 - 5 8

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

DWDM Optics

Overview

Metropolis

DMX Access Multiplexer supports low-cost DWDM optics. These optics include 16 different OLIUs (2 wavelengths per

OLIU) for OC-48 transmission, and a choice of 5 different Passive

Optics Units (POUs) where the various wavelengths are combined for transmission over one fiber. The DWDM wavelengths or channels are chosen at 100 GHz increments per the ITU grid.

In R4.0, DMX also supports 3 OC-192 DWDM circuit packs that feature “tunable” lasers. The optics on each pack can be tuned to any one of four separate frequencies to provide a flexible range of DWDM frequencies that enable each circuit pack to serve in four different

DMX DWDM systems. This makes each pack more versatile, reusable, and efficient in DWDM applications. The LNW523, LNW527, and

LNW554 are the circuit packs featuring tunable optics.

Port units

DMX OC-48 DWDM OLIUs are available in 32 different wavelengths.

Each port unit is capable of transmitting 2 different wavelengths (1 wavelength at a time). These units are compatible with the SONET standards.

The DWDM OLIUs are designed to be used with the Lucent POUs. By using the DWDM OLIUs and the POUs, you are able to increase fiber from 1 to 32.

Passive optics units

As the variety of applications listed above suggests, there are various versions of the POU, each designed to maximize functionality in a variety of deployment scenarios. The bulleted list below details the various forms of POUs:

• 16 Channel MUX or DMUX (odd numbered channels): This POU supports unidirectional and bidirectional transmission systems.

• 16 Channel MUX or DMUX with Interleaver (even numbered channels): This POU supports unidirectional and bidirectional transmission systems, and includes an interleaver to support 16 additional channels.

• Dual 1-Channel Optical Add Drop: This POU supports unidirectional transmission systems and can add/drop one channel from a DWDM line carrying up to 32 different channels.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 5 9

DWDM Optics

Applications and Configurations

• Dual 2-Channel Optical Add Drop: This POU supports unidirectional transmission systems and can add/drop two channels from a DWDM line carrying up to 32 different channels.

• Dual 4-Channel Optical Add Drop: This POU supports unidirectional transmission systems and can add/drop four channels from a DWDM line carrying up to 32 different channels.

• Dual 1310 + 4x1550 MUX/DMUX: This POU provides one I/O port for 1310 nm signals and four I/O ports for 1550 nm signals.

This POU supports unidirectional transmission systems and can

MUX or DMUX a 1310 channel and four 1550 bands to/from a

DWDM line.

Important!

The last four bulleted items in the list above describe the various OADMs and MUX/DMUX as “Dual”.

“Dual” is in reference to the fact that each of these specific POUs are comprised of two complete sets of OADMs or MUX/DMUX units. Thus, the dual 1-channel OADM POU contains 2 OADMs interfaces, enabling it to support 1 add/drop in each direction.

Protection

The passive optic port units support the same protection modes as the standard port units. For example, both sets of passive port units support

BLSR, UPSR, and 0x1 protection. The DWDM passive OLIUs also support 1+1 protection.

MUX/DMUX Example

The figure below shows 16 lines to and from DMX systems. The

OC-48 traffic from the 8 incoming (receive) and 8 outgoing (transmit) lines is transmitted over one fiber using DWDM on the Lucent passive optics shelf to a remote Lucent passive optics shelf. The traffic is similarly transmitted and received by that system. Alternatively, the equipment can be set up to handle 16 or 32 transmit lines on one end of the passive optics unit and 16 or 32 receive lines on the other end.

3 - 6 0

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

DWDM Optics

Applications and Configurations

Figure 3-36 Lucent Passive Optics Unit with DMX

DMX DMX

To/From other

Nodes and

Tributaries

DMX

WaveStar

2.5G/10G

DMX

WaveStar

Bandwidth

Manager

OC-48/192

BLSR or UPSR

DWDM

OC-48/192

BLSR or UPSR

WaveStar

2.5G/10G

DMX

WaveStar

Bandwidth

Manager

DMX

To/From other

Nodes and

Tributarie

DMX DMX nc-dmx-11

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 6 1

Applications and Configurations

Increased Span Length: External DWDM Optical Amplifiers (OAs)

Overview

For OC-192 spans of up to 140km, Lucent Technologies offers DWDM optical amplifiers. The DWDM optical amplifier is a stand-alone shelf and can be used with both regular and DWDM OC-48 and OC-192 optics.

Concept

Optical amplifiers consist of one booster and one pre-amplifier part.

The booster part is connected via a Dispersion Compensation Module

(DCM) to the transmit interface of the respective OC-192 or OC-48 port unit. The pre-amplifier is connected by means of a DCM to the receive interface of the associated port unit.

Applications

The DWDM optical amplifier has two main applications:

• Single span application

• Multiple span application

A simple example for a single span application is shown in the following figure.

Figure 3-37 External Optical Amplifier Application

Office A

Transmitt Amplifier

Metropolis

DMX

Remote Site

Line Amplifier

Office B

Pre-Amplifier

Metropolis

DMX

Nc-dmx-165

Further Information

For a description of the optical amplifier’s physical specifications, see the section entitled “External Optical Amplifier” in Chapter 4 of this document.

For a description of the optical amplifier’s optical specifications, see the section entitled “External Optical Amplifier” in Chapter 10 of this document.

3 - 6 2

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Dual Node Ring Interworking

Overview

Dual node ring interworking (DRI) is a configuration that provides path-level protection for selected STS-N circuits that are being carried through two UPSRs. Protection for the route between the two rings is

provided by interconnecting the rings at two places (see Figure 3-38

(3-64).

Each circuit that is provisioned with DRI protection is dual-homed, meaning it is duplicated and subsequently passed-through at two different nodes on a ring. The two interconnecting nodes in each ring do not need to be adjacent.

DRI protection

The self-healing mechanisms of the two UPSRs remain independent and together protect against simultaneous single failures on both rings

(not affecting the interconnections). The DRI configuration additionally protects against failures in either of the interconnections between the rings, whether the failure is in a facility or an interconnection node.

Ring interworking

All DMX tributary SONET interfaces (OC-3, OC-12, and OC-48) support DRI. The DMX high-speed ring can be an OC-12/48/192

UPSR. A DMX ring supports DRI with UPSRs, including rings using the following products:

• DMX

• WaveStar TDM 2.5G/10G (2-Fiber)

• WaveStar BandWidth Manager

• DDM-2000 OC-3

• DDM-2000 OC-12

• FT-2000 ADR

Additionally, there can be intermediate network elements in the interconnection routes between the two rings.

UPSR-to-UPSR interworking

In the UPSR to UPSR interworking both UPSR DRI nodes select the better of two paths travelling in the drop direction and pass traffic to one rotation of the ring in the add direction.

UPSR drop and continue

DMX supports the drop and continue method of DRI, in which both

UPSR DRI nodes select the better of two paths travelling in the drop direction and pass traffic to one rotation of the ring in the add direction.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 6 3

Applications and Configurations

UPSR to UPSR protection switching example

Each node drops the circuit in the direction of the other ring and a pass-through circuit to the other DRI node is made. The best of the 2 resulting signals is dropped at the terminating node of the new ring.

The figure below illustrates a failure of the interconnection to a DRI node at the point labeled “X” in the figure. A failure in the route from

Node A to Node Z results in a path switch at the surrounding nodes adjacent to the failure. The DRI nodes themselves will only perform the protection switch if they are the nodes adjacent to the failure. As you can see, while all nodes and lines remain fully functional, DRI functions as described in the section above. Both DRI nodes in the top ring select the best of the 2 signals received from that ring, and transmit them to the DRI nodes in the lower ring. The best of the signals received at the terminating node is dropped.

A path protection switch in a DMX occurs in <50 milliseconds (not counting the detection time) at the nodes adjacent to any failure.

Figure 3-38 Dual Ring Interworking Protection

Primary

Nodes

Secondary

Nodes

1. DRI configurations: two rings interconnected by two nodes

2. Circuit originating and terminating in

Nodes A and Z

3. Failure (depicted by x) triggers

DRI switch at primary nodes, which automatically selects traffic from secondary nodes

NC-DMX-149

3 - 6 4

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Single and Dual-Homing

Overview

End users are demanding service with high availability. Service providers are responding with tariffs that rely on self-healing networks to offer high availability service. Some of these tariffs even call for penalties for the service provider when service is interrupted or has a high error rate. The Lucent SONET product family offers many options for meeting these service needs. One of these, OC-3/12/48 ring transport on DMX ring networks, can be implemented in single- and dual-homing configurations.

For lower-density TDM applications, DMX can provide an OC-3/12/48 optical ring termination for a DDM-2000 OC-3 Multiplexer,

DDM-2000 OC-12 Multiplexer, DDM-2000 FiberReach, or any other compliant network element. This feeder ring is useful for evolving lower-density access transport applications into high-rate access networks.

Description

The figure below shows a dual-homed OC-3 extension from two remote nodes on a DMX access ring. OC-3 extensions from DMX rings are available when the DMX Function Unit groups are equipped with

OC-3 OLIU circuit packs. OC-12/48 extensions from DMX rings are also available. The host nodes must be DMX NEs. For an example of single homing, see the following page.

Figure 3-39 Dual Homing Example

WBDCS/

DMX

WaveStar

BWM/TDM

10-G

OC-48/192 UPSR

Metropolis

DMX

DS1,DS3,

OC-3(c)/12(c)/48(c)

Metropolis

DMX

OC-3/12

Hub/RT

DS1,DS3,

OC-3(c)/12(c)/48(c)

0x1 rings

DDM-2000

OC-3/FiberReach

Customer

Location

DS1/DS3/OC-3(c) nc-dmx-011

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 6 5

Single and Dual-Homing

Applications and Configurations

Description (continued)

The figure below provides an example of both single and dual-homing.

Path protection switching is employed for dual-homed and single-homed applications in the same manner. That is, 50 millisecond path switching is supplied by the remote DDM-2000

OC-3/OC-12/FiberReach nodes and the DMX systems. The DMX host node dual homing configuration differs from that used for single-homing because each host node transports only one leg of the

OC-3/OC-12/OC-48 extension. At each host node, a connection is made from the single OC-3/OC-12/OC-48 extension to just one rotation of the DMX host ring. Dual- and single-homed extensions can also be mixed at a host node, allowing the access network to be tailored efficiently to different groups of customers. Host nodes could also be

DMXtends.

Figure 3-40 Multinode OC-3/OC-12 Ring with OC-48 Ring

Transport

DDM

DDM OC-3/12/48

UPSR

Metropolis

DMX

Metropolis

DMX

OC-12/48/192

UPSR

Metropolis

DMX

DDM

Single

Homed

OC-3/12/48

Ring

DDM

Metropolis

DMX

Metropolis

DMX

DDM

Dual

Homed

OC-3/12/48

Ring

DDM

DDM nc-dmx2-027

Configuration advantage

The DMX provides a seamless transmission and operations integration with lower-capacity ring networks, as well as increased scalability for those established networks. So, single and dual-homing provide additional topological flexibility in UPSR configurations supporting voice and data services.

3 - 6 6

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Hairpinning

Overview

The DMX supports both inter-function group, intra-function group, intra-port as well as pass-through hairpinning cross-connections. These capabilities allow you to route traffic in and out of the DMX system without consuming bandwidth on the high-speed (OC-12/48/192)

UPSR interfaces, and to host multiple rings on the low-speed interfaces of the DMX shelf (OC-48, OC-12, OC-3).

Inter-function group hairpin

In a “hairpinning” topology, low-speed tributary traffic is routed into the system and back out of the system without ever being placed on the high-speed (OC-12/48/192) UPSR interfaces (this description assumes that the MAINs are provisioned for UPSR protection, but intra-function group hairpins are supported on all MAIN application/protection schemes). The cross-connection capability of connecting any input on a circuit pack in a function or growth slot to any output on a circuit pack in a different function or growth slot of the same shelf allows you to use a combination of add/drop and hairpinning of compatible payloads through a variety of interfaces. You can bring traffic in from one remote site and cross-connect it at the VT, STS-1, STS-3c, STS-12c, or

STS-48c level back out to other remote sites without consuming any capacity on the high-speed UPSRs.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 6 7

Hairpinning

Applications and Configurations

The figure below demonstrates a topology in which traffic is hairpinned among OC-12 and OC-3 low-speed interfaces (OC-48 also an option).

For instance, a signal dropped from the OC-3 UPSR in the bottom left of the figure can travel out of the DMX on the OC-12 UPSR on a completely different tributary.

Figure 3-41 Inter-function group hairpin

PWR

OC-12/48/192

UPSR

PWR

OC-3

OLIU

FAULT

ACTIVE

OC-3

OLIU

FAULT

ACTIVE

OC-12

OLIU

FAULT

ACTIVE

OC-12

OLIU

FAULT

ACTIVE

OUT IN OUT IN

1G SX OC-48

OLIU

FAULT

ACTIVE

FAULT

ACTIVE

OUT IN OUT IN

FAULT

ABN

ACO

TST

IND

SEL

UPD

INT

LAN

RS232

OC-48

OLIU

FAULT

ACTIVE

OUT IN

28DS1

FAULT

ACTIVE

28DS1

FAULT

12DS3/

EC1

FAULT

12DS3/

EC1

FAULT

ACTIVE ACTIVE ACTIVE

DDM-2000

A1 A2 B1 B2

OC-3

UPSR

OC-12

UPSR

G1 M1 CTL

Fiber Tray

DDM-2000

Metropolis

DMX press

M2 C1 C2 D1 D2 nc-dmx-018

3 - 6 8

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Hairpinning

Applications and Configurations

Low-speed Ring closure

The DMX can host multiple rings on the low-speed interfaces of the

DMX shelf. This is accomplished by either protected drops from a

UPSR or UPSR pass-throughs. The DMX can close a low-speed ring by supporting a cross-connection between a receive port on one circuit pack and a corresponding transmit port on another companion circuit pack in the same function or growth group (cross-connections can also be made to ports in any other slot on the shelf). All protection switching advantages/capabilities of UPSR configurations still apply in the low-speed ring closure application shown below.

The figure below demonstrates a ring closure topology in which both an OC-3 or OC-12 ring is being hosted on the low-speed interfaces alone. Notice that this consumes no bandwidth on the OC-48, high-speed UPSR in the top of the figure.

Figure 3-42 Low-speed ring closure

PWR

OC-12/48/192

UPSR

PWR

OC-3

OLIU

FAULT

ACTIVE

OC-3

OLIU

FAULT

ACTIVE

OC-12

OLIU

FAULT

ACTIVE

OC-12

OLIU

FAULT

ACTIVE

OUT IN OUT IN

1G SX OC-48

OLIU

FAULT

ACTIVE

FAULT

ACTIVE

OUT IN OUT IN

FAULT

ABN

ACO

TST

IND

SEL

UPD

INT

LAN

RS232

OC-48

OLIU

FAULT

ACTIVE

OUT IN

28DS1

FAULT

ACTIVE

28DS1

FAULT

12DS3/

EC1

FAULT

12DS3/

EC1

FAULT

ACTIVE ACTIVE ACTIVE

A1 A2 B1 B2 G1 M2 C1 C2 D1 D2 M1 CTL

Fiber Tray

DDM-2000

OC-3/12/48

UPSR

OC-3/12/48

1+1

DDM-2000

DDM-2000 nc-dmx2-013

Intra-function group hairpin

DMX supports intra-function group, hairpin cross-connections that are cross-connections between different tributaries on different ports within the same function group. Again, the application above could be enabled by either intra-function group hairpins or UPSR pass-throughs.

Intra-function group hairpins are available in all protection schemes, not just in UPSR applications.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 6 9

Hairpinning

Applications and Configurations

Intra-port hairpin

DMX supports the provisioning of intra-port cross connection on

UPSR interfaces. Intra-port characterizes cross connections between channels/timeslots/tributaries hosted on the same port.

3 - 7 0

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Linear Optical Extensions

Overview

An additional topological flexibility offered by the DMX is 1+1 protected linear OC-3, OC-12, OC-48, OC-192 optical extensions from the DMX ring. Using this capability, DMX can support many of the new network configurations desired in evolving access networks.

Description

An access provider can use linear optical extensions from an

OC-12/48/192 ring to provide OC-3, OC-12, and OC-48 signals directly to end users. This gives the end users the bandwidth they need for large bandwidth applications, such as video, data, and ATM.

Linear optical extensions can also be used to interconnect SONET subnetworks. Examples include interconnection of two access networks and interconnection between access and interoffice rings.

Optical extensions can be used to interconnect DMX ring networks to an OC-3, OC-12, or OC-48 terminal, an OC-3, OC-12, OC-48, or

OC-192 add/drop network, or another OC-3, OC-12, OC-48, or

OC-192 ring. Intra-port hairpins are supported on 1+1 protected interfaces.

The figure below shows a DMX OC-48/OC-192 path switched ring with OC-3/OC-12/OC-48 services using linear optical extensions.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 7 1

Linear Optical Extensions

Applications and Configurations

Figure 3-43 Linear Optical Extensions

Customer Location

OC-3/12/48

Broadband

Terminal

Central Office

OC-3/

OC-12

Metropolis

DMX

DDM-2000

OC-3

DS1/DS3/EC-1

OC-3

DDM-2000

OC-3

DS1/DS3/EC-1

OC-3/

OC-12/

OC-48

DS3/EC-1 Remote Terminal

Metropolis

DMX

Metropolis

DMX

OC-48/OC-192

UPSR or BLSR

DS3/EC-1

Remote Terminal

OC-3/

OC-12

Metropolis

DMX

FT-2000 or

2.5G/10G

(2-Fiber)

DS3/EC-1

Central Office nc-dmx-010

Configuration advantage

Optical extensions from a DMX ring provide fast, reliable transport of voice, video, data, and ATM directly to end users when fiber topologies warrant protected linear (rather than ring) connections.

3 - 7 2

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

Applications and Configurations

Hubbing

Overview

The DMX hubbing topology provides metropolitan-area and regional-area network infrastructures based on a single NE.

Description

A DMX high-speed UPSR ring can serve as a core feeder ring, transporting voice and data from metropolitan networks to the optical core network and vice versa.

As shown in Figure 3-28, one DMX node is configured as a core feeder node, providing a conduit from the optical core to the OC-48/192 access network. On the ring, another DMX is configured as the hub node, where several DMX and DDM UPSR rings are terminated. The hub node grooms the traffic and cross-connects it to the appropriate ring.

One DMX can be configured as a hub node for up to 80 OC-3 rings, 40

OC-12 rings, 20 OC-48 rings, or, as pictured below, a mixture of high- and low-speed rings.

Figure 3-44 Hubbing Application

Metropolis

DMX

press

DDM-2000

DMX

OC-48

OC-3/12

CO/Hub

Node

DMX

DMX OC-48

OC-12

Metropolis

DMX

press

DDM-2000

DMX = Metropolis DMX Access Multiplexer

DMX

OC-48/192

UPSR

DMX

Metro

Core

Optical

Core

NC-DMX-155

Configuration advantage

Hubbing provides high-capacity, low-cost grooming between multiple optical rings. It also provides greater flexibility and efficiency in serving large numbers of customers on multiple fiber rings.

365-372-300

Issue 8.0 September 2006

Lucent Technologies – Proprietary

See notice on first page

3 - 7 3

Hubbing

Applications and Configurations

3 - 7 4

Lucent Technologies – Proprietary

See notice on first page

365-372-300

Issue 8.0 September 2006

4 Product Description

Overview

Purpose

This chapter provides a detailed view of the DMX Access Multiplexer architecture. After introducing the DMX shelf, this chapter describes the system circuit packs, control, power, and cabling.

Contents

The following hardware is described in this chapter:

Shelf Description

Circuit Pack Descriptions

Passive Optics Units (POUs)

External Optical Amplifiers

Control

Power Specifications

DMX 20 Amp Shelf Power Specifications

Cabling

365-372-300

Issue 8.0, September 2006

4 - 1

Product Description

Shelf Description

Overview

The DMX is a single-shelf multiplexer that may house DS1/E1, DS3/

EC1, TransMUX, OC-3, OC-12, OC-48, OC-192, 10/100T (optical and electrical), 1G TX/SX/LX/ZX, and SAN (FICON/ESCON/FC) circuit packs.

Size

When equipped with VLF Mains (LNW59), each Function Unit and

Growth slot in the DMX shelf has a 10 Gb/s IO capacity. The LNW59

VLF Main increases the capacity of the Main slots to 20 Gb/s.

When VLF Mains are not used, each Function Unit slot in the DMX shelf has a 2.5 Gb/s IO capacity. The Growth slots have 5 Gb/s capacity, and the Main slots have 10 Gb/ps. Up to four DMX systems can fit in a bay, and all shelves are individually mounted.

The High-Capacity shelf also has the following characteristics:

• Width: 17.6 inches

• Height: 19 inches (includes integral fan unit)

• Depth (front to back): 13.75 inches (all optical applications only: without back cover and interface connectors*)

• Weight (with circuit packs): 57 pounds

• Weight (without circuit packs): 38 pounds

Important!

*: 15 inches with interface connectors, 16 inches with connectors and cover.

Up to four DMX high capacity shelves can fit in a bay (including integral fan unit), and all shelves are individually mounted.

The DMX high capacity shelf is available with 30 amp circuit breakers or 20 amp circuit breakers.

High Capacity Shelf

The high capacity shelf can operate using any release of DMX software.

This new design incorporates additional DS1/DS3 D-SUB cable connectors on the rear of the shelf that enable the DMX to support 224

DS1/E1s or 192 DS3/EC-1s. In order to support this amount of traffic, the DMX high capacity shelf must be equipped with new, higher density DS1/E1 and DS3/EC-1 circuit packs.

All other existing and future electrical, optical, Ethernet, and SAN circuit packs can also be used in the high capacity shelf.

4 - 2

365-372-300

Issue 8.0, September 2006

Shelf Description

Product Description

Interface Density

0x1 Fn/Growth slot equipage beginning in R7.0. In many cases, this doubles the overall capacity of the shelf.

1000BASE-SX/LX/ZX ports if both slots in all four Function Unit and

Growth groups are equipped with the LNW64 circuit packs (this 0x1 configuration requires VLF Main packs).

Table 4-1 Interface Densities

Interface Type

DS1/E1

DS3/EC-1

TransMUX

OC-3

OC-12

OC-48

OC-192

192

Capacity/Main Switch

VLF

(0x1 equipped)

Large/

Medium

Fabric

224

192

224

192

Comments

Electrical TDM packs, and other packs that require rear access, do not support true 0x1, hence, overall capacity does not increase with VLF Mains

192 capacity requires the 48 port LNW20

80 unprotected, 40 protected

40 unprotected, 20 protected

40 capacity requires LNW62, only supported on VLF equipped shelves. 40/10 unprotected, 20/5 protected

4 capacity requires LNW59. LNW59 provides 2 OC-192 ports. 4 unprotected with LNW59 only, 2/1 protected

100BASE-TX

100BASE-LX (optical)

1000BASE-SX/LX/ZX

1000BASE-TX

FICON/ESCON/

Fibre-Channel

Larger capacities associated with VLF Mains require 0x1 equipage in all slots, only supported in R7.0 and later releases.

365-372-300

Issue 8.0, September 2006

DMX also provides STS-1 virtual concatenation. STS-1 VCAT increases flexibility when managing Ethernet services. Each

4 - 3

Shelf Description

Product Description

10/100BASE-TX/PL and 1000BASE-SX/LX/ZX Ethernet service can be provisioned to any number of STS-1s (up to 21 STS-1s per VCG).

This is true for all Ethernet packs except LNW71. The LNW71 and

LNW74 can accept 1 or 2 STS-1s or a single STS-3c per port. The

LNW73/73C provides STS-1 and STS-3c virtual concatenation.

4 - 4

365-372-300

Issue 8.0, September 2006

Shelf Description

Front view

Product Description

The figure below shows the front of the DMX shelf equipped with the following:

• 28DS1 circuit packs in Function Unit group A

• 12DS3/EC1 circuit packs in Function Unit group B

• Quad OC-3 circuit packs in Function Unit group C

• Dual OC-12 circuit packs in Function Unit group D

• 1G SX circuit pack in Growth slot G1

• an apparatus blank in Growth slot G2

• OC-48 circuit packs in Main slots 1 and 2

• LNW2 SYSCTL circuit pack in the CTL slot.

Note that high-speed OC-192, OC-12, and the LNW80 (headless switch pack) network interface OLIUs are not pictured, but could populate Main slots 1 and 2. Many other tributary packs are not

pictured either. For pack-specific slot equipage rules refer to

Circuit pack slots and compatible circuit packs

and

Very Large Fabric (VLF)

Engineering Rules

Figure 4-1 Shelf Front View

a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

LNW6

Sx:x

LUCENT

LNW6

Sx:x

LUCENT

LNW16

Sx:x

LUCENT

LNW16

Sx:x

LUCENT

LNW67

Sx:x

LUCENT

LNW26

Sx:x

LUCENT

LNW1

Sx:x

LUCENT

177D

Sx:x

LUCENT

LNW26

Sx:x

LUCENT

LNW36

Sx:x

LUCENT

LNW36

Sx:x

LUCENT

LNW46

Sx:x

LUCENT

LNW46

Sx:x

LUCENT

Heat Baffle

FAULT

ACTIVE

28DS1

FAULT

ACTIVE

28DS1

FAULT

ACTIVE

FAULT

ACTIVE

12DS3/

EC1

12DS3/

EC1

FAULT

ACTIVE

1G SX

FAULT

ACTIVE

OC-48

OLIU

OUT IN

FAULT

ABN

ACO

TEST

IND

SEL

UPD/

INT

LAN

CIT

232

177D

BLANK

FAULT

ACTIVE

OC-48

OLIU

FAULT

ACTIVE

OC-3

OLIU

OC-3

OLIU

OUT IN OUT IN

FAULT

ACTIVE

FAULT

ACTIVE

OC-12

OLIU

FAULT

ACTIVE

OC-12

OLIU

OUT IN 1 1

2 2

OUT IN OUT IN

1 1

2 2

A1 A2

Lucent Technologies

Metropolis

DMX

B1 B2 G1 M1 CTL G2 M2 C1 C2 D1

OFF

Fan Filter

MA-DMX-405

365-372-300

Issue 8.0, September 2006

4 - 5

Shelf Description

Product Description

Circuit pack slots and compatible circuit packs

The DMX high capacity shelf has 8 function unit slots, 2 Main slots, 2

Growth slots, and one Control slot.

Function units slots

The function unit slots are divided into four groups designated A, B, C, and D. Function unit slots A1, A2, B1, B2, C1, C2, D1, and D2 can be equipped, depending on the application, with the following circuit packs

• 28DS1

• 56DS1/E1

• 12DS3/EC1

• 48DS3/EC1

• 48DS3/EC1/TMUX

• TMUX

• OC-3

• OC-12 (LNW46 and LNW49)

• OC-48 (LNW31, LNW62, and LNW421 - LNW459 only)

• 10/100T

• 10/100-PL

• 1000BASE-LX

• 1000BASE-SX

• 1000BASE-X/ 100BASE-LX

• 100BASE-LX/ 10/100 BASE-TX

• SAN circuit pack with choice of FICON/ESCON/Fibre-channel interfaces using PTM optics (LNW73 and LNW73C)

When the shelf is equipped with non-VLF Mains (LNW59), Ethernet and SAN circuit packs are restricted to slot 1 of a function unit (for example, slot A1). If slot 1 of a function unit is equipped with an

Ethernet or SAN circuit pack, then slot 2 must be equipped with a 177D apparatus blank or an LNW98 detectable blank circuit pack.

When the shelf is equipped with the LNW59 VLF Main, Ethernet and

SAN packs can reside in Slots 1 and 2 of a function unit (see Chapter 5 for restrictions).

4 - 6

365-372-300

Issue 8.0, September 2006

Shelf Description

Product Description

Growth slots

Growth slots G1 and G2 can be equipped, depending on the application, with the following circuit packs:

• 48DS3/EC1TransMUX (LNW20)

• OC-3

• OC-12 (LNW46 and LNW49)

• OC-48 (LNW31, LNW62, and LNW421 - LNW459 only)

• 1000BASE-LX

• 1000BASE-SX

• 1000BASE-X/ 100BASE-LX

• 100BASE-LX/ 10/100 BASE-TX

• FC-DATA (FICON/FC/Fibre-Channel)

When the shelf is equipped with non-VLF Mains (LNW59), Ethernet and SAN circuit packs are restricted to slot G1. If slot G1 is equipped with an Ethernet or SAN circuit pack, then slot G2 must be equipped with a 177D apparatus blank or an LNW98 detectable blank circuit pack. The LNW66 and LNW71 can not be housed in the growth slots.

When the shelf is equipped with the LNW59 VLF Main, Ethernet and

SAN packs can reside in Slots 1 and G2 (See Chapter 5 for restrictions.

R7.0 also supports Link Aggregation on the LAN ports of the LNW70 when they are in switched mode. Link Aggregation can be used to provide protection on LNW70 Ethernet ports. For more information on

Link Aggregation, refer to Appendix A.

Also, the LNW74 can only be installed in G1 and only the optical ports are available for service.

The LNW20 (48 DS3/EC1TransMUX) will not function in Portless mode when the shelf is equipped with certain Main interface packs. It is also restricted to Portless mode only when installed in Growth Slots.

Therefore the LNW20 cannot ben used in the Growth Slots when certain Main packs are used (see

Main packs that allow portless LNW20 operation

365-372-300

Issue 8.0, September 2006

4 - 7

Shelf Description

Product Description

Main slots

The main slots M1 and M2 can be equipped, depending on the application, with the following circuit packs:

• OC-12 OLIU circuit pack: LNW48, LNW50, and LNW54

• OC-48 OLIU circuit packs: LNW26B, LNW27, LNW28,

LNW29, LNW32, LNW76, LNW77, LNW121B-159B, or

LNW221-LNW259

• OC-192 OLIU circuit packs: LNW56, LNW57, LNW58, LNW59,

LNW60, LNW523, LNW527, LNW554, or LNW555

• Main Switch Circuit Pack: LNW80

The Stratum 3 timing generator and central TDM switch fabrics are embedded in the all of the MAIN circuit packs. If main slot M1 or M2 is not equipped with a circuit pack, the slot must be equipped with a

177E apparatus blank or an LNW97 detectable blank circuit pack.

There is no switch fabric on the blank circuit packs.

In R7.0, DMX introduces the LNW59 VLF Main. VLF Mains are designed to drastically increase the overall switch fabric capacity of

DMX. When DMX is equipped with VLF Mains, the switch fabrics of the low-speed, tributary packs are not used. Rather, all switching functions are performed on the VLF Main Fabric.

Control slot

The control slot CTL is reserved for the non-redundant System

Controller (SYSCTL) circuit pack. R6.0 (and all later releases) software requires the use of the LNW2 SYSCTL. The LNW1 is operational with R5.x software and all prior releases.

4 - 8

365-372-300

Issue 8.0, September 2006

Shelf Description

Product Description

Rear view (high-capacity shelf)

The figure below shows the various jacks and cable inputs on the DMX high-capacity shelf backplane.

Figure 4-2 DMX High Capacity Shelf Backplane Connectors

-48VB

-48RTNB

P15

J14

SYNC2

J11

MISC

J17

MODEM

J15

FAN

SYNC1 P14

-48VA

-48RTNA

J22 C IN

J23 D IN

J26 C OUT

J27 D OUT

J20 A IN

J21 B IN

J24 A OUT

J25 B OUT

J19

INTEROP

D OUT

D IN

C OUT

C IN

J16

IAOLAN

EXP2

CTL

OUT

J18

DLAN

J10

X.25

J12

ALM

EXP1

OUT

CTL

B IN

J13

ALM MULT

B OUT

A IN

A OUT

NC-DMX-156

The shelf backplane provides the following connectors:

• Communications modem (J17 MODEM)

• Intraoffice LAN (J16 IAOLAN)

• External DS1 synchronization input and output (J9 SYNC1 and

J14 SYNC2)

• Fan shelf power/alarm (J15 FAN)

• -48 V DC power feeder A and B (P14 -48VA, -48RTNA and

P15 -48VB, -48RTNB)

• Miscellaneous (environmental) discrete telemetry (J11 MISC)

• TL1 interface (J10)

• Office alarm interface (J12 ALM)

• Office alarm multiple (J13 ALM MULT)

• J18 DLAN (Reserved for use in a future release)

365-372-300

Issue 8.0, September 2006

4 - 9

Shelf Description

Product Description

• J19 INTEROP (Reserved for use in a future release)

• EXP1 IN, OUT, CTL (Reserved for use in a future release)

• EXP2 IN, OUT, CTL (Reserved for use in a future release)

• Eight DS1/DS3 and 10/100Base-T inputs (J2 A IN, J4 B IN,

J5 C IN, J7 D IN, J20 A IN, J21 B IN, J22 C IN, J23 D IN)

• Eight DS1/DS3 and 10/100Base-T outputs (J1 A OUT, J3 B OUT,

J6 C OUT, J8 D OUT, J24 A OUT, J25 B OUT, J26 C OUT,

J27 D OUT)

The -48 V DC power feeder interfaces (BAT A and BAT B) are located on the sides of the shelf.

4 - 1 0

365-372-300

Issue 8.0, September 2006

Product Description

Circuit Packs

Available circuit packs

The table below contains a list of each circuit pack supported by the

DMX, indicates which slots they are able to be housed in, and in what release each circuit pack is available.

Table 4-2 Circuit Packs in DMX Shelf

Circuit Pack

System Controller

(SYSCTL)

Apparatus

Code

LNW1

Slot(s)

CTL

Release

1.0-5.x only

Comments

System Controller

(SYSCTL)

Main Switch Pack

LNW2

LNW80

CTL

M1, M2

6.0

4.0

Extended temp. certification for outside cabinet deployment (OSP

Hardened), supports R5.x software and earlier releases

New controller that must be used for for R6.0. Additional memory to support R6.0 and beyond. Extended temp. certification for outside cabinet deployment (OSP

Hardened)

High-speed, 96 STS-1 VT fabric, based on LNW 27, no optics on pack, OSP hardened.

365-372-300

Issue 8.0, September 2006

4 - 1 1

Circuit Packs

Circuit Pack

OC-192 OLIUs

Apparatus

Code

LNW59

Slot(s)

M1, M2

LNW58

LNW56

LNW60

M1, M2

LNW57 M1, M2

LNW523 M1, M2

LNW527 M1, M2

LNW554 M1, M2

LNW555 M1, M2

Product Description

Release Comments

7.0

2.1

5.1

4.0

3.1

2 port, High-speed, 1.3SR1/1.5IR2/

1.5LR2 via XFP PTMs, 20G optical main, 240G STS fabric, 30G VT termination capacity, and 40G VT fabric

High-speed, very short reach,

1310nm, 48 STS-1 VT fabric

High-speed, intermediate reach,

1550nm, 48 STS-1 VT fabric

High-speed, long reach, 1533.47 nm, 48 STS-1 VT fabric, with tone circuitry and on-board amplifier

High-speed, long reach, 1533.47 nm, 48 STS-1 VT fabric, with tone circuitry

High-speed, DWDM, 1550 nm range, 48 STS-1 VT fabric, tunable laser (four lambda range).

High-speed, long reach (80 km),

1550 nm range, 48 STS-1 VT fabric/ can also be used as a single channel (channel 55) DWDM pack.

4 - 1 2

365-372-300

Issue 8.0, September 2006

Circuit Packs

Circuit Pack

OC-48 OLIU

Product Description

Apparatus

Code

LNW26B

LNW27

LNW28

LNW29

LNW31

LNW32

LNW62

(4-port)

LNW76

LNW77

LNW121B-

LNW159B and

LNW221-

LNW259

LNW421-

LNW459

Slot(s) Release Comments

M1, M2

A-D, G1, G2 2.0

M1, M2

A-D, G1, G2

M1, M2

2.0

2.1

1.0

2.1

4.0

7.0

2.1

2.0

2.0 and 2.1

A-D, G1, G2 3.0

High-speed, long reach, 1310nm, 12

STS-1 VT fabric

High-speed, long reach, 1310nm, 48

STS-1 VT fabric

High-speed, long reach, 1310nm, 12

STS-1 VT fabric

, OSP Hardened

High-speed, long reach, 1550nm, 48

STS-1 VT fabric

Low-speed, intermediate reach,

1310nm, 12 STS-1 VT fabric

High-speed, long reach, 1310nm, 48

STS-1 VT fabric, OSP Hardened

4 port, Low-speed, 1.3LR1/1.5LR2 via PTMs, no switch fabric, requires use of LNW59 VLF Main, OSP

Hardened

High-speed, short reach, 1310nm,

48 STS-1 VT fabric

High-speed, intermediate reach,

1310nm, 12 STS-1 VT fabric

High-speed, 16 DWDM circuit packs support 32 different wavelengths in the 1550 nm range.

The 121B series supports 12 STS-1

VT fabric while the 221 series supports 48 STS-1 VT mapping.

Low-speed 16 DWDM circuit packs support 32 different wavelengths in the 1550 nm range, 12 STS-1 VT fabric.

365-372-300

Issue 8.0, September 2006

4 - 1 3

Circuit Packs

Product Description

Circuit Pack

OC-12 OLIU

(1 port)

OC-12 OLIU

(4 ports)

OC-12 OLIU

(2 ports)

OC-3 OLIU

(4 ports)

OC-3 OLIU

(4 ports)

OC-3 OLIU

(8 ports)

12DS3/EC1

48DS3/EC1

48DS3/EC1/TMUX

(with portless operation)

Apparatus

Code

LNW48

LNW50

LNW54

LNW49

LNW46

LNW36

LNW37

LNW45

LNW16

LNW19

LNW19B

LNW20

Slot(s)

M1, M2

Release

3.1

5.1

A-D, G1, G2 4.0

A-D, G1, G2 1.1

A-D, G1, G2 4.0

A-D, G1, G2 5.0

A-D

A-G

(see comments)

1.0

3.1

5.0

7.0.1

Comments

High-speed, Intermediate reach.

1310 nm, OSP Hardened, 12 STS-1

VT fabric

High-speed, Long reach. 1310 nm,

OSP Hardened, 12 STS-1 VT fabric

High-speed, Long reach. 1550 nm,

OSP Hardened, 12 STS-1 VT fabric

Low-speed, 48 STS-1 VT fabric,

PTM optics, OSP hardened

Low-speed, long reach. 1310 nm,

12 STS-1 VT fabric, OSP Hardened

Low-speed, long reach 1310 nm,

12 STS-1 VT fabric, OSP Hardened

Low-speed, 12 STS-1 VT fabric,

PTM optics, OSP hardened, supports facility loopbacks, backwards compatible to R1.1

Low-speed, 48 STS-1 VT fabric,

PTM optics, OSP hardened, supports facility loopbacks

12 ports, OSP Hardened

48 ports, for use in DMX High

Capacity Shelf, OSP Hardened

48 ports, for use in DMX High

Capacity Shelf, OSP Hardened, supports DS3 Loopbacks

48 ports, OSP Hardened, DS3, EC1, and TMUX functionality on a portby-port basis. LNW20 is supported in G1/2 for portless mode only with certain Mains. When Mains that don’t support portless are used,

LNW20 can only be installed in A-

4 - 1 4

365-372-300

Issue 8.0, September 2006

Circuit Packs

Product Description

Circuit Pack

DS1/DS3

TransMUX

28DS1

28DS1PM

56DS1/E1

Electrical

Continuity Test

Tool

In-service

Electrical

Continuity Test

Tool

1000BASE-SX/LX/

ZX (4 ports)

Private Line

1000BASE-TX/SX/

LX/ZX (8 ports)

Private Line

Apparatus

Code

LNW18

Slot(s)

A-D

LNW6

LNW7

LNW8

LNW94

LNW93

LNW63

LNW64

A-D

Release Comments

3.0

1.0

3.1

4.0

A-G

(See Note 1)

6.0

A-G

(See Note 1)

7.0

12 ports, receives/transmits channelized DS3, OSP Hardened

28 ports, OSP Hardened, not supported with VLF Mains

56 ports, for use in DMX High

Capacity Shelf, OSP Hardened, E1 service is provisionable on a per pack basis, E1 became available in

R4.0

For use in DMX to test the integrity of cables connected to the DS1,

DS3, and Ethernet interfaces on the

DMX shelf

For use in DMX to test the integrity of cables that will be connected to a high-capacity DS1, DS3, or

Ethernet circuit pack while a lower capacity pack is in-service in the other slot of the function group.

1000BASE-SX/LX/ZX Ethernet interface via optical PTMs, can be used is slot 1 and/or 2 in a VLF equipped DMX and either slot 1 or

2 in a non-VLF equipped DMX,

GbE private lines, includes no switch fabric, OSP hardened

1000BASE-TX/SX/LX/ZX

Ethernet interface via PTMs, can be used is slot 1 and/or 2 in a VLF equipped DMX and in slot 1 in a non-VLF equipped DMX, GbE private lines, includes no switch fabric, OSP hardened

365-372-300

Issue 8.0, September 2006

4 - 1 5

Circuit Packs

Product Description

Circuit Pack

10/100T

(24 ports)

10/100 PL (24 ports)

Private Line

Apparatus

Code

LNW66

LNW71

Slot(s)

A-D

(See Note 2)

A-D

(See Note 2)

Release

1.1

3.1

1GbE SX

(2 ports)

1GbE LX

(2 ports)

Enhanced Ethernet

Switch Pack

(100/1000 BASE-T or 1000BASE-LX/

—

4 ports,

10/100 LX

—

4 ports

FC-DATA

(SAN Interface)

FC-DATA w/ compression

(SAN Interface)

LNW67

LNW68

LNW70

LNW73

LNW73C

A-G

(See Note 1)

1.1

A-G

(See Note 1)

1.1

A-G

(See Note 1)

5.1

A-G

(See Note 1)

5.1

A-G

(See Note 1)

7.0

Comments

100BASE-TX Ethernet interface

100BASE-TX PL Ethernet interface, supports Ethernet Private

Lines

1000BASE-SX Ethernet interface, may occupy slot 1 or 2 of a function group or a growth slot, requires multi-mode cable

1000BASE-LX Ethernet interface, may occupy slot 1 or 2 of a function group or a growth slot, requires single-mode cable

Hybrid 100/1000 BASE-TX or

1000BASE-X (ports 1-4), and 100

BASE-LX (ports 5-8) Ethernet interface, may occupy slot 1 or 2 of a function group or a growth slot, uses PTMs, supports enhanced

Ethernet QoS

4 ports, PTM optics supporting either FICON/Fibre-Channel or

ESCON, can be installed in slot 1 or

2 of a function group or a growth slot with VLF mains, slot 1 only with non-VLF

4 ports, PTM optics supporting either FICON/Fibre-Channel or

ESCON, also supports compression of SAN traffic, can be installed in slot 1 or 2 of a function group or a growth slot with VLF mains, slot 1 only with non-VLF

4 - 1 6

365-372-300

Issue 8.0, September 2006

Circuit Packs

Product Description

Circuit Pack

100BASE-LX

(8 ports)

10/100BASE-TX

(16 ports)

Private Line

Apparatus Blank

Detectable

Apparatus Blank

Detectable

Apparatus Blank

Apparatus

Code

LNW74

Slot(s)

A-G

(See Note 1)

Release

5.0

RPR 1GbE X

100/1000BASE-X

(2 ports),

100BASE-LX

(4 ports)

LNW78

177D

177E

LNW97

LNW98

A-G

(See Note 1)

6.0

A-D, G1, G2 1.0

2.0

3.1

A-D, G1, G2 3.1

Comments

Hybrid 100BASE-LX and 10/100

BASE-TX Ethernet interface, OSP hardened, may only occupy slot 1 of a function group or a growth slot, uses PTM optics for LX interfaces, supports private lines, when in G1 slot, only the optical ports (17-24) of the LNW74 function

Hybrid 100/1000BASE-X and 100

BASE-LX Ethernet interface, may only occupy slot 1 of a function group or a growth slot if non-VLF mains are used, slot 1 and 2 are available with VLF mains, uses

PTM optics, supports RPR protection and enhanced Ethernet

QoS, adds support for Ethernet over

SONET in R7.0

Filler plates to be used in unpopulated slots of the DMX shelf

Filler plates to be used in unpopulated M2 slot of the

DMX shelf. The PC-CIT will show a blank plate when slot is equipped with this pack.

Filler plates to be used in unpopulated Function Unit or

Growth Slot of the

DMX

shelf. The

PC-CIT will show a blank plate when slot is equipped with this pack.

Notes

1. In order to support Ethernet and SAN packs in both Slot 1 and 2 of a

Function Group or Growth Slot, DMX must be equipped with VLF

365-372-300

Issue 8.0, September 2006

4 - 1 7

Circuit Packs

Product Description

Mains (LNW59) and R7.0 software.

2. DMX does not allow installation of two packs with electrical interfaces in adjacent slots within the same Function Unit or Growth

Group (other then an equipment-protected pair). Therefore, in systems equipped with LNW59 VLF mains, LNW66 and LNW71 packs can reside in either Slot 1 or Slot 2 of a group, but not both at the same time.

Telcordia will only support electrical packs in Slot 1 of a group.

However, another optical (Ethernet or SONET) pack may be installed in the other slot. In non-VLF equipped shelves, LNW66 and LNW71 can only occupy Slot 1 of a particular group.

3. When populating the MAIN slots in the DMX shelf, it is imperative that both MAIN 1 and MAIN 2 contain circuit packs with identical VT switch fabric size. The DMX OC-48 circuit packs, for example, contain fabrics ranging from 6 to 48 STS-1 capacity. It is therefore very important that you look carefully at the switch fabric sizes of your high-speed circuit packs while planning your order.

This information can be found in the Comments column of the table above, or in the text associated with the various circuit packs detailed in the following section.

4 - 1 8

365-372-300

Issue 8.0, September 2006

Product Description

Circuit Pack Descriptions

Overview

This section briefly describes DMX circuit packs.

System Controller (LNW1)

The LNW1 is operational with Release 5.x software and all prior releases. It cannot be used with R6.0 and later releases

The SYSCTL provides communication with other circuit packs on the

DMX shelf. The SYSCTL supports all DMX operations interfaces, including IAO LAN (OSI or TCP/IP), TL1/X.25, PC-CIT, office alarms, and miscellaneous discretes. The SYSCTL also supports DCC terminations for each optical line interface.

The SYSCTL faceplate has push-button switches, alarm/status LEDs, and a 7-segment numeric display to facilitate local operations. The

SYSCTL provides redundancy by duplicating all cross-connect information on the OLIU circuit packs. Transmission is not affected if the SYSCTL fails.

The SYSCTL circuit pack provides a microprocessor, nonvolatile memory to store the generic program software and provisioning database, and additional memory for system operation. The SYSCTL circuit pack also has interfaces across the backplane to monitor and control every circuit pack in the shelf.

The SYSCTL supports PC-CIT front access to the DMX via the IAO

LAN and a serial RS-232 port located on the back of the DMX shelf.

System Controller (LNW2)

The LNW2 functions in the same capacity and with the same capabilities as LNW1, except that it contains a memory upgrade to support the enhanced feature sets of R6.0 and upcoming releases and it does not support X.25. The LNW2 must be used with R6.0 and later releases.

LNW2 also contains two removable Non-volatile Memory (NVM) cards that are separately orderable from the LNW2 card itself (although the SYSCTL does come equipped with two NVM cards). A DMX shelf running R6.0 software will only function properly when it is equipped with a LNW2 card that contains two fully functioning NVM cards. The

NVM cards are removable/replaceable.

365-372-300

Issue 8.0, September 2006

4 - 1 9

Circuit Pack Descriptions

Product Description

Main Switch Pack

(LNW80)

The LNW80 high-speed circuit pack is designed to save cost in CO hub applications where there is no need to transmit traffic over networkside interfaces. LNW80 is best used in a DCS type of application. It can cross-connect signals amongst multiple low-speed tributary interfaces and perform VT mapping into OC-3/12/48 tributaries. It can crossconnect signals at the VT1.5, STS-1, STS-3(c), STS-12(c), and STS-

48(c) level. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the LNW80.

The LNW80 circuit pack design is based on the design/capabilities of the LNW27 pack, minus the optical interfaces.

The LNW80 circuit pack supports VT mapping in 96 STS-1s.

The LNW80 may occupy Main slots 1 and 2 and contains NO interfaces on the faceplate of the pack. Due to the increased switch fabric size and the absence of any optics on the pack’s faceplate, the

LNW80 is not upgradeable to a high-speed optical pack.

28DS1 (LNW6) and

28DS1PM (LNW7)

The LNW6 and LNW7 are not supported when DMX is equipped with

VLF Main (LNW59) packs. LNW6/7 contain 28 DS1 ports that can be cross-connected to VT1.5 timeslots when the system is operating with a

UPSR, 1+1, or BLSR Main interface. Hairpin cross-connections to OCn and other electrical interfaces are also supported. Both packs are 1x1 protected, and non-revertive protection switching is supported. Line build-outs and DS1 signal encoding are software provisionable. Both circuit packs terminate up to 28 bidirectional DS1 electrical signals and support the transport of DS1 signals coded in either alternate mark inversion (AMI) or bipolar 8-zero substitution (B8ZS) modes. The signals received from the DSX-1 are mapped into SONET VT1.5 signals and then routed to the high-speed OLIU circuit pack.

Both circuit packs can occupy Function Unit groups A, B, C, and D.

All electric interface circuit packs are 1x1 hardware protected. So, although both slots in each function group can house a LNW6 or

LNW7 circuit pack, one slot in each function group populated by

LNW6 or LNW7 circuit packs is always used for hardware protection.

Thus the DMX shelf supports up to 112 working ports when four

Function Unit groups are equipped with the LNW6 or LNW7 circuit pack.

In addition to maintenance and provisioning functions, the 28DS1PM circuit pack provides performance monitoring capabilities.

Whenever upgrading LNW6 to LNW7 circuit packs, it is necessary to first install an LNW8 circuit pack to ensure that the upgrade is completed without loss of service.

4 - 2 0

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

56DS1/E1 (LNW8)

These circuit packs can be used only in the high capacity shelf and contain 56 DS1/E1 ports that can be cross-connected to VT or STS-1 timeslots in DS1 mode and STS3(c) timeslots in E1 mode. 56DS1/E1 packs are 1x1 protected by default, and non-revertive protection switching is supported. LNW8 can be provisioned for 0x1 protection, allowing the pack to go unprotected. Yet, DMX does not allow electrical TDM packs (and other packs that require rear access) to be paired with any other working packs in the same Function group or

Growth slot. For a detailed description of circuit pack slot equipage guidelines, refer to Chapter 5.

Line build-outs and DS1 signal encoding are software provisionable.

These packs terminate up to 56 bidirectional DS1 electrical signals and support the transport of DS1 signals coded in either alternate mark inversion (AMI) or bipolar 8-zero substitution (B8ZS) modes. The signals received from the DSX-1 are mapped into SONET VT1.5 signals and then routed to the high-speed OLIU circuit pack. DS1 signals can be connected directly to high-speed BLSRs at the VT1 rate.

The E1 ports have 120 Ohm terminations, and are HDB3-encoded. The mapping is E1 <-> VC-12 <-> TU-12 <-TUG2 <-> TUG3 <->VC-4

(treated as an STS3c). When the LNW8 is provisioned for E1 interfaces the output of the card will always be an STS-3c regardless of the amount of traffic it is actually handling.

56DS1/E1 circuit packs can occupy Function Unit groups A, B, C, and

D. Electric interface circuit packs are 1x1 hardware protected. So, although both slots in each function group can house a LNW8 circuit packs, one slot in each function group populated by LNW8 circuit packs is always used for hardware protection. Thus the DMX shelf supports up to 224 working ports when four Function Unit groups are equipped with the LNW8 circuit pack.

In addition to maintenance and provisioning functions, the 56DS1/E1 circuit pack provides performance monitoring capabilities.

12DS3/EC1 (LNW16)

The 12DS3/EC1 (LNW16) circuit pack contains 12 ports and supports non-revertive protection switching. The 12DS3/EC1 circuit pack provides bidirectional transport of 12 DS3 or EC-1 signals and maps the DS3s into STS-1 signals, and supports transport of DS3 signals coded in bipolar 3-zero substitution (B3ZS). DS3 or EC-1 service is provisionable on a per-port basis within each pack.

The LNW16 may occupy Function Unit groups A, B, C, and D.

Electric interface circuit packs are 1x1 hardware protected. So, although both slots in each function group can house a LNW16 circuit

365-372-300

Issue 8.0, September 2006

4 - 2 1

Circuit Pack Descriptions

Product Description

pack, one slot in each function group populated by LNW16 circuit pack is always used for hardware protection. Thus the DMX shelf supports up to 48 working ports when four Function Unit groups are equipped with the LNW16 circuit packs.

Trans/MUX circuit pack

(LNW18)

DMX supports a 12-port Trans/MUX card that can collect various DS1 signals from around a ring and combine them into a channelized DS3 signal. LNW18 is environmentally hardened for outside plant (OSP) deployments.

The LNW18 may occupy Function Unit groups A, B, C, and D.

Electric interface circuit packs are 1x1 hardware protected. So, although both slots in each function group can house a LNW18 circuit pack, one slot in each function group populated by LNW18 circuit pack is always used for hardware protection. Thus the DMX shelf supports up to 48 working ports when four Function Unit groups are equipped with the LNW18 circuit packs.

The Trans/MUX circuit pack functions in the following manner:

Transmit Functions

• Receives a B3ZS-encoded DS3 signal from a DSX-3

• Recovers DS3 clock and NRZ data

• Calculates parity errors on the DS3 input

• Demultiplexes the M13 or C-bit formatted DS3 signal into 28

DS1s

• Maps the 28 DS1s into VT1.5s and then into an STS-1

• Inserts STS-1 path overhead

• Provides the STS-1 signal to the OLIU circuit packs

Receive Functions

• Interprets the STS-1 pointer values

• Terminates the STS-1 path

• Disinterleaves the STS-1 signal into 28 VT1.5s and interprets VT pointer values

• Converts the VT1.5 signals to 28 DS1 signals

• Multiplexes the 28 DS1 signals to an M13 or C-bit formatted DS3 signal

• B3ZS encodes the outgoing DS3 signal

• Pre-equalizes the DS3 signal (with LBO) and transmits it to a

DSX-3

4 - 2 2

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

48DS1/E1/TransMUX

(LNW20

—

R7.0.1)

The LNW20 provides 48 ports supporting DS3, EC1, and TMUX functionality on a port-by-port basis. Each port can be individually provisioned as DS3 or EC1 (unchannelized), or as TransMUX

(channelized DS3s). With the LNW20, one high-density pack can be used for all DS3, EC1, and/or TransMUX applications.

The LNW20 can also function in portless mode. Portless mode does not utilize any of the electrical ports on the pack. When operating in portless mode, LNW20 pulls DS1s from channelized DS3 signals that enter DMX on a SONET STS-1 interface (on another pack) and converts them to VT mapped STS-1s. This VT-mapped STS-1 is crossconnected at the VT level in the Main packs (at least one side of the cross-connect is OCn/EC1) to any interface that supports the signal structure today (DS1, channelized DS3, EC1, optical). Portless mode can be provisioned on a per-port basis. When certain Mains are used, only odd numbered ports can be configured as portless and the corresponding even-numbered port will be unavailable for service.

LNW20 can be 1x1 protected or function in 0x1 unprotected mode. It supports hairpins to other packs in the shelf, and between ports on the same pack. LNW20 can occupy slots A1/A2 through G1/G2 when the

LNW59 VLF Main is used. LNW20 only functions in portless mode in

G1/G2. Certain Main packs do not support portless mode (see table below). Therefore, when these packs are used, LNW20 cannot be used in G1/G2.

Table 4-3 Main packs that allow portless LNW20 operation

Rate

OC-48

Circuit packs

LNW27

LNW29

LNW32

LNW76

LNW221-259

OC-192 LNW56

LNW57

LNW58

LNW59

LNW60

LNW521-559

Switch pack (headless) LNW80

DMX does not allow 2 electrical TDM packs of different types (or any packs that require rear access) to occupy adjacent slots in the same

365-372-300

Issue 8.0, September 2006

4 - 2 3

Circuit Pack Descriptions

Product Description

Function Group. So, although 0x1 functionality allows LNW20 to function unprotected, overall capacity is not increased. A total of 192 ports are available when all slots are equipped with LNW20 circuit packs (a maximum of 240 ports are available when the LNW20 is functioning in portless mode and the shelf is equipped with VLF

Mains). This is because LNW20 must function in portless mode when installed in the Growth Slots. Though the LNW20 supports 0x1 protection, companion slots (ex. A1 and A2) can only be equipped with

LNW20 packs (no circuit pack/interface mixing in the same Function

Group) providing 1+1 protection.

OC-3 OLIU (LNW36)

The quad OC-3 OLIU low-speed circuit pack is a four-port, long-reach,

1310 nm optical line interface unit supporting VT1.5, STS-1 and STS-

3c path switching. LNW36 supports VT mapping in 12 STS-1s. The

LNW36 can interface with other OC-3 rings in the network and can also be used as an interface for OC-3 linear optical extensions, as well as single- and dual- homed ring extensions. Fiber access is provided via four pairs of LC-type connectors on the LNW36 faceplate.

The LNW36 can occupy any Function Unit group on the DMX shelf

(including Growth slots), and up to 40 ports are addressable when all

Function Unit groups are equipped with the LNW36 circuit pack.

The LNW36 is being DA’d and will no longer be available as of 12/31/

07.

OC-3 OLIU (LNW37)

The quad OC-3 OLIU low-speed circuit pack is a four-port, PTMbased optical line interface unit supporting VT1.5, STS-1 and STS-3c path switching. The LNW37 can interface with other OC-3 rings in the network and can also be used as an interface for OC-3 linear optical extensions, as well as single- and dual- homed ring extensions. LNW37 supports VT mapping in 12 STS-1s. The LNW37 also supports facility loopbacks for testing purposes. The LNW37 is OSP hardened.

The LNW37 features Pluggable Transmission Module (PTM) optics, also known as SFP optics. PTM optics are “pluggable” in the sense that they can be plugged into a circuit pack as they become necessary. This allows customers to grow their network incrementally, only realizing the full cost for optics as the need to provision service on (and thus receive revenue from) them becomes necessary. LNW37 packs are purchased and shipped with no sockets populated with functioning optics. The ports remain empty until the customer decides to place optics in them.

4 - 2 4

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

OC-3 OLIU (LNW45)

The LNW37 can occupy any Function Unit group on the DMX shelf

(including Growth slots), and up to 40 ports are addressable when all

Function Unit groups are equipped with the LNW37 circuit pack. The

LNW37 is also backward compatible to R1.1.

The OC-3 OLIU low-speed circuit pack is an 8-port, PTM-based optical line interface unit supporting VT1.5, STS-1 and STS-3(c) path switching. The LNW45 can interface with other OC-3 rings in the network and can also be used as an interface for OC-3 linear optical extensions, as well as single- and dual- homed ring extensions. LNW45 supports VT mapping in 48 STS-1s. The LNW45 also supports facility loopbacks for testing purposes. The LNW45 is OSP hardened.

The LNW45 features Pluggable Transmission Module (PTM) optics, also known as SFP optics. PTM optics are “pluggable” in the sense that they can be plugged into a circuit pack as they become necessary. This allows customers to grow their network incrementally, only realizing the full cost for optics as the need to provision service on (and thus receive revenue from) them becomes necessary. LNW45 packs are purchased and shipped with no sockets populated with functioning optics. The ports remain empty until the customer decides to place optics in them.

The LNW45 can occupy any Function Unit group on the DMX shelf

(including Growth slots), and up to 80 ports are addressable when all

Function Unit groups are equipped with the LNW45 circuit pack.

365-372-300

Issue 8.0, September 2006

4 - 2 5

Circuit Pack Descriptions

Product Description

OC-12 OLIU (LNW46)

The dual OC-12 OLIU (LNW46) low-speed circuit pack is a two-port, long-reach, 1310 nm optical line interface unit supporting VT1.5, STS-

1, STS-3(c), and STS-12(c) path switching. LNW46 supports VT mapping in 12 STS-1s. The LNW46 provides an OC-12 interface to other OC-12 rings, linear optical extensions, and single- and dualhomed ring extensions. Fiber access is provided via two pairs of LCtype connectors on the LNW46 faceplate.

The LNW46 can occupy any Function Unit group on the DMX shelf

(including Growth slots), and up to 20 ports are addressable when all

Function Unit groups are equipped with the LNW46 circuit pack.

The LNW46 is being DA’d and will no longer be available as of 12/31/

07.

OC-12 OLIU (LNW48)

The OC-12 OLIU (LNW48) high-speed circuit pack is an intermediate reach 1310 nm circuit pack. The LNW48 supports OC-12 add/drop,

UPSR configurations, single- and dual-homing, non-revertive linear and bidirectional 1+1 protection switching, and VT1.5, STS-1, STS-

3(c), and STS-12(c) signal transport. The LNW48 OLIU can crossconnect VTs in 12 of 12 STS-1s. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-12 OLIU.

The LNW48 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW48 faceplate.

OC-12 OLIU (LNW49)

The quad OC-12 OLIU (LNW49) low-speed circuit pack is a four-port,

PTM-based optical line interface unit supporting VT1.5, STS-1, STS-

3(c), and STS-12(c) path switching. LNW49 supports VT mapping in

48 STS-1s. The LNW49 provides an OC-12 interface to other OC-12 rings, linear optical extensions, and single- and dual-homed ring extensions. LNW49 supports VT mapping in 48 STS-1s.

The LNW49 features Pluggable Transmission Module (PTM) optics.

PTM optics are “pluggable” in the sense that they can be plugged into a circuit pack as they become necessary. This allows customers to grow their network incrementally, only realizing the full cost for optics as the need to provision service on (and thus receive revenue from) them becomes necessary. LNW49 packs are purchased and shipped with no ports populated with functioning optics. The ports remain empty until the customer decides to place optics in them.

The LNW49 can occupy any Function Unit group on the DMX shelf

(including Growth slots), and up to 40 ports are addressable when all

Function Unit groups are equipped with the LNW49 circuit pack. The

LNW49 is approved for OSP deployments.

4 - 2 6

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

OC-12 OLIU (LNW50)

The OC-12 OLIU (LNW50) high-speed circuit pack is a long reach

1310 nm circuit pack. The LNW50 supports OC-12 add/drop, UPSR configurations, single- and dual-homing, non-revertive 1+1 linear protection switching, and VT1.5, STS-1, STS-3(c), and STS-12(c) signal transport. The LNW50 OLIU can cross-connect VTs in 12 of 12

STS-1s. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-12 OLIU.

The LNW50 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW50 faceplate.

OC-12 OLIU (LNW54)

The OC-12 OLIU (LNW54) high-speed circuit pack is a long reach

1550 nm circuit pack. The LNW54 supports OC-12 add/drop, UPSR configurations, single- and dual-homing, non-revertive 1+1 linear protection switching, and VT1.5, STS-1, STS-3(c), and STS-12(c) signal transport. The LNW54 OLIU can cross-connect VTs in 12 of 12

STS-1s. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-12 OLIU.

The LNW54 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW54 faceplate.

OC-48 OLIU (LNW26B)

The LNW26B high-speed circuit pack is a long reach OC-48, 1310 nm optical line interface unit. The LNW26B supports OC-48 add/drop,

BLSR and UPSR configurations, single- and dual-homing, nonrevertive linear and bidirectional 1+1 protection switching, and VT1.5,

STS-1, STS-3(c), STS-12(c), and STS-48) signal transport. The

LNW26B pack can cross-connect VTs in 12 of 48 STS-1s of the OC-48 signal. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-48 OLIU.

The LNW26B may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW26B faceplate.

OC-48 OLIU (LNW27)

The LNW27 high-speed circuit pack is a long reach OC-48, 1310 nm optical line interface unit. The LNW27 supports OC-48 add/drop,

BLSR and UPSR configurations, single- and dual-homing, nonrevertive linear and bidirectional 1+1 protection switching, and VT1.5,

STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport. The

Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-48 OLIU.

The LNW27 circuit pack can cross-connect VTs in all 48 STS-1s of the

OC-48 signal.

365-372-300

Issue 8.0, September 2006

The LNW27 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW27 faceplate.

4 - 2 7

Circuit Pack Descriptions

Product Description

OC-48 OLIU (LNW28)

The LNW28 will no longer be available as of 5/17/06.

The LNW28 has the same capabilities as the LNW26B circuit pack. It is, however, designed specifically for outside cabinet deployment and has been certified to withstand extreme temperatures.

The OC-48 OLIU (LNW28) high-speed circuit pack is a long reach

1310 nm optical line interface unit. The LNW28 supports OC-48 add/ drop, BLSR and UPSR configurations, single- and dual-homing, nonrevertive linear and bidirectional 1+1 protection switching, and VT1.5,

STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport. The

LNW28 can cross-connect 12 of 48 selected STS-1s. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the

OC-48 OLIU.

The LNW28 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW28 faceplate.

OC-48 OLIU (LNW29)

The LNW29 high-speed circuit pack is a long reach OC-48, 1550 nm optical line interface unit. The LNW29 supports OC-48 add/drop,

BLSR, UPSR, and 1+1 configurations, single- and dual-homing, nonrevertive linear and bidirectional 1+1 protection switching, and VT1.5,

STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport. The

Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-48 OLIU.

The LNW29, like the LNW27 circuit pack, can cross-connect VTs in all 48 STS-1s of the OC-48 signal.

The LNW29 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW29 faceplate.

OC-48 OLIU (LNW31)

The OC-48 OLIU low-speed circuit pack is a single port

(bidirectional), intermediate reach, 1310 nm optical line interface unit.

The LNW31 supports OC-48 add/drop, BLSR, UPSR, and 1+1 configurations, single- and dual-homing, non-revertive linear and bidirectional 1+1 protection switching, and VT1.5, STS-1, STS-3(c),

STS-12(c), and STS-48(c) signal transport. The LNW31 circuit pack can route VTs in 12 STS-1s of the OC-48 signal to the MAIN circuit packs for VT grooming. The central TDM switch/grooming fabrics are embedded in the OC-48 MAIN OLIU.

The LNW31 may occupy any Function Unit group on the DMX shelf

(including Growth slots), and up to 10 ports are addressable when all

Function Unit groups are equipped with the LNW31 circuit pack. Fiber access is provided via a pair of LC-type connectors on the LNW31 faceplate.

4 - 2 8

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

OC-48 OLIU (LNW32)

Product Description

OC-48 OLIU (LNW62

—

R7.0)

The LNW32 high-speed circuit pack is a long reach OC-48, 1310 nm optical line interface unit. LNW32 is OSP hardened for outside plant applications. The LNW32 supports OC-48 add/drop, BLSR and UPSR configurations, single- and dual-homing, non-revertive linear and bidirectional 1+1 protection switching, and VT1.5, STS-1, STS-3(c),

STS-12(c), and STS-48(c) signal transport. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-48

OLIU.

The LNW32 circuit pack can cross-connect VTs in all 48 STS-1s of the

OC-48 signal.

The LNW32 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW32 faceplate.

LNW62 is a 4 port OC-48 circuit pack supporting add/drop, UPSR, and

BLSR configurations, single- and dual-homing, non-revertive or revertive linear 1+1 protection switching, and 0x1 operation. A maximum of 16 BLSRs (between low-speed and high-speed slots) are supported per shelf when the LNW62 is equipped in all tributary slots and LNW59 VLF Mains are used in the Main slots.

The LNW62 provides 4 PTM (also known as SFP) ports capable of supporting 1.3LR1 and 1.5LR2 PTMs.

As an R7.0 circuit pack, the LNW62 does not have an on-board switch fabric and therefore can only be used with the LNW59 packs in the

Main slots. All switching functions are performed on the VLF Main packs (LNW59).

LNW62 supports VT1.5, STS-1, STS-3c, STS-12c, and STS-48c signal transport. The LNW62 boasts a 10G backplane interface capacity and may occupy both Function and Growth slots, providing a total port density of 20 OC-48 ports per shelf if every Function and Growth slot is equipped with an LNW62.

OC-48 OLIU (LNW76)

The LNW76 high-speed circuit pack is a short reach, 1310 nm optical line interface unit. It is designed for intra-office transmission. The

LNW76 supports OC-48 add/drop, BLSR, UPSR, and 1+1 configurations, single- and dual-homing, non-revertive linear and bidirectional 1+1 protection switching, and VT1.5, STS-1, STS-3(c),

STS-12(c), and STS-48(c) signal transport. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-48

OLIU.

The LNW76 circuit pack can cross-connect VTs in all 48 STS-1s of the

OC-48 signal.

365-372-300

Issue 8.0, September 2006

4 - 2 9

Circuit Pack Descriptions

Product Description

The LNW76 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW76 faceplate.

OC-48 OLIU (LNW77)

The LNW77 circuit pack is a intermediate reach (20km), high-speed

1310 nm optical line interface unit. The LNW77 supports OC-48 add/ drop, BLSR and UPSR configurations, single- and dual-homing, nonrevertive linear and bidirectional 1+1 protection switching, and VT1.5,

STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport. The

Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-48 OLIU.

The LNW77 pack can cross-connect VTs in 12 of 48 STS-1s of the

OC-48 signal.

The LNW77 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW77 faceplate.

OC-48 High-speed (network interface) DWDM OLIUs

The DMX OC-48 DWDM OLIUs are optical port units designed for use with passive MUX/DMUX and optical add/drop shelves. This

DWDM feature supports 32 different wavelengths. Each port unit supports two wavelengths via a special hardware configuration. These units are compatible with the SONET and SDH standards.

The optical port units are designed to be used with the Lucent Passive

Optics Units (POUs). By using the DWDM port units and the POUs, you are able to increase fiber capacity by a factor of 16 or 32.

OC-48 DWDM OLIUs support add/drop, BLSR and UPSR configurations, single- and dual-homing, non-revertive linear and bidirectional 1+1 protection switching, and VT1.5, STS-1, STS-3(c),

STS-12(c), and STS-48(c) signal transport. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-48

OLIU.

One set of OC-48 DWDM OLIUs can cross-connect VTs in any 12 of

48 selected STS-1s (LNW121B-159B). Another set of OC-48 DWDM

OLIUs can cross-connect VTs in all 48 STS-1s of the OC-48 signal

(LNW221-259).

The OC-48 DWDM OLIUs may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the OC-48

DWDM OLIU faceplate.

The LNW121B, 123B, 131B, 135B, 137B, 143B, 145B, 147B, 149B,

157B, and 159B packs are no longer available. All other 100 series packs will still be available. The LNW221, 243, and 257 packs are no longer available. All other 200 series packs will still be available.

4 - 3 0

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

OC-48 Low-speed (tributary interface) DWDM OLIUs

The low-speed OC-48 DWDM OLIUs (LNW421-459) are similar to those mentioned above, except that they are tributary interface circuit packs that any Function Unit group on the DMX shelf (including

Growth slots), and up to 10 ports are addressable when all Function

Unit groups are equipped with the low-speed DWDM circuit packs.

These packs can cross-connect VTs in any 12 of 48 selected STS-1s.

The LNW421, 423, 431, 433, 435, 437, 443, 445,457 packs are no longer available. All other 400 series packs will still be available.

OC-192 OLIU (LNW56)

The OC-192 OLIU (LNW56) circuit pack is an intermediate reach

1550 nm optical line interface unit. The LNW56 supports OC-192 add/ drop, UPSR, and BLSR configurations, single- and dual-homing, nonrevertive linear and bidirectional 1+1 protection switching, and VT1.5,

STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport. The

LNW56 circuit pack can cross-connect VTs in any 48 of 192 STS-1s in the OC-192 signal. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-192 OLIU.

The LNW56 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW56 faceplate.

OC-192 OLIU (LNW57)

The OC-192 OLIU (LNW57) circuit pack is a long reach (80 km)

1533.47 nm optical line interface unit. The LNW57 supports OC-192 add/drop, UPSR, and BLSR configurations, single- and dual-homing, non-revertive linear and bidirectional 1+1 protection switching, and

VT1.5, STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport.

The LNW57 circuit pack can cross-connect VTs in any 48 of 192 STS-

1s in the OC-192 signal. The Stratum 3 timing generator and central

TDM switch fabrics are embedded in the OC-192 OLIU.

The LNW57 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW57 faceplate.

The LNW57 circuit pack utilizes a “dither tone” to frequency modulate the laser. This technique is used to minimize the effects of Stimulated

Brillouin Scattering (SBS).

At high optical launch powers, SBS can cause an acoustic backscattering phenomenon in fibers. The dither tone effectively broadens the spectrum of the narrow optical pulse, thus raising the threshold power where SBS becomes an issue.

Normally, Lucent recommends that optical output of the OC-192 circuit packs be amplified to no more than +10 dBm. However, with the dither tone circuit incorporated into the LNW57, optical

365-372-300

Issue 8.0, September 2006

4 - 3 1

Circuit Pack Descriptions

Product Description

amplification of this circuit pack to much higher power levels is acceptable.

For fibers carrying multiple wavelengths in DWDM systems, it should be noted that the individual channel (individual wavelength) power determine the SBS threshold, not the total composite power of all the channels.

OC-192 OLIU (LNW58)

The OC-192 OLIU (LNW58) circuit pack is a short reach 1310 nm optical line interface unit. The LNW58 supports OC-192 add/drop,

UPSR, and BLSR configurations, single- and dual-homing, nonrevertive linear and bidirectional 1+1 protection switching, and VT1.5,

STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport. The

LNW58 circuit pack can cross-connect VTs in any 48 of 192 STS-1s in the OC-192 signal. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-192 OLIU.

The LNW58 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW58 faceplate.

OC-192 OLIU (LNW59

—

R7.0)

2 port OC-192 VLF Mains (LNW59) support OC-192 add/drop, UPSR, and BLSR configurations, single- and dual-homing, and revertive or non-revertive linear 1+1 protection switching. The LNW59 provides 2 ports capable of supporting 1.3SR1, 1.5IR2, and 1.5LR2 XFPs. It can also function headlessly (with no optics), similar to the LNW80.

For overall capacity, the LNW59 boasts a 20G optical main with a

240G centralized STS switch fabric, 30G centralized VT termination capacity, and 40G VT switch fabric. When DMX is equipped with the

The LNW59 also enables true 0x1 operation amongst the tributary slots. It also enables hairpin cross-connections between unprotected

0x1 interfaces located in the same Function or Growth Unit.

LNW59 supports STS-1, STS-3c, STS-12c, and STS-48c signal transport. The OC-192 OLIU can cross-connect VTs in any 192 STS-

1s. LNW59s may occupy Main slots 1 and 2.

All tributary circuit packs, with the exception of the LNW6 and LNW7 are supported by the LNW59.

4 - 3 2

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

OC-192 OLIU (LNW60)

The LNW60 is based on the LNW57 described above. It has the same characteristics, capabilities, and specifications as the LNW57, but it also includes an on-board, integrated optical amplifier. When the onboard amplifier is in use, the LNW60 is capable of bridging spans of up to 127 km. The LNW60 presents the possibility of savings in CAPEX,

OPEX (no separate management for external optical amplifier required), and space.

OC-192 OLIU (LNW555)

The OC-192 OLIU (LNW555) circuit pack is a long reach (80 km)

1533.47 nm optical line interface unit. The LNW555 supports OC-192 add/drop, UPSR, and BLSR configurations, single- and dual-homing, non-revertive linear and bidirectional 1+1 protection switching, and

VT1.5, STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport.

The LNW555 circuit pack can cross-connect VTs in any 48 of 192

STS-1s in the OC-192 signal. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-192 OLIU.

The LNW555 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW555 faceplate.

OC-192 OLIU (LNW523/527/

LNW554)

The OC-192 OLIU (LNW523/527/554) circuit pack is a DWDM optical line interface units. These DWDM packs support OC-192 add/ drop, UPSR, and BLSR configurations, single- and dual-homing, nonrevertive linear and bidirectional 1+1 protection switching, and VT1.5,

STS-1, STS-3(c), STS-12(c), and STS-48(c) signal transport. These circuit packs can cross-connect VTs in any 48 of 192 STS-1s in the

OC-192 signal. The Stratum 3 timing generator and central TDM switch fabrics are embedded in the OC-192 OLIU.

The LNW523/527/554 may occupy Main slots 1 and 2. Fiber access is provided via a pair of LC-type connectors on the LNW527/554 faceplate.

The LNW523/527/554 employ tunable lasers that support 4 separate frequencies on each of the three packs. The LNW523/527/554 lasers can be made to transmit different frequencies. This feature offers obvious advantages to single frequency circuit packs in that one pack may be ordered and used to support a variety of frequency requirements. Packs can be reused in new applications requiring different frequencies and thus the need to order new packs simply to support different frequencies can, in some cases, be avoided.

The LNW523 is being DA’d and will no longer be available as of

6/30/07.

365-372-300

Issue 8.0, September 2006

4 - 3 3

Circuit Pack Descriptions

Product Description

GbE Private Line (LNW63)

The LNW63 provides 4 PTM ports that can be equipped with

1000BASE-SX/LX/ZX single mode PTMs. Beginning in R7.0,

LNW63 supports an Electrical 100/1000BASE-TX PTM in all ports, though only the 1000BASE-TX rate is supported on the LNW63. The

LNW63 provides data transport at the rate of 1000 Mbps using standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU

G.7041), and standard STS-1 virtual concatenation according to ITU

G.707.

The LNW63 contains 4 internal 1000 Mbps WAN ports supporting enhanced private line services such as low-order virtual concatenation and Link Capacity Adjustment Scheme (LCAS). The LNW63 and

PTM optics are also OSP hardened for outside plant applications. The

LNW63 is an unprotected pack.

Prior to Release 7.0, LNW63 packs could only be placed in Slot 1 of any function group or growth slot in the shelf (A1-G1) and DMX supported a total add/drop capacity of 20 private line GbE ports if all slots are equipped with LNW63 circuit packs.

When DMX is equipped with VLF Main (LNW59) packs, Ethernet packs can occupy both Slot 1 and 2 of a Function or Growth Unit

(where applicable). With VLF Mains and all tributary slots populated with LNW63 packs, DMX provides a total add/drop capacity of 40 private line GbE ports.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW63 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

4 - 3 4

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

10/100T (LNW66) 100BASE-

TX ethernet interface

The 10/100T circuit pack has 24 ports and provides data transport at the rate of 10/100 Mbps using standard ethernet switching IEEE 802.1, standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU

G.7041), and standard STS-1 virtual concatenation according to ITU

G.707. The LNW66 can transmit signals across spans as long as 100 meters. Each LNW66 circuit pack can support 1 packet ring. The

LNW66 is an unprotected pack.

The 10/100T may occupy slot 1 of Function Unit groups A, B, C, and

D, and 96 10/100T ports are addressable when four Function Unit groups are equipped with LNW66 circuit packs. When the LNW66 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

GbE Private Line (LNW64)

Ethernet interface (R7.0)

The LNW64 provides 8 private line, PTM (also known as SFP) GbE ports. The ports can be populated with 8 1000BASE-SX/LX/ZX PTMs or 8 100/1000BASE-TX electrical PTMs, though only 1000BASE-TX rates are supported on the LNW64. LNW64 can also support a mix of 4 electrical and 4 optical PTMs. The LNW64 contains 8 internal VCG ports supporting enhanced private line services such as low-order virtual concatenation (VT1.5) and Link Capacity Adjustment Scheme

(LCAS).

LNW64 is OSP hardened and can only be used with VLF Mains

(LNW59).

LNW64 supports STS-1 and STS-3c cross-connections with or without

VCAT, and STS-12c cross-connections without VCAT. All ports are capable of transmitting at wire speed (1000 Mbps) simultaneously, making full capacity of the pack 168 STS-1s. With VLF Mains,

LNW64 can occupy both slots 1 and 2 of a Function/Growth unit, making the total capacity of a systems fully populated with LNW64s,

80 GbE private line ports.

10/100T (LNW71) Private

Line Ethernet interface

The LNW71 circuit pack conforms to the same specifications as the

LNW66 described above. Yet, rather than supporting packet ring transport (like the LNW66), the LNW71 circuit pack is designed specifically to support Fast Ethernet Private Line applications. Each

LNW71 circuit pack can support 24 private lines. The LNW71 can also support STS-3(c) cross connections instead of virtual concatenation.

The 10/100T-PL may occupy slot 1 of Function Unit groups A, B, C, and D, and 96 10/100T ports are addressable when four Function Unit groups are equipped with LNW71 circuit packs. When the LNW71

365-372-300

Issue 8.0, September 2006

4 - 3 5

Circuit Pack Descriptions

Product Description

1000BASE-SX (LNW67) optical Ethernet interface

circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

The LNW71 is being DA’d and will no longer be available as of 3/1/08.

This 2-port Ethernet interface provides short-reach high-speed optical data transport at the rate of 1 Gb/s using standard ethernet switching

IEEE 802.1, standard encapsulation according to ANSI T1X1.5/2000-

024R4 (ITU G.7041), and standard STS-1 virtual concatenation according to ITU G.707.

The LNW67 is an unprotected pack. Fiber access is provided by two

LC-type connector pairs on the LNW67 faceplate. The LNW67 transmits signals at a wavelength of 850nm. The LNW67 requires the use of multimode fiber cable. Each LNW67 circuit pack can support 2 packet rings or 2 GbE private lines (protected or unprotected).

Prior to Release 7.0, LNW67 packs could only be placed in Slot 1 of any function group or growth slot in the shelf (A1-G1) and DMX supported a total add/drop capacity of 10 optical GbE ports if all slots are equipped with LNW67 circuit packs.

When DMX is equipped with VLF Main (LNW59) packs, Ethernet packs can occupy both Slot 1 and 2 of a Function or Growth Unit

(where applicable). With VLF Mains and all tributary slots populated with LNW67 packs, DMX provides a total add/drop capacity of 20 optical GbE ports.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW67 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

The LNW67 is being DA’d and will no longer be available as of 3/1/08.

1000BASE-LX (LNW68) optical Ethernet interface

While providing the same functionality as the 1G SX interface, the

LNW68 supports long-reach optics. LNW68 transmits signals at a wavelength of 1310nm. The LNW68 requires the use of single-mode fiber cable. Each LNW68 circuit pack can support 2 packet rings. For more information on LNW68, please refer to the section entitled

Ethernet/Data Optical Specifications, in Chapter 10.

The LNW68 is being DA’d and will no longer be available as of 3/1/08.

4 - 3 6

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

1000BASE-X/100BASE-LX

(LNW70) switched Ethernet interface

The LNW70 circuit pack provides four 1000BASE-X (SX, LX, and/or

ZX— very long reach 80km), IEEE 802.3-compliant (1000Mbps) GbE interfaces and four 100BASE-LX IEEE 802.3-compliant (100 Mbps) fast Ethernet interfaces. The LNW70 circuit pack performs protocol transparent filtering and bridging of incoming media access control

(MAC) frames. MAC frames with a destination address on the local bus are filtered by the LNW70 to prevent unnecessary transmission of frames over the wide area network (WAN). The LNW70 is not equipment protected, however, protection is provided via SONET

UPSR/BLSR or through the IEEE 802.1w (or 802.1d) spanning tree algorithm.

The LNW70 can also use electrical PTMs that are provisionable to support either 100BASE-T or 1000BASE-T traffic. The electrical

PTMs can occupy ports 1-4.

The LNW70 uses standard Ethernet switching (IEEE 802.1), standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU G.7041), and standard STS-1 virtual concatenation according to ITU G.707.

Fiber access is provided by LC-type connector pairs on the LNW70 faceplate.

The LNW70 is an unprotected pack by default. R7.0 incorporates support of Link Aggregation on LNW70 LAN ports, which can be used to provide facility protection. For more information on Link

Aggregation, refer to Appendix A.

Prior to R7.0, the LNW70 could only occupy slot 1 of any Function

Unit group on the shelf (including Growth slots), and up to 20

1000BASE-X and 20 100BASE-LX ports were addressable when all

Function Unit groups are equipped with LNW70 circuit packs.

When DMX is equipped with VLF Main (LNW59) packs, Ethernet packs can occupy both Slot 1 and 2 of a Function or Growth Unit

(where applicable). With VLF Mains and all tributary slots populated with LNW70 packs, up to 40 1000BASE-X and 40 100BASE-LX ports are addressable.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW70 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

365-372-300

Issue 8.0, September 2006

4 - 3 7

Circuit Pack Descriptions

Product Description

revenue from) them becomes necessary. LNW70 packs are purchased and shipped with no ports populated with functioning optics. The ports remain empty until the customer decides to place interfaces in them.

4- ports are available for 1000BASE-X (SX and/or LX) optics or 100/

1000BASE-TX electrical interfaces and 4 ports are available for

100BASE-LX optics.

100Mb/GbE Electrical PTM for the LNW70 (R6.0)

The LNW70 now supports a dual function electrical PTM that is provisionable for 100 or 1000 Mbps traffic. It conforms to the

IEEE802.3 standards for 100BASE-T and 1000BASE-T in its respective settings (IEEE802.3z and IEE802.3ab). Connectivity is provided for an RJ-45 Cat 5 cable and the PTM has a maximum span length of 100 meters.

100BASE-LX/100BASE-TX

(LNW74) optical Fast

Ethernet interface

This 24-port Ethernet interface provides 8-ports for optical 100BASE-

LX transport at 100 Mbps using standard ethernet switching IEEE

802.1, standard encapsulation according to ANSI T1X1.5/2000-024R4

(ITU G.7041), and standard STS-1 and VT virtual concatenation according to ITU G.707. The LNW74 also provides 16 electrical ports for the 10/100BASE-TX interfaces. These electrical ports transmit at

10/100 Mbps using standard ethernet switching IEEE 802.1, standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU G.7041), and standard STS-1 and VT virtual concatenation according to ITU

G.707. The LNW74 electrical interfaces can transmit signals across spans as long as 100 meters. The LNW74 is an unprotected pack and is

OSP hardened.

The LNW74 circuit pack is designed specifically to support Fast

Ethernet Private Line applications. Each LNW74 circuit pack can support 24 private lines. The LNW74 can also support STS-3(c) cross connections instead of virtual concatenation.

Prior to Release 7.0, LNW74 could only occupy slot 1 of any Function

Unit group on the shelf (including Growth slots), and up to 40

100BASE-LX ports and 64 10/100BASE-TX ports were addressable when all Function Unit groups are equipped with LNW74 circuit packs.

When used in the Growth slot, only the optical ports can be used.

In R7.0, with use of true 0x1 and LNW59 VLF Main packs, Ethernet packs can be installed in either slot 1 or 2 of Function Unit or Growth groups. DMX does not allow electrical interface packs to occupy adjacent slots within the same Function or Growth unit next to other electrical interface packs. Therefore, two LNW74s can not be installed within the same group. However, beginning in R7.0 (and when VLF

4 - 3 8

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

Mains are used), LNW74 can be installed next to another optical TDM or Ethernet pack with in the same group (ex. LNW74 and LNW67 or

LNW32).

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW74 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

The LNW74 features Pluggable Transmission Module (PTM) optics for all 100BASE-LX interfaces. PTM optics are “pluggable” in the sense that they can be plugged into a circuit pack as they become necessary. This allows customers to grow their network incrementally, only realizing the full cost for optics as the need to provision service on

(and thus receive revenue from) them becomes necessary. LNW74 packs are purchased and shipped with no ports populated with functioning optics. The ports remain empty until the customer decides to place optics in them. 8 ports are available for 100BASE-LX optics.

There are 24 internal WAN ports (capable of transmitting signals to the

MAIN circuit packs) in the LNW74 circuit pack.

FC-DATA Optical SAN interface (LNW73 and

LNW73C- R7.0)

The LNW73 and LNW73C (R7.0) are 4-port Storage Area Networking

(SAN) interface cards designed to facilitate SAN distance extensions via the DMX platform using GFP-T (G.7041). These cards employ standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU

G.7041), and standard STS-1 and VT virtual concatenation according to ITU G.707. For extended FC/FICON interfaces, the LNW73/73c also supports buffer_to_buffer credit management spoofing consistent with ANSI T11 FC-BB-3_GFPT draft standard.

They utilize PTM optics to provide the option of FICON, ESCON, or

Fibre-channel interfaces natively on the DMX shelf. Each pack must be equipped with only one type of PTM (FICON/FC or ESCON). The

LNW73/73c can operate at 1 Gbps or 2 Gbps and in either

Asynchronous or Synchronous transmission modes. When operating in async Fibre Channel (FC) mode, 2 ports are available at 2Gbps FC, or 4 ports at 1Gbps FC, or 1 port at 2Gbps FC and 2 ports of 1Gbps FC.

When operating in synchronous FC mode, 1 port is available at 2Gbps

FC, or 2 at 1Gbps FC.

While the capacity of each port is 2Gbps, the true capacity of each port is relative to the type of PTM it is equipped with. For ESCON traffic, the PTM ports have a capacity of 200 Mbps. The 2Gbps capacity of the ports is sufficient to support FC2G and FICON Express.

While the LNW73 and 73C do support LCAS, the LNW73 only uses

LCAS with asynchronous FC traffic.

365-372-300

Issue 8.0, September 2006

4 - 3 9

Circuit Pack Descriptions

Product Description

The LNW73C differs from the LNW73 in that it enables compression of SAN traffic.

The R7.0 implementation of SAN compression enables a high throughput of up to two full-line rate FC-2G interfaces in a single pack.

The LNW73C is able to compress asychronous Fibre Channel traffic and conserve up to 50% of bandwidth versus uncompressed asynchronous FC traffic in typical applications.

Compression for asynchronous FC traffic is pre-standard and will be standardized by FC-BB-4. The R6.0 implementation of SAN compression enables a high throughput of up to two full-line rate FC-

2G interfaces in a single pack.

Prior to R7.0, the LNW73/73c could only occupy slot 1 of any

Function Unit group on the shelf (including Growth slots). When DMX is equipped with VLF Main (LNW59) packs, FC-DATA packs can occupy both Slot 1 and 2 of a Function or Growth Unit (where applicable).

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW70 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

1000BASE-X/100BASE-LX

(LNW78) RPR Ethernet interface

This 8-port Ethernet interface provides 4-ports for short-reach and/or long-reach high-speed optical data transport at the rate of 1 Gb/s and

4-ports for optical 100BASE-LX transport at 100 Mbps. The first 4 ports (1-4) are for the GbE traffic (ports 3 and 4 are not available in

R7.0) and the second 4 ports (5-8) are for FE traffic. The LNW78 utilizes PTM optics, allowing you to equip additional ports as necessary. In R7.0, LNW78 adds support for the electrical 100/

1000BASE-TX, electrical Ethernet PTM. This PTM may only occupy ports 1 and 2 of the pack. The LNW78 also supports similar port, switching, and traffic management capabilities as the LNW70.

The LNW78 supports standards compliant RPR switching per IEEE

802.17. LNW78 will support one RPR instance in R6.0 and two in the future. The LNW78 provides two internal Virtual Concatenation Group

(VCG) WAN ports (will support 4 in the future) with a total capacity of

2.5 Gbps capacity for Ethernet RPR traffic (24 STS-1s in each direction).

4 - 4 0

365-372-300

Issue 8.0, September 2006

Circuit Pack Descriptions

Product Description

separate shelf using EoS VCGs is also supported. Finally, EoS traffic can be managed with QoS support on EoS VCGs.

Prior to R7.0, LNW78 packs could only be placed in Slot 1 of any function group or growth slot in the shelf (A1-G1) and DMX supported a total add/drop capacity of 10 RPR GbE ports and 20 RPR FE ports if all slots were equipped with LNW78 circuit packs.

Beginning in R7.0, with the use of true 0x1 and the LNW59 VLF Main,

LNW78 can occupy slots 1 and 2 of a Function or Growth group. This can increase the overall capacity of the system to 20 RPR GbE (optical only) ports and 20 RPR FE (optical only) ports per shelf.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW78 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

Detectable blank circuit packs

DMX supports detectable blank circuit packs: LNW98 in unequipped

Function and Growth slots, LNW97 in an unequipped M2.

The WaveStar

Electric Continuity Test

Tool (LNW94)

DMX supports a circuit pack designed to aid technicians in the installation and maintenance of Electrical interfaces and cables. The

Electrical Continuity Test Tool (LNW94) can be placed in any

Function slot on the DMX shelf (NOT including Growth Slots). It is used to test the cables which will be connected to DS1, DS3, or

Ethernet electrical interfaces. LNW94 tests the integrity of electrical cables to both identify where trouble exists and which cables or DSX panels are faulty prior to installation and turn up.

In-service Electric

Continuity Test Tool

(LNW93)

The In-service Electrical Continuity Test Tool (LNW93) test circuit pack is used for upgrades in the DMX high capacity shelf. An inservice shelf might have a function unit with low capacity DS1 (LNW6 or 7) or DS3 (LNW16) packs. When these packs are upgraded with higher capacity packs (DS1, LNW8; DS3, LNW19), as part of the upgrade procedure, new DS1 or DS3 connectorized cables are added to the DSX cross-connect frames and to the DMX shelf. The LNW93 pack is used to test out the new wiring without disrupting traffic on the in-service pack.

The LNW93 is very similar to the LNW94 test tool except that it has no backplane connectors for DS1 ports #1-28 or for DS3 ports #1-12.

365-372-300

Issue 8.0, September 2006

4 - 4 1

Circuit Pack Descriptions

Product Description

Cable Management Bracket

This feature will be available on the detectable apparatus blanks also, but may be phased in; this would allow visibility via the CIT.

4 - 4 2

365-372-300

Issue 8.0, September 2006

Product Description

Passive Optics Units (POUs)

Passive Optics Units

The Passive Optics Units (POUs) are a lower-cost solution to using

DWDM for transmitting large amounts of traffic on one fiber. The shelf fits in a bay frame with DMX. If the POU is used in the same bay frame with DMX, then the number of DMX shelves in that bay frame is limited to three. The POUs do not need any power supply or management system.

POU shelves are available to support the following applications:

• Dual optical add-drop module (OADM): 1, 2, or 4 wavelengths

• Dual optical add-drop module (OADM): one 1310 nm port and four 1550 nm ports

• 16 unidirectional/bidirectional wavelengths: MUX or DMUX

• 32 wavelengths using 16 unidirectional/bidirectional wavelengths

(MUX or DMUX) with a wavelength interleaver used to add another 16 wavelengths: MUXINT or DMUXINT

The following figure shows the POU shelves.

Figure 4-3 Passive Optics Unit (POU) Shelves (DWDM Filter

Units): MUX/DMUX

Common

Lucent Technologies nc-dmx-103

The dimensions of the passive optical unit (POU) are:

Height (mm/inches)

74/2.913

Width (mm/inches)

498/19.606

Depth (mm/inches)

378.64/14.907

365-372-300

Issue 8.0, September 2006

4 - 4 3

Passive Optics Units (POUs)

Product Description

POU Versions

• 16 Channel MUX or DMUX (odd numbered channels): This POU supports unidirectional and bidirectional transmission systems.

• Dual 1-Channel Optical Add Drop: This POU supports unidirectional transmission systems and can add/drop one channel from a DWDM line carrying up to 32 different channels.

• Dual 2-Channel Optical Add Drop: This POU supports unidirectional transmission systems and can add/drop two channels from a DWDM line carrying up to 32 different channels.

• Dual 4-Channel Optical Add Drop: This POU supports unidirectional transmission systems and can add/drop four channels from a DWDM line carrying up to 32 different channels.

• Dual 1310 + 4x1550 MUX/DMUX: This POU provides one I/O port for 1310 nm signals and four I/O ports for 1550 nm signals.

This POU supports unidirectional transmission systems and can

MUX or DMUX a 1310 channel and four 1550 bands to/from a

DWDM line.

Important!

The last four bulleted items in the list above describe the various OADMs and MUX/DMUX as “Dual”.

“Dual” is in reference to the fact that each of these specific POUs are comprised of two complete sets of OADMs or MUX/DMUX units. Thus, the dual 1-channel OADM POU contains 2 OADMs, enabling it to support 1 add/drop in each direction.

4 - 4 4

365-372-300

Issue 8.0, September 2006

Passive Optics Units (POUs)

Product Description

The following figure shows a diagram of transmission with up to 32 wavelengths (channels) being received and passed-through one of the

Add/Drop units. Also, the diagram shows how 1, 2, or 4 wavelengths can be added and/or dropped from a passive DWDM OC-48/192 line using the Add/Drop Units.

Figure 4-4 Add/Drop Unit

Add/Drop Unit

Up to 32

Wavelengths In

Up to 32

Wavelengths Out

1,2, or 4 OC-48/192

Wavelengths Added/Dropped

(# of dropped channels

= # of added channels) nc-dmx-166

365-372-300

Issue 8.0, September 2006

4 - 4 5

Passive Optics Units (POUs)

Product Description

The following figure shows a diagram of transmission with 16 lines transmitting at one end of the fiber and 16 lines receiving at the other end. The 16 port units on each side of transmission may be a combination of OC-192 DWDM OLIUs and/or OC-48 DWDM OLIUs.

Each OLIU is equipped with a bidirectional port (both transmit and receive). The fiber between the two POUs (DWDM Filter Units) on the upper portion of the figure is unidirectional in the east direction. The fiber between the two Passive Optics Shelves on the lower portion of the figure is unidirectional in the west direction. Another Passive

Optics Shelf, with a wavelength interleaver, can be added to transport

32 wavelengths in each direction at the OC-192 or OC-48 rate on one fiber.

Figure 4-5 MUX/DMUX Passive Optics Shelf (16 Transmit at One

End, 16 Receive at the Other End)

16 MUX 16 DMUX

16 OC48 DWDM and / or

OC192 DWDM

Circuit packs

1 Unidirectional

Fiber

16 OC48 DWDM and / or

OC192 DWDM

Circuit packs

16 DMUX

16 MUX

1 Unidirectional

Fiber wbwm02021

4 - 4 6

365-372-300

Issue 8.0, September 2006

Passive Optics Units (POUs)

Product Description

The following figure shows a diagram of bidirectional transmission with eight lines transmitting at one end of the fiber and eight lines receiving at the other end. This is the same POU pictured above, except that it is being used in a bidirectional application. The eight port units on each side of transmission may be a combination of OC-192 DWDM

OLIUs and/or OC-48 DWDM OLIUs. Each OLIU is equipped with a bidirectional port (both transmit and receive). The fiber between the two POU shelves (DWDM filter unit box) is bidirectional (transmit and receive).

Figure 4-6 MUX/DMUX Passive Optics Shelf (8 Transmit and 8

Receive at Each End)

8 Mux 8 Demux

8 OC48 DWDM and / or

OC192 DWDM

Circuit packs

8 OC48 DWDM and / or

OC192 DWDM

Circuit packs

8 Demux

1 Bidirectional

Fiber

8 Mux

8 wbwm02020

Important!

This figure assumes a full set of 8 bidirectional point-to-point cross-connections.

365-372-300

Issue 8.0, September 2006

4 - 4 7

Product Description

External Optical Amplifiers

Overview

The Lucent external optical amplifier provides service providers, system integrators, and network equipment manufacturers with one of the key technologies needed to build next generation DWDM and

OADM networks. With the optical amplifier, operators enhance system performance while minimizing capital expenditures.

The optical amplifier can be configured to provide variable gain between 13 dB and 22 dB. This enables users to optimize optical transmission performance as needs grow. After gain setting is provisioned, the amplifier dynamically controls and maintains signal levels even as the number of amplified wavelengths change.

The amplifier features dynamic transient suppression and gain flattening across C-band to reduce the likelihood of data errors, channel outage, and signal degradation. In dynamic metro access networks or long-haul optical networks, these features allow service providers to provision and deliver reliable wavelength services to their end customers on demand.

The external optical amplifiers are available in front access and rear access versions.

The figure below shows the front access version of the external optical

amplifier, and Figure 4-8 shows the rear access version of the external

optical amplifier.

Figure 4-7 Optical Amplifier (Front Access)

Input

Port

Output

Port

Status

LEDs

Product

Label

RJ45 Alarm

Relay Contact

ESD

Jack

-48VA

-48RTNA

-48VA

-48RTNA

Output

Monitor

Laser

Warning

POWER

FAIL

LOS

Lucent Technologies

RS-232

ALARM OUT

LAN

-48VA

-48RTNA

RS-232

Craft Port

RJ45 LAN Port -48VB

-48RTNB

MA-DMX-297

4 - 4 8

365-372-300

Issue 8.0, September 2006

External Optical Amplifiers

Product Description

Figure 4-8 Optical Amplifier (Rear Access)

Input

Port

Output

Port

Status

LEDs

POWER

FAIL

LOS

Lucent Technologies

Laser

Warning

Output

Monitor

RS-232

Craft Port

ESD

Jack

Product

Label

MA-DMX-298

Interfaces

The optical amplifiers provide a 10/100 Mbps and an RS-232 port for operations and maintenance communications (similar to DMX). The optical amplifier continuously monitors its own electrical and optical performance. If operating parameters exceed user-specified thresholds, autonomous alarms are reported.

The optical amplifier may be managed by any of the following means:

• Simple Network Management Protocol (SNMP Version 1 and 2c)

• TL1 messages (GR-833 CORE)

• File Transfer Protocol (FTP) (RFC 956)

• Alarm relay contact closures.

For more information about the Lucent external optical amplifiers, consult your account executive.

365-372-300

Issue 8.0, September 2006

4 - 4 9

Product Description

Control

Overview

DMX provides extensive control features, accessible through a number of technician and operations system (OS) interfaces. In addition to accessing local DMX NEs through direct interfaces, technicians and

OSs can use the operations features supported via the DCC in the optical signals to access remote NEs. Control functions are supported by the SYSCTL circuit pack.

Beginning in R6.0 DMX requires an upgrade to the LNW2 SYSCTL.

The LNW1 supports all software releases prior to R6.0, but the LNW2 must be used for R6.0 and going forward.

Three-tiered operations interface

DMX maintenance procedures are built on three levels of system information and control. The first tier is provided by the LEDs, displays, and push-button switches located on the faceplate of the

SYSCTL circuit pack. The second tier uses a DMX PC-CIT to provision and retrieve detailed reports of performance monitoring, alarm and status, and system configuration for both local and remote

NEs. The third tier uses the OS interfaces such as TL1 and TL1 over

IAO LAN (TCP/IP or OSI) or PC-CIT to monitor performance, gather alarm information, and configure the system. Also, the IAO LAN interfaces provisioned for TCP/IP support software download and provisionable database backup/restore via FTP.

SYSCTL faceplate

The faceplate of the SYSCTL circuit pack contains indicators that provide system-level information and control functions. The condition of the individual transmission circuit packs can be determined using faceplate LEDs.

The figure on the following page, shows the SYSCTL faceplate. There is a 35-segment numeric LED display and three push-button switches for Update/Initialize (UPD/INIT), ACO/test (ACO/TEST), and Select

(SEL) for local operations.

4 - 5 0

365-372-300

Issue 8.0, September 2006

Control

Product Description

In addition to the Active and FAULT LED, there are also seven alarm/ status LEDs on the SYSCTL faceplate, listed below. The FAULT LED is lit if the SYSCTL detects its own failure:

• Critical (CR)

• Major (MJ)

• Minor (MN)

• Abnormal (ABN)

• Far End Activity (FE)

• Near End Activity (NE)

• Alarm Cut-Off (ACO)

Figure 4-9 SYSCTL Circuit Pack (LNW2)

SEL

UPD

INT

LAN

CIT

232

ACO

TST

IND

Active

FAULT

ABN

Active

CrItical

Minor

Far End

Fault

Major

Abnormal

Near End

ACO

ACO/TST (Push-button)

IND (35 segment

Alphanumeric LED display)

SEL (Switch)

UPD/INIT (Switch)

IAO LAN Port

Serial Port (RS232)

Nc-dmx-009

365-372-300

Issue 8.0, September 2006

4 - 5 1

Control

Product Description

Embedded operations channel

Access and control extends beyond the local DMX to remote network elements via the SONET section data communications channel (DCC).

Craft interface dialogs and operations messages are exchanged in the

DCC overhead bytes on each OC-3, OC-12, OC-48, and OC-192 interface.

4 - 5 2

365-372-300

Issue 8.0, September 2006

Product Description

Power Specifications

Power supply

The following table lists DMX High Capacity shelf power requirements.

Table 4-4 DMX 30 Amp High Capacity Shelf Power Supply

Requirements

Item

Voltage range, all components

Description

-40.0V to -60.0V

Power Feeders two -48V power feeders

[BREAKER (A) and BREAKER (B)]

Circuit Breakers (two per shelf) 30.0 A

The following table lists DMX 20 Amp High Capacity shelf power requirements.

Table 4-5 DMX 20 Amp High Capacity Shelf Power Supply

Requirements

Item

Voltage range, all components

Power Feeders

Description

-40.0V to -60.0V

two -48V power feeders

[BREAKER (A) and BREAKER (B)]

Circuit Breakers (two per shelf) 20.0 A

Circuit breakers

DMX uses on-board power conversion eliminating the need for slots for bulk power converters. Two independent -48V office power feeders

(A and B) enter the shelf through connectors and are filtered and distributed to the circuit packs through circuit breakers. Power conversion is performed through modular power converters located on the circuit packs. In each circuit pack, the feeders are diode ORed, fused, filtered, and regulated by the board-mounted power modules.

This provides the required redundancy in case of the loss of one feeder or circuit breaker. The green Power LEDs located next to each circuit breaker (A and B) indicate power is being fed to the breaker.

365-372-300

Issue 8.0, September 2006

4 - 5 3

Power Specifications

Product Description

Current drains

The following table provides the maximum and average current drain requirements for a shelf if only one feeder is present.

Table 4-6 High-capacity Shelf Current Drains

Shelf Current Drains in Amperes

Typical @

−

48V

DMX High Capacity Shelf 6.3

Maximum

−

23.0

48V

Typical

−

40V

7.5

Maximum

−

40V

27.5

The following table provides the maximum and average current drain requirements for a bay equipped with four high-capacity shelves.

Table 4-7 Bay Current Drains

Bay Current Drains

Typical @

−

48V

Maximum

−

48V

25.2

92.0

Typical

−

40V

30.0

Maximum

−

40V

110.0

Bay equipped with four

DMX High Capacity

Shelves

The following table provides the maximum and typical heat dissipation figures for the High Capacity Shelf.

Table 4-8 High-capacity Shelf Heat Dissipation

Shelf

DMX High Capacity

Heat Dissipation in Watts

Typical @

−

48V

Maximum

−

48V

302 1100

Typical

−

40V

300

Maximum

−

40V

1100

4 - 5 4

365-372-300

Issue 8.0, September 2006

Product Description

DMX 20 Amp Shelf Power Specifications

Overview

The table below provides the current drains for various configurations populating the Metropolis

DMX Access Multiplexer 20 Amp shelf.

These configurations demonstrate that it is highly unlikely that any configuration available through R6.0 would have a current drain exceeding the maximum power supply of the 20 Amp shelf.

The packs used in these calculations were chosen because they require the greatest power supply of any pack in their individual class (service type). Also, all configurations contain protected network interfaces

(high-speed <HS>). Therefore, these are truly the maximum current drains for the listed configurations.

Configuration Circuit Pack Slot Equipage Current Drain of

Configuration

High-density DS1/E1 shelf:

HS OC-48 with 224DS1/E1s

High-density DS3 shelf:

HS OC-192 with 192 DS3s

Hybrid Shelf:

HS OC-192

1- 2 port GbE pack

2- 48 port DS3 packs

2- 4 port OC-3 packs

2- 2 port OC-12 pack

Max Optical Shelf

HS OC-192 and full set of OC-48 LS

Max data shelf:

HS OC-192

5 GbE packs

Fan + LNW1/2+ 2 LNW77s + 8

LNW8s

Fan + LNW1/2 + 2 LNW55xs +

8 LNW19s

Fan + LNW1/2 + 2 LNW55xs +

1 LNW67 or 68 + 2 LNW192

+ 2 LNW36s + 2 LNW46s

Fan + LNW1/2 + 2 LNW55xs +

10 LNW31s

Fan + LNW1/2 + 2 LNW55xs +

5 LNW67 or 68s

12.07 amps

10.57 amps

9.93 amps

12.95 amps

10.7 amps

365-372-300

Issue 8.0, September 2006

4 - 5 5

Product Description

Cabling

Overview

This section briefly describes cabling information, including the number of particular cables required.

Cable types

The table below lists available cables along with the required number

(if any).

Table 4-9 Cables

Cable Assembly Description

Power

DS1/E1

Quantity per Shelf

1 per shelf

1 per Function Unit housing a

28DS1 circuit pack

—

LNW6/7(as required)

2 per Function Unit housing 56DS1/

—

LNW8

DS3/EC1/TransMUX

12 conductors

DS3/EC1/TransMUX (highcapacity)

24 conductors

LNW93 and LNW94 cable kit

(comcode 848957437)

1 per Function Unit housing a

LNW16 or LNW18 circuit pack (as required)

2 per Function Unit housing a

LNW19/19B or LNW20 circuit pack (as required)

1 per LNW93 or LNW94 Test Pack

(as desired by customer)

Office Alarm

Office Alarm Mult

Miscellaneous Discrete (right angle connector)

Miscellaneous Discrete (straight connector)

LAN 10/100 BaseT (Crossover)

LAN 10/100 BaseT (Straight

Through)

1 (bottom shelf in bay frame only) 4

1 for any adjacent shelves (as required)

1 per shelf (as required), Standard

Shelf only

1 per shelf (as required), Highcapacity Shelf only

1 per shelf (as required) Standard and High-capacity Shelf

See Note

4 - 5 6

365-372-300

Issue 8.0, September 2006

Cabling

Product Description

Cable Assembly Description

LAN 100 BASE-TX

Sync Timing

PC-CIT Interface

Modem Cable Assembly

Quantity per Shelf

1 per Function Unit (as required)

1 per shelf (as required)

1 per shelf (as required), Standard and High-capacity Shelf

See Note

Table notes

1. One cable assembly supports both the -48VA and -48VB main power feeders on the DMX shelf. Cable assemblies are available in 2,4, 6, and 10 AWG cable kits including the required Storey connectors for connection a the shelf. The connectors are also available seperately for customers who choose to supply their own cable.

2.One DS1 Cable Assembly provides one input and one output cable for

28 DS1s, i.e. for one DS1 function group, e.g.: “J1 A OUT” & “J2 A

IN” used on both the standard and high capacity shelf. Two DS1 Cable

Assemblies are required for the high capacity 56DS1 LNW8, i.e. for 2 function groups, e.g.: “J1 A OUT” & “J2 A IN” and “J24 A OUT” &

“J24 A IN”. The DS1 Cable Assembly consists of two separate cables, each containing 28 pairs of 24 gauge shielded cable. On each of the 28 pairs of cable, cable 1 is for input and cable 2 is for output.

3. One DS3/EC1 Cable Assembly (12 conductors) provides one input and one output cable for 12 DS3/EC-1s (LNW16) or TransMUXs

(LNW18), i.e. for one “12DS3/EC-1 or TransMUX” function groups, e.g.: for “J1 A OUT” and “J2 A IN”.

One DS3/EC1 Cable Assembly (24 conductors) provides one input and one output cable for up to 24 signals, i.e. for the first 12 of 24 connectors used for the LNW16 or LNW18 function groups, e.g.: for “J1

A OUT” and “J2 A IN”.

Two assemblies are required for the high capacity 48DS3 (LNW19), e.g.: “J1 A OUT” & “J2 A IN” and “J24 A OUT” & “J24 A IN”.

4. One Office Alarm Cable Assembly is required for the bottom DMX shelf in a bay frame. Other DMX shelves in the bay frame do not require this assembly, but may use the Office Alarm Mult (J13) cables.

5. One Office Alarm Mult Cable Assembly is required for any adjacent

DMX shelves in a bay frame (above the lowest shelf). For example, if four DMX shelves are located in a single 7-foot bay frame, three cable assemblies are required. These cables cannot reach any further than an adjacent shelf.

6. The Crossover cable is used when connecting to a PC. The Straight

365-372-300

Issue 8.0, September 2006

4 - 5 7

Cabling

Product Description

Through cable is used when connecting with a hub.

7. This cable kit is an accesory to the LNW93 or LNW94 and is meant to aid in testing procedures. It is not critical to the use and function of these packs, but han help ease cabling in testing procedures. The kit contains the folowing cables:

(1) BNC-BNC DS3 3-foot cable

(1) BNC-LCP DS3 3-foot cable

(1) Bantam-Bantam DS1 3-foot cable

(1) RJ45 - RJ45 LAN Patch Cord

(1) DB9-DB9 connector cable for the RS232 port (6 feet)

4 - 5 8

365-372-300

Issue 8.0, September 2006

Cabling

Product Description

LNW70 faceplate cabling guidelines

The LNW63/64/70/78 can use both optical and electrical PTM transceivers. The figure below shows the connections to the electrical

PTM transceivers. The RJ45 cables that connect to the BASE-T-C1 and

FE/GbE Electrical PTM will be directed downward at a 45 o angle. In order to ensure proper cable routing, the copper cables must be above any optical cables/attenuators, etc. that may be installed.

The first four ports of the LNW70 can be used for either optical or electrical PTM transceivers. So, if there’s a plan to have electrical

PTMs in the pack at any point, the user should reserve the first four ports for electrical PTMs and install any optical PTMs in the bottom four sockets. If there is no plan to have electrical PTMs in the pack, optical PTMs may reside in any socket.

For more information on the LNW70 refer to 1000BASE-X/100BASE-

LX (LNW70) switched Ethernet interface (4-37).

For detailed information on all PTMs available, refer to Allowed PTM

Tranceivers (10-109) and the sections that follow.

Figure 4-10 LNW70 Faceplate

MA-DMX4377

365-372-300

Issue 8.0, September 2006

4 - 5 9

Cabling

Product Description

4 - 6 0

365-372-300

Issue 8.0, September 2006

5 System Planning and

Engineering

Overview

Purpose

This section summarizes basic system planning and engineering information to plan procurement and deployment of the DMX Access

Multiplexer. There are a number of considerations that should be kept in mind when planning the DMX’s role in the network. Projected customer requirements will determine initial capacity needed, as well as evolution to higher capacities. The advanced networking capabilities of the DMX offer many economic and planning benefits, and certain guidelines should be followed to maximize these benefits. Physical installation considerations will be guided by the installation location

(central office, uncontrolled, or customer locations). Initial network configuration will determine synchronization requirements.

Synchronization should be planned on a network basis considering items like topology, reliability, internetwork connectivity, and service evolution.

Contents

The following sections are included in this chapter:

Physical Arrangements

Cross-connections

Synchronization

365-372-300

Issue 8.0, September 2006

5 - 1

System Planning and Engineering

Physical Arrangements

Overview

Purpose

This section describes the possible physical arrangements of the DMX

Access Multiplexer.

Contents

The following physical arrangement considerations are covered in this section:

Shelf Configurations

Medium and Large Fabric Engineering Rules

Environmental Considerations

Network Bay Frames

Typical Bay Arrangement

Cabinet Arrangements

Cabling

5 - 2

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Shelf Configurations

Overview

DMX is designed to provide a vast array of wideband and broadband voice and data services. Therefore, there is great flexibility in the configuration of the shelf. Various combinations of circuit packs may be used for whatever service is desired. The following paragraphs outline the specific packs that may be used in the Function Unit groups for certain applications.

Important!

Please refer to the following section entitled

“Medium Fabric Engineering Rules” for important information regarding the functioning and capacities of circuit packs with the medium-sized switch fabric (such as the LNW48, LNW50,

LNW26B, LNW28, LNW31, LNW77, LNW121B-159B and

LNW421-459).

Refer to the section entitled Very Large Fabric (VLF) Engineering

Rules for important information regarding circuit pack slot equipage and electrical/optical interface compatibility with regard to use of the LNW59 VLF Main packs.

Requirements

DMX has the following shelf configuration requirements:

• The Main Switch Pack (LNW80) may be located in the main M1 and M2 slots for protected service

• OC-12 OLIU LNW48, LNW50, LNW54 must be located in the main M1 and M2 slots for protected service

• OC-48 OLIUs LNW26B, LNW27, LNW28, LNW29, LNW32,

LNW76, LNW77, LNW121B-LNW159B, and LNW221-259 must be located in the main M1 and M2 slots for protected service

• OC-192 OLIUs LNW56, LNW57, LNW58, LNW59, LNW60,

LNW523, LNW527, LNW554, and LNW555 must be located in the main M1 and M2 slots for protected service

• The LNW36, LNW37, and LNW45 (OC-3), LNW46 and LNW49

(OC-12), and LNW31, LNW62, and LNW421-459 (OC-48) packs may be used interchangeably. The Function slots 1 and 2 of a particular group (A, B, C, D, or G) need not be populated with the same pack.

• The service and protection slots of a function unit (for example,

A1 and A2) and growth slots G1 and G2 must contain the same circuit pack type except when running in unprotected scenarios.

365-372-300

Issue 8.0, September 2006

5 - 3

Shelf Configurations

System Planning and Engineering

Beginning in R7.0, with the use of VLF Main packs (LNW59),

DMX supports true 0x1 configurations, wherein slots 1 and 2 of a group can be populated with two working packs of the same kind, or with different working packs (certain restrictions apply).

Whenever a companion slot is left empty, an apparatus blank must be placed in the other slot of that group regardless of what software release or Main packs are installed in the shelf.

• The electrical interface circuit packs (LNW6, LNW7, LNW8,

LNW16, LNW18, LNW19/19B, and LNW20) must be located in function unit slots A - D. Growth slots do not support electrical interface circuit packs. Yet, the LNW20 can be installed in the

Growth slots where it functions in portless mode only. LNW6 and

LNW7 circuit packs are not supported with the use of the LNW59

VLF Main packs.

• Prior to R7.0, the Gigabit Ethernet circuit packs (1G SX, 1G LX, and RPR) must be located in slot 1 of a function unit (including growth slots). The other slot must contain a 177D apparatus blank or an LNW98 detectable blank circuit pack. With R7.0 and later releases, when the VLF Main packs are used, Ethernet packs can be used in both slots of a group. Certain restrictions apply. Refer

• Prior to R7.0, the FC-DATA SAN circuit packs (LNW73/73C) must be located in slot 1 of a function unit (including growth slots). The other slot must contain a 177D apparatus blank or an

LNW98 detectable blank circuit pack. With R7.0 and later releases, when the VLF Main packs are used, SAN packs can be used in both slots of a group. Certain restrictions apply. Refer to

• Prior to R7.0, 10/100T (LNW66) and 10/100-PL (LNW71) circuit packs must be located in slot 1 of a function unit. The other slot must contain a 177D apparatus blank or an LNW98 detectable blank circuit pack. Growth slots G1 and G2 do not support the 10/

100T and 10/100-PL circuit packs. With R7.0 and later releases, when the VLF Main packs are used, some Ethernet packs can be used in both slots of a group. Certain restrictions apply. For instance, LNW71 and LNW74 cannot be used for true 0x1 configurations and must be housed in Slot 1 of a function unit or growth group. Refer to

restrictions apply. Refer to

• Prior to R7.0, the Fast Ethernet Private Line circuit pack

(LNW74) must be located in slot 1 of a function unit. The other slot must contain a 177D apparatus blank or an LNW98 detectable blank circuit pack. The LNW74 can be used in G1 as well, but only the optical ports will function (true for all Releases). With

5 - 4

365-372-300

Issue 8.0, September 2006

Shelf Configurations

System Planning and Engineering

R7.0 and later releases, when the VLF Main packs are used, some

Ethernet packs can be used in both slots of a group. Certain

Very Large Fabric (VLF) Engineering

Rules

• The SYSCTL LNW2 circuit pack must be located in the control

CTL slot.

• An apparatus blank (177D or 177E) or detectable blank circuit pack (LNW97 or LNW98) must be used in every unequipped slot.

365-372-300

Issue 8.0, September 2006

5 - 5

System Planning and Engineering

Shelf Configurations

Overview

This section provides lists detailing the kind of circuit packs that can be used to support various applications. Note that the LNW59 (R7.0) VLF

Main pack provides 2 sets of ports on the faceplate. Each set of 2 ports can function independently, meaning that both need not be provisioned for the same application (or e populated with PTMs at all). Therefore, with VLF Mains and R7.0 software, a shelf could be both a BLSR and

UPSR shelf simultaneously (or BLSR and 1+1, 1+1 and UPSR etc).

STS-1/STS-3c/STS-12c/

STS-48c/VT1.5 UPSR shelf

The STS-1/STS-3c/STS-12c/STS-48c/VT1.5 UPSR shelf configuration has OC-12, OC-48, or OC-192 OLIUs in the main M1 and M2 slots and can house the following circuit packs in various combinations:

• 28DS1 (LNW6)

• 28DS1PM (LNW7)

• 56DS1/E1 (LNW8)

• 12DS3/EC-1 (LNW16)

• 48DS3/EC-1 (LNW19/19B)

• 48DS3/EC-1/TMUX (LNW20)

• TMUX (LNW18)

• OC-3 OLIU (LNW36 and LNW37—

4-ports each or LNW45— 8-ports)

• OC-12 OLIU (LNW46— 2-ports or LNW49— 4-ports)

• OC-48 OLIU (LNW31, LNW62, and LNW421 - LNW459)

• 10/100T

• 10/100-PL

• 1000BASE-LX/SX/ZX

• 1000BASE-X/ 100BASE-LX

• 100BASE-LX/ 10/100 BASE-TX

• RPR

• FC-DATA (SAN)

Note that the OC-3/OC-12/OC-48 OLIUs are required for STS-3c/

STS-12c/STS-48c UPSR configurations. The OC-3/OC-12/OC-48

OLIUs can also be used in STS-1/VT1.5 configurations. The LNW62 has 4 ports, all other OC-48 packs have 1 port. For detailed information

5 - 6

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

on circuit packs, including shelf equipage rules and port densities, refer

BLSR shelf

The BLSR shelf configuration has OC48 or OC-192 OLIUs in the main

M1 and M2 slots and the following circuit packs in various combinations:

• 28DS1 (LNW6)

• 28DS1PM (LNW7)

• 56DS1/E1 (LNW8)

• 12DS3/EC-1 (LNW16)

• 48DS3/EC-1 (LNW19/19B)

• 48DS3/EC-1/TMUX (LNW20)

• TMUX (LNW18)

• OC-3 OLIU (LNW36 and LNW37—

4-ports each or LNW45— 8-ports)

• OC-12 OLIU (LNW46— 2-ports or LNW49— 4-ports)

• OC-48 OLIU (LNW31, LNW62, and LNW421 - LNW459)

• 10/100T

• 10/100-PL

• 1000BASE-LX/SX/ZX

• 1000BASE-X/ 100BASE-LX

• 100BASE-LX/ 10/100 BASE-TX

• RPR

• FC-DATA (SAN)

The LNW62 has 4 ports, all other OC-48 packs have 1 port. For detailed information on circuit packs, including shelf equipage rules and port densities, refer to

DCS shelf (Using Main

Switch pack)

The DCS shelf configuration has the Main Switch pack (LNW80) or the VLF Main pack (LNW59) with no PTMs installed in the main M1 and M2 slots and the following circuit packs in various combinations:

• 28DS1 (LNW6)

• 28DS1PM (LNW7)

• 56DS1/E1 (LNW8)

• 12DS3/EC-1 (LNW16)

• 48DS3/EC-1 (LNW19/19B)

365-372-300

Issue 8.0, September 2006

5 - 7

System Planning and Engineering

• 48DS3/EC-1/TMUX (LNW20)

• TMUX (LNW18)

• OC-3 OLIU (LNW36 and LNW37—

4-ports each or LNW45— 8-ports)

• OC-12 OLIU (LNW46— 2-ports or LNW49— 4-ports)

• OC-48 OLIU (LNW31, LNW62, and LNW421 - LNW459)

• 10/100T

• 10/100-PL

• 1000BASE-LX/SX/ZX

• 1000BASE-X/ 100BASE-LX

• 100BASE-LX/ 10/100 BASE-TX

• RPR

• FC-DATA (SAN)

The LNW62 has 4 ports, all other OC-48 packs have 1 port. For detailed information on circuit packs, including shelf equipage rules and port densities, refer to

OC-12/OC-48/192 linear shelf

The OC-12/48/192 linear shelf configuration has OC-12/48/192 OLIUs in the main M1 and M2 slots and the following circuit packs in various combinations:

• 28DS1 (LNW6)

• 28DS1PM (LNW7)

• 56DS1/E1 (LNW8)

• 12DS3/EC-1 (LNW16)

• 48DS3/EC-1 (LNW19/19B)

• 48DS3/EC-1/TMUX (LNW20)

• TMUX (LNW18)

• OC-3 OLIU (LNW36 and LNW37—

4-ports each or LNW45— 8-ports)

• OC-12 OLIU (LNW46— 2-ports or LNW49— 4-ports)

• OC-48 OLIU (LNW31, LNW62, and LNW421 - LNW459)

• 10/100T

• 10/100-PL

• 1000BASE-LX/SX/ZX

• 1000BASE-X/ 100BASE-LX

5 - 8

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

• 100BASE-LX/ 10/100 BASE-TX

• RPR

• FC-DATA (SAN)

The LNW62 has 4 ports, all other OC-48 packs have 1 port. For detailed information on circuit packs, including shelf equipage rules and port densities, refer to

Assignment of VT Bandwidth on OC-48 and OC-12 Highspeed Interface

Single and dual homing shelf

The single homing and dual homing shelf configurations has OC-12,

OC-48 or OC-192 OLIUs in the main M1 and M2 slots and require at least one of the following circuit packs:

• OC-3 OLIU (LNW36 and LNW37—

4-ports each or LNW45— 8-ports)

• OC-12 OLIU (LNW46— 2-ports or LNW49— 4-ports)

• OC-48 OLIU (LNW31)

• OC-48 OLIU (LNW62)

• OC-48 OLIU (LNW421 - LNW459)

If an OC-3 shelf is homing to DMX, the LNW36, LNW37, LNW45 circuit pack must occupy at least one function unit or growth group

(with VLF Main packs (LNW59) and R7.0 software, the other slot of a function unit or growth group can be occupied with a different OLIU or a faceplate-based Ethernet pack). If an OC-12 shelf is homing to DMX, the LNW46 or LNW49 must occupy at least one function unit or growth group. If an OC-48 shelf is homing to DMX, the LNW31,

LNW62, or LNW421 - LNW459 circuit pack must occupy at least one function unit or growth group. It is possible to home to OC-3, OC-12, and/or OC-48 rings on the same shelf. Any other circuit pack may occupy other function units depending on the desired service.

365-372-300

Issue 8.0, September 2006

5 - 9

System Planning and Engineering

Medium and Large Fabric Engineering Rules

Overview

This section describes the functionality and limitations resulting from the use of the medium-sized switch fabrics in certain high-speed circuit packs. Use this section to help plan the use of circuit packs in Main slots of the DMX shelf. Because of the smaller switch fabric in these cards, they are less costly, but this smaller switch fabric cannot handle the same volume of cross-connects as the full-sized switch fabric (48

STS-1). The use of these cards therefore results in certain cross-connect restrictions as described below.

Medium Fabric Cards

The table below lists the DMX circuit packs equipped with the medium-sized switch fabric mentioned above.

Table 5-1 Circuit packs with medium sized switch fabric

Circuit Pack Apparatus

Code

Slot(s)

LNW26B M1, M2

Release Comments

OC-48 OLIU

(1 port)

LNW28

LNW77

LNW121B to

LNW159B

LNW48

OC-12 OLIU

(1 port)

LNW50

LNW54

M1, M2

2.0

1.0

High-speed, long reach, 1310nm, 12 STS-1

VT fabric

High-speed, long reach, 1310nm, 12 STS-1

VT fabric

, OSP Hardened

2.0

High-speed, intermediate reach, 1310nm, 12

STS-1 VT fabric

2.0 and 2.1

High-speed 16 DWDM circuit packs. 32 different wavelengths in the 1550 nm range. The

121B series supports 12

STS-1

VT fabric.

3.1

5.1

High-speed, Intermediate reach. 1310 nm, OSP

Hardened, 12 STS-1 VT fabric

High-speed, Long reach. 1310 nm, OSP

Hardened, 12 STS-1 VT fabric

High-speed, Long reach. 1550 nm, OSP

Hardened, 12 STS-1 VT fabric

5 - 1 0

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Differences at the Shelf

Level

This sections describes the impact of medium-size fabric cards versus full-size fabric cards at the shelf level.

Shelf with Large-sized Fabric Main Circuit Packs

The figure below shows the DMX shelf with MAIN circuit packs containing 48 STS-1-VT switch fabric. The capabilities of the switch fabric and each function unit are described below the figure.

Figure 5-1 DMX with large fabric Main circuit packs

Main 1

48 STS-VT Fabric

Main 2

48 STS-VT Fabric

FN a

1 2

FN b

1 2

FN g

1 2

FN c

1 2

FN d

1 2

STS-1

Electrical

Optical

STS-1

Electrical

Optical

STS-1

Optical

Only

STS-1

Electrical

Optical

STS-1

Electrical

Optical

MA-DMX-399

• Function Groups A, B, C, and D are general purpose slots and support all low-speed circuit packs except certain packs associated with R7.0 (LNW62 and LNW64).

• Function Group G is referred to as the growth slot. The growth slot supports only optical, low-speed circuit packs, these includes all of the OC-3/12 & 48 port cards as well as the LNW67 SX GbE

& LNW68 LX GbE cards. Also in release 5.0/5.1, the growth slot supports new Ethernet hardware. The new hardware supported are the LNW70, LNW73, and LNW74 port cards. Certain packs associated with R7.0 are not supported (LNW62 and LNW64).

Growth slots can also house LNW20 TransMUX packs functioning in portless mode.

• All function groups have an STS add/drop capacity of 48 STS-1s.

365-372-300

Issue 8.0, September 2006

5 - 1 1

System Planning and Engineering

Shelf with Medium-sized Fabric Main Circuit Packs

The figure below shows the DMX shelf with MAIN circuit packs containing 12 STS-1-VT switch fabric. The capabilities of the switch fabric and each function unit are described below the figure.

Figure 5-2 DMX with medium fabric Main circuit packs

Main 1

12 STS-VT Fabric

Main 2

12 STS-VT Fabric

FN a

1 2

FN b

1 2

FN g

1 2

FN c

1 2

FN d

1 2

STS-1

Electrical

Optical

STS-1

Electrical

Optical

STS-1

Optical

Only

STS-1

Electrical

Optical

STS-1

Electrical

Optical

MA-DMX-400

• Function Groups A, B, C, and Dare general purpose slots and support all low-speed circuit packs, except certain packs associated with R7.0 (LNW62 and LNW64).

& LNW 68 LX GbE cards. Also in release 5.0/5.1, the growth slot will support new Ethernet hardware. The new hardware supported are the LNW70, LNW73, and LNW74 port cards. Certain packs associated with R7.0 are not supported (LNW62 and LNW64).

• Function groups A, B, and C have an STS add/drop capacity of 24

STS-1s. This is a hardware-based restriction imposed by the use of the medium-sized STS switch fabric in the MAIN cards.

• Function groups D and G have an STS add/drop capacity of 48

STS-1s.

5 - 1 2

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Engineering Restrictions at the Circuit Pack Level

This section describes engineering/cross-connection restrictions relative to the use of medium-sized switch fabric cards.

OC-12 medium fabric (LNW48/50/54)

The LNW48, LNW50, and LNW54 employ a 12 STS-1/VT1.5 switch fabric with the following capacity:

• 784x784 VT matrix

• 216x216 STS matrix

Function Groups A, B, and C support 24 STS-1 add/drop capacity

• Additional pass-through traffic is supported

• Any circuit pack with a capacity of 48 STS-1s is limited to 24

STS-1s (ex. 24 DS-3 add/drop capacity with LNW19)

• 1 virtual concatenation group (VCG) pair is accessible to GbE circuit packs

Function Groups D and G support 48 STS-1 add/drop capacity

• Full add/drop capacity to circuit packs capable of 48 STS-1s

OC-48 medium fabric (LNW26B/LNW28/LNW77, LNW121B-159B)

The OC-48 packs listed above employ a 12 STS-1/VT1.5 switch fabric with the following capacity:

• 784x784 VT matrix

• 288x288 STS matrix

Function Groups A, B, and C support 24 STS-1 add/drop capacity

• Additional pass-through traffic is supported

• Any circuit pack with a capacity of 48 STS-1s is limited to 24

STS-1s (ex. 24 DS-3 add/drop capacity with LNW19)

• 1 virtual concatenation group (VCG) pair is accessible to GbE circuit packs

Function Groups D and G support 48 STS-1 add/drop capacity

• Full add/drop capacity to circuit packs capable of 48 STS-1s

OC-48/192 large fabric (LNW27/29/LNW32/LNW76, LNW221B-

259B, LNW58, LNW527/554/555)

The OC-48/192 packs listed above employ a larger, 48 STS-1/VT1.5 switch fabric with the following capacity:

• 2688x2688 VT matrix

365-372-300

Issue 8.0, September 2006

• 432x432 STS matrix (for OC-48);

720x720 STS matrix (for OC-192)

5 - 1 3

System Planning and Engineering

Function Groups A, B, C, D, and G support 48 STS-1 add/drop capacity

• Full add/drop capacity to circuit packs capable of 48 STS-1s

• Two VCG pairs are accessible to GbE circuit packs

Source/Destination

Engineering Rules

Due to hardware limitations in medium-fabric Mains, crossconnections may be denied even though the capacity of the crossconnect fabric has not been exceeded.

The source and destination for VT1.5 cross-connections are designated according to the priorities listed below. In any VT1.5 cross-connect pair, the Function Group (FN) closer to the left will always be the source. Therefore, in any cross-connect that utilizes the Main switch fabric, the Main group will be the source.

Source <<<<<<<<<<<<<<<<

Main<<FNA<<FNB<<FNC<<FND<<FNG

Destination

In addition to the position of the shelf, source/destination demarcation is also determined by the STS number. The lower STS number is the source and the higher STS number is the destination.

Once a cross-connect utilizing a VT1.5 within an STS-1 is established, no part of that STS-1 can be used in a cross-connect to a slot/group on the other side of the shelf. For example, if a VT1.5 from an STS-1 entering the shelf at Function Group B1 (FNB1) was cross-connected to FNA1, another VT1.5 in that same STS-1 could not be cross connected to FNC, FND, or FNG.

Cross-connections made with the LNW6 and LNW7 circuit packs are exceptions to this rule. These packs are always the cross-connect

destination. Hairpin cross-connections between these packs are not allowed.

Intra-port hairpins are supported by DMX. Yet when a DMX is equipped with medium fabric mains, intra-port hairpinns are not allowed.

5 - 1 4

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Very Large Fabric (VLF) Engineering Rules

Overview

This section describes the functionality and limitations relating to circuit pack/slot equipage and electrical/optical port availability when the VLF Main packs introduced in R7.0 are used. Use this section to help plan the use of circuit packs in the Function and Growth units of a shelf equipped with VLF Mains.

VLF Cards

In R7.0 DMX introduces the LNW59 VLF Main circuit pack. In addition to providing 2 OC-192 ports via PTMs (also known as SFPs and/or XFPs), the LNW59 represents a large upgrade to the overall switch fabric capacity of the DMX shelf. This increased capacity makes true 0x1 configurations possible for the first time. Prior to R7.0,

DMX could not host differnt packs within the same Function or

Growth Unit. Use of the VLF Main in R7.0 makes this feature possible, in some cases resulting in double the overall port density for a given interface type.

However, there are certain restrictions with regard to which packs can reside next to each other in the same Function Unit or Growth slot. This section details these restrictions and provides general guidelines for circuit pack/slot equipage with the VLF Mains.

With VLF Mains, all switching and cross-connect functions are centralized on the STS and VT fabrics located on the VLF Main pack.

This is in contrast to shelves equipped with non-VLF Mains, where switching and cross-connection functions are distributed across the

Main (high-speed) and tributary (low-speed) packs/fabrics. When VLF

Mains are used in conjunction with tributary packs that contain their own switch fabrics, the switch fabrics on the tributary packs are automatically disabled.

Tributary packs supported

The VLF Main pack supports all circuit packs available in previous releases of the DMX shelf with the exception of the LNW6 and LNW7

28DS1 packs. Customers requiring DS1 connectivity and VLF Mains must employ the LNW8 56DS1/E1 pack.

365-372-300

Issue 8.0, September 2006

5 - 1 5

System Planning and Engineering

Pack compatibility for unprotected (0x1) configurations

The 0x1 capability allows compatible packs of different types to reside in the same low-speed group. Generally speaking packs which use the rear-access electrical backplane connectors are not compatible with any other packs; that is, they cannot be installed in adjacent slots within the same group. This includes, but is not limited to: LNW19/19B, LNW66,

LNW71, and LNW74.

Certain circuit pack/slot equipage guidelines are the same either VLF or non-VLF Mans are used. The use of electrical ports on the LNW70 ad LNW78 are not restricted when these packs are installed in the

Growth slots because their electrical interfaces are confined to the faceplate only. The electrical interfaces on the LNW71 and LNW74 are backplane only and will not function in the Growth slot. However, the

LNW74 also contains faceplate optical interfaces that will function in the growth slot.

In the following list of compatibility guidelines, “Ethernet” includes

Ethernet and SAN packs, “electrical” not modified by “TDM” refers to any pack that uses rear-access backplane connectors, and “TDM electrical” excludes Ethernet and Data packs. Note that “electrical” does not include Ethernet/Data packs using electrical PTMs.

Important!

The LNW74 can be installed in the Growth slots, but only the optical ports will be functional. Also, the LNW20 may be used in the Growth slots, but it will only function in portless mode.

0x1 Circuit pack/slot compatibility guidelines:

Listed below are circuit pack combinations that are incompatible for

0x1 configurations:

• TDM electrical pack/any other pack

• Any accepted pack/another TDM electrical pack

• 0x1-compatible Ethernet electrical pack/any other electrical pack

All other packs are compatible with each other for 0x1 configurations:

• OLIU/different OLIU

• OLIU/same OLIU

• non-electrical 0x1-compatible Ethernet pack/non-electrical 0x1compatible Ethernet pack

• OLIU/0x1-compatible Ethernet pack (whether electrical or not)

5 - 1 6

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

• electrical 0x1-compatible Ethernet pack/non-electrical 0x1compatible Ethernet pack

Supported combinations of packs within a Function/Growth

Group

The table below summarizes the guidelines detailed above for 0x1 compatible pack combinations within the same group. An OLIU is in

0x1 mode when all ports in the OLIU are set to the 0x1 application.

Table 5-2 0x1 compatible combinations

Slot 2

Rear Access

Mixed Front and Rear

Access

Front Access

Rear Access

Compatible

Circuit Pack Type

Slot 1

Not Compatible

Mixed Front and Rear

Access

Not Compatible

Compatible

Front Access

Compatible

NOTES

1. Front access packs include all OLIUs (Optical Line Interface Units), and the following Ethernet/Data packs: LNW63, LNW64, LNW67,

LNW68, LNW70, LNW73, and LNW78

365-372-300

Issue 8.0, September 2006

5 - 1 7

Differences at the Shelf

Level

System Planning and Engineering

This section describes the general capabilities and switch fabric capacities of the VLF Main packs.

Shelf with Large-sized Fabric Main Circuit Packs

The figure below shows how the general capabilities of the DMX shelf are enhanced/changed with the use of VLF Main circuit packs

(LNW59).

When the LNW59 VLF Main is installed in a DMX shelf, all switching and cross-connect functionality is centralized on the LNW59 fabrics.

Switching within the fabrics on the low-speed OLIUs is disabled and traffic is routed directly to the STS fabric on the Mains, bypassing any

VT fabric on the low-speed OLIUs.

The LNW59 increases the overall capacity of the shelf with a 240G

STS-1 fabric (4608x4608), 40G VT1.5 fabric (24,192x24,192), and

30G of VT termination capacity (5,376 VTs of UPSR protected 2-way add/drop cross-connections).

Figure 5-3 DMX with VLF Main circuit packs (LNW59)

2 x OC-192 Interfaces per Pack

Support for 2 Protected

1+1, UPSR, BLSR

LNW59

VLF Main

10 Gb per Slot (20 Gb per Fn)

Fn A Fn B Fn G Fn C

LNW59

VLF Main

True 0x1 Functionality Allows

For Flexibility Within a

Function Group:

! Double Density

! Mixing of Services

Fn D

4 x OC-48 Tributary Cards

Total of 192 STS1s

Mixed Interfaces Within a Function Group

2 Independent Interface Types

Enabled by True 0 x 1 Feature

8 x GbE Tributary Cards

Total of 168 STS1s

From Each Port Unit

MA-DMXAPG-040

5 - 1 8

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

• Function Groups A, B, C, and D are general purpose slots and support all low-speed circuit packs (except the LNW6 and

LNW7).

• Function Group G is referred to as the growth slot. The growth slot supports only optical, low-speed circuit packs, these include all of the OC-3/12 & 48 port cards as well as the LNW64,

LNW67, LNW68, LNW70, LNW73/73C, LNW74, and LNW78 port cards. In R7.0, growth slots can also house LNW20

TransMUX packs functioning in portless mode.

• VLF Mains provide up to 10G add/drop capacity to each lowspeed slot in the shelf.

365-372-300

Issue 8.0, September 2006

5 - 1 9

System Planning and Engineering

Network Bay Frames

Overview

The DMX can be mounted in frames of both 23-inch and 19-inch widths. 23-inch wide frames available through Lucent include the

ED8C800 (for rear mounting) and the ED8C801 (for front mounting).

Both of these 7-foot frames may accommodate up to four DMX shelves per bay. Yet, when a fuse panel is mounted at the top of one of these 7foot bays, 4 high-capacity shelves will fit. 19-inch wide EIA310-D bay frames are available through a number of third-party suppliers.

Bay arrangements

A standard 7-foot bay arrangement may contain up to four DMX

Access Multiplexers. When a bay frame is fully equipped with four

DMX shelves, a 0.515-inch space must remain open at the bottom of the rack to allow for proper air circulation. DMX shelves should be installed from bottom to top. This arrangement is configured for rear access cabling.

Important!

The high-capacity shelf uses an integral fan unit that comes attached to the DMX high-capacity shelf at the bottom of the shelf. The heat baffle is located at the top of the DMX highcapacity shelf.

5 - 2 0

365-372-300

Issue 8.0, September 2006

Network Bay Frames

System Planning and Engineering

The figure below shows a typical bay arrangement using the highcapacity DMX shelf. Note that the Fan Unit is an integral part of the

DMX high-capacity shelf.

Figure 5-4 Typical Bay Frame Arrangement Using High-capacity

Shelf

Metropolis

DMX

High-capacity

Shelf

Integral Fan Unit

Metropolis

DMX

High-capacity

Shelf

Integral Fan Unit

Metropolis

DMX

High-capacity

Shelf

Feet

Integral Fan Unit

Metropolis

DMX

High-capacity

Shelf

Integral Fan Unit

0.515 inch for proper air circulation nc-dmx2-026

Important!

When using the high-capacity DMX shelf, 4 shelves can fit in a bay with a fuse panel.

365-372-300

Issue 8.0, September 2006

5 - 2 1

System Planning and Engineering

Typical Bay Arrangement

Overview

Up to four DMX high capacity shelves, including fan units, can fit in one 7-foot network bay frame (19 or 23 inches wide).

When a network bay frame is fully equipped with DMX high-capacity shelves, a 0.515-inch space must remain open at the bottom of the frame to allow proper air circulation.

These arrangements meet network equipment-building system (NEBS) central office requirements for bay heat dissipation. If typical arrangements are not used, normal heat flow could be interrupted and adversely affect shelf operation. Fan units must be used to guarantee proper air circulation.

Fan unit

Fan units are required (in all environments) to guarantee proper air circulation. The DMX high capacity shelf includes an integral fan unit.

Adding shelves

Fan filters

The fan unit is equipped with a fan filter. To keep the fan unit operating properly, it is recommended that users routinely change the fan filter every 6 to 9 months.

Shelves can be added incrementally by local technicians (since all cabling is connectorized) if interbay cabling is initially provided for the bay layout. If shelves are incrementally installed, it is recommended that they be installed from bottom to top to simplify bay mult cabling.

However, shelves may be added in any position if proper bay mult cabling is selected.

If a shelf is added above existing non-DMX equipment one heat baffle

(408474799 or 848862181) must be installed between the shelf and the existing equipment.

For detailed information about network bay frame arrangements and installation instructions, refer to the Metropolis

DMX Access

Multiplexer, Installation Manual, 365-372-304.

5 - 2 2

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Cabinet Arrangements

Overview

Outside plant (OSP) cabinet configurations are available using the OSP

Hardened Main packs: LNW28, LNW32 (OC-48), LNW48, LNW50, and LNW54 (OC-12) OLIUs. Many of the low-speed (tributary) packs supported by DMX are OSP hardened.

Air Filter in OSP

Environment

Additional Information

The OSP environment may cause false clogged filter alarms. When the shelf is installed in an outside plant cabinet, the cooling air filter must be removed. The filter is not needed when operating in an OSP. This measure will improve air flow and thus enhance cooling performance and equipment life. See the DMX User Operations Guide (

365-372-301

) or Installation Manual (

365-372-304) for instructions to suppress the clogged filter alarm. Suppression of the clogged air filter alarm is required when installing the shelf in an OSP.

Detailed information regarding the installation of all Metropolis

DMX products in OSP applications can be found in Appendix D, Physical,

Electrical, and Thermal Compatibility Requirements for OSP

Applications. For more information regarding the OSP capabilities of low-speed packs, refer to Chapter 4 of this document.

365-372-300

Issue 8.0, September 2006

5 - 2 3

System Planning and Engineering

Cabling

Overview

Lucent offers a full complement of transmission cables and optical jumpers. All interfaces to the DMX are connectorized. For synchronization interfaces, wire-wrap connections are available. Also, a special 9-pin D-SUB connector (408267722) can be used for synchronization purposes. Rear access cabling is available.

For more information

For more information regarding cable ordering, refer to Chapter 7,

“Ordering.” For more information on required cables and cable arrangements, refer to Chapter 4, “Product Description.”

5 - 2 4

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Environmental Considerations

Overview

DMX meets NEBS Level 3 standards for use in central office environments as specified in GR-63-CORE and GR-1089-CORE.

DMX also meets standards for uncontrolled environments as specified in GR-63-CORE and GR-499-CORE. For detailed specifications, refer to Chapter 10, “Technical Specifications.”

Recycling / take-back / disposal of product

Electronic products bearing or referencing the symbol shown below when put on the market within the European Union, shall be collected and treated at the end of their useful life, in compliance with applicable

European Union and local legislation. They shall not be disposed of as part of unsorted municipal waste. Due to materials that may be contained in the product, such as heavy metals or batteries, the environment and human health may be negatively impacted as a result of inappropriate disposal.

Figure 5-5 Take Back Symbol

In the European Union, a solid bar under the crossed-out wheeled bin indicates that the product was put on the market after 13 August 2005.

Moreover, in compliance with legal requirements and contractual agreements, where applicable, Lucent Technologies will offer to provide for the collection and treatment of Lucent Technologies products at the end of their useful life, or products displaced by Lucent

Technologies equipment offers.

For information regarding take-back of equipment by Lucent

Technologies, or for more information regarding the requirements for recycling/disposal of product, please contact your Lucent Account

Manager or Lucent Takeback Support [email protected].

365-372-300

Issue 8.0, September 2006

5 - 2 5

System Planning and Engineering

Cross-connections

Overview

Purpose

This section provides cross-connection information for the DMX

Access Multiplexer. For cross-connect provisioning information, refer to Chapter 6, “Operations, Administration, Maintenance, and

Provisioning.”

Contents

The following cross-connect information is included in this section:

Cross-Connect Types

Allowable Cross-Connects

5 - 2 6

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Cross-Connect Types

Overview

The DMX has cross-connect capabilities offering users flexibility in directing traffic flow through systems to support a wide variety of customer applications using one-way and multi-point (data specific) cross-connections.

Making cross-connections

Cross-connections are made by specifying the SONET rate (VT1.5 or

STS-n), the end point addresses (AIDs), and the cross-connection type

(for example, 1WAY). Each single cross-connection command establishes a 1-way cross-connection.

Atomic cross-connections

Beginning in R6.0, DMX employs atomic cross-connections for all cross-connect provisioning. The introduction of atomic crossconnections simplifies cross-connection provisioning and lays the ground work for the support of additional applications and combinations of cross-connections in future releases. Atomic crossconnections are one-way cross-connections between logical ring channels which can be set up and taken down by a single command, and which cannot be broken down into smaller parts. Logical ring channels are the tributaries of a port or port protection group used for transmission in the absence of any line or equipment protection.

Atomic cross-connections are more flexible than the cross-connect provisioning structure employed previously. They allow for the support of more detailed applications because multiple atomic crossconnections can be provisioned to construct the desired crossconnection application.

For customers who use the WaveStar PC-CIT, Telcordia Operating

365-372-300

Issue 8.0, September 2006

5 - 2 7

Cross-Connect Types

System Planning and Engineering

Bidirectional (two-way) cross-connections

A bidirectional connection can be used to send signals between two high-speed ports (pass-through), two low-speed ports (hairpin or passthrough), and a high-speed and low-speed port (add/drop).

Bidirectional cross-connections are supported at the VT1.5, STS1,

STS3c, STS12c and STS48c rates as a function of the port types (OC-

12/48/192— high-speed). Bidirectional cross-connections can be used in hairpinning and pass-through applications as well. Beginning in

R6.0, DMX employs atomic cross-connects. Therefore, DMX no longer supports a single TL1 command to set up a two-way crossconnect; rather the user must provision two one-way cross-connects.

Unidirectional (one-way) cross-connections

A one-way cross-connection is a single-ended connection that can be used to send signals between two high-speed ports (pass-through or hairpin, hairpin with the LNW59 only), two low-speed ports (hairpin or pass-through), and a high-speed and low-speed port (add/drop). In add/ drop applications, this is used where VT1.5, STS-1, STS-3(c), STS-

12(c), STS-48(c) signals on high-speed channels are cross-connected to low-speed DS1/E1, DS3, EC-1, OC-3, OC-12, 100BASE-TX,

100BASE-LX, 1000BASE-SX/LX, or FC-DATA ports. With highspeed OC-192/48 optics, high-speed STS-48(c) signals may also be cross-connected. DMX allows one-way cross-connections in support of

DRI, bridge and roll, and true 0x1 unprotected scenarios.

Hairpinning crossconnections

In “hairpinning” topologies prior to R7.0 that employed the LNW45 and LNW49 circuit packs, tributary (low-speed) traffic was routed into the system and back out without ever being placed on the high-speed

(OC-12, OC-48 or OC-192) interfaces. If the VLF Main pack

(LNW59) available in R7.0 is used, all cross-connect and switching functions are centralized on the Main pack. Switching within the fabrics on the tributary (low-speed) OLIUs is disabled and traffic is routed directly to the STS fabric on the Mains, bypassing any VT fabric on the tributary OLIUs.

DMX is capable of connecting any input on a circuit pack in a function or growth slot to any output on a circuit pack in a different function or growth slot in the same shelf (known as inter-fn hairpin). DMX also supports intra-port hairpins, by which DMX can hairpin between different ports in the same group. R7.0 adds support for hairpin crossconnections to 0x1Sn interfaces. When R7.0 or later software is used in conjunction wit VLF Mains, hairpin cross-connections between unprotected ports on different slots of the same low-speed group are also supported.

5 - 2 8

365-372-300

Issue 8.0, September 2006

Cross-Connect Types

Locked DS1/DS3 Cross

Connections

System Planning and Engineering

This feature is extremely useful in utility applications.

Locked VT Cross

Connections (R7.0)

In the “locked” mode, DMX does not select the best signal from both rotations of a UPSR. Instead, traffic is added and dropped (locked) from one rotation of the ring only (provisionable). The main advantage of locked VT cross-connections is the lack of UPSR switching which results in the ability to reuse timeslots around a UPSR.

The ability to mix locked, unlocked, and pass-through VT1.5s within the same STS-1 was added in R6.0.2.

Locked cross-connections are only used in systems that are not equipped with VLF Mains because VLF mains allow unprotected

(linear) UPSR cross-connections which allow users to independently provision cross-connections on UPSR tributaries. In systems with non-

VLF Mains, once a locked cross-connection is established from a

UPSR tributary, the companion tributary cannot be cross-connected.

Linear/Unprotected UPSR

(R7.0)

In R7.0, DMX also allows both rotations of a ring to be used simultaneously. Prior to 7.0, if a 1WAY (as opposed to a path-protected

1WAYPR) cross-connection was established with the source from a

DMX permits simultaneous 1WAY cross-connections sourced from the

2 associated ring channels in a UPSR application, simultaneous 1WAY cross-connection sourced from a ring channel, and 1WAY or

1WAYPR destined to the associated ring channel.

This feature removes the need for unswitched cross-connections on

Ethernet/Data packs which don’t require VCG pairing, yet they will still be supported to ensure backwards compatibility.

365-372-300

Issue 8.0, September 2006

5 - 2 9

Cross-Connect Types

System Planning and Engineering

Multi-point (data-specific) cross-connections

The data specific multi-point cross-connect is a bidirectional crossconnection between two STS-1 Virtual Concatenation Groups (VCGs) on 100BASE-TX or 1000BASE-SX/LX ports to two different ring interfaces. All multi-point cross-connections are done at the STS-1 level (multi-point cross-connections can also be made at the STS-3c, and STS-12c level using the LNW63, LNW70, LNW71, LNW78 circuit pack-- the LNW71 does not support STS-12c). Multi-point cross-connections are used to create packet rings.

Beginning in R6.0, multiple 1WAY UNSWITCHED cross-connections provide unprotected SONET connections to Ethernet circuit packs.

Each can be used to form two individual connections. With atomic cross-connections, multipoint cross-connections are provisioned by way of 1WAY UNSWITCHED cross-connects.

5 - 3 0

365-372-300

Issue 8.0, September 2006

Cross-Connect Types

System Planning and Engineering

Bridged cross-connections

DMX supports multicast (1xN) cross-connections where N is limited only by the available cross-connect fabric (fr VTs) and the compatible output tributaries. Bridging of an existing cross-connection consists of adding a one-way cross-connection with the same input tributary as that of an existing cross-connection, resulting in a 1x2 multicast from an input tributary to two output tributaries. DMX supports bridging for each of the supported SONET cross-connection rates. You can bridge any existing cross-connection to a second output port without impairing the existing signal. Conversely, either half of a bridged signal can be taken down without impairing the remaining crossconnected signal.

Pipe-mode (adaptive-rate) cross-connections

DRI cross-connections

Pipe mode is a fault and PM feature whereby fault and PM are reported independently for each constituent signal within a cross-connection rather than simply at the xc rate.

DRI cross-connections, used in Dual Ring Interworking applications, are accomplished by means of a one-way, protected drop from a UPSR, a one-way pass-through, and a one-way add to the same UPSR.

Manual cross-connect rates

The following lists the signals that can be cross-connected:

• VT1.5

• STS-1

• STS-3c

• STS-12c

• STS-48c

365-372-300

Issue 8.0, September 2006

5 - 3 1

System Planning and Engineering

Allowable Cross-Connects

Overview

The DMX utilizes several types of SONET, DSn/Electrical, and

Ethernet cross-connections, including:

• add/drop

– Unidirectional Path Switched Ring (UPSR)

– Bidirectional Line Switched Ring (BLSR)

– Linear 1+1

– Bidirectional 1+1

– Unswitched UPSR

• unprotected optical

– 0x1Sn

(only available on shelves that do not employ LNW59 VLF

Main)

– 0x1

(only available in R7.0 and later Releases with the use of the

LNW59 VLF Main)

• hairpin

– inter-function group

– intra-function group

– intra-port

• pass-through

• multi-point (Ethernet only)

• Ethernet hairpinning

5 - 3 2

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

Add/Drop

System Planning and Engineering

All connections from a high-speed interface to a low-speed interface are considered add/drop. An add/drop cross-connection is bidirectional cross-connection between a high speed interface and a low speed interface. DMX also supports unidirectional add and drop crossconnections. A signal can also be add/dropped from electrical and

Ethernet interfaces.

Unidirectional Path Switched Ring (UPSR)

A UPSR is self-healing ring configuration in which traffic is sent onto both rotations (both fibers) of the ring in opposite directions. “Pathswitched” means that if the working signal fails, the path switches to the protection signal. UPSRs operate in an integrated, single ended fashion— negating the need for complex network-level coordination in the effort to restore traffic.

Bidirectional Line Switched Ring (BLSR)

A 2-fiber is a self-healing ring configuration in which bidirectional traffic travels over the same set of nodes in each direction.

Bidirectional switching makes use of redundant (protection) bandwidth on the bidirectional lines that interconnect the nodes in the ring to provide protection for traffic carried on the working bandwidth.

Because the traffic is bidirectional, a single circuit does not necessarily consume bandwidth on every span in the ring. This leaves the spans between other nodes available for additional traffic. Therefore, with distributed switching patterns, a BLSR can carry more traffic than the same facilities could carry if configured for a unidirectional pathswitched ring.

365-372-300

Issue 8.0, September 2006

5 - 3 3

Allowable Cross-Connects

System Planning and Engineering

Unswitched

DMX provides an equipment-unprotected cross-connect mode, referred to as unswitched UPSR, on OC-3/12/48 low-speed ports, OC-12/48/

192 high-speed UPSRs, and OC-48/192 BLSR NUT tributaries. This option is user-provisionable on a per cross-connection basis and supports single- and dual-homed ring on ring topologies.

0x1Sn

0x1Sn is not supported when DMX is equipped with VLF Main packs

(LNW59). VLF Main packs make true 0x1 cross-connections available beginning in R7.0.

With 0x1Sn, the OC-n 0x1 provisioning and alarming capability provides the user with a method of provisioning a LS OC-n port in one slot of a slot pair to operate as an unprotected interface. Crossconnections to 0x1Sn ports are provisioned using the ring channel

AIDs corresponding to the active side/port. The inactive port, if equipped, always outputs STS1 UNEQ or AIS-P on all tributaries, as a function of the system default idle signal provisioning.

Cross-connections are supported between 0x1Sn ports and all other interface types. For DHA applications, 1WAYPR and 1WAY crossconnections between a 0x1Sn port to a UPSR ring channel are required.

Cross-connections supported at all rates supported by the LS OC-n port. Multipoint and unswitched cross-connections to 0x1Sn interfaces are not supported.

The figure below shows high-level schematics of two-way add/drop, unswitched, and 0x1Sn cross-connections.

5 - 3 4

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

Figure 5-6 Two-way add/drop, Unswitched, and 0x1Sn

OC-N

MAIN Fabric

A1+2-

G1+2

OC-n

1+1 or UPSR

(a) OC-n Two-way drop

MAIN1 Interface MAIN2 Interface

OC-N

DS1,DS3, EC1

(b) Two-way drop terminated or drop non-terminated path

MAIN1 Interface

OC-N

Function or

Growth Slot

Interface

(A1...G1)

OC-N

Function or

Growth Slot

Interface

(A2...G2)

OC-N

Function or

Growth Slot

Interface

(A1...G1)

NC-DMX-154

365-372-300

Issue 8.0, September 2006

5 - 3 5

Allowable Cross-Connects

System Planning and Engineering

True 0x1 (R7.0)

With the introduction of the VLF Main pack (LNW59) in R7.0, DMX allows true 0x1 unprotected circuit packs. That means that any slot can be equipped with any pack (some restrictions apply). Two of the same circuit packs can also populate adjacent slots in the same group (this includes some Ethernet packs). For detailed information on circuit pack/slot equipage restrictions in 0x1 mode, refer to

Very Large Fabric

(VLF) Engineering Rules

In the case of OLIUs (SONET optical line interface packs), all ports in a pack must be set to 0x1 application in order for a different pack to be used in the companion slot. If any pair of lines is provisioned for a protected application (1+1, UPSR, BLSR), then both packs in the group must be of the same type.

True 0x1 replaces 0x1Sn functionality when VLF Mains are used. True

0x1 supports all the capabilities 0x1Sn allow, but adds the capability for both slots of a single group to function independently. 0x1Sn will still be supported when the shelf is equipped with non-VLF Mains.

True 0x1 is only available on the low-speed/tributary packs, not on the

Main (M1/M2) interfaces.

When two circuit packs in the same low-speed group are operating in

0x1 mode, all provisioning, reporting and retrieval (of alarms) associated with the pack, ports and tributaries in Slot 1 are independent of the provisioning, reporting and retrieval associated with the pack, ports and tributaries in Slot 2.

When provisioned for 0x1 operation, the affect on service and severity of alarms issued against a pack in Slot 1 of a particular group are independent from the affect on service and the severity of the alarms issued against the pack in Slot 2 of that group.

When DMX is equipped with VLF Mains, all 1-way cross-connections presently supported on an unprotected port/line (including ports/lines on an unprotected pack) in one slot of an LS group can be supported independently and simultaneously on an unprotected port/line in either slot of a Function or Growth group. 1-waypr cross-connections are not allowed to be sourced from 0x1 interfaces.

True 0x1 enables hairpin cross-connections between channels on packs in different slots of the same Function or Growth group.

5 - 3 6

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

Pass-through

A pass-through cross-connection is made between two ring interfaces in the same MAIN or Function Unit group, allowing the signal to be

“passed-through” a ring node on the same timeslot.

The figure below shows a pass-through cross-connection on the highspeed interface (OC-12, OC-48, or OC-192).

Figure 5-7 Pass-through cross-connection on High-speed interface

Main TDM Fabric

OC-N OC-N

Two-way pass-through path nc-dmx-160

365-372-300

Issue 8.0, September 2006

5 - 3 7

Allowable Cross-Connects

System Planning and Engineering

Low-speed pass-throughs

The DMX can host multiple rings on the low-speed interfaces of the

DMX shelf. This is accomplished by intra-function group, passthrough cross-connections. The DMX can close a low-speed ring by supporting a cross-connection between a receive port on one circuit pack and a transmit port on another circuit pack in the same function or growth group. All protection switching advantages/capabilities still apply in VT and STS-n Ring Closure applications. When VLF Main packs are used, all cross-connect switching occurs on the main packs, including low-speed, tributary pass-through cross-connects. This means that the line depicting the pass-through cross-connect in the figure below would have to extend out of the tributary packs, up into the MAIN switch fabric at the top of the figure when VLF Mains are used.

Figure 5-8 Pass-through hairpin

MAIN TDM Fabric M1 + 2

A-G A-G

Ring Pass - Through

(VT - Ring Closure) nc-dmx-159

5 - 3 8

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

SONET hairpinning Crossconnections

(OC-12, OC-48 or OC-192) interfaces. If the VLF Main pack

also supported (certain restrictions apply, refer to

Very Large Fabric

(VLF) Engineering Rules

These flexible cross-connect capabilities allow you to use a combination of add/drop and hairpinning of compatible payloads through a variety of interfaces.

DMX supports intra-function group, hairpin cross-connections that are cross-connections between different tributaries on different ports within the same function group. Intra-port hairpins are crossconnections between channels hosted by the same physical port of the

DMX shelf. These intra-port hairpins are only supported on 1+1 protected interfaces.

365-372-300

Issue 8.0, September 2006

5 - 3 9

Allowable Cross-Connects

System Planning and Engineering

The figure below shows some of the various SONET hairpinning schemes.

Figure 5-9 SONET hairpinning

MAIN TDM Fabric M1 + 2 MAIN TDM Fabric M1 + 2

A-G

(a) 1+1 Hairpin

MAIN TDM Fabric M1 + 2

A-G A-G

OC-3/OC-12/

OC-48

UPSR

OC-3/OC-12/

OC-48

UPSR

(b) 2 Closed UPSR, Hairpin

A-G

MAIN TDM Fabric M1 + 2

A-G

OC-3/OC-12/

OC-48

UPSR

1+1

1+1 Hairpin

A-G

1+1 or UPSR

(d) 1+1 or UPSR

DS1,DS3,EC1

DS1, DS3, EC1, Hairpin

NC-DMX-151

5 - 4 0

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

Portless mode hairpin cross-connections

(LNW20)

The figure below depicts hairpin cross-connects involving the LNW20 in portless mode. When operating in portless mode, LNW20 pulls

DS1s from channelized DS3 signals that enter DMX on a SONET STS-

1 interface (on another pack) and converts them to VT mapped STS-1s.

This VT-mapped STS-1 is cross-connected at the VT level in the Main packs (at least one side of the cross-connect is OCn/EC1) to any interface that supports the signal structure today (DS1, channelized

DS3, EC1, optical).

For portless functionality, incoming STS-1s must contain a channelized

DS3. This STS-1 is cross-connected to the LNW20 and then hairpinned to the STS fabric on the Main pack. Once the signal is finally converted to a VT1.5 it can be cross-connected to any port that accepts that signal format.

Figure 5-10 LNW20 portless mode cross-connects

monitor DS1/DS3 egress fault/PM

Main

STS fabric

STS1->

DS3->

DS1->

VT->

STS1

STS1->

VT->

DS1->

DS3->

STS1

LNW20 in group a

STS1->

VT->

DS1

VT fabric

STS1 containing channelized DS3 monitor DS1 fault/

PM monitor

STS fault/

SONET/SDH fn/main

DS1 DSX

DS1 card in group b

Important!

In the figure above, the LNW20 is depicted in function group “a” as an example, not a requirement. The different colored solid lines also represent independant cross-connects.

365-372-300

Issue 8.0, September 2006

5 - 4 1

Allowable Cross-Connects

System Planning and Engineering

Multi-point (Ethernet only)

The data-specific multi-point cross-connect is a bidirectional crossconnection between two STS-1 Virtual Concatenation Group (VCG) on 100BASE-TX/LX or 1000BASE-SX/LX and ports to two different ring interfaces (UPSR or BLSR with NUT provisioning).

The figure below shows Ethernet Multipoint cross-connection schematic.

Figure 5-11 Ethernet Multi-point cross-connection

OC-48/OC-192 OC-48/OC-192

M1 M2

Lan Switch

Empty

Slot

A1-G1

100 BASE-TX

1000 BASE-SX/LX

Multipoint Ethernet

A2-G2

NC-DMX-152

5 - 4 2

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

Ethernet hairpining Crossconnections

With Ethernet-to-Ethernet hairpinning, traffic may travel from one

Ethernet port on a circuit pack in one set of slots, to another port on a circuit pack in a different set of slots (from A1 to C1 or A2 to C2, for example). From there, the traffic may be multiplexed with other packet traffic before being switched onto another Ethernet or SONET interface.

In shelves equipped with R7.0 software and VLF Mains (LNW59), hairpins between 0x1 compatible Ethernet packs located in Slot 1 and

Slot 2 of the same group are also supported. For detailed information regarding 0x1 circuit pack compatibility, refer to

Very Large Fabric (VLF)

Engineering Rules

The figure below shows some of the high-level schematics of Ethernet hairpinning cross connections.

Figure 5-12 Ethernet hairpinning

MAIN TDM Fabric M1+2 MAIN TDM Fabric M1+2

A1+A2-

G1+G2

UPSR or

1+1

(a) 1+1 or UPSR

Lan Switch

A1+G1

100 BASE-TX/FX

1000 BASE-SX/LX

Ethernet Hairpin

MAIN TDM Fabric M1+2

A1+A2-

G1+G2

Lan Switch

A1-G1

OC-n

0X1 or UPSR

(b) OC-N 0X1 or UPSR

100 BASE-TX/FX

1000 BASE-SX/LX

Multi-Point Ethernet Hairp

Lan Switch

A1-G1

Lan Switch

A1-G1

100 BASE-TX/FX

1000 BASE-SX/LX

100 BASE-TX/FX

1000 BASE-SX/LX

Important!

Ethernet hairpinns to BLSR interfaces are also supported.

NC-DMX-1

365-372-300

Issue 8.0, September 2006

5 - 4 3

Allowable Cross-Connects

System Planning and Engineering

Multi-point Ethernet

Combinations

Multi-point Ethernet cross-connections are supported from Ethernet ports, to ports provisioned for UPSR or BLSR with NUT only. In much the fashion as shown in the figure below, the DMX supports Multipoint Ethernet cross-connections between the following combinations of interfaces:

• OC-12/48/192 MAIN OLIUs & one 100-TX/LX or 1000-SX/LX/

ZX (A-G)

• OC-3/12/48 OLIU (A-G) & one 100-TX/LX or 1000-SX/LX/ZX interface (A-G)

Figure 5-13 Multi-point Combinations

MAIN TDM Fabric

M1+2

LAN Switch LAN Switch LAN Switch OC-3/12/48

OC-3/12/48

100BASE-TX/LX

1000 BASE-SX/LX

Multipoint GbE

Combinations nc-dmx-161

5 - 4 4

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

Ethernet Circuit Pack

Capacities Summary

The table below details various characteristics of the Ethernet and FC-

DATA (SAN) circuit packs. The table covers the rate, transport format

(PL or Switched), differential delay, frame size, LCAS capability,

Release number, OSP capability as well as the number, format and capacity of VCGs supported by each Ethernet circuit pack in the DMX.

Table 5-3 Ethernet Circuit Pack Capacities Summary Part 1

Pack Rate

(port #)

LNW63

1G SX/LX/

ZX PL

LNW64

1G SX/LX/

ZX PL

LNW66

10/100 T

LNW67

1G SX

LNW68

1G LX

LNW70

100/1G FS

1000BASE-SX/LX/

ZX (4)

1000BASE-SX/LX/

ZX (8)

100BASE-TX

(24)

1000BASE-SX (2)

1000BASE-LX (2)

100BASE-LX

(4- PTM)

1000BASE-X

(4-PTM)

LNW78

100/1G

RPR

LNW78

100/1G

EoS

LNW71

10/100 PL

100BASE-LX

(4- PTM)

1000BASE-X

(4-PTM)

100BASE-TX

(24)

PL or

Switched

VCG

Ports

PL 4

VT1.5xv

VCG Format and Capacity (Max # of tributaries per VCG

STS-1 STS-1xv

21 21

STS-3c STS-3cxv

STS-12c

7 7 1

Switched

PL /

Switched

PL /

Switched

PL /

Switched

2-4

(only on

VCGs

1-28)

2 -

365-372-300

Issue 8.0, September 2006

5 - 4 5

Allowable Cross-Connects

System Planning and Engineering

Pack Rate

(port #)

LNW73/73c

FC-DATA

(SAN)

FC-1G/FICON (4)

ESCON (4)

PL or

Switched

VCG

Ports

VT1.5xv

VCG Format and Capacity (Max # of tributaries per VCG

STS-1 STS-1xv

(FC-

FICON)

(ESCON)

STS-3c STS-3cxv

STS-12c

(FC-

FICON)

(ESCON)

(FC-

FICON)

24 63 X 3 X LNW74

10/100 T/F

100BASE-TX

(16)

100BASE-LX

(8-PTM)

Pack

LNW63 GbE PL A-G

LNW64 GbE PL A-G

Table 5-4 Ethernet Circuit Pack Capacities Summary Part 2

Slots where Differential packs can reside

Delay (ms)

LCAS

Support

108

Maximum

Frame Size

10240

1536

OSP

(optical PTM/

SFPs only)

Release

6.0

7.0

1.1

LNW66 10/100 T A-D

LNW67

1G SX

A-G

A-G LNW68

1G LX

LNW70

100/1G FS

LNW78

RPR/EoS

LNW71

10/100 PL

A-G

A-D

1536

10240

10240 -

1.1

5.1

6.0

3.1

5 - 4 6

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

Pack Slots where Differential packs can reside

Delay (ms)

LCAS

Support

A-G 120 Y

LNW73/73C

FC-DATA

(SAN)

LNW74

10/100 T/F

A-G

65 Y

Maximum

Frame Size

System Planning and Engineering

OSP Release

2160

9632

5.1

5.0

NOTES

1.For every pack other than the LNW64, maximum 2.5G (48 STS-1) between any function slot and the backplane - double (5G) with multipoint cross connections for

DMX. LNW64 has a maximu backplane capacity of 10G (192 STS-1s).

2. 24 ports when set to STS-1 mode – 16 when set to STS-3c mode

3. 2 with 2waypr cross-connections; 2 with mltpt cross-connections; the LNW67 and

LNW68 have 4 VCGs, only two of which are addressable for xc provisioning. The other two are automatically connected when the xc is provisioned. This is no longer the case with Atomic cross-connects (R6.0). With atomic cross-connects, unswitched (the atomic equivalent of multipoint) cross-connects are provisioned seperately for odd/even number VCG pairs.

4. Maximum frame size for async-FC provisioned ports is 2160.

5. When the LNW74 is used in slot G1, only the optical ports are functional.

6. The LNW73 and LNW73C do support LCAS, but only for asyncFC traffic.

365-372-300

Issue 8.0, September 2006

5 - 4 7

Allowable Cross-Connects

System Planning and Engineering

Ethernet Circuit Pack

Capacities for Ring

Configurations

The table below details the allowable Ethernet-related ring configurations (Ethernet applications within UPSR and BLSR topologies) and the number of these configurations that may be supported by each Ethernet circuit pack in the DMX.

Important!

Capacities for each configuration are available in the later of the release numbers shown at the left of the row and the top of the column.

For more information on Packet Rings, Ethernet Private Lines, and Ethernet Rate Shaping, refer to the corresponding section in

Chapter 3 of this document.

Table 5-5 Ethernet Circuit Pack Capacities for Ring

Configuration

Configurations

Release

1.1

LNW63/

LNW64

1000

Mbps

(GbE-PL)

(4-port/8port)

LNW66

10/100

Mbps

(FE-BPR)

R6/7.0

2/4

R1.1

LNW67/

1000

Mbps

(GbE-

BPR)

Port Units

LNW71 LNW74

10/100

Mbps

(FE-EPL)/

1000

Mbps

(GbE-PL)

10/100

Mbps

(FE-EPL)

R1.1

R3.1

R5.0

LNW70 LNW78

10/100/

1000

Mbps

(FE/GbE-

BPR)

R5.1

10/100/

1000

Mbps

(FE/GbE-

RPR/

EoS)

R6.0

1 Packet Rings on

UPSRs

Packet Rings on

BLSRs

Packet Rings on

BLSRs w/ NUT

PL on UPSR w/

UPSR protection

PL on UPSR w/

out UPSR protection

PL on BLSR

EPL on BLSR w/ NUT

2.1

3.0

1.1

2.1

3.0

2/4

16-24

16-32

5 - 4 8

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

Configurations

Release

LNW63/

LNW64

1000

Mbps

(GbE-PL)

(4-port/8port)

LNW66

10/100

Mbps

(FE-BPR)

LNW67/

1000

Mbps

(GbE-

BPR)

R1.1

Port Units

LNW71 LNW74

10/100

Mbps

(FE-EPL)/

1000

Mbps

(GbE-PL)

R3.1

10/100

Mbps

(FE-EPL)

R5.0

R6/7.0

BPR= Basic Packet Ring

RPR= Resilient Packet Ring

EPR= Enhanced Packet Ring (w/ rate shaping

EPL= Ethernet Private Line (point-to-point)

PL= Private Line (point-to-point)

FE= Fast Ethernet (10/100 Mbps)

GbE= Gigabit Ethernet (1000 Mbps)

FC-DATA= SAN card (FICON/ESCON/FC)

R1.1

LNW70 LNW78

10/100/

1000

Mbps

(FE/GbE-

BPR)

R5.1

10/100/

1000

Mbps

(FE/GbE-

RPR/

EoS)

R6.0

NOTES

1.Each span of the packet ring has BLSR protection. It is not necessary to “close” the packet ring on a BLSR: BLSR protection is provided on each span, so spanning tree protection is unnecessary. Capacity on one span of the BLSR can be used for other purposes.

2. For LNW71: 16 ports for STS-3c mode, 24 ports otherwise.

3.The number of EPL cross-connections on the LNW74 is relative to the slot in which the circuit pack is housed and not the cross-connection rate. 24 VCGs are provisionable in slots A-D. 8 VCGs are provisionable in slot G.

365-372-300

Issue 8.0, September 2006

5 - 4 9

Allowable Cross-Connects

System Planning and Engineering

All Allowable UPSR Adddrop Cross-connections

The table below contains a list of UPSR add-drop cross-connections supported by

DMX

in Release 7.0. The cross-connections in the table below are all drop cross-connections

Important!

R6.0 and later releases employ atomic crossconnections. With atomic cross-connects, all cross-connections are oneway. For cross-connects not involving UPSR interfaces, the same 1-way cross-connects are supported in the opposite direction to provide twoway connectivity.

R7.0 also introduces the LNW59 VLF Main which makes true 0x1 cross-connections and shelf equipage possible. When the LNW59 is used, the shelf doesn’t support 0x1Sn cross-connections (only 0x1) or the LNW6 and LNW7. In shelves equipped with VLF Mains, unprotected (linear) UPSR cross-connections are also supported.

Unprotected UPSR cross-connections are independent crossconnections to/from the companion UPSR tributaries. For these reasons, the capabilities of the shelf when equipped with the LNW59 are listed separately.

In the “To” column of the table below, “TransMUX” includes the

LNW18 and LNW20 in both ported and portless mode.

Table 5-6 All Allowable UPSR Add-drop Cross-connections

5 - 5 0

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

From

VLF Main OC-192 (LNW59) OLIU

(UPSR)

1-way STS-n --------------------->

1-way VT1.5-------->

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

1-waypr STS-n ------------------->

1-waypr VT1.5 -------------------->

NOTE: LNW59 has more than one OC-192 port, making cross-connections between different OC-192 ports on the same Main are possible when it is used. All of the cross-connect types listed in the left column are supported between LNW59 ports.

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, UPSR, 0x1), OC-48 (BLSR), 100-TX/LX,

1000-SX/LX/ZX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1), 100-TX/LX (LNW74 only)

OC-3/12/48 (UPSR), OC-48 BLSR w/ NUT, 100-

TX/LX, 1000-SX/LX/ZX (no LNW74)

OC-48/192 (UPSR, BLSR w/ NUT)

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, UPSR, 0x1), OC-48 (BLSR), 100-TX/LX,

1000-SX/LX/ZX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1), 100-TX/LX (LNW74 only)

Non-VLF OC-192 OLIU (UPSR)

1-way STS-n --------------------->

1-way VT1.5-------->

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

1-waypr STS-n ------------------->

1-waypr VT1.5 -------------------->

DS1, E1, DS3, TransMUX, OC-3/12/48 (0x1Sn),

100-FX/1000 SX/LX/ZX (LNW78 only)

DS1, EC-1, TransMUX, OC-3/12/48 (0x1Sn)

OC-3/12/48 (UPSR), OC-48 BLSR w/ NUT,

1000-SX/LX/ZX, 100-TX/LX

OC-3/12/48 (UPSR), OC-48 BLSR w/ NUT

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, 0x1Sn, UPSR), OC-48 BLSR, 1000-SX/LX/

ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (0x1Sn, 1+1 and UPSR), 100-TX/LX (LNW74 only)

OC-48 High-Speed OLIU (UPSR)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, TransMUX, OC-3/12/48 (0x1Sn)

DS1, EC-1, TransMUX, OC-3/12/48 (0x1Sn)

365-372-300

Issue 8.0, September 2006

5 - 5 1

Allowable Cross-Connects

From

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

1-waypr STS-n ------------------->

1-waypr VT1.5 -------------------->

OC-12 High-Speed OLIU (UPSR)

1-way STS-n --------------------->

1-way VT1.5-------->

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

1-waypr STS-n ------------------->

1-waypr VT1.5 -------------------->

System Planning and Engineering

OC-3/12/48 (UPSR), OC-48 BLSR w/ NUT,

1000-SX/LX, 100-TX

OC-3/12/48 (UPSR) and OC-48 BLSR w/ NUT

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, 0x1Sn, UPSR), OC-48 BLSR, 1000-SX/LX,

100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (0x1Sn, 1+1 and UPSR), and OC-48 BLSR, 100-TX/LX

(LNW74 only)

DS1, E1, DS3, TransMUX, OC-3/12/48 (0x1Sn)

DS1, EC-1, TransMUX, OC-3/12/48 (0x1Sn)

OC-3/12/48 (UPSR), OC-48 BLSR w/ NUT,

1000-SX/LX, 100-TX

OC-3/12/48 (UPSR) and OC-48 BLSR w/ NUT

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, 0x1Sn, UPSR), OC-48 BLSR, 1000-SX/LX,

100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (0x1Sn, 1+1 and UPSR), and OC-48 BLSR, 100-TX/LX

(LNW74 only)

5 - 5 2

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

All Allowable 1+1 Add-drop

Cross-connections

The table below contains a list of linear/bidirectional (1+1) add-drop cross-connections supported by DMX in Release 7.0. The crossconnections in the table below are all drop cross-connections.

Important!

R6.0 and later Releases employ atomic crossconnections. With atomic cross-connects, all cross-connections are one-way. For cross-connects not involving UPSR interfaces, the same 1-way cross-connects are supported in the opposite direction to provide two-way connectivity.

Table 5-7 All Allowable 1+1 Add-drop Cross-connections

From

VLF Main OC-192 (LNW59) OLIU

(1+1)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, UPSR, 0x1), OC-48 (BLSR), 100-TX/LX,

1000-SX/LX/ZX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1), OC-48 BLSR, 100-TX/LX (LNW74 only)

Non-VLF Main OC-192 OLIU (1+1)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, 0x1Sn, UPSR), OC-48 BLSR, 1000-SX/LX/

ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, 0x1Sn,

UPSR), OC-48 BLSR, 100-TX/LX (LNW74 only)

OC-48 High-Speed OLIU (1+1)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, 0x1Sn, UPSR), OC-48 BLSR, 1000-SX/LX,

100-TX/LX, FC-DATA

DS1, TransMUX, OC-3/12/48 (1+1, 0x1Sn,

UPSR), OC-48 BLSR, and 100-TX/LX

OC-12 High-Speed OLIU (1+1)

365-372-300

Issue 8.0, September 2006

5 - 5 3

Allowable Cross-Connects

From

1-way STS-n --------------------->

1-way VT1.5-------->

System Planning and Engineering

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, 0x1Sn, UPSR), OC-48 BLSR, 1000-SX/LX,

100-TX/LX, FC-DATA

DS1, TransMUX, OC-3/12/48 (1+1, 0x1Sn,

UPSR), OC-48 BLSR, 100-TX/LX

5 - 5 4

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

All Allowable BLSR Adddrop Cross-connections

The table below contains a list of BLSR add-drop cross-connections supported by DMX in Release 7.0. The cross-connections in the table below are all BLSR drop cross-connections.

Important!

R6.0 and later Releases employ atomic crossconnections. With atomic cross-connects, all cross-connections are one-way. For cross-connects not involving BLSR interfaces, the same 1-way cross-connects are supported in the opposite direction to provide two-way connectivity.

Table 5-8 All Allowable BLSR Add-drop Cross-connections

From

VLF Main OC-192 (LNW59) OLIU

(BLSR)

1-way STS-n --------------------->

1-way VT1.5-------->

1-way unswitched STS-n-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, UPSR, 0x1), OC-48 (BLSR), 100-TX/LX,

1000-SX/LX/ZX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1), 100-TX/LX (LNW74 only)

OC-3/12/48 (UPSR), 100-TX/LX, 1000-SX/LX/

OC-3/12/48 (UPSR) 1-way unswitched VT1.5-------->

Non-VLF OC-192 High-Speed OLIU

(BLSR)

1-way STS-n --------------------->

1-way VT1.5-------->

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

OC-48 High-Speed OLIU (BLSR)

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, UPSR, 0x1Sn), OC-48 (BLSR), 100-TX/

LX, 1000-SX/LX/ZX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1Sn), 100-TX/LX (LNW74 only)

OC-3/12/48 (UPSR), 100-TX/LX, 1000-SX/LX/

OC-3/12/48 (UPSR)

365-372-300

Issue 8.0, September 2006

5 - 5 5

Allowable Cross-Connects

System Planning and Engineering

From

1-way STS-n --------------------->

1-way VT1.5-------->

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, 0x1Sn, UPSR), OC-48 BLSR, 1000-SX/LX,

100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, 0x1Sn,

UPSR), OC-48 BLSR, 100-TX/LX

OC-3/12/48 (UPSR), 1000-SX/LX, 100-TX

OC-3/12/48 (UPSR)

All allowable UPSR and

BLSR Pass-through Crossconnections (high-speed interface)

DMX supports direct pass-through cross-connections from a particular timeslot on one side of a UPSR to/from the same timeslot on the other side of the ring. BLSR pass-through cross-connections function in the same manner. Pass-through cross-connections are available at the same rates as add/drop cross-connections.

5 - 5 6

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

All Allowable Hairpin

Cross-connections

The table below contains a list of hairpin cross-connections supported by DMX in Release 7.0. The cross-connections in the table below are all Hairpin cross-connections.

Table 5-9 All Allowable Hairpin Cross-connections

From

OC-3/12 (1+1)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, UPSR, 0x1, 0x1Sn), OC-48 BLSR, 1000-

SX/LX/ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1 and

UPSR), 100-TX/LX (LNW74 only)

OC-3/12 (UPSR)

1-way STS-n --------------------->

1-way VT1.5-------->

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

1-waypr STS-n ------------------->

1-waypr VT1.5 -------------------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(UPSR), 1000-SX/LX/ZX, 100-TX/LX, FC-

DATA

DS1, EC-1, TransMUX, OC-3/12/48 (UPSR,

0x1Sn), 100-TX/LX (LNW74 only)

OC-3/12/48 (UPSR), 1000-SX/LX/ZX, 100-LX/

TX (no LNW74)

OC-3/12/48 (UPSR)

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, UPSR, 0x1, 0x1Sn), OC-48 BLSR, 1000-

SX/LX/ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1, 0x1Sn), OC-48 BLSR, 100-TX/LX (LNW74 only)

OC-3/12 (0x1) (requires LNW59 VLF

Main)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(UPSR, 1+1, 0x1) and OC-48 BLSR, 1000-SX/

LX/ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1), 100-TX/LX (LNW74 only)

365-372-300

Issue 8.0, September 2006

5 - 5 7

Allowable Cross-Connects

System Planning and Engineering

From

OC-3/12 (0x1Sn) (non-VLF Mains only)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(UPSR, 1+1, 0x1Sn) and OC-48 BLSR, 1000-SX/

LX/ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1Sn), 100-TX/LX (LNW74 only)

OC-48 Low-Speed OLIU (1+1)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(1+1, UPSR, 0x1Sn, and 0x1), OC-48 BLSR,

1000-SX/LX/ZX, 100-TX/LX, FC-DATA

DS1, DS3, EC-1, TransMUX, OC-3/12 (1+1,

UPSR, 0x1Sn, and 0x1), OC-48 (1+1 and UPSR),

100-TX/LX (LNW74 only)

OC-48 Low-Speed OLIU (UPSR)

1-way STS-n --------------------->

1-way VT1.5-------->

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

1-waypr STS-n ------------------->

1-waypr VT1.5 -------------------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12 (1+1,

UPSR, 0x1Sn, 0x1), OC-48 (BLSR and UPSR)

1000-SX/LX/ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12 (1+1, 0x1Sn,

0x1, UPSR) OC-48 UPSR) 100-TX/LX (LNW74 only)

OC-3/12/48 (UPSR), OC-48 BLSR, 1000-SX/LX/

ZX, 100-LX/TX

OC-3/12/48 (UPSR) and OC-48 BLSR w/ NUT

DS1, E1, DS3, EC-1, TransMUX, OC-3/12 (1+1,

0x1Sn, 0x1, and UPSR), OC-48 (UPSR and

BLSR), 1000-SX/LX/ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12 (1+1, 0x1Sn,

0x1, and UPSR), OC-48 (UPSR), 100-TX/LX

(LNW74 only)

OC-48 Low-Speed OLIU (BLSR)

1-way STS-n ---------------------> DS1, E1, DS3, EC-1, TransMUX, OC-3/12 (1+1,

UPSR, 0x1, and 0x1Sn), OC-48 (BLSR), 1000-

SX/LX/ZX, 100-TX/LX, FC-DATA

5 - 5 8

365-372-300

Issue 8.0, September 2006

Allowable Cross-Connects

System Planning and Engineering

From

1-way VT1.5-------->

1-way unswitched STS-n-------->

1-way unswitched VT1.5-------->

OC-48 Low-Speed OLIU (0x1)

(requires LNW59 VLF Main)

1-way STS-n --------------------->

Future Feature

OC-3/12 (UPSR), 1000-SX/LX/ZX, 100-LX/TX

OC-3/12 (UPSR)

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(UPSR, 1+1, 0x1) and OC-48 BLSR, 1000-SX/

LX/ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1), 100-TX/LX (LNW74 only)

OC-48 Low-Speed OLIU (0x1Sn) (non-

VLF Mains only)

1-way STS-n --------------------->

1-way VT1.5-------->

DS1, E1, DS3, EC-1, TransMUX, OC-3/12/48

(UPSR, 1+1, 0x1Sn) and OC-48 BLSR, 1000-SX/

LX/ZX, 100-TX/LX, FC-DATA

DS1, EC-1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1Sn), 100-TX/LX (LNW74 only)

1000-SX/LX (LNW67/68)

1-way STS-n ---------------------> 100-TX/LX, 1000-SX/LX/ZX, OC-3/12/48 (1+1,

UPSR, 0x1, 0x1Sn), OC-48 BLSR

OC-3/12/48 (UPSR) and OC-48 BLSR w/ NUT 1-way unswitched STS-n-------->

100-TX/LX- non private line

1-way STS-n --------------------->

1-way unswitched STS-n-------->

1000-SX/LX/ZX, OC-3/12/48 (1+1, UPSR, 0x1,

0x1Sn) and OC-48 BLSR

1000-SX/LX/ZX, OC-3/12/48 (UPSR) and OC-48

BLSR w/NUT

100-FEPL (private line)

1-way STS-n --------------------->

1-way unswitched STS-n-------->

FC-DATA (FC/FICON/ESCON)

1000-SX/LX/ZX, OC-3/12/48 (1+1, UPSR, 0x1,

0x1Sn) and OC-48 BLSR

OC-3/12/48 (UPSR) and OC-48 BLSR w/ NUT

365-372-300

Issue 8.0, September 2006

5 - 5 9

Allowable Cross-Connects

From

1-way STS-n --------------------->

TransMUX (LNW18 and LNW20)

1-way STS-n --------------------->

1-way VT1.5 ------->

DS1/E1

1-way STS-n --------------------->

1-way VT1.5 ------->

DS3

1-way STS-n --------------------->

EC-1

1-way STS-n --------------------->

System Planning and Engineering

OC-3/12/48 (1+1 and UPSR) and OC-48 BLSR

TransMUX, DS1, OC-3/12/48 (1+1 and UPSR) and OC-48 BLSR

DS1/E1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1, 0x1Sn) and OC-48 BLSR

DS1/E1, TransMUX, OC-3/12/48 (1+1 and

UPSR) and OC-48 BLSR

DS3, OC-3/12/48 (1+1, UPSR, 0x1, 0x1Sn) and

OC-48 BLSR

EC-1, DS1, TransMUX, OC-3/12/48 (1+1, UPSR,

0x1, 0x1Sn) and OC-48 BLSR

5 - 6 0

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Assignment of VT Bandwidth on OC-48 and OC-12 High-speed

Interface

Overview

When using the OC-48 OLIU (LNW26B, LNW28, LNW77,

LNW121B-LNW159B) or OC-12 OLIU (LNW48, LNW50, and LNW

54) in M1 and M2, for VT add/drop cross-connections, VT hairpin cross-connections, and VT pass through cross-connection, the following restrictions apply

Important!

The following restrictions do not apply to the

LNW27, LNW29, LNW76, and LNW221-LNW259 OC-48 OLIU circuit packs.

VT Fabric Capacity

The VT fabric on the main OC-12/48 OLIU circuit packs (M1 and M2) supports several types of VT cross-connections.

• VT add/drop from/to OC-N OLIUs in the Function Unit and

Growth slots.

• VT add/drop from/to DS1 ports.

• VT hairpins.

• VT pass-throughs on the MAIN OC-12/48 OLIUs in M1 and M2.

The total provisionable bidirectional VT cross-connect capacity of 336

VT1.5s is shared among the four types of VT cross-connections.

Important!

The "dual tatrib" modes (MONEF and SPLTEF) of

VT test access are not possible when the system is equipped with small/medium VT fabric Main OLIUs, such as those listed above.

For more information refer to the

VT1.5 Test Access Matrix

Source and Destination Restrictions

The user can not provision a VT1.5 connection whose source STS is the same as the destination STS of another VT1.5 connection. Source and destination are not a function of the src_aid and dest_aid in the

ENT-CRS-rr command. Rather source and destination are determined based on the relative STS number. The lower STS number is designated as the source and the higher STS number is designated as the destination based on the following ordering of the slots, main < fna

< fnb < fnc < fnd < growth.

365-372-300

Issue 8.0, September 2006

5 - 6 1

Assignment of VT Bandwidth

System Planning and Engineering

The one exception to this rule is for cross-connections to DS1 ports on the LNW6 and LNW7 packs. For these connections the OC-N port is always the source and the DS1 port is always the destination. The following example illustrates the restriction. Note, the commands are not syntactically correct. They are intended only to show the aids.

Example

The ENT-CRS-VT1 command uses the following aid format for the src_aid and dest_aid parameters. {group}-{line}-{STS}-{VTG}-

{VT1.5}.

Step 1:

Ent-crs-vt1:b-1-1-1-1,a-1-1-1-1 cross-connects a VT1.5 in FN Group A to a VT1.5 in Function Group B. According to the rule defined above, the lower STS channel (a-1-1) is designated the source and the higher

STS channel (b-1-1) is designated the destination.

Step 2:

Ent-crs-vt1:b-1-1-1-2,c-1-1-1-2 cross-connects a VT1.5 in FN Group B to a VT1.5 in Function Group C.

In the above example, the cross-connection in step 2 (b-1-1-1-1 to c-1-

1-1-2) would be denied because the source STS (b-1-1) is the same as the destination STS channel (b-1-1) in the cross-connect established in step 1 (b-1-1-1-1 to a-1-1-1-1).

Pass-through Restrictions

If the Main slots are equipped with OC-48 OLIU (LNW26 only-- not supported in R6.0) or OC-12 OLIU (LNW48, LNW50, and LNW 54) circuit packs provisioned to support VT1.5 signals in up to 6 STS-1 signals, VT pass-through cross-connections on the Main circuit packs can in some cases conflict with VT add/drop cross-connections and VT hairpin cross-connections. This restriction, however, cannot be characterized by a set of rules. Requests to establish a VT crossconnection that would result in a conflict between a VT pass-through cross-connection on the main and a VT add/drop or VT hairpin crossconnection will be denied.

5 - 6 2

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Synchronization

Overview

Purpose

This section describes synchronization features and functions for the

DMX Access Multiplexer.

Contents

The following synchronization topics are discussed in this section:

Network Synchronization Environment

Synchronization Features

Network Configurations

Timing Distribution

Synchronization Messaging

Sync Messaging Feature Details and Options

Sync Messaging Examples

Frequently Asked Network Timing Distribution Questions

365-372-300

Issue 8.0, September 2006

5 - 6 3

System Planning and Engineering

Network Synchronization Environment

Overview

Careful consideration should be given to proper design of the SONET network’s synchronization environment. Proper synchronization engineering minimizes timing instabilities, maintains quality transmission network performance, and limits network degradation due to unwanted propagation of synchronization network faults. The synchronization features of the DMX are designed to complement the existing and future synchronization network and allow it not only to make use of network timing but also to take on an active role in facilitating network synchronization.

Published sources

A number of published sources give generic recommendations on setting up a synchronization network. The DMX is designed to operate in a network that complies with recommendations stated in GR-253-

CORE and the following documents:

• GR-436-CORE, Digital Synchronization Network Plan

• GR-378-CORE, Generic Requirements for Timing Signal

Generators (TSG)

• ANSI T1.101, Synchronization Interface Standards for Digital

Networks

• GR-1244-CORE, Clocks for the Synchronized Network: Common

Generic Criteria.

5 - 6 4

365-372-300

Issue 8.0, September 2006

Network Synchronization Environment

Recommendations

System Planning and Engineering

The following are some key recommendations from the documents listed above. For further detailed explanation, the sources should be consulted directly.

A node can only receive the synchronization reference signal from another node that contains a clock of equivalent or superior quality (Stratum level).

The facilities with the greatest availability (absence of outages) should be selected for synchronization facilities.

Where possible, all primary and secondary synchronization facilities should be diverse, and synchronization facilities with the same cable should be minimized.

The total number of nodes in series from the Stratum 1 source should be minimized. For example, the primary synchronization network would ideally look like a star configuration with the

Stratum 1 source at the center. The nodes connected to the star would branch out in decreasing Stratum level from the center.

No timing loops may be formed in any combination of primary and secondary facilities.

Stratum 3 Timing

Generator

DMX supports a Stratum 3 Timing Generator (TG3) embedded in each high speed (MAIN) Main Switch pack (LNW80), OC-12, OC-48, and

OC-192 optical interface circuit pack. The TG3 operates with an internal oscillator of ± 4.6 ppm long-term accuracy in the free running mode, while in holdover the accuracy is ± .37 ppm over the full -40 to

+65 o

C temperature range. The TG3 should be used according to the recommendations in the documents referenced previously.

365-372-300

Issue 8.0, September 2006

5 - 6 5

System Planning and Engineering

Synchronization Features

Overview

Synchronization is an important part of all SONET products. DMX is designed for high performance and reliable synchronization and can be used in a number of synchronization environments. Each DMX can be provisioned to free run from an internal oscillator, line time from an incoming high-speed interface, or get external timing from the digital synchronization network via DS1/E1 references. DMX also supports distribution of timing references using DS1/E1 timing outputs.

Synchronization features

DMX supports three synchronization reference configurations:

•

External Timing

from a Stratum 3 or better office clock (typical

CO installations should be synchronized with DS1 or E1 timing references from a Stratum 3).

•

Line Timing

from incoming high-speed OC-12/OC-48/OC-192 signal (for small COs or remote sites).

•

Line Timing from tributaries

derived from incoming low-speed

OC-3/12/48 signal.

•

Free Running

from the multiplexer’s internal Stratum 3 Timing

Generator (no synchronization inputs).

These timing modes are supported by the embedded Stratum 3 Timing

Generator in the OC-12, OC-48 or OC-192 circuit pack. The four basic timing modes can be combined into various network configurations.

Line timing from high-speed lines is not available when using the

LNW80 in the MAIN slots; line timing from tributaries is available when using the LNW80.

Internal timing functions such as reference interfaces, the on-board clock elements, and timing distribution, are provided by the Stratum 3

Timing Generator. The timing generator distributes clock and frame signals, derived from the selected reference source, to the transmission packs.

5 - 6 6

365-372-300

Issue 8.0, September 2006

Synchronization Features

External timing mode

System Planning and Engineering

In external timing mode, the timing generator accepts two DS1 or E1 references from an external Stratum 3 or better clock. This Stratum 3

(or better) clock would typically be traceable to a primary reference source (PRS). The DS1/E1 references from the clock synchronize the local DMX with other network equipment operating under the same primary clock source. A high-stability digital phase-locked loop

(DPLL) removes transient impairments on the DS1/E1 references for improved jitter performance.

The PRS is equipment that provides a timing signal whose long-term accuracy is maintained at 10

-11

or better with verification to universal coordinated time, and whose timing signal is used as the basis of reference for the control of other clocks in the network. Universal coordinated time is a time and frequency standard maintained by the

US National Institute of Standards and Technology.

Line timing mode

In line timing mode, the TG3 derives local shelf timing from the incoming service OC-12, OC-48, or OC-192 high-speed signal in the

Main slot. The DPLL serves to remove any timing transients for improved network jitter performance. When provisioned for automatic protection switching, if one of the OC-n references is corrupted or unavailable, the TG3 will make a revertive or nonrevertive protection switch to the other reference without causing timing degradations.

Beginning in R4.0, synchronization reference mode switching can be either revertive or nonrevertive. You can also provision MAIN-1-1 or

MAIN-2-1 as the primary reference. If all OC-n timing signals are lost, the TG3 will switch to holdover mode. The TG3 will normally switch back to the line timing mode when a reference is no longer corrupted and clock mode switching is set to revertive. Yet it can be provisioned to require a manual switch. Switching between the two Main OC-n reference inputs can also be done using a manual command.

365-372-300

Issue 8.0, September 2006

5 - 6 7

Synchronization Features

System Planning and Engineering

Line Timing from Optical

Tributary Packs (R7.0)

Function Unit, or Growth slots.

All optical circuit packs can derive a 6.48MHz timing signal from an incoming optical line.

There is a single line timing reference clock signal from each Function

Unit/Growth slot to the MAIN/Timing Generator (TG). On a Function

Unit/Growth circuit pack with multiple ports, port selection is made on the Function Unit/Growth pack, not on the MAIN/TG. Non-VLF

MAINs have 2 MAIN, 2 Growth and one Function group line reference input. Function group slot selection and line reference protection switching is done on the MAIN circuit pack, but remains external to

TG. VLF MAINs have separate inputs for all MAIN, Growth and

Function Unit slots. Slot selection and line reference protection switching is done within the TG. DS1/E1 Sync Out is always derived from the provisioned line timing source.

Free running mode

In free running mode, no mode switching is performed. The timing generator derives timing from a high stability temperaturecompensated, voltage-controlled crystal oscillator that has an end of life performance of +/- 4.6 ppm. This oscillator is capable of Stratum 3 accuracy. Only one DMX in a subnetwork can be provisioned in the free running mode. All other DMX NEs in the subnetwork must be line timed to this free running system to avoid performance degradation.

DS1/E1 timing output

DMX also supports a DS1 or an E1 timing output feature that facilitates network timing distribution. E1 timing outputs are available with the

LNW59 VLF Main. The DS1/E1 timing output is derived from the OCn line rate, so it is not subjected to multiplexing or pointer processing effects. The result is a DS/E1 traceable to the far-end source with extremely low jitter and wander. The timing output can be locked to an

OC-n line or the OC-n source can be automatically selected using synchronization messages. In either case Threshold AIS may be enabled to insert AIS if the synchronization message of the OC-n source matches a provisioned threshold.

The frame format on the DS1 output is provisionable as superframe format (SF) or extended SF (ESF). The E1 frame format can be provisioned as FAS or CRC4. The DS1/E1 is a framed all-ones signal under normal conditions or an AIS signal under failure conditions.

5 - 6 8

365-372-300

Issue 8.0, September 2006

Synchronization Features

System Planning and Engineering

SDH Synchronization

(R7.0)

Beginning in R7.0, and with the use of the LNW59 VLF Main pack,

DMX supports E1 timing references. SDH synchronization conforms to industry standards for frequency accuracy, pull-in, hold-in and pullout ranges, wander, jitter, noise tolerance, noise transfer, transient response, holdover performance (per ITU-T G.813), and for SDN Sync

Status Messaging (per ITU-T G.704).

Dual Reference Monitoring

(DRM) (R7.0)

Beginning in R7.0, and with the use of VLF Mains, both external timing references are monitored simultaneously, even when the Timing

Generator (TG) is in holdover mode. So, if an external reference fails, the Out of Lock (OOL) status of the standby reference is already known and the decision to switch to the standby reference can be made with certainty that the standby reference is not in an OOL condition. If the TG is in holdover mode, or if it has switched references with revertive reference switching enabled, it can monitor the OOL reference(s) for a non-OOL condition and switch to the good reference with certainty that the reference is in fact not in an OOL condition. It will also autonomously clear the OOL alarm.

With non-VLF MAINs both external timing references are monitored for LOS, LOF, AIS, BER & EOOF failures, but only the active reference can be monitored for frequency offset OOL failures, and only when the TG is locked to the reference. Frequency offset of either external reference cannot be monitored when the TG is in holdover or freerunning modes.

When a failure of the active reference occurs, if reference switching is enabled, and if the standby reference doesn’t have an LOS, LOF, AIS,

BER & EOOF failure, the NE switches to the standby reference and locks to it, and then monitors its frequency offset for an OOL condition. If the standby reference does have an OOL failure, the TG goes into holdover mode and issues a major sync alarm for both references failed (subject to ASAP provisioning).

Holdover mode

When line or external timing is used, in case of unprotected synchronization reference failure, the TG3 will switch to “holdover mode” and continue to provide system timing using the internal oscillator to maintain the last known good reference frequency. If the

DS1/E1 timing output is enabled for network synchronization, DS1 or

E1 AIS is inserted on detection of unprotected optical reference failure.

365-372-300

Issue 8.0, September 2006

5 - 6 9

System Planning and Engineering

Network Configurations

Overview

The following pages detail the three different network configuration types: free running/line timing, external timing/line timing, and external timing.

Free running/line timing configuration

For initial SONET deployment with DS1 and/or DS3 low-speed interfaces, minimum first cost may be a primary concern. The free running/line timing network can operate without an external clock source, so the expense of connecting to one is eliminated. This configuration may be useful for initial access transport and customer location applications, and also meets the needs of an end-office trunk facility. This configuration should not be used to provide OC-n timing distribution or where SONET interconnections to other SONET networks are needed.

The local DMX times its transmitted signals at the low- and high-speed interfaces from the internal +/- 4.6 ppm of the Stratum 3 timing generator. The remote DMX recovers timing from the incoming OC-n signal and uses this timing for its transmitted signals.

Certain interconnected equipment may be sensitive to such jitter and this configuration should not be used in cases where it would cause a problem for that equipment. In particular, downstream equipment containing Stratum 3 or better clocks could be sensitive to this jitter.

5 - 7 0

365-372-300

Issue 8.0, September 2006

Network Configurations

System Planning and Engineering

The figure below shows free running/line timed configuration in a ring network.

Figure 5-14 Free Running/Line Timed Configuration - Ring

Network

TG3

DMX

Line-Timed

Note

OC3/12/48/192

TG3

DMX

Free Running

Note

OC3/12/48/192 OC3/12/48/192

TG3

OC3/12/48/192

DMX

Line-Timed

Note

Note: DS1/DS3/EC-1/E1/Ethernet/OC-3/OC-12/OC-48

TG3

DMX

Line-Timed

Note nc-dmx2-025

365-372-300

Issue 8.0, September 2006

5 - 7 1

Network Configurations

Present Mode of Operation

System Planning and Engineering

Line timing from Main interfaces vs. line timing from tribs

The figure below shows various DMX shelves in line timing mode. The top portion of the figure shows the present mode of operation where line timing references must be derived from optical lines entering the

Main network interface circuit packs.

The bottom portion of the figure represents DMX’s capability to derive timing references from optical lines entering both the Main and tributary interface circuit packs. Line timing from tributary interfaces is made possible in R7.0. Prior to R7.0, DMX could only derive timing references from the Main network interface circuit packs. DMX can utilize tributary line timing when equipped with VLF Mains (LNW59),

Non-VLF Mains (all other Main interface optical packs), and headless

Main (LNW80) packs.

As shown in the top right of the figure below, the only two shelves that can serve as line timing sources in the present mode of operation are the two furthest to the right. This is because they are connected Main to

Main, while the other shelves are transmitting optical signals from tributary interfaces to Main interfaces (or vice versa). The bottom portion of the figure shows how tributary line timing allows any DMX shelf in the topology pictured to serve as the line timing source.

Figure 5-15 Tributary line timing references

Timing Source must be either of these two nodes

OC-48 1 + 1 OC-48 1 + 1

OC-483 1 + 1

OC-48 1 + 1

Main to Trib

Timing From Tribs

OC-48 1 + 1

Main to Trib

Main to Trib i b

T r s

OC-48 1 + 1

Trib to Trib

Main to Trib Main to Main

Timing Source can be at any node

OC-48 1 + 1

Main to Trib

OC-483 1 + 1

Main to Main

MA-DMXAPG-043

5 - 7 2

365-372-300

Issue 8.0, September 2006

Network Configurations

System Planning and Engineering

External timing/line timing configuration

The external timing/line timing configuration integrates access transport and customer location networks into the digital synchronization network as required by the SONET standard. This application is ideal for networks where only one location has a building integrated timing supply (BITS) clock, for example, access transport.

The network is synchronized to a local central office clock via DS1 references. The local office clock should be Stratum 3 or better, with timing traceable to a primary reference source. The local DMX times its transmitted signals at the low- and high- speed interfaces from the internal oscillator that is locked on the external reference. The remote

DMX recovers timing from the incoming OC-n (OC-3/12/48/192, tributary or Main interface) signal and uses this timing for its transmitted signals.

External timing is required when EC-1 low-speed interfaces are used to interconnect the local DMX with other SONET equipment. Thus, the external timing/line timing configuration should be the long-term goal for all access transport and customer location applications.

In a ring topology, synchronization messaging allows automatic synchronization reconfiguration in the event of a fiber or equipment failure.

The figure below shows external timing/line timing in a ring configuration.

365-372-300

Issue 8.0, September 2006

5 - 7 3

Network Configurations

System Planning and Engineering

Figure 5-16 External Timing/Line Timing - Ring Network

External Clock

(Stratum 3 or better)

DS1

TG3

OC3/12/48/192

DMX

Line-Timed

Note

DMX

External-Timed

Note

OC3/12/48/192 OC3/12/48/192

TG3

DMX

External-Timed

Note

Note: DS1/DS3/EC-1/E1/Ethernet/OC-3/OC-12/OC-48

OC3/12/48/192

TG3

DMX

Line-Timed

Note nc-dmx2-024

5 - 7 4

365-372-300

Issue 8.0, September 2006

Network Configurations

System Planning and Engineering

External timing configuration

The external timing configuration uses external DS1or E1 timing to each DMX in the network. Since it requires local office clocks at each site, it is most suited to interoffice applications. A DMX network may have all DS1/E1 references traceable to a common primary reference source (for example, outstate trunking) referred to as synchronous, or to multiple primary reference sources (for example, a carrier-to-carrier interface). The multiple primary reference source is referred to as plesiochronous operation. The figure below shows an external timing configuration.

A tributary signal (for example, DS1) that traverses several plesiochronous regions may encounter increased STS-1 and VT pointer adjustments compared to that encountered in a synchronous environment. These pointer adjustments may increase jitter on the tributary when dropped from the SONET network. While standard jitter generation limits are perfectly acceptable for most service needs, some data services or other equipment may be particularly sensitive to jitter-induced degradations. Therefore, it is generally desirable to minimize the number of plesiochronous regions within a network, through Stratum 1 clock traceability and line timing of remote SONET elements.

Figure 5-17 External Timing Configuration - Ring Network

PRS Traceable

External Clock

(Stratum 3 or better)

DS1

External Clock

(Stratum 3 or better)

DS1

PRS Traceable

TG3

OC-3/12/48/192

DMX

External-Timed

Note

TG3

DMX

External-Timed

Note

OC-3/12/48/192 OC-3/12/48/192

TG3

OC-3/12/48/192

DMX

External-Timed

Note

TG3

DMX

External-Timed

Note

DS1

PRS Traceable

External Clock

(Stratum 3 or better)

DS1

Note: DS1/DS3/EC-1/E1/Ethernet/OC-3/OC-12/OC-48

DS1

External Clock

(Stratum 3 or better)

PRS Traceable nc-dmx2-023

365-372-300

Issue 8.0, September 2006

5 - 7 5

Network Configurations

System Planning and Engineering

External timing with DS1/E1 timing output

External timing may be combined with the DS1/E1 timing output feature as shown in the figure below (E1 not pictured). Note that the

DS1/E1 timing output feature and plesiochronous operation are mutually exclusive. Each of the network topologies (linear, hubbing, ring) can use external timing.

Figure 5-18 DS1/E1 Timing Output and Plesiochronous Timing

Configurations

Clock Source

(Stratum 3 or better)

DS1

External Clock

(Stratum 3 or better)

DS1 DS1 Timing out

TG3

OC-3/12/48/192

Metropolis

DMX

TG3

Metropolis

DMX

DS1/DS3/EC-1/E1/Ethernet/OC-3/

OC-12/OC-48

(a) External Timing Configuration

DS1/DS3/EC-1/E1/Ethernet/OC-3/

OC-12/OC-48

Clock Source

(Stratum 3 or better)

DS1

May be Plesiochronous

External Clock

(Stratum 3 or better)

DS1

TG3

OC-3/12/48/192

Metropolis

DMX

TG3

Metropolis

DMX

DS1/DS3/EC-1/E1/Ethernet/OC-3/

OC-12/OC-48

DS1/DS3/EC-1/E1/Ethernet/OC-3/

(b) External Timing Plesiochronous

OC-12/OC-48

CO nc-dmx2-022

5 - 7 6

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Timing Distribution

Network timing distribution

DS1 signals have long been used to pass timing information through the network synchronization hierarchy. With R7.0 and the LNW59

VLF Main, E1 timing outputs are also supported. These DS1/E1 timing references should be transmitted between master and slave clock sources over the most reliable facilities available. In some cases, these

DS1/E1 signals also carry traffic. The facility of choice has evolved from T-carrier through asynchronous lightwave systems to SONET lightwave systems. As these systems are upgraded to SONET systems, timing distribution plans should be revisited to ensure the quality of the timing signals are not degraded. With proper planning, SONET can be used to improve the overall quality of the network timing.

Interoffice timing distribution

One way SONET can be used to improve the quality of interoffice network timing is through the use of OC-n (OC-3/12/48/192) timing distribution. DMX supports the evolution to interoffice OC-n timing distribution by providing a DS1/E1 timing output derived from the incoming OC-n signal. The DS1/E1 timing output is traceable to the clock source that times the DMX subnetwork and has extremely low jitter and wander. This is true regardless of the number of DMX systems connected in the network. This DS1/E1 can be fed to the local

BITS clock which subsequently times the local DMX and the other equipment in the office. If a BITS clock is not available in the office, the DS1/E1 timing output can be used to time other equipment

(including another DMX) directly. DMX can provide DS1/E1 timing outputs in all supported topologies (for example, add/drop and ring) in the main slots prior to R7.0. R7.0 adds support for line timing from tributary optical interfaces, allowing DMX to provide DS1 timing outputs even when equipped with the LNW80 headless main. E1 timing outputs are available only when the LNW59 Main is used.

365-372-300

Issue 8.0, September 2006

5 - 7 7

Timing Distribution

System Planning and Engineering

With OC-n timing distribution, the OC-n line signal, rather than a DS1/

E1 multiplexed into the SONET payload, will provide a timing transport mechanism better suited to a complex, heavily interconnected

SONET network. In this configuration, a DS1 reference from the CO

BITS clock still times the OC-n transmitted to the remote site. At the remote site, a DS1/E1 output reference is created directly from the received OC-n signal, as shown in the figure below (E1 not pictured).

Figure 5-19 OC-n (OC-3/12/48/192) Derived DS1 Timing Reference

Slave Clock

DS1 out

DS1

External Clock

(Stratum 3 or better)

DS1

OC-3/12/48/192

Other

Network

Elements

TG3

DMX

DS1/DS3/EC-1/E1/Ethernet/OC-3/

OC-12/OC-48

TG3

DMX

DS1/DS3/EC-1/E1/Ethernet/OC-3/

OC-12/OC-48

CO nc-dmx2-021

Potential advantages

OC-n (OC-3/12/48/192) timing distribution has several potential advantages. It preserves transport bandwidth for customer services and guarantees a high-quality timing signal. Also, as the CO architecture evolves to replace DSX interconnects with SONET EC-1 interconnects and direct OC-n interfaces, OC-n distribution becomes more efficient than multiplexing DS1 references into an access facility in the CO.

A previous drawback to using OC-n timing distribution was that the network timing failures could not be communicated to downstream clocks via DS1 AIS, since the DS1 signal does not pass over the OC-n interface. A standard SONET synchronization messaging scheme to convey synchronization failures is now in place. The DMX multiplexer supports this synchronization messaging scheme. With this option, clock Stratum levels can be passed from NE to NE, allowing downstream clocks to switch timing references without creating timing loops, if a network synchronization failure occurs. If a quality timing reference is no longer available, the DMX sends AIS over the DS1 interface. If the local OC-n lines fail, DMX outputs AIS on the DS1 output or an upstream DMX enters holdover.

5 - 7 8

365-372-300

Issue 8.0, September 2006

Timing Distribution

System Planning and Engineering

Access network timing distribution

OC-n (OC-3/12/48/192) timing distribution can also be used in access networks or to small COs. In this configuration, a DS1 reference from the CO BITS clock still times the OC-n transmitted to the remote site.

The line timing capability of DMX provides the ability to recover OC-n timing. The DS1 timing output feature can be used to also extend timing to customer networks or remote sites. In this case, the DS1 timing output may be used to time switch remotes, DMX shelves, or other local equipment directly. Ideally, the equipment can provide an external timing reference. Otherwise, the signal must be input to a traffic DS1 port on the external equipment which will tie up some of this equipment’s bandwidth. In this configuration, it is important that the DS1 reference to the DMX in the CO be traceable to the same clock used to source the DS1s being carried to the customer site or small CO.

If it is not, slips may occur.

Alternate timing sources

Although an ideal source of timing, OC-n timing distribution, via a

DS1 timing output, cannot be used to provide timing in all applications.

In cases where the local equipment is not provided with an external timing reference input, or in some private networks where the timing is to be distributed from another private network location, timing may be distributed via traffic-carrying DS1s. In these applications, a stable

DS1 timing source can be achieved by ensuring that all elements in the

SONET network are directly traceable to a single master clock via line timing. In this environment, the high-performance desynchronizer design of the DMX allows a DS1 timing reference to be carried as a multiplexed DS1 payload.

It is recommended that, where possible, the DS1 sources (switch, PBX, or other equipment) be traceable to the same timing source used to time the DMX SONET network. Multiplexed DS1 reference transport is also consistent with current planning and administration methods.

Applications include passing synchronization from the public switched network to a PBX-based private network (see figure on following page) and synchronizing an end-office remote switch to a larger office’s host switch.

Note:

Synchronous operation via line timing eliminates the generation of VT pointer adjustments, thus maintaining the phase stability needed for a high-quality DS1 timing reference. Cross-connecting at the STS-1 level also eliminates the VT pointer adjustments. While the design of the

DMX maintains jitter/wander within standard DS1 interface requirements, even in the presence of VT pointer adjustments, and

365-372-300

Issue 8.0, September 2006

5 - 7 9

Timing Distribution

System Planning and Engineering

while the DS1 is likely to be stable enough for most equipment to use as a timing reference, some equipment may have more stringent stability requirements for its timing references.

Figure 5-20 Timing from Multiplexed DS1

External Clock

(Stratum 3 or better)

DS1

TG3 TG3

OC-N

DMX

Customer

Network

DS1

DS1 Carrying Data and Used as a

Timing Reference

PBX

Signal may not go directly from DMX to the POX, but may pass through another piece of equipment such as a DDM-2000 OC-3 multiplexer

DMX = Metropolis DMX Access Multiplexer

DMX

DS1

CO nc-dmx2-020

5 - 8 0

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Synchronization Messaging

Overview

DMX provides a synchronization messaging feature to ensure the integrity of network synchronization during both normal and abnormal conditions. Through the use of synchronization messaging, the current quality of the timing source can be conveyed from one DMX

Multiplexer to the next. This capability allows the DMX to automatically change its timing reference in order to always maintain the highest quality timing available. The capability also allows the

DMX to inform a local BITS clock when the DS1/E1 timing output has been degraded and should no longer be used as a reference. This synchronization messaging feature is compliant with the scheme developed in the ANSI T1X1 standards committee.

Also, the same parameter used to chose between DS1 and E1 timing outputs is employed to choose between SONET sync messaging (ANSI

T1X1 mentioned above) and SDH sync messaging.

Applications

The applications that are currently supported with the synchronization messaging feature can be divided into three categories:

• DS1/E1 timing output integrity

• Automatic synchronization reconfiguration

• Synchronization provisioning integrity.

365-372-300

Issue 8.0, September 2006

5 - 8 1

Synchronization Messaging

System Planning and Engineering

DS1 timing output integrity

The derived DS1 timing outputs are typically used as a synchronization reference to a BITS clock which provides the timing reference to an externally-timed DMX Multiplexer. The synchronization reference is derived from the SONET transmission facility which is synchronized from an upstream timing reference. In this way, the timing from the

BITS clock in one office (master) is distributed to the next office

(slave) using the SONET transmission facilities between them as the synchronization vehicle.

The BITS are typically capable of synchronizing to a Stratum 3 or better accuracy. The DMX equipped with the embedded Stratum 3 timing generator is capable of synchronizing to a +/- 4.6 ppm clock or better. The Stratum timing hierarchy requires that clocks of equal or better Stratum level be used to synchronize other clocks. In this way, the Stratum timing hierarchy is preserved under all failure conditions.

Under non-failure conditions, the DMX does not introduce its own internal timing source onto the SONET facility, but merely transfers the quality of its timing reference. A failure of all derived DS1 timing references to the BITS at the master office will cause the BITS to enter holdover mode, whose minimum accuracy is dependent on its internal clock. If the BITS internal clock is of equal or better Stratum level than the DMX, the externally-timed DMX will use this reference to synchronize all outgoing SONET transmission facilities. This preserves the required hierarchical structure of the timing network and should be maintained at all times.

If the externally-timed DMX at the master office enters holdover due to a disconnected reference cable or a local BITS failure, the quality of the derived DS1 timing output at the slave office will now be traceable directly to the DMX. The Stratum timing hierarchy will be violated if the slave office BITS requires timing accuracy of better Stratum level than that provided by the master DMX’s internal clock. Because the

DMX contains the embedded Stratum 3 Timing Generator, Stratum 3 accuracy will be maintained indefinitely. This provides acceptable timing for Stratum 3 NEs at slave offices.

Another scenario that will cause the Stratum timing rules to be violated is when at least one line-timed DMX exists at a site between the master and slave offices. In this scenario, a fiber cut between the master office and the line-timed site will cause the line-timed DMX to enter holdover

(with accuracy dependent upon its internal clock). If the BITS at the slave office requires a higher accuracy clock than that generated by the

DMX in holdover, the Stratum timing hierarchy will be violated.

5 - 8 2

365-372-300

Issue 8.0, September 2006

Synchronization Messaging

System Planning and Engineering

Automatic synchronization reconfiguration

SONET was designed to operate optimally in a synchronous environment. Although plesiochronous and asynchronous operation can be supported through the use of pointer adjustments, transmission quality is affected by the generation of additional jitter and wander due to pointer adjustments. Because of this, it is desirable to maintain synchronous operation whenever possible. Through the use of synchronization messages, the quality of the different timing references can be made available at each DMX NE. The DMX shelf can be optioned to determine the best timing reference available and switch to that reference. Through this mechanism, the synchronous operation of the subnetwork can be maintained. The switching of timing references is hitless, and the synchronization messages also allow it to be done without creating timing loops in the process.

365-372-300

Issue 8.0, September 2006

5 - 8 3

Synchronization Messaging

System Planning and Engineering

Access ring network

Under normal operation in the access ring network pictured in the figure below, the ring has one DMX externally timed and the others line timed in one direction (clockwise or counterclockwise). The result is that the ring is again operating synchronously. The ring already provides self-healing of the traffic, so it is especially important to maintain synchronous operation during this type of failure to prevent service degradation due to increased jitter and wander.

Figure 5-21 Synchronization Reconfiguration - Access Ring

Normal Failure/Reconfiguration

PRS

Traceable

BITS

PRS

Traceable

BITS

DMX DMX

DMX DMX DMX DMX

DMX

Sync Flow nc-dmx2-019

Synchronization provisioning integrity

A welcome side feature of synchronization messaging is that it helps prevent provisioning errors. Provisioned timing loops on DMX

Multiplexers will be quickly detected through the synchronization messaging algorithm and prevented by forcing a shelf into holdover.

The system can then be reprovisioned correctly.

5 - 8 4

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Sync Messaging Feature Details and Options

Overview

As mentioned previously, SONET sync messaging is used to communicate the quality of the subnetwork timing throughout the subnetwork. This is done using bits 5-8 of the S1 byte in the SONET overhead. If a DMX shelf is deriving timing from a given OC-n interface, and sync messaging is enabled on that interface, the system interprets the received message to determine the system’s timing status.

The system also determines the state of the DS1 output, if the DS1 output is enabled, by forcing a DS1 AIS on the DS1 sync outputs if the timing status received on the OC-n interface is below a provisioned quality threshold. DMX also transmits over the particular OC-n interface, and all other OC-n interfaces that are enabled for sync messaging, the appropriate message indicating the quality of its timing and its usability.

365-372-300

Issue 8.0, September 2006

5 - 8 5

Sync Messaging Feature Details and Options

Sync messages using

S1 byte

System Planning and Engineering

The following table lists the associated internal timing status and DS1/

E1 output states that are associated with sync messages (using the S1 byte) received from the OC-n interface when sync messaging is enabled. The same parameter used to chose between DS1 and E1 timing outputs is employed to choose between SONET sync messaging and SDH sync messaging. Messages are listed from low to high quality.

Table 5-10 Sync Messages with the S1 Byte

Received Message

Don’t Use (DUS)

Traceable Stratum 4 (ST4)

(Note 4)

Traceable SONET Clock w/S3-TG

(SMC)

Traceable Stratum 3 (ST3) (Note 3)

Traceable Stratum 3E (ST3E)

Traceable Transit Node Clock (TNC)

Traceable Stratum 2

Sync Trace Unknown (STU)

PRS Traceable (Note 3)

Active Timing

Mode (Note 1)

Holdover

OK to use

Ok to use

OK to use

DS1/E1

Output State

(Note 2)

AIS

Good

Quality

Level

Notes:

This column applies only when provisioned for line timing mode.

This table represents DS1/E1 output AIS threshold equal to level

The embedded TG3 is Stratum 3.

As of R7.0, Telcordia has not assigned a value to the S1 byte for

ST4.

5 - 8 6

365-372-300

Issue 8.0, September 2006

Sync Messaging Feature Details and Options

System Planning and Engineering

Disabling sync messaging

Sync messaging using the SONET S1 byte can be disabled on a per

OC-n interface basis. A

Don’t Use for Service (DUS)

message is transmitted on bits 5-8 of the S1 byte if this is done.

“Don’t use” (DUS)

The

DUS

message is sent to indicate that its timing is not suitable for synchronization (for example, back towards the line timing source).

External timing with

SYNC OUT

When DMX is configured for external timing and its DS1/E1 output port is provisioned for the SYNC OUT mode, the DUS is sent on the

OC-n interface towards the NE from which the DS1/E1 timing output is being derived. The Synchronized - Traceability Unknown (STU) message is sent on all other OC-n interfaces where sync messaging is provisioned. If the DS1/E1 output is generating AIS while the system is configured in this way, the message STU is transmitted on all OC-n interfaces.

TG3 with free running or holdover

When using the embedded TG3, if DMX is configured for free running or is in holdover mode, the Traceable Stratum 3 message is sent on all

OC-n interfaces for which sync messaging is enabled.

Line timing

When DMX is configured for line timing, the

DUS

message is sent on the OC-n interface towards the NE from which the timing is being derived. The message received on the OC-n interface is sent on all other OC-n interfaces where sync messaging is enabled.

Automatic synchronization reconfiguration

With automatic synchronization reconfiguration, the DMX shelves receive and compare the incoming sync messages on the OC-n interfaces available for line timing to select the highest quality synchronization reference available. If the received quality levels are the same on the references available for timing, the active line timing reference takes precedence. This feature guarantees the non-revertive operation of reconfiguration. In R4.0, DMX added a revertive option.

The existence of automatic synchronization reconfiguration does not affect OC-n line protection switching.

Hitless Timing and

Equipment Switching

(R7.0)

Hitless timing equipment switching enables switching from an active timing generator (TG) on one Main circuit pack to the TG on the other

Main circuit pack without incurring transmission hits on any of the

Main, Function Unit, or Growth circuit packs. This feature is only available on the VLF Main packs (LNW59). Low-speed, tributary

OLIUs that allow hitless timing switching include the following:

LNW45, LNW49, LNW55. DS1 & DS3 signals/cards are

365-372-300

Issue 8.0, September 2006

5 - 8 7

Sync Messaging Feature Details and Options

System Planning and Engineering

asynchronous, and are not affected by a timing switch. Ethernet packs are also unaffected.

5 - 8 8

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Sync Messaging Examples

Overview

In this section, some detailed examples are given to show specifically how the sync messages propagate through network and assist in the recovery from a fiber failure. Through these examples, one can extend the same concept to any other network that may include different topologies, number of sites, failure locations, and number of BITS clocks. Some examples are depicted in a linear configuration because the particular sync messaging concept is more easily conveyed in linear terms. Those concepts can be applied to DMX ring networks.

365-372-300

Issue 8.0, September 2006

5 - 8 9

Sync Messaging Examples

System Planning and Engineering

Derived DS1 with NO

Synchronization autoreconfiguration using externally timed ring

Part “a” of the figure below illustrates an externally timed access ring operating in its normal configuration. The DMX shelf at Site A is externally timed from a BITS clock referenced to a Primary Reference

Source (PRS). The remaining DMX shelves (Sites B, C, and D) are externally timed from a BITS referenced to a derived DS1 timing reference output. The STU message is sent to indicate where timing is traceable to an external BITS and where it is valid to be used.

Automatic synchronization reconfiguration is not an option for externally timed DMX shelves. Therefore, a change in the sync message will not cause an automatic synchronization reconfiguration.

In part “b”, a fiber has been cut between Sites A and B. Immediately,

DMX at site B changes the format of its derived DS1 to AIS. All other non-host nodes will track the holdover clock at Site B. Although no timing loops have been formed, the timing of all non-host nodes will differ from the host node by the accuracy of the holdover clock at Site

Figure 5-22 External Timing with Derived DS1 Output,

Part A and B

PRS Traceable

Source a) Synchronization Reconfiguration

Example (Before Failure)

BITS

CLOCK b) Synchronization Reconfiguration

(After Failure)

PRS Traceable

Source

BITS

CLOCK

STU

DMX

STU

Site A

STU

DMX

Site D Site B

DMX

STU

DMX

STU

Site A

STU

Site D Site B

DMX

STU

BITS

CLOCK

STU

Site C

DMX

STU

BITS

CLOCK

BITS

CLOCK

GOOD

STU

Site C

DMX

STU

BITS

CLOCK

BITS

CLOCK

AIS

BITS

CLOCK

Holdover

Mode

Sync Flow

DMX = Metropolis DMX Access Multiplexer nc-dmx-074

5 - 9 0

365-372-300

Issue 8.0, September 2006

Sync Messaging Examples

System Planning and Engineering

NOTE:

The BITS clocks above are shown with only one input in order to demonstrate the effects of autoreconfiguration versus nonautoreconfiguration.

365-372-300

Issue 8.0, September 2006

5 - 9 1

Sync Messaging Examples

System Planning and Engineering

Synchronization autoreconfiguration in an access ring

Part “a” of the figure below illustrates an access ring operating in its normal configuration. The DMX shelf at the CO is externally timed, and each of the other DMX shelves are line timed in a counterclockwise direction. The STU message is sent to indicate where timing is traceable to an external BITS and where it is valid to be used.

The DUS message is sent on the interface that is being used as the line timing reference and, thus, where using that timing would create a timing loop. Sync messaging and automatic synchronization have both been enabled for this network.

In part “b”, a fiber has been cut between sites A and B. Immediately, the DMX shelf at site B enters holdover and sends out the Stratum 3 message to site C. The DMX shelf at site B cannot switch to line time from site C because it is receiving the

DUS

message on that interface.

Figure 5-23 Automatic Synchronization Reconfiguration,

Part A and B

a) Before Failure

PRS

Traceable

BITS b) Failure Occurs,

Site B Changes Message

PRS

Traceable

BITS

DMX

STU

DMX

Site A

STU

DMX

Site A

STU

Site B Site D

Site C

DMX

STU

DMX

Stratum

DMX Site B Site D

Site C

DMX

STU

DMX

Sync Flow nc-dmx-173

5 - 9 2

365-372-300

Issue 8.0, September 2006

Sync Messaging Examples

System Planning and Engineering

In part c of the figure below, the DMX shelf at site C detects the incoming Traceable Stratum 3 message and sends the message to site

D. The DMX shelf at site C cannot switch to line timing from the other rotation because it is receiving the

DUS

message on that interface.

In part D of the figure below, the DMX shelf at site D detects the incoming Traceable Stratum 3 message. The STU message is a better quality message than the Traceable Stratum 3 message, so the DMX shelf at site D switches to line timing from site A. After the switch occurs, the

DUS

message is sent back to site A, and the STU message is retransmitted to site C.

Figure 5-24 Automatic Synchronization Reconfiguration,

Part C and D

c) Site C Changes Message

PRS

Traceable

BITS d) Site D Reconfigures

PRS

Traceable

BITS

STU

DMX

Site A

STU

S T3

DMX

Site B Site D

DUS

Site C

DUS

DMX

ST3

DMX

S T3

Sync Flow

DMX

ST3

STU

DMX

ST3

Site A

DUS

STU

DUS

Site B Site D

DMX

S T3

DUS

Site C

STU

DMX

S T3 nc-dmx-172

365-372-300

Issue 8.0, September 2006

5 - 9 3

Sync Messaging Examples

System Planning and Engineering

In part e of the figure below, the DMX shelf at site C detects the incoming STU message from site D. The STU message is a better quality message than the Traceable Stratum 3 message being received from site B, so the DMX shelf at site C switches to line time from site

D. After the switch occurs, the

DUS

message is sent back to site D, and the STU message is retransmitted to site B.

In part f of the figure below, the DMX shelf at site B detects the incoming STU message from site C. The STU message is a better quality message than the internal holdover capability, so the DMX shelf at site B switches to line time from site C. After the switch occurs, the

DUS

message is sent back to site C, and the STU message is forwarded to site A. When the failure clears, the synchronization remains in the new configuration unless it is manually switched back.

Figure 5-25 Automatic Synchronization Reconfiguration

Part E and F

e) Site C Reconfigures

PRS

Traceable

BITS f) Site B Reconfigures

PRS

Traceable

BITS

STU

DMX

ST3

Site A

DUS

STU

DUS

ST3

Sync Flow

DMX

STU

Site B Site D

Site C

STU

S T3

DMX

DUS

DMX

DUS

DMX

DUS

STU

DUS

DMX

Site A

STU

DUS

Site B

STU

Site D

Site C

STU

DMX

DUS

DMX

DUS nc-dmx-171

5 - 9 4

365-372-300

Issue 8.0, September 2006

System Planning and Engineering

Frequently Asked Network Timing Distribution Questions

Overview

The following are some frequently asked questions about network timing distribution.

How do I time DMX shelves in a central office environment?

Each DMX should be externally referenced to the BITS clock in the office. If a BITS clock is not available in the office, a traffic-carrying

DS1 from the local switch may be bridged (for example, using a bridging repeater) as the reference to the DMX. Line timing the DMX may also be used, but at least one DMX in the network must be externally timed.

Where do I use the DS1 timing output feature?

The primary application is for supplying one source for the BITS clock timing input reference. This allows the BITS clock to be slaved to a

BITS clock in another office that is, in turn, traceable to the primary reference source (PRS). Typically, the DMX supplying the DS1 timing output will, in turn, be externally timed by the BITS clock. The BITS clock should only derive one of its timing reference inputs from a particular network. Its other reference should be derived from another network to assure that it does not enter holdover mode.

If there is no BITS clock, the DS1 timing output can be used to time a switch or switch remote (if the switch remote is equipped for that option) directly— or even another DMX Multiplexer.

How do I prevent my BITS clock from using a DS1 timing output when a failure in the network results in this DS1 being timed from a SONET

NE in holdover?

SONET sync messaging informs the local DMX of this condition, and

AIS is inserted on the DS1 timing output.

What is the advantage of using the DS1 timing output instead of a multiplexed DS1 as the timing reference?

The DS1 timing output is derived from the optical line rate and is superior because:

• The DS1 is virtually jitter-free

• Sync messages guarantee the traceability of the timing

• Administration of traffic DS1s for timing is eliminated.

365-372-300

Issue 8.0, September 2006

5 - 9 5

Frequently Asked Network Timing Distribution

Questions

System Planning and Engineering

Can I ever use the DMX in the free running timing mode?

If a PRS traceable external reference is available, it is the recommended timing mode for any/all CO applications. The free running timing mode can be used but a slight increase in jitter will result. If one DMX is provisioned for free running, all other DMX NEs in the network must be line timed and SONET interfaces to other equipment are not allowed. The DS1 timing output should not be enabled with a free running network.

How do I provide timing to a central office host switch that does not have the option for an external reference?

A DS1 carried over SONET may contain significant jitter/wander and be unacceptable to the switch as a timing reference. If the central office has a BITS clock, the recommendation is to use the output from the

BITS clock into an unused DS1 traffic port on the switch. If the central office does not have a BITS clock, the recommendation is to use the

DS1 timing output from the DMX as the line timing reference into an unused DS1 traffic port on the switch.

Can a DS1 carried over SONET ever be used as a timing reference?

YES! In many applications there is no other choice. Most switch remotes, for instance, obtain their timing from a specific DS1 signal generated by their host switch, so these remotes must time from the

DS1 signal. In addition, DLC equipment, channel banks, and PBXs will not likely have external references and may be allowed to line time from a DS1 carried over SONET.

Are there any specific concerns when using a DS1 carried over SONET to time equipment such as a switch remote or DLC?

Yes. The major concern is to make sure all the equipment is synchronous. The DMX NEs should be synchronous to each other to prevent pointer adjustments. This can be accomplished by having one source DMX that is externally timed. The other DMX NEs in the network should be line timed, or they should be externally timed to a clock to which they provide a DS1 timing output. The DMX NEs should also be synchronous to the switch to prevent excessive mapping jitter. This can be done by synchronizing the host switch to the BITS clock used to reference the DMX.

5 - 9 6

365-372-300

Issue 8.0, September 2006

Frequently Asked Network Timing Distribution

Questions

System Planning and Engineering

Will I have any problems providing timing to a customer that has a high quality PBX or switch?

If the network is completely synchronous, as described in the previous answer, there should be no problems. If the PBX is sensitive to the jitter produced, even under the synchronous conditions, the DS1 timing output of DMX may be required to be used as a timing reference to this equipment.

Why does Telcordia say that DS1s carried over SONET should not be used for timing?

Telcordia has provided this recommendation because there are several limitations. Telcordia says that DS1s carried over SONET must be used in applications such as switch remotes and will be acceptable, provided pointer adjustments are not created.

Can pointer adjustments be prevented?

Neither random nor periodic pointer adjustments will occur if the DMX shelf is provisioned for line timing.

How do I time DMX at a remote site?

Line time.

How many DMX NEs can I chain together in an add/drop configuration before the timing becomes degraded?

The Stratum level traceability of the nth node in an add/drop chain is the same as that in the first node. Also, while timing jitter will theoretically increase as the number of nodes is increased, the high quality timing recovery and filtering on the DMX allows add/drop chains to be extended to any practical network limit without detectable increases in jitter levels. In practice, the only effects on timing at the nth node will occur whenever high-speed protection switches occur in any of the previous n-1 nodes. These effects should be rare.

How do I time a DMX ring network?

An interoffice ring should have each node externally timed if BITS clocks are available. All other rings should have one node externally timed (two in some dual homing architectures) and the rest of the nodes line timed. Synchronization reconfiguration is automatic.

365-372-300

Issue 8.0, September 2006

5 - 9 7

Frequently Asked Network Timing Distribution

Questions

System Planning and Engineering

Why are there more issues related to timing with SONET equipment than there are with asynchronous equipment?

SONET equipment was designed to work ideally in a synchronous network. When the network is not synchronous, mechanisms such as pointer processing and bit-stuffing must be used and jitter/wander increases.

Can DS3 signals be used to carry DS1 timing signals without the worry of having the network synchronous?

Yes, although this option is more expensive.

What are the limitations on automatic synchronization reconfiguration?

Automatic synchronization reconfiguration is only available when the

DMX is provisioned for line timing mode. This allows the timing direction of an OC-n (OC-3/12/48/192) ring network to change automatically in response to a failure. OC-3 line timing is only available beginning in R7.0, through support of tributary line timing

(OC-12/48 tributary optical line can also be used). When the DMX is provisioned for external timing, automatic synchronization reconfiguration is not available. When an OC-n fault is detected in the timing direction, AIS is inserted on the derived DS1s which forces the

BITS to switch to another good timing source or into holdover preventing timing loops.

How do I synchronize a BITS clock and maintain automatic synchronization reconfiguration on a DMX ring?

Provision all but the host node (node with co-located PRS) for line timing. Provide each non-host BITS clock with a pair of derived DS1s.

The DMX will detect faults and provide the BITS clocks with good inputs if available. Timing loops will be prevented. The host node should be set for external timing and get its timing from an externally timed BITS clock. To prevent a timing loop, the host BITS clock should get its timing from a PRS traceable source. The non-host nodes should not be timed from the co-located BITS clock since this would disable the automatic synchronization reconfiguration feature.

5 - 9 8

365-372-300

Issue 8.0, September 2006

6 Operations, Administration,

Maintenance, and Provisioning

Overview

Purpose

This chapter describes the operations, administration, maintenance, and provisioning (OAM&P) functions for the DMX Access Multiplexer.

Contents

The following sections are included in this chapter:

Performance Monitoring

SNMP Parameters and Traps

Provisioning

Reports

Administration

365-372-300

Issue 8.0 September 2006

6 - 1

Operations, Administration, Maintenance, and Provisioning

Maintenance

Overview

Purpose

This section describes the maintenance philosophy of the DMX Access

Multiplexer.

Contents

The following maintenance topics are discussed in this section:

Three-tiered Operations

IAO LAN Ports (detail)

Operations Philosophy

Lucent Operations Interworking

Multi-Vendor Operations Interworking

Data Communications Channel (DCC)

Software Download (Generic)

Database Backup and Restore

Maintenance Signaling

Fault Detection, Isolation, and Reporting

Loopbacks and Tests

Test Access

6 - 2

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Three-tiered Operations

Overview

The figure below, shows the three-tiered operations procedures for

DMX. The DMX operations procedures are built on three levels of system information and control, spanning operations needs from summary-level status to detailed reporting.

Figure 6-1 Three-Tiered Operations

TIER 3:

OS Access

IAO LAN (TCP/IP or OSI)

Operations Center

TIER 1:

Metropolis DMX

SYSCTL LEDs and Pushbuttons

Circuit Pack Fault and Active LEDs

Routine Operations and Maintenance

Fault Verification

Circuit Pack Replacement

Default Provisioning

TIER 2: PC-CIT

Serial or

IAO LAN

Enhanced Maintenance and Provisioning

Detailed Reports

Manual Controls

Provisioning

Security

Software DoWnload/

Database Backup and Restoration

Remote Maintenance and Provisioning

Alarm Surveillance

Performance Monitoring

Automated Service

Provisioning

Remote Control

Security

Software DoWnload/

Database Backup and Restoration nc-dmx-016

SYSCTL faceplate

(Operations Tier 1)

Office alarms are provided by a set of discrete relays that control office audible and visual alarms. Separate relays handle critical (CR), major

(MJ), and minor (MN) alarms, although the CR and MJ alarms can be wire ORed and reported as office major, if desired.

The light-emitting diodes (LEDs) and push buttons on the SYSCTL faceplate allow routine tasks to be performed without a PC-CIT or any test equipment. The SYSCTL faceplate LEDs provide system-level alarm and status information for the local NEs and a summary for all remote NEs in the alarm group. The circuit pack faceplate FAULT

LEDs allow fast and easy fault isolation to a particular circuit pack.

The SYSCTL faceplate LEDs default to show local system information. The highest active alarm level is shown by the red LEDs for CR and MJ alarms. Yellow LEDs are shown for MN alarms. An

365-372-300

Issue 8.0 September 2006

6 - 3

Three-tiered Operations

Operations, Administration, Maintenance, and Provisioning

ACO button is used to activate the alarm cutoff function. When activated, the LED is on. The ACO button also initiates an LED test when the button is depressed and held. A green PWR ON LED shows that the power is on and the terminal is receiving a -48V source. Three yellow status LEDs show abnormal (ABN) conditions, near-end activity (NE), and far-end activity (FE). The yellow ABN LED is lighted when a temporary condition, potentially affecting transmission, exists. For example, this condition could be a manual protection switch or lockout, loopback, or system test in progress.

The Update/Initialize (UPD/INIT) button addresses the local system.

The recessed UPD/INIT button serves several functions during installation and circuit pack replacement. During the first 10 seconds after powering up the SYSCTL circuit pack, depressing this button initializes the nonvolatile memory with provisioning and state information. Secondly, after removing a circuit pack, optical module, or low-speed input, depressing this button updates the system equipment list to show the slot, socket, or signal is now unequipped.

The SYSCTL faceplate’s remote display functions serve the singleended maintenance needs of access transport applications. When any alarm or status condition exists at a remote DMX shelf in the same alarm group, the FE LED on the faceplate is lit.

6 - 4

365-372-300

Issue 8.0 September 2006

Three-tiered Operations

LED/Push-button

Active

FAULT

ABN

ACO

ACO/TEST

SEL

UPD/INIT

Operations, Administration, Maintenance, and Provisioning

The table below details the various LEDs and push-button switches and describes their functions.

Table 6-1 SYSCTL Faceplate Indicators and Functions

Indicator name

Active

Fault

Critical

Major

Minor

Abnormal

Far-End Activity

Near-End Activity

Alarm Cut-Off

Alarm Cut-Off/Test

Select

Update/Initialize

Function

Indicates the SYSCTL is Active.

Indicates isolated circuit pack failure.

Indicates critical alarm for local system.

Indicates major alarm for local system.

Indicates minor alarm for local system.

Indicates temporary transmission-affecting condition.

Indicates remote alarm or status condition.

Indicates local alarm or status condition.

Activates alarm cut-off (will also display software version information when depressed for 3 seconds).

Performs LED tests.

When SEL and UPD/INIT button are held down together, you get a 4 segment square (::).

Updates the local system.

Circuit pack LEDs

To supplement the SYSCTL faceplate’s system-level view, each circuit pack provides a red FAULT LED on its faceplate. A lighted FAULT

LED shows that the DMX has isolated a failure to that circuit pack. On transmission circuit packs, a flashing FAULT LED shows that an incoming signal to that circuit pack has failed.

Important!

All circuit packs that use PTM optics have per-port

LEDs. The LNW37 can be used with pre-R4 software, but in that case the per-port LEDs are unused, and the paragraph above applies). The board FAULT LED on the PTM packs is lit solid when there's a board failure, and blinks if there's a port or socket failure. The per-port LED is lit solid if there's a socket failure, and blinks if there's an incoming port (signal) failure.

365-372-300

Issue 8.0 September 2006

6 - 5

Three-tiered Operations

Operations, Administration, Maintenance, and Provisioning

Local craft interfaces

(Operations Tier 2)

The local craft interfaces include the PC-CIT, which may be utilized in a variety of ways.

DMX has two serial ports for PC-CIT access, one in the front one and one at the rear of the shelf.

TL1 is supported for both serial ports, but software download is supported via the front serial port only.

DMX also has two LAN ports for PC-CIT (and/or OS) access, one in the front and one in the rear. Both TL1 over OSI and TL1 over TCP/IP are supported via these two LAN ports. Software download via FTAM or FTP and FTTD are also supported.

PC-CIT (TL1 over TCP/IP)

The PC-CIT is a small CIT interface that provides a flexible TL1 command instructor. The PC-CIT connects to a DMX using either the front or rear serial ports, the front IAO LAN port, or the rear IAO LAN port. The PC-CIT supports TCP/IP (or OSI) through both the front and rear IAO LAN interfaces.

The PC-CIT is used for report generation, as well as command and system response. Access to the system is provided via serial or IAO

LAN interfaces.

Operations System (OS)

TL1/LAN interfaces

(Operations Tier 3)

The third operations tier consists of OS access. DMX OS interfaces are

IAO LAN ports.

TL1

The TL1 message-based OS interface provides remote OS access, as well as detailed reporting and control capabilities. The interface uses standard TL1 and needs no mediation device (i.e., the interface can be connected directly). The remote user could be an OS or a user at a terminal. Lucent Technologies is involved in an active OSMINE process to ensure compatibility of DMX NEs with Telcordia OSs.

The DMX supports TL1 alarm surveillance and performance monitoring with OSs such as Telcordia’s Network Monitoring and

Analysis (NMA). The DMX supports service provisioning with memory administration OSs such as Lucent’s Navis OMS or

Telcordia’s TEMS. The DMX also supports remote recovery and control functions, installation provisioning, and security over the TL1 link. The TL1 message set used has been updated to offer full remote reporting capabilities.

6 - 6

365-372-300

Issue 8.0 September 2006

Three-tiered Operations

Operations, Administration, Maintenance, and Provisioning

The OS can use more than one NE as a GNE to provide redundancy and/or to distribute TL1 message volume. The TL1 GNE serves as a single interface to the OS for the NEs in the same subnetwork. The TL1

GNE receives operations information from all the NEs through the

DCC and reports this information, as well as its own information, to the

OS. The operations information is in the form of TL1 messages.

Through the GNE, the OS can send TL1 commands to any NE in the subnetwork. Lucent’s Navis OMS, as well as other-vendor NEs that adhere to GR-253-CORE, can serve as the TL1 GNE for the DMX.

365-372-300

Issue 8.0 September 2006

6 - 7

Three-tiered Operations

Operations, Administration, Maintenance, and Provisioning

Front IAO LAN

The front IAO LAN interface provides a connection to the PC-CIT and supports OSI or TCP/IP communications. The front IAO LAN is located on the faceplate of the SYSCTL circuit pack.

Rear IAO LAN

The primary purpose of the rear IAO LAN port is to provide remote OS access such as OS TL1 access over TCP/IP Gateway. It also supports a faster software download from Navis

EMS (or any FTP server) using file transfer protocol (FTP) to Lucent DMX systems when software is being upgraded (both the rear and front IAO LAN ports support this functionality). This rear IAO LAN port can also be used for PC-CIT

OSI-based interfaces and TCP/IP support.

The figure below shows how DMX works with the various operations interfaces.

Figure 6-2 Operations Interfaces

Local Operations

Interfaces (Front)

PC-CIT

TL1/EIA-232D Asynch

TL1/TCP-IP or TL1/OSI/

IAOLAN

Remote NE

TL1/OSI/IP SONET DCC

LEDs

Buttons

Metropolis

DMX

SYSCTL

(Rear)

TL1/TCP-IP or TL1/OSI/

IAOLAN*

Tl1

Rear Serial Port

(Modem - CIT)

Office Alar ms

Miscellaneous Discretes

Remote

NMS/EMS

TL1 over OSI supports TARP

Protocol per GR-253-CORE

* LAN could also interface with LAN on another NE nc-dmx-013

6 - 8

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

IAO LAN Ports (detail)

Overview

DMX supports a front and rear IAO LAN port. Each IAO LAN port operates independently (DMX does not support an internal IAO LAN hub). The front IAO LAN port is recommended for convenient, temporary local WaveStar

CIT access. When, for example, the

WaveStar

CIT is directly connected to either IAO LAN port, a LAN crossover cable is required (to connect the transmit wire-pair at one end to the receive wire-pair at the other end, and vice versa).

The rear IAO LAN port is recommended for permanent local

WaveStar

CIT access and all remote WaveStar

CIT access via TCP/

IP as well as for OS access. DMX’s rear IAO LAN port is typically expected to be connected to an Ethernet LAN hub in CO applications, but unused at remote sites.

The DMX IAO LAN ports support 10/100BaseT Ethernet (per

Telcordia Technologies GR-253, ANSI/IEEE 802.2 and 802.3, and ISO

8802.2 and 8802.3) over four-wire twisted pair using an RJ-45 connector. Each IAO LAN port automatically adapts its rate to 10 Mb/s or 100 Mb/s to match the capability of the other nodes on the same IAO

LAN, with 10 Mb/s as the default rate.

OSI on the IAO LAN

When the OSI protocol stack is used on an IAO LAN port, the term

“OSI LAN” is sometimes used. The OSI LAN is effectively an extension of the DCC. All remote operations supported over the DCC are also supported over the OSI LAN. The term “DCC connectivity” is used throughout this document to mean DCC and/or OSI LAN connectivity.

OSI communications on the IAO LAN port can be enabled or disabled.

Beginning in R3.1.1, by default, OSI is enabled on the front IAO LAN port, but disabled on the rear IAO LAN port.

TCP/IP on the IAO LAN

The IAO LAN ports also support the TCP/IP protocol stack. TCP/IP communications on the IAO LAN ports can be enabled or disabled. By default, TCP/IP is disabled on the IAO LAN ports.

When the TCP/IP protocol stack is used on an IAO LAN port, the term

“TCP/IP LAN” is sometimes used.

DMX supports TL1 over TCP/IP for the IAO LAN. As a TL1 responder, DMX TCP/IP GNE accepts incoming TL1 connections to the following TCP ports with corresponding TL1 encodings.

365-372-300

Issue 8.0 September 2006

6 - 9

IAO LAN Ports

Operations, Administration, Maintenance, and Provisioning

Port 3081: Length-Value Encoding. With length-value encoding, each TL1 message is encapsulated into the TCP data stream as follows:

• Version number (1 byte, value set to 3)

• Reserved (1 byte, value set to 0)

• Length (2 bytes, value set to length in bytes of TL1 message + 4)

• TL1 Message (variable length

The length-value encoding is the preferred encoding for machine machine interactions.

Port 3082: Raw Encoding. Each raw encoded TL1 message is encapsulated into the TCP data stream of length 1 - 4096 bytes. The

TL1 message must be parsed to find the boundary between successive

TL1 messages (see Telcordia GR-831 CORE for the syntax of TL1 messages).

Port 3083: Telnet Encoding. The telnet encoding is a variation on the raw encoding. It encapsulates TL1 messages in a TCP stream and uses

Telnet for transmitting text over TCP/IP.

6 - 1 0

365-372-300

Issue 8.0 September 2006

IAO LAN Ports

Operations, Administration, Maintenance, and Provisioning

OSI or TCP/IP on the same

IAO LAN

It is generally recommended that each IAO LAN port be used for OSI or TCP/IP, but not both protocols simultaneously on the same IAO

LAN port.

The figure below provides examples of common applications using the

IAO LAN ports.

Figure 6-3 IAO LAN Port Applications

Operations Center

WaveStar

CIT

OSs

10/100 BaseT

Ethernet

LAN Hub

Remote Location

WaveStar

CIT

WaveStar

CIT

Front IAO

LAN Port

WaveStar

CIT

OSI

Metropolis

DMX

SYSCTL

OC-48

UPSR with

DCC

TCP/IP

Rear IAO

LAN Port

10/100 BaseT

Ethernet

LAN Hub

IP WAN

Metropolis

DMX

SYSCTL

OSI

Front IAO

LAN Port

Remote Site

WaveStar

CIT nc-dmx-003

365-372-300

Issue 8.0 September 2006

6 - 1 1

IAO LAN Ports

Operations, Administration, Maintenance, and Provisioning

IAO LAN compatibility

The following table documents DMX IAO LAN communications compatibility with other products and the applicable OSI and/or TCP/

IP protocol stacks. (WaveStar

CIT and OS access applications compatibility via the IAO LAN is covered separately later.)

Table 6-2 IAO LAN Compatibility

Product

DMX

DMXplore

DMXtend

DDM-2000 OC-3

DDM-2000 OC-12

FiberReach

FT-2000 ADR

WaveStar

TDM 2.5G/10G (2-Fiber)

WaveStar

BandWidth Manager

Lambda Unite

WaveStar

CIT

Navis

Optical Element Management

System

(formerly SNMS)

Navis

Ethernet Management System

DMX

OSI

yes

yes yes yes yes yes yes yes yes yes yes yes yes

TCP/IP

yes yes

yes

yes yes yes yes

6 - 1 2

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Operations Philosophy

Overview

The DMX has incorporated an operations philosophy that is optimized for operations in the access transport environment. This allows operation and maintenance of remote NEs from a single location.

Similarly, a technician working at a remote site can gain access to other

NEs. In addition, OSs are available to allow operation of the DMX NEs from a centralized operations center.

The DMX uses the SONET data communications channel (DCC) to provide remote PC-CIT access, remote CO alarms, remote alarm reports, and remote OS access. The terms remote operations, singleended operations (SEO), and Operations Interworking (OI) are synonymous.

365-372-300

Issue 8.0 September 2006

6 - 1 3

Operations Philosophy

Operations, Administration, Maintenance, and Provisioning

SEO capability

The figure below shows the SEO capability that provides remote access to all DMX systems in a subnetwork from a single DMX location. This minimizes the need for technician travel because most maintenance, provisioning, and administration can be performed on all NEs with

DCC connectivity by accessing any one NE. The SEO capability can be disabled between NEs to create maintenance boundaries (for example, interoffice applications) or for security reasons.

Figure 6-4 Remote Operations Philosophy

Remote

Operation

Center

IAO LAN,

TCP/IP LAN, or

TL1/X.25

Single Span

Single-Ended Operations

Serial PC/CIT or

IAOLAN

OC-48

CIT

SYSCTL

OC-48 OC-48

Metropolis DMX

OC-48

Legend:

SONET

DCC enabled nc-dmx-014

6 - 1 4

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Lucent Operations Interworking

Overview

Operations interworking (OI) provides the capability to access, operate, administer, maintain, and provision remote Lucent NEs from any

Lucent NE with DCC connectivity in a network or from a centralized

OS.

OI support

Lucent OI is available among NEs that are connected through the

SONET DCC or IAO LAN. With this feature, users can perform

OAM&P activities on a centralized basis, saving travel time and money.

OI features including the following:

• Remote OS access via TL1 over TCP/IP (or OSI) or TL1

• Remote OS access via IP over DCC

• Remote PC-CIT access

• Remote NE status

• Remote software download and copy

• Remote time and date synchronization

For more information on OI, refer to Lucent Technologies WaveStar

Product Family Operations Interworking Guide, 365-372-303.

The following table summarizes DMX OI compatibility with the products and releases specified in the previous table.

Table 6-3 DMX OI Compatibility Summary

Product

DMX

DMXplore

DMXtend

DDM-2000 OC-3

DCC IAO

LAN

WaveStar

CIT

Access

OS Access from

DMX

DMX tl1-gne

DMX tl1-rne

yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes -

yes

Remote

Software

Downloa d

yes yes yes yes

Auto.

Time/

Date

Sync

yes yes yes yes

Remot e

Status

yes yes yes yes

DDM-2000 OC-12

FiberReach yes yes yes yes yes yes yes -

yes yes yes yes

yes

FT-2000 ADR yes yes yes -

365-372-300

Issue 8.0 September 2006

6 - 1 5

Lucent Operations Interworking

Operations, Administration, Maintenance, and Provisioning

Product DCC IAO

LAN

WaveStar

CIT

Access

OS Access from

DMX

DMX tl1-gne

DMX tl1-rne

WaveStar

TDM

2.5G/10G (2-Fiber)

WaveStar

BandWidth

Manager yes yes yes yes yes yes yes

yes yes yes

yes yes

Lambda Unite yes yes

Ciena

Core Director yes -

Navis

Optical

Element Management

System

(formerly SNMS)

Navis

Ethernet

Management System

yes yes

NMA

Transport (TEMS)

yes yes

yes yes yes yes yes yes yes yes

Remote

Software

Downloa d

Auto.

Time/

Date

Sync

Remot e

Status

yes yes

Alarm groups

An alarm group is a set of NEs that share status information between themselves, such as alarms, LEDs, and ACO status. The set of remote

NEs that an NE can exchange status information which is determined by the value of the local alarm group parameter. This parameter is provisioned at each local NE and specifies whether that local NE does or does not exchange remote NE status with other Lucent NEs in the same SONET subnetwork. In DMX, all NEs are defaulted into the same alarm group (number 255).

Alarm groups can be nodes in a ring, nodes of a linear extension, or any other logical grouping such as a maintenance group or geographical group. For example, 24 NEs could be provisioned into three alarm groups with eight NEs that share a community of interest such as the same OC-3 low-speed optical interface.

All members of the same alarm group share NE status information but do not share information with other alarm groups.

Alarm group functions

Depending on provisioning, a member of an alarm group can:

6 - 1 6

365-372-300

Issue 8.0 September 2006

Lucent Operations Interworking

Operations, Administration, Maintenance, and Provisioning

• Know the alarm/status of all members of the same alarm group and, if the NE is at the CO, activate audible office alarms for the alarm group.

• List a report of the summary alarm or status condition of other

NEs in the group.

• Display composites of the highest alarm level among other member NEs in the same alarm group.

Alarm Gateway Network

Element (AGNE)

Members of an alarm group exchange information through one or more alarm gateway NEs (AGNEs) that are defined in the same alarm group.

All DMX NEs use the DCC to receive and report alarm and status information to the AGNE(s). The AGNE rebroadcasts all alarm and status information from one NE to all the other NEs in the same alarm group.

This information is used to activate remote far-end summary alarm reports and remote office alarms for each NE in the alarm group. At least one NE in each alarm group must be provisioned as the AGNE.

An additional AGNE can be provisioned for redundancy, but it is recommended that only one AGNE be provisioned for each alarm group. Considerations for choosing an NE as an AGNE include being central to the group to make communications links easily accessible for maintenance purposes.

The AGNE and TL1 GNE should be separate NEs. Furthermore, the

AGNE is a “collection point” and does not have to be a NE in a CO.

365-372-300

Issue 8.0 September 2006

6 - 1 7

Operations, Administration, Maintenance, and Provisioning

Multi-Vendor Operations Interworking

TARP

To support multi-vendor OI, the DMX supports Target ID Address

Resolution Protocol (TARP).

TARP provides NSAP-TID translations and is the established multivendor standard for SONET NEs that support TL1 OS interfaces. DMX supports the TARP Data Cache (TDC) function to reduce the frequency of TARP propagation throughout the subnetwork and to improve performance.

Compatibility

DMX is developed to be compatible with any other-vendor NEs that support TARP, OSI, IAO LAN, and TL1 as specified in Telcordia

Technologies GR-253. In addition, DMX’s TARP Manual Adjacency feature enables it to operate in networks that include CMISE-based

NEs which may not support TARP propagation. DMX supports user provisioning of several OSI parameters to allow users to adjust their operations network, if necessary. For example, to support Level 2

Routing in large networks, DMX supports user provisioning of NSAP area addresses and Level 2 Intermediate System (IS) functionality.

DMX’s compatibility with other-vendor NEs may be tested by customers or independent third parties such as Telcordia Technologies.

6 - 1 8

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Data Communications Channel (DCC)

Provisioning the DCC

To support remote operations over the DCC embedded in the SONET section overhead of the optical signal, the DCC itself must be provisioned as indicated in the following paragraphs.

DCC enable/disable

By default, the DCC is enabled on all optical ports. DCC communications can be enabled or disabled on each port independently.

DCC protection mode

The DCC protection mode is determined by the transmission protection mode assigned to each optical port (per the application parameter). The protection mode can be linear (1+1) identical, or distinct (UPSR).

Linear (1+1) identical is the default for the low-speed optical ports.

Release 7.0 also supports 15 low-speed OC-48 BLSRs.

In systems equipped with Release 2.0 or earlier software, the highspeed optical ports are always distinct (UPSR) and are not provisionable.

In systems equipped with Release 2.1 software, the OC-48 high-speed optical ports may be provisioned for UPSR or BLSR applications. The

OC-192 high-speed ports are autoprovisioned for UPSR applications only.

In systems equipped with Release 3.0 and later software, the OC-48 high-speed optical ports may be provisioned for UPSR, BLSR, or 1+1 applications. The OC-192 high-speed ports may be provisioned for

UPSR (R2.1), BLSR (R3.0), or 1+1 (R4.0) applications.

In systems equipped with Release 3.1 and later software, the OC-12 high-speed optical ports may be provisioned for UPSR or 1+1 applications.

365-372-300

Issue 8.0 September 2006

6 - 1 9

Data Communications Channel (DCC)

Operations, Administration, Maintenance, and Provisioning

The following table summarizes the DCC protection modes.

Table 6-4 DCC Protection Modes

Optical Port

Protection Mode

Shelf Slots

OC-12/OC-48/OC-192

UPSR

OC-48/OC-192 BLSR

OC-12/OC-48/OC-192

Linear (1+1)

OC-12/OC-48/OC-192

Bidirectional (1+1)

OC-48 UPSR

OC-48 BLSR

OC-48 Linear (1+1)

OC-48 Bidirectional (1+1)

OC-48 0x1

OC-48 0x1Sn

OC-12 UPSR

OC-12 Linear (1+1)

OC-12 Bidirectional (1+1)

OC-12 0x1

OC-12 0x1Sn

OC-3 UPSR

OC-3 Linear (1+1)

OC-3 Bidirectional (1+1)

OC-3 0x1

OC-3 0x1Sn

High-speed Main slots

Low-speed Function and Growth slots

15 pair

20 pairs

40 pairs

80 pairs

Max. Number

Simultaneous

Optical Ports

(see note)

1 pair (2 for

OC-192)

1 pair (2 for

OC-192)

1 pair (2 for

OC-192)

1 pair (2 for

OC-192)

20 pairs

Max. Number

Simultaneous

Section DCCs

1 pair (2 for OC-

192)

1 pair (2 for OC-

192)

1 (2 for OC-192)

80 pairs

20 pairs

15 pair

40 pairs

6 - 2 0

365-372-300

Issue 8.0 September 2006

Data Communications Channel (DCC)

Operations, Administration, Maintenance, and Provisioning

Optical Port

Protection Mode

Shelf Slots Max. Number

Simultaneous

Optical Ports

(see note)

Max. Number

Simultaneous

Section DCCs

Notes:

1. In this table, each optical port counted includes both a transmit and receive fiber.

2. 0x1 mode is supported in R7.0 (and going forward) with the use of the VLF Main packs

(LNW59). 0x1Sn is supported in Releases prior to R7.0 and in R7.0 when non-VLF Mains are used. 0x1 is only available on low-speed/tributary packs, not high-speed network interface packs.

365-372-300

Issue 8.0 September 2006

6 - 2 1

Data Communications Channel (DCC)

Operations, Administration, Maintenance, and Provisioning

User side and network side

The operation of each DCC span also depends on one end of the span being designated the “User” side and the other end being designated the

“Network” side. The DCC User/Network side assignments are provisionable.

By default, the high-speed port dcc-m1-1 is designated the “User” side and dcc-m2-1 is designated the “Network” Side. If each DMX on a high-speed ring application is connected to its neighbor with a fiberpair between ports main-1 and main-2, the default DCC User side/

Network side assignments are sufficient.

The figure below shows an example of the User and Network side designations for DMXs on a high-speed UPSR or BLSR.

Figure 6-5 User/Network Side Designation on a UPSR/BLSR

User Side

Metropolis

DMX

OC-48 OLIU

Network Side

Metropolis

DMX

OC-48 OLIU

User Side

UPSR/BLSR

User Side

Metropolis

DMX

OC-48 OLIU

Network Side nc-dmx-188

6 - 2 2

365-372-300

Issue 8.0 September 2006

Data Communications Channel (DCC)

Operations, Administration, Maintenance, and Provisioning

By default, low-speed linear (1+1) DCC is designated “Network” side but low-speed UPSR/BLSR DCC designations alternate between each

Function Slot and Growth Slot, for example, dcc-a1-1 is designated

“Network” side and dcc-a2-1 is designated “User” Side. If each DMX on a low-speed UPSR is connected to its neighbor with a fiber-pair between ports fn-a-1-1 and fn-a-2-1 (for example), the default DCC

User side/Network side assignments are sufficient. For 0x1Sn, the active side of the topology is set to “Network”. For 0x1, both sides of the topology are set to “Network”.

The figure below shows an example of the User and Network side designations for DMXs on a low-speed UPSR with DDM-2000.

Figure 6-6 User/Network Side Designation on an OC-3/12 UPSR with DDM-2000

Network

Side

Metropolis

DMX

Metropolis

DMX

User Side

OC-3 or OC-12

UPSR with DCC

User Side

Network Side

User

Side

DDM-2000 nc-dmx-002

365-372-300

Issue 8.0 September 2006

6 - 2 3

Data Communications Channel (DCC)

Operations, Administration, Maintenance, and Provisioning

The figure below shows an example of the User and Network side designations for DMXs on a low-speed OC-48 BLSR.

Figure 6-7 User/Network Side Designation on a Low Speed OC-

48 BLSR

Metropolis

DMX

Network

Side

Network

Side

User

Side

User Side

OC-48 BLSR

Network

Side

User

Side

Metropolis

DMX

Metropolis

DMX nc-dmx-269

6 - 2 4

365-372-300

Issue 8.0 September 2006

Data Communications Channel (DCC)

Operations, Administration, Maintenance, and Provisioning

DCC compatibility

Product

DMX

DMXplore

DMX supports the optical interfaces with DCC communications compatibility as shown in the following table. DMX supports Section

DCC running the OSI protocol stack and IP. The “1+1” entries represent linear and bidirectional (1+1) protected DCC compatibility.

Optical Interfaces

Supported

High-Speed

Low-Speed

High-Speed

Table 6-5 DCC Compatibility

OC-192

OC-48

OC-12

OC-48

OC-12

OC-3

DMX

High-Speed Main Slots

OC-192 OC-48 OC-12 OC-48 OC-12 OC-3

UPSR/

BLSR/

1+1

UPSR/

BLSR/

1+1

UPSR/

BLSR/

1+1

UPSR/

1+1

UPSR/

1+1

Low-Speed Function and Growth Slots

UPSR/

BLSR/

1+1/

0x1Sn/

0x1

UPSR/

BLSR/

1+1/

0x1Sn/

0x1

UPSR

1+1/

0x1Sn/

0x1

UPSR/

1+1/

0x1Sn/

0x1

UPSR/

1+1/

0x1Sn/

0x1

UPSR/

1+1

DMXtend High-Speed OC-12

UPSR/

1+1

UPSR/

1+1/

0x1Sn/

0x1

OC-3 UPSR

1+1/

0x1Sn/

0x1

365-372-300

Issue 8.0 September 2006

6 - 2 5

Data Communications Channel (DCC)

Operations, Administration, Maintenance, and Provisioning

Product

DDM-2000

OC-3

DDM-2000

OC-12

FiberReach

FT-2000 ADR

WaveStar

TDM

2.5G/10G (2-

Fiber)

Optical Interfaces

Supported

High-Speed

Low-Speed

OC-12

OC-3

High-Speed OC-12

Low-Speed OC-3

High-Speed OC-12

OC-3

High-Speed OC-48

Low-Speed

High-Speed OC-48

Low-Speed

OC-12

OC-3

OC-12

OC-3

DMX

High-Speed Main Slots Low-Speed Function and Growth Slots

OC-192 OC-48 OC-12 OC-48 OC-12 OC-3

UPSR

UPSR/

0x1Sn/

0x1

UPSR/

0x1Sn/

0x1

1+1/

0x1Sn/

0x1

UPSR

UPSR/

0x1Sn/

0x1

1+1/

0x1Sn/

0x1

UPSR

UPSR/

0x1Sn/

0x1

UPSR/

0x1Sn/

0x1

BLSR

BLSR/

0x1Sn/

0x1

1+1

1+1/

0x1Sn/

0x1

1+1/

0x1Sn/

0x1

UPSR/

BLSR

UPSR/

BLSR/

1+1/

0x1Sn/

0x1

UPSR

1+1

UPSR

1+1/

0x1Sn/

0x1

1+1/

0x1Sn/

0x1

6 - 2 6

365-372-300

Issue 8.0 September 2006

Data Communications Channel (DCC)

Operations, Administration, Maintenance, and Provisioning

Product

WaveStar

BandWidth

Manager,

Release 4.0

Optical Interfaces

Supported

High-Speed

Low-Speed

OC-48

OC-12

OC-3

DMX

High-Speed Main Slots Low-Speed Function and Growth Slots

OC-192 OC-48 OC-12 OC-48 OC-12 OC-3

UPSR/

BLSR

UPSR/

BLSR/

1+1/

0x1Sn/

0x1

UPSR/

1+1

UPSR/

1+1/

0x1Sn/

0x1

1+1/

0x1Sn/

0x1

Lambda Unite High-Speed OC-192 UPSR/

BLSR/

1+1

OC-48

UPSR/

BLSR

UPSR/

BLSR/

0x1Sn/

0x1

Low-Speed OC-12

UPSR/

1+1

UPSR/

1+1/

0x1Sn/

0x1

OC-3 1+1/

0x1Sn/

0x1

365-372-300

Issue 8.0 September 2006

6 - 2 7

Operations, Administration, Maintenance, and Provisioning

Software Download (Generic)

Overview

DMX supports local and remote software downloads.

For complete coverage of DMX’s software download features, refer to the

Metropolis

DMX Access Multiplexer Installation Manual, 365-

372-304.

Local software download

DMX supports the following local software downloads.

• Local software installation via File Transfer Protocol (FTP) from a

WaveStar

CIT connected to the

CIT LAN

(IAO LAN) port on the

SYSCTL circuit pack faceplate or the

J16 IAOLAN

(IAO LAN) port on the shelf backplane. Software installation via FTP requires the following:

– FTP Client software is enabled on the NE

– IP parameters are provisioned on the NE.

• Remote software download via an FTAM-FTP gateway to DMX.

The FTAM-FTP gateway is also referred to as the file transfer translation device (FTTD).

Important!

Download time over FTP has been reduced from 7 minutes to approximately 4 minutes.

Important!

FTP must be used to install software when using the

Windows



XP Operating System.

Remote software download

Remote software download reduces the need to travel to remote sites when the software version of multiple DMX systems is being upgraded throughout a network.

• Remote software download via an FTAM-FTP gateway to DMX.

The FTAM-FTP gateway is also referred to as the file transfer translation device (FTTD).

• Software copy from the local DMX to a remote:

– DMX

– DMXtend

– DMXplore

– DDM-2000 OC-3

– DDM-2000 OC-12

– FiberReach

6 - 2 8

365-372-300

Issue 8.0 September 2006

Software Download (Generic)

Operations, Administration, Maintenance, and Provisioning

Important!

The software must be in the dormant area of DMX.

Both the local and remote NEs must have an active software generic.

• Remote software download via FTP to DMX. Both the FTP gateway network element (GNE) and remote NE must have an active software generic.

Important!

Release 2 and later software supports IP tunneling.

Impact of software download and activation

Initial local software installation temporarily disrupts operations communications because the system controller is reset to activate the software immediately.

Other local software downloads temporarily disrupt operations communications, too, because a system controller reset is involved, but the dormant software is not activated immediately.

Remote software download or copy of compressed dormant software is accomplished without any disruption of operations communications

(that is, no system controller resets), because the dormant software is not activated immediately.

If there is no valid generic or database on the controller, or if there are multiple valid generics or databases when the shelf resets, the shelf enters maintenance mode, using the default database. If necessary, the

WaveStar CIT wizard will guide the user through the download/restore process and prompt generic and database selection.

365-372-300

Issue 8.0 September 2006

6 - 2 9

Software Download (Generic)

Operations, Administration, Maintenance, and Provisioning

Remote software download compatibility

The following table lists DMX remote software download compatibility with other products.

Table 6-6 Remote Software Download Compatibility

Product

DMX

DMXplore

DMXtend

DDM-2000 OC-3

DDM-2000 OC-12

FiberReach

From PC Connected to:

DMX

Front Serial Port

yes yes yes yes yes yes

Digital signature capability

NOTE:

DMX shelves running pre-R6.0 software releases can only perform downloads to other pre-R6.0 DMX or other pre-R4.0 DMXtends. Any shelf running R6.0 and later releases can download previous releases.

In Release 3.0 and later releases, DMX verifies software downloads using a digital signature. When FTP over TCP/IP is used for a software download, a digital signature is transmitted with the software download and verified by the network element. If the verification fails, DMX reports an autonomous message and the software download fails. The digital signature is discarded after verification.

Checking the digital signature of software download can be enabled or disabled using the

Configuration > Software > Software Download

command.

6 - 3 0

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Database Backup and Restore

Overview

This section describes the database backup and restore feature in DMX.

IP tunneling is required to support remote database backup/restore for remote DMX systems.

The DMX uses the following connections to perform database backup and restore:

• A direct IP connection

• OSI connectivity to an FTP GNE.

• FTAM Backup and Restore

Database backup

DMX can back up all provisionable data via a local or remote FTP file transfer. In Release 3.0 and later releases, data can be backed up to a remote operations system via an FTAM-FTP gateway. The FTAM-FTP gateway is also referred to as the file transfer translation device

(FTTD).

The backup database is stored on a WaveStar

CIT, and Navis™

Optical Element Management System (Navis™ Optical EMS), or another FTP server. For information about the

Configuration>Software>Remote Backup

command, refer to the WaveStar

CIT help.

Database restore

In the event of a catastrophic failure, DMX can restore all provisionable data (from the backup file) via local or remote FTP. In

Release 3.0 and later releases, data can be restored from a remote operations system via an FTAM-FTP gateway. The FTAM-FTP gateway is also referred to as the file transfer translation device

(FTTD).

The backup database maybe stored on a WaveStar

CIT, and Navis™

Optical Element Management System (Navis™ Optical EMS), or another FTP server. For information about the

Configuration>Software>Remote Restore

command, refer to the WaveStar

CIT help. For more information about restoring the network element database, refer to The User Operations Guide.

365-372-300

Issue 8.0 September 2006

6 - 3 1

Database Backup and Restore

Operations, Administration, Maintenance, and Provisioning

Automatic database backup

DMX supports automatic database backups. This allows users to establish a backup interval, date, and time. The database backups may be saved on the WaveStar

CIT or another FTP server.

The user can also specify the number of backups to destination files before overwriting those same files with subsequent backups. To eliminate the scenario of multiple DMX systems initiating automatic backups simultaneously, DMX does not support a default scheduled backup date/time; the user must provision their own date/time. For information about the

Configuration>Software>Configure Auto Backup

Interval

command, refer to the Wavestar CIT help.

6 - 3 2

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Maintenance Signaling

Alarm indication signals

Alarm indication signals (AIS) are one example of maintenance signals that notify equipment downstream that a failure has been detected and alarmed by upstream equipment. AIS is a signal that replaces the normal traffic signal when a maintenance alarm indication has been activated.

RAI and RDI are then used to notify a piece of equipment upstream that a failure has been detected by downstream equipment.

Compliance

Maintenance signaling is compliant with SONET (Telcordia

Technologies GR-253) and asynchronous (Telcordia Technologies TR-

TSY-000191) network requirements. Alarm indication signals include

SONET OC-n line AIS, STS-1 path AIS, virtual tributary (VT) path

AIS, DS3 AIS, and DS1 AIS. Remote defect indication signals include

STS-1 path RDI and VT path RDI. Other maintenance signals include

STS-1 path unequipped, VT path unequipped, Loss of Signal (LOS,

Loss of Frame (LOF), and Loss of Pointer (LOP).

365-372-300

Issue 8.0 September 2006

6 - 3 3

Operations, Administration, Maintenance, and Provisioning

Fault Detection, Isolation, and Reporting

Overview

DMX continuously monitors incoming signals and internal system conditions. Incoming signals are monitored at the line level for loss of signal (LOS), loss of frame (LOF), and Alarm Indication Signal (AIS), and BER threshold crossings. Incoming signals are monitored at the path level for loss of pointer (LOP), Alarm Indication Signal (AIS), unequipped (UNEQ), and BER threshold crossings.

The BER threshold crossings are detected for DS1, DS3, E1, EC-1,

VT1.5, OC-3, OC-12, OC-48, OC-192, STS-1, STS-3c, STS-12c, and

STS-48c signals.

Fault detection

In addition to detecting line and path faults, the system also detects internal circuit pack faults. When an internal fault is detected, automatic diagnostics isolate the faulty circuit pack. Faults are reported to local technician and OSs so that technician dispatch and repair decisions can be made. If desired, OS personnel and local technicians can use the PC-CIT to gain more detailed information on the fault condition.

Fault isolation

All fault conditions detected by the system are stored and made available to be reported, on demand, through the PC-CIT. In addition, a history of past alarm and status conditions and PC-CIT events is maintained and available for on-demand reporting. Each event is realtime and date stamped.

Fault reporting

The system can also report all detected alarm and status conditions through the appropriate office alarm relays, SYSCTL faceplate LEDs, transmission circuit pack LEDs, and TL1 interfaces.

6 - 3 4

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Loopbacks and Tests

Overview

The DMX allows technicians to perform loopback tests on all low- and high-speed interfaces. Low-speed DS1, DS3, E1, and EC-1 electronic loopbacks, directed toward the high-speed line (terminal loopback), are individually controllable from the CIT or the OS interface. Active electronic loopbacks are shown by the ABN LED on the SYSCTL faceplate and in the alarm and status report. EC-1, E1, DS1, DS3, and

Ethernet facility loopbacks toward the DSX are also available.

Manual optical loopbacks

Front access to the optical connectors on the optical line interface unit

(OLIU) circuit pack allows easy manual optical loopback. This loopback is performed by connecting a fiber jumper from the OLIU circuit pack output to its input. In some cases a lightguide buildout assembly is required to prevent receiver overload when performing loopbacks.

Internal testing capabilities

Technicians can use the internal testing capabilities for installation and manual troubleshooting. The DS1 and DS3 test signal generators and detectors are integrated into the system, eliminating the need for external test equipment to perform transmission tests.

Specific testing

DMX also allows technicians to test specific system components. In addition to the automatic diagnostics, DMX provides tests for LEDs, office alarms, and the SYSCTL circuit pack.

365-372-300

Issue 8.0 September 2006

6 - 3 5

Operations, Administration, Maintenance, and Provisioning

Test Access

Overview

Test access, a traditional DCS function, allows the user visibility into any VT1.5/STS-1 signal in the network. Test access aids users in turning up connections and in identifying faults in existing service connections. DMX supports three different types of test access. The non-intrusive method simply taps the VT1.5/STS-1 channel as it passes through the system and routes it to an external testing device. The more intrusive mode splits the VT1.5/STS-1 from the incoming signal and sends it to an external testing device. The third form of test access involves using the internal test head, located on the LNW59 only, to generate and detect Pseudo Random Bit Sequences (PRBSs) on up to

12 STS-1s or 4 STS-3(c) signals. Test access facilitates DMX functioning in a DCS application.

PRBS generation/detection

For detailed information regarding internal test access using PRBS, refer to

PRBS generation/detection

Test access interworking

DMX supports interworking with various Test-Head vendors.

Test access rates

DMX supports test access sessions at the STS-1, STS3(c) and VT1.5 rates.

Test access modes

DMX supports test access sessions in the following modes:

• MONE

• MONEF

• SPLTE

• SPLTEF

• SPLTA (for PRBS generation/detection only)

6 - 3 6

365-372-300

Issue 8.0 September 2006

Test Access

MONE mode

Operations, Administration, Maintenance, and Provisioning

The MONE mode is used to monitor the E Tributary input signal of a one-way cross-connection or an idle E Tributary input signal (no crossconnection).

The following figure shows an example of the MONE mode used to monitor the E Tributary input signal of 2 separate one-way crossconnections.

Network Element

A Direction

Tributary

B Direction

Test Access

Tributary 1

Testing System

Legend:

- No connection

MA-DMX-373

If the F Tributary is entered, the F Tributary must be the destination of a one-way cross-connection that has the E Tributary as the source. If the

E Tributary is part of a one-way multicast cross-connection, entering the F Tributary is optional. The system automatically retrieves the other end. The E Tributary or F Tributary can not be on an Ethernet circuit pack.

SPLTE mode

The SPLTE mode is used to test the E Tributary signal.

The following figure shows an example of the SPLTE mode used to test the E Tributary signal of 2 separate one-way cross-connections.

Network Element

A Direction

AIS

Tributary

B Direction

Test Access

Tributary 1

Testing System

Legend:

- No connection

MA-DMX-374

The E Tributary signal is split from the F Tributary signal. AIS is transmitted on the outgoing F Tributary signal. and the incoming F

Tributary signal is terminated. If more than one independent one-way cross-connection exists to the E Tributary, the SPLTE mode is denied.

The E Tributary can also be idle (no cross-connection). The E Tributary or F Tributary cannot be on an Ethernet circuit pack.

365-372-300

Issue 8.0 September 2006

6 - 3 7

Test Access

STS-1 Test Access Matrix

Operations, Administration, Maintenance, and Provisioning

The table below provides all the STS-1 test access specifications supported by DMX. The numbers in the table below (e.g. R4.0, R5.1, etc....) represent the software release number in which that configuration is first supported. Test access on STS-3(c) signals is only supported in SPLTA, SPLTE, and MONE modes using the internal test head located in the VLF Main packs for PRBS generation/detection

Table 6-7 STS-1 Test Access

TATRIBs

Main Add/

Drop STS1

XC To: d,e

Thru XC

ETRIB and

FTRIB

DS3/EC1

(FN A-D) hairpin to: d,e

OC3/12/48

(FN A-G) hairpin to: d,e

OC-192 h

(M1/M2) hairpin to

Slot Signal

A-G DS3/

EC1

A-G OC-3/

12/48 f,g

A-D DS3/

EC1

A-G OC-3/

12/48 f,g

TMUX i

A-D DS3/

EC1

A-G OC-3/

12/48 f,g

M1/

OC-

192

R4.0

BLSR R4.0

UPSR R5.1

R4.0

R7.0

R4.0

R7.0

A-D Slots (elect)

DS3/EC1 TMUX

LNW16

LNW19

LNW19B

LNW20

LNW18

LNW20

A-G Slots

1+1 only b

OC-3/

LNW36

LNW37

LNW46 a

(opt)

M1/M2

Slots a

1+1 only b

(opt)

OC-3/

LNW31

OC-48 OC-12/48/

192 h

LNW45

LNW49

LNW62

All Main

OLIUs

Deny

R7.0

Deny

R7.0

R4.0

R5.1

R4.0

R7.0

R4.0

R7.0

R5.1

R7.0

R5.1

R7.0

R4.0

R5.1

R4.0

R7.0

R4.0

R7.0

R4.0

R5.1

R4.0

R7.0

R4.0

R7.0

6 - 3 8

365-372-300

Issue 8.0 September 2006

Test Access

Operations, Administration, Maintenance, and Provisioning

Notes

a.TATRIB1 and TATRIB2 are always connected to the same optical interface b.Intended for unprotected interfaces to locally-connected testheads only;

Network-connected testheads - Future c.EC1 mode interfaces only.

d.Test Access of locked cross connections restricted to electrical TATRIBs e.Test Access of UPSR Dual Ring Interworking cross connections not supported f.LNW45 and LNW49 begins in R5.1

g.Test access of low-speed BLSR cross-connections not supported h.All high-speed Main OLIUs allow the STS-1 test access modes specified in this table. Hairpins from high-speed Main interfaces to other high-speed Main interfaces only allowed on the LNW59 because it is the only Main OC-192 pack with multiple ports. Generation and detection of PRBS only supported on the LNW59.

i.TMUX test access in the G slots only supported using the LNW20 in portless mode.

365-372-300

Issue 8.0 September 2006

6 - 3 9

Test Access

VT1.5 Test Access Matrix

Operations, Administration, Maintenance, and Provisioning

Important!

The "dual tatrib" modes (MONEF and SPLTEF) of VT test access are not possible when the system is equipped with small/ medium VT fabric Main OLIUs. This applies to all systems equipped with OC3 or OC12 Main OLIUs.

The table below provides all the VT1.5 test access specifications supported by

DMX

. The numbers in the table below (e.g. R4.0, R5.1, etc) represent the software release number in which that configuration is first supported.

Table 6-8 VT1.5 Test Access

TATRIBs

ETRIB and

FTRIB d

Main

Add/

Drop

VT1.5

XC To: e,f

DS1/E1

TMUX

(FNA-D)

VT1.5 hairpin to: e,f

A-

Slot Signal

A-

DS3/

EC1 c

R4.0

TMUX

DS1/E1

R4.0

OC-3/12/

48 g

DS3/

EC1 c

TMUX

R4.0

DS1/E1 R4.0

OC-3/12/

48 g

R4.0

A-D Slots

EC1

LNW16

LNW19

LNW19B

LNW20

A-G Slots aunprotected 1+1 only b

TMUX

LNW18

LNW20

DS1/E1 OC-3/

LNW6/

7/8

LNW36

LNW37

LNW46

OC-3/

LNW45

LNW49

OC-48

LNW31

LNW62

M1/M2

Slots a

1+1 only b

OC-12/

48/192 i

All Main

OLIUs

R4.0

R5.1

R4.0

R7.0

6 - 4 0

365-372-300

Issue 8.0 September 2006

Test Access

TATRIBs

Operations, Administration, Maintenance, and Provisioning

ETRIB and

FTRIB

(cont.) d

OC3/12/

48 (FN

A-G)

VT1.5 hairpin to: e,f

A-

M1/

DS3/

EC1 c

TMUX

DS1/E1 f

OC-3/12/

48 g

TMUX

(LNW20 portless only)

OC-12/

48/192 i

LNW16

LNW19

LNW19B

LNW20

R4.0

R7.0

R4.0

A-D Slots

EC1

A-G Slots aunprotected 1+1 only b

TMUX

LNW18

LNW20

DS1/E1 OC-3/

LNW6/

7/8

LNW36

LNW37

LNW46

OC-3/

LNW45

LNW49

OC-48

LNW31

LNW62

M1/M2

Slots a

1+1 only b

OC-12/

48/192 i

All Main

OLIUs

R4.0

R7.0

R4.0

R7.0

R4.0

R7.0

R4.0

R5.1

R7.0

R5.1

R4.0

R7.0

R4.0

R7.0

R4.0

Notes

a. TATRIB1 and TATRIB2 are always connected to the same optical interface b. Intended for unprotected interfaces to locally-connected testheads only;

Network-connected testheads - Future c. EC1 mode interfaces only.

d. Large VT Fabric Mains Only; restrictions apply for LNW26/26B-type, or any OC3/12 Main OLIU.

e. Test Access of locked cross connections restricted to electrical TATRIBs.

f. Test Access of UPSR Dual Ring Interworking cross connections not supported.

g. LNW45 and LNW49 begins in R5.1.

h. Test access of low-speed BLSR cross-connections not supported.

i. All high-speed Main OLIUs allow the STS-1 test access modes specified in this table. Generation and detection of PRBS only supported on the LNW59

(R7.0).

365-372-300

Issue 8.0 September 2006

6 - 4 1

Test Access

Operations, Administration, Maintenance, and Provisioning

PRBS generation/detection

PRBS) generated internal to the NE, and/or monitoring a received test signal internal to the NE. PRBS generation/detection is supported on

STS1 and STS3c tributaries.

DMX allows up to 12 test access sessions at a time and for a mix of the old style test access sessions described on the previous pages

Test access for STS3c rates is new in R7.0. Only internal test access is supported on STS3c signals; requests using the tatrib parameter(s) will be denied. It’s important to note that when a generator or detector is allocated to an STS3c session, it uses 3 of the 12-STS1 capacity, and that 3 generators or detectors on the STS3c boundary must be available.

Generation and detection functionality

PRBS Generation is totally independent of detection and error counting. The only similarity is that they both occur in the context of test sessions. One session may produce a signal that is detected/ measures by a different session (in the same, or different DMX).

While measurement/monitoring of incoming PRBS signals is occurring, the shelf collects total measurement session counts and PMstyle counts, including 15-minute and day bins tied to the time-of-day clock. The bins are retrieved by the user on-demand and are freed when the test access session (not the measuring session) ends. Bins survive a non-powerup shelf restart and are initialized by a power-up shelf restart.

6 - 4 2

365-372-300

Issue 8.0 September 2006

Test Access

Operations, Administration, Maintenance, and Provisioning

Modes allowed for PRBS functionality

DMX supports PRBS enabled internal test access sessions in the following modes:

• MONE

• SPLTE

• SPLTA (new in R7.0)

DMX must be in MONE mode to initiate a PRBS enabled test access session. The mode must then be changed to either SPLTE or SPLTA in order to support the configurations detailed below.

Testing to a far-end loopback

This configuration involves a SPLTE test session at a single DMX node, with generation and detection at the same node. The tributary under test must be cross-connected.

AIS

Network Element

Tributary

Loopback

PRBS

Generator

PRBS

Detector

DMX Test Node: SPLTE Mode

Far-end Node (may be other vendor’s equipment or another DMX)

JK-E-21

DMX is first set to MONE mode and then changed to SPLTE mode.

AIS is inserted into the tributary being tested until the PRBS generator is set to generate and insert a bit sequence on that tributary. The

Generator and detector are then connected to the tributary. The PRBS is inserted into the tributary, sent to and looped back at the far-end, and then monitored for errors by the PRBS detector located on the VLF

Main.

365-372-300

Issue 8.0 September 2006

6 - 4 3

Test Access

Operations, Administration, Maintenance, and Provisioning

Head-to-head testing

This configuration involves generating a signal at one node (node A), and monitoring the signal at a different node (node B). Note that the tributary under test at node A must be cross-connected. The tributary at node B may or may not be cross-connected.

Tributary

PRBS

Generator

DMX Test Node A: SPLTA Mode

PRBS

Detector

DMX Test Node B: SPLTA Mode

JK-E-23

Node A and B are first set to MONE mode, but while the generator on

Node A is then connected to the tributary and the detector on Node B is also connected to the tributary. The PRBS signal originating at Node A is monitored for errors by the PRBS detector located on the VLF Main in Node B.

Total network testing

This configuration involves a SPLTA test session at a single DMX node, with generation and detection at the same node. The tributary under test must be cross-connected.

Loopback

Tributary

Far-end Node (may be other vendor’s equipment or another DMX)

PRBS

Detector

PRBS

Generator

DMX Test Node: SPLTA Mode

Far-end Node (may be other vendor’s equipment or another DMX)

JK-E-21

DMX is first set to MONE mode and then changed to SPLTA mode.

AIS is inserted into the tributary being tested until the PRBS generator is set to generate and insert a bit sequence on that tributary. The generator and detector are then connected to the tributary. A PRBS is inserted into the tributary, sent to and looped back at the far-end, passed-through Node A and sent to a far-end node in the other direction where it is looped back to Node A. The PRBS signal is then monitored for errors by the PRBS detector located on the VLF Main in Node A before the tributary is terminated.

6 - 4 4

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

WaveStar

CIT

Overview

Purpose

This section describes the WaveStar

CIT.

Contents

The information provided in this section includes:

Introduction to the WaveStar

CIT

WaveStar

CIT Access

365-372-300

Issue 8.0 September 2006

6 - 4 5

Operations, Administration, Maintenance, and Provisioning

Introduction to the WaveStar

CIT

What is the WaveStar

CIT?

WaveStar

CIT functionality

TL1 interface

The WaveStar

CIT is the primary tool used to interface with DMX. It is a personal computer (PC) with the WaveStar

CIT user-interface software installed.

The WaveStar

CIT supports the following user interface options:

• Graphical user interface (GUI)

• TL1 command builder

• TL1 cut-through access to other NEs

The WaveStar

CIT is referred to as the “WaveStar

CIT” because the

DMX user-interface software is integrated with the WaveStar

CIT software for the WaveStar

products.

The WaveStar

CIT provides an easy-to-use interface and security features to prevent unauthorized access. The WaveStar

CIT supports the following:

• Local access control based on login and password

• OSI neighbor discovery for easy access to the local NE(s)

• User provisioning of cross-connections, equipment, Ethernet services, software management, protection provisioning, and fault management

• Reports on NE equipage, cross-connections, alarms, and states

The interface between the WaveStar

CIT and the DMX supports TL1 messages. This interface allows the WaveStar

CIT to issue TL1 commands and receive responses, as well as receive TL1 alarm reports from autonomous events that are detected by the DMX.

6 - 4 6

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

WaveStar

CIT Access

WaveStar

CIT access methods

The WaveStar

CIT can access a network element using the following:

• Front and rear IAO LAN ports supporting OSI communications

• Front and rear IAO LAN ports supporting TCP/IP communications

• Front serial port

• Rear serial port

WaveStar

CIT direct local access

The recommended method for temporary local access is to connect the

WaveStar

CIT to DMX via the CIT

LAN

port on the system controller

(

SYSCTL

) circuit pack faceplate.

The WaveStar

CIT can also be connected to the serial

CIT RS-232

port on the

SYSCTL

circuit pack faceplate.

Figure 6-8 CIT Direct Local Access

OSI or TCP/IP

Front IAO LAN Port

Metropolis

DMX

Serial

Front Serial Port

SYSCTL nc-dmx-001

Important!

When the WaveStar

CIT is directly connected to the CIT LAN port (not to an Ethernet LAN hub), a LAN crossover cable is required.

365-372-300

Issue 8.0 September 2006

6 - 4 7

WaveStar® CIT Access

WaveStar

CIT access via rear IAO LAN Port

Operations, Administration, Maintenance, and Provisioning

The rear IAO LAN port supports local and/or remote WaveStar

CIT access. The figure below shows how the rear IAO LAN port can be used to provide local WaveStar

CIT access by connecting to a local

Ethernet LAN hub. The WaveStar

CIT is depicted as being local but could also be remote. For local access, either the OSI protocol stack or

TCP/IP could be used. For remote access, typically TCP/IP would be used.

Figure 6-9 WaveStar

CIT Access via rear IAO LAN Port

WaveStar

CIT

OSI or

TCP/IP

10/100BaseT Ethernet

LAN Hub

OSI or

TCP/IP

OSI or

Rear IAO

TCP/IP

LAN Port

Metropolis

DMX

OC-48

UPSR with

DCC

Metropolis

DMX

Rear IAO

LAN Port

Metropolis

DMX

OC-48

UPSR with

DCC

Metropolis

DMX nc-dmx-005

WaveStar

CIT access via

TCP/IP LAN

For security reasons (and per SIF standards), neither local nor remote

TCP/IP access via the DMX IAO LAN ports is allowed by default.

6 - 4 8

365-372-300

Issue 8.0 September 2006

WaveStar® CIT Access

Operations, Administration, Maintenance, and Provisioning

WaveStar

CIT remote access using DCC

A WaveStar

CIT with direct physical access to a local DMX can also be used to access remote NEs with DCC connectivity to the local

DMX. WaveStar

CIT remote access over DCC is functionally equivalent to WaveStar

CIT direct access.

Figure 6-10 WaveStar

CIT Access via DCC

WaveStar

CIT

IAO LAN (OSI or TCP/IP) or front serial ports

Metropolis

DMX

OC-48

UPSR with

DCC

Metropolis

DMX nc-dmx-004

365-372-300

Issue 8.0 September 2006

6 - 4 9

WaveStar® CIT Access

Operations, Administration, Maintenance, and Provisioning

Remote access to the rear serial port

DMX can also be accessed remotely via dialup modems, but not by the

WaveStar

CIT software. The rear serial port when equipped with the recommended cable is configured as DTE to allow a permanent modem connection.

A PC with a terminal emulation software package, such as

HyperTerminal, can be used for access to DMX’s rear serial port via dialup modems. The PC can use its internal modem or an external modem (shown). This form of access supports TL1 messages only, and can be used to access remote NEs with DCC connectivity to the DMX with the modem connection.

Figure 6-11 Remote WaveStar

CIT Access via modem

WaveStar

CIT

Serial

Modem

Rear

Serial Port

Metropolis

DMX

OC-48

UPSR with

DCC

Metropolis

DMX nc-dmx-006

6 - 5 0

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Protection Switching

Overview

Purpose

This section describes the types and functions of protection switching in the DMX Access Multiplexer.

Contents

The following protection switching topics are discussed in this section:

Line Protection Switching

Path Protection Switching (Path Switched Rings)

Line Protection Switching (Line Switched Rings)

Spanning Tree

Resilient Packet Ring (RPR)

Link Aggregation (LNW70 LAN ports)

Equipment Protection

Application modes

There are five types of protection application modes, listed below:

•

BLSR (OC-48 and OC-192)

• UPSR

• Linear 1+1

—Unidirectional 1+1

—Bidirectional 1+1

—Bidirectional optimized 1+1

• 0x1

• 0x1Sn

The UPSR application mode provides ring path protection switching on high-speed interfaces.

The linear application mode provides 3 types of protection switching:

Unidirectional 1+1. Bidirectional 1+1, and Bidirectional Optimized

1+1. It is functionally equivalent to a 1+1 protected configuration, providing path switching on all paths within a high-speed line if that particular line fails.

365-372-300

Issue 8.0 September 2006

6 - 5 1

Overview

Operations, Administration, Maintenance, and Provisioning

R6.0 added support of revertive unidirectional and bidirectional 1+1, in additional to the non-revertive option offered in past releases.

0x1Sn mode

When not equipped with VLF Main packs (LNW59), DMX supports an unprotected 0x1Sn mode. This option is user-provisionable on a perport basis. 0x1S1 and 0x1S2 are provisionable applications for LS OCn port pairs. For 0x1S1, the port in slot 1 is unprotected and the companion port in slot 2 is unused. For 0x1S2, the port in slot 2 is unprotected and the companion port in slot 1 is unused.

6 - 5 2

365-372-300

Issue 8.0 September 2006

Overview

True 0x1 mode

Operations, Administration, Maintenance, and Provisioning

Very Large Fabric

(VLF) Engineering Rules

In the case of OLIUs (SONET optical line interface packs), all ports in a pack must be set to 0x1 application in order for a different pack to be used in the companion slot. If any pair of lines is provisioned for a protected application (+1, UPSR, BLSR), then both packs in the group must be of the same type.

True 0x1 replaces 0x1Sn functionality when VLF Mains are used. True

True 0x1 is only available on the low-speed/tributary packs, not on the

Main (M1/M2) interfaces.

When two circuit packs in the same low-speed group are operating in

True 0x1 enables hairpin cross-connections between channels on packs in different slots of the same Function or Growth group.

365-372-300

Issue 8.0 September 2006

6 - 5 3

Overview

Operations, Administration, Maintenance, and Provisioning

Ethernet interface protection

On the WAN (SONET) side of the network, DMX utilizes standard

IEEE 802.1D and fast 802.1w spanning tree protection for multipoint applications and/or STS-1 UPSR protection (for point-to-point applications). Spanning Tree protection is not available on the 10/100-

FEPL (LNW71) pack. See the section entitled Spanning Tree (6-61) for

more information.

DMX also supports Resilient Packet Ring (RPR) protection for

Ethernet interfaces using the LNW78. For more information on RPR bridging and switching refer to the sections entitled

Resilient Packet Ring

(RPR)

In R7.0, DMX adds support for link aggregation on any two LNW70

LAN ports of the same rate (i.e. 100 or 1000 Mbps), operating in switched mode. In R7.0, the two ports comprising a LAG must be located on the same pack.

Link aggregation can also provide facility protection on LNW70 LAN ports. Link aggregation is also able to remove failed links automatically, thereby providing a means of facility protection. When a link fails, traffic is shifted to the remaining links in that Link

Aggregation Group (LAG). More links than are needed can be added to the group and each is active until it fails (similar to utilizing LCAS protection for SONET tributaries). For more information on link aggregation, refer to

Link Aggregation (LNW70 LAN ports)

6 - 5 4

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Line Protection Switching

Overview

DMX offers 5 modes of linear protection switching: unidirectional 1+1 non-revertive line switching, bidirectional 1+1 non-revertive, unidirectional 1+1 revertive line switching, bidirectional 1+1 revertive, and bidirectional optimized 1+1 protection switching. All three types of linear protection switching occur automatically in response to detected faults, as well as in response to external commands from technicians at a local or remote CIT or OS.

Protection switching priorities

DMX uses standard protection switching priorities as follows:

• Lockout of protection

• Forced switch (FS)

• Automatic switch: signal fail (SF)

• Automatic switch: signal degrade (SD)

• Manual switch (MS)

DMX allows you to provision these parameters with different priorities in relation to each other. For example, SF can be set with a higher priority than FS and vice versa.

Unidirectional and bidirectional 1+1 non-revertive and revertive line switching use switch procedures as specified by the SONET standards.

DMX offers bidirectional optimized 1+1 protection switching which uses switching procedures specified in ITU-T G.841, Annex B.

Bidirectional optimized 1+1 is designed to enable interoperability between DMX and SDH equipment. It is a separate switching scheme from standard 1+1 bidirectional and does not work with standard 1+1.

365-372-300

Issue 8.0 September 2006

6 - 5 5

Line Protection Switching

Operations, Administration, Maintenance, and Provisioning

Automatic line switching

Automatic line switches are initiated by signal fail and signal degrade conditions on the received OC-n signal. This signal’s BER is calculated from violations in the SONET line overhead B2 parity byte. Signal fail is declared for incoming loss of signal, loss of frame, line AIS, or a

BER exceeding a provisionable 10

-3

to 10

-5

threshold, while a BER exceeding a provisionable 10

-5

to 10

-9

threshold causes the signal degrade condition. A line protection switch is completed within 50 milliseconds of the onset of a hard failure such as a fiber cut.

In multispan applications (for example, hubbing), each OC-n span switches independently. For example, in hubbing applications, a switch on the central office-to-hub span will not cause switches on any of the hub-to-remote spans. Similarly, a line switch on a hub-to-remote span will not propagate to other hub-to-remote or central office-to-hub spans.

6 - 5 6

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Path Protection Switching (Path Switched Rings)

Overview

DMX supports path switched ring applications using the path protection switching schemes described in Telcordia Technologies GR-

1400. This scheme offers 60-millisecond restoration times and simple network administration for access applications. The ring facility consists of two fibers, with service and protection rotating in opposite directions. Each input is bridged and transmitted in both directions around the ring. The receiving end terminal monitors the quality of both signals and selects the best signal to drop.

UPSR configurations

DMX supports the following OC-3/OC-12/OC-48/OC-192 path switched ring configurations:

• OC-3: VT1.5/STS-1/STS-3c

• OC-12: VT1.5/STS-1/STS-3c/STS-12c

• OC-48: VT1.5/STS-1/STS-3c/STS-12c/STS-48c

• OC-192: VT1.5/STS-1/STS-3c/STS-12c/STS-48c

Path protection switching is non-revertive. A manual path protection switching command allows switching to the other path for ease of ring maintenance. STS-n path switching is indirectly triggered by the line defects LOS and LOF by virtue of the fact that these generate downstream path AIS. The system also supports VT path protection switching based on VT AIS, LOP, unequipped, and signal degrade.

DMX also supports STS-1/STS-3c non-revertive path protection switching on low-speed OC-3 optical interfaces, STS-1/STS-3c/STS-

12c non-revertive path protection switching on low-speed OC-12 optical interfaces, and STS-1/STS-3c/STS-12c non-revertive path protection switching on low-speed OC-48 optical interfaces. Path protection is user-provisionable on a per-cross-connection basis when the port is set to UPSR.

Unswitched UPSR

DMX provides an unprotected cross-connect mode, referred to as unswitched UPSR, on OC-3/12/48 low-speed ports and OC-12/48/192 high-speed UPSRs. This option is user-provisionable on a per crossconnection basis and supports single- and dual-homed ring on ring topologies. Path protection and internal equipment (switch fabric) protection is disabled in Unswitched configurations.

Mixed protection modes

By supporting protection mode provisioning on a per port basis, DMX provides for the mixing of protection modes across the ports of a multiport pack.

365-372-300

Issue 8.0 September 2006

6 - 5 7

Path Protection Switching (Path Switched Rings)

Locked DS1/DS3 Cross

Connections

Operations, Administration, Maintenance, and Provisioning

Locked VT Cross

Connections (R7.0)

In the “locked” mode, DMX does not select the best signal from both rotations of a UPSR. Instead, traffic is added and dropped (locked) from one rotation of the ring only (provisionable). The main advantage of locked VT cross-connections is the lack of UPSR switching which results in the ability to reuse timeslots around a UPSR.

The ability to mix locked, unlocked, and pass-through VT1.5s within the same STS-1 was added in R6.0.2. In R7.0, DMX also allows both rotations of a ring to be used simultaneously.

Locked cross-connections are only used in systems that are not equipped with VLF Mains because VLF mains allow unprotected

(linear) UPSR cross-connections which allow users to independently provision cross-connections on UPSR tributaries. In systems with non-

VLF Mains, once a locked cross-connection is established from a

UPSR tributary, the companion tributary cannot be cross-connected.

6 - 5 8

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Line Protection Switching (Line Switched Rings)

Overview

A 2-fiber bidirectional line-switched ring (BLSR) is a self-healing ring configuration in which switching is bidirectional between each pair of adjacent nodes and is protected by redundant bandwidth on the bidirectional lines that interconnect the nodes in the ring. Because switching is bidirectional between nodes, traffic can be added at one node and dropped at the next without traveling around the entire ring.

This leaves the spans between other nodes available for additional traffic. Therefore, with distributed traffic patterns, a BLSR can carry more traffic than the same facilities could carry if configured for a unidirectional line-switched ring.

The DMX supports one high-speed OC-48 2-fiber BLSR, 2 high-speed

OC-192 2-fiber BLSRs (requires LNW59), and up to 15 low-speed

OC-48 BLSRs. In the latter application, the low-speed OC-48 BLSR is hosted by OC-48 circuit packs housed in the Function slots and can add and drop traffic with the high-speed OC-48/192 circuit packs housed in the Main slots as well as any circuit packs housed in the Function Units or Growth slots. The maximum number of 15 low-speed BLSRs requires the use of the LNW62 (4-port OC-48) pack. When the LNW62 is not used, DMX can support a maximum of 5 low-speed OC-48

BLSRs.

Self-healing rings

DMX 2-fiber BLSRs are self-healing in that transport is automatically restored after node or fiber failures. Each OC-192 line carries 96 STS-1 equivalent timeslots of working capacity plus 96 STS-1 equivalent timeslots of protection capacity. Each OC-48 line carries 24 STS-1 equivalent timeslots of working capacity plus 24 STS-1 equivalent of protection capacity. In the event of a fiber or node failure, service is restored by switching traffic from the working capacity of the failed line to the protection capacity in the opposite direction around the ring.

In the event of a node failure, traffic added and dropped from the failed node is not protected by line switching.

Protection switching

When a line failure triggers a protection switch, the nodes adjacent to the failure switch traffic on to protection capacity. Traffic heading toward the failure is looped back on to the protection capacity traveling away from the failure to reach its destination by traveling the opposite way around the ring. Service is reestablished on the protection capacity

365-372-300

Issue 8.0 September 2006

6 - 5 9

Line Protection Switching (Line Switched

Rings)

Operations, Administration, Maintenance, and Provisioning

≤

50 milliseconds after detection of the failure (for catastrophic failures in rings without existing protection switches or extra traffic).

6 - 6 0

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Spanning Tree

Overview

This section provides information on the spanning tree protocol and spanning tree groups. The DMX now supports a faster spanning tree algorithm documented in IEEE 802.1w.

Important!

DMX has been designed with multi-vendor interoperobility in mind. As many vendor’s equipment (including legacy equipment) may not be able to use IEEE802.1w, DMX can automatically fall back on IEEE802.1d in the event that other NEs in the network are running standard spanning tree protocol.

However DMX employs IEEE 802.1w as a default spanning tree protocol.

Function of spanning tree

If there is a loop in the network, that is, if there is more than one way to get to a destination device, two problems can result:

• Frames may be duplicated in the network. That is, the same frame may be sent to a node via two different paths.

• The address information will be changed as packets from that device are received across different paths. In a meshed network, the reconfiguration of the filtering database can begin to use up all the network resources, so that little bandwidth is left for data traffic.

The spanning tree accomplishes two important functions:

• It removes loops from the bridged network

• It allows reconfiguration if a link fails.

How it works

The spanning tree works as follows:

Initially, every node in the group thinks it is the root node.

As information about the network becomes clear, one node is designated the root node.

It is from this node that the distance to any point in the network may be measured.

365-372-300

Issue 8.0 September 2006

6 - 6 1

Spanning Tree

Operations, Administration, Maintenance, and Provisioning

Configuration BPDUs are sent from each node to determine the most economical route from each node to the root node.

Some ports are blocked so that there are no loops in the network and so that the network provides the most efficient paths from the root to the nodes.

This effectively creates a tree structure for the network.

If an active link fails, the network is re configured so that previously blocked links can be used for traffic.

The following figure illustrates the spanning tree:

Figure 6-12 Spanning Tree Switch

Root Bridge

6 7 nc-dmx-162

Legend:

Active Links 1- 2; 2- 3; 3 -4; 5-6; 6-7; 7-1

Inactive Links 4-5

X Indicates a blocked port (no packets sent or received on this port).

Note that the configuration provides the shortest (most efficient) path from each node to the root. The configuration also provides only one path from the root node to any other node.

Re configuration

If one of the active links were broken, the network would reconfigure to allow traffic to get to the nodes. For example, if the link between 3 and 4 were broken, the link between 5 and 4 would be enabled. When the failure/break is repaired, the network will revert to the original configuration.

6 - 6 2

365-372-300

Issue 8.0 September 2006

Spanning Tree

Operations, Administration, Maintenance, and Provisioning

Spanning Tree on LAN ports

DMX added support for spanning tree on the LAN (customer facing) ports in R6.0. STP on LAN ports ensures that single LAN interconnects are protected. Because redundant LAN interconnects create loops, STP manages the loops. In R6.0, STP is supported on the LAN ports of the

LNW70 only.

Both LAN ports and VCGs can belong to STP groups. A LAN port can belong to only one STP group at a time. Beginning in R6.0, the BDPU

VLAN ID becomes provisionable. VLAN IDs are provisionable on a per-port basis. Prior to R6.0 all VLAN IDs were #4094

LAN based STP works exactly as described in the section above. The figure below depicts STP functioning on the customer side of a DMX with LNW70 circuit packs. The nodes marked A and B represent remote Ethernet switches or similar CPEs.

Figure 6-13 Spanning Tree on LAN ports

Root bridge

Path 1

JK-E-14.eps

Legend:

Active Links 1 to 2; 1 to B; B to A

Inactive Links A to 2

X Indicates a blocked port (frame forwarding is disabled)

365-372-300

Issue 8.0 September 2006

6 - 6 3

Operations, Administration, Maintenance, and Provisioning

Resilient Packet Ring (RPR)

Overview

DMX supports Resilient Packet Ring (RPR) Ethernet transport compliant with IEEE 802.17. RPR is intended to optimize Ethernetbased metro ring networks for packet transport with resiliency equivalent to that of SONET rings. A description of protection switching in RPR is below.

Steering Protection

DMX uses steering protection to recover from failures in RPR mode.

As shown in the figure below, all the nodes around the RPR ring learn of a failure through topology messaging. The nodes then redirect transmission to reach destination addresses. RPR steering provides <50 msec recovery time (similar to SONET) and is revertive.

Steering with Enhanced Bridging

The figure below depicts steering protection as it would function with

Enhanced RPR bridging. With enhanced bridging all nodes learn the location to which the destination address belongs and transmit packets one-way (unicast), directly toward the destination node. If packets are originating at node “x” and their destination is node “y”, and a failure occurs in the shortest path, the “x” node will perform the steering function to send packets back around the ring in the other direction.

With enhanced bridging, the post-failure transmissions will also be unicast.

Figure 6-14 Steering Protection with Enhanced Bridging

Enhanced Bridging

1 1

8 2

6 4

3 7

Before Steering

After Steering

MA-DMXplore-063

6 - 6 4

365-372-300

Issue 8.0 September 2006

Resilient Packet Ring (RPR)

Operations, Administration, Maintenance, and Provisioning

Steering with Basic Bridging (R7.0)

The figure below depicts steering protection with basic bridging. Basic bridging is supported in R7.0. Basic bridging functions using unidirectional flooding (see the graphic on the left of the figure below).

If the RPR ring is set to use basic bridging with unidirectional flooding, steering will force it into bidirectional flooding as pictured on the right side of the figure below.

Figure 6-15 Steering Protection with Basic Bridging

Basic Bridging

1 1

Y Y

8 2 8 2

3 7

6 4

Before Steering

(Unidirectional Flooding)

Cleave point - Based on

Failed Span

After Steering

(Bidirectional Flooding)

MA-DMXplore-064

365-372-300

Issue 8.0 September 2006

6 - 6 5

Operations, Administration, Maintenance, and Provisioning

Link Aggregation (LNW70 LAN ports)

Overview

DMX supports link aggregation on any two LNW70 LAN ports of the same rate (i.e. 100 or 1000 Mbps), operating in switched mode. In

R7.0, the two ports comprising a LAG must be located on the same pack.

Link aggregation can also provide facility protection on LNW70 LAN ports.

Hitless bandwidth increase/ decrease

Ordinarily, multiple Ethernet links between two bridges form loops

(unless a spanning tree blocks all but one) so they can’t be used to increase bandwidth. Link Aggregation causes defined groups of links to be treated as a single logical link, making multiple LAN ports appear as one. In this way, Bandwidth may be increased without requiring an upgrade to a higher rate link.

Facility protection

More links than are needed can be added to the group and each is active until it fails (similar to utilizing LCAS protection for SONET tributaries).

Link aggregation control protocol

Link Aggregation is specified in IEEE 802.3 clause 43, formerly specified in 802.3ad. The LNW70 can be configured to either use this standard protocol to control link aggregation (which negotiates with the equipment at the other end of the link) or to simply force aggregation without a control protocol.

6 - 6 6

365-372-300

Issue 8.0 September 2006

Link Aggregation (LNW70 LAN ports)

Operations, Administration, Maintenance, and Provisioning

General link aggregation rules

Link aggregation is available for LAN ports on the LNW70 pack beginning in R7.0 and behaves along the following basic guidelines:

• Available for LAN ports on the LNW70 in switched mode only

• Maximum of 4 LAGs per pack, 2 ports per LAG, and 8 LAGs per function unit or growth group. There are 8 ports on each LNW70 pack.

• The two ports in a LAG must be on the same pack, and be functioning at the same rate (i.e. 100 or 1000 Mbps).

• All links in a LAG are in-service until they fail. Standby links, providing 1x1 SONET-style protection, are a future feature.

• When a LAG is created, the attributes (VLAN, virtual switch, and other L2 provisioning) of the first port used to establish the LAG are transferred to the LAG. When the second port is added, it then inherits the L2, VLAN and Virtual Switch (VS) characteristics of the LAG for the time it remains a member. It can not be part of a

VS or have any VLAN provisioning when added.

-- Both member ports can also be added simultaneously and DMX recognizes a parameter that distinguishes the "Lead Port". The

LAG (and by association, the other port in the LAG) inherits the

L2, VLAN, and VS attributes of the Lead Port.

• When a port is removed from a particular LAG, it is no longer a member of a VS.

• A port must have L2 and VS provisioning in order for a port to be used as the Lead port or to establish a LAG (VLAN provisioning not required). This information is then transferred to the LAG once it’s created.

• The last port/member of a LAG cannot be removed from the

LAG; the LAG itself must be deleted. The last port/member of a the inherits the LAG’s L2, VLAN, and VS attributes.

-- If the last member in the LAG was the first member added originally, and if there were no subsequent changes to L2 and

VLAN attributes, the port will effectively revert to it’s original state when the LAG is deleted.

-- If the last member/port in the LAG was not the first added initially it will inherit the characteristics of the LAG rather than reverting to its original state.

365-372-300

Issue 8.0 September 2006

6 - 6 7

Link Aggregation (LNW70 LAN ports)

Operations, Administration, Maintenance, and Provisioning

Link Aggregation Example

Traffic entering incoming ports is aggregated into a LAG. While both ports are in-service, outgoing traffic is split between working ports.

Figure 6-16 Link aggregation at 100 Mbps

(all ports in-service)

Link Aggregation Group (LAG)

100 Mb

Up to

200 Mbps

LNW70

Link Aggregation Group (LAG)

LNW70

100 Mb

200 Mbps per conversation

MA-DMXAPG-044

The algorithm uses the XOR of the least significant bits of the address

6 - 6 8

365-372-300

Issue 8.0 September 2006

Link Aggregation (LNW70 LAN ports)

Operations, Administration, Maintenance, and Provisioning

pairs to assign a port/link. Therefore, the actual load balancing achieved depends on the distribution of MAC/IP addresses.

365-372-300

Issue 8.0 September 2006

6 - 6 9

Operations, Administration, Maintenance, and Provisioning

Equipment Protection

Overview

All transmission circuit packs are optionally 1x1 protected (not including Ethernet interfaces) and use non-revertive switching. The

ACTIVE LEDs on the 1x1 protected circuit pack faceplates show which circuit packs are carrying service. This aids technicians in circuit pack replacement procedures.

True 0x1 mode

With the introduction of the VLF Main pack (LNW59) in R7.0, DMX allows true 0x1 unprotected circuit packs. That means that tributary packs can function unprotected and any slot can be equipped with any pack (some restrictions apply). Two of the same circuit packs can also populate adjacent slots in the same group (this includes some Ethernet packs). For detailed information on circuit pack/slot equipage

restrictions in 0x1 mode, refer to

Very Large Fabric (VLF) Engineering

Rules

True 0x1 is provisionable on a per-port basis. This allows packs with multiple ports to function in mixed modes with some ports running in a protected mode (UPSR, BLSR, 1+1), while others can be 0x1 unprotected.

In order for an entire pack to be considered 0x1, allowing 2 packs of the same kind to populate adjacent slots as stated above, all ports on the pack must be provisioned for 0x1.

When tributary circuit packs are provisioned for 0x1, all provisioning, reporting and retrieval (of alarms) associated with the pack, ports and tributaries in Slot 1 are independent of the provisioning, reporting and retrieval associated with the pack, ports and tributaries in Slot 2.

Protection switching priorities

The following protection switching priorities on equipment are usercontrollable through TL1 commands:

• inhibit switch (low-speed interfaces only)

• forced switch (low-speed interfaces only)

• manual switch (low and high-speed interfaces)

If protection is not desired, interfaces can be provisioned for no protection by not equipping the adjacent Function Unit slot (for

6 - 7 0

365-372-300

Issue 8.0 September 2006

Equipment Protection

Operations, Administration, Maintenance, and Provisioning

socketed packs using PTMs, the corresponding socket could be unequipped), or by provisioning 0x1Sn. 0x1Sn switching can only be used on low-speed OC-n lines.

365-372-300

Issue 8.0 September 2006

6 - 7 1

Operations, Administration, Maintenance, and Provisioning

Performance Monitoring

Overview

Purpose

This section lists and describes performance monitoring parameters,

SNMP traps and parameters, data storage, thresholds, and TCA transmission.

Contents

The following performance monitoring information is included in this section:

Performance Monitoring Parameters

Performance Monitoring Data Storage

Performance Parameter Thresholds

TCA Transmission to OS

SNMP Parameters and Traps

6 - 7 2

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Performance Monitoring Parameters

Overview

DMX uses performance monitoring (PM) to support proactive maintenance of the network and tariffed service performance verification. Proactive maintenance refers to the process of detecting degrading conditions not severe enough to initiate protection switching or alarming but indicative of an impending hard or soft failure. Hard and soft failures result in reactive maintenance. PM conditions are reported on both SONET and electrical interfaces.

Proactive maintenance

Proactive maintenance consists of monitoring performance parameters associated with the SONET sections, lines and paths within the SONET network, as well as incoming and outgoing bytes and frames on electrical (DS1/3) ports. Table 6-7, PM Parameters (6-57), lists the

SONET performance parameters monitored by DMX. These parameters are thresholded to indicate degraded performance. When a performance-monitoring threshold is crossed, it is reported to the message-based operations system where all threshold crossings associated with a particular path can be correlated, and the likely source of the degradation can be identified. Electrical performance monitoring parameters are listed later in this section.

The figure below shows DS1/DS3 line and path and DS3 path performance monitoring. DMX monitors DS3 line and path parameters from the DSX-3 and DS3 path parameters from the optical path.

Figure 6-17 DS1/DS3 Line/Path Performance Monitoring

DS1/DS3 Line, Path DS3 Path

DSX-1

DSX-3

Metropolis

DMX

OC-12/48/192

Input

DMX = Metropolis DMX Access Multiplexer

NC-DMXPM1

Section parameter

No Far-End PM parameters are defined for the Section layer. The system, as it receives SONET signals, terminates the SONET Section and Line layers and therefore is involved with Section layer PM. Section layer PM applies to optical and electrical SONET interfaces. It also applies to service and protection sections of optical sections.

365-372-300

Issue 8.0 September 2006

6 - 7 3

Performance Monitoring Parameters

Operations, Administration, Maintenance, and Provisioning

Line Layer

A line is a physical transport vehicle that provides the means of moving digital information between two points in a network. The line is characterized by a metallic transmission medium and its specific coding type. A line is bounded by its two end points, known as line terminations. A line termination is the point where the electrical, bipolar line signal is generated and transmitted, or received and decoded.

Path parameter

A path is a framed digital stream between two points in a network and represents digital signal transport at a specified rate, independent of the equipment and media providing the physical means of transporting the signal. A path is defined by its two end points, called path terminations, where its frame structure is generated and decoded. A path may be carried wholly within one transport segment (line), or it may span a sequential arrangement of two or more transport segments.

DS1 performance monitoring

Tariffed service verification consists of monitoring performance parameters that can be associated with the customer’s end-to-end service. The DMX system provides this capability for DS1 services with the DS1 performance monitoring feature. Based on ANSI T1.403 extended superframe format (ESF), this capability retrieves performance messages written into the ESF data link by the customer’s terminal equipment. From these messages, the DMX can determine and report the end-to-end error performance of the entire DS1 link as seen

by the customer. These parameters, listed in Table 6-7, PM Parameters

(6-57), are thresholded and reported to indicate degraded performance, and the counts are retrieved by the message-based operations system to determine if the service is operating within tariffed limits.

Application of the DS1 performance monitoring feature for tariffed service verification is shown in the figure below. This shows an ANSI

T1.403 ESF format DS1 service carried between points A and Z, using an OC-48/OC-192 system and terminated at the customer’s premises with channel service units (CSUs). At the “A” end, the received error performance, (Z - A) is detected and written by the customer CSU onto the outgoing (A - Z) ESF data link as a performance report message

(PRM). The DS1 PM circuit pack interfacing the A end reads the incoming DS1 signal’s PRM (received from the customer’s premises) and reports the Z - A performance. Likewise, the OC-48/OC-192 system interfacing the Z end reports the A - Z performance by reading the PRM from the customer’s “Z” CSU. By reviewing data from each

OC-48/OC-192 system, the service provider can determine the

6 - 7 4

365-372-300

Issue 8.0 September 2006

Performance Monitoring Parameters

Operations, Administration, Maintenance, and Provisioning

complete end-to-end performance (A - Z and Z - A) of the customer’s service.

DS1PM circuit pack

Additionally, each PM enabled DS1 circuit pack measures the near-end performance of the incoming DS1, allowing the service provider to determine if a good DS1 signal was received from the customer before transporting it through the network. This information can then aid in sectionalizing any reported performance problems. The circuit pack can also provide this same near-end information for super frame (SF) formatted (sometimes known as “D4 framing”) DS1 services, but complete end-to-end performance verification is limited due to the lack of the PRM in the SF format.

Figure 6-18 DS1 Path Performance Monitoring

DS1 PATH

PERFORMANCE

MONITOR

POINT B POINT C

Z-A

Performance

Report

A-B

Performance

Report

Metropolis

DMX

OC-12/48/192

DSX-1 DSX-1

Metropolis

DMX

DS1 PATH

PERFORMANCE

MONITOR

Z-A

Performance

Report

Z-C

Performance

Report

Z-A

PRM

POINT A

CSU

Network

A-Z

PRM

POINT Z

CSU

Legend:

CSU-Channel Service Unit

PRM - Performance Report Message nc-dmx2-033

DS3 performance monitoring

DMX provides DS3 performance monitoring with three DS3 path PM options: P-bit (parity bit), adjusted F&M bit (frame and multiframe bit), and C-bit.

P-Bit

When FMT is set to P-bit, P-bit errors are used as the basis for determining code violation counts. When provisioned for P-bit, the system calculates and provides counts of DS3 P-bit coding violations

(CV), errored seconds (ES), and unavailable seconds (UAS) incoming from the fiber. Quarter-hour and day registers are provided with

365-372-300

Issue 8.0 September 2006

6 - 7 5

Performance Monitoring Parameters

Operations, Administration, Maintenance, and Provisioning

provisionable threshold crossing alerts (TCAs) on a per-shelf basis.

Severely errored frame seconds (SEFS) are also monitored.

Because P-bits can be corrected at nodes provisioned for VMR along a

DS3 path, the DS3 P-bit PM data may not provide a complete report of the end-to-end DS3 path errors.

Adjusted F&M Bit

When FMT is set to FM-bit, F & M bits are used as the basis for determining code violation counts. Adjusted F&M bit performance monitoring provides an alternative method for determining and accumulating DS3 path performance data based on an error estimation technique using errors on the F&M framing bits to approximate the actual error counts in the DS3 path payload. F&M bits are not corrected at nodes provisioned for VMR along a DS3 path. When provisioned for adjusted F&M bit, the system calculates and provides estimated counts of DS3 adjusted F&M bit coding violations (CV), errored seconds

(ES), severely errored seconds (SES), and unavailable seconds (UAS) incoming from the fiber.

Quarter-hour and current day registers are provided with provisionable threshold crossing alerts (TCAs) on a per-shelf basis. Severely errored frame/AIS seconds (SAS-P) are also monitored.

C-Bit

When FMT is set to cbit, C-bit errors are used as the basis for determining code violation counts.

The system provides counts of DS3 C-Bit parity coding violations (CV-

P), errored seconds (ES-P), severely errored seconds (SES-P), and unavailable seconds (UAS-P) incoming from the DSX-3 and the fiber.

The type of performance monitoring is provisioned per DS3 service by a CIT command.

For C-bit PM, the DS3 service can be provisioned in violation monitor

(VM) or violation monitor and removal (VMR) modes. In VM mode, the C-bit errors are not corrected as in the P-bit option.

Quarter-hour and day registers are provided with provisionable threshold crossing alerts (TCAs). The TCAs are provisionable on a pershelf basis. Severely errored frame seconds (SEFS) counts are also provided.

6 - 7 6

365-372-300

Issue 8.0 September 2006

Performance Monitoring Parameters

Operations, Administration, Maintenance, and Provisioning

Provisionable PM parameters

The table below, lists performance monitoring parameters with provisionable thresholds for SONET, Ethernet, SAN, and electrical interfaces.

Table 6-9 Provisionable PM Parameters

DS1 Path

Facility

DS1 Line

DS3 Path

DS3 Line

Parameter definition

CV-P (SF) (Coding Violation count - Path)

CV-P (ESF) (Coding Violation count - Path)

CV-PFE (ESF) (Coding Violation count - Path Far End)

ES-P (Errored Second count - Path),

ES-PFE (Errored Second count - Path Far End)

SES-P (Severely Errored Second count - Path),

SES-PFE (Severely Errored Second count - Path Far End)

UAS-P (Unavailable Second Count - Path),

UAS-PFE (Unavailable Second Count - Path Far End)

SAS-P (SEF/AIS defects Second count - Path),

SEFS-PFE (Severely Errored Frame Second count - Path Far End)

CV-L (Coding Violation count - Line)

ES-L (Errored Second count - Line),

ES-LFE (Errored Second count - Line Far End)

SES-L (Severely Errored Second count - Line)

CV-P (Coding Violation count - Path),

CV-PFE (Coding Violation count - Path Far End)

ES-P (Errored Second count - Path),

ES-PFE (Errored Second count - Path Far End)

SES-P (Severely Errored Second count - Path),

SES-PFE (Severely Errored Second count - Path Far End)

UAS-P (Unavailable Second Count - Path),

UAS-PFE (Unavailable Second Count - Path Far End)

SAS-P (SEF/AIS defects Second count - Path),

SAS-PFE (SEF/AIS defects Second count - Path Far End)

CV-L (Coding Violation count - Line)

ES-L (Errored Second count - Line)

SES-L (Severely Errored Second count - Line)

365-372-300

Issue 8.0 September 2006

6 - 7 7

Performance Monitoring Parameters

E1 Path

E1 Line

Facility

STS-n Path

VT1.5 Path

VC-12 Path

Operations, Administration, Maintenance, and Provisioning

Parameter definition

BBE-P (Background Block Errors - Path),

BBE-PFE (Background Block Errors - Path Far End)

ES-P (Errored Second count - Path),

ES-PFE (Errored Second count - Path Far End)

SES-P (Severely Errored Second count - Path),

SES-PFE (Severely Errored Second count - Path Far End)

UAS-P (Unavailable Second Count - Path),

UAS-PFE (Unavailable Second Count - Path Far End)

ES-L (Errored Second count - Line)

SES-L (Severely Errored Second count - Line)

B3 SES-P (Severely Errored Second count - Path),

SES-PFE (Severely Errored Second count - Path Far End)

B3 UAS-P (Unavailable Second Count - Path),

UAS-PFE (Unavailable Second Count - Path Far End)

FC-P (Failure Counts - Path),

FC-PFE (Failure Counts - Path Far End)

B3 CV-P (Coding Violation count - Path),

CV-PFE (Coding Violation count - Path Far End)

V5 CV-P (Coding Violation count - Path),

CV-PFE (Coding Violation count - Path Far End)

V5 ES-P (Errored Second count - Path),

ES-PFE (Errored Second count - Path Far End)

V5 SES-P (Severely Errored Second count - Path),

SES-PFE (Severely Errored Second count - Path Far End)

V5 UAS-P (Unavailable Second Count - Path),

UAS-PFE (Unavailable Second Count - Path Far End)

FC-P (Failure Counts - Path),

FC-PFE (Failure Counts - Path Far End)

BBE-P (Background Block Errors - Path),

BBE-PFE (Background Block Errors - Path Far End)

ES-P (Errored Second count - Path),

ES-PFE (Errored Second count - Path Far End)

SES-P (Severely Errored Second count - Path),

SES-PFE (Severely Errored Second count - Path Far End)

UAS-P (Unavailable Second Count - Path),

UAS-PFE (Unavailable Second Count - Path Far End)

FC-P (Failure Counts - Path),

FC-PFE (Failure Counts - Path Far End)

6 - 7 8

365-372-300

Issue 8.0 September 2006

Performance Monitoring Parameters

Operations, Administration, Maintenance, and Provisioning

Facility Parameter definition

OC-n Line

OC-n Section

B2 ES-L (Errored Second count - Line),

ES-LFE (Errored Second count - Line Far End)

B2 SES-L (Severely Errored Second count - Line),

SES-LFE (Severely Errored Second count - Line Far End)

B2 UAS-L (Unavailable Second Count - Line),

UAS-LFE (Unavailable Second Count - Line Far End)

FC-L (Failure Counts - Line),

FC-LFE (Failure Counts - Line Far End)

PSC-L (Protection Switch Count - Line)

PSC-P (Protection Switch Count - Path)

PSC-W (Protection Switch Count - Working (BLSR only)

PSD-L (Protection Switch Duration (BLSR only)

PJCDiff-P (Count of the absolute difference between generated and detected pointer justifications - Path)

PPJC-PGen (Positive Pointer Justification Counts Generated)

PPJC-PDet (Positive Pointer Justification Counts Detected)

NPJC-PDet (Negative Pointer Justification Counts Detected)

B2 CV-L (Coding Violation count - Line),

CV-LFE (Coding Violation count - Line Far End)

B1 ES-S (Errored Second count - Section)

B1 SES-S (Severely Errored Second count - Section)

B1 CV-S (Coding Violation count - Section)

EC1 Line

SEFS (Severely Errored Frame Second count - Section)

B2 CV-L (Coding Violation count - Line),

CV-LFE (Coding Violation count - Line Far End)

B2 ES-L (Errored Second count - Line),

ES-LFE (Errored Second count - Line Far End)

B2 SES-L (Severely Errored Second count - Line),

SES-LFE (Severely Errored Second count - Line Far End)

B2 UAS-L (Unavailable Second Count - Line),

UAS-LFE (Unavailable Second Count - Line Far End)

FC-L (Failure Counts - Line),

FC-LFE (Failure Counts - Line Far End)

PJCDiff-P (Count of the absolute difference between generated and detected pointer justifications - Path)

PPJC-PGen (Positive Pointer Justification Counts Generated)

NPJC-PGen (Negative Pointer Justification Counts Detected)

PPJC-PDet (Positive Pointer Justification Counts Detected)

NPJC-PDet (Negative Pointer Justification Counts Detected)

365-372-300

Issue 8.0 September 2006

6 - 7 9

Performance Monitoring Parameters

Facility

Fast Ethernet

1GE

SAN (FC-DATA pack)

Operations, Administration, Maintenance, and Provisioning

Parameter definition

EDFE (Dropped Frames - Errors (Ethernet))

EDFC (Dropped Frames - Congestion (Ethernet))

EDFE (Dropped Frames - Errors (Ethernet))

EDFC (Dropped Frames - Congestion (Ethernet))

INTXWD (Invalid Transmission Word)

Performance Monitoring

Reports

TCA summary report

The DMX provides a report that lists the number of SONET, DS1, and

DS3 performance-monitoring parameters that have crossed their thresholds. This report provides a snapshot of the system performance level. If there is signal degradation, it is quickly pinpointed so that corrective action may be taken before customers are affected, thus supporting proactive maintenance. In R4.0 threshold-crossing alerts

(TCAs) are reported on the Ethernet parameters listed in the table above.

This report provides separate parameter summaries for each signal level in the system, including SONET section, line, and path and

Electrical line and path. The parameter summaries show the user which performance status to request if they want further information.

Ethernet performance monitoring

Performance Status Reports

These reports provide detailed information on the current and previous

8 hours in quarter-hour (15-minute) increments, as well as the current and previous day’s performance. Threshold crossing alerts are clearly identified and the time the performance registers were last initialized is also shown. Any registers that may have been affected by this initialization are marked. There are separate reports for section, line, and path parameters, as well as Ethernet parameters.

DMX provides PM capabilities for the 10/100/1000T, 1G SX, and 1G

LX, 1G ZX Ethernet interfaces, and all RPR interfaces. PM data is collected at each LAN and WAN interface in the network for both incoming and outgoing directions. The WAN interface provides a connection to a SONET Virtual Concatenation Group (VCG).

For details regarding Ethernet and RPR PM and SNMP capabilities, please refer to Appendix B of this document.

6 - 8 0

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Performance Monitoring Data Storage

Quarter-hour and current day registers

Access/Initialization

For each parameter supported, DMX provides one current 15-minute, one current day, one previous 15-minute, one previous day, and 32 recent 15-minute accumulation and storage registers.

The DMX system can initialize these registers through the TL1 interfaces at any time, as well as retrieve and report their contents.

Beginning in R6.0, the registers are no longer initialized by a shelf restart (unless caused by a power failure).

365-372-300

Issue 8.0 September 2006

6 - 8 1

Operations, Administration, Maintenance, and Provisioning

Performance Parameter Thresholds

Provisioning

The current quarter-hour and current day thresholds for each parameter type are provisionable, on a per-shelf basis (PSD-L, FC-L, and FC-P do not have thresholds). If values other than the defaults are used, only one value for each parameter type needs to be set.

The FC-DATA packs (LNW73 and LNW73C SAN interfaces) and the

RPR Ethernet pack (LNW78) provide a different set of parameters. For more information on the parameters supported by these packs, please refer to Appendix B of this document.

Threshold crossing alerts

(TCAs)

Whenever the current quarter-hour or the current day threshold for a given parameter is exceeded, DMX generates a threshold-crossing alert

(TCA) that is entered into the performance monitoring exception report and reported to the OS through the TL1 interface.

6 - 8 2

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

TCA Transmission to OS

Overview

The TCA information can be reported to the OS using any of the TL1

OS interfaces. TCAs can be used to trigger proactive maintenance activity.

TL1 access

The TL1 over TCP/IP OS interfaces should be used to derive full benefit from DMX’s performance monitoring capabilities. The full set of PM data stored by DMX (TCAs and the contents of PM registers) is provided through any of the TL1 interfaces.

365-372-300

Issue 8.0 September 2006

6 - 8 3

Operations, Administration, Maintenance, and Provisioning

SNMP Parameters and Traps

Support of Simple Network

Management Protocol

DMX makes use of Simple Network Management Protocol (SNMP).

SNMP is the most common protocol used by data network management applications to query a management agent using a supported Management Information Base (MIB). SNMP operates at the

OSI Application layer. The IP-based SNMP is the basis of most network management software, to the extent that today the phrase

“managed device” implies SNMP compliance.

Parameters Supported

For detailed information on SNMP parameters, traps and MIBs supported by DMX, please refer to Appendix B of this document.

6 - 8 4

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Provisioning

Overview

Purpose

This section describes the many types of provisionable parameters available in DMX.

General

DMX allows the user to customize many system characteristics through provisioning features. Provisioning parameters are set by software controls.

Contents

The provisionable parameters described in this section include:

Default Provisioning

Remote Provisioning

Cross-Connect Provisioning

Automatic Provisioning on Circuit Pack Replacement

Port State Provisioning

Channel State Provisioning

Line State Provisioning

365-372-300

Issue 8.0 September 2006

6 - 8 5

Operations, Administration, Maintenance, and Provisioning

Default Provisioning

Default values

Installation provisioning is minimized with thoughtfully chosen default values set in the factory. Every parameter has a factory default value.

These factory defaults for software parameters are maintained in the

SYSCTL circuit pack, and a single command is provided to restore all default values. The original values assigned at the factory cannot be changed. However, the current values can be overridden through local or remote provisioning.All provisioning data is stored in nonvolatile memory to prevent data loss during power failures and maintenance operations.

A parameter is a characteristic of the system that affects its operation.

The parameter value may be a number, text string, or other menu selection.

6 - 8 6

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Remote Provisioning

Overview

Software control allows remote provisioning of DMX NEs. This feature is provided especially for provisioning parameters likely to change in service, in support of centralized operations practices.

365-372-300

Issue 8.0 September 2006

6 - 8 7

Operations, Administration, Maintenance, and Provisioning

Cross-Connect Provisioning

Overview

The DMX can be provisioned for signal routing. Depending on the application, VT1.5, STS-1, STS-3(c), STS-12(c), or STS-48(c) signal cross-connections may be established to route traffic in a specific manner. Cross-connections may be bidirectional or unidirectional.

Beginning in R6.0 and going forward, DMX employs atomic crossconnections for all cross-connect provisioning. Atomic crossconnections are one-way cross-connections between logical ring channels which can be set up and taken down by a single command, and which cannot be broken down into smaller parts. Logical ring channels are the tributaries of a port or port protection group used for transmission in the absence of any line or equipment protection.

Atomic cross-connections are more flexible than the cross-connect provisioning structure employed previously. They allow for the support of more detailed applications because you are able to provision each portion of a cross-connection.

Typical cross-connections

Any VT1.5 or STS-n signal may be provisioned for the following signal routes:

• Main to Main

• Main to Function Unit.

• Hairpin (Function Unit to Function Unit).

DMX supports unidirectional cross-connections.

STS-1 cross-connections to Ethernet interfaces are also available. The

1WAY and 1WAYPR cross-connection is used for UPSR point-to-point

Ethernet applications. A 1WAY UNSWITCHED cross-connect is used for multipoint Ethernet applications.

The unidirectional pass-through cross-connect is used to pass VT1.5 or

STS-n signals through the NE all on the same timeslot. For passthrough cross-connects, the channel state default is NMON rather than

AUTO as with other cross-connects.

For more info

For more information on cross-connections, refer to Chapter 5,

“System Planning and Engineering.”

6 - 8 8

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Automatic Provisioning on Circuit Pack Replacement

Overview

Replacement of a failed circuit pack is simplified by automatic provisioning of the original circuit pack values. The SYSCTL circuit pack maintains a provisioning map of the entire shelf. Prior to R6.0, when a transmission pack was replaced, the SYSCTL (LNW1) circuit pack automatically downloaded the correct values to the new circuit pack. Likewise, when the LNW1 circuit pack was replaced, the correct provisioning data from every other circuit pack in the shelf was automatically uploaded to the new SYSCTL circuit pack's nonvolatile memory.

Beginning in R6.0, the provisioning map for the entire shelf is stored redundantly within the SYSCTL (LNW2). Therefore is does not need to be uploaded from other packs. In order to replace the LNW2, the user removes the NVM from the old LNW2 and places it in the new

LNW2. Alternatively, the user may backup the database, install a factory-fresh LNW2 (with new NVM cards), enter maintenance mode, download the generic, and restore the database.

Auto provisioning

Auto provisioning is the ability of an NE to detect the presence of equipment, validate it, and then assign default original values or preprovisioned parameter values to new equipment. Nonvolatile memory

(NVM) and/or hardware registers maintain the parameter values. If you have predefined or pre-provisioned some or all of the parameters, the auto provisioning function validates the request and assigns the preprovisioned values or default values as required. Auto-provisioning allows an NE to be set up initially with minimal user intervention.

Auto-provisioning also supports a self inventory function which allows operations center personnel to learn about and track activities at a remotely located NE.

365-372-300

Issue 8.0 September 2006

6 - 8 9

Automatic Provisioning on Circuit Pack

Replacement

Operations, Administration, Maintenance, and Provisioning

Automatic provisioning on circuit pack replacement

Beginning in R6.0, the provisioning map for the entire shelf is stored redundantly within the SYSCTL (LNW2). Therefore is doesn’t need to be uploaded from other packs. In order to replace the LNW2, the user removes the NVM from the old LNW2 and places it in the new LNW2.

Alternatively, the user may backup the database, install a factory-fresh

LNW2 (with new NVM cards), enter maintenance mode, download the generic, and restore the database.

Items auto provisioned

Some items that are auto-provisioned include the following:

• System target identifier (TID) (which can be changed at initial start-up)

• Default threshold-crossing alert (TCA) profiles

• Circuit packs

• Synchronization default mode

Equipment removal

The NE detects and reports the removal of equipment. The removal of equipment does not cause the NE to delete any entities. Removal of a piece of equipment may result in equipment alarms and insertion of maintenance signals when the state related data is updated. However, removal of equipment does not necessarily mean that the provisioning of the shelf slot has changed. The user must execute specific commands to remove an entity from the system database.

6 - 9 0

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Port State Provisioning

Overview

Port state provisioning is a feature provided on DMX NEs that can help suppress alarm reporting and performance monitoring by supporting multiple states for DS1, DS3, E1, EC-1, and Ethernet LAN ports.

The states supported are as follows:

• automatic (OOS-MA-AS)

• in-service (IS)

• not monitored (OOS).

Ethernet states supported are as follows:

• automatic (AUTO)

• in-service (IS)

• not monitored (NMON).

Port states

Ports without signals (undriven) are in the automatic state until changed to the in-service state. Ports are changed to the in-service state when a signal is present or they can be provisioned as in-service by the user. Commands allow a user to retrieve and change the state of a port to the not-monitored state or from the not-monitored state to the automatic state.

365-372-300

Issue 8.0 September 2006

6 - 9 1

Operations, Administration, Maintenance, and Provisioning

Channel State Provisioning

Overview

Automatic channel state provisioning is a capability provided on DMX

NEs that suppresses reporting of transient alarms and events during provisioning by supporting multiple states (see previous section) for

VT1.5, VC-12, STS-1, STS-3(c), STS-12(c), STS-48(c) channels.

Automatic channel state provisioning

While an end-to-end circuit is being set up, particularly during VT1.5/

VC-12 and STS-n cross-connect provisioning, several transient maintenance signals result. Without automatic channel state provisioning, these are reported as alarms and events. The technicians are expected to ignore these transient alarms and initiate corrective action only if the alarms persist after the provisioning is completed. To avoid the confusion created by this, DMX provides automatic channel state provisioning.

Channel states

A VT1.5 or STS-n channel is kept in the default automatic (OOS-MA-

AS) state until the reception of a valid signal (for STS channel states, a valid signal is one free of LOP-P, AIS-P, UNEQ-P, and SF-- for VT channel states, a valid signal is one free of LOP-V, AIS-V, and UNEQ-

V.) in that channel. While in OOS-MA-AS state, no alarms or events are reported on the channel. On receiving a valid signal, which occurs when the end-to-end circuit is completely provisioned, the channel automatically changes to the in-service (IS) state, where it resumes normal alarm and event reporting. An additional state, not-monitored

(OOS), is also supported in which alarm and event reporting is suppressed regardless of the validity of the signal being received on the channel. Like the port state provisioning capabilities already provided for physical ports like DS1, DS3, and EC-1, the user can submit commands to manually change a channel from IS or OOS-MA-AS to

OOS, and from OOS to OOS-MA-AS. A user cannot manually change from OOS-MA-AS or OOS to IS.

Note that for pass-through cross-connects, the channel state transitions from OOS-MA-AS to OOS upon receiving a good signal. This is different than what happens on dropped tribs. On dropped tribs, the channel state automatically transitions from OOS-MA-AS to IS upon receiving a good signal.

6 - 9 2

365-372-300

Issue 8.0 September 2006

Channel State Provisioning

Operations, Administration, Maintenance, and Provisioning

Note on LOP-P

LOP-P is reported regardless of channel state. STS LOP (LOP-P) is reported on any cross-connected tributary, even when the STS channel state is OOS-MA-AS or OOS. For BLSR, LOP-P is also reported on all working and protection tribs, independent on whether or not there is a cross-connect.

365-372-300

Issue 8.0 September 2006

6 - 9 3

Operations, Administration, Maintenance, and Provisioning

Line State Provisioning

Overview

The state of the low-speed OC-3/12/48 and the high-speed OC-12/48/

192 ports can be set manually to OOS. On OLIUs with multiple ports, the line state default is OOS-MA-AS. In R7.0, it also becomes possible to manually provision any equipped line to IS (in-service)

Refer to the previous section of this chapter entitled Port State

Provisioning (6-91) for more information about the AUTO line state.

6 - 9 4

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Reports

Overview

Purpose

This section describes reports generated by DMX.

Contents

Reports described in this section include:

Alarm and Status Reports

Performance Monitoring Reports

Maintenance History Reports

State Reports

Provisioning Reports

Version/Equipment List

365-372-300

Issue 8.0 September 2006

6 - 9 5

Operations, Administration, Maintenance, and Provisioning

Alarm and Status Reports

Overview

The system provides alarm reports that list the active alarm and status conditions, including a remote alarm/status feature that summarizes alarms in other NEs in an alarm group. A description of the condition

(for example, controller failure, incoming high-speed signal failure, synchronization hardware or reference failure, etc.) is included in the reports along with a time stamp indicating when the condition was detected, its severity, and whether it is service affecting or not. The option to display specified subsets of alarm conditions is provided (for example, critical alarms only).

Circuit Pack Status conditions

Circuit pack status conditions include:

• Manually initiated abnormal conditions (for example, forced switch, manual lockouts, loopbacks, system testing)

• Incoming AIS detected

• ACO active.

A description of the status condition (for example, DS1 loopback active, DS3 facility loopback active, etc.) is included in the report along with a time stamp indicating when the condition began.

DMX began support of Alarm Severity Assignment Profiles (ASAPs) in R6.0. With ASAPs, any alarm supported for a particular circuit pack/ interface can now be a status condition as well.

6 - 9 6

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Performance Monitoring Reports

TCA summary report

DMX provides a report that lists the number of SONET performancemonitoring parameters that have crossed their thresholds. This report provides a snapshot of the system performance level. If there is signal degradation, it is quickly pinpointed so that corrective action may be taken before customers are affected, thus supporting proactive maintenance.

This report provides separate parameter summaries for each signal level in the system, including SONET section, line, and path, as well as dropped/incoming/outgoing Ethernet bytes and frames. The parameter summaries show the user which performance status to request if they want further information.

Performance status reports

These reports provide detailed information on the current and previous

365-372-300

Issue 8.0 September 2006

6 - 9 7

Operations, Administration, Maintenance, and Provisioning

Maintenance History Reports

Overview

A maintenance history report contains the following past conditions:

• alarms

• status

• protection switching

• user interface commands (e.g., provisioning, loopback request, manual protection, etc.)

Summary

The maintenance history report contains time stamps indicating when each condition was detected and when it cleared, as well as when the command was entered. Note that beginning in R6.0, any system controller (SYSCTL) reset no longer clears all records in the log. The

LNW2 contains removable NVM memory cards that store these logs.

Reference

See the DMX Access Multiplexer User Operations Guide, 365-372-

301, for details on the history log.

6 - 9 8

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

State Reports

Overview

The state report shows the protection state of all circuit packs installed in the system and the state of the individual low/high-speed channels.

Circuit pack states

The circuit pack state is reported as “active” or “standby.”

Path states

The state of the individual VT1.5/VC-12 /STS-n channels and paths may be one of the following:

• not monitored (NMON)

• in service (IS)

• auto (AUTO).

The system reports this information on all interfaces. For VT1.5/VC-

12/STS-n channels and paths, the AUTO state would transition to the

IS state if a good signal is detected.

Port states

The state of individual ports, including those contained in multiport circuit packs (DS1/E1, DS3/EC-1, Ethernet interface packs, quad

OC-3, dual and quad OC-12, or OC-48), may be NMON, IS, or AUTO.

Line states

The state of individual lines may be IS, NMON, or AUTO for all OC-n ports.

365-372-300

Issue 8.0 September 2006

6 - 9 9

Operations, Administration, Maintenance, and Provisioning

Provisioning Reports

Overview

The DMX provides a variety of provisioning reports that contain the current values of all electronically-provisionable parameters. For more information on the provisioning reports generated, refer to the DMX

Access Multiplexer User Operations Guide, 365-372-301.

6 - 1 0 0

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Version/Equipment List

Overview

The DMX system provides a full inventory report on all hardware and software currently installed.

Information provided

The version/equipment list provides the following information relative to circuit packs:

• Circuit pack name

• 10-character CLEI code

• 6-digit equipment catalog item (ECI)

• 10-character apparatus code

• 6-character series number

• 12-character serial number (includes date and location of manufacture)

• Program version (software generic) code

• Program versions in dormant area.

The version/equipment list provides the following information relative to pluggable transmission modules (PTMs):

• Comcode

• CLEI code

• Date of manufacture

• 10-character apparatus code

• 6-character series number

• 12-character serial number (includes date and location of manufacture)

• Manufacturer identifier

• Module name

• Module product ID

• Reach (i.e. short, intermediate, long)

365-372-300

Issue 8.0 September 2006

6 - 1 0 1

Operations, Administration, Maintenance, and Provisioning

Administration

Overview

Purpose

This section provides information on system administration.

Contents

System administration considerations included in this section are:

Software Upgrades

IP Access for network management

Time and Date Synchronization

Office Alarms Interface

Password Administration (CIT and System)

User-setable Miscellaneous Discrete Interface

6 - 1 0 2

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Software Upgrades

Overview

DMX provides an in-service software installation capability to update the generic program in local and remote systems. Upgrades are distributed on CD-ROMs containing the new software and an installation program. These software upgrades are the primary mechanism to add new feature enhancements to the in-service DMX network.

Beginning in R6.0, DMX employs provisionable alarm severity profiles known as ASAPs. Therefore, previous alarm severity level provisioning is lost when upgrading to R6.0. Also, because R6.0 introduces atomic cross-connections, any existing 2WAY, 2WAYPR, and MLTPT cross-connects will be automatically replaced with equivalent 1WAY, 1WAYPR, and UNSWITCHED cross-connects.

Prior to R6.0, all in-service software upgrades did not affect any provisionable parameters. For example, cross-connections were left unchanged by the software upgrade.

Software download

In the DMX system, software download takes place in two stages. In the first stage, the new generic software is downloaded into a dormant

“flash” area as a compressed file. In the second stage, the new generic is uncompressed and moved into an active “flash” space. During this process, the old release continues to run from random access memory

(RAM). Installation is not service-affecting, so down time is limited to the reboot time.

Local installation procedure

The procedure is straightforward. The technician connects a personal computer (PC) to the IAOLAN port on the local DMX, starts the installation program, and is prompted with a few warnings before the upgrade installation actually begins. After the technician confirms to proceed, the PC takes over the process and completes the installation.

Installation may also be performed via Lucent’s Navis OMS or PC-CIT over the IAO LAN interface using FTP or FTAM. For more information on software download and upgrade via Navis OMS, refer to the Subnetwork Management System (SNMS) User Guide, 190-224-

100.

365-372-300

Issue 8.0 September 2006

6 - 1 0 3

Operations, Administration, Maintenance, and Provisioning

IP Access for network management

Overview

For network management purposes, the DMX supports the following types of IP Access:

• DMX can serve as a TL1 Translation Device (T-TD) by acting as a gateway network element that allows Navis

Optical EMS and/or

WaveStar

CIT to communicate to other network elements (NEs) through an IP access network. This capability allows you to send

TL1 commands from Navis

Optical EMS or WaveStar

CIT located on a TCP/IP based network to various NEs connected on an OSI network.

• DMX can functionally encapsulate IP packets within OSI packets to be transmitted through the OSI network to the proper NE. Thus

DMX supports IP based protocols such as FTP by providing endto-end IP connectivity between OS and NE. This capability is called IP tunneling. IP tunneling is required to support remote database backup/restore in between DMX systems.

• DMX can also serve as a File Transfer Translation Device (FTTD) by acting as an FTAM-FTP gateway network element. The

FTAM-FTP gateway network element translates FTAM over OSI presentation to FTP over TCP/IP. The FTAM-FTP gateway supports software downloads, database backups, and database restores.

• DMX also supports Simple Network Management Protocol

(SNMP). DMX provides limited support for certain reports and traps (alarms and events autonomous messages).

• DMX also supports Network Time Protocol (NTP) using IP tunneling to synchronize the time and date to a standard time reference.

6 - 1 0 4

365-372-300

Issue 8.0 September 2006

IP Access for network management

Operations, Administration, Maintenance, and Provisioning

TL1 Translation

The DMX can copy the application information within an IP packet into an OSI packet. This translation is performed at the application layer. When acting as a TL1 translation device, the DMX system must be provisioned with a list of possible OSs. If an OS is not on the list residing within the system, a connection from that OS will not be accepted. When the DMX is used as a TL1 translation device it is referred to as the T-TD GNE (Gateway Network Element). The T-TD

GNE provides the same functionality as the NCC TL1 TCP/IP gateway.

Figure 6-19 TL1 Translation Device

WaveStar

CIT

Navis

Optical

EMS

TCP/IP

TL1

TCP/IP

TL1

TCP/IP

WAN

OSI

DMX

TCP/IP

TL1

T-TD GNE

IP to OSI

Translation

OSI

DMX or

Compatible

OSI

OC-48/OC-192

BLSR or

UPSR

DMX or

Compatible

DMX or

Compatible

OSI nc-dmx-097

365-372-300

Issue 8.0 September 2006

6 - 1 0 5

IP Access for network management

Operations, Administration, Maintenance, and Provisioning

IP Tunneling

Today, Telecom networks mix a wide range of heterogeneous protocols and applications.

The Lucent IP tunneling solution consists in encapsulating IP packets inside CLNP (ISO 8473 ConnectionLess Network Protocol) PDU, in order to be able to use an existing OSI-based embedded Data

Communications Network (DCN) for IP traffic.

With the IP tunneling over CLNP solution, the DMX NE can support the following two customer applications: IP access and IP fringe.

An IP access application is shown in Figure 1, where an IP based OS

(for example, SNMP manager) located in the IP access DCN manages a remote DMX NE located in the OSI-based embedded DCN. The IP application initiated at the OS terminates at the remote NE.

Figure 6-20 IP Tunneling

Navis

Optical

EMS

FTP/IP

WaveStar

CIT

FTP/IP

TCP/IP

WAN

OSI

FTP/IP

DMX

Tunneling

GNE

OSI

DMX or

Compatible

OC-48/OC-192

BLSR or UPSR

DMX or

Compatible

OSI

DMX or

Compatible

OSI

- FTP through IP Tunnel

GNE - GateWay Network Element nc-dmx-098

An IP fringe application, where an IP based OS located in the IP access

DCN manages an IP managed NE (non DMX) on the fringe of DMX

OSI-based embedded DCN. The IP application initiated at the OS

6 - 1 0 6

365-372-300

Issue 8.0 September 2006

IP Access for network management

Operations, Administration, Maintenance, and Provisioning

terminates at the IP managed NE. Note that if the IP managed NE is not directly connected to the DMX remote NE via the

LAN, but can be reached via additional routers, some static routes have to be provisioned manually on the routers.

Encapsulating IP Packets

The DMX GNE acts as the tunnel entrance, i.e., the interface between

IP and CLNP. When an IP packet is received from the LAN interface of the GNE, if it is not destined for the GNE, the received IP packet is encapsulated into CLNP PDU(s) as simple CLNP user data, loosing any IP protocol meanings (such as IP addressing and life time), as shown in the figure below.

Figure 6-21 Encapsulated IP Packets

IP Packet

IP Header User Data

Encapsulated

CLNP Header IP Header User Data

Encapsulated and

(if necessary)

Segmented

CLNP Header IP Header

User Data

CLNP Header IP Header

User Data

For the CLNP PDU that contains the encapsulated IP packet, the CLNP source address is the NSAP of the NE where the IP packet is encapsulated (tunnel entrance), and the CLNP destination address is the

NSAP of the NE where the IP packet will be de-capsulated (tunnel exit). The CLNP PDU then is routed via the ISO-10589 “IS to IS intradomain information exchange protocol (IS-IS)” within the embedded

OSI DCN. Therefore, the IP tunneling over CLNP is transparent for the

IP world. The CLNP world is only used to carry the IP traffic and there is no possible connections between the OSI applications and the IP applications. The IP tunnel serves as a normal point-to-point link for the IP traffic between two NSAP entities (the tunnel entrance and tunnel exit). Note that because the IP traffic flows in both directions between two NSAP entities, the tunnel entrance entity also serves as the tunnel exit entity, and vice versa.

In the tunnel entrance, the way to associate an IP destination address in the IP packet with an OSI NSAP address (the NSAP of tunnel exit entity) can be derived by the static user provisioned information or by the automatic distributed tunnel routing information, called Tunnel

Auto Provisioning (TAP).

365-372-300

Issue 8.0 September 2006

6 - 1 0 7

IP Access for network management

Operations, Administration, Maintenance, and Provisioning

Tunnel Auto Provisioning (TAP)

In the OSI networks, the network elements use the ISO-10589 “IS to IS intra-domain information exchange protocol (IS-IS)” to exchange the topology information. The knowledge by every network element of the whole network topology at a given time allows the computation of the optimal route to any possible destination on the network. The IS-IS protocol provides for the inclusion of optional variable length fields in all IS-IS packets. This allows additional IP specific information to be added to the OSI IS-IS routing packets.

The topological information between network elements (or called intermediate systems) is communicated by sending a specific IS-IS

PDU called LSP (Link-State PDU). In the LSP optional fields, the NEs send (advertise) information about the IP subnets that can be reached via that NE. By default, this will be locally attached subnet, but other subnets can also be provisioned for the advertisement.

The advertising of IP information using the LSP options can be enabled or disabled via the user interfaces. Based on the specification of the IS-

IS protocol, any intermediate systems that could not recognize the encoded optional fields shall just ignore and pass through these fields unchanged. This makes it possible that the NEs that advertise both OSI and IP routing information can seamlessly interwork with the NEs that advertise the OSI routing information only.

With automatic distribution of IP routing information via IS-IS LSP, a

NE, which learned such information, then can associate an IP destination address of an IP packet with an OSI NSAP address, and uses this NSAP address as the destination address of CLNP PDU(s) which encapsulates the IP packet.

6 - 1 0 8

365-372-300

Issue 8.0 September 2006

IP Access for network management

Operations, Administration, Maintenance, and Provisioning

FTAM-FTP gateway network element

DMX can serve as a File Transfer Translation Device (FTTD) by acting as an FTAM-FTP gateway network element. The FTAM-FTP gateway network element translates FTAM over OSI presentation to FTP over

TCP/IP. The FTAM-FTP gateway supports software downloads, database backups, and database restores.

The figure below shows a DMX provisioned as an FTAM-FTP gateway network element. The FTAM-FTP gateway network element allows remote DMX network elements to request software downloads and database restores from an FTP server. The FTAM-FTP gateway network element also allows remote DMX network elements to backup databases to an FTP server.

Figure 6-22 FTAM-FTP Gateway

FTP

Server

TCP/IP

WAN

TCP/IP

DMX

FTAM-FTP

GateWay

OSI OSI

DMX or

Compatible

OC-48/OC-192

BLSR or

UPSR

DMX or

Compatible

OSI

DMX or

Compatible

DMX = Metropolis DMX Access Multiplexer

OSI nc-dmx-243

365-372-300

Issue 8.0 September 2006

6 - 1 0 9

IP Access for network management

Operations, Administration, Maintenance, and Provisioning

IP over DCC

The sections above described how DMX can act as a GNE providing

FTTD and TTD functionality. If there is no DMX in a particular office where GNE can connect, via IAO LAN interface, to the IP WAN, these options can prove ineffective. For this reason R5.1 incorporates IP communications over the DCC channel. This feature allows operations communications to flow through another device (like Ciena Core

Director) to the DMX GNE via an IP over DCC link. This feature also enables interworking with Ciena Core Director (CD).

Management Traffic Flow (OMS to DMX)

OMS originates IP packets destined to DMX GNE, and uses Router R1 as the Default Router. Router R1 routes the packets via IP access DCN to Router R2. Router R2 forwards the packets to CD via Proxy ARP supported by CD. Based on the static routing, CD forwards the IP packets to DMX GNE via IP over DCC link. DMX GNE translates IP messages to OSI messages and routes CLNP packets to the remote NE

(RNE) via OSI embedded DCN.

Management Traffic Flow (DMX to OMS)

DMX RNE originates CLNP packets destined to DMX GNE, and routes CLNP packets to DMX GNE via OSI embedded DCN. The

DMX GNE translates OSI messages to IP messages, and originates IP packets destined to OMS. Based on static routing, the DMX GNE uses the IP over DCC link to forward the IP packets to the CD. CD forwards the IP packets to Router R2 via default routing provisioned by user.

Router R2 routes the IP packets via IP access DCN to Router

R1.Router R1 forwards the IP packets to OMS.

The figure below depicts the functionality of IP over DCC.

Figure 6-23 Operations Communication via IP over DCC

Telcordia

OMS

Router 1

TCP/IP

WAN

Router 2

DMX

RNE

OSI

Ciena

Core

Director

IP over DCC

DMX

GNE

OC-12/48/192

BLSR or UPSR

OSI

GNE - GateWay Network Element

RNE - Remote Network Element

DMX = Metropolis DMX Access Multiplexer

DMX

RNE

OSI

DMX

RNE

OSI

6 - 1 1 0

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Time and Date Synchronization

Overview

Synchronizing the time and date among all NEs in a network is useful to correlate events reported by different NEs.

The time and date is synchronized:

• Manually using the WaveStar

CIT

Administration > Set Date and

Time

command.

• Automatically from another NE via the DCC.

• Automatically by the OS

Provisioning

In a new installation, it is recommended that the time and date be manually provisioned in at least the first DMX in each ring. Each subsequent DMX that is added to the network tries to learn the current time and date from one of the existing NEs automatically.

After start-up (or any subsequent controller resets), the DMX's time and date revert back to the last time and date before the reset. DMX waits 5 minutes, in case other NEs are also resetting (for example, as part of a software upgrade of the network), before starting to check with other NEs for the current time and date. If necessary, the DMX checks with all remote NEs for the current time and date.

The DMXs allow up to 2 minutes for each remote NE to respond before checking with the next remote NE for the current time and date, and keep checking until a valid current time and date is found.

The DMX accepts a provisioned time and date value or any remote NE date later than

00-01-01

as a valid current time and date.

Network Time Protocol

Network Time Protocol (NTP) assures accurate synchronization of the

DMX with reference to radio and/or atomic clocks located on the

Internet.

Considerations

The automatic time and date synchronization is intended to achieve time and date synchronization among compatible NEs with DCC connectivity in a network, but such synchronization can not be guaranteed at start-up for all network configurations or over the course of time.

365-372-300

Issue 8.0 September 2006

6 - 1 1 1

Time and Date Synchronization

Operations, Administration, Maintenance, and Provisioning

TL1 command responses and autonomous messages include DMX’s current time and date. As an alternative to manually provisioning and confirming the current time and date in each DMX in a network,

Navis™ Optical Element Management System, (formerly SNMS), automatically checks the current date and time, periodically or ondemand.

Time and date synchronization compatibility

The following table lists DMX Time and Date Synchronization compatibility with other products.

Table 6-10 DMX Time and Date Synchronization Compatibility

Products

DMX

Metropolis

DMX

Metropolis

DMXplore

Metropolis

DMXpress

Metropolis

DMXtend

DDM-2000 OC-3

DDM-2000 OC-12

FiberReach

FT-2000 ADR

DMX

yes yes yes yes yes yes yes yes yes

6 - 1 1 2

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Office Alarms Interface

Description

The office alarms interface is a set of discrete relays controlling audible and visible office alarms. Relays are provided for the following types of alarm conditions:

• CR (critical)

• MJ (major)

• MN (minor)

If desired, critical and major alarm outputs can be wired so that either, neither, or both of the outputs control the major office alarm.

Steady state current

The steady state current for office alarm connections must not exceed

1.0 Amp at 60 Volts or 1.8 Amps at 30 Volts. The maximum transient currents (20 msec duration) during initial contact closure must not exceed 9 Amps at 60 Volts or 18 Amps at 30 Volts.

Provisionable alarm delay and alarm clear delay

DMX provides provisionable incoming signal alarm delay and alarm clear delay. The office alarms are not activated unless an incoming signal condition of greater duration than the alarm delay occurs. When a failure clears, a provisionable alarm clear delay prevents premature clearing of the alarm.

365-372-300

Issue 8.0 September 2006

6 - 1 1 3

Office Alarms Interface

Operations, Administration, Maintenance, and Provisioning

Multiple alarms

When multiple alarm conditions occur, the highest-level office alarm

(audible and visible) is activated. When the highest-level alarm condition clears, the office alarm “bumps down” to the next highest level alarm condition.

If enabled, the Remote NE Status feature includes alarms at other NEs in the same alarm group as the local NE to determine when to activate the local office alarm and the appropriate alarm level.

Alarm cut-off

The audible office alarms are silenced through activation of the alarm cut-off (ACO) function. Visible alarms are not extinguished by the

ACO function.

If the ACO function has been activated to silence the active audible alarm and a “bump down” occurs, the audible alarm remains silent (that is, the lower level visible alarm is activated, but the corresponding audible alarm is not reactivated). If another alarming condition occurs while the ACO is active, the highest level audible alarm is activated even if the new condition is a lower level. For example, if a major (MJ) alarm was active and silenced using the ACO function and a minor

(MN) alarming condition occurs, the MJ audible alarm will sound.

6 - 1 1 4

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Remote NE Status

Overview

If enabled, the Remote NE Status feature reflects the summary alarm/ status level for both the local and remote NEs in the same alarm group as the local NE with the following local indications.

Office alarms

The local office visual alarm always shows the highest alarm level. The local office audible alarm is activated in response to each new alarm occurrence among the local and remote NEs. Thus alerting on-site craft of problems in the network with an indication of the severity.

SYSCTL faceplate LEDs

The CR, MJ, or MN LED on the local SYSCTL circuit pack faceplate shows the highest alarm level among the local and remote NEs. The FE

LED on the local SYSCTL circuit pack faceplate is illuminated if any remote NE has an active alarm, abnormal status (indicated by the ABN

LED), or “activity” status condition, thus identifying the local NE to query further. (Although not dependent on the Remote NE Status feature, the Near-End LED on the local SYSCTL circuit pack faceplate is only illuminated if the local NE itself has an active alarm, abnormal status, or “activity” status condition.)

Remote NE status and alarm/status retrieval

The local NE can retrieve the highest alarm/status level of each NE in a network with an active alarm, abnormal status, or “activity” status condition, thus identifying the remote NE to further query.

Determination of the highest alarm/status level of each NE includes the alarm/status level of active miscellaneous discrete alarm/status inputs.

The Remote NE Status feature can be used to expedite maintenance activities for NEs that report TL1 autonomous alarm/status messages to a maintenance OS at an operations center.

The Remote NE Status feature may be enabled or disabled. By default, the Remote NE Status feature is disabled.

Alarm group

By default, all DMX systems are assigned to alarm group 255. This is typically sufficient for small networks of up to 50 nodes. All NEs with

DCC connectivity that have the same alarm group number are members of the same alarm group. All alarm group members share summary alarm/status information with each other but not with NEs in different alarm groups. To take advantage of the remote activation of local office alarms, in particular, at least one member of the alarm group should be located in a central office.

365-372-300

Issue 8.0 September 2006

6 - 1 1 5

Remote NE Status

Operations, Administration, Maintenance, and Provisioning

In large networks, with IS-IS Level 2 Routing and multiple Level 1 areas, each alarm group must be confined to within a single Level 1 area only. For example, a network with three different Level 1 areas would require a minimum of three alarm groups, that is, one alarm group for each Level 1 area. If desired, multiple alarm groups can be defined within a Level 1 area, also. The maximum number of NEs in an alarm group is limited by the maximum number of nodes in a Level 1 area.

Alarm gateway NE (AGNE)

By default, no NE is enabled as an AGNE. Even if the default alarm group number for all NEs is used, at least one NE in each alarm group must be enabled as an AGNE. Any NE in an alarm group can be enabled as an AGNE, for example, an AGNE does not need to be located in a central office, in fact, it is recommended that an AGNE should not also be a TL1 TCP/IP GNE or IS-IS Level 2 Router.

A second NE in each alarm group may be enabled as a backup AGNE, if required. It is recommended that the maximum number of AGNEs per alarm group be limited to at most two to assure good performance.

Instead of having every NE exchange alarm/status information with every other NE in the same alarm group directly, only the AGNE receives alarm/status information from every NE directly, and the

AGNE distributes the accumulated alarm/status information for all the

NEs to every NE in the alarm group.

Provisioning sequence

If there is no AGNE, each NE in an alarm group reports an

AGNE

Communications Failure

alarm; therefore, the following provisioning sequence is recommended:

Provision one or two (at most) NEs as the AGNE

• Enable the Remote NE Status parameter

• Enable the network element as an Alarm Gateway

• Provision the alarm group number, if different than the default.

Provision the other NEs in the same alarm group

• Enable the Remote NE Status parameter

• Provision the alarm group number, if different than the default.

For more information about the

Administration>Set NE

command, refer to the WaveStar

CIT help.

6 - 1 1 6

365-372-300

Issue 8.0 September 2006

Remote NE Status

Operations, Administration, Maintenance, and Provisioning

Remote NE status compatibility

The following table lists DMX remote NE status compatibility with other products.

Table 6-11 Remote NE Status Compatibility

DMX

Product

DMX

Metropolis

DMX

tend

Metropolis

DMXpress

Metropolis

DMXplore

DDM-2000 OC-3

DDM-2000 OC-12

FiberReach yes yes yes yes yes yes yes

365-372-300

Issue 8.0 September 2006

6 - 1 1 7

Operations, Administration, Maintenance, and Provisioning

Network Size

Overview

There is no inherent limit to the total number of NEs in a SONET transmission network, but there is a limit to the number of nodes that can be part of the same OSI domain, that is, with OSI LAN and/or DCC connectivity for operations communications among the NEs.

Maximum number of OSI nodes

In R6.0, the total number of OSI associations per TCP has been increased from 64 to 300 and the number of OSI associations for TL1 per Gateway Network Element (GNE) has been increased from 200 to

300. These changes make DMX able to support a total of 250 NEs per

Level 1 area.

Prior to R6.0, the maximum number of OSI nodes supported was 50, unless IS-IS Level 2 Routing was used, in which case, up to 256 OSI nodes were supported. Each DMX counts as one OSI node.

IS-IS level 2 routing

IS-IS Level 2 Routing involves the assignment of NEs to multiple areas of less than 50 nodes each. Level 2 routers support OSI communications between the NEs in different areas. Both the assignment of NEs to areas and the enabling of NEs as Level 2 routers is accomplished by provisioning.

6 - 1 1 8

365-372-300

Issue 8.0 September 2006

Operations, Administration, Maintenance, and Provisioning

Directory Services

What are directory services?

OS and WaveStar

CIT users access remote DMXs using the remote

DMX Target Identifier (TID, name) but remote DMXs are addressed on the DCC using

Network Service Access Point Address (

NSAP). Therefore, a method to provide TID-to-NSAP (name-to-address) and NSAP-to-

TID (address-to-name) translations is necessary. Target Identifier

Address Resolution Protocol (TARP) provides this capability.

For SONET NEs that support TCP/IP and TL1 OS interfaces, TARP is the de facto directory services standard to support multi-vendor OI compatibility. TARP is specified in Telcordia GR-253-CORE, SONET

Transport Systems: Common Criteria.

TID provisioning

Each NE in a network must be provisioned with a unique TID. The

DMX’s default TID is “LT-DMX”. The terms TID and source identifier

(SID) are generally used interchangeably.

Important!

Some other-vendor NEs may require that all TIDs adhere to specific rules, for example, that each TID start with an alphabetic character and/or that each TID consist of at least 6-to-7 characters.

To be compatible with WaveStar products, DMX TIDs should not include special characters “%” and “#”. Even though DMX TID provisioning allows those special characters, T1.245 SONET

Directory Services (SDS) does not support those special characters.

NSAP provisioning

By default, each DMX has a unique Network Service Access Point

(NSAP) address, thus no NSAP provisioning is necessary in small networks. If the network size exceeds 50 OSI nodes, NSAP provisioning is required.

TARP provisioning

Although TARP functions automatically without any user provisioning, using standard default values, DMX allows provisioning of the following TARP parameters. All TARP parameters are provisionable:

• Lifetime

• Manual Adjacency

• Timers

• Loop Detection Buffer (LDB) Flush Timer

365-372-300

Issue 8.0 September 2006

6 - 1 1 9

Directory Services

Operations, Administration, Maintenance, and Provisioning

TARP TID-to-NSAP translations

• TARP Data Cache (TDC) Enable/Disable

• TDC TID-NSAP Entries.

It is recommended that the TARP default values always be used.

The three operations that depend on TARP TID-to-NSAP translations are:

TL1 OS access

WaveStar

CIT access

Remote (Software) Install Program/Copy Program.

When a TL1 TCP/IP

Gateway Network Element (

GNE) receives a TL1 login request for a TL1-RNE, the TL1 login request includes the TL1-

RNE’s TID. The TL1-GNE relies on TARP to determine the TL1-

RNE’s NSAP. The TL1-GNE needs the NSAP to establish an OSI association with the TL1-RNE. The TL1 login request is forwarded to the TL1-RNE over that OSI association.

The local DMX serves as a TL1-GNE and uses TARP as described above for WaveStar

CIT access via DMX’s serial ports or TCP/IP.

When accessing DMX via OSI LAN, the WaveStar

CIT (or OS) performs the TL1-GNE function and uses TARP in a similar manner, also. The local DMX uses TARP as described above to support remote

Install Program/Copy Program.

TARP propagation

The first time a TL1-GNE (or local DMX) requires a TARP TID-to-

NSAP translation for each remote NE, the TL1-GNE originates a

TARP query. The TARP query is propagated to all NEs in the same OSI routing area, and if no response is received from within the area, up to two additional TARP queries are propagated throughout the OSI domain. Each NE forwards the TARP queries to each of its neighboring

OSI nodes (that is, adjacencies), except the neighbor from which the

TARP query was received.

When the TARP query reaches the remote NE with the requested TID, that remote NE responds to the originating NE with the remote NE’s

NSAP address. If there is no response to any of the TARP queries for a

TID, after the third query times out, an error response (for example,

TL1- GNE unknown TID

TID not found

) is returned to the originating NE.

TARP NSAP-to-TID translations

When a DMX is commanded to perform this translation, it knows the

NSAPs of the remote NEs to be included in the responses but relies on

TARP to determine the corresponding TIDs.

6 - 1 2 0

365-372-300

Issue 8.0 September 2006

Directory Services

Operations, Administration, Maintenance, and Provisioning

To ensure that the responses to these commands always include the most up-to-date network information, real-time TARP queries are originated instead of relying on the TARP Data Cache or TDC

(although the TDC is updated, as appropriate, based on the responses to these NSAP-to-TID queries).

Because the NSAPs are known, these TARP queries are addressed directly to each remote NE (TARP propagation is not necessary). Each remote NE responds to the originating NE with the remote NE’s TID.

TARP data cache

In order to reduce the frequency of TARP propagation, and to improve the performance of the affected operations, DMX supports a TDC option. By default, the TDC is enabled.

Each DMX maintains its own TDC, independently. The TDC consists of TID-NSAP translations. Each DMX automatically updates its own

TDC based on the responses to previous TARP queries. The TDC may also be updated upon receipt of an unsolicited, automatic notification from another NE in the same OSI domain of a TID or NSAP change.

DMX checks its TDC to see if it already has a required TID-to-NSAP translation before originating a TARP query. If a translation is not found in the TDC, the response to that TARP query is used to update the originating DMX’s TDC. DMX assures that its TDC maintains only one TID-NSAP translation for each unique TID. DMX supports TDC sizes of up to 110 TID-NSAP translations. If the TDC is disabled or

DMX’s system controller is reset, the contents of the TDC are deleted.

TDC accuracy

In the unlikely event that a TDC includes an inaccurate TID-to-NSAP translation, DMX confirms that both the NSAP and TID of the remote

DMX are correct before a remote operation proceeds. If there is a mismatch, an error response (for example,

TL1-RNE unknown TID

Inconsistent TID

, or

Association Setup Failure

) is returned to the originating

NE.

To correct such a situation, delete the subject TID (L4tdctid) from the

TDC, then re-request the remote operation for the subject TID. The subsequent TARP query results in an accurate TID-to-NSAP translation, and the TDC is updated accordingly. A broader solution is to disable and re-enable the TDC in which case all TDC entries are deleted.

365-372-300

Issue 8.0 September 2006

6 - 1 2 1

Operations, Administration, Maintenance, and Provisioning

Security

Capabilities

DMX provides security capabilities to protect against unauthorized access to the system.

User types

Five types of users (with tiered restriction levels) are allowed access to the system with a valid user ID and password:

• An Administrator user has access to all the security functional capabilities. Only the privileged and administrator users have access to the security and access functions. These functions include assigning/changing user ID/passwords for other users, setting target identifier (TID) names, resetting the system, and system initialization functions.

• Privileged users can execute all commands

A privileged user has access to all the system functional capabilities. Only the privileged and administrator users have access to the security and access functions. These functions include assigning/changing user ID/passwords for other users, setting target identifier (TID) names, resetting the system, and system initialization functions.

A privileged user can terminate the login session of other individual users (including other privileged users) or terminate all login sessions of non-privileged users.

• General users have access to all the system functional capabilities except security, access, system initialization and software installation functions.

• Maintenance users can only execute commands that access the system, extract reports and execute maintenance functions through a specific set of commands. No privileged commands may be executed by maintenance users.

• Reports-only users can only execute commands that retrieve reports from the system.

Security can be set to a “lockout” state, which blocks non-privileged users from logging in to the system.

System initialization

When the system is first initialized, three privileged default user IDs and passwords are provided. Up to 147 user IDs and passwords can be added, deleted, and/or changed by any of the privileged users. Timeouts are provisionable on a per-user basis.

6 - 1 2 2

365-372-300

Issue 8.0 September 2006

Security

Operations, Administration, Maintenance, and Provisioning

User IDs and passwords

The WaveStar

CIT always asks the user for the NE user ID and password with the first NE connection. The user ID and password can be saved for subsequent connections, but the user ID and password can not be saved past the current WaveStar

CIT session. User ID and password parameters must be administered on a per-NE basis. You may have a different user ID and/or password on one NE than you have on other NEs.

Each time the number of invalid sequential login attempts reach or exceed the provisionable user ID lockout threshold, the network element reports a Security Alert alarm.

Inactivity timeout period

The inactivity timeout period is the number of minutes after which a user with an inactive session is logged out. A provisionable inactivity timeout period is supported on a per-user basis.

Password aging

The password aging interval is the number of days allowed before a user’s password expires. When a user’s password expires, the user is prompted to select a new password prior to login. The values for the password aging interval are zero (0) or a range from 7 to 999 days. A value of zero (0) disables password aging. The default value is 0.

Password aging does not apply to privileged users’ passwords.

WaveStar

CIT default user

IDs and passwords

Two default Privileged user IDs and passwords are initially installed in the WaveStar

CIT are LUC01 and LUC02 (LUC-zero-one, and LUCzero-two). Their associated passwords are LUC+01, LUC+02, (LUCplus sign-zero-one, LUC-plus sign-zero-two), respectively.

NE default user IDs and passwords

Three default Privileged user IDs and passwords are initially installed in the NE is LUC01, LUC02, or LUC03 (LUC-zero-one, LUC-zerotwo, and LUC-zero-three). The default password is DMX2.5G.

MAC Address Locking

(R7.0)

DMX allows MAC locking on the LNW70. MAC locking prevents unauthorized users from gaining access to the network through an

365-372-300

Issue 8.0 September 2006

6 - 1 2 3

Operations, Administration, Maintenance, and Provisioning

Password Administration (CIT and System)

Overview

System administration includes performing the following:

• Changing passwords

• Changing notifications

• Performing security administration

• Viewing NE administration

• Setting TIDs

• Setting NE defaults

• Performing a LAN reset

• Provisioning data communications

• Viewing OSI routing map

WaveStar

CIT user ID/ password administration

The

Administration > Security > User Provisioning

command on the

WaveStar

CIT View menu allows a privileged user to create, change, or delete another user ID or password.

Important!

Any changes made to a user’s provisioning takes place the next time the user logs in. If the user is currently logged in, no changes take place until that user logs off and logs back in.

Valid WaveStar

CIT user IDs

A valid WaveStar

CIT user ID must be a minimum of one character to a maximum of ten characters (no character restrictions).

Valid WaveStar

CIT passwords

A valid WaveStar

CIT password must comply with the following:

• Length must be a minimum of six characters to a maximum of ten characters

• Must begin with a letter

• Must contain at least three non-alphabetic characters (symbol or number)

• At least one of the non-alphabetic characters must be a symbol

• When changing a password, the new password must be different from the previous password by at least three characters and cannot be one of the last 5 passwords used.

6 - 1 2 4

365-372-300

Issue 8.0 September 2006

Administration

Operations, Administration, Maintenance, and Provisioning

Important!

User passwords are case-sensitive.

Characters NOT allowed in a WaveStar

CIT password

The following table lists the characters that are not allowed in a

WaveStar

CIT password.

Table 6-12 Characters NOT Allowed in a WaveStar

CIT

Password

Character

Description Character

Space “

Commercial at &

Comma

Colon

;

Equals sign ?

Description

Quotation mark

Ampersand

Semicolon horizontal bar

(underscore)

Question mark

365-372-300

Issue 8.0 September 2006

6 - 1 2 5

Administration

Operations, Administration, Maintenance, and Provisioning

)

(

Characters allowed in a WaveStar

CIT password

The following table lists the characters that are allowed in a WaveStar

CIT password.

Table 6-13 Characters Allowed in a WaveStar

CIT Password

Character

A... Z a... z

0... 9

Description Character

Uppercase letters *

Lowercase letters [

Digits ]

Apostrophe

Hyphen

Left parenthesis {

Right parenthesis }

Period (full stop) |

Slash (Solidus) <

Plus sign

Exclamation mark

Percent sign #

Description

Asterisk

Left square bracket

Right square bracket

Caret

Grave accent

Left curly brace

Right curly brace

Vertical bar

Less than

Greater than

Tilde

Number sign

6 - 1 2 6

365-372-300

Issue 8.0 September 2006

Administration

Operations, Administration, Maintenance, and Provisioning

DMX user ID/password administration

Changing your own WaveStar

CIT password

The WaveStar

CIT

Administration > Change Password

command allows any user to change his or her own WaveStar

CIT password.

Only privileged users can change another user’s ID or password.

The Change Password screen is also automatically invoked immediately after the login screen if a user’s password has expired. The user is prevented from performing any other function until the password is successfully changed. This screen is also invoked the first time a login is attempted for a new user ID.

The

Administration > Security > User Provisioning

command on the network element System View menu allows a privileged user to create, change, or delete another network element user ID or password.

Important!

Any changes made to a user’s provisioning takes place the next time the user logs in. If the user is currently logged in, no changes take place until that user logs off and logs back in.

Valid DMX user IDs

A valid user ID must be a minimum of five allowed characters to a maximum of ten allowed characters.

Valid DMX passwords

A valid password must comply with the following conditions:

• Length must be a minimum of six characters to a maximum of ten characters

• Must contain at least one alphabetic character and at least three non-alphabetic characters (symbol or number)

• At least one of the non-alphabetic characters must be number and at least one must be a symbol

• When changing a password, the new password must be different from the previous password by at least one character.

Important!

User passwords are case-sensitive.

Characters NOT allowed in a DMX password and user ID

The following table lists the characters that are not allowed in a password and user ID.

365-372-300

Issue 8.0 September 2006

6 - 1 2 7

Administration

Operations, Administration, Maintenance, and Provisioning

Table 6-14 Characters NOT Allowed in a DMX Password and

User ID

Character

Description

Comma

Colon

Character

Space

Commercial at ;

“

Equals sign

Back slash

Description

Quotation mark

Semicolon

Asterisk

Exclamation

Mark

Question mark

Characters allowed in a DMX password and user ID

The following table lists the characters that are allowed in a password and user ID.

Table 6-15 Characters Allowed in a DMX Password and User ID

]

)

(

[

Character

A... Z

' a... z

0... 9

Description Character

Uppercase letters ^

Lowercase letters `

Digits {

Apostrophe

Hyphen |

}

Left parenthesis <

Right parenthesis >

Period (full stop) ~

Slash (Solidus) %

Plus sign

Left square bracket

Right square bracket

Description

Caret

Grave accent

Left curly brace

Right curly brace

Vertical bar

Less than

Greater than

Tilde

Percent sign

Number sign

Ampersand

Horizontal bar

(underscore)

6 - 1 2 8

365-372-300

Issue 8.0 September 2006

Administration

Operations, Administration, Maintenance, and Provisioning

Changing your own password

From the network element System View, the

Administration > Change

Password

command allows any user to change his or her own password. Only privileged users can change another user’s ID or password.

When a user changes their own password, the new password must be different in at least three character positions from the current password.

The original password, or a significant substring of it, must not be part of the new password.

• If the current and new passwords are the same length, then the characters in at least 3 character positions must be different.

• If the current and new passwords are different lengths, then for every possible contiguous substring of the length of the shorter password within the longer password, the characters in at least three character positions must be different between the shorter password and the character substring within the longer password.

Also, the password cannot be one of the last 5 used.

365-372-300

Issue 8.0 September 2006

6 - 1 2 9

Operations, Administration, Maintenance, and Provisioning

User-setable Miscellaneous Discrete Interface

Overview

This section describes the miscellaneous discrete environmental alarm/ status input points and (external) control output points.

Description

The user-setable miscellaneous discrete interface allows users to monitor and control equipment collocated with DMX through a set of discrete input and output points. There are 19 miscellaneous discrete inputs to monitor environmental conditions such as open doors or high temperature, and 4 miscellaneous discrete outputs to control equipment such as fans and generators.

Local miscellaneous discrete input points are included in the determination of the summary alarm/status level for each NE. But even if the Remote NE Status feature is enabled, the alarm/status of

individual miscellaneous discrete inputs/outputs is not exchanged among NEs.

Miscellaneous discrete input alarm level

The alarm level to be associated with each miscellaneous discrete input point is provisionable. By default, each miscellaneous discrete input is a minor alarm.

If a miscellaneous discrete input point is provisioned as an alarm

(minor, major, or critical), TL1 autonomous message REPT ALARM

EVT is used to report the alarm occurrence. This identifies the remote

NE to further query.

If a miscellaneous discrete input point is provisioned as not alarmed

(that is, status), TL1 autonomous message REPT EVT CON is used to report the condition. This identifies the need to retrieve any active miscellaneous discrete status conditions.

Miscellaneous discrete input description

The description to be associated with each miscellaneous discrete input alarm or status point may be provisioned. The provisioned description appears as the

almmsg

conddescr

parameter value in applicable TL1 messages. The default description for each miscellaneous discrete input point is

environment1

environment2

, and so forth.

Note that miscellaneous discrete Input Point 15 is reserved for fan failure.

Miscellaneous discrete output description

The description to be associated with each miscellaneous discrete output control point may be provisioned. The default description for each miscellaneous discrete output point is

control1

control2

, and so

6 - 1 3 0

365-372-300

Issue 8.0 September 2006

User-Setable Miscellaneous Discrete Interface

Operations, Administration, Maintenance, and Provisioning

forth. Control points for miscellaneous discrete outputs may be operated and then released.

Fan Failure

Miscellaneous Discrete #15 is reserved for fan failure. The possible alarm levels are CR, MJ, MN, with MJ being the default.

Reference

For information about the

Configuration>Misc. Discretes

command, refer to the WaveStar

CIT help. For detailed wiring information, refer to the

Metropolis

DMX Access Multiplexer Installation Manual,

365-372-

304

365-372-300

Issue 8.0 September 2006

6 - 1 3 1

User-Setable Miscellaneous Discrete Interface

Operations, Administration, Maintenance, and Provisioning

6 - 1 3 2

365-372-300

Issue 8.0 September 2006

7 Ordering

Overview

Purpose

This chapter contains information on ordering Metropolis DMX

Access Multiplexer equipment and software. The information in this chapter tells you where to go for ordering information.

Contents

Ordering topics included in this chapter are:

Introduction

Engineering Drawings

Software and Documentation

Miscellaneous Equipment and Tools

365-372-300

Issue 8.0, September 2006

7 - 1

Ordering

Introduction

Overview

Lucent has created a set of engineering drawings to facilitate the ordering of all products in the future. These drawings are updated for each planned Release, and contain all of the information needed to order DMX equipment. The information contained in the engineering drawings will not be duplicated anywhere in the interest of keeping all information current and consistent at all times. This chapter will explain how to make sure you are using the most current version of the engineering drawing and where to order it.

Software and Documentation ordering information is not included in the engineering drawings and is therefore included in this chapter. Any information about particular pieces of equipment (i.e. the uses of various cables versus other) is meant to convey useful information that may/may not be contained in the engineering drawings. This information is meant to be used in conjunction with engineering drawings, but not to replace them.

How to order

Equipment and software orders may be placed via Lucent’s online ordering process. For more information, contact your Account

Executive.

7 - 2

365-372-300

Issue 8.0, September 2006

Ordering

Engineering Drawings

Overview

In the interest of ensuring that ordering information is always consistent and up-to-date, Lucent has created a set of engineering drawing meant to contain all information needed to order a DMX system.

Where to Obtain

Engineering Drawings

The engineering drawing is likely to be updated more frequently than the Applications and Planning Guide. Order the most current version of the engineering drawing from CIC.

Whenever ordering equipment, first be sure that you have the most current version of ED8C871-10. You may do so by contacting CIC through one of the mediums detailed below.

How to order Engineering

Drawings

The most up-to-date version of the Engineering drawing

(ED8C871-10) may be obtained through CIC. There are 2 ways to obtain material from CIC.

If you are a Lucent employee and are on the Lucent internal web:

• Go to www.lucentdocs.com and follow the link for Drawings.

Enter the drawing number in the proper field (ED8C871-10).

• Verify that the drawing you have is the same Issue number as the drawing on the site.

• If it is not the same issue, follow the steps on the CIC website for ordering a new drawing.

• If it is the same issue, the drawing is sufficient to help you configure an order.

• Contact CIC by phone: 1-888-582-3688

If you are a non-Lucent employee/outside customer

• Contact CIC by phone: 1-888-582-3688 OR

• Go to http://www.lucent8.com/cgi-bin/CIC_store.cgi?

• Click on Drawings in the menu at the left of the screen.

• Enter the drawing number (ED8C871-10) in the field provided.

• Click on Search.

• Click on the drawing number.

• Choose the media by which you wish to receive the drawing and purchase the drawing.

365-372-300

Issue 8.0, September 2006

7 - 3

Ordering

Software and Documentation

Overview

This section provides software ordering information.

Software releases included in this section are:

• Release 7.0 Software

Software ordering information

Listed below are some need-to-know items before ordering DMX software:

• DMX software is shipped separately from the hardware.

• Order one set of software for each shelf ordered. Software orders must be placed in addition to the hardware order to receive software.

• All system controller (SYSCTL) circuit packs are shipped without software loaded on them. Therefore, software loading must occur at or before installation.

• It may be desirable to have backup CD-ROMs for all releases on hand for backup or initial downloading.

• The software ordering table includes a cross-reference to comcodes where available.

• DMX software includes PC/CIT software.

• Initial Release software includes a CD containing the current documentation to accompany the DMX. Hardcopies of the most current documentation are available through CIC.

7 - 4

365-372-300

Issue 8.0, September 2006

Ordering

Available software

The table below lists the DMX software that may currently be ordered.

Table 7-1 Orderable Software

Comcode Product Release Description

109629477 R7.0

109629485 R7.0

109629386 R7.0

(CD-ROM and SRD)

365-372-300

Issue 8.0, September 2006

7 - 5

Ordering

Available documentation

The table below lists documentation that may currently be ordered.

Documents that come with a shelf assembly order or a software order are noted.

Table 7-2 Orderable Documentation

Document

Number

365-372-300

Title

365-372-301

365-372-302

365-372-304

365-372-306

109596528

(comcode)

DMX Access Multiplexer Applications and

Planning Guide

(Note 1)

DMX Access Multiplexer User Operations

Guide

(Note 1)

DMX Access Multiplexer Alarm Messages and

Trouble Clearing Guide

(Note 1)

DMX Access Multiplexer Installation Manual

(Note 1)

DMX Access Multiplexer TL1 Message Details

DMX User Documentation CD, Release 6

(Note 2)

Important!

The comcodes for these documents are not supplied so as to limit confusion. This book, the Applications and Planning

Guide, is not updated concurrently with the other documents listed in this table, but before them. As such, if comcodes were supplied here, it could result in confusion and the ordering of the wrong version of a document. Use the telephone number for CIC, provided on page 3 of this Chapter, to obtain the correct comcodes for the desired documents. The comcode for the User

Documentation CD is supplied, but it is recommended that CIC be called to verify that the correct version of the CD is being ordered.

Table notes

1.The DMX Access Multiplexer User Operations Guide, Alarm

Messages and Trouble Clearing Guide, Installation Manual,

Aplications and Planning Guide, and TL1 Message Details (in CD-

ROM form) are shipped with the software. The documents may be ordered separately as well.

2.The DMX Access Multiplexer Software Release Description and User

Documentation CD-ROM are shipped with a software order. The CD-

ROM may be ordered separately.

7 - 6

365-372-300

Issue 8.0, September 2006

Ordering

Miscellaneous Equipment and Tools

Lightguide build-outs

DMX utilizes Lucent’s state-of-the-art AllWave ADVANTAGE

Fiber

Optic Attenuators. These attenuators reduce optical power from the transmitter that can result in over-saturation of the receiver, have low reflection to meet stringent system requirements, and are backwardcompatible with existing transmission systems. Unique to the AllWave

ADVANTAGE optical connectivity solution (OCS), the new LC

TM optic attenuators are designed to provide flat spectral loss across the full spectrum, allowing the attenuators to be used in the 1300 nm, 1400 nm, and 1500 nm bands. LC optical attenuators are ideal for networks deploying AllWave fiber, metropolitan or regional networks, applications supported by conventional single-mode optical fiber, multiservice network protocols, and DWDM networks.

The table below lists the available LC-type lightguide build-out attenuators for the DMX.

Table 7-3 Lightguide Build-outs and Accessories

Description

LC Build-Out Attenuators

5 dB

10 dB

15 dB

20 dB

Allwave ADVANTAGE

Fiber Optic

Identification Kit

108279381

108279431

108279480

108279530

108622929

Table notes

1.The LC build-out attenuators listed are connector style PC (polished connectors) at the fiber end. These attenuators must be used on the receive side in all cases. For the LNW36 and LNW39 OC-3 and

LNW46 and LNW49 OC-12 circuit packs, the specified attenuation may not be achieved if a SM-MM (single-mode-multi-mode) fiber signal is incoming to the LC SM-SM attenuator. In this case, a 15 dB attenuator, for example, may achieve an attenuation value less than the specified 15 dB.

2.The AllWave ADVANTAGE Fiber Optic Identification Kit includes labels for fiber optic apparatus products to identify Lucent AllWave

Fiber paths. An instruction sheet is included with recommendations on how to install and use the labels.

365-372-300

Issue 8.0, September 2006

7 - 7

Ordering

Pluggable Transmission

Modules

DMX utilizes Pluggable Transmission Modules (PTMs), also known as

SFPs, on the LNW37, LNW45, LNW49, LNW59, LNW62, LNW63,

LNW64, LNW70, LNW73/73C, LNW74, and LNW78 packs. To ensure proper optical performance, mechanical fit, compliance with

EMC, and compliance with laser safety standards, the Lucent specified

PTM transceivers listed in the table below must be used.

Only the Lucent specified PTM transceivers listed below are compatible with DMX software. If non-Lucent specified PTM transceivers are installed in DMX, the system will reject that transceiver, and that optical port will become inoperable (until approved parts are installed).

Laser Safety CAUTION!

Use only the Lucent specified Class 1 transceivers listed in the table below.

The table below lists the PTM optics that may be used in the LNW37,

LNW45, LNW49, LNW59, LNW62, LNW63, LNW64, LNW70,

LNW73/73C, LNW74, and LNW78 circuit packs.

7 - 8

365-372-300

Issue 8.0, September 2006

Ordering

SONET

Optical

PTMs

Apparatus Code

S15512

OC3IR1-I1

OC3LR1-I1

OC12IR1-I1

OC12LR1-I1

OC12LR2-I1

OC48LR1-I1

OC48LR2-I1

OC192SR1-C1

OC192IR2-C1

OC192LR2-C1

Table 7-4 PTM Optics for LNW37/45/49/59/62/63/64/70/73/73C/

74/78

Comcode

109602599

109453894

109453886

109453902

109467522

109604447

109493528

109504431

109537902

109537563

109537555

Description

OC3 PTM TRCVR

Short Reach, 1.3 SR-1, 1310nm

OC3 PTM TRCVR

Intermediate Reach, 1.3 IR-1,

1310nm

OC3 PTM TRCVR

Long Reach, 1.3 LR-1, 1310nm

OC12 PTM TRCVR Intermediate

Reach, 1.3 IR-1, 1310nm

OC12 PTM TRCVR

Long Reach, 1.3 LR-1, 1310nm

OC12 PTM TRCVR

Long Reach, 1.5 LR-2 (80km),

1510nm

OC48 PTM TRCVR

Long Reach, 1.3 LR-1 (40km),

1310nm

OC48 PTM TRCVR

Long Reach, 1.5 LR-2 (80km),

1550nm

OC192 XFP TRCVR

Short Reach, 1.3 SR-1 (2km),

1310nm

OC192 XFP TRCVR

Intermediate Reach, 1.5 IR-2

(40km), 1310nm

OC192 XFP TRCVR

Long Reach, 1.5 LR-2 (80km),

1550nm

Used In

LNW37/45

LNW49

LNW62

LNW59

365-372-300

Issue 8.0, September 2006

7 - 9

Ordering

Apparatus Code

100BASE-LX-I1

(FE-TX)

GE-1X2XFC-SX-C1

(1000BASE-SX,

1Gbps and 2 Gbps

Fibre-Channel)

GE-1X2XFC-LX-C1

(1000BASE-LX,

1Gbps and 2 Gbps

Fibre-Channel/

FICON)

GE-1X2XFC-SX-I1

(1000BASE-SX,

1Gbps)

Ethernet and SAN

PTMs

(optical and electrical)

GE-1X2XFC-LX-I1

(1000BASE-LX,

1Gbps)

1000BASE-ZX-I1

(1000BASE-ZX,

1Gbps)

BASE-T-C1

FE and GbE

(electrical- NOT OSP)

ESCON-MM-I1

(ESCON)

Comcode Description

109527812 Optical Fast Ethernet PTM,

LC-type connectors (FE-1310SM)

109527796

109527804

109570606

109568782

GbE short-reach, Single-Mode

PTM, supports Ethernet and Fibre-

Channel traffic, LC-type connectors

(GbE/FC/2FC-850)

GbE long-reach, Single-Mode PTM, supports Ethernet, FICON, and

Fibre-Channel traffic, LC-type connectors

(GbE/FC/2FC-1310)

GbE short-reach, Single-Mode

PTM, supports Ethernet and Fibre-

Channel traffic, LC-type connectors, OSP hardened

(GbE/FC/2FC-850)

GbE long-reach, Single-Mode PTM, supports Ethernet, FICON, and

Fibre-Channel traffic, LC-type connectors, OSP hardened

(GbE/FC/2FC-1310)

109541862

109565549

GbE Short-reach, Single-Mode

PTM, supports Ethernet, LC-type connectors, and is OSP hardened

(GbE-1550)

Electrical PTM, provisionable to

100 or 1000 Mbps, Lucent

Approved

RJ-45 Cat 5-E cable, maximum span length of 100 meters

109523886 ESCON, Multi-Mode PTM,

LC-type connectors (ESCON-1310)

Used In

LNW74/70/78

LNW70/73/

73C/78

LNW70/73/

73C/78

LNW63/64/70/

73/73C

LNW63/64/70/

73/73C

LNW63/64/70/

73/73C/78

LNW63/64/70

LNW73/73C

7 - 1 0

365-372-300

Issue 8.0, September 2006

Ordering

Accessories

The table below shows the miscellaneous accessories available for

DMX.

Table 7-5 Miscellaneous Accessories

Product Model/Description Comcode ITE#

ITE-7129

Installation

Order #

33712900 Optical Fiber

Scope

2.5mm Universal

Adapter Cap

1.25mm Universal

Adapter Cap

Video Fiber Scope

Individual, presaturated alcohol wipes

CLETOP Cleaning

Cassette

CLETOP Cleaning

Cassette

Replacement Reel

Luminex Stick port cleaners

Noyes OFS 300-200X 408197028

For use with the Noyes

OFS 300-200X

For use with the Noyes

OFS 300-200X

Noyes VFS-1

99% pure isopropyl alcohol

Type A Reel

1.25 mm

2.5 mm

5.5” x 5.5”

408197044

408197069

TBD

901375147

901375154

901375014

901375030

901375022

408201226

ITE-7129D1 33712901

ITE-7129D2 33712902

TBD

ITE-7136

ITE-7137

TBD

33713600

ITE-7137 D1 33713701

ITE-7134

ITE-7135

R6033

33713700

33713400

33713500

23603300

Table notes

1.This equipment may not be necessary at all locations. It is to be used when the ports need to be verified for cleanliness. If care is exercised when cleaning fibers, the video scope may not be needed.

2.The equipment and material listed above has been tested and is proven effective. Substitution of equipment or materials is at the discretion of the user and is not recommended.

365-372-300

Issue 8.0, September 2006

7 - 1 1

Ordering

7 - 1 2

365-372-300

Issue 8.0, September 2006

8 Product Support

Overview

Purpose

This chapter describes the support services available to Lucent

Technologies’ customers.

Lucent Technologies offers a number of services to assist customers with Engineering, Installation and Technical Support of their networks.

Additionally, Lucent Technologies offers product-specific training courses.

Contents

The following topics are discussed in this chapter:

Worldwide Services

Training

365-372-300

Issue 8.0 September 2006

8 - 1

Product Support

Worldwide Services

Overview

Lucent Worldwide Services provides a full life-cycle of services and solutions to help you plan, design, implement, and operate your network in today's rapidly changing and complex environment.

Engineering Services

Engineering Services provide information and technical support to customers during the planning, implementation, and placement of equipment into new or existing networks. We determine the best, most economical equipment solution for a customer and help ensure equipment is configured correctly for the customer’s network needs, works as specified, and is ready for installation on delivery. These services consist of the following:

• Equipment engineering

• Software engineering

• Site records

• Engineering consulting

• Additional engineering services (Network Realignment, System

Capacity Planning, System Health Assessment)

Installation Services

Lucent Technologies offers Installation Services focused on providing the technical support and resources customers need to efficiently and cost-effectively install their network equipment. We offer a variety of options that provide extensive support and deliver superior execution to help ensure the system hardware is installed, tested, and functioning as engineered and specified. Installation Services provides a complete flexible solution tailored to meet customers' specific needs. These services consist of the following:

• Equipment installation

• Specialized equipment installation

• Network connectivity services

• Installation support services

8 - 2

365-372-300

Issue 8.0 September 2006

Worldwide Services

Product Support

Technical Support

Web-Site

For technical support, contact your local customer support team. You can reach them via the Web at the Lucent Customer Support Web Site

(http://support.lucent.com) or the customer support telephone number listed at the Lucent Contact Us Web Site

(http://www.lucent.com/contact/).

For additional information regarding Worldwide Services, refer to the

Lucent Technologies’ web-site at

http://www.lucent.com/products

Click on

Browse the catalog

Click on

Worldwide Services Solutions

Select the desired service to display:

• Engineering and Installation

• Technical Support Services

365-372-300

Issue 8.0 September 2006

8 - 3

Product Support

Training

Overview

Lucent Technologies offers a formal training curriculum to complement your product needs.

Registering for a course

To review the available courses or to enroll in a training course at one of Lucent’s corporate training centers,

• Within the United States,

– Visit

https://www.lucent-product-training.com

– Call

1-888-LUCENT8

(888-582-3688): Prompt 2.

• Outside the continental United States,

– Visit

https://www.lucent-product-training.com

– Contact your in-country training representative

– Call:

+1-407-767-2798

– Fax:

+1-407-767-2677

Suitcasing

To arrange for a suitcase session at your facility,

• Within the United States, call

1-888-LUCENT8

(888-582-3688):

Prompt 2.

• Outside the continental United States,

– Contact your in-country training representative

– Call:

+1-407-767-2798

– Fax:

+1-407-767-2677

8 - 4

365-372-300

Issue 8.0 September 2006

9 Reliability and Quality

Overview

Contents

The following reliability and quality information is included in this chapter:

Lucent’s Quality Policy

Reliability Program and Specifications

Failure Rates

Sparing Information

International Standards Organization (ISO) Certification

Warranty

365-372-300

Issue 8.0, September 2006

9 - 1

Reliability and Quality

Lucent’s Quality Policy

Quality Policy

Quality plan

We will safeguard the customers' trust by building the capability to execute flawlessly on the promises we make.

This Lucent Technologies Quality Policy guided the development of the DMX Access Multiplexer and will continue affecting this product throughout its life cycle. The primary tool ensuring product quality is the Quality Plan.

9 - 2

365-372-300

Issue 8.0, September 2006

Reliability and Quality

Reliability Program and Specifications

Overview

The reliability program provides enhanced reliability and is implemented as an integral part of the Lucent Technologies’ Process

Management Architecture (PMA) process. The reliability program is comprehensive, and includes activities such as setting and ensuring compliance with customer-focused system-reliability requirements, ensuring component qualification is consistent with use environment and system design, assuring satisfactory component-attachment reliability, predicting failure rates of Field Replaceable Units (FRUs), making sparing recommendations, assessing reliability architecture, modeling system reliability, assuring satisfactory system-downtime performance, reducing hardware failure rates through Environmental

Stress Testing (EST), and tracking field returns.

Design and development

During the design and development stage, reliability predictions, qualification and selection of components, definition of quality assurance audit standards, and prototyping of critical areas of the system ensure built-in reliability.

Manufacturing and field deployment

During manufacturing and field deployment, techniques such as environmental stress testing, production quality audits, field-return tracking, failure-mode analysis, and feedback and corrective-action further enhance the ongoing reliability improvement efforts on the

DMX Access Multiplexer.

Environmental Stress

Testing

DMX circuit packs are subjected to an Environmental Stress Testing

(EST) program. The purpose of the program is to improve reliability by reducing early life failures and implementing root-cause analysis and corrective action on circuit packs that fail EST.

Transmission downtime

DMX satisfies a stringent set of reliability specifications. Some of the critical specifications include Telcordia Technologies downtime requirements and objectives for multiplexers. Telcordia Technologies requirements state that the downtime of a two-way channel within a

SONET multiplexer, due to hardware failure, shall be less than 1.75 minutes per year in a Central Office (CO) environment and 5.25 minutes per year in a Remote Terminal (RT) environment. The corresponding objectives for these parameters are 0.25 minutes per year in a CO environment and 0.75 minutes per year in an RT

365-372-300

Issue 8.0, September 2006

9 - 3

Reliability Program and Specifications

Reliability and Quality

environment. These requirements and objectives appear in Telcordia

Technologies GR-418-CORE.

These requirements and objectives apply to all system elements needed to process a two-way channel, including the core system as well as the high-speed and low-speed interfaces. System-reliability analysis employing Markov modeling is used to determine the system downtimes. As specified in Telcordia Technologies GR-418-CORE, this analysis assumes a mean time to repair of 2 hours for the CO environment and 4 hours for the RT environment. Individual Field

Replacable Unit (FRU) failure rates used in the model were determined using the method described in Telcordia Technologies SR-332,

“Reliability Prediction Procedure for Electronic Equipment (RPP).”

FRUs are system elements that can be replaced in the field, including items such as circuit packs, removable optical interfaces, housings, cooling units, and removable LEDs.

9 - 4

365-372-300

Issue 8.0, September 2006

Reliability and Quality

Failure Rates

Overview

This section provides circuit pack and equipment failure rates for

DMX.

Circuit Pack Failure rates

The table below provides failure-rate predictions for all circuit packs available through R7.0. These failure rates were determined per

Telcordia SR-332. System-inlet air of 25oC is assumed in the predictions for the CO environment. Failure-rate predictions are estimates; actual values may vary.

Circuit Pack Apparatus Code Slot(s) Release

Failure Rate in CO

(FIT)

Failure Rate in

(FIT)

System Controller

(SYSCTL)

System Controller

(SYSCTL)

LNW1

LNW2

Non-volatile Memory

Card

NVM

Headless MAIN Switch pack

LNW80

OC-192 OLIU

OC-192 PTM OLIU

OC-192 OLIU

LNW56

LNW57

LNW58

LNW59

LNW60

LNW523

LNW527

LNW554

CTL

LNW2

M1, M2

1.0

6.0

4.0

5.1

4.0

2.1

4.0

2.1

7.0

4565

7747

197

6108

8527

9227

7902

TBS

9188

9119

9131

15494

394

12216

OC-192 OLIU

OC-48 OLIU

LNW555

LNW29

LNW28

LNW26

M1, M2

3.1

2.1

2.0

1.0

8640

8259

6921

8452

13842

OC-48 OLIU

LNW26B

LNW27

M1, M2

2.0

2.1

6921

8090

OC-48 OLIU LNW31 A-D, G1, G2 2.0

5404 NA

OC-48 OLIU LNW32 A-D, G1, G2 4.0

8167 16335

365-372-300

Issue 8.0, September 2006

9 - 5

Failure Rates

Reliability and Quality

Circuit Pack

OC-48 PTM OLIU

OC-48 OLIU

OC-12 OLIU

OC-3 OLIU

28DS1PM

56DS1/E1

10/100T (100BASE-TX)

Private Line

1000BASE-SX

1000BASE-.LX

1000BASE-X

GbE Private Line (4 ports)

1000BASE-X

GbE Private Line (8 ports)

Apparatus Code

LNW62

LNW76

Slot(s)

A-D, G1, G2

M1, M2

LNW77

LNW121B-

159B

M1, M2

LNW221-259

LNW421-459

LNW46

LNW48

LNW54

LNW49

LNW50

LNW36

LNW7

LNW8

10/100T (100BASE-TX) LNW66

LNW71

LNW67

LNW68

LNW63

LNW64

M1, M2

A-D, G1, G2

M1, M2

A-D, G1, G2

M1, M2

A-D, G1, G2

OC-3 PTM OLIU

OC-3 OLIU

12DS3/EC1

48DS3/EC1

LNW37 (pack) A-D, G1, G2

LNW45 A-D, G1, G2

LNW16

LNW19

A-D

48DS3/EC1 LNW19B

12DS1/DS3 TransMUX LNW18

48DS3EC1TMUX

28DS1

LNW20

LNW6

A-D

A-G

A-D

1.0

3.1

A1, B1, C1, D1 1.1

A1, B1, C1, D1 3.1

A-G

7.0

2.1

2.0

5.1

4.0

3.1

1.1

2.1

3.0

1.1

3.1

5.0

3.0

7.0

1.0

4.0

5.0

1.0

3.1

1.1

6.0

7.0

Release

TBS

Failure Rate in CO

(FIT)

TBS

7042

Failure Rate in

TBS

(FIT)

5625

7215

8375

4847

3111

5091

4628

4523

5236

4076

5047

5226

10094

10452

4520 9040

5595 11190

5909

4294

11818

8587

TBS TBS

5575 11150

6222

10182

9256

9046

10472

8152

5575 11150

5309 10618

5102

6391

7264

7808

6884

13768

TBS

9 - 6

365-372-300

Issue 8.0, September 2006

Failure Rates

Reliability and Quality

Circuit Pack

1000BASE-X/

100BASE-FX

FC-DATA (FICON/

ESCON/FC)

FC-DATA (FICON/

ESCON/FC) w/

Compression

Apparatus Code

LNW70

LNW73

LNW73C

100BASE-LX/

10/100BASE-TX

Private Line

RPR 1000BASE-X/

100BASE-TX

Private Line

LNW74

LNW78

Electric Continuity Test

Tool

LNW94

A-G

A-D

Slot(s)

5.1

Release

5.1

7.0

5.0

6.0

3.1

Failure Rate in CO

(FIT)

9459

Failure Rate in

(FIT)

6445

TBD

7191

9459

14383

NOTE: These Circuit Pack Failure Rates are subject to change.

PTM (SFP/XFP) Failure rates

The table below provides failure-rate predictions for all Pluggable

Transmission Modules (PTMs, also known as SFPs and/or XFPs) available through R7.0. These failure rates were determined per

Telcordia SR-332. System-inlet air of 25oC is assumed in the predictions for the CO environment. Failure-rate predictions are estimates; actual values may vary.

Circuit Pack

OC-12 OLIU

OC-3 PTM OLIU

Apparatus Code

LNW49

Slot(s)

A-D, G1, G2

LNW49 (IR PTM) LNW49

LNW49 (LR-1

PTM)

LNW49

LNW49 (LR-2

PTM)

LNW49

LNW37 (pack) A-D, G1, G2

LNW37 (IR PTM) LNW37

LNW37 (LRPTM) LNW37

7.0

4.0

Release

Failure Rate in CO

(FIT)

4523

409

Failure Rate in

9046

818

(FIT)

TBS NA

5047

407

464

10094

814

928

365-372-300

Issue 8.0, September 2006

9 - 7

Failure Rates

Reliability and Quality

Circuit Pack

OC-48 PTM OLIU

OC-192 PTM OLIU

Apparatus Code

LNW62

OC48LR1-I1

OC48LR2-I1

LNW59

X10GMC2

X10GMC4

X10GMC5

GbE short-reach, Multi-

Mode PTM, supports

Ethernet and Fibre-

Channel traffic, LC-type connectors

(GbE/FC/2FC-850)

GE-1X2XFC-SX-

GbE long-reach,

Single-Mode PTM, supports Ethernet,

FICON, and Fibre-

Channel traffic, LC-type connectors

(GbE/FC/2FC-1310)

GE-1X2XFC-LX-

GbE short-reach, Multi-

Mode PTM, supports

Ethernet and Fibre-

Channel traffic, LC-type connectors, OSP

Hardened

(GbE/FC/2FC-850)

GE-1X2XFC-SX-

GbE long-reach,

Single-Mode PTM, supports Ethernet,

FICON, and Fibre-

Channel traffic, LC-type connectors, OSP

Hardened

(GbE/FC/2FC-1310)

GE-1X2XFC-LX-

Provisionable to 100 or

1000Mbps, supports

Ethernet

(FE and GbE, electrical)

BASE-T-C1

Slot(s)

A-D, G1, G2

LNW62

M1, M2

LNW59

7.0

LNW59 7.0

LNW70/73/73c/78 5.1

7.0

Release

LNW70/73/73c/78 5.1

LNW63/64/70/73/

73C

6.0

LNW63/64/70/73/

73c

6.0

LNW63/64/70 6.0

Failure Rate in CO

(FIT)

TBS

Failure Rate in

TBS

(FIT)

TBS

105

TBS

310

190

310

244

380

620

9 - 8

365-372-300

Issue 8.0, September 2006

Failure Rates

Reliability and Quality

Circuit Pack

Optical PTM, 100

Mbps, LC-type connectors, OSP hardened

(FE-TX)

Optical PTM, 100

Mbps, LC-type connectors, OSP hardened

(FE-1310SM)

GbE very long-reach,

Single-Mode PTM, supports Ethernet, LCtype connectors, OSP

Hardened

(GbE/FC/2FC-1310)

ESCON, Multi-Mode

PTM, LC-type connectors

Apparatus Code Slot(s)

100BASE-LX-I1 LNW78

100BASE-LX-I1 LNW70/74

ESCON-MM-I1

(ESCON)

LNW73/73C

6.0

5.0

1000BASE-ZX-I1 LNW63/64/70/78 6.0

5.1

Release

Failure Rate in CO

(FIT)

545

Failure Rate in

1090

(FIT)

545

500

392

1090

TBD

Equipment Failure Rates

The table below provides the failure rates for DMX hardware.

Equipment

Standard Shelf Assembly

Cooling Unit (standard shelf)

High-capacity Shelf Assembly

Cooling Unit (high-capacity shelf)

Failure Rate in CO (FIT)

1149

2156

1622

4016

Failure Rate in RT (FIT)

3244

8032

365-372-300

Issue 8.0, September 2006

9 - 9

Reliability and Quality

Sparing Information

Overview

This section provides guidelines and a procedure to determine the number of spares needed at each location. The number of spares for each field replaceable unit (FRU) must be determined and maintained separately, based on that FRU’s in-service population at each given location.

Lead Time

Lead time, or turnaround time is the elapsed time between a known

FRU failure at a given service location and the arrival of a repaired (or new) FRU at the location where spare circuit packs are stocked to maintain a spare FRU level consistent with the population in service.

Important!

The number of spares for each code must be determined and maintained separately, based on the in-service population of the code at each location.

Lead time should not be confused with mean time to repair, which is the elapsed time between discovery of the failure of an inservice FRU and when a replacement is put into service.

9 - 1 0

365-372-300

Issue 8.0, September 2006

Reliability and Quality

Sparing Graph

Overview

This section provides guidelines and a procedure to determine the number of spares needed at each location. The number of spares for each circuit pack or port unit code must be determined and maintained separately, based on that code’s in-service population at each given location.

Using the sparing graph

Use the following procedure to determine how many spare circuit packs, port units, or other pieces of equipment are required for each code at each location to maintain 99.9% service continuity, given a 10day lead time.

...........................................................................................................................................................................

Locate the failure rate for the unit under consideration using the tables above.

...........................................................................................................................................................................

Refer to the figure on the following page and select the curve that represents the nearest failure rate. Interpolation may be necessary.

...........................................................................................................................................................................

Follow the curve until it intersects the vertical line that represents the number of units in service at the given location. Interpolation may be necessary.

...........................................................................................................................................................................

Refer to the horizontal line immediately above the intersection. The number associated with this line is the minimum number of spares recommended for that location.

...........................................................................................................................................................................

Repeat steps 1-4 for each circuit pack, port unit, and type of equipment listed in the tables above.

N D O F S T E P S

365-372-300

Issue 8.0, September 2006

9 - 1 1

Sparing Graph

Reliability and Quality

Example of using the graph

If there are 100 LNW46 OC-12 OLIU port units (failure rate of 3111) in service at a given location and your lead time is 10 days, then you should order and stock 3 spare OC-12 OLIUs port units for that location.

Sparing graph for 10-day lead time

Use the graph below to plan the number of spares necessary for the circuit packs and equipment used in DMX.

Figure 9-1 Sparing Graph for a 10-Day Lead Time

CP FITs (in thousands)

10 20 30 10

1 2 3

Number of Circuit Pack/Equipment in Service

2x10

9 - 1 2

365-372-300

Issue 8.0, September 2006

Reliability and Quality

International Standards Organization (ISO) Certification

Overview

Various business units within Lucent Technologies have been certified to ISO 9001 and TL 9000 in past years. Lucent Technologies has moved to one quality management system for the entire company. The

Lucent Management System (LMS) achieved TL 9000 certification in

2004. DMX is certified to this quality standard as part of LMS. This certification includes ISO certification.

TL9000

TL 9000 is a telecommunications industry-specific set of requirements and measurements for software, hardware and services. TL 9000 is built on existing industry standards, including ISO 9001.

Conformance to TL 9000 constitutes conformance to corresponding

ISO 9001 requirements. TL 9000 consolidates various industry requirements and customer requests for measurements; it reduces problems caused by multiple requirements and audits; and it standardizes reporting and use of supplier performance data via defined measurements. TL 9000 requires well-documented and implemented controls for design development, production, delivery, installation, and service. Its purpose is to ensure manufacturers produce products with consistently high levels of quality and service.

365-372-300

Issue 8.0, September 2006

9 - 1 3

Reliability and Quality

Warranty

Hardware warranty

Lucent Technologies provides a one year hardware warranty on the

DMX Access Multiplexer, effective from the date the unit is shipped.

Lucent Technologies provides two contacts for hardware failure emergencies. The Repair and Return line is to be used whenever a piece of equipment has failed to the point that it requires repairs, or must be replaced. The only times the Hotline is to be used is in the event of a service outage or during the initial installation and turn-up of the DMX.

• Repair and Return: 1-800-255-1402

• Emergency Hotline: 1-800-869-6757

Lucent also provides one year of access to LWS On-Line Customer

Support web-site (http://www.lucent.com/solutions/lws.html). Any

3rd- party vendor warranty terms will be pass-through from original vendor.

Software warranty

Lucent Technologies offers a 90 day warranty for defect resolution. All warranties pertain to the deployment of a release and do not apply to individual software licenses. For more warranty information, contact your local Lucent Technologies Account Executive.

Lucent’s warranty on any software release will not exceed 90 days for defect resolution. All warranties pertain to the deployment of a release and do not apply to individual software licenses.

For more warranty information, contact your local Lucent

Technologies Account Executive.

9 - 1 4

365-372-300

Issue 8.0, September 2006

Warranty

Reliability and Quality

Recycling / take-back / disposal of product

Figure 9-2 Take Back Symbol

In the European Union, a solid bar under the crossed-out wheeled bin indicates that the product was put on the market after 13 August 2005.

Technologies equipment offers.

For information regarding take-back of equipment by Lucent

Technologies, or for more information regarding the requirements for recycling/disposal of product, please contact your Lucent Account

Manager or Lucent Takeback Support [email protected].

365-372-300

Issue 8.0, September 2006

9 - 1 5

Warranty

Reliability and Quality

9 - 1 6

365-372-300

Issue 8.0, September 2006

10 Technical Specifications

Overview

Purpose

This section contains the technical specifications for the DMX Access

Multiplexer.

Contents

This chapter contains the following sections:

Electrical Interfaces

TDM Optical Interfaces

Multimode Fiber Transmission with OC-3 and OC-12 circuit packs

Ethernet/SAN Optical Specifications

System Performance

Operations Interfaces

Physical Specifications

External Equipment Specifications

365-372-300

Issue 8.0, September 2006

1 0 - 1

Overview

Technical Specifications

Transmission interface standards

The table below lists the electrical and optical transmission standards for SONET, Ethernet, and SAN interfaces.

Table 10-1 Transmission Interface Standards

Interface

DS1/DS3/EC-1

OC-3/OC-12/OC-48/

OC-192

100BASE-TX, 100BASE-LX

1000BASE-SX and

1000BASE-LX

Standard

ITU G.703, G.704, G.706, G.736,

G.775, M.2100

ANSI T1.231-1997

GR-499-CORE, Issue 2, 1998

GR-253-CORE, Issue 3, 2000

GR-496-CORE, Issue 1, 1998

GR-1400-CORE, Issue 3, 2001

ANSI T1.231-1997

IEEE 802.3

IEEE 802.1D and 802.1Q

ITU G.7041, ITU G.707

Comments

B8ZS/AMI option, SF/ESF (DS1)

VMR, VM, or clear channel (DS3)

VC-12

FICON/ESCON/Fibre-Channel

ITU M.2101, ITU G.707

ITU G.7041,

SA22-7202-02, SA23-0394-03,

SG24-4662-00,

ANSI X3.296-1977

ANSI INCITS 352-2002

1 0 - 2

365-372-300

Issue 8.0, September 2006

Technical Specifications

Electrical Interfaces

Overview

Purpose

This section contains the technical specifications for the low-speed electrical interfaces.

Contents

This section provides information on the following interfaces:

28DS1 (LNW6), 28DS1PM (LNW7), and 56 DS1/E1

(LNW8)

12DS3/EC1 (LNW16) and 48DS3/EC1 (LNW19/19B)

DS3 TransMUX (LNW18)

48DS3/EC1/TransMUX (LNW20)

10/100T (10/100 Mbps) Ethernet (LNW66 and LNW71)

10/100BASE-TX (10/100 Mbps) Ethernet (LNW74)

Electrical PTM 100/1000BASE-TX (100/1000 Mbps)

Ethernet (LNW63/64/70)

365-372-300

Issue 8.0, September 2006

1 0 - 3

Technical Specifications

28DS1 (LNW6), 28DS1PM (LNW7), and 56 DS1/E1 (LNW8)

Overview

The LNW6 and LNW7 are not supported when the LNW59 VLF Main pack, introduced in R7.0, is used. However, they are supported by all other Main interface circuit packs from previous releases.

Electrical specification DS1

The DS1 low-speed interface transmits and receives a standard electrical DS1 signal as specified in GR-499-CORE (1.544 Mb/s nominal rate, DSX-1 interconnect specification). Line coding is provisionable per DS1 port to alternate mark inversion (AMI) or AMI with bipolar 8-zero substitution (B8ZS).

Electrical specification E1

The E1 low-speed interface transmits and receives a standard electrical

E1 signal as specified in ITU G.703, G.704, G.706, G.736,

G.775, M.2100

(1.544 Mb/s nominal rate, DSX-1 interconnect specification).

Format specification

The LNW6/7/8/112 can be provisioned for the following DS1 formats: unframed (UF), superframe (SF), or extended superframe (ESF) as specified in GR-499-CORE, Section 10. In the case of SF or ESF format selections, DS1 performance monitoring information is collected by monitoring the associated DS1 framing format per ANSI

T1.231-1997.

Alarm thresholding

The following parameters are monitored on the DS1 interfaces:

• Loss of signal (LOS): 28DS1 + 28DS1PM + 56DS1/E1

• Bit error rate threshold (BER) based on line coding violations

(CV-L)

The alarm level for the monitored parameters can be provisioned to critical (CR), major (MJ), minor (MN), not alarmed or status conditioned (NA), not reported (NR).

DS1/E1 Transmission

Length

When transmitting DS1/E1 signals to a DSX panel, the Approximate

Span Length is 655 feet.

When transmitting DS1 signals to another DS1 terminating device the

Approximate Span Length is 1110 feet.

Loopbacks

The following loopbacks are supported on the LNW6/7/8 interfaces:

• Per-port DS1/E1 facility loopback

• Per-port DS1/E1 terminal loopback.

1 0 - 4

365-372-300

Issue 8.0, September 2006

28DS1 (LNW6), 28DS1PM (LNW7), and 56 DS1/E1 (LNW8)

Technical Specifications

Line build-outs (LBOs)

Line build-outs are software-provisionable. The maximum distance depends on the cable type (maximum 665 feet).

Performance monitoring

PM data is reported for DS1/E1 signals when DMX is equipped with the LNW7/8 circuit packs.

For a detailed list of PM parameters and thresholds, refer to Appendix

B of this document.

365-372-300

Issue 8.0, September 2006

1 0 - 5

Technical Specifications

12DS3/EC1 (LNW16) and 48DS3/EC1 (LNW19/19B)

Electrical specification

(DS3)

The low-speed DS3 interfaces transmit/receive a standard electrical

DS3 signal as specified in GR-499-CORE, Section 9 (44.736 Mb/s rate,

DSX-3 interconnect specification, bipolar 3-zero substitution (B3ZS) encoding). However, the signal does not have to contain a standard

DS3 frame.

Electrical specification

(EC-1)

The EC-1 low-speed interfaces provide transport of any STS-1 signal compatible with the electrical STS-1 interface specification in

GR-253-CORE, Issue 3. The EC-1 low-speed port can be provisioned to provide STS-1 path termination functions for a VT1.5 structured

STS-1 with an asynchronous DS1 mapping.

The low-speed EC-1 interfaces transmit/receive a standard electrical

EC-1 signal as specified in GR-253-CORE, Issue 3 (51.844 Mb/s rate,

STSX-1 interconnect specification, bipolar 3-zero substitution (B3ZS) encoded and scrambled).

DS3/EC-1 Port Provisioning

The LNW16 and LNW19 circuit packs enable you to provision DS3 or

EC-1 service on a per-port basis. Thus, one of these circuit packs can host a variety of DS3 or EC-1 traffic.

DS3/EC-1 Transmission

Length

When transmitting DS3/EC1 signals to a DSX panel, the Approximate

Span Length is 450 feet.

When transmitting DS3/EC1 signals to another DS3 terminating device

(such as a DMX) the Approximate Span Length is 900 feet.

1 0 - 6

365-372-300

Issue 8.0, September 2006

Technical Specifications

DS3 TransMUX (LNW18)

Electrical specification

The TransMUX circuit pack provides 12 ports for DS3 service.

DS3 interfaces transmit/receive a standard electrical DS3 signal as specified in GR-499-CORE, Section 9 (44.736 Mb/s rate, DSX-3 interconnect specification, bipolar 3-zero substitution (B3ZS) encoding).

Trans/MUX circuit pack

DS1 and DS3 signals

DMX supports a 12-port Trans/MUX card that can collect various DS1 signals from around a ring and combine them into a channelized DS3 signal.

The Trans/MUX circuit pack functions in the following manner:

Transmit Functions

• Receives a B3ZS-encoded DS3 signal from a DSX-3

• Recovers DS3 clock and NRZ data

• Calculates parity errors on the DS3 input

• Demultiplexes the M13 or C-bit formatted DS3 signal into 28

DS1s

• Maps the 28 DS1s into VT1.5s and then into an STS-1

• Inserts STS-1 path overhead

• Provides the STS-1 signal to the OLIU circuit packs

Receive Functions

• Interprets the STS-1 pointer values

• Terminates the STS-1 path

• Disinterleaves the STS-1 signal into 28 VT1.5s and interprets VT pointer values

• Converts the VT1.5 signals to 28 DS1 signals

• Multiplexes the 28 DS1 signals to an M13 or C-bit formatted DS3 signal

• B3ZS encodes the outgoing DS3 signal

• Pre-equalizes the DS3 signal (with LBO) and transmits it to a

DSX-3

365-372-300

Issue 8.0, September 2006

1 0 - 7

Technical Specifications

48DS3/EC1/TransMUX (LNW20)

Electrical specification

The LNW20 provides 48 ports supporting DS3, EC1, and TMUX functionality on a port-by-port basis. Each port can be individually provisioned as DS3 or EC1 (unchannelized), or as TransMUX

(channelized DS3s). With the LNW20, one high-density pack can be used for all DS3, EC1, and/or TransMUX applications.

LNW59 VLF Main is used. LNW20 only functions in portless mode in

G1/G2. When the LNW20 is used with non-VLF Mains, it can not occupy G1/G2.

Ported chanelized DS3 mode of operation

The LNW20 Trans/MUX card that can collect various DS1 signals from around a ring and combine them into a channelized DS3 signal.

The Trans/MUX capability performs in the following manner:

Transmit Functions

• Receives a B3ZS-encoded DS3 signal from a DSX-3

• Recovers DS3 clock and NRZ data

• Calculates parity errors on the DS3 input

• Demultiplexes the M13 or C-bit formatted DS3 signal into 28

DS1s

• Maps the 28 DS1s into VT1.5s and then into an STS-1

• Inserts STS-1 path overhead

• Provides the STS-1 signal to the OLIU circuit packs

Receive Functions

• Interprets the STS-1 pointer values

• Terminates the STS-1 path

• Disinterleaves the STS-1 signal into 28 VT1.5s and interprets VT pointer values

• Converts the VT1.5 signals to 28 DS1 signals

1 0 - 8

365-372-300

Issue 8.0, September 2006

48DS3/EC1/TransMUX (LNW20)

Technical Specifications

• Multiplexes the 28 DS1 signals to an M13 or C-bit formatted DS3 signal

• B3ZS encodes the outgoing DS3 signal

• Pre-equalizes the DS3 signal (with LBO) and transmits it to a

DSX-3

Unchannelized DS3 operation

The low-speed DS3 interfaces transmit/receive a standard electrical

DS3 signal as specified in GR-499-CORE, Section 9 (44.736 Mb/s rate,

DSX-3 interconnect specification, bipolar 3-zero substitution (B3ZS) encoding). However, the signal does not have to contain a standard

DS3 frame.

EC-1 operation

The EC-1 low-speed interfaces provide transport of any STS-1 signal compatible with the electrical STS-1 interface specification in

GR-253-CORE, Issue 3. The EC-1 low-speed port can be provisioned to provide STS-1 path termination functions for a VT1.5 structured

STS-1 with an asynchronous DS1 mapping.

The low-speed EC-1 interfaces transmit/receive a standard electrical

EC-1 signal as specified in GR-253-CORE, Issue 3 (51.844 Mb/s rate,

STSX-1 interconnect specification, bipolar 3-zero substitution (B3ZS) encoded and scrambled).

DS3 portless mode of operation

The LNW20 can also function in portless mode. Portless mode does not utilize any of the electrical ports on the pack. When operating in portless mode, LNW20 converts channelized DS3 signals that enter

DMX on a SONET STS-1 interface (on another pack) to VT mapped

STS-1s. This VT-mapped STS-1 is cross-connected at the VT level in the Main packs (at least one side of the cross-connect is OCn/EC1) to any interface that supports the signal structure today (DS1, channelized

DS3, EC1, optical). Portless mode can be provisioned on a per-port basis when VLF Mains are used. When non-VLF Mains are used, odd numbered ports can be configured as portless and the corresponding even-numbered port will be unavailable for service.

365-372-300

Issue 8.0, September 2006

1 0 - 9

Technical Specifications

10/100T (10/100 Mbps) Ethernet (LNW66 and LNW71)

Electrical specification

These 10/100T circuit packs provide a 24-port, 100BASE-TX, IEEE

802.3-compliant interface that is capable of spanning distances of 100 meters. The 10/100T port performs protocol transparent filtering and bridging of incoming media access control (MAC) frames. MAC frames with a destination address on the local bus are filtered by the

10/100T circuit packs to prevent unnecessary transmission of frames over the wide area network (WAN). The 10/100T interface auto-negotiates mode (full/half duplex) and speed (10/100 Mbps) when interfacing with other 802.3-compliant devices over twisted pair media.

The 10/100T circuit packs must be housed in slot 1 of a Function Unit group and are not equipment protected. However, facility protection can be provided through the WAN via SONET (UPSR, BLSR, or 1+1) and/or (on the LNW66) through the IEEE 802.1W spanning tree algorithm.

The 10/100T Ethernet interfaces comply with the following transmission standards:

• standard IEEE 802.1D for transparent bridging and spanning tree protection.

• standard IEEE 802.3, Section 25 for 10/100 Mb autonegotiation

(including flow control, full-duplex transmission, and half-duplex transmission).

Important!

The LNW71 is being DA’d and will no longer be available as of 3/1/08.

Format specification

The 10/100T circuit packs comply with the following formatting standards:

•

Maximum frame size refer to Packet size in different tagging modes (A-86)

• standard IEEE 802.1Q VLANs

• Ethernet to SONET Mapping, (G.7041 (GFP) and G.707 (Virtual

Concatenation))

• Protection (SONET and/or 802.1W) and Ethernet Bridging

(802.1D)

1 0 - 1 0

365-372-300

Issue 8.0, September 2006

10/100T (10/100 Mbps) Ethernet (LNW66 and LNW71)

Technical Specifications

Performance monitoring

Performance monitoring capabilities are available on the 10/100T circuit packs. A detailed list of monitored parameters can be found in

Appendix B of this document.

365-372-300

Issue 8.0, September 2006

1 0 - 1 1

Technical Specifications

100/1000BASE-TX (10/100 Mbps) Ethernet (LNW70)

Electrical specification

The LNW70 uses electrical PTMs that are provisionable to support either 100BASE-T or 1000BASE-T traffic. The electrical PTMs can occupy ports 1-4.

The dual function electrical PTM is provisionable for 100 or 1000

Mbps traffic. It conforms to the IEEE802.3 standards for 100BASE-T and 1000BASE-T in its respective settings (IEEE802.3z and

IEE802.3ab). Connectivity is provided for an RJ-45 Cat 5 cable and the

PTM has a maximum span length of 100 meters. When the LNW70 is installed in slots G1 or G2, only the optical PTMs can be used.

For more information on the PTM optics available for the LNW70 refer

to the sections entitled

Electrical PTM 100/1000BASE-TX (100/1000 Mbps)

Ethernet (LNW63/64/70)

and

GbE (1000BASE-X)/ Fast-E (100BASE-LX/TX)

Optical/Electrical Ethernet (LNW70)

The LNW70 circuit pack can also support four 1000BASE-X (SX, LX, and/or ZX— very long reach 80km), IEEE 802.3-compliant

(1000Mbps) GbE interfaces and four 100BASE-LX IEEE

802.3-compliant (100 Mbps) fast Ethernet interfaces. The LNW70 circuit pack performs protocol transparent filtering and bridging of incoming media access control (MAC) frames. MAC frames with a destination address on the local bus are filtered by the LNW70 to prevent unnecessary transmission of frames over the wide area network

(WAN).

The LNW70 is an unprotected pack by default. R7.0 incorporates support of Link Aggregation on LNW70 LAN ports, which can be used to provide facility protection. For more information on Link

Aggregation, refer to

Link Aggregation on LNW70 LAN ports

Prior to R7.0, the LNW70 could only occupy slot 1 of any Function

Unit group on the shelf (including Growth slots), and up to 20

1000BASE-X and 20 100BASE-LX ports were addressable when all

Function Unit groups are equipped with LNW70 circuit packs.

When DMX is equipped with VLF Main (LNW59) packs, Ethernet packs can occupy both Slot 1 and 2 of a Function or Growth Unit

(where applicable). With VLF Mains and all tributary slots populated with LNW70 packs, up to 40 1000BASE-X and 40 100BASE-LX ports are addressable. When LNW70 is installed in slots G1 or G2, only optical PTMs can be used. DMX also does not allow packs with electrical interfaces to be installed in adjacent slots within the same

1 0 - 1 2

365-372-300

Issue 8.0, September 2006

100/1000BASE-TX (10/100 Mbps) Ethernet (LNW70)

Technical Specifications

Function or Growth unit next to another pack with Electrical interfaces.

Therefore, if slots A1/2 through D1/2 are equipped with LNW70 packs using electrical PTMs, up to 32 electrical 100/1000BASE-TX ports are addressable.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW70 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

The LNW70 features Pluggable Transmission Module (PTM) electrical and optical interfaces. PTMs are “pluggable” in the sense that they can be plugged into a circuit pack as they become necessary. This allows customers to grow their network incrementally, only realizing the full cost for optics as the need to provision service on (and thus receive revenue from) them becomes necessary. LNW70 packs are purchased and shipped with no ports populated with functioning optics. The ports remain empty until the customer decides to place interfaces in them.

4- ports are available for 1000BASE-X (SX and/or LX) optics or

100/1000BASE-TX electrical interfaces and 4 ports are available for

100BASE-LX optics.

The 100/100BASE-TX Ethernet interfaces comply with the following transmission standards:

• standard IEEE 802.1D for transparent bridging and spanning tree protection.

• standard IEEE 802.3, Section 25 for 10/100 Mb autonegotiation

(including flow control, full-duplex transmission, and half-duplex transmission).

Format specification

The LNW70 complies with the following formatting standards:

•

Maximum frame size refer to Packet size in different tagging modes (A-86)

• standard IEEE 802.1Q VLANs

• Ethernet to SONET Mapping, (G.7041 (GFP) and G.707 (Virtual

Concatenation))

• Protection (SONET and/or 802.1W) and Ethernet Bridging

(802.1D)

Performance monitoring

Performance monitoring capabilities are available on the 10/100T circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 3

Technical Specifications

10/100BASE-TX (10/100 Mbps) Ethernet (LNW74)

Electrical specification

The LNW74 provides 8-ports for optical 100BASE-LX transport at

100 Mbps using standard Ethernet switching IEEE 802.1, standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU G.7041), and standard STS-1 and VT VCAT according to ITU G.707.

For more information on the PTM optics available for the LNW74 refer to the section entitled

10/100T (10/100BASE-T)/ Fast-E (100BASE-LX)

Electrical/Optical Ethernet Private Line (LNW74)

The LNW74 also provides 16 electrical ports for the 10/100BASE-TX interfaces. These electrical ports transmit at 10/100 Mbps using standard Ethernet switching IEEE 802.1, standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU G.7041), and standard

STS-1 and VT virtual concatenation according to ITU G.707. The

LNW74 electrical interfaces can transmit signals across spans as long as 100 meters. The LNW74 is an unprotected pack.

The LNW74 circuit pack is designed specifically to support Fast

Ethernet Private Line applications. Each LNW74 circuit pack can support 24 private lines. The LNW74 can also support STS-3(c) cross connections instead of virtual concatenation.

The 10/100T Ethernet interfaces comply with the following transmission standards:

• standard IEEE 802.1D for transparent bridging and spanning tree protection.

• standard IEEE 802.3, Section 25 for 10/100 Mb autonegotiation

(including flow control, full-duplex transmission, and half-duplex transmission).

Mains are used), LNW74 can be installed next to another optical TDM or Ethernet pack with in the same group (ex. LNW74 and LNW67 or

LNW32).

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW74 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

1 0 - 1 4

365-372-300

Issue 8.0, September 2006

10/100BASE-TX (10/100 Mbps) Ethernet (LNW74)

Technical Specifications

Format specification

The LNW74 complies with the following formatting standards:

• Maximum frame size refer to

Packet size in different tagging modes

• standard IEEE 802.1Q VLANs

• Ethernet to SONET Mapping, (G.7041 (GFP) and G.707 (Virtual

Concatenation))

• Protection (SONET and/or 802.1W) and Ethernet Bridging

(802.1D)

Performance monitoring

Performance monitoring capabilities are available on the LNW74. A detailed list of monitored parameters can be found in Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 5

Technical Specifications

Electrical PTM 100/1000BASE-TX (100/1000 Mbps) Ethernet

(LNW63/64/70)

Electrical specification Electrical Fast Ethernet/GbE PTM for LNW63/64/70

The LNW63/64/70 now support a dual function electrical Pluggable

Transmission Module (PTM), also known as SFP, that is provisionable for 100 or 1000 Mbps traffic. On the LNW70, the PTM can function at both 100 and 1000BASE-TX rates. On the LNW63 and LNW64, only the 1000BASE-TX rate is supported.

The electrical Ethernet PTM conforms to the IEEE802.3 standards for

100BASE-T and 1000BASE-T in its respective settings (IEEE802.3z and IEE802.3ab). Connectivity is provided for an RJ-45 Cat 5 cable and the PTM has a maximum span length of 100 meters.

For more information on the PTM optics available for the Ethernet circuit packs refer to the section entitled

Ethernet/SAN Optical

Specifications

. For more information on the LNW63, LNW64, and

LNW70 packs themselves, refer to the following sections:

100/1000BASE-TX (10/100 Mbps) Ethernet (LNW70)

4-port GbE PTM

(1000BASE-TX and/or 1000BASE-SX/LX/ZX) Private Line Optical Ethernet

(LNW63)

8-port GbE PTM (1000BASE-TX and/or 1000BASE-SX/LX/ZX)

Private Line Optical Ethernet (LNW64)

(100BASE-LX/TX) Optical/Electrical Ethernet (LNW70)

GbE (1000BASE-X)/ Fast-E

The 100/100BASE-TX Ethernet interfaces comply with the following transmission standards:

• standard IEEE 802.1D for transparent bridging and spanning tree protection.

• standard IEEE 802.3, Section 25 for 10/100 Mb autonegotiation

(including flow control, full-duplex transmission, and half-duplex transmission).

Performance monitoring

Performance monitoring capabilities are available on the 10/100T circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

1 0 - 1 6

365-372-300

Issue 8.0, September 2006

Technical Specifications

TDM Optical Interfaces

Overview

Purpose

This section contains technical specifications for the low- and high-speed DMX TDM optical interfaces.

Contents

The following optical interfaces are discussed in this section:

Quad OC-3 Low-speed OLIU (LNW36)

Quad OC-3 Low-speed OLIU (LNW37)

8-port OC-3 Low-speed OLIU (LNW45)

Dual OC-12 Low-speed OLIU (LNW46)

OC-12 High-speed OLIU (LNW48)

Quad OC-12 Low-speed OLIU (LNW49)

OC-12 High-speed OLIU (LNW50)

OC-12 High-speed OLIU (LNW54)

OC-48 OLIU (DWDMs, LNW26B, LNW27, LNW28,

LNW29, LNW31, LNW32, LNW62, LNW76, and LNW77)

OC-192 OLIUs (LNW56, LNW57, LNW58, LNW59,

LNW60, LNW523, LNW527, LNW554, and LNW555)

SONET Optical Specifications: OC-3 and OC-12 Low-speed

OLIUs (LNW36, LNW46)

SONET Optical Specifications: OC-12 High-speed OLIUs

(LNW48, LNW50, and LNW54)

SONET Optical Specifications: OC-3 OLIUs (LNW37 and

LNW45) with PTM pluggable optics

SONET Optical Specifications: OC-12 OLIUs (LNW49) with PTM pluggable optics

SONET Optical Specifications: OC-48 OLIUs (LNW26B,

LNW27, LNW28, LNW29, LNW32)

SONET Optical Specifications: OC-48 OLIU (LNW62)

365-372-300

Issue 8.0, September 2006

1 0 - 1 7

Overview

SONET Optical Specifications: OC-48 OLIU (LNW76 and

LNW77)

SONET Optical Specifications: OC-48 Low-Speed OLIU

(LNW31)

OC-48 DWDM Optical Specification

(LNW121B-LNW159B, LNW221-LNW259, and

LNW421-LNW459)

SONET Optical Specifications: OC-192 OLIU (LNW59)

SONET Optical Specifications: OC-192 OLIU (LNW56 and

LNW58)

SONET Optical Specifications: OC-192 OLIU (LNW57 and

LNW60)

DWDM OC-192 OLIUs (LNW523, LNW527, LNW554, and

LNW555) Optical Specification

Technical Specifications

1 0 - 1 8

365-372-300

Issue 8.0, September 2006

Technical Specifications

Quad OC-3 Low-speed OLIU (LNW36)

Optical specification

The LNW36 OLIU optics meet or exceed SONET OC-3, long-reach specifications (SONET LR-1 DFB). The distributed feedback (DFB) laser transmitter supplies a 1310 nm, scrambled non-return-to-zero

(NRZ) coded signal (155.52 Mb/s).

The LNW36 OLIU long reach OC-3 interface supports span lengths up to 55 km and is OSP hardened. Refer to

SONET Optical Specifications:

OC-3 and OC-12 Low-speed OLIUs (LNW36, LNW46)

in this chapter for

detailed system, transmitter, receiver, and link budget specifications.

The LNW36 is being DA’d and will no longer be available as of

12/31/07.

Alarm thresholding

The following parameters are monitored on the OC-3 interface:

• LOS

• LOF

• AIS-L

• RFI-L (FERF)

• Signal degrade (BER)

• Signal fail (BER).

Performance monitoring

SONET line and path performance monitoring complies with the standards outlined in GR-253-CORE. For detailed PM parameter thresholds on the OC-3 interface, refer to Appendix B of this document.

365-372-300

Issue 8.0, September 2006

1 0 - 1 9

Technical Specifications

Quad OC-3 Low-speed OLIU (LNW37)

Optical specification

The LNW37 OLIU uses Pluggable Transmission Module (PTM) optics, also known as SFP optics, and is OSP hardened. PTM optics can be

“plugged” into the circuit pack as they become needed. Because the optics are pluggable, different ranges are available. The LNW37 can be equipped with OC-3 SR-1, IR-1 or LR-1 optics. These optics meet standard optical specs per Telcordia GR-253. and ITU G.957.

The multi-longitudinal-mode/Fabry-Perot (FP) laser is used for short or intermediate-reach transmission. Either a FP or a single-longitudinal- mode/distributed feedback (DFB) laser transmitter is employed in long-reach applications. The PTM optics for the LNW37 supply a 1310 nm, scrambled non-return-to-zero (NRZ) coded signal (155.52 Mb/s).

When equipped with SR-1 PTM optics, the LNW37 can span distances of 2 km.

When equipped with IR-1 PTM optics, the LNW37 can span distances of 20 km.

When equipped with the LR-1 PTM optics, the LNW37 can span distances of 55 km.

Refer to

SONET Optical Specifications: OC-3 OLIUs (LNW37 and LNW45) with PTM pluggable optics

in this chapter for detailed system, transmitter, receiver, and link budget specifications.

1 0 - 2 0

365-372-300

Issue 8.0, September 2006

Quad OC-3 OLIU (LNW37)

Technical Specifications

Allowed Optics

The table below lists the PTM optics, also known as SFP optics, that may be used in the LNW37 circuit pack.

DMX utilizes Pluggable Transmission Module (PTM) optics on the

LNW37 circuit pack. To ensure proper optical performance, mechanical fit, compliance with EMC, and compliance with laser safety standards, the Lucent specified PTM transceivers listed in the table below must be used.

Table 10-2 PTM Optics for LNW37

Apparatus Code

S155I2

(OC3SR1-I1)

OC3IR1-I1

Comcode

109602599

109453894

Description

OC3 PTM TRCVR

Short Reach, SR-1

OC3 PTM TRCVR

Intermediate Reach, IR-1

OC3LR1-I1 109453886

Long Reach, LR-1

Alarm thresholding

The following parameters are monitored on the OC-3 interface:

• LOS

• LOF

• AIS-L

• RFI-L (FERF)

• Signal degrade (BER)

• Signal fail (BER).

Performance monitoring

SONET line and path performance monitoring complies with the standards outlined in GR-253-CORE. For detailed PM parameter thresholds on the OC-3 interface, refer to Appendix B of this document.

365-372-300

Issue 8.0, September 2006

1 0 - 2 1

Technical Specifications

8-port OC-3 Low-speed OLIU (LNW45)

Optical specification

The LNW45 OLIU uses Pluggable Transmission Module (PTM) optics and is OSP hardened. PTM optics can be “plugged” into the circuit pack as they become needed. Because the optics are pluggable, different ranges are available. The LNW45 can be equipped with either

OC-3 SR-1, IR-1 or LR-1 optics. These optics meet standard optical specs per Telcordia GR-253. and ITU G.957.

The multi-longitudinal-mode/Fabry-Perot (FP) laser is used for short or intermediate-reach transmission. Either a FP or a single-longitudinal- mode/distributed feedback (DFB) laser transmitter is employed in long-reach applications. The PTM optics for the LNW45 supply a 1310 nm, scrambled non-return-to-zero (NRZ) coded signal (155.52 Mb/s).

When equipped with SR-1 PTM optics, the LNW45 can span distances of 2 km.

When equipped with IR-1 PTM optics, the LNW45 can span distances of 20 km.

When equipped with the LR-1 PTM optics, the LNW45 can span distances of 55 km.

Refer to

SONET Optical Specifications: OC-3 OLIUs (LNW37 and LNW45) with PTM pluggable optics

in this chapter for detailed system, transmitter, receiver, and link budget specifications.

1 0 - 2 2

365-372-300

Issue 8.0, September 2006

8-port OC-3 Low-speed OLIU (LNW45)

Technical Specifications

Allowed Optics

The table below lists the PTM optics, also known as SFP optics, that may be used in the LNW45 circuit pack.

DMX utilizes Pluggable Transmission Module (PTM) optics on the

LNW45 circuit pack. To ensure proper optical performance, mechanical fit, compliance with EMC, and compliance with laser safety standards, the Lucent specified PTM transceivers listed in the table below must be used.

Table 10-3 PTM Optics for LNW45

Apparatus Code

S155I2

(OC3SR1-I1)

OC3IR1-I1

Comcode

109602599

109453894

Description

OC3 PTM TRCVR

Short Reach, SR-1

OC3 PTM TRCVR

Intermediate Reach, IR-1

OC3LR1-I1 109453886

Long Reach, LR-1

Alarm thresholding

The following parameters are monitored on the OC-3 interface:

• LOS

• LOF

• AIS-L

• RFI-L (FERF)

• Signal degrade (BER)

• Signal fail (BER).

Performance monitoring

SONET line and path performance monitoring complies with the standards outlined in GR-253-CORE. For detailed PM parameter thresholds on the OC-3 interface, refer to Appendix B of this document.

365-372-300

Issue 8.0, September 2006

1 0 - 2 3

Technical Specifications

Dual OC-12 Low-speed OLIU (LNW46)

Optical specification

The LNW46 optics meet or exceed SONET OC-12, long-reach specifications (SONET LR-1). The distributed feedback laser (DFB) supplies a 1310 nm, scrambled NRZ-coded signal (622.08 Mb/s).

The LNW46 low-speed interface supports span lengths up to 53 km and is OSP hardened. Refer to the

SONET Optical Specifications: OC-3 and OC-12 Low-speed OLIUs (LNW36, LNW46)

section in this chapter for

detailed system, transmitter, receiver, and link budget specifications.

The LNW46 is being DA’d and will no longer be available as of

12/31/07.

Alarm thresholding

The following parameters are monitored at the low-speed OC-12 interface.

• LOF

• LOS

• AIS-L

• RFI-L (FERF)

• Signal Degrade (BER)

• Signal Fail (BER).

Performance monitoring

SONET line and path performance monitoring complies with the standards outlined in GR-253-CORE. For detailed PM parameter thresholds on the OC-12 interface, refer to Appendix B of this document.

1 0 - 2 4

365-372-300

Issue 8.0, September 2006

Technical Specifications

OC-12 High-speed OLIU (LNW48)

Optical specification

The LNW48 optics meet or exceed SONET OC-12 intermediate-reach specifications (SONET OC-12 IR-1). The multi-longitudinal-mode/Fabry-Perot (FP) laser supplies a 1310 nm, scrambled NRZ-coded signal (622.08 Mb/s).

The LNW48 high-speed interface supports span lengths up to 20 km and is OSP hardened. Refer to the

SONET Optical Specifications: OC-12

High-speed OLIUs (LNW48, LNW50, and LNW54)

section in this chapter for detailed system, transmitter, receiver, and link budget specifications.

Alarm thresholding

The following parameters are monitored at the OC-12 high-speed

(Network-side) interface.

• LOF

• LOS

• AIS-L

• RFI-L (FERF)

• Signal Degrade (BER)

• Signal Fail (BER).

Performance monitoring

SONET line and path performance monitoring complies with the standards outlined in GR-253-CORE. For detailed PM parameter thresholds on the OC-12 high-speed interface, refer to Appendix B of this document.

365-372-300

Issue 8.0, September 2006

1 0 - 2 5

Technical Specifications

Quad OC-12 Low-speed OLIU (LNW49)

Optical specification

The LNW49 OLIU uses Pluggable Transmission Module (PTM) optics.

PTM optics can be “plugged” into the circuit pack as they become needed. Because the optics are pluggable, different ranges are available. The LNW49 can be equipped with IR-1, LR-1, or LR-2 optics. These optics meet standard optical specs per Telcordia GR-253 and ITU G.957.

LNW49 is approved for OSP deployments.

The IR-1 optics available for this circuit pack also conform to SR-1 specifications. Thus, the LNW49 can also be employed in short reach applications.

The multi-longitudinal-mode/Fabry-Perot (FP) laser is used for short or intermediate-reach transmission. A single-longitudinal-mode/ distributed feedback (DFB) laser transmitter is employed in long-reach applications. The IR-1 and LR-1 PTM optics for the LNW49 supply a

1310 nm, scrambled non-return-to-zero (NRZ) coded signal (622.08

Mb/s). The LR-2 PTM optics for the LNW49 supply a 1550 nm, scrambled non-return-to-zero (NRZ) coded signal (622.08 Mb/s).

When equipped with IR-1 PTM optics, the LNW49 can span distances of 20 km.

When equipped with the LR-1 PTM optics, the LNW49 can span distances of 46 km.

When equipped with the LR-2 PTM optics, the LNW49 can span distances of 80 km.

Refer to the

SONET Optical Specifications: OC-3 OLIUs (LNW37 and

LNW45) with PTM pluggable optics

in this chapter for detailed system,

transmitter, receiver, and link budget specifications.

1 0 - 2 6

365-372-300

Issue 8.0, September 2006

Quad OC-12 Low-speed OLIU (LNW49)

Technical Specifications

Allowed Optics

The table below lists the PTM optics, also known as SFP optics, that may be used in the LNW49 circuit pack.

DMX utilizes Pluggable Transmission Module (PTM) optics on the

LNW49 circuit pack. To ensure proper optical performance, mechanical fit, compliance with EMC, and compliance with laser safety standards, the Lucent specified PTM transceivers listed in the table below must be used.

Table 10-4 PTM Optics for LNW49

Apparatus Code

OC12IR1-I1

OC12LR1-I1

OC12LR2-I1

Comcode

109453902

109467522

109604447

Description

OC12 PTM TRCVR

Intermediate Reach, IR-1

OC12 PTM TRCVR

Long Reach, LR-1

OC12 PTM TRCVR

Long Reach, LR-2

Alarm thresholding

The following parameters are monitored on the OC-12 interface:

• LOS

• LOF

• AIS-L

• RFI-L (FERF)

• Signal degrade (BER)

• Signal fail (BER).

Performance monitoring

SONET line and path performance monitoring complies with the standards outlined in GR-253-CORE. For detailed PM parameter thresholds on the OC-12 interface, refer to Appendix B of this document.

365-372-300

Issue 8.0, September 2006

1 0 - 2 7

Technical Specifications

OC-12 High-speed OLIU (LNW50)

Optical specification

The LNW50 optics meet or exceed SONET OC-12 long-reach specifications (SONET OC-12 LR-1). The single-longitudinal-mode/distributed feedback laser (DFB) supplies a

1310 nm, scrambled NRZ-coded signal (622.08 Mb/s).

The LNW50 high-speed interface supports span lengths up to 53 km and is OSP hardened. Refer to the

SONET Optical Specifications: OC-12

High-speed OLIUs (LNW48, LNW50, and LNW54)

in this chapter for detailed system, transmitter, receiver, and link budget specifications.

Alarm thresholding

The following parameters are monitored at the OC-12 high-speed

(Network-side) interface.

• LOF

• LOS

• AIS-L

• RFI-L (FERF)

• Signal Degrade (BER)

• Signal Fail (BER).

Performance monitoring

1 0 - 2 8

365-372-300

Issue 8.0, September 2006

Technical Specifications

OC-12 High-speed OLIU (LNW54)

Optical specification

The LNW54 optics meet or exceed SONET OC-12 long-reach specifications (SONET OC-12 LR-2). The single-longitudinal-mode/distributed feedback laser (DFB) supplies a

1550 nm, scrambled NRZ-coded signal (622.08 Mb/s).

The LNW54 high-speed interface supports span lengths up to 81 km

and is OSP hardened. Refer to SONET Optical Specifications: OC-12

High-speed OLIUs (LNW48, LNW50, and LNW54): page 10-40 in

this chapter for detailed system, transmitter, receiver, and link budget specifications.

Alarm thresholding

The following parameters are monitored at the OC-12 high-speed

(Network-side) interface.

• LOF

• LOS

• AIS-L

• RFI-L (FERF)

• Signal Degrade (BER)

• Signal Fail (BER).

Performance monitoring

365-372-300

Issue 8.0, September 2006

1 0 - 2 9

Technical Specifications

OC-48 OLIU (DWDMs, LNW26B, LNW27, LNW28, LNW29,

LNW31, LNW32, LNW62, LNW76, and LNW77)

Overview

Refer to the following sections in this chapter for detailed system, transmitter, receiver, and link budget specifications.

•

SONET Optical Specifications: OC-48 OLIUs (LNW26B, LNW27,

LNW28, LNW29, LNW32)

•

SONET Optical Specifications: OC-48 OLIU (LNW62)

•

SONET Optical Specifications: OC-48 DWDM PTM Optical Specification

(LNW62)

•

SONET Optical Specifications: OC-48 OLIU (LNW76 and LNW77)

•

SONET Optical Specifications: OC-48 Low-Speed OLIU (LNW31)

•

OC-48 DWDM Optical Specification (LNW121B-LNW159B,

LNW221-LNW259, and LNW421-LNW459)

Optical specification LNW26B, LNW27, LNW28 and LNW32

The high-speed LNW26B, LNW27, LNW28, and LNW32 OC-48 meet or exceed SONET OC-48 1310 nm LR-1 specifications.

The LNW28 and LNW32 are hardened for outside plant (OSP) temperature ranges. The LNW28 will no longer be available as of

5/17/06.

These interfaces supports span lengths up to 51 km (LNW28 and

LNW32 support spans of 49 km in OSP environments).

LNW29

The high-speed LNW29 meets or exceeds SONET OC-48 1550 LR-2 specifications.

These interfaces supports span lengths up to 81 km.

LNW31 and LNW77

The low-speed LNW31 and high-speed LNW77 meet or exceed

SONET OC-48 1310 nm IR-1 specifications.

These interfaces support span lengths up to 20 km.

1 0 - 3 0

365-372-300

Issue 8.0, September 2006

OC-48 OLIU (DWDMs, LNW26B, LNW27, LNW28, LNW29,

LNW31, LNW32, LNW62, LNW76, and LNW77)

Technical Specifications

LNW62

The low-speed LNW62 provides 4 PTM (also known as SFP) ports capable of supporting 1.3LR-1 and 1.5LR-2 PTMs. The LR-1 PTMs conform to SONET OC-48 1310 nm LR-1 specifications. The LR-2

PTMs conform to SONET OC-48 1550 nm LR-2 specifications.

When equipped with the LR-1 PTM optics, the LNW62 can span distances of 40 km.

When equipped with the LR-2 PTM optics, the LNW62 can span distances of 80 km.

LNW76

The high-speed LNW76 meets or exceeds SONET OC-48 1310 nm

SR-1 specifications. These interfaces support span lengths up to 2 km.

LNW121B through LNW159B, and LNW221 through LNW259

These are high-speed Dense Wavelength Division Multiplexing

(DWDM) 100 GHz-spacing OLIUs that exceed SONET OC-48 1550

LR-2 specifications. The difference between the LNW121B-159B series and the LNW221- LNW259 is the size of the VT switch fabric.

The LNW121B- LNW159 series can cross-connect VTs in any 12 of 48 selected STS-1s. LNW221- LNW259 can cross-connect VTs in all 48

STS-1s.

Without passive filters, these interfaces can support span lengths up to

85 km.

The LNW121B, 123B, 131B, 133B, 135B, 137B, 143B, 145B, 147B,

149B, 157B, and 159B packs are no longer available. All other 100 series packs will still be available. The LNW221, 243, and 257 packs are no longer available. All other 200 series packs will still be available.

LNW421 through LNW459

These are low-speed Dense Wavelength Division Multiplexing

(DWDM) 100 GHz-spacing OLIUs that exceed SONET OC-48 1550

LR-2 specifications. The low-speed LNW421- LNW459 series can cross-connect VTs in any 12 of 48 selected STS-1s.

Without passive filters, these interfaces can support span lengths up to

85 km.

The LNW421, 423, 431, 433, 435, 437, 443, 445, 457 packs are no longer available. All other 400 series packs are still available.

365-372-300

Issue 8.0, September 2006

1 0 - 3 1

OC-48 OLIU (DWDMs, LNW26B, LNW27, LNW28, LNW29,

LNW31, LNW32, LNW62, LNW76, and LNW77)

Alarm thresholding

Technical Specifications

The following parameters are monitored on the OC-48 interface:

• LOS

• LOF

• AIS-L

• RFI-L (FERF)

• Line AIS

• Signal Degrade (BER)

• Signal Fail (BER).

Performance monitoring

SONET line and path performance monitoring complies with the standards outlined in GR-253-CORE. For detailed PM parameter thresholds on the OC-48 interface, Appendix B of this document.

1 0 - 3 2

365-372-300

Issue 8.0, September 2006

Technical Specifications

OC-192 OLIUs (LNW56, LNW57, LNW58, LNW59, LNW60,

LNW523, LNW527, LNW554, and LNW555)

Optical specification

This section briefly details the optical specifications for the OC-192 circuit packs.

LNW59

The LNW59 provides 2 ports capable of supporting 1.3SR1, 1.5IR2, and 1.5LR2 PTM/XFPs.

The SR-1 PTMs conform to SONET OC-192 1310 nm SR-1 specifications. The IR-2 and LR-2 PTMs conform to SONET OC-192

1.5-IR2 and 1.5-LR2 specifications respectively.

When equipped with SR-1 PTM optics, the LNW59 can span distances of 2 km.

When equipped with the IR-2 PTM optics, the LNW59 can span distances of 40 km.

When equipped with the LR-2 PTM optics, the LNW59 can span distances of 80 km.

LNW56

These are high-speed, intermediate reach OLIUs that meet or exceed

SONET OC-192 1550 IR-2 specifications. The LNW56 circuit pack bridges span lengths up to 40 km. The LNW56 transmits in the general

1550 nm range.

LNW57 and LNW60

The LNW57 and LNW60 OC-192 OLIU circuit packs are high-speed, long-reach OLIUs that adhere to a modified GR-253 OC-192 LR-2 standard. The LNW57 and LNW60 transmit a single wavelength at

1533.465 nm (channel 55).

The LNW57 can support span lengths of up to 92 km. The LNW60 utilizes an on-board amplifier module to bridge spans of up to 124 km.

The LNW57 and LNW60 circuit packs utilize a “dither tone” to frequency modulate the laser. This technique is used to minimize the effects of Stimulated Brillouin Scattering (SBS).

At high optical launch powers, SBS can cause an acoustic back-scattering phenomenon in fibers. The dither tone effectively broadens the spectrum of the narrow optical pulse, thus raising the threshold power where SBS becomes an issue.

365-372-300

Issue 8.0, September 2006

1 0 - 3 3

OC-192 OLIUs

Technical Specifications

Normally, Lucent recommends that the optical output of the OC-192 circuit packs be amplified to no more than +10 dBm. However, with the dither tone circuit incorporated into the LNW57 and LNW60, optical amplification of these circuit packs to higher power levels is acceptable.

For fibers carrying multiple wavelengths in DWDM systems, it should be noted that the individual channel (individual wavelength) power determines the SBS threshold, not the total composite power of all the channels.

LNW58 (optical interface for intra-office applications)

These are high-speed, very short reach (VSR) OC-192 OLIUs that meet or exceed ITU G.693 VSR600-2R1 specifications. The LNW56 circuit pack bridges span lengths up to 600 meters. The LNW58 transmits in the general 1310 nm range.

LNW523, LNW527, and LNW554

The LNW523/527/554 circuit packs are DWDM, high-speed, long-reach OLIUs that adhere to a modified GR-253 LR-2 standard.

Without passive filters, the LNW523/527/554 can bridge span lengths up at 92 km.

The LNW523/527/554 employ tunable lasers that support 4 separate wavelengths on each of the three packs. With a simple adjustment, the

LNW523/527/554 lasers can be made to transmit different wavelengths. This feature offers obvious advantages to single frequency circuit packs in that one pack may be ordered and used to support a variety of frequency requirements. Packs can be reused in new applications requiring different wavelengths and thus the need to order new packs simply to support different wavelengths can, in some cases, be avoided.

The LNW523 is being DA’d and will no longer be available as of

6/30/07.

LNW555

The LNW555 is a DWDM, high-speed, long-reach OLIU that adheres to a modified GR-253 OC-192 LR-2 standard. The LNW555 can be used as a generic long-reach (80 km) OLIU or as a single wavelength

DWDM OLIU. When used as a generic, long-reach OLIU (without passive filters), the LNW555 circuit pack bridges span lengths up to 81 km. The LNW555 transmits a single wavelength at 1533.465 nm

(channel 55).

1 0 - 3 4

365-372-300

Issue 8.0, September 2006

OC-192 OLIUs

Technical Specifications

Reference

Refer to the following sections for detailed system, transmitter, receiver, and link budget specifications:

•

SONET Optical Specifications: OC-192 OLIU (LNW59)

•

SONET Optical Specifications: OC-192 OLIU (LNW57 and LNW60)

•

SONET Optical Specifications: OC-192 OLIU (LNW56 and LNW58)

•

DWDM OC-192 OLIUs (LNW523, LNW527, LNW554, and LNW555)

Optical Specification

Alarm thresholding

The following parameters are monitored on the OC-192 interface:

• LOS

• LOF

• AIS-L

• RFI-L (FERF)

• Line AIS

• Signal Degrade (BER)

• Signal Fail (BER).

Performance monitoring

SONET line and path performance monitoring complies with the standards outlined in GR-253-CORE. For detailed PM parameter thresholds on the OC-192 interface, refer to Appendix B of this document.

365-372-300

Issue 8.0, September 2006

1 0 - 3 5

Technical Specifications

SONET Optical Specifications: OC-3 and OC-12 Low-speed OLIUs

(LNW36, LNW46)

Overview

The following tables present the optical specifications for the OC-3

LNW36 low-speed OLIU, and the OC-12 LNW46 low-speed OLIU.

System specifications

The table below lists the LNW36 and LNW46 OLIU system specifications.

Table 10-5 SONET Optical System Specifications

System Information

Optical Line Rate

Optical Line Coding

Optical Wavelength

Performance

Temperature Range

LNW36

155.52 Mb/s

Scrambled NRZ

1310nm

SONET OC-3

LR-1 (Long Reach)

OSP Hardened

LNW46

622.08 Mb/s

Scrambled NRZ

1310 nm

SONET OC-12 LR-1

(Long Reach)

OSP Hardened

1 0 - 3 6

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-3 and OC-12

OLIUs

Technical Specifications

Transmitter specifications

The table below lists the LNW36 and LNW46 OLIU transmitter information.

Table 10-6 SONET Optical Transmitter Information

Transmitter Information

Optical Device Temperature

Controller

FDA Classification

Optical Source

Faceplate Optical Connector

LNW36

None

Class I

Distributed Feed-Back

(DFB)/ Fabry Perot (FP)

Laser

LC connector

LNW46

None

Class I

Distributed

Feed-Back (DFB)

Laser

LC connector

Receiver specifications

The table below lists the OLIU receiver information.

Table 10-7 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

LNW36

InGaAsP PIN

LC connector

LNW46

InGaAsP PIN

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 3 7

SONET Optical Specifications: OC-3 and OC-12

OLIUs

Link budgets

Technical Specifications

The table below lists the LNW36 and LNW46 OLIU link budgets.

Table 10-8 SONET Optical Specifications and Link Budgets

Parameter

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width (

∆λ

)

Maximum RMS Spectral Width

(

)

Minimum Side Mode Suppression

Ratio (SSR)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

Minimum Received Power

BER of 1x10

(-12)

)

System Gain (see Note 2)

Optical Path Penalty

(see Note 3)

Additional Connector Loss

Margin (see Note 4)

Additional Unallocated Margin

(see Note 5)

Minimum Loss Budget

(see Note 6)

Maximum Loss Budget

(see Note 7)

Approximate Span Length

(see Note 8)

LNW36

OC-3 LR-1

(Note 1)

1280 nm

1335 nm

1.0 nm

30 dB

0.0 dBm

-5.0 dBm

0.0 dBm

-34.0 dBm

29.0 dB

1.0 dB

1.5 dB

0.0 dB

25.0 dB

55 km

LNW46

OC-12 LR-1

(Note 1)

1280 nm

1335 nm

1.0 nm

30 dB

+2.0 dBm

-2.5 dBm

-7.0 dBm

-30.5 dBm

28.0 dB

1.0 dB

1.5 dB

9.0 dB

24.0 dB

53 km

NOTES

1.All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life.

2.The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

1 0 - 3 8

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-3 and OC-12

OLIUs

Technical Specifications

3.Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310 nm optics is normally 1.0 dB.

4.One additional connector (0.75 dB) on each end is assumed to connect station cable to outside plant.

5.Additional unallocated margin, or safety margin, can be 0-3 dB.

Typically, a 1.5 dB value is assumed.

6.For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

7.The stated maximum loss budget equals the System Gain, less the

Optical Path Penalty, the Additional Connector Loss Margin, and the

Additional Unallocated Margin. The resultant Maximum Loss Budget is available for station cable loss, transmission cable loss, and splice loss.

8.The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.45 dB/km is used for 1310 nm optics.

This estimate includes typical cable loss (0.40 dB/km) and up to 11 splice losses (0.2 dB per splice). For 1310 nm OC-3 and OC-12 systems, dispersion is not a limiting factor, and the applications are attenuation-limited. Approximate span lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

365-372-300

Issue 8.0, September 2006

1 0 - 3 9

Technical Specifications

SONET Optical Specifications: OC-12 High-speed OLIUs (LNW48,

LNW50, and LNW54)

Overview

The following tables present the optical specifications for the OC-12

LNW48, LNW50, and LNW54 high-speed OLIUs.

System specifications

The table below lists the OC-12 LNW48, LNW50, and LNW54 system specifications.

Table 10-9 SONET Optical System Specifications

System

Information

LNW48

Optical Line Rate 622.08 Mb/s

Optical Line Coding Scrambled NRZ

Optical Wavelength 1310 nm

Performance SONET OC-12 IR-1

(Intermediate Reach)

Temperature Range OSP Hardened

LNW50 LNW54

622.08 Mb/s

Scrambled NRZ

622.08 Mb/s

Scrambled NRZ

1310 nm 1550 nm

SONET OC-12

LR-1 (Long Reach)

SONET OC-12

LR-2 (Long Reach)

OSP Hardened OSP Hardened

1 0 - 4 0

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-12 High-speed OLIUs (LNW48,

LNW50, and LNW54)

Technical Specifications

Transmitter specifications

The table below lists the OC-12 LNW48, LNW50, and LNW54 transmitter information.

Table 10-10 SONET Optical Transmitter Information

Transmitter Info.

Optical Device

Temperature

Controller

FDA Classification

Optical Source

Faceplate Optical

Connector

LNW48

None

Class I

Fabry Perot

(FP) Laser

LC connector

LNW50

None

Class I

Distributed

Feed-Back

(DFB) Laser

LC connector

LNW54

None

Class I

Distributed

Feed-Back

(DFB) Laser

LC connector

Receiver specifications

The table below lists the OC-12 LNW48, LNW50, and LNW54 receiver information.

Table 10-11 SONET Optical Receiver Information

Receiver

Information

Optical Detector

Faceplate Optical

Connector

LNW48

InGaAsP PIN

LC connector

LNW50

InGaAsP PIN

LC connector

LNW54

InGaAsP PIN

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 4 1

SONET Optical Specifications: OC-12 High-speed OLIUs (LNW48,

LNW50, and LNW54)

Technical Specifications

Link budgets

The table below lists the OC-12 LNW48, LNW50, and LNW54 link budgets.

Table 10-12 SONET Optical Specifications and Link Budgets

Parameter

Minimum Wavelength

Maximum Wavelength

LNW48

OC-12 IR-1

(Note 1)

1274 nm

(1293 nm)

1356 nm

(1334 nm)

Maximum Spectral Width

(

∆λ

)

Maximum RMS Spectral

Width (

)

Minimum Side Mode

Suppression Ratio (SSR)

2.5 nm

(4.0 nm)

Maximum Transmitter Power -8.0 dBm

Minimum Transmitter Power -15.0 dBm

-8.0 dBm Maximum Received Power

Minimum Received Power

BER of 1x10

(-12)

)

-28.0 dBm

13.0 dB System Gain (see Note 2)

Optical Path Penalty

(see Note 3)

Additional Connector Loss

Margin (see Note 4)

Additional Unallocated

Margin (see Note 5)

Minimum Loss Budget

(see Note 6)

Maximum Loss Budget

(see Note 7)

Approximate Span Length

(see Note 8)

1.0 dB

1.5 dB

0.0 dB

9.0 dB

20 km

LNW50

OC-12 LR-1

(Note 1)

LNW54

OC-12 LR-2

(Note 1)

1280 nm

1335 nm

1.0 nm

30 dB

+2.0 dBm

-2.5 dBm

-7.0 dBm

-30.5 dBm

28.0 dB

1.0 dB

1.5 dB

9.0 dB

24.0 dB

53 km

1480 nm

1580 nm

1.0 nm

30 dB

+2.0 dBm

-3.0 dBm

-8.0 dBm

-29.0 dBm

26.0 dB

1.0 dB

1.5 dB

10.0 dB

22.0 dB

81 km

1 0 - 4 2

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-12 High-speed OLIUs (LNW48,

LNW50, and LNW54)

Technical Specifications

NOTES

1.All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life.

2.The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

3.Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. At OC-12 rates, the optical path penalty is normally 1.0 dB for both 1310 nm and 1550 nm optics.

4.One additional connector (0.75 dB) on each end is assumed to connect station cable to outside plant.

5.Additional unallocated margin, or safety margin, can be 0-3 dB.

Typically, a 1.5 dB value is assumed.

6. For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

7.The stated maximum loss budget equals the System Gain, less the

Optical Path Penalty, the Additional Connector Loss Margin, and the

Additional Unallocated Margin. The resultant Maximum Loss Budget is available for station cable loss, transmission cable loss, and splice loss.

8.The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.45 dB/km is used for 1310 nm optics.

This estimate includes typical cable loss (0.40 dB/km) and up to 11 splice losses (0.2 dB per splice). For 1550 nm optics, an attenuation of 0.27 dB/km is used. Again, appropriate fiber-cable loss and numerous splice losses are included. For 1310 nm OC-3 and OC-12 systems, dispersion is not a limiting factor, and the applications are attenuation-limited. Approximate span lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

365-372-300

Issue 8.0, September 2006

1 0 - 4 3

Technical Specifications

SONET Optical Specifications: OC-3 OLIUs (LNW37 and LNW45) with PTM pluggable optics

Overview

The following tables present the optical specifications for the OC-3

LNW37 and LNW45 OLIUs.

System specifications

DMX utilizes Pluggable Transmission Module (PTM) optics on the

LNW37 and LNW45 circuit packs. To ensure proper optical performance, mechanical fit, compliance with EMC, and compliance with laser safety standards, the Lucent specified PTM transceivers must be used.

Only the Lucent specified PTM transceivers are compatible with DMX software. If non-Lucent specified PTM transceivers are installed in

DMX, the system will reject that transceiver, and that optical port will become inoperable (until approved parts are installed).

Refer to Chapter 7 or

Allowed Optics

for specific ordering information concerning these transceivers.

Laser Safety CAUTION!

Use only the Lucent specified Class 1 transceivers.

The table below lists the LNW37 and LNW45 OLIU system specifications.

Table 10-13 SONET Optical System Specifications

System Information

Optical Line Rate

Optical Line Coding

Optical Wavelength

Performance

Temperature Range

LNW37/45

155.52 Mb/s

Scrambled NRZ

1310 nm

PTM Optics for SONET OC-3 SR-1 (Short Reach),

IR-1 (Intermediate Reach), and LR-1 (Long Reach)

OSP

1 0 - 4 4

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-3 OLIUs (LNW37 and LNW45) with PTM pluggable optics

Technical Specifications

Transmitter specifications

The table below lists the LNW37/45 OLIU transmitter information.

Table 10-14 SONET Optical Transmitter Information

Transmitter Info.

Optical Device Temperature

Controller

FDA Classification

Optical Source

(FP for SR and IR, LED for SR only, FP or DFB for LR)

Faceplate Optical Connector

LNW37/45

None

Class I

Distributed Feed-Back (DFB)/

Fabry Perot (FP)/ Light Emitting

Diode (LED)

Laser

LC connector

Receiver specifications

The table below lists the OLIU receiver information.

Table 10-15 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

LNW37/45

InGaAsP PIN

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 4 5

SONET Optical Specifications: OC-3 OLIUs (LNW37 and LNW45) with PTM pluggable optics

Technical Specifications

Link budgets

The table below lists the LNW37/45 OLIU link budgets.

Table 10-16 SONET Optical Specifications and Link Budgets

Parameter

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width (

∆λ

)

Maximum RMS Spectral Width (

)

Minimum Side-Mode Suppression

Ratio (SSMR)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

Minimum Received Power

BER of 1x10

(-10)

)

System Gain (see Note 2)

Optical Path Penalty

(see Note 3)

Additional Connector Loss margin

(see Note 4)

Additional Unallocated Margin

(see Note 5)

Minimum Loss Budget

(see Note 6)

Maximum Loss Budget

(see Note 7)

Approximate Span Length

(see Note 8)

LNW37/45

OC-3 SR-1

(Note 1)

LNW37/45

OC-3 IR-1

(Note 1)

FP /LED Laser FP Laser

1260 nm

1360 nm

40/80 nm

1261 nm

1360 nm

7.7 nm

-8.0 dBm

-15.0 dBm

-8.0 dBm

-23.0 dBm

8.0 dB

1.0 dB

1.5 dB

0 dB

4.0 dB

2 km

-8.0 dBm

-15.0 dBm

-8.0 dBm

-28.0 dBm

13.0 dB

1.0 dB

1.5 dB

0 dB

9.0 dB

20 km

LNW37/45

OC-3 LR-1

(Note 1)

FP / (DFB) Laser

1263 nm

1360 nm

NA / (1.0 nm)

3.0 nm / (NA)

NA / (30 dB)

0.0 dBm

-5.0 dBm

-10.0 dBm

-34.0 dBm

29.0 dB

1.0 dB

1.5 dB

10.0 dB

25.0 dB

55 km

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life. Optical specifications meet or exceed

1 0 - 4 6

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-3 OLIUs (LNW37 and LNW45) with PTM pluggable optics

Technical Specifications

equivalent GR-253-CORE requirements.

2. The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

3. Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310 nm optics is normally 1.0 dB.

4. One additional connector (0.75 dB) on each end is assumed to connect station cable to outside plant.

5. Additional unallocated margin, or safety margin, can be 0-3 dB.

Typically, a 1.5 dB value is assumed.

6. For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

7. The stated maximum loss budget equals the System Gain, less the

Optical Path Penalty. The resultant Maximum Loss Budget is available for station cable loss, transmission cable loss, and splice loss.

8. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.45 dB/km is used for 1310 nm optics. This estimate includes typical cable loss (0.40 dB/km) and up to 11 splice losses (0.2 dB per splice). For 1310 nm OC-3 and OC-12 systems, dispersion is not a limiting factor, and the applications are attenuation-limited. Approximate span lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

365-372-300

Issue 8.0, September 2006

1 0 - 4 7

Technical Specifications

SONET Optical Specifications: OC-12 OLIUs (LNW49) with PTM pluggable optics

Overview

The following tables present the optical specifications for the LNW49

OC-12 OLIU.

DMX utilizes Pluggable Transmission Module (PTM) optics on the

LNW49 circuit packs. To ensure proper optical performance, mechanical fit, compliance with EMC, and compliance with laser safety standards, the Lucent specified PTM transceivers must be used.

Only the Lucent specified PTM transceivers are compatible with DMX software. If non-Lucent specified PTM transceivers are installed in

DMX, the system will reject that transceiver, and that optical port will become inoperable (until approved parts are installed).

Refer to Chapter 7 or

Allowed Optics

(LNW49) for specific ordering information concerning these transceivers.

Laser Safety CAUTION!

Use only the Lucent specified Class 1 transceivers.

System specifications

The table below lists the LNW49 OLIU system specifications.

Table 10-17 SONET Optical System Specifications

System Information LNW49

Optical Line Rate

Optical Line Coding

622.08 Mb/s

Scrambled NRZ

Optical Wavelength

Performance

Temperature Range

1310 nm (1550 nm for LR-2)

PTM Optics for SONET OC-12

IR-1 (Intermediate Reach),

LR-1 (Long Reach), and

LR-2 (Very Long Reach)

OSP

1 0 - 4 8

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-12 OLIUs (LNW49) with PTM pluggable optics

Technical Specifications

Transmitter specifications

The table below lists the LNW49 OLIU transmitter information.

Table 10-18 SONET Optical Transmitter Information

Transmitter Info.

Optical Device Temperature

Controller

FDA Classification

Optical Source

(FP for SR and IR, FP or DFB for

LR)

Faceplate Optical Connector

LNW49

None

Class I

Distributed Feed-Back (DFB)/

Fabry Perot (FP)

Laser

LC connector

Receiver specifications

The table below lists the OLIU receiver information.

Table 10-19 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

LNW49

InGaAsP PIN

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 4 9

SONET Optical Specifications: OC-12 OLIUs (LNW49) with PTM pluggable optics

Link budgets

The table below lists the LNW49 OLIU link budgets.

Technical Specifications

Table 10-20 SONET Optical Specifications and Link Budgets

Parameter

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width (

∆λ

)

Maximum RMS Spectral Width (

)

Minimum Side-Mode Suppression

Ratio (SSMR)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

Minimum Received Power

BER of 1x10

(-10)

)

System Gain (see Note 2)

Maximum Dispersion

Optical Path Penalty

(see Note 3)

Minimum Loss Budget

(see Note 5)

Maximum Loss Budget

(see Note 6)

Approximate Span Length

(see Note 7)

LNW49

OC-12 IR-1

(Note 1)

FP Laser

1274 nm

1356 nm

2.5 nm

-8.0 dBm

-15.0 dBm

-8.0 dBm

-28.0 dBm

13.0 dB

1.0 dB

0 dB

12.0 dB

15 km

LNW49

OC-12 LR-1

(Note 1)

DFB Laser

1280 nm

1335 nm

1.0 nm

30 dB

+2.0 dBm

-3.0 dBm

-8.0 dBm

-28.0 dBm

25.0 dB

1.0 dB

10.0 dB

24.0 dB

40 km

LNW49

OC-12 LR-2

(Note 1)

DFB Laser

1480 nm

1580 nm

1.0 nm

30 dB

+2.0 dBm

-3.0 dBm

-8.0 dBm

-28.0 dBm

25.0 dB

1600 ps/nm

1.5 dB

10.0 dB

21.0 dB

80 km

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life. Optical specifications meet or exceed equivalent GR-253-CORE requirements.

2. The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

3. Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310

1 0 - 5 0

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-12 OLIUs (LNW49) with PTM pluggable optics

Technical Specifications

nm optics is normally 1.0 dB.

4. One additional connector (0.75 dB) on each end is assumed to connect station cable to outside plant.

5. For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

6. The stated maximum loss budget equals the System Gain, less the

Optical Path Penalty. The resultant Maximum Loss Budget is available for station cable loss, transmission cable loss, and splice loss.

7. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.45 dB/km is used for 1310 nm optics. This estimate includes typical cable loss (0.40 dB/km) and up to 11 splice losses (0.2 dB per splice). For 1310 nm OC-3 and OC-12 systems, dispersion is not a limiting factor, and the applications are attenuation-limited. Approximate span lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

365-372-300

Issue 8.0, September 2006

1 0 - 5 1

Technical Specifications

SONET Optical Specifications: OC-48 OLIUs (LNW26B, LNW27,

LNW28, LNW29, LNW32)

Overview

The following tables present the optical specifications for the OC-48

OLIUs.

System specifications

The table below lists the OC-48 OLIU system specifications.

Table 10-21 SONET Optical System Specifications

System Information LNW26B

Optical Line Rate

Optical Line Coding

Optical Wavelength

Performance

Temperature Range Central Office

(CO)

LNW27

1310 nm

SONET LR-1 (Long Reach)

LNW28

OSP Hardened

LNW29

2.488 Gb/s

Scrambled NRZ

1550 nm

SONET LR-2

(Long Reach)

LNW32

1310 nm

SONET LR-1

(Long Reach)

OSP Hardened

Transmitter specifications

The table below lists the OC-48 OLIU transmitter information.

Table 10-22 SONET Optical Transmitter Information

Transmitter Info.

Optical Device

Temperature Controller

FDA Classification

Optical Source

Faceplate Optical

Connector

LNW26B LNW27 LNW28

None

LNW29

Class I

Distributed Feed-Back (DFB) Laser

LC connector

LNW32

1 0 - 5 2

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-48 OLIUs

(LNW26B, LNW27, LNW28, LNW29, LNW32)

Technical Specifications

Receiver Specifications

The table below lists the OC-48 OLIU receiver information.

Table 10-23 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

LNW26B LNW27 LNW28 LNW29 LNW32

APD

LC connector

Link budgets

The table below lists the OC-48 OLIU link budgets.

Table 10-24 SONET Optical Specifications and Link Budgets

Parameter (NOTE 1)

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width (

∆λ

)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

(1x10

-12

BER)

Minimum Received Power

(1x10

-12

BER)

Minimum System Gain (see Note 2)

LNW26B

OC-48

LR-1

1280 nm

1335 nm

1.0 nm

1335 nm

1.0 nm

+3.0 dBm +3.0 dBm +3.0 dBm +3.0 dBm +3.0 dBm

-2.0 dBm

-8.0 dBm

LNW27

OC-48

LR-1

1280 nm

1335 nm

1.0 nm

-2.0 dBm

-8.0 dBm

LNW28

OC-48

LR-1

1280 nm

1335 nm

1.0 nm

-2.0 dBm

-8.0 dBm

LNW29

OC-48

LR-2

1500 nm

1580 nm

1.0 nm

-2.0 dBm

-8.0 dBm

LNW32

OC-48

LR-1

1280 nm

-2.0 dBm

-8.0 dBm

Dispersion

-29.0 dBm -29.0 dBm -29.0/-28.0 dBm*

27.0 dB 27.0 dB

NA NA

27.0/26.0

dB*

1.0 dB 1.0 dB 1.0 dB

-29.0 dBm -29.0/-28.0 dBm*

27.0 dB

1600 ps/nm

27.0/26.0

dB*

2.0 dB 1.0 dB

1.5 dB 1.5 dB 1.5 dB 1.5 dB 1.5 dB

Optical Path Penalty (see Note 3)

Additional Connector Loss Margin

(see Note 4)

Additional Unallocated Margin

(see Note 5)

Minimum Loss Budget (see Note 6)

Maximum Loss Budget (see Note 7)

1.5 dB

11.0 dB

23.0 dB

1.5 dB

11.0 dB

23.0 dB

1.5 dB

11.0 dB

23.0/22.0* dB

1.5 dB

11.0 dB

22.0 dB

1.5 dB

11.0 dB

23.0/22.0* dB

365-372-300

Issue 8.0, September 2006

1 0 - 5 3

SONET Optical Specifications: OC-48 OLIUs

(LNW26B, LNW27, LNW28, LNW29, LNW32)

Technical Specifications

Parameter (NOTE 1) LNW26B

OC-48

LR-1

LNW27

OC-48

LR-1

LNW28

OC-48

LR-1

LNW29

OC-48

LR-2

Approximate Span Length (see Note 8) 51 km 51 km 51/49 km* 81 km

*The LNW28 and LNW32 are environmentally hardened OLIUs (it is capable of operating in outside plant temperature ranges). The first number applies to deployments in standard CO applications; the second number applies to deployments where temperature excursions (found in OSP environments) may occur.

LNW32

OC-48

LR-1

51/49 km*

Notes

1. All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life (EOL). Optical specifications meet or exceed equivalent GR-253-CORE requirements.

2. The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

3. Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310 nm optics is 1.0 dB maximum. The optical path penalty for the 1550 nm optics is 2.0 maximum.

4. One additional connector (0.75 dB) on each end is assumed to connect station cable to outside plant.

5. Additional unallocated margin, or safety margin, can be 0-3 dB.

Typically, a 1.5 dB value is assumed.

6. For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

7. The stated maximum loss budget equals the System Gain, less the

Optical Path Penalty, the Additional Connector Loss Margin, and the

Additional Unallocated Margin. The resultant Maximum Loss

Budget is available for station cable loss, transmission cable loss, and splice loss.

8. The approximate Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.45 dB/km is used for 1310 nm optics.

dB/km is used. Again, appropriate fiber-cable loss and numerous splice losses are included. For long-reach 1550nm applications, dispersion may be a limiting factor. Approximate Span Lengths can

1 0 - 5 4

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-48 OLIUs

(LNW26B, LNW27, LNW28, LNW29, LNW32)

Technical Specifications

be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

365-372-300

Issue 8.0, September 2006

1 0 - 5 5

Technical Specifications

SONET Optical Specifications: OC-48 OLIU (LNW62)

Overview

The following tables present the optical specifications for the LNW62

OC-48 PTMs.

Allowed Optics

The table below lists the PTM optics, also known as SFP optics, that may be used in the LNW62 circuit pack.

To ensure proper optical performance, mechanical fit, compliance with

EMC, and compliance with laser safety standards, the Lucent specified

PTM transceivers listed in the table below must be used.

Table 10-25 PTM Optics for LNW62

Apparatus Code

OC48LR1-I1

OC48LR2-I1

Comcode

109493528

109504431

Description

OC48 PTM TRCVR

Long Reach, 1.3 LR-1 (40km),

1310nm

OC48 PTM TRCVR

Long Reach, 1.5 LR-2 (80km),

1550nm

1 0 - 5 6

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-48 OLIU

(LNW62)

Technical Specifications

System specifications

The following table lists the LNW62 PTM system specifications.

Table 10-26 SONET Optical System Specifications

System Information

Optical Line Rate

Optical Line Coding

Optical Wavelength

Performance

Temperature Range

LNW62

2.488 Gb/s

Scrambled NRZ

1310 nm

SONET LR-1 (Long

Reach)

OSP hardened

2.488 Gb/s

Scrambled NRZ

1550 nm

SONET LR-2 (Long

Reach)

OSP hardened

Transmitter specifications

The following table lists the LNW62 PTM OLIU transmitter information.

Table 10-27 SONET Optical Transmitter Information

Transmitter Info.

LNW62

Optical Device Temperature

Controller

FDA Classification

Optical Source

Faceplate Optical Connector

SONET LR-1

None

Class I

Distributed Feed-Back

(DFB) Laser

LC connector

SONET LR-2

None

Class I

Distributed Feed-Back

(DFB) Laser

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 5 7

SONET Optical Specifications: OC-48 OLIU

(LNW62)

Technical Specifications

Receiver specifications

The following table lists the LNW62 PTM receiver information.

Table 10-28 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

SONET LR-1

InGaAsP PIN

LC connector

LNW62

SONET LR-2

APD

LC connector

1 0 - 5 8

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-48 OLIU

(LNW62)

Technical Specifications

Link budgets

The following table lists the LNW62 PTM link budgets. Text inserts in parenthesis under the PTM name in each column denote the apparatus codes for the equivalent unified PTMs also available in R7.0.

Table 10-29 SONET Optical Specifications and Link Budgets

Parameter

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width (

∆λ

)

Maximum RMS Spectral Width (

)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

(1x10

-10

BER)

Minimum Received Power

(1x10

-10

BER)

Maximum Dispersion

Minimum System Gain

(see Note 2)

Optical Path Penalty

(see Note 3)

Additional Connector Loss margin

(see Note 4)

Additional Unallocated Margin

(see Note 5)

Minimum Loss Budget

Maximum Loss Budget

(see Note 6)

Approximate Span Length

(see Note 7)

LNW62

OC-48 LR-1

1280 nm

1335 nm

1.0 nm

3.0 dBm

-2.0 dBm

-9.0 dBm

-27.0 dBm

25.0 dB

1.0 dB

1.5 dB

12.0 dB

21.0 dB

46 km

LNW62

OC-48 LR-2

1500 nm

1580 nm

1.0 nm

3.0 dBm

-2.0 dBm

-9.0 dBm

-28.0 dB

1600 ps/nm

26.0 dB

2.0 dB

1.5 dB

12.0 dB

21.0 dB

78 km

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life (EOL). Optical specifications meet or

365-372-300

Issue 8.0, September 2006

1 0 - 5 9

SONET Optical Specifications: OC-48 OLIU

(LNW62)

Technical Specifications

exceed equivalent GR-253-CORE requirements.

2. The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

3. Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310 nm optics is normally 1.0 dB.

4. One additional connector (0.75 dB) on each end is assumed to connect station cable to outside plant.

5. Additional unallocated margin, or safety margin, can be 0-3 dB.

Typically, a 1.5 dB value is assumed.

6. For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

7. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.45 dB/km is used for 1310 nm optics.

This estimate includes typical cable loss (0.40 dB/km) and up to 11 splice losses (0.2 dB per splice). For 1310 nm OC-48 systems, dispersion is not a limiting factor, and the applications are attenuation-limited. Approximate Span Lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules. However, the short-reach MLM

(Multi-Longitudinal Mode— also known as Fabry Perot [FP]) laser is only recommended for spans of up to 2 km.

1 0 - 6 0

365-372-300

Issue 8.0, September 2006

Technical Specifications

SONET Optical Specifications: OC-48 OLIU (LNW76 and LNW77)

Overview

The following tables present the optical specifications for the LNW76 and LNW77 OC-48 OLIUs.

System specifications

The following table lists the LNW76 and LNW77 OC-48 OLIU system specifications.

Table 10-30 SONET Optical System Specifications

System Information

Optical Line Rate

Optical Line Coding

Optical Wavelength

Performance

Temperature Range

LNW76

2.488 Gb/s

Scrambled NRZ

1310 nm

SONET SR-1 (Short Reach)

Central Office (CO)

LNW77

2.488 Gb/s

Scrambled NRZ

1310 nm

SONET IR-1 (Intermediate Reach)

Central Office (CO)

Transmitter specifications

The following table lists the LNW76 and LNW77 OC-48 OLIU transmitter information.

Table 10-31 SONET Optical Transmitter Information

Transmitter Info.

Optical Device Temperature

Controller

FDA Classification

Optical Source

Faceplate Optical Connector

LNW76

None

Class I

Fabry-Perot (FP) Laser

LC connector

LNW77

None

Class I

Distributed Feed-Back (DFB) Laser

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 6 1

SONET Optical Specifications: OC-48 OLIU

(LNW76 and LNW77)

Technical Specifications

Receiver specifications

The following table lists the LNW76 and LNW77 OC-48 OLIU receiver information.

Table 10-32 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

LNW76

InGaAsP PIN

LC connector

LNW77

InGaAsP PIN

LC connector

1 0 - 6 2

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-48 OLIU

(LNW76 and LNW77)

Technical Specifications

Parameter

Link budgets

The following table lists the LNW76 and LNW77 OC-48 OLIU link budgets.

Table 10-33 SONET Optical Specifications and Link Budgets

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width (

∆λ

)

Maximum RMS Spectral Width (

)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

(1x10

-12

BER)

Minimum Received Power

(1x10

-12

BER)

Minimum System Gain

(see Note 2)

Optical Path Penalty

(see Note 3)

Additional Connector Loss Margin

(see Note 4)

Additional Unallocated Margin

(see Note 5)

Minimum Loss Budget

Maximum Loss Budget

(see Note 6)

Approximate Span Length

(see Note 7)

LNW76

OC-48 SR-1

1266 nm

1360 nm

4.0 nm

-3 dBm

-10 dBm

-3 dBm

-18 dBm

8 dB

1.0 dB

1.5 dB

0.0 dB

4.0 dB

2 km

LNW77

OC-48 IR-1

1280 nm

1335 nm

1.0 nm

0.0 dBm

-5.0 dBm

0.0 dBm

-18.0 dBm

13.0 dB

1.0 dB

1.5 dB

0.0 dB

9.0 dB

20 km

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life (EOL). Optical specifications meet or exceed equivalent GR-253-CORE requirements.

2. The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

365-372-300

Issue 8.0, September 2006

1 0 - 6 3

SONET Optical Specifications: OC-48 OLIU

(LNW76 and LNW77)

Technical Specifications

3. Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310 nm optics is normally 1.0 dB.

4. One additional connector (0.75 dB) on each end is assumed to connect station cable to outside plant.

5. Additional unallocated margin, or safety margin, can be 0-3 dB.

Typically, a 1.5 dB value is assumed.

6. For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

7. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.45 dB/km is used for 1310 nm optics.

(Multi-Longitudinal Mode— also known as Fabry Perot [FP]) laser is only recommended for spans of up to 2 km.

1 0 - 6 4

365-372-300

Issue 8.0, September 2006

Technical Specifications

SONET Optical Specifications: OC-48 Low-Speed OLIU (LNW31)

Overview

The following tables present the optical specifications for the low-speed (tributary interface) OC-48 OLIUs.

System specifications

The table below lists the low-speed OC-48 OLIU system specifications.

Table 10-34 SONET Optical System Specifications

System Information

Optical Line Rate

Optical Line Coding

Optical Wavelength

Performance

Temperature Range

LNW31

2.488 Gb/s

Scrambled NRZ

1310 nm

SONET IR-1 (Intermediate Reach)

Transmitter specifications

The table below lists the low-speed OC-48 OLIU transmitter information.

Table 10-35 SONET Optical Transmitter Information

Transmitter Info.

Optical Device

Temperature Controller

FDA Classification

Optical Source

Faceplate Optical

Connector

LNW31

None

Class I

Distributed Feed-Back (DFB) Laser

LC connector

Reciever Specifications

The table below lists the low-speed OC-48 OLIU receiver information.

Table 10-36 SONET Optical Receiver Information

Receiver Information

Optical Detector

LNW31

Faceplate Optical Connector LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 6 5

SONET Optical Specifications: OC-48

Low-Speed OLIU (LNW31)

Technical Specifications

Link budgets

The table below lists the low-speed OC-48 OLIU link budgets.

Table 10-37 Optical Specifications and Link Budgets

Parameter (NOTE 1)

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width (

∆λ

)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

(1x10

-12

BER)

Minimum Received Power

(1x10

-12

BER)

Minimum System Gain (see Note 2)

Dispersion

Optical Path Penalty (see Note 3)

Additional Connector Loss Margin

(see Note 4)

Additional Unallocated Margin

(see Note 5)

Minimum Loss Budget (see Note 6)

Maximum Loss Budget (see Note 7)

Approximate Span Length (see Note 8)

LNW31

OC-48 IR-1

1260 nm

1360 nm

1.0 nm

0.0 dBm

-5.0 dBm

0.0 dBm

-18.0 dBm

13.0 dB

1.0 dB

1.5 dB

0.0 dB

9.0 dB

20 km

Notes

1. All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life (EOL). Optical specifications meet or exceed equivalent GR-253-CORE requirements.

2. The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

4. One additional connector (0.75 dB) on each end is assumed to connect

1 0 - 6 6

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-48

Low-Speed OLIU (LNW31)

Technical Specifications

station cable to outside plant.

5. Additional unallocated margin, or safety margin, can be 0-3 dB.

Typically, a 1.5 dB value is assumed.

6. The LNW31 does not require an external lightguide build-out (optical attenuator) as part of the connector assembly for optical loopbacks.

7. The stated maximum loss budget equals the System Gain, less the

Optical Path Penalty, the Additional Connector Loss Margin, and the

Additional Unallocated Margin. The resultant Maximum Loss

Budget is available for station cable loss, transmission cable loss, and splice loss.

365-372-300

Issue 8.0, September 2006

1 0 - 6 7

Technical Specifications

OC-48 DWDM Optical Specification (LNW121B-LNW159B,

LNW221-LNW259, and LNW421-LNW459)

Overview

The following tables present the optical specifications for the OC-48

DWDM circuit packs.

System specifications

The following table lists the DWDM low-speed (tributary interface) and high-speed (network interface) system specifications.

Table 10-38 SONET Optical System Specifications

System Information

Optical Line Rate

Optical Line Coding

Optical Wavelength

Performance

Temperature Range

OC-48 low-speed DWDM Optics

(LNW421-LNW459)

2.488 Gb/s

Scrambled NRZ

1530 nm - 1560 nm

Customized LR-2 (for DWDM)

OC-48 high-speed DWDM Optics

(LNW121B-159B & LNW221-259)

2.488 Gb/s

Scrambled NRZ

1530 nm - 1560 nm

Customized LR-2 (for DWDM)

Important!

The LNW421, 423, 431, 433, 435, 437, 443, 445,

457 packs are no longer available. All other 400 series packs will still be available. The LNW121B, 123B, 131B, 133B, 135B,

137B, 143B, 145B, 147B, 149B, 157B, and 159B packs are no longer available. All other 100 series packs will still be available.

The LNW221, 243, and 257 packs are no longer available. All other 200 series packs will still be available.

1 0 - 6 8

365-372-300

Issue 8.0, September 2006

OC-48 DWDM Optics (LNW121B- LNW159B,

LNW221- LNW259, and LNW421-LNW459)

Technical Specifications

Transmitter specifications

The following table lists the DWDM optics transmitter information.

Table 10-39 SONET Optical Transmitter Information

Transmitter Info.

OC-48 low-speed DWDM Optics

(LNW421-LNW459)

Optical Device Temperature

Controller/Thermo-Electric

Cooler (TEC)

Transmission Medium

Yes

FDA Classification

Optical Source

Faceplate Optical Connector

Input Fiber:

Standard Single-Mode

Non-Dispersion Shifted Fiber

Output Fiber:

Standard Single-Mode

Non-Dispersion Shifted Fiber

Class I

Distributed Feed-Back (DFB) Laser or

Externally Modulated Laser (EML)

LC connector

OC-48 high-speed DWDM Optics

(LNW121B-159B & LNW221-259)

Yes

Input Fiber:

Standard Single-Mode

Non-Dispersion Shifted Fiber

Output Fiber:

Standard Single-Mode

Non-Dispersion Shifted Fiber

Class I

Distributed Feed-Back (DFB) Laser or

Externally Modulated Laser (EML)

LC connector

Receiver specifications

The following table lists the passive DWDM optics receiver information.

Table 10-40 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

OC-48 low-speed DWDM Optics

(LNW421-LNW459)

Avalanche Photodiode (APD)

LC connector

OC-48 high-speed DWDM

Optics

(LNW121B-159B & LNW221-259)

Avalanche Photodiode (APD)

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 6 9

OC-48 DWDM Optics (LNW121B- LNW159B,

LNW221- LNW259, and LNW421-LNW459)

Technical Specifications

Operating wavelengths

The table below lists the channel numbers, operating wavelengths, and frequencies that adhere to the ITU grid for the OC-48 DWDM OLIUs.

Table 10-41 OC-48 DWDM OLIUs Wavelength Plan

Port Unit

LNW121B, LNW221, & LNW421

LNW123B, LNW223, & LNW423

LNW125B, LNW225, & LNW425

LNW127B, LNW127, & LNW427

LNW131B, LNW231, & LNW431

LNW133B, LNW233, & LNW433

LNW135B, LNW235, & LNW435

LNW137B, LNW237, & LNW437

LNW143B, LNW243, & LNW443

LNW145B, LNW245, & LNW445

LNW147B, LNW247, & LNW447

LNW149B, LNW249, & LNW449

LNW153B, LNW253, & LNW453

LNW155B, LNW255, & LNW455

LNW157B, LNW257, & LNW457

LNW159B, LNW259, & LNW459

Channel #

1547.715

1546.917

1543.730

1542.936

1542.142

1541.349

1540.557

1539.766

1538.976

1538.186

1535.822

1535.036

1534.250

1533.465

1532.681

1531.898

1531.116

1530.334

Wavelength (nm)

1560.606

1559.794

1558.983

1558.173

1557.363

1556.555

1555.747

1554.940

1552.524

1551.721

1550.918

1550.116

1549.315

1548.515

193.70

193.80

194.20

194.30

194.40

194.50

194.60

194.70

194.80

194.90

195.20

195.30

195.40

195.50

195.60

195.70

195.80

195.90

Frequency (THz)

192.10

192.20

192.30

192.40

192.50

192.60

192.70

192.80

193.10

193.20

193.30

193.40

193.50

193.60

1 0 - 7 0

365-372-300

Issue 8.0, September 2006

OC-48 DWDM Optics (LNW121B- LNW159B,

LNW221- LNW259, and LNW421-LNW459)

Technical Specifications

Optical requirements and loss budgets

The table below lists the optical requirements and link budgets for the

OC-48 DWDM OLIUs.

Table 10-42 Optical Requirements and Link Budgets for the

OC-48 DWDM OLIUs

Parameter

Interface Type (Note 1)

DWDM Wavelength Range (100 GHz spacing)

Maximum Center Wavelength Deviation

Maximum Spectral Width

(∆λ

)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power (1x10

-12

BER)

Minimum Received Power (1x10

-12

BER)

Minimum System Gain (see Note 2)

Dispersion

Optical Path Penalty (see Note 3)

Additional Connector Loss Margin

(see Note 4)

Additional Unallocated Margin

(see Note 5)

Minimum Loss Budget (see Note 6)

Maximum Loss Budget (see Note 7)

LNW121B-159B, LNW221-259,

LNW421-459

OC-48 Custom LR-2 for DWDM

1530.334-1560.606 nm

+/- 100 picometers

(+/ 12.5 GHz)

0.5 nm

+2.0 dBm

-1.0 dBm

-8.0 dBm

-29.0 dBm

28.0 dB

1800 ps/nm

2.0 dB

1.5 dB

10.0 dB

23.0 dB

Approximate Span Length (see Note 8) 85 km*

*This span length assumes no passive optical unit (POU) is being used.

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life (EOL). Optical specifications meet or exceed equivalent GR-253-CORE requirements.

2. The System Gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

3. Optical path penalty includes effects of dispersion, reflection, and

365-372-300

Issue 8.0, September 2006

1 0 - 7 1

OC-48 DWDM Optics (LNW121B- LNW159B,

LNW221- LNW259, and LNW421-LNW459)

Technical Specifications

jitter that occur on the optical path. The optical path penalty for 1550 nm optics is normally 2.0 dB.

4. One additional connector (0.75 dB) on each end is assumed to connect station cable to outside plant.

5. Additional unallocated margin, or safety margin, can be 0-3 dB.

Typically, a 1.5 dB value is assumed.

6. For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

7. The stated maximum loss budget equals the System Gain, less the

Optical Path Penalty, the Additional Connector Loss Margin, and the

Additional Unallocated Margin. The resultant Maximum Loss

Budget is available for station cable loss, transmission cable loss, and splice loss. The stated maximum loss budget is conservative; i.e., if the additional connector loss margin and additional unallocated margin are not needed, an additional 3 dB budget is available.

8. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.27 dB/km is used for 1550 nm optics.

This estimate includes typical cable loss (0.22 dB/km) and up to 11 splice losses (0.2 dB per splice). For 1550 nm OC-48 systems, dispersion can also be a limiting factor. Approximate Span Lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

1 0 - 7 2

365-372-300

Issue 8.0, September 2006

Technical Specifications

SONET Optical Specifications: OC-192 OLIU (LNW59)

Overview

The following tables present the optical specifications for the PTM modules approved for the LNW59.

Allowed Optics

The table below lists the PTM optics, also known as SFP/XFP optics, that may be used in the LNW59 circuit pack.

To ensure proper optical performance, mechanical fit, compliance with

EMC, and compliance with laser safety standards, the Lucent specified

PTM transceivers listed in the table below must be used.

Table 10-43 PTM Optics for LNW59

Apparatus Code

X10GMC2

Comcode

109603704

Description

OC192 XFP TRCVR

Short Reach, 1.3 SR-1 (2km),

1310nm

X10GMC4 109603712

Intermediate Reach, 1.5 IR-2

(40km), 1550nm

X10GMC5 109603720

Long Reach, 1.5 LR-2 (80km),

1550nm

365-372-300

Issue 8.0, September 2006

1 0 - 7 3

SONET Optical Specifications: OC-192 OLIU

(LNW59)

Technical Specifications

System specifications

The table below lists the OC-192 OLIU system specifications.

Table 10-44 SONET Optical System Specifications

System Information

Optical Line Rate

Optical Line Coding

Optical Wavelength

Performance

Temperature Range

SR-1

9953.28 Mb/s

Scrambled NRZ

1310 nm

GR-253 OC-192 SR-1

(Short Reach)

Central Office

LNW59

IR-2

9953.28 Mb/s

Scrambled NRZ

1550 nm

GR-253 OC-192 IR-2

(Intermediate Reach)

Central Office

LR-2

9953.28 Mb/s

Scrambled NRZ

1550 nm

GR-253 OC-192 LR-2

(Long Reach)

Central Office

Transmitter Specifications

The table below lists the OC-192 OLIU transmitter information.

Table 10-45 SONET Optical Transmitter Information

Transmitter Info.

None

SR-1

None

LNW59

IR-2

None

LR-2

Optical Device

Temperature Controller

FDA Classification

Optical Source

Faceplate Optical

Connector

Class I

1310 nm, FP or DFB

Laser Structure

LC connector

Class I

1550 nm, ELM Laser

Structure

LC connector

Class I

1550 nm, ELM Laser

Structure

LC connector

1 0 - 7 4

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-192 OLIU

(LNW59)

Technical Specifications

Receiver specifications

The table below lists the OC-192 OLIU receiver information.

Table 10-46 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

SR-1

PIN Diode

LC connector

LNW59

IR-2

PIN Diode

LC connector

LR-2

APD

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 7 5

SONET Optical Specifications: OC-192 OLIU

(LNW59)

Technical Specifications

Link budgets

The table below lists the OC-192 PTM link budgets for the LNW59.

The text in parenthesis denotes the apparatus code for the unified PTM equivalent of each pack.

Table 10-47 Optical Specifications and Link Budgets

Parameter (Note 1)

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width

(

∆λ

)

Maximum RMS Spectral Width (

)

Minimum Side Mode Suppression Ratio

(SSR)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

Minimum Received Power

@ BER or 1x10

-12

Minimum System Gain

(see Note 2)

Maximum Dispersion

Optical Path Penalty (see Note 3)

Minimum Loss Budget

(see Note 4)

Maximum Loss Budget

(see Note 5)

Approximate Span Length

(see Note 6)

SR-1

1290 nm

1330 nm

1.0 nm

30 dBm

-1 dBm

-6 dBm

-1 dBm

-11 dBm

5 dB

+6.6 ps/nm

1.0 dB

0.0 dB

4.0 dB

2 km

LNW59

IR-2

1530 nm

1565 nm

1.0 nm

30 dB

+2.0 dBm

-1.0 dBm

-14.0 dBm

13.0 dB

+800 ps/nm

2.0 dB

3.0 dB

11.0 dB

40 km

24.0 dB

+1600 ps/nm

2.0 dB

11.0 dB

22.0 dB

80 km

LR-2

1530 nm

1565 nm

TBD

30 dB

+4.0 dBm

0.0 dBm

-7.0 dBm

-24.0 dBm

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3 and ITU

G.693. All values are worst-case end of life. Optical specifications meet or exceed equivalent GR-253-CORE requirements.

2. The system gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

1 0 - 7 6

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-192 OLIU

(LNW59)

Technical Specifications

3. Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310 nm is a maximum of 1.0 dB. The optical path penalty for 1550 nm is a maximum of 2.0 dB.

4. For all packs where the Minimum Loss Budget (MLB) is 0, no attenuator is required for loopbacks. For all packs where the MLB is greater than 0, an attenuator is required. The value of the LBO shall be equal to or greater than the MLB. The MLB is found in the table above.

5. The stated maximum loss budget equals the miniumum system gain, minus the optical path penalty. Maximum loss budget is available for both station and transmission cable and splices.

6. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.27 dB/km is used for 1550 nm optics.

This estimate includes typical cable loss (0.22 dB/km) and up to 11 splice losses (0.2 dB per splice). For 1550 nm OC-192 systems, dispersion can also be a limiting factor. Approximate Span Lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

365-372-300

Issue 8.0, September 2006

1 0 - 7 7

Technical Specifications

SONET Optical Specifications: OC-192 OLIU (LNW56 and LNW58)

Overview

The following tables present the optical specifications for the OC-192

OLIUs.

System specifications

The table below lists the OC-192 OLIU system specifications.

Table 10-48 SONET Optical System Specifications

System Information LNW58

Optical Line Rate

Optical Line Coding

9953.28 Mb/s

Scrambled NRZ

Optical Wavelength

Performance

Temperature Range

1310 nm

ITU-T G.693

VSR600-2R1

(Very Short Reach)

Central Office

LNW56

9953.28 Mb/s

Scrambled NRZ

1550 nm

GR-253 OC-192 IR-2

(Intermediate Reach)

Central Office

Transmitter Specifications

The table below lists the OC-192 OLIU transmitter information.

Table 10-49 SONET Optical Transmitter Information

Transmitter Info.

Optical Device

Temperature Controller

FDA Classification

Optical Source

Faceplate Optical

Connector

LNW58

None

Class I

1310 nm, FP or DFB

Laser Structure

LC connector

LNW56

None

Class I

1550 nm, ELM Laser

Structure

LC connector

1 0 - 7 8

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-192 OLIU

(LNW56 and LNW58)

Technical Specifications

Receiver specifications

The table below lists the OC-192 OLIU receiver information.

Table 10-50 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

LNW58

PIN Diode

LC connector

LNW56

PIN Diode

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 7 9

SONET Optical Specifications: OC-192 OLIU

(LNW56 and LNW58)

Link budgets

The table below lists the OC-192 OLIU link budgets.

Technical Specifications

Table 10-51 Optical Specifications and Link Budgets

Parameter (Note 1)

Minimum Wavelength

Maximum Wavelength

Maximum Spectral Width

(

∆λ

)

Maximum RMS Spectral Width (

)

Minimum Side Mode Suppression Ratio

(SSR)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

Minimum Received Power

@ BER or 1x10

-12

Minimum System Gain

(see Note 2)

Dispersion

Optical Path Penalty (see Note 3)

Optical Signal to Noise Ratio (OSNR);

1x10

-12

BER, -10 to -20 dBm, +1600 ps/nm, 0.1 nm RBW

Minimum Loss Budget

(see Note 4)

Maximum Loss Budget

(see Note 5)

Approximate Span Length

(see Note 6)

LNW58

1260 nm

1360 nm

3.0 nm

-1.0 dBm

-6.0 dBm

-1.0 dBm

-11.0 dBm

5.0 dB

1.0 dB

0.0 dB

4.0 dB

600 meters

LNW56

1530 nm

1565 nm

1.0 nm

30 dB

+2.0 dBm

-1.0 dBm

-14.0 dBm

13.0 dB

+800 ps/nm

2.0 dB

3.0 dB

11.0 dB

40 km

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3 and ITU

G.693. All values are worst-case end of life. Optical specifications meet or exceed equivalent GR-253-CORE requirements.

2. The system gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

3. Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310

1 0 - 8 0

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-192 OLIU

(LNW56 and LNW58)

Technical Specifications

nm is a maximum of 1.0 dB. The optical path penalty for 1550 nm is a maximum of 2.0 dB.

5. The stated maximum loss budget equals the miniumum system gain, minus the optical path penalty. Maximum loss budget is available for both station and transmission cable and splices.

6. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.27 dB/km is used for 1550 nm optics.

Note that the 1310 nm VSR OC-192 LNW58 is recommended for spans of up to 600 meters only.

365-372-300

Issue 8.0, September 2006

1 0 - 8 1

Technical Specifications

SONET Optical Specifications: OC-192 OLIU (LNW57 and LNW60)

Overview

The following tables present the optical specifications for the OC-192

OLIUs.

System specifications

The table below lists the OC-192 OLIU system specifications.

Table 10-52 SONET Optical System Specifications

System Information LNW57

Optical Line Rate 9953.28 Mb/s

Optical Line Coding

Optical Wavelength

Performance

Temperature Range

Scrambled NRZ

1533.465 nm

GR-253 OC-192 LR-2

(Long Reach)

Central Office

LNW60

9953.28 Mb/s

Scrambled NRZ

1533.465 nm

GR-253 OC-192 LR-2+

(Extended Long Reach)

Central Office

Important!

The LNW57 and LNW60 circuit packs utilize a

“dither tone” to frequency modulate the laser. This technique is used to minimize the effects of Stimulated Brillouin Scattering

(SBS).

Normally, Lucent recommends that the optical output of the

OC-192 circuit packs be amplified to no more than +10 dBm.

However, with the dither tone circuit incorporated into the

LNW57 and LNW60, optical amplification of the LNW57 to higher power levels is acceptable. The LNW60 is already amplified by an on-board optical amplifier.

1 0 - 8 2

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-192 OLIU

(LNW57 and LNW60)

Technical Specifications

Transmitter Specifications

The table below lists the OC-192 OLIU transmitter information.

Table 10-53 SONET Optical Transmitter Information

Transmitter Info.

Optical Device

Temperature Controller

FDA Classification

Optical Source

LNW57

None

Class I

1550 nm, Externally

Modulated Mach-Zehnder

Type

Faceplate Optical

Connector

LC connector

LNW60

None

Class 1M (IEC 60825)

1550 nm, Externally

Modulated Mach-Zehnder

Type with an On-Board

Optical Amplifier

LC connector

Receiver specifications

The table below lists the OC-192 OLIU receiver information.

Table 10-54 SONET Optical Receiver Information

Receiver Information

Optical Detector

Faceplate Optical Connector

LNW57

Avalanche Photo

Diode (APD)

LC connector

LNW60

Avalanche Photo Diode (APD) with Improved Tolerance to Chromatic

Dispersion in the Signal

LC connector

365-372-300

Issue 8.0, September 2006

1 0 - 8 3

SONET Optical Specifications: OC-192 OLIU

(LNW57 and LNW60)

Technical Specifications

Link budgets

The table below lists the OC-192 OLIU link budgets.

Table 10-55 Optical Specifications and Link Budgets

Parameter (Note 1)

Minimum Wavelength (see Note 7)

Maximum Wavelength (see Note 7)

Maximum Spectral Width

(

∆λ

)

Minimum Side Mode Suppression Ratio

(SSR)

Maximum Transmitter Power

Minimum Transmitter Power

Maximum Received Power

Minimum Received Power

@ BER or 1x10

-12

Minimum System Gain

(see Note 2)

Dispersion

Optical Path Penalty (see Note 3)

Optical Signal to Noise Ratio (OSNR);

1x10

-12

BER, -10 to -20 dBm, +1600 ps/nm, 0.1 nm RBW

Minimum Loss Budget

(see Note 4)

Maximum Loss Budget

(see Note 5)

Approximate Span Length

(see Note 6)

LNW57 LNW60

1533.405 nm 1533.405 nm

1533.525 nm 1533.525 nm

0.04 nm 0.04 nm

30 dB 30 dB

+6.0 dBm

+3.0 dBm

-7.0 dBm

-24.0 dBm

27.0 dB

+12.5 dBm

+11.5 dBm

-7.0 dBm

-24.0 dBm

35.5 dB

+1600 ps/nm +2000 ps/nm

2.0 dB 2.0 dB

23.0

21.0

13.0 dB

25.0 dB

92 km

19.5 dB

33.5 dB

124 km

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3 and ITU

G.693. All values are worst-case end of life. Optical specifications meet or exceed equivalent GR-253-CORE requirements.

2. The system gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

3. Optical path penalty includes effects of dispersion, reflection, and jitter that occur on the optical path. The optical path penalty for 1310

1 0 - 8 4

365-372-300

Issue 8.0, September 2006

SONET Optical Specifications: OC-192 OLIU

(LNW57 and LNW60)

Technical Specifications

nm is a maximum of 1.0 dB. The optical path penalty for 1550 nm is a maximum of 2.0 dB.

5. The stated maximum loss budget equals the miniumum system gain, minus the optical path penalty. Maximum loss budget is available for both station and transmission cable and splices.

6. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.27 dB/km is used for 1550 nm optics.

This estimate includes cable loss and and splice losses. For 1550 nm

OC-192 systems, dispersion can also be a limiting factor.

Approximate Span Lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

Important!

With the LNW57, span lengths of 92 km are possible as long as total dispersion is less than 1600 ps/nm. With the LNW60, span lengths of 124 km are possible as long as total dispersion is less than 2000 ps/nm.

7. The transmitted wavelength of the LNW57 and LNW60 circuit packs is a fixed single wavelength of nominally 1533.465 nm, 195.5 THz

(single-color, Ch 55). The Maximum Center Wavelength Deviation is

+/- 60 picometers (+/- 12.5 GHz).

365-372-300

Issue 8.0, September 2006

1 0 - 8 5

Technical Specifications

DWDM OC-192 OLIUs (LNW523, LNW527, LNW554, and

LNW555) Optical Specification

Overview

The following tables present the optical specifications for the OC-192

LNW523, LNW527, LNW554 and LNW555 OLIU.

System specifications

The table below lists the LNW523, LNW527, LNW554, and LNW555

OC-192 OLIU system specifications.

Table 10-56 SONET Optical System Specifications

System

Information

LNW523

Optical Line Rate 9953.28 Mb/s

Optical Line

Coding

Scrambled NRZ

LNW527

9953.28 Mb/s

Scrambled NRZ

LNW554

9953.28 Mb/s

Scrambled NRZ

Optical Wavelength

=See Note

Performance

1550 nm*

(4 tunable wavelengths)

1550 nm*

(4 tunable wavelengths)

1550 nm*

(4 tunable wavelengths)

Modified GR-253

OC-192 LR-2 (Long

Reach)

Modified GR-253

OC-192 LR-2 (Long

Reach)

Modified GR-253

OC-192 LR-2

(Long Reach)

Temperature Range Central Office Central Office Central Office

LNW555

9953.28 Mb/s

Scrambled NRZ

1533.465 nm

Modified GR-253

OC-192 LR-2 (Long

Reach)

Central Office

Note

*: See Table 10-59 for tunable wavelength frequencies.

Important!

The LNW555 circuit pack can operate as either an

• 80 km long-reach TDM optical interface

• 80 km long-reach DWDM optical interface

(single-color CH 55) capable of interfacing with the passive optics filters

In either application, the transmitted wavelength is a fixed, single wavelength 1533.465 nm/195.5 THz.

1 0 - 8 6

365-372-300

Issue 8.0, September 2006

DWDM OC-192 OLIUs (LNW523, LNW527, LNW554, and

LNW555)

Technical Specifications

Transmitter Information

The table below lists the LNW523, LNW527, LNW554, and LNW555

OC-192 OLIU transmitter information.

Table 10-57 SONET Optical Transmitter Information

Transmitter Info. LNW523

Optical Device

Temperature

Controller

None

FDA Classification Class I

Optical Source

Faceplate Optical

Connector

LNW527

None

Class I

LNW554

None

Class I

1550 nm Externally

Modulated Mach-

Zehnder Type

1550 nm Externally

Modulated Mach-

Zehnder Type

1550 nm Externally

Modulated

Mach-Zehnder Type

LC connector LC connector LC connector

LNW555

None

Class I

1550 nm Externally

Modulated

Mach-Zehnder Type

LC connector

Receiver specifications

The table below lists the LNW523, LNW527, LNW554, and LNW555

OC-192 OLIU receiver information.

Table 10-58 SONET Optical Receiver Information

Receiver Information LNW523 LNW527 LNW554 LNW555

Optical Detector Avalanche

Photo Diode

(APD)

Avalanche

Photo Diode

(APD)

Avalanche

Photo Diode

(APD)

Avalanche

Photo Diode

(APD)

Faceplate Optical Connector LC connector LC connector LC connector LC connector

365-372-300

Issue 8.0, September 2006

8 7 1 0 -

DWDM OC-192 OLIUs (LNW523, LNW527, LNW554, and

LNW555)

Technical Specifications

Operating wavelengths

The LNW523/527/554 employ tunable lasers that support 4 separate frequencies on each pack. Using software controls, the

LNW523/527/554 lasers can be made to transmit different wavelengths.

The LNW555 employs a fixed laser that transmits a single wavelength at 1533.465 nm (ch 55).

The table below lists the channel numbers, operating wavelengths, and frequencies that adhere to the ITU grid for OC-192 DWDM OLIUs.

Table 10-59 OC-192 DWDM OLIUs Wavelength Plan

Circuit Pack

LNW523

Channel #

Wavelength (nm) Frequency (Thz)

1560.606 192.1

1559.794 192.2

1558.983 192.3

1558.173 192.4

LNW527

LNW554

LNW555

1557.363 192.5

1556.555 192.6

1555.747 192.7

1554.940 192.8

1535.822 195.2

1535.036 195.3

1534.250 195.4

1533.465 195.5

1 0 - 8 8

365-372-300

Issue 8.0, September 2006

DWDM OC-192 OLIUs (LNW523, LNW527, LNW554, and

LNW555)

Technical Specifications

Link budgets

The table below lists the OC-192 LNW523, LNW527, LNW554, and

LNW555 OLIU link budgets.

Table 10-60 Optical Specifications and Link Budgets

Parameter (Note 1)

Minimum Wavelength

Maximum Wavelength

Maximum Center Wavelength

Deviation

Maximum Spectral Width

(

∆λ

) TBD

Maximum RMS Spectral Width (

) NA

30 dB Minimum Side Mode Suppression

Ratio (SSR)

Maximum Transmitter Power

LNW523 LNW527 LNW554 LNW555

1560.606 nm 1557.363 nm 1535.822 nm 1533.465 nm

1558.173 nm 1554.940 nm 1533.465 nm

(see Note 7)

TBD

+/- 60 picometers

(+/ 7.5 GHz)

TBD TBD

+6.0 dBm

30 dB

Minimum Transmitter Power

Maximum Received Power

Minimum Received Power

Minimum System Gain

(see Note 2)

Dispersion

Optical Path Penalty (see Note 3)

+3.0 dBm

-7.0 dBm

-24.0 dBm

27.0 dB

+6.0 dBm

+3.0 dBm

-7.0 dBm

-24.0 dBm

27.0 dB

+6.0 dBm

+3.0 dBm

-7.0 dBm

-24.0 dBm

27.0 dB

+6.0 dBm

+2.0 dBm

-9.0 dBm

-22.0 dBm

24.0 dB

+1600 ps/nm +1600 ps/nm +1600 ps/nm +1600 ps/nm

2.0 dB 2.0 dB 2.0 dB 2.0 dB

TBD TBD TBD NA Optical Signal to Noise Ratio

(OSNR); 1x10

-12

BER, -10 to -20 dBm, +1600 ps/nm, 0.1 nm RBW

Minimum Loss Budget

(see Note 4)

Maximum Loss Budget

(see Note 5)

Approximate Span Length

(see Note 6)

13.0 dB

25.0 dB

92 km

13.0 dB

25.0 dB

92 km

13.0 dB

25.0 dB

92 km

15.0 dB

22.0 dB

81 km

NOTES

1. All terminology is consistent with GR-253-CORE, Issue 3. All values are worst-case end of life. Optical specifications meet or exceed equivalent GR-253-CORE requirements.

365-372-300

Issue 8.0, September 2006

1 0 - 8 9

DWDM OC-192 OLIUs (LNW523, LNW527, LNW554, and

LNW555)

Technical Specifications

2. The system gain includes connector loss at the transmitter and receiver points S and R in GR-253-CORE, Issue 3.

5. The stated maximum loss budget equals the miniumum system gain, minus the optical path penalty. Maximum loss budget is available for both station and transmission cable and splices.

6. The Approximate Span Length values are calculated per an attenuation assumption. As a general rule, for attenuation-limited systems, an attenuation of 0.27 dB/km is used for 1550 nm optics.

This estimate includes cable loss and splice losses. For 1550 nm

OC-192 systems, dispersion can also be limiting factor. Approximate

Span Lengths can be calculated more precisely based on particular fiber and splice characteristics and local engineering rules.

Important!

With the LNW523, LNW527, and LNW524 span length of 92 km are possible as long as the maximum dispersion is less than 1600ps/nm.

7. The transmitted wavelength of the LNW555 circuit pack is a fixed single wavelength of 1533.465 nm/195.5 THz (single-color, CH 55).

1 0 - 9 0

365-372-300

Issue 8.0, September 2006

Technical Specifications

Lightguide Jumpers and Buildouts

Overview

The DMX provides standard LC-type connectors on all optical interfaces. 5 dB, 10 dB, 15 dB, and 20 dB attenuating build-outs are supported.

Single-mode jumpers

The OC-3, OC-12, OC-48, OC-192, and 1000BASE-LX lightguide interfaces use single-mode jumpers for connecting to and from the outside plant LGX panel and the DMX.

Multi-mode jumpers

The 1000BASE-SX interface must use multi-mode jumpers.

Build-outs

DMX supports the use of single-mode to single-mode (SM-SM) fiber exclusively, except on the 1000BASE-SX interface.

Reference

For more information, including a complete list of available jumpers and build-outs, refer to the Miscellaneous Equipment and Tools section in Chapter 7, Ordering.

365-372-300

Issue 8.0, September 2006

1 0 - 9 1

Technical Specifications

Multimode Fiber Transmission with

OC-3 and OC-12 circuit packs

Overview

Purpose

This section details the use of OC-3 and OC-12 circuit packs to transmit signals over Multi-Mode Fiber (MMF).

OC-3 and OC-12 circuit packs used on DMX are designed to meet or exceed Optical Performance Standards per Telcordia GR-253 CORE on standard Single-Mode Fiber (SMF). This section reflects the results of tests demonstrating successful transmission over shorter distances of

MMF.

Based on this testing, transmission of OC-3 and OC-12 signals over

MMF can be supported by a DMX system equipped with LNW36,

LNW46, or LNW50 circuit packs within the limits specified in this section.

1 0 - 9 2

365-372-300

Issue 8.0, September 2006

Technical Specifications

Background Information

Core Diameters

Standard SMF core diameters are specified to be in the range of

8-10

µ m

MMF core diameters are specified to be 50

µ m or 62.5

µ m

Receiver Ports

All existing DMX circuit pack codes that utilize OC-3 or OC-12 optical interfaces incorporate optical receiver ports that accept optical inputs from fiber cores up to 62.5

µ m in diameter. Therefore, the receivers are designed to capture all of the incoming light from both SMF and MMF.

Transmitter Ports

The LNW36, LNW46, and LNW50 circuit packs utilize optical interfaces that incorporate laser transmitter ports designed to launch into

8-10

µ m

SMF. The laser transmitters in these circuit packs are Distributed Feedback (DFB) or Single Longitudinal (SLM) mode lasers.

365-372-300

Issue 8.0, September 2006

1 0 - 9 3

Technical Specifications

Recommendations

Recommendations

With multi-mode fiber specified to meet 1 GbE fiber standards per the original IEEE 802.3z

(now found in IEEE 802.3-2002) and rated at

500 MHz-km or greater, “Single-mode Fiber Offset-Launch Mode-

Conditioning Patch Cords” (Mode-Conditioning Patch Cord) are required for the transmitter ports of LNW36, LNW46, and LNW50 circuit packs. Mode-Conditioning Patch Cords take the transmitter port output from the single-mode fiber and couple it to the multi-mode fiber core at an offset. This offset launch into the MMF minimizes differential mode delay and modal dispersion. With the use of Mode-Conditioning patch cords, transmission distances of up to 300 meters are

allowed (refer to Figure 10-1).

With improved, recently introduced MMF specified to exceed 1 GbE fiber standards, transmission distances of up to 300 meters are allowed without the use of Mode-Conditioning patch cords. Several manufacturers offer this improved MMF (see the table below). These fibers, or their equivalents, do not require Mode-Conditioning patch cords when used with the LNW36, LNW46, and LNW50 circuit pack codes.

MMF Types that Do Not Require Mode-Conditioning Patch Cords

Manufacturer

Product Name Core Size

GigaGuide 62.5

OFS Fitel

Corning

Draka Comteq

GigaGuide 62.5 XL

InfiniCor CL 1000

HiCap 62.5 mm

62.5

µ m

62.5

µ m

62.5

µ m

62.5

µ m

Per usual practice, one must adhere to Lucent’s receiver overload and sensitivity specifications for the circuit pack codes listed above. Multimode attenuators may be needed at the LGX.

1 0 - 9 4

365-372-300

Issue 8.0, September 2006

Recommendations

Technical Specifications

Figure 10-1 Transmission Over Multi-Mode Fiber

Connection Diagram using:

Single-Mode Fiber Offset-Launch Mode-Conditioning

Patch Cord

Duplex mode-conditioning patch cord*

DMX

OC-3 or OC-12 circuit pack:

LNW36, LNW46, LNW50

SMF

MMF

LC LC

SMF

Offset

Splice

MMF

SC SC

MMF

SC SC

MMF

LGX

LC = LC type optical connector

SC = SC type optical connector

SMF = single-mode fiber

MMF = multi-mode fiber

* Mode-Conditioning Patch Cord

may extend to the LGX

MMF

Other Terminal Equipment

365-372-300

Issue 8.0, September 2006

1 0 - 9 5

Technical Specifications

Ethernet/SAN Optical Specifications

Overview

Purpose

This section contains technical specifications for the optical interfaces for the Ethernet/SAN OLIUs.

Contents

The following optical interfaces are discussed in this section:

4-port GbE PTM (1000BASE-TX and/or

1000BASE-SX/LX/ZX) Private Line Optical Ethernet

(LNW63)

8-port GbE PTM (1000BASE-TX and/or

1000BASE-SX/LX/ZX) Private Line Optical Ethernet

(LNW64)

Short-reach GbE (1000BASE-SX) Optical Ethernet

(LNW67)

Long-reach GbE (1000BASE-LX) Optical Ethernet

(LNW68)

GbE (1000BASE-X)/ Fast-E (100BASE-LX/TX)

Optical/Electrical Ethernet (LNW70)

FC-DATA: FICON/ESCON/Fibre-Channel (LNW73 and

LNW73C) SAN Transport Interface

10/100T (10/100BASE-T)/ Fast-E (100BASE-LX)

Electrical/Optical Ethernet Private Line (LNW74)

RPR Enabled GbE (1000BASE-X)/ Fast-E

(100BASE-LX/TX) Optical Ethernet (LNW78)

1000BASE-ZX Optical Ethernet/SAN Specification

100BASE-LX Optical Ethernet Specification

ESCON SAN Transport Specification (LNW73 and

LNW73C)

1 0 - 9 6

365-372-300

Issue 8.0, September 2006

Technical Specifications

4-port GbE PTM (1000BASE-TX and/or 1000BASE-SX/LX/ZX)

Private Line Optical Ethernet (LNW63)

Description

The LNW63 provides 4 PTM ports that can be equipped with very long-reach (1000BASE-ZX) 1550 nm, long-reach (1000BASE-LX)

1310 nm, and/or short-reach (1000BASE-SX) 850 nm optical PTMs.

LNW63 can also be equipped with 100/1000BASE-TX electrical

Ethernet SFPs used in the LNW70, though only 1000BASE-TX rates are supported on the LNW63.

The LNW63 provides data transport at the rate of 1000 Mbps using standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU

G.7041), and standard STS-1 virtual concatenation according to ITU

G.707. The LNW63 is an unprotected pack.

When DMX is equipped with VLF Main (LNW59) packs, Ethernet packs can occupy both Slot 1 and 2 of a Function or Growth Unit

(where applicable). With VLF Mains and all tributary slots populated with LNW63 packs, DMX provides a total add/drop capacity of 40 private line GbE ports.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW63 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

The LNW63 contains 4 internal 1000 Mbps WAN ports supporting enhanced private line services such as low-order virtual concatenation

(VT1.5) and Link Capacity Adjustment Scheme (LCAS). The LNW63 and PTM optics are also OSP hardened for outside plant applications.

Optical Specification

The LNW63 utilizes 1000BASE-SX/LX/ZX PTM optics. Refer to the sections entitled

1000BASE-ZX Optical

for the detailed

specifications of these optics.

365-372-300

Issue 8.0, September 2006

1 0 - 9 7

4-port GbE PTM (1000BASE-TX and/or 1000BASE-SX/LX/ZX)

Private Line Optical Ethernet (LNW63)

Technical Specifications

Performance monitoring

Performance monitoring capabilities are available on the GbE circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

1 0 - 9 8

365-372-300

Issue 8.0, September 2006

Technical Specifications

8-port GbE PTM (1000BASE-TX and/or 1000BASE-SX/LX/ZX)

Private Line Optical Ethernet (LNW64)

Description

The LNW64 provides 8 private line, PTM (also known as SFP) GbE ports. The ports can be equipped with 8 1000BASE-SX/LX/ZX PTMs or 8 100/1000BASE-TX electrical PTMs, though only 1000BASE-TX rates are supported on the LNW64. LNW64 can also support a mix of 4 electrical and 4 optical PTMs. The LNW64 contains 8 internal VCG ports supporting enhanced private line services such as virtual concatenation and Link Capacity Adjustment Scheme (LCAS).

LNW64 is OSP hardened and can only be used with VLF Mains

(LNW59).

LNW64 supports STS-1 and STS-3c cross-connections with or without

VCAT, and STS-12c cross-connections without VCAT. All ports are capable of transmitting at wire speed (1000 Mbps) simultaneously, making full capacity of the pack 168 STS-1s. With VLF Mains,

LNW64 can occupy both slots 1 and 2 of a Function/Growth unit, making the total capacity of a systems fully populated with LNW64s,

80 GbE private line ports.

Optical Specification

The LNW64 utilizes 1000BASE-SX/LX/ZX PTM optics. Refer to the sections entitled

1000BASE-ZX Optical

for the detailed

specifications of these optics.

Performance monitoring

Performance monitoring capabilities are available on the GbE circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 9 9

Technical Specifications

Short-reach GbE (1000BASE-SX) Optical Ethernet (LNW67)

Description

This 2-port Ethernet interface provides short-reach high-speed optical data transport at the rate of 1 Gb/s using standard Ethernet switching

IEEE 802.1, standard encapsulation according to ANSI

T1X1.5/2000-024R4 (ITU G.7041), and standard STS-1 virtual concatenation according to ITU G.707. The LNW67 is an unprotected pack. Fiber access is provided by two LC-type connector pairs on the

LNW67 faceplate. The LNW67 transmits signals at a wavelength of

850nm. The LNW67 requires the use of multi-mode fiber cable. Each

LNW67 circuit pack can support 2 packet rings or 2 GbE private lines

(protected or unprotected).

When DMX is equipped with VLF Main (LNW59) packs, Ethernet packs can occupy both Slot 1 and 2 of a Function or Growth Unit

(where applicable). With VLF Mains and all tributary slots populated with LNW67 packs, DMX provides a total add/drop capacity of 20 optical GbE ports.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW67 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

Important!

The LNW67 is being DA’d and will no longer be available as of 3/1/08.

Optical Specification

The LNW67 utilizes 1000BASE-SX optics. Refer to the section entitled

for the detailed

specifications of these optics.

Performance monitoring

Performance monitoring capabilities are available on the GbE circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

1 0 - 1 0 0

365-372-300

Issue 8.0, September 2006

Technical Specifications

Long-reach GbE (1000BASE-LX) Optical Ethernet (LNW68)

Description

This 2-port Ethernet interface provides long-reach high-speed optical data transport at the rate of 1 Gb/s using standard Ethernet switching

IEEE 802.1, standard encapsulation according to ANSI

T1X1.5/2000-024R4 (ITU G.7041), and standard STS-1 virtual concatenation according to ITU G.707. The LNW68 is an unprotected pack. Fiber access is provided by two LC-type connector pairs on the

LNW68 faceplate. The LNW68 transmits signals at a wavelength of

1310nm. The LNW68 requires the use of single-mode fiber cable. Each

LNW68 circuit pack can support 2 packet rings or 2 GbE private lines

(protected or unprotected).

Prior to Release 7.0, LNW68 packs could only be placed in Slot 1 of any function group or growth slot in the shelf (A1-G1) and DMX supported a total add/drop capacity of 10 optical GbE ports if all slots are equipped with LNW68 circuit packs.

When DMX is equipped with VLF Main (LNW59) packs, Ethernet packs can occupy both Slot 1 and 2 of a Function or Growth Unit

(where applicable). With VLF Mains and all tributary slots populated with LNW68 packs, DMX provides a total add/drop capacity of 20 optical GbE ports.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW68 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

Important!

The LNW68 is being DA’d and will no longer be available as of 3/1/08.

Optical Specification

The LNW68 utilizes 1000BASE-LX optics. Refer to the section entitled

needed. Refer to the sections entitled

for the detailed specifications of these optics.

Performance monitoring

Performance monitoring capabilities are available on the GbE circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 0 1

Technical Specifications

GbE (1000BASE-X)/ Fast-E (100BASE-LX/TX) Optical/Electrical

Ethernet (LNW70)

Description

The LNW70 circuit pack provides four 1000BASE-X (SX, LX, and/or

(MAC) frames. MAC frames with a destination address on the local bus are filtered by the LNW70 to prevent unnecessary transmission of frames over the wide area network (WAN). Protection is provided via

SONET UPSR/BLSR or through the IEEE 802.1w (or 802.1d) spanning tree algorithm.

The LNW70 can also use electrical PTMs that are provisionable to support either 100BASE-T or 1000BASE-T traffic. The electrical

PTMs can occupy ports 1-4.

Prior to R7.0, the LNW70 could only occupy slot 1 of any Function

Unit group on the shelf (including Growth slots), and up to 20

1000BASE-X and 20 100BASE-LX ports were addressable when all

Function Unit groups are equipped with LNW70 circuit packs.

When DMX is equipped with VLF Main (LNW59) packs, Ethernet packs can occupy both Slot 1 and 2 of a Function or Growth Unit

(where applicable). With VLF Mains and all tributary slots populated with LNW70 packs, up to 40 1000BASE-X and 40 100BASE-LX ports are addressable.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW70 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

Optical Specification

The LNW70 can utilize 1000BASE-LX, 1000BASE-SX, and

1000BASE-ZX PTM optics. The LNW70 can also utilize

100BASE-LX PTM optics for optical fast Ethernet. These PTM optics can be ordered and plugged into the LNW70 as their capacity becomes

1000BASE-LX Optical Ethernet/SAN

1000BASE-ZX Optical Ethernet/SAN Specification

100BASE-LX Optical

Ethernet Specification

100/1000BASE-TX (100/1000 Mbps) Ethernet (LNW63/64/70)

for the detailed specifications of these optics.

1 0 - 1 0 2

365-372-300

Issue 8.0, September 2006

GbE (1000BASE-X)/ Fast-E (100BASE-LX/TX) Optical/Electrical

Ethernet (LNW70)

Technical Specifications

100Mb/GbE Electrical PTM for the LNW70 (R6.0)

The LNW70 now supports a dual function electrical PTM that is provisionable for 100 or 1000 Mbps traffic. It conforms to the

Electrical PTM

for more

information on the electrical PTMs for the LNW70.

Performance monitoring

Performance monitoring capabilities are available on the LNW70 circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 0 3

Technical Specifications

FC-DATA: FICON/ESCON/Fibre-Channel (LNW73 and LNW73C)

SAN Transport Interface

Description

The LNW73 and LNW73C (R6.0) are 4-port Storage Area Networking

(SAN) interface cards designed to facilitate SAN distance extensions via the DMX platform using GFP-T (ITU G.7041). These cards employ standard encapsulation according to ANSI T1X1.5/2000-024R4 (ITU

G.7041), and standard STS virtual concatenation according to ITU

G.707. For extended FC/FICON interfaces, the LNW73/73C also supports buffer_to_buffer credit management spoofing consistent with

ANSI T11 FC-BB-3_GFPT draft standard.

They utilize PTM optics to provide the option of FICON, ESCON, or

Fibre-channel interfaces natively on the DMX shelf. Each pack must be equipped to support only one type of traffic at a time (FICON/FC or

ESCON). The LNW73/73C can operate at 1 Gbps or 2 Gbps. When the pack is operating at 2 Gbps only every other port may be used. So, the total number of SAN interfaces on a DMX shelf is 20 (40 in 0x1) when the LNW73/73c is operating at 1G FC/FICON or ESCON, and 10 (20 in 0x1) when it is set to 2G FC/FICON.

The LNW73C differs from the LNW73 in that it enables compression of asynchronous FC traffic. The LNW73C is able to conserve up to

50% of bandwidth versus uncompressed SAN traffic in typical applications. The R6.0 implementation of SAN compression enables a high throughput of up to two full-line rate FC-2G interfaces in a single pack.

Prior to R7.0, the LNW73/73c could only occupy slot 1 of any

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW70 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

1 0 - 1 0 4

365-372-300

Issue 8.0, September 2006

FC-DATA: FICON/ESCON/Fibre-Channel (LNW73 and LNW73C)

SAN Transport Interface

Technical Specifications

Optical Specification

The LNW73 and LNW73C can utilize both 1000BASE-LX and

1000BASE-SX PTM optics. Both the 1000BASE-LX and

1000BASE-SX optics can support FICON traffic. The LNW73/73C can also utilize ESCON PTM optics for ESCON traffic. These PTM optics can be ordered and plugged into the LNW73/73C as their

capacity becomes needed. Refer to the sections entitled

1000BASE-LX

Optical Ethernet/SAN Specification

1000BASE-SX Optical Ethernet/SAN

ESCON SAN Transport Specification (LNW73 and LNW73C)

and

for the detailed specifications of these

optics.

Performance monitoring

Performance monitoring capabilities are available on the LNW73/73C circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 0 5

Technical Specifications

10/100T (10/100BASE-T)/ Fast-E (100BASE-LX) Electrical/Optical

Ethernet Private Line (LNW74)

Description

The LNW74 circuit packs provide sixteen 10/100BASE-TX, IEEE

802.3-compliant electrical interfaces (via the backplane of the shelf) that are capable of spanning distances of 100 meters. The LNW74 also provides 8 optical 100BASE-LX IEEE 802.3-compliant (100 Mbps) fast Ethernet interfaces. The LNW74 is a Private Line circuit pack.

The 10/100T interface function is full duplex mode and auto-negotiates speed (10/100 Mbps) when interfacing with other 802.3-compliant devices over twisted pair media. The LNW74 circuit pack must be housed in slot 1 of a Function Unit group and is not equipment protected. However, facility protection can be provided through the

WAN via SONET (UPSR, BLSR, or 1+1). The LNW74 also supports low- and high-order (STS/VT) VCAT.

Optical Specification

The LNW74 utilizes 100BASE-LX PTM optics. These PTM optics can be ordered and plugged into the LNW74 as their capacity becomes needed. Refer to the section entitled

100BASE-LX Optical Ethernet

and

below for the detailed

specifications of these optics.

Performance monitoring

Performance monitoring capabilities are available on the LNW74 circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

1 0 - 1 0 6

365-372-300

Issue 8.0, September 2006

Technical Specifications

RPR Enabled GbE (1000BASE-X)/ Fast-E (100BASE-LX/TX)

Optical Ethernet (LNW78)

Description

This 8-port Ethernet interface provides 4-ports for short-reach and/or long-reach high-speed optical data transport at the rate of 1 Gb/s and

4-ports for optical 100BASE-LX transport at 100 Mbps. The first 4 ports (1-4) are for the GbE traffic (ports 3 and 4 are not available in

R7.0) and the second 4 ports (5-8) are for FE traffic. The LNW78 utilizes PTM optics, allowing you to equip additional ports as necessary. In R7.0, LNW78 adds support for the electrical

100/1000BASE-TX, electrical Ethernet PTM. This PTM may only occupy ports 1 and 2 of the pack. The LNW78 also supports similar port, switching, and traffic management capabilities as the LNW70.

The LNW78 supports standards compliant RPR switching per IEEE

802.17. LNW78 will support one RPR instance in R6.0 and two in the future. The LNW78 provides two internal Virtual Concatenation Group

(VCG) WAN ports (will support 4 in the future) with a total capacity of

2.5 Gbps capacity for Ethernet RPR traffic (24 STS-1s in each direction).

Beginning in R7.0, VCG ports 17-22 available to provide EoS connectivity. This feature allows EoS port connectivity to RPR ring interfaces via the faceplate of the LNW78 and/or hairpin cross-connects. Interconnection of multiple RPR rings on the same shelf or separate shelf using EoS VCGs is also supported. Finally, EoS traffic can be managed with QoS support on EoS VCGs.

Beginning in R7.0, with the use of true 0x1 and the LNW59 VLF Main,

LNW78 can occupy slots 1 and 2 of a Function or Growth group. This can increase the overall capacity of the system to 20 RPR GbE (optical only) ports and 20 RPR FE (optical only) ports per shelf.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW78 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

Optical Specification

The LNW78 can utilize both 1000BASE-LX and 1000BASE-SX PTM optics. The LNW78 can also utilize 100BASE-LX PTM optics for

365-372-300

Issue 8.0, September 2006

1 0 - 1 0 7

RPR Enabled GbE (1000BASE-X)/ Fast-E (100BASE-LX/TX)

Optical Ethernet (LNW78)

Technical Specifications

optical fast Ethernet. These PTM optics can be ordered and plugged into the LNW78 as their capacity becomes needed. Refer to the sections entitled

100BASE-LX Optical

Ethernet Specification

for the detailed specifications of these optics.

Performance monitoring

Performance monitoring capabilities are available on the LNW78 circuit packs. A detailed list of monitored parameters can be found in

Appendix B.

1 0 - 1 0 8

365-372-300

Issue 8.0, September 2006

Technical Specifications

Allowed PTM Tranceivers

Overview

DMX utilizes Pluggable Transmission Module (PTM), also known as

SFP, transceivers on the LNW63, LNW64, LNW70, LNW73/73C,

LNW74, and LNW78 circuit packs. To ensure proper optical performance, mechanical fit, compliance with EMC, and compliance with laser safety standards, the Lucent specified PTM transceivers listed in the table below must be used.

BASE-T-C1) will become inoperable (until approved parts are installed).

Allowed Optics

The table below lists the PTM transceivers that may be used in the

LNW63, LNW64, LNW70, LNW73/73C, LNW74, and LNW78 circuit packs.

Table 10-61 PTM Optics for LNW63/64/70/73/73C/74/78

Apparatus Code

100BASE-LX-I1

(FE-TX)

GE-1X2XFC-SX-C1

(1000BASE-SX,

1Gbps and 2 Gbps

Fibre-Channel)

GE-1X2XFC-LX-C1

(1000BASE-LX,

1Gbps and 2 Gbps

Fibre-Channel/FICON)

Comcode

109527812

109527796

109527804

Description

Optical Fast Ethernet PTM,

LC-type connectors (FE-1310SM), OSP hardened. Specification:

100BASE-LX Optical

Ethernet Specification

GbE short-reach, Single-Mode PTM, supports

Ethernet and Fibre-Channel traffic, LC-type connectors (GbE/FC/2FC-850)

Specification:

1000BASE-SX Optical

GbE long-reach, Single-Mode PTM, supports

Ethernet, FICON, and Fibre-Channel traffic,

LC-type connectors (GbE/FC/2FC-1310):

Specification:

1000BASE-LX Optical

1000BASE-SX Optical Ethernet/SAN

Used In

LNW74/70/

LNW70/73/

73C/78

LNW70/73/

73C/78

365-372-300

Issue 8.0, September 2006

1 0 - 1 0 9

Allowed PTM Tranceivers

Technical Specifications

Apparatus Code

GE-1X2XFC-SX-I1

(1000BASE-SX,

1Gbps)

GE-1X2XFC-LX-I1

(1000BASE-LX,

1Gbps)

1000BASE-ZX-I1

(1000BASE-ZX,

1Gbps)

BASE-T-C1

FE and GbE (electrical-

NOT OSP)

ESCON-MM-I1

(ESCON)

Comcode

109570606

109568782

109541862

109565549

109523886

Description

GbE short-reach, Single-Mode PTM, supports

Ethernet and Fibre-Channel traffic, LC-type connectors, OSP hardened,

(GbE/FC/2FC-850). Specification:

GbE long-reach, Single-Mode PTM, supports

Ethernet, FICON, and Fibre-Channel traffic,

LC-type connectors, OSP hardened

(GbE/FC/2FC-1310)

Specification:

1000BASE-LX Optical

1000BASE-ZX Optical Ethernet/SAN

GbE long-reach, Single-Mode PTM, supports

Ethernet, LC-type connectors, and is OSP hardened, (GbE-1550). Specification:

Specification (LNW73 and LNW73C)

Electrical PTM, provisionable to 100 or 1000

Mbps, Lucent Approved

RJ-45 Cat 5-E cable, maximum span length of 100 meters

ESCON, Multi-Mode PTM,

LC-type connectors (ESCON-1310),

Specification:

ESCON SAN Transport

Used In

LNW63/64/

70/73/73C

LNW63/64/

70/73/73C

LNW63/64/

70/73/73C/

LNW63/64/

LNW73/73C

Note:

In the columns titled “Apparatus Codes”, notice that each code ends in

either I1 or C1. These characters denote the operating environment the tranceiver is approved for. The characters I1 following an apparatus code mean that tranceiver is approved for OSP deployments. C1 means the tranceiver is approved for CO deployments.

1 0 - 1 1 0

365-372-300

Issue 8.0, September 2006

Technical Specifications

1000BASE-SX Optical Ethernet/SAN Specification

Overview

The 1000BASE-SX PTMs can be used for Gigabit Ethernet,

Fibre-Channel, and FICON service over Multi-Mode Fiber (MMF).

System specifications

The following are the 1000BASE-SX system specifications:

• Optical Line Rate: 1.25 Gb/s +/- 100 ppm

• Optical Line Coding: 8B/10B

• Performance: Short-reach.

GbE/FC/2XFC Compliance

The PTM optics are compliant with GbE, FC, and 2XFC specifications.

Operating range

The table below shows the operating range for the 1000BASE-SX optical Ethernet/SAN interface. A 1000BASE-SX compliant transceiver supports both 50

µ m and 62.5

µ m fiber media types. A transceiver that exceeds the operational range requirement while meeting all other optical specifications is considered compliant (e.g., a

µ m solution operating at 600 m meets the minimum range requirement of 2 to 550 m).

Table 10-62 1000BASE-SX Operating Range Over Each Optical

Fiber Type

62.5

µ m MMF

µ m SMF

Modal Bandwidth @ 850 nm

(minimum overfilled launch)

(MHz-km)

160

200

400

500

Not supported

Minimum Range

(meters)

2 to 220

2 to 275

2 to 500

2 to 550

Not supported

365-372-300

Issue 8.0, September 2006

1 0 - 1 1 1

1000BASE-SX Optical Ethernet/SAN Specification

Technical Specifications

Transmitter specifications

The 1000BASE-SX optical transmitter meets the specifications defined in IEEE 802.3. The table below shows some of the 1000BASE-SX optical transmitter specifications. Measurement techniques are defined in IEEE 802.3, Section 38, Clause 6.

The 1000BASE-SX transceiver also meets ANSI INCITS FC-PI standards for FC and 2xFC traffic (352-2002).

Table 10-63 1000BASE-SX Transmit Specifications

Description

Transmitter type

Signaling speed (range)

Wavelength (

T rise

, range) fall

(max; 20%-80%; l > 830 nm) rise

/T fall

(max; 20%-80%; l < 830 nm)

RMS spectral width (max)

62.5/50

m MMF

Shortwave Laser

1.25 +/- 100 ppm

770 to 860

0.26

0.21

0.85

0 (Note 1)

-9.5

Average launch power (max)

Average launch power (min)

Average launch power of OFF transmitter

(max)

(Note 2)

Extinction ratio (min)

-30

RIN (max) -117

Coupled Power Ratio (CPR) (min)

(Note 3)

9 < CPR

Unit

GBd nm ns ns nm dBm dBm dBm dB dB/Hz dB

Table notes

1.The 1000BASE-SX launch power shall be the lesser of the class 1 safety limit as defined by IEEE 802.3, Section 38, Clause 7.2 or the

average receiver power (maximum) defined by Table 10-64 below.

2.Examples of an OFF transmitter are as follows: no power supplied to the optical module, laser shutdown for safety conditions, and activation of a “transmit disable” or other optional module laser shut-down conditions.

3.Radial overfilled launches (described in IEEE 802.3, Section 38A,

Clause 2) should be avoided even if they meet CPR ranges.

1 0 - 1 1 2

365-372-300

Issue 8.0, September 2006

1000BASE-SX Optical Ethernet/SAN Specification

Technical Specifications

Receiver specifications

The 1000BASE-SX optical receiver meets the specifications defined in

IEEE802.3, Section 38.3.2. The table below shows some of the

1000BASE-SX optical receiver specifications. Measurement techniques are defined in IEEE802.3, Section 38, Clause 6.

Table 10-64 1000BASE-SX Receive Specifications

Description

Signaling speed (range)

Wavelength (range)

Average receive power (max)

Receive sensitivity

Return loss (min)

Receive electrical 3 dB upper cutoff frequency (max)

62.5

m MMF

1.25 +/- 100 ppm

770 to 860

-17

1500

m MMF

1.25 +/- 100 ppm

770 to 860

-17

1500

Unit

GBd nm dBm dBm dB

MHz

365-372-300

Issue 8.0, September 2006

1 0 - 1 1 3

1000BASE-SX Optical Ethernet/SAN Specification

Technical Specifications

Parameter

Link budgets

The worst-case power budget and link penalties for a 1000BASE-SX channel are shown in the table below.

Table 10-65 1000BASE-SX Link Budgets and Penalties

62.5

m MMF 50

m MMF Unit

Modal bandwidth as measured at

850 nm (minimum, overfilled launch)

Link power budget

Operating distance

Channel insertion loss

(Note 1)

Link power penalties

(Note 1)

Unallocated margin in link power budget

(Note 2)

160

7.5

220

2.38

4.27

0.84

200

7.5

275

2.60

4.29

0.60

400

7.5

500

3.37

4.07

0.05

500

7.5

550

3.56

3.57

0.37

MHz-km dB m dB dB dB

Table notes

1. A wavelength of 830 nm is used to calculate the channel insertion loss, link power penalties, and unallocated margin.

1 0 - 1 1 4

365-372-300

Issue 8.0, September 2006

1000BASE-SX Optical Ethernet/SAN Specification

Technical Specifications

Format specification

The 1000BASE-SX Ethernet/SAN interface complies with the following formatting standards:

•

Maximum frame size refer to Packet size in different tagging modes (A-86)

• standard IEEE 802.1Q VLANs

• Ethernet to SONET Mapping, (G.7041 (GFP) and G.707 (Virtual

Concatenation)

• Protection (SONET and/or 802.1W) and Ethernet Bridging

(802.1D)

Performance monitoring

Performance monitoring capabilities are available on the

1000BASE-SX interface. A detailed list of monitored parameters can be found in Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 1 5

Technical Specifications

1000BASE-LX Optical Ethernet/SAN Specification

Overview

The 1000BASE-LX PTMs can be used for GbE, 1Gbps and 2 Gbps

Fibre-Channel, and FICON service over Single-Mode Fiber (SMF).

System specifications

The following are the 1000BASE-LX system specifications:

• Optical Line Rate: 1.25 Gb/s +/- 100 ppm

• Optical Line Coding: 8B/10B

• Performance: Long-reach.

GbE/FC/2XFC/FICON

Compliance

The PTM optics are compliant with GbE, FC, and 2XFC specifications; and compatible with FICON specifications.

Operating range

The table below shows the operating range for the 1000BASE-LX optical Ethernet interface.

Table 10-66 1000BASE-LX Operating Range

Fiber Type

µ m SMF

Minimum Range (meters)

2 to 10,000

1 0 - 1 1 6

365-372-300

Issue 8.0, September 2006

1000BASE-LX Optical Ethernet/SAN Specification

Technical Specifications

Transmitter specifications

The optical 1000BASE-LX optical transmitter meets the specifications defined in IEEE802.3. The table below shows some of the

1000BASE-LX optical transmitter specifications.

The 1000BASE-LX transceiver also meets ANSI INCITS FC-PI standards for FC and 2xFC traffic (352-2002).

Table 10-67 1000BASE-LX Transmit Specifications

Description

Transmitter type

Signaling speed (range)

Wavelength (l, range)

T rise

/T fall

(max; 20%-80% response time)

RMS spectral width (max)

m SMF

Longwave Laser

Unit

1.25 +/- 100 ppm GBd

1270 to 1355 nm

0.26

4 ns nm

Average launch power (max)

Average launch power (min)

-3

-11.0

Average launch power of OFF transmitter (max) -30

RIN (max) -120 dBm dBm dBm dB/Hz

365-372-300

Issue 8.0, September 2006

1 0 - 1 1 7

1000BASE-LX Optical Ethernet/SAN Specification

Technical Specifications

Receiver specifications

The 1000BASE-LX receiver meets the specifications defined in IEEE

802.3. The table below shows some of the 1000BASE-LX optical receiver specifications.

Table 10-68 1000BASE-LX Receive Specifications

Description

Signaling speed (range)

Wavelength (range)

Average receive power (max)

Receive sensitivity

Return loss (min)

Receive electrical 3 dB upper cutoff frequency (max)

m SMF

1.25 +/- 100 ppm

1270 to 1355

-3

-19

1500

Unit

GBd nm dBm dBm dB

MHz

1 0 - 1 1 8

365-372-300

Issue 8.0, September 2006

1000BASE-LX Optical Ethernet/SAN Specification

Technical Specifications

Link budgets

The worst-case power budget and link penalties for a 1000BASE-LX channel are shown in the table below.

Table 10-69 1000BASE-LX Link Budgets and Penalties

Parameter

Link power budget

Operating distance

Allocation for link penalties

(Note 1)

m SMF Unit

8.0

10,000

2.0

m dB

Table notes

1.A wavelength of 1270 nm is used to calculate the link penalty.

365-372-300

Issue 8.0, September 2006

1 0 - 1 1 9

1000BASE-LX Optical Ethernet/SAN Specification

Technical Specifications

Format specification

The 1000BASE-LX Ethernet/SAN interface complies with the following formatting standards:

•

Maximum frame size refer to Packet size in different tagging modes (A-86)

• standard IEEE 802.1Q VLANs

• Ethernet to SONET Mapping, (G.7041 (GFP) and G.707 (Virtual

Concatenation))

• Protection (SONET and/or 802.1W) and Ethernet Bridging

(802.1D)

Performance monitoring

Performance monitoring capabilities are available on the

1000BASE-LX interface. A detailed list of monitored parameters can be found in Appendix B.

1 0 - 1 2 0

365-372-300

Issue 8.0, September 2006

Technical Specifications

1000BASE-ZX Optical Ethernet/SAN Specification

Overview

The 1000BASE-ZX PTMs can be used for GbE service over

Single-Mode Fiber (SMF). The 1000BASE-ZX PTMs are OSP hardened for outside plant applications.

System specifications

The following are the 1000BASE-ZX system specifications:

• Optical Line Rate: 1.25 Gb/s +/- 100 ppm

• Optical Line Coding: 8B/10B

• Performance: Long-reach (80 km).

Operating range

The table below shows the operating range for the 1000BASE-ZX optical Ethernet interface.

Table 10-70 1000BASE-ZX Operating Range

Fiber Type

µ m SMF

Minimum Range (meters)

2 to 80,000

365-372-300

Issue 8.0, September 2006

1 0 - 1 2 1

1000BASE-ZX Optical Ethernet/SAN Specification

Technical Specifications

Transmitter specifications

The 1000BASE-ZX optical transmitter meets the specifications defined in IEEE802.3. The table below shows some of the 1000BASE-ZX optical transmitter specifications.

Table 10-71 1000BASE-ZX Transmit Specifications

Description

Transmitter type

m SMF

Longwave Laser

Unit

Signaling speed (range)

Wavelength (l, range)

T rise

/T fall

(max; 20%-80% response time)

Maximum Spectral Width

(

∆λ

)

Average launch power (max) +5

Average launch power (min) 0

Average launch power of OFF transmitter (max) -40

RIN (max) -120

1.25 +/- 100 ppm GBd

1500 to 1580 nm

0.26

1 ns nm dBm dBm dBm dB/Hz

1 0 - 1 2 2

365-372-300

Issue 8.0, September 2006

1000BASE-ZX Optical Ethernet/SAN Specification

Technical Specifications

Receiver specifications

The 1000BASE-ZX receiver meets the specifications defined in the table below.

Table 10-72 1000BASE-ZX Receive Specifications

Description

Signaling speed (range)

Wavelength (range)

Average receive power (max)

Receive sensitivity

Return loss (min)

m SMF

1.25 +/- 100 ppm

1500 to 1580

-22.5

Unit

GBd nm dBm dBm dB

365-372-300

Issue 8.0, September 2006

1 0 - 1 2 3

1000BASE-ZX Optical Ethernet/SAN Specification

Technical Specifications

Link budgets

The worst-case power budget and link penalties for a 1000BASE-ZX channel are shown in the table below.

Table 10-73 1000BASE-ZX Link Budgets and Penalties

Parameter

Maximum Channel Insertion Loss

Minimum Channel Insertion Loss

Maximum Dispersion

Optical Path Penalty

m SMF Unit

21.0

5.0

1600

1.5

dB ps/nm dB

1 0 - 1 2 4

365-372-300

Issue 8.0, September 2006

1000BASE-ZX Optical Ethernet/SAN Specification

Technical Specifications

Format specification

The 1000BASE-ZX Ethernet/SAN interface complies with the following formatting standards:

• standard IEEE 802.1Q VLANs

• Ethernet to SONET Mapping, (G.7041 (GFP) and G.707 (Virtual

Concatenation))

• Protection (SONET and/or 802.1W) and Ethernet Bridging

(802.1D)

Performance monitoring

Performance monitoring capabilities are available on the

1000BASE-ZX interface. A detailed list of monitored parameters can be found in Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 2 5

Technical Specifications

100BASE-LX Optical Ethernet Specification

Overview

The 100BASE-LX PTMs can be used on the LNW70 and LNW74.

System specifications

The following are the 100BASE-LX system specifications:

• Optical Line Rate: 125 MBd+/- 50 ppm

• Optical Line Coding: 4B/5B

• Performance: Long-reach.

Operating range

The table below shows the operating range for the 100BASE-LX optical Ethernet interface. A 100BASE-LX compliant transceiver supports 10

µ m fiber media types.

Table 10-74 100BASE-LX Operating Range Single-Mode Fiber

Fiber Type

µ m SMF

Minimum Range (meters)

2 to 10,000

Transmitter specifications

The 100BASE-LX transmitter meets these specifications defined in

IEEE 802.3. The table below describes some of the transmit specifications for 100BASE-LX.

Table 10-75 100BASE-LX Transmit Specifications

Description

Transmitter type

Signaling speed (range)

Wavelength (range)

T rise

/T fall

(max; 20%-80% response time)

RMS spectral width (max)

Average launch power (max)

Average launch power (min)

Average launch power of OFF transmitter

(max)

Extinction ratio (min)

m SMF

Longwave Laser

-8

-15

-45

125 +/- 50 ppm

1260 to 1360

3.5

7.7

Unit

MBd nm ns nm dBm dBm dBm

1 0 - 1 2 6

365-372-300

Issue 8.0, September 2006

100BASE-LX Optical Ethernet Specification

Technical Specifications

Receiver specifications

The 100BASE-LX receiver meets these specifications defined in IEEE

802.3. The table below describes some of the receiver specifications for

100BASE-LX.

Table 10-76 100BASE-LX Receive Specifications

Description

Signaling speed (range)

Wavelength (range)

Average receive power (max)

Receive sensitivity

m SMF

125 +/- 50 ppm

1260 to 1360

-8

-25

Unit

MBd nm dBm dBm

365-372-300

Issue 8.0, September 2006

1 0 - 1 2 7

100BASE-LX Optical Ethernet Specification

Technical Specifications

Link budgets

The worst-case power budget and link penalties for a 100BASE-LX channel are shown in the table below.

Table 10-77 100BASE-LX Link Budgets and Penalties

Parameter

Link power budget

Operating distance

Allocation for link penalties (Note 1)

SMF

10,000

4.0

Unit

dB m dB

Table notes

1. A wavelength of 1270 nm is used to calculate the link penalty allocation.

1 0 - 1 2 8

365-372-300

Issue 8.0, September 2006

100BASE-LX Optical Ethernet Specification

Technical Specifications

Format specification

The 100BASE-LX Ethernet interface complies with the following formatting standards:

• standard IEEE 802.1Q VLANs

• Ethernet to SONET Mapping, (G.7041 (GFP) and G.707 (Virtual

Concatenation))

• Protection (SONET and/or 802.1W) and Ethernet Bridging

(802.1D)

Performance monitoring

Performance monitoring capabilities are available on the 100BASE-LX interface. A detailed list of monitored parameters can be found in

Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 2 9

Technical Specifications

ESCON SAN Transport Specification (LNW73 and LNW73C)

ESCON Specifications

The following are the ESCON system specifications for the

LNW73/73C:

• Optical Line Rate: 200 MBd

• Optical Line Coding: 8B/10B

• Performance: Short-reach.

Operating range

The table below shows the operating range for the ESCON optical

SAN interface. The ESCON transceiver supports 62.5 and 50

µ m multi-mode fiber media types.

Table 10-78 ESCON Optics Operating Range Multi-Mode Fiber

Fiber Type

62.5

µ m MMF

Range

3 km

2 km

Transmitter specifications

The ESCON transmitter conforms to the IBM Corporation

SA23-0394-03 standard. The table below describes some of the transmit specifications for ESCON transmitter.

Table 10-79 ESCON Transmit Specifications

Description

Transmitter type

Signaling speed (range)

Wavelength (range)

T rise

/T fall

(max; 20%-80% response time)

RMS spectral width (max)

Average launch power (max)

Average launch power (min)

Extinction ratio (min)

62.5/50

m MMF

LED

200 +/- 0.04

1280 to 1380

1.7

175

-14

-20.5

Unit

Mb/s nm ns nm dBm dBm dB

1 0 - 1 3 0

365-372-300

Issue 8.0, September 2006

ESCON SAN Transport Specification (LNW73 and LNW73C)

Technical Specifications

Receiver specifications

The ESCON receiver conforms to the IBM Corporation SA23-0394-03 standard. The table below describes some of the receive specifications for ESCON receiver.

Table 10-80 ESCON Receive Specifications

Description

Signaling speed (range)

Average receive power (max)

Receive sensitivity

62.5/50

m MMF

200 +/- 0.04

-14.5

-29

Unit

Mb/s dBm dBm

Link budgets

The worst-case power budget and link penalties for an ESCON channel are shown in the table below.

Table 10-81 ESCON Maximum Link Loss

Parameter

Link power budget

62.5

SMF

Unit

8.0

3 2 km

Format specification

The LNW73/73C interface complies with the following formatting standards:

• The LNW73/73C supports 4 VCGs with a capacity of 48 STS-1s

• FICON/ESCON/FC to SONET Mapping, (G.7041 and G.707

(Virtual Concatenation)), SA22-7202-02, SA23-0394-03, IBM

SG24-4662-00, ANSI X3.296-1977

• Protection SONET BLSR and UPSR (split routing available with

BLSR)

Performance monitoring

Performance monitoring capabilities are supported on the

FICON/ESCON/Fibre-channel interfaces. A detailed list of monitored parameters can be found in Appendix B.

365-372-300

Issue 8.0, September 2006

1 0 - 1 3 1

Technical Specifications

System Performance

Overview

Purpose

This section provides performance specifications for the DMX Access

Multiplexer.

Contents

The following performance specifications are discussed in this section:

Transient Performance

Transmission Delay

Performance Monitoring

1 0 - 1 3 2

365-372-300

Issue 8.0, September 2006

Technical Specifications

SONET Overhead Bytes

Overview

DMX uses SONET transport and path overhead bytes as specified in

GR-253-CORE.

V4 byte

The reserved V4 byte in the VT1.5 superframe is sometimes used for internal error detection in a DMX shelf. This internal usage of the V4 byte may cause the value of a transmitted V4 byte to vary. The DMX always ignores the value of the V4 byte received from another network element as required by GR-253-CORE.

365-372-300

Issue 8.0, September 2006

1 0 - 1 3 3

Technical Specifications

Wander/Jitter

Maximum time interval error (MTIE)

For SONET optical interfaces, the maximum time interval error

(MTIE) does not exceed 60 nanoseconds phase variation when timed with a wander-free reference.

Wander requirements

Wander transfer, tolerance, and generation requirements are met as specified in GR-253-CORE.

Jitter requirements

Jitter transfer, tolerance, and generation requirements are met as specified in GR-253-CORE and GR-499-CORE.

Short-term stability

The SONET interfaces meet the T1.101 OC-N output short-term stability mask as specified in GR-253-CORE, Section 5.

1 0 - 1 3 4

365-372-300

Issue 8.0, September 2006

Technical Specifications

Signal Performance

Overview

The following specifications apply to the standard networks defined in

GR-499-CORE, Issue 3.

DS1 rate

For systems interfacing at the DS1 rate, the number of errored seconds during a 7-hour, one-way loopback test, is less than 10.

DS3 rate

BER

For systems interfacing at the DS3 rate, the number of errored seconds during a 2-hour, one-way loopback test, is less than 29.

The BER is less than 2x10

-10 for both the DS1 and DS3 rates.

Burst-errored seconds are excluded.

Burst-errored seconds

The frequency of burst-errored seconds, other than those caused by protection switching induced by hard equipment failures, averages less than 4 per day.

365-372-300

Issue 8.0, September 2006

1 0 - 1 3 5

Technical Specifications

Synchronization

Overview

The embedded Stratum 3 Timing Generator meets the specifications of

GR-253-CORE, SONET Transport Systems Generic Criteria. The timing generator function is embedded in the 1x1 protected optical interface circuit packs in the main slot pair.

Timing modes

The timing generator supports four timing modes:

•

External timing

Locked to an external Stratum 3 (+/- 4.6 ppm) or better DS1/E1 reference.

•

Line timing

Locked to recovered clock from an OC-N signal (from Main or tributary OC-3/OC-12/OC-48/OC-192).

•

Free running

Timing derived from high-stability temperature-compensated voltage-controlled crystal oscillator (TCVCXO) with a long-term accuracy of +/- 4.6 ppm and temperature stability of -40 o

C to

+65 o

•

Holdover

Timing derived from the internal oscillator in the case of an unprotected synchronization reference failure. In this instance, the

Stratum Timing Generator switches to “holdover mode” and continues to provide system timing, using the internal oscillator to maintain the last known good reference frequency. If the DS1/E1 timing output is enabled for network synchronization, DS1/E1

AIS will be inserted on detection of unprotected optical reference failure. In holdover mode, the accuracy is +/-.37 ppm over the full

-40 to +65 o

C temperature range.

•

DS1/E1 timing outputs

In addition, each timing generator (main circuit pack) provides a single DS1 or E1 sync output derived from a received optical interface signal (OC-N). These DS1/E1 timing outputs may be used to provide a timing reference signal to a local BITS clock

(see Chapter 5 of this document).

1 0 - 1 3 6

365-372-300

Issue 8.0, September 2006

Synchronization

Technical Specifications

DS1 timing functions

The DS1 timing reference inputs and outputs meet the specifications of

GR-499-CORE for DS1 interfaces and GR-253-CORE for timing references. The following are the DS1 timing functions:

• Two DS1 timing reference inputs

• Two DS1 timing reference outputs

• Software-provisionable line build-outs for DS1 timing outputs (up to 655 feet depending on cable type)

• Alarms (Out of Frame, AIS, BER).

E1 timing functions

The E1 timing reference inputs and outputs meet the specifications of

ITU-T G.813 for frequency accuracy, pull-in, hold-in and pull-out ranges, wander, jitter, noise tolerance, noise transfer, transient response and holdover performance. E1 references also comply with ITU-T

G.704 standards for SDN SSM. The following are the E1 timing functions:

• Two E1 timing reference inputs

• Two E1 timing reference outputs

• Software-provisionable line build-outs for E1 timing outputs (up to 655 feet depending on cable type)

• Alarms (Out of Frame, AIS, BER).

365-372-300

Issue 8.0, September 2006

1 0 - 1 3 7

Technical Specifications

Protection Switching

1+1 networks

DMX complies with SONET 1+1 unidirectional and bidirectional revertive and nonrevertive protection switching requirements as specified in GR-253-CORE. Automatic line switches are initiated by signal fail and signal degrade conditions on the received low-speed

(OC-3/12/48) or high-speed (OC-12/48/192) optical signal and are completed within 50 milliseconds of a signal failure. The signal’s BER is calculated from violations of the SONET line overhead B2 parity bytes. Signal fail is declared for incoming LOS, LOF, line AIS, or BER exceeding a provisionable 10

-3

to 10

-5

threshold, while a BER exceeding a provisionable 10

-5

to 10

-9

threshold causes the signal degrade condition. Manual switch commands are available through the local and remote operations interfaces.

Important!

DMX now supports Bidirectional Optimized 1+1

Linear Protection Switching per ITU-T G.841 Annex B.

DMX also supports non-revertive bidirectional 1+1 switching to enable interworking between DMX and Ciena Core Director.

High-speed UPSR networks

Path protection rings feed a SONET payload (STS or virtual tributary

[VT]) from the ring entry point, simultaneously in both rotations of the ring, to the signal’s ring exit point. The node that terminates the signal from the ring monitors both ring rotations and is responsible for selecting the signal that has the highest quality based on LOS, LOF, and path BER performance. On pass-through paths, all detected hard failures (LOS, LOF, line AIS, or STS-1 path AIS) result in VT AIS insertion in the outgoing signals. This allows the terminating node to be aware of the failure and to switch to protection. Protection switching is completed within 50 milliseconds of failure detection.

Under normal conditions, both incoming SONET path signals to the switch selection point are of high quality, and the signal can be selected from either ring. A failure or transmission degradation on one of the rings requires that the other ring path be selected. The DMX provides nonrevertive switching. When and if the critical service should revert to a particular ring, a manual path protection switching command allows

1 0 - 1 3 8

365-372-300

Issue 8.0, September 2006

Protection Switching

Technical Specifications

switching back to the original path for ease of ring maintenance in non-revertive applications.

Low-speed UPSR networks

On low-speed SONET optical interfaces (OC-3/12/48), UPSR is optional and protection switching is provisionable (UPSR or 1+1) on a per-line basis.

365-372-300

Issue 8.0, September 2006

1 0 - 1 3 9

Technical Specifications

Transient Performance

Power loss restart

After system shutdown due to power loss, the system will exhibit a

2-second error free transmission interval which begins within 5 minutes of restoration of power.

Transmission start-up on signal application

The system, after having no signal applied for greater than 1 minute at the DSX-n interface, will exhibit a 2-second error free transmission interval which begins within 5 seconds of the reapplication of a signal.

1 0 - 1 4 0

365-372-300

Issue 8.0, September 2006

Technical Specifications

Transmission Delay

One-way transmission delay

The table below, lists the worst-case measured one-way transmission delay (microseconds) between DMX interfaces.

Table 10-82 Transmission Delay in Microseconds

Interface

Cross-Connect

OC-n

EC-1

DS1

DS3

OC-n EC1

STS-n VT VT

50 25 50

100

N/A

100

STS-1

DS1

100

STS-1

100

DS3

STS-1

365-372-300

Issue 8.0, September 2006

1 0 - 1 4 1

Technical Specifications

Performance Monitoring

Overview

DMX performance monitoring complies with GR-253-CORE and

ANSI T1.231-1997 specifications for SONET and asynchronous networks.

SONET PM parameters

For information concerning PM parameters and all other PM capabilities associated with DMX please refer to Appendix B of this document.

Ethernet parameters

DMX provides PM capabilities for the 10/100T, 100BASE-LX,

1000BASE-SX, and 1000BASE-LX Ethernet interfaces as well as the

FICON/FC and ESCON interfaces. PM data is collected at each LAN and WAN interface in the network for both incoming and outgoing directions and is stored in quarter-hour and day bins. The WAN interface provides a connection to a SONET Virtual Concatenation

Group (VCG).

Provisionable threshold crossing alerts (TCAs) are supported on the

Ethernet interfaces. PM parameters that provide PM data on all

Ethernet interfaces can be found in Appendix B of this document.

1 0 - 1 4 2

365-372-300

Issue 8.0, September 2006

Technical Specifications

Operations Interfaces

Overview

Purpose

This section presents the operation interfaces that are required to support technician access to the system and allow alarms and status information generated by the system to be reported. The operation interfaces include the CIT interface, IAO LAN (via OSI or TCP/IP),

SYSCTL faceplate LEDs, and equipment indicators. DMX supports office alarms, user-definable miscellaneous discretes, and TL1.

Contents

The following operation interfaces are discussed in this section:

Craft Interface Terminal (PC-CIT)

TL1/LAN

Personal Computer Specifications for Software Download

LEDs, Indicators, and Office Alarms

365-372-300

Issue 8.0, September 2006

1 0 - 1 4 3

Technical Specifications

Craft Interface Terminal (PC-CIT)

Overview

The DMX PC-CIT is the primary tool used to interface with the DMX.

It is a personal computer (PC) with the DMX user-interface software installed. The DMX PC-CIT is compatible with PCs running Microsoft

Windows XP, Windows NT and Windows 2000. The PC-CIT also provides a user-friendly TL1 command builder interface.

Minimum requirements

It is anticipated that most customers will dedicate a lap-top PC to run the DMX PC-CIT applications software. However, a properly configured desktop PC will also suffice.

The following list shows the minimum requirements for the customer-provided PC with recommended Windows operating system.

• Microsoft Windows XP, 2000 or NT 4.0 Operating System with service pack 4. The customer is responsible for ensuring that the

PC remains virus -free.

• Pentium 266 MHz processor; Pentium III 500 MHz processor is recommended for optimum performance

• 128 MB RAM minimum: 256 MB RAM minimum for 5 system view

• One-gigabyte hard-disk drive with at least 150 megabytes of free space. The DMX PC-CIT application requires 50 MB, and the installation requires 30MB. In addition, each copy of the NE generic requires an additional 60 MB.

• CD-ROM drive

• SVGA monitor 800x 600 resolution (1024 x 768 recommended)

• 10 BASE-T LAN interface

Pin Designations/signals are:

– -1 TD+

– -2 TD-

– -3 RD+

– -6 RD-

1 0 - 1 4 4

365-372-300

Issue 8.0, September 2006

Craft Interface Terminal (PC-CIT)

Technical Specifications

PC-CIT and Windows requirements

The following table illustrates the Windows operating system requirements for DMX PC-CITs.

DMX port/

Windows

Guidelines

Windows XP

Windows NT

Windows 98 and 2000

Serial Port

OSI/TCP-IP LAN

Port

365-372-300

Issue 8.0, September 2006

1 0 - 1 4 5

Technical Specifications

TL1/LAN

Overview

DMX supports a TL1 over TCP/IP interface or TL1 over OSI LAN interface for communication between a DMX NE and an Element

Management System (EMS) of a Network Management System

(NMS). TL1 over TCP/IP LAN complies with requirements specified in IEEE 802.3 and NSIF-AR-9806-088R11.

TL1 translation device

(T-TD Gateway)

The T-TD is a device that translates TL1 messages over a TCP/IP connection to a TL1 over OSI association, providing a TL1 TCP-OSI gateway. The T-TD, when used in conjunction with the PC-CIT, is an open system interconnection (OSI) proxy that accepts TCP/IP connections and sets up matching OSI connections. This requires the support of the TCP/IP stack and the seven-layer OSI stack.

Front IAO LAN interface

The DMX provides an RJ45-compatible front IAO LAN interface that is intended for use with a local PC. This interface will support a

TL1/TCP gateway via an IEEE 802.3-compliant interface with a graphical user interface (GUI) in future releases.

Rear IAO LAN interface

TL1 over TCP/IP or TL1 over OSI LAN is supported via an

RJ45-compatible IAO LAN rear interface (R1.1) on the DMX, enabling the DMX to connect with any NMS possessing a compatible

TCP/IP or OSI interface (such as the EMS or the PC-CIT). This allows

TL1 communication over a data network between several different

NEs. For instance, Lucent’s Navis Element Management System

(EMS) can communicate with a DDM-2000 that is on the same network as the DMX connected to the EMS via the rear IAO LAN interface. The IAO LAN complies with OSI requirements as specified in GR-253-CORE, Section 8.

SONET DCC

The SONET DCC provides TL1 over OSI connections with remote

NEs in a subnetwork.

1 0 - 1 4 6

365-372-300

Issue 8.0, September 2006

Technical Specifications

Personal Computer Specifications for Software Download

Specifications

The PC used for software download should have:

• Windows NT or 2000

• CD-ROM drive for CD-ROM download.

Compatible modems

A compatible modem must meet the following minimum requirements:

• 300, 1200, 2400, 4800, 9600, 19,200 or 115,000 baud

• Full duplex

• 8 data bits

• No parity bits

• 1 start bit

• 1 stop bit

• No flow control.

365-372-300

Issue 8.0, September 2006

1 0 - 1 4 7

Technical Specifications

LEDs, Indicators, and Office Alarms

LNW1 and LNW2 SYSCTL

Faceplate

The LNW1 and LNW2 SYSCTL circuit pack faceplate contain the following push-button switches and LEDs (LNW2 specific items are labeled as such):

• ACTIVE LED (LNW2 only)

• FAULT LED

• Critical (CR) LED

• Major (MJ) LED

• Minor (MN) LED

• Abnormal (ABN) LED

• Far End Activity (FE) LED

• Near End Activity (NE) LED

• Alarm Cut-Off/Test (ACO) LED

• ACO/TEST (ACO SW) button

• Select (SEL) button

• Update/Initialize (UPD INIT) button

• 7-segment numeric display (LNW1), or alphanumeric LED display (LNW2)

The seven segment/alphanumeric LED numeric display is used to identify the remote system presently displayed on the local user panel.

A green PWR ON LED is lighted when the shelf is receiving -48 V power. A green ACO LED is lighted when the ACO function is active.

The SEL, ACO SW, and UPD INIT push-buttons are provided to control system operation.

The LNW2 contains increased memory to support the enhanced feature set in R6.0 and upcoming releases. It must be used with R6.0. The

LNW1 supports R5.x and prior releases.

Equipment indicators

A red LED FAULT indicator is provided on all circuit packs. A green

LED ACTIVE indicator is provided on all 1x1 protected circuit packs to indicate which circuit packs are actively carrying traffic.

Office Alarms

The office alarms interface is a set of discrete relays that control office audible and visual alarms. Separate relays handle CR, MJ, and MN alarms. Each contact closure is rated at 1 A, 60 V maximum. The CR

1 0 - 1 4 8

365-372-300

Issue 8.0, September 2006

LEDs, Indicators, and Office Alarms

Technical Specifications

and MJ alarms can be wire-ORed. The CR alarm relays are fail safe against unprotected power failures.

365-372-300

Issue 8.0, September 2006

1 0 - 1 4 9

Technical Specifications

User-setable Miscellaneous Discrete Interface

Overview

The user-setable miscellaneous discrete interface allows an operations system (OS) to control and monitor equipment collocated with the

DMX through a set of input and output contact closures. Miscellaneous discrete environmental inputs can monitor conditions like open doors or high temperature, miscellaneous discrete outputs control equipment such as fans and generators. The status of the miscellaneous discrete environmental inputs can be queried on demand via the DMX PC-CIT.

DMX collects miscellaneous discrete alarms and automatically sends them to the operations system (OS)

External customer equipment

Any external customer equipment to be monitored by DMX must provide the electrical equivalent of a contact closure across the corresponding environmental input wiring pairs. The contact closure must be capable of passing at least 10 mA of drive current.

Power source

Reference

The power source to enable the control of external customer equipment may have a voltage range from a minimum of 3 V to a maximum of

72 V. DMX provides a unidirectional opto-isolator connection across each corresponding control output wiring pair. The load current across each control output wiring pair must be limited by the external customer equipment and must not exceed 35 mA.

For detailed wiring information, refer to the Metropolis

DMX Access

Multiplexer Installation Manual, 365-372-304 and Metropolis

DMX

Access Multiplexer Application Schematic, SD8C500-01.

1 0 - 1 5 0

365-372-300

Issue 8.0, September 2006

Technical Specifications

Physical Specifications

Overview

Purpose

This section provides DMX physical characteristics, including environmental and power specifications.

Contents

The following specifications are included in this section:

Physical Specifications

Environmental Specifications

Power Specifications

365-372-300

Issue 8.0, September 2006

1 0 - 1 5 1

Technical Specifications

Physical Specifications

DMX High Capacity shelf physical characteristics

The DMX High Capacity shelf has the following characteristics:

• Width: 17.6 inches

• Height: 19 inches (includes integral fan unit)

• Depth (front to back): 13.75 inches

• Weight (with circuit packs): 57 pounds

• Weight (without circuit packs): 38 pounds

1 0 - 1 5 2

365-372-300

Issue 8.0, September 2006

Technical Specifications

Environmental Specifications

Temperature and humidity

The DMX shelf meets Telcordia Technologies’ Network Equipment

Building System (“NEBS Generic Equipment Requirements,”

GR-63-CORE) requirements for use in CO environments.

A Fan Assembly is required above the standard DMX shelf in any environment except an outside cabinet (with ventilation) application.

The DMX High Capacity shelf has a fan unit built into the bottom of the shelf.

The DMX is environmentally hardened and will function at temperatures of -40 o

C to +65 o

C and humidity of 5 to 95 percent

(noncondensing) in all TDM applications when equipped with the following circuit packs:

LNW1, LNW2, LNW6, LNW7, LNW16, LNW18, LNW19, LNW19B,

LNW28, LNW32, LNW36, LNW37, LNW45, LNW46, LNW48,

LNW49, LNW50, LNW54, LNW63, LNW74, LNW80.

In all other applications the DMX functions at temperatures of 0 o

C to

+50 o

Important!

The DMX Standard Shelf has been DA’d and is no longer available. The High Capacity shelf is available.

EMC requirements

The DMX has been tested and found to comply with the limits for a

Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residence is likely to cause harmful interference in which case the user will be required to correct the interference at the user’s own expense.

365-372-300

Issue 8.0, September 2006

1 0 - 1 5 3

Environmental Specifications

Technical Specifications

Earthquake requirements

DMX meets the earthquake requirements defined in Telcordia

Technologies GR-63-CORE and Pacific Bell Standard

PBS-000-102PT.

Fire resistance

DMX meets ignitability requirements specified in ANSI T1.307-1997.

In addition, the DMX meets the fire resistance requirements of UL

60950, 3rd Edition.

Underwriters Laboratories

The DMX is UL recognized for restricted access installations in business and customer premises applications installed in accordance with Articles 110-16 and 110-17 of the National Electric Code,

ANSI/NFPA Number 70-87. Other installations exempt from the requirements of the National Electric Code may be engineered according to the accepted practices of the local telecommunications utility.

Canadian Standards

Association

The DMX has been certified by the Canadian Standards Association per standard CAN/CSA-C22.2 Number 60950-00.

1 0 - 1 5 4

365-372-300

Issue 8.0, September 2006

Technical Specifications

Power Specifications

Power supply

The following table lists DMX High Capacity shelf power requirements.

Table 10-83 DMX 30 Amp High Capacity Shelf Power Supply

Requirements

Item

Voltage range, all components

Description

-40.0V to -60.0V

Power Feeders two -48V power feeders

[BREAKER (A) and BREAKER (B)]

Circuit Breakers (two per shelf) 30.0 A

The following table lists DMX 20 Amp High Capacity shelf power requirements.

Table 10-84 DMX 20 Amp High Capacity Shelf Power Supply

Requirements

Item

Voltage range, all components

Power Feeders

Description

-40.0V to -60.0V

two -48V power feeders

[BREAKER (A) and BREAKER (B)]

Circuit Breakers (two per shelf) 20.0 A

Circuit breakers

DMX uses on-board power conversion eliminating the need for slots for bulk power converters. Two independent -48V office power feeders

365-372-300

Issue 8.0, September 2006

1 0 - 1 5 5

Power Specifications

Technical Specifications

Current drains

The following table provides the maximum and average current drain requirements for a shelf if only one feeder is present.

Table 10-85 High-capacity Shelf Current Drains

Shelf Current Drains in Amperes

Typical @

−

48V

DMX High Capacity Shelf 6.3

Maximum

−

23.0

48V

Typical

−

40V

7.5

Maximum

−

40V

27.5

The following table provides the maximum and average current drain requirements for a bay equipped with four high-capacity shelves.

Table 10-86 Bay Current Drains

Bay Current Drains

Typical @

−

48V

Maximum

−

48V

25.2

92.0

Typical

−

40V

30.0

Maximum

−

40V

110.0

Bay equipped with four

DMX High Capacity

Shelves

The following table provides the maximum and typical heat dissipation figures for the High Capacity Shelf.

Table 10-87 High-capacity Shelf Heat Dissipation

Shelf

DMX High Capacity

Heat Dissipation in Watts

Typical @

−

48V

Maximum

−

48V

302 1100

Typical

−

40V

300

Maximum

−

40V

1100

1 0 - 1 5 6

365-372-300

Issue 8.0, September 2006

Technical Specifications

External Equipment Specifications

Overview

Purpose

This section provides specifications for equipment frequently used with, but external to the DMX shelf.

Contents

The following specifications are included in this section:

External Optical Amplifier

365-372-300

Issue 8.0, September 2006

1 0 - 1 5 7

Technical Specifications

External Optical Amplifier

Overview

The following tables present the optical specifications for the external optical amplifier.

Optical specifications

The table below lists the optical specifications for the amplifier.

Table 10-88 Optical specifications

Parameter

Wavelength Range

Input Power Range

Output Power

Signal Gain

Noise

Signal Gain

FDA Classification

Polarization Mode Dispersion

Minimum

1530 nm

-27 dBm

13 dB

7.0 (for 22 dB Gain)

13 dB

Maximum (or basic value if there is no min/max measurement.

1563 nm

4 dBm

17 dBm

22 dB

16.0 (for 13 dB Gain)

22 dB

Class 1M (IEC 60825)

—

viewing the laser output with optical instruments can pose an eye hazard.

0.5 ps @ -20 dBm input

Performance Monitoring and Alarms

The below is a list of the alarms and alarm thresholds reported on the amplifier.

• Degradation of input signal

• Loss of input signal

• Excessive pump current

• EDFA case temperature out of range

• Degradation of output signal

• Loss of output signal

• Excessive TEC current

• Gain out of range

1 0 - 1 5 8

365-372-300

Issue 8.0, September 2006

A: Ethernet/SAN

Overview

Purpose

This section describes the Ethernet implementation for the Metropolis

DMX Access Multiplexer (DMX).

Contents

The following topics are covered:

Introduction to Ethernet Services

Ethernet/SAN Circuit Packs

Ethernet Transport

Tagging Modes

Quality of Service

Ethernet Service Management

Ethernet Service Configurations

SONET-Based Distance Extensions for

ESCON/FICON/Fibre-Channel Services

365-372-300

Issue 8.0 September 2006

A - 1

: Ethernet/SAN

Introduction to Ethernet Services

Ethernet services

Ethernet services are what network operators provide their subscribers.

DMX supports Private Line, Private LAN, Virtual Private LAN, and

Virtual Private Line.

The Private services are transported over their own dedicated SONET timeslots. If present, Ethernet switching functions may or may not be shared.

Subscribers of Virtual Private services share network bandwidth to take advantage of the efficiency of statistical multiplexing that is available due to the intermittent nature of data transmission. VLAN Tags are used to separate subscribers and maintain privacy. DMX supports

VLANs in the 1-4093 range for customer identification and isolation.

Private Line services are point-to-point in nature while Private LAN services are multipoint. Private LAN services always involve internal

Ethernet switching while Private Line services do not.

Private line

Private Line service provides a dedicated link between two locations.

The Ethernet ports and SONET bandwidth are dedicated to the subscriber and not shared. Private line service is characterized by minimal provisioning - typically just the SONET cross-connection. A subclass, Fractional Private Line, is distinguished by less than

Ethernet-line-rate SONET connectivity. It is a form of rate control that also improves efficiency by only consuming the required SONET bandwidth in STS-1 increments. For more information about how

STS-1 tributaries can be virtually concatenated to provide Fractional

Private Line service, refer to “Virtual concatenation” (A-33)

Another characteristic of Private Line service is little or no Layer 2 functionality. With Fast Ethernet, the physical layer must be terminated precluding transparency of auto-negotiation. In addition, performance of the Fractional Private Line may be improved by enabling flow control, a Layer 2 function. For more information about flow control, refer to “Flow control” (A-59) .

A - 2

365-372-300

Issue 8.0 September 2006

Introduction to Ethernet Services

: Ethernet/SAN

MAC address learning is another function. For more information about

MAC address learning, refer to “Ethernet LAN/VCG port density” (A-43) . Circuit packs that support multiple service modes

(Private Line and switched services such as Private LAN), for example the LNW67 1GSX circuit pack, typically have more Layer 2 functions available in the Private Line mode than circuit packs such as the

LNW71 10/100-PL that only support Private Line. For more information about Ethernet circuit packs, refer to

“Ethernet/SAN

Circuit Packs” (A-8) .

Private LAN

Private LAN service extends the concept of Private Line to connect more than two locations in an extended Ethernet LAN. This is accomplished by introducing embedded Ethernet switching at each node. The SONET bandwidth is still dedicated to one subscriber.

Because this is a switched service, the attendant QoS features are available.

VLAN tagging is an integral part of Private LAN service. VLANs are used to distinguish customers or organizations within customers. In the

Transparent Mode, the service provider provisions a port tag, or customer ID, for each DMX Ethernet port. This port tag is added to each incoming packet and carried with the DMX network in order to keep the traffic for each subscriber separate. When the packets exit the

DMX network, the port tag is removed. Any subscriber-inserted VLAN tags within the packets are carried through the network unchanged.

In 802.1Q mode, the provider coordinates VLAN tags with the subscriber to further manage traffic flows. For example, some VLANs can limit traffic among particular groups of sites representing communities of interest while others may be used for traffic common to all. This can be coupled with QoS features such as PIR and priorities to optimize the Private LAN network. For more information about

Quality of Service, refer to

“Quality of Service” (A-87)

. For more information about Tagging modes, refer to

“Tagging Modes” (A-79) .

365-372-300

Issue 8.0 September 2006

A - 3

Introduction to Ethernet Services

: Ethernet/SAN

Virtual Private LAN

Virtual Private LAN service extends the concepts of Private LAN service to include bandwidth sharing among multiple customers. In this way, less SONET bandwidth can be used to serve customers by taking advantage of the efficiency of statistical multiplexing. VLAN tags or port tags are used to keep each subscriber’s traffic private.

Virtual Private Line

Virtual Private Line, a shared service between two points, is a special case of Virtual Private LAN. It requires the use of Ethernet switching functions and is therefore configured and managed in the same way as

Virtual Private LAN.

Network topologies and configurations

Network topologies consist of two layers: the packet layer and the underlying SONET layer. Packet networks can be created over a variety of SONET topologies, and have different properties as a result.

For example, a Private Line service uses a point-to-point packet topology, but may be carried over a SONET ring, which may in turn be configured with UPSR protection or no SONET protection.

The following packet topologies are supported:

• Point-to-point

• Multipoint

• Hub-and-spoke.

Point-to-Point

The point-to-point topology is used to join two nodes. For example, a business may connect to an ISP via a point-to-point connection.

Because of its simplicity point-to-point configurations have a variety of protection options available. They may use any of the SONET layer protection mechanisms. They may also forgo SONET protection and use data-layer protection such as Link Aggregation.

Multipoint

In a multipoint network all points converse with each other. Note that connecting three locations by two point-to-point connections is not the same as if done by a multipoint connection. The location in the middle of the point-to point connections would have to provide external switching to enable the outer locations to converse with each other.

A - 4

365-372-300

Issue 8.0 September 2006

Introduction to Ethernet Services

: Ethernet/SAN

One useful case of multipoint configurations is a packet ring. In a closed-ring configuration all nodes may converse. An internal spanning tree may be configured for protection and loop prevention (this is not necessary with RPR). This is independent of any spanning tree protocol that may be running on the subscriber's network. The spanning tree

breaks one link, necessary with a ring of interconnected bridges. In the case of a link failure, the spanning tree algorithm restores connectivity by moving its break to coincide with the failed link.

A special case of multipoint configuration is where one node acts as a hub and all other nodes converse only with it. This hub configuration differs from a hub-and-spoke network only in that the spokes share bandwidth to reach the hub. It is more efficient and may be more practical because it conserves hub ports; only two VCG (WAN) ports are needed, regardless of the number of spokes. (In a packet ring configuration the broken link is placed between the two nodes most remote from the hub; because those nodes don't converse, there is no loss of useful bandwidth.) Both this topology and the hub-and-spoke described next are sometimes called point-to-multipoint.

Hub-and-spoke

The hub-and-spoke network is a hybrid between point-to-point and multipoint. Each node connects to the hub via a dedicated link; but, the links terminate on an embedded switch at the hub. In a typical back-haul application, the switch aggregates the traffic into a single

Ethernet link for hand off. As in the multipoint hub network, tags are used to identify and direct traffic to and from the hub.

Applications

Ethernet applications are examples of what users can do with the services and topologies described in previous sections. The user can be the owner of the equipment or a client of the owner. For example, an

ISP can have a private network or buy the services from an LEC to construct the application.

DMX supports the following applications:

• LAN interconnect

• LAN extension

• ISP access

• Internet access

• Video distribution

365-372-300

Issue 8.0 September 2006

A - 5

Introduction to Ethernet Services

: Ethernet/SAN

LAN Interconnect

Two or more enterprise LANs are interconnected. The LANs may be point-to-point Private Line connections, in which case Ethernet switching services are not provided. If Virtual Private Lines are desired, Ethernet switching is required. Even so, in a three-node LAN

Interconnect application composed of Virtual Private Lines the middle node has two termination ports, one for each neighbor. This is different from a three-node LAN Extension (next application) using Virtual

Private LAN in which the middle node may have only one (effectively a hub) port.

LAN Extension

Sometimes called intranet or Layer 2 VPN, this extends an enterprise

LAN to multiple locations via embedded Ethernet switching. Either

Private LAN or Virtual Private LAN may be used.

Transparent LAN is a common form of LAN Extension in which the subscriber's traffic is transported without regard to the presence of subscriber VLAN tags. Transparency is achieved by the use of Port

Tags, avoiding the need for the provider to administer VLANs with subscribers. The Port Tag is effectively a customer ID; only ports in the network assigned a particular customer ID will exchange traffic.

In Non-Transparent LANs, greater flexibility is available when the subscriber's 802.1Q tags are used for traffic management (802.1Q mode). For example, the priority bits within the tag can be used to give a portion of the subscriber's traffic, for example VoIP, preferential treatment through the network versus its file transfer or internet traffic.

DSCP (available in R6.0) offers an alternative to priority bits. DSCP can also be used to give certain packets/data streams preferential treatment.

Although in a Virtual Private LAN service a Non-transparent LAN application requires the administration of VLAN Id's among customers, in a Private LAN where no other customers share the embedded

Ethernet switch this is not necessary. For more information about priority bits, refer to “Priorities” (A-47) .

A - 6

365-372-300

Issue 8.0 September 2006

Introduction to Ethernet Services

: Ethernet/SAN

ISP Access

In this application an ISP uses a provider's network to collect internet traffic. It is also an example of a trunking application, where traffic from multiple customers is handed off to the ISP router on a single trunk link for efficiency. The Virtual Private LAN service may be used to efficiently transport the best-effort internet traffic. It is typically done using the 802.1Q mode for separating the ISP's clients' traffic. If the

ISP's router supports stacked VLANs then it can be done in Transparent

Mode The trunk link may be GbE while the access links may be 10 or

100 Mb/s Ethernet.

Internet Access

In this application the ISP owns the network. In this case the clients' traffic is untagged. The ISP adds tags for customer separation using the

802.1Q mode. The ISP administers the tags directly, there is no third party involved.

Video Distribution

Video distribution can be accomplished using Ethernet Multicasting. A

Private LAN service is used to guarantee the bandwidth. Video traffic, generated at the head end, is sent using a multicast address. Transparent mode or 802.1Q mode may be used. At each node the traffic is dropped to its user and also duplicated and sent to the rest of the Private LAN.

Important!

Because of the duplication process, the maximum throughput is only half the line rate on the LNW67 and LNW68

(500 Mb/s).

An alternative is to use SONET drop-and-continue cross-connections to implement multicasting. This is a variation of the Private LAN service. Although it is limited to one-way video distribution, it supports full line rate throughput.

365-372-300

Issue 8.0 September 2006

A - 7

: Ethernet/SAN

Ethernet/SAN Circuit Packs

1000BASE-SX/LX/ZX (4 ports)

Private Line

1000BASE-SX/LX/ZX (4 ports)

Private Line

10/100T

(24 ports)

10/100 PL (24 ports)

Private Line

1GbE SX

(2 ports)

1GbE LX

(2 ports)

Enhanced Ethernet Switch Pack

(10/100/1000 BASE-T or

1000BASE-LX/SX

—

4 ports,

10/100 LX

—

4 ports

Overview

DMX supports the following Ethernet circuit packs:

Application/Circuit Pack Code

LNW63

LNW64

LNW66

LNW71

LNW67

LNW68

LNW70

Compatible

Shelf Slots

A-G

(See Note 1)

A-G

(See Note 1)

Description

1000BASE-SX/LX/ZX Ethernet interface via optical PTMs, can be used is slot 1 and/or 2 in a VLF equipped

DMX and either slot 1 or 2 in a non-VLF equipped DMX, GbE private lines, includes no switch fabric, OSP hardened

1000BASE-SX/LX/ZX Ethernet interface via optical PTMs, can be used is slot 1 and/or 2 in a VLF equipped

DMX and either slot 1 or 2 in a non-VLF equipped DMX, GbE private lines, includes no switch fabric, OSP hardened

100BASE-TX Ethernet interface A-D

(See Note 2)

A-D

(See Note 2)

A-G

(See Note 1)

A-G

(See Note 1)

A-G

(See Note 1)

100BASE-TX PL Ethernet interface, supports Ethernet Private Lines

1000BASE-SX Ethernet interface, may occupy slot 1 or 2 of a function group or a growth slot, requires multi-mode cable

1000BASE-LX Ethernet interface, may occupy slot 1 or 2 of a function group or a growth slot, requires single-mode cable

Hybrid 10/100/1000 BASE-TX or

1000BASE-X (ports 1-4), and 100

BASE-LX (ports 5-8) Ethernet interface, may only occupy slot 1 of a function group or a growth slot, uses

PTMs, supports enhanced Ethernet QoS

A - 8

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

: Ethernet/SAN

Application/Circuit Pack

FC-DATA

(SAN Interface)

FC-DATA w/ compression

(SAN Interface)

100BASE-LX

(8 ports)

10/100BASE-TX

(16 ports)

Private Line

RPR 1GbE X

(1000BASE-LX/SX

—

2 ports 100

(4 ports)

Code

LNW73

LNW74

LNW78

Compatible

Shelf Slots

A-G

(See Note 1)

LNW73C

A-G

(See Note 1)

A-G

(See Note 1)

A-G

(See Note 1)

Description

4 ports, PTM optics supporting either

FICON/Fibre-Channel or ESCON

4 ports, PTM optics supporting either

FICON/Fibre-Channel or ESCON, also supports compression of SAN traffic

Hybrid 100BASE-LX and 10/100

BASE-TX Ethernet interface, OSP hardened, may only occupy slot 1 of a function group or a growth slot, uses

PTM optics for LX interfaces, supports private lines, when in G1 slot, only the optical ports (17-24) of the LNW74 function

Hybrid 1000BASE-X and 100

BASE-LX Ethernet interface, may only occupy slot 1 of a function group or a growth slot, uses PTM optics, supports

RPR protection and enhanced Ethernet

QoS

Notes:

1. 1. In order to support Ethernet and SAN packs in both Slot 1 and 2 of a

Function Group or Growth Slot, DMX must be equipped with VLF Mains

(LNW59) and R7.0 software.

2. 2. DMX does not allow installation of two packs with electrical interfaces in adjacent slots within the same Function Unit or Growth Slot. Therefore, in systems equipped with LNW59 VLF mains, LNW66 and LNW71 packs can reside in either Slot 1 or Slot 2 of a group, but not both at the same time.

However, another optical (Ethernet or SONET) pack may be installed in the other slot. In non-VLF equipped shelves, LNW66 and LNW71 can only occuppy Slot 1 of a paticular group.

365-372-300

Issue 8.0 September 2006

A - 9

Ethernet Circuit Packs

: Ethernet/SAN

4-Port GbE-PL Private Line

Fast Ethernet circuit pack

(LNW63)

The GbE-PL Private Line Gigabit Ethernet (LNW63) circuit pack provides point-to-point (Ethernet Private Line Service) data transport at the 1000 Mb/s rate. The GbE-PL circuit pack supports generic framing procedure (GFP) encapsulation and STS virtual concatenation.

The LNW63 circuit pack supports STS-1, STS-3c, STS-12c cross-connects. LNW63 has 4 VCGs, and each VCG can have up to 21

STS-1 tribs and the total available backplane link space is 48 STS-1s to

Main-1 and 48 STS-1s to Main-2. The tribs may be assigned freely, all

VCGs have access to all tribs (

Figure A-1 shows the LNW63 circuit

pack).

Each VCG can use 1 STS-1, or up to 21 (STS-1-xv, x=1-21) tributaries.

Each VCG can use 1 STS-3c, or up to 7 (STS-3-xv, x=1-7) or 1

STS-12c tributary.

Figure A-1 LNW63 Gigabit Ethernet (Private Line) Circuit Pack

1 2 3

1000BASE-X

LAN 1 GFP VCG1

LAN 2 GFP VCG2

A - 1 0

LAN 3 GFP VCG3

LAN 4

GFP VCG4

JK-E-15.eps

Legend:

1 External Ethernet Port

2 Generic Framing Procedure

3 Virtual Concatenation Group

LNW63 packs can be placed in Slot 1 of any function group or growth slot in the shelf (A1-G1) and DMX supports a total add/drop capacity of 20 private line GbE ports if all slots are equipped with LNW63 circuit packs.

For detailed information about Ethernet technologies, refer to

freely, all VCGs have access to all tribs ( Figure A-2 shows the LNW64

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

: Ethernet/SAN

When the LNW63 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

The LNW63 contains 4 internal 1000 Mbps WAN ports supporting enhanced private line services such as high-order virtual concatenation

(STS) and Link Capacity Adjustment Scheme (LCAS). The LNW63 and PTM optics are also OSP hardened for outside plant applications.

100BASE-T/1000BASE-T Electrical PTM (R7.0)

The LNW63 now supports a dual function electrical PTM that is provisionable for 100 or 1000 Mbps traffic. It conforms to the

The electrical PTM can be installed in ports 1-4 of the LNW63.

365-372-300

Issue 8.0 September 2006

A - 1 1

Ethernet Circuit Packs

: Ethernet/SAN

8-port GbE-PL Private Line

Fast Ethernet circuit pack

(LNW64)

The 8-port GbE-PL Private Line Gigabit Ethernet (LNW64) circuit pack provides point-to-point (Ethernet Private Line Service) data transport at the 1000 Mb/s rate. The GbE-PL circuit pack supports generic framing procedure (GFP) encapsulation and STS virtual concatenation.

LNW64 supports STS-1 and STS-3c cross-connections with or without

VCAT, and STS-12c cross-connections without VCAT. All ports are capable of transmitting at wire speed (1000 Mbps) simultaneously, making full capacity of the pack 168 STS-1s. LNW64 has 8VCGs, and each VCG can have up to 21 STS-1 tribs. The tribs may be assigned

circuit pack).

Each VCG can use 1 STS-1, or up to 21 (STS-1-xv, x=1-21) tributaries.

Each VCG can use 1 STS-3c, or up to 7 (STS-3-xv, x=1-7) or 1

STS-12c tributary.

Figure A-2 LNW64 Gigabit Ethernet (Private Line) Circuit Pack

1000BASE-X

LAN 1

LAN 2

LAN 3

LAN 4

LAN 5

LAN 6

LAN 7

LAN 8

GFP VCG1

GFP VCG2

GFP VCG3

GFP VCG4

GFP Vc5

GFP VCG6

GFP VCG7

GFP VCG8

JK-E-20.eps

Legend:

1 External Ethernet Port

2 Generic Framing Procedure

3 Virtual Concatenation Group

A - 1 2

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

: Ethernet/SAN

With VLF Mains, LNW64 can occupy both slots 1 and 2 of a

Function/Growth unit, making the total capacity of a systems fully populated with LNW64s, 80 GbE private line ports. When the LNW64 is installed in a Growth slot, only the optical PTMs can be used.

For detailed information about Ethernet technologies, refer to

When the LNW64 circuit packs occupies one slot of a Function Unit group, the other must be populated with an apparatus blank.

The LNW64 contains 8 internal 1000 Mbps WAN ports supporting enhanced private line services such as high-order virtual concatenation

(STS) and Link Capacity Adjustment Scheme (LCAS). The LNW64 and PTM optics are also OSP hardened for outside plant applications.

365-372-300

Issue 8.0 September 2006

A - 1 3

Ethernet Circuit Packs

: Ethernet/SAN

FC/FICON/ESCON SAN circuit pack (LNW73 and

LNW73C)

LNW73 and LNW73C circuit pack provides point-to-point SAN transport. The LNW73/73C circuit pack supports generic framing procedure (GFP) encapsulation and STS virtual concatenation. The

LNW73/73C circuit pack can be provisioned to operate in the STS-1 or

STS-3c mode. In the STS-1 mode, the The LNW73/73C circuit pack supports up to 24 VCG ports. In the STS-3c mode, the The

LNW73/73C circuit pack supports up to 16 VCG ports.

The LNW73/73C circuit pack supports STS-1, STS-3c, STS-12c cross-connect. The LNW73/73C has 4 VCGs, and each VCG can have up to 48 tribs (maximum capacity of 48 virtual concatenated STS-1s) and the total available backplane link space is 48 STS-1s to Main-1 and

48 STS-1s to Main-2. The tribs may be assigned freely, all VCGs have access to all tribs (

Figure A-1

shows the The LNW73/73C circuit pack).

When the The LNW73/73C is provisioned for STS-1 mode, each VCG can use 1 STS-1, or up to 48 (STS-1-xv, x=0-48) tributaries. When the

LNW63 is provisioned for STS-12c mode, each VCG can use 1

STS-3c, or up to 16 (STS-3-xv, x=1-16) or 1 STS-12c tributary. The circuit pack mode is user provisionable.

Figure A-3 LNW73/73C Gigabit Ethernet (Private Line) Circuit

Pack (STS-1 Mode)

1000BASE-X

LAN 1 GFP VCG1

LAN 2

GFP VCG2

LAN 3

LAN 4

GFP VCG3

GFP VCG4

JK-E-15.eps

Legend:

1 External Ethernet Port

2 Generic Framing Procedure

3 Virtual Concatenation Group

A - 1 4

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

: Ethernet/SAN

The LNW73C differs from the LNW73 in that it enables compression of SAN traffic.

The LNW73C is able to compress asychronous Fibre Channel traffic and conserve up to 50% of bandwidth versus uncompressed asynchronous FC traffic in typical applications.

Compression for asynchronous FC traffic is pre-standard and will be standardized by FC-BB-4. The R6.0 implementation of SAN compression enables a high throughput of up to two full-line rate

FC-2G interfaces in a single pack.

The R6.0 implementation of SAN compression enables a high throughput of up to two full-line rate FC-2G interfaces in a single pack.

LNW73/73C packs can be placed in Slot 1 of any function group or growth slot in the shelf (A1-G1) and DMX supports a total add/drop capacity of 20 private line GbE ports if all slots are equipped with

LNW73/73C circuit packs.

For detailed information about Ethernet technologies, refer to

STS-1 virtual concatenation. (Refer to Figure A-4 .) Connections to the

When the LNW73/73C circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

The LNW73/73C contains 4 internal 1000 Mbps WAN ports supporting enhanced private line services such as low-and high order virtual concatenation (VT1.5/STS) and Link Capacity Adjustment

Scheme (LCAS). The LNW73/73C and PTM optics are also OSP hardened for outside plant applications.

365-372-300

Issue 8.0 September 2006

A - 1 5

Ethernet Circuit Packs

10/100T Fast Ethernet circuit pack (LNW66)

: Ethernet/SAN

The 10/100T Fast Ethernet (LNW66) circuit pack has 24 LAN ports and provides data transport at the rate of 10/100 Mb/s using standard

Ethernet bridging, generic framing procedure (GFP) encapsulation, and

100BASE-TX interface are via multi-service connectors on the DMX system backplane.

Each LAN port performs protocol transparent filtering and bridging of incoming media access control (MAC) frames. MAC frames with a destination address on the local bus are filtered by the 10/100T circuit pack to prevent unnecessary transmission of frames over the wide area network (WAN). The ports auto-negotiate mode (full/half duplex), speed (10/100 Mb/s), and flow control when interfacing with other

802.3-compliant devices over twisted pair media. The LNW66 can group (concatenate) between 1 and 21 STS-1 SONET tributaries.

Figure A-4 LNW66 Fast Ethernet Circuit Pack

1 2 3 4

A - 1 6

24 v1

Ethernet

Switch v2

GFP VCG1

GFP VCG2 nc-dmx-093

Legend:

1 External Ethernet Port

2 Virtual Concatenation Group Port

3 Generic Framing Procedure

4 Virtual Concatenation Group

For detailed information about Ethernet technologies, refer to

(GFP) encapsulation, and STS-1 virtual concatenation. (Refer to Figure

The 10/100T circuit pack must be housed in slot 1 of a Function Unit group (A, B, C, or D-- Not G) and is not equipment protected.

However, facility protection can be provided through the WAN via

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

: Ethernet/SAN

SONET UPSR or through the spanning tree algorithm. When the

10/100T circuit pack occupies slot 1 of a Function Unit group, slot 2 must be populated with a 177D apparatus blank or an LNW98

Detectable Blank circuit pack.

365-372-300

Issue 8.0 September 2006

A - 1 7

Ethernet Circuit Packs

: Ethernet/SAN

1GSX Gigabit Ethernet circuit pack (LNW67)

The 1GSX (LNW67) circuit pack provides a short-reach, 2-port,

1000BASE-SX, IEEE 802.3-compliant interface. The 1GSX circuit pack provides short-reach high-speed optical data transport at the rate of 1 Gb/s using standard Ethernet bridging, generic framing procedure

A-5 .) Fiber access is provided by two LC-type connector pairs on the

circuit pack faceplate. The 1GSX circuit pack transmits signals at a wavelength of 850 nm. The SX ports require a 50

µ m or 62.5

µ m multimode optical cable and transmit up to 550 meters. The LNW67 can group (concatenate) between 1 and 21 STS-1 SONET tributaries.

Figure A-5 Gigabit Ethernet Circuit Pack

1 2 3 4

A - 1 8 v1

GFP VCG1

1 v2

Ethernet

Switch v3

GFP VCG2

GFP VCG3 v4 GFP VCG4 nc-dmx-094

Legend:

1 External Ethernet Port

2 Virtual Concatenation Group Port

3 Generic Framing Procedure

4 Virtual Concatenation Group

The 1GSX circuit pack performs protocol transparent filtering and bridging of incoming media access control (MAC) frames. MAC frames with a destination address on the local bus are filtered by the

1GSX circuit pack to prevent unnecessary transmission of frames over the wide area network (WAN).

For detailed information about Ethernet technologies, refer to

Figure A-5 .) The 1GLX transmits 1310-nm signals

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

: Ethernet/SAN

The 1GSX circuit pack must be housed in slot 1 of any Function Unit group (A, B, C, D or G) and is not equipment protected. However, facility protection can be provided via SONET UPSR or through the spanning tree algorithm. When the 1GSX circuit pack occupies slot 1 of a Function Unit group, slot 2 must be populated with a 177D apparatus blank or an LNW98 Detectable Blank circuit pack.

Up to 10 1GSX ports are addressable when all Function Unit groups are equipped with 1GSX circuit packs.

365-372-300

Issue 8.0 September 2006

A - 1 9

Ethernet Circuit Packs

: Ethernet/SAN

1GLX Gigabit Ethernet circuit pack (LNW68)

1000BASE-X/100BASE-LX

(LNW70) hybrid optical ethernet interface

The 1GLX (LNW68) circuit pack provides a long-reach, 2-port,

1000BASE-LX, IEEE 802.3-compliant interface. Except for the optical span length, it is functionally the same as the LNW67 1GSX circuit pack. (Refer to

using multimode or single mode optical cable. The port can transmit up to 10000 meters on single-mode fiber. The LNW68 can group (concatenate) between 1 and 21 STS-1 SONET tributaries.

This 8-port Ethernet interface provides 4-ports for short-reach and/or long-reach high-speed optical data transport at the rate of 1 Gb/s and

4-ports for optical 100BASE-LX transport at 100 Mbps using standard ethernet switching IEEE 802.1, standard encapsulation according to

ANSI T1X1.5/2000-024R4 (ITU G.7041), virtual concatenation according to ITU G.707.

The LNW70 circuit pack supports STS-1, STS-3c, STS-12c cross-connect. LNW70 may have up to 32 VCGs, and each VCG can have up to 48 tribs (maximum capacity of 48 virtual concatenated

STS-1s) and the total available backplane link space is 48 STS-1s to

Main-1 and 48 STS-1s to Main-2. The tribs may be assigned freely, all

VCGs have access to all tribs.

When the LNW70 is provisioned for STS-1 mode, each VCG can use 1

STS-1, or up to 48 (STS-1-xv, x=0-48) tributaries. When the LNW70 is provisioned for STS-12c mode, each VCG can use 1 STS-3c, or up to

16 (STS-1-xv, x=0-16) or 1 STS-12c tributary. The circuit pack mode is user provisionable.

Connections to the LNW70 are PTMs on the circuit pack faceplate.

100BASE-T/1000BASE-T Electrical PTM for the LNW70 (R6.0)

The LNW70 now supports a dual function electrical PTM that is provisionable for 100 or 1000 Mbps traffic. It conforms to the

The electrical PTM can only be installed in ports 1-4 of the LNW70.

Ports 5-8 are always reserved for 100BASE-LX optical Fast Ethernet interfaces.

A - 2 0

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

365-372-300

Issue 8.0 September 2006

The figure below shows the LNW70 in Private Line mode.

Figure A-6 LNW70 In Private Line Mode

1000BASE-X/ 100/1000BASE-T

LAN 1 GFP VCG1

LAN 2

LAN 3

GFP

VCG2

VCG3

LAN 4

100BASE-FX

LAN 5

LAN 6

GFP

VCG4

VCG5

VCG6

LAN 7

LAN 8

GFP

VCG7

VCG8

JK-E-1.eps

Legend:

1 External Ethernet Port

2 Generic Framing Procedure

3 Virtual Concatenation Group

The figure below shows the LNW70 in Switched (802.1q or

Transparent) mode.

Figure A-7 LNW70 In Switched Mode

1 2 3 4

: Ethernet/SAN

2 v1 v2

GFP

3 v3

Ethernet

Switch v4

GFP

VCG1

VCG2

VCG3

VCG4

VCG5

VCG6

VCG7

VCG8

JK-E-16.eps

A - 2 1

Ethernet Circuit Packs

: Ethernet/SAN

Legend:

1 External Ethernet Port

2 Generic Framing Procedure

3 Virtual Concatenation Group

For detailed information about Ethernet technologies, refer to

Figure A-8 shows the 10/100-PL circuit pack in the STS-1 mode.)

The LNW70 may occupy slot 1 of any Function Unit group on the shelf

(including Growth slots), and up to 20 1000BASE-X and

20 100BASE-LX ports are addressable when all Function Unit groups are equipped with LNW70 circuit packs. When the LNW70 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank. However, facility protection can be provided through the WAN via SONET.

A - 2 2

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

: Ethernet/SAN

10/100-PL Private Line Fast

Ethernet circuit pack

(LNW71)

The 10/100-PL Private Line Fast Ethernet (LNW71) circuit pack provides point-to-point (Ethernet Private Line Service) data transport at the 10/100 Mb/s rate. The 10/100-PL circuit pack supports generic framing procedure (GFP) encapsulation and STS-1 virtual concatenation. The LNW71 circuit pack can be provisioned to operate in the STS-1 or STS-3c mode. In the STS-1 mode, the 10/100-PL circuit pack supports up to 24 VCG ports. In the STS-3c mode, the

10/100-PL circuit pack supports up to 16 VCG ports.

When the LNW71 is provisioned for STS-1 (concatenate) mode, each

VCG can use 1 (STS-1v) or 2 (STS-2v) tributaries. When the circuit pack is provisioned for STS-3c mode, all VCGs can use 1 STS-3c or 1

STS-1 tributary. The circuit pack mode is user provisionable.

(

Connections to the 100BASE-TX interface are via multi-service connectors on the DMX system backplane.

Figure A-8 LNW71 Fast Ethernet (Private Line) Circuit Pack

(STS-1 Mode)

1 2 3

LAN 1

LAN 2

LAN 3

LAN 4

GFP VCG1

GFP VCG2

GFP VCG3

GFP VCG4

365-372-300

Issue 8.0 September 2006

LAN 24 GFP VCG24 nc-dmx-248

Legend:

1 External Ethernet Port

2 Generic Framing Procedure

3 Virtual Concatenation Group

The ports auto-negotiate speed (100 Mb/s) and flow control when interfacing with other 802.3-compliant devices over twisted pair media.

The ports supports the full duplex mode only.

A - 2 3

Ethernet Circuit Packs

: Ethernet/SAN

For detailed information about Ethernet technologies, refer to

The 10/100-PL circuit pack must be housed in slot 1 of a Function Unit group (A, B, C, D) and is not equipment protected. However, facility protection can be provided through the WAN via SONET UPSR.

When the 10/100-PL circuit pack occupies slot 1 of a Function Unit group, slot 2 must be populated with a 177D apparatus blank or an

LNW98 Detectable Blank circuit pack.

A - 2 4

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

: Ethernet/SAN

100BASE-LX/100BASE-TX

(LNW74) hybrid optical/electrical Ethernet interface

This 24-port Ethernet interface provides 8-ports for optical

100BASE-LX transport at 100 Mbps using standard GFP encapsulation according to ANSI T1X1.5/2000-024R4 (ITU G.7041). The LNW74 also provides 16 electrical ports for the 100BASE-TX interfaces. These electrical ports transmit at 10/100 Mbps using standard ethernet IEEE

802.1, standard encapsulation according to ANSI T1X1.5/2000-024R4

(ITU G.7041), LCAS according to IYU G.7042, and standard STS-1 and VT virtual concatenation according to ITU G.707. The LNW74 electrical interfaces can transmit signals across spans as long as 100 meters.

The 10/100-PL circuit pack supports STS-1, STS-3c, and VT1.5 (all may be used on different ports). Up to 336 VT1.5s may be used with between 0 and 63 assigned to any VCG. When VT mapping is selected,

12 STS-1s are reserved for the 336 VTs. Then 36 STS-1s are reserved for STS-1 VCAT or STS-3cs. Otherwise there is no VT mapping. In this case, 48 STS-1s are available for STS-1 VCAT or STS-3cs. Each

VCG can use 1 (STS-1) or (STS-1-xv, x=0-3) or 1 (STS-3c), or

(VT1.5-xv, x=0-63) tributaries. The circuit pack mode is user provisionable.

Connections to the 100BASE-TX interface are via multi-service connectors on the DMX system backplane. Fiber access for optical ports is provided by LC-type connector pairs on the LNW74 faceplate.

365-372-300

Issue 8.0 September 2006

A - 2 5

Ethernet Circuit Packs

A - 2 6

: Ethernet/SAN

The LNW74 circuit pack is designed specifically to support Fast

Ethernet Private Line applications. Each LNW74 circuit pack can support 24 private lines.

Figure A-9 LNW74 Fast Ethernet Hybrid (optical/electrical) Pack

1 2 3

100BASE-TX

LAN 1

LAN 2

GFP

VCG1

VCG2

LAN15

LAN16

100BASE-FX

LAN17

LAN18

GFP

VCG15

VCG16

GFP

VCG17

VCG18

LAN23

LAN24

GFP

VCG23

VCG24

JK-E-2.eps

Legend:

1 External Ethernet Port

2 Generic Framing Procedure

3 Virtual Concatenation Group

The electrical ports auto-negotiate speed (at 10/100 Mbps for TX ports only-- LX ports operate at 100 Mbps only) and flow control when interfacing with other 802.3-compliant devices over twisted pair media.

The ports supports the full duplex mode only. Optical ports on the

LNW74 do not auto-negotiate flow control.

For detailed information about Ethernet technologies, refer to

The LNW74 may occupy slot 1 of any Function Unit group on the shelf

(including Growth slots), and up to 40 100BASE-LX ports and 64

100BASE-TX ports are addressable when all Function Unit groups are equipped with LNW74 circuit packs. When the LNW74 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank. The LNW74 may also be housed in the Growth slot

(G1), but only the optical ports are supported in the Growth slot.

365-372-300

Issue 8.0 September 2006

Ethernet Circuit Packs

1000BASE-X/100BASE-LX

(LNW78) RPR Ethernet interface

: Ethernet/SAN

This 8-port Ethernet interface provides 4-ports for short-reach and/or long-reach high-speed optical data transport at the rate of 1 Gb/s and

4-ports for optical 100BASE-LX transport at 100 Mbps. The first 4 ports (1-4) are for the GbE traffic (ports 3 and 4 are not available in

R6.0) and the second 4 ports (5-8) are for FE traffic. The LNW78 utilizes PTM optics, allowing you to equip additional ports as necessary. In R7.0, LNW78 adds support for the electrical

10/1000BASE-TX, electrical Ethernet PTM. This PTM may only occupy ports 1 and 2. The LNW78 also supports similar port, switching, and traffic management capabilities as the LNW70.

The LNW78 supports standards compliant RPR switching per IEEE

802.17. LNW78 will support one RPR instance in R6.0 and two in the future. The LNW78 provides two internal Virtual Concatenation Group

(VCG) WAN ports (will support 4 in the future) with a total capacity of

2.5 Gbps capacity for Ethernet RPR traffic (24 STS-1s in each direction).

Beginning in R7.0, LNW78 adds support for EoS services on VCG ports 17-22. VCGs 17-22 are not preceded by RPR IF modules residing between the Ethernet switch and GFP wrapper device. Therefore, traffic exiting the switch proceeds directly to the GFP wrapper device and then on to the VCG.

The LNW78 circuit pack supports STS-1, STS-3c, STS-12c cross-connect. Each VCG can have up to 24 tribs (maximum capacity of 48 virtual concatenated STS-1s) and the total available backplane link space is 24 STS-1s to Main-1 and 24 STS-1s to Main-2. The tribs may be assigned freely, all VCGs have access to all tribs.

Connections to the LNW78 are PTMs on the circuit pack faceplate.

Figure A-10 LNW78 RPR Ethernet Interface

1 2 3 4

RPR

IF 1

Ethernet

Switch

RPR

IF 2

GFP

VCG1

VCG2

VCG3

GFP VCG4

VCG17

VCG22

JK-E-17.eps

365-372-300

Issue 8.0 September 2006

A - 2 7

Ethernet Circuit Packs

: Ethernet/SAN

Legend:

1 External Ethernet Port

2 RPR IF

3 Generic Framing Procedure

4 Virtual Concatenation Group

For detailed information about Ethernet technologies, refer to

switched mode. Refer to Figure A-15 on page A-36 and/or Figure A-17 on page A-38 for figures depicting the LNW70 in switched mode.

Beginning in R7.0, with the use of true 0x1 and the LNW59 VLF Main,

LNW78 can occupy slots 1 and 2 of and Function or Growth group.

This can increase the overall capacity of the system to 20 RPR GbE

(optical only) ports and 20 RPR FE (optical only) ports per shelf.

Certain restrictions apply when the LNW78 is equipped with electrical

PTMs. For a detailed description of circuit pack/slot equipage restrictions in 0x1, refer to Chapter 5.

Prior to Release 7.0 (and when VLF Mains are not used), if the LNW78 circuit packs occupy slot 1 of a Function Unit group, slot 2 must be populated with an apparatus blank.

100BASE-T/1000BASE-T Electrical PTM for the LNW78 (R7.0)

The LNW78 now supports a dual function electrical PTM that is provisionable for 100 or 1000 Mbps traffic. It conforms to the

The electrical PTM can only be installed in ports 1 and 2 of the

LNW78. Ports 5-8 are always reserved for 100BASE-LX optical Fast

Ethernet interfaces (ports 3 and 4 are not accessible in R7.0).

A - 2 8

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

Ethernet Transport

Overview

A DMX network accepts Ethernet frames at an ingress port and transmits them out of one or more egress ports. The egress port(s) can be on the same network element or on a different network element. If it is on a different network element, Ethernet frames are transmitted over a SONET network. To transport an Ethernet frame across the SONET network, the Ethernet Frame is moved between a LAN port and the

SONET network. (Refer to the following figure.)

Figure A-11 Ethernet Transport Through DMX

SONET Network

SONET Interfaces

STS-1

Virtual

Concatenator

(ITU G.707)

STS-1/STS-3c

Virtual

Concatenator

(ITU G.707)

Switched

Service

GFP Mapper

(ITUG.7041)

VCG (WAN) Ports

GFP Mapper

(ITUG.7041)

Private Line

Service

Ethernet Switch

Ethernet

Circuit

Pack

LAN Ports

Physical Ethernet Transceiver

LAN Ports

MA-DMX-343

365-372-300

Issue 8.0 September 2006

A - 2 9

Ethernet Transport

: Ethernet/SAN

The following occurs to transport an Ethernet frame over a SONET network:

• The DMX accepts an Ethernet Frame at an ingress LAN Port.

• The Ethernet frame is accepted at an Ethernet switch’s LAN port for switched services, processed, and then transmitted out one or more of its LAN and/or VCG (WAN) port(s). For the LNW71 or

LNW74 10/100-PL circuit pack (which supports only nonswitched services), the Ethernet frame is sent directly to the

GFP mapper via a VCG port.

• The generic framing procedure (GFP) mapper encapsulates the

Ethernet frame into a GFP Frame.

• The Virtual Concatenator maps the Ethernet stream into one or more SONET tributaries (timeslots). This allows the network to carry traffic (Ethernet stream) at higher speeds than allowed by a single SONET tributaries (time slot). The group of virtually concatenated tributaries is referred to as a Virtual Concatenation

Group (VCG).

• The VCG is then placed on SONET tributaries and transmitted over the SONET network.

A - 3 0

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Generic framing procedure

(GFP)

Generic Framing Procedure (GFP) is used to encapsulate Ethernet frames for transport over a SONET network. The DMX uses frame-based GFP with the core header and no optional extension headers. The DMX Ethernet circuit packs don’t use Frame Check

Sequence (FCS), except for the LNW70 and LNW74 which have a provisionable FCS setting (on/off).

To encapsulate an Ethernet frame, the Ethernet preamble and Start of

Frame Delimiter (SFD) fields are removed from the frame. A Type header and check (tHEC) is added to the Ethernet frame creating a GFP payload. The GFP payload is then scrambled and a Core header is added. The GFP frame is then sent to the Virtual Concatenator. The following figure shows the format of a GFP frame.

Figure A-12 GFP Frame Format

Octets

A. Original Ethernet Frame

Preamble

Start of Frame Delimiter (SFD)

Destination Address (DA)

Source Address (SA)

Stacked VLAN TAG

802.1Q VLAN TAG

Length/Type

Octets

B. GFP Frame

Pay Load Indicator

2 cHEC

Type

2 tHEC

0 or 4

Data and Pad

Frame Check Sequence

Note:

1 - May not be present

2 - Up to 1536 for LNW66, LNW67, and LNW68 circuit packs

Up to 10240 for LNW71 circuit packs

Raw Ethernet Frame

Core

Header

Payload

Header

Payload

MA-DMX-344

365-372-300

Issue 8.0 September 2006

A - 3 1

Ethernet Transport

: Ethernet/SAN

The GFP fields are described in the following table.

Section

Core Header

Payload

Header

Payload

Field

Payload Indicator

(PLI)

Core Header Error

Control (cHEC)

Type

Type Header Error

Control (tHEC)

Description

Binary number representing the number of octets in the GFP payload.

CRC-16 checksum that protects the integrity of the contents of the Core Header.

The type of information contained in the

Payload field. The value is 01hex.

CRC-16 checksum that protects the integrity of the contents of the Type Field.

The raw Ethernet Frame (that is, the original

Ethernet Frame without the Preamble and SFD.

In the opposite direction when the GFP Mapper receives a GFP frame from the Virtual Concatenator, it removes the Core Header and, using the cHEC field, performs a Header Error Check. If the header is correct, the payload area of the GFP is then descrambled and the Type field and tHEC in the GFP header are checked for correctness. The

Ethernet frame is extracted and the Preamble and SFD are added.

The GFP mapper at the far end of the network inserts idle GFP frames when there are no Ethernet frames to send. The near end GFP Mapper discards any idle GFP frames it receives over the SONET network. The idle GFP frames are not forwarded to the Ethernet Switch. (The

LNW71 circuit pack does not contain an Ethernet switch.)

The GFP Mapper contains GFP queues that are used to store Ethernet frames while they are being processed.

The Generic Framing Procedure is defined in ITU-T G.7041/Y.1303 and ANSI T1X1.105 Sections 7.3.2 and 7.3.3.

A - 3 2

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Virtual concatenation

Virtual Concatenation is a standard inverse multiplex scheme for transporting a payload using multiple channels each of which has a lower capacity than the payload to be transported. It allows finer granularity in allocating the transport bandwidth than is available in standard contiguous concatenation (STS-3c, STS-12c, STS-48c etc.).

For example, an STS-1 tributary has a usable bandwidth of approximately 48.4 Mb/s. This is too slow for a 1 Gbits/s Ethernet stream. An STS-48c tributary has approximately 2.4 Gb/s which would waste 1.4 Gb/s of bandwidth if used to carry a 1 Gb/s Ethernet stream.

Using virtual concatenation, 21 STS-1 tributaries can be used providing an effective rate of approximately 1.02 Gb/s. Fewer STS-1 tributaries can be virtually concatenated to provide sub-rate (fractional rate) service.

The grouped SONET tributaries form a Virtual Concatenation Group

(VCG). A VCG is treated as a single logical serial byte stream whose payload capacity equals that of the sum of the payload capacities of the constituent SONET tributaries. The following figure shows a virtual concatenation group.

Figure A-13 Virtual Concatenation Group

1 Gb/s Ethernet

365-372-300

Issue 8.0 September 2006

Virtual

Concatenation

Up to 21 STS-1s

A Virtual Concatenation Group

MA-DMX-345

Individual tributaries in the VCG are independently transported through the SONET network. Only the initial and final SONET nodes perform the Virtual Concatenation. Since the VCGs are invisible to the intermediate SONET nodes, the intermediate nodes only need to transport normal SONET traffic and do not need to understand VCGs.

This allows the tributaries to be transported through equipment which does not handle VCGs.

A - 3 3

Ethernet Transport

: Ethernet/SAN

Differential Delay Buffers

Because the individual tributaries of a virtual concatenation group

(VCAT) can take different paths through the SONET network, they may experience different delays through the network.

The table below provides the differential delay buffers for each of the

Ethernet circuit packs.

Circuit Pack

Name

LNW63

LNW66/67/68

LNW71

LNW70/78

LNW73/73C

LNW74

Delay (in milliseconds)

100ms

16ms

32ms

50ms

120ms

64ms

SONET Transport

Ethernet circuit packs contain LAN ports and VCG ports. The LAN ports connect to external Ethernet equipment. The VCG ports connect to the OLIUs via Generic Framing (GFP) Mappers and Virtual

Concatenation Groups (VCGs).

The OLIUs contain the hardware that perform the SONET cross-connections and process traffic at the SONET tributary level.

They do not know about the embedded Ethernet frames or Virtual

Concatenation Groups.

Connections to the SONET network can be configured to provide

SONET layer protection. DMX supports three types of SONET protection: Unidirectional Path Switched Rings (UPSRs), Bidirectional

Line Switched Rings (BLSRs) and 1+1.

DMX supports transport of Ethernet frames on the following:

• UPSR tributaries

• Unswitched UPSR tributaries

• BLSR tributaries

• 1+1 point-to-point tributaries

• 0x1Sn tributaries

• Ethernet-to-Ethernet hairpin cross-connections

A - 3 4

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

GFP VCG

Ethernet

Switch

GFP VCG

L24

A. Fast Ethernet (LNW66)

Protected Tributaries

On protected tributaries, both rings carry the same traffic placed in the same tributaries (time slots), but in opposite directions in the case of

UPSR. UPSR protected cross-connections are provisioned as one

1wayPR cross-connections and two 1way cross-connections. BLSR protected cross-connections are provisioned using 1way cross-connections only.

Figure A-14 SONET Protected Cross-Connections

Main 1

OC-48 or

OC-192

OC-48 or

OC-192

Main 2

GFP

Ethernet

Switch

GFP

VCG

Main 1

OC-48 or

OC-192

OC-48 or

OC-192

Main 2

B. Gigabit Ethernet (LNW67 or LNW68)

MAC

GFP VCG

L24

MAC

V24

GFP VCG

C. Fast Ethernet (LNW71 or LNW74)

Main 1

OC-48 or

OC-192

OC-48 or

OC-192

Main 2

MAC

Main 1

GFP VCG

MAC

GFP

VCG

OC-48 or

OC-192

GFP VCG

OC-48 or

OC-192

Main 2

C. Gigabit/Fast Ethernet (LNW70)

L1--> L4= 1000BASE-X/ L5-->L8= 100BASE-FX

JK-E-3.eps

On LNW66, LNW67, and LNW68 circuit packs, only the odd numbered VCG ports can be used for SONET protected cross-connections because some of the hardware associated with the even numbered VCG ports is used to protect the odd number ports.

On the LNW63, LNW71, LNW74, and LNW70 circuit packs, all VCG ports can be used. When the LNW71 is in the STS-1 mode, up to 24 ports are supported, and up to 16 ports are supported in the STS-3c mode. For the LNW63, LNW70, and LNW74, circuit packs, all ports are supported regardless of STS mode. The picture above depicts the

LNW70 in private line mode. The LNW70 can also function in

365-372-300

Issue 8.0 September 2006

A - 3 5

Ethernet Transport

: Ethernet/SAN

A - 3 6

Unprotected Tributaries

In the case of UPSR unprotected tributaries, the two sides of the ring carry different traffic. Each VCG is connected to only one side of the ring.

1-way unswitched cross-connections provide unprotected SONET connections to Ethernet circuit packs on a UPSR. On the other hand, only 1way cross-connections are used on BLSR w/NUT. Each can be used to form two individual connections. One VCG is connected to

MAIN 1 while the other VCG is connected to Main 2. The following figure shows examples of the multipoint cross-connections provisioned by way of 1-way and 1-way unswitched cross-connects.

Figure A-15 Multi-point Cross-connections (unprotected)

GFP

Ethernet

Switch

GFP

L24

A. Fast Ethernet (LNW66)

VCG

Main 1

OC-48 or

OC-192

OC-48 or

OC-192

Main 2

MAC

GFP VCG

Main 1

OC-48 or

OC-192

L13

MAC

V13

GFP VCG

L24

MAC

GFP VCG

V24

C. Fast Ethernet (LNW71 in STS-1 Mode)

OC-48 or

OC-192

Main 2

GFP

VCG

Main 1

OC-48 or

OC-192

Ethernet

Switch

GFP

VCG

OC-48 or

OC-192

Main 2

E. RPR Gigabit/FastEthernet (LNW78)

L1--> L2= 1000BASE-X/ L5-->L8= 100BASE-FX

Ethernet

Switch

GFP

VCG

GFP VCG

B. Gigabit Ethernet (LNW67 and LNW68)

Main 1

OC-48 or

OC-192

OC-48 or

OC-192

Main 2

MAC

GFP VCG

Main 1

MAC

GFP

VCG

OC-48 or

OC-192

GFP VCG

OC-48 or

OC-192

Main 2

D. Gigabit/Fast Ethernet (LNW70)

L1--> L2= 1000BASE-X/ L5-->L6= 100BASE-FX

MAC

GFP VCG

Main 1

MAC

GFP

VCG

OC-48 or

OC-192

MAC

GFP

F. Gigabit Ethernet (LNW63)

VCG

OC-48 or

OC-192

Main 2

JK-E-4.eps

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

On the LNW66, LNW67, and LNW68, LNW71, LNW74, and LNW78 circuit packs, the odd number VCGs are paired with the next higher number VCG (for example, VCG 1 is paired with VCG 2, and VCG 3 is paired with VCG 4.) For example, VCG 2 must be connected to one

OLIU when VCG 1 is provisioned to be connected to the other OLIU.

Both cross-connections use the same SONET tributaries. The following figure shows an example of the VCG port pairing.

Figure A-16 Gigabit Multipoint Cross-Connections (Unprotected)

Ethernet

Switch

Main 1

SONET Ring

Main 2

Ethernet

Switch

Main 2 Main 1

VCG 1 Connect to far end VCG2

VCG 2 Connect to far end VCG1

MA-DMX-348

Multipoint cross-connections can either be used as two unprotected point-to-point connections or as part of a packet ring. If they are used as part of a packet ring, the Ethernet switch will process traffic received on one side of the packet ring before it is forwarded out the other side of the ring.

365-372-300

Issue 8.0 September 2006

A - 3 7

Ethernet Transport

: Ethernet/SAN

Ethernet

Switch

On the LNW63 and LNW70, any VCG can be connected to any OLIU.

The following figure shows an example of the VCG port pairing. As the figure below demonstrates, V1 in the shelf on the left could be connected to V1 in the shelf on the right. it is also possible to connect

VCGs in the same fashion as the packs described above. Below, this is shown by V3 being connected to V4, and V4 being connected to V3.

Figure A-17 LNW63 and LNW70 Gigabit Multipoint

Cross-Connections (Unprotected)

Main 1 Main 2

SONET Ring

Main 2

VCG 1 Connect to far end VCG1

VCG 2 Connect to far end VCG2

VCG 3 Connect to far end VCG4

VCG 4 Connect to far end VCG3

Main 1

Ethernet

Switch

MA-DMX-348_b

A - 3 8

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

L13

L24

MAC

L16

MAC

The LNW71 Ethernet circuit pack can operate in either STS-1 or

STS-3c mode. The pairing of its LAN ports for multipoint cross-connections is dependent on the mode. Traffic that is transmitted out of one LAN port is received on its paired LAN port. The following figure shows an example of multipoint cross-connections in the STS-1 and STS-3c modes.

Figure A-18 LNW71 Multipoint Cross-Connections (Unprotected)

GFP VCG

Main 1

GFP VCG

SONET Ring

Main 2

VCG GFP

MAC

L13

GFP VCG

Main 2 Main 1

VCG GFP

GFP VCG

Note: In STS1 Mode

Port 1 connect to far end port 13

Port 13 connect to far end port 1

Main 1

SONET Ring

Main 2

VCG GFP

MAC

L24

GFP VCG

Main 2

Main 1

VCG GFP

MAC

L16

Note: In STS3c Mode

Port 1 connect to far end port 9

Port 9 connect to far end port 1

MA-DMX-349

A multipoint cross-connection is made up of multiple 1-way or 1-way unprotected cross-connections.

365-372-300

Issue 8.0 September 2006

A - 3 9

Ethernet Transport

A - 4 0

: Ethernet/SAN

The following table shows the LNW71 circuit pack VCG port pairings in the STS-1 and STS-3c modes.

STS-1 Mode

Port Paired with Port...

Port

STS-3c Mode

Paired with Port...

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Ethernet-to-Ethernet Hairpin Cross-Connections

Ethernet-to-ethernet hairpin cross-connections are used to connect a circuit pack to another circuit pack within the same DMX. The cross-connection goes through either Main 1 or Main 2, but not over the SONET ring.

Hairpin cross-connections with an Ethernet circuit pack are used to either connect a VCG on that circuit pack with a VCG on another circuit pack or to connect a VCG with an OLIU located in a function or growth slot. Hairpin connections between VCG ports are used to combine Ethernet traffic from different cards before it is transmitted over a packet ring or out of a LAN port. The following figure shows examples of 1-way hairpin cross-connections between two Ethernet circuit packs.

Figure A-19 Ethernet-to-Ethernet Hairpin Cross-Connections

LNW66 LNW67/LNW68

Main 1

Ethernet

Switch

L24

GFP

VCG

OC-48 or

OC-192

OC-48 or

OC-192

Main 2

GFP

VCG

Ethernet

Switch

A. 2 Way Cross-Connection

MA-DMX-353

365-372-300

Issue 8.0 September 2006

A - 4 1

Ethernet Transport

: Ethernet/SAN

The table below details the support of 1way cross-connections between

Ethernet packs. For hairpins between packs on the same shelf, only

1way cross-connections are used.

Table A-1 1way Cross-Connection Support

LNW63

LNW64

LNW66

LNW67/68

LNW70

From

LNW71

LNW73/73C

LNW74

LNW78

(RPR VCGs 1&2)

LNW78

(EoS VCGs 17-22)

LNW63, W64, LNW66,

LNW67/68, LNW70,

LNW71, LNW74

LNW63, W64, LNW66,

LNW67/68, LNW70,

LNW71, LNW74

LNW63, LNW64,

LNW67/68, LNW70

LNW63,LNW64, LNW66,

LNW67/68, LNW70

LNW63, LNW64, LNW66,

LNW67/68, LNW70,

LNW71, LNW74

LNW70, LNW63 LW64

LNW73/73C

LNW70, LNW63, LNW64

LNW78

LNW63,LNW64, LNW66,

LNW67/68, LNW70,

LNW71, LNW74

A - 4 2

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Ethernet LAN/VCG port density

The Ethernet Switch, also referred to as a Media Access Control

(802.1D MAC) bridge, processes the Ethernet frames and handles

Virtual LANs, frame priority, frame forwarding, and switching functions. The ports on the customer’s side of the switch are referred to as LAN ports, and the ports on the SONET side are referred to as VCG or WAN Ports.

The following table shows the number of LAN and VCG ports on the

Ethernet circuit packs.

Circuit Pack

Name

LAN Port

Line Rate

LNW63

LNW64

1 Gbps

LNW66 10/100 Mbps 24

LNW67, LNW68 1 Gbps 2

Number of Ports

LAN

(Boundary)

VCG

(Interior)

LNW70

LNW71

LNW74

LNW78

(RPR)

LNW78

(EoS)

1 Gbps/ and

100 Mbps

24 (STS-1 Mode)

10/100 Mbps

16 (STS-3c Mode)

10/100 Mbps 24

1 Gbps/ and

100 Mbps

1 Gbps/ and

100 Mbps

6 (LAN)

(VCG)

8 (Private Line Mode)

32 (Switched Mode)

24 (STS-1 Mode)

16 (STS-3c Mode)

2 (Switched Mode)

Maximum

Capacity of a VCG Port

1 Gbps

2.5 Gbps

100 Mbps

1.2 Gbps

Notes:

1. QoS provisioning on EoS VCGs in transparent mode, a new feature for

R7.0, allows LNW70 VCGs i transparent mode to be provisioned as either interior or boundary.

2. In R7.0, LNW78 adds support for EoS service on VCGs 17-22. EoS VCG ports are seen as boundary ports, not interior as with other packs. VCG ports

1-4 remain reserved for RPR service (VCGs 3 and 4 not available in R7.0).

365-372-300

Issue 8.0 September 2006

A - 4 3

Ethernet Transport

: Ethernet/SAN

Virtual LANs (VLANs)

A virtual LAN (VLAN) is a logical grouping of LAN ports, possibly spread across multiple DMX nodes, that act as if they comprise a single

LAN. Since a physical LAN can be associated with multiple virtual

LANs, VLANs can be used to segregate traffic across a network.

VLANs can be used to segregate different types of traffic for a single customer or to separate traffic belonging to multiple subscribers.

VLANs operate at the Ethernet (MAC) Layer. This allows different

VLANs to be carried on the same physical media and hides the VLANs from higher-level protocols (for example, TCP and IP). The higher-level protocols treat each VLAN as if it was a separate physical

LAN. VLAN-aware Ethernet Switches will forward VLAN traffic only on ports assigned to that VLAN. A port can be part of several VLANs and a VLAN can be assigned to several ports.

A frame’s VLAN can be assigned either by the subscriber’s equipment or by network equipment. User equipment specifies the VLAN by including a VLAN Tag in the frame. DMX determines a frame’s

VLAN either from the frame’s existing VLAN Tag or by the default

VLAN ID assigned to the frame’s ingress port. DMX can be provisioned to drop frames that do not contain a tag.

A - 4 4

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

VLAN Tags

VLAN Tags are located in the Ethernet Header. The following figure shows the format of Ethernet frames without a VLAN Tag, frames with a VLAN Tag, and the format of the VLAN Tag.

Figure A-20 Ethernet Frame Format

7 Bytes

1 Byte

6 Bytes

2 Bytes

A. Ethernet Frame without VLAN Tag

Preamble

Start of Frame Delimiter

Destination Address

Source Address

Length/Type

46-1500 Bytes

Data and Pad

4 Bytes

Frame Checksum Sequence

B. Ethernet Frame with a VLAN Tag

Preamble

Start of Frame Delimiter

Destination Address

Source Address

VLAN Tag

Length/Type

Data and Pad

Frame Checksum Sequence

7 Bytes

1 Byte

6 Bytes

4 Bytes

2 Bytes

46-1500 Bytes

4 Bytes

C. Details of a VLAN Tag

TPID (16 Bits)

TPID

User_priority

CFI

VLAN ID

User_priority (3 Bits) CFI (1 Bit) VLAN ID (12 Bits)

Tag Protocol ID (Ethertype)

User Priority Information

Canonical Format Indicator

VLAN Identity (001-FEE hex

)

MA-DMX-354

VLAN Tags can be generated by either user equipment or a switch. If a switch adds a VLAN Tag to a frame, it must also recalculate the frame’s Checksum (FCS). In Release 1.1 and later releases, DMX supports provisioning of 4093 VLAN IDs within the range of 1-4093.

Prior to Release 1.1, DMX supports provisioning of 270 VLAN IDs within the range of 1-4093. Additional information about VLAN tags can be found in IEEE 802.1Q.

365-372-300

Issue 8.0 September 2006

A - 4 5

Ethernet Transport

: Ethernet/SAN

Stacked VLANs (VLAN Transparency)

In order to allow carriers to administer VLAN IDs independent of their subscribers, DMX can be provisioned to add a second VLAN Tag to

Ethernet Frames. This tag, referred to as a Port Tag or Stacked VLAN

Tag, can be used by the service provider to identify and segregate customer (subscriber) traffic. The following figure shows the format of an Ethernet frame that contains stacked VLAN tags.

Figure A-21 Ethernet Frame Format with Stacked VLAN Tags

A. Ethernet Frame with Only a Port Tag

7 Bytes

1 Byte

Preamble

Start of Frame Delimiter

6 Bytes

4 Bytes

2 Bytes

46-1500 Bytes

4 Bytes

Destination Address

Source Address

Port (VLAN) Tag

Length/Type

Data and Pad

Frame Checksum Sequence

B. Ethernet Frame with Both a VLAN Tag and Port Tag

Preamble

Start of Frame Delimiter

7 Bytes

1 Byte

Destination Address

Source Address

Port (VLAN) Tag

6 Bytes

4 Bytes

802.1Q VLAN Tag

Length/Type

Data and Pad

Frame Checksum Sequence

2 Bytes

46-1500 Bytes

4 Bytes

C. Details of a VLAN or Port Tag

TPID (16 Bits) User_priority (3 Bits)

TPID

User_priority

CFI

VLAN ID

Tag Protocol ID (Ethertype)

User Priority Information

Canonical Format Indicator

VLAN Identity (001-FEE hex

)

CFI (1 Bit) VLAN ID (12 Bits)

MA-DMX-355

The port tag is formatted according to IEEE 802.1Q except:

• The frame is given a provisioned Ethertype (TPID). The TPID became provisionable on DMX in Release 4.0. In Releases prior to Release 4.0, the TPID parameter is not provisionable and has a proprietary value of FFFFhex.

• The Canonical Format Indicator (CFI) field is set to 0

• A Customer ID is encoded into VLAN ID field and can contain a value in the range of 1-4093.

A - 4 6

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

DMX is capable of handling frames with multiple layers of VLAN tags; ultimately the limit is that frames greater than 1536 bytes are rejected as too large. When processing VLAN tags, DMX only looks at the outermost tag (that is, the one that most closely follows the Source

Address) that it recognizes. Recognition of a tag is based on the TPID value. In 802.1Q mode, the expected TPID value is 8100hex. In transparent mode, the expected TPID value is provisioned by the user, with the default value being FFFFhex. Legal provisioned values for

TPID are between 0601hex and FFFFhex. These TPID values are also used to identify any tags inserted by DMX.

Based on provisioning at the network ingress and egress points, it is possible for an Ethernet frame to enter and leave the network with a different number of VLAN tags

Priorities

Each Ethernet frame is assigned a priority level. The priority level can be based on a field in a VLAN Tag or a default priority assigned to the frame’s ingress port. If an ingress port is provisioned with a default priority, the default priority will take precedence over the priority field in the VLAN tag.

A VLAN Tag contains a three-bit user_priority field. This allows higher priority frames to be processed at a faster rate than lower priority frames. For the LNW66, LNW67, LNW68 packs, DMX maps the three-bit user priority field to two priority levels. These circuit packs contain two priority queues. Ethernet frames are processed using an 8:1 weighted round robin queue service algorithm. The LNW70 pack contains 4 priority queues. For more information about the

LNW70, refer to the section of this Appendix entitled

“QoS services

(LNW70 and LNW78)” (A-90) .

365-372-300

Issue 8.0 September 2006

A - 4 7

Ethernet Transport

A - 4 8

: Ethernet/SAN

For tagged frames, the following table shows the mapping between values in the user priority field and the priority queues for all of the

Ethernet packs except the LNW70. An Ethernet port can be provisioned to drop untagged frames, or add a VLAN tag containing the port’s default user priority field value of 0 (low) or 7 (high).

VLAN Tag User Priority

Field Value

Queues

Low

High

For tagged frames, the following table shows the default mapping between values in the user priority field and the priority queues for the

LNW70 when the pack is in no traffic management mode.

VLAN Tag User Priority

Field Value

(3)

(4)

(1)

(2)

(3)

Queues

(1=lowest --> 4=highest)

(2)

For more information about frame priority rules, refer to “802.1Q

VLAN mode” (A-80) and to the section entitled

“QoS services

(LNW70 and LNW78)” (A-90) .

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Ethernet Bridge/Switch

This section pertains to the LNW66, LNW67, LNW68, LNW70, and

LNW78.

An Ethernet bridge moves a frame from an ingress port to an egress port(s). It will not forward a frame if the frame contains errors or has the same source and destination addresses.

The bridge looks up the destination MAC address/VLAN ID combination in the address table. If the MAC address is found, the bridge sends the frame to the port(s) found in the address table. If the

MAC address is not found, the bridge sends the frame to all ports associated with the VLAN ID (except the originating port).

Enhanced RPR bridging, supported by the LNW78, will look-up the

Remote RPR station address for the purpose of spatial reuse.

All multicast and broadcast frames are broadcasted including spanning tree BPDUs.

The size of the address table is 8K entries for the LNW66, 67, and 68.

The size of the address table is 256K for the LNW70 and LNW78 packs. Each combination of MAC Address/VLAN ID is one entry.

Entries will be removed if they are not used within 300-600 seconds

(5-10) minutes. During a topology change, they will be deleted as soon as the change is detected.

For more information on Bridging and Steering in RPR (LNW78 only), please refer to

“Ethernet Transport via RPR” (3-31) .

365-372-300

Issue 8.0 September 2006

A - 4 9

Ethernet Transport

A - 5 0

: Ethernet/SAN

Virtual Switch

The single physical Ethernet switch on an LNW66/67/68/70 Ethernet circuit pack can be logically divided into multiple virtual switches. A virtual switch, identified by an id number between 1 and 4095 (between

1 and 16 on LNW70), consists of a collection of LAN and VCG ports.

Any VLANs and spanning tree groups associated with the ports also become associated with the virtual switch. Each LAN port, VCG port,

VLAN ID and spanning tree group id can only be associated with one virtual switch per Ethernet circuit pack. On the LNW66/67/68 each

VLAN ID can only be associated with one virtual switch. On the

LNW70, the same VLAN ID can be associated with many virtual switches and each virtual switch has its own VLAN ID. A minimum of one virtual switch must be created on the LNW66/67/68/70 Ethernet circuit pack in order to provision VLANs and spanning tree groups when in 802.1Q or Transparent Tagging mode. When a port is removed from a virtual switch it returns to its default parameters. Virtual switches are not used in Private Line mode or on LNW71 and LNW74 circuit packs.

The following figure shows one possible assignment of LAN ports and

VCG ports into virtual switches. The figure shows one physical switch that is divided into two virtual switches. Virtual switch 1 supports a packet ring configuration encompassing LAN port 1 and VCG ports 1 and 2. Virtual Switch 2 supports a point-to-point configuration encompassing LAN port 2 and VCG ports 1 and 2. Ethernet traffic will not be allowed to cross between the virtual switches.

Figure A-22 Virtual Switches

LAN

Service 1

Virtual SW 1

LAN

Service 1

LAN

Service 2

Packet Ring

GFP

VCG

Point-to-point Protected

UPSR

Virtual SW 2

LAN

Service 2

MA-DMX-356

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Spanning tree protocol

(STP)

Spanning tree protocol (STP) provides a protection scheme for

Ethernet packet transmission as a by-product of its primary function of eliminating loops in Ethernet networks. This protection is independent of any SONET-level protection mechanisms such as UPSR switching.

In fact, undesirable interactions can occur if both protection mechanisms are used, so it is recommended that spanning tree protocol be used only in configurations with no SONET protection.

Loops can arise within Ethernet networks as a result of multiple paths between a source and a destination. The spanning tree protocol identifies links that must be blocked to ensure that no such multiple paths can exist. Any link failure in the resulting network triggers the spanning tree protocol to re-analyze the network and identify a new set of blocked links that provide full connectivity with no duplicated paths.

It is this reconfiguration in response to failures that constitutes the packet layer protection mechanism.

How it Works

Spanning tree works as follows:

Initially, every node in the group thinks it is the root node.

Configuration BPDUs are sent from each node to determine the most economical route from each node to the root node.

As information about the network becomes clear, one node is designated the root node; from this node, the distance to any point in the network may be measured.

Once the network has become clear, some ports are blocked so that there are no loops in the network and so that the network provides the most efficient paths from the root to the nodes.

This effectively creates a tree structure for the network.

365-372-300

Issue 8.0 September 2006

A - 5 1

Ethernet Transport

: Ethernet/SAN

If an active link fails, the network is reconfigured so that previously blocked links can be used for traffic.

Figure A-23 Spanning Tree

Path 1

Root bridge nc-dmx-095

Legend:

Active Links 1 to 2; 2 to 3; 3 to 5; 1 to 6; 6 to 4; 4 to 7

Inactive Links 5 to 7

X Indicates a blocked port (frame forwarding is disabled)

Important!

The configuration provides the least (most efficient) path from each node to the root. The configuration also provides only one path between any two nodes.

Reconfiguration

If one of the active links is broken, the network reconfigures to activate the inactive link. For example, if the link between 2 and 3 is broken, the link between 5 and 7 would be enabled.

Migration to 802.1W Rapid Spanning Tree Protocol

Prior to Release 2.0, DMX implemented the 802.1D version of the spanning tree protocol. In Release 2.0 and later releases, DMX migrated to the 802.1W rapid spanning tree protocol (RSTP) and made

A - 5 2

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

some other spanning tree enhancements. The changes are summarized in the following:

• Faster Failure Detection - DMX uses SONET-layer failure detection to trigger packet-layer (spanning tree) reconfiguration, so packet-layer reconfiguration starts within a few milliseconds after a failure rather than several seconds later.

• IEEE 802.1W Rapid Reconfiguration - DMX supports this new standard packet-layer restoration protocol, which uses new messages between spanning tree protocol entities to significantly reduce convergence time.

• Spanning tree version interworking - Each DMX node will query its Ethernet link partners to determine if they are capable of running the 802.1W rapid spanning tree protocol. If so, the

802.1W protocol will be used. If not, the DMX will fall back to running the 802.1D version of spanning tree protocol.

• Enhanced STP configuration reports and controls - Together with

802.1W, these enable support for much larger networks than are supported with IEEE 802.1D Spanning Tree Protocol.

365-372-300

Issue 8.0 September 2006

A - 5 3

Ethernet Transport

: Ethernet/SAN

Spanning Tree on LAN ports

LNW70 only.

Both LAN ports and VCGs can belong to STP groups. A LAN port can belong to only one STP group at a time. Beginning in R6.0, the BDPU

VLAN ID becomes provisionable. VLAN IDs are provisionsable on a per-port basis. Prior to R6.0 all VLAN IDs were #4094

Figure A-24 Spanning Tree on LAN ports

Root bridge

Path 1

JK-E-14.eps

Legend:

Active Links 1 to 2; 1 to B; B to A

Inactive Links A to 2

X Indicates a blocked port (frame forwarding is disabled)

A - 5 4

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Link Aggregation on

LNW70 LAN ports

DMX supports link aggregation on any two LNW70 LAN ports of the same rate (i.e. 100 or 1000 Mbps), operating in switched mode. In

R7.0, the two ports comprising a LAG must be located on the same pack.

Link aggregation can also be used for facility protection on LNW70

LAN ports.

Bandwidth increase/decrease

Ordinarily, multiple Ethernet links between two bridges form loops

(unless a spanning tree blocks all but one) so they can’t be used to increase bandwidth. Link Aggregation causes defined groups of links to be treated as a single logical link, making multiple LAN ports appear as one. In this way, Bandwidth may be increased without requiring an upgrade to a higher rate link.

Facility protection

More links than are needed can be added to the group and each is active until it fails (similar to utilizing LCAS protection for SONET tributaries).

Link aggregation control protocol

365-372-300

Issue 8.0 September 2006

A - 5 5

Ethernet Transport

A - 5 6

: Ethernet/SAN

General link aggregation rules

Link aggregation is available for LAN ports on the LNW70 pack beginning in R7.0 and behaves along the following basic guidelines:

• Available for LAN ports on the LNW70 in switched mode only

• Maximum of 4 LAGs per pack, 2 ports per LAG, and 8 LAGs per function unit or growth group. There are 8 ports on each LNW70 pack.

• The two ports in a LAG must be on the same pack, and be functioning at the same rate (i.e. 100 or 1000 Mbps).

• All links in a LAG are in-service until they fail. Standby links, providing 1x1 SONET-style protection, are a future feature.

VS or have any VLAN provisioning when added.

-- Both member ports can also be added simultaneously and DMX recognizes a parameter that distinguishes the "Lead Port". The

LAG (and by association, the other port in the LAG) inherits the

L2, VLAN, and VS attributes of the Lead Port.

• When a port is removed from a particular LAG, it is no longer a member of a VS.

• The last port/member of a LAG cannot be removed from the

LAG; the LAG itself must be deleted. The last port/member of a the inherits the LAG’s L2, VLAN, and VS attributes.

-- If the last member in the LAG was the first member added originally, and if there were no subsequent changes to L2 and

VLAN attributes, the port will effectively revert to it’s original state when the LAG is deleted.

-- If the last member/port in the LAG was not the first added initially it will inherit the characteristics of the LAG rather than reverting to its original state.

365-372-300

Issue 8.0 September 2006

Ethernet Transport

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

Link Aggregation Example

Traffic entering incoming ports is aggregated into a LAG. While both ports are in-service, outgoing traffic is split between working ports.

Figure A-25 Link aggregation at 100 Mbps

(all ports in-service)

Link Aggregation Group (LAG)

100 Mb

Up to

200 Mbps

LNW70

Link Aggregation Group (LAG)

LNW70

100 Mb

200 Mbps per conversation

MA-DMXAPG-044

The algorithm uses the XOR of the least significant bits of the address pairs to assign a port/link. Therefore, the actual load balancing achieved depends on the distribution of MAC/IP addresses.

A - 5 7

Ethernet Transport

: Ethernet/SAN

Link aggregation transparency

Link aggregation allows multiple physical links between Ethernet switches to be treated as a single link. This provides for more bandwidth between the switches than can be transmitted over a single

Ethernet port and it can provide protection from a cable, Ethernet port, or Ethernet circuit pack failure.

While R7.0 supports link aggregation, the DMX also supports link aggregation transparency in both R7.0 and previous releases. As shown in the following figure, this allows the attached equipment to use link aggregation without participation by the DMX provisioning.

Figure A-26 Link Aggregation

External

Ethernet

Equipment

(Device)

Metropolis

DMX

SONET Network

Metropolis

DMX

Link

Aggregation

Group

LAN Ports

Located on 1

Or More

Circuit Packs

LAN Ports

Located on 1

Or More

Circuit Packs

Link

Aggregation

Group

External

Ethernet

Equipment

(Device)

Ethernet Links

(10 or 100 or 1000 Mbps)

Ethernet Links

(10 or 100 or 1000 Mbps)

Link Aggregation Group (e.g. Links that are aggregated together)

MA-DMX-357

The figure shows two Ethernet devices running link aggregation interconnected via Ethernet circuit packs and a SONET Network. The

DMX shelves and the SONET network are invisible to the two Ethernet devices. The Ethernet traffic is transparently transferred between the external devices. Link aggregation is typically implemented using two dedicated unprotected point-to-point links (Ethernet Private Line

Service) for each pair of external ports.

Link aggregation transparency requires a default VLAN ID tag or port tag in 802.1Q and Transparent Tagging mode. If a default VLAN or port tag is not specified at the port, the link aggregation messages are dropped.

A - 5 8

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Flow control

This section describes how DMX controls the flow of Ethernet traffic.

DMX supports the following types of flow control:

• Local flow control

• End-to-end flow control

Local Flow Control (Ingress Traffic Direction)

If the external equipment delivers Ethernet frames to the Ethernet circuit pack faster than they can be delivered across the network, the data buffers in the Ethernet circuit pack fill up. When the data buffers reach the flow control threshold, the Ethernet circuit pack initiates flow control. On full duplex links, the Ethernet circuit pack issues a flow control request to the external equipment, requesting that the flow of frames be suspended. On half duplex links, the JAM signal is used to stop all traffic. The flow control request is repeated periodically, or the

JAM signal continuously generated until the buffers empty sufficiently.

(Refer to the following figure.)

Figure A-27 Local Flow Control of Ingress Traffic

Metropolis

DMX 1

Metropolis

DMX2

External

Equipment 1

Data

Ethernet

Link

Ethernet

Circuit Pack

Buffer

SONET

Sub Rate

Ethernet

Circuit Pack

Flow

Control

Request

When data rate from External Equipment 1 exceeds SONET bandwidth, DMX 1 will invoke flow control toward External Equipment 1

External

Equipment 2

MA-DMX-358

Note that this local flow control mechanism is concerned only with congestion (full packet buffers) at the local DMX. If the DMX at the other end of the SONET network is unable to deliver the Ethernet frames to the attached external equipment due to flow control conditions there, that does not directly affect the local flow control operation at the ingress DMX.

365-372-300

Issue 8.0 September 2006

A - 5 9

Ethernet Transport

: Ethernet/SAN

Local Flow Control (Egress Traffic Direction)

If the local Ethernet circuit pack attempts to deliver Ethernet frames to the attached external equipment faster than the external equipment can accept them, the external equipment may initiate flow control. On full duplex links, the external equipment issues a flow control request to the

Ethernet circuit pack requesting that the flow of frames be suspended.

On half duplex links, the JAM signal is used to stop all traffic. (Refer to the following figure.)

Figure A-28 Local Flow Control of Egress Traffic

2. A Flow Control

Request is generated by External Equipment 1

On receiving the Flow Control

Request, the DMX 1 stops sending

Ethernet Frames to External Equipment 1

Metropolis

DMX1

Metropolis

DMX 2

External

Equipment 1

Flow

Control

Request

Ethernet

Link

Ethernet

Circuit Pack

Buffer

SONET

Sub Rate

Ethernet

Circuit Pack

Ethernet

Link

External

Equipment 2

4. When the buffers are full, additional Ethernet Frames are dropped

1. Data from

External

Equipment 2

A Flow Control Request generated by External Equipment 1 is handled in the local Ethernet Circuit Pack

DataFrames generated by External Equipment 2, will be stored in a buffer in DMX

tend

Any frames received after the buffer is filled will be dropped

MA-DMX-359

This causes the Ethernet circuit pack to stop sending Ethernet frames to the external equipment for the time requested in the flow control request. During this time, Ethernet frames accumulate in the packet buffers in the Ethernet circuit pack. Once these buffers fill completely, further Ethernet frames arriving from the SONET network for the egress Ethernet port are dropped.

A - 6 0

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

365-372-300

Issue 8.0 September 2006

End-to-End Flow Control

If the external equipment at the destination of an Ethernet connection cannot handle the rate of traffic being sent to it, it may be desirable to apply back pressure across the network to slow down the external source of the Ethernet traffic. This cross-network back pressure can only work well, however, when the source of the traffic can be identified unambiguously. Only the Ethernet Private Line Service offers this opportunity; thus, it is the only service that supports

End-to-End Flow Control.

End-to-End Flow Control (LNW66, LNW67, LNW68 Circuit Packs)

With end-to-end flow control, flow control requests that are received by the LNW66, LNW67, and LNW68 Ethernet circuit packs at the egress point of the network, are regenerated during congested conditions by the Ethernet circuit pack at the ingress point of the network and transmitted to the originating external equipment.

Figure A-29 End-to-End Flow Control (LNW66, LNW67, LNW68)

2. A Flow Control

Request is initiated by

External Equipment 1

3. When the buffer reaches the Flow Control

Threshold, DMX 1 transmits a Flow Control

Request towards the

External Equipment 2

4. In Response to the

Flow Control Request,

DMX 2 stops transmitting

Frames toward DMX1

6. External Equipment 2 stops sending frames in response to the Flow

Control request

Metropolis

DMX 1

External

Equipment 1

Flow

Control

Request

Ethernet

Link

Ethernet

Circuit Pack

Buffers

SONET

Metropolis

DMX 2

Ethernet

Circuit Pack

Buffers

Flow

Control

Request

Ethernet

Link

External

Equipment 2

3a. When the queue is full additional Ethernet Frames are dropped

1. Data from

External

Equipment 2

5. When the ingress queue is full, a Flow control Request is transmitted to External Equipment 2

Flow Control Requests generated by External Equipment 1

Data Frames received in DMX 1 from External Equipment 2 will be stored in a latency buffer

Any Frames received in DMX1 after the latency buffer is full will be dropped

DMX = Metropolis DMX Access Multiplexer

MA-DMX-360

While waiting for the originating external equipment to receive and process the flow control request, the destination Ethernet circuit pack

A - 6 1

Ethernet Transport

: Ethernet/SAN

buffers Ethernet frames received over the SONET network. If the buffer fills before the frame flow stops, the excess frames will be discarded.

End-to-End Flow Control (LNW71/70/63 Circuit Pack)

The LNW71/70/63 circuit pack implements the following changes intended to improve the frame loss behavior of end-to-end flow control.

• When provisioned for end-to-end flow control, the LNW71/70/63 circuit pack sends a flow control request across the SONET network immediately upon receiving a flow control request from external equipment.

• The LNW71/70/63 circuit pack contains large latency buffers to hold data while waiting for far-end equipment to respond to end-to-end flow control requests. (Refer to the following figure.)

Figure A-30 End-to-End Flow Control (LNW71/70/63)

2. A Flow Control

Request is initiated by

External Equipment 1

Metropolis

DMX 1

External

Equipment 1

Flow

Control

Request

Ethernet

Link

Ethernet

Circuit Pack

Latency

Buffer

200KB for

LNW71

2MB for

LNW70

10MB for

LNW63

SONET

Metropolis

DMX 2

3b. External Equipment 2 reacts to the to

Flow Control request

Ethernet

Circuit Pack

Flow

Control

Request

Ethernet

Link

External

Equipment 2

Buffer

1. Data from

External

Equipment 2

A - 6 2

3a. Large latency buffer supports

1000 miles

Flow Control Request is generated by External Equipment 1

Flow Control Request is sent immediately to External Equipment 2

Data Frames received from External Equipment 2 will be stored in a large latency buffer

External Eqipment 2 stops sending data in time for a loss-less transmission

DMX = Metropolis

DMX Access Multiplexer

JK-E-6

After a flow control request is received, the LNW71/70/63 circuit pack buffers frames instead of sending them to the equipment that generated

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

the flow control request. Each port has its own latency buffer. A latency buffer can store 16ms of traffic that allows the equipment to be about 1000 miles apart (2000 miles round trip).

End-to-End Flow Control (LNW74 Circuit Pack)

The LNW74 circuit pack implements the following changes intended to improve the frame loss behavior of end-to-end flow control.

• When provisioned for end-to-end flow control, the LNW74 circuit pack sends a flow control request across the SONET network immediately upon receiving a flow control request from external equipment.

• The LNW74 circuit pack does not buffer data while waiting for far-end equipment to respond to end-to-end flow control requests.

Data is transmitted to the client.(Refer to the following figure.)

Figure A-31 End-to-End Flow Control (LNW74)

2. A Flow Control

Request is initiated by

External Equipment 1

Metropolis

DMX 1

External

Equipment 1

Flow

Control

Request

Ethernet

Link

Ethernet

Circuit Pack

LNW74

SONET

Metropolis

DMX 2

3b. External Equipment 2 reacts to the to

Flow Control request

Ethernet

Circuit Pack

Buffer

Flow

Control

Request

Ethernet

Link

External

Equipment 2

1. Data from

External

Equipment 2

Flow Control Request is generated by External Equipment 1

Flow Control Request is sent immediately to External Equipment 2

External Eqipment 2 stops sending data in time for a loss-less transmission

DMX = Metropolis DMX Access Multiplexer

JK-E-7

365-372-300

Issue 8.0 September 2006

A - 6 3

Ethernet Transport

: Ethernet/SAN

Flow Control Provisioning (LNW66, LNW67, LNW68 Circuit Packs)

A combination of flow control settings on the LNW66, LNW67 and

LNW68 circuit pack LAN ports and VCGs determine how flow control operates.

The following table shows the flow control settings for the LNW66,

LNW67, and LNW68 circuit packs.

LAN Port

Flow

Control

State

Disabled

VCG Flow

Control

Provisione d Value

Don’t Care

Enabled

Transparent

Local

None

(Disabled)

Flow

Control

Status

Use/Comments

Disabled

Flow control is disabled for that port/link. Flow control requests are ignored and discarded.

End-to-End

Mode

Enabled

The LAN port responds to flow control requests by stopping frame transmission. Flow control requests are generated and sent to far end DMX based on congestion. Frames are dropped once the egress buffer is full.

LAN port generates flow control requests due to congestion from the far end DMX.

For Ethernet Private Line Full Rate Service

(Point-to-Point).

Local

Mode

Enabled

Disabled

The LAN port responds to flow control requests by stopping frame transmission. No flow control requests are sent to far end DMX.

LAN port generates flow control requests for fractional service.

For Ethernet Private Line Fractional (Partial)

Rate Service and Packet Ring Services.

The LAN port responds to flow control requests by stopping frame transmission. No flow control requests are sent to the far end DMX.

LAN port does not generate flow control requests.

A - 6 4

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

LAN Port

Flow

Control

State

Flow Control Provisioning (LNW71 Circuit Pack)

The LNW71 circuit pack automatically provides both local and end-to-end flow control if flow control is enabled for a LAN port.

Similarly, disabling flow control for an LAN port disables both forms of flow control.

The following table shows the flow control settings for the LNW71 circuit pack.

Flow

Control

Status

Use/Comments

Disabled

Enabled

Disabled

Enabled

DMX does not participate in flow control.

The LAN port does not respond to flow control requests.

The LAN port does not generate flow control requests due to congestion.

Flow control requests are transported when received.

The LAN port responds to flow control requests by stopping frame transmission. Flow control requests are sent to the far end DMX. Frames are stored in the

Latency buffer for loss-less transmission.

LAN port generates flow control requests for fractional service.

365-372-300

Issue 8.0 September 2006

A - 6 5

Ethernet Transport

: Ethernet/SAN

Flow Control Provisioning (LNW70/74/63 Circuit Pack)

The LNW70/74/63 circuit pack automatically provides both local and end-to-end flow control if flow control is enabled for a LAN port.

Similarly, disabling flow control for an LAN port disables both forms of flow control.

The following table shows the flow control settings for the

LNW70/74/63 circuit pack.

LAN Port

Flow

Control

State

Flow

Control

Status

Use/Comments

Disabled

Enabled

Disabled

Enabled

DMX does not participate in flow control.

The LAN port does not respond to flow control requests.

The LAN port does not generate flow control requests due to congestion.

Flow control requests are transported when received.

Flow control requests are sent to the far-end DMX. LAN ports generate flow control requests for fractional service.

Disables Network-element controlled flow control and

Drop Drop drops end-to-end flow control messages.

A - 6 6

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Physical interface

Each Ethernet circuit pack contains a transceiver that implements the physical interface for that circuit pack's line type. For the 10/100 Mbps circuit packs, this physical interface must be provisioned to or auto-negotiate to the proper line rate and duplex mode in order to communicate successfully with the connected equipment. Gigabit

Ethernet interfaces only support the 1000 Mbps line rate and full duplex mode, so this is not an issue for these circuit packs. All optical

100BASE-LX interfaces support the 100 Mbps line rate only.

At the physical layer, many types of LANs can be used for multiple line rates and duplex modes. For example the LAN port on most PCs can be connected to a 10BASE-TX (10 Mbps) or a 100BASE-TX (100 Mbps)

LAN. Before data traffic can be transmitted onto a LAN, all ports connected to the LAN must operate with the same line rate and duplex mode. LAN ports can either be provisioned with these values or provisioned to automatically negotiate (auto-negotiate) the values.

Auto-negotiation

In the auto-negotiation process, a LAN port advertises its acceptable parameters, compares these with the advertised parameters of its link partner, and then agrees upon a set of parameters with the link partner.

IEEE 802.3 allows the line rate, duplex mode, and flow control mode to be auto-negotiated. A LAN port not configured to support auto-negotiation will use provisioned values for these parameters. A

LAN port configured for auto-negotiation that is connected to a LAN port not configured for auto-negotiation will follow prescribed rules for parameter settings.

On connected 1GSX/1GLX Ethernet ports with auto-negotiation enabled, if transmission is interrupted in one direction of transmission on a 1GSX/1GLX Ethernet port, then transmission is disabled in the other direction. For example, if one fiber in the transmit/receive pair is cut, then one-way transmission on the other fiber is maintained only if auto-negotiate is disabled and the link state is forced good at the transmit source equipment.

365-372-300

Issue 8.0 September 2006

A - 6 7

Ethernet Transport

: Ethernet/SAN

Line Rate Operation for LNW66, LNW71, and LNW74 Circuit Packs

The following table summarizes line rate operation for the LNW66,

LNW71, and LNW74 Ethernet circuit packs.

DMX LAN Port

Provisioning

100

Rate

Connected Equipment

Provisioning

Auto-Negotiation

Advertised/

Set at

Disabled

Enabled

Disabled

Enabled

Disabled

100

10/100

100

10/100

100

Ethernet

Link Rate

(Note 1)

No Link

100

No Link

100

Auto Enabled

Enabled

100

Enabled 10/100 100

Note 1: Both the DMX and the connected equipment will try to determine a common line rate. The link will not come up if both ends have auto-negotiation enabled and advertise incompatible duplex modes.

A - 6 8

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Duplex Mode Operation for LNW66 Circuit Packs

The following table summarizes duplex mode operation for the

LNW66 Ethernet circuit packs.

DMX LAN Port

Provisioning

Connected Equipment

Provisioning

Duplex

Mode

Auto-

Negotiation

State

(Note 1)

Auto-

Negotiation

Advertised/

Set at

Auto Enabled

Disabled

Enabled

Full

Half

Full

Half

Full

Duplex Mode State

DMX

(Note 2)

Connected

Equipment

Bidirectional

Traffic (Link

Rate must be resolved)

Full

Half

Full

Yes

Full

Enabled

Disabled

Enabled

Disabled

Half

Half/Full

Full

Half

Full

Half

Half/Full

Full

Half

Full

Half

Full

Unavailable Full

Unavailable Half

Full

Note 3

Full

Yes

Half

Disabled

Enabled

Disabled

Enabled

Disabled

Enabled

Half

Full

Half

Half/Full

Full

Half

Full

Half

Half/Full

Full Half

Unavailable Note 4

Full

Half

Full

Half

Unavailable Note 4

Half Half

Yes

No Note 4

365-372-300

Issue 8.0 September 2006

A - 6 9

Ethernet Transport

: Ethernet/SAN

DMX LAN Port

Provisioning

Connected Equipment

Provisioning

Duplex

Mode

Auto-

Negotiation

State

(Note 1)

Auto-

Negotiation

Advertised/

Set at

Half Disabled

Disabled

Enabled

Full

Half

Full

Half

Duplex Mode State

DMX

(Note 2)

Half

Connected

Equipment

Bidirectional

Traffic (Link

Rate must be resolved)

Full

Half

Note 4

Half

Yes

No (Note 4)

Yes

Enabled Half/Full Half Half Yes

Notes:

1. Auto-negotiation will be enabled if Line Rate or Duplex Mode or Flow Control is provisioned for auto-negotiation.

2. Duplex mode will be reported as unavailable if the link could not be established.

3. The link will not come up because the duplex mode could not be established.

4. According to IEEE 802.3, the connected equipment should default to half duplex. Because that equipment doesn’t support half duplex the link may be prevented from coming up. If it does come up, bidirectional traffic will not be supported.

A - 7 0

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Flow Control Operation for LNW66, LNW71, and LNW74 Circuit

Packs

The following table summarizes flow control operation for the

LNW66, LNW71, and LNW74 Ethernet circuit packs.

DMX LAN Port

Provisioning

Connected Equipment

Provisioning

Flow

Control

Auto-

Negotiation

State

(Note 1)

Auto-

Negotiation

Advertised/

Set at

(Note 2)

Duplex Mode State

DMX

(Note 3)

Connected

Equipment

Comments

(Note 4)

Auto Enabled

Disabled

Enabled

Disabled

Enabled

Inconsistent

Provisioning

Inconsistent

Provisioning

Enabled

Disabled

Enabled

Note 5

Note 6

Disabled

Enabled

Disabled

Enabled

Disabled

Enabled

Inconsistent

Provisioning

Inconsistent

Provisioning

Enabled

Disabled

Enabled

Disabled

Enabled

Disabled

Disabled Enabled Disabled

Inconsistent

Provisioning

Enabled Enabled Enabled

Disabled

Enabled

Disabled

Enabled

Unknown

Inconsistent

Provisioning

Inconsistent

Provisioning

365-372-300

Issue 8.0 September 2006

A - 7 1

Ethernet Transport

: Ethernet/SAN

A - 7 2

DMX LAN Port

Provisioning

Connected Equipment

Provisioning

Flow

Control

Auto-

Negotiation

State

(Note 1)

Auto-

Negotiation

Advertised/

Set at

(Note 2)

Duplex Mode State

DMX

(Note 3)

Connected

Equipment

Comments

(Note 4)

Enabled

Disabled

Enabled

Disabled

Enabled

Inconsistent

Provisioning

Inconsistent

Provisioning

Disabled

Enabled

Disabled

Enabled

Disabled

Enabled

Disabled

Enabled

Disabled

Enabled

Unknown

Inconsistent

Provisioning

Inconsistent

Provisioning

Inconsistent

Provisioning

Notes:

1. Auto-negotiation will be enabled on the LNW66 LAN port if Line Rate or Duplex Mode or Flow

Control is provisioned for auto-negotiation. Auto-negotiation will be enabled on the LNW71 LAN port if Line Rate or Flow Control is provisioned for auto-negotiation

2. Flow control will only be enabled if the connected equipment is capable of Symmetric Flow Control.

3. IEEE 802.3 does not define flow control states for half duplex links or when only one side of a link is provisioned for auto-negotiation. This is the expected behavior of the connected equipment.

4. IEEE 802.3 recommends that equipment be configured for auto-negotiation to avoid inconsistent provisioning.

5. On LNW66 LAN ports, flow control will be enabled if the duplex mode is provisioned for half duplex and disabled if the duplex mode is provisioned for full duplex or auto-negotiate. Flow control will be disabled on LNW71 LAN ports.

6. Flow control will be enabled on LNW71 LAN ports. On LNW66 LAN ports, flow control will be enabled if the duplex mode is provisioned for full duplex, or auto-negotiates to full duplex, or is provisioned for half duplex. It will be disabled on LNW66 LAN ports if the duplex mode auto-negotiates to half duplex.

Important!

Flow control on all optical Fast Ethernet ports must be provisioned manually.

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

Flow Control Operation for LNW67, and LNW68, and LNW70

(100BASE-X ports only) Circuit Packs

The following table summarizes flow control operation for the

LNW67, and LNW68, and LNW70 (100BASE-X ports only) Ethernet circuit packs.

DMX LAN

Port Flow

Control

Provisioning

Connected Equipment

Provisioning

Auto-

Negotiation

Advertised/

Set at

(Note 2)

Flow Control State

DMX

(Note 2)

Connected

Equipment

Comments

(Note 3)

Auto

Disabled

Enabled

Disabled

Enabled

Inconsistent

Provisioning

Inconsistent

Provisioning

Enabled

Disabled

Enabled

Disabled

Enabled

Disabled

Enabled

Disabled

Disabled Enabled Disabled

Inconsistent

Provisioning

Enabled Enabled Enabled

Enabled

Disabled

Enabled

Unknown

Inconsistent

Provisioning

Inconsistent

Provisioning

365-372-300

Issue 8.0 September 2006

A - 7 3

Ethernet Transport

: Ethernet/SAN

DMX LAN

Port Flow

Control

Provisioning

Connected Equipment

Provisioning

Auto-

Negotiation

Advertised/

Set at

(Note 2)

Disabled

Enabled

Disabled

(Drop on

LNW70 only

)

Disabled

Enabled

Flow Control State

DMX

(Note 2)

Disabled

Connected

Equipment

Disabled

Enabled

Unknown

Comments

(Note 3)

Inconsistent

Provisioning

Inconsistent

Provisioning

Inconsistent

Provisioning

Notes:

1. The link will not be operational if the connected equipment is not configured for 1 Gbps and full duplex mode.

2. Flow control will only be enabled if the connected equipment is capable of Symmetric Flow

Control.

3. IEEE 802.3 recommends that equipment be configured to avoid inconsistent provisioning.

4. Drop mode only applies for the LNW70 circuit pack.

Queues and buffers

Ethernet circuit packs contain small buffer pools that provide storage of

Ethernet frames for brief periods of congestion or until flow control requests can be honored. These small buffer pools are associated with the Ethernet switch and the Generic Framing Procedure (GFP) mechanism. The GFP mechanism is described further in “Generic framing procedure (GFP)” (A-31) . A larger buffer pool designed to handle different path lengths for individual STS-1s is associated with the virtual concatenation process. Its function is described in more detail in “Virtual concatenation” (A-33) . Two priority-based queues are provided on the LNW66/67/68 to allow high priority traffic to be forwarded ahead of low priority traffic. The LNW70 provides 4 priority queues. For more information refer to “Metering (CIR and

PIR)” (A-100) .

A - 7 4

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

LNW66, LNW67, and LNW68 Circuit Pack Queues and Buffers

The Ethernet switches on LNW66, LNW67, and LNW68 circuit packs contain ingress (input) and egress (output) buffers. The following figure shows the LNW66, LNW67, and LNW68 circuit pack queue and buffer architecture.

Figure A-32 Queue and Buffer Architecture (LNW66, LNW67,

LNW68)

VCG

GFP Buffer

8K bytes

(5-128 Packets)

High

Priority

Packets

Low

Priority

Differential Delay Buffers 16ms

(94.5k bytes/STS-1)

GFP Buffer

8K bytes

(5-128 Packets)

Packets

2 or 4 VCG Ports

Packets

High

Priority

Low

Priority

Packets

Switch

Fabric

2 X 1GE LAN Port

(LNW67/68)

128

Packets

31 Packets

High

Priority

Low

Priority

3 X 8 LAN Ports

(LNW66)

MA-DMX-362

365-372-300

Issue 8.0 September 2006

A - 7 5

Ethernet Transport

: Ethernet/SAN

High and low priority queues are provided for packets leaving the

Ethernet switch in the direction of either the SONET network or a customer port. Each LAN and VCG port has one ingress and two egress queues. Ingress queues buffer Ethernet frames going into the Ethernet switch and egress queues buffer Ethernet frames leaving the Ethernet switch. One egress queue is for high priority Ethernet frames and the other egress queue is for low priority Ethernet frames.

On the LNW66 circuit pack, the LAN ports are divided into groups of eight. The groups consist of LAN ports 1-8, 9-16, and 17-24. Each group of eight LAN ports shares a set of 128 frame buffers. In the egress direction, each LAN port can buffer up to 31 Ethernet frames which can be placed in a high or low priority queue. Each LNW66 circuit pack VCG port can buffer 40 Ethernet frames in the ingress queue and a total of 37 Ethernet frames across the high and low priority egress queues.

All ports on the LNW67 and LNW68 circuit packs are independent and each port can buffer 40 Ethernet frames in its ingress queue and a total of 37 frames across its high and low priority egress queues.

All frame buffers are sized to handle the maximum frame size (1536 bytes). The buffer pool sizes described above are independent of frame size (that is, they do not increase if the Ethernet traffic consists of small frames).

A - 7 6

365-372-300

Issue 8.0 September 2006

Ethernet Transport

: Ethernet/SAN

LNW63/70/71/74 Circuit Pack Buffers

In Private Line Mode, the Ethernet frame buffers are all associated with the Generic Framing Procedure (GFP) and virtual concatenation mechanisms. The following figure shows the LNW63/70/71/74 circuit pack buffer architecture.

NOTE: In switched mode, the LNW70 buffers are provisionable up to

256 K.

Figure A-33 Buffer Architecture (LNW63/70/71/74)

VCG

GFP Buffer

LNW70 GbE--> up to 128K bytes

LNW70 FE--> up to 64K bytes

LNW71--> up to 64K bytes

LNW74--> up to 64K bytes

LNW63 GbE--> up to 128K bytes

Differential Delay BufFers

GFP Buffer

LNW70 GbE--> up to 2 Mb

LNW70 FE--> up to 200K bytes

LNW71--> up to 200K bytes

LNW74--> up to 200K bytes

LNW63 GbE--> up to 10 Mb

VCG Ports

LAN Ports

MA-DMX-363

The LNW63/70/71/74 circuit pack provides larger buffer pools to allow for longer response times to flow control requests. In addition, buffer storage can be flexibly assigned to Ethernet frames, allowing maximal usage of the memory available.

NOTE: For additional information on differential delay buffers, refer to “Differential Delay Buffers” (A-34) .

365-372-300

Issue 8.0 September 2006

A - 7 7

Ethernet Transport

: Ethernet/SAN

Head-of-Line (HOL) Blocking Prevention

As an Ethernet frame arrives from the SONET network destined for a customer LAN port on LNW66/67/68 circuit packs, it is placed in the egress queue associated with the destination LAN port(s). If that queue is full, the VCG port on which the packet arrived could hold the packet until space is available, but that would stop the incoming flow of all packets arriving on that VCG port, even those destined for uncongested

LAN ports. This situation is known as Head-of-Line (HOL) blocking.

To avoid Head-of-Line (HOL) blocking, the LNW66/67/68 circuit packs support the discarding of packets received on a VCG port destined for a LAN port with a full egress queue. Broadcast frames, multicast frames, and frames with unknown destination addresses are not discarded but are forwarded only to those LAN ports that are accepting traffic. Frames dropped due to HOL blocking prevention are not reported as dropped in the performance monitoring statistics.

HOL blocking prevention is used in the 802.1Q and transparent modes.

These modes are described in

“Tagging Modes” (A-79) .

A - 7 8

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

Tagging Modes

Overview

Private line mode

DMX supports the following tagging modes.

• Private line mode (also know as no tag or repeater mode)

• Switched mode

• 802.1Q mode

• Transparent mode.

The tagging mode is user provisionable on a circuit pack basis.

Different circuit packs on a single DMX shelf can be provisioned for different modes but, all ports on a circuit pack must use the same mode.

The private line mode (also known as no tag or repeater mode) is used to establish simple point-to-point connections between two ports with no Ethernet switching functions applied. No additional Ethernet provisioning is required after the cross-connection is established.

Private line mode can be used to provide either a full rate or sub-rate

(fractional rate) dedicated Ethernet link across SONET networks. No preferential treatment for high priority packets is provided. In a sub-rate service, frames may be dropped due to congestion. Any correctly formatted Ethernet frame received at a source port is transmitted out of the destination port.

The private line mode supports the following features:

• Point-to-point topology with only two LAN ports

• MAC address filtering is enabled (not available for LNW71/74)

• Protection is provided at the SONET network layer by either

UPSR switching

• No spanning tree protocol (supports transparency of customer spanning tree protocol)

• No VLAN ingress filtering or classification (VLAN tags are not verified or added)

• Ethernet PM per port

For packet size info refer to

Packet size in different tagging modes

A - 86 .

365-372-300

Issue 8.0 September 2006

A - 7 9

Tagging Modes

: Ethernet/SAN

Switched Mode

Switched mode allows 802.1Q or Transparent mode to be selected based on a virtual switch (grouping of ports). Refer to the sections below and to "Virtual switch" on page A-112 and

“QoS services

(LNW70 and LNW78)” (A-90) for more information.

802.1Q VLAN mode

In 802.1Q Mode, a circuit pack can be provisioned to use an incoming frame's VLAN tag, to add a VLAN tag associated with the port for untagged frames, or to drop an incoming frame if its VLAN tagging does not meet provisioned specifications. The priority bits in an incoming frame's VLAN tag can also be used to affect the handling of the frame.

The following table summarizes the 802.1Q Mode VLAN ID and

Frame Priority Rules. For more information regarding frame priority

rules on the LNW70 and LNW78, refer to “QoS services (LNW70 and

LNW78)” (A-90)

Frame

Contains a VLAN

Tag

Yes

Ingress Port is

Provisioned with a

Default

VLAN ID Priority

Don’t Care

Yes

Results

Yes

The frame’s VLAN ID is used. It must be on the Port’s VLAN List, otherwise the frame will be discarded.

The port’s user_priority field is used for queuing

The frame’s VLAN ID is used. It must be on the Port’s VLAN List, otherwise the frame will be discarded.

The frame’s priority is used for queuing.

Yes

A VLAN tag is added to the frame containing the port’s default VLAN ID and priority.

A VLAN tag is added to the frame containing the port’s default VLAN ID and the priority is set to low (VLAN

Tag’s User_priority field set to 0).

Don’t Care Frame is dropped.

A - 8 0

365-372-300

Issue 8.0 September 2006

Tagging Modes

: Ethernet/SAN

A VLAN ID can only be assigned to one virtual switch on a circuit pack.

On the LNW70/78, the same VLAN ID can be assigned to different virtual switches on the same pack.

When using the 802.1Q mode, a service provider must coordinate

(specify) the use of VLAN IDs with customers. If a VLAN ID is assigned to more than one customer, the customers could receive each others traffic.

In DMX, the VLAN ID may be a numerical value in the range 1-4093.

If a port has been provisioned with a default VLAN ID for untagged frames, all incoming untagged frames (this includes frames containing a VLAN tag with a TPID value other than 8100hex) will have VLAN tag added with the default VLAN ID. Any frame exiting the DMX network tagged with the default VLAN ID will have its VLAN tag removed before the frame is sent out the LAN port. Thus, assuming symmetric provisioning at the network edges, frames that enter the

DMX network untagged will leave untagged as well.

Frames that enter the network carrying a standard 802.1Q VLAN tag

(identified with a TPID value of 8100hex) have their VLAN ID checked against a VLAN list for the entry port. If a match is found, the frame is admitted; otherwise, the frame is discarded. On exiting the network, customer-tagged frames will be delivered with the customer-provided VLAN tag intact unless it matches the default

VLAN ID for the exiting port. In such a case, the customer-provided

VLAN tag will be removed before the frame is delivered.

365-372-300

Issue 8.0 September 2006

A - 8 1

Tagging Modes

A - 8 2

: Ethernet/SAN

Ethernet

The following figure shows the end-to-end frame processing combinations considering the following:

• Incoming frame tagging

• Default VLAN ID provisioning for source LAN port

• Default VLAN ID provisioning for destination LAN port

Figure A-34 802.1Q Mode VLAN Tag Processing

Ethernet

Over

SONET

Ethernet

Metropolis

DMX

Metropolis

DMX

Dropped if no default

VLAN ID provisioned

Packet

TPID=xxxx

(not 8100)

Tagged Packet

TPID=8100

Untagged

Packet

Dropped if no default

VLAN ID provisioned

Default

VLAN

Tagged

Packet

TPID=8100, xxxx

VLAN

List

Tagged Packet

TPID=8100 xxxx

Default

LAN

Packet

TPID=xxxx

VLAN

List

Default

VLAN

Tagged

Packet

TPID=8100

VLAN

List

Tagged Packet

TPID=8100

Default

VLAN

Untagged

Packet

LAN Port VLAN

Provisioning

MA-DMX-364

If VLAN tags are used, the ports support a maximum packet size of

1536 bytes (10236 for LNW70/78). If VLAN tags are not used, the ports support a maximum packet size of 1532 bytes (10240 for

LNW70/78).

The LNW66, LNW67, LNW68, LNW70, and LNW78 circuit packs support the 802.1Q mode. The LNW71 circuit pack does not support the 802.1Q mode.

Important!

After the VLAN ID is provisioned for untagged incoming Ethernet frames and service is established in the 802.1Q mode, changing the VLAN ID may affect service. When the

VLAN ID for untagged incoming Ethernet frames is changed at one point in the network, the VLAN ID must be changed at all points. If the VLAN IDs are different, service will be affected.

365-372-300

Issue 8.0 September 2006

Tagging Modes

: Ethernet/SAN

Transparent mode

In Transparent Mode, port tags (which are actually VLAN tags with a provisionable TPID value) are used to separate traffic for different customers. A port tag is added to each incoming frame at the ingress

LAN port. The port tag contains a provisionable customer ID and priority level.

The port tag, along with the destination MAC address, is used in switching the Ethernet frame to its correct destination. Assuming the destination port is also provisioned for Transparent Mode, the port tag is removed as the frame is delivered out the destination port.

When using the Transparent Mode, service providers usually assign one customer ID to each customer LAN port. The service provider need not coordinate the selection of this customer ID with the customer since it is independent of any 802.1Q VLAN tags generated by the customer.

Customers can use any VLAN ID they want without interfering with any other customer carried on the service provider's network.

In the transparent mode, the ports support a maximum packet size of

1532 bytes (LNW66/67/68) or 10240 bytes (LNW70/78).

The LNW66, LNW67, LNW68, LNW70, and LNW78 circuit packs support the transparent mode. The LNW71 and LNW74 circuit packs do not support the transparent mode.

365-372-300

Issue 8.0 September 2006

A - 8 3

Tagging Modes

: Ethernet/SAN

Ethernet

Tagged Packet

TPID=8100 or

TPID=8100, 8100 or

TPID=9100, 8100

Dropped if no default

TAG provisioned

Untagged

Packet

Dropped if no default

TAGID provisioned

The following figure shows end-to-end frame processing combinations considering the following:

• Provisionable TPID value set to its default value (0xFFFF)

• Incoming frame tagging

• Default port tag provisioning for the source LAN port

• Port tag provisioning for the destination LAN port.

Figure A-35 Transparent Mode Tag Processing

Default

TAG

Default

TAG

Metropolis

DMX

Ethernet

Over

SONET

Tagged Packet

TPID=FFFF, 8100 or

TPID=FFFF, 8100, 8100 or

TPID=FFFF, 9100, 8100

Tagged

Packet

TPID=FFFF

Metropolis

DMX

TAG

List

Default

TAG

List

Ethernet

Tagged Packet

TPID=FFFF, 8100 or

TPID=FFFF, 8100

8100 or

TPID=FFFF, 9100,

8100

Tagged Packet

TPID=8100 or

TPID=8100, 8100 or

TPID=9100, 8100

Tagged Packet

TPID=FFFF

Default

TAG

Untagged

Packet

LAN Port TAG

Provisioning

Provisionable

TPID=FFFF

MA-DMX-365

A - 8 4

365-372-300

Issue 8.0 September 2006

Tagging Modes

: Ethernet/SAN

365-372-300

Issue 8.0 September 2006

TPID Provisioning and Tag List Provisioning

In Release 4.0 and later releases, the value of the TPID (Ethertype) parameter used with generated VLAN Tags can be provisioned (in transparent mode only). Also starting in Release 4.0, the user may provision a list of acceptable customer tags for a LAN port. This pair of added features allows DMX to interoperate with other equipment that supports stacked VLANs.

The TPID became provisionable on DMX in Release 4.0. In Releases prior to Release 4.0, the TPID parameter is not provisionable and has a proprietary value of FFFFhex.

The following figure shows the end-to-end frame processing combinations considering the following:

• User provisionable TPID value (to 0x9100 in the example)

• Incoming frame tagging

• Default port tag provisioning for the source LAN port

• Port tag provisioning for the destination LAN port.

Figure A-36 Transparent Mode Tag Processing with Stacked

VLANs

Ethernet

Metropolis

DMX

Ethernet

Over

SONET

Metropolis

DMX

Tagged Packet

TPID=9100 or

TPID=8100, 8100 or

TPID=9100, 8100

Dropped if

TAG associated with

TPID=9100 not in Tag List

TAG

List

Tagged Packet

TPID=9100 or

TPID=9100, 8100

Untagged

Packet

Dropped if no default

TAG provisioned

Default

TAG

Tagged

Packet

TPID=9100

LAN Port TAG

Provisioning

DMX = Metropolis DMX Access Multiplexer

Provisionable

TPID=9100

TAG

List

Default

TAG

List

Default

TAG

Ethernet

Tagged Packet

TPID=9100 or

TPID=9100, 8100

Packed

Untagged or

TPID=8100

Tagged Packet

TPID=9100

Untagged

Packet

MA-DMX-366

A - 8 5

Tagging Modes

: Ethernet/SAN

Packet size in different tagging modes

The following table shows a comparison of the Ethernet tagging modes.

Tagging

Mode

Private Line

802.1Q

Transparent

VLAN Tag

N/A

Coordinated with customers

Independent of customer tags

VLAN

Filtering

Yes

Spanning

Tree

Priority

Optional

VLAN or Port

Based

Port

Based

Max.

Frame Size

(Bytes)

1532

Applicable

Circuit

Packs

LNW67,

LNW68

MTU

Size

9614

10240 LNW71

9632 LNW74

10240

LNW70,

LNW63

1536

(Tagged)

1532

(Untagged)

LNW66,

LNW67,

LNW68

10222

10240

LNW70,

LNW78

10222

1536

(Tagged)

1532

(Untagged)

LNW66,

LNW67,

LNW68

10240

LNW70,

LNW78

10222

A - 8 6

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

Quality of Service

Overview

DMX supports the following Quality of Service (QoS) capabilities:

• Private line service provides dedicated bandwidth between two points service (best QoS).

• Fractional rate services provide basic rate shaping with SONET tributary granularity.

• Committed information rate (CIR) policing provides rate limiting with 1 Mbps granularity.

• Peak information rate (PIR) policing provides rate limiting with 1

Mbps granularity.

• LNW70 enables advanced QoS capabilities including CIR rate metering.

For detailed information about Ethernet frame priority levels, refer to “Priorities” (A-47) and “802.1Q VLAN mode” (A-80) .

Peak information rate (PIR) shaping on LNW66,

LNW67, and LNW68 circuit packs

The LNW66, LNW67, and LNW68 circuit packs support a provisionable PIR rate limiting mechanism for traffic entering the

SONET network. A PIR value, in multiples of 1 Mbps, can be provisioned per VLAN for traffic leaving a VCG toward the SONET network. Traffic in excess of the provisioned value for each VLAN will be dropped. The PIR capability applies to all tagging modes supported by the listed circuit packs. For the LNW67 and LNW68 circuit packs in private line mode, PIR is specified per port rather than per VLAN.

The PIR policer uses a leaky bucket mechanism with a provisionable burst size and credit interval. The burst size determines how many tokens get put into the bucket each time it is replenished. This determines the length of a traffic burst that can be tolerated before packets are discarded. The credit interval determines the frequency with which the bucket is replenished. The burst size and credit interval parameters affect policing for all ports (in private line mode), all

VLANs (in 802.1Q mode) or all port tags (in transparent mode) on a particular Ethernet circuit pack.

Note that when sending data from a Gigabit Ethernet circuit pack, through the SONET network to a Fast Ethernet circuit card, the function described above is slightly different. With this configuration, the worst case is that a number of bytes equal to the full size of the token bucket in the GbE circuit pack will be sent using whatever SONET bandwidth has been provisioned (approximately 1 Gb/s in the worst case) to the

365-372-300

Issue 8.0 September 2006

A - 8 7

Quality of Service

A - 8 8

: Ethernet/SAN

Fast Ethernet card. The egress FE LAN port will be limited to sending the data out at 100 Mb/s. If the rapid arrival of a token bucket's worth of bytes exceeds the limited egress buffering capacity of the FE LAN port, packets will be dropped. This loss of packets can be minimized by minimizing the number of bytes in the token bucket at the GbE sending end by setting the smallest practical credit interval and burst size.

For more detailed information on metering, refer to “Metering (CIR and PIR)” (A-100) .

Adding Tokens

Every credit interval, tokens are added to the token bucket for each

VLAN/Port TAG/LAN port for which a PIR is provisioned. Each token represents 1 byte. (One credit interval is provisioned per circuit pack, and the provisioned credit interval applies to all VLANs/Port

TAGs/LAN ports on that circuit pack. The credit interval is a multiple of 524.288 µs; the multiple is determined by the provisionable credit interval parameter.)

The number of available tokens (A) in the token bucket for each

VLAN/Port TAG/LAN port is increased by at most,

(PIR*credit interval)/8 each credit interval, where PIR is the provisioned PIR in Mbps, and

credit interval is the provisioned credit interval for the circuit pack.

The divisor, 8, is required to convert from bits to bytes.

The number of available tokens (A) in each token bucket is subject to a maximum, which is determined by the provisioned PIR, the provisioned credit interval, and the provisioned maximum burst parameter. So each credit interval,

A = min (A + (PIR*credit interval)/8, BRST*(PIR*credit interval)/8)

The maximum burst represents the maximum size (in bytes) of the

burst (above the PIR) that will be passed by the policer. That is, a burst of this size (or smaller) will be allowed through the policer if the token bucket for the VLAN/Port TAG/LAN port is full (for example, because no packets have been processed for BRST credit intervals). If a burst of this size is passed, then the token bucket will be emptied and another burst will not be allowed through the policer until enough tokens have been accumulated in the token bucket. Another way to look at this is that the policer will pass a burst of packets above the PIR, as long as the long term average is no more than the provisioned PIR, where long term is defined as BRST*credit_interval.

365-372-300

Issue 8.0 September 2006

Quality of Service

: Ethernet/SAN

Removing Tokens

When a packet arrives, the token bucket for the associated VLAN/Port

TAG/LAN port is checked.

If no tokens are available for the VLAN/Port TAG/LAN port, then the packet is discarded.

If tokens are available, the packet is forwarded and the number of available tokens for that VLAN/Port TAG/LAN port is decreased by the packet size:

If A >= 1 A = A - packet size and forward the packet, else discard the packet.

QoS services (LNW71/74)

The LNW71 and LNW74 circuit packs provide 10 Mbps and 100 Mbps private line services. They do not contain an Ethernet Switch. Each

LAN port is connected to its own VCG. 100 Mbps traffic can be rate-limited by provisioning less SONET bandwidth than required to carry the full line rate. Traffic is buffered and flow control is invoked when ingress traffic on a LAN port exceeds the VCG’s SONET bandwidth. If flow control is disabled or ignored by the external equipment, Ethernet frames are dropped when the ingress buffer overflows. The LNW74 offers 1.5Mbps VT granularity.

365-372-300

Issue 8.0 September 2006

A - 8 9

Quality of Service

: Ethernet/SAN

QoS services (LNW70 and

LNW78)

The capabilities of the LNW70, available beginning in R5.1, enable enhanced QoS features. The LNW70 can function in either Private Line or Switched mode. The LNW78 is available beginning in R6.0. It is an

RPR enabled switched Ethernet card. It does not support Private Line.

The QoS capabilities of the LNW70 are different depending on the mode the card is in. Also, within the two modes below, there are a variety of traffic conditioners which can be applied, depending on the mode) which further govern the QoS capabilities of the pack.

• Private Line: DMX can perform rate controlling at a sub-STS level and on a per-port basis in PL mode. In PL mode, if rate control is desired, the traffic management mode will be port mode

(see Traffic Conditioners below). LNW78 does not support private line.

• Switched Mode: DMX can perform VLAN processing and enhanced QoS in switched mode. There are two settings within switched mode: Transparent and IEEE 802.1q mode. Refer to

"Tagging Modes" on page A-79.

In order to provide enhanced QoS services, traffic must be classified, and conditioned. This is accomplished using traffic conditioners that are applied to packets at the boundary port (see Boundary vs. Interior

Port below).

A - 9 0

365-372-300

Issue 8.0 September 2006

Quality of Service

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

Traffic Management Mode

The QoS features available on any given port will vary depending on the particular traffic conditioners applied to that port. The 5 traffic conditioners supported by DMX are as follows:

• PORT mode: One traffic conditioner for the port. All traffic that is permitted to be transported flows through a single traffic conditioner.

• COSPORT mode: One traffic conditioner for each class of service at the port. All traffic for an individual CoS is provisioned with its own traffic conditioner.

• TAGPORT mode: One traffic conditioner for each Packet Tag at the port. Traffic for all classes of service that have the same Packet

Tag flow through a single traffic conditioner.

• COSTAGPORT mode: One traffic conditioner for each class of service for each Packet Tag/VLAN at the port. All traffic for an individual CoS on each Packet Tag is provisioned with its own traffic conditioner.

• NOTC mode: In this mode all traffic is bridged through the switch as usual but there is no traffic conditioning performed on the traffic. NOTC mode emulates the (basic) QoS behavior on the older DMX circuit packs (user_priority values 0,1,2 and 3 are mapped to CoS 0 and user_priority values 4,5,6 and 7 are mapped to CoS 3; no modification of user_priority bits in user packets).

Boundary versus Interior Ports

When speaking of QoS, a port is either a Boundary or Interior port. A boundary port is at the edge of a differentiated services (DiffServ) domain and an Interior port in a the core of a DiffServ domain. All traffic policing, conditioning, and marking is done at boundary ports. It is assumed that these functions have been performed by the time packets reach the interior ports. Boundary/Interior demarcation is controlled by an explicit parameter. By way of provisioning, a LAN port can be either boundary or interior, but a VCG is usually an interior port. A VCG can be a boundary port, but this limits the traffic management mode provisionable for that port to NOTC only.

QoS functionality is built around the concept of boundary and interior ports. Though the terminology customer and network are often used in place of boundary and interior (where customer equals boundary and interior equals network), this is incorrect with reference to DMX.

However, customer and network terminology is still applied to ports

A - 9 1

Quality of Service

: Ethernet/SAN

with respect to their overall VLAN tagging behavior, rather than QoS specific functions.

For the LNW78 RPR card the following is true. An RPR VCG is always interior. A LAN port is always boundary.

The table below details what traffic management modes are allowed to be provisioned on ports depending on wether they are boundary or interior ports. Attempts to provision a VLAN tagging mode/traffic management mode combination that is not listed in the table below shall be denied.

Table A-2 Allowed Traffic Management Modes per Port Type

Traffic Management Mode

VLAN Tagging Mode Port Type

Private Line

Transparent

802.1TAG

Boundary Port*

Interior Port*

Boundary Port

Interior Port

Boundary Port

LNW70

NOTC

PORT

N/A

COSPORT

NOTC

PORT

N/A

NOTC

PORT

TAGPORT

COSPORT

COSTAGPORT

N/A

LNW78

PORT

N/A

PORT

N/A

COSPORT

N/A

Interior Port N/A N/A

*NOTE: In Private Line mode, it is not possible to change the Boundary/Interior demarcation of LAN and

VCG ports. The LNW78 does not support Private Line

A VCG can be a boundary port, but this limits the traffic management mode provisionable for that port to NOTC only.

A - 9 2

365-372-300

Issue 8.0 September 2006

Quality of Service

: Ethernet/SAN

Untagged or Unprovisioned Packets

The table below explains what happens at the ingress when untagged or unconditioned packets are received. If a packet arrives at a port and it is marked with a CoS and Packet Tag for which a traffic conditioner has not been provisioned at that particular port, the traffic will be handled as described in the table below.

Table A-3 Handling of Untagged or Unprovisioned service at

Boundary Ports

VLAN tagging mode

Private Line

Transparent

802.1TAG

Traffic Management mode

NOTC

PORT

NOTC

PORT

NOTC

Untagged traffic

Pass all traffic unmodified

Tag with default port tag and default CoS and pass traffic

CoS-Packet Tag

Traffic Conditioner not provisioned

Pass all traffic unmodified

Not Applicable

Tag with default port tag and default CoS and pass traffic

Tag with default port tag and default CoS and pass traffic unmetered

(marked Yellow)

Tag with default

VLANid and default

CoS and pass traffic

Not Applicable

365-372-300

Issue 8.0 September 2006

A - 9 3

Quality of Service

A - 9 4

: Ethernet/SAN

QoS in Private Line Mode

Private Line mode should be employed when deploying point-to-point service connections using dedicated resources. Private Line can either be a full-rate service or a subrate service. Full-rate services dedicate enough network resources to transport the data from the ingress

Boundary Port through the network to the egress Boundary Port at the full data rate of the Boundary Ports. Subrate services transport data at a fraction of the full data rate of the Boundary Ports.

In Private Line Mode, the Boundary Ports (see Boundary vs. Interior

Ports above) can have either NOTC or PORT traffic management mode; the Interior Ports are always NOTC. All packets received are handled uniformly using a single queue. Packets are not modified or remarked in this mode. Therefore, it is not possible to encode color.

Consequently, packets are either dropped or passed-through transparently. This is achieved by setting CIR values equal to PIR values and by forcing CBS to equal PBS.

QoS in Transparent and 802.1q mode

Transparent mode

Transparent mode provides a trunked Private Line or “Virtual Private

LAN” service. The Boundary Ports use either a NOTC or PORT traffic management mode. In transparent mode, customers packets are not changed.

In NOTC mode, just as with Private Line, there is no traffic conditioning performed on any of the boundary Ports. Traffic conditioning is never performed on the Interior ports.

In the PORT mode all traffic that enters the port is tagged (stacked

VLAN) with the provisioned TPID and the default port tag. The CoS is set to the default priority for that port and the user_priority is set based on this CoS and the conformance level determined in the traffic conditioner.

Packets that are within the committed contract parameters are marked with a Drop Precedence of DP1 (green). Packets that arrive out of the guaranteed contract, but within some allowable excess, are marked with a Drop Precedence of DP0 (yellow). Packets that arrive outside of the allowed excess are discarded.

The user_priority is determined from the CoS level and Drop

Precedence. The packet is remarked with this user_priority before leaving the egress port.

365-372-300

Issue 8.0 September 2006

Quality of Service

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

In both NOTC and PORT mode, if no default priority is specified for the port, the CoS value is set to 0. There is no traffic conditioning on

Interior Ports (see Boundary vs. Interior Ports above).

With Transparent tagging, both PIR, CIR, PBS and CBS are used to allocate the appropriate network resources to each service. Transparent mode supports user network configurations with more than two nodes in case a multipoint “Virtual Private LAN” service is needed. For this service each Boundary Port is provisioned with the same default port tag and default priority. This results in the required traffic separation to provide a virtual private network.

802.1q mode

The 802.1TAG tagging mode assumes that packets arrive at the boundary to the network already tagged with a standards-compliant

VLAN tag. It is possible then to offer a number of services at a single port simultaneously.

In 802.1q mode, the packets should be tagged by the subscriber, however, some packets may arrive untagged. The CoS level for tagged packets is determined either by the default port CoS level (PORT mode) or the default VLAN CoS level (TAGPORT mode), or by examining the user_priority and setting the CoS according to a fixed mapping (NOTC and PORT mode), or according to a provisionable mapping table. The mapping table is associated either with a port

(COSPORT mode) or a VLAN (COSTAGPORT mode). Untagged traffic is tagged with the default VLAN. The CoS is then set to either the default port CoS level (NOTC,PORT,COSPORT mode) or the default VLAN CoS level (TAGPORT, COSTAGPORT mode). The packets are then conditioned (except for NOTC) in the same fashion as tagged traffic.

Priority-tagged traffic is tagged with the default VLAN, and the CoS level is determined as it would be for a tagged packet.

In all cases, the Drop Precedence (DP) is set according to the level of conformance specified in the customer's SLA contract.

The functionality of each traffic management with regard to 802.1q mode is detailed below:

• PORT:

The PORT mode of operation, is very similar to the services offered in the Transparent tagging mode, except that in this case the standard TPID (Ethertype) of 8100 is used so that this mode is interoperable with other 802.3 networks. Also more than one VLANid

A - 9 5

Quality of Service

A - 9 6

: Ethernet/SAN

can be supported at a single port and treated as a single traffic flow. In this mode the traffic conditioning for all traffic that is admitted to the port is performed as an aggregate data flow by a single traffic conditioner. Only traffic that is either untagged or tagged with a

VLANid that has been provisioned at the port will be admitted. In this mode the user_priority bits will be remarked according to the packets

user_priority (0,1,2,3 map to CoS 0 and 4,5,6,7 map to CoS 3) unless overruled by the default priority. Drop Precedence is determined as a result of the packets conformance to the SLA. Any remarking that occurs is irreversible and will be present on the packet at the network egress.

•

TAGPORT:

In the TAGPORT mode of operation, a single CoS is associated with each VLAN. The traffic flows through a traffic conditioner per VLAN where it is metered and policed as per the terms of the SLA. In this mode each VLAN has its own PIR, CIR, PBS and

CBS. Packets that arrive untagged are tagged with the port default

VLANid and CoS for that VLAN. As with the other modes, the Drop

Precedence is determined based on the conformance to the SLA. Any remarking that occurs is irreversible and will be present on the packet at the network egress.

•

COSTAGPORT:

In the COSTAGPORT mode of operation, traffic for each CoS on each VLAN flows through its own traffic conditioner.

Traffic that is tagged with one of the port’s provisioned VLANids is admitted to the network. Packets that arrive untagged or priority-tagged are tagged with the port default VLANid. Packets tagged with an unprovisioned VLANid are discarded. The user_priority bits in a priority-tagged frame are used to determine the CoS when selecting the traffic conditioner. In this mode each CoS on each VLAN has its own

PIR, CIR, PBS and CBS. On each VLAN each CoS can be individually enabled or disabled. The Drop Precedence is determined by the SLA conformance level and the packet is remarked accordingly. This marking is not reversible and will be present when the packet egresses the network.

• COSPORT:

In the COSPORT mode of operation, traffic for each class of service flows through its own traffic conditioner. Traffic that is tagged with one of the port’s provisioned VLANids is admitted to the network.

Packets that arrive untagged or priority-tagged are tagged with the port default VLANid. Packets tagged with an unprovisioned VLANid are discarded. The user_priority bits in a priority-tagged frame are used to determine the CoS when selecting the traffic conditioner. In this mode each CoS has its own PIR, CIR, PBS and CBS. Each CoS can be

365-372-300

Issue 8.0 September 2006

Quality of Service

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

individually enabled or disabled. The Drop Precedence will be remarked according to the conformance to the SLA. This marking is not reversible and will be present when the packet egresses the network.

The table below shows the default mapping of user priority bits to CoS.

Table A-4 Default mapping of User Priority to CoS user_priority

000

001

010

011

100

101

110

111

CoS

The table below shows the default mapping of DSCP to CoS. In R6.0,

DMX adds support of DSCP for traffic classification on the LNW70.

DSCP to CoS is available in PORT mode only. DSCP can be used as an alternative to priority bits. So, the criteria for traffic classification can now be user priority bits, DSCP, VLANid, or default value. DSCP allows for three differentiated services code point values: IP precedence value (also called Class Selector-- CS in the table below),

Assured Forwarding (AF), and Expedited Forwarding (EF).

Table A-4 Default mapping of DSCP to CoS

CoS

DSCP

Default

CS1

AF11

AF12

AF13

CS2

AF21

Binary

000000

001000

010010

001100

001110

010000

010010

Decimal

A - 9 7

Quality of Service

CoS

: Ethernet/SAN

AF33

CS4

AF41

AF42

AF43

CS5

CS6

CS7

DSCP

AF22

AF23

CS3

AF31

AF32

011110

100000

100010

100100

100110

101000

101110

110000

111000

Binary

010100

010110

011000

011010

011100

Decimal

A - 9 8

365-372-300

Issue 8.0 September 2006

Quality of Service

: Ethernet/SAN

The table below shows the characteristics of which services are offered relative to the VLAN tagging mode and traffic management mode.

These characteristics include the number of services allowed at a port as well as the number allowed on the network. Certain columns are divided into LNW70 and LNW78, this is only done where the LNW78 supports the management mode detailed in that column.

Table A-5 Combination of VLAN Tagging and Traffic

Management Modes

Transparent

Private Line 802.1TAG

No.

Services at 1 port

No.

Services on

Network

NOTC PORT NOTC

PORT

LNW78

1 to

4093

Max. CoS

Support

Traffic

Conditioning

No No No

CoS/

Port

PIR

None

PBS

CIR

CBS

Non e

PIR

PBS

CIR

CBS

COSPORT

NOTC

LNW70

1 1

COSPORT

PORT

TAGPORT

COSTAG

PORT

LNW78 LNW70

1 per

VLANi d

4093 max.

1 per

CoS

Level

1 per

CoS

Level

3 max.

4 max.

1 per

CoS

Level per

VLANi d

16,372 max.

1 to

4093

1 to

4093

1 to

4093

1 to

4093

1 to

12,279

1 to

16,372

1 to

16,372

1 CoS/

Port

PIR

PBS

CIR

CBS

None

3 CoS/

Port

4 CoS/

Port

4 CoS/

VLAN

PIR

PBS

CIR

CBS

PIR

PBS

CIR

CBS

PIR

PBS

CIR

CBS

3 CoS/

Port

CoS/P ort

4 CoS/

VLAN

PIR

PBS

CIR

CBS

PIR

PBS

CIR

CBS

PIR

PBS

CIR

CBS

365-372-300

Issue 8.0 September 2006

A - 9 9

Quality of Service

: Ethernet/SAN

Transparent

Private Line 802.1TAG

COSPORT

NOTC

COSPORT

NOTC PORT NOTC

PORT PORT

TAGPORT

COSTAG

PORT

LNW78 LNW70 LNW78 LNW70 LNW78 LNW70

Packets

Altered?

No No No No

Maybe

Maybe untag’

VLANi d d user_pri ority

Maybe

VLANi d user_pri ority

Maybe

VLANid user_prior ity

Maybe

VLANi d

Maybe

VLANi d user_pri ority user_pri ority

Maybe

VLANid user_prio rity

The number of services at a port is the number of traffic conditioners used, except for the NOTC mode where there is 1 service with no traffic conditioner.

The number of services on a network is the total number of separate VLANids/default port tags allowed on the network in separate services times the number of traffic conditioners that are allowed for each VLANid/default port tag.

The maximum number of Classes of Service supported is the number that will be passed through any traffic conditioner on that port. For example, in 802.1TAG mode the PORT mode will allow all 4 CoS Levels to pass through a common traffic conditioner, whereas, in Transparent mode the PORT mode tags all traffic with the default CoS and therefore only a single

CoS is supported.

The traffic conditioning parameters shown are those available via TL1. In a practical sense fewer parameters are needed to provision the service

Packets are considered altered if the user packet that egresses the network at a Customer Port is not identical to the packet that ingressed the network at a Customer Port. Packets are generally altered in 802.1TAG mode due to the addition of a

VLAN tag or the alteration of the user_priority.

Metering (CIR and PIR)

Rate limiting is achieved using Peak Information Rate (PIR) provisioning. Guaranteed rate service is achieved using Committed

Information Rate (CIR) provisioning. PIR institutes a limit, or

“ceiling”, of maximum bandwidth to be allocated to a particular customer at any time. CIR, on the other hand, provides a guaranteed

A - 1 0 0

365-372-300

Issue 8.0 September 2006

Quality of Service

: Ethernet/SAN

minimum, or “floor” throughput even during periods of high congestion.

PIR

Burstable Bandwidth

CIR

Guaranteed Bandwidth nc-dmx2-032

When SLAs are written using CIR, Excess Burst Size (PBS), and

Committed Burst Size (CBS), they guarantee a CIR and CBS at a particular data rate. Traffic can be allowed to burst up to an excess burst size (PBS) beyond the CBS. This traffic will only be transmitted on a Best Effort basis. Any traffic above the PBS will be discarded. In this type of SLA, PIR is equal to CIR. The CIR must always be less than the maximum bandwidth that the port can support. If either CIR or

PBS is set to zero, service is effectively terminated.

The second method used to specify SLAs employs CBS, PIR, CIR, and

PBS. Burst Time can also be used in place of PBS. With SLAs of this sort, PIR, CIR, PBS, and CBS must be provisioned.

The figure below details the flow of traffic through the QoS packet with on the LNW70 and LNW78 circuit packs. The ingress and egress functions of the switch are explained further below the figure. Note that the DSCP Field has been added to the ingress port. DSCP functions only on the LNW70 in R6.0, though DSCP functionality on the

365-372-300

Issue 8.0 September 2006

A - 1 0 1

Quality of Service

: Ethernet/SAN

LNW78 is planned for a future release. On the egress functions side, the LNW78 supports 3 classes of service. So, for the LNW78, queue

"0" would be absent.

Ingress

Port

Ingress Filtering

– VLANid

Traffic Classification

– Determin CoS

Flow Classification

– Based on: Port, Tag,

CoS and DSCP field

(new for R6.0)

Figure A-37 Flow and Classifications of Traffic through QoS

Packet Switch

Ingress

Functions

Egress

Functions

Switch

Fabric

Traffic

Flow

Traffic

Conditioner

Metering

Policing

Counting

Marking

– with drop precedence

Remarking, if needed

Paremeters:

– Peak Information Rate (PIR)

– Committed Information Rate

(CIR)

– Excess Burst Size (EBS)

– Committed Burst Size (CBS)

CPU

– Slow Protocols

– Management

Output

Queues

– Dropper

– 4 Queues for

User Frames

– One Queue for

Management

Frames

Scheduling

Egress

Port

Management

A - 1 0 2

= The LNW78 supports

3 CoS. So, queue 0 does not exist on the

LNW78, but it does on the LNW70

JK-E-13.eps

The Ingress Port functions are as follows:

• Traffic Classification: Determines class of service (CoS), criteria can be 802.1p user priority, DSCP (R6.0), VLANid, or default value. Each class is mapped to an output queue. Internal management is classified into its own class.

• Flow Classification: A flow is a grouping of traffic based on certain criteria. The flow classification determines which Traffic

Conditioner will be used and multiple flows can be aggregated at a single traffic conditioner. Criteria is based on packet header, input port, flow, physical port, VLANid, DSCP (R6.0), and/or 802.1p user priority.

• Traffic Conditioner: Traffic Conditioners perform the metering, policing, marking, and counting of ingress packets. The parameters are PIR, CIR, PBS, and CBS. Metering measures the data rate which determines wether the packets conform to the settings for the user/port. Packets are marked according to conformance level (this is an internal marking). Policing discards

365-372-300

Issue 8.0 September 2006

Quality of Service

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

packets that exceed the PIR, PBS, or PBS (see Metering above).

The conformance level determines the drop precedence (DP) for non-conforming packets.

• Note: Flow Classification and Traffic Conditioning only apply to boundary ports. Once CoS and DP are determined at the boundary port, they are used consistently throughout the network. At internal ports, CoS and DP are then used to determine egress functions (i.e. dropping and queuing). For information on boundary and internal port demarcation, see the section below entitled Boundary versus Interior Ports.

The Egress Port functions are as follows:

• Dropping: Also known as Egress Queueing, Dropping is based on conformance level and the fullness of the queue. The drop function takes into account the total allocation queue for a particular port only. There are two drop methods employed by

DMX: Tail Drop and Weighted Random Early Detection

(WRED). The tail drop method discards all packets exceeding the maximum queue size. It uses only one parameter: Maximum

Queue Size. WRED dropping starts at the minimum threshold and increases up to the maximum. Two drop parameters govern

WRED: Minimum Threshold and Maximum Threshold. The CoS parameter, Maximum Drop Probability, is also provisionable in the WRED method. packets labeled with a higher drop precedence

(DP) will be discarded prior to those with a lower drop precedence.

• Scheduling: Scheduling allocates service for each queue. There are queues for each port: Expedited Forwarding (EF), Assured

Forwarding (AF). A combination of two algorithms controls scheduling. Packets in the Strict Priority queue are transmitted first. Strict Priority is used for EF queue. Weighted Round Robin

(WRR) ensures that the remaining bandwidth is allocated to each queue based on a provisioned weighting factor. WRR is used for the AF queues.

Egress functions support four classes of service (CoS). EF guaranteed low latency. There are three levels of AF offering various degrees of guaranteed delivery including best-effort.

Packets are handled differently depending on wether they originated from Boundary or Interior ports.

• Three Colors: RED: for packets that exceed peak rate limits.

Yellow: for packets that exceed committed rate limits.

Green: for packets within committed rate limits.

A - 1 0 3

: Ethernet/SAN

Ethernet Service Management

Overview

The Ethernet services are managed by provisioning the following:

• Tagging (VLAN) mode

• Cross-connections

• LAN ports

• VCG (WAN) ports

• Virtual switches

• Quality of service (QoS) features.

• Performance monitoring.

For detailed information about provisionable parameters and their values, refer to Appendix B: Performance Monitoring.

Tagging (VLAN) modes

DMX supports the private line, transparent, and 802.1Q tagging modes.

Tagging modes are provisioned on a circuit pack basis. Changing tagging modes will impact service. For detailed information about the

tagging modes, refer to “Tagging Modes” (A-79) and the WaveStar

CIT on line help.

Cross-connections

The following types of cross-connections are used with Ethernet circuit packs.

• 1way

• 1wayPR

• 1way unswitched

For detailed information about supported cross-connections refer to

Chapter 5 of this document and the WaveStar

CIT on line help.

Cross-connections with SONET Layer Protection

All SONET protected services are implemented using 1way or 1wayPR cross-connections. They are used to form a pair of bidirectional links between a VCG port and one side of a SONET tributary. 1way or

1wayPR cross-connection use two VCGs on LNW66, LNW67, and

LNW68 Ethernet circuit packs and one VCG on all other Ethernet circuit packs (LNW63, LNW73, LNW73C, LNW74, LNW70, and

LNW78). 1way or 1wayPR cross-connections are described in

“Protected Tributaries” (A-35) . The use of VCG ports is summarized in

“VCG (WAN) ports” (A-109) .

A - 1 0 4

365-372-300

Issue 8.0 September 2006

Ethernet Service Management

: Ethernet/SAN

Cross-Connections without SONET Layer Protection

Services that are not protected by the SONET layer are provisioned using either 1way or 1way unswitched cross-connections.

1way cross-connections can be used to provide unprotected services on

BLSRs, only if the tributary (time slot) is provisioned to carry non-preemptible unprotected traffic (NUT). The BLSR tributary(s) must be provisioned for NUT before the cross-connection is established or protected services will be provided. A packet ring bandwidth could be split between working and protection (extra traffic) freeing up protected working bandwidth for other TDM services. 1way cross-connections can be used to provide unprotected services over

BLSR w/ NUT, but they are less efficient than 1way unswitched cross-connections.

1way unswitched cross-connections can be used to provision unprotected traffic on UPSRs. One cross-connection can be made between a VCG port and one side of the SONET ring, and the other can be made between the paired VCG and the other side of the SONET ring.

Unprotected cross-connections (1way unswitched) to UPSRs and

BLSRs w/ NUT are all provisioned independently per VCG beginning in R6.0.

This pairing of VCG ports and USPR unprotected cross-connections is described in “Unprotected Tributaries” (A-36) . The use of VCG ports is summarized in “VCG (WAN) ports” (A-109) .

Cross-Connection Types and Supported Configurations

The number of Private Line Services and Packet Rings an Ethernet circuit pack can support is dependent on the type of cross-connection used and whether SONET layer protection is used.

365-372-300

Issue 8.0 September 2006

A - 1 0 5

Ethernet Service Management

: Ethernet/SAN

The following table shows the cross-connection types and supported services.

Table A-6 Ethernet Private Line Services

SONET

UPSR

Ethernet Private Line Cross Connections

Ethernet Circuit Pack

Cross Connection

Type

LNW63 LNW64 LNW66

LNW6

7/68

LNW7

VT1.5 1WAYPR and 1WAY

STS-1 1WAYPR and

1WAY

N/A

1 or 2

N/A

STS-3c 1WAYPR and

1WAY

STS-12c 1WAYPR and 1WAY

STS-1 1WAY

UNSWITCHED

STS-3c 1WAY

UNSWITCHED

STS-12c 1WAY

UNSWITCHED

N/A

LNW7

N/A

12 or

8 or 16

N/A

12 or

8 or 16

N/A

LNW74

12-24

N/A

8 or 16

N/A

1+1

VT1.5 1WAY

STS-1 1WAY

STS-3c 1WAY

STS-12c 1WAY

VT1.5 1WAY

BLSR

STS-1 1WAY

STS-3c 1WAY

STS-12c 1WAY

A - 1 0 6

N/A

1 or 2

N/A

12 or

8 or 16

N/A

8 or 16

N/A

1 or 2

N/A

12 or

8 or 16

N/A

12-24

8 or 16

N/A

365-372-300

Issue 8.0 September 2006

Ethernet Service Management

SONET

BLSR

3 w/

NUT

Cross Connection

Type

Ethernet Private Line Cross Connections

LNW63 LNW64

Ethernet Circuit Pack

LNW66

LNW6

7/68

LNW7

VT1.5 1WAY

UNSWITCHED

STS-1 1WAY

UNSWITCHED

STS-3c 1WAY

UNSWITCHED

STS-12c 1WAY

UNSWITCHED

N/A

LNW7

N/A

12 or

8 or 16

N/A

: Ethernet/SAN

LNW74

N/A

Notes:

1. A mix of VT1.5, STS-1, & STS-3c connections allowed; Max of 336 VT1.5

(12 STS-1s) of VT1.5 cross connect capacity.

2. When using small or medium fabric MAINs, the small value reflects the capacity for function groups A, B, & C. Values for function groups D & G are represented by the larger value. When using all large fabric MAINs, ALL function groups support the larger value.

3. SONET protection is provided if NUT is not provisioned, and disabled if

NUT is provisioned.

365-372-300

Issue 8.0 September 2006

A - 1 0 7

Ethernet Service Management

: Ethernet/SAN

The following table shows the cross-connection types and supported services.

Table A-7 Ethernet Packet Ring Services

SONET

Ethernet Packet Ring Cross Connections

Cross Connection

Type

LNW66

Ethernet Circuit Pack

RPR

Ring

RPR

Pack

LNW67/

LNW70 LNW71 LNW74 LNW78

UPSR 1WAY UNSWITCHED 1

1WAYPR and 1WAY

1WAY

N/A

0 BLSR

BLSR w/ NUT

1WAY UNSWITCHED N/A

1 or 2

0 or 1

N/A

Notes:

1. When using small or medium fabric MAINs, the small value reflects the capacity for function groups A, B, & C. Values for function groups D & G are represented by the larger value. When using large fabric MAINs, ALL function groups support the larger value.

A - 1 0 8

365-372-300

Issue 8.0 September 2006

Ethernet Service Management

: Ethernet/SAN

LAN ports

VCG (WAN) ports

All LAN ports have characteristics that must be the same on both sides of a link. Some characteristics are strictly physical in nature. They can only be changed by using different equipment. Some examples of these characteristics are cable type (for example, twisted pair, fiber) and optical type (short reach, long reach). For more information about the

Ethernet circuit packs, refer to

“Ethernet/SAN Circuit Packs” (A-8)

The

Configuration > Provision Equipment

WaveStar

CIT command is used to provision LAN ports. For more information about the

Configuration > Provision Equipment

command and LAN port provisioning, refer to the WaveStar

CIT on-line help.

The

Configuration > Provision Equipment

WaveStar

CIT command is used to provision VCG (WAN) ports. For more information about the

Configuration > Provision Equipment

command and VCG (WAN) port provisioning, refer to the WaveStar

CIT on-line help.

365-372-300

Issue 8.0 September 2006

A - 1 0 9

Ethernet Service Management

: Ethernet/SAN

The following table shows the available VCG (WAN) ports available on Ethernet circuit packs.

Table A-8 VCGs Available on Ethernet Circuit Packs

Type

LNW63

LNW66

LNW67 and

LNW68

Ethernet Circuit Pack

Slot

Tagging

Mode

Transparent and 802.1Q

(Switched)

Private Line

Provisionable VCG Ports

LNW26,

LNW26B, and PWDM

Equivalent

OLIUs

All other

OLIUs

VCG1-VCG8 VCG1-VCG8

Comments

A-1, B-1, C-1,

D-1, G-1

A-1, B-1, C-1,

D-1, G-1

Private Line

A-1, B-1, C-1,

&D-1

Transparent and 802.1Q

(Switched)

VCG1-VCG4

VCG1, VCG2

VCG1-VCG4

VCG1, VCG2 See Note 2

A-1, B-1, C-1,

&D-1

A-1, B-1, C-1,

&D-1

A-1, B-1, C-1,

&D-1

A-1, B-1, C-1,

&D-1

A-1, B-1, C-1,

D-1, G-1

Private Line

VCG1

VCG1, VCG3

VCG1, VCG2

VCG1-VCG4

VCG1, VCG3

VCG1-VCG4

See Note 3

LNW70

LNW78

(RPR ports)

LNW78

(EoS ports)

A-1, B-1, C-1,

D-1, G-1

A-1, B-1, C-1,

D-1, G-1

A-1, B-1, C-1,

D-1, G-1

Transparent and 802.1Q

(Switched)

Transparent and 802.1Q

(Switched)

Transparent and 802.1Q

(Switched)

VCG1-VCG32

VCG1 and

VCG2

VCG17-

VCG22

VCG1-VCG32

VCG1 and

VCG2

VCG17-

VCG22

See Note 5

A - 1 1 0

365-372-300

Issue 8.0 September 2006

Ethernet Service Management

: Ethernet/SAN

Type

Ethernet Circuit Pack

Slot

Tagging

Mode

Provisionable VCG Ports

LNW26,

LNW26B, and PWDM

Equivalent

OLIUs

All other

OLIUs

Comments

LNW71

A-1, B-1, C-1,

&D-1

A-1, B-1, C-1,

&D-1

A-1, B-1, C-1,

&D-1

A-1, B-1, C-1,

&D-1

Private Line

STS-1 Mode

Private Line

STS-3c Mode

VCG1-VCG24

VCG1-VCG8

VCG1-VCG24

VCG1-VCG16

See Note 1

LNW74

A-1, B-1, C-1,

D-1, & G-1

A-1, B-1, C-1,

D-1, & G-1

Private Line

VCG1-VCG24 VCG1-VCG24

Notes:

1. All 24 VCGs are available only when unswitched cross-connections are used. Only 12 VCGs are available if protected cross-connections are used.

2. Only VCG1 is available when protected cross-connection is used.

3. VCG2 is not available when protected cross-connection is used on VCG1. VCG4 is not available when protected cross-connection is used on VCG3

4. Although the LNW74 can be used in slot G-1, only the optical ports are functional.

5. R7.0 adds support of EoS service on VCGs 17-22 of the LNW78. VCG port pairings are consecutive. Therefore, when VCG18 is not available when a protected cross-connection is used on VCG17 etc...

6. In Release 7.0 and going forward, when the VLF Main pack (LNW59) is used, DMX allows ethernet pack to be installed in Slot 1 and/or 2 of a function unit or growth slot (where applicable).

Certain circuit pack/slot equipage restrictions apply. For more information refer to Very Large

Fabric (VLF) Engineering Rules

. Prior to R7.0, and when VLF Mains are not used, ethernet packs can only be installed in Slot 1 of a function unit or growth slot.

365-372-300

Issue 8.0 September 2006

A - 1 1 1

Ethernet Service Management

Virtual switch

: Ethernet/SAN

A virtual switch is a logical grouping of LAN ports and VCG ports that share interconnect and share a common set of properties. A virtual switch may support one or more spanning trees; a spanning tree can only belong to one virtual switch.

A port (LAN or VCG) can only be assigned to one virtual switch at a time. On the LNW66/67/68 packs VLANs (802.1Q mode) and port tags (transparent mode) that are assigned to a virtual switch cannot be assigned to another virtual switch on the same circuit pack.

The LNW70 circuit packs can support a maximum of 16 virtual switches on each circuit pack (LNW66/67/68 support 2).

The following WaveStar

CIT commands support virtual switch provisioning:

•

Configuration > Data > Create a Virtual Switch

•

Configuration > Data > Delete a Virtual Switch

•

Configuration > Data > Provision a Virtual Switch

For more information about provisioning virtual switches and the

WaveStar

CIT commands, refer to the WaveStar

CIT on-line help.

Quality of service (QoS)

The following Quality of Service (QoS) parameters are provisionable using the WaveStar

CIT.

• Default port priority (high, low, NA)

• Rate Policing (PIR)

• Peak information rate (PIR) is provisioned on a VLAN/port TAG or on a LAN port basis for protected private line.

• Burst size length

• Credit interval for adding tokens to the token buckets used by the

PIR

For more information about Quality of Service, refer to

“Quality of

Service” (A-87) and

“QoS services (LNW70 and LNW78)” (A-90)

For more information about the provisionable QoS parameters, refer to the WaveStar

CIT on line help.

Performance monitoring

Each Ethernet port has associated performance monitoring parameters and counters. The counters are provided for incoming and outgoing frames. For detailed information about Ethernet performance monitoring parameters, refer to Appendix B, “: Performance

Monitoring” .

A - 1 1 2

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

Ethernet Service Configurations

Overview

DMX supports the Ethernet services shown in the following table.

Table A-9 Supported Ethernet Services

Service

Private

Line

Private

LAN

Virtual

Private

LAN

Ethernet

Virtual

Private

LAN

VCGs (per

Circuit Pack)

1 Private Line per VCG

Protected

1 Private Line per VCG

Unprotected

1 Subscriber per

VCG

Several

Subscribers per

VCG

Ethernet

Ports

SONET

Capacity

Dedicated

Dedicated or Shared

Dedicated

Shared

Tagging

Mode

Private

Line

(No tag)

Ethernet

Forwarding

(Switching) based on

No Ethernet switching.

Point-to-Point connection is preconfigured.

Transparent No Ethernet switching.

802.1Q

Point-to-Point

Transparent Stacked VLAN Tag

802.1Q

Original or Port

Default VLAN Tag

Transparent Stacked VLAN Tag

802.1Q

Original or Port

Default VLAN Tag

Transparent Stacked VLAN Tag

1 Subscriber per

LAN port

Dedicated Shared

802.1Q

Original or Port

Default VLAN Tag

365-372-300

Issue 8.0 September 2006

A - 1 1 3

Ethernet Service Configurations

: Ethernet/SAN

The following table shows the typical Ethernet service configurations.

Table A-10 Typical Ethernet Service Configurations

Service

Private Line

Private

LAN

Virtual

Private

LAN

Virtual

Private Line

Service

Protection

SONET

Spanning

Tree

Ring

Type

Yes

Not

Allowed

UPSR

Cross-Connect

Type

1wayPR, 1way

UPSR 1way unswitched

BLSR 1way

No Yes

BLSR w/

NUT

1way unswitched

UPSR 1way unswitched

BLSR w/

NUT

1way unswitched

UPSR 1way unswitched

Tagging

Mode

Private Line

Transparent or 802.1Q

Yes

BLSR w/

NUT

1way unswitched

UPSR 1wayPR, 1way

UPSR 1way unswitched

BLSR 1way

BLSR w/

NUT

1way unswitched

802.1Q

Transparent or 802.1Q

A - 1 1 4

365-372-300

Issue 8.0 September 2006

Ethernet Service Configurations

: Ethernet/SAN

Private line service

Private line service is a point-to-point service with two dedicated LAN ports and dedicated SONET capacity. Because it is a point-to-point service, spanning tree protection is not used. Protection is provided at the SONET layer only.

Ethernet private line service can be provided over SONET UPSRs. The following figure shows an example of private line service with protection provided by a SONET UPSR.

Figure A-38 Ethernet Private Line Service over Protected UPSR

Ethernet

Switch

V4 V3 V2 V1

Main 2 Main 1

Main 1

Main 2

Ethernet

Switch

Ethernet

Switch

Main 2 Main1

Main 2 Main 1

V1 V2 V3 V4

Ethernet

Switch

Type of Ring

- UPSR

Type of Cross-Connection

- 2Way PR

Transport Protection

- UPSR Switching

= Traffic transmitted clockwise around the ring

= Traffic transmitted counter-clockwise around the ring

MA-DMX-367

365-372-300

Issue 8.0 September 2006

A - 1 1 5

Ethernet Service Configurations

: Ethernet/SAN

The following figure shows two independent unprotected links.

External or subscriber equipment can use these links to either provide two paths between equipment or separate paths for link aggregation.

Figure A-39 Dual Unprotected Ethernet Private Line over UPSR or

BLSR

Ethernet

Switch

V4 V3 V2 V1

Main 2 Main 1

External or

Subscriber

Equipment

Ethernet

Switch

Type of Ring

- UPSR or BLSR

Type of Cross-Connection

- Multipoint (UPSR and BLSR)

Transport Protection

- Externally Protected

Main 1

Main 2

Independent

Link (Services)

Main 1 Main 2

= Working Channels

V1 V2 V3 V4

Ethernet

Switch

L1 L2

External or

Subscriber

Equipment

MA-DMX-368

A - 1 1 6

365-372-300

Issue 8.0 September 2006

Ethernet Service Configurations

Private LAN, Virtual Private

LAN, and Virtual Private

Line services

: Ethernet/SAN

In Private LAN service, LAN ports and SONET capacity are dedicated to one subscriber. In Virtual Private LAN service, several subscribers share SONET capacity and can share LAN ports. Traffic is segregated by its VLAN/port TAG. Virtual Private Line service is subset of

Virtual Private LAN service, where the subscriber is given a point-to-point service with dedicated LAN ports.

Protection can be provided either by packet layer spanning tree protocols, by the SONET layer, or by both. The network could also use tributaries provisioned for nonpreemptible unprotected traffic (NUT).

If NUT is provisioned, the Ethernet traffic is protected by the spanning tree protocol.

The following figure shows multipoint cross-connections used to form a packet ring.

Figure A-40 Spanning Tree Protected Private LAN and Virtual

Private LAN Services

Ethernet

Switch

V4 V3 V2 V1

365-372-300

Issue 8.0 September 2006

Main 2 Main 1

Main 1

Main 2

Ethernet

Switch

Ethernet

Switch

V1 Main 2

Main 1

Extra traffic used for BLSR (blue)

Main 1 Main 2

Type of Ring

- UPSR or BLSR

Type of Cross-Connection

- Multipoint (UPSR and BLSR)

Transport Protection

- Spanning Tree

V1 V2 V3 V4

Ethernet

Switch

L1 L2

MA-DMX-371

A spanning tree is required to eliminate Ethernet forwarding loops. The

Ethernet traffic is protected by the spanning tree. In UPSRs, an additional packet ring could be supported on VCG 3 and VCG 4 protected by it's spanning tree.

A - 1 1 7

Ethernet Service Configurations

: Ethernet/SAN

Virtual Private Line LNW70

The figure below depicts the traffic flow of multiple virtual private lines in transparent mode over shared media (optical fiber). For more information on private lines in transparent mode, refer to the

Transparent mode

section above. For information on Boundary and

Interior port demarcation, refer to the section

Boundary versus Interior

Ports

above.

Figure A-41 Virtual Private Line with LNW70

Trafmgmtmd=COSPORT

VLANid=55

PBX

VoIP

LAN

Foundry

Customer 4

Customer 1

- Trafmgmtmd=PORT

VLANid=32

Metropolis

DMX

VLANid=66

Customer 3

Trafmgmtmd=PORT

Metropolis

DMX

OC12/48/192

UPSR/BLSR

Metropolis

DMX

Boundry Port

Interior Port

VLANid=55

Trafmgmtmd=COSPORT

Metropolis

DMX

VLANid=32

Customer 1

- Trafmgmtmd=PORT

Foundry

Customer 4

PBX

VoIP

LAN

DMX = Metropolis

DMX Access Multiplexer

JK-E-11.eps

VLANid=66

Customer 3

Trafmgmtmd=PORT

A - 1 1 8

365-372-300

Issue 8.0 September 2006

Ethernet Service Configurations

LAN Service with LNW70

: Ethernet/SAN

The figure below depicts the traffic flow of multiple VLANs over shared media (optical fiber). For more information on VLANs, refer to the

Private LAN, Virtual Private LAN, and Virtual Private Line services section above. For information on Boundary and Interior port demarcation, refer to the section

Boundary versus Interior Ports

above.

Figure A-42 LAN Service with LNW70

VLANid=55

PBX

VoIP

LAN

Foundry

Customer 4-

Trafmgmtmd=COSPORT

Customer 2 - Trafmgmtmd=PORT

VLANid=27

Router

Customer 1

Customer 2

Customer 3

VLANid=32

VLANid=27

VLANid=66

Metropolis

DMX

Metropolis

DMX

OC12/48/192

UPSR/BLSR

Metropolis

DMX

Trafmgmtmd=TAGPORT

Boundry Port

Interior Port

VLANid=55

Trafmgmtmd=COSPORT

Metropolis

DMX

VLANid=32

Customer 1 - Trafmgmtmd=PORT

Foundry

Customer 4

PBX

VoIP

LAN

DMX = Metropolis DMX Access Multiplexer

JK-E-11.eps

VLANid=66

Customer 3

Trafmgmtmd=PORT

365-372-300

Issue 8.0 September 2006

A - 1 1 9

Ethernet Service Configurations

: Ethernet/SAN

RPR Ethernet Transport with LNW78

The figure below shows a ring of DMX nodes supporting an RPR ring.

The center node has an RPR LNW78 card in slot A1 and OC-3/12/48 cards in slots B1 and B2. The LNW78 card sets up a RPR instance, connecting LAN ports on the LNW78 to a port on a card in the MAIN slot of the shelf. The other VCG port in the LNW78 is able to connect to the other MAIN slot, or to another function slot in the same shelf.

This is accomplished by way of a hairpin cross-connect. In the figure below, the hairpin cross-connect is between the LNW78 in A1 and another LNW78 card in function group B. Dotted lines are used to show the west bound port could be connected to the MAIN card or to

another function group via a hairpin cross-connect. See “Direction

Reversal in UPSRs Joined via RPR and Daisy Chained RPR Nodes within One NE” (A-121) for information on RPR over joined SONET

rings.

Figure A-43 RPR Packet Ring and Hairpin to Subtending Ring with LNW78

Metropolis

DMX

West

East

OC-12/48/192 UPSR/BLSR

West

Metropolis

DMX

East

DMX

West

LNW78 RPR Pack

East

West

B1 B2

1000BASE-X

RPR

East

West

JK-E-18.eps

A - 1 2 0

365-372-300

Issue 8.0 September 2006

Ethernet Service Configurations

: Ethernet/SAN

The figure below demonstrates 2 separate RPR characteristics. The top portion of the figure is meant to show how the direction of traffic on an

RPR ring travelling between different nodes can be reversed if necessary. In the course of connecting multiple SONET rings within a single RPR ring over multiple SONET rings, the direction of traffic flow may need to be corrected. Just as with SONET rings, RPR requires that east facing nodes always be connected to west facing nodes and vice versa. If the direction of traffic needs to be switched at some point in the

RPR ring, it can be done with 1WAY cross-connections by connecting

F1 to V2 instead of the usual F1 to V1, etc.

Figure A-44 Direction Reversal in UPSRs Joined via RPR and

Daisy Chained RPR Nodes within One NE

M1= MAIN 1

M2= MAIN 2

F1= Function Group 1

F2= Function Group 2

V2 V1

365-372-300

Issue 8.0 September 2006

JK-E-19.eps

The bottom portion of the figure above demonstrates the ability of a

DMX equipped with more than one LNW78 to daisy chain multiple cards in the same shelf on one RPR ring. In the figure above, slot C1 and D1 both contain LNW78 cards. Either an OC-48 or OC-192 card

A - 1 2 1

Ethernet Service Configurations

: Ethernet/SAN

would be is slots M1 and M2. The RPR ring is on the UPSR ring of M1 and M2. M1 connects to V1 in C1 as usual. V2 however connects to V1 in D1. V2 in D1 connects to M2 to complete the ring. In this way 2

RPR nodes are instantiated in one DMX shelf, making 12 LAN ports available to the RPR ring.

With this capability/configuration, the RPR ring hosted by the LNW78 in slot C1 is connected to the RPR ring being hosted by slot D1 and both are connected to the main SONET ring being hosted by the

OC-48/192 packs in the main slots.

A - 1 2 2

365-372-300

Issue 8.0 September 2006

Ethernet Service Configurations

: Ethernet/SAN

RPR interconnect and LAN port aggregation with

LNW78 EoS functionality

Figure A-45 RPR Packet Ring interconnect via EOS VCG with

LNW78 (multi-node interconnect)

RPR Ring 1

Metropolis

DMX

LNW78

Metropolis

DMX

LNW78

OC-n

LNW78

Metropolis

DMX

LNW78

Local Hairpin – LNW78 to

Optical Port Unit

OC-n

Optical Shelf

Interconnect

Local Hairpin – LNW78 to

Optical Port Unit

Metropolis

DMX

LNW78

OC-n

Metropolis

DMX

LNW78

RPR Ring 2

Metropolis

DMX

LNW78

365-372-300

Issue 8.0 September 2006

MA-DMXAPG-051

A - 1 2 3

Ethernet Service Configurations

: Ethernet/SAN

Metropolis

DMX

LNW78

Figure A-46 RPR Packet Ring interconnect via EOS VCG with

LNW78 (single-node interconnect)

RPR Ring 1

Metropolis

DMX

LNW78

OC-n

LNW78

Local Hairpin –

LNW78 to LNW78

Metropolis

DMX

LNW78

Metropolis

DMX

LNW78

OC-n

Metropolis

DMX

LNW78

RPR Ring 2

DMX = Metropolis DMX Access Multiplexer

MA-DMXAPG-052

A - 1 2 4

365-372-300

Issue 8.0 September 2006

Ethernet Service Configurations

: Ethernet/SAN

The configuration pictured below functions in a similar fashion to

TransMUX hub-and-spoke application, with EoS ports terminating services originating on other Ethernet packs. Typically these services are in NOTAG mode. The EoS ports are configured as LAN ports with

trafmgmtmd set to PORT or COSPORT and vlantagmd set to 802.1Q or Transparent mode. The received remote traffic has no added tags, and no CoS or drop precedence marking. Therefore it is received just as it originated at the remote LAN port. Tags are added at the EoS port ingress according to the vlantagmd command. This traffic is typically added to an RPR ring destined for NE-local LAN ports at the hub node.

Figure A-47 Remote LAN port aggregation/RPR interconnect

SONET

6 Eos VCG

With Rate Controls

RPR Ring

Metropolis

DMX

plore

VLNC15

Metropolis

DMX

plore

VLNC15

Metropolis

DMX

LNW70

Metropolis

DMX

tend

LNW74

RPR VCG

LNW78

RPR Port Unit

RPR VCG

Metropolis

DMX

tend

LNW74

DMX

plore

= Metropolis

DMX

plore

Access Multiplexer

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

LNW78

RPR Port Unit

LNW78

RPR Port Unit

LNW78

RPR Port Unit

MA-DMXAPG-049

365-372-300

Issue 8.0 September 2006

A - 1 2 5

Ethernet Service Configurations

: Ethernet/SAN

The NE-local LAN ports aggregation/interconnect configuration listed below functions similar to the Remote LAN Ports configuration described above except that the connections to Ethernet pack(s) providing LAN ports is via backplane hairpin(s).

Figure A-48 NE-local LAN port aggregation/interconnect

MAIN MAIN

Aggregated Traffic

From a SW Port Card

RPR VCG

EoS VCG

OC-3/12/48

LNW78 LNW74 LNW70

Local LNW78 Ports

Remote Private Line via

Optical Ring

OC-n

Local 10/100

Ports

Local 100/1000

Mbps Ports

Additional Local LAN

Ports to RPR

MA-DMXAPG-050

A - 1 2 6

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

SONET-Based Distance Extensions for

ESCON/FICON/Fibre-Channel Services

Overview

This section details the functionality of SONET-based SAN distance extension supported by the LNW73. For other information on the functionality of the LNW73, refer to the following sections within this

appendix: “Ethernet/SAN Circuit Packs” (A-8) , and

“Differential

Delay Buffers” (A-34) .

ESCON Design Guidelines

ESCON services enter DMX or DMXtend through ESCON PTM attached to LNW73 plugin circuit and are routed out OC48/192

SONET interfaces from SONET plugins (in slot main-1 (and main-2, if protection is desired)). The SONET signal can be routed through any number of intermediate SONET systems (including none) and terminates into another DMX or DMXtend to provide a network transport of ESCON services. A LNW73 may be placed in slots fn-a-1,fn-b-1,fn-c-1, fn-d-1 or growth-1 (5 slots) for DMX and in slots fn-d-1 and growth-1 (2 slots) for DMXtend. Up to 4 ESCON services may be provided in a single LNW73 plugin, each service requiring 4

STS-1 bandwidth reserved in the SONET domain. A DMX/OC48 system can provide 12 ESCON services (limited by SONET bandwidth).

A DMX/OC192 system can provide 20 ESCON services (limited by the number of slots that may be equipped with LNW73) A

DMXtend/OC48 system may provide 8 ESCON services (limited by the number of slots that may be equipped with LNW73).

Reliability/Line and Pack Protection Options

To protect against SONET network failures and main pack failures,

DMX can be equipped with redundant circuit packs in both main slots and can be provisioned for UPSR or BLSR protection. To protect against SONET network failures and main pack failures, DMXtend can be equipped with redundant circuit packs in both main slots and be provisioned for UPSR protection. Using SONET protection significantly increases the reliability of individual end-to-end ESCON services.

365-372-300

Issue 8.0 September 2006

A - 1 2 7

A - 1 2 8

: Ethernet/SAN

Circuit Pack Equipage and Provisioning

Each LNW73 used must be set to select the pack type of ESCON (see

ED-EQPT). Each port to be used must be equipped with a Lucent specified ESCON Pluggable Transmission Module (PTM). A PTM is similar in functionality to a GBIC pluggable unit. If a Virtual

Concatenated (VCAT) signal format is desired, the

ED-DPORT-DATA command is used to select it.

Circuit Bandwidth Choices

A full rate ESCON service may be provisioned as a SONET STS-1-4v

(VCAT), STS-3c-2v(VCAT) or a STS-12c Contiguously Concatenated

(CCAT). The most bandwidth efficient is STS-1-4v.

Interface Specifications to ESCON interfaces

DMX/DMXtend use standards compatible PTM modules. Refer to

Chapter 10 for optical specification, loss budget, connector and fiber type requirements.

Distance Limitations/Transmission Delay Engineering

Distance between the ESCON equipment and the DMX/DMXtend are typically limited by the interface link specification of the ESCON interface.

The total distance allowed including the SONET extension is typical a function of the delay requirements of the ESCON application.

Synchronous ESCON applications typically suffer performance droop if the application is subjected to more than 100 microseconds of one way transmission delay (the equivalent of delay through 20 km of fiber). For planning purposes, each DMX adds the equivalent 25 microseconds or 5 km of fiber. Therefore, synchronous ESCON applications would suffer droop if the total actual fiber distance (adding the ESCON to DMX and DMX to DMX links) is more than 10 km.

Asynchronous ESCON applications are much more tolerant to transmission delay, typically able to function at delays of 1000 microseconds (200 km) or longer. Each DMX/DMXtend or other

SONET system in the path of such a network would add the equivalent of 5 km of fiber.

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

Full-rate FICON/FC Design

Guidelines

FICON/FC services enter DMX or DMXtend through FICON/FC PTM attached to LNW73 plugin circuit is routed out OC48/192 SONET interfaces from SONET plugin (in slot main-1 (and main-2, if protection is desired)).

The SONET signal can be routed through any number of intermediate

SONET systems (including zero) and terminates into another DMX or

DMXtend to provide a network transport of a FC/FICON service.

A LNW73 may be placed in slots fn-a-1,fn-b-1,fn-c-1, fn-d-1 or growth-1 (5 slots) for DMX and in slots fn-d-1 and growth-1 (2 slots) for DMXtend.

Up to 2 full rate 1G FICON/FC services (or one 2G FICON/FC service) may be provided in a single LNW73 circuit pack, each service requiring 19 STS-1 or 6 STS-3c bandwidth units reserved in the

SONET domain (37 STS-1 or 12 STS-3c for 2G FICON/FC).

So, when operating in asynchronous Fibre Channel (FC) mode, 2 ports are available at 2Gbps FC, or 4 ports at 1Gbps FC, or 1 port at 2Gbps

FC and 2 ports of 1Gbps FC. When operating in synchronous FC mode,

1 port is available at 2Gbps FC, or 2 at 1Gbps FC.

A DMX/OC48 system can provide 2 full rate FICON/FC 1G services

(limited by SONET bandwidth).

A DMX/OC192 system can provide 10 FICON/FC 1G services

(limited by the number of slots that may be equipped with LNW73).

A DMXtend/OC48 system may provide 2 full rate 1G FICON/FC services (limited by SONET bandwidth).

Buffer-to-buffer credits are handled exclusively by FICON/FC switches/devices.

Reliability/Line and Pack Protection Options

To protect against SONET network failures and main pack failures,

DMX can be equipped redundant circuit packs in both main slots and be provisioned for UPSR or BLSR protection.

To protect against SONET network failures and main pack failures,

DMXtend can be equipped SONET plugins in both main slots and be provisioned for UPSR SONET Protection.

Using SONET Protection dramatically increases the reliability of end to end FICON/FC services.

365-372-300

Issue 8.0 September 2006

A - 1 2 9

A - 1 3 0

: Ethernet/SAN

Circuit Pack Equipage and Provisioning

Each LNW73 used must be set to select the pack type of FICON/FC

(see ED-EQPT). Each port to be used must be equipped with a Lucent specified FC/FICON Pluggable PTM. A PTM is similar in functionality to a GBIC pluggable unit. If a VCAT signal format is desired, the ED-DPORT-DATA command is used to select it.

Circuit Bandwidth Choices

A full rate 1G FICON/FC service may be provisioned as a SONET

STS-1-19v (VCAT), STS-3c-6v(VCAT). The most bandwidth efficient is STS-3c-6v. A full rate 2G FICON/FC service may be provisioned as a SONET STS-1-37v (VCAT), STS-3c-12v (VCAT). The most bandwidth efficient is STS-3c-12v.

Interface Specifications to FICON/FC interfaces

DMX/DMXtend use standards compatible PTMs. The same PTM works for both FICON and FC and both 1G and 2G. Refer to Chapter

10 for optical specification, loss budget, connector and fiber type requirements.

Distance Limitations/Transmission Delay Engineering

Distance between the FICON/FC equipment and the DMX/DMXtend are typically limited by the interface link specification of the

FICON/FC interface.

The total distance allowed including the SONET extension is typically a function of the delay requirements of the FICON/FC application.

Synchronous FICON/FC applications typically suffer performance droop if the application is subjected to more than 600 microseconds of one way transmission delay (the equivalent of delay through 120 km of fiber). Refer to your particular client equipment engineering rules for distance limitations. For planning purposes, each DMX adds the equivalent 25 microseconds or 5 km of fiber.

Asynchronous FICON/FC applications are much more tolerant to transmission delay, typically able to function at delays of 1000 microseconds (200 km) or longer. Many newer FC switches today offer extended buffer credits for asynchronous applications that allow up to

3600 microseconds of delay without performance droop. Each

DMX/DMXtend or other SONET system in the path of such a network would add the equivalent of 5 km of fiber.

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

FC/FICON Services-Extended Distances- BB Credits managed in

DMX/DMXtend

To extend asynchronous FICON/FC applications beyond the buffer to buffer credit limits of the attached FC Switches, DMX and DMXtend can be provisioned to manage the BB Credits and eliminate performance droop related to insufficient BB credit across the network.

This implementation is based on the ITU G.7041 and T11

FC-BB-3_GFPT standards work and provides sufficient credits for full performance at 2500 km for 2G services in R5.1.1.

To use this mode, the gfptype (in the ED-DPORT-DATA command) must be provisioned to ASYNC-FC (even if it is a FICON service).

Buffer credits are automatically adjusted within DMX/DMXtend and no additional provisioning required. Attached FICON/FC devices should be provisioned to use for R_RDY flow control (as opposed to proprietary Inter-Switch Link (ISL) flow control schemes.

Illustrative examples of some FC switch configurations are provided below.

EMC Certification

To achieve EMC certification, DMX has been tested with various

FC/FICON switches used with EMC storage equipment. Presently,

DMX has completed testing with the Brocade Silkworm 3800 and

2250, the McData Sphereon 4500, and Cisco MDS 9120 and MDS

9126. This testing has yielded some simple guidelines that need to be followed to ensure smooth interworking between DMX and the

FC/FICON switches listed above.

Refer to the sections below for these SAN interworking guidelines.

365-372-300

Issue 8.0 September 2006

A - 1 3 1

: Ethernet/SAN

General FC/FICON

Equipment port configuration for connection to

DMX/DMXtend

Please use the following guidelines to ensure interoperability between

FC/FICON equipment and DMX/DMXtend.

To assure minimal link start up and recovery times, the following configurations are recommended for all ports attached to

DMX/DMXtend:

• Configure port speed to match application: I.e. use 1G or 2G mode instead of auto-negotiate mode.

• Configure ports to not waste time trying to determine if DMX is arbitrated loop port type

To use buffer credits in DMX/DMXtend when gfptype is set to

async-FC, configure ports to use R_RDY mode buffer credit management instead of proprietary link buffer credit management.

If compression is desired on DMX/DMXtend and gfptype is set to

async-FC, set the number of link buffer credits to 8 or less, otherwise the operational state of compression will stay disabled.

Brocade interworking examples

Please use the following guidelines to ensure interoperability between the specified Brocade equipment and DMX/DMXtend.

Brocade Silkworm 3800:

Perform the following tasks on all ports connected to the

DMX/DMXtend:

• Through the CLI, use the portcfgSPEED {port num}, {1 or 2, not

• Then use the portcfgGPORT {portnum}, {1, not 0}

In addition, to use buffer credits on DMX/DMXtend when gfptype is set to async-FC, use portcfgISLMODE {portnum}, {1, not 0}.

To use compression on DMX/DMXtend when gfptype is set to

async-FC, use switchdisable, then use the configure command to set

fabric.ops.BBCredit to 8 or less.

Brocade Silkworm 2250:

Perform the following tasks on all ports connected to the

DMX/DMXtend:

• Through the CLI, use the portcfgSPEED {port num}, {1 or 2, not

• Then use the portcfgGPORT {portnum}, {1, not 0}

A - 1 3 2

365-372-300

Issue 8.0 September 2006

: Ethernet/SAN

In addition, to use buffer credits on DMX/DMXtend when gfptype is set to async-FC, use switchdisable, then use the configure command to set fabric.ops.longdistance=1

To use compression on DMX/DMXtend when gfptype is set to

async-FC, use switchdisable, then use the configure command to set

fabric.ops.BBCredit to 8 or less.

Cisco MDS 9120 or MDS

9216 interworking examples

Please use the following guidelines to ensure interoperability between the Cisco MDS 9120 or MDS 9216 equipment and DMX/DMXtend.

Perform the following tasks on all ports connected to the

DMX/DMXtend:

• Through the GUI, click on FC port, set admin Speed to 1Gb or

2Gb not auto

• Through the GUI, click on FC port, set admin Mode to E or TE, not auto

In addition, to use buffer credits on DMX/DMXtend when gfptype is set to async-FC, it is important to note that Cisco uses ISL mode as

R_RDY mode by default.

To use compression on DMX/DMXtend when gfptype is set to

async-FC, through the GUI, click on FC port, then click on BBCredit and then set admin BBCredit to 8 or less.

MC Data Sphereon 4500 interworking examples

Please use the following guidelines to ensure interoperability between the MC Data Sphereon 4500 equipment and DMX/DMXtend.

Perform the following tasks on all ports connected to the

DMX/DMXtend:

• Through the GUI, click on Configure, then click on ports, on the appropriate ports, set Speed to 1Gb/sec or 2Gb/sec

• Through the GUI, click on Configure, then click on ports, on the appropriate ports, set Type to E port

In addition, to use buffer credits on DMX/DMXtend when gfptype is set to async-FC, it is important to note that Sphereon uses ISL mode as R_RDY mode by default.

To use compression on DMX/DMXtend when gfptype is set to

async-FC, set any port numbered "4" or higher to use 5 credits (ports

0-3 use 12 credits).

365-372-300

Issue 8.0 September 2006

A - 1 3 3

: Ethernet/SAN

A - 1 3 4

365-372-300

Issue 8.0 September 2006

B: Performance Monitoring

Overview

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Purpose

This section lists and describes performance monitoring parameters, data storage, thresholds, and TCA transmission.

365-372-300

Issue 8.0 September 2006

B - 1

Overview

: Performance Monitoring

Contents

The following performance monitoring information is included in this section:

Introduction to Performance Monitoring

OC-N Performance Parameters

EC-1 Performance Parameters

E1 Performance Parameters

STS-N Performance Parameters

VT1.5 Performance Parameters

VC-12 Performance Parameters

DS3 Performance Monitoring Parameters

DS1 Performance Monitoring Parameters

Ethernet/SAN Performance Monitoring

Parameters

SNMP Parameters and Traps

B - 2

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

Introduction to Performance Monitoring

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Definition

Performance monitoring (PM) is the in-service, non-intrusive monitoring and reporting of transmission quality.

PM helps proactive maintenance detect and correct degrading signal conditions that are not yet severe enough to initiate protection switching or alarming.

Proactive maintenance

Proactive maintenance is the process of detecting degrading conditions that are indicative of an impending hard or soft failure, but not severe enough to initiate alarming.

Data registers

Reactive maintenance

Hard and soft failures result in reactive maintenance.

The following table lists the data registers that are provided for all performance monitoring parameters.

Table B-1 Data Registers

15-Minute Registers

One current

One previous

31 most recent

1-Day (24-Hour) Registers

One current

One previous

DMX retrieves and reports the contents of any parameter storage register. The WaveStar

CIT may be used to initialize (set to zero) the current 15-minute and/or current 1-day registers locally or remotely.

This capability enables the user to verify that a repair to a failed facility was successful.

The following events also initialize the data registers to zero:

• System reset is performed

• Performance monitoring is restarted (PST parameter fluctuates between IS and AUTO or NMON)

• INIT-REG (Initialize Register) TL1 command is executed

• Facility or terminal loopback is removed

• Transmission test is completed.

365-372-300

Issue 8.0 September 2006

B - 3

Introduction to Performance Monitoring

: Performance Monitoring

How registers are updated

The two registers (15 min. and day registers) are updated in the following manners:

15-minute registers

The registers are updated with a push-down methodology. At 0, 15, 30, and 45 minutes on the system clock, the contents of the 30th recent register is moved to the 31 st

recent register. The contents of each of the other recent registers are moved to the next higher register. The contents of the previous register are moved to the first recent register.

The contents of the current register are moved to the previous register.

The new measured value is placed in the current register.

Day registers

At day boundaries (midnight as defined by the local time/date function), the current day register is written to the previous day storage register and the current day register is set to zero. The day boundary is midnight by default, but may be provisioned to a different time.

PM scheduling

Performance monitoring can be scheduled to provide quarter hour and daily reports beginning at different time intervals. In order to schedule

PM reports, PM messaging must be enabled and you must use the

WaveStar

CIT TL1 cut-through mode or the TL1 Command Builder.

PM cannot be scheduled via the WaveStar

CIT Graphical interface.

Enabling/disabling performance monitoring

Performance monitoring can be enabled/disabled for DS1 ports, DS3 ports, E1 ports, EC-1 ports, STS-n paths, VT1.5 paths, VC-12 paths, and OC-N lines.

DS1 ports

Performance monitoring is enabled/disabled on a DS1 port basis using the Primary State (PST) parameter of the

Configuration > Provision

Equipment

command.

When the PST parameter is provisioned as AUTO and a valid signal

(non DS1 LOS) is detected, the PST parameter automatically transitions to the IS (in service) state. This initializes the data registers and enables DS1 line and path performance monitoring on the port.

When the PST parameter is provisioned as NMON or AUTO (with no valid input signal detected), DS1 line and path performance monitoring is disabled on the port.

B - 4

365-372-300

Issue 8.0 September 2006

Introduction to Performance Monitoring

: Performance Monitoring

On the TransMUX DS1 interfaces, "Receives a good signal" is defined as absence of

DS3: LOS, LOF, AIS and absence of DS1

LOS.

365-372-300

Issue 8.0 September 2006

B - 5

Introduction to Performance Monitoring

B - 6

: Performance Monitoring

DS3 ports

Performance monitoring is enabled/disabled on a DS3 port basis using the Primary State (PST) parameter of the

Configuration > Provision

Equipment

command.

When the PST parameter is provisioned as AUTO and a valid signal

(non DS3 LOS) is detected, the PST parameter automatically transitions to the IS (in service) state. This initializes the data registers and enables DS3 line and path performance monitoring on the port.

When the PST parameter is provisioned as NMON or AUTO (with no valid input signal detected), DS3 line and path performance monitoring is disabled on the port.

E1 ports

Performance monitoring is enabled/disabled on a E1 port basis using the Primary State (PST) parameter of the

Configuration > Provision

Equipment

command.

When the PST parameter is provisioned as AUTO and a valid signal

(non E1 LOS) is detected, the PST parameter automatically transitions to the IS (in service) state. This initializes the data registers and enables

E1 line and path performance monitoring on the port.

When the PST parameter is provisioned as NMON or AUTO (with no valid input signal detected), E1 line and path performance monitoring is disabled on the port.

EC-1 ports

Performance monitoring is enabled/disabled on a EC-1 port basis using the Primary State (PST) parameter of the

Configuration > Provision

Equipment

command.

When the PST parameter is provisioned as AUTO and a valid signal

(non LOS) is detected, the PST parameter automatically transitions to the IS (in service) state. This initializes the data registers and enables

EC-1 line performance monitoring on the port.

When the PST parameter is provisioned as NMON or AUTO (with no valid input signal detected), EC-1 line performance monitoring is disabled on the port.

STS-n paths

Performance monitoring is enabled/disabled on terminated STS-n paths using the Primary State (PST) parameter of the

Configuration >

Provision Equipment

command.

365-372-300

Issue 8.0 September 2006

Introduction to Performance Monitoring

: Performance Monitoring

When the PST parameter is provisioned as AUTO and a valid signal

(non LOP-P, SF, UNEQ-P, or AIS-P) is detected, the PST parameter automatically transitions to the IS (in service) state. This initializes the data registers and enables terminated STS-n path performance monitoring.

When the PST parameter is provisioned as NMON or AUTO (with no valid input signal detected), terminated STS-n path performance monitoring is disabled.

Intermediate STS-n path performance monitoring is always enabled on pass through cross-connections.

VT1.5 paths

Performance monitoring is enabled/disabled on terminated VT1.5 paths using the Primary State (PST) parameter of the

Configuration >

Provision Equipment

command.

When the PST parameter is provisioned as AUTO and a valid signal

(non AIS-V, LOP-V, UNEQ-V) is detected, the PST parameter automatically transitions to the IS (in service) state. This initializes the data registers and enables terminated VT1.5 path performance monitoring.

When the PST parameter is provisioned as NMON or AUTO (with no valid input signal detected), terminated VT1.5 path performance monitoring is disabled.

VC-12 paths

Performance monitoring is enabled/disabled on terminated VC-12 paths using the Primary State (PST) parameter of the

Configuration >

Provision Equipment

command.

When the PST parameter is provisioned as AUTO and a valid signal

(non AIS-V, LOP-V, UNEQ-V) is detected, the PST parameter automatically transitions to the IS (in service) state. This initializes the data registers and enables terminated VC-12 path performance monitoring.

When the PST parameter is provisioned as NMON or AUTO (with no valid input signal detected), terminated VC-12 path performance monitoring is disabled.

365-372-300

Issue 8.0 September 2006

B - 7

Introduction to Performance Monitoring

: Performance Monitoring

Low Speed OC-n lines

Performance monitoring is enabled/disabled on low speed OC-n lines using the Primary State (PST) parameter of the

Configuration >

Provision Equipment

command.

When the PST parameter is provisioned as AUTO and a valid signal

(non LOS) is detected, the PST parameter automatically transitions to the IS (in service) state. This initializes the data registers and enables

OC-n section and line performance monitoring.

When the PST parameter is provisioned as NMON or AUTO (with no valid input signal detected), OC-n section and line performance monitoring is disabled.

For more information about the

Configuration > Provision Equipment

command, refer to the WaveStar

CIT on-line help.

High Speed OC-n lines

Performance monitoring is always enabled on high speed OC-n lines when a circuit pack is installed and a valid (non LOS) signal detected.

B - 8

365-372-300

Issue 8.0 September 2006

Introduction to Performance Monitoring

: Performance Monitoring

PM during failed conditions

When a trouble condition is detected, DMX stops accumulating PM parameters affected by that failure. PM parameters are inhibited during unavailable time per GR-253-CORE. All unaffected performance parameters continue to accumulate during a trouble condition.

The following performance parameters are not inhibited during unavailable time.

• Severely Errored Frame Seconds (SEFS)

• Unavailable Seconds (UAS)

• Failure Counts (FC)

• Protection Switch Counts (PSC)

• Protection Switch Duration (PSD)

PM during loopbacks

When a loopback is established, DMX disables PM data collection on the associated line or path for the duration of the loopback. Any attempt to retrieve PM data on the looped back line or path is denied. When the loopback is removed, DMX initializes the data registers and restarts

PM data collection on the line or path.

PM during transmission tests

PM on extra traffic and nonpreemptible unprotected traffic (NUT)

Threshold crossing alerts

(TCAs)

When a transmission test is executed, DMX disables PM data collection on the associated port for the duration of the transmission test. Any attempt to retrieve PM data on the port is denied. When the transmission test completes, DMX initializes the data registers and restarts PM data collection on the port.

DMX supports performance monitoring on nonpreemptible unprotected traffic (NUT).

When the value of a current quarter-hour or the current day register meets or exceeds the corresponding provisioned threshold, DMX generates a threshold-crossing alert (TCA) that is entered into the performance monitoring exception report and reported to the OS through the TL1 interface.

In order to view autonomous TCAs, Event Messaging must be enabled.

365-372-300

Issue 8.0 September 2006

B - 9

Introduction to Performance Monitoring

: Performance Monitoring

Enabling/disabling TCA reporting

TL1 access

The TL1 interfaces should be used to derive full benefit from DMX’s performance monitoring capabilities. The full set of PM data stored by

DMX (TCAs and the contents of PM registers) is provided through the

TL1 interface.

TCA reporting can be enabled/disabled for DS1 ports, DS3 ports, E1 ports, EC-1 ports, STS-n paths, VT1.5 paths, VC-12 paths, and OC-N lines.

In order to disable TCAs set the threshold to zero or use the TCAMD parameter.

B - 1 0

DS1 ports

TCA reporting is available when a DS1 or TMUX circuit pack is installed, a valid signal is detected, and a cross-connection is established. TCA reporting is enabled/disabled on a DS1 port basis using the TCA Mode (TCAMD) parameter of the

Configuration >

Provision Equipment

command.

When the TCAMD parameter is provisioned as ENABLE, TCAs are reported for the DS1 line and path.

When the TCAMD parameter is provisioned as DISABLE, TCAs are not reported for the DS1 line and path.

The port primary state (PST) parameter must be IS (in service) for TCA reporting. If the port PST parameter is NMON or AUTO, performance monitoring and TCA reporting are disabled.

DS3 ports

DS3 line TCA reporting is available when a DS3 circuit pack is installed. DS3 path TCA reporting is available when a DS3 circuit pack is installed, a valid signal is detected, and a cross-connection is established. TCA reporting is enabled/disabled on a DS3 port basis using the TCA Mode (TCAMD) parameter of the

Configuration >

Provision Equipment

command.

When the TCAMD parameter is provisioned as ENABLE, TCAs are reported for the DS3 line and path.

When the TCAMD parameter is provisioned as DISABLE, TCAs are not reported for the DS3 line and path.

The port primary state (PST) parameter must be IS (in service) for TCA reporting. If the port PST parameter is NMON or AUTO, performance monitoring and TCA reporting are disabled.

365-372-300

Issue 8.0 September 2006

Introduction to Performance Monitoring

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

E1 ports

TCA reporting is available when a E1 circuit pack is installed, a valid signal is detected, and a cross-connection is established. TCA reporting is enabled/disabled on a E1 port basis using the TCA Mode (TCAMD) parameter of the

Configuration > Provision Equipment

command.

When the TCAMD parameter is provisioned as ENABLE, TCAs are reported for the E1 line and path.

When the TCAMD parameter is provisioned as DISABLE, TCAs are not reported for the E1 line and path.

The port primary state (PST) parameter must be IS (in service) for TCA reporting. If the port PST parameter is NMON or AUTO, performance monitoring and TCA reporting are disabled.

EC-1 ports

EC-1 line TCA reporting is available when a circuit pack is installed.

TCA reporting is enabled/disabled on an EC-1 port basis using the

TCA Mode (TCAMD) parameter of the

Configuration > Provision

Equipment

command.

When the TCAMD parameter is provisioned as ENABLE, TCAs are reported for the EC-1 line.

When the TCAMD parameter is provisioned as DISABLE, TCAs are not reported for the EC-1 line.

The port primary state (PST) parameter must be IS (in service) for TCA reporting. If the PST parameter is NMON or AUTO, performance monitoring and TCA reporting are disabled.

STS-n paths

STS-n terminated and intermediate path TCA reporting is available when an STS-n cross-connection is established. TCA reporting is enabled/disabled on an STS-n path basis using the TCA Mode

(TCAMD) parameter of the

Configuration > Provision Equipment

command.

When the TCAMD parameter is provisioned as ENABLE, TCAs are reported for the STS-n terminated and intermediate path.

When the TCAMD parameter is provisioned as DISABLE, TCAs are not reported for the STS-n terminated and intermediate path.

The STS-n terminated path primary state (PST) parameter must be IS

(in service) for TCA reporting. If the PST parameter is NMON or

AUTO, performance monitoring and TCA reporting of the STS-n

B - 1 1

Introduction to Performance Monitoring

: Performance Monitoring

terminated path are disabled. (The PST parameter does not affect performance monitoring on STS-n intermediate paths.)

VT1.5 paths

VT1.5 terminated path TCA reporting is available when an STS/VT cross-connection is established. TCA reporting is enabled/disabled on a path basis using the TCA Mode (TCAMD) parameter of the

Configuration > Provision Equipment

command.

When the TCAMD parameter is provisioned as ENABLE, TCAs are reported for the VT1.5 terminated path.

When the TCAMD parameter is provisioned as DISABLE, TCAs are not reported for the VT1.5 terminated path.

The VT1.5 terminated path primary state (PST) parameter must be IS

(in service) for TCA reporting. If the PST parameter is NMON or

AUTO, performance monitoring and TCA reporting are disabled.

If/when an STS path is set to NMON, the constituent VT1.5 paths will also be set to NMON. The customer may then change the VT1.5 path primary state to AUTO in order to continue reporting TCAs.

VC-12 paths

VC-12 terminated path TCA reporting is available when an STS/VC cross-connection is established. TCA reporting is enabled/disabled on a path basis using the TCA Mode (TCAMD) parameter of the

Configuration > Provision Equipment

command.

When the TCAMD parameter is provisioned as ENABLE, TCAs are reported for the VC-12 terminated path.

When the TCAMD parameter is provisioned as DISABLE, TCAs are not reported for the VC-12 terminated path.

The VC-12 terminated path primary state (PST) parameter must be IS

(in service) for TCA reporting. If the PST parameter is NMON or

AUTO, performance monitoring and TCA reporting are disabled.

If/when an STS path is set to NMON, the constituent VC-12 paths will also be set to NMON. The customer may then change the VC-12 path primary state to AUTO in order to continue reporting TCAs.

B - 1 2

365-372-300

Issue 8.0 September 2006

Introduction to Performance Monitoring

: Performance Monitoring

OC-n lines

OC-n section and line TCA reporting is available when a circuit pack is installed. TCA reporting is enabled/disabled on an OC-n line basis using the TCA Mode (TCAMD) parameter of the

Configuration >

Provision Equipment

command.

When the TCAMD parameter is provisioned as ENABLE, TCAs are reported for the OC-n section and line.

When the TCAMD parameter is provisioned as DISABLE, TCAs are not reported for the OC-n section and line.

The line primary state (PST) parameter must be IS (in service) for TCA reporting of a low speed OC-n section or line. If the PST parameter of a low speed OC-n line is NMON or AUTO, performance monitoring and

TCA reporting are disabled. (The PST parameter of high speed OC-n lines is not user provisionable.)

Provisioning TCA parameter thresholds

Retrieving TCAs

The current quarter-hour and current day thresholds for each parameter type are provisionable, on a per-shelf basis. If values other than the defaults are used, only one value for each parameter type needs to be set for each signal.

Provisioning an individual performance monitoring parameter threshold to zero (0) disables reporting the TCAs for that parameter.

For more information about provision performance monitoring thresholds refer to the WaveStar

CIT on-line help and the DMX User

Operations Guide (UOG).

All TCAs are retrievable either locally or remotely via the WaveStar

CIT. If provisioned for autonomous TCA reporting, the message-based operations system interface can communicate TCA reports to the operations centers.

365-372-300

Issue 8.0 September 2006

B - 1 3

: Performance Monitoring

OC-N Performance Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

This section describes the performance monitoring parameters that are applicable to SONET OC-N signals.

Monitored parameters

The following table lists the SONET OC-N section and line performance parameters that DMX monitors, including the default and ranges for the 15-minute and 1-day (24-hour) registers.

Table B-2 SONET OC-N Performance Parameters

Facility

OC-N Section

OC-192 Section

OC-48 Section

OC-12 Section

OC-3 Section

OC-192 Line

OC-48 Line

OC-12 Line

OC-3 Line

15-Min

Measured Provisionable Parameter

Default

Range

(Note)

Section Errored Seconds (ESS)

SE Frame Seconds (SEFS/SEFS-S)

0-900

1-Day

Default

Range

(Note)

0-65535

Severely Errored Seconds (SESS/LESS-S) 30

Coding Violations (CV-L) 8960

0-900

0-16383

86016

0-65535

0-1048575

Coding Violations (CV-L)

Coding Violations (CV-L), CV-L FE

2240

560

140

0-16383

21504

5376

0-1048575

0-16383 1344 0-1048575

8960 0-16383 86016 0-1048575

Coding Violations (CV-L), CV-L FE

2240 0-16383 21504 0-1048575

560 0-16383 5376 0-1048575

140 0-16383 1344 0-1048575

B - 1 4

365-372-300

Issue 8.0 September 2006

OC-N Performance Parameters

: Performance Monitoring

Facility

OC-N Line

15-Min

Measured Provisionable Parameter

Default

Range

(Note)

Errored Seconds (ES-L)

Errored Seconds Far End (ES-L FE)

Far-End Line Failure Counts (FC-L)

Far-End Line Failure Counts Far End

(FC-L FE)

0-900

1-72

Severely Errored Seconds (SES-L)

Severely Errored Seconds Far End (SES-L

FE)

Unavailable Seconds (UAS-L)

Unavailable Seconds Far-End (UAS-L FE)

Protection Switch Count Line (PSC-L)

Protection Switch Count Protection

(PSC-P) (BLSR only)

Protection Switch Count Working

(PSC-W) (BLSR only)

Protection Switch Duration (PSC-D)

(BLSR Only)

0-900

0-63

1-Day

Default

Range

(Note)

900

0-65535

1-4095

0-65535

0-255

Pointer Justification Count Difference

(PJCDIFF-P)

Negative Pointer Justification Count

Detected (NPJC-PDET)

Positive Pointer Justification Count

Detected (PPJC-PDET)

Negative Pointer Justification Count

Generated (NPJC-PGEN)

0-1048575

5760

0-16777215

Positive Pointer Justification Count

Generated (PPJC-PGEN)

60 0-1048575 5760 0-16777215

Note: When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

OC-N section parameter

DMX monitors the following near end SONET section parameters for incoming (from the lightguide cross-connect) OC-N signals. The parameters are measured at the input of the OC-N OLIU circuit pack on the line side (also referred to as LGX side).

365-372-300

Issue 8.0 September 2006

B - 1 5

OC-N Performance Parameters

: Performance Monitoring

Coding violations (CV-S)

The Section Coding Violations (CV-S) parameter for each SONET section is monitored. The CV-S parameter is a count of BIP errors at the Section Layer (i.e., B1 errors). Up to eight Section BIP errors can be detected per STS-N frame, with each error incrementing the CV-S current second register.

Errored seconds (ES-S)

The Section Errored Seconds (ESS) parameter for each SONET section is monitored. The ESS parameter increments once for each second in which at least one Section Layer BIP error was detected or an SEF or

LOS defect was present.

Severely errored frame seconds (SEFS/SEFS-S)

The SEFS/SEFS-S parameter increments once for each second during which DMX detects one or more near end severely errored frame defects.

OC-N Section PM Report

Use the

Performance > Reports > OCn Section

command to obtain the

OC-N Section PM Report. For more information about the OC-N section parameter and the

Performance > Reports > OCn Section

command, refer to the WaveStar

CIT on-line help.

OC-N line parameters

DMX monitors the following near end SONET line parameters for incoming (from the lightguide cross-connect) OC-N signals. The parameters are measured at the input of the OC-N OLIU circuit pack on the OC-N line side (also referred to as LGX side).

Coding violations (CV-L)

The Near-End Line Coding Violation (CVL) parameter for each

SONET Line is monitored. The Near-End CVL parameter increments once for every occurrence of a BIP error detected at the Line layer (i.e. using the B2 byte in the incoming SONET signal). Up to 8*N BIP errors can be detected per STS-N frame.

Errored seconds (ES-L)

The Near-End Line Errored Seconds (ESL) parameter for each SONET

Line is monitored. The Near-End CVL parameter increments once for every second that contains at least one BIP error detected at the Line layer (at any point during the second), or an AIS-L defect was present.

B - 1 6

365-372-300

Issue 8.0 September 2006

OC-N Performance Parameters

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

Severely errored seconds (SES-L)

The Near-End Line Severely Errored Seconds (SESL) parameter for each SONET Line is monitored. The Near-End SESL parameter increments once for every second that contains at least K BIP errors detected at the Line layer (at any point during the second), or an AIS-L defect was present. The value of K is hard-coded, see table 7 for a list of the values

Unavailable seconds (UAS-L)

The Near-End Line Unavailable Seconds (UASL) parameter for each

SONET Line is monitored. The Near-End UASL parameter increments once for every second that the Line was considered unavailable (at any point during the second). A Line becomes unavailable at the onset of 10 consecutive seconds that qualify as Near-End SESLs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as Near-End SESLs.

Far-End Line Failure Counts (FC-L)

The Far-End Line Failure Counts (FC-L) parameter for each SONET line is monitored. The Far-End FC-L parameter increments once for the beginning of each RFI-L event (RFI-L detected and cleared). A failure that begins in one period and ends in another period, is counted in the period in which it begins.

Protection switch count (PSC-L)

The PSC parameter records the number of times that service traffic switched to or from another line either automatically, by a WaveStar

CIT command, or operations system command. The Near-End

Protection Switch Counts (PSC-L) parameter for each SONET line

(that supports 1+1 protection switching for that line) is monitored.

Separate PSC counters is provided for differentiating between working and protection for each SONET line that supports 2F BLSR for that line. n a 2 Fiber ring, two separate PSC counts are maintained for the working and protection fibers in a given line. These parameters will be defined as PSC-W and PSC-P for Protection Switch Counts-Working and Protection Switch Counts-Protection respectively.

Pointer justifications counts difference (PJCDIFF-P)

This is a calculation of the absolute value of the PJC parameters listed under the headings below.

PJCDIFF-P is used to calculate the difference between calculate the difference between the PPJC-PGEN,

NPJC-PGEN and between PPJC-PDET and NPJC-PDET. DMX monitors the first cross-connected STS. From this STS, the calculation

B - 1 7

OC-N Performance Parameters

B - 1 8

: Performance Monitoring

is to (A) calculate the difference between the PPJC-PGEN,

NPJC-PGEN. (B) Calculate the difference of the PPJC-PDET,

NPJC-PDET. The resulting PJC is the absolute value of the difference between A and B.

Negative pointer justifications counts detected (NPJC-PDET)

This parameter summarizes all Negative Pointer Justifications detected by the system

DMX monitors negative line Pointer Justifications on an

STS-1 within the OC-n line in 1 second intervals. (Users may select which STS-1 to monitor by provisioning the PJC Monitoring point parameter using the

Performance > Provision PM

command.) The count increments for each incoming negative STS pointer justification.

Positive pointer justifications counts detected (PPJC-PDET)

This parameter summarizes all Positive Pointer Justifications detected by the system.

DMX monitors positive line Pointer Justifications on an

STS-1 within the OC-n line in 1 second intervals. (Users may select which STS-1 to monitor by provisioning the PJC Monitoring point parameter using the

Performance > Provision PM

command.) The count increments for each incoming positive STS pointer justification.

Negative pointer justifications counts generated (NPJC-PGEN)

This parameter summarizes all Negative Pointer Justifications generated by the system.

DMX monitors negative line Pointer

Justifications on an STS-1 within the OC-n line in 1 second intervals.

(Users may select which STS-1 to monitor by provisioning the PJC

Monitoring point parameter using the

Performance > Provision PM

command.) The count increments for each outgoing negative STS pointer justification.

Positive pointer justifications counts generated (PPJC-PGEN)

This parameter summarizes all Positive Pointer Justifications generated by the system.

DMX monitors positive line Pointer Justifications on an

STS-1 within the OC-n line in 1 second intervals. (Users may select which STS-1 to monitor by provisioning the PJC Monitoring point parameter using the

Performance > Provision PM

command.) The count increments for each outgoing positive STS pointer justification.

OC-N Line PM Report

Use the

Performance > Reports > OCn Line

command to obtain the OC-N

Line PM Report. For more information about the OC-N line parameters

365-372-300

Issue 8.0 September 2006

OC-N Performance Parameters

: Performance Monitoring

and the

Performance > Reports > OCn Line

command, refer to the

WaveStar

CIT on-line help.

365-372-300

Issue 8.0 September 2006

B - 1 9

: Performance Monitoring

EC-1 Performance Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

This section describes the performance monitoring parameters that are applicable to SONET EC-1 signals.

Monitored parameters

The following table lists the SONET EC-1 line performance parameters that DMX monitors, including the default and ranges for the

15-minute and 1-day (24-hour) registers.

Table B-3 SONET EC-1 Performance Parameters

Facility

EC-1 Line

Measured Provisionable Parameter

Coding Violations (CV-L), CV-LFE

Errored Seconds (ES-L), ES-LFE

Severely Errored Seconds (SES-L),

SES-LFE

Unavailable Seconds (UAS-L), UAS-LFE

Far-End Line Failure Counts (FC-L)

Far-End Line Failure Counts Far End (FC-L

FE)

Pointer Justification Count Difference

(PJCDIFF-P)

15-Min

Default

Range

(Note)

0-16383

0-900

1-72

0-900

Default

448

900

5760

1-Day

Range

(Note)

0-1048575

0-65535

1-4095

0-65535

Negative Pointer Justification Count

Detected (NPJC-PDET)

Positive Pointer Justification Count

Detected (PPJC-PDET)

Negative Pointer Justification Count

Generated (NPJC-PGEN)

Positive Pointer Justification Count

Generated (PPJC-PGEN)

0-900

5760

0-65535

Note: When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

B - 2 0

365-372-300

Issue 8.0 September 2006

EC-1 Performance Parameters

: Performance Monitoring

EC-1 line parameters

DMX monitors the following near end SONET line parameters on incoming (from the local cross-connect) EC-1 signals. The parameters are measured at the input of the 12DS3/EC1 circuit pack on the EC-1 line side (also referred to as facility, customer terminal, or STSX-1 side).

Coding violations (CV-L)

The Near-End Line Coding Violation (CVL) parameter for each

Errored seconds (ES-L)

The Near-End Line Errored Seconds (ESL) parameter for each SONET

Severely errored seconds (SES-L)

Unavailable seconds (UAS-L)

The Near-End Line Unavailable Seconds (UASL) parameter for each

Far-End Line Failure Counts (FC-L)

365-372-300

Issue 8.0 September 2006

B - 2 1

EC-1 Performance Parameters

B - 2 2

: Performance Monitoring

Pointer justifications counts difference (PJCDIFF-P)

This is a calculation of the absolute value of the PJC parameters listed under the headings below.

PJCDIFF-P is used to calculate the difference between calculate the difference between the PPJC-PGEN,

NPJC-PGEN and between PPJC-PDET and NPJC-PDET. DMX monitors the first cross-connected STS. From this STS, the calculation is to (A) calculate the difference between the PPJC-PGEN,

NPJC-PGEN. (B) Calculate the difference of the PPJC-PDET,

NPJC-PDET. The resulting PJC is the absolute value of the difference between A and B.

Negative pointer justifications counts detected (NPJC-PDET)

This parameter summarizes all Negative Pointer Justifications detected by the system

DMX monitors negative line Pointer Justifications on an

STS-1 within the OC-n line in 1 second intervals. (Users may select which STS-1 to monitor by provisioning the PJC Monitoring point parameter using the

Performance > Provision PM

command.) The count increments for each incoming negative STS pointer justification.

Positive pointer justifications counts detected (PPJC-PDET)

This parameter summarizes all Positive Pointer Justifications detected by the system.

DMX monitors positive line Pointer Justifications on an

STS-1 within the OC-n line in 1 second intervals. (Users may select which STS-1 to monitor by provisioning the PJC Monitoring point parameter using the

Performance > Provision PM

command.) The count increments for each incoming positive STS pointer justification.

Negative pointer justifications counts generated (NPJC-PGEN)

This parameter summarizes all Negative Pointer Justifications generated by the system.

DMX monitors negative line Pointer

Justifications on an STS-1 within the OC-n line in 1 second intervals.

(Users may select which STS-1 to monitor by provisioning the PJC

Monitoring point parameter using the

Performance > Provision PM

command.) The count increments for each outgoing negative STS pointer justification.

Positive pointer justifications counts generated (PPJC-PGEN)

This parameter summarizes all Positive Pointer Justifications generated by the system.

DMX monitors positive line Pointer Justifications on an

STS-1 within the OC-n line in 1 second intervals. (Users may select which STS-1 to monitor by provisioning the PJC Monitoring point

365-372-300

Issue 8.0 September 2006

EC-1 Performance Parameters

: Performance Monitoring

parameter using the

Performance > Provision PM

command.) The count increments for each outgoing positive STS pointer justification.

EC-1 Line PM Report

Use the

Performance > Reports > EC1 Line

command to obtain the EC-1

Line PM Report. For more information about the EC-1 line parameters and the

Performance > Reports > EC1 Line

command, refer to the

WaveStar

CIT on-line help.

365-372-300

Issue 8.0 September 2006

B - 2 3

: Performance Monitoring

E1 Performance Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

This section describes the performance monitoring parameters that are applicable to E1 signals.

Monitored parameters

The following table lists the E1 line performance parameters that DMX monitors, including the default and ranges for the 15-minute and 1-day

(24-hour) registers.

Table B-4 SONET E1 Performance Parameters

Facility

E1 Line

Measured Provisionable Parameter

Errored Seconds (ES-L)

Severely Errored Seconds (SES-L)

15-Min

Default

Range

(Note)

0-900

Default

648

100

1-Day

Range

(Note)

0-65535

Background Block Errors - Path

(BBE-P),

BBE-PFE

Errored Seconds (ES-P), ES-PFE

13290 0-16383 3865 0-1048575

E1 Path

Severely Errored Seconds (SES-P),

SES-PFE

Unavailable Seconds (UAS-P), UAS-PFE

0-900

648

100

0-65535

10 0-900 10 0-65535

Note: When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

B - 2 4

365-372-300

Issue 8.0 September 2006

EC-1 Performance Parameters

: Performance Monitoring

E1 line parameters

DMX monitors the following near end SONET line parameters on incoming (from the local cross-connect) E1 signals. The parameters are measured at the input of the DS1/E1 circuit pack on the E1 line side

(also referred to as facility, customer terminal, or STSX-1 side).

Errored seconds (ES-L)

The Near-End Line Errored Seconds (ESL) parameter for each SONET

The Far-End Line Errored Seconds parameter for each SONET line is monitored. The Far-End ESL parameter increments once for each second where one or more Far-End Line layer BIP errors are detected as reported by the REI-L indication of the line overhead or an RDI-L defect is detected.

Severely errored seconds (SES-L)

The Far-End Line Severely Errored Seconds parameter for each

SONET line is monitored. The Far-End SESL parameter increments once for each second where K or more Line layer BIP errors are detected as reported by the REI-L indication of the line overhead or an

RDI-L defect is detected. The integer value for K is set by standards and is selectable

EC-1 Line PM Report

Use the

Performance > Reports > EC1 Line

command to obtain the EC-1

Line PM Report. For more information about the EC-1 line parameters and the

Performance > Reports > EC1 Line

command, refer to the

WaveStar

CIT on-line help.

E1 path parameters

DMX monitors the following near end path parameters on incoming

(from the local cross-connect) E1 signals. The parameters are measured at the input of the DS1/E1 circuit pack on the E1 line side (also referred to as facility, customer terminal, or STSX-1 side).

365-372-300

Issue 8.0 September 2006

B - 2 5

EC-1 Performance Parameters

B - 2 6

: Performance Monitoring

Background Block Errors (BBE-P)

The Near-End E1 Background Block Errors (BBE-P) parameter for each E1 Path is monitored. The number of Near-End BBE-Ps in a one second period is equal to the Near-End EBC if the second is not a

Near-End SES. Otherwise, the BBE-P is set to zero for that second.

The Far-End E1 Background Block Errors (BBE-P) parameter for each

E1 Path is monitored. The number of Far-End E1 BBE-Ps in a one second period is equal to the Far-End EBC if the second is not a Far-End

SESP and there is not a Near-End Defect. Otherwise, the BBE-P is set to zero for that second.

The BBE-P parameter applies only to the CRC-4 MultiFrame format.

Errored seconds (ES-P)

The Near-End E1 Path Errored Seconds (ESP) parameter for each E1 signal is monitored. The ESP parameter applies to both FAS format and

CRC-4 MultiFrame format.

For the FAS format, the ESP parameter increments once for each one second interval containing one or more errored FAS anomalies, or one or more defects.

For the CRC-4 MultiFrame format, the ESP parameter increments once for each one second interval containing CRC-4 block errors, or one or more defects.

The Far-End E1 Path Errored Seconds (ESP) parameter for each E1 path is monitored. The Far-End ESP parameter applies to both FAS format and CRC-4 MultiFrame format.

For the FAS format, the Far-End ESP parameter increments once for each one second interval containing one or more RDI defects and there is not a Near-End Defect.

For the CRC-4 MultiFrame format, the Far-End ES parameter increments once for each one second interval containing one or more RDI defects, or a Far-End Block Error (FEBE), and there is not a Near-End

Defect.

If the A-Bit equals 1 in four or more double frames, then there is an

RDI defect.

Severely errored seconds (SES-P)

The Near-End E1 Path Severely Errored Seconds (SESP) parameter for each E1 path is monitored. The SES parameter applies to both FAS frame and CRC-4 MultiFrame formats.

365-372-300

Issue 8.0 September 2006

EC-1 Performance Parameters

: Performance Monitoring

For the FAS format, the SES parameter increments once for each one second interval containing 28 or more frame bit errors, or one or more defects.

For the CRC-4 MultiFrame format, the SES parameter increments once for each one second interval containing 300 or more CRC-4 block errors, or one or more defects.

The Far-End E1 Path Severely Errored Seconds (SESP) parameter for each E1 path is monitored. The Far-End SESP parameter applies to both

FAS format and CRC-4 MultiFrame format.

For the FAS format, the Far-End SESP parameter increments once for each one second interval containing one or more RDI defects and there is not a Near-End Defect.

For the CRC-4 MultiFrame format, the Far-END ESP parameter increments once for each one second interval containing one or more

RDI defects, or 300 or more FEBEs and there is not a Near-End Defect.

If the A-Bit equals 1 in four or more double frames, then there is an RDI defect.

FEBE is based on the E-bit (ITU-T G.704).

Unavailable seconds (UAS-P)

The Near-End E1 Path UAS Seconds (UASP) parameter for each E1 path is monitored. The UAS parameter is a count of 1 second intervals for which the E1 path is unavailable at the onset of 10 contiguous SESs.

The 10 SESs are included in the unavailable time. Once unavailable, the UAS continues to increment once for each second until ten consecutive seconds without SES are detected. The 10 seconds without

SESs are excluded from the unavailable time. The UAS parameter applies to both FAS frame and CRC-4 MultiFrame formats.

The Far-End E1 Path UAS Seconds (UASP) parameter for each E1 path is monitored. The Far-End UASP parameter is a count of 1 second intervals for which the E1 path is unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in the unavailable time.

Once unavailable, the Far-End UASP continues to increment once for each second until ten consecutive seconds without SES are detected.

The 10 seconds without SESs are excluded from the unavailable time.

The Far-End UASP parameter applies to both FAS frame and CRC-4

MultiFrame formats

365-372-300

Issue 8.0 September 2006

B - 2 7

: Performance Monitoring

STS-N Performance Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

This section describes the performance monitoring parameters on terminated (STS-1) and intermediate STS-N (STS-1, STS-3c,

STS-12c) paths that are cross-connected through the system.

Intermediate SONET STS-N path performance monitoring applies to

STS-N paths cross-connected to another SONET interface. Terminated

SONET STS-N path performance monitoring applies to STS-N paths cross-connected to a non-SONET interface (for example, DS3).

Monitored parameters

The following table lists the SONET STS-N path performance parameters that DMX monitors, including the default and ranges for the

15-minute and 1-day (24-hour) registers.

Table B-5 SONET STS-N Performance Parameters

Facility Measured Provisionable Parameter

STS-48c Path Coding Violations (CV-P), CV-PFE

STS-12c Path Coding Violations (CV-P), CV-PFE

STS-3c Path Coding Violations (CV-P), CV-PFE

STS-1 Path Coding Violations (CV-P), CV-PFE

STS-48c Path Errored Seconds (ES-P), ES-PFE

STS-12c Path Errored Seconds (ES-P), ES-PFE

STS-3c Path Errored Seconds (ES-P), ES-PFE

STS-1 Path Errored Seconds (ES-P), ES-PFE

FC-P, FC-PFE

240

15-Min

Default

Range

(Note)

300

0-16383

0-900

0-16383

0-900

1-72

Default

3000

750

250

150

2400

600

200

100

1-Day

Range

(Note)

0-1048575

0-65535

0-1048575

0-65535

1-4095

STS-N Path

Severely Errored Seconds (SES-P),

SES-PFE

3 0-900 7 0-65535

Unavailable Seconds (UAS-P), UAS-PFE 10 0-900 10 0-65535

Note: When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

B - 2 8

365-372-300

Issue 8.0 September 2006

STS-N Performance Parameters

: Performance Monitoring

STS-N path parameters

DMX monitors the following near end SONET STS path parameters on incoming (from the SONET interface) STS-N signals.

Coding violations (CV-P)

The Near-End STS Path Coding Violations (CVP) parameter for each

SONET path is monitored. The CVP parameter increments once for each BIP error detected at the STS path layer (the B3 byte of the incoming SONET STS Path overhead). Up to 8 BIP errors can be detected per frame.

The Far-End STS Path Coding Violations (CVP) parameter for each

SONET path is monitored. The Far-End CVP parameter increments as reported by the REI-P indication of the STS path overhead.

Errored seconds (ES-P)

The Near-End STS Path Errored Seconds (ESP) parameter for each

SONET path is monitored. The ESP parameter increments once for each second where one or more STS Path layer BIP errors are detected or an AIS-P, LOP-P, or UNEQ-P defect is detected.

The Far-End STS Path Errored Seconds (ESP) parameter for each

SONET path is monitored. The Far-End ESP parameter increments once for each second where one or more Far-End STS Path layer BIP errors are detected as reported by the REI-P indication of the line overhead or an RDI-P defect is present, or an ERDI-P (if supported) defect is detected.

Currently this product detects 1-bit RDI, but treats it as though it is the high order bit of a 3-bit ERDI in that it includes UNEQ.

365-372-300

Issue 8.0 September 2006

B - 2 9

STS-N Performance Parameters

: Performance Monitoring

Severely errored seconds (SES-P)

The Near-End STS Path Severely Errored Seconds (SESP) parameter for each SONET path is monitored. The SESP parameter increments once for each second where K or more STS Path layer BIP errors are detected or an AIS-P, LOP-P, or UNEQ-P defect is detected. The integer value for K is set by standards and is selectable (values are shown in Table 8). Currently DMXdetects 1-bit RDI, but treats it as though it is the high order bit of a 3-bit ERDI in that it includes UNEQ.

The Far-End STS Path Severely Errored Seconds (SESP) parameter for each SONET path is monitored. The Far-End SESP parameter increments once for each second where K or more STS Path layer BIP errors are detected as reported by the REI-P indication of the path overhead or a one bit RDI-P defect was present or (if ERDI-P is supported), an

ERDI-P defect is detected. The integer value for K is set by standards and selectable (values are shown in Table 8).

Currently this product detects 1-bit RDI, but treats it as though it is the high order bit of a 3-bit ERDI in that it includes UNEQ.

Unavailable seconds (UAS-P)

The Near-End STS Path Unavailable Seconds (UASP) parameter for each SONET path is monitored. The UASP parameter increments once for each second where SESP is detected after ten consecutive seconds with SESP detected. UASP continues to increment once for each second until ten consecutive seconds without SESP are detected.

The Far-End STS Path Unavailable Seconds (UASP) parameter for each SONET path is monitored. The Far-End UASP parameter increments once for each second where Far-End SESP is detected after ten consecutive seconds with Far-End SESP detected. Far-End UASP continues to increment once for each second until ten consecutive seconds without Far-End SESP are detected

B - 3 0

365-372-300

Issue 8.0 September 2006

STS-N Performance Parameters

: Performance Monitoring

Failure Counts Path (FC-P)

The Far-End STS Path Failure Counts (FC-P) parameter for each

SONET path is monitored. The Far-End FC-P parameter increments once for the beginning of each RFI-P event (RFI-P detected and cleared). A failure that begins in one period and ends in another period, is counted in the period in which it begins.

STS-N Path PM Report

Use the

Performance > Reports > STSn Path

command to obtain the

STS-N Path PM Report. For more information about the STS-N path parameters and the

Performance > Reports > STSn Path

command, refer to the WaveStar

CIT on-line help.

365-372-300

Issue 8.0 September 2006

B - 3 1

: Performance Monitoring

VT1.5 Performance Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

This section describes the terminated SONET VT1.5 performance monitoring parameters. Terminated SONET VT1.5 path performance monitoring applies to VT1.5 paths cross-connected to a non-SONET interface (for example, DS1 or TMUX).

Monitored parameters

The following table lists the SONET VT1.5 path performance parameters that DMX monitors, including the default and ranges for the

15-minute and 1-day (24-hour) registers.

Table B-6 SONET VT1.5 Performance Parameters

Facility

VT1.5 Path

Measured Provisionable Parameter

Coding Violations (CV-P), CV-PFE

V5 Errored Seconds (ES-P), ES-PFE

V5 Severely Errored Seconds (SES-P)

V5 Unavailable Seconds (UAS-P)

UAS-PFE

15-Min

Default

Range

(Note)

0-16383

0-900

40 0-900

Default

1-Day

Range

(Note)

750

900

0-1048575

0-65535

900 0-65535

FC-P, FC-PFE 10 1-72 10 1-4095

Note: When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

VT1.5 path parameters

DMX monitors the following near end SONET VT1.5 path parameters on incoming (from the SONET interface) VT1.5 signals.

Coding violations (CV-P)

The Near-End STS Path Coding Violations (CVP) parameter for each

The Far-End VT Path Coding Violations (CVP) parameter for each

SONET path is monitored. The VT Far-End CVP parameter increments as reported by the REI-V indication of the VT path overhead.

B - 3 2

365-372-300

Issue 8.0 September 2006

VT1.5 Performance Parameters

: Performance Monitoring

Errored seconds (ES-P)

The Near-End STS Path Errored Seconds (ESP) parameter for each

SONET path is monitored. The ESP parameter increments once for each second where one or more STS Path layer BIP errors are detected or an AIS-P, LOP-P, or UNEQ-P defect is detected.

The Far-End VT Path Errored Seconds (ESP) parameter for each

SONET path is monitored. The VT Far-End ESP parameter increments once for each second where one or more Far-End VT Path layer BIP errors were reported by the far-end VT-PTE (using the REI-V indication), a one-bit RDI-V defect was present, or an ERDI-V (if supported) defect is detected.

Currently this product detects 1-bit RDI, but treats it as though it is the high order bit of a 3-bit ERDI in that it includes UNEQ.

Severely errored seconds (SES-P)

The Far-End VT Path Severely Errored Seconds (SESP) parameter for each SONET VT path is monitored. The VT Far-End SESP parameter increments once for each second where K or more BIP errors are reported by the far-end VT-PTE (using the REI-V indication), or a one bit RDI-V defect was present or (if ERDI-V is supported), an ERDI-V defect is detected. The integer value for K is set by standards (values are shown in Table 10).

Currently this product detects 1-bit RDI, but treats it as though it is the high order bit of a 3-bit ERDI in that it includes UNEQ.

365-372-300

Issue 8.0 September 2006

B - 3 3

VT1.5 Performance Parameters

: Performance Monitoring

Unavailable seconds (UAS-P)

The Far-End VT Path Unavailable Seconds (UASP) parameter for each

SONET path is monitored. The VT Far-End UASP parameter increments once for each second where VT Far-End SESP is detected after ten consecutive seconds with VT Far-End SESP detected. VT

Far-End UASP continues to increment once for each second until ten consecutive seconds without VT Far-End SESP are detected.

Failure Counts Path (FC-P)

The Near-End STS Path Failure Counts (FC-P) parameter for each

SONET path is monitored. The FC-P parameter increments once for the beginning of each AIS-P event (AIS-P detected and cleared),

LOP-P event (LOP-P detected and cleared), UNEQ-P event (UNEQ-P detected and cleared). A failure that begins in one period and ends in another period, is counted in the period in which it begins.

The Far-End STS Path Failure Counts (FC-P) parameter for each

B - 3 4

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

VC-12 Performance Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

This section describes the terminated SONET VC-12 performance monitoring parameters. Terminated SONET VC-12 path performance monitoring applies to all VC-12 paths.

Monitored parameters

The following table lists the SONET VC-12 path performance parameters that DMX monitors, including the default and ranges for the

15-minute and 1-day (24-hour) registers.

Table B-7 SONET VC-12 Performance Parameters

Facility Measured Provisionable Parameter

15-Min

Default

Range

(Note)

Default

1-Day

Range

(Note)

VC-12 Path

Background Block Errors - Path

(BBE-P),

BB-PFE

Errored Seconds (ES-P), ES-PFE

Severely Errored Seconds (SES-P),

SES-PFE)

0-16383

0-900

750

900

0-1048575

0-65535

Unavailable Seconds (UAS-P), UAS-PFE

FC-P, FC-PFE

0-900

1-72

900

0-65535

1-4095

Note: When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

VC-12 path parameters Background Block Errors (BBE-P)

The Near-End E1 Background Block Errors (BBE-P) parameter for each E1 Path is monitored. The number of Near-End BBE-Ps in a one second period is equal to the Near-End EBC if the second is not a

Near-End SES. Otherwise, the BBE-P is set to zero for that second.

The Far-End Background Block Errors (BBE-P) parameter for each

Low Order Path is monitored. The number of Far-End VC-n BBE-Ps in a one second period is equal to the F_EBC if the second is not a Far-End

SES and if the second is not a N_DS. Otherwise, the Far-End BBE-P is set to zero for that second.

ITU-T standards refers to this parameter as F_BBE, but for consistency within the DMX product, this parameter will be referred to as BBE-P with a locn value of FEND to indicate that it is the Far-End Background

Block Errors.

365-372-300

Issue 8.0 September 2006

B - 3 5

VT1.5 Performance Parameters

: Performance Monitoring

Errored seconds (ES-P)

The Near-End VC-n Errored Seconds (ESP) parameter for each Low

Order VC-n is monitored. A Near-End VC-n ES parameter shall increment for each second in which there is one or more N_Bs (detected at the Low Order Path Layer) or a N_DS defect is present.

ITU-T standards refers to this parameter as N_ES, but for consistency within the DMX product, this parameter will be referred to as ES with a locn value of NEND to indicate that it is the Near-End Errored

Seconds.

The Far-End VC-n Errored Seconds (ESP) parameter for each Low

Order VC-n Path is monitored. A Far-End VC-n ES parameter shall increment for each second in which the Far-End errored block count

(F_EBC) is equal to or greater than 1 or when at least one F_DS defect is present for that second, and there is no N_DS present for that second.

ITU-T standards refers to this parameter as F_ES, but for consistency within the DMX product, this parameter will be referred to as ES with a locn value of FEND to indicate that it is the Far-End errored seconds.

Severely errored seconds (SES-P)

The Near-End VC-n Severely Errored Seconds (SESP) parameter for each Low Order VC-n is monitored. An Near-End VC-n SES parameter shall increment for each second in which the N_EBC is equal to or greater than K, or an N_DS defect is present. The integer value for K is set by standards (values are shown in Table 9). ITU-T standards refers to this parameter as N_SES, but for consistency within the DMX product, this parameter will be referred to as SES with a locn value of

NEND to indicate that it is the Near-End Severely Errored Seconds parameter.

The Far-End Severely Errored Seconds (SESP) parameter for each Low

Order VC-n Path is monitored. A Far-End VC-n SES parameter shall increment for each second in which the Far-End errored block count

(F_EBC) is equal to or greater than K or at least one F_DS defect is present for that second, and there is no N_DS defect present for that second. The integer value for K is set by standards (values are shown in

Table 9).

ITU-T standards refers to this parameter as F_SES, but for consistency within the DMX product, this parameter will be referred to as SES with a locn value of FEND to indicate that it is the Far-End Severely Errored

Seconds.

B - 3 6

365-372-300

Issue 8.0 September 2006

VT1.5 Performance Parameters

: Performance Monitoring

Unavailable seconds (UAS-P)

The Near-End VC-n Unavailable Seconds (UASP) parameter for each

Low Order Path is monitored. The Near-End VC-n UAS parameter increments once for every second that the Low Order Path was considered unavailable (at any point during the second). A Low Order Path becomes unavailable at the onset of 10 consecutive seconds that qualify as Near-End VC-n SESP, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as Near-End VC-n

SES.

The (un)available time can not be determined if it is unknown whether the previous 10 seconds are Severely Errored on non-Severely Errored.

Thus the SES must be processed to determine whether the SES are consecutively present or absent. ITU-T standards refers to this parameter as N_UAS, but for consistency within the DMX product, this parameter will be referred to as UAS with a locn value of NEND to indicate that it is the Near-End Unavailable Seconds.

The Far-End Unavailable Seconds (UASP) parameter for each Low

Order Path is monitored. The Far-End VC-n UAS parameter increments once for every second that the Far-End Low Order Path was considered unavailable (at any point during the second). A Far-End Low Order Path becomes unavailable at the onset of 10 consecutive seconds that qualify as Far-End VC-n SESs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as Far-End VC-n SESs.

The (un)available time cannot be determined if it is unknown whether the previous 10 seconds are Severely Errored on non-Severely Errored.

Thus the Far-End VC-n SES must be processed to determine whether the Far-End VC-n SES are consecutively present or absent.

ITU-T standards refers to this parameter as F_UAS, but for consistency within the DMX product, this parameter will be referred to as UAS with a locn value of FEND to indicate that it is the Far-End Unavailable

Seconds.

365-372-300

Issue 8.0 September 2006

B - 3 7

VT1.5 Performance Parameters

: Performance Monitoring

Failure Counts Path (FC-P)

The Near-End VC-n Path Failure Counts (FC-P) parameter for each

Low Order path is monitored. The FC-P parameter increments once for the beginning of each TU-AIS event (TU-AIS detected and cleared),

TU-LOP event (TU-LOP detected and cleared), LP-UNEQ event

(LP-UNEQ detected and cleared), HP-LOM event (HP-LOM detected and cleared). A failure that begins in one period and ends in another period, is counted in the period in which it begins.

The Far-End VC-n Path Failure Counts (FC-P) parameter for each Low

Order path is monitored. The VC-n Far-End FC-P parameter increments once for the beginning of each RDI event (RDI detected and cleared). A failure that begins in one period and ends in another period, is counted in the period in which it begins.

B - 3 8

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

DS3 Performance Monitoring Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

This section describes the performance monitoring parameters that are monitored on DS3 signals incoming from the high speed fiber and from the local DSX-3 cross-connect.

In order to generate DS3 PM reports, the port Primary State must be

IS (in service). (When the PST parameter is provisioned as AUTO and a valid DS3 signal is detected, the PST parameter automatically transitions to the IS state.) The VM mode should be off because the

P-bits can be corrected at nodes where the VM Mode is provisioned on, and the DS3 P-bit PM data may not provide a complete report of the end-to-end DS3 path errors.

Monitored parameters

The following table lists the DS3 line and path performance parameters that DMX monitors, including the default and ranges for the 15-minute and 1-day (24-hour) registers.

Table B-8 DS3 Performance Parameters

Facility

DS3 Line

Measured Provisionable Parameter

Coding Violations (CV-L)

Errored Seconds (ES-L)

Severely Errored Seconds (SES-L)

Coding Violations (CV-P)

Coding Violations Far End (CV-PFE)

15-Min

Default

Range

(Note)

1-Day

Default

Range

(Note)

387 0-16383 3865 0-1048575

25 0-900 250 0-65535

4 0-900 40 0-65535

382 0-16383 3820 0-1048575

Errored Seconds (ES-P)

Errored Seconds Far End (ES-PFE)

Severely Errored Seconds (SES-P)

Severely Errored Seconds

Far End

(SES-PFE)

25 0-900 250 0-65535

4 0-900 40 0-65535

DS3 Path

Unavailable Seconds (UAS-P)

Unavailable Seconds Far End (UAS-PFE)

SE Frame/Alarm Indication Signal Seconds (SAS-P)

SE Frame/Alarm Indication Signal Seconds Far End

(SAS-PFE)

0-900

0-65535

Note: When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

365-372-300

Issue 8.0 September 2006

B - 3 9

DS3 Performance Monitoring Parameters

: Performance Monitoring

DS3 line parameters

DMX monitors the following ingress near end DS3 line parameters on incoming (from the DSX-3 cross-connect) DS3 signals. Ingress refers to performance monitoring parameters that are measured at the input of the DS3 or TMUX circuit pack on the DS3 line side (also referred to as facility, customer terminal, or DSX side).

Supported performance monitoring signal formats

DMX supports DS3 line performance monitoring on DS3 signals with

P-bit parity, FM-bit parity, or CP-bit parity performance monitoring signal formats.

Coding violations (CV-L)

The near end CV-L parameter increments once for each bipolar violation (BPV) and excessive zeros (EXZ) detected at the DS3 line layer.

Errored seconds (ES-L)

The near end ES-L parameter increments once for each second during which DMX detects either one or more bipolar violations (BPVs) or excessive zeros (EXZ), or one or more LOS defects.

Severely errored seconds (SES-L)

The near end SES-L parameter increments once for each second during which DMX detects either one or more LOS defects, 2444 or more

BPVs at a minimum BER of 7.5 X 10

-5

, or 45 or more BPVs at a minimum BER of 1 X 10

-6

DS3 Line PM Report

Use the

Performance > Reports > DS3 Line

command to obtain the DS3

Line PM Report. Ingress near end DS3 line PM is reported with an AID of the DS3 or TMUX interface and a modifier of T3. For more information about the DS3 line parameters and the

Performance >

Reports > DS3 Line

command, refer to the WaveStar

CIT on-line help.

B - 4 0

365-372-300

Issue 8.0 September 2006

DS3 Performance Monitoring Parameters

: Performance Monitoring

DS3 path performance monitoring signal format

DMX supports the following DS3 path performance monitoring signal formats:

• P-bit parity: The P bits are monitored for detecting code violations at the near end.

• FM-bit parity: The F and M bits are monitored for detecting code violations at the near end.

• CP-bit parity: CP-bit parity is used for end-to-end DS3 path PM

(near end and far end). The C bits are monitored for code violations. CP-bit parity is only allowed on DS3 signals with the

C-bit signal format.

P-bit parity

When provisioned for P-bit parity, DMX calculates and provides counts of the following near end DS3 path parameters incoming from the fiber or DSX-3:

• Coding violations (CV-P)

• Errored seconds (ES-P)

• Severely errored seconds (SES-P)

• Unavailable seconds (UAS-P)

• Severely errored frame/alarm indication signal seconds(SAS-P)

FM-bit parity

FM-bit parity provides an alternative method for determining and accumulating DS3 path performance data based on an error estimation technique using errors on the F&M framing bits to approximate the actual error counts in the DS3 path payload.

Adjusted F&M bit performance monitoring estimates the following near end DS3 path parameters incoming from the fiber or DSX-3:

• Coding violations (CV-P)

• Errored seconds (ES-P)

• Severely errored seconds (SES-P)

• Unavailable seconds (UAS-P)

• Severely errored frame/alarm indication signal seconds (SAS-P)

365-372-300

Issue 8.0 September 2006

B - 4 1

DS3 Performance Monitoring Parameters

: Performance Monitoring

CP-bit parity

When provisioned for CP-bit parity, DMX calculates and provides counts of the following DS3 near end and far end path parameters incoming from the fiber or DSX-3:

• Coding violations (CV-P)

• Coding violations Far End (CV-PFE)

• Errored seconds (ES-P)

• Errored seconds Far End (ES-PFE)

• Severely errored seconds (SES-P)

• Severely errored seconds Far End (SES-PFE)

• Unavailable seconds (UAS-P)

• Unavailable seconds Far End (UAS-PFE)

• Severely errored frame/alarm indication signal seconds (SAS-P)

• Severely errored frame/alarm indication signal seconds Far End

(SAS-PFE)

B - 4 2

365-372-300

Issue 8.0 September 2006

DS3 Performance Monitoring Parameters

: Performance Monitoring

Violation monitoring and removal

The DS3 path performance monitoring signal formats support provisionable P-bit monitoring and correction (violation monitoring mode) on the outgoing DS3 signal toward the DS3 facility.

The following table shows the provisionable DS3 signal formats, performance monitoring signal formats, and VM modes.

Table B-9 DS3 Signal formats, PM signal formats, and VM modes

DS3 Signal

Format

C-Bit

Performance

Monitoring

Signal

Format

VM Mode

P-bit parity

FM-bit parity

CP-bit parity

Off

Monitor

P-Bits

Correct

P-Bits

Near end DS3 path parameters

DMX monitors the following ingress and egress near end DS3 path parameters at the local network element. Ingress refers to parameters that are measured on incoming DS3 signals at the input of the local

DS3 or TMUX circuit pack on the DS3 line side (also referred to as facility, customer terminal, or DSX side). Egress refers to parameters that are measured on incoming DS3 signals at the input of the local

DS3 port unit on the SONET side (also referred to as fiber side).

Coding violations (CV-P)

The near end CV-P parameter increments once for each parity error detected at the path level. The CV-P parameter applies to all performance monitoring signal formats.

In the P-bit parity signal format, unidentical P-bits corresponding to the same DS3 M-frame also increment the CV-P parameter.

For CP-bit parity signal format, the three C-bits in subframe 3 of a

C-bit formatted DS3 frame carry the DS3 path-parity information. At the DS3 transmitter, the CP bits in the DS3 C-bit frame are set equal to the two P-bits in frame “n”. These CP bits are then inserted into frame

“n+1”. Since the CP bits are not modified in any way while passing

365-372-300

Issue 8.0 September 2006

B - 4 3

DS3 Performance Monitoring Parameters

: Performance Monitoring

through the network, the DS3 high-speed receiver can determine if errors occurred in the DS3 path. The DS3 receiver computes the parity of frame “n” and compares that parity with the value received in the CP bits in frame “n+1”. If the values do not match, DS3 path parity violations are counted.

Errored seconds (ES-P)

The near end ES-P parameter increments once for each second during which DMX detects either one or more parity errors, one or more SEF defects, or one or more AIS defects. The ES-P parameter applies to all performance monitoring signal formats.

Severely errored seconds (SES-P)

The near end SES-P parameter increments once for each second during which DMX detects either one or more AIS or SEF defects, 2444 or more BPVs at a minimum BER of 7.5 X 10

-5

, or 45 or more BPVs at a minimum BER of 1 X 10

-6

. The SES-P parameter applies to all performance monitoring signal formats.

Unavailable seconds (UAS-P)

A near end UAS-P is a second during which the path is unavailable. A path is considered unavailable from the beginning of 10 consecutive severely errored seconds until the beginning of 10 consecutive seconds, none of which are severely errored. The UAS-P parameter applies to the P-bit parity and FM-bit parity performance monitoring signal formats.

Severely errored frame/alarm indication signal seconds (SAS-P)

The SAS-P parameter increments once for each second during which

DMX detects either one or more severely errored frame defects, or one or more AIS defects. The SAS-P parameter applies to all performance monitoring signal formats.

B - 4 4

365-372-300

Issue 8.0 September 2006

DS3 Performance Monitoring Parameters

: Performance Monitoring

Near End DS3 Path PM Report

Use the

Performance > Reports > DS3 Path

command to obtain the DS3

Path PM Report. Ingress near end DS3 path PM is reported with an

AID of the DS3 or TMUX interface and a modifier of T3. Egress near end DS3 path PM is reported with an AID of the SONET interface and a modifier of T3. For more information about the DS3 path parameters and the

Performance > Reports > DS3 Path

command, refer to the

WaveStar

CIT on-line help.

Far end DS3 path parameters

DMX monitors the following ingress and egress far end DS3 path parameters at the local network element. If the far end network element detects an incoming error, the far end network element communicates the error back to the local near end network element using far end block error (FEBE) bits in the DS3 path overhead. (This allows the local near end DMX to perform the PM accumulation, storage, thresholding, and reporting functions for both the near end and far end.)

Ingress refers to far end parameters that are measured at the input of the local DS3 or TMUX circuit pack on the DS3 line side (also referred to as facility, customer terminal, or DSX side). Egress refers to far end parameters that are measured at the input of the local DS3 port unit on the SONET side (also referred to as fiber side).

Important!

The DS3 signal format must be provisioned for

C-Bit and the performance monitoring signal format must be provisioned for CP-Bit Parity to monitor the far-end parameters.

Coding violations Far End (CV-PFE)

The CV-PFE parameter increments as reported by the FEBE indication in the line overhead. At the far end if an incoming DS3 path error (for example, C-bit, F-bit, or M-bit error) is detected, an error indication is communicated back to the near end equipment by using the far end block error (FEBE) bits.

The FEBE message sent back from the far end is set to “111” if no path errors are detected. If a path error is detected, the FEBE message is set to “not 111." The FEBE monitor parameter (CV-PFE) increments once for each occurrence of a received “not all ones” pattern in the received

FEBE message.

365-372-300

Issue 8.0 September 2006

B - 4 5

DS3 Performance Monitoring Parameters

: Performance Monitoring

Errored seconds Far End (ES-PFE)

The ES-PFE parameter increments once for each second containing one or more M-frames with the three FEBE bits not all set to ONE or one or more far-end SEF or one or more far-end AIS defects.

Severely errored seconds Far End (SES-PFE)

The SES-PFE parameter increments once for each second where 2444 or more FEBE errors at a minimum BER of 7.5 X 10

-5

, or 45 or more

FEBE errors at a minimum BER of 1 X 10

-6

are detected as reported by the FEBE indication of the path overhead or one or more far-end SEF or one or more far-end AIS defects are detected.

Unavailable seconds Far End (UAS-PFE)

The UAS-PFE parameter is a count of 1 second intervals for which the

DS3 path is unavailable at the onset of 10 contiguous SES-PFEs. The

10 SES-PFEs are included in the unavailable time. Once unavailable, the UAS-PFE continues to increment once for each second until ten consecutive seconds without SES-PFE are detected. The 10 seconds without SES-PFEs are excluded from the unavailable time

Severely errored frame/alarm indication signal seconds Far End

(SAS-PFE)

The SAS-PFE parameter increments once for each second where one or more far end severely errored frame defects, or one or more far end AIS defects are detected

Far End DS3 Path PM Report

Use the

Performance > Reports > DS3 Path

command to obtain the DS3

Path PM Report. Ingress far end DS3 path PM is reported with an AID of the DS3 or TMUX interface and a modifier of T3. Egress far end

DS3 path PM is reported with an AID of the SONET interface and a modifier of T3. For more information about the DS3 path parameters and the

Performance > Reports > DS3 Path

command, refer to the

WaveStar

CIT on-line help.

B - 4 6

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

DS1 Performance Monitoring Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

This section describes the performance monitoring parameters relevant to DS1 signals incoming from the fiber or DSX-1.

DS1 ESF format

Tariffed service verification consists of monitoring performance parameters that can be associated with the customer’s end-to-end service. The DMX system provides this capability for DS1 services when equipped with 28DS1 circuit packs with the DS1 performance monitoring feature (28DS1PM [LNW7]) and the high density LNW8

56DS1/E1 circuit pack. Based on ANSI T1.403 extended superframe format (ESF), this capability retrieves performance messages written into the ESF data link by the customer’s terminal equipment. From these messages, DMX can determine and report the end-to-end error performance of the entire DS1 link as seen by the customer. The counts are retrieved by the message-based operations system to determine if the service is operating within tariffed limits.

DS1 SF format

Each 28DS1PM and 56DS1/E1 circuit packs measure the near-end performance of the incoming DS1 signals, allowing the service provider to determine if a good DS1 signal was received from the customer before transporting it through the network. This information can then aid in sectionalizing any reported performance problems. The

28DS1PM and 56DS1/E1 circuit packs can also provide this same near-end information for super frame (SF) formatted (sometimes known as “D4 framing”) DS1 services, but complete end-to-end performance verification is limited due to the lack of the PRM in the SF format.

365-372-300

Issue 8.0 September 2006

B - 4 7

DS1 Performance Monitoring Parameters

: Performance Monitoring

Monitored parameters

The following table lists the DS1 line and path performance parameters that DMX monitors, including the default and ranges for the 15-minute and 1-day (24-hour) registers.

Table B-10 DS1 Performance Parameters

Facility

DS1 Line

Measured Provisionable Parameter

Errored Seconds (ES-L), ES-LFE

Coding Violations (fmt=ESF)

(CV-L)

Severely Errored Seconds (SES-L)

Coding Violations (fmt=SF) (CV-P)

Coding Violations (fmt=ESF)

(CV-P)

Coding Violations

Far End (CV-PFE)

Errored Seconds (ES-P)

Errored Seconds

Far End

(ES-PFE)

15-Min

Default

Range

(Note)

Default

1-Day

Range

(Note)

65 0-900 648 0-65535

13340 0-16383 133400 0-1048575

0-900

0-16383

648

691

0-65535

0-1048575

13296 0-16383 132960 0-1048575

65 0-900 648 0-65535

DS1 Path

Severely Errored Seconds (SES-P)

Severely Errored Seconds

Far End

(SES-PFE)

Unavailable Seconds (UAS-P)

Unavailable Seconds Far End (UAS-PFE)

0-900

100

0-65535

SE Frame/Alarm Indication Signal Seconds

(SAS-P)

SE Frame Seconds Far End (SEFS-PFE)

2 0-900 17 0-65535

Note: When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

B - 4 8

DS1 line parameters

DMX monitors the following near end DS1 line parameter on incoming

(from the DSX-1 cross-connect) DS1 signals. The parameter is measured at the input of the DS1 circuit pack on the DS1 line side (also referred to as facility, customer terminal, or DSX side).

Coding violations (CV-L)

The Near-End Line Coding Violation (CVL) parameter for each

365-372-300

Issue 8.0 September 2006

DS1 Performance Monitoring Parameters

: Performance Monitoring

Errored seconds (ES-L)

The near end ES-L parameter increments once for each second during which DMX detects either one or more bipolar violations (BPVs) or excessive zeros (EXZ), or one or more LOS defects.

Severely errored seconds (SES-L)

DS1 Line PM Report

Use the

Performance > Reports > DS1 line

command to obtain the DS1

Line PM Report. Near end DS1 line PM is reported with an AID of the

DS1 interface and a modifier of T1. For more information about the

DS1 line parameter and the

Performance > Reports > DS1 line

command, refer to the WaveStar

CIT on-line help.

Near end DS1 path parameters

DMX monitors the following near end DS1 path parameters at the local network element. The parameters are measured at the input of the local

DS1 or TMUX circuit pack on the DS1 line side (also referred to as facility, customer terminal, or DSX side).

Coding violations (CV-P)

For the SF format, the CV-P parameter increments once for each frame synchronization bit error (FE) detected at the path level. For the ESF format, the CV-P parameter increments once for each cyclic redundancy check error (CRC) detected at the path level.

Errored seconds (ES-P)

For the SF format, he ES-P parameter increments once for each second during which DMX detects FE errors, CS events, SEF defects, or AIS defects. For the ESF format, he ES-P parameter increments once for each second during which DMX detects CRC errors, CS events, SEF defects, or AIS defects.

Severely errored seconds (SES-P)

For the SF format, the SES-P parameter increments once for each second during which DMX detects 8 or more FE events (if Ft and Fs

365-372-300

Issue 8.0 September 2006

B - 4 9

DS1 Performance Monitoring Parameters

: Performance Monitoring

bits are measured) or 4 or more FE events (if only Ft bits are monitored), or SEF defects, or AIS defects.

Unavailable seconds (UAS-P)

A UAS-P is a second during which the path is unavailable. A path is considered unavailable from the beginning of 10 consecutive severely errored seconds until the beginning of 10 consecutive seconds, none of which are severely errored.

Severely errored frame/alarm indication signal seconds (SAS-P)

The SAS-P parameter increments once for each second during which

DMX detects either one or more severely errored frame defects, or one or more AIS defects. The SAS-P parameter applies to SF and ESF frame formats.

Far end DS1 path parameters

Near End DS1 Path PM Report

Use the

Performance > Reports > DS1 path

command to obtain the DS1

Path PM Report. Near end DS1 path PM is reported with an AID of the

DS1 or TMUX interface and a modifier of T1. For more information about the DS1 path parameters and the

Performance > Reports > DS1 path

command, refer to the WaveStar

CIT on-line help.

DMX monitors the following far end DS1 path parameters at the local network element. If the far end network element detects an incoming error, the far end network element communicates the error back to the local near end network element using Performance Report Message

(PRM) frames or a Remote Alarm Indication (RAI) signal.

The far end parameters are measured at the input of the local DS1 or

TMUX circuit pack on the DS1 line side (also referred to as facility, customer terminal, or DSX side).

Important!

The format must be set to ESF to monitor the far end parameters (CV-PFE, ES-PFE, SES-PFE, and UAS-PFE).

B - 5 0

365-372-300

Issue 8.0 September 2006

DS1 Performance Monitoring Parameters

: Performance Monitoring

Coding violations Far End (CV-PFE)

The CV-PFE parameter increments based on the PRM G bits defined in the following table.

Table B-11 CV-PFE parameter increments

PRM Bit = 1

100

319

333

CV Count Accumulated

Errored seconds Far End (ES-PFE)

The ES-PFE parameter is a count of one second PRM intervals containing an RAI or RAI-CI signal, or a 1 in any of the following bits:

G1, G2, G3, G4, G5, G6, SE, or SL.

Severely errored seconds Far End (SES-PFE)

The SES-PFE parameter is a count of one second PRM intervals containing an RAI or RAI-CI signal or a 1 in any of the following bits:

G6 or SE.

Unavailable seconds Far End (UAS-PFE)

A UAS-PFE is a second during which the path is unavailable. A path is considered unavailable from the beginning of 10 consecutive severely errored seconds until the beginning of 10 consecutive seconds, none of which are severely errored.

365-372-300

Issue 8.0 September 2006

B - 5 1

DS1 Performance Monitoring Parameters

: Performance Monitoring

Severely errored frame seconds (SEFS-PFE)

The SEFS-PFE parameter is a count of 1 second PRM intervals that SE bit is equal to 1.

Far End DS1 Path PM Report

Use the

Performance > Reports > DS1 path

command to obtain the DS1

Path PM Report. Far end DS1 path PM is reported with an AID of the

DS1 or TMUX interface and a modifier of T1. For more information about the DS1 path parameters and the

Performance > Reports > DS1 path

command, refer to the WaveStar

CIT on-line help.

B - 5 2

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

Ethernet/SAN Performance Monitoring Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

DMX provides PM capabilities for the Fast Ethernet and Gigabit

Ethernet interfaces. PM data is collected at each LAN and WAN interface in the network for both incoming and outgoing directions and is stored in quarter-hour and day bins. The WAN interface provides a

Ethernet

Ethernet dropped frames (congestion)

(EDFC) (See Note 1)

0-72862694

Ethernet dropped frames (errors)

(EDFE) (Note 1)

0-72862694

0-6994818653

0-6994818653 connection to a SONET Virtual Concatenation Group (VCG).

TCAs

Provisionable threshold crossing alerts (TCAs) are not supported on the

Ethernet interfaces.

Monitored parameters

The following table lists the Ethernet performance parameters that

DMX monitors, including the ranges for the 15-minute and 1-day

(24-hour) registers.

Table B-12 Ethernet Performance Parameters

Facility Monitored Parameter

Ethernet

(all packs)

EDFC-- Ethernet dropped frames congestion

EDFE-- Ethernet dropped frames errors

EDFP-- Ethernet dropped frames - policer

EINB-- Incoming number of bytes

EINF--Incoming number of frames

EONB--Outgoing number of bytes

EONF-- Outgoing number of frames

15-Min

Range

0-72862694

TBS

1-Day

Range

0-6994818653

TBS

365-372-300

Issue 8.0 September 2006

B - 5 3

Ethernet Performance Monitoring Parameters

: Performance Monitoring

Facility

LNW73 packs

LNW70 packs

Monitored Parameter

INTXWD-- Count of invalid transmission words received.

LOS--Count of instances of signal loss detected.

TBS

LSYNC--Count of instances of synchronization loss detected

DSPERR--Count of disparity errors received

TBS

RFOVD-- Count of received overflow frames dropped TBS

TFOVD--Count of transmit overflow frames dropped TBS

TFCRC--Count of transmitted frames with CRC errors TBS

T10BERR-- Count of transmitted 10B_ERR errors TBS

RCORH-- Count of received single-bit error corrected

GFP header count

TBS

RCRCH-- Count of received uncorrected multi-bit error

GFP header count

TBS

RCORF-- Count of received single-bit error corrected

GFP super-block count

EDFCG-- Dropped Green frames-congestion

EDFCY-- Dropped Yellow frames-congestion

EINDB-- Incoming number of dropped frames-broadcast/multicast rate limit

TBS

EINDP-- Incoming number of dropped PAUSE frames TBS

EINFU-- Incoming number of unicast frames TBS

EINFM-- Incoming number of multicast frames

EINFB-- Incoming number of broadcast frames

TBS

EONFU-- Outgoing number of unicast frames

EONFM-- Outgoing number of multicast frames

EONFB-- Outgoing number of broadcast frames

EINCP-- Number of frames trapped to CPU

EOCP-- Number of frames received from CPU

ALL-- All of the above monitored types

TBS

15-Min

Range

Notes:

1. Counter can overflow.

B - 5 4

TBS

1-Day

Range

365-372-300

Issue 8.0 September 2006

Ethernet Performance Monitoring Parameters

: Performance Monitoring

2. Does not apply to the LNW71 circuit pack.

Enabling/disabling

Performance monitoring is enabled/disabled via the WaveStar

CIT.

From the System View menu, select

Provision > Prov PM Ports

, then navigate to the port.

Ethernet parameters

DMX monitors several Ethernet parameters.

Ethernet dropped frames (congestion) (EDFC)

The EDFC parameter counts the number of incoming Ethernet frames dropped at a specific LAN/WAN port due to buffer overflow. Buffer overflow occurs when the network is congested.

For LNW70, this count represents the number of frames that could not be transmitted on the specified port because of congestion. For all other circuit packs, this count represents the number of frames that could not be received on the specified port because of congestion. This parameter does not apply to the LNW74 circuit pack.

Ethernet dropped frames (errors) (EDFE)

The EDFE parameter counts the number of incoming Ethernet frames dropped at a LAN/WAN port due to a frame check sequence (FCS) error or another defect in the frame.

For the LNW73: this count represents frames received with invalid CRC on data port. For VCG, this count represents dropped GFP super-block frames due to CRC error.

This parameter is valid only for VCGs - not LAN ports.

Ethernet dropped frames (policer) (EDFP)

This parameter is valid only for VCGs - not LAN ports. This parameter applies only to the LNW66/67/68 circuit packs.

Ethernet incoming number of bytes (EINB)

For the LNW73, ordered sets are not included in the count. This parameter is valid for the data ports only, not VCGs.

This parameter monitors the incoming number of bytes

Ethernet incoming number of frames (EINF)

This parameter monitors the incoming number of frames.

365-372-300

Issue 8.0 September 2006

B - 5 5

Ethernet Performance Monitoring Parameters

: Performance Monitoring

Ethernet outgoing number of bytes (EONB)

This parameter monitors the outgoing number of bytes. For the

LNW73, ordered sets are not included in the count. This parameter is valid for the data ports only, not VCGs.

Ethernet parameters for

LNW73 only

DMX monitors the following Ethernet parameters on the LNW73 pack.

Count of invalid transmission words received (INTXWD)

This parameter is valid for data ports only, not VCGs.

Count of instances for loss of signal detected (LOS)

This parameter is valid for data ports only, not VCGs.

Count of instances for sync loss detected (LSYNC)

This parameter is valid for data ports only, not VCGs.

Count of disparity errors received (DSPERR)

This parameter is valid for data ports only, not VCGs.

Count of received overflow frames dropped (RFOVD)

This parameter is valid for data ports only, not VCGs.

Count of transmit overflow frames dropped (TFOVD)

This parameter is valid for data ports only, not VCGs.

Count of transmitted frames with CRC errors (TFCRC)

This parameter is valid for data ports only, not VCGs.

Count of transmitted 10B_ERR errors (T10BERR)

This parameter is valid for data ports only, not VCGs.

Count of received single-bit error corrected GFP headers

(RCORH)

This parameter is valid for VCGs only, not data ports.

Count of received uncorrected multi-bit error GFP headers

(RCRCH)

This parameter is valid for VCGs only, not data ports.

B - 5 6

365-372-300

Issue 8.0 September 2006

Ethernet Performance Monitoring Parameters

: Performance Monitoring

Count of received single-bit error corrected GFP super-blocks

(RCORF)

This parameter is valid for VCGs only, not data ports.

Ethernet parameters for

LNW70 only

DMX monitors the following Ethernet parameters on the LNW70 pack.

Ethernet dropped green frames-- congestion (EDFCG)

This parameter the number of green frames that could not be transmitted due to congestion.

Ethernet dropped yellow frames-- congestion (EDFCG)

This parameter the number of yellow frames that could not be transmitted due to congestion.

Ethernet number of dropped frames-broadcast/multicast rate limit

(EINDB)

Ethernet number of incoming unicast frames (EINFU)

This parameter is valid for data ports only, not VCGs.

Ethernet incoming number of multicast frames (EINFM)

Multicast frames are frames where the destination address has the group address bit set to 1.

Ethernet incoming number of broadcast frames (EINFB)

Broadcast frames are frames where the destination address is all 1s.

Ethernet outgoing number of unicast frames (EONFU)

Ethernet outgoing number of broadcast frames (EINFB)

Broadcast frames are frames where the destination address is all 1s.

Ethernet number of frames trapped to CPU (EINCP)

Broadcast frames are frames where the destination address is all 1s.

Ethernet number for frames received from CPU (EOCP)

All of the above monitored parameters (ALL)

365-372-300

Issue 8.0 September 2006

B - 5 7

: Performance Monitoring

SNMP Parameters and Traps

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

DMX supports the following functionality through the Simple Network

Management Protocol (SNMP) interface:

• SONET (DS1/E1 and DS3/EC-1) performance monitoring management information base (MIB) module that specifies

SONET performance monitoring and traps using the SONET

15-minute (Standard- RFC2558

) and 24-hour (Private) registers.

• Private Ethernet performance monitoring MIB module that specifies Ethernet performance monitoring and traps using the

SONET 15-minute and 24-hour registers.

• Standard Ethernet interface MIB module that specifies Ethernet port performance monitoring counts using the Ethernet continuous counter (RFC2863)

• Standard Ethernet performance monitoring MIB module for the

Ethernet-like Interface Types that specifies additional Ethernet port performance monitoring counts using the Ethernet continuous counter (RFC2358/RFC2665)

• Private VCG MIB module that specifies VCG traps

• Private MIB module for equipment information and equipment traps.

The MIB files are stored on the user’s pc in folder

C:/Program Files/Lucent Technologies/WaveStar CIT/generics/

dmx/3.1.0/p.

B - 5 8

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Standard SONET PM MIB module

DMX supports a S

TANDARD

SONET PM MIB module defined in IETF

RFC2558. This module defines SONET PM parameters for the SONET physical medium, section layer, line, path and tributary. This Standard

SONET PM MIB module applies to individual SONET ports and tributaries.

Standard SONET PM MIB Module Parameters

The following table shows the Standard SONET PM MIB module parameters.

Group/Table

SonetMedium Group

SonetSectionCurrent Table

Parameters

sonetMediumType

(READ-ONLY)

Definition

value: “sonet” sonetMediumTimeElapsed sonetMediumValidIntervals seconds since the beginning of current period number of previous 15-min intervals for which data was collected (usually 32) sonetMediumLineCoding

(READ-ONLY) sonetMediumLineType

(READ-ONLY) sonetMediumCircuitIdentifier

(READ-ONLY) line coding,e.g., B3ZS short range single mode or long range single mode circuit ID sonetMediumInvalidIntervals number of intervals for which no data is available (usually 0) sonetMediumLoopbackConfig

(READ-ONLY) no loopback, facility loopback or terminalloopback sonetSectionCurrentStatus Current sonetSectionCurrentESs Current sonetSectionCurrentSESs sonetSectionCurrentSEFSs sonetSectionCurrentCVs

Current

365-372-300

Issue 8.0 September 2006

B - 5 9

SNMP Parameters and Traps

: Performance Monitoring

Group/Table Parameters

SonetSectionInterval Table

SonetLineCurrent Table sonetSectionIntervalESs 15 minute sonetSectionIntervalSEFSs sonetSectionIntervalCVs

15 minute

15 minute sonetSectionIntervalValidData 15 minute sonetLineCurrentStatus Current sonetLineCurrentESs sonetLineCurrentSESs sonetLineCurrentCVs sonetLineCurrentUASs

Current

SonetLineInterval Table

SonetFarEndLineCurrent Table sonetLineIntervalESs sonetLineIntervalSESs sonetLineIntervalCVs sonetLineIntervalUASs sonetLineIntervalValidData sonetFarEndLineCurrentESs sonetFarEndLineCurrentSESs sonetFarEndLineCurrentCVs sonetFarEndLineCurrentUASs

15 minute

Current

SonetFarEndLineInterval Table sonetFarEndLineIntervalESs sonetFarEndLineIntervalSESs sonetFarEndLineIntervalCVs

15 minute

15 minute sonetFarEndLineIntervalUASs 15 minute sonetFarEndLineIntervalValidData 15 minute

Definition

B - 6 0

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Group/Table

SonetPathCurrent Table

SonetPathInterval Table

SonetFarEndPathCurrent Table

SonetFarEndPathInterval Table

SonetVTCurrent Table

Parameters

sonetPathCurrentWidth sonetPathCurrentStatus sonetPathCurrentESs sonetPathCurrentSESs sonetPathCurrentCVs sonetPathCurrentUASs sonetPathIntervalNumber sonetPathIntervalESs sonetPathIntervalSESs sonetPathIntervalCVs sonetPathIntervalUASs sonetPathIntervalValidData sonetFarEndPathCurrentESs sonetFarEndPathCurrentSESs sonetFarEndPathCurrentCVs sonetFarEndPathCurrentUASs sonetFarEndPathIntervalNumber sonetFarEndPathIntervalESs sonetFarEndPathIntervalSESs sonetFarEndPathIntervalCVs sonetFarEndPathIntervalUASs

Current

15 minute

Current

15 minute

15 minute sonetFarEndPathIntervalValidData 15 minute sonetVTCurrentWidth Current

Definition

sonetVTCurrentStatus sonetVTCurrentESs sonetVTCurrentSESs sonetVTCurrentCVs sonetVTCurrentUASs

Current

365-372-300

Issue 8.0 September 2006

B - 6 1

SNMP Parameters and Traps

: Performance Monitoring

Group/Table

SonetVTInterval Table

SonetFarEndVTCurrent Table

SonetFarEndVTInterval Table

Parameters

sonetVTIntervalNumber sonetVTIntervalESs sonetVTIntervalSESs sonetVTIntervalCVs sonetVTIntervalUASs sonetVTIntervalValidData sonetFarEndVTCurrentESs sonetFarEndVTCurrentSESs sonetFarEndVTCurrentCVs sonetFarEndVTCurrentUASs sonetFarEndVTIntervalNumber sonetFarEndVTIntervalESs sonetFarEndVTIntervalSESs sonetFarEndVTIntervalCVs sonetFarEndVTIntervalUASs sonetFarEndVTIntervalValidData

15 minute

Current

15 minute

Definition

Private SONET Day PM MIB Module

DMX supports private SONET Day PM MIB Module. This module defines 24 hour SONET PM parameters for the SONET physical medium, section layer, line, path and tributary. This MIB module shall apply to individual SONET ports and tributaries.

Table

dmxSonetSectionDay Table

Parameters

dmxSonetSectionDayNumber dmxSonetSectionDayESs dmxSonetSectionDaySESs dmxSonetSectionDaySEFSs dmxSonetSectionDayCVs dmxSonetSectionDayValidData

B - 6 2

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Table

dmxSonetLineDay Table dmxSonetFarEndLineDay Table dmxSonetPathDay Table dmxSonetFarEndPathDay Table

Parameters

dmxSonetLineDayNumber dmxSonetLineDayESs dmxSonetLineDaySESs dmxSonetLineDayCVs dmxSonetLineDayUASs dmxSonetLineDayValidData dmxSonetFarEndLineDayNumber dmxSonetFarEndLineDayESs dmxSonetFarEndLineDaySESs dmxSonetFarEndLineDayCVs dmxSonetFarEndLineDayUASs dmxSonetFarEndLineDayValidData dmxSonetPathDayNumber dmxSonetPathDayESs dmxSonetPathDaySESs dmxSonetPathDayCVs dmxSonetPathDayUASs dmxSonetPathDayValidData dmxSonetFarEndPathDayNumber dmxSonetFarEndPathDayESs dmxSonetFarEndPathDaySESs dmxSonetFarEndPathDayCVs dmxSonetFarEndPathDayUASs dmxSonetFarEndPathDayValidData

365-372-300

Issue 8.0 September 2006

B - 6 3

SNMP Parameters and Traps

Table

dmxSonetVTDay Table dmxSonetFarEndVTDay Table

Parameters

dmxSonetVTDayNumber dmxSonetVTDayESs dmxSonetVTDaySESs dmxSonetVTDayCVs dmxSonetVTDayUASs dmxSonetVTDayValidData dmxSonetFarEndVTDayNumber dmxSonetFarEndVTDayESs dmxSonetFarEndVTDaySESs dmxSonetFarEndVTDayCVs dmxSonetFarEndVTDayUASs dmxSonetFarEndVTDayValidData

: Performance Monitoring

B - 6 4

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Alarm Identifiers for Alarm and Event Traps

In addition to standard SNMP traps, DMX supports the following five traps for all NE alarms: Alarms (dmxAlarm), Alarm Clears

(dmxAlarmCL), Standing Conditions (dmxStandingCond), Standing

Condition Clears (dmxStandingCondCL), and Transient Conditions

(dmxTransientCond).

365-372-300

Issue 8.0 September 2006

B - 6 5

SNMP Parameters and Traps

: Performance Monitoring

Standard DS1/E1 PM MIB Module

The following table shows the Standard DS1/E1 PM MIB tables and parameters defined in IETF RFC2495. This MIB module applies to individual DS1/E1 ports

B - 6 6

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

Dsx1ConfigEntry Table

: Performance Monitoring

Parameters

dsx1LineIndex dsx1TimeElapsed dsx1ValidIntervals dsx1LineType dsx1LineCoding dsx1SendCode dsx1CircuitIdentifier dsx1LoopbackConfig dsx1LineStatus dsx1SignalMode dsx1TransmitClockSource dsx1Fdl dsx1InvalidIntervals dsx1LineLength dsx1LineStatusLastChange dsx1LineStatusChangeTrapEnable dsx1LoopbackStatus dsx1Ds1ChannelNumber dsx1Channelization

Description

ifIndex seconds since the beginning of current period number of previous 15-min intervals for which data was collected (usually 32) type of DS1/E1 line, e.g., E1 unframed line coding, e.g. B8ZS code being sent circuit ID: 0,...,255 loopback configuration bit mapped line status information signaling mode loop timing, local timing or through timing facilities data link capabilities number of intervals for which no data is available (usually 0) length of the DS1/E1 line in meters time this DS1/E1 entered its current line status state indicates whether dsx1LineStatusChange traps should be generated for this DS1/E1 current state of the loopback on the

DS1/E1 interface

0..28

DS1/E1 channelization: disabled, enabled DS0 or enabled DS1

365-372-300

Issue 8.0 September 2006

B - 6 7

SNMP Parameters and Traps

Table

Dsx1CurrentEntry Table

Dsx1IntervalEntry Table

Parameters

dsx1CurrentIndex dsx1CurrentESs dsx1CurrentSESs dsx1CurrentSEFSs dsx1CurrentUASs dsx1CurrentCSSs dsx1CurrentPCVs dsx1CurrentLESs dsx1CurrentBESs dsx1CurrentDMs dsx1CurrentLCVs dsx1IntervalIndex dsx1IntervalNumber dsx1IntervalESs dsx1IntervalSESs dsx1IntervalSEFSs dsx1IntervalUASs dsx1IntervalCSSs dsx1IntervalPCVs dsx1IntervalLESs dsx1IntervalBESs dsx1IntervalDMs dsx1IntervalLCVs dsx1IntervalValidData

: Performance Monitoring

Current

15 minute

Description

B - 6 8

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

Dsx1TotalEntry Table

Dsx1ChanMappingEntry Table

Dsx1FarEndCurrentEntry Table

Parameters

dsx1TotalIndex dsx1TotalESs dsx1TotalSESs dsx1TotalSEFSs dsx1TotalUASs dsx1TotalCSSs dsx1TotalPCVs dsx1TotalLESs dsx1TotalBESs dsx1TotalDMs dsx1TotalLCVs dsx1ChanMappedIfIndex dsx1FarEndCurrentIndex dsx1FarEndTimeElapsed dsx1FarEndValidIntervals dsx1FarEndCurrentESs dsx1FarEndCurrentSESs dsx1FarEndCurrentSEFSs dsx1FarEndCurrentUASs dsx1FarEndCurrentCSSs dsx1FarEndCurrentLESs dsx1FarEndCurrentPCVs dsx1FarEndCurrentBESs dsx1FarEndCurrentDMs dsx1FarEndInvalidIntervals

Current

: Performance Monitoring

Description

24 hour

DS1/E1 channel number ifIndex

Current

365-372-300

Issue 8.0 September 2006

B - 6 9

SNMP Parameters and Traps

: Performance Monitoring

Table

Dsx1FarEndIntervalEntry Table

Dsx1FarEndTotalEntry Table

Parameters

dsx1FarEndIntervalIndex dsx1FarEndIntervalNumber dsx1FarEndIntervalESs dsx1FarEndIntervalSESs dsx1FarEndIntervalSEFSs dsx1FarEndIntervalUASs dsx1FarEndIntervalCSSs dsx1FarEndIntervalLESs dsx1FarEndIntervalPCVs dsx1FarEndIntervalBESs dsx1FarEndIntervalDMs dsx1FarEndIntervalValidData dsx1FarEndTotalIndex dsx1FarEndTotalESs dsx1FarEndTotalSESs dsx1FarEndTotalSEFSs dsx1FarEndTotalUASs dsx1FarEndTotalCSSs dsx1FarEndTotalLESs dsx1FarEndTotalPCVs dsx1FarEndTotalBESs dsx1FarEndTotalDMs

24 hour

15 minute

24 hour

Description

Standard DS1 Traps

DMX supports the following DS1 trap.

Table Parameters

ds1Traps dsx1LineStatusChange

B - 7 0

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

Dsx3ConfigEntry

: Performance Monitoring

Standard DS3/EC-1 PM MIB Module

The following table shows the Standard DS3/EC-1 PM MIB tables and parameters defined in IETF RFC2496. This MIB module applies to individual DS3/EC-1 ports

Parameters

dsx3LineIndex dsx3TimeElapsed dsx3ValidIntervals dsx3LineType dsx3LineCoding dsx3SendCode dsx3CircuitIdentifier dsx3LoopbackConfig dsx3LineStatus dsx3TransmitClockSource dsx3InvalidIntervals dsx3LineLength dsx3LineStatusLastChange dsx3LineStatusChangeTrapEnable dsx3LoopbackStatus dsx3Channelization dsx3Ds1ForRemoteLoop

Description

ifIndex seconds since the beginning of current period number of previous 15-min intervals for which data was collected

(usually 32) type of DS3/E3 line line coding, e.g. B3ZS code being sent

N/A - always “0” loopback configuration bit mapped line status information loop timing, local timing or through timing number of intervals for which no data is available (usually 0) length of the DS3/E3 line in meters time this DS3/E3 entered its current line status state indicates whether dsx3LineStatusChange traps should be generated for this DS3/E3 - read only current state of the loopback on the

DS3/E3 interface

“enabled DS1” if CP is TMUX, otherwise “disabled” not supported, always “0”

365-372-300

Issue 8.0 September 2006

B - 7 1

SNMP Parameters and Traps

Table

Dsx3CurrentEntry

Parameters

dsx3CurrentIndex dsx3CurrentPESs dsx3CurrentPSESs dsx3CurrentSEFSs dsx3CurrentUASs dsx3CurrentLCVs dsx3CurrentPCVs dsx3CurrentLESs dsx3CurrentCCVs dsx3CurrentCESs dsx3CurrentCSESs

: Performance Monitoring

Description

Current

Current - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

Current - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

Current

Current - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

Current

Current - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0”

Current - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0”

Current - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0”

B - 7 2

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

Dsx3IntervalEntry

Parameters

dsx3IntervalIndex dsx3IntervalNumber dsx3IntervalPESs dsx3IntervalPSESs dsx3IntervalSEFSs dsx3IntervalUASs dsx3IntervalLCVs dsx3IntervalPCVs dsx3IntervalLESs dsx3IntervalCCVs dsx3IntervalCESs dsx3IntervalCSESs dsx3IntervalValidData

: Performance Monitoring

Description

Current

15 minute

15 minute - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

15 minute - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

15 minute

15 minute - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

15 minute

15 minute - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0”

15 minute - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0”

15 minute - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0”

15 minute

365-372-300

Issue 8.0 September 2006

B - 7 3

SNMP Parameters and Traps

Table

Dsx3TotalEntry

Dsx3FarEndConfigEntry

: Performance Monitoring

Parameters

dsx3TotalIndex dsx3TotalPESs dsx3TotalPSESs dsx3TotalSEFSs dsx3TotalUASs dsx3TotalLCVs dsx3TotalPCVs dsx3TotalLESs dsx3TotalCCVs dsx3TotalCESs dsx3TotalCSESs dsx3FarEndLineIndex dsx3FarEndEquipCode dsx3FarEndLocationIDCode dsx3FarEndFrameIDCode dsx3FarEndUnitCode dsx3FarEndFacilityIDCode

Description

24 hour

24 hour - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

24 hour - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

24 hour

24 hour - valid only if

ENT-rr:

fmt=PBIT, otherwise “0”

24 hour

24 hour - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0”

24 hour - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0”

24 hour - valid only if

ENT-rr:

fmt=CPBIT, otherwise

“0” not supported not supported not supported not supported not supported not supported

B - 7 4

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

Dsx3FarEndCurrentEntry

Dsx3FarEndIntervalEntry

: Performance Monitoring

Parameters

dsx3FarEndCurrentIndex dsx3FarEndTimeElapsed dsx3FarEndValidIntervals dsx3FarEndCurrentCESs dsx3FarEndCurrentCSESs dsx3FarEndCurrentCCVs dsx3FarEndCurrentUASs dsx3FarEndInvalidIntervals dsx3FarEndIntervalIndex dsx3FarEndIntervalNumber dsx3FarEndIntervalCESs dsx3FarEndIntervalCSESs dsx3FarEndIntervalCCVs dsx3FarEndIntervalUASs dsx3FarEndIntervalValidData

Description

not supported (moved to Private

DS3 PM MIB) not supported (moved to Private

DS3 PM MIB)

365-372-300

Issue 8.0 September 2006

B - 7 5

SNMP Parameters and Traps

: Performance Monitoring

Table

Dsx3FarEndTotalEntry

Parameters

dsx3FarEndTotalIndex dsx3FarEndTotalCESs dsx3FarEndTotalCSESs dsx3FarEndTotalCCVs dsx3FarEndTotalUASs

Description

not supported (moved to Private

DS3 PM MIB) not supported (moved to Private

DS3 PM MIB)

DS3 Traps

Standard DS3 Traps

DMX supports the following DS3 trap.

Table Parameters

dsx3LineStatusChange

B - 7 6

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Table

DmxDmxDsx3CurrentEntry

DmxDmxDsx3IntervalEntry

DmxDmxDsx3TotalEntry

Private DS3/EC-1 PM MIB Module

DMX supports private DS3/EC-1 PM MIB Module. This MIB module shall apply to individual DS3/EC-1 ports and tributaries..

Parameters

dmxDsx3CurrentIndex dmxDsx3CurrentFMESs dmxDsx3CurrentFMSESs dmxDsx3CurrentFMCVs dmxDsx3IntervalIndex dmxDsx3IntervalFMESs dmxDsx3IntervalFMSESs dmxDsx3IntervalFMCVs

Description

Current

Current - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0”

Current - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0””

Current - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0”

Interval

Interval - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0”

Interval - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0””

Interval - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0” dsx3DMXIntervalValidData dmxDsx3TotalIndex dmxDsx3TotalFMESs dmxDsx3TotalFMSESs dmxDsx3TotalFMCVs

Total

Total - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0”

Total - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0””

Total - valid only if

ENT-rr

:fmt=FMBIT, otherwise “0”

365-372-300

Issue 8.0 September 2006

B - 7 7

SNMP Parameters and Traps

: Performance Monitoring

Table

DmxDsx3FarEndCurrentEntry

DmxDsx3FarEndIntervalEntry

DmxDsx3FarEndTotalEntry

Parameters

dmxDsx3FarEndCurrentIndex dmxDsx3FarEndTimeElapsed dmxDsx3FarEndValidIntervals dmxDsx3FarEndCurrentCFMESs dmxDsx3FarEndCurrentCFMSESs dmxDsx3FarEndCurrentCFMCVs dmxDsx3FarEndCurrentUASs

Description

Current

Current - far end PM based on

C-bit, F-bit and M-bit errors

Current - far end PM based on

C-bit, F-bit and M-bit errors

Current - far end PM based on

C-bit, F-bit and M-bit errors

Current - far end PM based on

C-bit, F-bit and M-bit errors

Current

15 minute dmxDsx3FarEndInvalidIntervals dmxDsx3FarEndIntervalIndex dmxDsx3FarEndIntervalNumber dmxDsx3FarEndIntervalCFMESs dmxDsx3FarEndIntervalCFMSESs dmxDsx3FarEndIntervalCFMCVs

15 minute

15 minute - far end PM based on

C-bit, F-bit and M-bit errors

15 minute - far end PM based on

C-bit, F-bit and M-bit errors

15 minute - far end PM based on

C-bit, F-bit and M-bit errors dmxDsx3FarEndIntervalUASs

15 minute - far end PM based on

C-bit, F-bit and M-bit errors dmxDsx3FarEndIntervalValidData 15 minute dmxDsx3FarEndTotalIndex dmxDsx3FarEndTotalCFMESs

24 hour

24 hour - far end PM based on

C-bit, F-bit and M-bit errors dmxDsx3FarEndTotalCFMSESs dmxDsx3FarEndTotalCFMCVs dmxDsx3FarEndTotalUASs

24 hour - far end PM based on

C-bit, F-bit and M-bit errors

24 hour - far end PM based on

C-bit, F-bit and M-bit errors

24 hour - far end PM based on

C-bit, F-bit and M-bit errors

B - 7 8

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Private Ethernet PM MIB module

DMX supports a private Ethernet PM MIB module for Ethernet traps and for retrieving Ethernet PM parameters. This private Ethernet PM

MIB module applies to individual Fast Ethernet and Gigabit Ethernet ports.

Private Ethernet PM MIB Module Parameters

The following table shows the private Ethernet PM MIB module parameters.

Object Parameter

dmxEthPmonTypeCurrent port type dmxEthPmonCurrentEinf dmxEthPmonCurrentEdfc dmxEthPmonCurrentEonb dmxEthPmonCurrentEonf dmxEthPmonIntervalIndex dmxEthPmonTypeInterval dmxEthPmonIntervalEinb dmxEthPmonIntervalEinf dmxEthPmonIntervalEdfc dmxEthPmonIntervalEdfe dmxEthPmonIntervalEonb dmxEthPmonIntervalEonf dmxEthPmonDayIndex dmxEthPmonDayType

Incoming number of frames (EINF)

Dropped frames: congestion (EDFC)

Outgoing number of bytes (EONB)

Outgoing number of frames (EONF)

15 minute bucket index port type

Incoming number of bytes (EINB)

Incoming number of frames (EINF)

Dropped frames: congestion (EDFC)

Dropped frames: errors (EDFE)

Outgoing number of bytes (EONB)

Outgoing number of frames (EONF) day index port type

Definition

FE or GbE port

Total Bytes Received

Frames Received or Total

Frames Received

Dropped Frames

CRC Error + Oversize Frames +

Fragments + Jabber + MAC Rx

Error a

Bytes Sent

Frames Sent

1 to 32

FE or GbE port

Total Bytes Received: 15 minute

Frames Received or Total

Frames Received: 15 minute

Dropped Frames: 15 minute

CRC Error + Oversize Frames

+ Fragments + Jabber + MAC

Rx Error: 15 minute

Bytes Sent: 15 minute

Frames Sent: 15 minute current or previous 24 hour period

FE or GbE port

365-372-300

Issue 8.0 September 2006

B - 7 9

SNMP Parameters and Traps

: Performance Monitoring

Object Parameter

dmxEthPmonDayEinb Incoming number of bytes (EINB) dmxEthPmonDayEinf dmxEthPmonDayEdfc

Incoming number of frames (EINF)

Dropped frames: congestion (EDFC) dmxEthPmonDayEdfe Dropped frames: errors (EDFE) dmxEthPmonDayEonb dmxEthPmonDayEonf dmxEthPmonCurrentEdfb dmxEthPmonCurrentEdfcg dmxEthPmonCurrentEdfcy dmxEthPmonCurrentEindp dmxEthPmonCurrentEincp dmxEthPmonCurrentEinfb dmxEthPmonCurrentEinfm dmxEthPmonCurrentEinfu dmxEthPmonCurrentEocp dmxEthPmonCurrentEonfb dmxEthPmonCurrentEonfm dmxEthPmonCurrentEonfu dmxEthPmonIntervalEdfb

Outgoing number of bytes (EONB)

Outgoing number of frames (EONF) dropped frames - broadcast rate limit

(EDFB) dropped green frames - congestion

(EDFCG) dropped yellow frames - congestion

(EDFCY) dropped PAUSE frames (EINDP) number of frames trapped to CPU

(EINCP) incoming number of broadcast frames

(EINFB) incoming number of multicast frames

(EINFM) incoming number of unicast frames

(EINFU) number of frames received from CPU

(EOCP) outgoing number of broadcast frames

(EONFB) outgoing number of multicast frames

(EONFM) outgoing number of unicast frames

(EONFU) dropped frames - broadcast rate limit

(EDFB)

B - 8 0

Definition

Total Bytes Received: 24 hour

Frames Received or Total

Frames Received: 24 hour

Dropped Frames: 24 hour

CRC Error + Oversize Frames

+ Fragments + Jabber + MAC

Rx Error: 24 hour

Bytes Sent: 24 hour

Frames Sent: 24 hour

LNW70 only

15 minute - LNW70 only

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Object Parameter

dmxEthPmonIntervalEdfcg dropped green frames - congestion

(EDFCG) dmxEthPmonIntervalEdfcy dmxEthPmonIntervalEindp dmxEthPmonIntervalEincp dmxEthPmonIntervalEinfb dropped yellow frames - congestion

(EDFCY) dropped PAUSE frames (EINDP) number of frames trapped to CPU

(EINCP) incoming number of broadcast frames

(EINFB) dmxEthPmonIntervalEinfm dmxEthPmonIntervalEinfu dmxEthPmonIntervalEocp dmxEthPmonIntervalEonfb dmxEthPmonIntervalEonfm dmxEthPmonIntervalEonfu dmxEthPmonDayEdfb dmxEthPmonDayEdfcg dmxEthPmonDayEdfcy dmxEthPmonDayEindp dmxEthPmonDayEincp dmxEthPmonDayEinfb dmxEthPmonDayEinfm incoming number of multicast frames

(EINFM) incoming number of unicast frames

(EINFU) number of frames received from CPU

(EOCP) outgoing number of broadcast frames

(EONFB) outgoing number of multicast frames

(EONFM) outgoing number of unicast frames

(EONFU) dropped frames - broadcast rate limit

(EDFB) dropped green frames - congestion

(EDFCG) dropped yellow frames - congestion

(EDFCY) dropped PAUSE frames (EINDP) number of frames trapped to CPU

(EINCP) incoming number of broadcast frames

(EINFB) incoming number of multicast frames

(EINFM)

365-372-300

Issue 8.0 September 2006

Definition

15 minute - LNW70 only

24 hour - LNW70 only

B - 8 1

SNMP Parameters and Traps

: Performance Monitoring

Object Parameter

dmxEthPmonDayEinfu incoming number of unicast frames

(EINFU) dmxEthPmonDayEocp dmxEthPmonDayEonfb dmxEthPmonDayEonfm dmxEthPmonDayEonfu number of frames received from CPU

(EOCP) outgoing number of broadcast frames

(EONFB) outgoing number of multicast frames

(EONFM) outgoing number of unicast frames

(EONFU)

Definition

24 hour - LNW70 only

24 hour - LNW70 only a.

The definition of Dropped Frames is based on the counters supported by the Galnet devices. The definition of this parameter for the private line board, which doesn’t have the Galnet devices, may differ.

Trap Object

dmxIncFeLanLos dmxIncFeLanLosClr dmxIncFeLanAnm dmxIncFeLanAnmClr dmxIncGeLanLos dmxIncGeLanLosClr

Private Ethernet PM MIB Module Traps

The following table shows the private Ethernet PM MIB module traps.

Definition

Loss of signal (LOS) on FE LAN port

LOS clear on FE LAN port

Auto-Negotiation Mismatch (ANM) on FE LAN port

ANM clear on FE LAN port

Loss of signal (LOS) on GbE LAN port

LOS clear on GbE LAN port dmxIncGeLanAnmClr dmxIncGeLanECV dmxIncGeLanECVClr dmxIncGeLanTEDFC dmxIncFeLanTEDFC dmxIncGeLanTEDFE dmxIncFeLanTEDFE

B - 8 2

ANM clear on GbE LAN port

Excessive Code Violation on GbE LAN port

Excessive Code Violation clear on GbE LAN port

Dropped frames due to congestion TCA on GbE LAN port

Dropped frames due to congestion TCA on FE LAN port

Dropped frames due to errors TCA on GbE LAN port

Dropped frames due to errors TCA on FE LAN port

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Private Ethernet PM MIB module QOS Parameters

DMX supports private Ethernet PM MIB module for retrieving QOS parameters. This private Ethernet PM MIB module applies to individual Fast Ethernet and Gigabit Ethernet ports for the LNW70 pack.

Private Ethernet PM MIB Module QOS Parameters

The following table shows the private Ethernet PM MIB module QOS parameters.

Object Parameter

dmxEthPmonQosCurrentTagid

VLANid in the range 1-4093 except for

PORT and COSPORT mode which has a value of “NA” dmxEthPmonQosCurrentCos Class of Service in the range 0-3 dmxEthPmonQosCurrentQibg Incoming bytes marked green (QIB-G) dmxEthPmonQosCurrentQipg Incoming packets marked green (QIP-G) dmxEthPmonQosCurrentQiby Incoming bytes marked yellow (QIB-Y) dmxEthPmonQosCurrentQipy Incoming packets marked yellow (QIP-Y) dmxEthPmonQosCurrentQibr

Incoming bytes marked red (dropped)

(QIB-R) dmxEthPmonQosCurrentQipr

Incoming packets marked red (dropped)

(QIP-R ) dmxEthPmonQosIntervalIndex 15 minute bucket index 1 to 32 dmxEthPmonQosIntervalTagid

VLANid in the range 1-4093 except for

PORT and COSPORT modewhich has a value of “NA”

Class of Service in the range 0-3

15 minute dmxEthPmonQosIntervalCos 15 minute dmxEthPmonQosIntervalQibg Incoming bytes marked green (QIB-G) 15 minute dmxEthPmonQosIntervalQipg Incoming packets marked green (QIP-G) 15 minute dmxEthPmonQosIntervalQiby Incoming bytes marked yellow (QIB-Y) 15 minute dmxEthPmonQosIntervalQipy Incoming packets marked yellow (QIP-Y) 15 minute dmxEthPmonQosIntervalQibr dmxEthPmonQosIntervalQipr

Incoming bytes marked red (dropped)

(QIB-R)

Incoming packets marked red (dropped)

(QIP-R )

15 minute

Definition

365-372-300

Issue 8.0 September 2006

B - 8 3

SNMP Parameters and Traps

: Performance Monitoring

Object Parameter

dmxEthPmonQosDayIndex dmxEthPmonQosDayTagid dmxEthPmonQosDayCos dmxEthPmonQosDayQibg dmxEthPmonQosDayQipg dmxEthPmonQosDayQiby dmxEthPmonQosDayQipy dmxEthPmonQosDayQibr dmxEthPmonQosDayQipr day index

VLANid in the range 1-4093 except for

PORT and COSPORT modewhich has a value of “NA”

Class of Service in the range 0-3

24 hour

Incoming bytes marked green (QIB-G) 24 hour

Incoming packets marked green (QIP-G) 24 hour

Incoming bytes marked yellow (QIB-Y)

Incoming packets marked yellow (QIP-Y)

Incoming bytes marked red (dropped)

(QIB-R)

Incoming packets marked red (dropped)

(QIP-R )

Definition

current or previous 24 hour period

24 hour

B - 8 4

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Fibre

Channel/ESCON/FICON private MIB module

DMX supports a private Fibre Channel/ESCON/FICON PM MIB module for retrieving Fibre Channel/ESCON/FICON PM parameters.

This private MIB module shall apply to individual ports for the

LNW73 circuit pack.

Private FC/ESCON/FICON MIB Module PM QOS Parameters

The following table shows the private Ethernet PM MIB module QOS parameters.

Table

dmxPortStatCountCurrentTable

Object Parameter

dmxPortStatCountCurrentRx

Elements dmxPortStatCountCurrentRx

Objects

The number of octets or bytes that have been received by this port. (EINB).

Note: for Fibre Channel, ordered sets are not included in the count.

The number of frames/packets that have been received by this port. (EINF)

Note: A Fibre Channel frame starts with

SOF and ends with EOF dmxPortStatCountCurrentInv alidCRC dmxPortStatCountCurrentInv alidTxWords dmxPortStatCountCurrentLos sofSignal dmxPortStatCountCurrentLos sofSynchronization dmxPortStatCountCurrentEnc odingDisparityErrors dmxPortStatCountCurrentTx

Elements dmxPortStatCountCurrentTx

Objects

Count of frames received with invalid

CRC (EDFE)

Count of invalid transmission words received at this port (INTXWD)

Count of instances of signal loss detected at port (LOS)

Count of instances of synchronization

(LSYNC)

Count of disparity errors received at this port (DSPERR)

The number of octets or bytes that have been transmitted by this port. (EONB)

Note: for Fibre Channel, ordered sets are not included in the count.

The number of frames/packets/ IOs/etc. that have been transmitted by this port.

(EONF) Note: A Fibre Channel frame starts with SOF and ends with EOF

Definition

365-372-300

Issue 8.0 September 2006

B - 8 5

SNMP Parameters and Traps

: Performance Monitoring

Table Object Parameter

dmxPortStatCountCurrentRx

OverflowFramesDropped

Count of received overflow frames dropped (RFOVD) dmxPortStatCountCurrentTx

OverflowFramesDropped dmxPortStatCountCurrentTxF ramesCRCErrors dmxPortStatCountCurrentTx1

0BERRErrors dmxPortStatCountIntervalTable dmxPortStatCountIntervalInd ex

Count of transmit overflow frames dropped (TFOVD)

Count of transmitted frames with CRC errors (TFCRC)

Count of transmitted 10B_ERR errors

(T10BERR)

15 minute bucket index dmxPortStatCountIntervalRx

Elements dmxPortStatCountIntervalRx

Objects

The number of octets or bytes that have been received by this port. (EINB).

Note: for Fibre Channel, ordered sets are not included in the count.

The number of frames/packets that have been received by this port. (EINF)

Note: A Fibre Channel frame starts with

SOF and ends with EOF

Count of frames received with invalid

CRC (EDFE) dmxPortStatCountIntervalInv alidCRC dmxPortStatCountIntervalInv alidTxWords dmxPortStatCountIntervalLos sofSignal dmxPortStatCountIntervalLos sofSynchronization dmxPortStatCountIntervalEnc odingDisparityErrors dmxPortStatCountIntervalTx

Elements

Count of invalid transmission words received at this port (INTXWD)

Count of instances of signal loss detected at port (LOS)

Count of instances of synchronization

(LSYNC)

Count of disparity errors received at this port (DSPERR)

The number of octets or bytes that have been transmitted by this port. (EONB)

Note: for Fibre Channel, ordered sets are not included in the count.

Definition

1 to 32

15 minute

B - 8 6

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Table

dmxPortStatCountIntervalTx

Objects

Object Parameter

The number of frames/packets/ IOs/etc that have been transmitted by this port.

(EONF) Note: A Fibre Channel frame starts with SOF and ends with EOF dmxPortStatCountIntervalRx

OverflowFramesDropped dmxPortStatCountIntervalTx

FramesCRCErrors dmxPortStatCountIntervalTx1

0BERRErrors dmxPortStatCountDayTable

Count of received overflow frames dropped (RFOVD)

Count of transmit overflow frames dropped (TFOVD)

Count of transmitted frames with CRC errors (TFCRC)

Count of transmitted 10B_ERR errors

(T10BERR)

Definition

15 minute dmxPortStatCountDayIndex day index current or previous 24 hour period dmxPortStatCountDayRxEle ments dmxPortStatCountDayRxObj ects dmxPortStatCountDayInvalid

CRC dmxPortStatCountDayInvalid

TxWords dmxPortStatCountDayLossof

Signal dmxPortStatCountDayLossof

Synchronization dmxPortStatCountDayEncodi ngDisparityErrors

The number of octets or bytes that have been received by this port. (EINB).

Note: for Fibre Channel, ordered sets are not included in the count.

The number of frames/packets that have been received by this port. (EINF)

Note: A Fibre Channel frame starts with

SOF and ends with EOF

Count of frames received with invalid

CRC (EDFE)

Count of invalid transmission words received at this port (INTXWD)

Count of instances of signal loss detected at port (LOS)

Count of instances of synchronization

(LSYNC)

Count of disparity errors received at this port (DSPERR)

24 hour

365-372-300

Issue 8.0 September 2006

B - 8 7

SNMP Parameters and Traps

: Performance Monitoring

Table

dmxPortStatCountDayTxEle ments

Object Parameter

The number of octets or bytes that have been transmitted by this port. (EONB)

Note: for Fibre Channel, ordered sets are not included in the count.

dmxPortStatCountDayTxObje cts

The number of frames/packets/ IOs/etc that have been transmitted by this port.

(EONF) Note: A Fibre Channel frame starts with SOF and ends with EOF

Count of received overflow frames dropped (RFOVD) dmxPortStatCountDayRxOve rflowFramesDropped dmxPortStatCountDayTxOve rflowFramesDropped dmxPortStatCountDayTxFra mesCRCErrors

Count of transmit overflow frames dropped (TFOVD)

Count of transmitted frames with CRC errors (TFCRC)

Count of transmitted 10B_ERR errors

(T10BERR) dmxPortStatCountDayTx10B

ERRErrors dmxVcgStatCountCurrentTable dmxVcgStatCountCurrentRx

Objects dmxVcgStatCountCurrentInv alidCRC dmxVcgStatCountCurrentTx

Objects dmxVcgStatCountCurrentRx

SingleBitErrCorrectedGFP dmxVcgStatCountCurrentRx

MultiBitUncorrectedGFP dmxVcgStatCountCurrentRx

SingleBitErrCorrectedGFPSu perblk

The number of frames/packets that have been received by this port

Count of frames received with invalid

CRC (EDFE)

The number of frames/packets that have been transmitted by this port

Count of received single-bit error corrected GFP header count (RCORH).

Count of received uncorrected multi-bit error GFP header count (RCRCH).

Count of received single-bit error corrected GFP super-block count

(RCORF).

dmxVcgStatCountIntervalTable dmxVcgStatCountIntervalInd ex dmxVcgStatCountIntervalRx

Objects

15 minute bucket index

The number of frames/packets that have been received by this port

Definition

24 hour

15 minute

B - 8 8

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Table Object Parameter

dmxVcgStatCountIntervalInv alidCRC

Count of frames received with invalid

CRC (EDFE) dmxVcgStatCountIntervalTx

Objects dmxVcgStatCountIntervalRx

SingleBitErrCorrectedGFP dmxVcgStatCountIntervalRx

MultiBitUncorrectedGFP dmxVcgStatCountIntervalRx

SingleBitErrCorrectedGFPSu perblk

The number of frames/packets that have been transmitted by this port

Count of received single-bit error corrected GFP header count (RCORH).

Count of received uncorrected multi-bit error GFP header count (RCRCH).

Count of received single-bit error corrected GFP super-block count

(RCORF).

dmxVcgStatCountDayTable dmxVcgStatCountDayIndex day index dmxVcgStatCountDayRxObj ects dmxVcgStatCountDayInvalid

CRC

The number of frames/packets that have been received by this port

Count of frames received with invalid

CRC (EDFE) dmxVcgStatCountDayTxObje cts dmxVcgStatCountDayRxSing leBitErrCorrectedGFP dmxVcgStatCountDayRxMul tiBitUncorrectedGFP dmxVcgStatCountDayRxSing leBitErrCorrectedGFPSuperbl k

The number of frames/packets that have been transmitted by this port

Count of received single-bit error corrected GFP header count (RCORH).

Count of received uncorrected multi-bit error GFP header count (RCRCH).

Count of received single-bit error corrected GFP super-block count

(RCORF).

Definition

15 minute

24 hour

Private FC/ESCON/Ficon PM MIB Module Traps

The following table shows the private Ethernet PM MIB module traps.

These traps are onlt supported on the LNW73 pack.

dmxAlarmId Parameter

dmxPortStatInc1GfcLos Loss of signal (LOS) on 1GFC port dmxPortStatInc1GfcLosClr LOS clear on 1GFC port

365-372-300

Issue 8.0 September 2006

B - 8 9

SNMP Parameters and Traps

: Performance Monitoring

dmxAlarmId Parameter

dmxPortStatInc2GfcLos Loss of signal (LOS) on 2GFC port dmxPortStatInc2GfcLosClr dmxPortStatIncEsconLos dmxPortStatIncEsconLosClr dmxPortStatIncFiconLos

LOS clear on ESCON port

Loss of signal (LOS) on 2GFC port

LOS clear on ESCON port

Loss of signal (LOS) on FICON port dmxPortStatIncFiconLosClr dmxPortStatInc1GfcLsync dmxPortStatInc1GfcLsyncClr dmxPortStatInc2GfcLsync dmxPortStatInc2GfcLsyncClr dmxPortStatIncEsconLsync dmxPortStatIncEsconLsyncClr dmxPortStatIncFiconLsync dmxPortStatIncFiconLsyncClr dmxPortStatCount1GfcTINTXWD dmxPortStatCount2GfcTINTXWD dmxPortStatCountFiconTINTXWD dmxPortStatCountEsconTINTXWD

LOS clear on FICON port inc. Loss of Synch (LSYNC) on 1GFC port

LSYNC clear on 1GFC port inc. Loss of Synch (LSYNC) on 2GFC port

LSYNC clear on ESCON port inc. Loss of Synch (LSYNC) on 2GFC port

LSYNC clear on ESCON port inc. Loss of Synch (LSYNC) on FICON port

LSYNC clear on FICON port

Invalid transmission words TCA received at this 1GFC port

Invalid transmission words TCA received at this 2GFC port

Invalid transmission words TCA received at this FICON port

Invalid transmission words TCA received at this ESCON port

Standard Ethernet interface

MIB module (RFC2863)

DMX supports the standard Ethernet interface MIB module defined in

RFC2863. This module defines Ethernet traps and retrievable Ethernet port and PM parameters. This MIB module applies to individual Fast

Ethernet and Gigabit Ethernet ports.

B - 9 0

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps ifDescr

Object

: Performance Monitoring

Standard Ethernet interface MIB Module Parameters

The following table shows the standard Ethernet interface MIB module parameters.

Definition

Interface description (mfg, product, version) ifSpeed ifAdminStatus ifOperStatus ifLastChange ifInOctets

IfInUcastPkts ifInMulticastPkts ifInBroadcastPkts ifInErrors

Interface maximum rate (bps) - for GbE circuit pack, this is

“1,000,000,000”, for FE circuit pack, value is based on value of the line rate parameter. If the line rate is 10M, ifSpeed value is “10,000,000”. If the line rate parameter is 100M, ifSpeed value is “100,000,000”.

Administration status (up, down or testing) (read only). Value is always

“up”.

Operational status (up, down, testing, unknown, dormant, notPresent or lowerLayerDown). If board/port is removed, value is “notPresent”. If there is an existing alarm on the port, i.e., Loss of signal (LOS) or

Auto-Negotiation Mismatch (ANM) on the port, then the value is “down”, else the value is “up”.

TimeTicks since last re-initialization

Total Bytes Received

Frames Received: Broadcast Frames Received - Multicast Frames

Received

Multicast Frames Received

Broadcast Frames Received

CRC Error + Oversize Frames + Fragments + Jabber + MAC Rx Error

365-372-300

Issue 8.0 September 2006

B - 9 1

SNMP Parameters and Traps

: Performance Monitoring

Object Definition

ifOutOctets

IfOutUcastPkts ifOutMulticastPkts ifOutBroadcastPkts ifOutErrors ifName ifHCInOctets ifHCInUcastPkts ifHCInMulticastPkts ifHCInBroadcastPkts

Bytes Sent

Frames Sent - Out Multicast Frames - Out Broadcast Frames

Out Multicast Frames

Out Broadcast Frames

(always 0) (not supported in this release)

Interface name - (always set to NULL)

Total Bytes Received

Frames Received: Broadcast Frames Received - Multicast Frames

Received

Multicast Frames Received

Broadcast Frames Received

Frames Sent - Out Multicast Frames - Out Broadcast Frames ifHCOutUcastPkts ifHCOutBroadcastPkts ifLinkUpDownTrapEnable ifHighSpeed ifPromiscuousMode

Out Broadcast Frames

Traps enabled or disabled - DMX, Metropolis

DMXpress and

Metropolis

DMX supports READ-ONLY

Interface speed (Mbps) - for GbE circuit pack, this is “1,000”, for FE circuit pack, value is based on line rate parameter. If the line rate is 10M,

ifSpeed value is “10”. If the line rate is 100M, ifSpeed value is “100”.

Promiscuous mode (true or false) - DMX, DMXpress and DMXtend supports READ-ONLY ifAlias ifCounterDiscontinuity

TimeTimeStamp

Interface alias name - READ-ONLY - - (always set to NULL)

Time of last counter discontinuity

B - 9 2

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Standard Ethernet interface MIB Module Traps

The following table shows the standard Ethernet interface MIB module traps.

Object Definition

linkUp linkDown link up link down

Standard Ethernet PM MIB module

(RFC2358/RFC2665)

DMX supports the standard Ethernet PM MIB module defined in

RFC2358 and RFC2665. This module defines additional retrievable

Ethernet PM parameters. This MIB module applies to individual Fast

Ethernet and Gigabit Ethernet ports.

Standard Ethernet PM MIB Module Parameters

The following table shows the standard Ethernet PM MIB module parameters.

Object Definition

dot3StatsAlignmentErrors dot3StatsFCSErrors dot3StatsSingleCollisionFrames dot3StatsMultipleCollisionFrames dot3StatsSQETestErrors dot3StatsDeferredTransmissions dot3StatsLateCollisions

Fragments

CRC Error

Collision

(always 0) (not supported in this release)

Late Collision dot3StatsExcessiveCollisions (always 0) (not supported in this release) dot3StatsInternalMacTransmitErrors (always 0) (not supported in this release) dot3StatsCarrierSenseErrors dot3StatsFrameTooLongs

(always 0) (not supported in this release)

Oversize Frames dot3StatsInternalMacReceiveErrors MAC Rx Error dot3StatsSymbolErrors (always 0) (not supported in this release) dot3StatsDuplex Status

Duplex Status (half duplex (2), full duplex (3) - added by

RFC2665

365-372-300

Issue 8.0 September 2006

B - 9 3

SNMP Parameters and Traps

: Performance Monitoring

Object

dot3ControlFunctionsSupported dot3ControlInUnknownOpcodes dot3PauseAdminMode dot3PauseOperMode dot3InPauseFrames dot3OutPauseFrames

Definition

pause (0) --802.3 flow control - added by RFC2665

(always 0) - added by RFC2665 (not supported in this release)

Flow control default mode (read only) - added by RFC2665

Flow control operational mode (disabled (1), enabled transmit & receive (4)) - added by RFC2665

(always 0) - added by RFC2665 (not supported in this release)

Private VCG MIB module

DMX supports a private VCG MIB module for VCG traps. This private

VCG MIB module applies to individual VCGs.

Private VCG MIB Module Traps

The following table shows the private VCG MIB module traps.

Trap Object

dmxIncVcgFail dmxIncVcgFailClr dmxIncVcgGeLanTEDFC dmxIncVcgFeLanTEDFC dmxIncVcgGeLanTEDFE dmxIncVcgFeLanTEDFE dmxIncVcgGfpRcfFail dmxIncVcgGfpRcfFailClr dmxIncVcgLopcFail dmxIncVcgLopcFailClr dmxIncVcgFoprFail

Definition

Incoming VCG fail

Incoming VCG fail clear

Dropped frames due to congestion TCA on VCG

GbE WAN port

Dropped frames due to congestion TCA on VCG FE

WAN port

Dropped frames due to errors TCA on VCG GbE

WAN port

Dropped frames due to errors TCA on VCG FE WAN port

General framing procedure remote client signal failed

(GFP_RCF)

General framing procedure remote client signal failed

(GFP_RCF) clear

VCG loss of partial capacity (VCGLOPC)

VCG loss of partial capacity (VCGLOPC) clear

VCG failure of LCAS protocol (Sink) (VCGFOPR)

B - 9 4

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Trap Object

dmxIncVcgFoprFailClr dmxIncVcgFoptFail dmxIncVcgFoptFailClr dmxIncVcgNOTLCAS dmxIncVcgNOTLCASClr dmxIncSts1Lom dmxIncSts1LomClr dmxIncSts3cLom dmxIncSts3cLomClr dmxIncVt1Lom dmxIncVt1LomClr dmxIncSts1Sqm dmxIncSts1SqmClr dmxIncSts3cSqmClr dmxIncVt1SqmClr dmxIncVcgSts1MSUL dmxIncVcgSts1MSULClr dmxIncVcgSts3cMSUL dmxIncVcgSts3cMSULClr dmxIncVcgVtMSUL dmxIncVcgVtMSULClr

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

Definition

VCG failure of LCAS protocol (Sink) (VCGFOPR) clear

VCG failure of LCAS protocol (Source)

(VCGFOPT)

VCG failure of LCAS protocol (Source)

(VCGFOPT) clear

Far End Not LCAS (NOTLCAS)

Far End Not LCAS clear (NOTLCAS)

Incoming STS1 loss of multiframe

Incoming STS1 loss of multiframe clear

Incoming STS3C loss of multiframe

Incoming STS3C loss of multiframe clear

Incoming VT1 loss of multiframe

Incoming VT1 loss of multiframe clear

Incoming STS1 sequence number mismatch

Incoming STS3C sequence number mismatch

Incoming Vt1 sequence number mismatch

STS1 Member Signal Unacceptable -LCAS

(MSU-L)

STS1 Member Signal Unacceptable -LCAS

(MSU-L) Clear

STS3c Member Signal Unacceptable -LCAS

(MSU-L)

STS3c Member Signal Unacceptable -LCAS

(MSU-L) Clear

VT1.5 Member Signal Unacceptable -LCAS

(MSU-L)

VT1.5 Member Signal Unacceptable -LCAS

(MSU-L) Clear

B - 9 5

SNMP Parameters and Traps

: Performance Monitoring

Private MIB module

DMX supports a private MIB module for retrieving equipment information parameters and equipment traps. This private MIB module applies to individual circuit packs.

Private MIB Module Parameters

The following table shows the private MIB module parameters.

Object

dmxCardType dmxCardAPP dmxCardSSN dmxCardCLEI dmxCardECI dmxCardSLN dmxSftwVersion dmxCardCPMode dmxCardEccMode dmxCardVlanTagMode dmxCardVtVcat dmxCardDataType

Definition

Circuit pack type.

Circuit pack apparatus code

Circuit pack series number

Common Language Equipment code

Equipment Catalog Item code

Circuit pack serial number

Version of the software currently stored in the circuit pack

Circuit pack mode. This parameter is only applicable to the

LNW26 and LNW26B circuit packs. It indicates the functional mode of the circuit pack. Values: NORMAL,

ENHANCED

Ethernet Cross-connect Mode. This mode only pertains to the LNW71 Fast Ethernet circuit pack. Values: STS1,

STS3c

Virtual LAN tagging mode. This parameter is ONLY reported for slots containing an Ethernet circuit pack.

Values: 802.1TAG (IEEE 802.1Q mode), TRANS

(Transparent mode), NOTAG (No Tag mode)

VT Virtual Concatenation. This parameter specifies the number of STS-1s dedicated to VT virtual concatenation.

Data type. Values are:

FC-FICON - in this mode, data ports are configured individually for Fibre Channel or FICON.

ESCON - in this mode all ports on the circuit pack are set for ESCON

This object applies only to the LNW73 circuit pack

B - 9 6

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Private MIB Module Traps

The following table shows the private MIB module traps.

Object Definition

dmxCpNotAllowed Circuit pack not allowed dmxCpNotAllowedClr Circuit pack not allowed clear dmxFACTERM dmxFACTERMClr dmxFETERM dmxFETERMClr

Illegal circuit pack type

Illegal circuit pack type clear

FE-LAN circuit pack failed

FE-LAN circuit pack failed clear dmxGETERM dmxGETERMClr dmxCpRemoved dmxCpRemovedClr dmxCpInserted

GE-LAN circuit pack failed

GE-LAN circuit pack failed clear

Circuit pack removed

Circuit pack removed clear

Circuit pack inserted

365-372-300

Issue 8.0 September 2006

B - 9 7

SNMP Parameters and Traps

: Performance Monitoring

RPR IEEE Draft

P802.17/D3.3 MIB tables supported

The RPR IEEE Draft P802.17/D3.3 MIB shall be supported for retrieving RPR information and RPR PM counters only. Provisioning of RPR parameters and objects through SNMP shall not be supported.

Span tables

Running counters tables

(Continuous counter paradigm)

Basic tables

Protocol tables

Standard RPR MIB tables supported

Starting in Release 6.0/4.0, DMX/DMXtend shall support the RPR

IEEE Draft P802.17/D3.3 MIB tables as follows:.

rprSpanTable rprSpanProtectionTable rprSpanCountersStatsTable rprClientCountersStatsTable rprSpanErrorCountersStatsTable rprIfTable rprTopoImageTable rprFairnessTable partially supported partially supported

Fully Supported

Fully Supported partially supported partially supported partially supported partially supported

B - 9 8

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

RPR IEEE Draft P802.17/D3.3

MIB objects supported

Starting in Release 6.0/4.0, DMX and DMXtend shall support the RPR

IEEE Draft P802.17/D3.3 MIB objects as specified in the following 6 tables.

RPR Basic Tables

Definition Value

rprIfTable rprIfIndex

Table/Object

rprIfStationsOnRing rprIfReversionMode rprIfProtectionWTR rprIfProtectionFastTimer rprIfProtectionSlowTimer rprIfAtdTimer rprIfKeepaliveTimeout rprIfFairnessAggressive rprIfPtqSize rprIfStqSize rprIfSTQFullThreshold rprIfIdleThreshold rprIfSesThreshold rprIfWrapConfig rprIfJumboFramePreferred rprIfMacOperModes rprIfRingOperModes rprIfCurrentStatus rprIfLastChange

InterfaceIndex

Unsigned32

TruthValue

Unsigned32

TruthValue

Unsigned32

TruthValue

BITS

TimeStamp

Always “TRUE”

Always “TRUE” not supported, always 0 not supported, always 0 not supported, always 0 bit 0: strictOrder always 0 bit 1: dropBadFcs always 1 not supported, always 0

365-372-300

Issue 8.0 September 2006

B - 9 9

SNMP Parameters and Traps

RPR Span Tables

Table/Object

rprSpanTable

Definition

rprSpanIfIndex rprSpanId

InterfaceIndex rprSpan rprSpanLowerLayerIfIndex InterfaceIndexOrZero rprSpanTotalRingletReservedRate Unsigned32 rprSpanCurrentStatus rprSpanLastChange rprSpanChanges rprSpanProtectionTable rprSpanProtectionIfIndex rprSpanProtectionSpan rprSpanProtectionNeighborValid rprSpanProtectionHoldOffTimer rprSpanProtectionCommand rprSpanProtectionCount rprSpanProtectionDuration rprSpanProtectionLastActivationTi me

BITS

TimeStamp

Counter32

InterfaceIndex rprSpan

TruthValue

Unsigned32

INTEGER

Counter32

TimeStamp

RPR Protocol Tables

Table/Object

rprTopoImageTable rprTopoImageIfIndex rprTopoImageMacAddress rprTopoImageSecMacAddress1

Definition

InterfaceIndex

MacAddress

B - 1 0 0

: Performance Monitoring

Value

not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0

Value

not supported, always

“FF:FF:FF:FF:FF:FF"

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table/Object

rprTopoImageSecMacAddress2 rprTopoImageStationIfIndex rprTopoImageStationName rprTopoImageInetAddressType rprTopoImageInetAddress

Definition

MacAddress

InterfaceIndex

SnmpAdminString

InetAddressType

InetAddress rprTopoImageCapability BITS rprTopoImageRinglet0Hops rprTopoImageRinglet0ReservedRa te rprTopoImageRinglet1Hops

Integer32

Unsigned32

Integer32 rprTopoImageRinglet1ReservedRa te rprTopoImageWestProtectionStatu s

Unsigned32 rprProtectionStatus rprTopoImageWestWeight Unsigned32 rprTopoImageEastProtectionStatus rprProtectionStatus rprTopoImageEastWeight Unsigned32

BITS rprTopoImageStatus rprFairnessTable rprFairnessIfIndex rprFairnessRinglet rprFairnessRingletWeight rprFairnessReservedRate rprFairnessMaxAllowed

365-372-300

Issue 8.0 September 2006

InterfaceIndex

INTEGER

Unsigned32

: Performance Monitoring

Value

not supported, always

“FF:FF:FF:FF:FF:FF" not supported, always 0 not supported, always 0 not supported, always “unknown” not supported, always 0 bit0 (jumboFrames) set according to

RTRV-MAP-RPR

:jumbo. If

jumbo=YES, then bit0=1, else bit0=0. All other bits=0.

not supported, always 0 not supported, always 0 bit0 (reachableRinglet0) and bit1

(reachableRinglet1) set according to

RTRV-MAP-RPR

:r0hops and

r1hops. If r0hops/r1hops=-1, then bit0/bit1 =0, else bit0/bit1 =1. All other bits=0.

not supported, always 0

B - 1 0 1

SNMP Parameters and Traps

Table/Object

rprFairnessAgeCoef rprFairnessRampCoef rprFairnessLpCoef rprFairnessAdvertisementRatio rprFairnessMcffReportCoef rprFairnessActiveWeightsCoef rprFairnessSTQHighThreshold rprFairnessSTQMedThreshold rprFairnessSTQLowThreshold rprFairnessRateHighThreshold rprFairnessRateLowThreshold rprFairnessResetWaterMarks rprFairnessSTQHighWaterMark rprFairnessSTQLowWaterMark rprFairnessLastChange rprFairnessChanges

Unsigned32

Definition

Unsigned32

INTEGER

Unsigned32

TimeStamp

Counter32

: Performance Monitoring

Value

not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0 not supported, always 0

B - 1 0 2

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

RPR Span Counters Tables

Table/Object

rprSpanCountersStatsTable rprSpanStatsIfIndex

Definition

InterfaceIndex rprSpanStatsSpan rprSpan rprSpanStatsInUcastClassAFrames Counter64 rprSpanStatsInUcastClassAOctets Counter64 rprSpanStatsInUcastClassBCirFram es

Counter64 rprSpanStatsInUcastClassBCirOcte ts rprSpanStatsInUcastClassBEirFram es

Counter64

Counter64 rprSpanStatsInUcastClassBEirOctet s

Counter64 rprSpanStatsInUcastClassCFrames Counter64 rprSpanStatsInUcastClassCOctets Counter64 rprSpanStatsInMcastClassAFrames Counter64 rprSpanStatsInMcastClassAOctets Counter64 rprSpanStatsInMcastClassBCirFra mes

Counter64 rprSpanStatsInMcastClassBCirOcte ts rprSpanStatsInMcastClassBEirFra mes

Counter64

Counter64 rprSpanStatsInMcastClassBEirOcte ts

Counter64 rprSpanStatsInMcastClassCFrames Counter64 rprSpanStatsInMcastClassCOctets Counter64 rprSpanStatsInCtrlFrames Counter64 rprSpanStatsInOamEchoFrames Counter64 - not supported, always 0

B - 1 0 3

SNMP Parameters and Traps

: Performance Monitoring

Table/Object

rprSpanStatsInOamFlushFrames

Definition

Counter64 - not supported, always 0 rprSpanStatsInOamOrgFrames rprSpanStatsInTopoAtdFrames rprSpanStatsInTopoChkSumFrame s rprSpanStatsInTopoTpFrames

Counter64 - not supported, always 0

Counter64

Counter64 rprSpanStatsOutUcastClassAFrame s

Counter64 rprSpanStatsOutUcastClassAOctets Counter64 rprSpanStatsOutUcastClassBCirFra mes rprSpanStatsOutUcastClassBCirOct ets rprSpanStatsOutUcastClassBEirFra mes rprSpanStatsOutUcastClassBEirOct ets

Counter64

Counter64 rprSpanStatsOutUcastClassCFrame s

Counter64 rprSpanStatsOutUcastClassCOctets Counter64 rprSpanStatsOutMcastClassAFram es rprSpanStatsOutMcastClassAOctet s

Counter64

Counter64 rprSpanStatsOutMcastClassBCirFr ames rprSpanStatsOutMcastClassBCirOc tets rprSpanStatsOutMcastClassBEirFra mes rprSpanStatsOutMcastClassBEirOc tets

Counter64

B - 1 0 4

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Table/Object

rprSpanStatsOutMcastClassCFrame s rprSpanStatsOutOamOrgFrames rprSpanStatsOutTopoAtdFrames rprSpanStatsOutTopoChkSumFram es rprSpanStatsOutTopoTpFrames

Counter64

Definition

rprSpanStatsOutMcastClassCOctets Counter64 rprSpanStatsOutCtrlFrames Counter64 rprSpanStatsOutOamEchoFrames Counter64 - not supported, always 0 rprSpanStatsOutOamFlushFrames Counter64 - not supported, always 0

Counter64 - not supported, always 0

Counter64

RPR Client Counters Tables

365-372-300

Issue 8.0 September 2006

Table/Object

rprClientCountersStatsTable rprClientStatsIfIndex

Definition

rprClientStatsInUcastClassAFrames rprClientStatsInUcastClassAOctets

InterfaceIndex

Counter64

Counter64 rprClientStatsInUcastClassBCirFrame s

Counter64 rprClientStatsInUcastClassBCirOctets Counter64 rprClientStatsInUcastClassBEirFrame s

Counter64 rprClientStatsInUcastClassBEirOctets Counter64 rprClientStatsInUcastClassCFrames rprClientStatsInUcastClassCOctets rprClientStatsInMcastClassAFrames rprClientStatsInMcastClassAOctets rprClientStatsInMcastClassBCirFram es

Counter64

B - 1 0 5

SNMP Parameters and Traps

: Performance Monitoring

Table/Object

rprClientStatsInMcastClassBCirOctet s

Counter64 rprClientStatsInMcastClassBEirFrame s

Counter64 rprClientStatsInMcastClassBEirOctets Counter64 rprClientStatsInMcastClassCFrames rprClientStatsInMcastClassCOctets

Counter64

Counter64 rprClientStatsInBcastFrames Counter64 rprClientStatsOutUcastClassAFrames Counter64 rprClientStatsOutUcastClassAOctets Counter64 rprClientStatsOutUcastClassBCirFra mes

Counter64 rprClientStatsOutUcastClassBCirOcte ts rprClientStatsOutUcastClassBEirFra mes

Counter64

Counter64 rprClientStatsOutUcastClassBEirOcte ts

Counter64 rprClientStatsOutUcastClassCFrames Counter64 rprClientStatsOutUcastClassCOctets Counter64 rprClientStatsOutMcastClassAFrames Counter64 rprClientStatsOutMcastClassAOctets Counter64 rprClientStatsOutMcastClassBCirFra mes

Counter64 rprClientStatsOutMcastClassBCirOct ets rprClientStatsOutMcastClassBEirFra mes

Counter64

Counter64 rprClientStatsOutMcastClassBEirOcte ts

Counter64 rprClientStatsOutMcastClassCFrames Counter64

Definition

B - 1 0 6

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Table/Object

rprClientStatsOutMcastClassCOctets Counter64 rprClientStatsOutBcastFrames Counter64

Definition

RPR Span Errors CountersTables

Table/Object

rprSpanErrorCountersStatsTable

Definition

rprSpanErrorStatsIfIndex rprSpanErrorStatsSpan

InterfaceIndex rprSpan rprSpanErrorStatsTtlExpFrames Counter64 rprSpanErrorStatsTooLongFrames Counter64 rprSpanErrorStatsTooShortFrames Counter64 rprSpanErrorStatsBadHecFrames Counter64 rprSpanErrorStatsBadFcsFrames Counter64 rprSpanErrorStatsSelfSrcUcastFra mes

Counter64 rprSpanErrorStatsPmdAbortFrame s

Counter64 rprSpanErrorStatsBadAddrFrames Counter64 rprSpanErrorStatsBadParityFrame s rprSpanErrorStatsContainedFrame s rprSpanErrorStatsScffErrors

Counter64

)

Value

not supported, always 0

(included in rprSpanErrorStatsBadFcsFrames)

(includes rprSpanErrorStatsTooShortFrames not supported, always 0 not supported, always 0

365-372-300

Issue 8.0 September 2006

B - 1 0 7

SNMP Parameters and Traps

: Performance Monitoring

Private RPR LAN PM counters

MIB

Starting in Release 6.0/4.0, DMX/DMXtend shall support the DMX

RPR PM Counters tables for LAN and VCG Ports, as specified in the table below

DMX Private RPR Counters Table

Table

dmxRprCurrentEntry

Object

dmxRprCurrentIndex dmxRprCurrentIUCAF dmxRprCurrentIUCAO dmxRprCurrentIUCBF dmxRprCurrentIUCBO dmxRprCurrentIUCBEF dmxRprCurrentIUCBEO dmxRprCurrentIUCCF dmxRprCurrentIUCCO dmxRprCurrentIMCAF

Description

Current index

Number of Class A unicast frames received with no errors- current

Number of Class A unicast octets received with no errors- current

Number of Class B unicast frames received below CIR with no errors- current

Number of Class B unicast octets received below CIR with no errors- current

Number of Class B unicast frames received below EIR with no errors- current

Number of Class B unicast octets received below EIR with no errors- current

Number of Class C unicast frames received with no errors- current

Number of Class C unicast octets received with no error- current

Number of Class A multicast frames received with no error- current

Application

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

B - 1 0 8

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

Object

dmxRprCurrentIMCAO dmxRprCurrentIMCBF dmxRprCurrentIMCBO dmxRprCurrentIMCBEF dmxRprCurrentIMCBEO dmxRprCurrentIMCCF dmxRprCurrentIMCCO dmxRprCurrentOUCAF dmxRprCurrentOUCAO dmxRprCurrentOUCBF dmxRprCurrentOUCBO

Description

Number of Class A multicast octets received with no error- current

Number of Class B multicast frames received below CIR with no error- current

Number of Class B multicast octets received below CIR with no error- current

Number of Class B multicast frames received below EIR with no error- current

Number of Class B multicast octets received below EIR with no error- current

Number of Class C multicast frames received with no error- current

Number of Class C multicast octets received with no error- current

Number of Class A unicast frames transmitted with no errors- current

Number of Class A unicast octets transmitted with no errors- current

Number of Class B unicast frames transmitted below

CIR with no errors- current

Number of Class B unicast octets transmitted below

CIR with no errors- current

Application

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

B - 1 0 9

SNMP Parameters and Traps

Table

: Performance Monitoring

Object

dmxRprCurrentOUCBEF dmxRprCurrentOUCBEO dmxRprCurrentOUCCF dmxRprCurrentOUCCO dmxRprCurrentOMCAF dmxRprCurrentOMCAO dmxRprCurrentOMCBF dmxRprCurrentOMCBO dmxRprCurrentOMCBEF dmxRprCurrentOMCBEO

Description

Number of Class B unicast frames transmitted below

EIR with no errors- current

Number of Class B unicast octets transmitted below

EIR with no errors- current

Number of Class C unicast frames transmitted with no errors- current

Number of Class C unicast octets transmitted with no error- current

Number of Class A multicast frames transmitted with no error- current

Application

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Number of Class A multicast octets transmitted with no error- current

Number of Class B multicast frames transmitted below CIR with no error- current

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Number of Class B multicast octets transmitted below CIR with no error- current

Number of Class B multicast frames transmitted below EIR, no error- current

Number of Class B multicast octets transmitted below EIR with no error- current

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

B - 1 1 0

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

dmxRprCurrentSpanIUCA

F dmxRprCurrentSpanIUCA

O dmxRprCurrentSpanIUCB

F dmxRprCurrentSpanIUCB

O dmxRprCurrentSpanIUCB

EF dmxRprCurrentSpanIUCB

EO dmxRprCurrentSpanIUCC

F dmxRprCurrentSpanIUCC

Object

dmxRprCurrentOMCCF dmxRprCurrentOMCCO dmxRprCurrentSpanIMCA

F dmxRprCurrentSpanIMCA

Description

Number of Class C multicast frames transmitted with no error- current

Number of Class C multicast octets transmitted with no error- current

Number of Class A unicast frames received with no errors- CurrentSpan

Number of Class A unicast octets received with no errors- CurrentSpan

Number of Class B unicast frames received below CIR with no errors- CurrentSpan

Number of Class B unicast octets received below CIR with no errors- CurrentSpan

Number of Class B unicast frames received below EIR with no errors- CurrentSpan

Number of Class B unicast octets received below EIR with no errors- CurrentSpan

Number of Class C unicast frames received with no errors- CurrentSpan

Number of Class C unicast octets received with no error- CurrentSpan

Number of Class A multicast frames received with no error- CurrentSpan

Number of Class A multicast octets received with no error- CurrentSpan

Application

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

B - 1 1 1

SNMP Parameters and Traps

Table

: Performance Monitoring

dmxRprCurrentSpanIMCB

F dmxRprCurrentSpanIMCB

O dmxRprCurrentSpanIMCB

EF dmxRprCurrentSpanIMCB

EO dmxRprCurrentSpanIMCC

F dmxRprCurrentSpanIMCC

O dmxRprCurrentSpanOUC

AF dmxRprCurrentSpanOUC

Object

dmxRprCurrentSpanOUCB

F dmxRprCurrentSpanOUCB

Description

Number of Class B multicast frames received below CIR with no error-

CurrentSpan

Number of Class B multicast octets received below CIR with no error-

CurrentSpan

Number of Class B multicast frames received below EIR with no error-

CurrentSpan

Number of Class B multicast octets received below EIR with no error-

CurrentSpan

Number of Class C multicast frames received with no error- CurrentSpan

Number of Class C multicast octets received with no error- CurrentSpan

Number of Class A unicast frames transmitted with no errors- CurrentSpan

Number of Class A unicast octets transmitted with no errors- CurrentSpan

Number of Class B unicast frames transmitted below

CIR with no errors-

CurrentSpan

Number of Class B unicast octets transmitted below

CIR with no errors-

CurrentSpan

Application

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

B - 1 1 2

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

: Performance Monitoring

dmxRprCurrentSpanOMC

AF dmxRprCurrentSpanOMC

AO dmxRprCurrentSpanOMC

BF dmxRprCurrentSpanOMC

BO dmxRprCurrentSpanOMC

BEF dmxRprCurrentSpanOMC

BEO

Object

dmxRprCurrentSpanOUCB

EF dmxRprCurrentSpanOUCB

EO dmxRprCurrentSpanOUCC

F dmxRprCurrentSpanOUCC

Description

Number of Class B unicast frames transmitted below

EIR with no errors-

CurrentSpan

Number of Class B unicast octets transmitted below

EIR with no errors-

CurrentSpan

Number of Class C unicast frames transmitted with no errors- CurrentSpan

Number of Class C unicast octets transmitted with no error- CurrentSpan

Number of Class A multicast frames transmitted with no error-

CurrentSpan

Application

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class A multicast octets transmitted with no error- CurrentSpan

Number of Class B multicast frames transmitted below CIR with no error- CurrentSpan

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class B multicast octets transmitted below CIR with no error-

CurrentSpan

Number of Class B multicast frames transmitted below EIR, no error- CurrentSpan

Number of Class B multicast octets transmitted below EIR with no error-

CurrentSpan

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

365-372-300

Issue 8.0 September 2006

B - 1 1 3

SNMP Parameters and Traps

Table

: Performance Monitoring

dmxRprCurrentSpanOMC

CF dmxRprCurrentSpanOMC

Object

dmxRprCurrentDRATEF dmxRprCurrentDTAGF dmxRprCurrentDSPIF dmxRprCurrentDSIZEF dmxRprCurrentDNOTAGF dmxRprCurrentDSMACF dmxRprCurrentDSMACO

Description

Number of Class C multicast frames transmitted with no error-

CurrentSpan

Number of Class C multicast octets transmitted with no error- CurrentSpan

Application

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Multicast and broadcast packets dropped due to exceeding port rate- current

Packets dropped due to

VLAN filtering- current

Packets dropped due to internal error (SPI4)- current

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Packets dropped due to being greater then configured maximum frame size for port- current

Packets dropped due to no tag when required- current

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Number of packets dropped due to MAC table source address filtering- current

Number of octets dropped due to MAC table source address filtering- current

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

B - 1 1 4

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

: Performance Monitoring

dmxRprCurrentIUCARED

F dmxRprCurrentIUCARED

O dmxRprCurrentIUCBRED

F dmxRprCurrentIUCBRED

O dmxRprCurrentIUCCRED

F dmxRprCurrentIUCCRED

Object

dmxRprCurrentDFCG dmxRprCurrentDFCY dmxRprCurrentIMCARED

Description

Green packets dropped due to congestion- current

Yellow packets dropped due to congestion- current

Application

Bridge counters valid for LAN, RPR Span

VCG (not RPR IF

VCG) ports

Bridge counters valid for LAN, RPR Span

VCG (not RPR IF

VCG) ports

Number of Unicast packets assigned to Class A and given drop precedence of red- current

Number of Unicast octets assigned to Class A and given drop precedence of red- current

Number of Unicast packets assigned to Class B and given drop precedence of red- current

Metering counters valid for LAN ports only

Number of Unicast octets assigned to Class B and given drop precedence of red- current

Number of Unicast packets assigned to Class C and given drop precedence of red- current

Number of Multicast octets assigned to Class C and given drop precedence of red- current

Number of Multicast packets assigned to Class A and given drop precedence of red- current

Metering counters valid for LAN ports only

365-372-300

Issue 8.0 September 2006

B - 1 1 5

SNMP Parameters and Traps

Table

: Performance Monitoring

dmxRprCurrentIMCBRED

F dmxRprCurrentIMCBRED

O dmxRprCurrentIMCCRED

F dmxRprCurrentIMCCRED

Object

dmxRprCurrentIMCARED

O dmxRprCurrentICTRF dmxRprCurrentIATDF dmxRprCurrentITPF dmxRprCurrentOCTRLF dmxRprCurrentOATDF dmxRprCurrentOTPF dmxRprCurrentITTLF

Description

Number of Multicast octets assigned to Class A and given drop precedence of red- current

Application

Metering counters valid for LAN ports only

Number of Multicast packets assigned to Class B and given drop precedence of red- current

Number of Multicast octets assigned to Class B and given drop precedence of red- current

Metering counters valid for LAN ports only

Number of Multicast packets assigned to Class C and given drop precedence of red- current

Number of Multicast octets assigned to Class C and given drop precedence of red- current

Metering counters valid for LAN ports only

Number of control frames received- current

Number of ATD frames received- current

Number of TP frames received- current

Number of control frames transmitted- current

Number of ATD frames transmitted- current

Number of TP frames transmitted- current

Number of frames received with expired TTL values- current

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

B - 1 1 6

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

: Performance Monitoring

Table

dmxRprIntervalEntry

Object

dmxRprCurrentDLONG dmxRprCurrentDHEC dmxRprCurrentDSS dmxRprCurrentDSA dmxRprCurrentDPTY dmxRprCurrentDSCFF dmxRprIntervalIndex dmxRprIntervalIUCAF dmxRprIntervalIUCAO dmxRprIntervalIUCBF dmxRprIntervalIUCBO dmxRprIntervalIUCBEF

Description

Number of frames received with length exceeding the max allowed length- current

Application

Span counters valid for

RPR Span VCG only

Number of frames received with HEC value not matching the expected HEC value- current

Number of frames received sourced by this station and then received by this station- current

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Number of frames received with bad SA (Multicast or

Broadcast)- current

Number of frames received with Parity value not matching the expected

Parity value- current

Number of SCFF frames received with bad FCS or bad parity- current

15 minute index

Number of Class A unicast frames received with no errors- 15 minute

Number of Class A unicast octets received with no errors- 15 minute

Number of Class B unicast frames received below CIR with no errors- 15 minute

Number of Class B unicast octets received below CIR with no errors- 15 minute

Number of Class B unicast frames received below EIR with no errors- 15 minute

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

365-372-300

Issue 8.0 September 2006

B - 1 1 7

SNMP Parameters and Traps

Table

B - 1 1 8

: Performance Monitoring

Object

dmxRprIntervalIUCBEO dmxRprIntervalIUCCF dmxRprIntervalIUCCO dmxRprIntervalIMCAF dmxRprIntervalIMCAO dmxRprIntervalIMCBF dmxRprIntervalIMCBO dmxRprIntervalIMCBEF dmxRprIntervalIMCBEO dmxRprIntervalIMCCF dmxRprIntervalIMCCO

Description

Number of Class B unicast octets received below EIR with no errors- 15 minute

Number of Class C unicast frames received with no errors- 15 minute

Number of Class C unicast octets received with no error- 15 minute

Number of Class A multicast frames received with no error- 15 minute

Number of Class A multicast octets received with no error- 15 minute

Application

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Number of Class B multicast frames received below CIR with no error- 15 minute

Number of Class B multicast octets received below CIR with no error- 15 minute

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Number of Class B multicast frames received below EIR with no error- 15 minute

Number of Class B multicast octets received below EIR with no error- 15 minute

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Number of Class C multicast frames received with no error- 15 minute

Number of Class C multicast octets received with no error- 15 minute

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

: Performance Monitoring

Object

dmxRprIntervalOUCAF dmxRprIntervalOUCAO dmxRprIntervalOUCBF dmxRprIntervalOUCBO dmxRprIntervalOUCBEF dmxRprIntervalOUCBEO dmxRprIntervalOUCCF dmxRprIntervalOUCCO dmxRprIntervalOMCAF dmxRprIntervalOMCAO

Description

Number of Class A unicast frames transmitted with no errors- 15 minute

Number of Class A unicast octets transmitted with no errors- 15 minute

Number of Class B unicast frames transmitted below

CIR with no errors- 15 minute

Number of Class B unicast octets transmitted below

CIR with no errors- 15 minute

Number of Class B unicast frames transmitted below

EIR with no errors- 15 minute

Number of Class B unicast octets transmitted below

EIR with no errors- 15 minute

Number of Class C unicast frames transmitted with no errors- 15 minute

Number of Class C unicast octets transmitted with no error- 15 minute

Number of Class A multicast frames transmitted with no error-

15 minute

Number of Class A multicast octets transmitted with no error- 15 minute

Application

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

365-372-300

Issue 8.0 September 2006

B - 1 1 9

SNMP Parameters and Traps

Table

B - 1 2 0

: Performance Monitoring

Object

dmxRprIntervalOMCBF dmxRprIntervalOMCBO dmxRprIntervalOMCBEF dmxRprIntervalOMCBEO dmxRprIntervalOMCCF dmxRprIntervalOMCCO dmxRprIntervalSpanIUCA

F dmxRprIntervalSpanIUCA

O dmxRprIntervalSpanIUCB

F dmxRprIntervalSpanIUCB

O dmxRprIntervalSpanIUCB

Description

Number of Class B multicast frames transmitted below CIR with no error- 15 minute

Application

Valid for LAN and

RPR IF VCG ports

Number of Class B multicast octets transmitted below CIR with no error- 15 minute

Number of Class B multicast frames transmitted below EIR, no error- 15 minute

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Number of Class B multicast octets transmitted below EIR with no error- 15 minute

Number of Class C multicast frames transmitted with no error-

15 minute

Valid for LAN and

RPR IF VCG ports

Valid for LAN and

RPR IF VCG ports

Number of Class C multicast octets transmitted with no error- 15 minute

Number of Class A unicast frames received with no errors- 15 minute

Number of Class A unicast octets received with no errors- 15 minute

Number of Class B unicast frames received below CIR with no errors- 15 minute

Number of Class B unicast octets received below CIR with no errors- 15 minute

Number of Class B unicast frames received below EIR with no errors- 15 minute

Valid for LAN and

RPR IF VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

dmxRprIntervalSpanIUCB

EO dmxRprIntervalSpanIUCC

F dmxRprIntervalSpanIUCC

O dmxRprIntervalSpanIMCB

F dmxRprIntervalSpanIMCB

O dmxRprIntervalSpanIMCB

EF dmxRprIntervalSpanIMCB

EO dmxRprIntervalSpanIMCC

F dmxRprIntervalSpanIMCC

Object

dmxRprIntervalSpanIMCA

F dmxRprIntervalSpanIMCA

Description

Number of Class B unicast octets received below EIR with no errors- 15 minute

Number of Class C unicast frames received with no errors- 15 minute

Number of Class C unicast octets received with no error- 15 minute

Number of Class A multicast frames received with no error- 15 minute

Number of Class A multicast octets received with no error- 15 minute

Application

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class B multicast frames received below CIR with no error- 15 minute

Number of Class B multicast octets received below CIR with no error- 15 minute

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class B multicast frames received below EIR with no error- 15 minute

Number of Class B multicast octets received below EIR with no error- 15 minute

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class C multicast frames received with no error- 15 minute

Number of Class C multicast octets received with no error- 15 minute

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

B - 1 2 1

SNMP Parameters and Traps

Table

: Performance Monitoring

dmxRprIntervalSpanOUC

AF dmxRprIntervalSpanOUC

AO dmxRprIntervalSpanOUC

BF dmxRprIntervalSpanOUC

BO dmxRprIntervalSpanOUC

BEF dmxRprIntervalSpanOUC

BEO dmxRprIntervalSpanOUC

CF dmxRprIntervalSpanOUC

Object

dmxRprIntervalSpanOMC

AF dmxRprIntervalSpanOMC

Description

Number of Class A unicast frames transmitted with no errors- 15 minute

Number of Class A unicast octets transmitted with no errors- 15 minute

Number of Class B unicast frames transmitted below

CIR with no errors- 15 minute

Number of Class B unicast octets transmitted below

CIR with no errors- 15 minute

Number of Class B unicast frames transmitted below

EIR with no errors- 15 minute

Number of Class B unicast octets transmitted below

EIR with no errors- 15 minute

Number of Class C unicast frames transmitted with no errors- 15 minute

Number of Class C unicast octets transmitted with no error- 15 minute

Number of Class A multicast frames transmitted with no error-

15 minute

Number of Class A multicast octets transmitted with no error- 15 minute

Application

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

B - 1 2 2

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

: Performance Monitoring

Object

dmxRprIntervalSpanOMC

BF dmxRprIntervalSpanOMC

BO dmxRprIntervalSpanOMC

BEF dmxRprIntervalSpanOMC

BEO dmxRprIntervalSpanOMC

CF dmxRprIntervalSpanOMC

CO dmxRprIntervalDRATEF dmxRprIntervalDTAGF dmxRprIntervalDSPIF

Description

Number of Class B multicast frames transmitted below CIR with no error- 15 minute

Application

Valid for RPR Span

VCG ports

Number of Class B multicast octets transmitted below CIR with no error- 15 minute

Number of Class B multicast frames transmitted below EIR, no error- 15 minute

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class B multicast octets transmitted below EIR with no error- 15 minute

Number of Class C multicast frames transmitted with no error-

15 minute

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class C multicast octets transmitted with no error- 15 minute

Multicast and broadcast packets dropped due to exceeding port rate- 15 minute

Valid for RPR Span

VCG ports

Packets dropped due to

VLAN filtering- 15 minute

Packets dropped due to internal error (SPI4)- 15 minute

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

365-372-300

Issue 8.0 September 2006

B - 1 2 3

SNMP Parameters and Traps

Table

: Performance Monitoring

dmxRprIntervalDNOTAG

F dmxRprIntervalIUCBRED

Object

dmxRprIntervalDSIZEF dmxRprIntervalDDMACF dmxRprIntervalDDMACO dmxRprIntervalDFCG dmxRprIntervalDFCY dmxRprIntervalIUCARED

F dmxRprIntervalIUCARED

Description

Packets dropped due to being greater then configured maximum frame size for port- 15 minute

Application

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Packets dropped due to no tag when required- 15 minute

Number of packets dropped due to MAC table destination address filtering- 15 minute

Number of octets dropped due to MAC table destination address filtering- 15 minute

Green packets dropped due to congestion- 15 minute

Yellow packets dropped due to congestion- 15 minute

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR Span

VCG (not RPR IF

VCG) ports

Bridge counters valid for LAN, RPR Span

VCG (not RPR IF

VCG) ports

Number of Unicast packets assigned to Class A and given drop precedence of red- 15 minute

Number of Unicast octets assigned to Class A and given drop precedence of red- 15 minute

Number of Unicast packets assigned to Class B and given drop precedence of red- 15 minute

Metering counters valid for LAN ports only

B - 1 2 4

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

365-372-300

Issue 8.0 September 2006

: Performance Monitoring

dmxRprIntervalIUCBRED

O dmxRprIntervalIUCCRED

F dmxRprIntervalIUCCRED

O dmxRprIntervalIMCBRED

F dmxRprIntervalIMCBRED

O dmxRprIntervalIMCCRED

F dmxRprIntervalIMCCRED

Object

dmxRprIntervalIMCARED

F dmxRprIntervalIMCARED

O dmxRprIntervalICTRF

Description

Number of Unicast octets assigned to Class B and given drop precedence of red- 15 minute

Application

Metering counters valid for LAN ports only

Number of Unicast packets assigned to Class C and given drop precedence of red- 15 minute

Number of Multicast octets assigned to Class C and given drop precedence of red- 15 minute

Metering counters valid for LAN ports only

Number of Multicast packets assigned to Class A and given drop precedence of red- 15 minute

Number of Multicast octets assigned to Class A and given drop precedence of red- 15 minute

Metering counters valid for LAN ports only

Number of Multicast packets assigned to Class B and given drop precedence of red- 15 minute

Number of Multicast octets assigned to Class B and given drop precedence of red- 15 minute

Metering counters valid for LAN ports only

Number of Multicast packets assigned to Class C and given drop precedence of red- 15 minute

Number of Multicast octets assigned to Class C and given drop precedence of red- 15 minute

Number of control frames received- 15 minute

Metering counters valid for LAN ports only

Span counters valid for

RPR Span VCG only

B - 1 2 5

SNMP Parameters and Traps

: Performance Monitoring

Table

dmxRprDayEntry

B - 1 2 6

Object

dmxRprIntervalIATDF dmxRprIntervalITPF dmxRprIntervalOCTRLF dmxRprIntervalOATDF dmxRprIntervalOTPF dmxRprIntervalITTLF dmxRprIntervalDLONG dmxRprIntervalDHEC dmxRprIntervalDSS dmxRprIntervalDSA dmxRprIntervalDPTY dmxRprIntervalDSCFF dmxRprDayIndex

Description

Number of ATD frames received- 15 minute

Number of TP frames received- 15 minute

Number of control frames transmitted- 15 minute

Number of ATD frames transmitted- 15 minute

Number of TP frames transmitted- 15 minute

Number of frames received with expired TTL values-

15 minute

Number of frames received with length exceeding the max allowed length- 15 minute

Number of frames received with HEC value not matching the expected HEC value- 15 minute

Number of frames received sourced by this station and then received by this station- 15 minute

Number of frames received with bad SA (Multicast or

Broadcast)- 15 minute

Number of frames received with Parity value not matching the expected

Parity value- 15 minute

Number of SCFF frames received with bad FCS or bad parity- 15 minute

Total 24 hour index

Application

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

: Performance Monitoring

Object

dmxRprDaySpanIUCAF dmxRprDaySpanIUCAO dmxRprDaySpanIUCBF dmxRprDaySpanIUCBO dmxRprDaySpanIUCBEF dmxRprDaySpanIUCBEO dmxRprDaySpanIUCCF dmxRprDaySpanIUCCO dmxRprDaySpanIMCAF dmxRprDaySpanIMCAO dmxRprDaySpanIMCBF

Description

Number of Class A unicast frames received with no errors- 24 hour

Number of Class A unicast octets received with no errors- 24 hour

Number of Class B unicast frames received below CIR with no errors- 24 hour

Number of Class B unicast octets received below CIR with no errors- 24 hour

Number of Class B unicast frames received below EIR with no errors- 24 hour

Application

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class B unicast octets received below EIR with no errors- 24 hour

Number of Class C unicast frames received with no errors- 24 hour

Number of Class C unicast octets received with no error- 24 hour

Number of Class A multicast frames received with no error- 24 hour

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class A multicast octets received with no error- 24 hour

Number of Class B multicast frames received below CIR with no error- 24 hour

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

365-372-300

Issue 8.0 September 2006

B - 1 2 7

SNMP Parameters and Traps

Table

: Performance Monitoring

Object

dmxRprDaySpanIMCBO dmxRprDaySpanIMCBEF dmxRprDaySpanIMCBEO dmxRprDaySpanIMCCF dmxRprDaySpanIMCCO dmxRprDaySpanOUCAF dmxRprDaySpanOUCAO dmxRprDaySpanOUCBF dmxRprDaySpanOUCBO dmxRprDaySpanOUCBEF dmxRprDaySpanOUCBEO

Description

Number of Class B multicast octets received below CIR with no error- 24 hour

Application

Valid for RPR Span

VCG ports

Number of Class B multicast frames received below EIR with no error- 24 hour

Number of Class B multicast octets received below EIR with no error- 24 hour

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class C multicast frames received with no error- 24 hour

Number of Class C multicast octets received with no error- 24 hour

Number of Class A unicast frames transmitted with no errors- 24 hour

Number of Class A unicast octets transmitted with no errors- 24 hour

Number of Class B unicast frames transmitted below

CIR with no errors- 24 hour

Number of Class B unicast octets transmitted below

CIR with no errors- 24 hour

Number of Class B unicast frames transmitted below

EIR with no errors- 24 hour

Number of Class B unicast octets transmitted below

EIR with no errors- 24 hour

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

B - 1 2 8

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

: Performance Monitoring

dmxRprDaySpanOMCBE

Object

dmxRprDaySpanOUCCF dmxRprDaySpanOUCCO dmxRprDaySpanOMCAF dmxRprDaySpanOMCAO dmxRprDaySpanOMCBF dmxRprDaySpanOMCBO dmxRprDaySpanOMCBEF dmxRprDaySpanOMCCF dmxRprDaySpanOMCCO

Description

Number of Class C unicast frames transmitted with no errors- 24 hour

Application

Valid for RPR Span

VCG ports

Number of Class C unicast octets transmitted with no error- 24 hour

Number of Class A multicast frames transmitted with no error-

24 hour

Number of Class A multicast octets transmitted with no error- 24 hour

Number of Class B multicast frames transmitted below CIR with no error- 24 hour

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class B multicast octets transmitted below CIR with no error- 24 hour

Number of Class B multicast frames transmitted below EIR, no error- 24 hour

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Number of Class B multicast octets transmitted below EIR with no error- 24 hour

Number of Class C multicast frames transmitted with no error-

24 hour

Number of Class C multicast octets transmitted with no error- 24 hour

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

Valid for RPR Span

VCG ports

365-372-300

Issue 8.0 September 2006

B - 1 2 9

SNMP Parameters and Traps

Table

: Performance Monitoring

Object

dmxRprDayDRATEF dmxRprDayDTAGF dmxRprDayDSPIF dmxRprDayDSIZEF dmxRprDayDNOTAGF dmxRprDayDSMACF dmxRprDayDSMACO dmxRprDayDFCG dmxRprDayDFCY

Description

Multicast and broadcast packets dropped due to exceeding port rate- 24 hour

Application

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Packets dropped due to

VLAN filtering- 24 hour

Packets dropped due to internal error (SPI4)- 24 hour

Packets dropped due to being greater then configured maximum frame size for port- 24 hour

Packets dropped due to no tag when required- 24 hour

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Number of packets dropped due to MAC table source address filtering- 24 hour

Number of octets dropped due to MAC table source address filtering- 24 hour

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Bridge counters valid for LAN, RPR IF VCG

(not RPR Span VCG) port

Green packets dropped due to congestion- 24 hour

Yellow packets dropped due to congestion- 24 hour

Bridge counters valid for LAN, RPR Span

VCG (not RPR IF

VCG) ports

Bridge counters valid for LAN, RPR Span

VCG (not RPR IF

VCG) ports

B - 1 3 0

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table

: Performance Monitoring

Object

dmxRprDayIUCAREDF dmxRprDayIUCAREDO dmxRprDayIUCBREDF dmxRprDayIUCBREDO dmxRprDayIUCCREDF dmxRprDayIUCCREDO dmxRprDayIMCAREDF dmxRprDayIMCAREDO dmxRprDayIMCBREDF

Description

Number of Unicast packets assigned to Class A and given drop precedence of red- 24 hour

Number of Unicast octets assigned to Class A and given drop precedence of red- 24 hour

Number of Unicast packets assigned to Class B and given drop precedence of red- 24 hour

Number of Unicast octets assigned to Class B and given drop precedence of red- 24 hour

Number of Unicast packets assigned to Class C and given drop precedence of red- 24 hour

Application

Metering counters valid for LAN ports only

Number of Multicast octets assigned to Class C and given drop precedence of red- 24 hour

Number of Multicast packets assigned to Class A and given drop precedence of red- 24 hour

Metering counters valid for LAN ports only

Number of Multicast octets assigned to Class A and given drop precedence of red- 24 hour

Number of Multicast packets assigned to Class B and given drop precedence of red- 24 hour

Metering counters valid for LAN ports only

365-372-300

Issue 8.0 September 2006

B - 1 3 1

SNMP Parameters and Traps

Table

: Performance Monitoring

Object

dmxRprDayIMCBREDO dmxRprDayIMCCREDF dmxRprDayIMCCREDO dmxRprDayICTRF dmxRprDayIATDF dmxRprDayITPF dmxRprDayOCTRLF dmxRprDayOATDF dmxRprDayOTPF dmxRprDayITTLF dmxRprDayDLONG dmxRprDayDHEC

Description

Number of Multicast octets assigned to Class B and given drop precedence of red- 24 hour

Application

Metering counters valid for LAN ports only

Number of Multicast packets assigned to Class C and given drop precedence of red- 24 hour

Number of Multicast octets assigned to Class C and given drop precedence of red- 24 hour

Metering counters valid for LAN ports only

Number of control frames received- 24 hour

Number of ATD frames received- 24 hour

Number of TP frames received- 24 hour

Number of control frames transmitted- 24 hour

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Number of ATD frames transmitted- 24 hour

Number of TP frames transmitted- 24 hour

Number of frames received with expired TTL values-

24 hour

Number of frames received with length exceeding the max allowed length- 24 hour

Number of frames received with HEC value not matching the expected HEC value- 24 hour

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

B - 1 3 2

365-372-300

Issue 8.0 September 2006

SNMP Parameters and Traps

Table Object

dmxRprDayDSS dmxRprDayDSA dmxRprDayDPTY dmxRprDayDSCFF

: Performance Monitoring

Description

Number of frames received sourced by this station and then received by this station- 24 hour

Number of frames received with bad SA (Multicast or

Broadcast)- 24 hour

Number of frames received with Parity value not matching the expected

Parity value- 24 hour

Number of SCFF frames received with bad FCS or bad parity- 24 hour

Application

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

Span counters valid for

RPR Span VCG only

365-372-300

Issue 8.0 September 2006

B - 1 3 3

SNMP Parameters and Traps

: Performance Monitoring

RPR Private Alarms

Starting in Release 6.0/4.0, DMX/DMXtend supports RPR alarms for the generation of private alarm traps as specified in the table below

(there are no traps specified in the RPR IEEE P802.17/D3.3 MIB). The specific type of alarm trap object to be issued depends on whether the alarm, when it occurs is an alarm, alarm cleared, standing condition, standing condition cleared or transient condition.

RPR Private Trap MIB Module dmxAlarmId

dmxEXSRSV dmxEXSRSVClr dmxTOPOUNST dmxTOPOUNSTClr dmxTOPOINCS dmxTOPOINCSClr dmxTOPOINV dmxTOPOINVClr dmxTOPOMAX dmxTOPOMAXClr dmxMISCBL dmxMISCBLClr dmxKALVTO dmxTOPOINCS dmxTOPOINCSClr

Description

RPR SPAN VCG - Excessive Reserved Rate on RPR

RPR SPAN VCG - Excessive Reserved Rate on RPR clear

RPR IF - RPR Topology Unstable

RPR IF - RPR Topology Unstable clear

RPR IF - RPR Topology Inconsistency

RPR IF - RPR Topology Inconsistency clear

RPR IF - RPR Topology Map Entry Invalid

RPR IF - RPR Topology Map Entry Invalid clear

RPR IF - RPR Topology Exceeded Max Stations

RPR IF - RPR Topology Exceeded Max Stations clear

RPR SPAN VCG - RPR Miscabling

RPR SPAN VCG - RPR Miscabling clear

RPR IF - RPR Keep-Alive Timeout

RPR IF - RPR Topology Inconsistency

RPR IF - RPR Topology Inconsistency clear

B - 1 3 4

365-372-300

Issue 8.0 September 2006

C: IS-IS Level 2 Routing Guidelines

Overview

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Purpose

This appendix details the guidelines for IS-IS Level 2 Routing in networks larger than 250 OSI nodes.

Contents

The following topics are included in this appendix:

Introduction

Area Address Assignment

Level 2 Router Assignment

IS-IS Level 2 Routing Remote Provisioning Sequence

IS-IS Level 2 Routing Provisioning Confirmation

Maximum Number of OSI Nodes

Engineering Rules and Guidelines

365-372-300

Issue 8.0 September 2006

C - 1

: IS-IS Level 2 Routing Guidelines

Introduction

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

If network sizes of more than 250 OSI nodes are required, hierarchical routing makes it possible to increase the number of nodes in an OSI management domain, (for example, NEs with OSI LAN and/or DCC connectivity for operations communications among the NEs).

Increasing the number OS nodes is achieved through the use of IS-IS

Level 2 Routing.

IS-IS Level 2 Routing involves assigning NEs to multiple areas of 250 nodes or less. Level 2 routers support OSI communications between the

NEs in different areas. Both the assignment of NEs to areas and the enabling of NEs as Level 2 routers is accomplished by provisioning

(refer to

“Area Address Assignment” (C-4)

and

“Level 2 Router

Assignment” (C-6) , respectively).

OSI Node vs. NE terminology

Each DMX is an OSI node, but some other NEs support multiple OSI nodes within a single NE, so the term “OSI node”, or simply “node”, is generally used in this context instead of “NE”.

Advantages

The primary advantage of IS-IS Level 2 Routing is to limit the OSI routing information that needs to be maintained by each node. Each node within an area maintains routing tables to route OSI LAN and

DCC messages to the other nodes in the same area. If a node needs to route a message to a node in a different area, the node relies on a

Level 2 router in its own area to route the message to a Level 2 router in the target area and from that Level 2 router to the target node within that area.

The Level 2 routers route messages between nodes in different areas.

These messages include all of the NE-NE (and OS-NE) OSI communications required for the supported OI applications, (for example, TL1 login messages from TL1-GNEs to TL1-RNEs.)

In addition to maintaining a routing table to route messages to other nodes in the same area, Level 2 routers need to maintain routing information for the Level 2 routers in all other areas (but not for all nodes within each of those other areas).

C - 2

365-372-300

Issue 8.0 September 2006

Introduction

: IS-IS Level 2 Routing Guidelines

Symbols

The graphical examples is this appendix use the symbols that are defined in the following figure.

Figure C-1 illustrates an example

network with nodes assigned to four different areas connected by Level

2 routers.

Figure C-1 Network with Level 2 Routers

Area 1

Level 2 Subdomain

Area 2

Area 4

Area 3

= NE Level 1 Router

= NE Level 2 Router

= Generic Level 2 Router

= SNMS

= OSI LAN

= DCC

= Area

= Level 2 Subdomain

NC-DMX-042

365-372-300

Issue 8.0 September 2006

C - 3

: IS-IS Level 2 Routing Guidelines

Area Address Assignment

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Area address

The area address is the first 26 characters of each DMX Network

Services Access Point (NSAP). [DMX supports a fixed-length 40character (20-byte) NSAP only.] The first eight characters of the

NSAPs are always the same and cannot be changed. The remaining

18 characters of the NSAP area address are provisionable but only the

Area field should be changed to assign a node to a different area. The remainder of the NSAP includes the System Identifier field, which is unique to each node, and the Selector (SEL) field.

The following table provides a break-down of an NSAP.

Table C-1 Area Addresses

NSAP Field: AFI IDI

1 2

IDI

PAD

DFI

1 Bytes:

Default Value:

(hex)

39 840 F 80 not provisionable

Organization

RES RD Area

System

Identifier

SEL

3 2 2 2 6 1

000000 0000 0000 0000 user provisionable none not

00 provisionable

A group of nodes are assigned to an area by changing each node’s

NSAP Area field to the same value. The entire NSAP area address must be identical for all nodes in an area and different from the NSAP area addresses for all other areas.

If more than one separate area with the same area address exists, routing to these areas from other areas would not be predictable and couldn’t be expected to function properly.

C - 4

365-372-300

Issue 8.0 September 2006

Area Address Assignment

: IS-IS Level 2 Routing Guidelines

Area field

The Area field consists of four hexadecimal characters, with a default value of 0000 (hex). TL1 command

ENT-ULSDCC-L3

can be used to change the Area field.

Area Terminology

Despite the technical differences between the area address and the Area field described previously, the term area address is commonly used to refer to the Area field value. Thus, for convenience, the term area address is used throughout this document.

Multiple area addresses

Multiple area addressing is the capability for a node to be assigned more than one area address. The provisioning of multiple area addresses is not supported on DMX, directly. However, if multiple area addresses are provisioned in another node, DMX would recognize its own primary area address plus up to two other area addresses. The use of multiple area addresses is not recommended.

365-372-300

Issue 8.0 September 2006

C - 5

: IS-IS Level 2 Routing Guidelines

Level 2 Router Assignment

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

OSI communications is supported within a network which may consist of a single area or multiple areas. Level 1 routers provide interconnectivity between nodes in an area (all DMXs are Level 1 routers). Level 2 routers provide connectivity between areas.

Guidelines and default

In a network with multiple areas, each area must contain at least one

Level 2 router. An area without a Level 2 router would be isolated from the rest of the network. The adjacent set of Level 2 routers form the

Level 2 subdomain. For proper OSI routing, every Level 2 router should have at least one neighbor (via OSI LAN or DCC) that is also a

Level 2 router. At least one of the Level 2 routers in an area must be adjacent to a Level 2 router in another area, otherwise, the former area would be isolated from the rest of the network.

Each DMX is not a Level 2 router by default. TL1 command

ENT-ULSDCC-L3

can be used to enable any DMX as a Level 2 router.

C - 6

365-372-300

Issue 8.0 September 2006

: IS-IS Level 2 Routing Guidelines

IS-IS Level 2 Routing Remote Provisioning Sequence

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Avoid isolating nodes

An important goal is to avoid isolating any nodes when provisioning area addresses and Level 2 routers remotely. Isolating a node may require craft dispatch to the isolated node to recover. To avoid isolating nodes, the sequence for remote provisioning is established with respect to the local node to which the WaveStar

CIT is connected or the

TL1-GNE through which Navis™ Optical Element Management

System (Navis™ Optical EMS) is connected. Typically, the local node or TL1-GNE is provisioned to be a Level 2 router first, but its area address is not changed initially. This general sequence can be modified in networks with redundant OSI LAN or DCC connectivity between and within areas.

The nodes and sub-tending rings that are furthest away from this local node or TL1-GNE are provisioned first.

Work back toward the local node or TL1-GNE’s sub-tending ring.

Provision the local node or TL1-GNE’s sub-tending ring.

Provision the local node or TL1-GNE last.

If Navis™ Optical EMS is part of the network via an OSI LAN or

WAN interface, provision the area address for the Navis™ Optical

EMS.

Important!

Before assigning area addresses and Level 2 routers in a network, be sure no alarms (especially

DCC failure

alarms) exist; otherwise, even the recommended remote provisioning sequence might result in isolated nodes. To confirm the network alarm status, it is recommended that a centralized maintenance center with TL1 OS support be consulted.

365-372-300

Issue 8.0 September 2006

C - 7

IS-IS Level 2 Routing Remote Provisioning Sequence

: IS-IS Level 2 Routing Guidelines

Provisioning sub-tending rings

Always provision new area addresses for a sub-tending ring by starting with a node that is adjacent to the node that connects this sub-tending ring to the rest of the network, and then provision the area address for each sequential adjacent node going around the sub-tending ring.

Provision the area address of the connecting node last, especially if the connecting node supports multiple sub-tending rings.

For single-homed sub-tending rings, provision the node that will be the

Level 2 router node last; otherwise, nodes in its area could be isolated.

For dual-homed rings, provision one of the nodes that will be Level 2 router first, so that OSI connectivity is established with provisioned nodes as soon as they complete their controller resets.

Minimizing OSI communications disruption

Another important goal is to provision the network in such a way that

OSI communications disruption is minimized. Changing a node’s area address and/or enabling a node as a Level 2 router causes the node to reset its controller. The reset is immediate and is part of the completion of the command. In addition to temporarily disrupting OSI communications, controller resets temporarily disable automatic transmission protection switching.

As one node is undergoing a controller reset in an area, the next adjacent node should be provisioned to minimize the overall time required to provision the nodes in an area and minimize the time that

OSI communications with the nodes in the area are lost.

Changing a node’s area address and enabling a node as a Level 2 router, if appropriate, should usually both be done with a single command per node.

C - 8

365-372-300

Issue 8.0 September 2006

: IS-IS Level 2 Routing Guidelines

IS-IS Level 2 Routing Provisioning Confirmation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

TL1

RTRV-MAP-NETWORK

commands can be used to confirm the area address and Level 2 router assignments of all nodes with OS LAN or

DCC connectivity in a network.

Small networks

In a small network without IS-IS Level 2 Routing, the

RTRV-MAP-

NETWORK

response includes the NSAPs (including the embedded area address field) of the local node and all remote nodes. This command may also be useful to confirm the uniqueness of the area addresses before combining two existing networks into one large network requiring IS-IS Level 2 Routing.

Large networks

In large networks with IS-IS Level 2 Routing, the

RTRV-MAP-

NETWORK

response can vary based on whether or not the local node is a Level 2 router itself.

If the local node is not a Level 2 router, the response includes only remote nodes in the same OSI area as the local node and indicates which remote node is the default Level 2 router for the local node.

The default Level 2 router is the node that the local node would rely on to route an OSI message outside the local NE’s own area.

When there are multiple Level 2 routers in the same area, not all nodes in the area would identify the same default Level 2 router typically.

If the local node is a Level 2 router, user input dictates whether the response includes: a.

only remote nodes in the same OSI area as the local node (as in #1 above) but indicating which of those remote nodes are

Level 2 routers b.

all remote nodes that are Level 2 routers across all OSI areas.

Thus, with a

RTRV-MAP-NETWORK

command to one Level 2 router in each area, all nodes in a large network with IS-IS Level 2 Routing can be identified. One

RTRV-MAP-NETWORK

command at at time per area should suffice and is recommended to avoid unnecessarily burdening the network with many simultaneous or redundant TARP queries.

365-372-300

Issue 8.0 September 2006

C - 9

IS-IS Level 2 Routing Provisioning Confirmation

: IS-IS Level 2 Routing Guidelines

Problem isolation

TL1 command

RTRV-MAP-NEIGHBOR

may indicate and help resolve

IS-IS Level 2 Routing provisioning mistakes. This command highlights any neighbors with which DCC is enabled but OSI communications is not fully functional. When addressed to a reachable node with an unreachable neighbor, this command identifies the NSAP area address and the Level 2 router status, if known, of the unreachable neighbor.

The unreachable neighbor may simply have the wrong area address or both nodes may need to be enabled as Level 2 routers.

There is no standing alarm or status condition at a node with Level 2 router functionality enabled or disabled. There is no automatic means of determining whether the area address is consistent with the rest of the network. The user must confirm that all IS-IS Level 2 Routing rules have been followed to ensure successful OSI communications among the nodes in a network.

C - 1 0

365-372-300

Issue 8.0 September 2006

: IS-IS Level 2 Routing Guidelines

Maximum Number of OSI Nodes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maximum number of nodes per area and OSI domain

The total number of nodes per OSI area cannot exceed 250. The total number of nodes in the OSI domain cannot exceed 1000.

365-372-300

Issue 8.0 September 2006

C - 1 1

: IS-IS Level 2 Routing Guidelines

Engineering Rules and Guidelines

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview

To use IS-IS Level 2 Routing, the user must plan and engineer the provisioning of Level 2 routers and area addresses in the network.

The goal is to create a network with all nodes having OSI LAN or DCC connectivity with each other so that access to all the nodes can be gained from any node in the network.

Rules must be followed to assure OSI LAN and DCC message routing.

Guidelines are recommendations that add survivability in the event of a node, OSI LAN or DCC failure. Rules must be followed. Guidelines

should be followed. There may be customer applications that cannot adhere to some or all of the guidelines. In most cases, the potential consequence is that a single failure would at least partially disrupt operations communications.

C - 1 2

365-372-300

Issue 8.0 September 2006

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Rule: OSI LAN or DCC connectivity within an area

All nodes in an area must have OSI LAN or DCC connectivity within the area to all other nodes in the same area. Otherwise, the area would be segmented and message routing could not be expected to function properly.

Figure C-2 illustrates a correct and an incorrect example of

assigning nodes to areas.

Figure C-2 Assigning Areas

CORRECT

INCORRECT Both A and B are isolated

= NE Level 1 Router

= NE Level 2 Router

= DCC

= Area

nc-dmx-043

365-372-300

Issue 8.0 September 2006

C - 1 3

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Rule: single Level 2 router subdomain

All Level 2 routers must have OSI LAN or DCC connectivity, either directly or indirectly via other Level 2 routers, to all other Level 2 routers in the network to form a single Level 2 router subdomain that provides connectivity to all areas. If more than one Level 2 router subdomain exists, the network becomes segmented and routing will not function properly.

Figure C-3 illustrates a correct and two incorrect examples of assigning

a Level 2 router subdomains.

Figure C-3 Assigning Subdomains

CORRECT

INCORRECT

This Level 2 router subdomain and area are isolated

INCORRECT

This area is isolated

= NE Level 1 Router

= NE Level 2 Router

= DCC

= Area

= Level 2 Subdomain nc-dmx-044

C - 1 4

365-372-300

Issue 8.0 September 2006

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Guideline: redundant routes within the Level 2 subdomain

When practical, redundant routes in the Level 2 subdomain should be available between all Level 2 routers to ensure that proper routing will occur in the event of a single failure. To satisfy this guideline, every

Level 2 router has at least two other Level 2 routers as direct neighbors.

Figure C-4 illustrates a recommended example and an example that is

not recommended for redundant routes within the Level 2 subdomain:

Figure C-4 Redundant Routes with the Level 2 Subdomain

RECOMMENDED

This Level 2 IS has only one neighboring

Level 2 IS

NOT RECOMMENDED

= NE Level 1 Router

= NE Level 2 Router

= Generic Level 2 Router

= SNMS

= OSI LAN/WAN

= DCC

= Area

= Level 2 Subdomain nc-dmx-045

365-372-300

Issue 8.0 September 2006

C - 1 5

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Guideline: Level 2 router assignment in a ring

The recommended number of Level 2 routers in a ring may be one of the following:

• None

• One

• All nodes in the ring

• Two; for example, when dual-homing or dual ring interworking

(DRI) is used.

Figure C-5 illustrates examples of recommended Level 2 router

assignments in various ring configurations.

Figure C-5 Recommended Level 2 Router Assignments

All Level 2 routers

No Level 2 routers

One Level 2 router

Two adjacent

Level 2 routers (DRI)

= NE Level 1 Router

= NE Level 2 Router

= Generic Level 2 Router

= SNMS

= OSI LAN/WAN

= DCC

Two adjacent

Level 2 routers nc-dmx-046

C - 1 6

365-372-300

Issue 8.0 September 2006

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Guideline: Level 2 router area assignments in a ring

For a ring of Level 2 routers, the recommended area assignments may be one of the following:

• All Level 2 routers are part of the same area.

• Each Level 2 router is part of a different area.

• A pair of adjacent Level 2 routers are in the same area (for example, with dual-homing or DRI), with either the other Level 2 routers similarly paired off or individually in different areas.

Figure C-6 illustrates examples of recommended Level 2 router area

assignments in a ring.

Figure C-6 Recommended Area Assignments same area different areas

= NE Level 1 Router

= NE Level 2 Router

= DCC

= Area

dual homing different areas

NC-DMX-047

365-372-300

Issue 8.0 September 2006

C - 1 7

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Guideline: adjacent Level 2 routers within an area

It is recommended that dual Level 2 routers in an area be adjacent to each other and have a redundant route within the area. Failure to meet this guideline would result in some messages not being routed properly in the event of a single failure that divides an area into two separate islands.

Figure C-7 illustrates a recommended example and two examples that

are not recommended of dual Level 2 routers in an area:

Figure C-7 Recommended Placement of Level 2 Routers

Failure

RECOMMENDED

If A or B sends a message to Z and there is a DCC failure between A and Z, routing will survive the failure.

Failure

NOT RECOMMENDED

If A or B sends a message to Z and there is a DCC failure between A and Z, routing will not be successful.

Failure

NOT RECOMMENDED

If A or B sends a message to Z and there is a DCC failure between A and Z, routing will not be successful.

= NE Level 1 Router

= NE Level 2 Router

= DCC

= Area nc-dmx-048

C - 1 8

365-372-300

Issue 8.0 September 2006

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Guideline: Navis™ Optical

EMS own area address and

Level 2 router

If Navis™ Optical EMS (or any other OS) access is via OSI LAN (or

WAN), Navis™ Optical EMS should be assigned to a different area and rely on a generic Level 2 router to communicate with a large network. (Navis™ Optical EMS is not expected to be a Level 2 router itself.) This is recommended to avoid routing all messages to/from

Navis™ Optical EMS through a single NE serving as a Level 2 router.

Although not shown in the examples below, Navis™ Optical EMS can support a second, redundant OSI LAN port. Each Navis™ Optical

EMS OSI LAN port has its own unique NSAP but both must be assigned the same area address.

365-372-300

Issue 8.0 September 2006

C - 1 9

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Figure C-8 illustrates a recommended example, an example that is not

recommended, and an incorrect example of Navis™ Optical EMS access via OSI LAN/WAN.

Figure C-8 Recommended Navis™ Optical EMS Access via OSI

LAN/WAN

Generic Level 2

Router for Navis

Optical EMS instead of an NE

RECOMMENDED

All Navis

Optical EMS messages through this one node

NOT RECOMMENDED

Navis

Optical

EMS has a unique area address but no

Level 2 router

INCORRECT

= NE Level 1 Router

= NE Level 2 Router

= Generic Level 2 Router

= Navis Optical EMS

= OSI LAN/WAN

= DCC

= Area nc-dmx-049

C - 2 0

365-372-300

Issue 8.0 September 2006

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Rule: Level 2 routers on an

OSI LAN

If an OSI LAN (or WAN) is used to connect between areas, then at least one node in each area on the OSI LAN must be provisioned to be a Level 2 router. Otherwise, the areas won’t route to each other via the

OSI LAN.

Figure C-9 illustrates a correct and an incorrect example of Level 2

router assignments on an OSI LAN:

Figure C-9 Level 2 Router Assignments on an OSI LAN

CORRECT

INCORRECT

This area is isolated

= NE Level 1 Router

= NE Level 2 Router

= Generic Level 2 Router

= Navis

Optical EMS

= OSI LAN/WAN

= DCC

= Area nc-dmx-050

365-372-300

Issue 8.0 September 2006

C - 2 1

Engineering Rules and Guidelines

: IS-IS Level 2 Routing Guidelines

Guideline: OSI LAN redundancy

If an OSI LAN (or WAN) is the only method of connecting between areas, then at least two Level 2 routers directly connected to the

OSI LAN for each area are recommended for redundancy purposes. A second, separate OSI LAN hub would provide additional redundancy.

Figure C-10 illustrates a recommended example for providing

redundancy between areas connected solely by OSI LANs:

Figure C-10 OSI LAN Redundancy

RECOMMENDED

= NE Level 1 Router

= NE Level 2 Router

= Generic Level 2 Router

= Navis Optical EMS

= OSI LAN/WAN

= DCC

= Area nc-dmx-051

C - 2 2

365-372-300

Issue 8.0 September 2006

D Physical, Electrical, and

Thermal Compatibility

Requirements for OSP

Applications

Overview

Purpose

This document details the specific requirements and standards that must be adhered to when installing the DMX, DMXtend, and

DMXplore in Outside Plant (OSP) cabinets. It describes the physical, electrical, and thermal requirements necessary to ensure Metropolis

DMXtend Access Multiplexer equipment operates reliably in OSP applications.

A cabinet that does not meet the requirements of this document will negatively affect the performance, reduce service life, and threaten service continuity of the Metropolis

DMXtend Access Multiplexer products described herein.

This document should be used by equipment suppliers, service providers and equipment system integrators of network access equipment.

Important!

This document is not intended to be used as a cabinet-level end-product requirements document. Cabinet level, end-product requirements (e.g., cabinet level electrical emissions, needed battery backup, etc) must be agreed to by the system supplier and customer.

365-372-324

Issue 4.2, April 2006

D - 1

Overview

Appendix D

Definitions Requirement

Feature or function that is necessary to satisfy the needs of an end user.

A requirement contains the words shall or must.

Objective

Feature or function that is desirable and may be required by an end user. An objective contains the words should or may.

Metropolis

DMX/DMXtend

Whenever “Metropolis

DMX products/services” is used in this section, it refers to the DMX, DMXtend, and DMXplore products only.

Contents

The following hardware is described in this chapter:

Shelf Description

Physical Requirements

Electrical Requirements and Objectives

Environmental Requirements and Objectives

Test Verification and Qualification

References

D - 2

365-372-324

Issue 4.2, April 2006

Appendix D

Shelf Description

Overview

The figures below illustrate typical shelf configuration for the four

Metropolis

DMX Access Multiplexer products. Meeting the requirements in this document for the Metropolis

DMXtend Access

Multiplexer shelves will ensure proper operation of all cabinet applications.

DMX Side/Front View Figure D-1 DMX Shelf Side/Front View with Mounting Bracket

19”

LNW6

Sx:x

28DS1

LUCENT

LNW6

Sx:x

28DS1

LUCENT

LNW16

Sx:x

12DS3/EC1

LUCENT

LNW16

Sx:x

12DS3/EC1

LUCENT

LNW67

Sx:x

1G SX

LUCENT

OC-48

1310 LR

LUCENT

LNW1

Sx:x

SYSCTL

LUCENT

177D

Sx:x

BLANK

LUCENT

OC-48

1310 LR

LUCENT

LNW36

Sx:x

OC-3

LUCENT

LNW36

Sx:x

OC-3

LUCENT

OC-12

1310LR

LUCENT

OC-12

1310LR

LUCENT

FAULT

ACTIVE

28DS1

FAULT

ACTIVE

FAULT

ACTIVE

FAULT

ACTIVE

28DS1 12DS3/

EC1

12DS3/

EC1

FAULT

ACTIVE

1G SX

OUT

FAULT

ACTIVE

OC-48

OLIU

OUT IN

FAULT

ABN

ACO

TEST

IND

SEL

UPD/

INT

LAN

CIT

232

177D

BLANK

FAULT

ACTIVE

OC-48

OLIU

FAULT

ACTIVE

OC-3

OLIU

OC-3

OLIU

OUT IN OUT IN

FAULT

ACTIVE

FAULT

ACTIVE

OC-12

OLIU

FAULT

ACTIVE

OC-12

OLIU

OUT IN 1 1

OUT IN OUT IN

1 1 2

2 2

4 4

Heat Baffle

A1 A2 B1 B2

Metropolis

DMX

G1 M1 CTL G2 M2 C1 C2 D1

OFF

13.75"

17.6”

MA DMX 410

DMXtend Side/Front View Figure D-2 DMXtend Shelf Side/Front View with Mounting

Bracket

Fan Filter

BRK A 10A

BRK B 10A

8.75”

Fiber

Tray

Metropolis

DMXtend

CTL

LNW39

DS1/DS3/16/31

Lucent

LNW39

DS1/DS3/16/31

Lucent

A2/B2

A1/B1

12DS3/EC1

OUT IN

OUT

28DS1

LNW40

Sx:x

OC3/1.3IR1

Lucent

LNW40

Sx:x

OC3/1.3IR1

Lucent

Lucent

Fan Unit

POWER

FAULT

13.75”

17.5”

MA-DMXtend-096

365-372-324

Issue 4.2, April 2006

D - 3

Shelf Description

Appendix D

DMXplore Wall-mount Side/

Front View

Figure D-3 DMXplore Wall-mount Shelf Side/Front View with

Mounting Bracket

10.5”

FAULT

CR/MJ

MN/ABN

ACO

LAN

CIT

RS-232

OUT

VLNC6

S1:1

XX:x

Lucent

FAULT

ACTIVE

OUT

FAULT

ACTIVE

XX:x

Lucent

PWR-A

PWR-B

-48V-A

RTN-A

RTN COM

GRD

RTN-B

-48V-B

1 2 3 4

C GROUP

OUT

1 2 3

B GROUP

2 3 4

6 7

A/D GROUP

10 11

13 14 15 16

MDI MDO ALARM

VLNC1

S1:1

SYSCTL

Lucent

CTL

12”

7.5”

DMXplore Rack-mount

Shelf Side/Front View

Figure D-4 DMXplore Rack-mount Side/Front View with

Mounting Bracket

MA-DMXplore-042

FAN

FAULT

PWR ON

Lucent

3.5

17.3”

MA-DMXplore-043

13.5”

D - 4

365-372-324

Issue 4.2, April 2006

Shelf Description

Appendix D

Metropolis

DMXtend

Access Multiplexer Product

Conformance

Metropolis

DMXtend Access Multiplexer equipment has been designed and tested to meet industry requirements for physical, electrical, thermal and product safety characteristics.

Principal requirements for Metropolis

DMX equipment are as follows:

• GR-63, covering physical requirements (earthquake resistance, thermal shock, fire, etc.)

• GR-1089 covering electrical requirements (electromagnetic interference, electrostatic discharge, grounding, etc.)

• CSA-C22.2, No. 60950-00, UL60950

Safety of information technology equipment.

365-372-324

Issue 4.2, April 2006

D - 5

Appendix D

Physical Requirements

Cabinet Design and

Equipment Reliability

Outside plant cabinets for use with Metropolis

DMX equipment in

NAR applications shall have demonstrated compliance in accordance with GR-487

. GR-487 describes cabinet level requirements to ensure a suitable environment for telecommunications equipment. Typical requirements covered in this specification include Water and Dust

Intrusion, Wind-Driven Rain, Thermal Shock, Impact Resistance and

Shock and Vibration.

The table below shows the dimensions of the Metropolis

DMX equipment.

Table D-1 Metropolis

Dimensions and Weight

Dimensions

DMX

Width

Height

Depth

17.6

13.75

Center-to-Center Mounting Hole Width 22.31

Metropolis

Products

DMXtend DMXplore

Wall Mount Rack Mount

7.5

17.5

8.75

22.31

10.5

12.0

17.3

3.5

13.5

22.31

Vertical Hole Spacing

Mounting Screw Size

(thread forming screw)

A pattern of 0.5 inch spacing.

No. 12x24

Shelf Weight lbs 38 Empty

57 Full

15 Empty

30 Full

7 Empty

10 Full

1) All dimensions are provided in inches unless otherwise specified

2) 15 inches with interface connectors. 16 inches with connectors and cover.

3) Not applicable for a wall-mounted DMXplore. For a Rack-mount or rack-mounted Wall-mount version of the

DMXplore the center-to-center mounting hole width is 22.31”.

D - 6

365-372-324

Issue 4.2, April 2006

Physical Requirements

Appendix D

Mounting Bracket

Positions

The figure below illustrates typical mounting bracket placements on the DMX shelf.

Figure D-5 Mounting Bracket Positions on DMX Shelf

Equipment Compartment

The DMXtend and DMXplore rack mount shelves offer the same mounting bracket as DMX. The mounting brackets can be placed differently depending on customer requirements (6, 5, or 8 inches back from the front of the shelf).

All doors, covers and faceplates that are part of the Metropolis

DMX systems design shall be in place when installed in the cabinet to minimize losses in cooling and maximize resistance to electromagnetic interference. Apparatus Blanks (see engineering drawings

) are ordered separately from the shelf and shall be used where no circuit packs are installed.

Splicing Compartment

Cable access ports shall be provided in the base of the splicing compartment to permit the entrance of metallic and fiber cables into the equipment. Ports shall be sized to allow cables to be placed in accordance with minimum bend radii guidelines, as specified by the cable supplier.

Battery Compartment

If a battery compartment is provided, it shall be segregated from the electronics compartment. A seal shall be provided to prevent gases from seeping into the electronics and splicing compartments. The compartment shall be vented to the outside.

365-372-324

Issue 4.2, April 2006

D - 7

Physical Requirements

Appendix D

Air Flow Air Flow Capacity

The fan unit shall supply a sufficient volume of air to cool the

Metropolis

DMX equipment whether using DMX internal fans or cabinet-level cooling equipment (it is required that Metropolis

DMX internal fan units be removed when installing the DMX, DMXtend, and

DMXplore in OSP environments). The amount of air required shall be based upon the environmental conditions and the self heating rates of the electronic equipment. An air mover shall be functional whenever circuit packs are in operation including during equipment AC power outages.

Refer to Environmental Requirements and Objectives: page D-15 for

thermal performance requirements.

Inlet/Exhaust

DMX requires air to enter the bottom of the shelf, flow vertically upward and exhaust at the top (and rear if an integrated baffle is used).

This direction of flow shall be provided to properly cool the circuit packs installed in the shelf.

DMXtend and DMXplore rack mount shelves require that air enters at the right of the shelf and exhausts on the left. The placement of these shelves should minimize blockage of vertical airflow. DMXtend can also be vertically mounted with the fan unit at the bottom of the shelf, allowing vertical airflow.

The DMXplore Wall-mount shelf is convection cooled.

The fan filter must be removed for all Metropolis

DMX shelves in all cabinets (the heat baffle must also be removed on the DMX shelf). If the cabinet fan can guarantee at least 200 LFM (linear feet per minute) through the shelf, then the internal fan is not needed. It is recommended that the fan be removed in these instances, and used as a spare for non

OSP deployments throughout your network.

Cable and Connector

Interfaces

Cable Placement and Routing

Refer to the Metropolis

DMX product’s respective Installation

Manuals

6 for cable placement and routing information. Cables shall be routed in accordance with the guidelines provided in the Installation

Manuals. Circuit pack cables shall be routed with half of the total number of cables from each side of the shelf.

D - 8

365-372-324

Issue 4.2, April 2006

Physical Requirements

Appendix D

Cable Routing

Cable shall be rated for a minimum temperature of 80 o

Connector Contacts

All connector contacts that mate to Metropolis

DMX equipment shall be of similar contact finishes. Lucent Technologies recommends the use of gold with a minimum of 30 micro-inches.

Installation and

Maintenance

Engineering and Interconnection drawings shall be made available to

Lucent Technologies upon request.

365-372-324

Issue 4.2, April 2006

D - 9

Appendix D

Electrical Requirements and Objectives

Overview of

Power Requirements

The power consumption of the Metropolis

DMX products is dependent on the circuit packs installed and their operating state. These variables must be taken into account when sizing the power system.

DMX Power supply

The following table lists DMX shelf power requirements.

Table D-2 DMX Shelf Power Supply Requirements

Item

Voltage range

Power Feeders

Description

-40.0V to -60.0V

two -48V power feeders

[BREAKER (A) and BREAKER (B)]

Circuit Breakers (two per shelf) 30.0 A

The following table lists DMX 20 Amp shelf power requirements.

Table D-3 DMX 20 Amp High Capacity Shelf Power Supply

Requirements

Item

Voltage range

Power Feeders

Description

-40.0V to -60.0V

two -48V power feeders

[BREAKER (A) and BREAKER (B)]

Circuit Breakers (two per shelf) 20.0 A

D - 1 0

365-372-324

Issue 4.2, April 2006

Electrical Requirements and Objectives

Appendix D

DMX Current drains

The following table provides the maximum current drain requirements for a shelf.

Table D-4 DMX Shelf Current Drains

Shelf

DMX Shelf (20 Amp)

DMX Shelf (30 Amp)

Current Drains per Feeder in

Amperes

Maximum

−

48V

14.5

Maximum

−

40V

17.5

23.0

27.5

365-372-324

Issue 4.2, April 2006

D - 1 1

Electrical Requirements and Objectives

Appendix D

DMXtend Power supply

The table below lists DMXtend power requirements.

Table D-5 DMXtend Power Supply Requirements

Item

Voltage range

Power Feeders

Circuit Breakers

Description

-40.0 VDC to -57.0 VDC two -48V power feeders

[BREAKER (A) and BREAKER (B)]

10.0A

DMXtend Current drains

The following table provides the maximum current drain requirements for a shelf.

Table D-6 DMXtend Shelf Current Drains

Shelf

DMXtend Shelf

Current Drains per Feeder in Amperes

Maximum

−

48V

7.1

Maximum

8.5

−

40V

D - 1 2

365-372-324

Issue 4.2, April 2006

Electrical Requirements and Objectives

Appendix D

DMXplore Power supply

The table below lists DMXplore power requirements.

Table D-7 DMXplore Power Supply Requirements

Item

Voltage range

Power Feeders

Circuit Breakers

Description

-40 to -57 volts

-48VDC (A and B)

Two, 2A fuses

DMXplore Current drains

The following table provides the maximum current drain requirements for a shelf.

Table D-8 DMXplore Shelf Current Drains

Shelf Current Drains per Feeder in Amperes

List 1

Maximum

−

48V

1.25 Amps

List 2

Maximum @

−

40V

1.5 Amps DMXplore Shelf

Power Quality

Metropolis

DMX products require a reliable low noise power source in accordance with GR-947

. This is usually accomplished by float charging batteries at the input to the Metropolis

DMX shelves.

Batteries are installed to provide back up power in the event of AC power outages. When deployed in a float charge configuration they also provide filtering of AC power line drop outs and noise generated by equipment in the cabinet. In all cases power must be configured to avoid dropping below or exceeding the voltage limits listed in the tables above.

Electrical Noise

Care must be taken to insure that electrical noise generated by the power system, fans, or other equipment does not interfere with the operation of the Metropolis

DMX products. Electrical noise on the –

48 volt power lines at the shelf must not exceed the voice frequency and wide-band noise limits in accordance with GR-947.

Interruptions

Momentary AC power line interruptions are accommodated by the batteries on float charge.

365-372-324

Issue 4.2, April 2006

D - 1 3

Electrical Requirements and Objectives

Appendix D

Inrush Current

While there is no requirement to limit the rate of power application to the Metropolis

DMX shelves, the voltage at the shelf must remain within the specified limits at all times.

Battery Backup

In all cases battery backup power must be configured to avoid dropping

below the voltage limits listed between Table D-2 on page 10 and

Table D-8 on page 13. The preferred method of battery backup is a

float charge configuration. Alternatively, a separate battery and charger system can be used utilizing a diode “OR” configuration. Systems employing transfer switches are not recommended unless sufficient capacitance is installed to carry the system over through the transfer period.

Alarm Interfaces Cooling System Failure

A system failure alarm shall be provided for cabinet cooling systems with forced air ventilation and other heat exchanger systems

Grounding and Bonding

High Temperature

A temperature sensor shall be located in the electrical equipment compartment to provide a high temperature alarm when an internal cabinet temperature of 65 o

C is reached. The air temperature shall be measured at the inlet of the upper-most Metropolis

DMX shelf.

Grounding must meet the appropriate Telcordia

, UL

, and NEC

10 requirements for outside plant and customer premises applications. The

Metropolis

DMX shelves require a single common ground reference.

The Metropolis

DMX shelf frame must be bonded to an earth ground within the cabinet. Metropolis

DMX shelf mounting screws should be used to provide a low impedance multipoint electrical connection through the mounting structure to earth ground. A frame ground wire located on the shelf shall be connected to the cabinet ground.

I/O Protection

The DS3 interfaces (traffic ports) or other metallic telecom interfaces shall not leave the cabinet unless connected to telecom devices providing primary and secondary protection, as per GR-1089 and UL-

60950

(not applicable for Ethernet packs).

D - 1 4

365-372-324

Issue 4.2, April 2006

Appendix D

Environmental Requirements and Objectives

Physical Strength Vibration

The cabinet shall be resistant to continuous low level vibrations from sources including train and vehicular traffic, rotating machinery, construction activities, etc. Physical tests shall be performed to assure the cabinet does not amplify vibrations from these sources such that the vibration levels transmitted to the equipment do not exceed design limits. Tests shall be performed in accordance with GR-487 and GR-63 to verify the performance of the cabinet and equipment during vibratory test conditions.

Thermal Operating

Temperature

Operating Temperature Range

Inlet air to the Metropolis

DMX equipment shall be controlled within the range of -40°C to +65°C. Ambient air from outside the cabinet cannot be introduced into the electronics compartment or used in any way to directly cool the Metropolis

DMX equipment within the cabinet.

Heat exchange systems for cabinet shall be sized so that maximum inlet temperature will not exceed 65°C even when the shelf is equipped in such a way that it approaches the maximum current drains detailed in

Table D-4 DMX Shelf Current Drains, Table D-6 DMXtend Shelf

Current Drains, and Table D-8 DMXplore Shelf Current Drains. Also,

the cabinet shall be sized to ensure that inlet temperature shall not exceed 65 o

C given both severe outside ambient temperature and solar heating relative to the conditions of the region where the shelf is deployed.

The supplier shall supply performance data upon request for cabinets cooled by compact heat exchangers or any other method. This information may include the appropriate factor of safety, or excess capacity, accounting for normal fouling of the heat exchanger core.

During operation, the time rate of change of the internal air temperature shall not exceed 30°C/hr as the result of solar heating and radiation cooling of the enclosure, and power cycling the equipment.

365-372-324

Issue 4.2, April 2006

D - 1 5

Environmental Requirements and Objectives

Appendix D

Air Velocity

The self-heating of the Metropolis

DMXtend Access Multiplexer

DMX is dissipated primarily by forced convection cooling as the result of air blowing vertically between the parallel circuit cards. When DMX is deployed in OSP cabinets, the air flow (provided by cabinet fans) shall be no less than 300 LFM (Linear Feet per Minute).

The self-heating of the Metropolis

DMXtend and DMXplore Rackmount is dissipated primarily by forced convection cooling as the result of air blowing horizontally between the parallel circuit cards. Air flow for the DMXtend and DMXplore Rack-mount shelves is provided by fans inside the shelves themselves. Still, it is important that the air flow caused by cabinet fans not be at such a velocity that it impedes the proper functioning of the DMXtend and DMXplore shelf fans. The

DMXtend requires an airflow of no less than 200 LFM. The DMXplore requires a minimum airflow of 100 LFM.

The DMXplore Wall-mount shelf is convection cooled.

Cabinet Condensation

The relative humidity of the internal air of an outside cabinet shall be maintained in accordance with GR-63. This applies even when the equipment within the cabinet is in an unpowered condition, e.g., during installation of equipment. During such times a source of heat, or desiccant packs, shall be provided for maintaining the necessary relative humidity level.

D - 1 6

365-372-324

Issue 4.2, April 2006

Appendix D

Test Verification and Qualification

Overview

Metropolis

DMXtend Access Multiplexer equipment shall be installed in cabinets that have demonstrated compliance in accordance with GR-487 and all other specifications as required by this document.

A cabinet that does not meet the requirements of this specification will negatively affect the performance, reduce service life, and threaten service continuity of any Metropolis

DMXtend Access Multiplexer system.

Compliance Reports covering cabinet performance to these specifications shall be made available to Lucent Technologies upon request.

System Thermal

Performance Verification

For the fully equipped cabinet configuration, a functional test of the

Metropolis

DMXtend Access Multiplexer shelf shall be performed with all systems powered at their appropriate levels for typical service applications that approach the maximum current drains detailed in

Table D-4 DMX Shelf Current Drains, Table D-6 DMXtend Shelf

Current Drains, and Table D-8 DMXplore Shelf Current Drains. The

cabinet surfaces shall be respectively heated at the appropriate maximum solar radiation levels. Absorbed solar heating shall be estimated using the formulations and methods in accordance with GR-

487 and the ASHRAE handbook

During this testing measure, record, and provide upon request:

• Power level into the cabinet in amperes

• Air Velocities in the airflow channels formed by the Metropolis

DMX, DMXtend, and DMXplore circuit packs in linear ft/min.

• Air temperature entering and exhausted from the Metropolis

DMXtend Access Multiplexer shelf (°C)

Three K or T type thermocouples shall be added at the inlet and exhaust of all circuit pack slots.

Take the average of the three thermocouples for each circuit pack slot for both inlet and exhaust and record (Tinlet_avg,

Texhaust_avg, TC type, and slot number).

• Ambient temperature (temperature outside the cabinet and measured in °C).

• Solar heating loads on respective cabinet surfaces (°C).

365-372-324

Issue 4.2, April 2006

D - 1 7

Appendix D

References

Telcordia Document — Network Equipment - Building System

(NEBS) Requirements: Physical Protection, GR-63, Issue 2, April

2002.

Telcordia Document — Electromagnetic Compatibility and Electrical

Safety - Generic Criteria for Network Telecommunications Equipment,

GR-1089, Issue 3, October 2002.

UL 60950/ CAN/CSA- 22.2 NO. 60950-00 “Safety of Information

Technology Equipment”, December, 2000

Telcordia Document — Generic Requirements for Electronic

Equipment Cabinets, GR-487, Issue 2, March 2000.

Lucent Technologies Document — DMX Access Multiplexer

Engineering Drawing, ED8C871-10, Latest Issue.

Lucent Technologies Document — DMXtend Access Multiplexer

Engineering Drawing, ED8C951-10, Latest Issue.

Lucent Technologies Document — DMXplore Access Multiplexer

Engineering Drawing, ED8C947-10, Latest Issue.

Lucent Technologies Document — DMX Access Multiplexer

Installation Manual, 365-372-300, Latest Issue.

Lucent Technologies Document — DMXtend Access Multiplexer

Installation Manual, 365-372-327, Latest Issue.

Lucent Technologies Document — DMXplore Access Multiplexer

Installation Manual, 365-372-334, Latest Issue.

Lucent Technologies Document — DMX Access Multiplexer

Applications and Planning Guide, 365-372-300, Latest Issue.

Lucent Technologies Document — DMXtend Access Multiplexer

Applications and Planning Guide, 365-372-324, Latest Issue.

Lucent Technologies Document — DMXplore Access Multiplexer

Applications and Planning Guide, 365-372-331, latest Issue.

Telcordia Document — Generic Requirements for a –48 volt

Telecommunications Switchmode Rectifier/ Power Supply, GR-947,

Issue 1, December 1996.

D - 1 8

365-372-324

Issue 4.2, April 2006

References

Appendix D

Lucent Technologies Document — Metropolis

DMXtend Access

Multiplexer Access System Engineering Guidelines, TBS, Latest Issue.

10)

National Fire Protection Agency (NFPA-70), National Electrical Code

(NEC), 2002 Edition.

11)

2001 ASHRAE Handbook Fundamentals — American Society of

Heating, Refrigerating and Air Conditioning Engineers, Inc., Atlanta

GA.

365-372-324

Issue 4.2, April 2006

D - 1 9

References

Appendix D

D - 2 0

365-372-324

Issue 4.2, April 2006

Glossary

Acronyms and Abbreviations

Gigabit

A ABN

Abnormal (status condition)

ACO

Alarm Cutoff

ACO/SW

Alarm Cutoff and Test

ADR

Add/Drop Ring

AGNE

Alarm Gateway Network Element

ADM

Add/Drop Multiplexer

AIS

Alarm Indication Signal

AMI

Alternate Mark Inversion

ANSI

American National Standards Institute

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 1

APS

Automatic Protection Switch

ARM

Access Resource Manager

AS&C

Alarm, Status, and Control

ASCII

American Standard Code for Information Interchange

ASN.1

Abstract Syntax Notation 1

ASNE

Alarm Server Network Element

ATM

Asynchronous Transfer Mode

Auto

Automatic

AUXCTL

Auxiliary Control

B B3ZS

Bipolar 3-Zero Substitution

B8ZS

Bipolar 8-Zero Substitution

BDFB

Battery Distribution and Fuse Bay

BER

Bit Error Ratio

BIP

Bit Interleaved Parity

G L O S S A R Y

G L - 2

365-372-300

Issue 8.0 September 2006

BITS

Building Integrated Timing Supply

BLSR

Bidirectional Line Switched Ring

BPDU

Bridge Protocol Data Unit

BRI

Basic Rate Interface

C CC

Clear Channel

CCITT

Comité ConsultatifInternational Télégrafique & Téléphonique

International Telephone and Telegraph Consultative Committee

CEV

Controlled Environment Vault

CD-ROM

Compact Disk, Read-Only Memory

CDTU

Channel and Drop Test Unit

CIT

Craft Interface Terminal

CLEC

Competitive Local Exchange Carrier

CLEI

Common Language Equipment Identifier

CLF

Carrier Line Failure Status

CLK

Clock

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 3

CMISE

Common Management Information Service Element

CMTS

Cable Modem Termination System

Central Office

Circuit Pack

CPE

Customer Premises Equipment

Critical (alarm status)

CSF

Client Signal Fail

CSU

Channel Service Unit

CTL

Control

CTS

Customer Technical Support; now known as Technical Support Services (TSS)

Coding Violation

CVFE

Coding Violation Far End

D DACS

Data Access Cross-connect System

Decibels

G L O S S A R Y

G L - 4

365-372-300

Issue 8.0 September 2006

Direct Current

DCC

Data Communications Channel

DCE

Data Communications Equipment

DCS

Data Collection System

DEMUX

Demultiplexer

DLC

Digital Loop Carrier

DNS

Data Networking Services

DPLL

Digital Phase-Locked Loop

DRI

Dual Ring Interworking

DS1

Digital Signal Level 1

DS3

Digital Signal Level 3

DSL

Digital Subscriber Line

DSLAM

Digital Subscriber Line Access Multiplexer

DSNE

Directory Services Network Element

DSX

Digital Cross-Connect Panel

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 5

Distant Terminal

DTE

Data Terminating Equipment

DWDM

Dense Wave Division Multiplexing

E EC-1

Electrical Carrier Level 1

ECI

Equipment Catalog Item

EEPROM

Electrically-Erasable Programmable Read-Only Memory

EIA

Electronic Industries Association

EMC

Electromagnetic Compatibility

EMI

Electromagnetic Interference

EOOF

Excessive Out of Frame

EPORT

Ethernet Port

EPROM

Erasable Programmable Read-Only Memory

Equipped (memory administrative state)

EQPT

Equipment

G L O S S A R Y

G L - 6

365-372-300

Issue 8.0 September 2006

Errored Seconds

ESCON

Enterprise Systems Connection

ESD

Electrostatic Discharge

ESF

Extended Super Frame

EST

Environmental Stress Testing

F FC

Fibre-Channel

FC-1G

Fibre-Channel - 1 Gbps

FC-2G

Fibre-Channel - 2 Gbps

FCC

Federal Communications Commission

FDDI

Fiber Distribution Data Interface

Far End

FE ACTY

Far End Activity

FEBE

Far End Block Error

FEC

Forward Error Correction

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 7

FE ID

Far End Identification

FEPROM

Flash EPROM

FERF

Far End Receive Failure

FE SEL

Far End Select

FICON

Fibre Connection

FIT

Failures in 10

-9

hours of operation.

FTAM

File Transfer and Access Management

FTP

File Transfer Protocol

FTTD

File Transfer Translation Device

G GB

Gigabytes

Gb/s or Gbps

Gigabits per Second

GbE

Gigabit Ethernet

GHz

Gigahertz

GNE

Gateway Network Element

GR-XXX

Telcordia Technologies (Bellcore) General Requirement-XXX

G L O S S A R Y

G L - 8

365-372-300

Issue 8.0 September 2006

GTP

General Telemetry Processor

GUI

Graphical User Interface

H HECI

Humans Equipment Catalog Item

HFC

Hybrid Fiber Coaxial

High Speed

Hertz

I IAO LAN

Intra-Office Local Area Network

Internal Clock

Identifier

IEC

International Electrotechnology Commission

IEEE

Institute of Electrical and Electronics Engineers

IMF

Infant Mortality Factor

INC

Incoming Status

I/O

Input/Output

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 9

Internet Protocol

Intermediate Reach

In Service

ISCI

Intershelf control Interface

ISI

Intershelf Interface

ISDN

Integrated Services Digital Network

ISO

International Standards Organization

ISP

Internet Service Provider

K Kb/s

Kilobits per second

L LAN

Local Area Network

LAPD

Link Access Procedure "D"

LBC

Laser Bias Current

LBO

Line Build Out

LCN

Local Communications Network

G L O S S A R Y

G L - 1 0

365-372-300

Issue 8.0 September 2006

LEC

Local Exchange Carrier

LED

Light-Emitting Diode

LFD

Loss of Frame Delineation

LGX

Lightguide Cross-Connect

LOA

Loss of Alignment

LOF

Loss of Frame

LOP

Loss of Pointer

LOS

Loss of Signal

Long Reach

Low Speed

M MB

Megabytes

Mb/s

Megabits per second

Major Alarm

Multimode

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 1 1

MML

huMan-Machine Language

Minor Alarm

MPEG

Moving Picture Experts Group

MSDT

Multi-Services Distant Terminal

MSO

Metropolitan Serving Office

MTBF

Mean Time Between Failures

MTBMA

Mean Time Between Maintenance Activities

Mult

Multipling

MUX

Multiplex

N NA

Not Applicable

NAP

Network Access Point

Near End

Network Element

NE ACTY

Near-End Activity

G L O S S A R Y

G L - 1 2

365-372-300

Issue 8.0 September 2006

NEBS

Network Equipment-Building System

Nanometer (10

-9

meters)

NMA

Network Monitoring and Analysis

NMON

Not Monitored (provisioning state)

Not Reported

NRZ

Nonreturn to Zero

NNI

Network-Network Interface

NSA

Not Service Affecting

NSAP

Network Services Access Point

NTF

No Trouble Found

NTP

Network Time Protocol

NUT

Nonpreemptible unprotected traffic

NTF

Non-Volatile Memory

O OAM&P

Operations, Administration, Maintenance, and Provisioning

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 1 3

OC-1

Optical Carrier Level 1 Signal (51.84 Mb/s)

OC-192

Optical Carrier Level 192 Signal (9953 Mb/s)

OC-3

Optical Carrier Level 3 Signal (155 Mb/s)

OC-12

Optical Carrier Level 12 Signal (622 Mb/s)

OC-48

Optical Carrier Level 48 Signal

Operations Interworking

OLIU

Optical Line Interface Unit

OOF

Out of Frame

OOL

Out of Lock

OOS

Out-of-Service

OPS/INE

Operations System/Intelligent Network Element

Operations System

OSGNE

Operations System Gateway Network Element

OSI

Open Systems Interconnection

OSMINE

Operations Systems Modifications for the Integration of Network Elements

G L O S S A R Y

G L - 1 4

365-372-300

Issue 8.0 September 2006

OSP

Outside Plant

P P-bit

Performance Bit

Personal Computer

PCU

Power Conversion Unit

PID

Program Identification

PIR

Peak Information Rate

PINFET

Positive Intrinsic Negative Field Effect Transistor

PJC

Pointer Justification Count

PLL

Phase-Locked Loop

Performance Monitoring

PMN

Power Minor Alarm

POH

Path Overhead

POP

Points of Presence

POTS

Plain Old Telephone Service

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 1 5

PRM

Performance Report Message

PROTN

Protection

PRS

Primary Reference Source

PSU

Power Supply Unit

PTM

Pluggable Transmission Module, also known as SFP

PVC

Permanent Virtual Circuit

PWR

Power

Q QoS

Quality of Service

R RAM

Random Access Memory

RDC

Regional Data Center

RDI

Remote Defect Indication

RFI

Remote Failure Indication

RPP

Reliability Prediction Procedure (described in Telcordia Technologies TR-NWT-

00032)

Remote Terminal

G L O S S A R Y

G L - 1 6

365-372-300

Issue 8.0 September 2006

RTRV

Retrieve

Rack Unit

Return to Zero

S SA

Service Affecting

SAN

Storage Area Networking

Signal Degrade

SDH

Synchronous Digital Hierarchy

SEFS

Severely Errored Frame Seconds

SEO

Single-Ended Operations

SES

Severely Errored Seconds

Super Frame (format for DS1 signal)

SID

System Identification

SLA

Service Level Agreements

Single Mode

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 1 7

SMC

SONET Minimum Clock

SNMP

Simple Network Management Protocol

SONET

Synchronous Optical NETwork

SPE

Synchronous Payload Envelope

SQU

Sync Quality Unknown

SRD

Software Release Description

STS, STS-n

Synchronous Transport Signal

STM

Synchronous Transfer Mode

STS-1 SPE

STS-1 Synchronous Payload Envelope

STS-3c

Synchronous Transport Level 3 Concatenated Signal

STS-12c

Synchronous Transport Level 12 Concatenated Signal

STS-48c

Synchronous Transport Level 48 Concatenated Signal

STU

Synchronized - Traceability Unknown

SYSCTL

System Controller (circuit pack)

G L O S S A R Y

G L - 1 8

365-372-300

Issue 8.0 September 2006

T T1

A carrier system that transmits at the rate of 1.544 Mb/s (a DS1 signal)

T1X1 and T1M1

The ANSI committees responsible for telecommunications standards

A carrier system that transmits at the rate of 44.736 Mb/s (a DS1 signal)

Telcordia Technologies Technical Advisory

TABS

Telemetry Asynchronous Byte Serial (Protocol)

TARP

Target ID Address Resolution Protocol

TBD

To be Determined

TCA

Threshold-Crossing Alert

TCP/IP

Transmission Control Protocol/Internet Protocol

TCVCXO

Termperature-Compensated Voltage-Controlled Crystal Oscillator

TDC

TARP Date Cache

TDM

Time Division Multiplexing

THz

Terahertz (10

Hz)

TID

Target Identifier

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 1 9

TIRKS

Trunk Integrated Record Keeping System

TG3

Stratum 3 Timing Generator

TL1

Transaction Language 1

Telcordia Technologies Technical Requirement

TSA

Time Slot Assignment

TSI

Time Slot Interchange

TSO

Technical Support Organization

U UAS

Unavailable Seconds

UNI

User Network Interface

UOC

Universal Optical Connector

UPD/INIT

Update/Intialize

UPSR

Unidirectional Path Switched Rings

V VAC

Volts Alternating Current

VCG

Virtual Concatenation Group

G L O S S A R Y

G L - 2 0

365-372-300

Issue 8.0 September 2006

VCG FE

Virtual Concatenation Group - Fast Ethernet

VDC

Volts Direct Current

VLAN

Virtual Local Area Network

Violation Monitor

VMR

Violation Monitor and Removal

VoIP

Voice over Internet Protocol

VONU

Virtual Optical Network Unit

VPN

Virtual Private Network

vslot

Virtual Slot

Virtual Tributary

VT1.5

Virtual Tributary 1.5 (1.728 Mb/s)

VT-G

Virtual Tributary Group

W WAN

Wide Area Network

WDM

Wave Division Multiplexing

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 2 1

WTR

Wait To Restore

G L O S S A R Y

G L - 2 2

365-372-300

Issue 8.0 September 2006

Glossary

Terms and Definitions

0x1Sn

DMX provides an unprotected 0x1Sn mode. This option is userprovisionable on a per-port basis. 0x1S1 and 0x1S2 are provisionable applications for LS OC-n port pairs. For 0x1S1, the port in slot 1 is unprotected and the companion port in slot 2 is unused. For 0x1S2, the port in slot 2 is unprotected and the companion port in slot 1 is unused.

1+1 (bidirectional)

The bidirectional 1+1 protection switching architecture protects against failures of the optical transmit/receive equipment and their connecting fiber facility. One bidirectional interface (two fibers plus associated OLIUs on each end) is designated

″ service,

″ and the other is designated

″ protection.

″

In each direction, identical signals are transmitted on the service and protection lines (

″ dual-fed

″

). The receiving equipment monitors the incoming service and protection lines independently, and selects traffic from one line (the

″ active

″ line) based on performance criteria and technician/OS control. In bidirectional 1+1 only one line is active at a time.

1+1 (unidirectional)

The unidirectional 1+1 protection switching architecture protects against failures of the optical transmit/receive equipment and their connecting fiber facility. One bidirectional interface (two fibers plus associated OLIUs on each end) is designated

″ service,

″ and the other is designated

″ protection.

″

In each direction, identical signals are transmitted on the service and protection lines (

″ dual-fed

″

). The receiving equipment monitors the incoming service and protection lines independently, and selects traffic from one line (the

″ active

″ line) based on performance criteria and technician/OS control. In unidirectional 1+1 both service and protection lines could be active at the same time (service in one direction, protection in the other).

1xN, 1x1

1xN protection switching pertains to circuit pack protection that provides a redundant signal path through the DMX (it does not cover protection switching of an optical facility; see "1+1"). In 1xN switching, a group of N service circuit packs share a single spare protection circuit pack. 1x1 is a special case of 1xN, with N=1.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 2 3

In 1x1 only one is active at a time.

802.1Q mode

In 802.1Q Mode, a circuit pack can be provisioned to use an incoming frame’s VLAN tag, to add a VLAN tag associated with the port for untagged frames, or to drop an incoming frame if its

VLAN tagging does not meet provisioned specifications. The priority bits in an incoming frame’s

VLAN tag can also be used to affect the handling of the frame.

A Active

Active identifies a 1+1 protected entity which is currently selected by the receiver at either end as the payload carrying signal or a 1x1 or 1xN protected circuit pack that is currently carrying service. (See Standby).

Adaptive Rate

(see Pipe Mode).

Add/Drop Multiplexer

The term for a sychronous network element capable of combining signals of different rates and having those signals added to or dropped from the stream.

AGNE - Alarm Gateway Network Element

A defined NE in an alarm group through which members of the alarm group exchange information.

Aging (Ethernet MAC Address)

The filtering database entries are automatically removed after an aging period (300 seconds).

AIS - Alarm Indication Signal

A code transmitted downstream in a digital network that shows that an upstream failure has been detected and alarmed.

Alarm

Visible or Audible signal indicating that an equipment failure or significant event/ condition has occured.

Alarm Cut-Off (ACO)

A button on the SYSCTL used to silence audible alarms. Alarms can also be silenced using the

Fault

→

Alarm Cutoff

command.

AMI - Alternate Mark Inversion

A line code that employs a ternary signal to convey binary digits, in which successive binary ones are represented by signal elements that are normally of

G L O S S A R Y

G L - 2 4

365-372-300

Issue 8.0 September 2006

alternating, positive and negative polarity but equal in amplitude, and in which binary zeros are represented by signal elements that have zero amplitude.

APS Channel

The signaling channel carried in the K1 and K2 bytes of the SONET overhead on the protection line. It is used to exchange requests and acknowledgments for protection switch actions.

ASCII - American Standard Code for Information Interchange

A standard 8-bit code used for exchanging information among data processing systems and associated equipment.

Auto

One possible state of a DS1 or DS3 port. In this state, the port will automatically be put "in service" if a good signal is detected coming from the DSX panel.

Automatic Protection Switch

A feature that allows any entity to be automatically selected and the provisioning to be automatically reconfigured in the event of a failure or network change, for example, a fiber cut.

Autonomous Message

A message transmitted from the controlled Network Element to the ITM-SC which was not a response to an ITM-SC originated command.

Available Time

In performance monitoring, the 1-second intervals.

B B3ZS - Bipolar 3-Zero Substitution

A line coding method that replaces a string of three zeros with a sequence of symbols having some special characteristic.

B8ZS - Bipolar 8-Zero Substitution

A line coding method that replaces a string of eight zeros with a sequence of symbols having some special characteristic.

Backbone Ring

A host ring.

Backup

The backup and restoration features provide the capability to recover from loss of NE data because of such factors as human error or power failures.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 2 5

Bandwidth

The difference in Hz between the highest and lowest frequencies in a transmission channel. The data rate that can be carried by a given communications circuit.

Baud Rate

Transmission rate of data (bits per second) on a network link.

BER - Bit Error Rate

The ratio of bits received in error to the total bits sent.

Bidirectional Line

A transmission path consisting of two fibers that handle traffic in both the transmit and receive directions.

Bidirectional Line Switched Ring (BLSR)

A bidirectional ring in which protection switching is accomplished by switching working traffic into protection time slots in the line going in the opposite direction around the ring.

Bidirectional Ring

A ring in which both directions of traffic between any two nodes travel through the same network elements (although in opposite directions).

Bidirectional Switch

Protection switching performed in both the transmit and receive directions.

BIP - Bit Interleaved Parity

A method of error monitoring over a specified number of bits, that is BIP-3 or BIP-

BIT

The smallest unit of information in a computer, with a value of either 0 or 1.

BIT Error Rate (BER)

The ratio of error bits received to the total number of bits transmitted.

BIT Error Rate Threshold

The point at which an alarm is issued for bit errors.

BIT Interleaved Parity-N (BIP-N)

A method of error monitoring over a specified number of bits (BIP-3 or BIP-8).

BITS Clock

A BITS (Building Integrated Timing Source) clock is simply a clock within a central office that distributes timing to all the equipment in that central office. The BITS clock is tied to an

G L O S S A R Y

G L - 2 6

365-372-300

Issue 8.0 September 2006

external, stable timing source, such as a GPS (global positioning satellite).

BITS - Building Integrated Timing Supply

A single clock that provides all the DS1 and DS0 synchronization references required by clocks in a building.

Blocking

The state in which an Ethernet port does not participate in frame relay. The forwarding process discards received frames.

Bridge cross-connection

Two cross-connections which share a common input.

Broadband

Any communications channel with greater bandwidth than a voice channel; sometimes used synonomously with wideband.

Burst Size

The provisioned burst size determines the length or size of the data burst that is allowed by the peak information rate policer. This affects policing for all VLANs (in 802.1Q mode), all port tags (in transparent mode). and all Private line services (in Private Line or No Tag mode) on the

LNW63, LNW66, LNW67, LNW68, LNW70, LNW71, LNW74, and LNW78 Ethernet circuit packs.

Byte

Refers to a group of eight consecutive binary digits.

C C-BIT

A framing format used for DS3 signals produced by multiplexing 28 DS1s into a DS3. This format provides for enhanced performance monitoring of both near-end and far-end entities.

CC - Clear Channel

A provisionable mode for the T3 interface used for the transport of unframed DS3 signals. Only near-end line PM is available, but not path PM.

CCITT - International Telephone and Telegraph Consultative Committee

An international advisory committee under United Nations’ sponsorship that has composed and recommended for adoption worldwide standards for international communications. Recently changed to the International Telecommunications

Union Telecommunications Standards Sector (ITU-TSS).

Channel

A logical signal within a port. For example, for an EC-1 port, there is one STS-1

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 2 7

channel and sometimes 28 VT1.5 channels. See Port.

Channel State Provisioning

A feature that allows a user to suppress reporting of alarms and events during provisioning by supporting multiple states (automatic, in-service and not monitored) for VT1.5 and STS-1 channels. See Port State Provisioning.

Circuit

A set of transmission channels through one or more network elements that provides transmission of signals between two points, to support a single communications path.

CLEC - Competitive Local Exchange Carrier

Company that provides local phone services in competition with RBOCs.

Client Signal Fail

The local NE sends a Client Signal Fail (CSF) signal to the far-end equipment when a defect is detected in the ingress client signal.

Collocated

System elements that are located in the same location.

Concatenation

A procedure whereby multiple virtual containers are associated one with each other resulting in a combined capacity that can be used as a single container across which bit sequence integrity is maintained.

Constituent Signals

List of received signals for an adaptive rate (pipe mode) optical port.

Cost

Cost is used to help determine the efficiency of any given path. Cost is provisioned for a port

(depending on speed of transmission) and calculated automatically for a path (sum of the port costs for the path).

Craft Interface Terminal (CIT)

The user interface terminal used by craft personnel to communicate with a network element.

Credit Interval

The provisioned interval for adding tokens to the token bucket used by the peak information rate policer. This affects policing for all VLANs (in 802.1Q mode), all port tags (in transparent mode). and all Private line services (in Private Line or No Tag mode) on the

LNW63, LNW66, LNW67,

LNW68, LNW70, LNW71, LNW74, and LNW78

Ethernet circuit packs.

G L O S S A R Y

G L - 2 8

365-372-300

Issue 8.0 September 2006

Critical (CR)

Alarm that indicates a severe, service-affecting condition.

Cross-connect Capacity

The total bandwidth of cross-connections as measured by the bandwidth of input and output tributaries. A system with N STS-1 equivalent input tributaries and N STS-1 equivalent output tributaries (referred to as

″

NxN

″

) provides a cross-connection capacity of N STS-1 equivalents.

This system could provide N one-way point-to-point cross-connections or N/2 two-way point-to-point cross-connections at the equivalent rate of STS-1.

Cross-connect Rate

The attribute of a cross-connection that defines the constituent signal rate(s) it can carry. For a cross-connection with an STS-3

″ pipe

″ cross-connection rate, the constituent signals carried by the cross-connection can be either an STS-3c signal or three STS-3 signals. Similarly, for a cross-connection with an STS-12

″ pipe

″ cross-connection rate, the constituent signals carried by the cross-connection can be either an STS-12c signal or an allowed mix of STS-1 signals and

STS-3c signals.

Cut-Through

Refers to a simple ASCII interface to an NE. It enables the user to send TL1 messages directly to the NE with no interpretation or assistance provided by the WaveStar CIT.

CV - Coding Violation

A performance monitoring parameter.

CVFE - Coding Violation Far-End

An indication returned to the transmitting terminal that an errored block has been detected at the receiving terminal.

D DACS III-2000

Digital Access and Cross-Connect System that provides clear channel switching at either the DS3 or the STS-1 rates, eliminating the need for manual DSXs.

DACS IV-2000

Digital Access and Cross-Connect System that provides electronic DS3/STS-1 or

DS1/VT1.5 cross-connect capability, eliminating the need for manual DSXs.

DCC - Data Communications Channel

The embedded overhead communications channel in the SONET line. It is used for end-to-end communications and maintenance. It carries alarm, control, and status information between network elements in a SONET network.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 2 9

DCE - Data Communications Equipment

In a data station, the equipment that provides the signal conversion and coding between the data terminal equipment (DTE) and the line. The DCE may be separate equipment or an integral part of the DTE or of intermediate equipment. A DCE may perform other functions usually performed at the network end of the line.

DTE - Data Terminating Equipment

The equipment that originates data for transmission and accepts transmitted data.

DDM-2000

Lucent’s next generation network multiplexers that multiplex DS1, DS3, or EC-1 inputs into EC-1, OC-1, OC-3, or OC-12 outputs.

Default Provisioning

The parameter values that are preprogrammed as shipped from the factory.

Demultiplexing

A process applied to a multiplexed signal for recovering signals combined within it and for restoring the distinct individual channels of these signals.

DEMUX - Demultiplexer

The DEMUX direction is from the fiber toward the DSX.

Dense Wave Division Multiplexing (DWDM)

Transmitting two or more signals of different wavelengths simultaneously over a single fiber.

Digital Cross-connect Panel

A panel designed to interconnect to equipment that operates at a designated rate. For example, a

DSX-3 interconnects equipment operating at the DS3 rate.

Digital Multiplexer

Equipment that combines time-division multiplexing several digital signals into a single composite digital signal.

Digital Signal Levels 0, 1, 3, (DS0, DS-1, DS-3)

An ANSI-defined signal or service level corresponding to the following: DS0 is 64 Kb/s, DS1 is

1.544 Mb/s (equivalent to T1), and DS3 is 44.736 Mb/s (equivalent to 28 T1 channels or T3).

Directory Services Network Element

A designated network element that is responsible for administering a database that maps network element names (TIDs) to addresses (NSAPs - network service access points) in an OSI subnetwork. There can be one DSNE per ring. Can also be a GNE.

G L O S S A R Y

G L - 3 0

365-372-300

Issue 8.0 September 2006

Disable admin

An Ethernet port that does not participate in the spanning tree. The port is disabled by management.

Disable failure

A port in this state does not participate in the spanning tree. The port is disabled due to a hardware or software failure.

DRI - Dual Ring Interworking

Two ring networks interconnected at two common nodes.

Drop and Continue

A technique that allows redundant signal appearances at two central offices in a

DRI network, allowing protection against central office failures.

DS1

Digital Signal Level 1 (1.544 Mb/s)

DS1(28) Circuit Pack

The DS1(28) circuit pack interfaces to the DSX-1 panel.

DS3

Digital Signal Level 3 (44.736 Mb/s).

DS3/EC-1 Circuit Pack

The DS3/EC-1 circuit pack interfaces to the DSX-3 panel.

DSn - Digital Signal Rate n

One of the possible digital signal rates at DMX 2.5G Multiplexer interfaces: DS1

(1.544 Mb/s) or DS3 (44.736 Mb/s).

DSNE - Directory Services Network Element

DSX - Digital Cross-Connect Panel

A panel designed to interconnect to equipment that operates at a designated rate.

For example, a DSX-3 interconnects equipment operating at the DS3 rate.

DTE - Data Terminating Equipment

That part of a data station that serves as a data source (originates data for transmission), a data sink (accepts transmitted data), or both.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 3 1

Dual Homing

A network topology in which two OC-3 or OC-12 shelves serve as DMX 2.5G

Multiplexer hosts supporting up to 16 OC-3 rings or 4 OC-12 rings. Each DMX

2.5G Multiplexer ring is interconnected between the two separate hosts.

E E1

E1 is an SDH/PDH (Synchronous Digital Hierarchy/Pleiseosynchronous Digital Hierarchy, the

European equivalent of SONET/DSx) electrical signal comparable to (but slightly faster than) a

DS1. E1 is also sometimes called CEPT-1 (Conference of European Posts and Telecommunications) and is at 2.048 Mbps.

EC-1, EC-n - Electrical Carrier

The basic logical building block signal with a rate of 51.840 Mb/s for an EC-1 signal and a rate of n times 51.840 Mb/s for an EC-n signal. An EC-1 signal can be built in two ways: A DS1 can be mapped into a VT1.5 signal and 28 VT1.5 signals multiplexed into an EC-1 (VT1.5 based EC-1), or a DS3 can be mapped directly into an EC-1 (DS3 based EC-1).

ECI - Equipment Catalog Item

The bar code number on the faceplate of each circuit pack used by some inventory systems.

Electromagnetic Compatibility (EMC)

A measure of equipment tolerance to external electromagnetic fields.

Electromagnetic Interface (EMI)

High-energy, electrically induced magnetic fields that cause data corruption in cables passing through the fields.

Electronic Industries Association (EIA)

A trade association of the electronic industry that establishes electrical and functional standards.

Electrostatic Discharge (ESD)

Static electrical energy potentially harmful to circuit packs and humans.

ES - Errored Seconds

A performance monitoring parameter.

Enterprise Systems Connection (ESCON)

A 200-Mbps data signal used in storage area networking applications.

Event

A significant change. Events in controlled Network Elements include signal failures, equipment

G L O S S A R Y

G L - 3 2

365-372-300

Issue 8.0 September 2006

failures, signals exceeding thresholds, and protection switch activity. When an event occurs in a controlled Network Element, the controlled Network Element will generate an alarm or status message and send it to the management system.

The format for a DS1 signal.

Extended Super Frame (ESF)

A T1 format that uses the framing bit for non-intrusive signaling and control. A T1 frame is sent 8,000 times a second, with each frame consisting of a payload of 192 bits, and with each frame preceded by a framing bit. Because ESF only requires 2,000 framing bits for synchronization, the remaining 6,000 framing bits can be used for error detection.

Externally Timed

An operating condition of a clock in which it is locked to an external reference and is using time constants that are altered to quickly bring the local oscillator’s frequency into approximate agreement with the synchronization reference frequency.

Extra Traffic

Unprotected traffic that is carried over BLSR protection channels when their capacity is not used for the protection of working traffic. However, the extra traffic is unprotected and is preempted (lost) if a BLSR protection switch is activated. Preempted traffic is reestablished when the BLSR protection switch clears.

F Facility

A one- or two-way circuit that carries a transmission signal.

Facility Loopback

A facility loopback is where an entire line is looped back.

Facility Roll

The process of moving the input of an existing cross-connection to a new input using a single command to the NE.

Failure in Time (FIT)

Circuit pack failure rates per 10

9 hours as calculated using the method described in Reliability

Prediction Procedure for Electronic Equipment, Telcordia Method I, Issue 5,

September 1995.

Fault

Term used when a circuit pack has a hard (not temporary) fault and cannot perform its normal function.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 3 3

Fault Management

Collecting, processing, and forwarding of autonomous messages from network elements.

FE - Far End

Any other network element in a maintenance subnetwork other than the one the user is at or working on. Also called remote.

FE ACTY - Far End Activity

An LED on the SYSCTL circuit pack faceplate.

FEBE - Far End Block Error

An indication returned to the near-end transmitting node that an errored block has been detected at the far end.

FE ID - Far End Identification

The 7-segment display on the faceplate of the SYSCTL (LNW1) circuit pack. The

LNW2, used for R6.0 and beyond, has an alphanumeric LED display that is labeled

IND.

FEPROM - Flash EPROM

A new technology that combines the nonvolatility of EPROM with the in-circuit reprogrammability of EEPROM (electrically-erasable PROM).

FERF - Far End Receive Failure

An indication returned to the transmitting terminal that the receiving terminal has detected an incoming section failure.

FE SEL - Far End Select

An LED on the faceplate of the SYSCTL circuit pack.

Fibre-Channel - 1G (FC-1G)

A Fibre-Channel 1.0625 Gbps data signal.

Fibre-Channel - 2G (FC-2G)

A Fibre-Channel 2.1250 Gbps data signal.

Fibre Connection (FICON)

A 1.0625 Gbps data signal.

File Transfer and Access Management (FTAM)

FTAM is the Open System Interconnection (OSI) standard for file transfer, file access, and file management.

G L O S S A R Y

G L - 3 4

365-372-300

Issue 8.0 September 2006

Filtering Databese

The filtering database maintains a dynamic list of paths to which packets should be routed based on the destination adress. The database ewnteries are created, updated and removed by the learning process.

FIT

Failures in 10

9 hours of operation.

Flash EPROM

A technology that combined the non volatility of EPROM with the in-circuit reprogrammability of EEPROM (electrically-eraseable PROM).

Forced

Term used when a circuit pack (either working or protection) has been locked into a service-providing state by user command.

Forced Switch to Protection

The WaveStar CIT command that forces the protection group to be the

″

Active Unit.

″

The clear command is required to remove the Forced Switch state. While in the Forced Switch state the system may not switch the active unit either automatically, by means of the WaveStar CIT

Forced Switch, or Manual Switch command.

Forwarding

The state in which an Ethernet port participates in frame relay.

Free Running

An operating condition of a clock in which its local oscillator is not locked to an internal synchronization reference and is using no storage techniques to sustain its accuracy.

FT-2000

Lucent’s SONET OC-48 Lightwave System.

FTAM-FTP Gateway

In Release 3.0 and later releases, the Metropolis

DMX supports an FTAM-FTP gateway function. This is also referred to as file transfer translation device (FTTD). The FTTD translates

FTAM over OSI presentation to FTP over TCP/IP.

Function Unit

Refers to any one of a number of different circuit packs that can reside in the A, B,

C, or D function unit slots on the DMX 2.5G Multiplexer.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 3 5

G GNE - Gateway Network Element

A network element that passes information between other network elements and management systems through a data communication network.

H Hairpin Routing

A cross-connection between function units (inter-function unit). For example, function unit C to function untis A, B, or D. Also, a cross-connection within the same function unit (intra-function unit). Cross-connections go through Main, but no bandwidth or time slots are taken from the backbone ring. Eliminates need for another shelf.

Hashed FTP

In Release 3.0 and later releases, the hashed FTP (digital signature) capability prevents tampering withn a downloadable software image.

Holdover

An operating condition of a network element in which its local oscillator is not locked to any synchronization reference but is using storage techniques to maintain its accuracy with respect to the last known frequency comparison with a synchronization reference.

HFC - Hybrid Fiber Coaxial

Technology using coaxial and fiber cable to transport data services in addition to television channels.

I IC - Internal Clock

Used in synchronization messaging.

See shelf ID and site ID.

Insert

To physically insert a circuit pack into a slot, thus causing a system-initiated restoral of an entity into service and/or creation of an entity and associated attributes.

IR - Intermediate Reach

A term used to describe distances of 15 to 40 km between optical transmitter and receiver without regeneration. See long reach.

IS - In Service

One possible state of a DS1, DS3, or EC-1 port. Other possible states are "auto"

G L O S S A R Y

G L - 3 6

365-372-300

Issue 8.0 September 2006

(automatic) and "nmon" (not monitored).

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 3 7

J Jitter

Timing jitter is defined as short-term variations of the significant instants of a digital signal from their ideal positions in time.

Jumbo Frame

In Release 3.0 and later releases, Metropolis

DMX supports jumbo Ethernet frames. Jumbo frames increased network efficiency by reducing the number of frames to be processed.

L LBO - Lightguide Build Out

An attenuating (signal-reducing) element used to keep an optical output signal strength within desired limits.

LED - Light Emitting Diode

Used on a circuit pack faceplate to show failure (red) or service state. It is also used to show the alarm and status condition of the system.

LGX - Lightguide Cross-Connect

A SONET device that contains ports for optical fiber connections to an optical network element

(NE). An LGX is used to make and change connections to an NE without changing the cabling on the NE itself.

Line

A transmission medium, together with the associated equipment, required to provide the means of transporting information between two consecutive network elements. One network element originates the line signal; the other terminates it.

Line Timing

The capability to directly derive clock timing from an incoming OC-N signal while providing theuser the capability to provision whether switching to an alternate OC-

N from a different source (as opposed to entering holdover) will occur if the OC-

N currently used as the timing reference for that NE becomes unsuitable as a reference. For example, intermediate nodes in a linear network are line timed. See

Loop Timing.

Listening

The state in which an Ethernet port is preparing to participate in frame relay. In the listening state, frame relay is disabled. This is an interim state between blocking and learning.

Local

See Near-End.

G L O S S A R Y

G L - 3 8

365-372-300

Issue 8.0 September 2006

Local Area Network (LAN)

A communications network that covers a limited geographic area, is privately owned and user administered, is mostly used for internal transfer of information within a business, is normally contained within a single building or adjacent group of buildings, and transmits data at a very rapid speed.

Locked Cross-Connection

This is a variation of the ring cross-connection that allows the user to lock the path selector to a specified rotation of the ring. Any signal received from the other rotation of the ring is ignored.

LOF - Loss of Frame

A failure to synchronize to an incoming signal.

Long Reach (LR)

A term used to describe distances of 40 km or more between optical transmitter and receiver without regeneration. See Intermediate Reach.

A failure to synchronize to an incoming signal.

Loopback

Type of diagnostic test used to compare an original transmitted signal with the resulting received signal. A loopback is established when the received optical or electrical external transmission signal is sent from a port or tributary input directly back toward the output.

Loop Timing

Loop timing is a special case of line timing. It applies to NEs that have only one

OC-N interface. For example, terminating nodes in a linear network are loop timed.

See Line Timing.

LOP - Loss of Pointer

A failure to extract good data from an STS-1 payload.

LOS - Loss of Signal

The complete absence of an incoming signal.

LR - Long Reach

A term used to describe distances of 40 km or more between optical transmitter and reciever without regeneration. See Intermediate Reach.

M M23-Format

A standard framing format used for DS3 signals produced by multiplexing 28 DS1s into a DS3 (sometimes referred to as M13-format, without C-bit parity).

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 3 9

Main

The two slots (M-1 and M-2) on the DMX Multiplexer shelf in which the OC-12/

48/192 OLIU circuit packs are installed.

Major

Indicates a service-affecting failure, main or unit controller failure, or power supply failure.

Midspan Meet

The capability to interface between two lightwave terminals of different vendors.

This applies to high-speed optical interfaces.

Minor

Indicates a non-service-affecting failure of equipment or facility.

Miscellaneous Discrete Interface

Allows an operations system to control and monitor equipment collocated within a set of input and output contact closures.

Multiplexer

A device (circuit pack) that combines two or more transmission signals into a combined signal on a shared medium.

Multiplexing

The process of combining multiple signals into a larger signal at the transmitter by a multiplexer. The large signal is then split into the original smaller signals at the receiver by a demultiplexer.

Multipoint Cross-Connections

Multipoint cross-connections provide unprotected SONET connections to Ethernet circuit packs.

They form two individual connections.

N NE - Near End

The network element the user is at or working on. Also called local.

NE - Network Element

The basic building block of a telecommunications equipment within a telecommunication network that meets SONET standards. Typical internal attributes of a network element include: onr or more high- and low-speed transmission ports, built-in intelligence, synchronization and timing capability, and access interfaces for use by technicians and/or operation systems. In addition, a network element may also include a time slot interchanger.

G L O S S A R Y

G L - 4 0

365-372-300

Issue 8.0 September 2006

Network Service Access Point (NSAP) Adress

Network Service Access Point Address (used in the OSI network layer 3). An automatically assigned number that uniquely identifies a Network Element for the purposes of routing DCC messages.

Network Time Protocol

Network time protocol is an easy, accurate, and automatic method to get and synchronize date/time.

NMA - Network Monitoring and Analysis

An operations system designed by Telcordia Technologies which is used to monitor network facilities.

NMON - Not Monitored

A provisioning state for equipment that is not monitored or alarmed.

No Request State

This is the routine-operation quiet state in which no external command activities are occurring.

Node

A network element in a ring or, more generally, in any type of network. In a network element supporting interfaces to more than one ring, node refers to an interface that is in a particular ring. Node is also defined as all equipment that is controlled by one system controller. A node is not always directly manageable by a management system.

Non-Preemtible Unprotected Traffic (NUT)

Traffic carried on (working and/or protection) BLSR channels for which protection switching has been provisioned as disabled. As the name implies, NUT is unprotected and not preempted in the event of a BLSR protection switch. NUT carried on non-preemptible unprotected channels affords a higher level of survivability as compared to extra traffic, which is preempted during a protection switch, but a lower level of survivability as compared to working traffic, which is carried on its corresponding protection channel during a protection switch.

Non-Revertive Switching

In non-revertive switching, an active and standby line exist on the network. When a protection switch occurs, the standby line is selected to support traffic, thereby becoming the active line.

The original active line then becomes the standby line. This status remains in effect even when the fault clears. That is, there is no automatic switch back to the original status.

Non-Volatile Memory

Memory that retains its stored data after power has been removed. An example of NVM would be a hard disk. The LNW2 contains 2 NVM compact flash cards.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 4 1

Not Monitored (NMON)

Memory that retains its stored data after power has been removed.

Not Reported

NSAP - Network Services Access Point

An address that identifies a network element. Used for maintenance subnetwork communication using the OSI protocol.

O OC, OC-n - Optical Carrier

The optical signal that results from an optical inversion of an STS signal; that is,

OC-1 from STS-1 and OC-n from STS-n.

OC-1

Optical Carrier Level 1 Signal (51.844 Mb/s).

OC-3

Optical Carrier Level 3 Signal (155 Mb/s).

OC-3c (STS-3c)

Optical Carrier Level 3 Concatenated Signal. Low-speed broadband equivalent to three STS-1s linked together with a single path overhead.

OC-12

Optical Carrier Level 12 Signal (622 Mb/s).

OC-12c (STS-12c)

Optical Carrier Level 12 Concatenated Signal. High-speed broadband equivalent to twelve STS-1s linked together with a single path overhead.

OC-48

Optical Carrier Level 48 Signal.

Operations Interface

Any interface that provides information on the system performance or control.

These include the equipment LEDs, SYSCTL faceplate, and office alarms.

Operations Interworking

The capability to access, operate, provision, and administer remote systems through craft interface access from any site in a SONET/SDH network or from a centralized operations system.

G L O S S A R Y

G L - 4 2

365-372-300

Issue 8.0 September 2006

OS - Operations System

A central computer-based system used to provide operations, administration, and maintenance functions.

OSI - Open Systems Interconnection

Referring to the OSI reference model, a logical structure for network operations standardized by the Internation Standards Organization (ISO).

OSGNE - Operations System Gateway Network Element

An OSGNE serves as a single interface to the OS for NEs in the same subnetwork using X.25 interfaces.

P Pass Through

Paths that are cross-connected directly across an intermediate node in a ring network.

Path

A logical connection between the point at which a standard frame format for the signal at the given rate is assembled, and the point at which the standard frame format for the signal is disassembled.

Path Protection Group

The part of a cross-connection topology that is provisioned to provide path-level protection switching for all the constituent signals carried by the cross-connection. A path protection group can be identified as an entity by its logical output tributary and its cross-connection rate. A path protection group consists of one or more constituent path selectors.

PCMCIA

Personal Computer Memory Card International Association

Peak Information Rate Policer

The peak information rate policer meters packet traffic leaving the internal packet switch and going toward the SONET network. If the packets exceed the provisioned peak information rate, the packets are dropped. This affects the LNW66, LNW67, and LNW68 Ethernet circuit packs in Release 3.0 and later releases.

Performance Monitoring

Measures the quality of service and identifies degrading or marginally operating systems (before an alarm would be generated).

Pipe Mode

Metropolis

DMX supports cross-connections on adaptive rate OC-n ports (pipe mode). The

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 4 3

signal rates adapt to the supported set of signal rates. Cross-connections may be provisioned at any cross-connection rate that is supported for the tributaries associated with the OC-n ports. A cross-connections can carry any set of constituent signals; however, the total of the constituent signal rates must not exceed the cross-connection rate.

Plesiochronous Network

A network that contains multiple maintenance subnetworks, each internally synchronous and all operating at the same nominal frequency, but whose timing may be slightly different at any particular instant. For example, in SONET networks, each timing traceable to their own Stratum 1 clock are considered plesiochronous with respect to each other.

PM - Performance Monitoring

Measures the quality of service and identifies degrading or marginally operating systems (before an alarm would be generated).

Port (also called Line)

The physical interface, consisting of both an input and output, where an electrical or optical transmission interface is connected to the system and may be used to carry traffic between network elements. The words

″ port

″ and

″ line

″ may often be used synonymously.

″

Port

″ emphasizes the physical interface, and

″ line

″ emphasizes the interconnection. Either may be used to identify the signal being carried.

Port Protection Group

A user provisioned association of protected optical interface ports. This association is used for line protection. The group of ports represent both a protection switching entity and also a set of lines that carry services to/from another network element. The port protection groups also determine the set of logical tributaries from and to which cross-connections can be provisioned.

Port State Provisioning

A feature that allows a user to suppress alarm reporting and performance monitoring during provisioning by supporting multiple states (automatic, in-service, and not monitored) for low-speed ports.

Port Tag

In Transparent mode, a LAN port is assigned membership to a single VLAN with a unique

VLAN ID and this

″ port tag

″ is added to incoming packets and is used is separate that port’s traffic from any other LAN port. Using this added tag makes the network transparent to any

VLAN tags that the user might have in their packets.

Private Line Mode

The private line mode (also known as no tag or repeater mode) is used to establish simple point-to-point connections between two ports with no Ethernet switching functions applied. No

G L O S S A R Y

G L - 4 4

365-372-300

Issue 8.0 September 2006

additional Ethernet provisioning is required after the cross-connection is established.

Proactive Maintenance

Refers to the process of detecting degrading conditions not severe enough to initiate protection switching or alarming, but indicative of an impending signal fail or signal degrade defect (for example, performance monitoring).

Protection

As defined by the SONET standard, the protection line is the pair of fibers (one transmit and one receive) that carry the SONET APS channel (K1 and K2 bytes in the SONET line overhead). On a DMX 2.5G Multiplexer, a protection line is a pair of fibers that terminate an OLIU circuit pack in the Main-2, A-2, B-2, C-2, or D-2 slots. See Service Line.

Product Family 2000

Lucent’s line of SONET standard network products providing total network solutions.

Provisioning

The modification of certain programmable parameters that define how the node functions with various installed entities. These modifications are initiated locally or remotely by either a CIT or an OS. They may arrive at the node via the IAO LAN, CIT port, or any DCC channel. The provisioned data is maintained in NVM and/or hardware registers.

PSTN - Public Switched Telephone Network

The network that provides public telephone service.

PTM - Pluggable Transmission Modules

Also known as SFPs, PTMs are “pluggable” in the sense that they can be plugged into a circuit pack as they become necessary. This allows customers to grow their network incrementally, only realizing the full cost for optics as the need to provision service on (and thus receive revenue from) them becomes necessary.

Q Quality of Service

Quality of Service is a term used to denote traffic management capabilities, for the purpose of guaranteeing certain qualities through the network, such as Committed Information Rate (CIR), delay, or jitter. QoS Services are created and accessed based on the Traffic Management Mode (see

ED-

EPORT

) that is provisioned at the port, the port aid, the value of Tag ID and the value of COS. Together these will uniquely address a particular service within the network element.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 4 5

R Reactive Maintenance

Refers to decting defects/failures and clearing them.

Remote

See Far-End (FE).

Remote Failure Indication

An indication returned to a transmitting terminal that the receiving terminal has detected an incoming section failure. [Previously called far-end-receive failure (FERF).]

Remote Network Element

Any Network Element that is connected to the referenced Network Element through either an electrical or optical link. It may be the adjacent node on a ring, or N nodes away from the reference. It also may be at the same physical location but is usually at another (remote) site..

Revertive

A protection switching mode in which, after a protection switch occurs, the equipment returns to the nominal configuration (that is, the service equipment is active, and the protection equipment is standby) after the clearing of any failure conditions that caused a protection switch to occur or after any external switch commands are reset. See Non-Revertive.

Ring

A configuration of nodes comprised of network elements connected in a circular fashion. Under normal conditions, each node is interconnected with its neighbor and includes capacity for transmission in either direction between adjacent nodes.

Path switched rings use a head-end bridge and tail-end switch. Line switched rings actively reroute traffic over a protection line.

Ring (0x1) Low-speed Interface

Formerly referred to as dual 0x1 or single 0x1. In ring applications, the DMX 2.5G Multiplexer may use a 0x1 interface, meaning both fibers carry service, as opposed to a linear (1+1) low-speed interface where one fiber is used for service and other for protection. See 1+1.

Ring Circuit Audit

Ring circuit audits validate cross-connection/squelch map information that is manually entered by a user when cross-connections are provisioned and end-to-end circuit connectivity in a

BLSR.

RPP - Reliability Prediction Procedure

Described in Telcordia Technologies TR-NWT-00032.

G L O S S A R Y

G L - 4 6

365-372-300

Issue 8.0 September 2006

RT - Remote Terminal

An unstaffed equipment enclosure that may have a controlled or uncontrolled environment.

S Self-Healing

Ring architecture in which two or more fibers are used to provide route diversity.

Node failures only affect traffic dropped at the failed node.

SEO - Single-Ended Operations

The maintenance capability that provides remote access to all DMX 2.5G

Multiplexer systems from a single location over the DCC.

Service Line

On a DMX 2.5G Multiplexer system, a service (or "working") line is a pair of fibers

(one transmit and one receive) that terminate on an OLIU circuit pack in the Main-

1, A-1, B-1, C-1, or D-1 slots. As defined by the SONET standard, the SONET

APS channel is not defined on a service line. See Protection Line.

SES - Severely Errored Seconds

This performance monitoring parameter is a second in which a signal fail occurs, or more than a preset amount of coding violations (dependent on the type of signal) occurs.

SF - Super Frame

The format for DS1 signals.

Shelf ID

A switch-setable parameter with values from 1 to 8. Used to log into a selected shelf in a by using the CIT.

Single 0x1 Cross-Connection

In a dual-homed application, the DMX 2.5G Multiplexer uses a single 0x1 crossconnection to map the VT1.5 channels between the DDM-2000 FiberReach, OC-3

Multiplexer, or OC-12 Multiplexer and the DMX 2.5G Multiplexer rings. This single 0x1 architecture maps low speed to high speed on a specified ring rotation.

The high speed to low speed drop is made on the same specified ring with no path switching. Protection is provided at the VT1.5 end points.

Single Homing

A network topology in which a single DDM-2000 FiberReach, OC-3 Multiplexer, or OC-12 Multiplexer serves as a DMX 2.5G Multiplexer host supporting up to six

OC-3 or OC-12 rings.

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 4 7

Slot

A physical position in a shelf for holding a circuit pack and connecting it to the backplane. This term is also used loosely to refer to the collection of ports or tributaries connected to a physical circuit pack placed in a slot.

Software Backup

The process of saving an image of the current network element’s databases, which are contained in its NVM, to a remote location. The remote location could be the WaveStar CIT or an OS.

Software Download

The process of transferring a generic or provisioned database from a remote entity to the target network element’s memory. The remote entity may be the WaveStar CIT or an OS. The download procedure uses bulk transfer to move an uninterpreted binary file into the network element.

Spanning Tree Group

Nodes can be provisioned to belong to a spanning tree group. Only the nodes within that group participate in the spanning tree for the group.

Spanning Tree Protocol

Spanning Tree is a protocol that is run on an Ethernet switch that is connected to one or more

LANs for the purpose of preventing loops in a network. Using the protocol, switches communicate with each other to determine the best

″ tree

″ to span the network by

″ pruning

″

(blocking) links that would cause loops. Spanning Tree is used on packet rings as a protection mechanism by automatically moving the block to a failed link.

Squelch Map

The Squelch Map contains information for each cross-connection in a 2-fiber BLSR and indicates the source and destination nodes for the low-speed circuit that is part of the cross-connection. This information is used to prevent traffic misconnection in rings with isolated nodes or segments.

Standby

Standby identifies a 1+1 protected OC-N line which is not currently selected by the receiver at either end as the payload carrying signal, or 1x1 or 1xN protected circuit pack that is not currently carrying service. See Active.

Status

The indication of a short-term change in the system.

STS, STS-n - Synchronous Transport Signal

The basic building block signal with a rate of 51.840 Mb/s for an STS-1 signal and a rate of n times 51.840 Mb/s for an STS-n signal.

G L O S S A R Y

G L - 4 8

365-372-300

Issue 8.0 September 2006

STS-1 SPE - STS-1 Synchronous Payload Envelope

A 125-microsecond frame structure composed of STS path overhead and the STS-

1 payload.

STS-3c

Synchronous Transport Level 3 Concatenated Signal. See OC-3c.

Subnetwork

A group of interconnected/interrelated Network Elements. The most common connotation is a synchronous network in which the Network Elements have data communications channel (DCC) connectivity.

Superframe Format

A DS1 framing format in which 24 DS0 timeslots plus a coded framing bit are organized into a frame which is repeated 12 times to form the superframe.

Synchronization Messaging

SONET synchronization messaging is used to communicate the quality of network timing, internal timing status, and timing states throughout a subnetwork.

Synchronous Network

The synchronization of transmission systems with synchronous payloads to a master (network) clock that can be traced to a reference clock.

Synchronous Payload

Payloads that can be derived from a network transmission signal by removing integral numbers of bits from every frame. Therefore, no variable bit-stuffing rate adjustments are required to fit the payload in the transmission signal.

Synchronous Payload Envelope

The combined payload and path overhead of an STS-1, STS-3c, STS-12c or STS-

48c signal.

SYSCTL - System Controller

The system controller circuit pack that provides overall administrative control of the terminal.

T T1X1 and T1M1

The ANSI committees responsible for telecommunications standards.

Target Identifier (TID)

A provisionable parameter that is used to identify a particular Network Element within a network. It is a character string of up to 20 characters where the characters are letters, digits, or

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 4 9

hyphens (-).

TCA - Threshold Crossing Alert

A condition set when a performance monitoring counter exceeds a user-selected threshold. A TCA does not generate an alarm but is available on demand through the CIT and causes a message to be sent to NMA via the X.25/TL1 interface.

Telcordia Technologies

Telcordia Technologies (formerly Bellcore) is a well-recognized telecommunications standards organization.

Test Access

A set of cross-connection topologies used in conjunction with a testing system to monitor and

″ split

″ signal paths for purposes of fault isolation.

TG3 - Stratum 3 Timing Generator

The timing generator circuit pack, located in the Main (high-speed or network interface) OLIU circuit pack, generates clock signals for distribution to the transmit circuits. It operates in the free-running, loop-timing, external timing, and holdover modes.

Through (or Continue) Cross-connection

A cross-connection within a ring, where the input and output tributaries have the same tributary number but are in lines opposite each other.

TL1 - Transaction Language 1

A Telcordia Technologies machine-to-machine communications language that is a subset of ITU-TSS, formerly CCITT’s, human-machine language.

Time Division Multiplexing (TDM)

A technique for transmitting a number of separate data, voice, and/or video signals simultaneously over one communications medium by interleaving a portion of each signal one after another.

Time Slot Assignment (TSA)

A capability that allows any tributary in a ring to be cross-connected to any tributary in any lower-rate, non-ring interface or to the same-numbered tributary in the opposite side of the ring.

Time Slot Interchange (TSI)

The ability of the user to assign cross-connections between any tributaries of any lines within a

Network Element. Three types of TSI can be defined: Hairpin TSI, Inter-ring TSI (between rings), and Intra-ring TSI (within rings).

G L O S S A R Y

G L - 5 0

365-372-300

Issue 8.0 September 2006

Transparent Mode

In Transparent Mode, port tags (which are actually VLAN tags with a TPID value other than

8100hex) are used to separate traffic for different customers. A port tag is added to each incoming frame at the ingress LAN port. The port tag contains a provisionable customer ID and priority level.

Tributary

A path-level unit of bandwidth within a port, or the constituent signal(s) being carried in this unit of bandwidth, for example, an STS-1 tributary within an OC-N port.

U UAS - Unavailable Seconds

In performance monitoring, the count of seconds in which a signal is declared failed or, in which, 10 consecutively severely errored seconds (SES) occurred, until the time when 10 consecutive non-SES occur.

Unidirectional Path Switched Ring (UPSR)

Path-Switched rings employ redundant fiber optic transmission facilities in a pair configuration, with one fiber transmitting in one direction (for example, East) and the backup fiber transmitting in the other direction (for example, West). If the active path fails, then the standby path becomes active.

UOC - Univeral Optical Connector

Receptacles on the faceplate of some OLIUs that accept ST, SC, or FC connectors.

UPD/INIT

A push-button on the SYSCTL faceplate.

User Privilege

Permits a user to perform a predefined level of tasks on the computer system on which the system software runs.

V Violation Monitor (VM)

A mode of the DS3 circuit pack in which it will monitor but not remove P-bit parity violations on the DS3 signal from the received fiber.

Virtual LAN (VLAN)

A virtual LAN (VLAN) is a subset of a LAN. A VLAN is created by putting VLAN IDs in packets that indicate membership to a VLAN of that ID. A Local Area Network (LAN) can have multiple VLANs within it, up to the number of IDs available. Members (ports) of different

VLANs do not see the traffic of VLANs of which they are not members. A port may be a member of many VLANs (LAN ports in 802.1Q mode, WAN ports). A port may be a member of

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 5 1

many VLANs. In the Transparent mode, a LAN port is typically assigned membership to a single VLAN.

In Transparent mode, VLANs are assigned to ports using Port Tag (ed-eport and ed-vcg. In

802.1Q mode, VLANs are assigned to ports using VLAN IDs (ent-vlan/ed-vlan).

A VLAN tag is the specific field of information in a packet that carries the VLAN

ID number.

Virtual Switch

A virtual switch is a grouping of ports on an Ethernet switch that results in partitioning of the switch into multiple

″ logical

″ switches. A port may only be a member of one virtual switch.

Virtual Tributary (VT)

A structure designed for transport and switching of sub-STS-1 payloads. There are currently four sizes: VT1.5 (1.728 Mb/s), VT2 (2.304 Mb/s), VT3 (3.456 Mb/s), and VT6

(6.912 Mb/s).

VMR - Violation Monitor and Removal

A mode of the DS3 circuit pack in which it will monitor and remove P-bit parity violations on the DS3 signal received from the fiber.

VT1.5

A 1.728 Mb/s virtual tributary.

VT1.5 Tributary

A SONET logical signal with a data rate of 1.728 Mbps. In the 9-row structure of the STS-1

SPE, a VT1.5 occupies three columns. VT-structured STS-1 SPEs are divided into seven VT groups. Each VT group occupies twelve columns of the 9-row structure and, for VT1.5s, contains four VTs per group.

VT-G - Virtual Tributary Group

A 9-row by 12-column SONET structure (108 bytes) that carries one or more VTs of the same size. Seven VT groups (756 bytes) are byte-interleaved within the VTorganized STS-1 synchronous payload envelope

W Wait-to-Rename

Wait to Rename timer for Optimized 1+1 optical line protection. After a protection switch clears, the system waits the provisioned length of time before renaming the working section 1 and working section 2 as Primary and Secondary.

Wait-to-Restore (WTR)

Applies to revertive switching operation. The protection group enters the WTR state when all

G L O S S A R Y

G L - 5 2

365-372-300

Issue 8.0 September 2006

failure conditions are cleared, but the system has not yet reverted back to its working line. The protection group remains in the WTR state until the Wait-to-Restore timer completes the WTR time interval.

Wavelength Division Multiplexing (WDM)

A means of increasing the information-carrying capacity of an optical fiber by simultaneously transmitting signals at different wavelengths.

WaveStar Product Family

A Lucent line of network products.

WideArea Network (WAN)

A communication network that uses common-carrier provided lines and covers an extended geographical area.

Wizard

A form of user assistance that automates a task through a dialog with the user.

X X.25

An ITU standard defining the connection between a terminal and a public packet-switched network

X.25 Interface Protocol

The ITU packet-switched interface standard for terminal access that specifies three protocol layers: physical, link, and packet for connection to a packet-switched data network.

Z Zero Code Suppression

A technique used to reduce the number of consecutive zeros in a line-codes signal

(B3ZS for DS3 signals and B8ZS for DS1 signals).

365-372-300

Issue 8.0 September 2006

G L O S S A R Y

G L - 5 3

G L O S S A R Y

G L - 5 4

365-372-300

Issue 8.0 September 2006

Index

.............................................................................

0x1 application mode

0x1Sn

1+1 bidirectional

10/100 PL pack description

A-14

A-23

10/100BASE-TX

4-35

10/100T circuit pack description

4-35

technical specifications

1000BASE-LX

1000BASE-SX

1000BASE-X

100BASE-LX

optical specification

10-126

100BASE-TX

A-25

12DS3/EC1 circuit pack description

4-21

performance monitoring

6-75

technical specifications

10-6

1G LX circuit pack description

4-36

technical specifications

10-116

10-121

1G SX circuit pack description

1Mbps rate limiting

20 Amp shelf power

28DS1 circuit pack description

4-20

technical specifications

timing functions

10-137

28DS1PM circuit pack description

4-20

performance monitoring

6-74

technical specifications

4000 VLANs

2-18

56DS1PM

4-21

.............................................................................

access network timing

5-79

access transport application

3-7

ACO. See alarm cut-off

ACTIVE LED

add/drop cross-connection

adjusted F&M Bit

administration

software upgrades

alarm gateway network element (AGNE)

alarms

alarm indication signals

(AIS)

6-33

critical

DS1 thresholding

dual OC-12 thresholding

groups

major

minor

OC-48 thresholding

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 1

10-32

10-35

office

10-148

quad OC-3 thresholding

reports

application modes

0x1

distinct

identical

Applications

best effort services

Convergence

DMX as Hub

ethernet private line

3-9

ethernet rate shaping

3-13

Ethernet/TDM access to

IP network

3-25

Ethernet/TDM access top frame relay and ATM

3-24

Hitless Bandwidth

Provisioning, LCAS

3-15

link aggregation

3-17

multi-point ethernet private line

3-11

portless TransMUX

3-46

4-23

SAN Distance Extension

TransMUX

LNW20

transparent LAN

virtual LAN

applications access transport for voice and private line services

3-7

DSLAM access

3-44

established network evolution

3-5

features of

3-2

interoffice transport

3-8

with path switched rings

Area Address

C-4

arrangements bay frames

5-20

cabinet

ASAPs

Atomic cross-connections

5-27

Atomic cross-connects

2-28

automatic provisioning

6-89

automatic synchronization reconfiguration

access network

autoprovisioning

.............................................................................

bay arrangements

5-20

frames

5-20

bay arrangement typical

5-22

bidirectional cross-connections

5-28

bidirectional line-switched ring

BLSR

bridge and roll

bridged cross-connections

5-31

build-outs

7-7

burst-errored seconds

10-135

.............................................................................

cabinet arrangements

outside plant

cable management bracket

4-42

cabling

4-56

5-24

lightguide build-outs

required number

Capabilities

capacity

C-Bit

channel states

circuit breakers

circuit packs

10/100T description

12DS3/EC1 description

1G LX description

1G SX description

28DS1 description

28DS1PM description

48DS3/EC1

56DS1

56DS1PM

8-port GbE

automatic provisioning

6-89

available

4-11

descriptions

4-19

detectable blank LNW97

4-41

dual OC-12 description

4-26

electric continuity test

4-41

LEDs

6-6

LNW18

4-22

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 2

LNW27

LNW28

LNW29

LNW31

LNW32

LNW36

LNW45

LNW46

LNW48

LNW49

LNW50

LNW523/527/554

LNW54

LNW555

LNW56

LNW57

LNW58

LNW59

optical spec

LNW60

LNW62

optical spec

LNW63

LNW64

LNW66

LNW67

LNW68

LNW74

LNW66

LNW67

LNW68

LNW70

LNW71

LNW71

LNW73

LNW73C

LNW74

LNW76

LNW77

LNW78

LNW80

LNY76 and LNW77

OC-12 (high-speed)

OC-192 description

OC-48

OC-48 (low-speed)

OC-48 description

OC-48 DWDM

quad OC-3 description

sparing graphs

specifications

state reports

SYSCTL

description

Trans/MUX

TransMUX circuitpacks

10-7

10-8

OC-192

Circuitpacks, Release 5.1.1

CIT LAN

specifications

coding violations

Configuraqtions

configurations shelf

subnetwork

UPSR control

6-57

4-50

5-70

embedded operations channel

conventions used

course registration

CR (Critical) LED

craft interface terminal

6-6

10-144

Cross-connections

0x1

cross-connections

add/drop

add/drop (1+1)

add/drop (BLSR)

add/drop (UPSR)

allowable

bidirectional

bidirectional (two-way)

bridge and roll

bridged

DRI

dual 0x1

ethernet

hairpin

hairpinning

hairpinning (Ethernet)

locked DS1/DS3

locked VT

making

manual rates

mltpt (multi-point)

multi-point (Ethernet)

5-44

multipoint (Ethernet)

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 3

pass-through

pipe-mode

provisioning

single 0x1

types of

unidirectional

VT bandwidth

Cross-connects

Atomic

2-28

cross-connects atomic

current drain

customized login proprietary messages

.............................................................................

DCC enable/disable

6-19

Definition

B-3

digital subscriber line access multiplexer (DSLAM)

dimensions

Directory services

Distance Extensions

distinct application mode

DMX cabling

circuit packs

cross-connections

high capacity shelf

introduction to

physical arrangements

product description

synchronization

system planning and engineering

5-1

DMXplore

1-5

DMXtend

1-6

document

CD-ROM

conventions used

how to comment

intended audience

reason for reissue

documentation ordering

DRI

drop and continue

DS1 locked

DS1 timing output

DS3 sync messaging

locked

performance monitoring

(PM)

B-41

-??

DSLAM access application

3-44

dual 0x1 cross-connection

5-33

dual homing

2-16

3-65

dual OC-12 circuit pack description

4-26

technical specifications

10-24

Dual Ring Interworking

dual ring interworking

DWDM

LNW221-259,

LNW121-159B

1-19

DWDM amplifiers

3-62

Data communications channel

Compatibility

6-25

Provisioning the DCC

6-19

User side and network side

6-22

data communications channel specifications

see Data communications channel

Data communications channel (DCC)

6-19

data communications channel (DCC)

data storage

day bin

provisioning

DCC

DCC Compatibility

6-25

DCC compatibility

6-25

.............................................................................

E1 support of

2-25

earthquake requirements

10-154

electric continuity test tool

4-41

electrical interfaces

10/100T

12DS3/EC1

28DS1

28DS1PM

Electrical PTM

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 4

electrical SFPs

4-38

10-12

electronic documentation

2-xxviii

embedded operations channel

4-52

EMC requirements

10-153

engineering info

VLF rules

5-15

engineering information

5-10

5-15

engineering services

8-2

environmental considerations

5-25

earthquake requirements

EMC requirements

fire resistance

humidity

specifications

temperature

equipment indicators

LEDs

lightguide build-outs

ordering

equipment protection

ESCON

optical spec

optical specification

10-130

pack description

4-39

established network evolution

3-5

Ethernet cross-connections

5-42

cross-connections

(hairpinning)

5-43

cross-connections

(multipoint)

5-44

enhancements R4.0

2-25

enhancements R5.0 &

5.1

2-26

flow control

A-59

interworking w/

DDM-2000

link aggregation

LNW70

LNW74

loopbacks

multicast packets

optical Fast E

optical specifications

10-96

pack capacities

5-45

pack capacities for rings

5-48

physical interface

A-67

PIR, rate shaping

A-87

protection link aggregation

QoS

LNW70

LNW71/74

QoS on EoS VCGs

Quality of Service

SFP optics

specifications

switched

tagging modes

802.1Q VLAN mode

pricate line mode

, switched mode

transparent mode

ethernet

.............................................................................

Failure Rates

9-5

Fan Filter

5-22

far-end activity

Fast Ethernet private line

SFP optics

10-109

fault

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 5 multipoint applications

3-21

point-to-point applications

3-9

3-11

Ethernet Circuit Packs

A-8

ethernet interfaces

10/100T

1G LX

1G SX

performance monitoring

protection

ethernet over SONET

ethernet protection ethernet aggregation

6-66

Ethernet specifications

LNW63

LNW73C

LNW78

LNW78, RPR

ethernet specifications

LNW63

10-97

external equipment specifications

external timing mode

specification

detection

isolation

reporting

FC-DATA

Features

1+1

2-20

BLSR interworking

2-22

bridge and roll

2-29

cross-connection types

DRI

DWDM

E1 support

electrical packs

Etherenet interworking

2-21

Ethernet enhancements

R4.0

2-25

Ethernet enhancements

R5.0 & 5.1

2-26

Ethernet/SAN interface circuit packs

2-6

external optical amplifiers, SFP optics

2-8

Fast Enternet private line

FTP/FTAM

2-34

GbE packet rings,

VLANs

GbE private line

hardware

High-capacity shelf

high-speed 1+1

in-service upgrades

locked DS1/DS3

loopbacks

ethernet

low-speed UPSR

main switch pack, network interface circuit packs

2-3

multicast Ethernet

2-22

networking capabilities

NTP

NUT

operations

other hardware features

2-8

past releases

1-19

performance monitoring

pipe-mode

proxy ARP

rate limiting

Release 5.1.1 Release

Plan

SAN

SNMP

software download

spanning tree

SS bits

synchronization

test access

topologies

tributary interface circuit pacs

UPSR, BLSR, 1+1

VT1.5 granularity

features

Fibre-Channel

pack description

Fibre-channel optical spec

FICON

optical spec

pack description

fire resistance

FIT rates

equipment

forced switch

free running mode

specification

FTP over IP

FTP/FTAM

FTP/IP

2-34

6-104

function units

4-6

.............................................................................

GbE private line

private lines packet rings

2-18

GbE Private Line

10-97

GbE private line

4-34

Graphic User Interface

growth slots

4-6

GUI

.............................................................................

Hairpin

3-67

5-39

hairpin cross-connections

Hairpinning

hairpinning

hardware cabling

circuit packs

control

shelf description

headless main

High Capacity Shelf

high-capacity shelf

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 6

history log

holdover mode

specification

hubbing

hybrid optical ethernet interface

A-20

.............................................................................

IAO LAN

6-6

6-18

specifications

IAO LAN compatibility

6-12

IAO LAN ports

6-9

ID packets

3-20

identical application mode

6-51

inactivity timeout period

6-123

inhibit switch

6-70

installation services

8-2

intendend audience

2-xxvi

interfaces electrical

10-3

internal testing

6-35

interoffice timing

interoffice transport

interworking

introduction

IP Access

IP tunneling

Assignment

IS-IS level 2 routing

6-118

ISO standards

9-13

.............................................................................

jitter

10-134

jumpers

.............................................................................

Lambda UNITE

10-93

LAN port density

A-43

LCAS

3-15

lightguide build-outs

7-7

technical specifications

lightguide jumpers technical specifications

line build-outs

DS1

line parameter

line state reports

line states

line switching

automatic

line timing

Line timing from tributary packs

2-37

line timing mode specification

10-136

linear optical extensions

OC-48

Linear UPSR

linear UPSR

Link Aggregation

link aggregation

link budgets

1G LX

1G SX

LNW112 specifications

LNW121B-159B optical specifications

LNW2

LNW20

LNW221-259 optical specifications

10-68

LNW26B optical specifications

specifications

LNW27

4-27

optical specifications

specifications

LNW28

4-28

optical specifications

specifications

LNW29

4-28

optical specificationsLNW32 optical specifications

specifications

LNW31

specifications

LNW32

specifications

LNW36

allowed optics

optical specifications

10-36

specifications

10-19

LNW37 optical specifications

10-44

10-48

LNW421-459 optical specifications

10-68

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 7

LNW45

4-25

allowed optics

10-23

optical specifications

specifications

LNW46

optical specifications

specifications

LNW48

optical specifications

10-40

specifications

10-25

LNW49

4-26

optical specifications

specifications

LNW50

optical specifications

10-40

specifications

10-28

LNW523 optical specifications

10-86

LNW523/527/554

4-33

LNW527 optical specifications

10-86

specifications

LNW54

4-27

optical specifications

10-40

specifications

10-29

LNW554 optical specifications

specifications

LNW555

optical specifications

10-86

specifications

LNW56

4-31

optical specifications

specifications

LNW57

optical specifications

10-82

specifications

LNW58

4-32

optical specifications

specifications

LNW59

optical spec

LNW6 specifications

LNW60

optical specifications

specifications

LNW62

optical spec

LNW63

LNW64

LNW66

PIR

A-87

LNW67

PIR

A-87

specification

10-100

LNW68

PIR

specification

LNW7 specifications

LNW70

QoS

SFP optics

SFPs

specification

LNW71 pack description

LNW73

applications

SFP optics

specification

LNW73C

LNW74 pack description

A-25

SFP optics

10-109

LNW76

4-29

optical specifications

10-61

specifications

LNW77

4-30

optical specifications

specifications

LNW78

hubbing

LNW8 specifications

LNW80

LNW93

LNW94

LNW97

locked DS1/DS3

Locked VT cross-connections

loopbacks

DS1

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 8

.............................................................................

MAC address locking

Main slots

main switch pack

maintenance

fault detection

fault isolation

fault reporting

history reports

loopbacks and tests

proactive

remote

signaling

three-tiered operations

manual cross-connection rates

manual switch

medium fabric

medium fabric cards

Miscellaneous Discrete

Interfaces

6-114

6-130

miscellaneous equipment and tools

7-7

mixed protection modes

6-57

MJ (Major) LED

mltpt (multi-point) cross-connections

MN (Minor) LED

modems

MTBF

Multiple Area Addressing

C-5

multipoint ethernet applications

3-20

3-21

multi-service interfaces

2-20

multivendor

multi-vendor operations interworking

NVM

4-19

OC-192

VLF

2-14

4-32

6-18

.............................................................................

network bay frames

configurations

flexibility

synchronization

synchronization environment

5-64

timing distribution

timing distribution questions

5-95

topologies

3-48

Network element (NE) login administration and security

Security

network partitioning

Network size

6-118

network time protocol

NMA

Non-preemtible Unprotected

Traffic

2-19

Non-volatile Memory card

NSAP

NSAP AREA

NSAP provisioning

.............................................................................

OADMs

OC-12 (high-speed)

OC-12 high-speed

Main slots

OC-192 UPSR

configurations

specifications

OC-192/OC-48 unidirectional path switched ring

2-12

2-14

OC-48

4-port LNW62

LNW26B

UPSR

OC-48 circuit pack description

Main slots

technical specifications

OC-48 DWDM

OC-48 UPSR

configurations

specifications

OC-N performance parameters

OLIUs specifications

operations

alarm groups interworking

6-16

6-15

multi-vendor interworking

6-18

three-tiered

three-tiered operations interface

4-50

tier 1

OC-192 circuit pack description

4-31

4-32

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 9

tier 2 tier 3

optical line interfaces purpose of

topology

3-51

typical applications

Operations Interfaces

Miscellaneous Discrete

Interface

6-114

6-130

Office Alarms Interface

6-113

PC-CIT

6-46

operations interfaces

10-143

10-147

craft interface terminal

10-144

LEDs

10-148

PC/CIT

10-144

Operations Interworking

operations interworking

, optical linear extensions

parameters

OC-192

optical loopbacks ordering

7-1

accessories

6-35

7-11

documentation software

ordering,

7-4

how to order

7-2

lightguide build-outs and tools

shelf assembly

software

miscellaneous equipment

OSI

specifications

OSI on the IAO LAN

path switching application modes path witching

P-Bit

6-75

PC/CIT

PC-CIT

Features and Uses

performance status reports

6-97

system

10-132

performance monitoring

6-72

data storage

6-81

DS1

DS3

6-74

6-75

OSI or TCP/IP on the same

IAO LAN

6-11

outside plant cabinet

ethernet interfaces

6-80

ethernet specifications

line parameter

parameter thresholds

optical Ethernet

optical interfaces

1G LX

.............................................................................

packet rings

3-57

parameters and traps

B-58

6-84

passive optics passive optics box

parameters

path parameter

1G SX

dual OC-12

LNW31

OC-192

topology example pass-through

cross-connection

reports

SONET parameters specifications

10-142

performance monitoring

(PM)

OC-3

OC-48

quad OC-3

SONET specifications

password

password aging path parameter operation

path state reports

path switched rings

definition trouble performance parameters

OC-N

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 1 0

STS

B-28

B-32

B-35

personal computer specifications

10-147

physical arrangements

5-2

physical specification

10-152

physical specifications

power

pipe-mode

monitoring point-to-point ethernet applications

port state reports

port states

port units passive optics

portless TransMUX

POUs

power requirements

PRBS generation/detection

6-42

private line services

3-7

private lines

proactive maintenance

6-73

product description

4-1

D-1

Product Family 2000 interworking with

6-15

protection switch, in a BLSR

protection switching

equipment

ethernet interfaces

line

mixed modes

path

priorities

technical specifications

provisioning

auto provisioning

automatic

channel states

circuit pack replacement

cross-connections

default

line states

parameter thresholds

port states

remote

reports

Provisioning the DCC

proxy ARP

PTMs

.............................................................................

QoS

QoS on EoS VCGs

2-27

quad OC-3 circuit pack description

4-24

4-25

technical specifications

quarter-hour bin

provisioning

.............................................................................

R7.0

1-13

R7.0, Release 7.0, Features

reason for reissue

reliability warranty

remote maintenance

provisioning

Remote NE-NE Software

Copy

reports

alarm and status

circuit pack states

line states

maintenance history

path states

performance monitoring

port states

provisioning

threshold crossing alerts

6-80

version/equipment list

rings homing to

path switched

RPR

application, Bridging, fairness

3-31

MIBs

B-98

.............................................................................

S1 byte

safety labels

SAN

Compression

optical specification

packs description

SFP optics

specification

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 1 1

SAN compression

SAN pack detail

Section DCC

Security

Capabilities

System initialization

User types

security

default login and password

self healing

service applications

services worldwide

seven layer protocol stack

seven-layer protocol stack

SFP optics

SFPs

electrical SFPs

shelf assembly

backplane

cabling

capacity

circuit packs

configurations

Control slot

description

front view

Main slots

physical characterisics

power

size

signal performance

single 0x1 cross-connection

single homing

slot equippage

SNMP

Software Download

software download

personal computer specifications

10-147

SONET

data communications channel

overhead bytes

10-133

performance monitoring parameters

spanning tree

fast

sparing

circuit packs

graphs

specifications environmental

10-153

physical

10-151

10-152

SONET optical interfaces

technical

10-1

stacked VLANs

2-18

standards transmission interfaces

state reports

status reports

performance

Stratum 3 Timing Generator

5-65

stratum 3 timing generator

2-37

embedded in OC-48/192

I N D E X

I N - 1 2

365-372-300

Issue 8.0, September 2006

OLIUs

4-9

STS performance parameters

B-28

B-32

B-35

subnetwork configurations

5-70

external timing

5-75

external timing/line timing

5-73

free running/line timing

5-70

Subnetwork Partitioning

Advantages

Guidelines

suitcasing, training courses

8-4

super user

WaveStar CIT

6-123

switch fabric engineering rules

5-10

5-15

switched Ethernet

4-37

switching

1+1 bidirectional

2-20

sync messaging

5-81

automatic synchronization reconfiguration

5-83

DS1 timing output integrity

5-82

synchronization provisioning integrity

5-84

synchjronization tributary line timing

5-67

Synchronization

Line timing from tributary packs

synchronization

DS1 timing output

dual reference monitoring

5-69

external timing

5-75

external timing/line timing

5-73

features

5-66

free running

5-68

free running/line timing

functions

holdover mode

line timing

network synchronization environment

5-64

provisioning integrity

5-84

recommendations

5-65

SDH sync

5-69

Stratum 3 Timing

Generator

5-65

sync messaging

5-81

technical specifications

timing distribution

timing modes

synchronization messaging

2-37

SYSCTL circuit pack control

Control slot

description

faceplate

operations tier 1

system planning

System Controller circuit pack

FAULT LED

System initialization

system overview

system performance

jitter

peformance monitoring

protection switching

signal performance

SONET overhead bytes

synchronization

transient performance

10-140

transmission delay

10-141

wander

10-134

.............................................................................

TARP

Parameters

Provisioning

TARP data cache

Accuracy

TARP NSAP-to-TID translations

6-120

TARP propagation

6-120

TARP provisioning

6-119

TARP TID-to-NSAP translations

TCP/IP

performance monitoring

6-83

specifications

TCP/IP on the IAO LAN

6-9

technical specifications

10/100T

365-372-300

Issue 8.0, September 2006

I N D E X

I N - 1 3

12DS3/EC1

1G LX

1G SX

28DS1

28DS1PM

dual OC-12

electrical interfaces

ethernet

external equipment

OC-48

operations interfaces

optical interfaces

optical link budgets

optical receiver

optical system

optical transmitter

performance monitoring

physical

power

protection switching

quad OC-3

signal performance

SONET overhead bytes

synchronization

system performance

transient performance

10-140

transmission delay

10-141

technical specifications

48DS3EC1

10-6

technical specifications

56DS1

technical specifications

OC-12 (high-speed)

10-25

10-28

10-29

technical specifications

OC-48 (low-speed)

10-65

technical specifications

OC-48 DWDM

10-69

technical specifications

TransMUX

TEMS

Test Access detail

test access

testing internal

specific

three-tiered operations interface

4-50

threshold crossing alerts

reports

transmission to OS

thresholds

TID

TID provisioning

Time and Date

Synchronization

6-111

timing access network

5-79

alternate sources

5-79

distribution

distribution questions

5-95

DS1 timing functions timing modes

TIRKS

TL1

free running

holdover mode

external

specifications

tributary line timing

TCP/IP

translation device

Tl1 Translation

increased span length amplifiers

3-62

packet rings

3-57

DS1 timing output

5-68

interoffice distribution

external timing/line timing

5-73

free running

5-68

free running/line timing

command builder

management

messaging

over TCP/IP

TL1 Translation Device

(T-TD)

TL1/X.25

tools

Topologies

0x1

DWDM

hairpinning

topologies

dual homing

hubbing

linear optical extensions

3-71

path switched rings single homing

3-65

transient performance

10-140

transmission

.............................................................................

unidirectional cross-connections

unprotected paths

Unprotected UPSR

unprotected UPSR

Update/Initialize

UPSR

configurations

specifications

User side and network side

6-22

User types

.............................................................................

V4 byte

10-133

Trans/MUX circuit pack

delay

interface standards

threshold crossing alerts

TransMUX

LNW20

portless

True 0x1

two-way cross-connections

5-28

I N D E X

I N - 1 4

365-372-300

Issue 8.0, September 2006

VCAT

A-33

VCG

A-33

port density

A-43

virtual concatenation

virtual LAN (VLAN)

VLAN

VLANs

VLF Main

engineering rules

VLF Main, LNW59

voice services

VT bandwidth assignment of

VT fabric capacity

VT Ring closure

VT Ring-closure

VT1.5 granularity

.............................................................................

wander

10-134

warranty

9-14

WaveStar Product Family interworking with