Paul, With my limited exposure to HP PSP, I believe if you were to use their install###vibs.sh with --silent (if no GUI) and feeding a config file, it will automatically configure the snmp.conf.
Using RPMs will work - but configuring SNMP as post work is a bit painful. Easier way would be to edit the XML file that comes with installer and modify the install flag from yes to no for the packages that aren't needed (just like Edmund White mentioned in his response). We run the installer in silent mode in post of kickstart on our ESX/VSphere - though not RHEL, with your and Edmonds response, it is going to change :) Thank you for your input, Regards ilya -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Krizak Sent: Wednesday, February 02, 2011 10:21 AM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] RHEL 4, 5, 6 and deployment of HP PSP We avoid using the drivers because of the hassles with the modified initrd. We only pull out the driver RPMs and install them in isolated cases where there's a known bug affecting our systems and the HP driver fixes it. We don't really "use" SNMP either, in the sense that we're not setting up SNMP traps to catch bad disks and stuff. We use the syslog messages. But note that the HP management webpage thing (hpsmh) uses SNMP on the loopback interface to communicate with the system, so you have to install hp-snmp-agents for it to work. I would hardly call it "painless" -- By not using the HP installer, there are a bunch of odds and ends you end up having to configure manually: * snmpd.conf has to have the HP dlmod added * snmpd.conf perms have to be set properly * /opt/hp/hpsmh/data/webapp-data/webagent/csginkgo -> /opt/hp/hp-snmp-agents/webagent/csginkgo symlink has to be created (this one took me hours to figure out) There may be other stuff you have to do to make it work too. And of course my setup revolves mostly around getting the hpsmh to work so our datacenter ops staff are able to log into the web interface and see which dimm/disk/psu has failed. Your particular needs may vary. For example, if all you want is to be able to manage the disk arrays, just install hpacucli and be done with it. If you just want to manage the ILO (and I think the BIOS upgrades), install hp-ilo and hponcfg, and nothing else. Paul Krizak 7171 Southwest Pkwy MS B200.3A MTS Systems Engineer Austin, TX 78735 Advanced Micro Devices Desk: (512) 602-8775 Linux/Unix Systems Engineering Cell: (512) 791-0686 Global IT Infrastructure Fax: (512) 602-0468 On 02/01/11 22:54, Scott Dowdle wrote: > Greetings, > > ----- Original Message ----- >> Using the RPMs I listed does not affect the initrd (because you're >> not installing any drivers). > > Glad to hear that. My previous experiences have always been that > HP's stuff always wanted to install everything for dependencies... > including the drivers... and they were always way behind Red Hat's > current kernels... and it was basically broken. I see that some have > taken a lot of effort to figure out how HP's system works and build > modified installation setups... good for them... but that is way more > work than I want. I don't use SNMP either. > > So from your description, it is truly painless, an easy set of rpms > you install that are actually useful and work? Or are you leaving > out some pain somewhere? Your description does sound too good to be > true... but I'd like it to be true. :) > > TYL, _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
