sonet transmission products s/dms transportnode …npatrick/nortel-sdms-docs/n3rlz7xm.pdf ·...

NT7E65DJ 323-1111-101

SONET Transmission Products

S/DMS TransportNodeOC-3/OC-12 NE—TBM

Software Description

Standard Rel 14 February 2001

What’s inside ...

Software features for the OC-3/OC-12 network elementShelf configurationsInterfaces and data communicationsOAM&P software featuresOPC features

Copyright

1992–2001 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks and S/DMS TransportNode are trademarks of Nortel Networks. VT100 is a trademark of Digital Equipment Corporation. UNIX is a trademark of X/Open Company Ltd.

Printed in Canada

iii

Contents What’s inside ...About this document viiReferences in this document vii

Software features for the OC-3/OC-12 network element 1-1

Shelf configurations 2-1OC-3 terminal 2-1OC-3 linear add-drop multiplexer (ADM) 2-1OC-12 terminal 2-1OC-12 linear add-drop multiplexer (ADM) 2-1OC-12 NWK ring add-drop multiplexer (ADM) 2-2OC-12 VTM ring add-drop multiplexer (ADM) 2-2OC-12 regenerator 2-3SONET DCC bridge 2-3

Interfaces and data communications 3-1Preside and Integrated Network Management (INM) Broadband 3-1Network Manager 3-1Transaction Language 1 interface 3-1Port configuration software 3-2

User interface ports #1 and #2 3-2Serial telemetry (TBOS) ports #3 and #4 3-2Parallel telemetry ports #5 and #6 (IN/OUT) 3-2

Data communications 3-2Ethernet port/X.11 terminal interface (requires OPC) 3-2SONET data communications channel bridge 3-4Control network 3-4Target identifier resolution protocol (TARP) support over TL1 3-4

OAM&P software features 4-1Alarm cutoff (ACO) capability 4-1Alarm history 4-1Alarm provisioning 4-1Area address learning 4-2Area address provisioning 4-2Auto-in-service (AINS) 4-2Automatic and maintenance protection switching 4-2

Software Description 323-1111-101 Rel 14 Standard Feb 2001

iv

Contents

Automatic NE daylight saving time 4-2Automatic protection-switching (APS) exerciser for VTM ADMs 4-2Autoresume 4-3Basic provisioning 4-3Bay, shelf, and unit alarm and status indications 4-3C-bit transparency 4-3Central office alarms (critical, major, minor) 4-3Centralized security 4-3Command interpreter tools 4-4Common Language Equipment Identification 4-4Data communication interoperability 4-4DS1, DS3 and STS-1 loopback 4-4DS1 Remote test unit 4-5DS3 parity correction 4-5Data communications network 4-5Equipment and facility provisioning 4-6Event history 4-6Exerciser 4-7External synchronization interface (ESI) 4-7Firmware download 4-8FirstAlert alarm capability 4-8In-service upgrades, conversions, and capacity expansion 4-8Intersite OAM&P (single-ended operations) 4-9Intra-network element alarm diagnostics 4-10Matched nodes on OC-12 rings (NWK and VTM) 4-10Matched nodes in-service edit 4-10Matched node enhancements 4-10NE A and NE Z mismatch check 4-10NE ID and NE/OPC name enhancement 4-10Network element database backup 4-11Network management windows 4-11Network Upgrade Manager 4-11OC-3 Tributary Synchronization Status Messaging 4-11OPC boot from tape or cartridge 4-11Performance monitoring 4-12

STS-1 path performance monitoring for DS1 4-12Protection-switching performance monitoring 4-12

DS1 performance monitoring (Rx only) 4-13DS3 performance monitoring (Tx, Rx) 4-14STS-1 performance monitoring (Rx only) 4-15

Protection provisioning 4-15Protection provisioning for timing references 4-15Provisionable SONET DCC 4-15Remote inventory 4-16Security enhancements 4-17Software download/restore 4-17Software inventory 4-17SONET/SDH selective programming 4-17STS and VT In-Service Rollover 4-18Synchronization status messaging 4-18S/DMS TransportNode Express/TBM interworking 4-18

S/DMS TransportNode OC-3/OC-12 NE—TBM Vol 1 323-1111-101 Rel 14 Standard Feb 2001

Contents

v

TCP/IP access control 4-18Time-of-day synchronization 4-19Timing-reference provisioning 4-19TL1 Interface 4-19Unframed DS3 clear channel 4-20Universal path trace 4-20

OPC features 5-1OPC configuration software 5-1

Backup OPC 5-1Centralized printing 5-2Electronic software delivery using the File Transfer, Access, and Management

(FTAM) protocol 5-2Ethernet port for an X.11 terminal interface 5-2Network management windows 5-2OPC Port Configuration 5-2Standby TL1 interface access 5-2TL1 access over the Open Systems Interconnect (OSI) interface 5-2Target identifier resolution protocol (TARP) support over TL1 5-3

OPC application software 5-3Alarm Monitor 5-3Backup/Restore Manager 5-4Centralized User Administration 5-4Commissioning Manager 5-4Configuration Manager 5-4Connection Manager 5-4Enable Clear Commissioning 5-5Ethernet Administration 5-5Event Browser 5-5Hardware Baseline 5-5IP Routing Administration 5-5Load Manager 5-6Log Archive 5-6Logout 5-6NE Login Manager 5-6Network Browser 5-6Network Summary 5-6Network Upgrade Manager 5-7OPC Alarm Provisioning 5-7OPC Date 5-7OPC PM Collection Filter 5-7OPC Save and Restore 5-8OPC Shutdown 5-8OPC Status 5-8OPC Switch 5-8Password Update 5-8Port Configuration 5-8Protection Manager 5-8Reboot/Load Manager 5-9Remote OPC Login 5-9


vi

Contents

Remote OPC Software Installation 5-9Remote Telemetry 5-9STPPROV (OPC batch provisioning) 5-9TL1 Configuration 5-9TPB Commissioning tool 5-9Unix Shell 5-10

OPC security 5-10


vii

About this documentThis document provides a description of the OC-3/OC-12 network element software and its associated features.

AudienceThis document is for the following members of the operating company:

• strategic planners

• current planners

• provisioners

• transmission standards engineers

• network administrators

References in this documentThis document refers to the following documents:

• System Description, 323-1111-100

• Signal Flow and Protection Switching Descriptions, 323-1111-103

• Alarms and Surveillance Description, 323-1111-104

• Performance Monitoring Description, 323-1111-105

• Commissioning Procedures, 323-1111-220

• Protection Switching Procedures, 323-1111-311

• Network Manager User Guide, 323-4001-050


viii

About this document


1-1

Software features for the OC-3/OC-12 network element 1-

This chapter describes the various FiberWorld product software features available for the OC-3/OC-12 terminal network element, OC-3/OC-12 linear add-drop multiplexer (ADM) network element, OC-12 ring ADM network element, and OC-12 regenerator network element as well as the individual features associated with each package.

Table 1-1 lists the current software features for the OC-3/OC-12 terminal network element, OC-3/OC-12 linear ADM network element, OC-12 ring ADM network element, and OC-12 regenerator network element for the different categories. These features are described in some detail later in this document.

The software features are grouped into five categories:

• shelf configuration software

• operations, administration, maintenance, and provisioning (OAM&P) software

• operations controller (OPC) configuration software

• OPC application software

• port configuration software


1-2

Software features for the OC-3/OC-12 network element

Table 1-1 Software features for the OC-3/OC-12 network elements

Software features Terminal LinearADM

RingADM

Regenerator

Shelf configurations

OC-3 terminal X

OC-3 linear add-drop multiplexer (ADM) X

OC-12 terminal X

OC-12 linear add-drop multiplexer (ADM) X

OC-12 NWK ring add-drop multiplexer (ADM) X

OC-12 VTM ring add-drop multiplexer (ADM) X

OC-12 regenerator X

SONET DCC bridge X X X X

OAM&P features

Area Address learning X X X

Area Address provisioning X X X

Auto-in-service (AINS) X X X

Autoresume X X X

C-bit transparency X X X X

Common language Equipment Identification X X X

DS1 Remote test unit X X X X

Matched nodes & Enhancements X (See Note 1)

Universal path trace X X X

STS-1 and VT in-service rollover X X X

Matched nodes in-service edits X

Provisionable SONET DCC X X X X

Central office alarms (critical, major, minor) X X X X

Alarm cut-off (ACO) capability X X X X

Bay, shelf, and unit alarm/status indications X X X X

Intra-NE alarm diagnostics X X X X

Automatic and maintenance protection switching X X X

Exerciser (DS1, DS3, STS-1, OC-3, OC-12) X X X

—continued—



1-3

Basic provisioning X X X X

Intersite OAM&P (single-location operations) X X X X

Software download/restore X X X X

Software inventory X X X X

Network element database backup X X X X

External synchronization interface X X X

Automatic NE daylight saving time X X X X

Time-of-day synchronization X X X X

DS1, DS3, and STS-1 loopback X X X

DS3 parity correction X X X

Unframed DS3 clear channel X X X

Alarm provisioning X X X X

Protection provisioning X X X

In-service upgrade X X X X

Event history X X X X

Remote inventory X X X X

Alarm history X X X X

TL1 interface X X X X

Centralized Security X X X

Network Management Windows(for Remote OPC Login tool)

X X X

