I fixed mine by checking \windows\system32\drivers\etc\services file - it was practically empty - port 25 was missing - I copied from a known good server - done.
Re: HP Insight Event Notifier service not starting
System Managment Homepage 7.3 and Windows Server 2003
Has anyone else noticed that the last version of the System Management Homepage to work on Windows Server 2003 operating systems is 7.2.2.9? The 7.3 releases say they apply to Windows Server 2003 and Windows Server 2003 x64 and the install completes sucessfully but the page does not load (Tested version 7.3.0.9, 7.3.1.4 and 7.3.2.1). Not a big deal since we only have a few Windows 2003 servers left but I can't add the new versions to our Version Control Repository since the latest version does not work across the board. Just trying to find out if HP actually tests these before releasing.
P.S. This thread has been moved from ProLiant Servers (ML,DL,SL) to ITRC HP Systems Insight Manager Forum. -HP Forum Moderator
Re: How to view versions of SMH using SIM
Is there really no other way ? Since SMH is afected by heartbleed, i need to filter out the affected versions out of over 600+ servers.
Thanks,
Adi
SIM agent installation problems SUSE 11 SP2
Hi all,
I am trying to install the SIM agent on a SUSE 11 SP2 box and having some problems rounding up all of the required packages. So far I have installed the RPM listed below and everythig is going great, however I cannot find any of the other dependancy packages on the site. Can someone please point me in the right direction.
hp-health-9.50-1628.39.sles11.i586.rpm
I am running "rpm -ivh hp-snmp-agents-9.25-2384.9.sles11.x86_64.rpm " and getting the following error:
error: Failed dependencies:
libcpqci64.so.3()(64bit) is needed by hp-snmp-agents-9.25-2384.9.sles11.x86_64
libhpasmintrfc64.so.3()(64bit) is needed by hp-snmp-agents-9.25-2384.9.sles11.x86_64
libhpev64.so.1()(64bit) is needed by hp-snmp-agents-9.25-2384.9.sles11.x86_64
Can someone please let me know what packages I need to download off of this site to get these libraries installed, thanks!
Re: OneView replacing SIM?
I pretty much have the same information.
Note that OneView and SIM is a not a 1:1 comparison. OneView is much more and only a subset of SIM features right now. OneView is slated to be the single point of management to replace functions of VCEM, SIM. It's not a perfect conversion. You can set up OneView yourself with the downloadable appliance.
So, what's not in OneView that is in SIM today? Warranty entitlement lookups, IRS/IRSA, support for pre-G7 machines and some of the plugins from Insight Control (power management, performance management). There are also no current plans for multi-vendor support. Now, given that HP Cloud tools do support multi-vendor, it is my assumption that OneView as well, as a piece of the overall automation suite, it's just not on the current roadmap.
In my opinion, you'll keep SIM for your legacy equipment and multi-vendor stuff, but from Gen7+ onward, especially if you have enclosures or new deployments, you'll want to go OneView, but if you use IRS, i'd wait. Basically, OneView needs to catch up a bit before people can replace SIM with it. I am all for it, however - SIM is getting "long in the tooth" and was in dire need of a technology update (lose java, UI update, combine plugins into one too for better management). Plus, managing VCs and storage within OneView is great. I am looking forward to learning more at Discover..
Re: How to view versions of SMH using SIM
I didn't really have an issue with this. You can export that software report to Excel, then just filter on the SMH software column. Take those machines with the version numbers and put them into another sheet and drop them into a pivot table, or just a standard filter (or just keep filtering the entire raw list). I have over 2,000 devices and it took me about 10 minutes to get a list of machines that I sent to our security team to evaluate.
Re: HP SIM 7.2, not getting hardware alerts
I created a special event collection based off a system collection that only shows critical/major events. On this special event collection, i created an event handler that just forwards anything that drops in there. It was easier for me to manage the events this way, so if I want to change anything, i just update the collection attributes and the event handler automatically works since it forwards ALL events - the filtering is done at the collection level.
So i have a few event collections:
- Major/Critical for HP hardware (tied to an HP system collection)
- Minor/Warnings for Storage events (since the "status change" events are sometimes warnings for PFAs - very annoying)
- Major/Critical for Dell machines (tied to a Dell system collection)
The criteria for those event collections are simply the built-in event collection called 'Critical and Major' and the system collection for whatever hardware I want (or i guess, All Systems if you want - too much information for me).
How to disable an FC HBA alert on ProLiant DL380 G7
I Have HP Systems Insight Manager 7.1 Update 1 installed on a Windows 7 x64 system. I have discovered several VMWare ESXi 5.5 hosts running on HP ProLiant DL380 G7 servers. All of these servers were installed using the HP custom .ISO for VMWare ESXi 5.5, so they are running the HP agents.
I have WBEM credentials configured and it is correctly reading the hardware with the exception that it is throwing the following warning/error on all systems under the Health Status --> WBEM header on teh System Status page:
! FC HBA
If I click on the FC HBA link it generates the following detailed information:
FC HBA Ports
Port Status Port Name Controller ID Port Type Port Type Description Current State
Stopped Fibre Channel Port 1 QLogic QLE8152 Other Fabric There is a minor problem that is causing limited interference.
Stopped Fibre Channel Port 2 QLogic QLE8152 Other Fabric There is a minor problem that is causing limited interference.
FC Port Statistics
Controller ID Bytes Transmitted Bytes Received Pkts Transmitted Pkts Received CRC Errors Link Failures
QLogic QLE8152 0 Bytes 0 Bytes 35741347 24021341 1 0
QLogic QLE8152 0 Bytes 0 Bytes 35741562 24021616 1 0
I can see entries for the following under Storage Adapters in vSphere:
ISP81xx-based 10 GbE FCoE to PCI Express CNA
vmhba1
vmhba2
I assume this is the hardware causing the FC HBA events in HP SIM. I am looking for a way to stop getting these events or ignore them.
Possible solutions:
1. Filter/ignore the FC HBA within HP SIM (it is not an option under "WBEM Health Inclusion Status"
2. Disable the hardware on the VMWare ESXi 5.5 server so that it no longer registers with VMWare or responds to HP SIM WBEM query.
Anyone have steps to accomplish either of these or an alternate solution to accomplish stopping the FC HBA events?
Re: hpsmh heartbleed
Please be aware that the 32 bit Windows 7.3.2.1 version of the patch breaks the HP smh, the service starts but is not listening on 2381
smhstart_err.log show it cannot load the php5apache2.so module
Re: hpsmh heartbleed
mikj , I think I installed this on a 32bit windows 7.3.2.1 version and now when I try to open up https://localhost:2381 i get a page can not be displayed ... are you having same issue as me ?
I installed this on my windows 2003 standard version.
thanks.
Re: hpsmh heartbleed
Yes, the new(er) versions seems to break SMH and will not load.
I stayed on 7.2.2.9 for that reason alone.
Except for 2008 R2, if I install it on 2003 x32 or x64, the SMH page no longer loads.
Rather frustrating.
Links to download PSP or SPP
Hi Team,
Could anyone let me know the download link of SPP or PSP of below mentioned servers for windows 2003 to 2012:
ProLiant BL460c G7
ProLiant DL380 G7
ProLiant BL460c Gen8
ProLiant DL580 G7
ProLiant DL380p Gen8
I need to create baseline in VCRM. Thanks
P.S. This thread has been moved from Community Feedback & Suggestions to ITRC HP Systems Insight Manager Forum. - Hp Forum Moderator
Re: System Managment Homepage 7.3 and Windows Server 2003
Yep,
Noticed and stayed on 7.2.2.9 becuase of sadly.
Re: Change settings of ILO through HP SIM
NO, we can not change ILO power setting through HP SIM.
Re: How to disable an FC HBA alert on ProLiant DL380 G7
After 3 months of digging and researching, I was able to find my own answer to this.
What appears to be happening, as best I can tell, is that the VMWare ESXi kernel is detecting the QLogic QLE8152 10GB NIC as both being an iSCSI NIC device (loading system driver "qlge" for it) as well as being a Fibre Channel device (loading system driver "qlnativfc" for it). HP Systems Insight Manager sees the Fibre Channel driver loaded, but does not see any successful connectivity for it, so generates an alert (similar to what it does for NICs that aren't connected, but with no option in the "WBEM Health Inclusion Status" to Ignore it).
Solution:
Disable the "qlnativefc" system/kernel driver within VMWare ESXi.
I have tested the following against VMWare ESXi 5.5.0 (build 1331820), but suspect it will be the same/similar for other VMWare ESXi versions.
Detailed Steps
1. Enable SSH for the Host via vSphere (Configuration tab :: Security Profile :: Click "Properties" on Services window :: highlight SSH :: click "Options" :: Click "Start" )
2. SSH connect to the VMWare Host using Putty (or your favorite SSH program) and login as root.
3. Run the following command to check the status of the QLogic kernel/system drivers:
esxcli system module list | grep ql
Normal output should look something like:
qlnativefc true true
qlge true true
4. Disable the qlnativefc system driver from loading on kernel boot by issuing the following command:
esxcli system module set --enabled=false --module=qlnativefc
5. Verify that the qlnativefc system driver is diabled by running the same list command from step 3. Output should look something like:
qlnativefc true false
qlge true true
6. Reboot the ESXi Server (will not load the qlnativefc system driver on the next boot...did not find a way to unload without a reboot):
7. Re-establish an SSH connection after the host reboots and verify that the qlnativefc system driver is both disabled and did not load by running the same list command from step 3. Output should look something like:
qlge true true
qla2xxx true true
qlnativefc false false
NOTE: Not entirely sure why it started loading a new qla2xxx driver after I disabled the qlnativefc driver...could be a lower detect order driver in the kernel that matches the same hardware id string as the qlnativefc driver. In any event, having it load did not cause the same HP SIM alerts for "FC HBA".
Re: FC HBA - There is a minor problem that is causing limited interference
After months of struggling with narrowing this down, I actually found a solution to the problem (at least for my servers). I had to disable the "qlnativefc" system driver within VMWare ESXi and reboot the host and then the problem goes away.
I have posted full details of the problem and fix at the following URL:
Re: Blade server FC HBA minor alert
After months of struggling with narrowing this down, I actually found a solution to the problem (at least for my servers). I had to disable the "qlnativefc" system driver within VMWare ESXi and reboot the host and then the problem goes away.
I have posted full details of the problem and fix at the following URL:
Re: hpsmh heartbleed
Hello: To All,
HP is committed to delivering secure systems that effectively manage our invaluable customer and employee data. Therefore we kindly request you to reach out to our Software Security Response Team (SSRT).
Kindly find the given below "Report a potential security vulnerability to HP" link, If any claims you people have been impacted and/or have details where you can share with HP -
https://h41268.www4.hp.com/live/index.aspx?qid=11503
Re: Adding a server in SIM
ich ip is that ILO or system IP?
Re: Systems Management Home Page shows No Items
hI, could you tell me when I add Proliant DL series servers to HP SIM,whis IP do I have to give in discovery section?
(Ping inclusion ranges, system (hosts) names, and/or hosts files )
is that ILO IP ? or system IP?