Ericsson LBI-39169 User Manual
User’s Guide
EDACS NETWORK
MANAGEMENT
LBI-39169
ericssonz
LBI-39169
NOTICE!
This manual covers Ericsson and General Electric products manufactured and sold by
NOTICE!
Ericsson Inc
.
This product may only be used for the functions described in this manual. Use of the product for other purposes shall
constitute a violation of the license. Moreover, any addition of non-Ericsson approved hardware and software may cause the
product to malfunction.
NOTICE!
The software contained in this device is copyrighted by
Ericsson Inc
laws of the United States.
This manual is published by
Ericsson Inc
., without any warranty. Improvements and changes to this manual necessitated by
typographical errors, inaccuracies of current information, or improvements to programs and/or equipment, may be made by
Ericsson Inc
., at any time and without notice. Such changes will be incorporated into new editions of this manual. No part
of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including
photocopying and recording, for any purpose, without the express written permission of
EDACS and MASTR are registered trademarks of
is the registered trademark of UNIX Systems Laboratories in the U.S.A. and other countries.
Unix
TSSterm
is the trademark of Thursby Software System, Inc.
Ericsson Inc
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Digital, DEC, DECnet, DECwindows, VT, VT420, and VMS are trademarks of Digital Equipment Corporation.
is a trademark and Gradient is a resistered trademark of Gradient Technologies, Inc.
FOR
i
The Graphics Interchange Format
is the Copyright property and GIFSM is the Service Mark property of Compuserve
Incorperated.
OSF/Motif is a trademark of the Open Software Foundation.
MultiNet and MultiWare are registered trademarks of TGV, Inc.
. Unpublished rights are reserved under the copyright
Ericsson Inc
.
.
Copyright October 1996, Ericsson, Inc.
2
LBI-39169
TABLE OF CONTENTS
Section/Paragraph Page
1. PREFACE........................................................................................................................................................... 9
1.1 MANUAL ORGANIZATION....................................................................................................................9
2. DOCUMENTATION.........................................................................................................................................11
2.1 HEWLETT-PACKARD DOCUMENTATION..........................................................................................11
2.2 RELATED ERICSSON PUBLICATIONS.................................................................................................11
3. INTRODUCTION.............................................................................................................................................. 13
3.1 FAULT MANAGEMENT..........................................................................................................................14
3.2 CONFIGURATION MANAGEMENT...................................................................................................... 14
3.3 ACCOUNTING MANAGEMENT.............................................................................................................14
3.4 PERFORMANCE MANAGEMENT ......................................................................................................... 15
3.5 SECURITY MANAGEMENT ...................................................................................................................15
3.5.1 Access Levels ................................................................................................................................... 15
3.5.2 System Access .................................................................................................................................. 16
3.6 HIERARCHICAL MAPS........................................................................................................................... 16
3.7 EDACS NM MENUS AND THEIR FUNCTIONALITY.......................................................................... 17
4. NETWORK MANAGER BASICS................................................................................................................... 18
4.1 PULLDOWN MENU SELECTION PROCEDURE USING THE MOUSE.............................................. 18
4.2 PULLDOWN MENU SELECTION PROCEDURE USING THE KEYBOARD ..................................... 18
4.3 EDITOR OPTIONS....................................................................................................................................18
4.4 MAP TRAVERSAL ................................................................................................................................... 19
5. STARTUP PROCEDURES............................................................................................................................... 21
5.1 STARTING A NETWORK MANAGER WORK SESSION.....................................................................21
5.2 ENDING A NETWORK MANAGER WORK SESSION .........................................................................22
5.2.1 LOGGING OUT OF THE NETWORK MANAGER SESSION .....................................................22
5.2.2 LOGGING OUT OF THE HP VUE SESSION................................................................................22
6. RETRIEVING THE SOFTWARE VERSION................................................................................................ 23
6.1 SUBCOMPONENT SOFTWARE VERSIONS......................................................................................... 23
6.2 NETWORK MANAGER SOFTWARE APPLICATION VERSIONS......................................................24
7. EDACS HELP....................................................................................................................................................25
7.1 TASK HELP............................................................................................................................................... 25
7.2 FUNCTION HELP .....................................................................................................................................25
8. MONITORING EDACS FAULT CONDITIONS...........................................................................................26
8.1 DETECTING AND ISOLATING FAULTS (ALARMS) ..........................................................................26
8.1.1 Notification through the Event Notification Interface....................................................................... 26
8.1.2 Notification Through Icon Color ......................................................................................................26
8.1.3 Fault Propagation..............................................................................................................................28
8.2 REPORTING FAULTS (ALARMS).......................................................................................................... 28
8.2.1 Fault Configuration...........................................................................................................................28
8.2.2 Latching Transient Events ................................................................................................................ 29
8.2.3 Associating Actions With Events...................................................................................................... 29
8.2.4 Disabling Events at Remote Agent Devices...................................................................................... 29
8.2.5 UnManaging Devices........................................................................................................................ 30
8.2.6 Managing Devices ............................................................................................................................30
8.2.7 Fault Updating Managed Devices.....................................................................................................30
8.2.8 Setting-up Threshold Oriented Events at RTM Devices...................................................................30
3
LBI-39169
TABLE OF CONTENTS
Section/Paragraph Page
8.3 IDENTIFYING THE CAUSE OF ALARMS.............................................................................................31
8.3.1 Using Hierarchical Maps...................................................................................................................31
8.3.2 Using The OpenView Event Browser...............................................................................................32
9. CONFIGURING EDACS DEVICES................................................................................................................36
9.1 INTEGRATED CEC/IMC MANAGER.....................................................................................................36
9.1.1 Starting The CEC/IMC Session ........................................................................................................37
9.1.2 Sample CEC/IMC Manager Screens.................................................................................................38
9.2 TELNET SESSIONS TO THE PI, BCU, CAL, AND EDG.......................................................................39
9.3 TELNETING TO THE SYSTEM MANAGER..........................................................................................39
9.4 USER ACTION LOGGING .......................................................................................................................41
10. TRANSFERRING DEVICE FILES ...............................................................................................................42
11. MONITORING PERFORMANCE TRENDS...............................................................................................46
11.1 USING TWO-DIMENSIONAL LINE GRAPHS.....................................................................................46
11.1.1 Line Graph Example .......................................................................................................................47
11.1.2 Customizing Line Graphs................................................................................................................47
11.2 TRACKING EDACS DEVICE UTILIZATION.......................................................................................49
11.3 TRACKING EDACS DEVICE ACCESSIBILITY ..................................................................................50
11.4 COMPARING PERFORMANCE FROM MULTIPLE SITES OR NODES............................................51
12. MONITORING REAL-TIME CALL ACTIVITY........................................................................................52
12.1 USING THE MULTISITE MONITOR APPLICATION.........................................................................53
12.1.1 Filtering Call Traffic.......................................................................................................................54
12.1.2 Viewing Call Type Colors...............................................................................................................56
12.1.3 Displaying Site Statistics Rows.......................................................................................................56
12.1.4 Indicating Quiet Drops....................................................................................................................56
12.2 USING THE SITE MONITOR APPLICATION......................................................................................57
12.2.1 Turning On Statistics Rows.............................................................................................................58
12.2.2 Adding The Phone Digits Column..................................................................................................58
12.2.3 Setting The Time Fields..................................................................................................................58
12.2.4 Enabling Quiet Drops......................................................................................................................58
12.2.5 Changing Phone Call Keying Update Parameters...........................................................................58
13. USING OPENVIEW NETWORK NODE MANAGER................................................................................59
13.1 LOADING/UNLOADING MIBS.............................................................................................................59
13.2 VIEWING/GRAPHING PERFORMANCE PARAMETERS..................................................................59
13.3 ADDING CUSTOM MENU ITEMS........................................................................................................59
13.4 COLLECTING AND GRAPHING PERFORMANCE DATA.................................................................59
13.5 THRESHOLD TRAPS ON COLLECTED DATA...................................................................................60
13.6 VIEWING HISTORICAL TRENDS........................................................................................................60
13.7 EVENT HISTORY ...................................................................................................................................60
13.8 CUSTOMIZING EVENT MESSAGES AND ACTIONS........................................................................60
13.9 BACKGROUND GEOGRAPHICAL MAPS...........................................................................................61
13.10 MAP SNAPSHOTS ................................................................................................................................61
13.11 MULTIPLE EDACS NETWORK MANAGER SESSIONS..................................................................62
13.12 INTEGRATION WITH OTHER NETWORK MANAGER APPLICATIONS.....................................62
13.13 CUSTOMIZING ICONS ........................................................................................................................63
13.13.1 Icon Labels....................................................................................................................................63
13.13.2 Object Descriptions.......................................................................................................................63
13.13.3 Icon Bitmaps.................................................................................................................................63
4
LBI-39169
TABLE OF CONTENTS
Section/Paragraph Page
13.14 LOADING MIBS.................................................................................................................................... 63
14. PROCEDURES................................................................................................................................................ 64
14.1 REBOOTING THE NETWORK MANAGER......................................................................................... 64
14.2 SYSTEM SHUTDOWN PROCEDURES................................................................................................ 64
14.3 DEVICE POLLING INTERVAL............................................................................................................. 64
14.3.1 Polling Interval Setup .....................................................................................................................65
14.3.2 Clock Synchronization....................................................................................................................65
14.3.3 Clock Polling Interval.....................................................................................................................65
14.4 MODIFYING EVENT DESCRIPTIONS.................................................................................................65
14.5 ADDING SYMBOLS TO EDACS MAPS............................................................................................... 66
14.6 DELETING SYMBOLS........................................................................................................................... 66
14.7 ADDING A CONNECTION.................................................................................................................... 66
14.8 CUSTOMIZING MSM/SM SITE/DEVICE LABELS............................................................................. 67
14.9 ADDING DESCRIPTIONS TO OBJECTS..............................................................................................68
14.10 DELETING ORPHANED SUBMAPS................................................................................................... 68
14.11 VERIFYING AN OBJECT WAS DELETED FROM THE OPENVIEW DATABASE.......................68
14.12 VIEWING/MODIFYING EDACS IDENTIFIERS................................................................................ 69
14.13 VIEWING/MODIFYING TRAP SEVERITY LEVELS........................................................................ 69
14.14 MODIFYING EVENT DESCRIPTIONS...............................................................................................69
14.15 RESTORING DEFAULT EVENT DESCRIPTIONS............................................................................ 70
14.16 MAPPING SEVERITY LEVEL TO ICON COLOR .............................................................................70
14.17 CREATING A FULL SYSTEM IMAGE BACKUP.............................................................................. 70
14.18 RESTORING A FULL SYSTEM IMAGE FROM THE BACKUP....................................................... 71
15. TROUBLESHOOTING...................................................................................................................................72
15.1 CD-ROM DOES NOT WORK.................................................................................................................72
15.2 MSM/SM DOES NOT SHOW PI TRAFFIC........................................................................................... 72
15.3 ATTEMPT TO LOG IN FAILS ...............................................................................................................72
15.4 EDACS ICON IS BLUE...........................................................................................................................73
15.5 EDACS ICON IS BROWN ......................................................................................................................73
15.6 RPC FAILURES.......................................................................................................................................73
15.7 MAP GENERATION VERIFY OPERATION IS NOT WORKING PROPERLY .................................73
15.8 POPUP STATES NO NODE LICENSE ..................................................................................................74
15.9 PERFORMANCE NOT SHOWING TRAFFIC.......................................................................................74
15.10 POOR SYSTEM PERFORMANCE.......................................................................................................74
15.11 APPLICATION DOES NOT RESPOND TO VERIFICATION REQUEST WHEN ADDING ICON. 75
15.12 IFOR/LS CONFUSED............................................................................................................................ 75
15.13 SYSTEM MANAGER SNMP “SETS” FAILING .................................................................................75
15.14 IMC DETECTED LINK FAILURES.....................................................................................................76
15.15 MSM/SM OUT OF COLOR MAP ENTRIES........................................................................................ 76
15.16 POPUP WARNING................................................................................................................................ 77
15.17 MULTINODE TRAFFIC NOT SEEN CORRECTLY ON MSM SESSIONS....................................... 77
16. GLOSSARY...................................................................................................................................................... 78
17. INDEX............................................................................................................................................................... 88
5
LBI-39169
LIST OF FIGURES AND TABLES
Figure Title Page
Figure 1 - EDACS Menu on Main Menu Bar...........................................................................................................17
Figure 2 - Example of Map Traversal.......................................................................................................................19
Figure 3 - Example of Exploding a Switching Center and Site Icon ........................................................................20
Figure 4 - Network Manager Login Dialog Box.......................................................................................................21
Figure 5 - Network Manager Login Dialog Box.......................................................................................................21
Figure 6 - Software Version Screen Example...........................................................................................................23
Figure 7 - EDACS Help Menu .................................................................................................................................25
Figure 8 - Event Category Window..........................................................................................................................26
Figure 9 - Event Configuration.................................................................................................................................29
Figure 10 - Using Hierarchical Maps to Identify Fault Events.................................................................................31
Figure 11 - EDACS Fault Menu...............................................................................................................................32
Figure 12 - EDACS Event Browser Example...........................................................................................................33
Figure 13 - Event Description ..................................................................................................................................34
Figure 14 - CEC/IMC Client-Server Paradigm ........................................................................................................36
Figure 15 - EDACS Configuration Menu.................................................................................................................36
Figure 16 - CEC/IMC Manager Main Window and Menu Bar................................................................................37
Figure 17 - CEC/IMC Manager Login .....................................................................................................................37
Figure 18 - System Options for Digital Console Pre-empt Example Screen ............................................................38
Figure 19 - Site Channel Configuration Example Screen.........................................................................................38
Figure 20 - Console User Profile Configuration Example Screen............................................................................39
Figure 21 - System Manager Login Screen ..............................................................................................................40
Figure 22 - System Manager User Menu..................................................................................................................40
Figure 23 - Transferring PI Activity Data Using FTP..............................................................................................43
Figure 24 - Transferring a BCU Billing Record Using FTP.....................................................................................44
Figure 25 - Transferring System Manager Activity Data Using FTP.......................................................................45
Figure 26 - Example of a 2-Dimensional Line Graph...............................................................................................47
Figure 27 - EDACS Performance -> Utilization Menu ............................................................................................49
Figure 28 - EDACS Performance / Accessibility Menu...........................................................................................50
Figure 29 - EDACS Performance -> Compare Menu...............................................................................................51
Figure 30 - EDACS Performance -> Monitor Menu ................................................................................................52
Figure 31 - Multisite Monitor Display Example.......................................................................................................53
Figure 32 - Multisite Monitor Menu Bar..................................................................................................................54
6
LBI-39169
LIST OF FIGURES AND TABLES
Figure Title Page
Figure 33 - Traffic Filter Window............................................................................................................................55
Figure 34 - Multisite Monitor Legend......................................................................................................................56
Figure 35 - Site Monitor Display Example ..............................................................................................................57
Figure 36 - Site Monitor Menu Bar..........................................................................................................................58
Figure 37 - Modify Event Screen.............................................................................................................................60
Table 1 - Status Colors/Levels.................................................................................................................................27
Table 2 - Event Naming Convention Prefix.............................................................................................................33
7
LBI-39169
This page intentionally left blank
8
PREFACE LBI-39169
1. PREFACE
This is one of four manuals for the EDACS Network Manager. This manual pr ovides operating instructio ns for users
and administrators of the Network Manager system.
Additional documentation for the Network Manager is available in the following publications:
•
EDACS Network Management System Manual (LBI-39215):
This manual provides a system level overview of EDACS Network Management.
•
EDACS Network Management Enterprise Management Information Base (MIB) Reference Manual (LBI-39170):
This manual contains the EDACS common MIBs and defines each item identified within the MIB groups.
•
EDACS Network Management Installation Manual (LBI-39171):
This manual contains detailed information for installing, configuring, and customizing the Network Manager
application and the EDACS SNMP Agent platforms.
1.1 MANUAL ORGANIZATION
The manual is divided into the following sections:
Section 1 Preface
and introduces the reader to the organization of this manual.
Section 2 Documentation
elements which might interface with the Network Manager. It also provides a list of manual and
documents which may be obtained (or are provided) by vendors and outside sources.
Section 3 Introduction
and features.
Section 4 Network Manager Basics
use when running the Network Manager application.
Section 5 Startup Procedures
Network Manager application.
Section 6 Retrieving Software Version
revision levels of software running on the Network Manager platform and associated devices.
Section 7 EDACS Help
Section 8 Monitoring EDACS Fault Conditions
Network Manager to detect, isolate, and report alarm or fault conditions associated with the
various Network Elements.
Section 9 Configuring EDACS Devices
devices directly connected to the Network Manager, such as CEC/IMC Manager for Windows
NT and the System Manager.
- The preface section identifies the other manuals in the Network Manager manual set
- This section provides a list of Ericsson documents for the associated EDACS
- This section provides an overview of the Network Manager, listing its functions
- This section describes some of the basic processes the operator will
- This section provides step by step procedures for starting and stopping the
- This section provides instructions for obtaining the current
- This section provides information on using the EDACS Help function.
- This section provides instruction for running and configuring
- This section provides instructions for using the
Section 10 Transferring Device Files
option, and provides examples on its use.
Section 11 Monitoring Performance Trends
dimensional line graphs, the MultiSite Monitor, and the Site Monitor. This allow the user to
evaluate the network’s past and present performance and to identify any adverse trends or areas
requiring optimization.
Section 12 M onitoring Real-Time Call Activity
Monitor and Site Monitor to monitor real-time call activity. The monitors are customizable to
meet the user’s needs.
- This section information for using the Accounting: File Transfer
- This section provides instructions for invoking two-
- This section provides instructions for using the MultiSite
9
LBI-39169 PREFACE
Section 13 Using OpenView Network Node Manager - This section provides supplemental information on
using some of the features available through HP OpenView Network Node Manager.
Section 14 Procedures - T his section pr ovid es pr oced ures for customizing, configuring, and maintaining the
Network Manager application.
Section 15 Troubleshooting - This section presents a list of problems which may be encountered and
possible corrective action.
Section 16 Glossary - Contains a glossary of terms.
Section 17 Index - This section provides a quick reference to key functions throughout the manual.
10
DOCUMENTATION LBI-39169
2. DOCUMENTATION
In may be necessary to consult one or more of the following documents when operating the Network Management
system.
2.1 HEWLETT-PACKARD DOCUMENTATION
The following Hewlett-Packard (HP) manuals provide additional information on the HP prod ucts used with the Network
Manager:
•
HP 9000 Series Owner’s Guide
•
B1171-90079 HP Visual User Environment User’s Guide
•
J2316-90001 HP OpenView Network Node Manager User’s Guide
•
J2316-90000 HP OpenView Windows User’s Guide
•
J2310-90002 HP OpenView Windows Application Design and Style Guide
•
J2311-90001 HP OpenView SNMP Programmer’s Guide and Reference
•
J2311-90004 HP OpenView SNMP Management Platform Performance and Configuration Guide with HP
Network Node Manager Examples for Release 3.3
•
J2319-90002 HP OpenView Programmer’s Guide
•
J2319-90009 HP OpenView Programmer’s Reference
•
B2355-90037 HP Remote Access Manual
2.2 RELATED ERICSSON PUBLICATIONS
The following Ericsson publications provide additional information on EDACS elements which interface directly or
indirectly with Network Management System:
Console Electronics Controller (CEC) and Integrated MultiSi te and Console Controller (IMC)
Documentation:
LBI-38662 - EDACS Console Electronics Controller (CEC) and Integrated MultiSite and Console Controller (IMC)
Digital Audio Switch
LBI-38939 - CEC/IMC Customer-Specific System Documentation Overview
LBI-39031 - EDACS StarGate Controller Digital Audio Switch Maintenance Manual
LBI-39041 - EDACS CEC/IMC Digital Dispatch DVIU Equipment Maintenance Manual
LBI-39062 - EDACS C3 Maestro Console System Maintenance Manual
LBI-39100 - EDACS C3 Maestro Console System with Enhanced Audio Enclosure
LBI-39124 - EDACS CEC Manager operations Guide, V4.0l
LBI-39224 - CEC/IMC Manager for Windows NT
11
LBI-39169 DOCUMENTATION
System Manager Documentation:
LBI-38703 - EDACS VAX/VMS System Manager Installation, Setup, and Troubleshooting Technical Reference
Manual
LBI-38984 - EDACS VAX/VMS System Manager User’s Guide
AE/LZT 123 1908/1 - Keyboard Mapping Template.
Billing Correlation Unit (BCU) and Centralized Activity Logger (CAL) Documentation:
LBI-38965 - EDACS BCU/CAL System and Installation Manual
LBI-38967 - EDACS Billing Correlation Unit/Centralized Activity Logger (BCU/CAL) User Interface Manual
Data Gateway Documentation:
LBI-38961 - EDACS Data Gateway Technical Description
LBI-38962 - EDACS Data Gateway Installation and Maintenance Manual
LBI-38963 - EDACS Data Gateway User’s Reference Manual
LBI-38964 - EDACS Data Gateway Configuration Reference Manual
Jessica PBX Gateway Documentation:
LBI-39000 - EDACS Jessica PBX Gateway Systems Manual
LBI-39001 - EDACS Jessica PBX Gateway Operator’s Manual
LBI-39039 - EDACS Jessica PBX Gateway MD110 Configuration Manual
LBI-39040 - EDACS Jessica PBX Gateway PI User’s Manual
LBI-39080 - EDACS Jessica PBX Gateway Operator’s Manual (Pocket Guide)
Miscellaneous Ericsson Documents:
ECR-1895 - Glossary of Mobile Radio Terms including Acronyms and Abbreviations.
Protocol Standards:
rfc-1213 - Management Information Base for Network Management of TCP/IP-Based internets: MIB-II.
12
INTRODUCTION LBI-39169
3. INTRODUCTION
The International Organization for Standards (ISO) Network Management forum identifies five functional areas of
network management, often referred to simply as “FCAPS.” This model se rves as the basis for the Network Management
system. The five management areas are as follows:
•
ault Management
F
•
onfiguration Management
C
•
ccounting Management
A
•
erformance Management
P
•
ecurity Management
S
In addition to the functional areas listed above, the EDACS Network Manager also provides the following:
Integrated CEC/IMC
Manager
Integration with Other
OpenView Network
Management
Applications
Scaleable Network
Manager Platform
Multiple EDACS
Network Manager
Sessions
Internationalization
Alarm Log/Reports
Using an integrated client o n the EDACS Network Manager pl atform, administrators
can view the same data, using the same windows that are available to technicians who
configure and debug locally. In this mode, the CEC/IMC Manager acts as the server,
while the application on the EDACS Network Manager participates as a client. The
EDACS Network Manager and CEC/I MC Manager platforms provide a client-server
applications that have a common look and feel.
The customer is responsible for maintaining the configuration of the other Network
Management applications. The EDACS Network Element icons may exist on the same
map as the customer’s OpenView T1/Microwave/PBX network icons to form an
integrated network management map.
The EDACS Network Manager application is available on a variety of HP
workstations/servers so that large and small networks can be supported cost
effectively.
The EDACS Network Manager allows multiple simultaneous users to be lo gged in and
viewing network information via X-sessions, either fr om X Stations or PCs r unning Xterminal emulation.
The EDACS Network Ma nager Applica tion uses the UN IX Native La nguage Support
(NLS). This feature supports other languages without recompiling the application.
Currently, English is the only language supported.
A report can be generated listing the past and present alarms.
Basic Help Menu
Internationalization
On-line help for the EDACS Network Manager application.
This feature supports other languages without recompiling the application. Currently,
English is the only language supported.
13
LBI-39169 INTRODUCTION
3.1 FAULT MANAGEMENT
Fault Management is responsible for detecting, isolating, and reporting anomalous conditions affecting network
operation. Central to the concept of a fault is the fact that some corrective action must be taken, whether automatically over a
Local Area Network (LAN) or by manual intervention by technicians at a site.
The following features are available through Fault Management:
Fault Notification
Hierarchical Network
Map for Fault
Notification
Alarm Help
Alarm Log/Reports
EDACS platforms send all alarm and status event information to a central point. The
Network Manager can periodically poll remote devices for missed events. Events are
logged at the EDACS Network Manager and displayed on the Hierarchical map.
Popup messages or automatic notification actions, such as email, are customizable.
Each Network Management Station is provided a consistent, integrated view of the
alarm status of its entire EDACS network. Alarms are propagated from lower network
layers all the way up to the top-level map.
On-line help is provided describing the fault and, where possible, suggesting the
corrective action. In addition, to the EDACS-provided alarm information, site-specific
alarm help/corrective action suggestions are customizable.
A report can be generated listing the past and present alarms.
3.2 CONFIGURATION MANAGEMENT
Configuration Management is responsible for identifying and controlling the state of elements within the network,
including subscriber access to the services provided by the network. This management area performs the following:
•
Using a local client Graphical User Interface to configure a device.
•
Using a Telnet session to configure devices in their native format.
•
Reboot, Restart, or Shutdown certain EDACS devices.
Configuration control of the CEC/IMC is thro ugh the CEC/IMC M anager for Windo ws NT. The CEC/IMC Mana ger for
Windows NT employs the client-server paradigm. The server, which interfaces to the CEC/IMC, runs on the Windows NT
platform while the client may run on either the Windows NT platform or the EDACS Network Manager UNIX platform.
This allows the CEC/IMC Manager user interface to be run either on the EDACS Network Manager or on the CEC/IMC
Manager PC.
Configuration Management of other devices is via native access i.e., Telnet session into the System Manager, BCU/CAL,
and PI. Each device retains its password protection, therefore users must have login privileges. The ability to log in to
multiple platforms and operate in their native modes from one terminal provides a migration path for devices converting to the
client-server paradigm.
Remote ability to perform shutdown, restart, and reboot operations to selected EDACS devices is provided. The
execution of these actions is recorded in the same log used for alarms.
3.3 ACCOUNTING MANAGEMENT
Accounting Management is responsible for capturing the usage of network resources by end users.
Billing subsystems are available on the BCU (stand-alone), BCU option on the PI platform, and Enhanced Local
Interconnect (ELI). Only the BCU and PI are accessible from the EDACS Network Manager (via File Transfer Protocol) to
retrieve billing records.
14
INTRODUCTION LBI-39169
3.4 PERFORMANCE MANAGEMENT
Performance Management is responsible for characterizing the usage and efficiency of the network. This area is
conceptually composed of three major areas:
•
Utilization
being used.
•
Accessibility
customer expectations.
•
Tuning
accessibility.
EDACS devices provide vario us performance values via SNMP Management Information B ases (MIBs). T he EDACS
NM requests and receives these values for display and/or collection. The performance values required, and the network
element(s) responsible for providing them, are given in the following subsections on a per map object basis.
Graphs to address Utilization and Accessibility may be invoked via menu items. See Section 0. Other parameters may
be useful when troubleshooting.
Graphical Performance
Monitoring
Multisite Monitor
Site Monitor
-- Provides information regarding which aspects of, and the degree to which, the network interfaces are
-- Provides information which may be used in determining that the network services are meeting
-- Provides information which may be used to evaluate adjustments to the network to increase utilization and
EDACS Network Administrators can monitor system performance at node and site
levels. Results may be saved to disk and later displayed. Performance graphs may
also be saved. Performance graphs are available with the Billing Correlation
Unit/Centralized Activity Logger (BCU/CAL) or as a separate Jessica Private Branch
Exchange Interface (PI) option.
The Multisite Monitor oversees call activity for an entire node. It is available with
BCU/CAL or as a separate PI option.
The Site Monitor oversees call activity for an individual site. It is available with
BCU/CAL or as a separate PI option.
3.5 SECURITY MANAGEMENT
The Network Manager provides security of both user and system access. There are three levels of users authorized to use
the Network Manager system. These are classified as Administrator (or SuperUser), Technician, and User.
System Access is controlled by assigning user account passwords, assigning unique community names to devices, and
through the profile configuration of remote elements.
3.5.1 Access Levels
The classifications of Network Management users are:
•
Administrator
the Network Management system. This allows the administrator to re trie ve, vie w, and cha nge Ne twork M ana gement
system attributes. However, only one write copy of OpenView may be operating at any one time. All other
simultaneous sessions will be read only.
•
Technician
retrieve and view network data, but restricts the Technician from making unauthorized changes to the Network
Management system attributes.
•
- The User has a reduced menu set and read only access to OpenView. This limits the users access to critical
User
EDACS functions and editing features in OpenView.
- The Administrator has a full menu set and write access to OpenView, thus complete control over
- The Technician has a full menu set and read only access to OpenView. This allows the Technican to
15
LBI-39169 INTRODUCTION
3.5.2 System Access
Security Management is responsible for administering user access to network resources, including the Network Elements
(NEs) themselves. The approach will encompass:
•
Password Protection: Native Access Mode -- Native access refers to currently existing security measures, such as
account-password validation. This mode applies to local (i.e., user console) and remote (i.e., Telnet and File
Transfer Protocol) access procedures implemented by Network Elements.
•
SNMPv1 protocol protection: SNMP provides some inherent security mechanisms. This will mainly serve as
protection against data corruption due to application errors.
•
To enhance SNMPv1 security, the directly connected NE supports a community name profile which allows
restriction of IP Addresses to specific community names with specific read-write access.
3.6 HIERARCHICAL MAPS
The Network Management graphically illustrates an EDACS network by using a set of hierarchical map levels. By
traversing down the maps, a greater level of detail is revealed.
Four network levels are suggested:
•
EDACS
•
Multi-Node
•
Node
•
Site
All submaps are created such that the icons may be moved freely about the map, there are no restrictions regarding
placement of EDACS icons on maps. Thus, all icons could be on one submap if desired. For customers without all the
network levels listed above, the EDACS icon will explode into the first available level. The EDACS, Node, and Site icons
are explodable icons, meaning that double-clicking on them will bring up the next lower level. See the examples of the Map
Traversal Screens shown in Figures 2 and 3.
The EDACS Map Generation Application assists in setting up EDACS maps and is d escribed in the Installation manual,
LBI-39171.
A new term “Switching Center” is being introduced with the Network Manager. To represent 30 consoles, 32 sites,
BCU/CAL, CEC/IMC Manager, System Manager, EDG, and PI on one map would make the map very busy. Therefore, the
term “Switching Center” was coined to represent the devices physically located at the IMC Node. This includes the IMC,
consoles, BCU/CAL, EDG, PI, CEC/IMC Manager, and System Manager. As an analogy to this, the Site represents the
devices physically located at the site such as channels, TU, ACU, SC, PMU, and ELI.
All EDACS “symbols” will require identifiers to uniquely identify them. These identifiers are specified in the “EDACS
Identifiers” attribute section of the Describe/Modify popup window.
The following is a summary of map features:
Assisted Map
Generation
Customized Maps
When the following symbols are added, popup windows prompt for information to
generate the map hierarchy: IMC Nod e, CEC Node, Remote CEC Node, Switching
Center, and Site.
As the EDACS NM application leverages HP OpenView Network Node Manager,
EDACS icons can be positioned anywhere on the submap. Although Ma p Gener ation
places icons on default submaps, the customer may create his own hierarchical view.
Icons for non-EDACS devices may be placed on EDACS maps.
16
INTRODUCTION LBI-39169
p
Background Network
Map Overlays
This standard HP OpenView Network Node Manager feature allows customers to
flexibly place network icons on top of actual area maps. Topological maps (in
standard GIF format) are easily added, but are not provided.
Customizable Icons
The labels on icons may be modified. The user may add text to an icon’s object for
customer-specific information such as the site contact, location, etc.
3.7 EDACS NM MENUS AND THEIR FUNCTIONALITY
There is a common set of pull-down menu options available to icons. Menu options are grayed out for functions that are
not applicable for a specific icon. The EDACS Network Manager’s EDACS-specific functionality can only be activated by:
1) Selecting an icon that represents an EDACS manageable element, and
2) Activating the EDACS menu located on the Main Menu bar at the top of the screen.
If an icon is not selected, the EDACS menu option may be grayed out, meaning that it is inaccessible. Figure 1 shows the
initial set of submenus which include Faults, Configuration, Accounting File Transfer, Performance, and Software Version.
Refer to the following text for additional details on each EDACS menu option.
. Provides alarm information about
Faults
the EDACS device represented by the icon.
File...
Configuration
configuration functi ons
associated with the EDACS
device represented by the icon.
Software Version
software version information for
each directly connected device
and its subcomponents.
. Presents
. Displays the
EDACS
Faults
Faults
Configuration
ccounting: File Transfer
A
P
erformance
S
oftware Version
Figure 1 - EDACS Menu on Main Menu Bar
Hel
Accounting: File Transfer.
device-specific accounting r ecords or
configuration file s to be trans fe r re d
to the EDACS Network Manager
using File Transfer Protocol (FTP).
Performance.
information about the EDACS
device represented by the icon.
Presents performance
Allows
17
LBI-39169 NETWORK MANAGER BASICS
4. NETWORK MANAGER BASICS
4.1 PULLDOWN MENU SELECTION PROCEDURE USING THE MOUSE
Select one of the two options below to select the Pulldown Menu:
Position the cursor to the desired menu option, and quickly press/release the left mouse button once. The pulldown
menu will fix itself to the screen. Position the cursor to the next desired option, and press/release the left mouse
button once.
OR
Position the cursor to the desired menu option, press (but do not release) the left mouse button. Drag the cursor to
the next desired option and release the left mouse button.
4.2 PULLDOWN MENU SELECTION PROCEDURE USING THE KEYBOARD
Each menu option contains a mnemonic (one-letter hot key) that is shown visually with an underline. To select an op tion
on the main menu bar, press the ALT key and the mnemonic simultaneously. A pulldown menu will appear. Press the
mnemonic of the next desired option to select it.
4.3 EDITOR OPTIONS
vuepad editor - HP VUE editor, menu-driven, simple, intuitive
> /usr/vue/bin/vuepad filename
NOTE: Also available via an icon on the VUE menu pad. Automatically invoked via the File Manager utility
when the user chooses to edit a file.
NOTE: To edit a file, the file must have write privileges for your user type. See the Unix man pages for the
chmod / chown commands to reset file permissions and ownership.
vi editor - standard Unix editor, command-driven
> vi filename
NOTE: Recommend book by O'Reilly & Associates, Inc. entitled Learning the vi Editor
18
NETWORK MANAGER BASICS LBI-39169
4.4 MAP TRAVERSAL
The following submaps are examples of map traversal. The first two submaps contain background graphics, while the
last two do not. Background graphics may be loaded in all submaps.
Exploding the EDACS icon brings up a screen similar to that shown below.
Exploding the IMC Node 37 icon brings up the IMC Node 37 submap screen similar to the one shown above.
Figure 2 - Example of Map Traversal
19
LBI-39169 NETWORK MANAGER BASICS
Exploding the Switching Center icon (SW Ctr #37) on the IMC Node 37 submap brings up a Switch Center 37 submap
similar to the screen shown below.
Exploding a Site icon (such as Site 1) on the IMC Node 37 submap brings up the Site 1 submap similar to the screen
shown below.
20
Figure 3 - Example of Exploding a Switching Center and Site Icon
STARTUP PROCEDURES LBI-39169
5. STARTUP PROCEDURES
Use the following proced ures to login and start a Network Mana ger work session. A Ne twork Manager work session is
described as the time between logging in and logging out.
5.1 STARTING A NETWORK MANAGER WORK SESSION
The Ericsson Login Screen is the gateway to the Network Management System. After entering your login name and
password, the session will start by displaying HP VUE (Visual User Environment) screen containing the HP VUE Front
Panel.
Login into the Network Management system by using the following procedures:
1. Select the Login box and enter your login name.
Press the <ENTER> button or use the mouse and
place the cursor in the Password box.
2. Type in your password. Press the <ENTER>
button or click on OK.
If the Login Manager does not recognize your
name or password, click on
the information.
CLEAR
and reenter
3. Successfully logging into the HP OpenView
session will result in displaying the HP VUE
Front Panel.
EDACS Icon
Figure 5 - Network Manager Login Dialog Box
4. Start the Network Manager application by clicking on the EDACS icon. The terminal will display a READ version
Network Management Home submap.
Additionally, a popup message will be displayed indicating the Polling Status and the Clock Synchronization Source.
Figure 4 - Network Manager Login Dialog Box
5. You are now able of retrieve and view those Network Management attributes authorized by your Network
Administrator.
21
LBI-39169 STARTUP PROCEDURES
5.2 ENDING A NETWORK MANAGER WORK SESSION
Use the following procedures to properly end a work session.
CAUTION
CAUTION
When you finish a working session, DO NOT turn off the Network Manager Sta tion. This equipment is part of a
multi-user network, and other people may be using it. If you turn off the Network Manager station, you will deny
them access to it.
NOTE
NOTE
If a complete system shutdown is required, refer to the System Shutdown Procedures after logging out.
5.2.1 LOGGING OUT OF THE NETWORK MANAGER SESSION
To exit the Network Management session, perform the following:
1. From any Network Management submap, select File->Exit from the menu bar.
2. OpenView will display a Warning popup menu, indicating your session is ending. Click on OK to end the session.
3. OpenView will close all applicable files and return to the HP VUE screen.
5.2.2 LOGGING OUT OF THE HP VUE SESSION
To completely exit the HP VUE session, perform the following:
1. Click on the EXIT button on the HP VUE Front Panel.
2. The Session Manager will prompt you with the Logout Confirmation popup menu.
This popup menu will indicate “This session not saved. Instead your Home Session will be restored upon startup.”
This is normal operation configured into the system during installation. If it is necessary to make changes to the
Startup Session, consult with your Network Administrator.
3. Click OK to continue the logout process.
4. After logging out, the terminal will return to the Login screen.
22
RETRIEVING THE SOFTWARE VERSION LBI-39169
6. RETRIEVING THE SOFTWARE VERSION
The Software Version feature allows you to obtain the versions of software installed on the Network Manager platform
and software installed on directly connected devices and the devices they proxy for.
6.1 SUBCOMPONENT SOFTWARE VERSIONS
All software versions for the directly connected device and its subcomponents are available by using the following
procedure:
1. From the hierarchical map, select the icon representing the desired subcomponents.
NOTE:
2. The Network Manager will respond with the Software Table screen showing the software versions of all devices (or
boards) directly connected to the selected device.
For example, the response to an inquiry about the software version of the CEC/IMC Manager includes the versions
of its boards as shown in Figure 6. The IP Address or host name of the directly connected EDACS device is listed in
the IP Address field.
3. Select the CLOSE button at the bottom of the screen to exit the Software Table screen.
If an icon is not selected, the EDACS->Software Version menu may be greyed out.
Part Number
Major Version
Figure 6 - Software Version Screen Example
The Part Number field identifies the Ericsson Part Number o f the software. If the software is installed on
a ROM chip, then the part number will be preceded by the ROM’s reference designator (or location).
The Major Software vision is an integer number representing the major software revision number, for
example the number “2” in 2.1.
23
LBI-39169 RETRIEVING THE SOFTWARE VERSION
Major Version The Minor Software vision is an integer number representing the minor software revision number, for
example the number “1” in 2.1.
Description The description field provides a brief description of the software component.
Software Path This field will identify the ROM or the location of the software on the disk.
6.2 NETWORK MANAGER SOFTWARE APPLICATION VERSIONS
A list of software applications installed in the Network Manager and their software version can be obtained by using the
following procedure:
1. Select Help -> On Version from the Main Menu Bar.
2. The Network Manager will display a list of software installed in the Network Manager and their software versions.
A list of software applications, their software version, copyright data, and description can be obtained by using the
following procedure:
1. Select Help -> Index -> Application from the Main Menu Bar.
2. The display will list the application software installed in the Network Manager platform.
3. Select the desired application and the pertinent data will be displayed.
24
EDACS HELP LBI-39169
7. EDACS HELP
EDACS Help has been integrated into the OpenView Network Node Manager help system. EDACS Help items are
preceded with “EDACS” to make them easily identifiable.
. Explains the Op enView
Display Legend
color associations.
Application
Application
T
asks F1
unctions
F
. Provides a graphical list of icons and their
Index->Application.
information on each software application
installed on the platform, including
version and description.
Index->Task.
OpenView tasks and task procedures.
Provides detailed
Provides a list of
File...
Glossary.
line definitions for many
OpenView terms.
On Version.
of application software
installed on the platform
and their ve rsion numbers.
Provides on
Provides a list
Index->Functions.
OpenView Functions and their capabilities.
Help
elp
On H
D
isplay Legend
ndex
I
Index
G
lossary
ersion
On V
Provides a list of
On Help
Help system.
Figure 7 - EDACS Help Menu
7.1 TASK HELP
On-line help is available for performing various EDACS and OpenView tasks. The Task Index provides a list of
OpenView and EDACS menu bar and Map Generation help files and when opened, provides detailed procedures for
performing the task. Perform the following when requesting task assistance.
1. Select Help -> Index -> Tasks from the Main Menu Bar.
2. The display will list the various OpenView and EDACS tasks.
3. Select the desired task and the click on the Open button.
4. OpenView will provide a description of the task and suggested procedure.
7.2 FUNCTION HELP
On-line help is available for performing various OpenView functions. The Function Index provides a list of OpenView
and EDACS Functions and when opened, provides detailed procedures to perform the function. Perform the following when
requesting on assistance.
1. Select Help -> Index -> Function from the Main Menu Bar.
2. The display will list the various OpenView functions.
3. Select the desired function and the click on the Open button.
4. OpenView will provide a description of the function and recommended usage.
25
LBI-39169 MONITORING EDACS FAULT CONDITIONS
8. MONITORING EDACS FAULT CONDITIONS
Fault Management is responsible for detecting, isolating, and reporting alarm or fault conditio ns affecting the various
Managed Elements (ME) in the EDACS network.
8.1 DETECTING AND ISOLATING FAULTS (ALARMS)
Fault (alarm) or event status notification results from the Network Manager either receiving information from the EDACS
platforms or as a response to polling. When an event is received the user is notified of the event through the Event
Notification Interface or by changing the color of the appropriate icon on the hierarchical maps.
EDACS Fault Management tracks five user-configurable severity levels for each managed EDACS Network Element:
•
Normal
•
Warning
•
Minor
•
Major
•
Critical
Table 1 lists the severity levels, descriptions, and associated colors. The severity levels and colors are configured
according to HP OpenView Network Node Manager conventions. Each alarm received is tracked internally. The color of the
icon does not change until all alarms received at that severity level have cleared, or an alarm at a higher severity level is
received. For the EDACS Network Manager application, green icons indicate there are no known managed faults against the
device represented by the icon.
Fault Management can periodically poll remote elements for missed traps. Elements on unlicensed nodes or sites will
have Restricted status, and any corresponding traps will be ignored. Refer to FCAPS section in LBI-39215 for the actual fault
items and Table 1 for the meaning of icon colors. The meaning of icon colors may also be obtained by selecting the Help ->
Display Legend from the main menu.
An application sets the status to “normal” when the object is in a normal operational state.
An application sets the status to “warning” when an object may face a potential problem.
An application sets the status to “minor/marginal” when an object has a minor problem; this
status should not, however, impede the normal use of the device.
An application sets the status to “major” when an object has serious problems; these problems are
likely to impede normal use of the device.
An application sets the status to “critical” when a device is not functioning or is not accessible by
the EDACS Network Manager.
8.1.1 Notification through the Event Notification Interface
Once an alarm is generated, it is logged into the Event Logs. After the event is logged, the alarm specifics are available
through the Event Notification Interface. The Event Notification Interface includes the Event Categories window and the
multiple Event Browser windows.
The Event Categories Window acts as an event notification window. The push
buttons in this window light up to indicate when events have been received and have
not been deleted from the Events Browser. The color of the p ush b utton reflects the
most severe event in the category, or background color if no events are present. The
“All Events” category contains all the events which are present in the other
categories. The “EDACS Events” category is added by the Network Manager
application software.
8.1.2 Notification Through Icon Color
After the Network Manager logs the event, it will change the appropriate map
icon(s) color if necessary, and if enabled, display a popup window reporting the
event and its severity.
26
Figure 8 - Event Category Window
MONITORING EDACS FAULT CONDITIONS LBI-39169
Table 1 - Status Colors/Levels
Category Status
Condition
Administrative Unmanaged Users can set this value, which indicates that
the object should not be monitored and that the
status should be ignored. When the user sets
the object back to “managed.” the EDACS>Fault->Update operation must be performed.
Administrative Testing An application sets the status to “testing” when
an object is undergoing temporary diagnostic
or maintenance procedures. This category is
not used by the EDACS Network Manager
application.
Administrative Restricted An application sets the status to “restricted”
when a valid associated CEC/IMC/RCEC/SG
node license does not exist for this element.
Administrative Shutdown An application sets the status to “shutdown”
when an object is inactive (although there may
not be anything necessarily wrong with the
object). This category is not used by the
EDACS Network Manager application.
Operational Unknown An application sets the status to “unknown”
when the status of an object cannot be
determined. EDACS icon may be blue if there
is another icon with the same Network Number
and Node Number or if polling does not detect
a physical device corresponding to this icon.
Operational Normal An application sets the status to “normal” when
the object is in a normal operational state.
Operational Warning An application sets the status to “warning”
when an object may face a potential problem.
Operational Minor/
Marginal
Operational Major An application sets the status to “major” when
Operational Critical An application sets the status to “critical” when
An application sets the status to
“minor/marginal” when an object has a minor
problem; this status should not, however,
impede the normal operation of the network.
an object has serious problems; these
problems are likely to impede normal use of
the network.
a device is not functioning or is not accessible
by the EDACS Network Manager.
Status Meaning Icon Color
Off-white
Salmon
Tan
Dark Brown
Blue
Green
Cyan
Yellow
Orange
Red
27
Loading...