DEFINITY G3 Proxy Agent1-3
Your Network Management System1-3
■ Supported PBXs1-4
■ Fault Management’s User Interface1-4
Color1-4
Alarms Display1-5
Menu Bar1-5
Hotspots1-5
Scroll Bars1-7
Close Button1-7
Exit Button1-8
Accelerator Keys1-8
■ How to Enter Data1-8
Data Typed into Fields1-8
Pull-down Lists1-8
Check Boxes1-9
Radio B utt o n s1-9
Issue 2 April 1996iii
Contents
■ Management Information B as e1-9
■ Data Refresh1-9
Startup Refresh1-10
Configuration Data Refresh1-11
Bulletin Board Refresh1-11
Alarms and Errors Data Refresh1-11
2 Starting/S toppi ng Fault Management 2-1
■ Starting Fault Management2-1
■ The Startup Screen2-2
Start-Up Messag es2-3
Exit Button2-4
■ The Startup Process2-4
Retrieving Data2-4
Failing to Retrieve Data2-5
Requestin g Dat a2-5
■ Stoppi ng Fault Mana gem e nt2-5
3 Cu stomizing Fault Management 3-1
■ Op enin g the Setup Screen3-1
■ Th e Setup Screen3-1
Sa mple Setup Screen3-2
Menu Bar3-3
■ Changing Colors3-4
■ Cha nging Ti me Inte rv al s3-5
■ Changing Other Options3-7
■ Testing Your Changes3-8
■ Saving Changes3-8
■ Reverting to Default Setting s3-9
■ Exiting the Set u p Screen3-9
Issue 2 April 1996iv
Contents
4 The Config uratio n Map 4-1
■ Overview of the Configuration Map4-1
Faults Displayed as Colors4-2
Screens in the Configurat ion View4-2
■ Switch View4-3
How to Open the Swi tch View4-3
Sa mple Switch View4-3
Menu Bar for Switc h View4-4
Screen Heading for Switch View4-6
Alarms for Switch View4-6
Switch View Hotspots4-7
Switch View Messages4-8
■ Cabinet View4-8
How to Open the Cabinet View4-8
Sample C a b inet View4-8
Menu Bar for the C a b inet View4-9
Graphic Display Area4-10
Cabinet Data Area4-11
Cabinet Messages4-14
■ Circuit Pack Information4-14
How to Open Circuit Pack Information4-14
Sample Circuit Pack Information Screens4-15
Menu Bar for Circuit Pack Information4-17
Data Area for Circuit Pack Information4-17
Circuit Pack Hotspots4-20
■ Port Information4-20
How to Ope n Port Information4-20
Sample Port Information Screens4-20
Menu Bar for Port Information4-24
Data Area for Port Information4-25
Port Hotspots4-29
Port Messages4-29
■ External Devices4-30
How to Open External Devices4-30
Issue 2 Ap ril 1996v
Contents
Sample External Devices Screen4-30
Menu Bar for External Devices4-32
Screen Heading for External Devices4-32
Alarms for External Devices4-32
External Device Hotspots4-33
External Device Messages4-33
■ Individual External Devices4-33
How to Open Individual External Devices4-34
Sa mple Individual External Devices Screen4-34
Menu Bar for In d ivid ual External Device4-35
Data Area for In d ividual External Device4-35
5 The Fault Manag er 5-1
■ Overview of Fault Manager5-1
■ Wh e n Fault Manager Receives Da ta5-2
■ How Fault Manager Displays Faults5-2
Color Highlighti n g5-2
Alarms5-2
Alarms Reports5-3
Error Reports5-6
■ How to open Report Windows5-10
■ How to Print Reports5-11
■ How t o Cl ose Rep ort Wind ow s5-11
■ How to Get More Report Information5-11
■ Error Descript i on Screen5-11
How to Open Error Descriptions5-12
Sample Error Description Screen5-12
Menu Bar for Error Descriptions5-13
Screen Heading for Error Descriptions5-13
Error Description Panel5-13
Notes Panel5-13
■ Bulletin Board5-14
How to O p e n the B ullet in Board5-14
viIssue 2 April 1996
Contents
Sa mple Bulle t in Board5-14
Menu Bar for the Bulletin Board5-15
Data Area for the Bulletin Board5-16
How to Refresh this Screen5-17
6 The Configuration Manager 6-1
■ Overview of Configuration Manager6-1
Types of Configuration Data6-2
■ Har dware/Software Information Report6-2
■ Circuit Pack Inventory Report6-4
■ How to Save Inventory Reports6-6
■ Circuit Pack Reports6-7
■ DS1 Circuit Pack Reports6-9
■ How to Open Config urati on Reports6-11
■ How to Print Configuration Reports6-11
■ How to Close Confi g uration Reports6-12
■ Cabinet Displays6-12
Circuit Pack Filters6-12
How to Identify Circuit Pack Conf i gurations6-13
How to Clear Filter Highlighting6-14
■ How to Refresh Configuration Data6-14
Scheduled Refresh6-14
7 Report Builder 7-1
■ Overview for Report Builder7-1
Types of Tabl es7-2
Search Criteria7-2
Report Format7-2
■ Report Builder Screen7-3
How to O p e n Rep ort B uild er7-3
Sample Report Builder Screen7 -3
Issue 2 A pril 1996vii
Contents
Menu Bar for Report Builder7-5
Data Area for Re port Builder7-5
Button Line7-8
■ Overview for Creating Reports7-8
■ How to Name the Rep ort7-9
Guidelines for the Report Name Field7-9
■ How to S elect the Tab l e to Search7-9
Gui d eline s for the Table to Search Field7-9
How to Display All Alarms7-10
■ How to Enter Search Criteria7-10
Gui delines for Data Selection Fields7-10
How to Search for an Exact M atch7-11
How to Search for a Range7-13
How to Search for a Pa rtial Matc h7-15
■ How to Format the Report7-15
Gui d eline s for the Table to Outp u t Field7-16
■ How to Sort Report Data7-16
Guidelines for the Sort Fields7-16
■ How t o Save Report Specif ic ations7-17
■ How to Run the Rep ort7-17
How to Change the Report7-17
8 Output Options 8-1
■ Overview for Output Options8-1
■ Output Opti ons Screen8-1
How to Open Output Options8-2
Sample Output Options Screen8-2
Menu Bar for Out p u t Op tions8-3
Data Area for Output Op t ion s8-4
Output Options Messages8-6
Button L ine for Out put O p tio n s8-7
■ How to Disp lay Reports8-7
■ How to Highlight Objects8 - 7
viiiIssue 2 April 1996
Contents
■ How to Print R e p o rts8-7
■ How to Save Reports8-8
9 Troubleshooting 9-1
■ xnmevents Crash (HP OpenView)9-1
■ Switch View Messages9 -2
Messages Specific to HP OpenView9-5
■ Port Messa g e s9-6
Messages Specific to HP OpenView9-6
■ Pop-up Messages9-7
■ Startup Me s sages9-9
10 Integrating With Remedy 10-1
■ Ac t ion Request System Overview10-1
■ HP OpenView10-1
Create a Schema10-2
Create a Macro10-2
Test the Macro10-3
Test the Script10-3
■ Cabletron SP ECTRUM10-3
11 Quick Reference for Screens 5
■ General Comme nts5
IN Index IN-1
Issue 2 April 1996ix
About This Book
The purpose of this document is to help private branch exchange (PBX)
administrators and managers use DEFINIT Y
guide provides a description o f the screens, fields, access methods, reports, and
other features that are p a rt of the application.
Intended Audience
This gu i de is i ntended for DE FINITY G3 and network managers who are
managing DEFIN ITY G3 PBXs as nodes on a network management system
(NMS). B ecause Fault M a nagement provides information about fault conditions
on a PBX, it is aime d p rim arily towa rd people who are concerned with the health
of a PBX. That person may be responsible for the PBX, the NMS, or both.
Associated Documents
Documents associated with this online guide are:
■
OneVision DEFINITY G3 Fault Management Installation and Integration
This gu i de explains ho w to install and set up Fault Management software,
how to set up PBXs and Proxy Agents as nodes on the NMS, how to
change Fault Management’s polling int ervals an d d e fault colors, and how
to verify that the Proxy Agent is connected to a PBX.
This gu i de explains how to install, set up , a nd c ustom ize Proxy Agent
software. It al so contain s basic hardware and software requirements,
inform at ion fo r c o nnect in g the Proxy Agent to a LAN, and troubleshooting
guidelines.
Issue 2 April 1996xi
About This Book
■BCS Produc ts Security Handbook (555-025-600)
■The appropriate maintenance manual f or each DEFINITY G3 PBX that you
Conventions
This gu i de uses the followin g text c o nventi ons:
Text formatType of information
BoldCommand names and parameters, informa tion you
italic
are managing on your NMS.
type, and file names
Emphasized key words
[bold and
bracketed]
Variables
Example: Enter aruser -e [mac ro-nam e ] means to
substitute the name of the macro for [macro-name].
constant width Sy stem messages and responses
small type Keyboard keys
à
Example: Press
Menu selections
Ex ample: Select Options àClose
Return.
, means to select
Options, then sele c t Close from the pull-down menu.
Throughout this document, tol l fraud security hazards are indicated by an
exclamation poi nt inside a triangle and the word Caution.
!
CAUTION:
A security alert may indicate the presence of a toll fraud security hazard.
Toll fraud is the unauthorized use of your telecommunications system by an
unauthorized party. Examples of unauthori zed pa rti es are p ersons other
than your com pany’s employees, a g e nts, s u b contractors, or persons
working on your company’s behalf. Additional security information is
included in Security Considerations later in this preface.
Trademarks
The fol lowing AT&T trademarks or registered trademarks are used in this
document:
■DynaText is a registered trademark of Electronic Book Technologies, Inc.
■HP, HP-UX, and OpenView are trademarks of Hewlett-Packard Company
xiiIssue 2 April 1996
Security Considerations
■OneVision and DEFINITY are trademarks or registered trademarks of AT&T
■Remedy and Actio n Request System are trademarks of Remedy
Corporation
■SP ECTRUM an d Sp ectroSERVER a re r eg istered trad emarks of Cabletron
Systems, Inc.
■SunOS an d SPARC are trademarks or registered trademarks of Sun
MicroSystems, Inc.
All other bra nds and product names are the trademarks of their respective
holders.
Security Considerations
Your NMS provides the security for your network. As a part of that network, F ault
Management neither adds to nor detracts from the level of security your NMS provides.
Fault Management is a display-only application; you can view the data from your P BX, but
not change it.
Reader Comments
If you have any comme nts o r su g gestions abou t this document, please send
them to AT&T at the following address.
AT&T
Product Documentation Development Department
Room 22-2C11
11900 North Pecos Street
Denver, CO 80234
FAX: (303) 538-1741
Please include the following infor mat ion:
■The nam e o f this document:
DEFINITY G3 Fault Ma nagement
■Your NMS: HP OpenView
■Your p l atfor m : SunOS
Credentials
DEFINITY G3 Fault Ma nagement is ISO 9001 certified.
OneVision Network Management Solutions
or IBM NetView
, HP-UX, or AIX
Issue 2 April 1996
xiii
About This Book
AT&T BCS is also an HP OpenView Solution Partner; and Faul t M a nagem ent is
listed in the HP OpenView Solutions c a talog.
xivIssue 2 April 1996
Introduction
This chapter provi des an overview of the DEFINITY G3 Fault Management
software, and incl udes:
■Fault Management Featu res
■System Int e g rati on
1
■Suppo r t e d PBXs
■Fault Management’s User Interface
■Data Refresh
This chapter lays the groundwork for subsequent chapters which cover the
application in greater detail.
Fault Management Features
DEFINITY G3 Fault Ma nagement (referred to as Fault Management throughout
this guide) provides a PBX manager with a graphical tool for monitoring the
status of a DEFI NITY G3 PB X.
Fault Ma nagement displays DEFINITY G3 PBX faul t a n d c o n f i g urat ion d a t a in a
graphical format. It resides on an industry-standard network management
system (NMS).
Fault Ma nagement consists of the following features:
■Configuration Map
■Fault Manager
■Configuration Manager
Issue 2 Apri l 19961-1
Introduction
Configuration Map
The configuration map provides a graphical user interface (GUI) that displays
information ab out a DEFI NITY G3 PB X m anaged by your NMS.
You display this information by clicking on a pictoral rep rese ntation of the PBX’s
hardware. Each time you click, you peel away the layers of the PBX and uncover
more specific data.
The configuration map allows you to uncover the following PBX hardware layers.
The most general layer is shown first; the most sp ecific layer is shown last.
This layer …Includes data for …
SwitchThe entire PBX
Cabinet One cabinet in the PBX
Circuit Pack One circuit pack in the cabinet
Port One port on th e c i rcuit pac k
The configuration map also has the following layers for external devices:
This layer …Includes data for …
External DevicesEach external device
Individual External
Device
Faul t Manager
The fau lt manager provides information about active (non-resolved) alarm
conditions that exist within a PBX. The inf o rmat i o n is i n a color-coded graphical
format so that you can find faults quickly and easily.
Fault ma nager alerts you to fault condit ions by:
■Highlighting the graphic depiction of the PBX hardware that has an alarm.
administered on the PBX
A specif ic external device on the
PBX
The color of the highlight corresponds to the highest severity alarm. T his
highlighting allows you to see the following items at a glance:
— Where alarm conditions exist
— How severe the alarms are
— The q uant i t y of each alarm type
■Displaying alarm counts that are sor t e d b y:
— The location of the ala r m
1-2Issue 2 April 1996
System Int e g ration
— The severity of the alarm (major, minor, or warning )
Configuration Manager
The config uration manager provides, in a graphical and report format,
information about your PBX, cabinet, and external device configurations. This
information consists of a PBX ’s hardware and software versions and an inventory
of circuit packs and their locations.
System Integration
The Fault Management ap p lication is closely integrated with, and relies heavily
on, two other applications:
■DEFIN ITY G3 Proxy Agent
■Your network management system (NMS)
DEFINITY G3 Proxy Agent
Fault Ma nagement receives data from the PBX via AT&T’s DEFINITY G3 Proxy
Agent, release 1.2 (referred to as the Proxy Ag e nt throughout this gu i de). The
Proxy Agent and Fault Management are installed on two separate co mputers.
The purpose of the Pr oxy Agent is to receive status information from the PBX and
then translate that information into a format that your NMS can understand. That
format is SNMP (Simp le Network Management System).
Yo u r Netwo rk M anag emen t System
Fault Ma nagement is an add-on to your network management system (NMS).
Fault Ma nagement integrates with your NMS in such a way that Fault
Management must be executed from the NMS.
Both the NMS and Fault Man a gem en t receive d ata from the Proxy Agent. The
NMS can display within various views the d ata that it rec eives from the Proxy
Agent.
Fault Ma nagement can only manage the PBXs that are set up on your NMS. To
have status information available to you via Fault Management, the PBX must be
a node on Fault Management’s host NMS platform.
This section describes the following elem ents i n c luded in the Fault
Management’s user interface:
■ Accelerator Keys■ Hotspots
Color
■ Alarms Display■ Menu B ar
■ Color■ Scroll Bars
■ Close Button
When the information is b est explained in the context of co m plet ing a Fault
Management task, this section refers you to another chapter for detail s.
Fault ma nager highlights the affe c ted ha rdware with the c o l or of the hi g hest
severity fault.
For example, if a cabinet has four warnings and one minor alarm, the cabinet is
highlighted with the color of the minor alarm.
NOTE:
You can change these color settings on the Setup me nu. See Ta ble 3-6 for
instructions.
To learn more
about color and …Go to this chapter …
Default settingsChapter 3, Customizing Fault
Management
Configuration managementChapter 6, The Configuration Manager
1-4Issue 2 April 1996
Fault Management’s User Interface
Alarms Display
An alarms display, similar to the one shown below, is located on the ri g ht side of
any configuration s creen.
Figure 1-1. A l arms Display
Menu Bar
Fault Ma nagement uses a standard menu ba r with the following pull-down
men us. The actual list of c o m ma nds that you see is de t e r mined b y the active
screen.
Hotspots
MenuDescription
Op tionAllows you to perform application-wide com mands. For
exampl e, op e ning Fault Management features, savin g d a t a,
and closing screens.
FaultAllows you to see lists or reports of current errors and
alarms . These lists display in new windows.
Config u rationA llow s you to ge t informatio n a b out the confi guration for the
current PBX. This menu is available only at the following
screens:
■ Switch View
■ Cabinet View
■ External Devices
HelpThe Help menu opens a window that contain s
context-sensitive help (help specific to the active window.)
To learn more about the menu bar for a specific screen, go to the Menu Bar
section for that screen.
When you click the mouse on an area of the screen designated as a hotspot, the
system performs a predetermined function.
Issue 2 April 1996
1-5
Introduction
NOTE:
This gu ide ref ers to hotspots in Fault M a nagement, not DynaText. The
Fault Management screens and windows that display when you double
cli c k on th e c ame ra i c on in this g u i d e d o not have functioning hotspots.
However, you c a n try out the hotspots when you return to the Fault
Management ap plication.
Fault Ma nagement hotspots open up a s c ree n at the next ha rdware layer.
For example:
If you are at this
layer …
SwitchCabinet iconCabinet
CabinetCircuit pack co deCircuit pack
Circuit packPort numbe rPort
External DevicesExternal d evic e iconIndividual
The port and indi vidual external device layers do not have hotspots because
they are the last layers.
Each window that a hotspot opens is specific to the hotspot itself. For example, if
you click on the Cab inet 1 i c o n in the Switch View, the sys tem opens a window
containing only Cabinet 1 d a t a, as shown in the following figure :
And you click on this
hotspot …
External devices ic o nExternal Devices
Then this layer
display s…
External Device
1-6Issue 2 April 1996
Fault Management’s User Interface
Figure 1-2. Cab inet View
Scroll Bars
Fault Ma nagement uses standard scroll bars. The sc ro ll b a r s ap pear only when
there is more information than can a ppear in the window, such as more cabinets
or more report items. If the window does not include scroll bars, all the relevant
information or dat a is visible in the window.
Close Bu tton
When you click o n th e close button, the system closes the current window and all
open "child" windows.
A child window is a window associated with a lower level or with a report fo r th e
current or l ower level. For examp le, the c i rc u i t pa c k d i splay is the child window
of a specific cabinet level disp lay window.
Issue 2 April 1996
1-7
Introduction
Exit Button
The exit bu t ton end s your Fault Management session. This button is available on
the Startup and Switch View screens.
Accelerator Keys
Accelerat or keys allow you to use the keyboard to execute a menu co m man d
(instead of pointing and clicking with a mouse). Each menu co m m and in Fault
Management has one letter underlined.
To use accelerator keys:
■For top level menus, simu ltaneously press the meta key on your keyboard
and the underlined letter of the menu opt ion .
■For a submenu, press the underlined letter of the menu item.
How to Enter Data
You c a n enter d a t a int o Fault Management screens in the following ways:
■Data typed into fields
■Pull-down lists
■Check boxes
■Radio buttons
Data Typed into Field s
You type data into some fields. You can also copy the dat a from one screen or
report and paste it into a field on another screen.
Pull-down Lists
Many fields have pull-down lists that allow you to select the vali d values fo r that
field.
Field s tha t have pull-down lists look like this:
1-8Issue 2 April 1996
Management Information Base
Check Boxes
Check boxes allow you to turn an option on or off. Y ou can turn on as many check
boxes as you want.
Check boxes look like this:
In this examp le, all the check boxes are turned off.
Radio Bu t ton s
Radio buttons allow you to select one o p tion f rom a list of op t ions.
Radio buttons look like this:
In this examp le, the Ascending radio button is turned on.
Management Information Base
The management information base (MIB) is a da t abase of network management
information. The MI B is located in the following directory:
/usr/OV/OneVision/DG3FM/g3mib.asn1
You c a n p rint the MIB b y using your system’s print comma nd .
Data Refresh
Data refresh is the process Fault Management uses to signal the Proxy Age n t to
refresh its cache, if necessary, and then to rea d the d ata . Once t he Proxy Agent
Issue 2 April 1996
1-9
Introduction
has completed refreshing d a ta from the PBX, Fault Management u pdates the
alarm and circuit p a ck mismatch displays that use the data. This data includes:
■ Alarm dat a■ Error data
■ Bulletin board data■ External devices
■ Cabinet data■ Trunk group
■ Configuration data■ Vintage data
■ DS1
Fault Ma nagement uses the following refresh c a t egories:
■S tartup Re fresh
■Configuration Data Refresh
■Bulletin Boa rd Refresh
■Alarms and Errors Data Refresh
Each refresh process differs sli g h tly fro m the others. The next subsections
describe these op erati ons.
Startup Refresh
Startup refresh can occur when you invoke the application from the NMS. By
default, it occurs automatically on startup. The Fault Management Startup screen
displays the following message indicating the status of the startup refresh.
Refresh in progress, estimated delay 250 seconds, 50
seconds elapsed.
Startup refresh up d a t es the followin g information.
■ Alarm da t a■ Error data
■ Bulletin board data■ External devices
■ Cabinet data■ Trunk group
■ Configuration data■ Vintage data
■ DS1
If the Proxy Agent is unable to connect to the PBX and refresh the data, the
startup refresh fails. In this ca se, the follow ing message a ppears when you
invoke Fault Management fr o m the NMS.
Refresh on startup failed! Continuing with cache data.
Turning Off Startup Refresh
You ca n tur n off the startup refresh op t ion as foll ows:
1-10Issue 2 April 1996
Data Refresh
1. Access the Switch View.
2. Select Options à Setup.
3. Change the value in Refresh Proxy Ag ent On Startup to FALSE.
4. Click Apply.
5. Select Options à Save.
For more information about the Setup screen, refer to the Chapter 3, Customizing
Fault Ma nagement.
Configuration Data Refresh
Config u ration d ata refresh consists of updating all th e c ircuit pack information,
including the circuit pack types and locations, and p o r t inform at ion.
The followin g events cause Fault Ma nagement to refresh the confi g urat ion d a t a.
■The refresh timer for the c i rcuit pack expires.
Fault Ma nagement includes a refresh timer which you can turn off or set
for be tween 1 (one) hour and 1000 hours. The timer is reset before the
refresh process begins.
When the refresh timer expires, Fault Management starts the data refresh.
For more information about changing the timer for the ci rcuit pack refresh
interval, see Changing Time Intervals.
NOTE:
For a c onfi guration refresh, Fault Management close s any open
Ca b inet View and External Devices sc reen and their chi l d windows.
■A user requests a refresh.
See How to Refresh Configuration Data for more informat ion.
Bulletin Board Refresh
Bulletin b o a rd refresh allows you to upd at e the me ss a g es on the Bu llet in Bo ard
screen. These messages originate on the PBX bulletin b oard and are only
updated upon request.
See Bulletin Board and How to Refresh this Screen for more information.
Alarms and Errors Data Refresh
The followin g events cause Fault Ma nagement to refresh the alarms and errors
data:
■Fault Man agem ent receives a trap from the Proxy Agent
Issue 2 A pril 1996
1-11
Introduction
■The alarm and er rors refresh interval has passed
■The alarm poll detected a mismatch between the number of alarms on the
■You request a refresh
NOTE:
Fault Management updates cabinet information only during the startup
refresh proc e ss. If you want to u pdate c a binet information, you must close
Fault Management and re-invoke it from your NMS.
Receiving a Trap
When Fault Man agement receives a trap from the Pr oxy Agent, it refreshes the
alarms an d errors data. A trap can indicate t hat
■The PBX has generated a new major, minor, or warning alarm
■All PB X alarms have be e n c leared
Receiving a trap from the Proxy Agent is the p ri ma ry met h od Fault Management
uses to refresh alarm and error data. However, if the Proxy A gent fails to forward
traps, Fault Management can us e the methods o f ref r es hing data described later
in this ch apt er.
NMS and the number of alarms on the Proxy Age nt.
Figure 1-3. Trap Message
1-12Issue 2 April 1996
Data Refresh
Table 1-1.Field Descriptions for Trap Messages
FieldDes crip tion
Heading InformationThe first line of text, including:
■ The da t e and time that th e P roxy Agent
received the trap
■ The nam e o f t he no d e o n the NM S
LocationThe location of the alarm tha t is relate d to the
trap.
SeverityOne of the followin g alarm states:
■ Major
■ Minor
■ Warning
DescriptionThe MO (ma i ntenance object) name for the
alarmed object.
On Board?Ind icates whether the fa ult is on the
associated circuit pack or on an off-board
element c onnected to the circuit pack.
Valid values are:
■ y = yes
■ n = no
Issue 2 A pril 1996
1-13
Introduction
Figure 1-4. Trap Mess age for Extern al Devices
1-14Issue 2 April 1996
Data Refresh
Table 1-2. Field Descriptions for Trap Messages for External Devices
FieldDes crip tion
Heading InformationThe first line of text, including:
■ The da t e and time that th e P roxy Agent
received the trap
■ The nam e o f t he no d e o n the NM S
LocationThe location of the alarm tha t is relate d to the
trap.
SeverityOne of the followin g alarm states:
■ Major
■ Minor
■ Warning
DescriptionThe MO (ma i ntenance object) name for the
alarmed object.
On Board?Ind icates whether the fa ult is on the
associated circuit pack or on an off-board
element c onnected to the circuit pack.
Valid values are:
■ y = yes
■ n = no
External Device
Information
A heading that identifies the fields for external
devices.
Alternate Nam eThe n ame of the ext ernal device.
DescriptionThe description of the external device.
BuildingThe nam e o f t h e building that the external
device is in.
AddressThe mailing ad d re ss fo r the b uil ding.
Product IDThe id entification number for the external
device.
Issue 2 A pril 1996
1-15
Introduction
Figure 1-5. Trap Message for Resolved Alarms
Table 1-3. Field Descriptions for Trap Messages for Resolved Alarms
FieldDes crip tion
Heading InformationThe first line of text, including:
ALL ALARMS
RESOLVED
Alarm and Error Refresh Interval
Fault Management periodically polls the P BX for alarm and error information. The
interval of time specified in the Alarm and Error R efr esh I nterval field on the S etup
sc reen de t er mi nes how often polli ng o cc urs. When the amount of time sp ecified
in this field passes, Fault Ma nagement sta rts the data refresh. The cycle begins
again when Fault Management completes the refresh.
Fault Ma nagement allows you to:
■ Set this time interval for anytime from 5 and 1500 m inut es
■ Turn off p olling for alarm and error data
For more information about changing the interval for the alarm and error refresh,
see Changing Time Intervals.
■ The da t e and time that th e P roxy Agent
received the trap
■ The nam e o f t he no d e o n t he N MS
Trap messag e tha t in d icates all alarms have
been cleared.
1-16Issue 2 April 1996
Data Refresh
Detecting a Mismatch
Fault Ma nagement periodically polls the P roxy Agent for the following MIB
objects:
■ healthMajor
■ healthMinor
■ healthWarning
■ snmpOutTraps
Mismatches in the application view of the values of these object s results in a
refresh.
For the MIB-II object snmpOutTraps, Fault Management compares the number of
traps in the initial sta rt u p poll p lus the traps received to the number of traps in
subsequent polls. Any difference between the two indicates the need for a
refresh.
Fault Ma nagement allows you to:
■ Set this time interval for anytime from 1 and 60 min ute s. When the interval
has passed, Fault Management starts pollin g th e MI B objects from the
Proxy Agent.
■ Turn off p olling for MIB objects.
For more information about changing the interval for alarm polling on the Proxy
Agent, see Changing Tim e Intervals.
Requesting a Refresh
Fault Ma nagement allows you to refresh alarm and error da ta manuall y, as
follows:
1. Open the Switch View.
2. From the menu bar, select Faul t àRefresh Alarms and Errors.
Issue 2 A pril 1996
1-17
Starting/Stopping Fault Management
This chapter describes:
■ Star t ing Fault Mana g emen t
■ The Sta rtu p Screen an d it s messages
2
■ The Sta r tup Process (an overview)
■ Stopping Faul t Manage me nt
Starting Fault Management
Fault Ma nagement is an application hosted by your NMS. Because Fault
Management is integrated into your NMS, when you add a DEFINITY PBX as a
node on your NMS, the system creates DEFINITY G3 Faul t Management as an
executable app licat ion.
You use the node icons on the NMS map to start Fault Management. Double click
on the following icon for the procedure for starting Fault M a nagement:
:
Issue 2 Apri l 19962-1
Loading...
+ 123 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.