HP Insight Integration for Unicenter version 3.2

-----

Installing the integration:

Run setup.exe to install the integration.

-----

What's New:

1)  Updated to support version 7.40 of the HP Management Agents.

2)  Updated the overall status monitoring policy for Unicenter 3.x
    to minimize monitored items and changed all the state messages 
    to begin with "HP_".

3)  Added Message Records and Actions for events from HP OpenView
    Storage Area Manager (OVSAM).  These message records support
    OVSAM version 3.1 and above.

4)  Removed requirements for editing the integration classes with the
    browser path.  Menu options now launch the default browser configured
    on the Unicenter system.  This is done by using the following 
    executables in the Unicenter\bin directory.
      - hpim7.exe
      - hpim72.exe
      - hpqweb.exe
      - hpqriloe.exe

    Note: To launch Systems Insight Manager 5.0, remove hpim7.exe and
    hpim72.exe from the Unicenter\bin directory, then rename 
    hpsimlnh.exe and hpsimlnh2.exe and place those files in the
    Unicenter\bin directory.

5)  Discovery information from the hpqdscvr program is displayed and
    logged to the file hpqdscvr.log, located in the %CA_TND_HOME%
    directory. This file will be over-written each time the hpqdscvr 
    program is executed.

6)  Updated the Agent View to include the Windows OS MIB status and
    the Linux OS MIB status.  Also added the Insight Agent version
    string to the summary page.  Note: This string is only returned
    by version 7.10 agents and greater.  All other agents will return
    unknown.

7)  Added a software versions table entry to the Agent View.

8)  Added an upgrade option to the installer program. The upgrade option
    performs the following actions:
     - Runs the hpqrmv.exe program.  This program removes all existing 
       InsightManager agent objects and the InsightManager class so the 
       new policy files will be installed properly.  
     - Installs the message records and actions in the \cpqem\new32 
       directory.
     - Installs the message records in the \cpqem\updated32 directory.
       Since these are updated message records, the existing message 
       records and actions for these alarms will be removed before
       the updates are installed.

-----

Fixes Added:


Fixed an issue with the DSM policy files enumerating multiple 
array controllers in a system.  A system with multiple array
controllers would have the controller status reported incorrectly.

Fixed an issue with the Thermal Condidition in the DSM policy.
The policy was updated with an SNMP poll object.  The previous
evaluator was polling an old MIB OID.

Fixed an issue with the Correctable Memory condition in the DSM
policy.  The poller would not leave the unknown state.  The .dat
and .cnf files were update to correct this.

Fixed an issue with the hpqdscvr.exe program to correctly delete
the InsightManager object from systems classified as RemoteInsight
devices.

Fixed an issue with the overall status monitoring policy not
correctly monitoring the Windows_NetServer class.


-----

Using the new executables provided in this release, you 
may also configure buttons in the Enterprise Management 
console to launch to the Insight Agents or Remote Insight
Interface.

1. Select Options->Settings in the EM Console.  
2. Check the Auto checkbox for the desired button.
3. Check the Local checkbox for the desired button.
4. For the web agents, enter the Label "Insight Agents".
5. For the web agents, enter the Command "hpqweb &node".
6. For RILOE, enter the Label "Remote Insight".
7. For RILOE, enter the Command "hpqriloe &node".

An event from the server must be selected before 
clicking the "Insight Agents" button.

An event from the Remote Insight or Integrated Lights
Out must be selected before clicking the "Remote Insight"
button.

-----

Message Record Updates:

Message Records have been updated from '* SNMPTRAP: * * 232'
to '* SNMPTRAP: * * *232' to allow for the different display
settings for the Enterprise OID ("Enterprise OID displayed as"
in EM Settings under the Common Environment Settings tab).
Supported Values: NUMBER, OID, and STRING

If name is chosen as the display option, then the '*232' will
need to be replaced with 'Compaq' in the message records.

-----

Severity Propagation Notes:

In order to avoid severity propagation errors like the one below, 
HP_RemoteInsight devices are no longer monitored for the HP Management
Agents.  Only the host servers are monitored for the agents.

In order to achieve this, the hpqdscvr program deletes any InsightManager
objects that have the state "ANY:ABSENT" when it is executed.  Any devices
that are reclassified as HP_RemoteInsight objects will have their 
InsightManager objects deleted during this step.

