Nortel INM 4.1 Technical manual

Planning Guide PG OC 98-13
*NTRS10HB.0120*
Integrated Network Management Products
Integrated Network Management
Broadband Release 4.1
Planning Guide
Document release: Issue 1.2
Date: February 1999

Planning Guide PG OC 98-13 Issue 1.2
Integrated Network Management Products
Integrated Network Management
Broadband Release 4.1
Planning Guide
1999 Northern Telecom
All rights reserved
Ethernet is a trademark of Xerox Corporation.
HP is a trademark of Hewlett-Packard Co.
NCD is a trademark of Network Computing Devices
S/DMS AccessNode is a trademark of Northern Telecom.
S/DMS TransportNode is a trademark of Northern Telecom.
Tektronix is a trademark of Tektronix Corporation.
UNIX is a registered trademark of UNIX System Laboratories, Inc.
VT100 is a trademark of Digital Equipment Corporation of Maynard, Mass.
X Window System is a trademark of the Massachusetts Institute of Technology.
Planning Guide Number: PG OC 98-13
Document status: Issue 1.2
Date: February 1999

iv of 202
Integrated Network Management Broadband Release 4.1 PG OC 98-13 Issue 1.2
Publication history
February 1999
1.2 (Caroline Samson)
- Official release for INM 4.1 General Availability, updated to include minor
changes.
November 1998
1.1 (Caroline Samson)
- Official release for INM 4.1 General Availability, updated to include
additional information in the INM Broadband Release 4.1 Requirements and
Ordering Information sections.
November 1998
1.0 (Caroline Samson)
- Official release for INM 4.1 General Availability.

Table of Contents v of 202
INM Broadband Release 4.1 PG OC 98-13 Issue 1.2
Table of Contents
About this document 9
Common Object Request Broker Architecture 10
An Overview 10
Application structure and principles of CORBA 11
Summary of new features 12
Audience 25
Integrated Network Management Broadband Description 27
Migration to CORBA 28
INM Release 4.1 Software Units capabilities 29
Connection Management Building Block 30
Fault Management Building Block 30
Resource Management Building Block 30
Performance Management Building Block 31
Application Management 31
Graphical User Interface and the SONET MOA 31
INM 4.1 New Feature Description 39
New GUI Applications 42
Linear Traffic and Protection Status Display (including 4 Fiber Ring) 42
Protection Control 44
PM Threshold Provisioning 46
Drop and Continue on Protection (DCP) 49
Scalability Enhancements 54
Alarm List GUI Enhancements 56
Snap Grid enhancement 60
Centralized Alarm Printing 61
Trouble Ticketing 63
Contract Interfaces Feature Overview 66
Fault Management Building Block (FMBB) 66
Resource Management Building Block (RMBB) 69
Performance Management Building Block (PMBB) 73
Connection Management Building Block (CMBB) 78
Support for new Network Elements 81
Support for the Passport ATM switch 81
Support for INM NETWORKS switches 81
Support for OC-192 82
Support for the Express CX Release 1.0 and 1.1 and the OC-3 Express Release
3.1 and 4.0 91

vi of 202 Table of Contents
INM Broadband Release 4.1 PG OC 98-13 Issue 1.2
Support for the JungleMUX Network element 96
Support for AccessNode and Accessnode Express NE 97
INM Broadband Historical Overview 101
Federated Networks 101
Fault Management 102
High-Speed Traffic Display for OC-12/48 BLSRs 104
Centralized Performance Monitoring 105
Centralized Software Management 107
Centralized Inventory Collection 108
User Interface Enhancements 109
Supported products 111
INM Security Access 113
Customer Network Management 113
Controller, NPC and NE Login Access 113
Additional INM User Support 114
Integrated Network Management Broadband Compatibilities 115
Building Block Compatibilities 144
Bridging 145
INM Broadband Release 4.1 Engineering Considerations 147
INM Engineering Rules 147
INM Engineering Capacities 147
X Terminals Engineering Capacities 152
INM Bandwidth Consumption 152
Bandwidth between Indirect Clients and Indirect Servers 153
Building Block considerations 155
Generic Requirements for CORBA applications 155
CORBA Gateway 156
SONET MOA 157
SONET_MOA_PSC 158
Building Blocks 158
INM Broadband Release 4.1 Requirements 163
Hardware Requirements 163
Hardware restrictions/limitations 166
INM mixed federations limitations note 166
Operating System Requirements 166
Upgrades 168
Installation summary 169
First-time installation 169
Upgrade 170
Workstation setup summary 172
Screen saver 172
Swap space 172
Disk Partition requirements 172
X Terminals 174
Hardware 174

