HPE Operations Agent for NonStop
Object Configuration Client Guide
Abstract
Object Configuration Client (OCC) facilitates configuration of the HPE NonStop server components for management by the HPE Operations
environment. The OVNM Object Configuration Client Guide gives you information about the OCC product and the instructions on how to use it
effectively.
Part number: 540076-011
Published: January 2016
Edition: 11
Legal and notice information
© Copyright 2016Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such products and
services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise
shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation,
and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial
license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise
has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
No part of this documentation may be reproduced or transmitted in any form or by any means without prior written
consent of Hewlett Packard Enterprise.
The information contained herein is subject to change without notice.
Warranties
HEWLETT PACKARD ENTERPRISE MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. Hewlett Packard Enterprise shall not be liable for errors contained herein or for incidental
or consequential damages in connection with the furnishing, performance, or use of this material.
The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty
statements accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions
contained herein.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United
States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Revision History
Rebranded for Hewlett Packard Enterprise
January 2016
i
Contents
Preface ·········································································································································································································· 4
Before You Begin ··································································································································································································································4
Audience ···················································································································································································································································4
Goals of Documentation ···················································································································································································································4
Organization············································································································································································································································ 5
OVNM Documentation Map ············································································································································································································ 5
Electronic Versions of the Manuals ····························································································································································································· 5
OVNM Manuals ······································································································································································································································ 6
Additional OVNM-Related Products ·························································································································································································· 6
About OVNM Online Help················································································································································································································ 6
1 Object Management: Introduction············································································································································· 8
About OVNM ·········································································································································································································································· 8
Why OVNM? ············································································································································································································································ 8
Object Management through OVNM ························································································································································································· 9
Introducing OCC···································································································································································································································· 9
2 Object Configuration Client Interface ···································································································································· 10
OCC Window ········································································································································································································································ 10
Menu Bar ·················································································································································································································································· 11
Toolbar······················································································································································································································································ 11
Monitoring Toolbar····························································································································································································································· 11
Status Bar ················································································································································································································································ 11
Menus ······················································································································································································································································· 12
File Menu ······················································································································································································································12
Threshold Menu ········································································································································································································13
Edit Menu ···················································································································································································································· 14
Monitoring Menu ······································································································································································································15
Recovery Menu ········································································································································································································· 16
View Menu ···················································································································································································································17
Tools Menu ················································································································································································································· 18
Help Menu ···················································································································································································································20
Toolbar and Monitoring Bar Icons ····························································································································································································· 21
Toolbar ···························································································································································································································21
Monitoring Bar ···········································································································································································································21
Right-Click Menus ····························································································································································································································· 23
Object Class Pane ···································································································································································································· 23
Threshold Pane·········································································································································································································24
Objects Pane ·············································································································································································································· 27
3 Object Configuration Client: The Understanding ·············································································································28
Managed Subsystems ····················································································································································································································· 28
Authentication and Security ········································································································································································································ 29
Scheduling············································································································································································································································· 30
SCHEDULE FILE·································································································································································································································· 31
HOLIDAY FILE ···································································································································································································································· 32
Monitoring ············································································································································································································································· 33
ii
Actions ···················································································································································································································································· 35
EMS Alerts···················································································································································································································36
E-Mail Alerts···············································································································································································································39
Recovery ······················································································································································································································ 41
eEvents ·························································································································································································································42
EMS Actions ········································································································································································································································· 47
ObjectMAP ··················································································································································································································47
eBurst ····························································································································································································································50
Group & Subgroup Management of Objects ······································································································································································· 54
Object Location ·································································································································································································································· 55
Maintenance ········································································································································································································································· 56
4 Working With Object Configuration Client ··························································································································58
Prerequisites ········································································································································································································································ 58
Managing the Environment·········································································································································································································· 59
Creating a Threshold Configuration ························································································································································································· 61
Listing Configurations and Objects·························································································································································································· 72
Listing Configurations ··························································································································································································· 72
Listing Objects ·········································································································································································································· 73
Color Coding ··············································································································································································································74
Maintaining Configurations & Objects···················································································································································································· 75
Modifying Configurations ···················································································································································································· 75
Modifying Objects ··································································································································································································· 76
Deleting Configurations························································································································································································ 77
Deleting Objects ······································································································································································································· 77
Appendix A: Subsystems Managed ···············································································································································78
Appendix B: EMS Message Handling ··········································································································································· 81
EMS Processing Sequence ············································································································································································································ 87
Appendix C: OSS Log Handling······················································································································································ 89
Appendix D: Default Policies ····························································································································································92
Appendix E: Substitution Parameters ··········································································································································95
Appendix F: OCC Errors ····································································································································································· 96
Appendix G: NetBatch Monitoring················································································································································ 98
iii
Preface
HPE Operations NonStop Server Management (OVNM) is an out-of-the-box solution that provides seamless
integration of HPE Operations (previously known as HPE OpenView – OVO) with HPE NonStop servers. The
software is a natural extension of HPE Operations and provides you with true end-to-end management of your
NonStop environment.
Object Configuration Client (OCC) facilitates configuration of the HPE NonStop server components for
management by the HPE Operations environment. The OVNM Object Configuration Client Guide gives you
information about the OCC product and the instructions on how to use it effectively. Designed to meet the practical
needs of the HPE NonStop environment, this manual explains the concepts behind OCC and illustrates all the facets
of the software. This Guide contains all the information necessary to understand OCC and to use it effectively to
solve your HPE NonStop Enterprise Management issues.
Before You Begin
Before reading the documentation, you are expected to have a basic understanding of HPE Operations
environment, as well as the HPE NonStop environment. Familiarity with the HPE NonStop Distributed Systems
Management software, especially the Event Management Service, would be helpful.
Audience
This guide is intended for two types of users.
•
Administrators, who plan, set up, and maintain OVNM and HPE Operations Manager
•
Operators, who perform daily tasks using OVNM and HPE Operations Manager
Goals of Documentation
After reading the Object Configuration Client Guide, you should know the following information.
•
Introduction to Object Management and how it is implemented using Object Configuration Client (OCC).
•
Navigating through the various menu options and screens.
•
Finding the step-by-step procedure that corresponds to the task that you want to perform.
•
Steps to configure monitoring and escalation.
4
Organization
The guide is organized as follows.
Table 1.
Guide Organization
S. No.
Chapter Name
Description
Chapter 1
Object Management:
Introduction
Introduces Object Management and how it is implemented with OVNM.
Chapter 2
Object Configuration Client Gives detailed reference for the various components of the Object Configuration
Introduction
Client GUI.
Chapter 3
Object Configuration Client: Gives information about the concepts related to the Object Configuration Client.
The Understanding
Chapter 4
Working with Object
Configuration Client
Gives instructions for using the various features, such as creating a threshold
configuration, of the Object Configuration Client.
Appendix A.
Subsystems Managed
Gives a list of all the predefined subsystems managed by Object Configuration
Client.
Appendix B.
EMS Message Handling
Gives an example of setting up an EMS threshold.
Appendix C.
OSS Log Handling
Gives an example of setting up OSS threshold for monitoring OSS logfile.
Appendix D.
Default Policies
Gives a table containing the list of pre-configured policies.
Appendix E.
Substitution Parameters
Gives a list of substitution parameters or macros that are used during message
construction.
Appendix F.
OCC Errors
List the common messages of Object Configuration Client.
OVNM Documentation Map
HPE Operations Agent for NonStop (OVNM) provides a set of manuals and online help that help you use the
product and understand the concepts underlying the product. This section describes what information is available
and where you can find it.
Electronic Versions of the Manuals
All manuals are available as Adobe Portable Document Format (PDF) files in the documentation directory on the
OVNM product CD-ROM. All manuals are also available in the HPE Web server directory. For details, contact the
appropriate HPE support service.
5
OVNM Manuals
This section provides an overview of the OVNM manuals and their contents.
Table 2.
OVNM Manuals
Manual
Description
Media
OVNM Concepts Guide
Explains OVNM features, functions, benefits, architecture, and data flow.
Describes OVNM agent and server components.
PDF
OVNM Installation Guide
Explains how to install, configure and start & stop OVNM components.
PDF
OVNM User Guide
Explains how to start & stop OVNM components. Also includes OVNM utilities
and troubleshooting.
PDF
OVNM Object Configuration
Client Guide
Explains the Object Configuration Client (OCC) interface and provides the
instructions on how to use the software effectively.
PDF
OVNM ObjectStats Guide
Explains the ObjectStats interface and the instructions on how to use it
effectively.
PDF
OVNM Console Guide
Explains the OVNM Policy Manager interface and provides the instructions on
how to use the software effectively.
PDF
OVNM ObjectMAP Guide
Explains the ObjectMAP interface and provides the instructions on how to use
the software effectively.
PDF
OVNM Event Management Guide Explains the concepts of Event Integration.
PDF
Object Reference guide
Lists the various threshold policies in Object Configuration Client (OCC).
PDF
OVNM Troubleshooting Guide
Explains the common troubleshooting queries along with the common OVNM
error messages and how to handle them.
PDF
Additional OVNM-Related Products
This section provides an overview of the OVNM-related manuals and their contents.
Table 3.
OVNM-related manuals
Manual
Description
Media
Performance Agent
PDF
OVNM Performance Agent for
NonStop
SMART Plug-In
SPI for MQ-SERIES
PDF
SPI for BASE24
PDF
About OVNM Online Help
This preface describes online documentation for the HPE Operations Agent for NonStop Server (OVNM) graphical
user interfaces (GUIs).
6
Table 4.
OVNM Online Help
Help File
Description
Object Configuration Client
Explains the Object Configuration Client GUI and how to use the interface effectively.
ObjectStats
Explains the ObjectStats GUI and how to use the interface effectively.
Console
Explains the Console GUI and how to use the software effectively.
ObjectMAP
Explains the ObjectMAP GUI and how to use the software effectively.
Host Installation Client
Explains the Host Installation Client GUI and how to use the interface effectively.
Host Management Client
Explains the Host Management Client GUI and how to use the interface effectively.
7
1 Object Management: Introduction
About OVNM
HPE Operations Agent for NonStop (OVNM) is a fully integrated, out-of-the-box solution that seamlessly works
with many Enterprise Management Systems (HPE OM, Tivoli, BMC, etc.), extending the managed domain to include
HPE NonStop Servers.
This tight integration gives organizations a cost-efficient, easily configurable, and time-saving way to rapidly and
successfully incorporate HPE NonStop business applications and management solutions into their service delivery
infrastructure.
OVNM helps administrators efficiently monitor distributed enterprise-wide NonStop environments from a central,
best-in-class console. The agent helps you increase availability and performance, visualize capacity shortages and
trends and lower the overall cost of maintaining your NonStop environment.
Why OVNM?
•
Increased Service Availability
•
Health-Monitoring of HPE NonStop Systems
•
Enhanced Productivity
•
Enhanced Flexibility
•
Consolidated Policy Based Management Views
•
Reduced Costs
8
Object Management through OVNM
OVNM is an integrated set of modules to manage HPE NonStop servers from any of the most popular Enterprise
Management Systems. It also provides the ability to manage the HPE NonStop environment without an Enterprise
Management system if that is your desire. The modules include both Object Management and Event
Management.
Object management enables you to define HPE objects and an easy way to manage them. OVNM provides the
Object Configuration Client (OCC) GUI to easily create, maintain and manage HPE NonStop Objects.
Figure 1. Object Management
The figure provides an overview of the OVNM Object Management capabilities.
The NonStop object integration provides the ability to:
•
Generate EMS events based on object resources.
•
Define thresholds, which can be set using the OCC interface.
•
Set Message severity and various token values for the Enterprise Management System, such as HPE
Operations Manager (HPE OM) service view ID’s.
Introducing OCC
OCC is designed to configure HPE NonStop Server system objects for management, such as CPUs, Disks, Files and
Processes. It allows you to set the attributes to be monitored for such objects. You define the desired state of an
object in operation, and what should be considered as an odd or undesirable state for the object. You can configure
multiple HPE NonStop nodes from a single management workstation, a single node from multiple workstations, or
any other combination thereof.
The most important feature of the OCC is to configure events that need to be managed by the Enterprise
Management System.
9
2 Object Configuration Client Interface
The following figure illustrates OVNM Object Configuration Client Interface.
Figure 2.OCC Interface
OCC Window
The OCC window is divided into the following areas.
•
Object Class Panel: Object Class is the vertical panel on the left side of the window displaying a list of object
classes. The objects are displayed in a tree view that lists the various nodes configured along with the
subsystems.
•
Threshold or Configuration Panel: This is the first horizontal area in the upper right side of the window,
which lists all the thresholds configured for a selected object type. It also displays the Operator, Monitoring
and Recovery Status; Multi-node and Creator / Modifier information; Created and Last Modified date along
with the Comments. You can choose the columns and the sequence in which they will be displayed.
•
Objects Panel: This is the lower right horizontal area, which lists all the objects corresponding to a selected
threshold in the Threshold pane along with their severity status. It also displays the Manager, Operator,
Threshold, Monitoring and Recovery Status, Created date, Last Polled Time and Last Polled Value. You can
choose the columns and the sequence in which they will be displayed.
•
Message/Log Panel: This is the horizontal panel at the bottom of the OCC window. It displays the list of
messages/logs related to OCC and Elink. This pane is not displayed by default. You can display or hide it by
selecting the Messages option in the View menu.
10
Menu Bar
The following figure illustrates the Menu Bar of OVNM Object Configuration Client Interface.
Figure 3. OCC Menu Bar
The first bar at the top of the window is the Menu Bar, giving access to various menus. The menus available are
File, Threshold, Edit, Monitoring, Recovery, View, Tools and Help.
Toolbar
The following figure illustrates the Toolbar of OVNM Object Configuration Client Interface.
Figure 4.
OCC Toolbar
The Toolbar is displayed at the top of the window, below the Menu bar. It consists of various icons, which are
shortcuts to some of the frequently used commands in the various menus on the Menu bar. Along with the icons, it
gives you the option to select HPE NonStop nodes using the Node box. You can display or hide it by selecting the
Toolbar option in the View menu. It is a dock-able bar, which means that it can be positioned anywhere you want
on the screen. The various icons are enabled or disabled depending on the selections made in the various panes.
Monitoring Toolbar
The following figure illustrates the Monitoring Bar of OVNM Object Configuration Client Interface.
Figure 5. OCC Monitoring Toolbar
The Monitoring bar is displayed adjacent to the Toolbar. You can display or hide it by selecting the Monitoring
Toolbar option in the View menu. It is a dock-able bar. The bar consists of various icons, which are shortcuts to the
frequently used commands in the Monitoring and Recovery menus. The various icons are enabled or disabled
depending on the selections made in the various panes and the conditions specified.
Status Bar
The following figure illustrates the Status Bar of OVNM Object Configuration Client Interface.
Figure 6.
OCC Status Bar
The Status bar can be seen at the base of window. The Status bar can be divided into three areas, which offer the
following information.
•
Left Area: In this area, tips are provided on various menu options and icons present on the Toolbar, along
with other status messages.
•
Middle Area: In this area, the Node name and IP address of the selected node along with the status of the
action executed is displayed.
•
Right Area: This area shows whether the local OCC application is registered and connected with the local
Elink.
11
Menus
The various menus available on the Menu bar are as follows.
•
File
•
Threshold
•
Edit
•
Monitoring
•
Recovery
•
View
•
Tools
•
Help
File Menu
This is the first menu on the Menu bar. The option available in this menu is as follows.
•
Exit: Use this option to exit from the OCC application.
Figure 7.OCC File Menu
12
Threshold Menu
The Threshold menu includes options related to threshold configurations and objects, such as creating new
threshold configurations, modifying existing ones, and deleting objects. The shortcuts for most of the commands in
the Threshold menu are available on the Toolbar.
Figure 8.
OCC Threshold Menu
The various options available in the Threshold menu are as follows:
•
New Configuration: Use this option to create a new threshold configuration. Clicking this option displays the
Threshold dialog box, in which the specifications for the threshold like the Subsystem and Object Type can be
specified.
•
List Configurations: Use this option to list all the thresholds corresponding to the selected Object Class in
the Thresholds pane.
•
Modify Config: Use this option to access the Modify Configuration / Object dialog box. This allows you to
modify the configuration settings for an existing threshold.
•
Delete Config: Use this option to delete the selected threshold(s).
•
List Objects: Use this option to list all the objects corresponding to the selected threshold configuration. It is
especially useful in case the threshold was created using wildcard characters.
•
Stop Listing Objects: Use this option to stop the listing of objects. This option is enabled only for the period
when the command for listing objects is being executed. As soon as the listing is complete or is stopped, the
option is disabled.
•
Modify Object: Use this option to access the Modify Configuration / Object dialog box, using which you can
modify the configuration settings for the selected object. This option is enabled only when you select an
object in the Objects pane.
•
Delete Object: Use this option to delete the selected object(s). This option is enabled only when you select an
object(s) in the Objects pane.
•
Add New Object: Use this option to add new objects to an existing threshold without using the Auto
Maintenance feature. New objects can be added irrespective of the template set for the threshold. Clicking
this option displays the Add User Object dialog box.




When you use the Add New Object feature, you will notice that the manager field is now open whenever
the manager field is also used to create the original threshold.
You can use wildcards in both the Object and the Manager fields
This feature will add whatever objects match the template that is entered, even if the object is already on
the database, so you need to be careful when using this feature.
There is no way to view what templates were already used in previous 'add new object' transactions. This
information is not recorded anywhere.
13

