Hello! I have problem with SIM 7.6 and  DL380 G7 (windows 2012 R2). Storage show "the current state can not be determined". Look the picture. What a problem?

We have HP SIM 7.6 latest hotfix etc. I have VCRM 7.6.3.0 setup, added into HP SIM and the latest SPP uploaded as a baseline.

How do I now get all the servers in HP SIM to report their software/firmware status, servers have baseline assigned but software status unknown.

Do I need VCA agent as some posts say HP dropped it, I can't find an ESXi one and people say WBEM.

What do I need to do next to get the servers scanned and reporting in HP SIM? Mixture of 2003, 2008, 2012, ESXi 6 etc.  OS

We've been using SIM for a few years and initially it worked well.

more recently we've found that it's not been alerting us of disk errors but seems to alert for other things like failed login attempts, or discovery failures so the email alerting side is working ok.

the servers IML (via ilo4 login) is showing degraded array/failed disk and SIM is showing Health Status > SNMP > Drive Array as a yellow warning triangle, however it simply isn't triggering an event to email us.

fwiw, servers are bl460c gen8 and a dl380p gen8; both have the same issue.

we're currently on 7.6+feb18 hotfixes.

Originally, i was thinking it's a broken install so i've completely removed 7.5, wiped the sql DB, installed 7.6 fresh with a new DB but problem remains.

Could i have missed something re-configuring things? it does feel like something simple and obvious but cant find much info to help diagnose what i've missed or where to look.

thanks for any help

Hi, I have two HP DL380p Gen8 servers...., 3-4yrs old now...

I want to be able to get hardware alerts from these two servers via email for free...

Could someone help me, as over the years I've got "lost in the plot" with how to get alerts for these servers.. I was so simple back in the the mid 2000's, but now, I don't have a clue what I need to install

Both servers are Windows 2012 R2 Hypervisors running Hyper-V, really simple setup, nothing complicated..

"Free" is the word here...

If anyone can point me to what I need to download and install, I can work the rest out and I will be eternally grateful..

Thanks in advance..

Hallo,

wir haben ein neuen ML350 Gen 9 gekauft und Server 2k16 installiert. Nach der Installation habe ich Framework 3.5, SNMP Dienst und HP SIM installiert. Bei dem Dienst habe ich unter Security den "public" mit Leserechte hinzugefügt. Leider bekomme ich keine Daten vom Server wo ich den Status etc. sehe. Hoffe jemand hat eine Idee weil im Netz finde ich nur den Fehler mit den public, was ich getan habe.....

Hi,

I have just installed a new fresh HP Insight Manager 7.6. I have created a discovery job to discover all my enclosure and it works fine except for one enclosure.

The most relevant error i have is : The system responds to the HTTP request but cannot get the XML
output.

When connected on the OA of this enclosure i can see teh XML using URL https://IPADDRESS/xmldata?item=all.

Thanks for your help.

We have 16 servers which are continuously being blocked by Access Protection from McAfee in relation to the HP Insight Foundation Agents process 'CQMGHOST.exe' and as per the article from McAfee https://kc.mcafee.com/corporate/index?page=content&id=KB87659 and various support calls they are stating this a HP issue and HP will need to provide a fix\exclusion list to resolve this.

Has anyone else experienced this issue and how have you resolved it as being shunted between McAfee and HP at the moment?

I initially was having some SIM issues, including the discovery page not loading & system tasks page not loading - they just don't respond to clicks regardless of browser.  I found out there were >700k "informational' events in the SIM database - I had been cleaning the higher level ones but wasn't paying attention to the informational ones. 

I cleaned them all out using a SQL command & shrunk the database when finished.  I'm working on permanently cleaning up the systems that are spamming info events (ESX hosts on blade hardware), but for now I'm just deleting them every couple of days.

Once the initial cleanup was done, I ran "mxinitconfig -a" & restarted SIM & it worked well for a couple of days.  But now when I go to click on the name of a blade chassis in a collection, instead of taking me to the page for the chassis it just does nothing.  Restarting SIM will fix it temporarily, but even with the db cleanup it takes an hour or more to initialize when restarted.

Has anyone else seen this & is there a fix besides restarting SIM?  Looking at eventually upgrading to 7.6 or newer, but that requires new SQL server software I believe (Running SQL 2008).   This is all older stuff that will retire in the future so hence it running the older software.

Thanks!

Just wondering if anyone has seen this issue before & if you were able to work around it.  Thanks!

I'm trying to reinstall SIM 7.6. I was able to uninstall the previous instance but it did not remove the old database (which I want it to do). When I try to run the install I get as far as the database selection and there doesn't seem to be a way to just start fresh with a new database. It detects the old one but I have no idea what the password is. I can't simply uninstall the SQL server beacause other programs are using it. All I want to do is start with a fresh database. How do I do that?

Hi,

I have the following environment:

1- Windows Server 2012 R2

2- HP SIM 7.5.0