OC-12 optical performance monitoring X X X X (See Note 2)

OC-3 optical performance monitoring X X X (See Note 3)

Protection switching performance monitoring X X X

DS1 Rx performance monitoring X X X

DS3 Tx performance monitoring X X X

DS3 Rx performance monitoring X X X

STS-1 Performance monitoring X X X

—continued—

Table 1-1 (continued)Software features for the OC-3/OC-12 network elements


RingADM

Regenerator


1-4


Timing-reference provisioning X X X

Protection provisioning for timing references X X X

Provisionable SONET DCC X X X X

SONET/SDH selective programming X (See Note 4)

— — —

Synchronization-status messaging

Secure data communication channel access control

TCP/IP access control

X (See Note 5)X

X

X

X

X

X

X

X

X

OPC configuration software

Backup OPC X X X X

Electronic software delivery using the File Transfer, Access, and Management (FTAM) protocol

X X X X

Standby TL1 interface access X X X X

Ethernet port for an X.11 terminal interface X X X X

Network management windows (for remote OPC log-in)

X X X X

TL1 access over the open Systems Interconnect (OSI) interface

X X X X

Target identifier resolution protocol (TARP) over TL1

X X X X

Centralized printing X X X

OPC application software

Software Admin

Reboot/Load Manager X X X

Backup/Restore Manager X X X

Event Browser X X X X

Network Upgrade Manager X X X X

Alarm Monitor X X X X

—continued—



RingADM

Regenerator



1-5

Connection Mngr

Connection Manager X X X

Connection Mngr (BP) X X X

Connection Mngr (AC) X X X

Connection Mngr (R) X X X

OPC Admin

Centralized User Administration X X X X

Port Configuration X X X

OPC Save and Restore X X X X

OPC Shutdown X X X

OPC Date X X X

Unix Shell X X X X

Event Browser X X X

IP Routing Administration X X X X

OPC PM Collection Filter X X X

TL1 Configuration X X X X

Log Archive X X X X

Security Log Dump X X X X

OPC Alarm Provisioning X X X

Network Admin

Remote Telemetry X X X X

Connection Manager X X X

Configuration Manager (AC) X X X

Network Surveillance

Alarm Monitor X X X

Event Browser X X X

Network Summary X X X X

Network Browser X X X X

Protection Manager X X X X

—continued—



RingADM

Regenerator


1-6


Connection Manager (R) X X X

Outside SOC admin

Load Manager X X X X


TPB Commissioning X X X

Restricted Tools

OPC Switch X X X X

Enable Clear Commissioning X X X X

Ethernet Admin X X X X

NE ID Renumbering X X X X

Surveillance (View)

Alarm Monitor X X X X

Network Summary X X X X


Protection Manager (V) X X X

NE Login Manager X X X X

Network Browser X X X X

SLAT

Commissioning Manager X X X X

Event Browser X X X X¬

Reboot/Load Manager X X X

OPC Save and Restore X X X

OPC Shutdown X X X X

OPC Date X X X

OPC Alarm Provisioning X X X

Utilities

NE Login Manager X X X X

Password Update X X X X

—continued—



RingADM

Regenerator



1-7

The following sections provide a brief description of each of the software features available for the OC-3/OC-12 terminal network element, OC-3/OC-12 linear ADM network element, OC-12 ring ADM network element, and OC-12 regenerator software packages.

Remote OPC Login (only graphical UI using Preside Windows)

X X X X

Hardware Baseline X X X X

Port configuration software

User interface port #1 and #2 X X X