If you use this feature multiple times on the same threshold, all of the objects are basically lumped
together; there is no way to determine which objects were added at the same time.
Figure 9.
OCC Add User Object Dialog Box
Edit Menu
Edit is the third menu on the Menu Bar. The option available in the Edit menu is:
Find Object: If you have numerous objects defined within a threshold, you may find it difficult to locate a specific
object in the List Objects display in the Objects pane.
Figure 10.
OCC Edit Menu
Use the Find Object option to display the Find Object dialog box where you can enter the object name and then
click the Find button. This will highlight the specified object in the display.
Figure 11.
OCC Find Object Dialog Box
14
Monitoring Menu
This is the fourth menu on the Menu Bar. This has various commands related to controlling monitoring at different
levels. The shortcuts for the options in this menu are available on the Monitoring toolbar and in the right-click
menus of the various panes.
Figure 12.
OCC Monitoring Menu
The various options available in the Monitoring menu are as follows.
•
Activate Node Monitoring: Clicking this option activates monitoring for the selected node. This reactivates
monitoring for the threshold flagged for active monitoring in the node. It does not change the status of the
thresholds configured for inactive monitoring. This option is enabled only when the overall monitoring is
inactive and a node is selected in the Object Class pane.
•
Inactivate Node Monitoring: Clicking this option inactivates monitoring for the selected node. This command
inactivates all the thresholds flagged for active monitoring in the node. This option is enabled if the overall
monitoring is active and a node is selected in the Object Class pane.
NOTE:
In the previous OVNM versions, when you used the Object Configuration Client to turn Node Monitoring OFF,
the OVNM application would continue to consume EMS messages and react to them (if they were defined in an
EMS threshold) and send them to HPE OM (if specified). With OVNM release 4.8, when you use the Object
Configuration Client to turn monitoring off/on for the entire node, you have the option of having this impact the
EMS traffic as well. For details on how to enable the feature, refer to Customizing Node Monitoring Feature
section in User Guide.
•
Activate Config Monitoring: Use this option to activate monitoring for the selected threshold
configuration(s). It activates monitoring for all the objects under the selected threshold(s), which are flagged
for active monitoring. This option is enabled only if monitoring is inactive for the selected threshold(s).
•
Inactivate Config Monitoring: Use this option to deactivate monitoring for the selected threshold
configuration(s) only. It inactivates monitoring for all the objects under the selected threshold(s), which are
flagged for active monitoring. This option is enabled only if monitoring is active for the selected threshold(s).
•
Activate Object Monitoring: Use this option to activate monitoring for the selected object(s) in the Objects
pane. This option is enabled only if the monitoring for the selected object(s) is inactive.
•
Inactivate Object Monitoring: Use this option to deactivate monitoring for the selected object(s) in the
Objects pane. This option is enabled only if the monitoring for the selected object(s) is active.
15
Recovery Menu
The various options available in the Recovery menu are as follows.
•
Activate Config Recovery
•
Inactivate Config Recovery
•
Activate Object Recovery
•
Inactivate Object Recovery
Figure 13.
OCC Recovery Menu
The various options available in the Recovery menu are as follows.
•
Activate Config Recovery: Use this option to activate recovery for the selected threshold configuration(s). It
activates recovery for all the objects under the selected threshold(s) for which recovery has been configured.
This option is enabled only if recovery has been configured but inactive for the selected threshold(s).
•
Inactivate Config Recovery: Use this option to deactivate recovery for the selected threshold
configuration(s). It inactivates recovery for all the objects under the selected threshold(s) for which recovery
has been configured. This option is enabled only if recovery has been configured and active for the selected
threshold(s).
•
Activate Object Recovery: Use this option to activate recovery for the selected object(s). This option is
enabled only if recovery has been configured but inactive for the selected threshold(s).
•
Inactivate Object Recovery: Use this option to deactivate recovery for the selected object(s). This option is
enabled only if recovery has been configured and active for the selected threshold(s).
16
View Menu
The various options available in the View menu are as follows.
•
Toolbar
•
Monitoring Toolbar
•
Status Bar
•
Messages
•
Columns
Figure 14.
OCC View Menu
The various options available in the View menu are as follows.
•
Toolbar: This option enables you to toggle between the displayed and hidden modes of the Toolbar.
•
Monitoring Toolbar: This option enables you to toggle between the displayed and hidden modes of the
Monitoring toolbar.
•
Status Bar: This option enables you to toggle between the displayed and hidden modes of the Status bar.
•
Messages: This option enables you to toggle between the displayed and hidden modes of the Message/Log
panel.
•
Columns: This option enables you to select the fields to be displayed in the Threshold and the Objects pane.
Clicking this option displays the Column Settings dialog box.
Figure 15.
Column Setting Dialog Box
Use the Configurations View and Objects View tabs to configure the information display in the Threshold and
Objects pane, respectively.
Select the options from the Available Columns list and Click the Add button to add the column to the Current
Columns list. Use the Remove button to hide the display of the selected column. Move Up and Move Down buttons
allow you to specify the sequence in which the columns are displayed.
17
Tools Menu
The various options available in the Tools menu are as follows.
•
Managed Subsystems
•
Log on
•
Log off
•
Cancel all requests for this node
•
Options
Figure 16.
OCC Tools Menu
The Tools menu offers the following options.
•
Managed Subsystems: This option displays the Managed Subsystems dialog box, using which; you can
select the subsystems to be configured.
•
Log on: This option can be used to log on to the selected node. Logging on authenticates you for operations
like creating, modifying or deleting configurations and objects. This option is enabled if a node is selected in
the Object Class pane and if you are not logged on to the selected node.
•
Log off: This option can be used to log off from the selected node. This option is enabled if a node is selected
in the Object Class pane and if you are already logged on to the selected node.
•
Cancel all requests for this node: This option can be used to cancel all the requests for the selected node.
This option is enabled only for the period when a request is sent to the node. As soon as the task is completed
or is stopped, the option is disabled.
•
Options: Clicking the Options displays the Options dialog box. This dialog box can be used to configure the
auto-logoff time, the default enterprise solution selection and whether or not to save the values used when
adding new thresholds as a default value for future thresholds.
Figure 17.
OCC Options Dialog Box
18
There are two Severity fields that can be defined when using the OCC.
The first one is located in the Actions/Alert panel. This severity is used to define the severity that will be used in
the Violation EMS message that is generated by OVNM. This value is also used in ObjectMap and ObjectStats.
The second field is defined in the Actions/eEvents panel. This severity is used when sending the message to the
Enterprise Management system and Console.
As the values of these severities are different, the Keep severities in sync checkbox is checked. When this
checkbox is checked, a change to one of those values will automatically change the other value, unless the value in
the eEvents panel is Original. If the option is not checked, the user can update both fields – no automatic updates
will be applied. This allows you to intentionally use different severities in the Enterprise Management system than
what is seen in ObjectMap, which could be viewed by a different department.
The default value for the Session Timeout is 2 hours. After 2 hours of no activity within the OCC application, any
future action that requires modifying the database will require the user to log on again.
Most OVNM customers will want to create eEvents records for every single threshold. By checking this box, it
makes that process automatic (as it was in previous releases). By default, it will also select OVO (HPE OM) as the
default enterprise solution. If you are not using any Enterprise Management solution, you can turn this feature off –
there is no need to create eEvents records if the messages are not going to be forwarded on. Console will always
get the messages regardless of this setting. If you are using an Enterprise Solution, but not HPE OM, you can
change this to match your environment.
The ‘Save Last-Used Threshold Schedule’ feature allows you to decide if you want to save the values you specify
in the “Schedule” panel as default values for future thresholds. Each subsystem will have its own default values.
The ‘Save Last-used Alert Schedule’ refers to the ‘repeat every’ and escalation values in the Alert tab. Each
subsystem will have its own default values.
When these options are turned off, the OCC goes back to the original default values regardless of what values you
may have saved in the past.
The Auto-start elink at startup allows you to automatically start up the elink process while launching the Object
Configuration Client.
NOTE:
Under normal circumstances, Elink should already be running before you start this application, which would make
this option meaningless. In the event that you require a VPN connection to be established before you can connect
to the HPE NonStop, then you can configure the Elink Service to be MANUALLY started and use the
Configuration Client to start it when needed. The Auto-start elink at startup should always be checked.
Un-checking this option will prevent the Configuration Client from starting Elink when Elink is not already
running.
For more information about configuring Services, see Control Panel  Administrative Tools  Services option.
19
Help Menu
The various options available in the Help menu are as follows.
•
Help Topics
•
About
Figure 18.
OCC Help Menu
The Help menu offers the following options.
•
Help Topics: This option provides you help on various features of OCC.
•
About: This option provides the version number of the OCC software and the copyright and license
information.
NOTE:
The various options and icons will be enabled or disabled depending on the selections made in the various panes.
For example, the options related to modifying thresholds will be enabled only when you select the threshold to be
modified in the Threshold pane.
20
Toolbar and Monitoring Bar Icons
Toolbar
The following table lists and describes the various Icons available in OCC Toolbar
Table 5.
Toolbar Icons
S. No
Toolbar Icons
Menu Options
Menu
1.
New Configuration
Threshold
2.
List Configurations
Threshold
3.
Modify Config
Threshold
4.
Delete Config
Threshold
5.
List Objects
Threshold
6.
Modify Object
Threshold
7.
Delete Object
Threshold
8.
Find Object
Edit
Node Box: Along with the various icons, the Toolbar also has the Node box, using which you can select the HPE
NonStop node to be monitored.
Figure 19.
OCC Monitoring Bar Node Box
Monitoring Bar
The following table lists and describes the various Icons available in OCC Monitoring Bar.
Table 6.
S. No
Monitoring Bar Icons
Monitoring Bar Icons
Menu Option
Menu
1.
Activate Node Monitoring
Monitoring
2.
Inactivate Node Monitoring
Monitoring
3.
Activate Config Monitoring
Monitoring
4.
Inactivate Config Monitoring
Monitoring
5.
Activate Config Recovery
Recovery
6.
Inactivate Config Recovery
Recovery
21
S. No
Monitoring Bar Icons
Menu Option
Menu
7.
Activate Object Monitoring
Monitoring
8.
Inactivate Object Monitoring
Monitoring
9.
Activate Object Recovery
Recovery
10.
Inactivate Object Recovery
Recovery
22
Right-Click Menus
OCC provides the right-click feature in its interfaces, which makes it user-friendly. Right-click menus are provided in
various panes, which have some of the most frequently accessed commands along with other commands specific to
the selection made. To access the right-click menus, you need to make a selection in the pane and then right-click
on it.
Object Class Pane
The following right-click menus can be accessed in the Object Class panel.
Node Icons
Figure 20.
OCC Object Class Pane Node Icon Right-Click Menu
The right-click menu available by clicking on any of the node icons in the Object Class panel has been displayed
above. The options available in the menu are:
•
Log on: Use this option to log on to the selected node.
•
Log Off: Use this option to log off from the selected node.
•
Stop Listing Objects: Use this option to stop the process of listing objects.
•
Cancel Request(s): Use this option to cancel request(s) sent to the selected node.
•
Start Monitoring: Use this option to start monitoring for the selected node. This option will be enabled only
when monitoring for the node is in inactive state.
•
Stop Monitoring: Use this option to stop monitoring for the selected node. This option will be enabled only
when monitoring for the node is in active state.
•
Refresh Monitoring state: Use this option to refresh the monitoring status of the selected node.
•
Configure Managed Subsystems: Use this option to access the Managed Subsystems dialog box.
Object Class Icons
The right-click menu available using the right-click action on the Object Class icon is displayed above. It has only
one option, List Configurations. You need to select an Object Type from the tree structure in the Object Class pane
and then right-click on it to access this menu.
Figure 21.
•
OCC Object Class Pane Object Class Icon Right-click Menu
List Configurations: Use this option to list all the thresholds configured for the selected Object Type. The list
is displayed in the Threshold pane. This is a shortcut for the List Configurations option in the Threshold
menu.
23
Threshold Pane
The menu displayed above is the right-click menu of the Threshold pane. To access this menu, right-click on
selected threshold configuration in the Threshold pane.
Figure 22.
OCC Threshold Pane Right-click Menu
The various options in this menu are as follows.
•
View Config Detail: Using this option, you can check the conditions specified for the selected threshold
configuration. Clicking this option displays the Configuration / Object Detail dialog box. Modifications cannot
be made using this dialog box, as only the Cancel button is enabled. The OK and the Apply buttons are
disabled.
Figure 23.
OCC Configuration / Object Detail Dialog Box
24
•
Modify Configuration: Use this option to access the Modify Configuration / Object dialog box, using which
you can modify the configuration settings for the selected threshold configuration. It is a shortcut for the
Modify Config option in the Threshold menu.
•
Delete Configuration: Use this option to delete a selected threshold configuration. It is a shortcut for the
Delete Config option in the Threshold menu.
•
List Objects: Use this option to list all the objects under the selected threshold configuration. The list is
displayed in the Objects pane. This is a shortcut for the List Objects option in the Threshold menu.
•
Monitoring Active: Use this option to activate monitoring for the selected threshold configuration(s) only. It
activates monitoring for all the objects under the selected threshold(s), which are flagged for active
monitoring. This option is enabled only if monitoring is inactive for the selected threshold(s). This is a shortcut
for the Activate Config Monitoring option in the Monitoring menu.
•
Monitoring Inactive: Use this option to inactivate monitoring for the selected threshold configuration(s) only.
It inactivates monitoring for all the objects under the selected threshold(s), which are flagged for active
monitoring. This option is enabled only if monitoring is active for the selected threshold(s). This is a shortcut
for the Inactivate Config Monitoring option in the Monitoring menu.
•
Recovery Active: Use this option to activate recovery for the selected threshold configuration(s) only. It
activates recovery for all the objects under the selected threshold(s), which are flagged for active recovery.
This option is enabled only if recovery is inactive for the selected threshold(s). This is a shortcut for the
Activate Config Recovery option in the Recovery menu.
•
Recovery Inactive: Use this option to inactivate recovery for the selected threshold configuration(s) only. It
inactivates recovery for all the objects under the selected threshold(s), which are flagged for active recovery.
This option is enabled only if recovery is active for the selected threshold(s). This is a shortcut for the
Inactivate Config Recovery option in the Recovery menu.
•
Copy to Node(s): Use this option to copy the selected threshold to multiple nodes.
•
Add New Object: Use this option to add new objects to an existing threshold without using the Auto
Maintenance feature. This option enables you to add new objects irrespective of the template set for the
threshold. This option is a shortcut to the Add New Object option in the Threshold menu.
25
•
Auto-Maintenance: Use this option to to perform a "one time - on demand" discovery. When new objects
have been added to the backend environment and you don't want to wait for the scheduled auto maintenance
time, or the threshold does not use auto maintenance feature, you can force a re-discovery by using this
option. There is a need to remember the following points while working with the Auto-Maintenance feature.





When you use the Add New Object feature, you will notice that the manager field is now open whenever
the manager field is also used to create the original threshold.
You can use wildcards in both the Object and the Manager fields.
This feature will add whatever objects match the template that is entered, even if the object is already on
the database, so you need to be careful when using this feature.
There is no way to view what templates were already used in previous 'add new object' transactions. This
information is not recorded anywhere.
If you use this feature multiple times on the same threshold, all of the objects are basically lumped
together; there is no way to determine which objects were added at the same time.
Figure 24.
Apply Auto-Maintenance Immediately Dialog Box
The options supported by this feature are, Rebuild and Update (add only).
NOTE:
If you use Rebuild, be aware that objects could be deleted from the database if they no longer exist or they do
not match the template that was specified when the threshold was first added. So if you had manually added
objects via the "Add Object" feature that does not match the template, those objects will be deleted.
This feature is not allowed if there are no wildcards in the threshold definition since it would not have anything
more to discover. It is not related at all to the scheduled/normal auto maintenance. You can use this feature on
any threshold; auto maintenance does not have to be defined for the threshold.
26
Objects Pane
The right-click menu of the Objects pane is displayed above. Selecting object(s) in the Objects pane and then right
clicking on it can access this.
Figure 25.
OCC Objects Pane Right-Click Menu
The various options in this menu are as follows.
•
View Object Detail: Use this option to check the conditions specified for the selected object. Clicking this
option displays the Configuration / Object Detail dialog box. Modifications cannot be made using this dialog
box, as only the Cancel button is enabled. The OK and the Apply buttons are disabled.
•
Modify Object: Use this option to do modifications for already created Objects. This is a shortcut for the
Modify Object option in the Threshold menu.
•
Delete Object: Use this option to delete the selected objects. This is a shortcut for the Delete Object option in
the Threshold menu.
•
Monitoring Active: Use this option to activate monitoring for the selected object(s). This option is enabled
only if monitoring for the selected object(s) is inactive. It is a shortcut for the Activate Object Monitoring
option in the Monitoring menu.
•
Monitoring Inactive: Use this option to inactivate monitoring for the selected object(s). This option is enabled
only if monitoring for the selected object(s) is active. It is a shortcut for the Inactivate Object Monitoring
option in the Monitoring menu.
•
Recovery Active: Use this option to activate recovery for the selected object(s). This option is enabled only if
recovery for the selected object(s) is configured but inactive. It is a shortcut for the Activate Object Recovery
option in the Recovery menu.
•
Recovery Inactive: Use this option to inactivate recovery for the selected object(s). This option is enabled
only if recovery for the selected object(s) is configured and active. It is a shortcut for the Inactivate Object
Recovery option in the Recovery menu.
27
3 Object Configuration Client: The Understanding
Object Configuration Client (OCC) is an interface, which enables you to create threshold configurations to ensure
monitoring, escalation and mapping for HPE NonStop objects. This section covers the various concepts of OCC.
Managed Subsystems
The intuitive OCC interface enables you to define sets of monitoring thresholds for each object. Each set is known
as a configuration or threshold configuration for that object. The first step in defining threshold configurations for
one or more objects is to select the subsystems that you want to monitor for each HPE NonStop node. You can
select the subsystems and their object types using the Managed Subsystems dialog box. Only the subsystems
selected in this dialog box are visible in OCC. You can also access the dialog box using the Managed Subsystems
option in the OCC Tools menu.
Figure 26.
OCC Managed Subsystems Dialog Box
OCC allows you to monitor most of the major HPE NonStop subsystems.
Refer to Appendix A: Subsystems Managed for a list of all the subsystems managed by OCC.
28
Authentication and Security
OCC provides security features, which make sure that only authorized users can access the OCC database.
Authentication is required for operations like creating, modifying or deleting configurations and objects. The Log
on to dialog box is displayed.
Figure 27.
OCC Log on to Dialog Box
You need to enter the user ID and the password in the User Name and Password boxes, respectively, to access the
HPE NonStop host. The HPE NonStop administrator specifies these. Select the Use this user-id across all nodes
check box to use the same user name across all the configured nodes. Click the OK button after specifying the
necessary details. When this box is selected, the user id and password will be verified on all nodes, so it really only
works when the password is the same across the network.
You can configure authentication information using the General tab page in the Options dialog box. To access this,
click the Options command in the Tools menu.
Figure 28.
OCC Options Dialog Box
You can specify the time-out parameter for a particular session using the Session Timeout box in the
Authentication area in the Options dialog box. After the specified time, the system will logout and you will have to
login again. The default value is 2 hours.
29
Scheduling
OCC allows you to schedule object monitoring for a specified time period. The alert messages for object violations
are generated or suppressed according to the schedule defined for a particular threshold. The schedule can be
specified while creating a threshold configuration using the Schedule dialog box. To access the Schedule dialog
box click the Schedule button in the New/Modify Threshold dialog box.
Figure 29.
OCC Schedule Dialog Box
By default, monitoring will poll the system for violations every 5 minutes, 24 hours a day, and 7 days a week. Use the
Schedule dialog box to specify a schedule according to your business requirements.
The default Poll Interval value is 5 minutes. This means that the OCC monitoring process on the HPE NonStop host
will check for object state changes every 5 minutes. The unit for Poll Interval can be changed from minutes to
seconds or hours. The frequency can also be changed within the range of 01 to 59, giving a possible range of 1
second to 59 hours for the time between violation checks.
The daily default Start Time and Stop Time are 00:00 and 23:59, respectively. This indicates that monitoring will
be active throughout the day, based on the HPE NonStop system time. You can enter a different monitoring start
time and stop time by entering the appropriate hours and minutes in the Start Time and Stop Time boxes,
respectively. Using the Start Time and Stop Time options and creating separate threshold records can monitor the
same object monitored for different thresholds during different periods. Other uses would be to monitor the same
object for the same threshold, but for discrete periods, or on different days by making two different threshold
configurations. However, if you have a need to use a complicated schedule, it is better if you select the “Use
Extended host schedule” box and use that feature instead.
By default the thresholds are monitored continuously seven days a week using the All check box in the Days area.
You can select specific days using the check boxes for different days of the week.
30
If you select the Use Extended Host Schedule check box, you will be presented with a new screen for defining the
schedule.
Figure 30.
OCC Schedule Dialog Box
Using the Extended Schedule feature, you can define complex schedules (outside of the OCC) and then use them
for your thresholds. This window allows you to specify the polling interval and the schedule ID number. This is a
6-digit number that is defined in the SCHEDULE file. The SCHEDULE file is an edit file you maintain in the OVNM
subvolume, along with the HOLIDAY file.
There are sample files that are included with OVNM called SAMPSCHD and SAMPHOLI.
NOTE:
The Extended Schedule feature is available for all subsystems except the EMS and Scheduler subsystems.
SCHEDULE FILE
The SCHEDULE file must contain the definition of any Extended Host Schedule before you can specify it in the
OCC. The SCHEDULE file supports a variety of methods to define a particular schedule ID. The Schedule ID will be
listed in the first 6 columns of the file - and it must be exactly 6 digits. Only numbers are allowed, alphabetic and
special characters are not allowed. And the Schedule ID must be followed by a colon (:). The information that
follows the Schedule ID defines when the schedule would be active or inactive. An individual Schedule ID must be
defined on a single line of text, although you can combine Schedule IDs to create complex schedules.
An exclamation point (!) designates that everything on the line that follows is a comment and should be ignored.
You should define the conventions first that will be used when defining Schedule IDs. For example - you should plan
on supporting compound schedules. You may want to designate the range of schedule IDs from 000001 to 001000
(1 to 1000) for the simple schedules. These could be used within a compound threshold, but (if you decide) never
by themselves (so they can be changed without worrying about altering when a particular threshold will be active).
You may want to designate a range of IDs for weekly schedules, monthly schedules, year-end schedules,
holiday-based schedules, etc. You may want to designate a range of IDs for particular applications - so Payroll can
have a range, Distribution will have a range, File Transfer will have a range, etc. Or you may want your schedules
based on the type of schedule - jobs that run Monday through Friday, jobs that run only on weekends, job that run
only after standard working hours, third shift jobs, etc. But, you should spend some time planning the range of
numbers that will be used for what purpose.
And ideally, the Schedule IDs would be kept in sequential order within the SCHEDULE file.
Once you have created the conventions for what number to assign to the ID, you have to define what the schedule
will look like.
•
Days of the week are abbreviated as Mon Tue Wed Thu Fri Sat and Sun.
•
Commas are used to create a list (Mon, Tue, Wed)
•
Hyphens are used to define a range (Mon - Wed or 10:00 - 15:00)
•
Times are entered in a 24-hour clock format (00:00 thru 23:59)
31
•
If no time is entered, it assumes the time is 'all day'.
•
You can exclude holidays by creating a Holiday Schedule ID and then using EXCEPT SCHEDULE <holiday
schedule ID> when defining the Schedule ID. The Holiday Schedules are defined in the HOLIDAY file.
•
You can merge schedules by using OR. For example,
001000: sched 000103 or sched 000104 or sched 000105
HOLIDAY FILE
There are many times when systems are brought down for maisntenance or do not run on national holidays. If you
have thresholds that will alert you when the application is not running, you do not want to be alarmed if the
application is supposed to be down. This is what the HOLIDAY file is used for. You create a Holiday ID and then
define the dates that are part of that holiday. The Holiday ID can contain numeric and alphabetic characters and the
underline (_). The Holiday ID is followed by a colon just like in the Schedule file. If a particular holiday always falls on
the same DATE (like January 1), you can enter Jan 01 and every January 1st will be considered a holiday. If your
holiday date changes from year to year, you will need to edit the holiday file each year to account for that. If this is
needed, it is recommended that you enter 2-3 years into the future so you don't have to rush to change this file
during a 'freeze' period. You will need to remember to update it each year, but the updates could be performed at
any time.
Once you have completed your changes to the SCHEDULE or HOLIDAY files, you need to run the ZTCHGSCH Tacl
routine. This routine will edit your changes and if there are no errors, it will send a message to the monitoring
program informing it of the changes. For more information about this, see the appendix in the User and Installation
guide that describes the use of the ZTCHGSCH Tacl routine
32
Monitoring
Monitoring is inactivated by default on the HPE NonStop host when OCC is started. The OCC Monitoring Gateway
is responsible for the overall monitoring. When any object’s monitoring is started, OCC forwards the appropriate
commands to the OCC Monitoring Gateway, which further reads the information from the Objects database and
starts the monitoring process. The HPE NonStop host will do the monitoring as per the checks specified for the
threshold configuration.
The initial monitoring status of the configuration can be specified using the Monitoring box in the Threshold
dialog box while creating a threshold configuration.
Figure 31.
OCC Threshold Dialog Box with Monitoring Box
The objects can be in two different states. The two different states are as follows.
•
Active: This option activates monitoring for the objects that are to be monitored at a particular time of the
day. OCC polls each configured object to check for any violations.
•
Inactive: This option inactivates monitoring for the objects that are not to be monitored at present and OCC
will temporarily stop polling the configured objects for any violations. This is the default option.
First, the HPE NonStop host checks for the value in the Monitoring box. It will proceed with monitoring only in case
the value has been set as Active. If the value in the Monitoring box is Inactive, it will skip monitoring for that object
and move on to the next one.
Next, it checks for the parameters like Poll Interval set in the Schedule dialog box when the threshold was created.
Depending on the values specified in this dialog box, it will proceed with the appropriate actions assigned for that
object.
Refer to the Scheduling section for more details on the various parameters in the Schedule dialog box.
NOTE:
Inactivating the monitoring is considered as a Pause in the monitoring process. This means that OCC will stop
issuing events for the objects in the Violation State and the database will not be modified. If at the time of
inactivation the object was in a violation state, the state after activation will be the same as before inactivation,
even though the object could be in a normal state now. This situation will be in effect until the next poll interval.
This is applicable for inactivating at the object, configuration and system levels.
33
Monitoring can be specified at three different levels; the overall monitoring of the Node, the Threshold level, and
the Object level. The commands through which you can configure monitoring can be accessed using the
Monitoring menu, the Monitoring bar and the right-click menus of the Threshold and the Objects pane.
•
Node Level Monitoring: You can configure the overall monitoring of a node by using the Activate Node
Monitoring and the Inactivate Node Monitoring commands. These can be accessed from the Monitoring
menu and the Monitoring bar. Only one of the two options is enabled at a given time. Selecting any one of the
options automatically disables the other.
•
Threshold Level Monitoring: Monitoring for a selected threshold and all its corresponding objects can be
configured using the commands on the Monitoring menu (Activate Config Monitoring, Inactivate Config
Monitoring), the Monitoring bar (Activate Configuration Monitoring, Inactivate Configuration
Monitoring), and the right-click menu of the Threshold pane (Monitoring Active, Monitoring Inactive). Only
one of the two options, activating or inactivating is enabled at a given time. Selection of one disables the
other.
•
Object Level Monitoring: You can configure the monitoring of selected Object(s) by using the Activate
Object Monitoring and the Inactivate Object Monitoring commands in the Monitoring menu and on the
Monitoring bar. This action can also be performed using the Monitoring Active and Monitoring Inactive
commands in the right-click menu of the Objects pane. Only one of the two options, activating or inactivating
is enabled at a given time. Selection of one deactivates the other.
34
Actions
Once thresholds are defined, OCC continuously and automatically monitors your chosen system resources and
system objects. If a violation is detected, indicating that a system object is no longer in the desired operational
state, OCC immediately triggers pre-programmed action(s). Pre-programmed actions can include: generation of an
EMS event message, transmission of e-mail alerts to support personnel and/or execution of automated recovery
scripts to correct the original fault. You choose the type of action you want to execute for each violation, however,
OCC will always generate an EMS message. To access the Actions dialog box, click the Actions button in the
Threshold dialog box.
Figure 32.
OCC Actions Dialog Box
The various types of actions have been described in this section.
•
EMS Alerts
•
E-Mail Alerts
•
Recovery
•
eEvents
35
EMS Alerts
OVNM always generates EMS alerts in response to threshold violations. EMS alerts can be configured using the
Alert tab page in the Actions dialog box
Figure 33.
OCC Actions Dialog Box Alert Tab Page
The Exception section of the Alert tab allows you to adjust the initial violation, repeat, and escalation event
messages. The Severity box allows you to set the internal OVNM severity levels as Critical, Major, Minor, Warning,
or Info for the violation messages generated in response to the threshold violations.
NOTE:
The default severity level is Critical.
Severity is shown in the EMS message. This value also dictates what severity will be displayed in ObjectMap and
ObjectStats. Note that the severity on this panel does not affect the severity COLOR shown in Console. That value
is based on the value in the eEvents panel. You must be aware of the value in the Tools, Options, Keep, and
Severity in the Sync option. Based on how that is set, changes to this field may or may not be automatically
transferred to the Violation Severity field in the eEvents panel.
You determine how frequently the Exception Event should be generated using the Repeat Every box. The default
value is 9 minutes, but the unit can be changed to seconds or hours and the required frequency value can be
entered as desired, from 00 to 59. Entering a value of 00 allows only a single exception Event to be generated. The
polling interval specified in the Schedule dialog box determines how often OVNM checks the object state when the
object is in the normal state.
The Repeat Every interval determines how often the violation message is generated. The object will always be
checked based on the polling interval. So if the polling interval is 5 minutes and the Repeat Every interval is 15
minutes, the object will be polled every 5 minutes regardless of its current state (normal or in violation). However,
OVNM will only report it as in violation, once every 15 minutes. As soon as it determines it is back to normal, it will
generate a ‘back to normal’ EMS message. This feature is not currently available for EMS-driven thresholds. Repeat
messages are not generated until the Repeat Every interval is exceeded, so it is recommended that this value be a
multiple of the polling interval.
The selection of the Escalate check box determines when the first Escalation Event is generated after the initial
violation, by specifying data in the Log Escalation Event After box. Once Escalation Events are being generated
36
for a violation, Exception Events are no longer generated. The default value is 30 minutes, but the unit can be
changed to seconds or hours and the required frequency value can also be specified, from 01 to 59. It must be
greater than the Poll Interval value and must be greater than Repeat Every IF Repeat Every is not zero. By setting
the Repeat Every value to zero, OVNM will only generate an alert when the object goes into an abnormal state and
when it has continued to be in an abnormal state for time specified by Log Escalation Event After. This feature is
not currently available for EMS-driven thresholds.
The behavior of AO for escalation event in case of Repeat Int: 00
When the Repeat Interval is 00 min and the Escalation Int is 2 mins, the ORMCOM is logging escalation event in
every 2 mins
13-12-30 02:07:06 \VEGAS.$VOM01
*TANDEM.OVMON.H01
002474 OVNM: File
\VEGAS.$DATA01.USER.TEST1, Escalation
If : File^eof Greater Than 0, Current :
2098, Current State = Critical, Prev State
= Critical, Sampling Int = 30 SECS
13-12-30 02:09:06 \VEGAS.$VOM01
*TANDEM.OVMON.H01
002474 OVNM: File
\VEGAS.$DATA01.USER.TEST1, Escalation
If : File^eof Greater Than 0, Current :
2098, Current State = Critical, Prev State
= Critical, Sampling Int = 30 SECS,
Escalation int = 2 MINS
When an Escalation event occurs the event will have a unique Event Number, and the text Escalation will be
included in the original violation text. You have the option of sending an email (assuming Email server is
configured) in case of an escalation. For details, refer to Email Alerts.
Specifying Unique Escalation Actions
It is also possible to perform different actions for the escalation event that OVNM generates. If you have specified
the Log escalation event after time period, you can create a separate EMS threshold for that event and then define
unique actions, Emails and/or messages to the Enterprise Management system. Normally, you will define
everything you need to on the original threshold definition. But when the object has been in a violation mode too
long (has reached its escalation time) and you need to take a different action, by creating an EMS threshold on the
OVNM-generated EMS message, you can specify different activities. The activities defined on the original threshold
(email and auto-recovery) will still happen – these ‘escalation’ activities will happen in addition to those. To use this
feature, configuration changes must be made to the OVNM configuration file OCCCONF.
To use this feature for Email and recoveries, you must EDIT and add the CHECKALLEVENTSFOR ACTION
parameter to the OCCCONF file.
SET OCC CHECKALLEVENTSFORACTION
YES
This line must be placed between the Customer Changes #1 lines in the OCCCONF file.
Without those lines, EMS violation messages that are generated by OVNM will NOT be checked to determine if
there are EMS thresholds defined. The standard process is for OVNM to ignore its own events for that function.
An EMS threshold for the OVNM-generated escalation event needs to be added via the Object Configuration Client.
The escalation event numbers can be found in Threshold Events section of the Object Reference guide. The SSID
will be TANDEM.OVMON.
While creating the EMS threshold, you can use the normal process for defining the email, recovery and/or eEvent
message that will be used for the escalation event. Please note that on the Email page, there is a check box for Mail
on Escalation Only and Mail on Normal. Neither of these options actually applies to EMS thresholds. These
options are no longer available for EMS thresholds with OVNM 5.3.2 onwards.
In addition to specifying additional email and/or recovery options for the Escalation event, you can also alter the
message that is sent to the Enterprise Management system (the eEvents panel). But in order for this to work, you
need to add the same CheckAllEventsForAction parameter as above to the OVNMCONF file, between the Customer
Changes #1 lines. In this case, you will use SET OVNM instead of SET OCC. Note that if you use this option, the
37
message defined in the normal threshold will be overridden with the message defined in the EMS threshold – you
will not receive two messages in the Enterprise Management system. This does allow you to have one message for
the standard violation alert (and repeated alerts), a different message for the ‘back to normal’ event and a third
message for the Escalation event if you create 2 EMS thresholds (one for the violation alert and one for the
escalation alert).
38
E-Mail Alerts
Once thresholds are defined, OCC continuously and automatically monitors your chosen system resources and
system objects. If a violation is detected, indicating that a system object is no longer in the desired operational
state, OCC immediately triggers transmission of e-mail alerts to support personnel. This is to notify the concerned
people that manual corrective actions need to be taken. You can also configure to send e-mail alerts when the
object returns to its normal state. The e-mail alerts can be configured using the Mail tab page in the Actions dialog
box, which can be accessed using the Actions button in the Threshold dialog box.
Figure 34.
OCC Actions Dialog box with Mail Tab Page
The e-mail feature is disabled by default. To enable e-mail escalations in case of a violation, you can use the Mail on
Violation check box. Use the Mail on Normal check box to enable e-mail alerts when the object in violation returns
to its normal state. After enabling the feature, if you deselect the check box, e-mail alerts will be suspended.
Use the To box to specify the e-mail addresses, profile names or the distribution list to whom the alerts should be
sent. If multiple addresses are used, use commas and/or semicolons to separate them. The To box can accept 240
characters. It is mandatory to fill-out the information in this box.
In the Subject box, you need to specify the subject for the e-mail. The text in this box should not exceed 80
characters. It is mandatory to specify the subject for a mail.
The Repeat Count box allows you to specify the number of e-mail messages to be sent in case of a violation. These
e-mail messages will be sent while the object remains in violation and the counter value will be cleared once the
object goes to the normal state. If the object goes in a violation state again, e-mail messages will be sent until the
Repeat Count value is reached. The default value is set to 2 and can take a value in the range of 1-32767.
NOTE:
The Repeat Count value does not apply to the EMS subsystem thresholds. In this case, e-mail messages will be
sent to the specified recipients whenever a violation condition is met, unless the Burst Definition data is
configured.
The actual message text to be sent is specified in the Violation Message box in case of violation and the Normal
Message box when the object comes back to the normal state. You can type a maximum of 1024 characters in this
box. But with substitution, the maximum size of the text can be 2048 bytes.
The Mail on escalation only check box can be selected to allow OVNM to send e-mail alerts only when an
escalation event is generated. This suppresses the email sent for a violation, but still allows the email on normal.
Even though this check box is available on EMS thresholds, it is not supported since there is no way to define an
‘escalation time period’ for EMS thresholds.
39
The message text supports a list of parameters, which can be accessed using the Parameter list link. Clicking the
Parameter list link displays the Substitution Parameters dialog box. This lists all the parameters that can be
substituted during message construction. To use a parameter, select it from the list and Click the Insert button.
Figure 35.
OCC Actions Dialog Box Mail Tab Page with Substitution Parameters
For example, if the file name is taken from the variable %s%, the Subject token will contain the file name that is in
violation. The same is true of the Node (%n%) and the Current Value (%cv%) of the threshold being checked. In
this case the violation will be for a file becoming full and %cv% will contain the current percentage size of the file
being monitored. This type of substitution is very generic simply because the substitution parameters provide all
the information, therefore this message will suit all file full monitoring violations.
The description for these parameters is given in Appendix E: Substitution Parameters.
These parameters are supported in the Violation Message, Normal Message and the Subject fields. The parameters
are case insensitive and need to have the % symbol typed in both the sides as denoted.
40
Recovery
One of the most important features of OVNM OCC is Recovery, which triggers automated actions in case of a
violation. You can define the recovery actions to be taken for different violation conditions. This feature is disabled
by default and has to be enabled manually. Recovery can be activated or inactivated at the configuration and the
object level using OCC.
•
Threshold Level Recovery: To initiate recovery at the configuration level you can use the Activate Config
Recovery and Inactivate Config Recovery options in the Recovery menu. These two options can also be
accessed using the Activate Configuration Recovery and Inactivate Configuration Recovery icons on the
Monitoring toolbar.
•
Object Level Recovery: To activate or inactivate recovery at the object level you can use the Activate Object
Recovery and Inactivate Object Recovery options in the Recovery menu. These options are also available as
the Activate Object Recovery and Inactivate Object Recovery icons on the Monitoring toolbar.
Recovery can be enabled manually using the Action tab page in the Actions dialog box.
Figure 36.
OCC Actions Dialog Box Action Tab Page
You can select the actions to be executed in case of a threshold violation using the first Command box. The default
value is None, which indicates that no recovery action will be triggered. Selecting the User defined command
option enables a second Command box, where you can enter the command to be executed. You can specify any
command that can be executed from a TACL prompt, like TACL command, TACL macro or Command Line
Utility/Program; in the User-defined command option. For more details please refer to Log Success/Failure of User
Defined Command for Recovery section in the OVNM User guide. To use substitution parameters in your command,
click the Parameter list link.
There are also many thresholds that have pre-canned recoveries in the drop down list. Not every threshold has
these, but if they do, you should think about using these instead of writing your own recovery.
A generic ‘recovery’ option for all thresholds is “turn monitoring off/on for group/subgroup”. This is typically used
with EMS thresholds to automate the function of turning monitoring off or on for a set of objects. Using this
feature, you can group a variety of objects into the same group/subgroup and then create an EMS threshold for a
specific event that would use the Turn monitoring off for group/subgroup. When the EMS event is generated,
OVNM will consume it and automatically turn monitoring off for all objects that have the same value for group and
subgroup that was specified in the recovery. The same mechanism can be used to turn monitoring back on. This is
quite useful when you have a planned outage and do not want to send alerts or perform recoveries for objects you
know are going to be down. Another option instead of using EMS thresholds is to use the ZTALTMON Tacl utility.
This is described in more detail in the User Guide, in Appendix C: OVNM Utilities.
41
You can schedule recovery 24 hours, seven days a week using the 24x7 option button in the Schedule section.
Define a customized schedule using the User Defined option button, which enables the Schedule button. Clicking
the Schedule displays the Schedule dialog box. Use the various options available on the Schedule dialog box to
specify a customized recovery schedule.
Figure 37.
OCC Recovery Schedule Dialog Box
The default Delay Interval value is 05 minutes. This means that the OVNM recovery process on the HPE NonStop
host will check for object state changes every 5 minutes. The unit for Delay Interval can be changed from minutes to
seconds or hours. The frequency can also be changed within the range of 01 to 59, giving a possible range of 1
second to 59 hours for the time between violation checks.
The daily default Start Time and Stop Time are 00:00 and 23:59, respectively. This indicates that OVNM recovery
will be active throughout the day, based on the HPE NonStop system time. You can enter a different recovery start
time and stop time by entering the appropriate hours and minutes in the Start Time and Stop Time boxes,
respectively. By default the thresholds are recovered continuously seven days a week using the All check box in the
Days group box.
You can select specific days using the check boxes for different days of the week. Select the Next scheduled day
check box to start recovery on the next day scheduled.
You can activate or inactivate recovery using the Recovery box in the Action tab page.
The Log area is used to specify the message log to be generated if the recovery is a Success or a Failure. The three
options available are None, User Text and Default. If you select None, no message will be generated. You can
specify the text for the message by selecting the User Text option or log the default message using the Default
option.
For details on various recovery methods, refer to Recovery Methods section in the Object Reference guide.
eEvents
OVNM provides direct correlation and formatting facility for leading Enterprise Management Console solutions
provided by Tivoli, HPE OM and/or SNMP. Each one of these Enterprise solutions supports specific event
information in the event that triggers the user-defined policies at the Enterprise level. For instance, HPE OM view
makes considerable usage of the Service area impacted by the failure. This information can be predefined and
formatted by OVNM, before it is presented to the HPE OM. Similar enhancements to support Tivoli TEC and HPE
42
Operations are also available. The event translation and forwarding facility is designed to support any event
produced on the HPE NonStop platform to be forwarded to the Enterprise Management system.
This feature is available for all thresholds.
The eEvents tab page allows the user to achieve the following using the various radio buttons.
•
Disable Events: This option can be selected to disable the forwarding of the events. This option is selected by
default. A new default value can be defined in Tools/Options by selecting the default Enterprise Management
system.
•
HPE OM/OVO: Select this option to forward the events to the Console or the HPE OM interface.
•
Tivoli: Select this option to forward the events to the Tivoli Management console.
•
SNMP: Select this option to forward the events to the SNMP Adapter console.
The other fields are displayed on the tab page depending on the radio button selected.
Figure 38.
OCC Actions Dialog box − eEvents Tab Page
43
The eEvent Status drop-down box allows the user to specify the action to be performed on the event.
•
ACTIVE: If selected, this option will allow the processing of the message as described in the eEvents tab page
and send the message to the Enterprise console. This is the default option.
•
INACTIVE: If selected, this option will not apply the instructions defined in the Events tab page. The overrides
will not be applied to the message but the message will still be sent to the Enterprise console with the default
EMON formatting.
•
DROP THIS EVENT: If selected, this option will not forward the message to the Enterprise console. This will
block the message from being forwarded. No other information needs to be provided when this option is
selected.
•
CUSTOM: This option is available only when the Tivoli option is selected and the customized message is
forwarded to the Tivoli Management Console. OVNM allows logging of any user message with user supplied
class and/or user supplied slots. The CUSTOM option allows the user to define the message class and its slots.
During message construction, the user can use a static text, supplied substitution parameters or any
standard/user token value of the actual EMS message.
The format to define the message layout is simple and follows the below mentioned convention.
MsgClassName;
soltName=’slotVal’;
slotName=’slotVal’;
……………………
……………………
slotName=’slotVal’;
Where, slotVal could be a static text, supplied macro or User/Standard EMS token
Figure 39.
OCC Actions Dialog Box Events Tab Page – CUSTOM eEvents Status
In the example above, the message class will be set to HOST_MRO_OPS. The severity slot will be set to CRITICAL.
The msg slot will be set to the first 256 bytes of the message text. The msg_type slot will be set to ‘actionid: Value
of the supplied token’. The location slot will be set to the ‘collName: Value of the supplied token’. The value of the
ownership will be set to ‘Process: Value of the supplied token’.
If the Append mode check box is selected, the slots will be appended to the standard message format and the
message class will be decided using the cdf file conditions.
The Violation Severity box allows you to change the severity of a message before it is forwarded to the Enterprise
console. These severity settings match those available for the Enterprise console selected.
44
The options available for HPE OM/OVO and SNMP are as follows:
•
CRITICAL
•
MAJOR
•
MINOR
•
WARNING
•
NORMAL
•
ORIGINAL
The options available for Tivoli are as follows:
•
FATAL
•
CRITICAL
•
MINOR
•
WARNING
•
HARMLESS
•
ORIGINAL
The severity value of the message will be overridden with the specified value if any of the Severity options other
than ORIGINAL is selected. If ORIGINAL is selected, severity override will take place and the value specified in the
Action panel is used. The value specified on the eEvents panel impacts the value that is used in the Console and
the Enterprise Management System. If the Tools/Options/Keep Severity in the Sync option is turned ON, then any
change here affects the value in the Action panel. If that option is turned OFF, then it is possible to use a different
severity in the Enterprise Management System and Console, then the value displayed within the text of the EMS
violation message.
Specify the Object Name, Manager Name, Customer Name, Location, Service ID, Message Group/Layer and
Event Text Replacement in the various fields available.
The Insert from file link on the eEvents tab page allows loading the message format from a saved template file.
This is a .txt file that contains information to specify the Custom message format. This allows you to define a
common format that can then be used for many thresholds without having to enter the same text over and over
again.
45
Click the Parameter list hyperlink to view the Substitution Parameters dialog box. All the Supplied macros that
can be substituted during message construction are displayed.
Figure 40.
Substitution Parameters Dialog Box
The Token list hyperlink displays the Event Token Numbers dialog box. The dialog box displays a list of tokens.
Figure 41.
Event Token Numbers Dialog Box
All the displayed tokens in the list are from the standard zspic C header files. These files are installed by using the
Host Installation Client (Tools  Get Token Files). Third party C header files can be added as well using the same
procedure.
46
EMS Actions
ObjectMAP
Polling and escalations are not allowed for EMS thresholds as they are driven by EMS messages and not by polling
at certain intervals. ObjectMAP is an application that brings real time and customized monitoring of object states at
the Group, Sub-Group, System, Subsystem, Threshold and Object levels for your Enterprise.
NOTE:
The ObjectMAP tab page is displayed in the Actions dialog box only when the EMS subsystem is selected.
This tab page is used to define how to add, update or delete objects from the ObjectMAP GUI that are triggered by
EMS thresholds.
Figure 42.
OCC Actions Dialog Box ObjectMAP Tab Page
Select the Do not map event radio button in case the event is not to be mapped. That is the default – so if you do
nothing with this screen, EMS thresholds will not show up on ObjectMap. To define how to add or update
information on ObjectMap for EMS thresholds, select the Add/Update radio button. The Delete radio button is
used to specify the conditions that would cause an object to be deleted from ObjectMAP once they are met.
The other fields on the tab page get enabled when you select the Add/Update or Delete radio buttons. To map an
event using default attributes, select the Map event using default attributes radio button. This is the default
option. The event can also be mapped using rule numbers using the Map event using rule number radio button
and specifying the number in the corresponding field. Knowledge of RDL (Rule Definition Language) is required to
use this feature. RDL is used to write the code for the rule. This is included primarily to support people who used
PNA – not for new OVNM customers. To map an event using the subject or the manager token number, select the
Map event using radio button and specify the subject and manager token numbers in the Subject token number
and Manager token number boxes, respectively.
47
Selecting the MAP event using radio button also activates the Lookup token numbers hyperlink. Clicking the
hyperlink displays the EMS Event Token Numbers dialog box.
Figure 43.
EMS Event Token Numbers Dialog Box
This dialog box can be used to select the Subject Token Name and Manager Token Name to get the
corresponding values in the Subject token number and Manager token number fields.
Figure 44.
OCC Actions Dialog Box ObjectMAP Tab Page
NOTE:
The token information is taken from the files, which can be imported using the Tools - Get Token Files option in
the OVNM Host Installation Client. For details, refer to User guide.
You can also specify the duration for which the object is to be displayed in ObjectMAP using the Auto-remove
object check box. This is used if there is no event generated that can be used to remove the violation from
ObjectMAP. Using this option allows you to automatically have items removed from ObjectMAP. The risk of using
this option is that an item could be removed before it has actually been resolved. Select the After radio button and
specify the number of hours or minutes after which the object is to be removed from the map. Selecting the At time
option allows you to specify the time when the object is to be removed from the map.
48
The Group Name and Threshold name boxes are used to specify the group and threshold names, respectively.
These fields must match to link the UP and DOWN EMS messages. These values will be displayed in ObjectMAP.
NOTE:
The initial messages generated by OVNM after checking the status of objects for the first time allows the current
state of the object to be mapped to the ObjectMAP. In case these messages are causing you problems, then the
SkipEMS: Yes option or SkipEMS: All options can be used to suppress the first EMS message.
The SkipEMS: Yes option suppresses the first EMS message if the object is in Normal state and the threshold has
been defined with the eEvents pane. The SkipEMS: All option suppresses the first EMS message if the object is
Normal regardless of whether or not an eEvents record was defined.
The default is value is set as SkipEMS: Yes. To change this option you need to edit the MONCONF file and create
a CUSTCHGS Tacl routine. For more information about how to create the CUSTCHGS routine, refer to Appendix
Q in the User Guide.
The EMSON utility turns the flag ON for every EMS threshold. This enables OVNM to send ALL the EMS
thresholds to ObjectMAP, even if the Map Event to ObjectMAP check box has not been configured for that
threshold. To run the EMSON utility, execute the run EMSON / in <your ORMCONF file>/ command at the TACL
prompt.
NOTE:
In case of linked EMS thresholds, the DOWN object state is displayed in the ObjectMAP until an UP event is
detected by OVNM. Once an UP event occurs, the DOWN state is deleted from ObjectMAP automatically.
However, if the DOWN and UP states of the EMS thresholds are not linked then once the DOWN event is
detected, it will be displayed in ObjectMAP and will not be deleted until a manual action is taken.
49
eBurst
OVNM provides the facility to define the burst criteria to be used to suppress the burst of EMS messages. The
eBurst criterion is linked to an individual EMS threshold. The eBurst tab page in the Actions dialog box is displayed
only when the EMS subsystem is selected.
Figure 45.
OCC Actions Dialog Box eBurst Tab Page
•
eBurst Panel : This is the panel you will use to define how a burst should be detected. You have the option of
processing all of the messages until a burst is detected or ignoring all of the messages until a burst is
detected. If you check None, the Burst Definition record will be deleted (if one existed).
•
Process Until Burst: Use this option if you want the first EMS message to cause an email, recovery or
message sent to Console and the Enterprise Management system (such as HPE OM). This option will process
every EMS message until the burst is detected.
•
Ignore Until Burst: Use this option if you do not want any of the EMS messages processed at all until an
excessive number of them are seen. For example, if an application generates error messages occasionally, and
you don’t care about them until more than 100 of them are generated in short time duration, then you would
use this option. Using this option will prevent emails, recoveries and messages to Console and the Enterprise
Management system until an excessive number are consumed.
•
Burst = x events within y minutes: This is the actual burst definition. This describes how many events in
what time frame need to be consumed before a burst is declared as active.
•
Event Subject