Table of Contents vii of 202
INM Broadband Release 4.1 PG OC 98-13 Issue 1.2
Operating System Parameters 174
Northern Telecom Software Requirements 175
TCP/IP Network Requirements 177
Ethernet 177
TCP/IP 178
LAN requirements 178
X.25 179
WAN requirements 180
Summary 181
Ordering Information 183
INM Broadband Software Ordering 184
INM Broadband Documentation Ordering 187
INM Broadband HP Workstation & X Terminal Ordering 193
List of Terms 195
Appendix 1:
Technical support and information 199
INM Customer Care: How to reach us 199
Critical Issues 199
Product Warranty 200
INM Product Services 200

viii of 202 Table of Contents
INM Broadband Release 4.1 PG OC 98-13 Issue 1.2

INM Broadband 4.1 Planning Guide PG OC 98-13 Issue 1.2
9of202
About this document
This document describes the Integrated Network Management (INM)
Broadband Release 4.1 application which provides centralized management
across multiple controller subnetworks. INM Broadband Release 4.1 provides
a common network management framework which includes a common
hardwareandsoftwareplatform for allapplications,a GraphicalUser Interface
(GUI) for day-to-day operations, and open Applications Programming
Interfaces (APIs) to facilitate customization and adaptation for a wide variety
of broadband network elements.
INM Broadband Release 4.1 combines the functionality of the previous Nortel
network management graphical user interfaces provided by the S/DMS
Network Manager or INM Broadband products with the Information
Networking Architecture (INA) Transport product, which provided open
interfaces based on the HP DPE technology.
In INM Broadband Release 4.1, all existing HP DPE APIs are replaced with
CORBA APIs, thereby migrating to a new and open standards based
architecture. Beginning with INM Broadband Release 4.1, CORBA becomes
the technology of choice for distributed network management applications.
INM Broadband Release 4.1 is the first release of Integrated Network
Management targeted at both the SONET Broadband and ATM marketplaces.
It extends the graphical network management functionality offered in previous
releases of Network Manager/INM, and combines it with CORBA APIs to
form one single product offering.
The INM Broadband Release 4.1 product portfolio has the following
characteristics:
• It is a suite of software applications deployed on Hewlett-Packard 700
Series workstations.
• It contains open, standards-based Common Object Request Broker
Architecture (CORBA) interfaces to manage Nortel and non-Nortel
network elements.
• It provides graphical user interfaces for centralized network management.

10 of 202 About this document
Integrated Network Management Broadband Release 4.1 PG OC 98-13 Issue 1.2
INM not only provides for surveillance but also provides for provisioning,
performance monitoring, shelf level graphics, protection control, centralized
software management, and inventory collection. INM provides a single point
of operational access for multiple S/DMS TransportNode OC-3/12/48/192
subnetworks, S/DMS AccessNode, SONET Radio, DV-45, Tellabs Titan 5500
Digital Cross-Connect systems (DCS), OC-3 Express, JungleMUX, INM
NETWORKS NEs as well as Nortel ATM Passport Network Elements and
potentially other network elements through a graphical consolidated view
which may encompass thousands of widely separated individual Network
Elements (NEs).
Common Object Request Broker Architecture
An Overview
Common Object Request Broker Architecture (CORBA) is a multi-vendor
standard for object-oriented distributed computing. CORBA technology is
based on specifications defined by the Object Management Group (OMG)
which is a consortium of computing involved companies. The OMG is an
international organization of over 600 members, and includes all of the major
vendors of systems and software from around the world, as well as
independent software vendors, large and small consulting companies, and an
increasing number of end user companies.
The OMG only produces specifications and not software. The specifications
are freely available for any company to implement. An implementation of
CORBA is referred to as an ORB (Object Request Broker). There are many
ORBs in the marketplace today, Nortel has chosen Orbix, from Iona
Technologies as its distributed middleware CORBA technology to provide the
capabilities to develop distributed applications around its INM Broadband
Release 4.1 product.
Rapidly changing technologies, increased complexity and need for
responsiveness to customer needs have led telecommunication service
providers such as Nortel to explore new and novel methods for deploying new
telecommunications systems and networks. As a result, the telephony world
has devoted a significant amount of time developing architectures such as
Telecommunications Management Network (TMN).
Concurrent with efforts made in the telecommunication world, the computing
world has been developing and refining concepts, architectures and platforms
such as OMG CORBA that enable software modules to cooperate and
communicate transparently across different implementations of operating
system, hardware and networks.

