Critical: The managed system is not reachable.

[Sands15]

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.

[shocko]

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

[Sands15]

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

[BPE]

What is the result of the discovery inside sim?

did you allow snmp access from the sim server?

[Sands15]

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.

[Sands15]

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.


                       

[BPE]

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.

[Sands15]

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

[BPE]

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

[Sands15]

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

[BPE]

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.

[Andrew_Haak]

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

[Sands15]

Could you please ellaborate more  with steps explained?

[Sands15]

Hi,

I need to set community and traps through windows GPO.

[Andrew_Haak]

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

[Sands15]

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.

[Andrew_Haak]

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

[Sands15]

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..

[Andrew_Haak]

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

[Sands15]

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

[Andrew_Haak]

Hello again,

Does the System management homepage work on the systems you applied the gpo to? Is the datasource snmp or wbem?
When you export the registry on the working server and then import the registry in one of the not working servers restart the snmp agent does it work then? When you restart the snmp service the other hp services should be dependand on snmp and also restart. Can you mail the snmp screen of the server that does not work.

Is the firewall turend off or is port 7,2301, 2381 and 161 opendeed on the server you want to discover?

Kind regards,

Andrew

[Sands15]

Yes, system management homepage is working fine and its accessible from SIM server also.

The database used is SNMP.

I have copied registry from one server and applied it from GPO on other system.
HP services are dependable on SNMP and also HP services are restarting with SNMP.

I dont think its an firewall issue as the configuration is working fine when SNMP settings are appied manually.

[Andrew_Haak]

Hello,

The discovery log shows that either snmp is unreachable or configured wrong. You could as a last resort try a tool like

http://www.snmpsoft.com/freetools/snmpwalk.html

If this or any other snmpwalk tool does not work the problem clearly is the server(s) you want to discover.

kind regards,

Andrew

[Sands15]

Getting following output from SNMPWALK:

%Failed to get value of SNMP variable. Timeout.

[Andrew_Haak]

Hello again,

Guess than that the destination is not reachable, if you do the same for the system that works in SIM do you get reply?

kind regards,

Andrew