HP Operations Agent for NonStop Troubleshooting Guide Part number: 540079-006 Sixth edition: 12/2008
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 ..................................................................................................................................... 9 Audience ................................................................................................................................................ 9 Goals of Documentation ........................................................................................................................... 9 Organization .......................
5-2 6 5-1-3 Check if a valid port is configured for Elink ........................................................................... 98 Console Configuration Errors......................................................................................................... 99 5-2-1 Valid Values for Configuring Console Options ....................................................................... 99 5-2-2 Querying Events.........................................................................................
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 2-1 OVNM Host Installation Client Dialog Box Buttons ........................................................................
Figure Figure Figure Figure Figure Figure Figure Figure 5-13 Open Policies Dialog Box ......................................................................................................... 110 5-14 Acknowledge Events Dialog Box ............................................................................................... 111 6-1 NonStop Nodes Status Option .................................................................................................... 113 6-2 NonStop Nodes Status Option ...........
Tables Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 2-1 Adding NonStop Host Configuration.............................................................................................. 15 2-2 Adding Communication Configuration ......
Tables 8
Preface HP Operations Agent for NonStop (OVNM) is an out-of-the-box solution that provides seamless integration of HP Operations Software (previously known as HP OpenView) with HP NonStop servers. The software is a natural extension of HP Operations and provides you with true end-to-end management of your NonStop environment. Before reading the documentation, you are expected to have a basic understanding of HP Operations environment, as well as the HP NonStop environment.
OVNM Documentation Map 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 HP web server directory.
About 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.
1 Troubleshooting OVNM 1-1 Introduction This guide provides assistance for troubleshooting issues associated with OVNM. It provides general diagnostic steps and specific issues with verification and fix information. This manual provides information relating problems that occur during installation, OVNM Runtime errors along with the error that may occur during configuration of the OVNM utilities.
2 Host Installation Client: Errors & Warnings 2-1 Introducing OVNM Host Installation Client The OVNM Host Installation Client is a Windows based interactive GUI, which is used to automate the procedures like installation and modifications on the HP NonStop managed node. This chapter details the various warnings and error messages, which are displayed while working with OVNM Host Installation Client.
2-2 Troubleshooting Host Installation Client 2-2-1 Errors When Configuring a New NonStop Host The New button in the OVNM Host Installation Client dialog box can be used to add a new HP NonStop host. Clicking on the button displays the New OVNM Configuration dialog box. 2-2-1-1 Adding NonStop Host Configuration The Host tab page is displayed by default, which allows you to configure the Host information along with the parameters to be used to logon to the host.
The different error messages and warnings displayed when adding a new OVNM Configuration related to the Host tab page, their causes and the action to be taken are described in the following table. Table 2-1 Adding NonStop Host Configuration Sr.No. Error Message and Warning Possible Causes: This message box is displayed when the Node Name field in the Host tab page is left blank or has an invalid value. Action to be taken: Enter the NonStop Node Name in the Node Name field in the Host tab page.
Table 2-1 Adding NonStop Host Configuration Sr.No. Error Message and Warning 5. Possible Causes: This message box is displayed when the User ID field in the Host tab page is left blank. Action to be taken: Enter the Guardian User ID or alias that will be used to logon to the HP NonStop Server in the User ID field in the Host tab page. 6. Possible Causes: This message box is displayed when the TCPIP Process field in the Host tab page is left blank or has an invalid value.
Table 2-1 Adding NonStop Host Configuration Sr.No. Error Message and Warning Possible Causes: This message box is displayed when the OVNM Subvolume field in the OVNM tab page is left blank or has an invalid value. Action to be taken: Enter the subvolume to operate the OVNM application in the OVNM Subvolume field. By default this field has the value $SYSTEM.OVNM. The validations for the OVNM Subvolume field are: 1 It should begin with “$”. 2 The format of this field is $..
Table 2-1 Adding NonStop Host Configuration Sr.No. Error Message and Warning 12. Possible Causes: This message box is displayed when the OVNM Port field in the Host tab page is left blank. Action to be taken: Enter the IP port used for communicating from the Host to the HP Operations Manager server in the OVNM Port field. By default this field has the value 5030. This field accepts only positive integers in the range of 0-65535. 13.
2-2-1-2 Adding Communication Configuration The Communication tab page in the New OVNM Configuration dialog box allows you to configure Telnet and FTP Information. Host Installation Client: Errors & Warnings Figure 2-3 New OVNM Configuration Dialog Box Communication Tab Page The different error messages and warnings displayed when adding a new OVNM Configuration related to the Communication tab page, their causes and the action to be taken are described in the following table.
Table 2-2 Adding Communication Configuration Sr.No. Error Message and Warning 3. Possible Causes: This message box is displayed when the FTP Port field in the Telnet and FTP Information area in the Communication tab page is left blank or has an invalid value. Action to be taken: Enter the IP Port used for FTP session to the Host in the FTP Port field in the Communication tab page. 4.
Table 2-2 Adding Communication Configuration Sr.No. Error Message and Warning Possible Causes: This message box is displayed when the Console Address in Console and Enterprise Information area in the Advance Host Configuration screen is left blank or has an invalid value. Action to be taken: Enter the Console IP Address used to access the NonStop Server in the Address field in the Advance Host Configuration tab page. 8.
Table 2-2 Adding Communication Configuration Sr.No. Error Message and Warning 12. Possible Causes: This message box is displayed when the Port entry in OCC, ObjectMAP and ObjectStats Information area in the Advance Host Configuration screen is left blank or has an invalid value. Action to be taken: Enter the unique OCC Port entry in the Port field in the Advance Host Configuration tab page.
2-2-1-3 Adding Mail Configuration The Mail tab allows you to configure E-mail facility on the HP NonStop server. Host Installation Client: Errors & Warnings Figure 2-4 New OVNM Configuration Dialog Box Mail Tab Page The different error messages and warnings displayed when adding a new OVNM Configuration related to the Mail tab page, their causes and the action to be taken are described in the following table. Table 2-3 Adding Mail Configuration Sr.No. Error Message and Warning 1.
Table 2-3 Adding Mail Configuration Sr.No. Error Message and Warning 3. Possible Causes: This message box is displayed when the Email Port field in the Mail tab page has an invalid value. Action to be taken: Enter the IP port to be used by the Mail server in the Email Port field in the Mail tab page. By default Email Port is 25 and the recommended range is 0- 65535. 4. Possible Causes: This message box is displayed when the Sender ID field in the Mail tab page is left blank.
Table 2-3 Adding Mail Configuration Sr.No. Error Message and Warning Possible Causes: This message box is displayed when the Giveup Interval field in the Mail tab page has an invalid value. Action to be taken: Specify how long to keep trying to send an email in the Giveup Interval field in the Mail tab page. Once it has been in the queue for the specified number of minutes it will be deleted. The default value for Giveup Interval is 120 minutes and the recommended range is 1-600.
2-2-1-4 Adding EMS Distributors Configuration The Distributor tab page of the New OVNM Configuration dialog box allows you to configure the HP NonStop distributors and the collectors and filters associated with them. Figure 2-5 New OVNM Configuration Dialog Box Distributor Tab Page The different error messages and warnings displayed when adding a new OVNM Configuration related to the Distributor tab page, their causes and the action to be taken are described in the following table.
Table 2-4 Adding EMS Distributors Configuration Sr.No. Error Message and Warning Possible Causes: This message box is displayed when the Collector(s) field in the Distributor tab page is left blank or has an invalid value. Action to be taken: Enter the unique value in the Collector(s) field that displays the list of collectors in the Distributor tab page. These are comma separated values. The format of this field is $. 4.
2-2-1-5 Adding OCC Configuration The OCC tab allows you to configure the OVNM Object Configuration Client (OCC) application. Figure 2-6 New OVNM Configuration Dialog Box OCC Tab Page The different error messages and warnings displayed when adding a new OVNM Configuration related to the OCC tab page, their causes and the action to be taken are described in the following table. Table 2-5 Adding OCC Configuration Sr.No. Error Message and Warning 1.
Table 2-5 Adding OCC Configuration Sr.No. Error Message and Warning Possible Causes: This message box is displayed when the Collector(s) field in the OCC tab page is left blank or has an invalid value. Action to be taken: Enter the unique value in the Collector(s) field that displays the list of collectors in the OCC tab page. These are comma separated values. The format of this field is $. 4.
2-2-1-6 Adding Plug-In Configuration The Plug-Ins tab page is optional and is intended for future OVNM Plug-In support. Figure 2-7 New OVNM Configuration Dialog Box Plug-Ins Tab Page The different error messages and warnings displayed when adding a new OVNM Configuration related to the Plug-Ins tab page, their causes and the action to be taken are described in the following table. Table 2-6 Adding Plug-In Configuration Sr.No. Error Message and Warning 1.
Table 2-6 Adding Plug-In Configuration Sr.No. Error Message and Warning Possible Causes: This message box is displayed when the STAT Subvolume field in the Plug-Ins tab page has an invalid value. Action to be taken: Enter the location of STAT Subvolume in the STAT Subvolume field in the Plug-Ins tab page. By default this field is empty. The validations for the STAT Subvolume field are: 1 It should begin with “$”. 2 The format of this field is $.. 3 The ‘$’ and dot(.
2-2-1-7 Adding EMS Template Configuration The EMS Template tab page allows you to configure for EMS template files. Figure 2-8 New OVNM Configuration Dialog Box EMS Template Tab Page The different error messages and warnings displayed when adding a new OVNM Configuration related to the EMS Template tab page, their causes and the action to be taken are described in the following table. Table 2-7 Adding EMS Template Configuration Sr.No. Error Message and Warning 1.
Table 2-7 Adding EMS Template Configuration Sr.No. Error Message and Warning Possible Causes: This message box is displayed when you have chosen not to use the standard EMS template by unselecting the Use Standard EMS Template check box but you have not specified the location for any user-defined template in the EMS Template File Location field in the EMS Template tab page.
2-2-1-8 Adding BASE24 Configuration The BASE24 tab page allows you to configure BASE24. Figure 2-9 New OVNM Configuration Dialog Box BASE24 Tab Page The error message displayed when adding a new OVNM Configuration related to the BASE24 tab page, its cause and the action to be taken is described in the following table. Table 2-8 Adding BASE24 Configuration Sr.No. Error Message and Warning 1.
2-2-1-9 Errors during Nonstop Node Installation The installation procedure on the HP NonStop Node can be started by clicking on the Install button on the New OVNM Configuration dialog box after specifying the various parameters. Host Installation Client: Errors & Warnings Figure 2-10 New OVNM Configuration Dialog Box – Install Button The different error messages and warnings displayed when installing OVNM on the specified host, their causes and the action to be taken are described in the following table.
Table 2-9 During NonStop Node Installation Sr.No. Error Message and Warning 2. Possible Causes: This message box is displayed when the NonStop node name provided in the Node Name field in the Host tab page does not match with the actual NonStop node name. Action to be taken: Enter the correct node name in the Node Name field in the Host tab page of New OVNM Configuration dialog box and reinstall OVNM. 3.
Table 2-9 During NonStop Node Installation Sr.No. Error Message and Warning Possible Causes: The OVNM Host Response for Installation dialog box shows the error “BAD PORT NUMBER OR ALIAS” when Host Installation Client is unable to connect to the port specified in the Telnet Port or the FTP Port field in the Host tab page. Action to be taken: Enter the Telnet port and the FTP port in the Telnet Port and the FTP Port fields respectively and continue with the installation.
Table 2-9 During NonStop Node Installation Sr.No. Error Message and Warning 9. Possible Causes: The OVNM Host Response for Installation dialog box shows the error code “10053” when the connection was aborted possibly due to a data transmission timeout or protocol error. Action to be taken: Make sure that the connectivity between the NonStop Server and workstation where Host Installation Client is installed is not broken during OVNM installation. You will have to reinstall OVNM. 10.
Table 2-9 During NonStop Node Installation Sr.No. Error Message and Warning Possible Causes: The OVNM Host Response for Installation dialog box shows the error code “43” when Host Installation Client is unable to obtain disk space for file extent. Action to be taken: Check the disc space available on the NonStop Node. If the disk space is less than the space required to install OVNM on the NonStop Node then delete the unwanted files and reinstall OVNM.
2-2-1-10 Errors When Modifying HP NonStop Host Information The Modify button in the OVNM Host Installation Client dialog box can be used to modify the host information. Clicking on the button displays the Modify OVNM Configuration dialog box. Figure 2-11 Modify OVNM Configuration Dialog Box The different error messages and warnings displayed when modifying the host information, their causes and the action to be taken are described in the following table. Table 2-10 Modifying NonStop Host Installation Sr.
Table 2-10 Modifying NonStop Host Installation Sr.No. Error Message and Warning Possible Causes: The OVNM Host Response for Modification dialog box shows the error “CONNECT FAILED FOR IP ADDRESS” when Host Installation Client is unable to connect to the IP address specified in the IP Address field in the Host tab page. Action to be taken: Enter the correct Host IP address in the IP Address field in the Host tab page and modify the host information again.
2-2-1-11 Errors When Upgrading Software Release The Upgrade Release option in the Upgrade menu of the OVNM Host Installation Client dialog box allows you to perform a full software release upgrade. Figure 2-12 OVNM Host Installation Client Dialog Box Upgrade Menu The different error messages displayed when upgrading the host information, their causes and the action to be taken are described in the following table. Table 2-11 Upgrading Software Release Sr.No. Error Message and Warning 1.
Table 2-11 Upgrading Software Release Sr.No. Error Message and Warning Possible Causes: The OVNM Host Response for Modification dialog box shows the error “CRITICAL FILES ARE STILL OPEN – MUST STOP THE APPLICATION” if you have not stopped the agents before upgrading the node. Action to be taken: Make sure you stop the OVNM agents using the Stop Agents options in the Start\Programs\HP OVNM\Management Server Tools menu before performing the full software release upgrade.
2-2-1-12 Errors When Applying Patch The Apply Patch option in the Upgrade menu of the OVNM Host Installation Client dialog box allows you to upgrade the software with a new patch or fix. Figure 2-13 Apply Patch to Host Dialog Box The different error messages displayed when applying patch, their causes and the action to be taken are described in the following table. Table 2-12 Applying Patch Sr.No. Error Message and Warning 1.
Table 2-12 Applying Patch Sr.No. Error Message and Warning Possible Causes: The OVNM Host Response for Applying Patch dialog box shows the error “CONNECT FAILED FOR IP ADDRESS” when Host Installation Client is unable to connect to the IP address specified in the IP Address field in the Host tab page. Action to be taken: Enter the correct Host IP address in the IP Address field in the Host tab page and reapply the patch.
2-2-1-13 Errors When Deleting HP NonStop Host The Delete button in the OVNM Host Installation Client dialog box allows you to delete an existing host configuration. You can select the Delete From Workstation, Delete From Host or Delete From Both menu options to delete the host configuration from a workstation, host or both, respectively.
2-2-1-14 Errors When Importing Host Configuration The Import button in the OVNM Host Installation Client dialog box allows you to import the host configuration(s) from a file having a .cfg extension. Host Installation Client: Errors & Warnings Figure 2-15 OVNM Host Installation Client – Import Button The error messages displayed when importing host configuration, their causes and the action to be taken are described in the following table. Table 2-14 Importing Host Configuration Sr.No.
2-2-1-15 Errors When Getting Token Files The Get Token Files option in the Tools menu gets enabled once a node is added to the Managed Host list. This button can be used to obtain EMS token files from the selected HP NonStop Host. The files imported from the HP NonStop Server are copied to the OVNM\OCC\EmsTokenFiles folder in the directory where OVNM has been installed.
2-2-1-16 Errors While Synchronizing With Host The Sync With Host option in the Tools menu can be used to synchronize Host information with the PC. The error messages displayed when synchronizing host information, there causes and the action to be taken are described in the following table. Table 2-16 Synchronizing with Host Sr.No. Error Message and Warning Host Installation Client: Errors & Warnings 1.
2-2-1-17 Errors While Updating Host Information The OVNM Host Installation Client updates the configuration information when it performs the following functions: • Add New HP NonStop Host • Modify HP NonStop Host Information • Upgrade • Delete HP NonStop Host • Import Host Configuration • Get Token Files and Synchronize Host Information with PC The error messages displayed when updating the host configuration, there causes and the action to be taken is described in the following table.
3 Host Management Client: Errors & Warnings 3-1 Introducing OVNM Host Management Client The OVNM Host Management Client is a Windows based interactive GUI, which is used to automate the HP NonStop host management procedures like starting and stopping OVNM agent. This chapter details the various warnings and error messages, which are displayed while working with OVNM Host Management Client.
The different error messages and warnings displayed when starting agents, their causes and the action to be taken are described in the following table. Table 3-1 Starting OVNM Agent on NonStop Server Sr.No. Error Message and Warning 1. Possible Causes: Clicking on the Start Agent button in the OVNM Host Management Client dialog box displays the Login to Host dialog box.
Table 3-1 Starting OVNM Agent on NonStop Server Sr.No. Error Message and Warning 3. Host Management Client: Errors & Warnings Possible Causes: The OVNM Host Response for Starting Agent dialog box shows the error “Expecting the name of an existing file” when the Host Management Client is unable to find the STRTOVNM utility in the specified location. Action to be taken: To run the STRTOVNM utility it should be available in the volume.subvolume where OVNM is installed. Switch to the volume.
3-2-2 Errors When Stopping OVNM Agent on NonStop Server The Stop Agent utility in the Host Management Client can be used to stop the OVNM agent on the HP NonStop host. Figure 3-3 OVNM Host Management Client Dialog Box Stop Agent Button The different error messages and warnings displayed when stopping OVNM Agents, their causes and the action to be taken are described in the following table. Table 3-2 Stopping OVNM Agent on NonStop Server Sr.No. Error Message and Warning 1.
Table 3-2 Stopping OVNM Agent on NonStop Server Sr.No. Error Message and Warning 2. Possible Causes: The OVNM Host Response for Stopping Agent dialog box shows the error “Expecting the name of an existing file” when the Host Management Client is unable to find the STOPOVNM file in the specified location. Action to be taken: To run the STOPOVNM utility, it should be installed in the volume.subvolume where OVNM is installed. Switch to the volume.
Table 3-2 Stopping OVNM Agent on NonStop Server Sr.No. Error Message and Warning 4. Possible Causes: The OVNM Host Response for Stopping Agent dialog box shows the error “Unable to connect to \NODE” when the connectivity between the NonStop Server and the workstation where Host Management Client is installed was broken at some point during stopping agents.
3-2-3 Errors When Checking OVNM Status on NonStop Server The Status utility in the Host Management Client can be used to view the status of the OVNM and OCC components on the HP NonStop host. The different error messages and warnings displayed when checking the status of agent, their causes and the action to be taken are described in the following table. Table 3-3 Checking OVNM Status on NonStop Server Sr.No. Error Message and Warning 1.
Table 3-3 Checking OVNM Status on NonStop Server Sr.No. Error Message and Warning 2. Possible Causes: The OVNM Host Response for Status of Agent dialog box shows the error “Expecting the name of an existing file” when the Host Management Client is unable to find the STATOVNM utility. Action to be taken: To run the STATOVNM utility, it should be available in the volume.subvolume where OVNM is installed. Switch to the volume.
3-2-4 Errors When Viewing OVNM Agent Information on NonStop Server The View Info utility in the Host Management Client is used to get information about OVNM and OCC applications on the HP NonStop host. The different error messages and warnings displayed when using the View Info utility, their causes and the action to be taken are described in the following table. Table 3-4 Viewing OVNM Agent Information on NonStop Server Sr.No. Error Message and Warning 1.
Table 3-4 Viewing OVNM Agent Information on NonStop Server Sr.No. Error Message and Warning 2. Possible Causes: The OVNM Host Response for Viewing Information of Agent dialog box shows the error “Expecting the name of an existing file” when the Host Management Client is unable to find the INFOOVNM utility. Action to be taken: To run the INFOOVNM utility, it should be available in the volume.subvolume where OVNM is installed. Switch to the volume.
3-2-5 Errors When Generating OVNM Policy Report on NonStop Server The Policy Report utility in the Host Management Client is used to generate a report, which contains information about all the policies/threshold(s) that have been deployed at the NonStop host. The different error messages and warnings displayed when using the Policy Report utility, their causes and the action to be taken are described in the following table. Table 3-5 Generating OVNM Policy Report on NonStop Server Sr.No.
Table 3-5 Generating OVNM Policy Report on NonStop Server Sr.No. Error Message and Warning 2. Possible Causes: The OVNM Host Response for Generating Policy Report dialog box shows the error “File does not exist” when the Host Management Client is unable to find the POLCSV file, which is created after running the PLYREPT utility. Action to be taken: To run the PLCYREPT utility, it should be available in the volume.subvolume where OVNM is installed. Switch to the volume.
3-2-6 Errors When Collecting OVNM Agent Information on NonStop Server The Collect Info utility in the Host Management Client is used to gather detailed information of the OVNM environment on the HP NonStop node and save the information in the form of file(s), which may be helpful in diagnosing problems with the OVNM agent on the HP NonStop Host.
Table 3-6 Collecting OVNM Agent Information on NonStop Server Sr.No. Error Message and Warning 2. Possible Causes: The OVNM Host Response for Collecting Information of Agent dialog box shows the error “File does not exist” when the Host Management Client is unable to find CLCTINFO in the specified location. Action to be taken: To run the CLCTOVNM utility, it should be available in the volume.subvolume where OVNM is installed. Switch to the volume.
3-2-7 Errors When Generating Test Message on NonStop Server The Test Message utility in the Host Management Client is used to check the communication between the HP NonStop Node and the HP Operations Management Server. The different error messages and warnings displayed when using the Test Message utility, their causes and the action to be taken are described in the following table. Table 3-7 Generating Test Message on NonStop Server Sr.No. Error Message and Warning 1.
Table 3-7 Generating Test Message on NonStop Server Sr.No. Error Message and Warning 2. Possible Causes: The OVNM Host Response for Generating Test Message dialog box shows the error “Expecting the name of an existing file” when the Host Management Client is unable to find GENEMS in the specified location. Action to be taken: To run the GENEMS utility, it should be available in the volume.subvolume where OVNM is installed. Switch to the volume.
3-2-8 Errors When Importing Node Configuration on Nonstop Server The Import Node Configuration button in the OVNM Host Management Client dialog box helps you to import HP NonStop Host(s) configuration(s) from a file. The different error messages and warnings displayed when importing node configuration, their causes and the action to be taken are described in the following table. Table 3-8 Importing Node Configuration on Nonstop Server Sr.No. Error Message and Warning 1.
4 OCC: Errors and Warnings 4-1 Connectivity Problems with NonStop Servers NonStop Nodes Not Appearing in OCC: Not Connected to Elink OR NonStop Nodes Appear but are All RED: Lost Connection with Local Elink Figure 4-1 OCC Connectivity Problems with the NonStop Servers NonStop Servers Win dows Man agem en t Wor k s t at ion \DEV1 Port 5020 E Elinlink k OVMN MN OV Agent t Agen OR OCC E lin k S er v ice elink.
NonStop Nodes appear but Not All are Connected (Red Indicator) Figure 4-3 OCC Connectivity Problems with the NonStop Servers NonStop Servers Win dows Man agem en t Wor k s t at ion \DEV1 Port 5020 OCC E lin k S er v ice 5020 elink.log 5020 E Elinlink k OVMN MN OV Agent t Agen \DOTCOM OVMN MN OV Agent t Agen E Elinlink k OVNM NonStop Server components must be up in order to manage and configure Object Thresholds using Object Configuration Client (OCC).
Elink status can also be monitored using the OCC View -Message/Log pane. Figure 4-6 OCC Message / Log Pane If the error condition still exists, you can view the Elink Service Log File with Nodepad.exe. The location of the Elink Service Log File is: C:\Program Files\OVNM\Elink\elink.log. The status of Elink can also be verified using the NonStop Nodes Status window, which can be accessed by selecting the Start\Programs\HP OVNM\NonStop Server Tools\NonStop Nodes Status menu option.
4-2 OCC Configuration Errors 4-2-1 Failure to Load the Database The OCC fails to load the database due to the following reasons. Database Missing During OCC installation, the database file is automatically copied in the folder where the OCC is installed. If OCC is unable to access the file while starting up, the following error will be displayed.
4-2-2 Managing Subsystems The Managed Subsystems dialog box allows you to select the subsystems and their object types that you want to monitor for each HP NonStop node. Only the subsystems selected in this dialog box are visible in OCC. You can access this dialog box using the Managed Subsystems option in the OCC Tools menu. Figure 4-9 OCC Managed Subsystem Dialog Box The error message displayed when managing subsystems, its cause and the action to be taken is described below.
4-2-3 Authenticating the User 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 allows the authentication of the user. Figure 4-10 OCC Log on to Dialog Box The different error messages and warnings displayed when authenticating users, their causes and the action to be taken are described in the following table.
Table 4-2 Authenticating the User Sr.No. Error Message and Warning 4. Possible Causes: This message box is displayed during authenticating the user when the Node is offline. Action to be taken: Refer to the Connectivity Problems section to find the possible causes and actions to be taken when the node is offline. 5. Possible Causes: This message box is displayed during authenticating the user when the connection with the local elink is lost.
4-2-4 Configuring OCC Options You can configure authentication and Startup options using the General tab page in the Options dialog box. To access this, click on the Options command in the Tools menu. Figure 4-11 OCC Options Dialog Box The different error messages and warnings displayed when configuring options, their causes and the action to be taken are described in the following table. Table 4-3 Configuring OCC Options Sr.No.
4-2-5 Enabling or Disabling Recovery The Recovery features in OCC 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. Recovery can be enabled manually using the Action tab page in the Actions dialog box.
4-2-6 Configuring E-Mail Alerts 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. This dialog box can be accessed using the Actions button in the Threshold dialog box. Figure 4-13 OCC Actions Dialog box with Mail Tab Page The different error messages and warnings displayed when configuring E-Mail alerts, their causes and the actions to be taken are described in the following table.
Table 4-5 Configuring E-mail Alerts Sr.No. Error Message and Warning 2. Possible Causes: The To box in the Mail tab page can accept 240 characters. This message box is displayed when the characters in the To box exceed this limit. Action to be taken: Specify the e-mail addresses, profile names or the distribution list to whom the alerts should be sent in the To box in not more than 240 characters.
4-2-7 Creating Threshold Configurations The Threshold dialog box is used to create a new threshold configuration in OCC. You can access the Threshold dialog box by clicking on the New Configuration option in the Threshold menu. Figure 4-14 OCC Threshold Dialog Box The different error messages and warnings displayed when creating threshold configurations, their causes and the actions to be taken are described in the following table. Table 4-6 Creating Threshold Configurations Sr.No.
Table 4-6 Creating Threshold Configurations Sr.No. Error Message and Warning 2. Possible Causes: This message box is displayed when the Manager field in the Threshold dialog box is left blank. This field is available for the following thresholds: • BASE24 • EXPAND • ICE • ICE-DLSW • NETBATCH • MQ-SERIES • SNAX-XF • SPOOLER • SPOOLERP • TCPIP • TELCO Action to be taken: Specify the manager name in the Manager field.
Some of the fields available in the Object Details section are different for ATP6100, BASE24, EMS, OSS, PROCESS and TCPIP subsystems. The different error messages and warnings displayed when creating threshold configurations for these subsystems, their causes and the actions to be taken are described below: 4-2-7-1 ATP6100 Table 4-7 ATP6100 Subsystem Sr.No. Error Message and Warning 1.
4-2-7-3 EMS Table 4-9 EMS Subsystem Sr.No. Error Message and Warning 1. Possible Causes: This message box is displayed when the Owner.Subsystem field available in the Object Details section for the EMS subsystem is left blank. Action to be taken: Specify the owner and the subsystem of the event in the owner.subsystem format in the Owner.Subsystem field. You can either type in the line name or select from the list of the entries already made. 2.
4-2-7-4 OSS Table 4-10 OSS Subsystem Sr.No. Error Message and Warning 1. Possible Causes: This message box is displayed when the Object File Name field available in the Object Details section for the OSS subsystem is left blank. Action to be taken: Specify the name and location of the OSS logfile in the Object File Name field. The Object File Name field can accept any string of 64 characters and is case-sensitive. 2.
4-2-7-5 PROCESS Table 4-11 PROCESS Subsystem Sr.No. Error Message and Warning 1. Possible Causes: This message box is displayed when the Object File Name field available in the Object Details section for the PROCESS subsystem is left blank. The Object File Name field gets activated when the DYNAMIC or OBJECT is selected as the Object Type. Action to be taken: Specify the name in the Object File Name field. This field can accept any string of 8 characters. 2.
4-2-7-6 TCPIP Table 4-12 TCPIP Subsystem Sr.No. Error Message and Warning 1. Possible Causes: This message box is displayed when the Port field available in the Object Details section for the TCPIP subsystem is left blank. Action to be taken: Specify the port in the Port field. This field allows * wildcard character. For a specific port, enter PORT;IPADDR (Use a semicolon between Port and IP Address). 2.
4-2-8 Configuring Maintenance Information The Advanced Options dialog box is displayed by clicking on the Advanced button in the Threshold dialog box. The Maintenance tab page of the Advanced Options dialog box can be used to schedule maintenance and reconfigure the environment. Figure 4-15 OCC Advanced Options Dialog Box The error message displayed when configuring maintenance information, its cause and the action to be taken is described below. Table 4-13 Configuring Maintenance Information Sr.No.
4-2-9 Configuring Monitoring Schedule While creating a threshold configuration the schedule can be specified using the Schedule dialog box. You can access the Schedule dialog box using the Schedule button of the Threshold dialog box. Figure 4-16 OCC Schedule Dialog Box The error message displayed when configuring monitoring schedule, its cause and the action to be taken is described below. Table 4-14 Configuring Monitoring Schedule Sr.No. Error Message and Warning 1.
4-2-10 Using OCC Features OCC allows you to create, modify, or delete configurations and objects. You can also copy a configured threshold to other nodes. OCC displays the One or more operations failed message box in case of errors while using these features. Figure 4-17 One or More Operations Failed Message Box The different error messages displayed in the One or more operations failed message box, their causes and the actions to be taken are described in the following table.
Table 4-15 Using OCC Features Error Possible causes Action to be taken Lost connection with node The connection with the NonStop node is lost. Refer to the Connectivity Problems section to find the possible causes and actions to be taken when 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.
4-2-11 Copying the Configuration to Multiple Nodes Selecting the Copy to Node(s) option in the right-click menu of the Threshold pane allows you to copy the selected threshold to multiple nodes. Right-click on the selected threshold configuration in the Threshold pane to access this menu. The different error messages and warnings displayed when copying configurations, their causes and the actions to be taken are described in the following table. Table 4-16 Copying Configuration to Multiple Nodes Sr.No.
4-2-12 Listing Configurations and Objects After creating new thresholds, you can list the thresholds and the corresponding Objects in the Threshold and the Objects pane, respectively. The List Configuration option in the right-click menu of the Object Class pane allows you to list the created thresholds in the Threshold pane. The List Objects option in the right-click menu of the Threshold pane allows you to list all the corresponding objects for the selected threshold in the Objects pane.
4-2-14 Stop Monitoring on Node The Stop Monitoring option in the Object Class pane right-click menu can be used to stop monitoring for the selected node. This means that OCC will stop monitoring and issuing events for the objects in the Violation State and the database will not be modified. You can access this option by right-clicking on the Node icon in the Object Class pane.
Table 4-20 Connection Lost With Local Elink Sr.No Error Message or Warning 3.
4-2-16 NonStop Server Components Not Running In order to get the information from the NonStop Server and saving the information specified using the front-end, the OVNM NonStop Server components should be up and running. The different error messages and warnings displayed when the NonStop Server components are not running, their causes and the action to be taken are described in the following table. Table 4-21 NonStop Server Components Not Running Sr.No Error Message or Warning 1.
5 Console: Errors and Warnings 5-1 NonStop Events Not Seen in Console The following steps are intended to assist in diagnosing why NonStop events are not being populated in the Console. • Ensure that there is a connection established between the Nonstop Server(s) being monitored and Console running on the Management Workstation. The NonStop Node Indicators must be Green before messages can be received for a given NonStop Node • Generate Test Message, if the NonStop Node indicators are Green.
Figure 5-3 OVNM Host Response for Status of Agent Dialog Box Review the status output for errors. If an error has occurred and more information is needed, refer to the NonStop Server EMS event log for additional messages. HP OVNM EMS errors events are generated with “TANDEM.OVNM” SYSID. If you need to restart the NonStop Server components, use the Stop Agents/Start Agent button in the OVNM Host Management Client.
Elink Should be Up and Running The Elink status can be checked using the Console view Application Log window. Figure 5-5 : Console Application Log Window The status of Elink can also be verified using the NonStop Nodes Status window, which can be accessed using the Start/Programs/HP OVNM/NonStop Server Tools/NonStop Nodes Status option. You can also access the window by clicking on the Node Status option under OVNM Applications in the Console Management pane.
5-1-3 Check if a valid port is configured for Elink Elink for Console is configured using the Host tab page in the OVNM Host Installation Client’s New OVNM Configuration dialog box. Please make sure that a valid port value is provided in the OVNM Port field. The default value for Console is 5030.
5-2 Console Configuration Errors 5-2-1 Valid Values for Configuring Console Options The various Console options are configured using the Options dialog box, which can be accessed using the Options command on the Tools menu. Figure 5-8 Console Options Dialog Box Console: Errors and Warnings The Console’s Option dialog box has the following fields in the Misc area, which prompts you to enter the valid values.
5-2-1-1 List maximum number of events in memory to The maximum number of events in the memory is limited from 1 to 999999. The default value is 10000. In case you have entered an invalid value, the OVNM Console message box will be displayed giving you information about the valid values.
5-2-1-2 List maximum number of acknowledged events to The maximum number of acknowledged events in the memory is limited from 1 to 999999. The default value is 1000. In case you have entered an invalid value, the OVNM Console message box will be displayed giving you information about the valid values.
5-2-1-3 List number of combo box history strings saved to The number of combo box history strings to be saved is limited from 0 to 200. The default value is 30. In case you have entered an invalid value, the OVNM Console message box will be displayed giving you information about the valid values.
5-2-2 Querying Events The Query Events feature allows you to run queries for events based on the criteria specified. Figure 5-12 Query Events Dialog Box The different error messages and warnings displayed while running a query, their causes and the action to be taken is described in the following table. Table 5-1 Querying Events Sr.No Error Message or Warning 1.
Table 5-1 Querying Events Sr.No Error Message or Warning 2. Possible Causes: This message box is displayed when you enter a valid search string in the Collector combo-box and click on the Search button to retrieve all the collector files for an offline Node. 3. Possible Causes: This message box is displayed when you enter an invalid search string in the Collector combobox and click on the Search button to retrieve all the collectors/log files on the server.
Table 5-1 Querying Events Sr.No Error Message or Warning 7. Possible Causes: This message box is displayed when you do not select the log file from the Search Results list using the >> button and send a request to run the query. Action to be taken: Click on the log file in the Search Results list and select it using the >> button. Click on the Send Request button to send a request for running the query 8.
Table 5-1 Querying Events Sr.No Error Message or Warning 11. Possible Causes: This message box is displayed when you close an active window running a query. Action to be taken: Click on the Yes button if you want to close the window, else click on the No button.
5-2-3 Working with My Applications Console provides the facility to add a new application and edit or delete an existing application. The different error messages and warnings displayed while adding, editing or deleting an application, causes and the action to be taken is described in the following table. Table 5-2 Working with My Applications Sr.No Error Message or Warning 1. Possible Causes: This message box is displayed when the Name field in the Add Application dialog box is left blank.
5-2-4 Working with Web Links Depending on your business requirement and preference, Console allows you to add groups and web links, thus increasing the operator productivity. The different error messages and warnings displayed while adding, editing or deleting a web link or group, causes and the action to be taken is described in the following table. Table 5-3 Working with Web Links Sr.No Error Message or Warning 1.
Table 5-3 Working with Web Links Sr.No Error Message or Warning 5. Possible Causes: This message box is displayed when you try to edit a group with an active link. Action to be taken: Close the active link and then edit the group by right-clicking on the name of the group and selecting the Edit option. 6. Console: Errors and Warnings Possible Causes: This message box is displayed when you try to delete a group, which has an active link.
5-2-5 Opening Policies Selecting the Open option in the Policies menu displays the Select policy dialog box. The user can open an existing policy using this dialog box. Figure 5-13 Open Policies Dialog Box The error message displayed while opening policies, its cause and the action to be taken is described below. Table 5-4 Opening Policies Sr.No Error Message or Warning 1. Possible Causes: This message box is displayed when the policy to be opened is not selected in the Select Policy dialog box.
5-2-6 Acknowledging Policies Selecting the Acknowledge Selected Event(s) option in the Tools menu displays the Acknowledge event(s) dialog box. This option enables you to acknowledge the selected events. Figure 5-14 Acknowledge Events Dialog Box The error message displayed while acknowledging events, its cause and the action to be taken is described below. Table 5-5 Acknowledging Policies Sr.No Error Message or Warning 1.
5-2-8 Searching Events The Search bar is used to search events based on Node, SSID, Event#, Process, Manager and Event Text. The error message displayed while searching events, its cause and the action to be taken is described below. Table 5-7 Searching Events Sr.No Error Message or Warning 1. Possible Causes: This message box is displayed if you enter an invalid range or integer in the Event# box in the Search bar while searching events based on event number.
6-1 Specific Troubleshooting This troubleshooting section has been provided to assist in diagnosing OVNM integration problems with Enterprise Manager server. The figure illustrates the message flow from the HP NonStop Server to the Enterprise Manager Message Browser for both Windows and UNIX.
6-2 Messages not Getting Populated on HPOM Windows The following steps are intended to assist in diagnosing why NonStop messages are not flowing to the HP Operations Manager Windows Message Browser. 6-2-1 Check Connectivity between HPOM and NonStop Server To check the connectivity between the HP Operations Manager server and the NonStop server, execute the NonStop Nodes Status utility. Click on the Start\Programs\HP OVNM\NonStop Server Tools\NonStop Nodes Status option.
Verify that the OVNM NonStop Server components are up and running by obtaining status of OVNM components on the NonStop Server using the Host Management Client Status button. Verify that the OVNM Components (including the Collectors and Distributors) are up and running by scrolling through the Host Response log. Also, check the status of the EMON process.
If both Elink Ports 5020 and 5030 are red then the Elink session between the HP Operations Manager Server and the NonStop Host has failed. Stop and Start the OVNM Agents on the HP Operations Manager Server using the Start Agents and Stop Agents options in the Start\Programs\HP OVNM\Management Server Tools menu. Figure 6-6 Management Server Tools Menu Check for the HP OVNM SPI Service either by using the ‘net start’ command or from the Services window.
Once the Elink.cfg has been modified, run Elinktrace to start tracing. Generate a Test message using the Test Message button in the OVNM Host Management Client while Elink is being traced. If no message is traced, check the NonStop EMS Log $0. If Test message are in the EMS Log, then the problem is with the OVNM components on the NonStop Server. If message are seen in the Elink trace, but are still not seen on the HP Operations Manager Console, try tracing the OVNM Smart Plug-in process.
Option 3: NOCATCHUP OVNM provides the NOCATCHUP facility, which can be used in case the user is not willing to retrieve the events logged during any kind of connection outage. In this case, no catch up request will be sent for the particular node. Follow the steps below to configure the HP NonStop node in Nocatchup file. 1. Access the Nocatchup file available at “C:\Program Files\HP OpenView\bin” location. 2.
The following steps are intended to assist in diagnosing why NonStop messages are not flowing to the HP Operations Manager UNIX Message Browser. 6-3-1 Check Connectivity between HPOM and NonStop Server To check the connectivity between the HP Operations Manager server and the NonStop server, run the ovnm_status.sh script. # /opt/OV/ovnm/bin/ovnm_status.sh root502500018:33:42?0:01elink root609500018:33:42?0:03ovnm_spi Status of OVNM NonStop Servers SN Node(Ipaddress:Port) State. 1 \NODE(111.111.111.
The following steps will change the tracing level from ERROR, which is the default value (Logging all ERROR messages) to PROGRESS, (Trace all messages). • Turn the tracing off using the following command. #cd /opt/OV/ovnm/bin #./elinktrace –off • -cfg /opt/OV/ovnm/bin/elink.cfg Edit the Elink.cfg located in the /opt/OV/ovnm/bin directory and modify the SET ELINK TRACE parameter to PROGRESS. A part of the elink.
1. 2. Access the Nocatchup file available at “C:\Program Files\HP OpenView\bin” location. Add the HP NonStop node name for which NOCATCHUP facility is to be activated using the following syntax. NODE \NODE1 NODE \NODE2 NOTE: Node name should be same as specified in the elink.cfg file. 3. Restart the Agents OVNM also provides the OVNMMODE 311 feature. This feature provides the facility to receive the events in the 3.1.1 version format. Follow the steps below to configure the functionality. 4.
Appendix A Elink Messages Seen in HP Operations Manager This section provides a list of common Elink messages along with explanations. 1. Connection lost with remote Node This alert is generated by OVNM_SPI process. This implies the connection is lost with the specified HP NonStop node. It could be due to OVNM component on the NonStop is brought down or network outage between the front-end OVNM system and NonStop system.
Appendix B Internal Messages Generated by OVNM-SPI Enhancements have been made in the OVNM SPI to perform the following functions related to HP Operations Manager events generated by the OVNM SPI process. 1. Enabling/Disabling HP Operations Manager Messages Windows: You can use the following parameter in the OVNMCONF to enable or disable the HP Operations Manager messages generated by OVNM SPI process.
Table 8 Internal Messages Logged to HP Operations Manager by OVNM SPI Message Description OVNM: local Elink is not responding (hung state) Message logged when the local Elink goes into Hung state and is not responding. The severity of this message can be controlled by modifying the internalmsgseverity parameter in the OVNMCONF file.
Documentation Feedback Form We would appreciate your comments on the OVNM Troubleshooting Guide. 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. Guide 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.) 10.