This can result in other InsightManager objects with the status of
"ANY:ABSENT" being deleted.  In this case, the agents will be rediscoverd
by the DSM when they return to the UP state.


"CA-Unicenter TND Severity Propagation_0_E: <No Message Table> CA-Unicenter 
TND Severity Propagation Circular reference. Inclusion object ignored. 
Inclusion: ccd495bd-68f1-447b-aa75-e90266b8373f   
Parent: 8bd6702b-43c4-4e4d-9019-bcffee624362   
Child: 15a57601-5a94-4719-acee-03cdd39eade7"

-----

Remote Insight Inclusion Links Information:

Inclusion links for Remote Insight and Integrated Lights-Out products
are created in the database with the following properties in the 
tng_inclusion table.

parent_class:       Unispace
child_class:        HP_RemoteInsight
parent_sequence_no: 99
child_Sequence_no:  99

These entries are deleted when hpqdscvr.exe is executed in order
to prevent duplicate inclusion links from being created.

-----

Executable Summary:

Below is a summary of the various executable files provided with
the HP Insight Integration for Unicenter.  Information about which 
executables are used with the integration by default is also provided.

hpqweb.exe    - (default) used to launch the default browser to the web agents 
hpqriloe.exe  - (default) used to launch the default browser to the Remote  
                Insight/Integrated Lights-Out Interface 
hpim7.exe     - (default) used to perform an in-context launch of HP Insight 
                Manager 7 with the current node displayed 
hpim72.exe    - (default) used to launch to the homepage of HP Insight Manager 7
                or HP Systems Insight Manager
hpqemc.exe    - (default) used to launch to the web agents running on a node from
                the Enterprise Management Console.  The node name is 
                taken from the currently selected alarm.
hpqemc2.exe   - used to launch to the web agents running on a node from
                the Enterprise Management Console if the customer is using
                the DSM event policy.  The node name is taken from the 
                currently selected alarm.
hpsimlnh.exe  - used to perform an in-context launch of HP Systems 
                Insight Manager with the current node displayed     
hpsimlnh2.exe - used to perform an in-context launch of HP Systems Insight
                Manager with the current node selected from the Enterprise
                Management Console.  This is for use with the DSM event
                policy and allows the user to access event details in
                Systems Insight Manager by clicking on the Events tab.

hpqdscvr.exe       - used to reclassify objects from the default Unicenter
                     classes to HP specific classes
hpqunclass.exe     - used to reclassify objects from the HP specific classes
                     to the default Unicenter classes.  This is used when
                     the integration is un-installed.
migrateobjects.exe - used to migrate objects from the Compaq classes
                     defined in previous versions of the integration to
                     the new HP classes

-----

Message Records and Actions updates:

Minor updates have been made to some message records (see the \cpqem\updated32 
directory for details).

New message records have been added to support new HP alarms up to version 
7.40 of the HP Management Agents (see the \cpqem\new32 directory for details).


Installing the new HP message records:

Run the event installation script (LOADNEW.BAT) to install the new message 
records into the Unicenter database.

See the README.TXT file in the \cpqem\new32 directory for information
on the new alarms.

-----

Adding the HP Systems Insight Manager launch to other devices:

Users may want to add the in-context launch funtionality of Systems
Insight Manager to other devices, for example HPUnix systems.

In this example, the menu edited for the HPUnix class is the 
ManagedObject object menu.  This change will apply to all classes
that use this menu.

1. Right click on the device and select Edit Class.
2. Click the Menu tab.
3. Select the last entry in the menu list.
4. Click the Insert button.
5. Click the Method Name drop down and select the name of the 
   launch executable being used (either hpim7 or hpsimlnh).
6. The Command field should say hpim7.exe or hpsimlnh.exe,
   respectively.
7. The Parameter field should contain &address&.
8. Type HP Insight Manager in the Caption field.
9. Click Ok to close the edit class window.

-----

Troubleshooting:

-----

Reloading the classes after rebuilding the repository:

If you rebuild the Unicenter repository, the Insight Integration class
definitions will be lost and must be reloaded.

Change to the \cpqtnd\cpqwv\classes direcotory and run hpqclass.exe
to load the extended HP classes back into the repository.

Change the the \Unicenter\services\config\aws_wvgate directory
and run the command "awwvcfg -c insightmanager.wvc" to reload the 
Insight Agent definition into the repository.  Reset the DSM after 
this step.