3- HP SMH 7.5.1

4- HP VCRM 7.5.3.0

5- IE 11

The service for the HP VCRM is always having the status "starting" and consuming CPU time always (as if it is trying to do something). I have tried to kill the process "cpqsrhmo.exe" but it then tries to start again with the same symptoms.
On the other hand, the HP SMH won't open on the IE although it initially responds and asks me to continue with the self-signed certificate.
So, what could be the reason for this behavior? And how I could possibly troubleshoot it and resolve it?

Thanks you in advance,

Hello,

adding Integrity server running HPUX 11.31 as managed hosts to HPE SIM CMS (HPE SIM 7.6) running under HPUX 11.31 too, no ILO links

Integrated Lights-Out 3 (iLO 3) for Integrity

can be found on System Page for added hosts on customer system,. whereas they exist on LAB system. How can I check for the reason of missing links, and how can these links be added?

It’s important to implement Security Best Practices to protect the iLO Management Interface in your ProLiant servers. With security a key concern in all aspects of data center—including remote management—we have created the HPE Integrated Lights-Out Security Technology Brief which describes the firmware and hardware methods iLO uses to protect against the risks of unauthorized access. It also describes utilities and services providing access points into iLO and its host system, and offers recommendations for configuring iLO security parameters and iLO connectivity options.

-Vajith

I am not sure if this is the correct place to post this but I'm gonna do it anyways.  I recently setup HP Insight Manager. I was wondering if its possible to manage/update my HP printer firmare and also my HPE 2530 Series switches? If so how? I have added them into inventory and my scans recongize them as printers and switches but i cant seem to create a repository for them.

I have a GEN10 server that will not associate with the iLO when I add the iLO to HPE SIM.  I get this error message:

The discovered management processor is not associated with its server. Verify that the supported management processor firmware version is installed.

I have updated the iLO to the latest version (1.30) and just patched HPE SIM this morning to 7.6 June Hotfix, but it still will not work,  I have tried rebooting the server, the iLO, and cold-booting the iLO (pulling the power cables out of the server),  The AMS service is running and appears heathly.  I am not seeing any events related to this type of problem in either the iLO event logs or the Windows event logs.  I dont see any driver errors when I open device manager in Windows.  The CHiF is installed and shows normal in device manager.

There is a firewall between the Server/ILO and the SIM server, but not one between the iLO and the server itself (plus the AMS should eliminate the need for network communication between the two anyways).  I can discover the iLO no problem in SIM...it just will not associate to the server when I do the discovery.  So since I can discover the iLO, I dont think it is a FW issue.

Any suggestions.

NK

Please excuse this basic question, but I'm new to HPE SIM and I've been having a terrible time with it and HPE giving me the runaround so I thought I'd come here.

Within the Options, Discovery, General Configuration Settings, Even if I enable discovery filters, all the the system types are still greyed out and I cannot select any of them.

We've got C Calss Chassis, BL servers running ESX 6.0 as VMWARE hosts, DL servers, and some ML servers. Does anyone have advice or best practices for General Settings for All Discoveries ?

Thanks

Hi,

I'm running a single physical server (HPE ProLiant ML350 G9) running Windows Hyper-V Server 2016 (essentially the same as Windows Server 2016 Core with the HyperV role).  That in turn hosts a couple of Windows virtual servers (the usual - AD, file, print etc.).  I'm trying to find the best way to automate the monitoring of the underlying HPE hardware (e.g. looking out for failed disks, PSUs etc.).

I've got remote agents monitoring the virtual servers, and if the underlying hypervisor was VMWare running the HPE custom image and hence HP VIBs, I'd use standard CIM\WBEM\PowerCLI queries to interograte the VMWare host via the virtual machine.

With my HyperV setup I can install my remote agent directly into the host OS, but then need a way to query the hardware (i.e. some sort of HP tool\integration).  I've looked at various things like the Agentless Management Service (seems to be too big for what I need and relies on SNMP traps and\or email alerting) and Insight Management WBEM Providers (doesn't seem to want to install, so maybe isn't compatiable with a Core MS Server OS?).

I've got more experience with Dell server hardware and know that their OMSA tool would do the job beautifully - it can be installed on to the host OS (including Server Core), and will capture alerts\warnings and write them to the Windows Event Logs (which my remote agent will then pickup).  I'm hoping there's a similar HPE software suite available that I don't know about!

Any thoughts would be valued.
Thanks in advanced!

Hallo!

Gibt es eine Möglichkeit über die Seriennumer oder der Bezeichnung eines Servers das Alter heraus zu finden?

LG Roland

Hi all,

I am the lucky guy who is assigned to migrate our current HPSim 7.6 server from Windows server 2008 R2 to a new 2016 server. This new server also is joined to a different domain.

I am wondering how to complete this migration. From what I have read in the documentation the two servers for the migration must be in the same domain. Is this really true?

