topic Re: Critical: The managed system is not reachable. in Server Management - Systems Insight Manager

Critical: The managed system is not reachable.

Sands15 — Tue, 14 Jan 2014 20:47:41 GMT

Hi,

I am not able to discover a new server in HP SIM.
I have just installed the server.
I have installed PSP package and configure SNMP service on new server.
I am able to see listning port of HP on new server.
I am able to access the SMH homepage of the new server from CMS server.

I am getting below error while discovering new server with status FAILED:
Critical: The managed system is not reachable.

Please help regarding the same.

Re: Critical: The managed system is not reachable.

shocko — Wed, 15 Jan 2014 09:42:07 GMT

Check that the CMS can resolve the FQDN of the server you are trying to discover. Post the full discovery results.

Re: Critical: The managed system is not reachable.

Sands15 — Wed, 15 Jan 2014 18:18:37 GMT

CMS able to resolve the FQDN.
Full Discovery result:
Critical: The managed system is not reachable.

Re: Critical: The managed system is not reachable.

BPE — Wed, 15 Jan 2014 18:46:19 GMT

What is the result of the discovery inside sim?

did you allow snmp access from the sim server?

Re: Critical: The managed system is not reachable.

Sands15 — Wed, 15 Jan 2014 18:55:42 GMT

Discovery result inside SIM:
Critical: The managed system is not reachable.

Yes I have allowed SIM server in SNMP settings
Same SNMP settings are working on other servers.

Re: Critical: The managed system is not reachable.

Sands15 — Wed, 15 Jan 2014 19:58:49 GMT

When I swtched off public firewall of the server, I am getting following output:

********* 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 did not respond to SNMP. Verify security settings and
          community strings in Options->Security->Credentials->System
          Credentials
        * Running HP ProLiant management agent identification...
Normal:   The system does not support SNMP.
        * Running SNMP base cluster identification using common cluster
          MIB...
Normal:   SNMP is not supported or globally disabled, skipping SNMP cluster
          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 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:   The system does not support SNMP.
        * Running HP-UX SNMP identification...
Normal:   The system does not support SNMP.
        * 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.
        * 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...
Minor:    The system(s) do not have Secure Shell (SSH) installed or it is not
          running on the managed system(s).
        * Running SSH Identification...
Normal:   SSH Protocol is not enabled so skipping SSH Identification.
        * 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:   The system does not support SNMP.
        * Running SNMP subtypes identification...
        * 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 MxVirtualCenter Identifier
        * Running Virtual Machine Management (VMM) Plug-in Identification...
        * System did not pass the discovery filter and will not be added.

Re: Critical: The managed system is not reachable.

BPE — Wed, 15 Jan 2014 21:14:41 GMT

I guess in this case you have a IPV4/V6 confusion.

Try a ping from the sim server and check the address try a nslookup of the server name.

I once saw that the return of packets did not work due to W2008 IP V6 settings.

Re: Critical: The managed system is not reachable.

Sands15 — Wed, 15 Jan 2014 21:35:05 GMT

I have checked both NSlookup and ping results
Both are perfect.

Re: Critical: The managed system is not reachable.

BPE — Wed, 15 Jan 2014 21:47:37 GMT

If you have HP IRS installed you can open a case at HP., because your HW alerting is not possible. Such questions are supported if you have HW support or HW warranty.

HP SIM has the possibility to check SNMP acces under theOptions manage system type

Re: Critical: The managed system is not reachable.

Sands15 — Wed, 15 Jan 2014 22:08:46 GMT

Please find the below screenshot after checking SNMP acces under theOptions manage system type

Re: Critical: The managed system is not reachable.

BPE — Wed, 15 Jan 2014 23:14:33 GMT

Do you have NAT between the system and your SIM Server? SNMP has problem to handle network address translations.

If it is possble I would test snmp access with allow any system in the security property of the SNMP Service.

I also would use the ip address of the sim server and the managed system in the access list. After you get a SNMP ID back you can run the identify system again.

If your managed system is not on the same subnet as your sim server you have perhaps a router which does not forward the SNMP traffic. Check with your network people or use wireshark and compare the answer of a good system and your not reachble sytem using the SNMP system type check.

Re: Critical: The managed system is not reachable.

Andrew_Haak — Fri, 17 Jan 2014 20:28:38 GMT

Hello there,

You could also do a repair for the server to set a SNMP read and write comunity. To do this you will need sign-in credentials.

Kind regards,

Andrew

Re: Critical: The managed system is not reachable.

Sands15 — Sat, 18 Jan 2014 07:40:44 GMT

Could you please ellaborate more with steps explained?

Re: Critical: The managed system is not reachable.

Sands15 — Sun, 26 Jan 2014 02:22:49 GMT

Hi,

I need to set community and traps through windows GPO.

Re: Critical: The managed system is not reachable.

Andrew_Haak — Mon, 27 Jan 2014 07:17:34 GMT

Hello again,

That's an option, that way you have your SNMP set automated, you can also set the WBEm substription in a GPO. All you have to do is set the wbem seeting by a powershell script or VBS. The other option is the repair option in SIM, but the SNMP set is an manual thing you would do every once in a week or month. The GPO is set every time the server boot and you have to group your servers in your AD. Otherwise alle server (including virtuals) get the subscription.

By default your virtuals would then also be added to SIM. If that's nu problem to you you could use this option. If you don't want virtuals in your SIM server you can set an option in SIM under Options > Discovery and click the Configure General Settings. Here you can uncheck the first option "Automatically discover a system when an events is received from it". But then again if that does not bother you now you also have an auto add for alle servers that send a SNMP trap to the SIM server. If you want to use the repair option for SNMP you select the servers you want to repair, select Configure > Configure or Repair Agents. Click on next and set the Configure SNMP options. The first could be Public or anything other that you want to use for your readonly string. When you select the Set traps to refer to this instance of Hp Systems Insight Manager a write string is created unique for every individual host. Last you set where he server has to send it's traps to in can of an allert. For WBEM you choose Options > Events > Subscribe to WBEM Events, as target you could choose All Servers collection now you can Schedule this job to run automaticly every week or any other timeframe.

Kind regards,

Andrew

Re: Critical: The managed system is not reachable.

Sands15 — Mon, 27 Jan 2014 08:45:09 GMT

Hi,

I need to configure group policy with SNMP service only. I dont want to use WBEM. I problem I am getting is when I implement group policy manually its working fine but when I tried to implement the same settings through GPO, SNMP stops communicating with SIM server.

Re: Critical: The managed system is not reachable.

Andrew_Haak — Mon, 27 Jan 2014 18:01:57 GMT

Hello again,

Did you export your registry and used that in a vbs script? Can you share what you put in your script.

Kind regards,

Andrew

Re: Critical: The managed system is not reachable.

Sands15 — Tue, 28 Jan 2014 10:11:25 GMT

I am exporting the registry from a working server and applying the same settings through GPO and also applying the same setting from Network\SNMP GPO to other servers..

Re: Critical: The managed system is not reachable.

Andrew_Haak — Tue, 28 Jan 2014 10:24:19 GMT

Hello,

did you export the registry settings of a server that got it's config from the gpo and compared it to the original?

You could try a restart of the snmp service to reload the registry you just changed.

Kind regards,

Andrew

Re: Critical: The managed system is not reachable.

Sands15 — Tue, 28 Jan 2014 10:37:23 GMT

Yes I have export and apply it from GPO along with I also configured the same SNMP setting under Netrwork thorugh GPO.

I have also compared from original..it seems to be identical.

I have already restarted to apply GPO effectively.

but still no luck