HP Operations Agent for NonStop Object Configuration Client Guide Part number: 540076-009 Tenth Edition: 12/2013
Legal notices Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Preface Before You Begin ........................................................................................................................................ 8 Audience ................................................................................................................................................... 8 Goals of Documentation .............................................................................................................................. 8 Organization................
3-9 Maintenance ........................................................................................................................ 56 4 Working With Object Configuration Client 4-1 Prerequisites ......................................................................................................................... 58 4-2 Managing the Environment .................................................................................................... 59 4-3 Creating a Threshold Configuration ............
Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 1-1 Object Management........................................................................................................
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 4-7 OCC Advanced Options Dialog Box Maintenance Tab Page ............................................................. 63 4-8 OCC Schedule Dialog Box .............................................................................................................. 64 4-9 OCC Actions Dialog Box with Alert Tab Page ...................................................................................
Tables Table Table Table Table 2-1 Toolbar Icons ................................................................................................................................. 23 2-2 Monitoring Bar Icons ...................................................................................................................... 24 4-1 Color Coding................................................................................................................................. 73 2 EMS Threshold List ............
Preface Object Configuration Client (OCC) facilitates configuration of the HP NonStop server components for management by the HP 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 HP NonStop environment, this manual explains the concepts behind OCC and illustrates all the facets of the software.
Organization Sr. No Chapter Name Description Chapter 1. Object Management: Introduction Introduces Object Management and how it is implemented with OVNM. Chapter 2. Object Configuration Client Introduction Gives detailed reference for the various components of the Object Configuration Client GUI. Chapter 3. Object Configuration Client: The Understanding Gives information about the concepts related to the Object Configuration Client. Chapter 4.
OVNM Manuals This section provides an overview of the OVNM manuals and their contents. 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 and stop OVNM components PDF OVNM User Guide Explains how to use the OVNM utilities and troubleshooting procedures for OVNM.
1 Object Management: Introduction 1-1 About OVNM HP Operations Agent for NonStop (OVNM) is a fully integrated, out-of-the-box solution that seamlessly works with many Enterprise Management Systems (HPOM, Tivoli, BMC, etc.), extending the managed domain to include HP NonStop Servers.
1-4 Introducing OCC OCC is designed to configure HP 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 HP NonStop nodes from a single management workstation, a single node from multiple workstations, or any other combination thereof.
2 Object Configuration Client Interface Object Configuration Client Interface Figure 2-1 OCC GUI 2-1 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.
2-2 Menu Bar Figure 2-2 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. 2-3 Toolbar Figure 2-3 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.
2-6 Menus The various menus available on the Menu bar are as follows: • File • Threshold • Edit • Monitoring • Recovery • View • Tools • Help 2-6-1 File Menu This is the first menu on the Menu bar. The option available in this menu is: • Exit This option is used to exit from the OCC application.
• Delete Config This option is used to delete the selected threshold(s). • List Objects This option is used 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 You can 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.
2-6-3 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 2-9 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.
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 HPOM (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.
2-6-6 View Menu The various options available in the View menu are: • Toolbar • Monitoring Toolbar • Status Bar • Messages • Columns Figure 2-13 OCC View Menu The various options available in the View menu are: • 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.
2-6-7 Tools Menu The Tools menu offers the following options • Managed Subsystems • Log on • Log off • Cancel all requests for this node • Options Figure 2-15 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.
• Options Clicking the Options displays the Options dialog box. This dialog box can be used to configure the autologoff 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 2-16 OCC Options Dialog Box There are two Severity fields that can be defined when using the OCC. The first one is located in the Actions/Alert panel.
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 HP 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.
2-6-8 Help Menu The Help menu offers the following options: • Help Topics • About Figure 2-17 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.
2-7-2 Monitoring Bar S. No 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 7. Activate Object Monitoring Monitoring 8. Inactivate Object Monitoring Monitoring 9. Activate Object Recovery Recovery 10.
2-8 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. 2-8-1 Object Class Pane The following right-click menus can be accessed in the Object Class panel.
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 2-20 OCC Object Class Pane Object Class Icon Right-click Menu • List Configurations This command is used to list all the thresholds configured for the selected Object Type.
• Modify Configuration This option is used 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 The deletion of selected threshold configurations can be made using this option. It is a shortcut for the Delete Config option in the Threshold menu.
e. 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 2-23 Apply Auto-Maintenance Immediately Dialog Box The options supported by this feature are: • Rebuild • Update (add only).
2-8-3 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 2-24 OCC Objects Pane Right-Click Menu The various options in this menu are as follows: • View Object Detail Using this option, you can check the conditions specified for the selected object. Clicking this option displays the Configuration / Object Detail dialog box.
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 HP NonStop objects. This section covers the various concepts of OCC. 3-1 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.
3-2 Authentication & 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 3-2 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 HP NonStop host. The HP NonStop administrator specifies these.
3-3 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. You can access the Schedule dialog box using the Schedule button in the Threshold dialog box.
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.
3-4 Monitoring Monitoring is inactivated by default on the HP 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 HP NonStop host will do the monitoring as per the checks specified for the threshold configuration.
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.
3-5 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.
3-5-1 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 3-8 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.
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 a 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.
3-5-2 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 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.
3-5-3 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.
the Schedule displays the Schedule dialog box. Use the various options available on the Schedule dialog box to specify a customized recovery schedule. Figure 3-12 OCC Recovery Schedule Dialog Box The default Delay Interval value is 05 minutes. This means that the OVNM recovery process on the HP 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.
3-5-4 eEvents OVNM provides direct correlation and formatting facility for leading Enterprise Management Console solutions provided by Tivoli, HPOM 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, HPOM 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 HPOM.
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 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.
The Token list hyperlink displays the Event Token Numbers dialog box. The dialog box displays a list of tokens. Figure 3-16 Event Token Numbers Dialog Box Object Configuration Client: The Understanding 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.
3-6 EMS Actions 3-6-1 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.
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 3-18 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.
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.
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 HPOM). 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.
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 HP documentation for more details. 2.
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).
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 Subject: TCP1 TANDEM.PATHWAY.D44/1043 Subject: TCP1 Suppressed 9 events. TANDEM.PATHWAY.D44/1043 When the “ignore burst” message is generated, it will show you how many events were suppressed since the last time its counter was reset.
3-7 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.
3-8 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.
3-9 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.
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: Auto maintenance should be used responsibly.
4 Working With Object Configuration Client 4-1 Prerequisites The prerequisites for using OCC are as follows: 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.
4-2 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 HP 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.
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 4-3 OCC 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.
4-3 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 HP 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.
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.
Figure 4-6 OCC Object Properties Dialog Box Location Tab Page 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 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.
Step I: Entering Action Details The Actions button helps you to access the Actions dialog box using, which you can configure alert, recovery, email and page options. You can also provide specifications for Tivoli and HPOM. To access the Actions dialog box, click the Actions button in the Threshold dialog box. Figure 4-9 OCC Actions Dialog Box with Alert Tab Page 1. Entering Alert Definition Data: a.
2. Entering Recovery Data To specify the recovery details, click the Action tab on the Actions dialog box. This displays the Action tab page. Figure 4-10 OCC Actions Dialog Box with Action Tab Page a. Select the recovery type to be applied using the first Command box. b. 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.
i. 3. Activate or deactivate recovery using the Recovery box in the Options section in the Action tab page. Entering E-Mail Alert Information 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 4-12 OCC Actions Dialog Box with Mail Tab Page a.
4. eEvents a. Click the eEvents tab in the Actions dialog box. Figure 4-13 OCC Actions Dialog Box eEvents Tab Page b. Select the HPOM/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.
Step J: Configuring EMS Actions 1. ObjectMAP a. Click the ObjectMAP tab to configure the objects to be displayed in the ObjectMAP interface. The tab page is displayed only when you select the EMS subsystem. Figure 4-14 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 radio button. c.
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 4-15 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.
4-4 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. 4-4-1 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 4-16 OCC List Configurations Option An easy way to list configurations is by double-clicking on the Object Type.
4-4-2 Listing Objects 1. List the thresholds for the required subsystem in the Threshold pane. 2. Select the threshold whose objects you want to list. 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.
4-4-3 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 4-1 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.
4-5 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 rightclick menu in the Threshold & Objects panes.
4-5-2 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 4-20 OCC Modify Configuration / Object Dialog Box 4.
4-5-4 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.
Appendix A: Subsystems Managed OCC allows you to monitor most of the major HP NonStop subsystems. A list of all the predefined subsystems managed by OCC is as follows: NOTE: The BASE24, MQ-SERIES and TELCO 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.
7. EXPAND 8. FILESYS The FILESYS subsystem deals with the monitoring and management of files on a HP 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*. 9.
17. 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.
Appendix B: EMS Message Handling This appendix contains an example of setting up an EMS event for forwarding to the HP 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 HPOM panel. 1.
3. Select the nodes on which the configuration is to be applied using the Nodes area. Figure B-3 OCC Threshold – Nodes Area 4. Select the Subsystem and Object Type as EMS and EVENT in the Threshold dialog box. Figure B-4 OCC Threshold Dialog Box with EMS Subsystem and EVENT Object Type Selected 5. Specify the owner and the subsystem of the event in the owner.subsystem format in the Owner.Subsystem box. You can use the button next to the box to type the text in upper or lower case.
Appendix B Figure B-5 OCC Threshold Dialog Box with Owner.Subsystem Information Examples of valid Owner.Subsystem are: TANDEM.EMS TANDEM.PATHWAY MYORG.1 For HP NonStop subsystems, the subsystem owner is “TANDEM”. 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.
Figure B-6 OCC Threshold Dialog Box with Event Number Information 7. 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 B-7 OCC Threshold Dialog Box with Threshold Information 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.
• 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 ”, “Contains ” and “Equals at offset ”. The easiest method to test for text within an EMS message is using “Contains ”. The text can occur anywhere in the message and it is NOT case sensitive.
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 B-9 OCC Actions Dialog Box NOTE: Service IDs are associated with NonStop Server Service Components in HPOM Services View. 10. Configure recovery, e-mail and events facility using the Action, Mail and eEvents tab pages, respectively. 11.
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).
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 HP Operations environment. 1. Select the OSS subsystem in Object Class pane and Click the New Configuration option in the Threshold menu. Figure C-1 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.
4. Specify the name and location of the OSS logfile in the Object File Name box. Figure C-3 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//G//
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 C-5 OCC Threshold Dialog Box with Monitoring Information 7. 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.
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 HP 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.
Object Type THRESHOLD Poll Interval Repeat Every Severity 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 I
Appendix E: Substitution Parameters 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% Event Text Message (default = <0:255>) %t(index)#TokenNumber
Appendix F: 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.
Index absolute schedule, 57 actions, 39 activate config monitoring, 18 activate config recovery, 18 activate node monitoring, 17 activate object monitoring, 18 activate object recovery, 18 add default policies, 90 add new object, 16, 27 advanced options, 56 audience, 8 authentication & security, 31 auto maintenance, 56 inactivate object monitoring, 18 inactivate object recovery, 18 Is box, 64 L line box, 62 list configurations, 15, 26 list objects, 16 listing configurations, 71 listing objects, 72 log off
Document Feedback Form We would appreciate your comments on the OVNM Object Configuration Client. After you have read the Guide and used the software, please take a few moments to complete this form and return it to appropriate HP product support service. 1. The organization of the Guide makes it easy to locate topics quickly. Strongly Disagree 1 2. Strongly Agree 2 3 4 The appearance of the pages makes it easy to locate information quickly. Strongly Disagree 1 3.
9. The level of writing in this book is: Too Basic Just Right Too Technical (Please be specific.) Do you have any other suggestions for improvement? Document Feedback Form 10.
