README for HP Systems Insight Manager 4.2 with Update 2 - Linux README for HP Systems Insight Manager 4.2 with SP2 - Windows README for HP Systems Insight Manager 4.2 with Update 1 - HP-UX Copyright (c) 2003-2005 Hewlett-Packard Development Company, L.P Part Number: 359314-006 _________________________________________ CONTENTS: PRODUCT RELEASE INFORMATION for UPDATES to HP SIM 4.2 1. HP SIM 4.2 with Update 2 - Linux 2. HP SIM 4.2 with SP2 - Windows 3. HP SIM 4.2 with Update 1 - HP-UX KNOWN ISSUES: 1. General BROWSER ISSUES CERTIFICATE ISSUES CLUSTER ISSUE CONFIGURE OR REPAIR AGENT TASK ISSUE CONTAINER VIEW ISSUES DISCOVERY ISSUES EVENT ISSUES HP SERVICEGUARD MANAGER ISSUES HP SYSTEMS INSIGHT MANAGER ISSUES IDENTIFICATION ISSUES INSTALLATION ISSUES JAVA ISSUES LICENSE MANAGER ISSUE LINUX SYSTEM ISSUES LIST ISSUES LOGIN ISSUES MIB ISSUE PARTITION MANAGER ISSUES PERFORMANCE MANAGEMENT PACK ISSUES PRINTING ISSUES REPORTING ISSUES SEARCH ISSUE SECURITY ISSUE SNMP ISSUE SOFTWARE/FIRMWARE ISSUES SQL ISSUE SSH ISSUES TASK ISSUES TOOL ISSUES TRAP ISSUE UPGRADE ISSUE VPM ISSUE WMI ISSUE 2. Migration from Insight Manager 7 MIGRATION ISSUES AUTHORIZATIONS ISSUE CERTIFICATE ISSUE DISCOVERY ISSUE HOSTS FILE ISSUE JAVA ISSUES LIST ISSUES SOFTWARE/FIRMWARE ISSUE TASK ISSUES _________________________________________ PRODUCT RELEASE INFORMATION for UPDATES to HP SIM 4.2 1. HP SIM 4.2 with Update 2 - Linux This release provides a full installation of HP SIM 4.2 - Linux including all updates through Update 2. It provides a full in-place upgrade from HP SIM 4.0, 4.0 with Update 1, 4.1, or 4.1 with Update 1. Users wishing to upgrade existing Linux installations of HP SIM 4.2 or 4.2 with Update 1 should utilize the update install available on the HP SIM - Linux download page. The following fixes are included in this release: - Replaced the 7.3 postgreSQL JDBC driver with the 7.4 version. This is required for the gWLM product to work with HP SIM. - Fixed problems with HP BladeSystem blade/enclosure/rack associations. In some cases extra racks were appearing based on the correct rack name but with portions of the serial number appended (for example, "ENCL--EA-JK-LJ--".) Most of the enclosures and blades would be associated with the improperly named rack. There was also the potential to have racks named "unknown". Note that after this patch, any unknown or incorrect enclosures and racks can be deleted. - Fixed problem with email or pager messages sometimes being sent for old events while an Automatic Discovery was running. Note, this applies to any automatic event handling task that used system type as one of the filters. - Fixed problems with device-specific WBEM credentials not being used if they were provided. - Fixed problem with ignoring the "Use global defaults" setting under "Ping (ICMP) Settings" on the "System Protocol Settings" page. - Fixed problem with device showing same IP address multiple times. - Fixed a problem with importing a certificate into HP System Insight Manager that specified the Domain Component field in the subject field of the certificate response. - Fixed problem with scaling of "File System Size" and "File System in Use" to scale with 1024*1024 instead of 1000*1000 to show megabytes. - Modified the "Tools/System Management Homepage" menu item to qualify on presence of the System Management Homepage on the target system, rather than on the operating system of the target system. - Modified the mxnodesecurity executable to disable display of credentials used by "Configure or Repair Agent Settings". - Fixed a SOAP call used for internal application integration. This fix is required to properly support Rapid Deployment Pack version 2.0. - Fixed a problem with the status of "My Favorites" folders not always reflecting the proper status when multiple users were monitoring the same folders. - Updated postgreSQL JDBC driver on Linux to version 7.4.1. HP-UX was already using this driver. _____________________________________________ 2. HP SIM 4.2 with SP2 - Windows This release provides a full installation of HP SIM 4.2 - Windows including all service packs through service pack 2. It provides a full in-place upgrade from HP SIM 4.0, 4.0 with SP1, 4.1, or 4.1 with SP1. Users wishing to upgrade existing Windows installations of HP SIM 4.2 or 4.2 with SP1 should utilize the update install available on the HP SIM - Windows download page. The following fixes are included in this release: - Addressed problem of ProLiant Essentials products and HP Systems Insight Manager tools not working if SSH (Secure Shell) is not configured properly on the central management server (CMS). In some cases, it was difficult to get SSH properly configured on the CMS for all accounts that needed to use SSH. A mechanism has been added for the CMS to run local tools even if SSH is not configured properly. By default, this new mechanism is used for all tools that use SSH locally on the CMS to target the CMS and that execute with the "Administrator" account. Other accounts can also be added by adding the account name to the "mx_dtf_ssh_ bypass_user" property in \config\globalsettings.props. Account names should be separated by a comma, with no spaces. Domain accounts require two backslashes between the domain name and the user name, such as "domain\\user". This feature can be disabled entirely by setting "mx_dtf_enable_ssh_ bypass=false" in the same properties file. The following ProLiant Essentials and tools can take advantage of this: - HP ProLiant Essentials Vulnerability and Patch Management Pack - HP ProLiant Essentials Virtual Machine Management Pack - Install OpenSSH - Initial ProLiant Support Pack Install - Configure or Repair Agents - Custom Commands, if the login user is added to the property. Further information on SSH is available in the white paper 'SSH in HP Systems Insight Manager' available from the HP website. - Enhanced the OpenSSH installer to work with domain users on Windows 2003. Also enhanced to correct user home directory references for SSH. The OpenSSH service runs with service credentials on all versions of Windows now, instead of just on Windows 2003. - Fixed a problem with folder status if the 1.5 Java Plug-in is in use. - Fixed a problem with email or pager messages sometimes being sent for old events. _____________________________________________ 3. HP SIM 4.2 with Update 1 - HP-UX This release provides a full installation of HP SIM 4.2 - HP-UX including Update 1. It provides a full in-place upgrade from HP SIM 4.0, 4.0 with Update 1, 4.1, or 4.1 with Update 1. This is the same version of HP SIM which is included with the 0505AR/OE build of HP-UX 11i v2 and 11i v2 update 2. Users wishing to upgrade existing HP-UX installations of HP SIM 4.2 should utilize the update install available on the HP SIM - HP-UX download page. The following fixes to HP SIM 4.2 are included in this release: - Fixed problems with HP BladeSystem blade/enclosure/rack associations. In some cases extra racks were appearing based on the correct rack name but with portions of the serial number appended (for example, "ENCL--EA-JK-LJ--".) Most of the enclosures and blades would be associated with the improperly named rack. There was also the potential to have racks named "unknown". Note that after this patch, any unknown or incorrect enclosures and racks can be deleted. - Fixed problem with email or pager messages sometimes being sent for old events while an Automatic Discovery was running. Note, this applies to any automatic event handling task that used system type as one of the filters. - Fixed problems with device-specific WBEM credentials not being used if they were provided. - Fixed problem with ignoring the "Use global defaults" setting under "Ping (ICMP) Settings" on the "System Protocol Settings" page. - Fixed problem with device showing same IP address multiple times. - Fixed a problem with importing a certificate into HP System Insight Manager that specified the Domain Component field in the subject field of the certificate response. - Fixed problem with scaling of "File System Size" and "File System in Use" to scale with 1024*1024 instead of 1000*1000 to show megabytes. - Modified the "Tools/System Management Homepage" menu item to qualify on presence of the System Management Homepage on the target system, rather than on the operating system of the target system. - Modified the mxnodesecurity executable to disable display of credentials used by "Configure or Repair Agent Settings". - Fixed a problem with the status of "My Favorites" folders not always reflecting the proper status when multiple users were monitoring the same folders. _________________________________________ KNOWN ISSUES -------------------------------------------------------------------------------- 1. General Issues -------------------------------------------------------------------------------- BROWSER ISSUES When browsing to HP Systems Insight Manager using Microsoft Internet Explorer 6.0.3790.0 on Windows 2003, the billboard in lower corner of the Home page will be blank. To correct this issue, enable Play Animations in Web Pages in Internet Explorer. To access this, select Tools>Internet Options>Advanced, and select Play Animations in Web Pages under the multimedia section. -------------------------------------------------------------------------------- When browsing into a Red Hat Linux CMS from a Windows Internet Explorer client, the applets might be extremely slow in loading. The applet might timeout or the screen might appear to hang with the Loading message displayed. Updating to the 1.4.2_05 or newer JRE resolves this issue. -------------------------------------------------------------------------------- If you receive a Page Not Found browser error when launching Performance Management Pack (PMP) tools from within HP Systems Insight Manager, the CMS name link might not have resolved correctly on the network. Make note of the name being used in the browser window and ensure that the name resolves on the network and that it is not being affected by any proxy settings in the browser. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- CENTRAL MANAGEMENT SERVER ISSUES When you cannot access HP Systems Insight Manager on a Windows system using a full DNS hostname, your Windows DNS configuration is not set properly. There are several reasons for this: - The TCP/IP Settings for your Network Connection are not configured properly. HP recommends the following workaround: 1. On the CMS, open the Control Panel, and select Network Connections>Local Area Connection Settings> Properties>Internet Protocol (TCP/IP)>Properties> Advanced. 2. Select the DNS tab. 3. Be sure that DNS suffix for this connection contains the full DNS suffix for the system. 4. Be sure both the Register this connection's address in DNS and the Use this connection's DNS suffix in DNS registration checkboxes are selected. - The System name for the CMS is not configured properly. HP recommends the following workaround: 1. On the CMS, open Control Panel>System. 2. Click Network Identification. 3. Click Properties or Change next to the rename this computer or join a domain field. 4. On the pop-up dialog click More. 5. Be sure the primary DNS suffix is set correctly. If not, set it, and click OK until all dialog boxes are closed. - The proxy settings on the client browser is configured to proxy local systems. HP recommends the following workaround: 1. In Internet Explorer, select Tools>Internet Options> Connections>LAN Settings>Advanced. 2. Add the DNS suffix for the CMS to the Exceptions list. - It is possible that the company DNS servers are having problems. HP recommends that you contact your company's network support group. -------------------------------------------------------------------------------- Use careful planning if you want to deploy new drivers, firmware agents, or other software to the local CMS since you might receive unexpected results, such as a mandatory reboot of the CMS. -------------------------------------------------------------------------------- Installing the CMS on Windows uses the user desktop locale to determine the CMS local. For example, if you install the CMS on a German Windows system and the user desktop locale happens to be English, then the CMS installed becomes an English CMS, which is incorrect. The language of mxlog.txt (a log file) currently depends on the CMS locale. If the installer user desktop locale is German, mxlog.txt is logged in German, even though the CMS is installed on an English Windows system and browser locale is also English. This happens because the Log On As property of the HP Systems Insight Manager service is configured as the install user name, instead of Local System, which specifies system environment. Running the service with the credentials of the user that installed the application is necessary for the service to have the necessary credentials for database access, and other CMS settings. If you run into this problem and you would like the logs to be in a different language (German or English), then you have three options: - Stop HP Systems Insight Manager service. Change the default locale of the user account specified in the Log On As property of the HP Systems Insight Manager service (the user that performed the install) to the desired language and restart the service. - Stop HP Systems Insight Manager service. Change the Log On As user for the HP Systems Insight Manager service to the local administrator account, and be sure its locale is set to the desired language. Restart the service. - If you do not want to change the default locale of either of the previous accounts to the desired language for the logs, then create a new administrator-level account with the desired default locale. Then uninstall HP Systems Insight Manager and reinstall HP Systems Insight Manager specifying the new administrator-level account. -------------------------------------------------------------------------------- On a Windows NT 4.0 system running Internet Explorer 6 Service Pack 1, remotely browsing into a CMS causes a DLL failure after being connected for hours. This occurs on a Windows CMS, as well as an HP-UX CMS. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- CERTIFICATE ISSUES If HP Systems Insight Manager is installed on a server with IPv6 enabled, the server certificate might use the IP address as the name in the certificate instead of the system name. To solve this issue create a new certificate: 1. Log into HP Systems Insight Manager. 2. Go to the Server Certificate page, select Options> Security>Certificate>Server Certificate. 3. Click New, and specify the name of the server in the Common Name (CN) field. 4. Click OK to create the server certificate. 5. Restart HP Systems Insight Manager for the new certificate to take effect. -------------------------------------------------------------------------------- When importing a trusted certificate into HP Systems Insight Manager through the Options>Security>Certificates>Trusted Certificates menu item using Mozilla 1.6 and you select an invalid file to import, you receive an HTTP 500 error a few minutes after clicking OK. This error overwrites the Import Trusted System Certificate workspace in the browser window. If you click the Import button again, the correct information returns to the workspace. This is an issue with JRE 1.4.2. Updating to a newer JRE, such as JRE 1.4.2_05 resolves the problem. -------------------------------------------------------------------------------- By default, the version of Internet Explorer 6 that is packaged with Windows Server 2003 prompts you to specify if you would like to add new Web servers to your list of trusted sites. If you disable this option, you must manually configure trusted sites. If you allow the wizard to build the list of trusted sites, then HP Systems Insight Manager does not encounter the issue. However, if you select to manually add the entries for accessing an HP Systems Insight Manager server, you must understand how a Windows system with Internet Explorer installed manages systems and access rights. To allow HP Systems Insight Manager to redirect from port 280 to 50000, two trusted entries are required: one over HTTP, and the other over HTTPS. For a Windows system with Internet Explorer installed to identify trusted sites, it uses a primitive method of string-comparing hostnames. If you add the IP address of your site to the trusted list but then use a hostname in the URL, the site will not be recognized. Likewise, if you add the DNS name of your site to the trusted list but then use a different WINS name in the URL, the site will not be recognized. You must use the following combination: The trusted sites you specify must exactly match the hostname in the URL that is used to log in to the HP Systems Insight Manager server. ------------------------------------------------------------------------------- The HP Systems Insight Manager server certificate and the Management HTTP Server certificate are synchronized during installation. However you must reboot the server after the installation of HP Systems Insight Manager for it to take affect. Until that is complete, multiple certificate warning messages might occur when browsing into HP Systems Insight Manager and when managing the server agents for the server where HP Systems Insight Manager is installed. ------------------------------------------------------------------------------- When creating a new certificate, you cannot use non-ASCII characters in the certificate name. If you do, an error message is displaying stating "Error - invalid parameter". ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- CLUSTER ISSUE You might be unable to change invalid polling values entered under Options> Cluster Monitor>Cluster Resource Settings when running the United Linux operating system. To resolve, reload the page by selecting All (MSCS) from the Cluster dropdown list and MSCS from the Resource dropdown list and enter a valid polling rate. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- CONFIGURE OR REPAIR AGENT TASK ISSUE When configuring a Configure or Repair Agents task, limit the number of target servers to 100 or less so that the internally created Windows command will not exceed the maximum Windows command line length. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- CONTAINER VIEW ISSUES If an HP ProLiant BL30p blade server is physically removed from its enclosure and another blade server is inserted in its place, you should manually delete the BL30p device from HP Systems Insight Manager. Otherwise the Rack/Enclosure diagram might be displayed incorrectly. -------------------------------------------------------------------------------- The picture view of a rack that is empty and no longer contains any enclosures might display as a gray box with no information. You can safely delete the rack device in this case. -------------------------------------------------------------------------------- If the table view of a rack appears empty but the picture view has a rack diagram, re-run discovery. This can happen if you unplug then plug back in the power supply. -------------------------------------------------------------------------------- If HP ProLiant BL e-Class blade servers or the HP bc1000 blade PC picture view is empty but the table view displays all blades correctly, run identification on the Integrated Administrator management processor. This happens when the Integrated Administrator is discovered before blades are discovered. 1. Select Options>Discovery>Identify Systems. 2. Select the ProLiant BL e-Class Integrated Administrator. 3. Click Run Now. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- DISCOVERY ISSUES When a Linux server is discovered as an unmanaged system: 1. Be sure to make the changes similar to the following in the /etc/hosts file on the discovered system before installing agents: #Do not remove the following line, or various programs #that require network functionality will fail. 127.0.0.1 localhost 172.24.30.34 HPSIM HPSIM.wbemqa.com HPSIM NOTE: Replace the IP address, hostname, and alias previously listed with your localhost IP address, DNS name and hostname. 2. Install agents. 3. Verify that that the following lines are entered in the /etc/snmp/snmpd.conf file. If not, stop the SNMP service, enter them manually, and restart the SNMP service. rwcommunity private rocommunity public NOTE: The community strings used should match those community strings on the CMS. After completing these steps, the system will be discovered properly. -------------------------------------------------------------------------------- To discover detailed information for Linux running on ProLiant systems, you can: - Install the Linux ProLiant agents on the system. To install the latest Linux ProLiant agents, go to: http://h18023.www1.hp.com/support/files/server/us/WebDoc/700/ psp-users-guide.pdf. or - Update the snmpd.conf file. If you choose this option and do not update the snmpd.conf file, LINUX appears in the OS Name column on the system lists page, instead of the true operating system name, such as Red Hat Advanced Server. To solve this issue: 1. Stop the SNMP service. 2. Add the following line to the /etc/snmp/snmpd.conf file: rocommunity public 3. Restart SNMP. -------------------------------------------------------------------------------- If you use a Hosts file to manually discover a system, you must verify the protocol settings for the system. To do so, click All Systems in the System Lists region then click the system's name to access the System Page for the newly discovered system. Select Links>System protocol settings. -------------------------------------------------------------------------------- When HP Systems Insight Manager is installed on an HP ProLiant server, the GUID value of the CMS is not collected during initialization. This can be fixed by manually running discovery on the CMS by entering the IP address of the CMS in the IP address ranges field on the Automatic Discovery - General Settings page and clicking Save and Run. -------------------------------------------------------------------------------- HP Systems Insight Manager supports hostnames that conform to Internet standards (such as those identified in DNS RFC1034). Allowed hostnames are those that contain less than 64 characters and contain only letters, digits, and hyphens. Other characters, such as underscores, spaces, and symbols are not supported and might have unexpected results. -------------------------------------------------------------------------------- If you have systems with special characters in the name, the special characters are replaced by dashes (-). For example, if you name an enclosure Encl/2 HP Systems Insight Manager displays this enclosure as Encl--. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- EVENT ISSUES If you try to subscribe for WBEM events from either the command line (mxwbemsub) or the GUI (Options->Events->Subscribe to WBEM Events) and receive the error message "String index out of range", check to see if the name of the local host resolves to a fully qualified name via DNS. The command needs the fully qualified DNS name. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- HP SERVICEGUARD MANAGER ISSUES HP Serviceguard Manager is not supported on Windows Server 2003. -------------------------------------------------------------------------------- When you uninstall HP Serviceguard Manager after it has been integrated with HP Systems Insight Manager, you receive an HTTP 404 error. This is because the Serviceguard Manager uninstall application deletes the directory "sgmgr" under the webapps directory which is located: on HP-UX and Linux: /opt/hpwebadmin/webapps on Windows: \ProgramFiles\HP\Systems Insight Manager\hpwebadmin\webapps To avoid the HTTP 404 error in the future, you must remove the tool from HP Systems Insight Manager using the following command from the path /var/opt/mx/tools on Linux or HP-UX: mxtool -r -f sgmw-web-tools.xml If Serviceguard Manager is reinstalled in the future, you must re-add the tool to HP Systems Insight Manager using the following command from the path /var/opt/mx/tools on Linux or HP-UX and \ProgramFiles\HP\Systems Insight Manager\tools on Windows: mxtool -a -f sgmw-web-tools.xml NOTE: If there is a task that utilizes the SGMgr tool, if the tool is removed and then re-added, the tasks might no longer work since the GUID has changed byre-adding the tool. These tasks must be deleted, then re-added. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- HP SYSTEMS INSIGHT MANAGER ISSUE HP Systems Insight Manager is not compatible with version 2.0.1 of the Pegasus WMI Mapper. HP Systems Insight Manager 4.2 ships with version 2.0 of the Pegasus WMI Mapper and customers are recommended to use this version with HP Systems Insight Manager. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- IDENTIFICATION ISSUES After upgrading from HP Systems Insight Manager 4.0 or 4.1 to HP Systems Insight Manager 4.2, the Product ID field on the System Page for upgraded systems, is blank. You must re-run Identification and Data Collection to collect this information. -------------------------------------------------------------------------------- To discover and properly identify SNMP based HP NAS systems, you must add the cpqPublic community string on the Global Protocol Settings page. To access the Global Protocol Settings page, select Options>Protocol Settings>Global Protocol Settings. -------------------------------------------------------------------------------- Depending upon the information provider, inconsistent operating system version information is returned. For instance, Microsoft's WMI always returns the operating system type for all of Windows NT, Windows 2000, Windows XP, and Windows 2003 as Windows NT, even though code values for the other variants are defined. In addition, data from the SNMP providers is also inconsistent for some Windows versions. For example, Windows XP systems are displayed on the Windows NT system list page. Also, the System Page>Identity tab for a Windows XP system displays both Windows XP and Windows NT in the Software description field. -------------------------------------------------------------------------------- Serviceguard Clusters are only identified on HP-UX systems. They are not identified on Linux or Windows. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- INSTALLATION ISSUES The OpenSSH service will run as the user who installs HP SIM. This user account must be an administrative account and have specific user rights to allow OpenSSH to run correctly. The following user rights are required, and will be automatically added to this account by the OpenSSH installer if needed: - Log on as a service - Create a token object - Replace a process level token These may be controlled by the ‘Local Security Policy’ administrative tool. A domain policy may control these settings, in which case these settings may need to set for a domain user. ------------------------------------------------------------------------------ On a Windows 2003 system, when setup.exe is initially run, the following error message is displayed An error occurred in the script on this page Line: 167 Char: 9 Error: Permission denied Code: 0 URL: ....setup.exe/default.htm. Click Yes to clear the message and use the Windows Task Manager to stop setup.exe from running. Restart setup.exe and it will work as expected. This happens if you run setup.exe over a mapped drive. If you run setup.exe from the CD or a local drive, you will not receive this error. -------------------------------------------------------------------------------- On a Windows 2003 system running Internet Explorer 6.0, Service Pack 1 and SQL 2000, Service Pack 3, when setup.exe is initially run, nothing is displayed. Use the Windows Task Manager to stop setup.exe. Restart setup.exe and it will work as expected. This happens if you run setup.exe over a mapped drive. If you run setup.exe from the CD or a local drive, you will not receive this error. -------------------------------------------------------------------------------- When running a custom install of HP Systems Insight Manager on a Windows system, and installing OpenSSH, you might receive an application error on mkpasswd.exe. The workaround for this error is: 1. From the CLI, enter cd \etc. 2. Enter mkpasswd -l -u administrator >> passwd. -------------------------------------------------------------------------------- If, after installing MSDE, you see one or more dialog boxes requesting a reboot you must answer yes to insure successful installation of HP Systems Insight Manager. -------------------------------------------------------------------------------- The Windows installer verifies if Internet Explorer 6.0 or later is present and if not, it aborts the installation. If Internet Explorer 5.x or earlier is installed, it must be upgraded to Internet Explorer 6.0 or later for the HP Systems Insight Manager install to complete successfully. -------------------------------------------------------------------------------- The domain user needs to be a part of the local administrators group (or domain admin) to run custom commands. On Windows 2003, if after adding a domain user account to HP Systems Insight Manager, custom commands do not execute for that user: 1. Add the domain user information to the group and password files by running the following commands: - mkpasswd -d -u >> ..\etc\passwd - mkgroup -d >>..\etc\group 2. Deploy the SSH keys with the following command: - mxagentconfig -a -n -u -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- JAVA ISSUES If you receive an error stating that a suitable Java Plug-In was not detected on your system, you will not be able to log in until the appropriate Java Plug-In (Java Virtual Machine) is detected. The following areas might be preventing HP Systems Insight Manager from detecting your Java Plug-In: - SOCKS server settings - Proxy server settings - Firewall configuration - Java CLASSPATH Also, a conflict might exist if multiple Java Plug-Ins are installed, in which case, uninstall the conflicting Java Plug-Ins and then re-install the Java Plug-In that is required by HP Systems Insight Manager. Refer to the HP Systems Insight Manager Installation and User Guide for the appropriate Java Plug-In version for your system. -------------------------------------------------------------------------------- If you require multiple Java Plug-Ins to be installed on your system, ensure that none of them are set to run by default. This is configured in the control panel applet for the plug-in. -------------------------------------------------------------------------------- If you require multiple Java Plug-Ins to be installed, install them in the order they were released by Sun. You should uninstall a later version before installing an earlier version. -------------------------------------------------------------------------------- With SUSE 9, to add the JRE plugin to Mozilla 1.6, after the plugin has been downloaded, complete the following: 1. Change to the Mozilla bin directory by typing: cd /opt/mozilla/bin 2. Execute the following script, which locates and adds the plugin: ./plugins.sh -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- LICENSE MANAGER ISSUE When using License Manager with Performance Management Pack (PMP) tools, it is important to note that PMP maintains its licensing information on the HP Systems Insight Manager host it is co-resident with. Consequently, when deploying or collecting keys using License Manager, the target system should always be the HP Systems Insight Manager host machine for PMP. Details on which targets are actually licensed by PMP is only available using PMP itself. License Manager provides information on the various keys in use on their actual usage. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- LINUX SYSTEM ISSUES Linux operating systems must have the Java Virtual Machine (JVM) installed before browsing to HP Systems Insight Manager. If you do not have JVM installed, the pages do not display correctly. -------------------------------------------------------------------------------- If, as an administrator, you browse into a Linux CMS where the HP Insight Management Agents are installed, and a Security Alert dialog box is displayed when you click a Management Agent, then the Management HTTP Server certificate has not been overwritten with the HP Systems Insight Manager certificate. This is because OpenSSL is not configured correctly. On Linux, OpenSSL should be installed to the /usr/bin/ directory. In HP-UX, OpenSSL should be installed in the /opt/apache/ssl/bin/ directory. Install OpenSSL to the correct directory, then create a new HP Systems Insight Manager certificate to resolve this issue. -------------------------------------------------------------------------------- HP Systems Insight Manager running on a Linux system might not receive HTTP Events from the Version Control Agent performing an Install Software and Firmware task. Therefore, the task status remains at 0% for an extended period and shows In Progress on the Task Results page. Set up the Hosts file on the target device running the Version Control Agent to include the name and IP address of the Linux CMS system. Edit the \System32\Drivers\Etc\HOSTS file by adding the following lines: For example: hpsim01 192.168.1.1 -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- LIST ISSUES To have the CMS listed in the All Systems list when logged in as a user with full configuration rights, give the automatically generated administrator user two authorizations, one for All Tools and All Managed Systems and another for All Tools and CMS. The All Managed Systems authorization does NOT include the CMS. -------------------------------------------------------------------------------- When editing lists with very large criteria items selected (Device by Name, Event by Type), the browser will be unresponsive until the criteria list is built. -------------------------------------------------------------------------------- If the system or event list shows as all white in the browser on Windows, this is caused by a known bug in the Java Plug-in. This is sometimes seen when logging out and back in within the same browser or leaving a session logged in overnight. There is a work around for this problem. 1. Open the Control Panel on the client machine this is seen on. 2. Double click the Java Plugin or Java Plugin 1.4.1_* Control Panel applet. 3. Select the Advanced tab, and in the Java Runtime Parameters field enter the following: -Dsun.java2d.noddraw=true 4. Click Apply and close both the browser and the Control Panel applet. 5. Restart the browser and the problem should not occur again. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- LOGIN ISSUES In specific instances, after entering your login credentials, you might be unable to log in to HP Systems Insight Manager or to log in to managed systems when browsing from HP Systems Insight Manager using Internet Explorer 6.0. Reason 1: Some versions of Internet Explorer have a problem with underscores in the system name, preventing the session cookie from working properly. This problem applies to Internet Explorer versions 5.5 and 6.0 that have applied Internet Explorer patch Q313675 or any patch that supersedes or includes that patch, such as Q316059 and Q319182. Solution 1A: If your HP Systems Insight Manager server has an underscore in the name, use the IP address of the HP Systems Insight Manager server instead of the name in the Internet Explorer address field. Solution 1B: For managed systems, if the names of the systems have an underscore, use the IP address of the system. You can configure HP Systems Insight Manager to create links to the system using the IP address instead of the name by following these steps: 1. Browse and log into HP Systems Insight Manager. 2. Select Options>Security>System Links Configuration. The System Links Configuration page is displayed. 3. Select Use System IP Address. 4. Click Apply. NOTE: By using IP addresses instead of names, you might encounter Security Alerts if the name in the managed system certificate does not match the name in the link. The default certificate for managed systems uses the system name, not the IP address. NOTE: Using HP Systems Insight Manager with systems that have an underscore in the name might have unexpected results. -------------------------------------------------------------------------------- If you receive the Warning HTTPS Hostname Mismatch when accessing HP Systems Insight Manager and you click No, you will continue to receive the error until you click Yes. You will then be taken to the login page. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- MIB ISSUE Do not rename, move, or delete MIB files from the MIBs directory after they are registered. For a MIB file to be listed as registered, the MIB file must reside in the MIBs directory. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- PARTITION MANAGER ISSUE On an HP-UX 11.23 system when HP Systems Insight Manager is installed and Partition Manager (ParMgr) is currently installed or going to be installed, there are minor incompatibilities that exist. This is only seen if ParMgr is installed after HP Systems Insight Manager is installed. Run the following mxtool commands to work around this issue. /opt/mx/bin/mxtool -r -f /var/opt/mx/tools/parmgr-web-tools.xml /opt/mx/bin/mxtool -a -f /var/opt/mx/tools/parmgr-web-tools.xml -------------------------------------------------------------------------------- After installing HP Systems Insight Manager on HP-UX 11.23 the command /opt/parmgr/bin/parmgr command might fail to start Partition Manager with the error message: ERROR: The command to start the server succeeded, but the server is not listening on port 50000. Command: /sbin/init.d/mxtomcat start If this occurs, verify that the server is running with the command: /usr/bin/netstat -an | grep 50000 | grep LISTEN If the server is not running, no output will occur. If the server is running you will see output similar to the following: tcp 0 0 *,50000 *,* LISTEN If the server is running you can start Partition Manager from a Web browser such as Mozilla or Internet Explorer by entering the following URL into the browser: https://hostname:50000/parmgr/ where hostname is the hostname of the machine on which the previous server is running. This problem has been fixed in the latest release of Partition Manager which will ship on the next release of HP-UX. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- PERFORMANCE MANAGEMENT PACK ISSUES If Performance Management Pack (PMP) data was successfully exported, and if the PMP data Import is not automatically launched, then the importing of this data must be launched manually, by running pmpshell.exe from the pmp directory. -------------------------------------------------------------------------------- After a PMP installation, the PMP menu options might not appear on the HP Systems Insight Manager console. Manually add the PMP menu options by performing one of the following: - From the command line, enter: mxtool -a -f ": \Performance Management Pack 3\ToolsMenu\PMPTools.xml" - Copy PMPTools.xml from :\Performance Management Pack 3\ToolsMenu to :\System Insight Manager\Setup Then, restart HP System Insight Manager Service. -------------------------------------------------------------------------------- A user created with the user template or operator template might not be able to see menus related to PMP, or might be required to log in (single sign-on does not work) after accessing the menus. Perform the following to give the user-template-based user authorization on the CMS: 1. Login as an administrator to HP Systems Insight Manager. 2. Select Options>Security>Users and Authorizations, and select the Authorizations tab. 3. Create a new authorization for the desired user with the Monitor Tools toolbox and the CMS system and click OK. NOTE: This gives the user single sign-on as a user level, which is sufficient for a user based off the user template. For users based on the operator template, a higher single sign-on level is required 1. Log in as an administrator to HP Systems Insight Manager. 2. Select Options>Security>Users and Authorizations, and select the Toolboxes tab. 3. Create a new toolbox with all tools in the PMP category and the System Management Homepage as Operator in the View category and click OK. 4. From the Authorizations tab, create a new authorization for the desired user with the newly created toolbox and the CMS system and click OK. -------------------------------------------------------------------------------- After an integrated installation, the PMP license might not be added for the CMS until after the Software Status Polling task runs. You can either wait one hour after installation for the task to automatically run or you can manually run the task. To manually run the task: 1. Select Options>Status Polling>Software Status Polling. 2. Select the target system from the All Systems list. 3. Click Run Now. -------------------------------------------------------------------------------- If the menu items Licensing... and Configuration... under Options, Performance Management Pack Options generate HTTP 404 Page Not Found errors, but the Manual Log Purge... menu works, restart the HP Performance Management Pack service. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- PRINTING ISSUES When printing a System or Event List in HP Systems Insight Manager, using the Mozilla browser, changes made in the print window are not reflected in the hardcopy. For example, after you click Print, click Appearance and verify that the One Side option is selected. Click Print. The hardcopy is double sided. To correct, change the system printer configuration (Settings>Printers), and deselect double-sided print. Click Print. The hardcopy is correct. -------------------------------------------------------------------------------- In HP Systems Insight Manager, when printing, selecting, or deselecting the Don't show this dialog box again option and clicking Yes in the Print Request dialog box has no effect. However, if you select No in the Print Request dialog box, the request remains until you select Yes. In addition, if you click the Print option in HP Systems Insight Manager and click Cancel, then click the Print option again, the Print Request dialog box does not display at all. These are all issues with the Sun Java Plug-In. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- REPORTING ISSUES When reports are too wide to print, even in Landscape mode, save the report in CSV format and print from a tool such as Microsoft Excel, or select fewer data items for each category in the report. Refer to the "HP Systems Insight Manager Online Help" for information on saving a report in CSV format. NOTE: This recommendation applies to all reports EXCEPT Snapshot Comparison reports. -------------------------------------------------------------------------------- Snapshot Comparison reports might not show accurate differences from different snapshots. This is a known limitation with HP Systems Insight Manager that will be corrected in an upcoming release. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- SEARCH ISSUE If you receive a script error when editing the Events by Time search, click No when asked if you want to debug the error. You are then able to edit the search. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- SECURITY ISSUE If HP Systems Insight Manager is installed after SMH is installed, the SMH 2048-bit key pair is replaced with the HP Systems Insight Manager 1024-bit key pair. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- SNMP ISSUE Windows 2003 installations do not have SNMP installed by default, so you must install SNMP manually. After SNMP is installed, the security settings have the local host enabled only. The default configuration for Windows 2003 must be modified to properly discover the system. Refer to the Windows documentation on how to install the SNMP service. How should SNMP be configured? The SNMP service must have the security settings changed to enable SNMP communications with other systems. The same community string used by HP Systems Insight Manager should be added to and at least the address of the system on which HP Systems Insight Manager is installed should be listed in the list of allowed IP addresses. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- SOFTWARE/FIRMWARE ISSUES The Install Software and Firmware task for a switch appears to complete successfully, but the firmware is not deployed on the target switch. One reason for this is if the c:\cpqsystem\log\cpqsetup.log file is locked the installer terminates immediately with no error code. To solve the problem, delete or rename this file and restart the task. -------------------------------------------------------------------------------- When updating switch software and firmware, the software update is performed, but the firmware update is not. There is no log file describing the error. This issue is resolved with firmware version 2.1.1 for the GbE Interconnect Switch and version 1.2.0 of GbE2 Interconnect Switch. -------------------------------------------------------------------------------- For a switch firmware upgrade to be successful, the correct SNMP write community string of the switch must be specified in the Global Protocol Settings page. -------------------------------------------------------------------------------- When executing the Install Software/Firmware task on an upgraded Windows 2003 Advanced Server, the status is not updated and the task times out. Perform the following actions to allow the task to complete as expected. On the Linux target node, edit the /etc/hosts file to add an entry for the CMS. The entry in /etc/hosts should appear as: -------------------------------------------------------------------------------- If you do not include the HP Version Control Repository Manager during the installation of HP Systems Insight Manager, you will receive an error message when running the Install Software and Firmware task. If this happens, install the HP Version Control Repository Manager and select Options->Version Control Repository to make this your default. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- SQL ISSUE Uninstalling Insight Manager 7 or HP Systems Insight Manager does not uninstall the SQL database that was created for these products. To attempt another installation of HP Systems Insight Manager after it has been uninstalled and still use the same database server, the database itself must either be manually deleted or renamed (deleting is permanent data loss; renaming is more cautious but does require disk space). This is a problem on Windows only. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- SSH ISSUES The HP Systems Insight Manager SSH keys might need to be set up. To have command line and custom tasks work in HP Systems Insight Manager, re-run mxagentconfig for Administrator if HP Systems Insight Manager was installed by someone other than Administrator. To do this, run mxagentconfig -a -n -u Administrator -p Where is the name of your management server and is the password for the administrator account. Alternately, run mxagentconfig from the command line with no parameters and enter the Central Management Server (CMS) system name and the administrative user details into the graphical user interface (GUI). This sets up the authorized_keys2 file in the administrator/.ssh directory with the CMS key. Note that this only works if the user 'Administrator' is a valid user on the CMS and that user has logged in to Windows, creating the home directory. Further information on SSH is available in the white paper 'SSH in HP Systems Insight Manager' available from the HP website. -------------------------------------------------------------------------------- mxagentconfig does not work properly for a domain user: Check to see if the home directory of the user is not of the form "c:\documents and settings\". In some cases it will be at a different location for a domain user, such as "c:\documents and settings\.xxxx" where xxxx is usually a domain name. If this is the case, then: 1. Go to "c:\Program files\OpenSSH\etc" folder 2. Edit the passwd file using wordpad 3. Look for the part that says \home\ 4. Replace with 5. Restart the OpenSSH service -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- TASK ISSUES Command line tasks that create large amounts of output, for example, an ls -laR /,can cause the DTF to hang. Therefore, the output from the command line tasks should not exceed 1 MB. -------------------------------------------------------------------------------- On an HP-UX system, when a full configuration rights user edits a task and changes the owner to a limited configuration rights user, and then views the task, the original owner is still shown as the owner. If you open another browser and view the task, the correct owner is displayed. This is a sporadic error. -------------------------------------------------------------------------------- To successfully execute the Initial ProLiant Support Pack Install task, you must reboot the system after Installing HP Systems Insight Manager. If not you will receive an error stating Installpsp.bat is not an internal or external command operable program or batch file. -------------------------------------------------------------------------------- To successfully execute the Install OpenSSH task, you must reboot the system after installing HP Systems Insight Manager. If not you will receive an error stating Installssh.bat is not an internal or external command operable program or batch file. -------------------------------------------------------------------------------- After setting up a trust relationship to a target system using the Configure link, the Trusted? column still shows No. This occurs in the Install Software and Firmware, Initial ProLiant Support Pack Install, and Replicate Agent Settings tasks. This also occurs on the Version Control Repository setting panel. To resolve this issue, click the Last Update link above the table to update the selected row. Note that for performance reasons only, the currently selected row is updated. If the Last Update does not refresh the trust status, start a new browser session and the trust status is updated. -------------------------------------------------------------------------------- The message "The task cannot be edited because the repository used when creating the task is not found in HP Systems Insight Manager or has been deleted and rediscovered. You will need to delete this task and recreate it using a different repository system" can be displayed when editing a task where the HP Version Control Repository system is no longer in the HP Systems Insight Manager database. In this case, it is necessary to recreate the task using a different HP Version Control Repository system. This message can also be displayed if the HP Version Control Repository system has been deleted and subsequently rediscovered. In this case, simply log out of HP Systems Insight manager and log back in to eliminate the error. ------------------------------------------------------------------------------- Action on Events tasks upgraded from HPSIM 4.0 are not paging users as expected. To correct this issue, edit the tasks and save them (even with the same settings). -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- TOOL ISSUES If an mxauthenticationexception is generated when a tool is run, either from the GUI or the command line interface (CLI): 1. Be sure that the user you are trying to run as has privileges to run the tool on that system. Refer to the 'HP Systems Insight Manager Online Help Guide' to check and grant privileges. 2. Be sure that the SSH daemon is accessible on the target system. a. From the CMS, attempt to manually install SSH to the system. There is no need to log in, but be sure that you can connect. b. Try to log in as an administrative user to a Windows system or as root on an HP-UX or Linux system. i. From an HP-UX or Linux CMS, enter: ssh root@< HP-UX/Linux node> or ssh Administrator@ ii. From a Windows CMS, enter: \bin\ssh root@ \bin\ssh Administrator@ If you are prompted to accept a host key or enter a password, then the SSH daemon is accessible. 3. Re-run mxagentconfig to be sure that the keys are transferred: mxagentconfig -a -n -u -p 4. On the system on which you are attempting to run tools, verify the permissions of some directories. Verify the permission on the home directory of the user you are trying to run the tool as. - The home directory should have permissions: drwxr-xr-x (755) - The .ssh directory within the home directory should have permissions: drwxr-xr-x (755) - The authorized_keys2 file in the .ssh directory should have permissions: -rw-r--r-- or -rwxr-xr-x (644 or 755) a. Verify these permissions: On Windows: Run "\bin\ls -ld " On HP-UX or Linux: Run "ls -ld " b. Change permissions: On Windows: Run "\bin\chmod " On HP-UX or Linux: Run "chmod " (Permission number is the previous number, for example, 644/755) 5. When the command is run, the Execute-as user is listed in the status. This is the user for whom you must run mxagentconfig. 6. If execution has worked in the past and is now failing, verify that SSH has been reinstalled on the target system. Reinstalling SSH causes the system to create a different host key. Therefore, the SSH client used by the CMS is unable to verify that it is the system that it is trying to contact. - If SSH has been reinstalled, open the known_hosts file for editing /etc/opt/mx/config/sshtools/known_hosts or \config\sshtools\ known_hosts - Remove the lines that refer to the system on which to execute. Remove all references to the system (for example, nodename, nodename.hp.com, or the IP address of the system). - Alternately, you can also remove the entire known_hosts file (located in \config\sshtools\) on the CMS, which means that the SSH client used by the CMS re-registers the keys of every system the next time it contacts them through discovery and identification. This is a security problem until each system has been contacted and keys exchanged. 7. Remove the .ssh directory from the home directory of the user on the managed system, which ensures that there are no old keys or old permissions that could cause mxagentconfig to fail. 8. Run mxagentconfig again. -------------------------------------------------------------------------------- Mxagentconfig fails when trying to authorize a user on a Windows system that did not install OpenSSH. 1. If trying to run as a Domain User, you MUST log in to Windows with that domain account before running mxagentconfig. Your "Documents and Settings" directory does not exist until the you log on, and if the "Documents and Settings" directory does not exist, then mxagentconfig fails. 2. Login to the CMS as the domain user (the domain user must be either a member of the local Administrators group or a member of the Domain Administrators group) and run: cd "c:\Program Files\OpenSSH\bin" mkpasswd -d -u >> ..\etc\passwd mkgroup -d >> ..\etc\group NOTE: One of these might end with an error, depending on the user. This is acceptable and expected. 3. Restart OpenSSH service. 4. Re-run mxagentconfig. If mxagentconfig still fails, be sure SSH is running. 1. Be sure that the username being sent to mxagentconfig does not include the domain. Use myusername instead of mydomain\myusername. 2. Remove the .ssh directory from the home directory of the user on the managed system. The home directory is typically "C:\Documents and Settings\username". From a Windows command window, typing "set HOMEPATH" will report the home directory of the currently logged-in user. This step ensures that there are no old keys or old permissions that could cause mxagentconfig to fail. 3. If the failure still occurs, then manually copy the key by transferring the file .dtfSshKey.pub to the managed system from the CMS. The file can be found at /etc/opt/mx/config/sshtools/ on Linux and HP-UX. On Windows, you can find the file at \config\sshtools. On Windows: >> "\.ssh\authorized_keys2" On HP-UX or Linux: "cat >> ~/.ssh/authorized_3 -------------------------------------------------------------------------------- When executing a task, the message Unknown OS is displayed. 1. If the system that you are trying to execute a task against is a Windows system, verify that it was rebooted after installation of SSH. A reboot is required to complete the installation. 2. Enable DMI, WBEM, or SNMP on the system so the type of operating system can be determined, and then run data collection to update the HP Systems Insight Manager database. 3. Verify that the commands to determine the operating system are working. On Windows: ver On HP-UX and Linux: uname -------------------------------------------------------------------------------- The kill option is not currently supported from a partner application. Connect to the managed system directly and enter the kill command. -------------------------------------------------------------------------------- A limited configuration rights user is not able to see or select some of Custom Command tools that were assigned to them when using a Mozilla browser. There is a limitation of the number of tools that can be displayed with a screen resolution of 1024 x 768. Typically, the screen is limited to 25 to 35 tools depending on font sizes, and so on. -------------------------------------------------------------------------------- If you install a newer version of a tool than the version shipped with HP Systems Insight Manager 4.1, localization might be affected. If you feel that both TDEFs serve equally well but would like to keep the localization version, then you should use mxtool to remove the TDEF file that came with the newer tool and use the version that shipped with HP Systems Insight Manager. -------------------------------------------------------------------------------- When launching an HP Systems Insight Manager tool in an external window, you might not have the same user privileges that you had in HP Systems Insight Manager. -------------------------------------------------------------------------------- Using the mxnodesecurity command on an HP-UX system to add a system from a different domain, the command does not work properly. For example, if you enter mxnodesecurity -a -p wbem -c openview\wmi:wmi -n testnode10 the single backslash between openview and wmi is missing. The UNIX shell environment recognizes the single backslash as an escape character. If you want to add a system from a different domain, you should add another backslash for it to be recognized. For example, mxnodesecurity -a -p wbem -c openview\\wmi:wmi -n testnode10. -------------------------------------------------------------------------------- On HP-UX 11.11 and 11.23 systems, the mxinitconfig command displays a warning if kernel parameters are set in hexadecimal. -------------------------------------------------------------------------------- The HP Systems Insight Manager tools on an English Windows system run as Administrator. If you have a policy set to not use an account with this name, or install on a foreign language OS that does not use Administrator, you should refer to the "Secure-Shell (SSH) in HP Systems Insight Manager" white paper located at http://www.hp.com/go/hpsim/. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- TRAP ISSUE HP Systems Insight Manager does not provide out-of-the box SNMP trap support for HP GbE switches. This support will be included in a future version of HP Systems Insight Manager. Contact HP support to obtain the manual process for installing GbE switch trap support. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- UPGRADE ISSUE Go to http://www.hp.com/go/hpsim/ and click Questions & Answers for more information on migrating from Insight Manager 7 or Servicecontrol Manager 3.0 to HP Systems Insight Manager. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- VPM ISSUE Vulnerability and Patch Management reporting is not supported on HP-UX and Linux with HP Systems Insight Manager 4.2. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- WMI ISSUE HP Systems Insight Manager can have problems accessing WMI data on managed systems with a hyphen (-) in the fully qualified DNS system name when using a WMI mapper that is not installed on that managed system. If this is the case, HP recommends that you install the WMI mapper on every managed system with a hyphen (-) in the system name. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- 2. Migration from Insight Manager 7 -------------------------------------------------------------------------------- MIGRATION ISSUES After running DMT to create an export file and then importing that file into HP Systems Insight Manager, not all of the systems are listed on the System Overview page. The system (device) will not be imported if one of the following is true: - Unable to ping the system - DNS cannot resolve the system name - System name or IP address has changed since the system was exported -------------------------------------------------------------------------------- After upgrading from Insight Manager 7, the pager users that were migrated have a dummy domain associated with them and no longer receive pages. Edit the user accounts to add a valid domain. 1. Select Options>Security>Users and Authorizations. 2. Select the user account you want to edit and click Edit. The Edit User section is displayed. 3. In the Domain (Windows(r) domain for login name) field, edit the Windows domain name for the login name if running a Windows operating system. 4. Click OK to save and close the New User section. The user changes are saved. -------------------------------------------------------------------------------- After upgrading to HP Systems Insight Manager, my network devices, racks, and enclosures are not being displayed on the system list page. After performing an upgrade, you must run identification before these systems are displayed. To identify systems in between discoveries, select Options>Discovery>Identify Systems, The Identify Systems page is displayed. From this page, select target systems to add. -------------------------------------------------------------------------------- Systems managed by IPX are not migrated from Insight Manager 7 to HP Systems Insight Manager 4.2. -------------------------------------------------------------------------------- When upgrading from Insight Manager 7, Service Pack 2.0, 2,2, or 2.3 to HP Systems Insight Manager 4.2 from a mapped drive on Windows NT Standard or Enterprise Server, exclusive of the database software installed, you might receive the erroneous message "Existing Insight Manager Installation detected", instead of a message offering to upgrade a Service Pack 2.0, 2.1, or 2.2 installation to Service Pack 2.3 installation, or a message offering to export Insight Manager 7 data from a Service Pack 2.3 configuration. After clicking Finished, the Pre-installation and Installation show as Done, and the Post-installation shows as Not Run. Installing from a Windows NT local drive or CD works properly. -------------------------------------------------------------------------------- If user items were not migrated correctly from Insight Manager 7 to HP Systems Insight Manager, complete the following: Extract user-defined data from the file user-data.dmt. Execute the following commands from a command prompt: cd %programfiles%\hp\Systems Insight Manager Data Migration Tool\user-defined-data ..\tar xvf ..\user-data.dmt This extracts all user-defined data files that were created during data export. To re-create any items that were not migrated correctly, find the command line in the IM7Import.log that corresponds to the failed command and type it from the command line. For example, the following shows that the email notification task EMail Notification2.xml timed out: 10:41:18 AM: Tasks: "C:\Program Files\HP\Systems Insight Manager\ bin\mxtask" -cf "C:\Program Files\HP\Systems Insight Manager Data Migration Tool\ user-defined-data\ tasks\EMail Notification2.xml" 10:56:22 AM: Tasks: MxTask returned status = 1 10:56:24 AM: Tasks: Process timed out 10:56:24 AM: Tasks: ***ERROR: Process timed out To attempt to re-create the email notification task, enter the following command line from a command prompt: "C:\Program Files\HP\Systems Insight Manager\bin\mxtask" -cf "C:\Program Files\HP\Systems Insight Manager Data Migration Tool\user-defined-data\tasks\EMail Notification2.xml" NOTE: Attempting to re-create any item does not guarantee success. There are a variety of conditions which affect the ability to re-create any item. -------------------------------------------------------------------------------- If some systems were not migrated from Insight Manager 7 to HP Systems Insight Manager 4.2, you should: 1. Change to %programfiles%\Systems Insight Manager Data Migration Tool\Utils directory. 2. Run getmissdev.bat. The file getmissdev.bat generates systems list which contains all the systems in HP Systems Insight Manager (after it is upgraded) called devices.list. It also generates and runs a file called missingdev.bat, which contains all the missing systems and adds them to HP Systems Insight Manager. You must run getmissdev.bat under %programfiles%\Systems Insight Manager Data Migration Tool\Utils directory while HP Systems Insight Manager is running. You can verify the missing systems by viewing missingdev.bat. This batch file contains statements (mxnode -a ) for all the missing systems, for example, mxnode -a 16.129.17.33. -------------------------------------------------------------------------------- ICMP retry and timeout settings are not migrated from Insight Manager 7 to HP Systems Insight Manager. You must enter new values for these settings in the globalsettings.prop file. To configure the ICMP retry and timeout setting: 1. Open the globalsettings.props file. On a Windows operating system, the globalsettings.props file is located in the install directory/config folder. On an HP-UX/Linux operating system, the globalsettings.props file is located in the /etc/opt/mx/config directory. 2. Change IcmpRetries and IcmpTimeout to the correct settings. 3. Click File>Save. The updates are saved. 4. Close the globalsettings.props file. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- AUTHORIZATIONS ISSUE Administrator accounts migrated from Insight Manager 7 to HP Systems Insight Manager are full configuration rights users, but do not have authorizations on tools or systems. Refer to the HP Systems Online Help, Administering the Software, Users and Authorizations section. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- CERTIFICATE ISSUES If the Insight Manager 7 server certificate fails to migrate to HP Systems Insight Manager, this will invalidate any existing trust-by-certificate relationships between the HP Insight Management Agents and HP Systems Insight Manager. To properly migrate the Insight Manager 7 server certificate to HP Systems Insight Manager, run the following command from a command prompt on the CMS: mxpassword -n -u \config\certstor For example, if your Insight Manager 7 installation is in the default directory: mxpassword -n -u "\Program Files\HP\Insight Manager 7 SP2.3\config\certstor" NOTE: this only applies to a migration on the same system. -------------------------------------------------------------------------------- If you currently have any managed systems configured to trust the Insight Manager 7 system by name and you did not migrate the Insight Manager 7 certificate, note that HP Systems Insight Manager has changed the default name format in its server certificate from short name to fully qualified name. The name in the certificate must match the name configured in the HP Insight Management Agents Trust By Name list, or the trust relationship will not work. First confirm the name in the server certificate by selecting Options>Security> Certificates>Server Certificate and observing the name in the Common Name field. If it does not match what is configured in the Web agents, you can either: - Change the name in the Trust By Name list in the Web agents by clicking Settings>Options. or - Regenerate a new server certificate in HP Systems Insight Manager using the short name instead of the fully qualified name by selecting Options>Security>Certificates>Server Certificate. This process requires you to restart HP Systems Insight Manager. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- DISCOVERY ISSUES If you find that the discovery templates from Insight Manager 7 did not migrate to HP Systems Insight Manager 4.2, then extract them from the user-defined-data.dmt file and manually add them into HP Systems Insight Manager. In case of In-Place migration, if the templates have not migrated: 1. Select Options>Discovery>Automatic Discovery>and click templates in the IP address ranges section of the page. The Automatic Discovery - Manage Templates page is displayed. 2. Click New. The Create New Template section is displayed. 3. In the Discovery template name field, enter a name for the new template. This is a required field. 4. Click Browse to select an existing discovery template file created in IM7 under C:\Program Files\HP\Systems Insight Manger 7 SP 2.3\config\advanced discovery\IMXE\. 5. Click OK to save the discovery template file, or click Cancel to close without saving changes. In case of Remote Migration, if the templates have not migrated: 1. Manually extract the template from the user-data.dmt file by copying the template contents on to a notepad. 2. Add the template manually to HPSIM Refer to "HP Systems Insight Manager User Guide" for adding a template file. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- HOSTS FILE ISSUE If Hosts files are not migrated from Insight Manager 7, you should extract the data from the exported data file and manually add them. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- JAVA ISSUES After an In-Place migration from Insight Manager 7, browsing from CMS for the first time, an error message is displayed. The Java Runtime Environment (JRE) cannot be loaded from \bin\hotspot\jvm.dll. The browser must be stopped and restarted to get around this error, which is caused by having multiple instances of the JRE installed. After restarting the browser, go to Control Panel, double-click Java Plug-In, and change the directory for JRE 1.4.1_04, under Advanced tab, to point to the latest JRE. Be sure that the JRE needed for HP Systems Insight Manager is the last JRE installed. The current version supported by HP Systems Insight Manager on Windows is JRE 1.4.1_04 or later. -------------------------------------------------------------------------------- After upgrading from Insight Manager 7 to HP Systems Insight Manager, you should uninstall the JRE (1.3.1) used by Insight Manager 7 completely. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- LIST ISSUES You might observe that private lists that were created in Insight Manager 7 for local accounts are not visible in the GUI, but are available in the HP Systems Insight Manager database after a remote migration of Insight Manager 7 data. If you want to do a remote migration, delete the Insight Manager 7 local users accounts and then run an export of the data using only the domain accounts. This is because using local account of Insight Manager 7 server you will not be able to log into the HP Systems Insight Manager remote server. -------------------------------------------------------------------------------- Because of differences in discovery and identification algorithms between Insight Manager 7 and HP Systems Insight Manager, during the migration process node names for some systems might be changed. Queries by Device Name created in Insight Manager 7 and migrated to HP Systems Insight Manager might not function as expected because of these name changes. Manually verify all migrated queries to ensure that they return the correct system results. If necessary, edit any lists with Device by Name criteria to match the new system name. In most cases, the problem is that HP Systems Insight Manager was not able to resolve the system IP address to a node/DNS name during migration. The system was likely then added to the HP Systems Insight Manager database by IP address only. -------------------------------------------------------------------------------- Device by Operating System queries migrated from Insight Manager 7 to HP Systems Insight Manager might not be properly added during migration. Specifically queries that match exact Operating System description strings might not be fully recreated. Verify all migrated lists with Operating System criteria in HP Systems Insight Manager to ensure that they are correctly matching what is expected. For example, a typical change is that a query criteria in Insight Manager 7 might match a string such as Windows 2000 Advanced Server and might map to Windows 2000 Advanced Server (Service Pack 3) and Windows 2000 Advanced Server (Service Pack 4) in HP Systems Insight Manager. -------------------------------------------------------------------------------- If the number of event-type criteria imported from Insight Manager 7 is large, HP Systems Insight Manager does not load the original criteria into the editing page for the list. Saving this list overwrites the original criteria with the new criteria specified. Canceling maintains the existing criteria. -------------------------------------------------------------------------------- Queries migrated from Insight Manager 7 using the Devices with Software and Firmware might not be editable in HP Systems Insight Manager after migration. Please ensure that you have a Version Control Repository Manager configured to work with HP Systems Insight Manager. If you are still unable to edit the query, then you will need to manually recreate the query. -------------------------------------------------------------------------------- Queries by Operating System with United Linux 1.0 and Red Hat 8.0 criteria might not be successfully migrated from Insight Manager 7 to HP Systems Insight Manager. If problems are encountered, these queries will need to be manually recreated. -------------------------------------------------------------------------------- When importing queries from HP Insight Manager 7 to HP Systems Insight Manager, queries with extra spaces in the name are not imported. For example, 'Test Query' would not be imported. -------------------------------------------------------------------------------- Queries migrated from Insight Manager 7 using the IP address criteria, where IP is "a.b.c.d-a.b.c.d", behave differently when edited in HP Systems Insight Manager, The criteria will read "is between" "a.b.c.d" and "000.000.000.000". This will not impact the execution of the query in HP Systems Insight Manager. -------------------------------------------------------------------------------- Queries migrated from Insight Manager 7 that have names longer 70 characters might have a blank line below under customize list. This will not have any impact on the execution of the query in HP Systems Insight Manager. -------------------------------------------------------------------------------- During migrations, events are not migrated into Systems Insight Manager. Therefore, event queries will not function correctly until events are received with that particular list criteria (for example, Login Events, Logout Events, etc.). Until events are received that fit custom event queries, a Java error will be produced until that particular list criteria event is in the database. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- SOFTWARE/FIRMWARE ISSUE If you try to edit the Software/Firmware task which is imported into HP Systems Insight Manager from the Insight manager 7 an Http Status 500 exception is displayed. However, the task will run correctly While editing the task reselect the component to deploy before clicking Next to schedule the task, and the error is not displayed. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- TASK ISSUES Since HP Systems Insight Manager limited configuration rights users cannot create tasks, any tasks created by an operator in Insight Manager 7, can only be viewed by a full configuration rights user. -------------------------------------------------------------------------------- After you migrate from Insight Manager 7 to HP Systems Insight Manager 4.2, you can run the Software firmware task but if you edit the task, you must re-select the components in each step (if no components were selected) and save the task. -------------------------------------------------------------------------------- If Notification tasks migrated from Insight Manager 7 relied on queries containing Event Cleared criteria, Event Time criteria or any Cluster criteria, then these notification tasks are added on Automatic Event Handling tasks but must be edited before they can be run. Event Cleared criteria, Event Time criteria or any Cluster criteria are not valid for Automatic Event Handling tasks in HP Systems Insight Manager. -------------------------------------------------------------------------------- Notification tasks migrated from Insight Manager 7 using the default "All Unknown Clusters" query will be mapped to the "All Clusters" criteria in HP Systems Insight Manager. If you wish to retain the "Unknown" status criteria, please edit the migrated Automatic Event Handling task. -------------------------------------------------------------------------------- If the number of event-type criteria imported from Insight Manager 7 is large, HP Systems Insight Manager does not load the original criteria into the editing page for an Automatic Event Handling task. Continuing overwrites the original criteria with the new criteria specified. Canceling maintains the existing criteria-this task continues to run as scheduled. -------------------------------------------------------------------------------- Application Launch tasks with multiple consecutive spaces in the task name in Insight Manager 7 (for example, "My Custom Application Launch Task" will not be properly migrated to HP Systems Insight Manager. These tasks must be manually recreated. -------------------------------------------------------------------------------- Tasks in Insight Manager 7 that begin with a numeric character must be recreated in HP Systems Insight Manager because they will not be migrated. ________________________________________ HP SYSTEMS INSIGHT MANAGER DOCUMENTATION * HP Systems Insight Manager User and Installation Guide. This document provides information about installing and getting started using HP Systems Insight Manager. This guide includes an introduction to basic concepts, definitions, and functionality associated with HP Systems Insight Manager. This document is available at http://docs.hp.com/ or http://www.hp.com/go/hpsim/. * HP Systems Insight Manager Help System. The help system provides a complete set of documentation for using, maintaining, and troubleshooting HP Systems Insight Manager. A PDF of this document is available at http://www.hp.com/go/hpsim/. Additional information including general product information, white papers, and support information is also available at http://www.hp.com/go/hpsim/.