About this document 11 of 202
INM Broadband 4.1 Planning Guide PG OC 98-13 Issue 1.2
Inspired by the technological and architectural advances made, the next
generation of OSSs are rapidly evolving toward highly distributed multi-
vendor systems, with open interfaces, and applications that are independent
from the underlying transport technologies. The fundamental driver for this
migration is the need to develop and deploy highly scalable new services in a
rapid and cost-effective manner.
As such, in order to capitalize on the synergistic aspects of the two
architectures (TMN and CORBA), it is highly desirable to employ CORBA
services in a rapid and cost-effective manner to provide TMN compliant
applications that offer open and standard compliant interfaces.
Application structure and principles of CORBA
Networkmanagementapplicationsare distributedapplications. IntheCORBA
architecture, which is based on object-orientation methodology, a distributed
application is composed of objects that interact with each other. In general an
object is an abstraction of a resource, concept, or functionality that provides a
set of capabilities for other objects. In practice a CORBA object is more
viewed as a means to model an application entity. More precisely, a CORBA
object is described as “a package of data and code used to implement a
computational construct or to model an application entity”.
To enable other objects to access its capabilities, a CORBA object offers a
single interface, however the interface may inherit from other interfaces. Each
interface defines a set of operations (function calls) that can be invoked via the
interface.
The object that provides the interface is called the object implementation in
CORBA, and the object that invokes operations defined in the interface is
called a client. The terms “Client” and “Server” are used frequently in Corba
to describe the Peer-Peer relationship that exists between the two entities.
Servers contain one or more objects, and are often physically represented as
processes. Objects, not servers are invokable. An object in a server can be
invoked by a client, and this object can use the facilities of other objects in the
system. A CORBA server/executable which groups several CORBA objects
providing services in an application domain may be termed as a “building
block”.
An object’s interface is defined in OMG’s Interface Definition Language
(IDL). IDL is not a programming language. An IDL only defines interfaces,
where each interface definition lists the operations that can be applied to
objects with that interface. In other words, the IDL interface specifies all of the
operationsthe objectisgoing toperform,their inputandoutput parametersand
return values, and every exception that may be generated.

12 of 202 About this document
Integrated Network Management Broadband Release 4.1 PG OC 98-13 Issue 1.2
The IDL interface constitutes a contract with the clients, and is the key to
interworkingacrossnetworks,operatingsystemsandprogramming languages.
In CORBA, programmers tasked with developing client software require
knowledge about the IDL interface definition and the description of what the
object does in order to begin invoking operations on it.
The infrastructure for communication amongst objects in a distributed
environment is provided by middleware as CORBA ORB.
To illustrate the concepts presented in this section Figure 1 on page 12 shows
a simplified overview of a request passing from the client to the object
implementation in the CORBA architecture.
Figure 1. Passing a request from a client to object implementation
The IDL definition completely defines the server interface, but since it is an
abstract language, it does not provide the detailed data structures and function
calls that a programmer must make. To get this information, CORBA also
defines what is known as language mappings. This mapping of IDL to actual
language definitions is done using an IDL compiler.
Putting an IDL through an IDL compiler will generate the required code for
the particular language chosen. For a C++ mapping, the IDL compiler will
output a header file and a client stub. The header file is included in the client
application and the client stub is compiled and linked with the final product.
Summary of new features
The new features offered by the Integrated Network Management Broadband
Release 4.1 applications are summarized below.
• Protection Status and Control GUI and Contract Interfaces (CI) which
provide GUI enhancements to support protection status display and
protection control for OC3/OC12 TBM and OC-48 linear systems (1:1,
1+1, 1:N), 2 fiber-ring systems (OC12 TBM and OC-48 BLSR), as well as
OC-192 4-fiber rings. Protection control will provide the ability to issue
high speed protection control and lockout commands from the Graphical
CLIENT OBJECT
IMPLEMENTATION
IDL
Stub IDL
Skeleton
Request
Object Request Broker (ORB)