BLANK: If you leave this field blank, the burst detection logic will not consider the value in the subject of
the EMS message when creating ‘burst threads’. In this case, all events from the same SSID, regardless of
the subject will be counted towards the burst. The ‘subject’ of an EMS message is defined as the one with
the ‘subject token’ marker. For example, TANDEM.PATHWAY TCP stop EMS messages will contain the
name of the TCP as the subject. You must determine what the subject of an EMS message is before using
this feature – some applications do not use what you might expect to be the subject. To determine the
token that contains the subject marker, you can use EMSA, or some other utility that shows the subject
marker.
ASTERISK: If you enter an asterisk, you are asking OVNM to maintain separate burst threads for each
unique subject. So if Pathway generates 100 TCP down EMS messages, one for each TCP, then OVNM will
create 100 burst threads, each with a count of one event. Therefore, no burst will be detected, since only
one EMS message was consumed for each individual subject.
50

A SPECIFIC VALUE: If you enter a specific value here, only the EMS messages that also match the subject
you specified will be considered when deciding if there is a burst.
•
Reset: This is used to define when the burst should be considered as expired. Once a burst has been
detected, no more EMS messages will be processed until after the amount of time defined in this field. The
start of the burst will be defined as the EMS generation time of the first EMS message that is part of the burst
criteria. So if the burst is defined as 5 messages in 5 minutes, the reset time is defined as 30 minutes, and the
very first EMS message is generated at 12:00, 2 more at 12:02 and 2 more at 12:03 (5 total), the reset time will
be at 12:30 – 30 minutes after the first message that was part of the burst criteria. Using the same burst
criteria, if a message was consumed at 12:00, 12:01, 12:02, 12:04, 12:06, 12:08, 12:09; 12:10: 12:10, then the first
message that is part of the burst will be at 12:06, the burst detected message would be generated at 12:10 (the
second 12:10) and the burst will be ‘over’ at 12:36.
•
Generate start/end EMS burst notification messages: If this check box is checked, then both ACC ($OVOCC)
and EMON ($OVEMN) will generate EMS messages when they detect a new burst and when the burst expires.
If this box is not checked, then these messages will not be generated by OVNM.
EMS Burst Suppression Considerations
The following methods can be used to suppress duplicate EMS messages from being processed and/or sent to
Enterprise Managers.
1.
Collector Level Burst Suppression
The first method involves suppressing the duplicate EMS messages at the collector level. You will need to use
EMSCCTRL to configure this option. This method eliminates the workload from OVNM to implement burst
suppression. Refer to the appropriate HPE documentation for more details.
2.
EMS Distributor Level Burst Suppression
The second method involves suppression at the EMS Distributors that are used by OVNM. This method also
eliminates the workload from OVNM to implement burst suppression. Refer to the appropriate HPE documentation
for details.
3.
Object Configuration Client Level Burst Suppression
The Object Configuration Client can be used to define the EMS burst definitions for each EMS threshold where
burst suppression should be used. Burst suppression requires an EMS threshold to be defined .
When you create an EMS threshold, you specify the SSID, Event number and any other attributes that describe the
event(s) you want captured. The Object Configuration Client allows you to use wildcards in various portions of the
threshold definition. For example, you can create an EMS Threshold for the SSID TANDEM.PATHWAY and all
events (*). You can specify that the event text needs to contain a particular string. All of these attributes are used
to determine whether or not the EMS message should be processed by OVNM, and what actions should be
performed. You can configure it to send an email, or perform an automated action (user-defined command). You
can also use the EMS threshold definition to define how you want the message sent to HPE operations
Manager/Console or any other enterprise management system (using the eEvents panel).
When OVNM is deciding whether or not an EMS message should be considered part of a burst, it will always
compare the SSID and EVENT – regardless of how the EMS threshold was defined. So, for a given EMS threshold,
there could be several “threads” of burst definitions. For example – if you define an EMS threshold for SSID
TANDEM.PATHWAY and the event number you specify is an asterisk (all events), then each unique event number
that Pathway generates will be treated as a separate burst thread. So Pathway could generate 100 events and still
not cause a ‘burst’, if each event has a unique event number. Burst criteria can also use the SUBJECT of the event.
In the Object Configuration Client, if you enter a specific value in the Event Subject field in the eBurst panel, then
only events with that subject will be considered when ‘counting’ EMS messages (regardless of how the EMS
threshold was defined). If you leave the Event Subject blank, then subject will NOT be used when counting events –
in other words, only the SSID and Event Number will be used when counting events. In that scenario, ten events
with different subjects will all be counted in the same bucket (or burst thread). If you enter an asterisk into the
Event Subject field in the eBurst panel, then each unique subject will be treated independently. So if we use the
TANDEM.PATHWAY example again, and you are capturing TCP down events, then a given TCP will have to
generate enough of the down events for OVNM to consider it a burst. If you have 100 TCP’s and they all go down,
this would not be considered a burst since each subject would be different. If you want it to be considered a burst,
then leave Event Subject blank.
51
When deciding whether or not you should define the Event Subject in the eBurst panel, keep in mind how your EMS
threshold was defined. If you used the EVENT SUBJECT or EVENT SUBJECT MANAGER condition when defining
the threshold, then you may not need to specify anything in the eBurst panel for Event Subject since the threshold
criteria is already limiting which subjects are processed.
Since a given EMS threshold could have several or even hundreds of separate burst threads, you might have to
adjust some parameters. These parameters need to be defined between the CUSTOMER CHANGES #1 lines in the
OCCCONF and OVNMCONF files. Burst definitions are used by BOTH halves of the OVNM application – the
recovery/email portion (ACC) and the Enterprise/Console portion (EMON).
THREADTABLECOUNT is used to define the number of entries to be used in the burst thread table. The default
value is 100. This means that OVNM will support up to 100 individual/concurrent burst threads at a time. If you
need more than that, you will need to add a SET statement to the OCCCONF/OVNMCONF files. If this value is too
small, OVNM will generate Event 142 “Burst Thread Table is full. Increase THREADTABLECOUNT.” After you
increase the value, you will need to bounce OVNM for the change to take effect.
BURSTLINKCOUNT is used to define the number of entries in the burst link list table. For each unique Burst
Thread, an entry will be added to the burst link list for each EMS message received before the burst is declared.
These entries are rather small and consist of the time that the EMS message was generated. So if you expect 20
individual burst threads, and each of your EMS threshold eBurst definitions say that the burst requires five
messages, then this value will have to be at least 100 (20 * 5). If this table fills up, OVNM will generate EMS Event
143 “Burst Link List Table is full. Increase BURSTLINKCOUNT."
When setting the values for THREADTABLECOUNT and BURSTLINKCOUNT you should always leave plenty of
extra room. If either of those tables becomes full, the burst definition feature may not work properly.
BURSTCLEANUP-INTERVAL is used to tell OVNM how often to spin through the various tables to delete entries
that have expired (are longer than the burst reset time or the “within” time of the burst definition). The default for
this parameter is 1 hour (60 minutes). The value you specify here is in MINUTES. When this timer expires, OVNM
will spin through all the burst tables and delete any entry that is no longer required. It will also check to see if there
are any active bursts whose Max Burst Reset time has been exceeded. If so, that burst will be reset (and the end of
burst message will be generated). Cleaning up the old entries will make room for new entries. This is really only
important when events are consumed that are potential burst messages. When they are consumed, they will take
up entries in these tables. If OVNM never sees them again, this is the only way to delete those entries.
There are other parameters that can help improve the efficiency of OVNM as it processes EMS thresholds.
EVENTRULEFILEREADLEVEL is a flag that signifies whether or not OVNM should maintain the contents of the
EVNTRULE File in memory. This is the file that describes the EMS thresholds and is linked to the Burst Definition
records. If this is not in memory, then every time an EMS message is received, OVNM must read this file to
determine if the EMS message should be processed any further.
EEVENTSFILEREADLEVEL provides the same function for the eEvents file. This is the file that contains the data
from the eEvents panel in the OCC.
When the memory feature is turned on, then changes to these files will NOT be recognized by OVNM for a period of
time after the change was made. This is coded this way to reduce the likelihood of reading these files into memory
multiple times as you are making updates. A parameter (UPDATE-WAITTIME-MINS) can be modified to adjust the
wait time between the time the last update was made and when OVNM will re-read the files into memory. OVNM
will re-read the file into memory once that number of minutes has gone by with no additional changes. In other
words, if this is set to 5 minutes (the default), and you make a change every minute for 10 minutes, OVNM will not
re-read the file until 15 minutes have expired since the first update – which is 5 minutes after the last update. With
the default value, there will be at least a 5 minute delay between the time a record is changed and when OVNM
recognizes the change. You can set this lower if you want, but if you set it too low, then OVNM could end up
reading the file before you are actually done with your changes, causing it to re-read the file multiple times. If you
do not have very many eEvents or EVNTRULE records, then it may make more sense to have a very small value (1
minute). If you have 1000’s of records, then you will want a higher value to limit the chances of re-reading the file
multiple times. When making changes to this parameter, you need to add the SET statement between the
CUSTOMER CHANGES #1 lines. If you make it to the SET statement that is already in the OCCCONF/OVNMCONF
file, then the next time a change is made via the HIC or ALTROVNM, your change will be lost.
When the BURSTDEF file is re-read into memory, all information regarding bursts is lost – everything is reset to
zero, so you will want to be careful when making changes that impact the BurstDef file. When this happens, OVNM
52
will generate EMS Event 148 “Reloading burstdef file – all burst info will be reset”. In addition, any existing burst will
end, but no ‘expired’ message will be generated – the internal tables are not reviewed before wiping them clean.
If you have checked the “Generate start/end EMS Burst notification messages” check box in the eBurst panel, then
OVNM will generate messages whenever a burst is detected and when the burst has expired (exceeded the reset
time specified). Some of these messages will also include the number of messages that were suppressed. When it
is a “process until burst”, only the burst-expired EMS message will contain the number of messages suppressed.
For “ignore until burst”, both the ‘burst detected’ and ‘burst expired’ messages will contain the number of messages
suppressed. This counter is reset whenever the EMS message is displayed and whenever the BURSTDEF file is
re-read into memory.
When the burst is detected, OVNM will generate event 146 (for process until) or 147 (for ignore until). The message
will look like one of the following:
Process Burst Detected SSID/Event:
Ignore Burst Detected -
TANDEM.PATHWAY.D44/1043 Subject: TCP1
Suppressed 9 events.
TANDEM.PATHWAY.D44/1043 Subject: TCP1
When the “ignore burst” message is generated, it will show you how many events were suppressed since the last
time its counter was reset. The counter can be reset after a BurstCleanUp Interval as well, so this count may not
include every single EMS message that was suppressed prior to the burst being detected. The Subject will only be
reported if a specific subject is involved in the burst.
When the burst reset period ends, OVNM will generate event 144 (for process until) or 145 (for ignore until). The
message will look like the following (Process Burst will be Ignore Burst for an ignore until burst definition):
Process Burst Period ending - exceeded Reset Burst Period. Suppressed 1 events. SSID/Event:
TANDEM.PATHWAY.D44/1047 Subject: TCP1
53
Group & Subgroup Management of Objects
OVNM allows the user to manage objects in groups and subgroups. This feature allows the user to escalate objects
to the EMS or Enterprise Consoles based on their location or business significance.
For instance, all processes belonging to an ATM system can have a group name of ATM and SNAX objects can have
subgroup names of SNAX. In order to display objects that reported events on SNAX and belonging to the ATM
group, the user can take action against the objects in the group.
You can classify and organize objects into groups and sub-groups depending on the business requirements using
the Group tab page in the Objects Properties dialog box. For this, click the Object Properties link in the
Threshold dialog box.
Figure 46.
OCC Object Properties Dialog Box Group Tab Page
A default value will be used for Group/Subgroup unless a value is specified. The default value for Group is
Subsystem Name, for example, ATP6100, BASE24. The default value for Subgroup is Object Type, for example, Line,
Link, Process, Station, and System.
The object states of the user-defined Group and Sub-Group can be viewed using ObjectMAP.
NOTE:
The change in the monitoring and recovery status, active or inactive, for a group/subgroup only impacts the
objects and not the main configuration.
The GROUP and THRESHOLD NAME specified on the ObjectMAP tab must match to link the UP EMS message to
the DOWN EMS message. Those values will be displayed as group/subgroup in ObjectMAP.
54
Object Location
OVNM allows the user to define a physical and logical location of an object that is being monitored. This is
significant when OVNM shows an object in abnormal state. The operations staff can quickly identify the physical or
logical location of the object. The facility allows the user to maintain the objects with their physical location and
contact information. For example, the information for an ATM at 23 N. 1st St or Joe’s Trading Station in Building 5,
can quickly assist the support staff to dispatch the nearest help to the user.
The Location tab page in the Object Properties dialog box can be used to specify the location for the threshold
being created. Click the Object Properties link in the Threshold dialog box to access the Object Properties dialog
box. The information will include the name, phone number and complete address. The Comments field is read-only
and can be edited using the Threshold dialog box.
Figure 47.
OCC Object Properties Dialog Box Location Tab Page copy
55
Maintenance
An object is monitored for various policies and normally the object is always configured on the host system.
However, in a transient situation like the daily transaction files, it is not possible to know what the object state will
be from one day to the other. However, the policy to manage the object remains the same. For instance, a file that is
transferred or created on a daily basis for transaction processing will get generated daily, and it might not be
possible to configure the static name of the file object. However, once the file is generated, it is important that the
file does not get full or corrupted, as defined by the policy. The Auto Maintenance facility automatically rediscovers
new objects and applies the policy defined by the user. This can be done on a daily or an hourly basis depending
upon the requirement of the user. The smallest rediscovery time-period is 30 minutes.
Let’s take File Transfer as an example. Your application may receive files on a regular basis, several times a day. You
want to make sure those files are configured in such a way that they never fill up. You can create a
FILESYS/PERCENT FULL threshold using a template that describes where the files will exist. By using
Maintenance, you will be able to define the frequency of auto-maintenance. At that interval, OCC will search for
new files that are within that template and apply the PERCENT FULL threshold. If the files are transient and always
have unique names, you would use the Rebuild option to prevent the system from monitoring files that will never
exist again. By using this feature, you eliminate the need to manually tell OCC to rediscover new objects.
NOTE:
The Auto maintenance feature is not available for the EMS subsystem.
Clicking the Advanced button in the Threshold dialog box displays the Advanced Options dialog box. The
Maintenance tab page of the Advanced Options dialog box can be used to schedule maintenance and reconfigure
the environment.
Figure 48.
OCC Advanced Options Dialog Box
The Auto Maintenance list box provides the following options:
•
None
•
Rebuild
•
Update (add only)
56
You can remove all the objects and rebuild the environment or update the existing environment using the Auto
Maintenance list box. Select the None option in Auto Maintenance to disable maintenance.
You can also schedule maintenance using the Schedule section. Absolute Schedule allows you to specify the start
time and days for maintenance. To schedule maintenance after a specified interval, select the Relative Schedule
option button. Selecting the Relative Schedule option button enables the Interval box, which can be used to
specify the time interval.
NOTE:
NOTE:
Auto maintenance should be used responsibly. The lowest refresh time rate is 30 minutes, but you
should decide if that is too frequent for the threshold that you are creating. Most of the times, a once-a-day
refresh is adequate.
In case you do not want to wait for OCC to automatically update the newly added objects to a threshold, you can
use the Add New Object option in the Threshold menu to add objects to a threshold. The Add User Object
dialog box is displayed where the object can be entered in the Object field. However, no other changes can be
made, since all the other options are disabled.
The auto maintenance feature is not available for the EMS subsystem and OSS.LOGFILE object class.
57
4 Working With Object Configuration Client
Prerequisites
The prerequisites for using OCC are as follows:
1.
OVNM Backend Components Should be Running: In order to get the information from the backend and
saving the information specified using the front-end, the OVNM backend components should be up. Use the
following command to verify the status of the backend components. Switch over to the volume.subvolume,
where OCC is installed before issuing the command.
$ABC.OCCSUB>RUN STATOVNM
2.
Elink Should be Up and Running: Elink is the communication channel between the HPE NonStop host and the
front-end. Elink must be running for using the various features of OCC.
The status of Elink can be verified using the NonStop Nodes Status window, which can be accessed by
selecting the Start  Programs  HPE OVNM  NonStop Server Tools  NonStop Nodes Status menu
option.
Figure 49.
OCC NonStop Nodes Status Window
A Green icon next to the node name in the window indicates that the connection is established with the remote
HPE NonStop Elink. In case the remote HPE NonStop Elink is not up, the icon will be seen in red. The Red icon also
indicates that the backend applications are not running.
The Elink status can also be monitored using the OCC Message/Log pane.
58
Managing the Environment
The first step in defining, modifying or listing threshold configurations for one or more objects is to select the
subsystems that you want to monitor for each HPE NonStop node. You can select the subsystems or their object
types using the Managed Subsystems dialog box.
Follow the steps below to modify the list of subsystems and their object types in the OCC window.
1.
Click the Tools menu.
2.
In the displayed menu, click the Managed Subsystems menu option. This displays the Managed Subsystems
dialog box.
Figure 50.
OCC Managed Subsystems Dialog Box
3.
Select the HPE NonStop node using the Node box.
4.
The Configured subsystems box displays the list of subsystems, which can be managed by OCC. The
subsystems already selected have a tick mark on the left side. To select or uncheck a subsystem, click the
square box next to the subsystem name. A checkmark will appear next to each selected object. Click the check
box again in case you want to deselect an entry.
59
5.
Clicking the plus sign next to the subsystem names displays the list of object types for that subsystem. You
can select the individual object types using the list. To close the list, click the minus sign next to the
subsystem.
Figure 51.
6.
Managed Subsystems Dialog Box
To save the selected options and to continue working in the same screen without exiting, click the Apply
button. This way, you can save the entries for one node and then select a new node to configure. By clicking on
the Apply button, all the changes that you have made will be saved, but they will be reflected only when you
exit. Click the Finished button to save the current node’s settings and to close the Managed Subsystems
dialog box.
60
Creating a Threshold Configuration
Threshold configurations can be created using OCC. Creating a threshold configuration in OCC defines the
acceptable operational values for a specific HPE NonStop object. These are the conditions that OCC checks when
an object state is monitored.
If the threshold conditions defined for an object become true, a threshold violation is said to have occurred. Each
object can have different available threshold configuration conditions and possible settings for each threshold.
OCC provides a set of default policies that are configured automatically while installing OVNM on HPE NonStop
Managed server.
Refer to Appendix D: Default Policies for a list of default policies.
Follow the steps below to create a new threshold configuration.
Step A: Getting Started
The Threshold dialog box is used to create a new threshold configuration. To begin with the process, access the
dialog box by clicking on the New Configuration option in the Threshold menu. The shortcut for the option is
available on the Toolbar as the New Configuration icon. This displays the Threshold dialog box.
Figure 52.
OCC Threshold Dialog Box
Step B: Selecting Nodes
Use the Nodes area in the Threshold dialog box to select the nodes on which the configuration is to be applied. You
can select individual nodes using the check boxes in the Node Name list or use the Select All button to select all
the configured nodes. To unselect all the listed nodes, use the Unselect All button.
The threshold configuration will be applied on all the selected nodes.
61
Step C: Entering the Object Details
Use the various fields in the Object Details section in the Threshold dialog box to enter the object specifications.
1.
Select the subsystem using the Subsystem box. The options available depend on the selections made in the
Managed Subsystems dialog box. Refer to Appendix B: EMS Message Handling and Appendix C: OSS Log
Handling for details on how to manage threshold for the EMS and OSS subsystems, respectively.
2.
Specify the object type using the Object Type box. The options available depend on the subsystem selected.
3.
Type in the object name using the Object box. You can either type in the object name or select from the list of
the last five entries made. Wildcard characters are allowed for most of the subsystems.
4.
Specify the manager name for the objects in the Manager box. The Manager box is not activated for all the
subsystems. The objects belonging to subsystems such as SPOOLER, PATHWAY and SNAX typically have a
manager associated with it. The Object and the Manager fields support wildcard characters.
NOTE:
Use of wildcard characters makes adding objects to the OCC database easy. However, care should be taken to
prevent adding objects that do not need to be monitored. For example, you can add the Percent Full threshold for
all the files in the system, but most of the files on the system do not grow. In addition, there are files that always
fill up before rolling over to the next sequential file.
TIP:
The fields available in the Object Details section are different for the following subsystems.
• ATP6100: For the SU Object type, SU and Line fields are displayed instead of Object and Manager fields. SU should be
a valid SU or a wildcard character. The line name will be the name of the line under which the SU’s are defined.
•
•
BASE24: The Resource Node box is displayed in the Object Details section when you select the BASE24 subsystem.
Specify the BASE24 resource node in this box. This field accepts wildcard characters.
The Manager name in this case has to be the SVNCP process that owns the resource node and must have been defined
during the installation or using ALTROVNM before starting OCC. The SVNCP process name MUST be defined using
ALTROVNM/Option 28 (Add/alter Base24 NCP processes) before you will be allowed to enter BASE24 thresholds.
•
PROCESS: The fields available in the Object Details area will depend on the Object type selected for the Process
subsystem. For example, for the DYNAMIC object type, the Object File Name field is displayed.
•
TCPIP: The Port box is displayed instead of the Object box in the Object Detail section when you select the TCPIP
subsystem. Specify the port number in the Port box. This field allows * wildcard character.
The Process box is displayed instead of the Manager box in the Object Detail section for the TCPIP subsystem.
Specify the process name in this box. This field allows * wildcard character.
62
Step D:
Entering Object Properties
Specify the Object properties using the Object Properties link in the Object Details section.
1.
Click the Object Properties link in the Object Details section. This displays the Object Properties dialog box.
The dialog box has two tab pages, Group and Location. The Group tab page is displayed by default.
Figure 53.
OCC Object Properties Dialog Box Group Tab Page
2.
To classify the objects into groups and sub-groups, type in the group name and the sub-group names in the
Group and Sub-group boxes, respectively in the Group tab page.
3.
Click the Location tab on the Object Properties dialog box to access the Location tab page.
Figure 54.
OCC Object Properties Dialog Box Location Tab Page
63
4.
The Location tab page in the Object Properties dialog box can be used to specify the location for the
threshold being created. The information will include the name, phone number and complete address. Type in
the information in the various boxes and Click the OK button to save the information specified and close the
Object Properties dialog box.
Step E: Entering Maintenance Information
Specify the maintenance information using the Advanced button in the Threshold section.
1.
Click the Advanced button. The Advanced Options dialog box is displayed with the Maintenance tab page.
Figure 55.
OCC Advanced Options Dialog Box Maintenance Tab Page
2.
The maintenance feature is disabled by default. Select the type of auto maintenance using the Auto
Maintenance box in the displayed Maintenance tab page. The other options in the tab page will depend on
the selection made.
3.
Specify the schedule for maintenance using the Schedule section. You can either select the Absolute Schedule
radio button and specify the days on which maintenance is to be scheduled, or the Relative Schedule radio
button and select the interval.
4.
Click the OK button. This will save all the specifications and close the Advanced Options dialog box.
Step F: Entering the Violation Details
Enter the violation details using the various fields in the Threshold section in the Threshold dialog box.
1.
The Object is in violation, if box gives the list of threshold policies supported by a particular object class.
Select the required option from the list. When you select a particular threshold policy, the tip for Threshold
section at the right side of the dialog box shows additional information about that particular threshold. See
Object Reference guide for the list of valid threshold policies for the various subsystems.
2.
The Is box gives the list of operators supported for a given threshold. In cases where no operator is required,
the box is disabled. Select the appropriate operator from the list.
3.
The Value 1 and Value 2 boxes are activated only when operators are required. The entry is in the form of a
specific value. Type in the required values in the boxes.
4.
Enter the comments for the threshold in the Comments box.
Step G: Select the monitoring status for the threshold being created using the Monitoring box.
64
Step H: Entering Monitoring Schedule
OCC allows you to schedule the monitoring process according to your business requirements.
1.
Click the Schedule button in the Threshold dialog box. This displays the Schedule dialog box. This allows you
to organize object monitoring for a specified time period.
Figure 56.
OCC Schedule Dialog Box
2.
By default, monitoring will poll the system for violations of a threshold every 5 minutes. Change the polling
interval using the Poll Interval box in the Schedule dialog box.
3.
Specify the daily monitoring start time and stop time using the Start Time and the Stop Time boxes,
respectively.
4.
To schedule monitoring 7 days a week, select the All check box. You can select the specific days of the week
for monitoring using the various check boxes for different days of the week.
5.
If you select the Use Extended Host Schedule check box, you will be presented with a new screen for defining
the schedule. To define a schedule, refer to section Scheduling.
6.
Click the OK button to save the information specified and return to the Threshold dialog box.
65
Step I: Entering Action Details
The Actions button helps you to access the Actions dialog box using, which you can configure alert, recovery,
e-mail and page options. You can also provide specifications for Tivoli and HPE OM. To access the Actions dialog
box, click the Actions button in the Threshold dialog box.
Figure 57.
1.
OCC Actions Dialog Box with Alert Tab Page
Entering Alert Definition Data:
a. The Exception section of the Actions dialog box allows you to tailor the Exception and Escalation event
messages. Specify the internal severity levels using the Severity box. This severity is used in the text of
the alert message and determines the severity value in ObjectMap and ObjectStats. Changing this value
may or may not change the corresponding value in the eEvents panel, depending on the value set in
Tools/Options/Keep Severity in Sync.
b. Specify the frequency of the alert messages using the Repeat Every box.
c. Select the Escalate check box and specify the time when the first alert will be generated after the initial
violation in the Log Escalation Event After box.
d. Specify the sound alarm to be played in case of a violation using the ObjectMAP Alarm box. The sound
alarm is only played when objects go into violation. No sound is played when it returns to normal.
NOTE:
The Alert tab page will be disabled if you have selected the EMS subsystem in the Threshold dialog box.
66
2.
Entering Recovery Data
a. To specify the recovery details, click the Action tab on the Actions dialog box. This displays the Action
tab page.
Figure 58.
OCC Actions Dialog Box with Action Tab Page
b. Select the recovery type to be applied using the first Command box.
c. Other fields enabled in the tab page will depend on the recovery selected. If you select the User defined
command option in the Command box, the next Command box is activated. You can define the action to
be performed in case of a violation using this box. You can use the Parameter list link to use substitution
parameters. For more details on configuring thresholds with a user-defined Automatic Recovery
Command, refer to Appendix N: Log Success/Failure of User Defined Command for Recovery in User
Guide.
d. Select the 24x7 option button in the Schedule section to activate recovery 24 hours a day, seven days a
week. You can define a customized recovery schedule using the Schedule button. To activate the
Schedule button, select the User Defined option button.
Figure 59.
OCC Recovery Schedule Dialog Box
a. By default, OCC will start the recovery process for a threshold every 5 minutes. You can change the delay
interval using the Delay Interval box.
b. Specify the start time and stop time using the Start Time and Stop Time boxes, respectively.
c. To schedule monitoring 7 days a week, select the All check box. You can select the specific days of the
week for monitoring using the various check boxes for different days of the week.
d. You can use the Next schedule day check box to schedule recovery on the next scheduled day specified
in the Days section.
67
e. Click the OK button to close the Schedule dialog box and to return to the Actions dialog box.
f.
3.
Activate or deactivate recovery using the Recovery box in the Options section in the Action tab page.
Entering E-Mail Alert Information
a. To specify the e-mail alert data, click the Mail tab on the Actions dialog box. The e-mail feature is not
activated by default. Click the Mail on Violation check box to enable the e-mail feature.
Figure 60.
OCC Actions Dialog Box with Mail Tab Page
b. Enter the e-mail addresses, profile names or the distribution list to whom the alerts should be sent in the
To box.
c. Specify the subject of the message to be sent in case of a violation in the Subject box.
d. Enter the message to be sent in case of a threshold violation in the Violation Message box. You can also
click the Parameters list link to use substitution parameters.
e. The Mail on escalation only check box can be selected to allow OCC to send e-mail alerts only when an
escalation event is generated.
f.
To enter the specifications for the mail message to be sent when the object in violation returns to its
normal state, select the Mail on Normal check box.
g. Selecting the Mail on Normal check box activates the Subject and the Normal Message boxes. Specify
the subject in the Subject box and the message in the Normal Message box. As in the case of violation
message, you can use the Parameters list link.
68
4.
eEvents
a. Click the eEvents tab in the Actions dialog box.
Figure 61.
OCC Actions Dialog Box eEvents Tab Page
b. Select the HPE OM/OVO, Tivoli or SNMP radio button to forward the events to the corresponding
Management consoles. This activates the various fields in the tab page.
c. Select the eEvents status using the eEvents Status box.
d. If the event status is specified as ACTIVE or INACTIVE, select the internal severity levels using the
Violation Severity box. If you select ORIGINAL, the value specified in the Alert tab will be used. If you
select any other value, then the value in the Alert tab may or may not be automatically updated, based on
the value specified in Tools/Options/Keep Severity in Sync. The severity specified here is used in Console
and the Enterprise Management System. It does not impact ObjectMap, ObjectStats or the text in the
violation message. Specify the Object Name, Manager Name, Customer Name, Location, Service ID,
Message Group/Layer, and Event Text Replacement information in the respective fields. If you select
DROP THIS EVENT in the eEvent status field, then none of the other fields are necessary since the event
will not be passed on.
e. If the event status is specified as CUSTOM, specify the message layout in the Message box. Select the
Append mode check box to append the slots to the standard message format. In this case, the message
class will be decided by OCC using the cdf file conditions.
f.
You can also use the Parameters list link for the Event Text field. To load the message format from a
saved template file use the Insert from file link. To use event token numbers use the Token list link.
69
Step J: Configuring EMS Actions
1.
ObjectMAP
a. Click the ObjectMAP tab to configure the objects to be displayed in the ObjectMAP interface.
NOTE:
The ObjectMAP tab page is displayed only if you select the EMS subsystem.
Figure 62.
OCC Actions Dialog Box ObjectMAP Tab Page
b. Select the Add/Update radio button to add or update an object. To remove an object, select the Delete
radio button. In case you do not want to map the event, select the Do not map event option.
c. Select the appropriate radio buttons in order to map the event using default attributes, rule number or
the token numbers using the Map event using default attributes, Map event using rule number and
Map event using radio buttons, respectively. If you select the Map event using option, the Subject token
number and Manager token number fields are activated. You can either specify the appropriate token
numbers or select the token numbers using the Lookup token numbers link.
d. In order to remove the object automatically after a specified time, select the Auto-remove object check
box and specify the time using the After and At time fields.
e. Specify the group name using the Group Name box.
f.
Use the Threshold name box to enter the name for the threshold.
70
2.
eBurst
a. Click the eBurst tab to configure burst criteria to be used to suppress the burst of EMS messages. The
tab page is displayed only when you select the EMS subsystem.
Figure 63.
OCC Actions Dialog Box eBurst Tab Page
b. Selecting None radio button specifies that every EMS message will be processed even if no burst criteria
is defined and a burst of EMS messages is consumed. Selecting the Process Until Burst or Ignore Until
Burst radio button enables the Burst and Reset area. Process Until Burst radio button sets the burst
conditions for the EMS messages. The EMS messages are processed until the burst conditions are met.
The Ignore Until Burst option allows ignoring the processing of EMS messages until the burst conditions
are met.
c. You can reset the burst period using the Reset area. Enter the maximum burst time using the After MAX
burst period of field. The default value is set to 01 Minute.
d. To specify the burst condition, enter the number of events in the Burst field and specify the time duration
in minutes using the Within field. Enter the subject for the events using the Event Subject field.
By entering the burst criteria, you can limit the:
−
Number of messages that are sent to the Enterprise Solution
−
Number of emails that are generated
−
Number of recoveries that are performed
e. Select Generate start/end EMS burst notification messages check box to start generating the EMS
burst notification messages.
Step K: Saving the Threshold Data
After entering the necessary data, including any Schedule or Action changes, click either the Apply or the OK
button to record the data in the database. Use the Apply button to save the entered threshold and to continue with
the creation of another threshold. Use the OK button to save the entered threshold and exit the dialog box. In
either case, if the threshold’s monitoring was set to Active, OCC will start monitoring the new threshold as soon as
the data is saved.
NOTE:
The Object Configuration Client returns the number of objects added. If no objects were added, it is considered
an error and a message is displayed.
71
Listing Configurations and Objects
After having created new thresholds, you can list the thresholds and the corresponding Objects in the Threshold
and the Objects pane, respectively.
Listing Configurations
1.
Right-click on an object type in the Object Class pane.
2.
Select the List Configurations option in the displayed menu.
Figure 64.
OCC List Configurations Option
An easy way to list configurations is by double-clicking on the Object Type.
NOTE:
When you are viewing thresholds in the Threshold pane, you are looking at a copy from memory unless you click
the List Configurations option to refresh memory.
72
Listing Objects
1.
List the thresholds for the required subsystem in the Threshold pane.
2.
Select the threshold whose objects you want to list.
3.
Click the List Objects option in the Threshold menu. This is also available on the Toolbar as the List Objects
icon. You can also right-Click the particular configuration in the Threshold pane and select the List Objects
option in the displayed menu. The listing for all the objects in the selected threshold is shown in the Objects
pane.
Figure 65.
OCC Object Listing Result
Once the objects have been listed, you can refresh the displayed data by double clicking on the corresponding
threshold configuration in the Threshold pane. The data is updated from the backend. The data in the front-end
memory is shown in case you click the corresponding threshold configuration.
73
Color Coding
The color of the listed threshold and objects, in the Threshold pane and Objects pane, respectively, can be Green,
Red or Blue, depending on the status of monitoring and recovery.
Table 7.
Color Coding
S. No.
Color
Monitoring Status
Recovery Status
1.
Green
Active
Active
2.
Green
Active
Not Defined
3.
Red
Inactive
Active
4.
Red
Inactive
Not Defined
5.
Red
Inactive
Inactive
6.
Blue
Active
Inactive
Figure 66.
OCC Color Coding
74
Maintaining Configurations & Objects
Once a new threshold has been configured, you can modify or delete the thresholds and the objects as per your
requirement. The various options available for maintaining threshold configurations and objects are:
•
Modify Config
•
Delete Config
•
Modify Object
•
Delete Object
You can access these options using the Threshold menu, the shortcut icons available on the Toolbar and the
right-click menu in the Threshold & Objects panes.
Modifying Configurations
1.
List the thresholds in the Threshold pane.
2.
Select the threshold to be modified.
3.
Click the Modify Config option in the Threshold menu. This option is also available as the Modify
Configuration icon on the Toolbar. The Modify Configuration / Object dialog box is displayed.
Figure 67.
4.
OCC Modify Configuration / Object Dialog Box
Make the necessary modifications in the Modify Configuration / Object dialog box and Click the OK button to
save the modification and close the dialog box.
75
Modifying Objects
1.
List the objects in the Objects pane.
2.
Select the object to be modified.
3.
Click the Modify Object option in the Threshold menu. This option is also available as the Modify Object icon
on the Toolbar. The Modify Configuration / Object dialog box is displayed.
Figure 68.
4.
OCC Modify Configuration / Object Dialog Box
Make the necessary modifications in the Modify Configuration / Object dialog box and Click the OK button to
save the modification and close the dialog box.
NOTE:
When an object is modified, the status changes to Unknown. List the objects again to see the current status.
76
Deleting Configurations
1.
List the thresholds in the Threshold pane.
2.
Select the threshold to be deleted.
3.
Click the Delete Config option in the Threshold menu. This action can also be performed using the Delete
Configuration icon on the Toolbar.
4.
An OVNM Object Configuration Client confirmation box is displayed. Click the Yes button to delete the
selected threshold.
Figure 69.
OCC Confirmation Box
Deleting Objects
1.
List the objects in the Objects pane.
2.
Select the object to be deleted.
3.
Click the Delete Object option in the Threshold menu. This action can also be performed using the Delete
Object icon on the Toolbar.
4.
An OCC confirmation box is displayed. Click the Yes button to delete the selected object.
Figure 70.
OCC Confirmation Box
77
Appendix A: Subsystems Managed
OCC allows you to monitor most of the major HPE NonStop subsystems. A list of all the predefined subsystems
managed by OCC is as follows.
NOTE:
The BASE24, and MQ-SERIES subsystems will not be enabled in OCC by default. These subsystems will be
activated only when the corresponding plug-ins have been installed.
1.
ATP6100
The ATP6100 subsystem consists of the ATP6100 line-handler process and a protocol module. The ATP6100
line-handler process is a HPE NonStop™ process pair running in a HPE NonStop™ host. The process acts as a
file-system interface between an application and a protocol module that resides and runs in the Communication
Line Interface Process (CLIP) as a task. In the wide area network (WAN) subsystem that uses the SWAN
concentrator, the ATP6100 line-handler process thus allows communication over a variety of asynchronous
communication devices especially terminals and printers. Application data is passed to one of several protocol
modules by ATP6100. The protocol module gives the application extensive control over the line, and each
protocol module can control either a single line or multiple lines.
2.
BASE24
BASE24 is a major ATM application available from ACI. This software is used by most of the world’s major
banking institutions for their credit card transactions. The counters/modifiers defined under this subsystem
help monitor and manage various objects like LINE, LINK, PROCESS, STATION, SYSTEM and TDF-60. The
PNA24 module is used for discovery and recovery of the BASE24 objects and is included in the base product.
This greatly increases the Out-of-the-Box capabilities of OCC, especially regarding a major application such as
BASE24. The BASE24 subsystem will only be available if you have installed the BASE24 plug-in.
3.
CLIM-IP
The CLuster I/O Protocol (CLIM-IP) provides the physical interface to the network or storage devices. The CLIM
includes a ServerNet PCIe card with multiple ports that interface to the ServerNet fabric of the NonStop host
system.
4.
CP6100
The CP6100 subsystem consists of the CP6100 input-output process (IOP) and a protocol module. The CP6100
IOP, also known as the CP6100 Communication Access Process (CAP), is a NonStop™ process pair running in a
NonStop™ host. The process acts as a file-transfer mechanism to move data between an application and a
protocol module that resides and runs in the Communication Line Interface Process (CLIP) as a task. The
protocol module is a microcode file or a download module (DLM) that contains OSI Layer-1 and Layer-2
processing tasks. The CP6100 CAP thus provides the application with a data-link level interface to
asynchronous, byte-synchronous, or bit-synchronous protocol modules in a 6100 Communication Subsystem
(CSS), which uses the ServerNet Wide Area Network (SWAN) concentrator. Application data is passed to one of
several protocol modules by CP6100. The protocol module gives the application extensive control over the line,
and each protocol module can control either a single line or multiple lines.
5.
CPU
This subsystem manages and controls one of the major components of the system, the CPU. The
counters/modifiers predefined for this subsystem greatly facilitate the monitoring and recovery of all the CPUs’
for the HPE NonStop node.
6.
DISK
Another major component of a system is the Disk subsystem. The predefined disk counters/modifiers help in
managing, monitoring and recovering this complex and major subsystem on the HPE NonStop platform.
7.
EMS
EMS is the subsystem that handles EVENTS on a HPE NonStop node. The counters/modifiers defined for this
subsystem allow the customer to easily monitor and react to any kind of event generated on a HPE NonStop
78
system. The EMS management feature allows the user to trigger actions based on EMS events. This feature
allows the customer to define HPE NonStop subsystem generated events as well as user-application generated
events for escalation and automation. Additional slot values as they are known, can also be added for the HPE
Operations environment. Any EMS or Non-EMS event can be automated via Gateway processes or by simple
TACL macro commands.
8.
EXPAND
The EXPAND communication protocol is an NSK proprietary protocol that is used by different HPE NonStop
nodes to communicate with each other. Customers who have multiple HPE NonStop systems use and depend
upon EXPAND for their applications to run smoothly. OCC has predefined counters/modifiers that facilitate the
monitoring and recovery of the lines and paths defined under the EXPAND subsystem.
9.
FILESYS
The FILESYS subsystem deals with the monitoring and management of files on a HPE NonStop system. Files
can be monitored in various ways and predefined actions can be taken if and when the criterion is met. The
counters/modifiers that have been predefined for this system greatly facilitate the management of files.
You can use the FILESYS objects to manage SQL/M*.
10. ICE
Internet Communication for the Enterprise (ICE) is a major communication application available from Insession
Technologies. This software is used by hundreds of organizations worldwide to help run their mission critical
HPE NonStop applications. In this release, OCC helps to monitor and manage APPL, PU and TNSERVER
objects. Based on customer demand additional objects can be incorporated.
11. ICE-DLSw
ICE - DLSw connects HPE NonStop servers to backbone networks. The solution performs encapsulation
functions previously executed on data center routers. With ICE - DLSw, any IP router can be inter-connected,
and any HPE NonStop LAN controller can be used.
12. MQ-SERIES
MQSeries messaging products enable application integration by helping business applications to exchange
information across different platforms by sending and receiving data as messages. They take care of network
interfaces, assure ‘once only’ delivery of messages, deal with communications protocols, dynamically distribute
workload across available resources, handle recovery after system problems, and help make programs portable.
So programmers can use their skills to handle key business requirements, instead of wrestling with underlying
network complexities. The MQ-SERIES subsystem will only be available if you have installed the MQ-SERIES
plug-in.
13. NETBATCH
NetBatch subsystem is used for scheduling, and control systems for batch processing. It takes advantage of the
HPE multiprocessor architecture and allows running of batch operations in a single or in many processors
concurrently.
14. OSS
The Open System Services (OSS) environment provides a user and programming interface similar to that of the
UNIX operating system. The OSS environment combines the benefits of the UNIX operating system with the
features of the HPE NonStop operating system.
You can use OSS objects to monitor Weblogic and TUXEDO processes. The log files created by Weblogic and
TUXEDO can be monitored using the OSS LOGFILE objects.
15. PATHWAY
Pathway is an application framework shell provided on the HPE NonStop platform. Developers using Pathway
can utilize the various facilities offered by this framework. Predefined counters/modifiers manage, monitor and
recover the various objects defined under Pathway like Servers, TCP and Terminals.
16. PLUGPLAY
Plugplay subsystem monitors Primary CPU Switched, Backup CPU Switched, Device Audited Switched, Primary
Status Switched, Primary Access Switched, Primary Path Switched, Primary Path Used Switched, Backup Status
79
Switched, Backup Access Switched, Backup Path Switched and Backup Path Used Switched. Whenever any of
the above-mentioned attributes change their state, OCC treats it as a violation state.
17. PROCESS
The Process subsystem has predefined counters/modifiers to manage and monitor various processes running
on the HPE NonStop platform.
18. RDF
RDF monitors the changes made to a production database on a local (primary) system and maintains a copy of
that database on one or more remote (backup) systems. It applies changes to the backup database as soon as
they are detected on the primary system, RDF keeps the backup database continuously up to date with
changes made by business applications on the primary system. You are therefore able to switch your business
operations from the primary system to the backup system with minimal interruption and loss of data in the
event of planned or unplanned outages of the primary system.
The thresholds in this subsystem allow you to monitor the activities of RDF to make sure it is operating as you
expect to reduce the chance of any data loss or extended RDF recoveries.
19. SNAX-XF
This is a part of the SNAX family of products available on the HPE NonStop platform. SNAX-XF primary lines
control and serve attached SNA peripheral nodes (SNA type 2.0 nodes). This subsystem in OCC helps in
managing the LUs’ and PUs’ defined in this subsystem.
20. SPOOLER
The spooler subsystem is a set of utilities that form an interface between you & your application programs and
the print devices on a system. The spooler receives output from an application and stores data on the disk.
When the print device is available the output is sent to that device for printing. Predefined counters/modifiers
help in managing this important subsystem.
21. SPOOLERP
This is the new version of Spooler that is supplied for the HPE NonStop S-Series. This subsystem allows the
user to monitor and manage Spooler objects like the COLLECTOR, DEVICES and PRINT PROCESSES.
22. TAPE
This subsystem supervises all tape operations within the HPE NonStop platform. Counters such as Mounts are
predefined and are simple to set up.
23. TCPIP
The S-Series HPE NonStop platform uses TCPIP as a major protocol to communicate. TCPIP stacks or
processes and ports need to be monitored closely and actively. This subsystem achieves that through
predefined counters and modifiers.
24. TMF
Transaction Monitoring Facility or TMF is a major subsystem on the HPE NonStop platform. It provides services
for transactions like Rollback and Roll forward (in case of system failures), Audit trails and Audit dumps (for
data integrity). Various applications use these services for the Transaction protection that is built into this
subsystem.
25. X25
This is a commonly used communication protocol and is available on the HPE NonStop platform. The
counters/modifiers predefined in this subsystem help manage objects using this protocol.
80
Appendix B: EMS Message Handling
This appendix contains an example of setting up an EMS event for forwarding to the HPE Operations environment.
In this example, we will use the event logged by the Expand subsystem when a line is started. The highlight of the
example is the ability to customize the event text and the ability to assign Service-ID for the event that will be
propagated to the Service View in the HPE OM panel.
1.
Select the EMS subsystem in the Object Class pane and Click the New Configuration option in the Threshold
menu.
Figure 71.
2.
OCC Threshold – New Configuration Menu Option
Clicking the New Configuration option displays the Threshold dialog box. This dialog box is used to specify
the Object and Threshold details. Use the Help button in the Threshold dialog box to get help on how to
create a threshold configuration for a NonStop EMS event.
Figure 72.
OCC Threshold – EMS Help
81
3.
Select the nodes on which the configuration is to be applied using the Nodes area.
Figure 73.
4.
Select the Subsystem and Object Type as EMS and EVENT in the Threshold dialog box.
Figure 74.
5.
OCC Threshold – Nodes Area
OCC Threshold Dialog Box with EMS Subsystem and EVENT Object Type Selected
Specify the owner and the subsystem of the event in the owner.subsystem format in the Owner.Subsystem
box.
82
You can use the
Figure 75.
button next to the box to type the text in upper or lower case.
OCC Threshold Dialog Box with Owner.Subsystem Information
Examples of valid Owner.Subsystem are:
TANDEM.EMS
TANDEM.PATHWAY
MYORG.1
For HPE NonStop subsystems, the subsystem owner is “TANDEM”.
NOTE:
OCC version 5.3.x onwards will not allow *.* for EMS in Owner.subsystem name. The following message is
displayed.
6.
The Event Number box allows you to define a single threshold policy that would apply to all the events for a
given owner.subsystem. By entering an asterisk, the policy will apply to all events that are generated by the
owner.subsystem. If a second EMS threshold is created for the same owner.subsystem, then the event will take
the unique actions specified. For example, if the specific policy has a schedule that is a subset of the * policy,
and the event occurs outside its specific schedule, it will be ignored. If you want the actions specified for the *
policy to be taken for the event number outside its normal schedule, a third policy covering the rest of the day
has to be created.
83
The Event Number field can accept any string of 32 characters. The value can be:






Figure 76.
7.
Integer
Range, for example a:b, where a and b are numbers separated by a colon
Multiple integers separated by commas, for example 1,2,3,4
Multiple ranges separated by colons, for example 1:10, -5:-2 and 100:200
Multiple integers and range(s) together, for example 1,2,3,100:150, -100:99
Negative event number(s) and negative event range(s)
OCC Threshold Dialog Box with Event Number Information
Select the threshold violation criteria using The object is in violation, if box. Other fields in the Threshold area
get activated depending on the selected violation criteria.
Figure 77.
OCC Threshold Dialog Box with Threshold Information
84
The EMS Object provides several Threshold options. If you are not familiar with EMS Tokens then it is
recommended that you select either EXECUTE-DEFINED-ACTION or EVENT TEXT.
•
EXECUTE-DEFINED ACTIONS: This threshold type is used when you do not need any additional qualification
on the EMS event – when Owner.Subsystem and event number provide enough information to identify the
EMS event message you want to process. After selecting the option, click the Action button to define the
action to be taken.
•
EMPHASIS-TOKEN-TRUE: This threshold is used when SSID and Event are all that are needed to identify the
correct EMS message and you want only those events that contain an Emphasis Token that has a true value.
SSID can support * in subsystem portion. For example: TANDEM.*.
•
EVENT TEXT MESSAGE: This threshold can be used for matching event text associated with the event text
token or the text area of the EMS Message. The operators available with threshold are: “Equal to <value 1>”,
“Contains <value 1>” and “Equals <value 1> at offset <value 2>”. The easiest method to test for text within an
EMS message is using “Contains <value 1>”. The text can occur anywhere in the message and it is NOT case
sensitive. You can use the “*” and “?” wildcard characters with the “Contains <value 1>” operator.
CAUTION:
It is recommended that you do use wildcard characters with the “Equal to <value 1>” and “Equals <valiue 1> at
offset <value 2>” operators. This might lead to unexpected results.
•
EVENT PASS VALUE: This threshold type allows the user to check if the event contains the specified pass
value. The pass value is associated with the filter that passed the event. Refer to the NonStop Server EMS
Manual for details.
NOTE:
For TANDEM.EMS.512 thresholds, you must use a pass value less than or equal to 1000.
•
EVENT SUBJECT AND MANAGER: This threshold type allows the user to check if the event contains the
specified subject and manager associated with the subject and the manager token, respectively. Refer to the
NonStop Server EMS Manual for details. The event must match both subject and manager to be considered a
match.
•
EVENT SUBJECT: This threshold type allows the user to check if the event contains the specified subject
associated with the subject token. Refer to the NonStop Server EMS Manual for details.
8.
Set the monitoring for the objects as active using the Monitoring box. Monitoring is inactive by default. Use
the Schedule button to specify the monitoring schedule.
Figure 78.
OCC Threshold Dialog Box with Monitoring Activated
85
9.
Click the Actions button to open the Actions dialog Box. The Alert tab is displayed by default, but there are
no fields on this page that are useful for EMS thresholds.
Figure 79.
OCC Actions Dialog Box
NOTE:
Service IDs are associated with NonStop Server Service Components in HPE OM Services View.
10. Configure recovery, e-mail and events facility using the Action, Mail and eEvents tab pages, respectively.
11. Specify the map event and event burst information using ObjectMAP and eBurst tab pages respectively.
12. After entering all the relevant information, click the OK button in the Actions dialog box.
13. The Threshold dialog box is displayed. To save the information and to close the dialog box, click the OK
button.
For details, refer to Configuring HPE OM Services section in the Event Management for Windows guide.
86
EMS Processing Sequence
EMS thresholds allow wildcards in various locations of the SSID and Event number that specify which events should
be processed. You can use an asterisk in the Subsystem number and the event number fields. For example,
TANDEM.* with event *. This definition would then apply to any EMS message generated by the TANDEM SSID
Owner. When OVNM is processing EMS events and matching them against the EMS thresholds, it will always look
for a specific match before it looks for a generic match. Since it may not always be obvious which EMS threshold(s)
will be used for a given event, the following will try to describe the process that is used.
There are 4 types of EMS thresholds that can be defined.
Table 8.
EMS Threshold List
A
Owner.Subsystem Number
Specific Event Number
B
Owner.Subsytem Number
Event *
C
Owner.*
Specific Event Number
D
Owner.*
Event *
87
The thresholds will be searched in the below given sequence.
1.
OVNM will attempt to match a record with the same SSID and Event number (TANDEM.PATHWAY, event 203
for example).
2.
If no match is found or a match is found but the qualification fails, then it will continue the search to the next
level. This will match on the SSID only (TANDEM.PATHWAY) and will match any event for that SSID.
3.
If again there is no match, then it will check to see if a threshold exists for the Owner and the specific event
(TANDEM.*, Event 203 for example).
4.
If there is still no match found, then it will look for a match on Owner and any event (TANDEM.*, any event).
Normally, once a match is made, it will not check any other match level. The exception to this rule is for the exact
match (A). As stated above, when it searches for an exact match (SSID and Event) and finds it, it will continue
checking the other levels, if the qualification for the event fails. So if you had specified Event Text Contains and the
text was not found, then it will go on to the next match levels B, C and D. This is not performed on the other levels
though. So if no match is made at level A but there is at level B, but the qualification fails, the event is not
processed. If the qualification is successful, then it is processed.
In addition, once a match is made at a given level, all thresholds at that same level will be processed. So if you have
different qualifications specified, all those thresholds will be evaluated and all thresholds will be processed in which
the event passes the qualification test.
For example, consider these EMS thresholds – all using “executed-defined-actions”.
A
APPL.PAYROLL
123
Execute defined actions
B
APPL.ATM
123
Text contains cash
C
APPL.PAYROLL
124
Text contains check
D
APPL.PAYROLL
124
Text contains cashed
E
APPL.PAYROLL
124
Text contains check cashed
F
APPL.PAYROLL
*
Execute defined actions
G
APPL.ATM
*
Text contains cash
H
APPL.*
123
Execute defined actions
I
APPL.*
*
Execute defined actions
•
APPL.PAYROLL.123 will be processed by level A.
•
APPL.PAYROLL.100 will be processed by level F.
•
APPL.ATM.123 will be processed by level B if it contains “cash”. If not, it will be processed by level G. It is an
exact match for SSID and Event, but if it fails the qualification test, then OVNM will continue looking for
thresholds with wildcards.
•
“APPL.ATM.100 just-this-text” will be bypassed. There is no exact match for it, so the first threshold that is a
match is level G, but since the event does not contain ‘cash’, it fails the qualification test. Since this is not the
‘exact match’ level, no lower levels are checked.
•
“APPL.PAYROLL.124 Check Cashed” will be processed by level C, D and E since it matches the criteria for all of
those thresholds.
The above describes the process used for both Actions and deciding which message should be sent to the
Enterprise Management Solution. The only differences between the action processing and the Enterprise
Management processing is that only one message will be sent to the Enterprise Management system regardless of
the number of ‘matches’ and it will be based on the LAST threshold that was added. The last one added will be the
first one to be processed.
88
Appendix C: OSS Log Handling
This appendix contains an example of setting up OSS event for monitoring OSS logfile and forwarding these events
to the HPE Operations environment.
1.
Select the OSS subsystem in Object Class pane and Click the New Configuration option in the Threshold
menu.
Figure 80.
OCC Threshold – New Configuration Menu Option
2.
Clicking the New Configuration option displays the Threshold dialog box. This dialog box is used to specify
the Object and Threshold details. Select the nodes on which the configuration is to be applied using the Nodes
area.
3.
Select the Subsystem and Object Type as OSS and LOGFILE.
Figure 81.
OCC Threshold Dialog Box with OSS Subsystem and LOGFILE Object Type Selected
89
4.
Specify the name and location of the OSS log file in the Object File Name box.
Figure 82.
OCC Threshold Dialog Box with Object File Name Information
The Object File Name field can accept any string of 64 characters and is case-sensitive. Specify the complete path
for the logfile in the field. For example: /home/tandem/admin/logfile.
In case you are specifying a file in guardian format in an expand node, use the following:
/E/<node name>/G/<volume>/<subvolume/file name
5.
Select the violation criterion in The object is in violation box. You can also add comments, if any, in the
Comments box.
Figure 83.
OCC Threshold Dialog Box with Threshold Information
90
6.
Set the monitoring for the objects as active using the Monitoring box. Monitoring is inactive by default. Use
the Schedule button to specify the monitoring schedule.
Figure 84.
7.
OCC Threshold Dialog Box with Monitoring Information
Click the Actions button to access the Actions dialog box. The Log Event tab page can be used to configure
the Collector where the OSS events will be logged. The other information that needs to be specified includes
Owner, Subsystem Num and Error Number.
Figure 85.
OCC Actions Dialog Box Log Event Tab Page
8.
Configure severity, recovery, e-mail and enterprise management console facility using the Alert, Action, Mail
and eEvents tab pages, respectively.
9.
After entering all the relevant information, click the OK button in the Actions dialog box.
10. The Threshold dialog box is displayed. To save the information and to close the dialog box, click the OK
button.
91
Appendix D: Default Policies
The following table contains the list of pre-configured policies. These policies are configured automatically during
the OVNM installation on the HPE NonStop Managed Host if you select the Add Default Policies check box in the
Policies tab page of the Host Installation Client New OVNM Configuration dialog box.
Figure 86.
Host Installation Client’s New OVNM Configuration Dialog Box
For details, refer to Installing OVNM on HPE NonStop Server section in the installation guide.
Table 9.
Default Policies
Subsystem
Object Type
Threshold
Poll Interval
Repeat Every
Severity
CPU
CPU
CPU IS DOWN
1 min
0 min
Critical
CPU
CPU
CPU QUEUE LENGTH > 5
1 min
0 min
Critical
CPU
CPU
LOW PCBS IN USE > 220
1 min
0 min
Critical
DISK
DISK
DISK IS DOWN
5 min
0 min
Critical
DISK
DISK
PERCENT FULL > 80
5 min
0 min
Critical
EMS
EVENT
EXECUTE-DEFINED-ACTION
TANDEM.OVNM.*
-
-
Original
EMS
EVENT
EXECUTE-DEFINED-ACTION
TANDEM.OVMON.*
-
-
Original
EMS
EVENT
EXECUTE-DEFINED-ACTION
TANDEM.OVMON.999
-
-
Warning
EMS
EVENT
EXECUTE-DEFINED-ACTION
TANDEM.OVNPM.*
-
-
Original
EMS
EVENT
EXECUTE-DEFINED-ACTION
TANDEM.OVNPM.999
-
-
Warning
92
Subsystem
Object Type
Threshold
Poll Interval
Repeat Every
Severity
EXPAND
LINE
NOT STARTED
5 min
0 min
Critical
EXPAND
PATH
NOT STARTED
5 min
0 min
Critical
PATHWAY
PATHMON
PATHMON STOPPED
30 min
0 min
Critical
PATHWAY
TCP
TCP IS NOT STARTED
30 min
0 min
Critical
PLUGPLAY
DISK
DISK PLUGPLAY
14 min
0 min
Major
PLUGPLAY
EXPAND
EXPAND PLUGPLAY
14 min
0 min
Major
PLUGPLAY
SNAX-XF
SNAXXF PLUGPLAY
14 min
0 min
Major
PLUGPLAY
TAPE
TAPE PLUGPLAY
14 min
0 min
Major
PLUGPLAY
X25
X25 PLUGPLAY
14 min
0 min
Major
PROCESS
LOOPING
ANY PROCESS IS LOOPING (DYNAMIC)
2 min
0 min
Critical
PROCESS
PROCESS
PROCESS IS DOWN, $ZPMON
2 min
0 min
Minor
PROCESS
PROCESS
PROCESS IS DOWN, $ZPNS
2 min
0 min
Minor
PROCESS
PROCESS
PROCESS IS DOWN, $ZTA*
2 min
0 min
Minor
SNAX-XF
SUBSYS
NOT STARTED
3 min
0 min
Minor
SPOOLER
COLLECTOR
COLLECTOR FILE PERCENT_FULL > 80
15 min
0 min
Warning
SPOOLER
DEVICE
DEVICE ERROR
15 min
0 min
Warning
SPOOLER
DEVICE
DEVICE PRINT PROCESS ERROR
15 min
0 min
Warning
SPOOLER
PRINTPROC
PRINT PROCESS ERROR
15 min
0 min
Warning
TAPE
TAPE
MOUNTS OUTSTANDING
10 min
0 min
Critical
TCPIP
PROCESS
PROCESS IS DOWN
1 min
0 min
Critical
TCPIP
PROCESS
PORT IS IN FIN-WAIT STATE
1 min
0 min
Critical
TMF
AUDITDUMP
AUDIT DUMP IS DISABLED
1 min
0 min
Critical
TMF
AUDITDUMP
AUDIT DUMP IS INACTIVE
1 min
0 min
Critical
TMF
AUDITTRAIL
CANNOT ROLLOVER
1 min
0 min
Critical
TMF
AUDITTRAIL
OVER FLOW IN USE
1 min
0 min
Critical
TMF
TMF
HUNG TRANSACTIONS
1 min
0 min
Critical
TMF
TMF
TMF IS STOPPED
1 min
0 min
Critical
TMF
TRANSACTIO
NS
TRANSACTION IS HUNG
1 min
0 min
Critical
X25
LINE
NOT STARTED
2 min
0 min
Minor
FILESYS
FILE
AUDITED
30 min
60 min
Minor
93
Subsystem
Object Type
Threshold
Poll Interval
Repeat Every
Severity
FILESYS
FILE
LICENSED
30 min
60 min
Minor
FILESYS
FILE
PROGID
30 min
60 min
Minor
FILESYS
FILE
FILE EXISTS
60 min
0 min
Critical
94
Appendix E: Substitution Parameters
Table 10.
Substitution Parameters
Parameter Name
Description
%s%
Subject Name or Object Name which has violated threshold
%m%
Manager Name for the Subject that violated threshold
%e%
Event Number of the event that reports violation
%n%
Node Name to which the subject belongs
%ssid%
Subsystem Name to which the subject belongs
%ssn%
Subsystem Number to which the subject belongs
%sso%
Subsystem Owner to which the subject belongs
%t<Offset:length>%
Event Text Message (default = <0:255>)
%t(index)#TokenNumber%
Token Number of the event that reports violation (default index =0)
%lt^mmddyy%
Log Event Time showing the date in mmddyy format
%lt^mmddyyyy%
Log Event Time showing the date in mmddyyyy format
%lt^ddmmmyyyy%
Log Event Time showing the date in ddmmmyyyy format
%lt^mm%
Log Event Time showing only the month
%lt^dd%
Log Event Time showing only the day
%lt^yy%
Log Event Time showing only the short year
%lt^yyyy%
Log Event Time showing only the long year
%gt^mmddyy%
Event Generation Time showing the date in mmddyy format
%gt^mmddyyyy%
Event Generation Time showing the date in mmddyyyy format
%gt^ddmmmyyyy%
Event Generation Time showing the date in ddmmmyyyy format
%gt^mm%
Event Generation Time showing only the month
%gt^dd%
Event Generation Time showing only the day
%gt^yy%
Event Generation Time showing only the short year
%gt^yyyy%
Event Generation Time showing only the long year
%cs%
Current state of the configured object. This is applicable only to OCC violation events.
%cv%
Current value of the configured object. This is applicable only to OCC violation events.
%v1%
Threshold value1 for a configured object. This is applicable only to OCC violation events.
%v2%
Threshold value2 for a configured object. This is applicable only to OCC violation events.
%transid%
TMF Transaction ID
95
Appendix F: OCC Errors
The following table enlists and describes various OCC Errors.
Table 11.
OCC Errors
Error
Description
Invalid Manager Name
Configuration
Invalid entry in the Manager Name field in the Threshold dialog box. This field is not available
for all the subsystems. For example, Manager name for BASE24 objects has to be the NCP
process that owns the resource node and must have been defined during the installation or
using ALTROVNM before starting OCC.
Invalid Object Name
Configuration
Invalid entry in the Objects field in the Threshold dialog box. This should contain the object
name for the selected subsystem. Wildcard characters are allowed for most of the subsystems.
Invalid EMS Owner. Subsys
Configuration
Invalid entry in the Owner.Subsystem field in the Threshold dialog box. This field is available for
the EMS subsystem.
Examples of valid entries are: TANDEM.EMS, TANDEM.PATHWAY, and MYORG.1.
For HPE NonStop subsystems, the subsystem owner is “TANDEM”.
Command Failed. Error =
-9999
Please List Again
Working with thresholds or objects without updating the displayed information with current
data in the Threshold and Objects pane. Update the displayed thresholds and objects with the
current data in the Threshold and Objects pane respectively by listing them again.
Multi-Node Key in use. Try
again!
This error is generated on trying to create a copy of a multi-node configuration. Check whether
the configuration is multi-node in the Multi-node column of the Threshold pane.
Lost connection with node
The connection with the NonStop node is lost.
Host version mismatch
There is a version mismatch between the OCC and the NonStop Server OVNM component.
Insufficient Write privileges The user trying to perform a particular task does not have the required Write privilege.
<value1> and <value2>
should be >=0
The user trying to enter negative values in the Value1 and Value2 boxes. Enter positive values
in the boxes and create the threshold configuration again.
Threshold obsolete, use
PROCESS/LOOPING
Too many wildcards used,
review config
Too many objects found for use. The system attempted to transfer too much data. Use wildcard
characters with care as this increases the search for objects to use for the threshold
configuration.
UPDATE OBJECTS/CONFIG
FAILED(201)
The current path to the device is down, an attempt was made to write to a non-existent
process, the message-system request was incorrectly formatted, or an error was found in the
message system interface.
Invalid Threshold in current Support for the DIAGNOSING and SUSPENDED thresholds is not available on Dxx machines.
OS Version
Selecting these thresholds will cause this error message to be displayed and no configuration
or object will be added to the database. For example, Creating a threshold configuration of
ATP6100 subsystem on Dxx machines will give this error message as these machines do not
support DIAGNOSING and SUSPENDED thresholds.
96
Error
Description
Please List Objects before
Add Object
When multiple users are working with thresholds or objects without updating the displayed
information with current data in the Threshold and Objects pane. For example, if one user has
deleted a particular threshold and then the other user on a separate workstation trying to Add
object to the threshold will encounter this error.
Update the displayed thresholds and objects with the current data in the Threshold and
Objects pane, respectively, by listing them again.
97
Appendix G: NetBatch Monitoring
This appendix describes how to set up NetBatch EMS thresholds to monitor jobs in Progress and jobs that
Abended.
The group and threshold names that are used in the ObjectMap panel do not have to be exactly what is
documented here, but they need to be consistent. In this example, NetBatch is the group name. Whatever name you
use, it has to be the same for all of these thresholds. The threshold names used are JobsInProgress and
AbendedJobs. Spaces are allowed, but it is recommended not to use spaces, as two spaces between words will be
considered different than a single space.
Only three Event numbers have been used here, but there are five thresholds defined.
•
Event 102 (job started) is used to ADD to the JobsInProgress group and DELETE from the AbendedJobs
group.
•
Event 202 (job ended normally) is used to DELETE from the JobsInProgress group.
•
Event 203 (job abended) is used to DELETE from the JobsInProgress group and ADD to the AbendedJobs
group.
Follow the procedure described below to set up NetBatch EMS thresholds to monitor jobs in Progress and the jobs
that have Abended.
1.
These thresholds will require you to tell AO what tokens to use in the ObjectMap display. NetBatch has many
tokens that are defined, but not all of them are used in the EMS messages, which get generated when a job
starts, completes or abends. The first step in this process is to collect the EMS token files for C. These files can
be interpreted by AO to assist in your token selection:
a. From the Host Installation Client, select any Tandem node – preferably the one with the most current
Operating System.
b. This step is performed only once per PC.
c. Click the Get Token Files button.
d. This will prompt you for your password and then start downloading the entire “C” files from
$system.zspidef. This process could take several minutes, depending on your LAN speed.
2.
The next step is to add the first threshold for event 102. This threshold will add the Job to the
Jobs-in-progress window in ObjectMap. Specify the following information in the various fields.
a. Subsystem/Object Type = EMS/Event
b. Owner.Subsystem = Tandem.NetBatch
c. Event number = 102
d. Object is in violation if “EXECUTE-DEFINED-ACTIONS”
e. Comments – Any relevant text can be specified.
f.
3.
Monitoring – Active
Click the Actions button and in the displayed dialog box specify the following information.
a. Severity: Anything you want, eventually this will be enhanced to include Normal.
b. Click the ObjectMap tab.
i.
Select add/update.
ii.
Click Map event using.
iii. Click Lookup token numbers:




Click where it says “select file to scan”. A list of files should be displayed. Select the file called
ZBATC (netBATch). If no files are displayed, then step 1 was not completed successfully.
In the left column (subject), select ZBAT Job Name ID.
In the right column (manager), select ZBAT Scheduler ID.
Click the Done button.
c. Enter NetBatch as the Group Name.
98
d. Enter JobsInProgress as the Thresholdname.
e. Click the OK button.
f.
Click the Apply button.
NOTE:
Be sure you click Apply to save the information for the next entry.
4.
Add the second threshold for the same event – 102. This threshold will DELETE the Job from the Abended
window in ObjectMap. All the data from above should still be available in the add threshold window.
a. Change the comments if required.
b. Click the Actions button.
i.
Click the ObjectMap tab.
ii.
Select Delete (at the top).
iii. Change “JobsInProgress” to “AbendedJobs”.
iv. Click the OK button.
v.
5.
Click the Apply button.
Add the third threshold. This one will be for the event 202, which signifies that a job has ended successfully. All
the previous data should still be available from the previous add.
a. Change the Event Number to 202.
b. Change the comments if required.
c. Click the Actions button.
i.
Click the ObjectMap tab.
ii.
Make sure that the Delete option is still selected.
iii. Change “AbendedJobs” to “JobsInProgress”.
iv. Click the OK button.
v.
6.
Click the Apply button.
Add the fourth threshold. This one will use the event number that is used when the job abends. This particular
threshold will add it to the AbendedJobs window.
a. Change the Event Number to 203
b. Change the comments if required.
c. Click the Actions button.
i.
Click the ObjectMap tab.
ii.
Note that the Delete option is still selected and the threshold name is JobsInProgress.
iii. Click the OK button.
iv. Click the Apply button.
7.
Add the fifth and last threshold. This is the abend event (203) and it will add it to the abended jobs window.
a. Change the comments if required.
b. Click the Actions button.
i.
Click the ObjectMap tab.
ii.
Change the Delete option to Add/Update.
iii. Change the threshold name to AbendedJobs.
iv. Click the OK button.
v.
Click the OK button.
When you view the thresholds in the main configuration pane, you should see five thresholds – two for event 102,
one for event 202 and two for event 203.
99
You can now use ObjectMap to view jobs that are in progress or in an abend state. However, since all of this is
based on EMS messages, ObjectMap will not report any jobs that were started or abended before you added these
thresholds. If you stop/restart ObjectMap, your pre-existing information will be lost and once again, you will only get
information about new jobs that start, stop or abend.
By clicking the JobsInProgress entry in the left pane of ObjectMap and clicking the ListMap icon on the top and
then doing the same for AbendedJobs, you can have two windows that are visible concurrently that show the list of
jobs in progress and those that have abended. These windows will be updated in real-time as long as ObjectMap is
communicating with the backend.
100