Maintenance. Lucent Technologies DMX Access Multiplexer

PDF

Dokument

Annonce

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

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. The generators and detectors are separately allocated.

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

Annonce

Maintenance

Overview

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

Relaterede

Lucent Technologies DMX Access Multiplexer User Operations Guide

Alcatel-Lucent 1665 DMX Applications and Planning Guide

Alcatel-Lucent 1665 DMX Applications and Planning Guide

DMX Access Multiplexer Metropolis DMX Installation Manual

Alcatel-Lucent Data Multiplexer Explore 1665 Installation Manual

Alcatel-Lucent 1665 DMXtend Applications and Planning Guide

DMXtend Access Multiplexer Installation Manual

Alcatel-Lucent 1665 DMX Guide | AI Chat & PDF Download

DMX Access Multiplexer User Operations Guide

Metropolis DMX Alarm Guide - Troubleshooting Manual

WaveStar TDM 10G OC-192 User Operations Guide

Metropolis DMXplore Access Multiplexer Applications and Planning Guide