About this document 13 of 202
INM Broadband 4.1 Planning Guide PG OC 98-13 Issue 1.2
Network Browser. This feature will also provide the open, standards-based
Contract Interfaces using the CORBA Interface Definition Language
(IDL) to perform high speed protection switch control on the topologies
mentioned above.
•Linear Systems Traffic Display which provides GUI enhancements to
support the traffic display for OC3/OC12 TBM and OC-48 linear systems
(1:1, 1+1, 1:N).
•OC-48 Release 14.1 support (Connection Management Interface
Enhancements) which provides enhancements to the Connection
Management Building Block (CMBB) Contract Interface (CI) to support
connection provisioning of concatenated STS-3c and STS-12c
bidirectional connections on OC-48 BLSR systems. Enhancements to
termination inventory and information services are also provided in order
to support OC-3 tributary cards on OC-48 Ring (BLSR) systems.
• Drop and Continue on Protection (DCP) GUI and Contract Interface
provides support for the new DCP provisioning scheme to be used when
provisioning unidirectional or bidirectional matched node connections on
OC-12TBM andOC-48BLSR systems.Enhancementsto theGUI support
the selection of either the Drop and Continue on Working (DCW) or the
Drop and Continue on Protection (DCP) provisioning scheme for creating
bidirectional or unidirectional matched node connections. As well, the
editing of an existing unidirectional or bidirectional matched node
connection from the DCW to the DCP scheme and vice versa is supported.
Enhancements to the Connection Management Building Block (CMBB)
Contract Interface (CI) provide the same DCP provisioning and editing
capabilities through the open, standards based CI using the CORBA
Interface Definition Language (IDL).
• OC3 Express Data Release 3.1 Contract Interfaces Support for Fault
Management, Performance Monitoring, Resource Management. The
supportfor thenew EIMcard isprovidedonlythrough theINMBroadband
GUI.
•OC192 Release 4 GUI and Contract Interfaces Support for Fault
Management, Remote Inventory (including Shelf Level Graphics),
Performance Monitoring and Connection Management (for 4 fiber BLSR
systems).
•Facility Provisioning Contract Interface Enhancements which support
additional attributes and additional facilities. This includes the support for
optical facilities (OC3, OC12, OC48) and electrical facilities (DS1, DS3,
STS1, STS3, STS12 and STS48 on OC3/OC12 TBM and OC48 Network
Elements.
•PM Threshold Provisioning GUI and Contract Interfaces Support where
threshold values for individual PM parameters can be set or queried for
DS1, DS3, STS1 and OCn facilities for OC3 TBM (LTE, linear ADM),
OC12 (LTE, linear ADM, ring ADM, Regen) and OC48 (LTE, ring ADM,

14 of 202 About this document
Integrated Network Management Broadband Release 4.1 PG OC 98-13 Issue 1.2
Regen) systems. This includes the ability to set up to two threshold values
for each PM on each facility.
•GUI Enhancements will be provided to the Alarm Dialog which will be
enhanced to permit resizing of the Dialog itself as well as different parts of
it. In addition, new GUI technology will allow the rearranging, removing,
and restoring of columns.
•Web User Interface for OC192 Support provides the user to login to the
OC-192 Network Element (which supports the Web UI) and use the new
Web Based NE User Interface that is being introduced in the
TransportNode OC-192 Release 5.0.
• Resource Management Contract Interfaces provide the equivalent support
and functionality existing in the INA Transport Release 2.0 by replacing
the Configuration INA DPE Contract Interfaces with the CORBA Contract
Interfaces (CI). The CORBA CIs will provide functionality for Network
Element discovery/query, equipment inventory query, as well as Facility
provisioning for OC3/OC12 TBM and OC48 systems.
• Integrated Fault Management provides integrated support for fault
information across multi-domain, multi-vendor networks. The Fault
Management Building Block (FMBB) provides open, standards based
contract interfaces using CORBA IDL supporting alarm query, alarm
notification, alarm count and event notification functionality, as well as
protection status and control.
•Express CX GUI Support of Fault Management, Performance Monitoring,
Remote Inventory, Electronic Software Delivery, Remote Login, Shelf
Level Graphics and Connection Management. The support for the Express
CXNetwork Element isprovidedthrough theOC-3 ExpressMOARelease
3.1.
•PC GUI Remote Login support (JungleMUX JNCI, OC-3 Express, and
AccessNode Express Voice Module) allows an INM Broadband user to
perform a remote login Reach-Through to the PC-GUI application running
on a Windows NT Server machine and running an Element Manager
application.
•AccessNodeExpress DataModule Supportfor NodeGraphics, ShelfLevel
Graphics as well as Remote Login.
• Scalability Enhancements for Contract Interfaces extends the engineering
limits introduced in the INM 3.1 to the new Contract Interfaces.
•Centralized Alarm Printing offers the capability to output the alarm
information (severity, reason, network element,...) for the raised and the
cleared alarms: if the Centralized Alarm Printing functionality is enabled,
all raising and all clearing alarms are printed out, in real time, as they
occur.

About this document 15 of 202
INM Broadband 4.1 Planning Guide PG OC 98-13 Issue 1.2
• Trouble Ticketing offers the capability to select a fault from the Alarm
Details dialog of the Graphical Network Browser, and generate a
corresponding Trouble Ticket in Clarify’s ClearSupportTM product.
These new features offered with the Integrated Network Management
Broadband Release 4.1 build upon the features offered with earlier releases to
provide both new and enhanced capabilities.
Features offered with earlier releases of the S/DMS Network Manager/INM
are summarized below.
Fault Management
• Problem Analyzer (PA) performs Intelligent Alarm Filtering (IAF) which
provides the correlation of alarms into direct detect and related alarm
events into a single Network Problem Report. The PA provides additional
information to the user by showing the alarm correlation, viewing
problems not alarms, giving probable cause, providing a NTP reference to
fix the problem, and performing preventive analysis. This feature is
optional and is delivered on a separate CD-ROM/DAT Tape.
•Alarm History and Enhanced Audit Trail for S/DMS OC-3/12/48, and
S/DMS OC-192. The Alarm History Retrieval option provides the ability
to retrieve historical alarm information for the network element from the
graphical user interface. The Enhanced Audit Trail (EAT) provides the
capability to record the alarm information of raised, acknowledged and
cleared alarms.
•NE Alarm Report Suspension offers the ability to suspend and resume
alarm reporting on an Network Element basis, in addition to the existing
alarm control mechanism available for element controllers (spans). These
two functions are complementary in nature and may be used together for
any subset of network elements being monitored by INM.
•External Alarm Control offers the ability to operate external devices and
relays via the serial port on the INM based on incoming alarm information.
Functionality to filter alarms based on element controllers and alarm
severity is provided through this UI enhancement. Alarms passing the
filter will cause simple configurable text strings to be sent to an external
device for post-processing, and as such special hardware is required in
conjunction with the INM platform in order to utilize this feature.
•First alert alarm banner displays a summary of all alarm counts in the
S/DMS TransportNode and S/DMS AccessNode network, notifying users
of any condition changes in the entire network monitored by the S/DMS
Network Manager.
•Real-Time/Snapshot Alarm Detail Display provides a dialog that updates
in real-time, as alarms are raised or cleared. The alarm display dialog lists
a one line summary of the active alarm conditions on a group of NEs or on

16 of 202 About this document
Integrated Network Management Broadband Release 4.1 PG OC 98-13 Issue 1.2
a single NE, thereby reducing the number of logins to the NE(s) to view
active alarms.
Connection Management
•Virtual Tributary Bandwidth Management (VTBM) support for OC-12
BLSR systems within TransportNode and AccessNode, enabling users to
provision a VT1.5 connection on a ring using a graphical point-and-click
interface, where the path is auto configured and only the endpoints need to
be specified.
•Connection Management for Linear Systems provides support for specific
linear system types, namely; OC-48 linear 1+1, linear 1:1 (single shelf),
linear unprotected (0:1), as well as OC-12 linear 1+1, and linear ADM
chain. A user is able to provision STS connections on a linear system using
a graphical point-and-click interface, and graphically display the
established connections. Service assurance capabilities providing the
ability to gather information about provisioned bandwidth and service
access points are also available for linear systems.
•OC-12 TBM Mux Provisioning provides support for STS connection
provisioning on OC-12 TBM mux subtending off an OC-48 NE.
•Service Assurance provides information about provisioned connections
within a selected BLSR network entity. For traffic restoration purposes,
service assurance will permit users to obtain a summary of the connections
affected by a link or nodal failure. Service assurance also monitors
bandwidth utilization.
•BLSR STS Connection Provisioning offers a graphical point-and-click
interface for provisioning connections on ring systems. Connection
provisioning provides an end-to-end specification and auto selection of
intermediate nodes for each ring system to facilitate user interaction. A
user can provision connections on OC-48 and OC-12 BLSRs to support
matched nodes, bidirectional, unidirectional (OC-48) and extra-traffic
(OC-48) services.
Performance Management
•Centralized Performance Monitoring enables early detection of signal
degradation within a network. Centralized performance monitoring
provides error and switch statistics to permit preventive maintenance prior
to service failures.
Configuration Management
•Partitioned Access support which allows the graphical view of the network
to be divided into several sub-views which may contain any or all of the

About this document 17 of 202
INM Broadband 4.1 Planning Guide PG OC 98-13 Issue 1.2
network elements in the network. These views can be configured to permit
some or all management functions to be enabled for the user.
•Facility Parameter Provisioning which extends the Tributary Facility State
Provisioning feature first introduced in the S/DMS Network Manager
Release 6.01 to include optical facilities (OC3, OC12, OC48) in addition
to electrical facilities (DS1, DS3, STS1). The user will be capable of
provisioning the parameters supported by each type of facility.
•Tributary Facility State Provisioning offers the capability to change the
state of a facility provisioned on an NE within TransportNode and
AccessNode systems. In the case of TransportNode, DS1, DS3, and STS1
tributary facilities may be activated by putting them in-service (IS) or
deactivated by putting them out-of-service (OOS). Similarly for
AccessNode systems, DS1,DS3, and TIC tributary facilities can be put IS
or OOS. These actions are initiated directly from the tributary usage dialog
of the Connection Manager tool.
•Nested Groups providing users the ability to nest groups within each other,
in any number of nesting levels, thereby removing the one level nesting
limitation in previous releases. Users may create groups inside any other
group or move the group from its existing group to any other group.
•Flexible Groups providing users the ability to customize the appearance of
a group, where groups can have any polygon shape, and in conjunction
with the Nested Groups feature, may contain any number of network
elements and/or other groups. Flexible Groups provide users a powerful
visualization tool whereby users can graphically display system-level
network components (e.g. ring systems, linear systems, and geographic
regions).
•Centralized Inventory Collection provides an accurate view of the
equipment provisioned in the network. The centralized inventory
collection feature can generate reports to facilitate upgrades, provisioning
and accounting activities.
•NE Shelf Level Graphics provides a graphical view of the inventory
information for a specified Network Element. NE shelf level graphics
improves communication between craft personnel, located in different
remote sites, when referring to shelf level details.
Specific Products Support
•OC-192 Performance Monitoring, Inventory, and Fault Management
support for Release 2.1/3.0. A new PM category; Intermediate Path is
added to the PM statistics display to enable a user to query STS path PMs
for OC-192. Inventory queries to OC-192 NEs are also supported for all
new cards which occupy existing shelves and for the new extension
shelves. In addition, alarms which occur on all new circuit packs
introduced in OC-192 Release 3.0 release are supported.

18 of 202 About this document
Integrated Network Management Broadband Release 4.1 PG OC 98-13 Issue 1.2
•S/DMS AccessNode Support offers the capability to have INM provide
real-time shelf level alarms for CDS and ABM shelves.
•AccessNode Express (ANX) Fault Management and Shelf Level View
support is provided. All severities of alarms (warning, minor, major,
critical)raisedagainst ANXequipmentare reportedonthe ANXnodesand
are included in summary alarm counts for groups containing ANX nodes
as well as in the GNB alarm banner. The shelf level graphics feature
permits the user to view the layout of the shelf as well as the cards installed
in the shelf and view which circuit packs or equipment have alarms raised
against them.
•OC-3 Express Connection Management, Performance Monitoring and
Remote Inventory (including Shelf Level Graphics) is supported. Nodal
connection management for OC-3 Express NEs for functionalities such as
Time Slot Assignment (TSA), Time Slot Interchange (TSI), Hairpinning,
Path switched connections and Drop-and-Continue and Broadcast is
provided. Remote Inventory, Shelf Level Graphics and Performance
Monitoring are supported with functionalities similar to that provided for
other types of NEs.
•DV45 Fault Management offers the capability to have INM in conjunction
with the MOA software load provide fault management for the DV45
Video Codec with respect to first alert, alarm counts and alarm details. For
full feature description on the DV45 MOA please refer to Planning Guide
PG 95-11.
•Tellabs Titan 5500 Digital Cross-Connect (DCS) Support offers the
capability to have INM in conjunction with the MOA to provide fault
management as well as remote login for the Tellabs Titan 5500 digital
cross-connect systems. Fault Management capabilities include first alert,
alarm counts, and alarm details. For full feature description on the DV-45
MOA please refer to Planning Guide PG 95-11.
General/Generic features
•Federated Networks support which provides the ability to manage a
network of up to 10,000 network elements and 750 controller (OPC/MOA)
pairs in a scalable environment by distributing the resources and data
required for the network across a number of communicating INM
workstations.
—Global Alarm Acknowledgment in a scalable environment provides an
unconditional propagation of alarm acknowledgment to all INM
workstations managing OPCs and MOAs that support alarm
surveillance functionality.
•On-line help which uses a World Wide Web (WWW) oriented method and
which provides the capability to access the INM documentation from

About this document 19 of 202
INM Broadband 4.1 Planning Guide PG OC 98-13 Issue 1.2
within the graphical user interface. Help information is available in HTML
format, to permit access with a WWW browser.
•Printing support which enables the user to print lists or text areas within a
window. The user can also print the whole graphical window screen
containing the graphical information to a postscript printer or to save the
image in a postscript file in a user definable directory. The texts and lists
are saved in a text format, which can be viewed by a text editor or printed.
Printing can be done in color or black & white (grey scale), depending on
the printer’s capabilities.
•OC-12/48 Bidirectional Line Switched Rings(BLSR) Traffic Display
displays both high speed traffic and protection status. With a graphical
view of the high speed traffic condition, users have an immediate
understanding of the BLSR condition without having to log into multiple
NEs.
•Centralized Software Management furnishes a central distribution facility
for the electronic delivery of a OPerations Controller (OPC) and NE
software throughout the network.
•OPCGraphicalUserInterface AccessforbothS/DMS TransportNodeand
S/DMS AccessNode OPCs, accessible from the local S/DMS Network
Manager.
•Direct OPC/NE login access to individual OPCs and network elements.

20 of 202 About this document
Integrated Network Management Broadband Release 4.1 PG OC 98-13 Issue 1.2
The INM Broadband Release 4.1 and earlier releases are summarized in the
table below. The items in bold represent new features offered with that release.
Table 1. INM Broadband Features
Features S/DMS Network Manager
Release 5.01
S/DMS Network
Manager
Release 6.01 INM Broadband Release 3.1 INM Broadband Release 4.1
Hardware
Platform
Supported
HP 9000 Model
7151/7355/
Model C100
HP 9000 Model
7151/7355/C100/C110 HP 9000 Model 7151/7355/C100/C110/C2
00
HP B-Series Model
132L+
HP 9000 Model
7151/7355/C100/C110/C2
00
HP B-Series Model 132L+
UNIXTM OS HP-UX 9.05 HP-UX 9.05/10.10 HP-UX 10.10/10.20 HP-UX 10.20 ACE 2
(June 1998) on C200 and
HP-UX 10.20 ACE 1 (July
1997) on the other plat-
forms.
HP-VUE HP VUE 3.0 HP VUE 3.0 HP VUE 3.0 HP VUE 3.0
Product
Support2•S/DMS TransportNode
•SONET Radio
•S/DMS AccessNode
•S/DMS TransportNode
•SONET Radio
•S/DMS AccessNode
•S/DMS OC-192
•Nortel DV45
•Tellabs Titan 5500 Digi-
talCross-ConnectSystem
(DCS)
•OC-3 Express6
•S/DMS TransportNode
•SONET Radio
•S/DMS AccessNode
•S/DMS OC-192
•Nortel DV45
•Tellabs Titan 5500Digital
Cross-Connect System
(DCS)
•OC-3 Express6
•AccessNode Express
(ANX)
•S/DMS TransportNode
•SONET Radio
•S/DMS AccessNode
•S/DMS OC-192
•Nortel DV45
•Tellabs Titan 5500Digital
Cross-Connect System
(DCS)
•OC-3 Express10
•AccessNode Express
(ANX)
• OC-192 Release 4.0 and
5.0
• Express Data Release
3.1 and 4.011
• Express CX Release 1.0
and 1.111
• Passport ATM12
• JungleMux13
• INM NETWORKS
switches14