Little scetch of the situation. We monitor around 200 servers (all HP) from our customers locations over site-to-site VPN tunnels. So servers which are monitored are not in the same domain and are being scanned over both WBEM and SNMP.

Is the correct approach to install / configure a new Windows server with HP SIM 7.6 and SQL server and use the mxexport / mximport tool to migrate the data or is this too easy and am I missing a few steps?
Hope to hear from you!

HP SIM 7..5

Host is BL460c G7 blade running CentOS 6, & has MCP 10.5 installed (all packages installed)

Discovering system completes with major error.  Logging into HPE SMH shows NULL hardware model, & missing most information

Discovery log below.  System is running dmidecode, & here are all of the packages installed

[root@hostname hpsim]# rpm -aq | grep hp

hponcfg-4.6.0-0.x86_64

hpdiags-10.60.2109-2176.x86_64

hpsmh-7.6.0-11.x86_64

hp-health-10.50-1826.38.rhel6.x86_64

hp-ams-2.5.2-2297.2.rhel6.x86_64

hp-snmp-agents-10.50-2926.39.rhel6.x86_64

hp-smh-templates-10.5.0-1462.26.noarch

[root@hostname hpsim]# rpm -aq | grep ssa

ssacli-2.60-19.0.x86_64

cyrus-sasl-gssapi-2.1.23-15.el6_6.2.x86_64

ssa-2.60-18.0.x86_64

ssaducli-2.60-18.0.x86_64

 

********* Significant issues and overall target discovery/identification
status:
Major: The system cannot be identified properly for HP SIM to manage;
unable to get one or more of the following: model, serial number or
unique identifier (UUID). For management processors, verify the
system is running the latest firmware. For Linux based operating
systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root
sign-in credential. For HP-UX, verify the sign-in credential. For
Windows, check if WMIMapper is configured correctly on the CMS and
verify the sign-in credential.


********* Additional results (listed for information only):

* Starting identification process...
* Checking for known running web servers...
* Checking for SNMP protocol support on system...
Normal: The system responded to an SNMP request; it supports SNMP Protocol
and has a valid read community string.
* Checking for SNMPv3 protocol support on system...
Normal: The system did not respond to SNMPv3. Verify security settings and
v3 credentials in Options->Security->Credentials->System
Credentials
* Running HP ProLiant management agent identification...
Normal: The ProLiant SNMP Foundation agents for servers are not installed
or are not configured.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: This system does not have the common cluster MIBs support.
* Checking for WBEM protocol support on system...
Minor: This system does not have any SMI-S CIMOMs installed. No storage
systems will be found on this system.
Minor: The Central Management System (CMS) cannot communicate with the
CIMOM locally installed on the managed system using the WBEM
protocol, Identification will try to identify Windows systems using
the WMI Mapper as proxy; for Linux and HP-UX systems, check
credentials by going to Options->Security->Credentials->System
Credentials. For Linux systems also check if the HP WBEM provider
is installed.
* Running WBEM rules based identification...
Minor: Identification cannot get computer system hardware data from the
WBEM / WMI providers.
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
Identification...
Normal: The system is not a VM Host (non HP Integrity VM Host), or WBEM
credentials may not be specified so skipping VM Identification.
* Running Storage identification...
* Did not detect the WBEM protocol support on this system. SMI
storage identification will be skipped.
* Storage identification completed.
* Running HP NetServer identification...
Normal: System supports the NetServer SNMP agent, adding system type.
* Running HP-UX SNMP identification...
Normal: System does not have the HP-UX SNMP agents installed.
* Running OA Identifier which will discover systems in an enclosure
if the automatic enclosure discovery option for OA is enabled...
Normal: The system is not an Onboard Administrator, skipping automatic
discovery of systems in the enclosure.
* Running XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
* Running iLO Identifier which will discover the server if the
automatic server discovery option for iLO is enabled...
Minor: The system responds to the HTTP request but cannot get the XML
output. It is normal for servers not to get the XML data.
Minor: If the http communication from CMS to target is working, but if it
is found to be slow then try increasing the Default connection
timeout parameter for http in global protocol settings.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Running SSH Protocol identification...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Minor: The system cannot be logged in using SSH protocol; check
credentials or check the settings in the SSH configuration file
* Running WS-Man identification...
Minor: The system did not respond to WS-Management (WS-Man) request.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Checking for System Management Homepage and other HP web agents...
Normal: The system is not a server, storage or desktop. Skipping the check
for System Management Homepage.
* Running HP Serviceguard Identification...
* Running SNMP System Type manager ...
Normal: No matching SNMP System Type Manager rule for sysObjID was found.
* Running SNMP subtypes identification...
* No additional subtype(s) found from SNMP.
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Skipping Virtual Center Identifier.
* Running HPE Synergy identification...
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
Minor: The Secure Shell key-based access authentication is not configured
on the system(s).
Minor: System Management Homepage (SMH) is not installed or is not
responding on the system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.