March 2003
ã Copyright 2003 Hewlett-Packard Company
Edition: 5.0-2
for the UNIX Operating System
hp OpenView TeMIP
Event Logging
User’s Guide
Legal Notices
Warranty
Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
A copy of the specific warranty terms applicable to your Hewlett-Packard product can be obtained from your local Sales and Service Office.
Restricted Rights Legend
Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause in DFARS 252.227-7013.
Hewlett-Packard Company United States of America
Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2).
Copyright Notices
©Copyright 2000-2003 Hewlett-Packard Company, all rights reserved.
No part of this document may be copied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. The information contained in this material is subject to change without notice.
Trademark Notices
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. Java™ is a U.S. trademark of Sun Microsystems, Inc.
Microsoft® is a U.S. registered trademark of Microsoft Corporation. Netscape is a U.S. trademark of Netscape Communications Corporation. NMOS™ is a trademark of RiverSoft Technologies Limited.
Oracle® is a registered U.S. trademark of Oracle Corporation, Redwood City, California. Oracle7™ and Oracle7 Server™ are trademarks of Oracle Corporation, Redwood City, California.
PostScript® is a trademark of Adobe Systems Incorporated. Riversoft™ is a trademark of RiverSoft Technologies Limited. UNIX® is a registered trademark of The Open Group.
Windows® and Windows NT® are U.S. registered trademarks of Microsoft Corporation. X/Open® is a registered trademark, and the X device is a trademark of X/Open Company Ltd. in the UK and other countries.
All other product names are the property of their respective trademark or service mark holders and are hereby acknowledged.
Contents
Preface ... 5
Chapter 1
Introduction ...7
1.1 Event Collection... 7
1.2 Event Logging... 8
1.3 Event Record Classes ... 8
1.4 OSI System Object ... 9
1.5 Event Log States ... 10
1.6 Event Record Retrieval ... 12
1.7 Time Modes ... 12
1.8 TeMIP Process Architecture ... 12
1.8.1 Foreground Process ... 12
1.8.2 Background Processes... 13
1.9 Framework Command Line Interface ... 13
1.10 System Considerations ... 14
1.10.1 Full Entity Name for Alarm Rules ... 14
1.10.2 Maximum Event Size ... 14
1.11 Low Level Filtering of Events ... 14
Chapter 2
Defining The Event Logging Environment ... 15
2.1 Event Logging in a Distributed System ... 15
2.1.1 Distributed Configuration Example ... 16
2.1.2 How to Configure a Distributed System ... 17
2.2 ASCII Synonym Support ... 19
2.2.1 Customization ... 20
2.2.2 Creating ASCII Synonyms... 20
2.2.3 ASCII Synonym Display... 20
2.3 Preconditions... 21
2.4 Creating and Defining an Event Log on Tru64 UNIX ... 21
2.5 Event Log Arguments ... 23
2.5.1 Associated Domain ... 23
2.5.2 Discriminator Construct ... 23
2.5.3 Scheduling Package ... 23
2.5.4 Reference Log Name ... 23
2.5.5 Initial Administrative State ... 23
2.5.6 Max Log Size ... 24
2.5.7 Capacity Alarm Threshold ... 24
2.5.8 Log Full Action ... 25
2.5.9 Repository Location ... 25
2.6 Event Filtering ... 25
2.7 Event Collection Scheduling ... 26
2.8 Using the Framework Command Line (FCL) ... 26
Chapter 3
Managing Event Logging... 27
3.1 Managing the Event Logging Environment... 27
3.2 Accessing the Event Log ... 27
3.3 Starting and Stopping Event Logging ... 28
3.4 Displaying the Event Log Attributes ... 29
3.5 Changing the Event Log Attribute Values ... 30
3.6 Self-Monitoring ... 31
3.7 Event Log Panel Window ... 32
3.7.1 What the Window Shows... 32
3.7.2 Viewing Event Records... 34
3.7.3 Management Operations From the Window on Tru64 UNIX ... 34
3.7.4 The Menu Bar ... 34
3.7.5 The Buttons ... 34
Chapter 4
Handling Event Records ... 35
4.1 Using The Mouse ... 35
4.2 Desktop Manager Window on Tru64 UNIX ... 37
4.3 Viewing Event Records on Tru64 UNIX ... 38
4.3.1 Stand-Alone Operation ... 38
4.3.2 Segmented Retrieval ... 39
4.3.3 Event Records View Window Menu Bar ... 39
4.3.4 Event Record Information Displayed ... 41
4.3.5 The Event Records View Window Buttons ... 42
4.3.6 Refreshing the Display ... 43
4.4 Using the Search Events Function ... 43
4.4.1 Selecting Search Criteria ... 44
4.4.2 Expanding a Search ... 46
4.5 Handling Event Records ... 47
4.5.1 Displaying Full Information ... 47
4.5.2 Displaying Other Records... 48
4.5.3 Printing Event Record Information ... 48
4.5.4 Printing Event Record Information to File ... 49
4.5.5 Deleting Event Records ... 49
Chapter 5
Online Customizing Options ... 51
5.1 Introduction... 51
5.2 Changing the Default Printer ... 51
5.3 Changing the Segment Size Value ... 52
5.4 Saving Window Sizes ... 53
5.5 Customizing the Event List ... 53
5.6 Search Scope Dependence ... 54
5.7 Saving the New Values ... 56
Chapter 6
User Messages ... 57
6.1 TeMIP Framework Exception Messages ... 57
6.2 TeMIP Internal Error Messages ... 58
6.3 User Information Messages ... 58
Appendix A Operation Context and Log Error Messages ... 59
A.1 List of Error Messages ... 59
Preface
This document explains how to configure and use the TeMIP Fault
Management Event Logging function. It contains information related to the TeMIP Event Logging FM and the associated GUI (TeMIP Event Logging PM), accessible from the TeMIP Client.
All references to the TeMIP Iconic Map are for Tru64 UNIX only.
Supported Software
The supported software referred to in this document is as follows:
The term UNIX is used as a generic reference to the operating system, unless otherwise specified.
Typographical Conventions
Courier Font:
• Source code and examples of file contents. • Commands that you enter on the screen. • Pathnames
• Keyboard key names
Italic Text:
• Filenames, programs and parameters.
• The names of other documents referenced in this manual. Bold Text:
• To introduce new terms and to emphasize important words.
Associated Documents
The following documents contain useful reference information: • OpenView TeMIP Product Family Introduction.
• OpenView TeMIP Customization Guide.
• OpenView TeMIP Iconic Map and FCL User’s Guide.
• OpenView TeMIP Director Configuration Management Guide.
• OpenView TeMIP Fault Management Reference Guide.
• OpenView TeMIP Alarm Handling User’s Guide.
TeMIP UNIX
HP OpenView TeMIP
Alarm Handling and Event Log Server 5.0
HP Tru64 UNIX Sun Solaris HP-UX
• OpenView TeMIP Classic Alarm Handling Client User’s Guide.
• OpenView TeMIP Event Filtering and Correlation User’s Guide.
For a full list of TeMIP documents, refer to Appendix A of the OpenView
TeMIP Product Family Introduction.
Support
Please visit our HP OpenView web site at: HP OpenView
There you will find contact information as well as details about OpenView products, services and support.
The OpenView support area of the OpenView web site includes: • Downloadable documentation
• Troubleshooting information • Patches and updates
• Problem reporting • Training information
Chapter 1
Introduction
This chapter introduces general information about the TeMIP Event Logging function. Topics covered are:
• Section 1.1 Event Collection • Section 1.2 Event Logging • Section 1.3 Event Record Classes • Section 1.4 OSI System Object • Section 1.5 Event Log States • Section 1.6 Event Record Retrieval • Section 1.7 Time Modes
• Section 1.8 TeMIP Process Architecture
• Section 1.9 Framework Command Line Interface • Section 1.10 System Considerations
• Section 1.11 Low Level Filtering of Events
1.1
Event Collection
The TeMIP Event Logging function is concerned with the collection and storing of all types of OSI events occurring in the network. Once stored, the event information can later be retrieved and used for analysis or whatever processing is required by the fault management system. Even status changes of Event Logs themselves (and operation contexts) are events that can be logged by the Event Logging function.
Instances of the Event Log
Multiple instances of Event Logs can be created, each with its own event collection characteristics. This enables the event traffic to be filtered and collected in different ways, to suit the various requirements of your
particular fault management scheme. In each Event Log instance that you create, the Discriminator Construct and Scheduling Package provide you with the means for defining the way in which events are filtered and when they are collected.
Background Event Collection
When event collection has been started for an Event Log (the
Administrative State of the Log set to Unlocked), the collection of events
continues without user intervention. Events are collected according to how the Discriminator Construct and Scheduling Package are defined, until
event collection is specifically stopped, through one of the following conditions:
• The Administrative State is changed to Locked by the user. • The Operational State is changed to disabled due to management
module or service malfunction. • The Event Log becomes full.
• The scheduled period of logging activity is over.
1.2
Event Logging
TeMIP is based on object-oriented technology and makes use of two OSI compliant support objects in the Event Logging process. These are the Log Object and the Log Record Object. The Log Object controls the way in which event collection is carried out, and also provides the repository for the Log Record Objects. The Log Record Object enables the user to handle and manipulate the event information through the user interface.
Events that are successfully collected, that is, events that pass through the discriminator filter during a scheduled period of logging activity, are stored by the Event Log in a repository as OSI-compliant Event Records. You define the location of the repository when creating an Event Log by assigning an appropriate UNIX path name.
Note
In this user guide, the Log Object and Log Record Object are referred to less formally as the Event Log and Event Record respectively.
TeMIP logs events according to how you have constructed and configured the Event Logging function. As a user of the Event Logging function you therefore need to know how to:
• Set up the Event Logging environment - Create and define Event Log instances
- Set the event collection characteristics of the Event Log • Control the Event Logging activity:
- Start or stop the Event Logging activity - Change the Event Logging characteristics • Handle the event data:
- Retrieve event records from the database - Display, print or delete the event records
1.3
Event Record Classes
Different types of events occurring in the network produce event records with differing information formats. The OSI standards define seven possible classes of events, and these are supported by the TeMIP Event
• Alarm record
• Security alarm record • Object creation record • Object deletion record
• Attribute value change record • State change record
• Relationship change records Generic Record Class
In additional to the seven OSI-defined record classes, TeMIP supports one extra class, identified as Log Record. The purpose of the Log Record class is to assist in the retrieval of event records from the repository. The Log Record class performs a "wildcard" function by allowing you to make a search through all event record classes in a single operation. See Section 1.6 for an explanation and an example of usage.
1.4
OSI System Object
TeMIP Event Logging function makes use of the OSI-defined OSI System Object to support Event Logging. When you create an instance of an Event Log it is created as a Child of the OSI System Object class. The OSI System Object is a global entity class. The Event Log hierarchy is shown in Figure 1-1.
Figure 1-1 The Event Log Hierarchy
Local OSI System
The OSI System represents the current system where the TeMIP
Operations System (OS) is located. Therefore, a single OSI System Object is created and registered on each TeMIPdirector that is installed in the network. During the setup and configuration process (see the OpenView
TeMIP Director Configuration and Management Guide), a name is assigned
to identify the "local" instance of the OSI System, which is usually the same name as your local node or processor.
You can only create an Event Log as a child of a Local OSI System.
However, you can create an Event Log as a child of a Local OSI System on a remote Director.
OSI System Directives
Five directives are provided for the OSI System:
• Show, to return the identifier attributes of the OSI System • Register, to register the current OSI System
• Deregister, to de-register the current OSI System • Create, to create an OSI System
• Delete, to delete an OSI System Creating the OSI System in the Domain
In order to create Event Logs in a given domain, the local OSI System must be added to the domain map. This is done in the same way as creating any other entity on the domain map using the TeMIP Graphics Toolbar. When you create the OSI System, TeMIP verifies that the entity class is
registered and allows you to add the OSI System icon to the domain map.
1.5
Event Log States
The event collection capability of an Event Log depends on the Log's two states, which are the:
• Administrative State • Operational State
The Administrative State and Operational State of the Event Log together determine whether the Log's ability to collect events is Enabled or Disabled.
The Administrative State
The Administrative State of the Event Log is controlled by the user through directives that are available at the TeMIP management interface. These directives are:
• Suspend
- Puts the Event Log into the Locked state and disables event collection.
• Resume
- Puts the Event Log into the Unlocked state and enables event collection.
• Delete
- Puts the Event Log into the transient state of ShuttingDown as the delete operation is carried out.
See Table 3-7 for a summary of the operations that are possible in the
Locked and Unlocked Administrative States.
The Operational State
The Operational State of the Event Log is governed by internal incidents, such as:
See also Section 3.7.1. The Availability Status
The Availability Status is an Event Log attribute that provides additional information concerning the Operational State. The Operational State is dependent on the availability of other modules and services. A situation could arise, where a service that is not essential becomes unavailable, and in this case the Operational State could be reduced in effectiveness
(degraded), but not disabled. In other words, the Operational State is qualified according to the Availability Status of external support. The
Availability Status is indicated in the Event Log Panel window.
For Example: If TeMIP detects that:
• An event has been lost (checked by the event manager and reported by the Notification FM)
or
• A remote director has been stopped during collection of an alarm/event it assumes that a problem has occurred that has reduced the reliability of the event collection mechanism. In this case the Availability Status is set to
degraded to indicate a possible collection capability of less than 100%.
The Availability Status remains degraded until the problem is cleared using the Cleanup directive, available from the Event Log Panel window
Operation menu (LOG Directives... entry). This resets the Availability Status and its associated Error Condition Explanation. Note that a State Change event is generated.
See also Section 3.7.1.
The possible Availability Status indications are given in Table 1-1. Table 1-1 Availability Status
Operational State
Possible Status Indications
Comment
Enabled No indication All OK
Degraded A transient problem was detected but collection is still running
Off duty Scheduling in operation, an inactive interval Disabled Failed A fatal processing error, collection stopped
Dependency Non-fatal processing error, but collection stopped
Log Full The Event Log is full
Failed, Dependency Values as described above
Failed, Log Full Values as described above
Failed, Dependency, Log
Full
Values as described above
In Test The TeMIP Event Logging function is
starting up
1.6
Event Record Retrieval
In order to retrieve and view event record data from the repository, it is necessary to specify the class of records to be searched. When you first select the View Event Records option from the TeMIP Client, TeMIP automatically begins to retrieve all event records, by using the Log Record class.
You can restrict the scope of the search by specifying the event record class to be searched, within the set of seven defined sub-classes, plus other criteria such as event type and so on.
Generic Searches using the Log Record Class
In some cases, the need to specify a particular event record class for a search is somewhat restrictive. For example, suppose you needed to retrieve and analyze all events that occurred during a certain period of time. Using the OSI-defined record classes, you would need to carry out separate searches through each of the seven classes.
The Log Record class is provided for this type of situation. By specifying
Log Record as the class to be searched, the search is actually made through
all the event record classes. The Log Record class effectively provides a "wildcard" function for event record searches.
1.7
Time Modes
During TeMIP configuration you are asked to specify default input and output time modes. If you want to change this format later, you can do so by changing the time mode variables contained in the configuration file
.temip_config, located in the directory /var/opt/temip/conf. Refer to the OpenView TeMIP System Reference Manual for further details.
1.8
TeMIP Process Architecture
This section gives a brief explanation of the TeMIP process architecture, to help in the understanding of TeMIPoperation and the use of certain utility programs. There are two categories of TeMIPprocess that need to be considered:
• Foreground Process
- The TeMIP Function Module process that runs under the
director_user_name of the individual TeMIP users (Foreground
process Userid = director_user_name). • Background Processes
- Alarm and event collection management processes that run under TeMIP itself (Background process Userid = director_user_name).
1.8.1 Foreground Process
The foreground process handles the directives that the user requests through a user interface.
1.8.2 Background Processes
Background processes provide support for all users of the TeMIP functions and are further divided into two groups:
1. Server Process
- The Event Logging FM has a single server process that handles the creation and deletion of Event Log instances. The server process also creates and performs general management of the Child processes.
2. Child Processes
- Child processes are created to handle event collection for each Event Log. There are as many child processes as there are instances of Event Logs. The child processes also manage the status of the Event Logs with which they are associated.
The background processes are common to all TeMIP users. For example, if the Event Logging background processes are stopped, the Event Logging function is disabled for all users. Figure 1-2 illustrates the TeMIP process structure.
Figure 1-2 Event Logging Process Architecture
1.9
Framework Command Line Interface
The FCL is a standard TeMIP Framework Presentation Module that is available to the TeMIP user. It is a simple command line facility that enables the TeMIP Framework User Commands to be entered from character cell terminals.
The FCL makes possible the management of TeMIP from almost anywhere in the network. This is convenient for management personnel who may
need access while temporarily away from the normal X-Windows workstations with only a character cell terminal available. Starting the FCL
At the UNIX prompt, type manage:
This will produce the TeMIP Framework prompt:
You can now use any of the FCL commands to manage the Event Logging function.
1.10
System Considerations
This section provides a number of practical points to consider in the configuration and usage of TeMIP.
1.10.1 Full Entity Name for Alarm Rules
When defining alarm rules you must use the FullEntityName identifier of the instance. This is because the TeMIP PM uses Target Entity or Managed Object values to work with, but waits for a full name.
1.10.2 Maximum Event Size
The maximum event size that can be handled by the Event Log FM is 64 K-bytes.
1.11
Low Level Filtering of Events
In TeMIP, filtering of events takes place at two levels, a low level and a high level. High level filtering takes place at the level of the Log entity, which provides a particular view of network activity. Low level filtering takes place at source and is designed to prevent a flood of events arriving at the user interface in the event of a problem.
Several types of low level filter can be defined, to provide you with the flexibility to use filters that suit a particular type of problem or that match your specific network requirements.
A detailed description of how to create, use and manage Event Filters is given in the OpenView TeMIP Event Filtering and Correlation User’s Guide.
> manage
TeMIP Framework (V5.0.0) TeMIP >
Chapter 2
Defining The Event Logging
Environment
This chapter explains how to set up the event logging environment after the installation process is completed. Topics covered are:
• Section 2.1 Event Logging in a Distributed System • Section 2.2 ASCII Synonym Support
• Section 2.3 Preconditions
• Section 2.4 Creating and defining an Event Log • Section 2.5 Event Log Arguments
• Section 2.6 Event Filtering
• Section 2.7 Event Collection Scheduling.
2.1
Event Logging in a Distributed System
Distributed event logging enables you to access and monitor Logs located on remote nodes (or Directors). The Log Panel window (launched from the TeMIP Client) opens and displays a list of all the registered Logs known to the system for the selected OSI System, see Section 3.7. You can choose the Logs you want to monitor from this list regardless of whether they are managed by a local Director or a remote Director. If you select more than one OSI System, a Log Panel window is opened for each OSI System. In TeMIP Event Logging, access to remote Logs is based exclusively on
Entity Access Distribution. This uses the Managing Director attribute,
allocated at OSI System registration time, to locate the Director on which the Log exists. This Director is designated as the Managing Director for the OSI System parent entity and is responsible for all call requests and responses to and from it. Note that the Director holding the OSI System (and its associated Log and Log Record repository), may not be the Director holding the domain associated with the Log.
Refer to the following documents for more detailed information on TeMIP distribution:
• OpenView TeMIP Product Family Introduction
2.1.1 Distributed Configuration Example
Figure 2-1 shows an example of a simple configuration that has a log_A01 associated with domain_A0. These two entities are located on Director
Toledo.
A log_B21 associated with domain_B2 is located on Director Madrid;
domain_B2 is also a subdomain of domain_A0.
In this configuration, the distribution of TeMIP allows you to use a Presentation Module situated on either Director to:
• Monitor transparently and in real-time, any Event Log situated locally or remotely.
• Monitor transparently and in real-time, any domain, its subdomains and members situated locally or remotely.
• Access transparently any entity in the distributed system and perform (allowed) management operations on it.
• Access transparently the Event Log Record repository information of any datastore in the system.
The only condition is that the target OSI Systems must have a Managing
Director assigned to them to grant access and handle the calls. Once you
have created an entity and assigned a Managing Director, the entity is always accessed through this Director using Entity Access Distribution.
Figure 2-1 Distributed Event Logs (only on Tru64 UNIX using IMPM)
2.1.2 How to Configure a Distributed System
You can configure your system in three ways: • From the Iconic Map (only on Tru64 UNIX) • From the FCL PM.
• From the TeMIP Map Editor Client. For more details refer to the
2.1.2.1 Configuring from the Iconic Map on Tru64 UNIX
Refer to Section 2.4 for details of how to create Event Logs from the Iconic Map. For details of how to create domains and domain members, refer to the OpenView TeMIP Iconic Map and FCL User’s Guide.
2.1.2.2 Configuring from the FCL
You may want to populate your database from the FCL using a script file. However, you must take care to ensure that the entities are created on the correct Managing Director. Correct configuration requires a "partial registration" to be done before the entity is created; otherwise the
Managing Director of the entity you are about to create is not known to
TNS. If the Managing Director attribute is not defined, the default value is used, which is the Director from where you issue the command.
The following example shows the steps involved to create the configuration shown in Figure 2-1.
1. Use the following commands to "partially register" domain_A0 and
domain_B2 in TNS specifying a Managing Director for each domain:
2. Use the following commands to create the domains domain_A0,
domain_A1 and domain_B2:
If these commands are entered alone, the domains are created on the local Director.
3. Use the following commands to "fully register" the domains domain_A0,
domain_A1 and domain_B2:
4. Use the following commands to create domain_B2 as a subdomain of
domain_A0:
5. Use the following command to "partially register" the OSI System osi_A in TNS with the Managing Director Toledo:
register domain palerm_ns:.domain_A0 Operation = plan,
Managing Director = palerm_ns:.temip.toledo_director register domain palerm_ns:.domain_B2
Operation = plan,
Managing Director = palerm_ns:.temip.madrid_director
create domain palerm_ns:.domain_A0 create domain palerm_ns:.domain_B2
register domain palerm_ns:.domain_A0 register domain palerm_ns:.domain_B2
create domain palerm_ns:.domain_A0 member palerm_ns:.domain_B2
register OSI palerm_ns:.osi_A Operation = plan,
6. Use the following command to create the OSI System osi_A:
7. Use the following command to "fully register" the OSI System osi_A:
8. Use the following command to "partially register" the OSI System osi_B in TNS with the Managing Director Madrid:
9. Use the following command to create the OSI System osi_B:
10. Use the following command to "fully register" the OSI System osi_B:
11. Use the following command to create log_A01 and associate it with
domain_A0:
12. Use the following command to create log_B21 and associate it with
domain_B2:
13. OSI Systems can be defined as members of domain(s) that are managed by different Directors. You can define OSI Systems as members of domains using commands such as the following (these commands are not represented in Figure 2-1):
2.2
ASCII Synonym Support
ASCII synonyms enable you to define an alternative name (synonym) for the entities that exist in your TeMIP system, and display this name in any Presentation Module (PM) or application capable of displaying TeMIP entities.
An ASCII synonym can be associated with an entity specification to provide a platform wide instance naming alternative, including user friendly names. An alternate naming system could, for example, involve the use of
create OSI palerm_ns:.osi_A
register OSI palerm_ns:.osi_A
register OSI palerm_ns:.osi_B Operation = plan,
Managing Director = palerm_ns:.temip.madrid_director
create OSI palerm_ns:.osi_B
register OSI palerm_ns:.osi_B
create OSI palerm_ns:.osi_A log log_A01 Associated Domain = palerm_ns:.domain_A0, INITIAL ADMINISTRATIVE STATE = locked
create OSI palerm_ns:.osi_B log log_B21 Associated Domain = palerm_ns:.domain_B2, INITIAL ADMINISTRATIVE STATE = locked
create domain palerm_ns:.domain_A0 member palerm_ns:.osi_A create domain palerm_ns:.domain_B2 member palerm_ns:.osi_B
shorter names, which avoids "crowding" of the display, especially in the case of large networks displaying many entities. For example, the entity:
could be represented by the synonym:
2.2.1 Customization
ASCII synonym support can be configured on a director (global) or application (specific) basis using the environment variables:
• TEMIP_SYNO_ASCII_USE
• <APPLI_NAME>_SYNO_ASCII_USE
You can use these variables to set the display of ASCII synonyms to On or
Off. The default value is Off (disabled). For further details of synonyms and
the environment variables you can use to customize the ASCII synonym behavior, refer to the OpenView TeMIP Customization Guide.
2.2.2 Creating ASCII Synonyms
ASCII synonyms can be created using the Iconic Map PM Add Entity function or by directly inputting commands at the FCL PM. Refer to the
OpenView TeMIP Iconic Map and FCL User’s Guide for further details.
2.2.3 ASCII Synonym Display
ASCII synonyms are supported for the following windows: • Event Records View window; see Section 4.3.
• Search Event Records window; see Section 4.4.
The following fields support ASCII synonyms in the two windows listed above:
• Managed Object
• Target Entity
• Domain
Figure 2-2 shows an example of the Event Records View window with synonyms displayed for the Managed Object and Domain fields.
NETWORK daz1 NE 28 SHELF 3 SLOT 4 DEVICE 12a
Figure 2-2 Synonyms in the Event Records View Window
2.3
Preconditions
In Section 2.4 to Section 2.7 the following assumptions have been made: • The Local OSI System object has been created and registered; see the
OpenView TeMIP Director Configuration and Management Guide.
• The management domain in which you will be working is defined and populated.
2.4
Creating and Defining an Event Log on
Tru64 UNIX
The basic steps required to create a new Event Log instance are as follows: 1. Select and display the required domain
2. Double click on the OSI System to display the next lower level - The Children of the OSI System are displayed (LOG)
3. Click on the No Entry icon in the top right-hand corner of the Iconic Map window to unlock and display the Graphics Toolbar and the Add Entity icon at the bottom of the window.
4. Either click on the Add Entity icon or select Add Entity from the Edit pull-down menu - the Add Entity window opens.
5. Double click on OSI_SYSTEM in the left-hand panel to display the child entities and then select LOG - The Event Log Create form is displayed.
You can also select the icon you want to use for this Event Log in the right-hand panel.
6. Enter the LOG creation arguments.
7. Add the new Event Log to the domain in the map window. 8. Add the new Event Log to the Event Log Panel window.
Figure 2-3 shows the Event Log Create Form that enables you to define the Event Log arguments.
Figure 2-3 The Event Log Creation Form
Note
1. An argument name in bold typeface means that a value must be provided (mandatory field).
2. If you add an entity to a domain with which an Event Log is already associated and collecting events, events from the new entity will not be taken into account until you perform a Suspend, then a Resume on the Event Log. This is a feature of the TeMIP Framework Notification FM.
2.5
Event Log Arguments
The Event Log arguments are described in Section 2.5.1 to Section 2.5.9.
2.5.1 Associated Domain
Description: Name of the management domain with which this Event Log is associated, or the top level domain if this is a domain tree.
Parameter format: Character string Domain_Name. FullName, 404 characters maximum.
Default value: None, this is a mandatory entry.
2.5.2 Discriminator Construct
Description: An event filter to select specified types of event. Parameter format: See Section 2.6.
Default value: No discriminator construct filtering, all OSI compliant
events accepted.
2.5.3 Scheduling Package
Description: When, and for how long, the event collection mechanism is to be active.
Parameter format: See Section 2.7.
Default value: No scheduling, event collection continuously active, On 24
hours every day.
2.5.4 Reference Log Name
Description: This argument allows you to specify an existing Log to be used as reference when creating a new Log. All characteristics of the new Log will be inherited from the referenced Log, with the exception of the Associated Domain Name (mandatory argument) and any other arguments that have been specifically defined in the creation process.
Format: Character string FullName (TeMIP Framework datatype). Default: None.
Example
This command will create the Log Europe_backup, with all its characteristics inherited from Log Europe (for example, Scheduling Package, Discriminator Construct, and so on) except for the Associated Domain name, which will be domain_europe, and the repository location.
2.5.5 Initial Administrative State
Description: The initial state of the Event Log when TeMIP is started. TeMIP> Create Osi_system Local_osi_system Log Europe_backup - TeMIP_> Associated Domain = domain_europe, -
TeMIP_> Reference Log Name = Europe, -
Parameter format: Locked or Unlocked Default value: Unlocked
Note
If the initial Administrative State of the Event Log is set to Locked, you must use the Resume directive to begin event logging.
2.5.6 Max Log Size
Description: The maximum size the Event Log can reach Parameter format: value in Octets
Default value: 100 000
Note
If the value zero (0) is entered, this defines the Max Log Size as "system dependent". This means that all available free disk space will be used.
2.5.7 Capacity Alarm Threshold
Description: At what capacity levels an OSI Processing Error alarm should be generated to indicate that the Event Log is filling up. At each level specified, an alarm is generated relative to the percentage of Max Log
Size.
Parameter format: A set of percentage integer values Default value: {80, 90, 100}
Note
1. The input required for this argument is a SET of integers. When entering values you must click MB3 on the label of the field to begin the assignment, not on the text field itself as is usually the case.
2. Severity levels for the Processing Error alarm are hard-coded to produce the following alarms for the given percentage ranges: • 00 to 39% = WARNING
• 40 to 59% = MINOR • 60 to 79% = MAJOR • 80 to 100% = CRITICAL
If Max Log Size is set to null (0), alarms are generated according to disk usage.
3. When a Log is collecting, a Clearance alarm and/or a Processing
Error alarm may be received. The behavior of the Capacity Alarm
Threshold is as follows:
• When the Capacity Alarm Threshold is crossed, a Processing Error alarm is generated.
• When the storage capacity is returned to a value less than the Capacity Alarm Threshold, a Clearance alarm is generated. • After a TeMIP startup, a Clearance alarm is generated to clear any
previous Processing Error alarm concerning a storage capacity problem. If a storage capacity problem still exists, a new Processing
Error alarm is generated.
• When any characteristic attribute is Set, a Clearance alarm is generated to clear any previous Processing Error alarm concerning a storage capacity problem. If a storage capacity problem still exists, a new Processing Error alarm is generated.
• When a Resume operation is performed, a Clearance alarm is generated to clear any previous Processing Error alarm concerning a storage capacity problem. If a storage capacity problem still exists, a new Processing Error alarm is generated.
2.5.8 Log Full Action
Description: Action to be taken when the Event Log is full. In the present release, logging can only be stopped.
Parameter format: Halt Default value: Halt
2.5.9 Repository Location
Description: The directory path name to where the event records file repository for this Event Log is to be located. This attribute is not settable once defined.
Parameter format: UNIX directory/path name Default value: /var/opt/temip
Note
The repository filename is given by the Event Logging FM itself.
2.6
Event Filtering
The Discriminator Construct attribute defines how event activity is to be filtered for this Event Log instance.
When the Discriminator Construct attribute is selected from the Iconic Map (clicking MB3), a dedicated editor is called that enables you to make the required definitions quickly and easily. Full details on how to use the Discriminator editor are given in the OpenView TeMIP Classic Alarm
Handling Client User’s Guide.
2.7
Event Collection Scheduling
The Scheduling Package attribute defines when event collection by this Event Log instance is to be active.
When the Scheduling Package attribute is selected from the Iconic Map (clicking MB3), a dedicated editor is called that enables you to make the required definitions quickly and easily. Full details on how to use the Scheduling package editor is given in the OpenView TeMIP Classic Alarm
Handling Client User’s Guide.
For further details of DC and SC Editor activation from the TeMIP Map Editor Client, refer to the OpenView TeMIP Client Overview.
2.8
Using the Framework Command Line (FCL)
An Event Log can be created using the FCL interface and all arguments can be entered, including the Discriminator Construct and Scheduling Package; see the OpenView TeMIP Alarm Handling User’s Guide.
If an Event Log is created using the FCL and the Discriminator Construct and Scheduling Package are not given a value, they are assigned their default values, which are - No filtering, all events accepted and On 24 hours every day respectively.
Chapter 3
Managing Event Logging
This chapter describes the management operations you can perform to monitor and control the Event Logging environment. Topics covered are: • Section 3.1 Managing the Event Logging Environment
• Section 3.2 Accessing the Event Log
• Section 3.3 Starting and stopping Event Logging • Section 3.4 Displaying Event Log Attributes • Section 3.5 Changing Event Log Attribute Values • Section 3.6 Monitoring of the Event Logging • Section 3.7 Event Log Panel Window
3.1
Managing the Event Logging Environment
Management of the event logging environment is carried out by means of the Event Log directives (commands). These are described in Table 3-1. By means of the Log directives you can examine the status of the event logging environment and modify the way event collection is carried out by an Event Log. In order to perform a management function on an Event Log, the relevant Event Log must be selected.
3.2
Accessing the Event Log
You can access the Event Log directives from three points: • From the Iconic Map on Tru64 UNIX
• From the Event Log Panel window
• From the TeMIP Map Viewer Client. Refer to the OpenView TeMIP
Client Overview.
The following procedures apply to any management operation you wish to perform on an Event Log:
Accessing from the Iconic Map on Tru64 UNIX 1. Display the required domain map
2. Double click on the OSI System
- The next lower level of the hierarchy is displayed (LOG) 3. Double click on LOG
4. Click on the required Log to select it
5. Select the operation you wish to perform on the Log from the
Operations menu.
Accessing from the Event Log Panel
1. Click on the required Event Log in the list to select it 2. Select LOG Directives... from the Operation menu
3. Select the required directive from the displayed pull-down menu.
3.3
Starting and Stopping Event Logging
Event Logging is controlled from the user interface by means of the directives:
• Suspend • Resume Suspend
The Suspend directive changes the Administrative State of the selected Event Log to Locked. Event collection is stopped. However, the Show, Set and Delete directives are still effective. This directive causes an OSI Status Change event to be generated.
To use the Suspend directive from Iconic Map: 1. Select the required Event Log
2. From the Operations menu select Suspend - The Suspend Form is displayed
3. Click on the Start button to initiate the Suspend directive. The result of the operation is displayed in the Suspend Form window. Resume
The Resume directive changes the Administrative State of the selected Table 3-1 Event Log Management Directives
Directive Effect
Create Creates a new Event Log instance
Delete Deletes an Event Log instance, provided that all event records have been deleted and the Log is in the Locked Administrative State
Suspend Changes the Administrative State to Locked. Event Logging for this Log instance is stopped
Resume Changes the Administrative State to Unlocked. Event Logging for this Log instance is restarted
Set Used to change characteristics of the Event Log that were entered in the Create operation
initial Administrative State of the Event Log at create time was set to
Locked). This directive causes an OSI Status Change event to be generated.
To use the Resume directive from Iconic Map: 1. Select the required Event Log
2. Select Resume from the Operations menu - The Resume Form is displayed
3. Click on the Start button to initiate the Resume directive. The result of the operation is displayed in the Resume Form window.
3.4
Displaying the Event Log Attributes
You display the current attribute values of a selected Event Log by means of the Show directive.
To use the Show directive from Iconic Map: 1. Select the required Event Log
2. Select Show from the Operations menu
3. From the resulting pop-up menu select the attribute group required: - Identifiers (see Table 3-2)
- Characteristics (see Table 3-3) - Status (see Table 3-4)
- Counters (see Table 3-5).
The Show Attributes Form is displayed showing the values of the attributes requested.
The Identifier Attribute
The Identifier Attribute is shown in Table 3-2. Table 3-2 Event Log Identifier Attribute Attribute Comment
The Characteristic Attributes
The Characteristic Attributes are shown in Table 3-3; these are the
attributes whose values are defined during the Create directive, see Section 2.5.
The Status Attributes
The Status Attributes are shown in Table 3-4.
The Counter Attributes
The Log Counter Attributes are shown in Table 3-5.
3.5
Changing the Event Log Attribute Values
You can change the values of certain Event Log attributes by means of the
Set directive, and so modify the event collection characteristics. Note that
Table 3-3 Event Log Characteristic Attributes
Attribute Comment
Domain Name Monitored domain. All the OSI alarms or OSI events generated by entities within this domain are collected. This is a mandatory entry.
Discriminator Construct
Select the Expand option to read the current setting of the discriminator construct
Scheduling Package Select the Expand option to read the current setting of the scheduling package
Max Log Size Maximum number of octets Capacity Alarm
Threshold
Set of percentage values
Repository Location Directory Pathnames of the repository
Log Full Action Halt
Table 3-4 Event Log Status Attributes
Attribute Comment
Administrative State Locked or Unlocked Operational State Enabled or Disabled Availability Status See Table 1-1
Table 3-5 Event Log Counter Attributes
Attribute Comment
Current Log Size The current size of the log, measured in octets Number of Records Shows the current number of records in the log
To change attribute values from Iconic Map: 1. Select the required Event Log
2. Select the Set directive from the Operation menu.
When Set is selected, the Set Attributes Form is displayed, showing the attributes which you are able to change. Enter your new values as appropriate and Click on the Start button to accept them as the current values.
Table 3-6 summarizes the operations that are possible in the two
Administrative States of the Event Log.
3.6
Self-Monitoring
In addition to the monitoring of managed entities in the domain, an Event Log also monitors itself and all other Event Logs in the domain. When operations are performed on an Event log, OSI Events are generated. Table 3-7 summarizes these OSI events.
Table 3-6 Log Administrative Stat Options Summary Event Log Administrative State
Operation Locked Unlocked
Delete Event Records Yes Yes †
Delete Event Log Yes No
Set Attributes Yes Yes †
Show Attributes Yes Yes
Suspend No Yes
Resume Yes No
† This operation can be carried out without loss of events during a Suspend / Resume sequence.
Table 3-7 Summary of Event Log OSI Events OSI Event Operation State Change Attribute Value Change Object Creation Object Deletion Create Event Records - - Yes
-Delete Event Log - - - Yes
Set - Yes -
-Suspend Yes - -
-3.7
Event Log Panel Window
Entry from:
The Event Log Panel window allows you to perform the following: • Monitor the status of the LOGs
- children of the Local OSI_SYSTEM that are included in the Event Logging function
• View selected event records in the LOG repository.
An example of the Event Log Panel window on Tru64 UNIX is shown in Figure 3-1. Note that the LOG Directives... and Open Associated Map Window buttons are not available on the Sun Solaris and HP-UX versions. Figure 3-1 The Event Log Panel Window
3.7.1 What the Window Shows
The following information is displayed in the Event Log Panel window: • Administrative State (Icon, updated in real-time), locked or
unlocked
• Operational State (Icon, updated in real-time), enabled or disabled
Window Operation Remark
Iconic Map (Tru64 UNIX)
Applications menu - TeMIP Event Logging
Opens the Event Log Panel window for the default OSI_System. This method will not function on a TeMIP PM Client because there is no local OSI_System. Iconic Map
(Tru64 UNIX)
Select an OSI_System, then - Monitor Logs from the Operations menu
Opens the Event Log Panel window for the selected OSI_System. This is the only method that will function from a TeMIP PM Client.
Iconic Map (Tru64 UNIX)
Select an OSI_System, then - Select Icon from the Applications bar menu
Opens the Event Log Panel window for the local OSI_System. This method will not function on a TeMIP PM Client because there is no local OSI_System.
• LOG Name (Text) • Domain Name (Text)
• Availability Status (Text) (see below)
• Error Condition Explanation (Text) (see below) • Error Status Text (Text) (see below).
Availability Status Values:
The Availability Status qualifies the Operational State of the Log (Enable/ Disable). When there is no Availability Status displayed, the Operational
State is fully enabled.
If the Operational State is degraded in some way by external conditions, the
Availability Status indicates the cause. The Availability Status values
constitute a set, of which more than one value may be displayed at the same time. The possible values are listed in Table 1-1. The Availability
Status is updated in real-time.
Error Condition Explanation:
This attribute qualifies and refines the Administrative State and the
Operational State of the Log by a text describing the current activity being
processed. The Error Condition Explanation is updated in real-time. Error Status Text:
This attribute qualifies the Error Condition Explanation. When an error is detected in the process, the current (and worst) Status (or CVR) is
displayed. Nothing is displayed if no errors are being detected by the process. The Error Status text is updated in real-time.
The Status Icons
Administrative State is LOCKED
Administrative State is UNLOCKED
Operational State is ENABLED
Operational State is DISABLED
Event Log is being deleted
3.7.2 Viewing Event Records
From the Operation menu of the Event Log Panel window you can open the
Event Records View window to begin a retrieval of event records from the
repository for the selected Log. Select the menu item: View Event Records,; see Table 3-8.
3.7.3 Management Operations From the Window on Tru64
UNIX
From the Operation menu and the buttons you can access the management directives for the selected Event Log (see Table 3-8). This enables you to directly manage the Event Logging environment from the Event Log Panel window.
3.7.4 The Menu Bar
The menu bar contains the items: File, Operation, Help. Table 3-8 summarizes the menu items, preconditions for using the menu items, and the results of selecting them.
3.7.5 The Buttons
The window contains several buttons that allow you to quickly perform some common functions:
• View Event Records, to open up the Event Records View window and display event records
• LOG Directives..., (Tru64 UNIX) to gain access to the directives available for the selected Log.
• Open Associated Map Window, (Tru64 UNIX) to open a domain in the Iconic Map window with which the selected Log is associated. Table 3-8 Log Panel Window Menu
Menu Menu Item Must Have Selected Result
File Quit n/a Closes the window
Operation View Event Records
One or more Logs Opens the Event Records View window
Log Directives... (Tru64 UNIX)
One Log Gives access to the directives
Show, Set, Suspend, Resume and Cleanup for the selected
Log Open Associated
Map Window
(Tru64 UNIX)
One Log Opens a Map window for the
Domain with which the Log is associated
Help On Version n/a Help on TeMIP
On Window n/a Help on Event Log Panel
Chapter 4
Handling Event Records
This chapter explains how to retrieve and handle event records from the repository. Topics covered are:
• Section 4.1 Using the Mouse
• Section 4.2 Desktop Manager Window • Section 4.3 Viewing Event Records
• Section 4.4 Using the Search Events Function • Section 4.5 Handling Event Records
Note
Operations on event data should be carried out only from the TeMIP Fault Managment windows. It is also possible to access Event Logs from the Iconic Map, but this is not recommended since it could cause a failure of the Iconic Map.
As an example, if you select an Event Log that has 5000 records, you will see all the event records. If you then select all these records and perform an action on them, the Iconic Map could fail and display the error message Can't Grow Stack.
4.1
Using The Mouse
The Event Logging windows contain lists in which actions can be
performed with the mouse. The action performed by the mouse depends on which list is being operated on. The windows and lists involved are: • View Events window
- List of retrieved event records • Event Search window
- Lists of search criteria. Mouse Operations
Table 4-1 summarizes the actions initiated by the mouse, and by the mouse in combination with the keyboard CTRL key.
Note
The term current line used in the table refers to the line that the pointer is on when the mouse button is pressed.
Table 4-1 Summary of Mouse Operations Mouse/
Keyboard
Window/List Action
Click MB1 Both windows/lists Selects the current line. Any other selected line is deselected.
CTRL + Click MB1
Both windows/lists Selects the current line and retains selection of other selected lines. If the current line is already selected, it is deselected.
Hold/Drag MB1
Retrieved events list
Selects all lines through which the pointer is dragged.
Search criteria lists No action Double-click
MB1
Retrieved events list
Full event information is displayed
Search criteria lists No action Hold MB3 Retrieved events
list
Selects the current line and displays a pop-up menu that stays selected as long as MB3 remains pressed. The command performed from the menu is that being pointed to when MB3 is released. If MB3 is released when the pointer is outside the pop-up menu, the menu closes and no action is taken. Search criteria lists No action
CTRL + Hold MB3
Retrieved events list
As above, but for use where multiple selections have been made.
Search criteria lists No action Double-click
MB3
Retrieved events list
Selects the current line and displays a pop-up menu that remains displayed when MB3 is released. An action is performed by clicking MB3 on the appropriate menu item. If MB3 is clicked with the pointer outside the pop-up menu, the menu closes and no action is taken.
Search criteria lists No action CTRL +
Double-click MB3
Retrieved events list
As above, but for use where multiple selections have been made.
4.2
Desktop Manager Window on Tru64 UNIX
The Desktop Manager window displays icons that correspond to specific windows and a new icon is added each time you open one of these windows. Using the Desktop Manager window, you can "tidy up" your screen if you have many windows displayed, but without having to stop the
corresponding applications. You can re-display the windows when required. The name of the window is displayed to the right of the icon to enable you to quickly identify the window you want to iconize/de-iconize. Icons are displayed for the following Event Logging windows:
• Event Records View window • Event Log Panel window • DC Editor window • DC/SF Librarian window • SP Editor window
If you double click Mouse Button 1 (MB1) on an icon in the Desktop
Manager window, the corresponding window is iconized. If you double click
on the icon again, the window is re-displayed. The icons displayed are the same as those in the Iconic Map applications bar at the top of the window and the multi screen display function is also supported. See the OpenView
TeMIP Customization Guide for further details.
Figure 4-1 shows an example of the Desktop Manager window. Figure 4-1 Desktop Manager Window on Tru64 UNIX
Note
1. If the TeMIP PM does not exit normally, the TeMIP Fault
Managment icons in the Desktop Manager window on Tru64 UNIX do not disappear.
2. Some icons may appear on Tru64 UNIX that correspond to TeMIP Framework applications.
3. For details of the Iconic Map, Desktop Manager and Console windows, refer to the manual OpenView TeMIP Iconic Map and
4.3
Viewing Event Records on Tru64 UNIX
You can retrieve and view event record information from the repository, for analysis or any other processing that is needed in your fault management scheme.
Entry from:
The Initial Display
When you start the view process, TeMIP begins to retrieve event records from the selected Log repository using the default search criteria, which is
ALL records. After a certain number of records have been retrieved (as
explained in Section 4.3.2), the retrieval operation is suspended.
At this point you can either continue the retrieval of all event records, or enter search criteria to narrow the retrieval down to specific types of records.
4.3.1 Stand-Alone Operation
You can open the Event Records View window in stand-alone mode, by entering the following command at the UNIX prompt:
If the LOG does not exist, the following exception is returned:
If you do not provide the <OSI_system_name> or <log_name>, the command usage is displayed. An example of the Event Records View window is shown in Figure 4-2.
Window Operation Remark
Iconic Map (Tru64 UNIX)
Operations menu - Monitor Logs - Then as below
Opens the Event Log Panel window for the selected OSI_System.
Event Log Panel
Select a LOG, and then - View Event Records from the Operation menu
Opens the Event Records View window for the selected LOG.
Event Log Panel
View Event Records button (must
have one or more LOGs selected)
Opens the Event Records View window for the selected LOG. Event Log
Panel
Double click on a LOG Opens the Event Records View window for the selected LOG. A stand-alone
application
temip_el_pm <OSI_system_name>
<log_name> at the UNIX prompt
Opens the Event Records View window for the input LOG name.
temip_el_pm <OSI_system_name> <log_name>
Figure 4-2 Event Records View Window
4.3.2 Segmented Retrieval
In the initial retrieval operation, and also in certain selective searches, a large number of event records may be involved. This could result in some delay before the retrieval operation is completed. To avoid this situation the search and retrieval operation is segmented, which means that events are retrieved a certain number at a time. The number of event records in a segment is a configuration variable with a default value of fifty (50), but can be set to any number required by the user.
The search is suspended when the first segment is retrieved. To continue the search and retrieve the next segment (if any) you click on the More... button.
This procedure can be repeated until all the retrievable events have been obtained. You will need to use the vertical scroll bar to view all the retrieved event records.
4.3.3 Event Records View Window Menu Bar
The menu bar of the Event Records View window contains the items: File, Edit, Search, Operation, Options. Table 4-2 summarizes the menu
items, preconditions for using the menu items, and the results of selecting them.
Table 4-2 Event Records View Window Menu Bar
Menu Menu Item Must Have
Selected
Result
File Expand Search to
LOG...
n/a Opens the Expand window to
continue the search through another Event Log within the same OSI System
LOG Directives... n/a Gives access to the window-associated Event Log directives
Close Window n/a Exits from the View function and
closes the window
Edit Select all Records n/a Selects all event records
Search Search... n/a Opens the Search Criteria
window
Redo Last Search n/a Repeats the last search and displays the latest event information
Operation Full Information One record Opens the Full Information window and displays details of the event record
Print One or more
records
Prints on the default printer
Print... One or more
records
Opens a window for you to select a printer
Print to File... One or more records
Opens the File Name prompt window for you to enter the target filename
Delete One or more
records
Deletes the selected event records from the repository
Entity Directives... n/a Gives access to the directives of the managed entity that produced the event
4.3.4 Event Record Information Displayed
A one-line summary of the event record information is displayed for each event record retrieved. Information displayed, starting with the left column, is as follows for each LOG class.
• LOG_RECORD Class - Event Type
- Managed Object (The network entity that produced the record) - Additional Text
- Εvent Time (Timestamp of event generation) - Logging Time (Timestamp of event collection) • ALARM_RECORD Class
- Event Type
- Managed Object (The network entity that produced the record) - The Alarm Perceived Severity
- The Probable Cause - Additional Text
- Event Time (Timestamp of event generation) - Logging Time (Timestamp of event collection) • SECURITY_ALARM_RECORD Class
- Event Type
- Managed Object (The network entity that produced the record)
Options General... n/a Opens the TeMIP General
Options window, for you to customize the default printer and the segment size value (see
Chapter 5)
Window... n/a Opens the TeMIP Window
Options window, for you to customize the event information list (see Chapter 5)
Save n/a Allows you to save customized
settings in your user-associated resource file. These will become the default settings for your next TeMIP PM session. See Chapter 5 for important information concerning the Save function.
Help On Version n/a Activates online help.
On Window n/a Activates online help.
Table 4-2 Event Records View Window Menu Bar (Continued)
Menu Menu Item Must Have
Selected