Serial telemetry (telemetry byte-oriented serial, or (TBOS) ports #3 and #4

X X X

Parallel telemetry ports #5 (input) and #6 (output) X X X

Ethernet/X.11 terminal interface (requires OPC) X X X

Note 1: Supported on NWK ADM rings and on VTM rings.

Note 2: Section performance monitoring only on the OC-12 regenerator.

Note 3: OC-3 optical performance monitoring is available for OC-3 tributaries on a VTM ring ADM.

Note 4: Available on OC-12 terminals only (not available on OC-3 terminals).

Note 5: Available on OC-12 linear systems, but not available on OC-3 systems.

—end—



RingADM

Regenerator


1-8



2-1

Shelf configurations 2-For more details on the shelf configurations, refer to System Description, 323-1111-100.

OC-3 terminalThis software feature defines the OC-3 shelf function to be a terminal. It can be configured to terminate a mix of DS1, DS3, and STS-1 tributaries. The DS1 VT and DS3 STS mapper circuit packs, and the STS-1 electrical interface circuit packs are protected in a revertive 1:N scheme. The OC-3 optical interfaces are protected in a nonrevertive 1+1 protection scheme.

OC-3 linear add-drop multiplexer (ADM)This software feature defines the OC-3 shelf function to be a linear ADM. It can be configured to add or drop a mix of DS1, DS3, and STS-1 tributaries along the route of a linear system. The DS1 VT and DS3 STS mapper circuit packs, and the STS-1 electrical interface circuit packs are protected in a revertive 1:N scheme. Both the primary and secondary OC-3 optical interfaces are protected in a nonrevertive 1+1 protection scheme.

OC-12 terminalThis software feature defines the OC-12 shelf function to be a terminal. It can be configured to terminate a mix of DS1, DS3, STS-1, and OC-3 tributaries. The DS1 VT and DS3 STS mapper circuit packs, and the STS-1 electrical interface circuit packs are protected in a revertive 1:N scheme. The OC-3 tributaries and the OC-12 optical interfaces are protected in a nonrevertive 1+1 protection scheme.

OC-12 linear add-drop multiplexer (ADM)This software feature defines the OC-12 shelf function to be a linear ADM. It can be configured to add or drop a mix of DS1, DS3, STS-1, and OC-3 tributaries along the route of a linear system. The DS1 VT and DS3 STS mapper circuit packs, and the STS-1 electrical interface circuit packs are protected in a revertive 1:N scheme. The OC-3 tributaries are protected in a nonrevertive 1+1 protection scheme. Both the primary and secondary OC-12 optical interfaces are protected in a nonrevertive 1+1 protection scheme.


2-2


OC-12 NWK ring add-drop multiplexer (ADM)This software feature defines the OC-12 shelf function to be a TA-1230 ring ADM, a bidirectional line-switched ring (BLSR) configuration for TBM that uses a revertive shared protection scheme as defined by the Bellcore TA-NWT-001230 standard. An OC-12 NWK ring ADM is equipped with OC-12 networking interface circuit packs and with ring loopback circuit packs. It can be configured to add or drop a mix of DS1, DS3, STS-1, and OC-3 tributaries at nodes in ring systems. The DS1 VT and DS3 STS mapper circuit packs, and the STS-1 electrical interface circuit packs are protected in a revertive 1:N scheme. The OC-3 tributaries are protected in a nonrevertive 1+1 protection scheme. Both the primary and secondary OC-12 optical interfaces are protected in a revertive 1:1 protection scheme. This protection scheme differs from the linear ADM shelf in that the lower six STS-1 channels in each ring fiber are reserved for working traffic, and the upper six STS-1 channels in each ring fiber are used for protection of the lower channels in the other fiber.

In contrast to the VTM ring ADM, the NWK ring ADM supports bandwidth management only at the STS-1 level.

Note: It is not possible to have a mixed ring, that is, a ring containing a mix of VTM ring ADMs and NWK ring ADMs.

OC-12 VTM ring add-drop multiplexer (ADM)This software feature defines the OC-12 shelf function to be a GR-1230 ring ADM, a bidirectional line-switched ring (BLSR) configuration for a TBM that uses a revertive shared protection scheme. An OC-12 VTM ring ADM is equipped with OC-12 VTM circuit packs. It can be configured to add or drop a mix of DS1, DS3, STS-1, or OC-3 tributaries at nodes in ring systems. The DS1 VT, DS3 STS, and STS-1 circuit packs are protected in a revertive 1:N scheme. The OC-3 tributaries are protected in a nonrevertive 1+1 protection scheme. The OC-12 optical interface is protected in a revertive 1:1 protection scheme. This protection scheme differs from the linear ADM shelf in that the lower six STS-1 channels in each ring fiber are used for working traffic, and the upper six STS-1 channels are used for protection of the lower channels in the other fiber.

In contrast to the NWK ring ADM, the VTM ring ADM supports bandwidth management at the VT1.5 level as well as at the STS-1 level. VT-bandwidth-management (VTM) functionality is available only for the VT1.5s handled by the DS1 VT mappers.

Note: A mixed ring is not possible (a ring containing a mix of VTM ring ADMs and NWK ring ADMs).



2-3

OC-12 regeneratorThis software feature defines the OC-12 shelf function to be an OC-12 regenerator. It complements the OC-12 regenerator standard OAM&P software. Each OC-12 optical interface circuit pack provides a unidirectional optical link. Hence, two OC-12 optical interface circuit packs are required for bidirectional transmission. Since no DS1, DS3, STS-1, or OC-3 circuit packs are located in the regenerator shelves, no processing is done to extract DS1, DS3, STS-1, or OC-3 tributaries.

SONET DCC bridgeThe SONET data communication channel (DCC) bridge feature permits OAM&P messages to be exchanged between the OC-3/OC-12 systems that are not connected by fiber but have network elements located at the same site. It does not transmit data or voice services (DS1, DS3, or orderwire). The SONET DCC messages from one system are bridged to another system using the control network (CNet) local area network (LAN). See Figure 2-1.

The DCC feature allows a single operations controller (OPC), or one primary and one backup OPC, to manage both systems, eliminating the need for duplicate equipment in each system. CNet supports the following:

• up to ten shelves

• up to 32 stations (a station is a card with CNet ports; a shelf may contain multiple stations)

• bus length of 122 m (400 ft)

• signaling rate of 2 Mb/s (this is the maximum signaling rate, not the message rate of CNet)

If line terminating equipment (LTE) from different transmission spans are close enough together to be linked by CNet, a communication bridge can be established between the spans. Two transmission spans bridged by CNet and administered by one OPC are shown in Figure 2-1.


2-4


Figure 2-1SONET DCC bridge for terminal application

FW-1479

More than one SONET DCC bridge can be used simultaneously between systems. However, the number of network elements managed by a pair of OPCs (their span of control) is restricted to 34. If performance statistics are collected at the OPC for reporting through TL1, then the maximum number LTEs in a span of control is either 24 or the number that contains up to 2016 DS1 circuits, whichever is the smaller. If performance statistics do not have to be collected at the OPC for reporting through TL1, the maximum number of LTEs in a span of control is 24.

The routing function of the LTEs making up the ends of the bridge allow OAM messages to be passed between the network elements making up each transmission span. The OPC can be connected to any network element in one of the bridged spans.

OPC

SONET DCCBridge (CNet Cable)

SONET DCCBridge (CNet Cable)

System 1

System 2

System 3

Terminal

OPC = Operations ControllerLegend:

Terminal Terminal

Terminal

TerminalTerminal


3-1

Interfaces and data communications 3-This chapter provides a description of the following features:

• the Broadband network management interfaces

• interfaces of the OC-12 network element

• data communications between shelves, sites, and systems

• port configuration software

Preside and Integrated Network Management (INM) BroadbandPreside and INM Broadband provide advanced telecommunication system management of S/DMS TransportNode and AccessNode networks. Preside is an evolution of INM Broadband. These products consist of software modules and a user interface. Users can manipulate software modules to customize the graphical user interface. The functions of the graphical user interface include surveillance, alarm management, connection provisioning, software delivery, remote inventory, and performance monitoring capabilities.

Network ManagerThe Network Manager provides a graphical end-to-end view of S/DMS TransportNode and AccessNode networks. This surveillance tool provides a single point of access for OAM&P functions for all OPCs and network elements. With the Network Manager, users can directly log in to OPCs and network elements, view traffic for many networks, and centrally access software management, performance monitoring, inventory collection, and a graphical view of the network elements in the network. Users can run up to five simultaneous Network Manager sessions and manage two active Network Managers through the same OPC subnetwork.

Transaction Language 1 interfaceThe OPC provides a Bellcore-compliant Transaction Language 1 (TL1) interface for communications between an operations system and the OC-12 network element. This interface provides both surveillance and provisioning functions by way of TL1 messages. The OC-12 network element complies with the Bellcore network monitoring and analysis (NMA) OS releases 2.4 and 3.2. Refer to TL1 Interface Description, 323-1111-190, for a list of TL1 interface standards.


3-2 Interfaces and data communications

Port configuration softwareIn addition to the two OPC ports controlled by the OPC Port Configuration tool (described above), the following seven physical ports are available for peripheral interfaces to the TBM shelf (see Figure 3-1):

• two RS-232 user interface ports (port #1 on the Side Interconnect Left card [SIL] and port #2 on the Local Craft Access Panel [LCAP])

• two RS-422 telemetry ports (ports #3 and #4 on the SIL)

• two parallel telemetry ports IN (port #5) and OUT (port #6 on the SIL)

• an Ethernet port supporting an X.11 terminal interface

User interface ports #1 and #2User interface port #1 and #2 provide an interface to any NE-compatible user interface by means of a null modem cable, or a modem. This interface provides complete alarm, protection, provisioning, and inventory for centralized operations in a single NE or an entire S/DMS network.

Serial telemetry (TBOS) ports #3 and #4 This feature provides access to two 2400-baud RS-422 E2A (TBOS) ports. Each port is capable of monitoring up to 512 alarm and status points as eight 64-point displays. The assignment of each display is optional and selectable by the operating company. Maximum application flexibility is achieved by allowing any combination of displays to be assigned to each TBOS port. Details can be found in Alarms and Surveillance Description, 323-1111-104.

Parallel telemetry ports #5 and #6 (IN/OUT)The parallel telemetry feature provides up to 11 external customer inputs and 18 form-A outputs per shelf for system alarms, status, and external equipment controls. Parallel telemetry provisioning is also provided with this feature, allowing external inputs to be labeled from an NE-compatible user interface. All inputs may also be mapped to specific outputs for remote alarm purposes. Details can be found in Alarms and Surveillance Description, 323-1111-104.

Data communicationsEthernet port/X.11 terminal interface (requires OPC)

The Ethernet port (IEEE 802.3 protocol) on the OPC supports communications between the OPC and X terminals, LANs, and the Network Manager. The same functionality as the OPC VT100 user interface is provided. In addition, OPC-to-OPC login is supported, allowing users to view multiple subnetworks from a single X terminal. The Ethernet port supports the following X terminals:

• models NCD19 and NCD19R made by Network Computing Devices

• model 700/RX manufactured by Hewlett-Packard

• model XP18 manufactured by Tektronix


Interfaces and data communications 3-3

Figure 3-1Association between provisioned ports and physical ports

FW-2060 (TBM)

FW-2060 (TBM)

User Interface

Ports provisioned through the NEsystem administration screens

Type

User interface

User interface

TBOS (Note)

TBOS (Note)

Input

Output

Side interconnectleft circuit pack

Note: This port is associated with the RS-422 Serial Telemetry Port.

Port

1

2

3

4

5

6

NE Port 2

UserInterfaceJ10

ParallelTelemetryports

SerialTelemetryports

NE Port 1

NE Port 3NE Port 4

NE Port 5NE Port 6

Ports provisioned through theOPC port configuration tools

Port

1

2

Type

User interface,printer, X.25,X.3 PAD, PPL

X.25

OPC Port 1

OPC Port 2

OC-3/OC-12


3-4 Interfaces and data communications

SONET data communications channel bridgeThe SONET data communications channel (DCC) bridge permits collocated OC-12 systems, which are not connected by fiber, to exchange OAM&P messages.

The SONET DCC bridge uses a control network (CNet) local-area network (LAN) to exchange messages between systems. The SONET DCC bridge enables an operations controller (and its backup operations controller) to communicate with different S/DMS TransportNode systems. For more information, refer to System Applications Description, 323-1111-150.

Note: The total length of the CNet LAN bus (cables and backplane tracking) is restricted to 122 m (400 ft.). For more details on CNet LAN specifications, refer to Technical Specifications, 323-1111-180.

Control networkThe control network (CNet) provides intra-site communications between the shelf processor and the OPC located within the same network element. CNet enables the OPC to download software and to pass alarm, performance, and provisioning data to other network elements within its span of control.

CNet also bridges shelves located at the same site. The bridge permits shelves to exchange SONET section overhead.

Target identifier resolution protocol (TARP) support over TL1TARP transparency is required for operations, administration, and maintenance (OAM) interoperability between OC-48 network elements and TL1-based network elements. The TARP transparency feature is supported on all tributaries that have data communications channel (DCC) capabilities. OC-48 network elements support TARP transparency in all linear and ring configurations, including across matched nodes in rings.


4-1

OAM&P software features 4-This chapter provides a description of the operations, administration, maintenance and provisioning (OAM&P) software features available on the OC-3/OC-12 network element.

Alarm cutoff (ACO) capability ACO capability silences audible central office alarms at both the bay and the shelf level. Maintenance personnel can access ACO from the network element user interface also. Visual alarms cannot be cut off.

Alarm historyThis feature provides a detailed description of the 50 most recent alarms (both active and cleared) that have occurred on a network element. The alarm report provides the following information:

• alarm report ID

• location ID

• cause of alarm

• physical information, depending on the type of alarm

• time stamp of when the alarm occurred

• severity of the alarm (critical, major, minor, or warning)

• alarm service code (service affecting or non-service affecting)

• facility and equipment IDs as required

In addition, the operations controller provides an Event Browser tool for consolidating and archiving the alarms from the various network elements within its span of control.

Alarm provisioningField alarm provisioning permits the enabling and disabling of specific alarm points through the user interface. Refer to Operations and Provisioning Procedures, 323-1111-310. Performance alerts can be set to be raised as alarms, as described in Performance Monitoring Procedures, 323-1111-520.


4-2 OAM&P software features

Area address learningNE Firmware can obtain (learn) the area address of other nodes in a multi-vendor network. This allows a new NE, when necessary, to remotely obtain the software load from the OPC in order for the NE to be provisioned.

Area address provisioningArea address provisioning removes the dependency on the default 49+0000 area address, adds flexibility to the OC-12, and improves interoperability with other vendors’ equipment.

Auto-in-service (AINS)The auto-in-service feature allows customers to provision facilities and filter tributary side alarms which are raised against them when the facility is not immediately used by the end users.

Automatic and maintenance protection switchingOC-12 software provides automatic and maintenance protection switching individually for each of the following: DS1, DS3, STS-1, OC-3, and STS-12 equipment and facilities, and ESI equipment and timing references.

The protection schemes for OC-12 include: 1+1 and 1:1 single-shelf applications, multishelf 1:N applications, the NWK Ring and the VTM ring.

The maintenance protection mechanisms include: forced switches, manual switches, and lockouts. More detailed descriptions of the various protection features are provided in Signal Flow and Protection Switching Description, 323-1111-103.

Automatic NE daylight saving timeThe automatic NE daylight saving time feature automatically maintains the correct time for a network element whether there has been an advancement or retrogression of time from standard time to saving time, regardless of the time zone in which the network element is situated.

Once the time zone for a network element has been entered by a craftsperson, the time on the network element automatically advances or falls back 1 hour at the appropriate time. For time zones that do not implement daylight saving time, the time does not change.

Automatic protection-switching (APS) exerciser for VTM ADMsIn a VTM ring ADM, the exercise command exercises ring protection switching of the requested channel, without completing the actual bridge and switch. The command is issued and the responses are checked, but no working traffic is affected. This command has the lowest priority and can run only when there is no ring protection-switching activity.


OAM&P software features 4-3

AutoresumeThe Autoresume feature adds the following three items to the items list menu of the existing NUM tool in the OPCUI.

• Cancel Pause - cancels any pause that may have been inserted

• Autoresume after - provides a warning to the user regarding the effects of Autoresume. The user is prompted to enter valid values for the hour and minute parameters.

• Remove Autoresume - removes any Autoresume that may have been inserted.

Basic provisioningThis feature supports the provisioning required for basic system operation. This involves setting the parameters for network elements (for example, NE name), shelves (for example, shelf ID), circuit packs (for example, protection priority), and facilities (for example, facility ID). Details can be found in Commissioning Procedures, 323-1111-220.

Bay, shelf, and unit alarm and status indicationsEquipment alarm and status indicators notify maintenance personnel at the bay, shelf, and circuit pack levels. Alarm lamps, power lamps, alarm LEDs, and maintenance status LEDs advise users of critical, major, and minor conditions. Warnings do not light any lamps, although they appear on the network element user interface screen. For more information about OC-12 alarms, refer to Alarm and Trouble Clearing Procedures, 323-1111-543.

C-bit transparencyThis feature has been added with OC-12 Release 14, to support DS3 C-bit parity type signals without impact on OA&M activities hence providing networks with the ability to evolve to data oriented transmissions and potentially allow C-bit based Performance Monitoring.

Central office alarms (critical, major, minor)In the event of service interruption, central office alarms notify maintenance personnel of critical, major, and minor alarms. Audible and visual alarms are available.

Centralized securityThis feature provides the administration of userIDs and passwords for all NEs within the subnetwork, from the OPC user interface. This feature is supported by the Centralized User Administration OPC tool. Network element access privileges, user IDs, and user passwords can also be administered through a TL1 connection.



Command interpreter toolsCommand interpreter (CI) tools are specialized tools accessible through the network element user interface. These tools are used for functions such as displaying connection and node information, troubleshooting alarms, and querying performance characteristics. For a list of CI tools, see User Interfaces Description, 323-1111-301.

Common Language Equipment IdentificationThe Common Language Equipment Identification (CLEI) is a universal ten character code used to identify communications equipment. A CI PECCLEI tool is available to add or modify PECCLEI codes for circuit packs introduced after the software has been released to the customer. You can also use the PECCLEI tool to view the existing list of CLEI codes.

Data communication interoperabilityThis feature allows TBM products and SONET products from other vendors to exchange information. Interoperability is provided at the network layer and data link layer of the OSI reference model. Each vendor’s products forward messages generated by the other vendor’s products, but application software between different vendors is not communicated.

DS1, DS3 and STS-1 loopbackBoth terminal and facility loopbacks are available for each DS1, DS3 or STS-1 tributary (see Figure 4-1 and Figure 4-2). This feature is used when turning up a system or adding a DS1, DS3 or STS-1 facility. It can also be used to sectionalize faults. In the terminal loopback, while the DS1/DS3 or the STS-1 signal from the optics (transport) side is looped back, an alarm indication signal is sent to the DS1, DS3 or STS-1 output port. The facility loopback loops the incoming DS1, DS3 or STS-1 line directly back to the outgoing DS1, DS3 or STS-1 port.

Figure 4-1DS1, DS3 and STS-1 terminal loopback at the local LTE

FW-4709

AIS

NE 1local LTE

NE 2remote LTE

AIS

FW-1465 (R8)

DS1, DS3 orSTS-1 line in

DS1, DS3 orSTS-1 line in

DS1, DS3 orSTS-1 line out

DS1, DS3 orSTS-1 line out

DS1, DS3 or STS-1 port DS1, DS3 or STS-1 port



Figure 4-2DS1, DS3 and STS-1 facility loopback at the local LTE

FW-0034 (R13)

DS1 Remote test unitThe DS1 Remote Test Unit feature allows a customer to perform DS1 testing and monitoring, reducing cost compared to the conventional method of performing digital testing by a local testperson with a test set.

This feature is only available with a DS1 NT7E04EA mapper.

DS3 parity correctionThis feature can be provisioned to provide parity correction on a DS3-by-DS3 facility basis, where the DS3 enters or exits the system. By default, parity correction is disabled (that is, parity is not corrected). If parity correction is enabled, the parity correction occurs at the transmit end or the receive end.

Data communications networkThe Data communications network access control feature allows you to prevent unauthorized access between nodes and the data communication channel (DCC), CNet, or Ethernet network. When a user appears in the Allow list, the user is allowed access to the SONET data communications network. If the user appears in Deny list (even if also listed in the Allow list), access is

NE 1local LTE

NE 2remote LTE

FW-0034 (R8)

DS1 or DS3 line in

DS1 or DS3 line in

DS1 or DS3 line out

DS1 or DS3 line out

DS1 or DS3 port DS1 or DS3 port

UEQ

a) For DS1, DS3

NE 1local LTE

NE 2remote LTE

FW-0034 (R8)

STS-1 line in

STS-1 line in

STS-1 line out

STS-1 line out

STS-1 port STS-1 port

AIS

b) For STS-1



denied. For example, for efficiency of data entry, you can allow all users access to all hosts. You can then explicitly deny specific users access to specific hosts. If both lists are empty and the feature is enabled, all users are denied access.

Access control for the DCC, CNet, or Ethernet is provisionable for incoming connection requests, outgoing connection requests, or both.

Equipment and facility provisioningThe OC-12 network element supports the provisioning of equipment (circuit packs) and facilities. Equipment and the corresponding facilities are automatically provisioned to be in service when the equipment is inserted into the shelf. Users can also manually provision and deprovision the equipment and facilities.

The commissioning process requires that certain basic provisioning parameters be set for network elements, circuit packs, and facilities (see Commissioning Procedures, 323-1111-220). Additional parameters and traffic-carrying STS connections are provisioned after the system is fully tested (see Provisioning and Operations Procedures, 323-1111-310).

Event historyThe event history system records all status changes and alarm occurrences in the OC-3 or OC-12 network element. The event log messages are stored per shelf at the network element and can be automatically routed to a printer connected to a local RS-232 port (provisioned as a printer port). It can also be printed at operator request through a printer attached to the VT100 or compatible user terminal. Each log contains a correlation ID, and a userID when applicable (for example, manual switch was performed). The logs provide descriptive change-of-state information. A searching capability is provided for event types.

Event messages generated by the OC-3 or OC-12 network element system are the following:

• facility (FAC)

• equipment (EQP)

• communication (COML or COMLOG)

• database (FWDB)

• event (EVNT)

• fault (FLT)

• host messaging unit (HMU)

• communication addressing (COADDR or COAD)



Reports can be set up and printed based on the different categories. When a particular buffer is full, a first-in first-out algorithm accommodates additional incoming messages.

Exerciser This routine provides automatic and manual verification of the tributary (low-speed) and transport (high-speed) protection paths and corresponding alarm reporting capabilities. The automatic exerciser runs at 2:00 a.m. every day or it can be scheduled to run at a designated time. The manual exerciser can be started by command and does not affect the automatic schedule.

In order to support a mid-span meet scenario in which any OC-3 tributary or OC-3 or OC-12 transport optic is connected to equipment that does not support exerciser functionality, it is possible to inhibit the exerciser from running on the optics. Consult Signal Flow and Protection Switching Descriptions, 323-1111-103, for more information on the exerciser, and Protection Switching Procedures, 323-1111-311, for the procedures involving the exerciser.

External synchronization interface (ESI)The ESI feature provides the ability to synchronize OC-3/OC-12 network elements to an external timing source and to distribute timing to a building integrated timing supply (BITS). The following features are provided:

• 1+1 ESI equipment protection (two ESI circuit packs)

• dual timing reference output

• for the timing-reference outputs (G1OUT and G2OUT), provisionable timing reference frame format (SF or ESF), line coding (B8ZS or AMI), and line build-out (LBO)

• for the timing-reference outputs (G1OUT and G2OUT), provisionable insertion of alarm indication signal (AIS) if the quality of the active timing source falls below a user-selectable threshold

• 1+1 line timing reference protection

• stratum 3 holdover

• equipment alarms

• LED management

• telemetry (TL1)

• filter mode indication

• hardware inventory

• autoprovisioning

• in-service upgrade to ESI (from systems not equipped with ESI)



• synchronization status messaging extracted from the external timing reference inputs (DS1 or from the TBM SONET line) which allows automatic resynchronization of the network element to the best available timing reference source in the event of a failure of the currently active timing reference

Note: The optional ESI subunit NT7E27CA/EA is required to insert or extract external DS1 signal synchronization messages.

Firmware download This feature automatically downloads firmware locally or remotely to the following circuit packs: the STS-1 interface, VTM circuit pack, and Ring Loopback circuit pack. An automatic firmware download is initiated by card insertion, NE restarts, resets, circuit pack provisioning or a circuit pack state change (that is, OOS to IS). After the automatic download has been initiated, the physical download will only take place if the firmware residing on the circuit pack does not match the software release. This decision is based on the firmware load information specified in the release catalogue. Firmware downloads can also be manually initiated, if required.

The affected shelf processor requests an automatic firmware download to a circuit pack. The firmware load is transferred from the OPC to the Network Element. The processor downloads the firmware to the circuit pack. The process of downloading firmware occurs using the SONET section overhead channel and CNet local-area networks. Traffic functions normally without interruption.

Parallel firmware downloading is also provided. This feature permits concurrent downloads of firmware loads to peripheral processor circuit packs (STS-1, VTM, and Ring Loopback) within the same network element. It also allows this activity to occur concurrently on all network elements within the entire span of control.

FirstAlert alarm capabilityThe FirstAlert alarm capability raises alarms on the OC-12 network element to indicate an alarm condition on either a connected Express network element, or alarms within the Express subnetwork. The user selects one SONET section data communication channel (SDCC) for each tributary connected to an Express shelf.

In-service upgrades, conversions, and capacity expansionThe OC-12 network element supports in-service upgrades, configuration conversions, and system expansion. Supported system alterations include the following:

• upgrading software and hardware

• expanding in-service capacity



• changing tributaries

• converting linear systems to rings

• interconnecting rings by way of matched-node connections

• converting a linear system to a NWK ring

• converting a NWK ring to a VTM ring

• converting the provisioning of STS-3c connections

• adding or deleting a VTM ring node

System expansions and conversions are detailed in System Expansion Procedures, 323-1111-224 and System Expansion Procedures II, 323-1111-225. All software upgrades must be performed according to the appropriate Change Application Procedure (CAP).

Intersite OAM&P (single-ended operations)This feature enables users to share network-wide operations, administration, maintenance, and provisioning information. As shown in Figure 4-3, users remotely access ADM nodes, regenerators, or terminals within a given span of OPC control. Users log into the user interface from a VT100-compatible terminal connected to either a network element or an OPC. Network element software automatically relays information using the SONET section overhead by way of the SONET section data communications channels (SDCCs) and CNet local-area networks.

Figure 4-3VT100-compatible interface

FW-0029

Modem

Telephone line

VT100-compatible interface

Networksurveillance

center

Regenerator RegeneratorTerminal Terminal



Intra-network element alarm diagnosticsThis feature processes the alarm and diagnostic information within a given network element. It analyses the various alarm points that have been triggered by a fault condition and raises the appropriate alarm.

Matched nodes on OC-12 rings (NWK and VTM)The matched nodes feature on OC-12 BLSRs provides a survivable path between OC-12 BLSRs interconnected with one or more OC-12 or OC-48 BLSRs as well as OC-3, OC-12, or OC-48 unidirectional path-switched rings (UPSRs). Matched nodes protect interconnected rings against link and node failures by having STS-1 signals cross ring boundaries at two different network elements.

Note: Matched nodes are supported on NWK and VTM rings.

Matched nodes in-service editThis feature provides the capability to perform the following in-service edits:

• Non-matched node connection to matched node connection and vice versa

• DS3 non-matched node connection to STS-1 matched node connection

• Matched -node DCW connection to matched node DCP connection and vice versa

• Edit tributary at the primary or secondary gateway node

Matched node enhancementsThis feature provides:

• two additional user-initiated protection requests, Lockout of Protection, and Manual Switch

• enhanced service selector alarms to include channel number

• additional information in Matched Node logs and alarms

NE A and NE Z mismatch checkWhen the user audits connections provisioned on NEs in a linear configuration the audit dialog displays a check box to include non-service affecting mismatches. The mismatches are now identified so that the user may correct them.

NE ID and NE/OPC name enhancementThe NE Id is a 5-digit parameter required to identify an NE. This enhancement extends the range from “1 to 32767” to “1 to 65534.”

NE name enhancement extends the size of the parameter from 13 to 20 characters.



OPC name enhancement extends the size of the parameter to 9 characters to align with the NE Id enhancement.

Network Id and System Id can be provisioned in the range from 1 to 65534.

Network element database backup Network element database backup provides nonvolatile storage for the current network element database and backup copies of earlier versions of database information. In the event of a shelf processor reload, the database backups enable restoration. Up to two backup copies can be kept on-line.

The network element database contains all the default and user-provisioned parameters, as well as system-defined hardware register values. Network element backups, stored as files on the OPC, are backed up in three ways: scheduled backup, user-initiated backup, or automatic backup reflecting an incremental threshold change.

Network management windowsThis feature provides multiple subnetwork OPC login sessions for up to five subnetworks that are displayed on a graphical terminal. To provide this feature, an X.11 terminal is connected to a subnetwork by way of Ethernet, and then OPC-to-OPC login is performed, using the Remote OPC Login tool, to interface with the other subnetwork. Then, the X.11 terminal can be used to display multiple VT100 type screens of each subnetwork’s alarm summary.

Network Upgrade ManagerThe Network Upgrade Manager allows the user to automatically upgrade the software load for all network elements in an OPC’s span of control. Network elements are upgraded according to a user-defined sequence. This tool simplifies the management of software upgrades for the network, during a network upgrade.

OC-3 Tributary Synchronization Status MessagingThis feature provides synchronization status messages on OC-3 tributaries. This allows subtending OC-3 NEs to use SSM when timing from OC-12 NEs.

OPC boot from tape or cartridgeThe OPC boot from tape or cartridge feature makes it possible to initialize and reboot the OPC hard disk or solid state hard disk using a disk initialization tape or cartridge. The process is controlled through a menu driven script that prompts the user for input as needed. Once the script has completed the disk initialization process, the user can then reboot and load the OPC application software.



With this feature, the number of spare OPCs can be reduced because the same spare OPC can be used for both OC-48 and OC-3/OC-12 systems. The spare OPC hard disk can be initialized and the proper software load, OC-3/OC-12 or OC-48, can then be installed.

Performance monitoring The OC-3/OC-12 network element monitors the performance of the signals in the system (DS1, DS3, STS-1, OC-3, and OC-12 rates) and provides counts for relevant parameters. It also provides protection-switching statistics. All performance-monitoring information collected by a given OC-3/OC-12 is transferred to the OPC for that span of control, if performance monitoring data collection is turned on.

STS-1 path performance monitoring for DS1The following counts are provided:

• code violation (CV-P) (Rx)

• error second (ES-P) (Rx)

• severely errored second (SES-P) (Rx)

Counts are provided over the following intervals:

• current and last 32 15-minute intervals

• current and last 7 days

• current untimed

Two threshold levels for line CV, line ES, and line SES, are user selectable. Details can be found in Performance Monitoring Description, 323-1111-105.

Protection-switching performance monitoringThis feature counts the automatic and manual protection switching (at DS3, STS-1, OC-3, and OC-12 levels) and switch durations and completions over the following intervals:



• current untimed

Note: Protecting switching statistics are collected for DS3, STS-1, OC-3, and OC-12 facilities, but not for DS1 facilities. OC-3/OC-12 optical performance monitoring

The following counts are provided:

• line code violation (CV) (Rx)

• line error second (ES) (Rx)

• line severely errored second (SES) (Rx)



• line unavailable seconds (UAS) (Rx)

• line failure counts (FC) (Rx)

• section code violation (CV) (Rx)

• section error second (ES) (Rx)

• section severely errored second (SES) (Rx)

• section severely errored frame second (SEFS) (Rx)

• laser bias current (LBC) (Tx)

Two user-selectable threshold levels are provided for line CV, line ES, line SES, line UAS, section CV, section ES, section SES, and section SEFS. One user-selectable threshold level is provided for the laser bias current. Details can be found in Performance Monitoring Description, 323-1111-105.

OC-12 far-end (Tx) performance monitoring is supported for network elements equipped with OC-12 VTM circuit packs. (This is in addition to the near-end (Rx) performance monitoring.) OC-12 far-end performance monitoring is available for the following parameters:

• line code violation (CV) (Tx)

• line error second (ES) (Tx)

• line severely errored second (SES) (Tx)

• line unavailable seconds (UAS) (Tx)

• line failure counts (FC) (Tx)




• current untimed

DS1 performance monitoring (Rx only)The following counts are provided:




• path code violation (CV) (Rx)

• path error second (ES) (Rx)

• path severely errored second (SES) (Rx)

• path severely errored frame/alarm indication signal second (SAS) (Rx)

• path unavailable second (UAS) (Rx)



• path failure count (FC) (Rx)




• current untimed

Two provisional thresholds are provided per parameter and facility, except for the path failure count (FC). DS1 performance analysis is done in-service or out of service. Parameters are generated for facilities that are out of service, however, threshold crossings are not reported to the user interface.

Note: The path performance parameters are not applicable to unframed DS1 clear channel facilities (framing is set to OFF).

DS3 performance monitoring (Tx, Rx)The following counts are provided:




• path alarm indication signal second (AISS) (Tx, Rx)

• path code violation (CV) (Tx, Rx)

• path error second (ES) (Tx, Rx)

• path severely errored second (SES) (Tx, Rx)

• path severely errored frame second (SEFS) (Tx, Rx)




• current untimed

Two provisional thresholds are provided per parameter, facility, and direction. DS3 performance analysis is done in-service and for both directions of transmission (BPV in receive direction only, with respect to S/DMS equipment).

Note: The path performance parameters are not applicable to unframed DS3 clear channel facilities (framing is set to OFF).



STS-1 performance monitoring (Rx only)The following counts are provided:




• line unavailable second (UAS) (Rx)

• line bipolar coding violation (BCV) (Rx)

• line bipolar errored seconds (BES) (Rx)

• line bipolar severely errored seconds (BSES) (Rx)




• current untimed

Two provisional thresholds are provided for each parameter, facility, and direction. STS-1 performance analysis is done in-service and for the receive direction.

Protection provisioningProtection provisioning allows the selection of either bidirectional or unidirectional OC-3 or OC-12 protection switching, as may be required in multi-vendor networks (the default is bidirectional).

Protection provisioning for timing referencesProtection for timing references is automatic, but you can specify priorities for the available timing references. If the network element must perform an automatic switch to an alternative timing source, and if there are two alternative sources of equal quality, then the network element switches to the source with the higher priority. If you use synchronization status messaging, and the network element must perform an automatic switch to an alternative timing source, then a switch will be made to the reference with the highest quality level. See 323-1111-192 for information on synchronization status messaging.

Provisionable SONET DCCThe provisionable SONET data communication channel (DCC) feature permits OAM&P messages to be exchanged between network elements that are connected by fiber. SONET DCCs can be enabled or disabled on both the transport and tributary optical interfaces. This is for mid-span meet scenarios in which security may be a concern or if there are incompatibilities when equipment is connected to another manufacturer’s equipment. When a



transport optical interface circuit pack, OC-3 or OC-12, is provisioned, the SONET DCC for that line is automatically added, that is enabled. When the tributary optical interface circuit pack, OC-3, is provisioned, the SONET DCC for that line is not automatically enabled.

Remote inventoryFrom an network element user interface, this feature offers the ability to remotely determine specific details pertaining to both shelf hardware and software.

When a specific shelf is interrogated, S/DMS will return the following data:

• shelf slot location of each circuit pack

• name of each circuit pack

• CLEI code of each circuit pack

• NT code of each circuit pack

• hardware vintage of each circuit pack

• serial number of each circuit pack

• circuit pack state

Such pertinent information can improve the overall efficiency of an operating company’s inventory control system. With its remoting capability, this feature reduces the manpower and time required for inventory verification. It proves especially beneficial for unmanned offices, such as remote repeater locations. The cost of inventory spares is also minimized with the S/DMS ability to remotely determine which cards need replacement during maintenance action.



Security enhancementsThis feature provides the following security features to aid the customers in monitoring the network.

• Account activity information for the user is displayed on login to the OPC and NE.

• Account activity information from all nodes in the span of control are summarized and displayed through the Centralized User Administration tool.

• User accounts are disabled if the account is not used for a preset number of days.

• The keyboard is automatically locked out if there has not been any inputs from the keyboard for a specified period of time.

Software download/restoreWith this feature, software can be downloaded locally or remotely to an S/DMS TransportNode shelf. The downloading of software to the processor (Proc) circuit pack is done automatically without the need for administrator intervention. This feature provides a facility to restore the current software version to the Proc when a software failure or a Proc failure has occurred.

The administrator may also manually initiate software download in order to upgrade software at a network element. In the event of a software restore, a request from the network element to the OPC is initiated to restore the software. When the OPC receives the request from the network element, the OPC will download the software to the requesting network element Proc. Downloading software is internal to the system and occurs using the SONET section overhead channel and CNet local area networks without affecting traffic (data communication beyond the network element being downloaded is not available during the restore process).

Software inventoryThis feature provides the inventory of all operational network element and OPC software within the subnetwork (includes load information). Software load identifiers are provided for both network element and OPC software.

SONET/SDH selective programmingThis feature provides the ability for a mix of SONET and SDH tributaries to co-exist on one NE by selective programming of the signal mode of individual OC-3 optics to SONET or SDH.



STS and VT In-Service RolloverThis feature provides the capability to allow the in-service movement of a circuit from one STS or VT1.5 time slot (source) to another STS or VT1.5 time slot (destination) within a network. Two types of IS Rollover are supported:

• IS Channel Rollover (ISCR): Traffic is moved from one transport channel to a different transport channel in the same direction. ISCR is supported on OC-3 linear, OC-12 linear, OC-12 NWK and OC12 VTM BLSR configurations.

• IS Route Rollover (ISRR): Traffic is moved from one transport channel to a different transport channel in the opposite direction, or traffic is moved from one transport channel to the same transport channel but in the opposite direction. ISSR is supported on OC-12 NWK and OC12 VTM BLSR configurations.

Synchronization status messagingSynchronization status messages travel from one network element to the next. In each network element, the messages are generated and placed in the SONET line overhead. At the next network element, the messages indicate the quality of the timing that can be derived from the SONET signal. If the timing reference degrades, or if a failure in the system causes an interruption of the SONET signal, the network element can perform an automatic switch to an alternative timing source. It chooses the highest-quality alternative timing source available, as indicated by the synchronization-status messages.

S/DMS TransportNode Express/TBM interworkingWith this feature, existing alarm conditions on remote S/DMS TransportNode Express shelves connected to TBM systems through OC-3 tributaries are indicated on the TBM shelf to which the Express is connected. Basic information such as alarm type, severity, and location is provided.

TCP/IP access controlThe TCP/IP access control feature allows you to prevent unauthorized access between the OPC and the TCP/IP network.

When a user appears in the Allow list, the user is allowed access to the TCP/IP network. If the user appears in Deny list (even if also listed in the Allow list), access is denied. For example, for efficiency of data entry, you can allow all users access to all hosts. You can then explicitly deny specific users access to specific hosts. If both lists are empty, all users are denied access.

Access control for the TCP/IP network is provisionable for incoming connection requests, outgoing connection requests, or both.



Time-of-day synchronizationTime-stamped information must be accurate to the nearest 2 seconds across all user interface screens on S/DMS TransportNode shelves, and the primary OPC within a subnetwork. The following is the format in which the time-of-day information is stamped: MM:DD:HH:MM:SS (month:day:hour: minute:second). Time stamping is used for performance monitoring, alarms, and troubleshooting purposes.

Timing-reference provisioningTiming-reference provisioning allows you to specify up to four potential sources of timing for a network element: two sources of line timing and two external (BITS) timing sources. With line timing, the network element takes its timing from the incoming SONET signal; with external timing, the network element takes its timing from a building integrated timing source (BITS). (You can specify external timing sources only if the network element contains one or two ESI cards.)

TL1 InterfaceThe OPC provides a Bellcore-compliant Transaction Language One (TL1) OS-to-NE interface for OC-3/OC-12 that is compatible with BellCore’s Network Monitoring and Analysis (NMA) and Operations Provisioning System (OPS)/INE commands. Messages are supported to provide fault management, performance monitoring, provisioning, and control capabilities. The interface is compliant to the CCITT X.25 protocol. NMA conformance depends upon Bellcore delivery of backwards compatibility.

The TL1 interface allows the OPC to communicate with the OS through a physical X.25 port (port B) located on the OC-3 or OC-12 terminal shelf. The OPC acts as a gateway through which the OS may access the different network elements in the subnetwork, therefore there is no need to have a separate physical link to each network element.

The TL1 interface does not require any additional hardware since it consists of a software implementation and upgrade. The features offered with the TL1 interface are:

• single-ended interface, remote capabilities

• no mediation device requirements

• standby TL1 interface provided by a separate X.25 physical connection (on another shelf in the subnetwork) for a given OPC’s span of control

• functional capabilities that include fault management, performance monitoring, provisioning, and protection switch control

• NE user administration

• switch virtual circuit at a baud rate of up to 19.2 kb/s



Unframed DS3 clear channel A DS3 clear channel signal operates at the same rate as a standard DS3 signal (44.736 Mb/s, B3ZS encoded), but it does not contain any sub-DS3 framing (such as DS2 framing). The DS3 clear channel feature provides the capability of carrying unframed signals as DS3 payloads. This feature allows TransportNode products to carry signals such as special video encoding and computer-to-computer exchanges.

The feature can be set on a per DS3 basis. Thus, a mix of framed and unframed DS3s can be supported on the same DS3 STS mapper circuit pack. The unframed facilities are provided with the same protection as standard DS3 signals. The exerciser remains fully operational and its diagnosis is identical to that of a standard DS3 signal.

Due to the inherent nature of the unframed signal, all processes involving parity correction and monitoring are not applicable. DS3 transmit/receive (Tx/Rx) parity correction should be set to OFF by the user. Path performance monitoring counters will increment when monitoring an unframed DS3, however, the counts should be ignored. It is recommended that the corresponding path alarms/alerts be turned off to avoid any false alerts from occurring.

Note 1: With an unframed DS3, the loss of signal (LOS) and bipolar violation alarms are still valid; but, the loss of frame (LOF) and parity error alarms will not be raised, regardless of their provisioning.

Note 2: DS3 AIS (which requires frame for direction) will not be raised.

The default setting of a framing parameter is ON.

Universal path traceThe universal path trace feature is a user-accessible feature designed to ensure the integrity of the path overhead (POH) embedded in the SONET STS-1 synchronous payload envelope (SPE) at a path terminating tributary. The universal path trace feature allows a craftsperson to provision a unique identifier for any connection established in the network to confirm that the routing is correct before adding traffic. The OPC connection services tool is enhanced to provide the interface for the provisioning and retrieval of path trace data.


5-1

OPC features 5-This chapter provides description of the operations controller (OPC) tools and features used with the OC-12 network elements.

The OPC plugs directly into any S/DMS TransportNode shelf and supports up to 34 OC-12 network elements. For more information on the OPC span-of-control limits and other engineering guidelines, see Technical Specifications, 323-1111-180.

The integrated tape or cartridge drive on the OPC provides the mechanism to upgrade systems with new software loads. Users upgrade the system by means of digital data storage (DDS) tapes or cartridges. One OPC with tape or cartridge drive is recommended for each OPC span of control.

OPC configuration softwareThis section describes the software that supports the various OPC configurations used with the OC-12 network elements.

Backup OPCThis feature provides the capability for a redundant OPC module to be equipped in the S/DMS TransportNode subnetwork to provide intersite OAM&P functionality in the event of an OPC hardware/software failure, cable cut, or node failure. The backup OPC is optional, but it is recommended that it be engineered for all systems.

In the event of an OPC hardware/software failure, services provided by one OPC’s span of control can be taken over by the backup OPC. The backup OPC provides no services until they are required, that is, when a primary OPC fails or in the event of a cable cut between NEs housing the primary and backup OPCs. It does not share the load of performing network services with the active OPC. The backup OPC runs in a warm backup mode, that is, the backup OPC has application software loaded and is ready to take over the functions of a primary OPC.


5-2 OPC features

In the event of a cable cut, service provided by the primary OPC to the nodes downstream of the cable cut will be provided by the backup OPC. In the event of a node failure/data communication failure, service provided by the primary OPC to the failed node and the nodes downstream of the failed node will be provided by the backup OPC.

Centralized printingThis feature provides the capability to print the event/alarm history for the subnetwork and reports generated by the OPC.

Electronic software delivery using the File Transfer, Access, and Management (FTAM) protocol

The OPC supports delivery of new software releases from a central software repository. The delivery uses the FTAM protocol over a TL1 connection as required by the Bellcore GR-1250-CORE specification.

Ethernet port for an X.11 terminal interfaceThe Ethernet port (IEEE 802.3 protocol) on the OPC supports a locally connected X.11 terminal. The same functionality as the OPC VT100-compatible user interface is provided. In addition, OPC-to-OPC log-in is supported, allowing users to view multiple subnetworks from a single X.11 terminal.

Network management windows This feature provides multiple OPC log-in sessions for up to four OPC spans of control, which are displayed on a graphical terminal. To provide this feature, an X.11 terminal is connected to a subnetwork by way of Ethernet, and then OPC-to-OPC log-in is performed using the Remote OPC Login tool to interface with the other subnetwork. Then, the X.11 terminal can be used to display multiple VT100-type screens of each subnetwork alarm summary.

OPC Port ConfigurationThe OPC Port Configuration tool is used to configure the OPC ports to support terminal, printer, or X.29/X.3 PAD communications.

Standby TL1 interface accessThe TL1 port associated with the backup OPC is the standby TL1 link. It is activated when the backup OPC becomes active. In the event of a cable cut between NEs housing the primary and backup OPCs, both primary and standby TL1 links are activated.

TL1 access over the Open Systems Interconnect (OSI) interfaceThe OPC can accept TL1 sessions initiated from other vendors’ network elements. The other vendors’ gateway network elements connect by way of SONET section data communications channels (SDCCs) to an OC-12 network element. The OC-12 network element then routes the TL1 connection to the


OPC features 5-3

OPC by way of SDCCs, the control network (CNet), or a combination of SDCCs and CNet. The connections use the OSI protocol to access the TL1 interface of the OPC.

Target identifier resolution protocol (TARP) support over TL1The OPC supports the target identifier address resolution protocol (TARP) as specified by Bellcore GR-253-CORE. The OPC can then accept TL1 communications from other vendors’ equipment by way of OC-12 network elements.

OPC application softwareThe OPC provides centralized data management (for example, data collection, storage, and consolidation), software management, and integrated OAM&P view for subnetwork NEs. Remote software delivery can be achieved by means of preloaded hardware or tape or cartridge. The OPC also provides network element database backup and restore capabilities. The four-slot OPC module plugs directly into any S/DMS TransportNode shelf and supports up to 12 shelves.

The integrated tape or cartridge drive on the OPC module provides the mechanism to upgrade systems with new software loads that are delivered by means of tape or cartridge. Tapes or cartridges can also be used for software and database backups. One OPC with tape or cartridge drive is required for each subnetwork. With the OPC-to-OPC file transfer feature, one OPC with tape or cartridge drive will be required for each network.

The OPC can also provide input to the Network Manager, a software application that runs on UNIX-based workstations. The Network Manager provides a graphical end-to-end view of the alarm counts collected from all the network elements in an S/DMS TransportNode subnetwork. Such a subnetwork can include several spans of control, with the OPC for each span of control handing off the alarm counts for all its NEs to the Network Manager.

The Network Manager also provides a single point of access to the OAM&P functions of the NEs. For more information on the Network Manager, refer to Network Manager User Guide, 323-4001-050.

The OPC applications software provides the basic OAM&P feature capabilities for the primary and backup OPC. The OPC applications software is packaged as tools.

Alarm MonitorThe alarm monitor feature enhances the alarm surveillance features on the OPC user interface. A one-line summary of alarm information is provided for all active alarms within the OPC’s span of control. For alarm details, the user


5-4 OPC features

can select an alarm line and choose Alarm Details from the menu. Sorting capabilities (for example, by network element, severity, or time) are also available.

Backup/Restore ManagerThe Backup/Restore Manager enables you to manage the network element database backup files that the OPC stores automatically. These database files are used to restore a network element after failure or after a software release upgrade.

You can set the number of backup files stored by the OPC for each software release of each network element, list all of the backup files that exist, and delete backup files that are no longer needed.

Centralized User AdministrationThe Centralized User Administration tool is used to define users and user passwords, and to control user access to tools by the assignment of security levels.

Commissioning ManagerThe commissioning process (required when initially setting up the system) includes setting OPC and network element addresses (serial numbers) for communication, and basic network element configuration. This is controlled by the commissioning manager tool. This tool is only available for the SLAT userID.

The commissioning manager tool is also used to transfer commissioning data from the primary OPC to the backup OPC.

Configuration ManagerThe Configuration Manager allows access to two subtools: the Linear Configuration Manager, for linear systems, and the Ring Configuration Manager, for ring systems. Using the appropriate subtool, you can specify the type and position of each network element (NE) in a network. The Configuration Manager also provides an overview of each configuration in the system. All configurations are listed, and all NEs in each configuration are described, by connectivity in the configuration and by network element type.

Connection ManagerThe Connection Manager provides the management of STS-1 connections and VT connections. It provides STS-1 connections in all types of systems; it provides VT connections only in VTM rings. It specifies where STS-1s and VTs are added and dropped in the network. In addition to setting up or changing STS-1 and VT connections, this feature displays all connections, including those that terminate in another OPC span of control, reviews STS-1


OPC features 5-5

and VT channels in use between two TBM network elements, reviews facilities (that is, tributaries) in use at a TBM network element, and audits the connection data at specified TBM NEs.

Enable Clear CommissioningThe Enable Clear Commissioning tool deletes the internal OPC commissioning data. This tool disables communication between the OPC and the network elements.

Ethernet AdministrationThe Ethernet Administration tool removes the Ethernet address to initialize, enable, and disable communications between the network and external operations systems.

Event BrowserThe Event Browser provides a detailed list of logs that capture events related to the OPC. The Event Browser covers events such as:

• communication between the OPC and NEs in the OPC’s span of control

• software and data administration events, such as software downloads and network element backups

• primary and backup OPC status changes

• general OPC level events

Hardware BaselineThe Hardware Baseline tool identifies the product engineering code and hardware release number of circuit packs, and schedules a hardware baseline audit. The default baseline can be modified to suit user-specified needs. There are two baselines which this tool supplies a default provided by Nortel Networks, and a customer-modified baseline. At any time, only one of two baselines can be active.

The Hardware Baseline tool permits the OPC to schedule an automatic hardware baseline audit once a day. Manual audits may be run any number of times. If the audit determines that a circuit pack is performing below the active baseline, it raises a minor non-service affecting alarm.

IP Routing AdministrationThe IP Routing Admin tool is used to add and delete entries from the gateway to network routing table. This tool is used to define the gateways that connect networks when TCP/IP over X.25 is enabled. The gateway to network routing table allows communication between the local network and remote networks. If the routing table is not defined, communication is only possible within the local X.25 network.


5-6 OPC features

Load ManagerThe Load Manager tool allows users to view the OC-3/OC-12 OPTera Metro 3000 series load currently stored on the local OPC, view the OC-3/OC-12 OPTera Metro 3000 series load on the tape or cartridge in the tape or cartridge drive, delete the OC-3/OC-12 OPTera Metro 3000 series load from the local OPC, and install an OC-3/OC-12 OPTera Metro 3000 series load on the local OPC. Although the OPC can store the OC-3/OC-12 OPTera Metro 3000 series load, it does not manage OC-3 or OC-12 OPTera Metro 3000 series network elements. To monitor or perform administrative activities for an OC-3 or OC-12 OPTera Metro 3000 series network element, users log in to the OC-3 or OC-12 OPTera Metro 3000 series network element user interface, the Network Manager, the Integrated Network Management (INM) Broadband product, or Preside.

Log ArchiveThe Log Archive tool provides a means of scheduling the collection of logs by the OPC from the network elements in its span of control. The logs collected by the OPC can be viewed using the OPC Event Browser tool.

LogoutThe Logout tool is available only on X-terminal sessions. It is used to log out of the OPC.

NE Login ManagerThe NE Login Manager tool allows the user to log in to any network element within the OPC’s span of control. A VT100 NE User Interface session is initiated. A userID (and password) is required to access the network element. Once logged in, the user may perform all operations supported by the NE User Interface.

Network BrowserThe network browser tool provides status information for each network element in the OPC’s span of control. Alarm, protection, and performance summaries are provided, as well as shelf details such as the shelf serial number, shelf type, and shelf function.

Network SummaryThe Network Summary tool provides a summary of alarms in the OPC’s span of control. Alarm counts for the subnetwork and for each network element are shown. After locating alarms in the subnetwork, the NE Login tool can be used to log in to a specific network element and get a detailed alarm report of each alarm.


OPC features 5-7

Network Upgrade ManagerThe Network Upgrade Manager allows the user to automatically upgrade the software load for all network elements in an OPC’s span of control. Network elements are upgraded according to a user-defined sequence. This tool simplifies the management of software upgrades for the network, during a network upgrade.

OPC Alarm ProvisioningThe OPC Alarm Provisioning tool allows you to enable, disable, and manually clear OPC alarms. As well, the tool allows you to enable and disable an OPC pointer alarm, which indicates that an alarm is active on the associated OPC. The severity of the pointer alarm and the network element on which it is raised can also be provisioned. For alarm-clearing procedures, see Alarm Clearing Procedures, 323-1111-543.

The OPC status line displays the sum of alarm counts for all network elements in a given OPC span of control, as well as the OPC alarm counts.

OPC DateThe OPC keeps track of local and Greenwich Mean Time (GMT), and sets the clock for the subnetwork. Many system events are time-stamped, and each network element receives its time reference from the OPC. The time, time zone, and date are set using the OPC Date tool.

The OPC date tool allows a user to maintain an accurate time of day clock and to provide an automatic time synchronization between the primary and the backup OPCs. It also allows the user to synchronize the primary OPC to an external, more accurate, time server using either Ethernet or DCC protocol, through SONET.

OPC PM Collection FilterThe OPC PM Collection Filter allows maintenance personnel to enable, disable, or query the status of the collection of performance statistics from network elements by the OPC.

Each network element in the OPC span of control collects its own performance-monitoring counts. With the OPC PM Collection Filter enabled, the OPC can collect this data from the network elements every 15 minutes. It can then make the data available for analysis through TL1 to an external operations system. Refer to Performance Monitoring Procedures, 322-1111-520, for more information on performance-monitoring data collection at the OPC.


5-8 OPC features

OPC Save and RestoreThe OPC Save and Restore tool is used to manage backups of OPC configuration, OPC data, and network element database backup files. These backups are stored on tape or cartridge and can be restored in the event of data corruption or OPC replacement.

The save and restore tool can be used to schedule a save-to-tape operation, and to enable or disable a scheduled save-to-tape operation. Once the save-to-tape operation has been scheduled and, if left enabled and if there is a digital data storage (DDS) tape or cartridge in the tape or cartridge drive of the primary OPC, the system data is automatically and continuously saved to tape or cartridge at the scheduled times.

OPC ShutdownWhenever the OPC is to be physically removed from the shelf or powered down, it should first be shut down. If this is not done, OPC database corruption may occur. The OPC Shutdown tool provides a safe means for shutting down the OPC before removal or power loss.

OPC StatusThe OPC status tool displays the current software version running in the OPCs in the span of control, and the current operational status of these OPCs.

OPC SwitchThe OPC Switch tool is used to switch between the primary and backup OPCs, depending on which OPC is active. The tool also can be set to prevent or enable activity switches between the primary and backup OPCs, and to lock or release the backup OPC as inactive.

Password UpdateEach user is assigned both a security level and password. The OPC password update tool allows the user to change the password.

Port ConfigurationThe Port Configuration tool provides a menu-based user interface for configuring the OPC serial ports 1 and 2. OPC port 1 maps to the physical connector labeled OPC port 1 on the OC-12 terminal shelf. OPC port 2 maps to the physical connector labeled OPC port 2.

Protection ManagerThe Protection Manager tool displays a subnetwork view of the protection status and control for all nodes in a selected 1+1 or 1:1 linear system or a TA-1230 Ring. The tool allows the user to initiate or release protection switches and to initiate and schedule the protection exerciser.


OPC features 5-9

Reboot/Load ManagerThe Reboot/Load Manager is used to manage software for each network element (NE) in an OPC’s span of control (subnetwork). This consists of performing software release upgrades and determining which software load should reboot the processor circuit pack in a network element in the event of a failure.

Remote OPC LoginAn X.11 graphical terminal is connected to a subnetwork by way of Ethernet, and OPC-to-OPC login is then performed to interface with the other subnetworks (five subnetworks maximum). The X.11 terminal can then display VT100-type screens of each subnetwork’s alarm summary.

Note: This tool is only available with an X.11 graphical terminal and the Network Management Windows feature.

Remote OPC Software InstallationThe Remote OPC Software Installation tool is used to transfer OPC software loads from the local OPC tape or cartridge drive to the backup OPC disk. This feature, along with the Software Delivery Manager tool, allows for simple management of software upgrades within a subnetwork.

Remote TelemetryThis feature provides the necessary management of TBOS displays and TBOS port for centralized surveillance by way of the serial telemetry. Centralized serial telemetry minimizes the number of wires needed between the monitoring equipment and the network elements.

STPPROV (OPC batch provisioning)The OPC STPPROV tool permits you to provision a series of consecutive STS connections at one time on linear systems. The tool adds connections on a one-to-one basis for each consecutive timeslot and tributary until no more connections can be added. Equipment and facilities do not need to be present to perform batch provisioning. Preprovisioning is therefore supported.

TL1 ConfigurationThrough the TL1 Configuration tool, users configure an X.25 port for TL1 communications, manage TL1 sessions (including querying active sessions or starting a session), configure virtual circuit profiles (which must be defined to support the TL1 protocol), and configure the OC-3 TL1 Router.

TPB Commissioning toolThe TPB Commissioning tool allows users to commission TPB. TPB commissioning information is used to map incoming OPTera Metro 3000 series MOA connection requests for TL1 OAM&P and ESWD applications to


5-10 OPC features

the proper remote OPTera Metro 3000 series Network Processor as well as provide ESWD authentication for a remote Network Processor at the OPC TPB.

Unix ShellThe Unix Shell tool provides the user with access to the Unix application environment. Only users with admin security levels have access to the Unix Shell.

OPC securityThe OPC security feature controls user access to the OPC user interface tools. There are the following OPC security levels or groups. See Technical Specifications, 323-1111-180 for a list of the OPC tools available for each OPC security level or group.

RootUsers with this security level can open any tool and have unlimited UNIX file permissions. This user account has special access privileges and cannot be viewed or modified in the Centralized User Administration tool. As a security precaution, this level should only be used when the required action is beyond the power of any other user account.

StandbyThis user account is responsible for operations on the inactive OPC; it also has special access privileges and cannot be viewed or modified in the Centralized User Administration tool.

AdminUsers with this security level can perform software downloads and network element database backups, as well as basic network surveillance functions. This user account is for administration and maintenance of the network.

NetsurvThe Netsurv level allows users to monitor the network using various network surveillance tools.

SLATAt this level, the tools required for commissioning of a new system and software downloading are available. Basic network surveillance capabilities are also provided.

MasterThis user account is for administration of the OPC.

demoThe demo account provides an on-line tutorial for new users. This userID has access to the Message Alarm Demo OPC training tool.


OPC features 5-11

oc3adminThis user account accesses the OC-3 Load Manager, Event Browser, OC-3 TPB Configuration, and Utilities tools.

techsuppThe techsupp account provides users with access to all toolsets, including user restricted tools.

viewsurvThis user account is responsible for network surveillance in view-only mode. Protection-switching functions cannot be performed in the OPC tools accessed from this account. However, protection status can be viewed.


5-12 OPC features


SONET Transmission Products

S/DMS TransportNodeOC-3/OC-12 NE—TBMSoftware Description

Copyright 1992–2001 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks and S/DMS TransportNode are trademarks of Nortel Networks. VT100 is a trademark of Digital Equipment Corporation. UNIX is a trademark of X/Open Company Ltd.

323-1111-101Rel 14 StandardFebruary 2001Printed in Canada

sonet transmission products s/dms transportnode …npatrick/nortel-sdms-docs/n3rlz7xm.pdf ·...

Documents