Avaya PeriView Reference Manual (Software Release 2.1) - Business Communications Manager Instrukcja Użytkownika Strona 265
- Strona / 288
- Spis treści
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
Alarm Viewer
# P0602566 Ver: 2.7 Page 251
Source of Alarm Information
The Alarm Viewer receives alarm text messages from alarm daemons (alarmd) that
execute on nodes to which the Viewer is currently connected. Alarm daemons are
node-specific. A single alarm daemon collects alarm information for all alarms
generated on a node.
This information is then written to component-specific default alarm log files for the
components that reside on the node. For additional information about alarm log files,
see Default Alarm Log Files on page 251.
Alarm definitions are stored in the alarm database, which is node-specific and should
contain alarms for all components configured for the node. Each node’s alarm
database resides in the following locations.
Solaris: $MPSHOME/common/etc
Windows 2000:%MPSHOME%\common\etc
Live alarms display as they are received from alarm daemons (alarmd). Logged
alarms display from the file in which they have been recorded.
The Alarm Viewer can display Live Alarms and the default Alarm Log Files. While
live alarms display as they are received, you must select alarm log files for viewing
before you can view them.
Use the View menu button to select the type of alarm log files to view. When logged
alarms display, the log file path name is identified with the title of the Alarm Log File
Viewer window.
Live Alarms
Alarm text messages display as live alarms in the Alarm Viewer window, as they are
received from the node-specific alarm daemons (alarmd) executing on the nodes to
which the Viewer is connected.
Alarm Viewer can apply with an alarm filter so, only the live alarms that pass the filter
will show in Alarm Viewer.
The information that is recorded in alarm log files is subject to the live alarm filtering
properties that were in use during logging. You can view these files in the Alarm Log
File Viewer window.
For additional information, see View Live Alarms on page 255.
Default Alarm Log Files
A component-specific default alarm log file is automatically created by each
component as part of the initial boot-up process. This file contains a continuous record
of all alarms, for that component, that were collected by the node’s alarm daemon
(alarmd).
Alarms on a node log by alarmd, based on the severities of these alarms. There are
three categories of alarm severities: info, warning, and alarm. Component-
specific default alarm log files are named in the following format:
Syntax:
info.<component_type>.<component_number>.log
- PeriView Reference Manual 1
- Table of Contents 3
- Page iv # P0602566 Ver: 2.7 4
- Page vi # P0602566 Ver: 2.7 6
- Intended Audience 10
- How to Use This Manual 10
- Organization of This Manual 11
- Trademark Conventions 13
- Working with 15
- PeriView 15
- Introduction to PeriView 16
- Working with PeriView 17
- PeriView Work Environment 18
- Components in the MPS 19
- Start PeriView and Login 21
- Client Based 21
- Browser Based 21
- Understanding PeriView 25
- Navigating PeriView 26
- Toolbars 26
- Right-click Menus 26
- Screen Tips 26
- PeriView Toolbars 27
- PeriView Menus 29
- The Navigation Pane 33
- Tree Objects and Their States 35
- Tree Objects 35
- Tree Object States 36
- User Manager 39
- Introduction to User Manager 40
- User Manager—User Tab 41
- Add a new User 41
- Remove a User 45
- Setting User Properties 46
- Setting User Privileges 50
- Membership Management 53
- User’s Advanced Properties 56
- Setting Password 59
- Configuring Global Properties 60
- User Manager—Group Tab 62
- Adding a new Group 62
- Remove a Group 64
- Setting Group Properties 65
- Setting Group Privileges 68
- Member Management 71
- Group’s Advanced Properties 74
- Application 77
- Configuration 77
- Configurations Options 79
- Application Configuration 101
- Application Manager 121
- Click to remove 125
- Magnifier tool 127
- Expand and Collapse the Tree 129
- Tree Object Information 130
- # P0602566 Ver: 2.7 Page 117 131
- Types of Applications 132
- Types of Phone Lines 133
- File Location Requirements 134
- Assign Action 137
- Start and Restart Action 139
- Terminate or Unassign Action 141
- Reorder Action 147
- # P0602566 Ver: 2.7 Page 139 153
- # P0602566 Ver: 2.7 Page 141 155
- Status Tools 159
- Working with the Status Tools 161
- Overview 163
- Phone Line Status 164
- Phone Line Status Graph Types 168
- Linked Graph Properties 177
- Component Span Status 181
- Component Host Status 187
- MPS Control Center 193
- MMDP Configuration 195
- Adding a Data Provider 196
- Removing Data Provider 202
- Adding Monitored System 206
- Removing Monitored System 207
- MPS Configuration 211
- MMF Configuration 218
- VOS Configuration 220
- VpsHosts Configuration 221
- Cluster Configuration 222
- IPML Configuration 222
- Telephony Link Server 229
- CCT-IVR Integration 234
- CTI Connection to the IVR 248
- TAPI Connection to the IVR 257
- Alarm Viewer 261
- Source of Alarm Information 265
- Live Alarms 265
- Default Alarm Log Files 265
- Alarm Viewer Window 267
- Alarm Information 267
- View Live Alarms 269
- View Default Alarm Log Files 270
- Filter Alarms 272
- Creating a Filter 273
- Simple Filter 273
- Advanced Filter 275
- Saving a Filter 278
- Filtering Alarm Log Files 279
- Configuring Data 281
- Provider for PeriView 281
- Introduction 282
- Netscape for Solaris 283
- Installation 283
- Installing Java Plug-in 284
Powiązane produkty i podręczniki dla Oprogramowanie Avaya PeriView Reference Manual (Software Release 2.1) - Business Communications Manager
(690 strony)© 2020, manymanuals.pl. Wszelkie prawa zastrzeżone. | 0.052 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji