******************************************************************************* ** ************* readme.ESX20 ************** ** ******************************************************************************* The file contained in the HP Advanced Server Management Package for VMware ESX 2.0 provide the user with multiple system management. The standard configuration would be to use the Insight Manager 7 SP 2 software. The web links for more information are: http://h18004.www1.hp.com/products/servers/management/cim7-description.html http://h18000.www1.hp.com/products/servers/management/cim7-documentation.html The hpasm package can be configured to proactively log events remotely or send e-mails for any serious error that occurs on the server. The remote logging uses the native Linux syslogd(8) facility. The e-mail notification requires that the sendmail(8) (or some other mail) facility be installed and configured. If something other than sendmail(8) is used, a link to "/bin/mail" must exist to enable the proactive e-mail alerts. INSTALLATION INSTRUCTIONS: ============================================================================ Note that you must always be logged on as username "root" for all of the instructions in this document. The VMware ESX 2.0 software needs to be installed and configured before installing the HP Advanced Server Management (HPASM) Package. The HPASM package will install if the VMware SNMP sub-agent is not enabled via the options menu but a warning will be issued. You may enable monitoring of VMware ESX 2.0 events by pointing a web browser at the IP address of the system (e.g. http://ip.add.ress) and log in to the VMware System Configuration menu as user name "root". Select the "Options" tab and then select SNMP Configuration. Make sure that SNMP and the VMware SNMP SubAgent areall enabled if you want full monitoring of the system. Once the VMware ESX 2.0 system has been configured, log onto the console operating system. Change the working directory to the directory where this file was unbundled (e.g. /home/vmware/hpmgmt). The installation script will perform some basic checks and will guide you through the installation process. Some things you will want to consider before you start the installation: 1. Is this a new installation or an upgrade? If you are upgrading VMware or you have previously installed a HP ProLiant SNMP stack or agents, you must run the "hpmgmt_uninstall.sh" script to remove the older packages. Future releases of this package will permit upgrading which will allow retention of the SNMP configuration. 2. Will you be using the Insight Manager 7 console? If so, you want to allocate an IP address for the Insight Manager 7 console as you will need to provide it during the installation process. You must provide either the IP address or the fully qualified DNS name for the IM7 console. This will be an additional "rocommunity" string in the snmpd.conf file. The installation script will ask for this information or you can skip this step and modify "/etc/snmp/snmpd.conf" to the necessary information. 3. Do you have other ProLiant or HP servers that you wish to manage? If so, you should layout what the SNMP community strings should be. The default is usually "public" but since everybody knows the default, this is not considered to be very secure. The snmpd.conf(5) man page has more information. In general, you need to know the "community strings" (e.g. public) and the IP address of the Insight Manager 7 console. NOTE: If you use a "community string" other than "public", you will need to edit the "/etc/snmp/snmpd.conf" file and find the line: com2sec notConfigUser default public Change "public" to what ever you chose the "community string" to be. This allows this server to be detected by the IM7 console. If you are not using IM7, then this step is not required but IM7 is a free management product from HP. 4. Do you wish to enable the HPASM proactive e-mail package? If so, you need to install the sendmail(8) package. You will need to contact VMware to determine which version of sendmail(8) is compatable with VMware ESX 2.0. 5. To be able to monitor the server via the SSL enabled web interface, you need to provide passwords for the Administrator, Operator and User. Each of these users have different priviledges. More information may be obtained from the Insight Manager 7 web pages referenced at the beginning of this document. Once you have the information to configure the SNMP and web enabled agent interfaces, you can install the packages. To install, you must be logged onto the console OS as user name "root". You should already be in the directory where you are reading this file from. At the command prompt: [root@myserver hpmgmt] sh hpmgmt_install.sh You will be led through the installation. The most common error is not having the VMware SNMP configured and running BEFORE installing this package. If you encounter errors and you have previously loaded a version of the HP ProLiant Advanced Server Management package, please run the "hpmgmt_uninstall.sh" script to perform some clean up. Then run the "hpmgmt_install.sh" script again. VALIDATING INSTALLATION: ============================================================================ You can run a few utilities to validate that the installation of the package was successful. lsmod The lsmod lists the active modules. You should see output similar to the following: Module Size Used by Tainted: PF cpqasm 305600 20 cpqevt 7008 2 [cpqasm] If you have an HP ProLiant Integrated Lights Out (iLO) Management controller, the hprsm package will have been installed. You should then see an entry similar to: Module Size Used by Tainted: PF cpqci 24188 5 If you have an HP ProLiant server that supports RAID or Hot Plug memory, you will have an entry similar to: Module Size Used by Tainted: PF cmhp 80320 1 There will be other modules listed but these are the ones that this package inserted. snmpwalk localhost public enterprises | grep cpq This command will list all the SNMP Management Information Block (MIB) items associated with "cpq". These are the HP management items. snmpwalk localhost public enterprises | grep 6876 This command will list all the SNMP Management Information Block (MIB) items associated with the VMware ESX software. The are the VMware management items. Note that once the system is rebooted, this command may no longer work if you have not enabled the VMware SNMP subagent to run at startup (automatic). If you want full monitoring of the system, you need to log onto the VMware console as previously described and enable automatic start of the VMware SNMP processes. https://fully.qualified.name.com:2381 Point your web browser to the fully qualified name of this server (or the IP address) and port 2381. Note that you MUST use the "https://" prefix and port ":2381" or this will not work. This will allow you to log into the Web Agent and view the status of the machine. You provided a password for the "Administrator" account when you installed this package. TUNING INSTRUCTIONS: ============================================================================ The hpasm package can be tuned for individual needs. The file used for tuning the base hpasm package is named: /etc/casmd.conf To decrease the amount of time the hpasm package polls various temperature sensors, you may modify the POLL_TIME variable in this file. Setting the POLL_TIME value to two (2) minutes is acceptable is well controlled environments. To set the POLL_TIME value to two (2) minutes, edit the /etc/casmd.conf file and find the line containing the POLL_TIME variable. Delete the comment symbol ("# ") from the beginning of the line and change the "45" second value to "120" seconds. REMOVAL INSTRUCTIONS: ============================================================================ You need to change to the directory where this file is located. Then enter the following command: sh hpmgmt_uninstall.sh The output is very verbose but this will remove all instances of the HP Advanced Management Software including the snmp stack. If you want to use the VMware SNMP stack without the HP ProLiant Advanced Server Management software, you will need to install the SNMP package from the VMware media. The VMware SNMP packages are located on the VMware media: ./VMware/RPMS/ucd-snmp-4.2.3-1.i386.rpm ./VMware/RPMS/ucd-snmp-utils-4.2.3-1.i386.rpm CONFIGURING FOR PROACTIVE E-MAIL ALERTS: ============================================================================ The hpasm package has the ability to send e-mail alerts when serious conditions are detected on the server. The "sendmail" (or some other mail) facility is required along with the "/bin/mail" (or a link to some other mail) utility. If the ProLiant Insight Manager (IM) console is utilized, this functionality is not required since the ProLiant IM console aggregates all messages and sends e-mail as configured. The design of the hpasm package active alert system is to send a message to a list of designated e-mail addresses (or mailing list) for all errors that generate a warning or a critical condition. The message will contain a description of the error condition and the fully qualified path to the server's web agent home page (e.g. https://myserver.mydomain.com:2381). Note that informational messages such as "repair" type messages are not sent. The hpasm package also allows messages that are logged to the /var/log/messages file via the syslogd(8) facility to be logged to a specific local file or a remote log by designating the syslog.conf(5) facility. CONFIGURING FOR REMOTE EVENT LOGGING VIA SYSLOGD(8) ============================================================================ The "/etc/cevtdl.conf" file is used to instruct the cevtd daemon how to log the hpasm messages. The normal default is to log the messages to the "/var/log/messages" file under the "daemon" facility but there are "local0" through "local7" configurable facilities available for use with the syslogd(8) service. This file allows the customer to specify the syslogd facility to be used. Please read the syslogd(8) and syslog.conf(5) documentation for further instructions on remote logging capabilities of the syslogd service. The "/etc/cevtdl.conf" file is well documented on the syntax and includes an example. EXAMPLE OF CONFIGURING HPASM PACKAGE ============================================================================ The "/etc/cevtdm/conf" file is used to specify mail addresses for events to be sent. The "/bin/mail" (mail(1)) utility is used for sending mail and the sendmail(8) (or some other mail) service must be configured. The file is simply a list of valid mail (or mailing list) addresses. The file is well documented and includes an example. The most portable and easy to maintain method would be the following: 1. Configure the "/etc/cevtdl.conf" to use the "local5" syslogd(8) facility for logging. Configure the syslog.conf(5) file to direct all "local5" mes- sages to either a local file on each server or to a remote syslogd(8) server. The syslogd(8) and sys- log.conf(5) documention provides details on how to accomplish this standard Linux administration task. 2. Setup a global "server administrators" e-mail list on a designated server. Edit the "/etc/cevtdm.conf" file and use the e-mail list as the designated e-mail address. This implies that only one e-mail needs to be managed as the "/etc/cevtdm.conf" file is packaged as part of the remote deployment strategy of the hpasm package and can be deployed preconfigured to multiple servers. SEE ALSO: hpasm(4) cpqhealth(4) snmpd.conf(5) Copyright (c) 2003 Hewlett-Packard Development Company, L.P.