Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

R2 Server Core DL360 G7 Server Unknown in SIM 6.3

 
SOLVED
Go to solution
Highlighted
Occasional Visitor

R2 Server Core DL360 G7 Server Unknown in SIM 6.3

Hi All

 

I hope you can provide some advice to an issue I'm having.  This is the first server core machine I have built on a DL360 G7, it will not identify itself correctly in my HP SIM 6.3 running on Windows 7.

 

- SSH is disabled, so I don't expect any results from there

- SMH works fine over :2381 with a certificate trust setup with my HPSIM machine, version control works fine

- using wmic /node:"myserver" bios get serialnumber it returns the serial OK

- I have tried with firewall disabled

- I have others DL360 G7 running full Windows OK

 

The only difference here is Server Core, any suggestions?

My ID log below:

thanks for any advice

 

********* 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.
Critical: The system(s) can not be identified by WBEM, SNMP or SSH

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

        * Starting identification process...
        * Checking for known running web servers...
        * Checking for System Management Homepage and other HP web agents...
Normal:   System Management Homepage (SMH) is installed or is responding on
          the system(s).
        * Checking for SNMP protocol support on system...
Normal:   The system did not respond to SNMP. Verify security settings and
          community strings in Options->Security->Credentials->System
          Credentials
        * Running SNMP System Type manager ...
Normal:   The system does not support SNMP.
        * Running SNMP base cluster identification using common cluster
          MIB...
Normal:   This system does not have the common cluster MIBs support.
        * Running IPMI protocol identification...
Normal:   IPMI protocol not detected so skipping IPMI Identification.
        * 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 WS-Man identification...
Major:    WS-Management(WS-Man) is globally disabled so skipping WS-Man
          identification.
        * Running HP ProLiant management agent identification...
Normal:   The system does not support SNMP.
        * Running HP NetServer identification...
Normal:   The system does not support SNMP.
        * Running HP-UX SNMP identification...
Normal:   The system does not support SNMP.
        * Running SSH Protocol identification...
Major:    Using SSH Protocol in discovery is disabled on the Central
          Management Server (CMS).
        * Running SSH Identification...
Major:    Using SSH Protocol in discovery is disabled on the Central
          Management Server (CMS).
        * Running Storage identification...
        * Did not detect the WBEM protocol support on this system. SMI
          storage identification will be skipped.
        * Storage identification completed.

6 REPLIES 6
Highlighted
Honored Contributor

Re: R2 Server Core DL360 G7 Server Unknown in SIM 6.3

What about SNMP settings? Check under Security Settings that Accept SNMP packets from these hosts is selected, but that your SIM server is in the list below... By default there is only localhost, now there should be at least 2 entries...

 

Do you only have an issue with this server? Is SIM recognizing other servers succesfully?

--------------------------------------------------------------------------------
If my post was useful, clik on my KUDOS! "White Star" !
Highlighted
Occasional Advisor

Re: R2 Server Core DL360 G7 Server Unknown in SIM 6.3

make sure you have provided valid SNMP community string in the credentials and also check the box "If these system credentials fail, try other credentials that may apply. This may impact performance" under sign-in System Credential

Lastly, have you tried installing WBEM providers and running discovery again?
Highlighted
Occasional Visitor

Re: R2 Server Core DL360 G7 Server Unknown in SIM 6.3

Thanks for the suggestion, I forgot to say that valid SNMP info was added during install.  I've looked in the registry and can see the strings and management station in there.

 

When I use the SMH it uses WBEM (I've changed to SNMP and tried discovery) so it shoud be good.  I have re-installed the agents from PSP.

 

The management station has several other servers, including DL360 running 2008R2 Std and that's all good.

 

The weird thing is the repairs fail:

WBEM protocol settings are not valid/enabled for this system in HP SIM. Check yo
ur HP SIM settings for identification via WBEM.
Subscribe to WBEM / WMI Indications ................................. [FAILED] 


HP Systems Insight Manager was unable to install the target's HP Repair Tool ser
vice.  This could be caused if another instance of the tool is currently running
.  Retry at a later time.

 

Is this something to do with Server Core, are others managing Server Core installs with HPSIM OK?

 

thanks again

Highlighted
Occasional Advisor

Re: R2 Server Core DL360 G7 Server Unknown in SIM 6.3

I would suggest you do the following

Remove the server from HP SIM
Uninstall SSH if you have one installed
Make sure you have WBEM installed
Enter Credentials for WBEM, make sure you have the account used in sign-in credentials are in the administrator group
Run discovery

Just to let you know that i also had the error about the HP Repair Tools Service and uninstalling SSH fixed this for me, may be this is not valid in your environment
Highlighted
Esteemed Contributor

Re: R2 Server Core DL360 G7 Server Unknown in SIM 6.3

Did you check the support matrix?  Bug or Feature;-)

 

What happens if you send a test trap using the SMH of the system to your SIM server?

If you see the trap inside SIM you could be sure that the there is no IP config problem.

At least in one direction.

I saw once 2008 Windows which did not send the trap due to some IPv4/IPv6 config errors.

 

 

 

 

Highlighted
Occasional Visitor
Solution

Re: R2 Server Core DL360 G7 Server Unknown in SIM 6.3

As it's always useful for an update, here's how I fixed my mistakes ;-)

 

Built a Windows R2 Std in a VHD, that identified by SNMP with no problem after a repair.  Exported the SNMP from that into my server core and it worked fine, so there must have been something bad with my orginal import.

 

WBEM on closer invetigating is looked like all the other servers were using SNMP not WBEM, so there was a problem with my HPSIM.  Closer look at WMI Mapper Proxy on my HPSIM machine and the IP address was incorrect!

 

So all is good with my Core install now, thanks for the pointers.