Hi,
Just ran through a test install of ESX 3.0.1 and found the HP Insight Agents 7.5.1a failed to install due to a version check in the install751vm.sh script. Upon investigation I have found that HP have released a 7.6.0 version and also the VMware documentation states the following....
http://www.vmware.com/pdf/vi3_systems_guide.pdf
Extract...
Management Application ESX Server 3.0 ESX Server 3.0.1[/b]
HP Insight Manager 7.5.1a X
HP Insight Manager Agent 7.6.0 X X
Latest 7.6.0 HP Insight Agent for ESX 3.0.1
http://h18007.www1.hp.com/support/files/server/us/download/25469.html?jumpid=reg_R1002_USEN
Just re-testing and will feed back any issues....
Michael.
Message was edited by: Correct formatting....
MichaelJKnight
I was able to get 7.6.0 working in my sandbox environment, but do you know when they might release a version of the virtual machine management pack that works with ESX 3.0?
During the install of the 760 agent I get:
For adding the HP Systems Insight Manager Certificate in SMH, the port \[280]
should be enabled in the firewall.
Do you want to enable this port? <y/n> (default is y) y
opening port 280 FAILED
Any ideas?
Hi,
I have been doing unattend installs and have not seen the issue.
Here is an extract of the log from /hpmgmt/760/hpmgmtlog[/b]
*********Tue Oct 3 13:51:53 BST 2006*********
HP Insight Manager Agent 7.6.0-38 Installer for VMware ESX Server
Verifying VMware ESX Server version \[ OK ]
Verifying RPM packages:
Verifying hpasm-7.6.0-146.vmware.i386.rpm \[ OK ]
Verifying hprsm-7.6.0-119.vmware.i386.rpm \[ OK ]
Verifying cmanic-7.6.0-5.vmware.linux.rpm \[ OK ]
Verifying hpsmh-2.1.6-156.vmware.i386.rpm \[ OK ]
Installing HP System Management Homepage:
Checking dependencies of hpsmh-2.1.6-156.vmware.i386.rpm \[ OK ]
Installing hpsmh-2.1.6-156.vmware.i386.rpm
Preparing... ##################################################
Detected Red Hat Advanced Server 2.1
Creating hpsmh user and group...
hpsmh ##################################################
**********************************************************
\* System Management Homepage installed successfully with *
\* default configuration values. To change the default *
\* configuration values, type the following command at *
\* the root prompt: *
\* *
\* perl /usr/local/hp/hpSMHSetup.pl *
\* *
**********************************************************
Stopping hpsmhd:
Starting hpsmhd:
hpsmhd: Could not determine the server's fully qualified domain name, using 10.128.136.222 for ServerName
\[ OK ]
\[ OK ]
Found SMH configuration file...copying
\[ OK ]
Installing HP Management Agents:
Checking dependencies of hpasm-7.6.0-146.vmware.i386.rpm \[ OK ]
Installing hpasm-7.6.0-146.vmware.i386.rpm
Preparing... ##################################################
hpasm ##################################################
Please read the Licence Agreement for this software at
/opt/compaq/hpasm/hpasm.license
By not removing this package, you are accepting the terms
of the "License for HP Value Added Software".
==============================================================================
NOTE: Your SNMP stack can load the 32-bit hp ProLiant Management Extension.
Problems may result from using your distribution's SNMP stack.
See hp Documentation (HOWTO, agent manual) for more details.
==============================================================================
==============================================================================
NOTE: New snmpd.conf entries were added to the top of /etc/snmp/snmpd.conf
==============================================================================
==============================================================================
NOTE: New cma.conf entries were added to the top of /opt/compaq/cma.conf
==============================================================================
Following environment variables were used to configure snmpd/agents:
CMALOCALHOSTRWCOMMSTR
CMALOCALHOSTROCOMMSTR
CMAMGMTSTATIONIPORDNS
CMAMGMTSTATIONRWCOMMSTR
CMAMGMTSTATIONROIPORDNS
CMAMGMTSTATIONROCOMMSTR
CMADEFTRAPCOMMSTR
CMATRAPDESTINATIONIPORDNS
CMATRAPDESTINATIONCOMMSTR
It has been determined that your server has more than 4GB of memory.
Due to a kernel performance issue on some 2.4 kernels, closing CCISS
device nodes may take lots of CPU time on servers that have a large
amount of memory. The storage agents will therefore keep CCISS device
handles open. Please be advised that by doing so you may have to
stop agents before you can configure the disks attached to CCISS
controllers with such tools as fdisk or cpqacuxe.
Starting HP Server Management Drivers and Agents, please wait ...
The hpasm RPM has installed successfully.
\[ OK ]
Checking dependencies of hprsm-7.6.0-119.vmware.i386.rpm \[ OK ]
Installing hprsm-7.6.0-119.vmware.i386.rpm
Preparing... ##################################################
hprsm ##################################################
Please read the License Agreement for this software at
/opt/compaq/hprsm/hprsm.license
By not removing this package, you are accepting the terms
of the "License for HP Value Added Software".
Looking for sources to build 2.4.21-37.0.2.ELvmnix
Rebuild successful.
..cpqci started.
Looking for sources to build 2.4.21-37.0.2.ELvmnix
Setting up hprsm sources for custom RPM
Custom RPM(s) available: /usr/src/redhat/RPMS/i386/hprsm-7.5.0-custom.i386.rpm
==============================================================================
NOTE: New cma.conf entries were added to the top of /opt/compaq/cma.conf
==============================================================================
Starting HP Lights-Out Drivers and Agents (hprsm): cpqriisd cmasm2d cmarackd
Starting cpqriisd:\[ OK ]
Starting RIB agent (cmasm2d):
Starting Rack agent (cmarackd):
The hprsm RPM has installed successfully.
===================================================================
NOTE: If you have not previously run the 'hpasm activate'
command you must type 'hpasm activate' as 'root' user
to activate the agent software in this package.
===================================================================
\[ OK ]
Checking dependencies of cmanic-7.6.0-5.vmware.linux.rpm \[ OK ]
Installing cmanic-7.6.0-5.vmware.linux.rpm
Preparing... ##################################################
cmanic ##################################################
cmanic installation: snmpd Start script is detected at runlevels 2 3 4 5
cmanic installation: cmanic Start script is installed at runlevels 2 3 4 5
cmanic installation: snmpd restarted
cmanic installation: Foundation agent (cmafdtn) restarted
\[ OK ]
Enabling the port for hpim service (2381) in the firewall \[ OK ]
Enabling snmpd service in the firewall \[ OK ]
Enabling the port \[280] for adding the HP SIM Certificate in SMH \[ OK ]
Stopping HP Insight Manager agents:
Stopping cmanic: \[ OK ]
Stopping hprsm: \[ OK ]
Stopping hpasm: \[ OK ]
Stopping System Management Homepage: \[ OK ]
Waiting for SMH to stop
SMH not stopped yet...sleeping for 5
Waiting for SMH to stop
SMH is now stopped
Stopping SNMP stack:
Stopping snmpd: \[ OK ]
Starting SNMP stack:
Starting snmpd: \[ OK ]
Starting System Management Homepage: \[ OK ]
Starting HP Insight Manager agents: \[ OK ]
Please read the Licence Agreement for this software at
/opt/compaq/hpasm/hpasm.license
By not removing this package, you are accepting the terms
of the "License for HP Value Added Software".
HP Insight Manager agents have been installed successfully!
I will try a manual install and see, could you post you installation log ?
Michael.
Hi
Do you need to uninstall the existing 7.51 agent before installing the 7.60 agent? Or will it upgrade nicely
Thanks
David
If it follows the pattern of the past upgrades it will uninstall first and then install the new version as part of the upgrade process
I had no issues updating my scripted build with this latest version , however I'm not seeing any information displayed when I log in, and the page is taking along time to load.
I have confirmed that the required ports are open.
Opened ports:
hpim : port 2381 tcp.in
sim-cert : port 280 tcp.out
Is anyone having similar issues?
I had no issues in updating the agents to 7.6.0 from 7.51a. The agents where uninstalled during the process. The new install process will verify if older agents are running and uninstall them. If you had everything running fine from before with firewall cfg and the ports leave the defaults.
Did you do your upgrade from 7.5.1a to 7.6.0 from ESX 3.0.0 ? It doesn't appear you can even install 7.5.1a on ESX 3.0.1 I wanted to test something.
I still have an issue with 7.6.0 on ESX3.0.1 , it installs ok, but some infomation is not displayed when I log in.to the web interface, Its as if no information is being returned from the agent.
Hi,
You can force it to 751 to install on ESX 3.0.1 by modifiying the version check in installvm751.sh script but I wouldn't recommend it though I did get it to work but then found the 7.6.0 version.
Michael.
Micheal,
Do you have 7.60 installed on 3.0.1 ?
Doe's everything seem to be displayed in the web interface?
The install of 7.6.0 on ESX 3.0.0 was fine for me, but I'm having problems with 3.0.1 ..
Hi,
It appears to be reporting ok, what are you missing ?
I assume your mean the web interface displayed from
I can email you offline a screenshot of the main status page if required.
Michael.
Message was edited by:
MichaelJKnight
When logging into the hp management site do you come to a page that states no failed/degraded items and there is no other information regarding the server? After installing the 7.6.0 agents did you run through the configuration by typing:
service hpasm configure
This is what I had to do even after specifying all the information that this configuration asks for in the silent install config file.
Yes thats pretty much what I get, a web page showing no failed/degraded items.
I didn' trun through the configuration after the install becasue I specified a config file as part of the slient install. So that should have done the trick. Certainly an installation using exactly the same build script and version 760 on 3.0.0 works fine!
However I will run though the configuration again tomorrow.
service hpasm configure has resolved my problem, not sure why this is happening! but a step in the right direction !
P2VPMP what hardware are you installing 760 on ESX3.0.1 on?
I'm running on a DL380 G3. The silent install did nothing for me either.
Does anyone know of a way to configure iLo from the service console without going into the BIOS like you can through Windows? That seems to be the only configuration option missing in these agents.
Any thoughts on what the answer to this question should be (and why)?
It has been determined that your server has more than 4GB of memory.
Due to a kernel performance issue on some 2.4 kernels, closing CCISS
device nodes may take lots of CPU time on servers that have a large
amount of memory. By answering 'y' to the following question, agents
will keep CCISS device nodes open without ever closing them to achieve
better performance. Please be advised that by doing so, you may have
to stop agents before you can configure the disks attached to CCISS
controllers with such tools as fdisk or cpqacuxe.
Do you wish to keep CCISS device handle open (y/n):
I answered NO in my dev ESX 3.0.1 servers. I wonder what kernel ESX 3.x uses... I hope not 2.4...
No problems so far, but I having done much disk management yet to see if CCISS acts up or not.
-H-
Just checked with "uname -a" and ESX is using 2.4
Anyone else have any opinions on answering this question for 7.6.0 agents?