-----

TRIX GIVES DR. WATSON                                   
                                                                         
TRIX generates a Dr. Watson when importing the HP specific classes
into a Unicenter 3.0 install.

For Unicenter 3.0, download and install patch QO39829.CAZ

ftp://ftp.ca.com/CAproducts/unicenter/CCS30/nt/0211/qo39829/QO39829.CAZ

-----

Discovery Command:

Since both the Remote Insight/Insight Lights-Out devices and the host systems
must be discovered by Unicenter for the device association to successfully 
occur, it is recommended that ping discovery be executed on the managed subnet.  

For example: dscvrbe -R REPOSITORY -J IP -D PINGSWEEP -M 172.25.161.*

-----

Discovery Problem:

If hpqdscvr.exe abends when running discovery, verify that the discovery
log file is not open.

-----

Discovery Menu Items not Installed:

The two Start Menu entries for the integration discovery programs are
only installed if the HP Class Extensions are installed from the 
selected system.

Both the discovery and un-classification programs can be run from
the command line instead of the Start Menu.

-----

GWCLASS.DAT with multiple entries:

If you install the integration multiple times, the gwclass.dat file
will have the string "HP_Host|HP_Workstation|" appended to the end
several times.  Edit the file to remove the extra occurrances of the
string.

-----

Discovered HP systems only show agents as Any:Absent:

The gwclass.dat file is edited during the installation to append 
"HP_Host|HP_Workstation|" to the end of the file.  If this edit is not
performed, systems in the HP* classes will not display discovred
agents.  Verify that this entry has been made in the gwclass.dat
file.

To make this addition to the file:

1. Change to the Unicenter\hpqtnd\classes directory.
2. Run the file hpgwedit.exe.
3. The output should be similar to the following:

C:\TND\hpqtnd\classes>hpgwedit

GWCLASS.DAT Current=Agent|Bridge|Host|Hub|Printers|Router|Switch|Workstation|ManagedPC|Xterm|OtherDe
vices|Unclassified_Class|Access_Point|UPS|

GWCLASS.DAT New=Agent|Bridge|Host|Hub|Printers|Router|Switch|Workstation|ManagedPC|Xterm|OtherDevice
s|Unclassified_Class|Access_Point|UPS|HP_Host|HP_Workstation|

File gwclass.dat successfully updated.

C:\TND\hpqtnd\classes>

Alternatively, you may edit the file and add the entry manually.

-----

Remote Insight Inclusion Links not created when using the R option:

When the discovery program runs with the R option, it only checks
the default Unicenter classes for Remote Insight Objects. Any 
objects in the HP classes will not be checked for Remote Insight
Objects.

To check systems in the HP classes for Remote Insight objects, run
hpqdscvr.exe with the S option.

-----

Remote Insight inclusion not created:

These conditions must be met before the inclusion link for the
Remote Insight/Integrated Lights-Out in a server will be created.

Both the server and the Remote Insight/Integrated Lights-Out must 
be discovered by Unicenter.  The Remote Insight object will remain
on the Unicenter segment map.

The Remote Insight/Integrated Lights-Out must be classified in the
HP_RemoteInsight class.

-----

Environment Variables not properly set:

The two environment variables used by the integration are placed
in the following location in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

If the IMAddress and CAI_MSG_EXIT environment variables do not get
set properly during the installation, they can be set manually.

1. Right-click on My Computer and select properties.
2. Click the Advanced Tab.
3. Click the Environment Variables button.
4. In the System Variables window, select CAI_MSG_EXIT and click 
   the edit button.
5. Enter hpqemc.exe in the Variable Value field and click ok.
6. In the System Variables window, select IMAddress and click 
   the edit button.
7. Enter the address of the Insight Manger server in the Variable
   Value field and click ok.
8. Click Ok twice to exit the windows.
9. Restart the system for the changes to take effect.

-----

New message records not used:

The integration kit was installed, but the new message records 
are not being utilized (most of the trap messages still say
Compaq).

The old message records are not removed by default when the new
message records are installed on a system.  Run the cpqem_remove
script from the previous version of the integration in order
to remove the old message records from the database.  

Existing message records are not automatically removed in order
to allow the user to preserve any customizations that may have 
been created.

If only the message records that new since the last version of 
the integration need to be installed, change to the cpqem\new3.1
directory and run the loadnew script.

-----

In-context launch to HP Systems Insight Manager fails:

When performing an in-context launch to Systems Insight Manager,
a web page stating "An error occured when generating the page"
is displayed.

Verify that you are using the correct launch program for Systems
Insight Manager.  The file hpsimlnh.exe should be used instead of
hpim7.exe.  If you are using Systems Insight Manager, you may
delete hpim7.exe from the Unicenter\bin directory, rename 
hpsimlnh.exe to hpim7.exe, and copy the renamed file to the
Unicenter\bin directory.

-----

Browser does not launch in-context to HP Insight Manager 7:

The installation is configured to launch in-context to HP Systems
Insight Manager by default.  The command for performing this type of 
launch to HP Insight Manager 7 is structured differently,
so a seperate executable was created for this purpose.

Replace the existing hpim7.exe file in the Unicenter\bin directory
with the hpim7.old file in the integration kit.  The hpim7.old file 
creates the command to launch to Insight Manager 7 in-context.

-----

At times, not all the HP ProLiant MIBs are loaded:

Sometimes not all of the HP MIBs are loaded into Unicenter.  MIBs that
are not loaded will not appear in the Unicenter MIB browser.

Make sure all the MIBs from the integration (\cpqwv\mibs) are 
copied to %CA_TND_HOME%\services\config\mibs directory and run 
CPQMIBS.BAT from the \cpqwv\mibs directory to reload the HP 
MIBs.


-----

Error when using mibbrowse.exe

The following error is generated when right-click and select Mib Browser 
from the pop-up menu: “could not access mib definition in Object Store.”

Run "agentctrl -m" to verify that the HP mibs are loaded.

<cpqApplianceMgmt>      is registered
<cpqCluster>    	is registered
<cpqClusteredRAID>      is registered
<cpqCmc>        	is registered
<cpqDriveArray> 	is registered
<cpqExternalMgmt>       is registered
<cpqFibreArray> 	is registered
<cpqHealth>    		is registered
<cpqHostOs>    		is registered
<cpqIde>        	is registered
<cpqRPM>        	is registered
<cpqRackInfo>   	is registered
<cpqScsi>       	is registered
<cpqSm2>        	is registered
<cpqSsStorageSys>       is registered
<cpqStdEquipment>       is registered
<cpqSystemInfo> 	is registered
<cpqThresholdMgmt>      is registered
<cpqUps>        	is registered
<cpqWinOsMgmt>  	is registered

If the HP MIBs are not registered, change to the integration\cpqwv\mibs
directory and run install_cpqmibs.bat.

-----

Parsing of HP alarms:

Some HP message records may not parse all of the information from the SNMP
traps correctly.  Reasons for this may vary, for example a varbind having a length
of 5 instead of an expected length of 4 would throw off the translation.

As a specific example, the following is the translation of a NIC status change trap.
The entries after 'Board Name' all contain VALUE because the board name was 6 words long
instead of the expected 5 words.

HP NIC: Redundancy Increased for adapter in slot 3, port 2. (SystemID: CPQ1669, NIC Status: 2, Board Name: Netelligent Dual 10/100TX PCI UTP, NIC Part: VALUE:, Address: VALUE:, OK Adapters: VALUE:) 

The trap is received and processed so you are alerted to the fault, but not all of the 
extended trap information (variable bindings) is processed.  All the information is 
available in the original SNMP trap.

-----

Removing all the HP specific menus:

Some of the HP specific menus will remain in the Unicenter repository after
the integration is removed.  Follow these steps to delete these entries.

1. Open a command prompt and run TRIX.
2. Select File-Open and browse to \cpqtnd\tools
3. Open the file DeleteCPQWVObj.txt
4. Select Actions - Import Repository.

This TRIX script has been updated to remove the menu items previously left in
the repository.

-----

HP Management Agents are not discovered:

Verify the correct SNMP community strings are configured for the 
InsightManager Agent Class in the DSM Wizard.

Verify the correct SNMP community strings are confitured for the 
InsightManager Agent Class in the Pollset Browser.

Note: Both of these settings default to "public".

-----

Installer created using Inno Setup: 

   Copyright (C) 1997-2004 Jordan Russell. All rights reserved.
   http://www.jrsoftware.org/ 

-----
