topic Re: Issues with Discovery of RedHat 5.3 Server in Server Management - Systems Insight Manager

Issues with Discovery of RedHat 5.3 Server

JDM_Nokia — Tue, 22 Jan 2013 21:42:23 GMT

I have a Proliant DL360 G3 running RedHat 5.3. I am having some issues with getting the SIM discovery working correctly.

Here are the details of what I have loaded on the server (NOTE: All packages were taken from PSP 8.63):

he-health-8.6.3.1-2

hpacucli-8.70-8.0

hponcfg-3.1.0-0

hpsmh-6.3.0-22

hp-snmp-agents-8.6.3.3-2

hp-smh-templates-8.6.3.1-1

cpqacuxe-8.60-7.0

hpdiags-8.6.0-18

All of these packages were installed so that I could get the SNMP portion of System Management Homepage (SMH) up and operational. SMH is working fine.

Below is a snippet of the errors that I am getting when I run a manual discovery on the RedHat Linux server in question. I have highlighted three things that have caught my eye. I was hoping that someone might be able to provide me with insight as to whether these need to be installed or can safely be ignored.

1) The ProLiant SNMP Foundation agents for servers are not installed
or are not configured.

2) This system does not have any SMI-S CIMOMs installed

3) The Central Management System (CMS) cannot communicate with the
CIMOM locally installed on the managed system using the WBEM
protocol

Appreciate the help!

********* Significant issues and overall target discovery/identification
          status:
Minor:    The name of the system could not be resolved to a fully qualified
          domain name. For a Windows CMS, make sure that the domain name of
          the managed system is included in the DNS suffixes in the Windows
          Advanced TCP/IP Settings page.
Minor:    The reverse DNS lookup using the IP address returns
          daects01-m.americas.nokia.com. However, the forward DNS lookup was
          not successful because HP SIM could not get the fully qualified
          domain name for the system being discovered. In HP SIM, the fully
          qualified domain name for the system will be empty. Verify that the
          system name is in the forward lookup table in the DNS server
          configuration, or that the fully qualified domain name and its IP
          address are in the host file.
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.
        * 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...

Re: Issues with Discovery of RedHat 5.3 Server

Tushar Bajpai — Wed, 23 Jan 2013 05:42:18 GMT

check if the snmp services is running: services snmpd status

1) Check for Community String configured in snmp.conf

2) Check if there is restriction for snmp reponse i.e (in that case CMS IP should be added to snmp.conf)

Re: Issues with Discovery of RedHat 5.3 Server

JDM_Nokia — Wed, 23 Jan 2013 16:39:11 GMT

Thank you for your reply.

I did verify that SNMP is running. I also believe that I am not being restricted from querying data from the Linux box.

I installed an SNMP tool called MIB Browser (ireasoning.com/mibbrowser.shmtl) onto the same windows box where I have SIM loaded. Using this tool, I can do an SNMPWALK to a remote server. I am able to do this to my Linux server and get data back. The intersting thing is that I do not get as much data as I thought that I should get (see attachment DAECTS01.xml). The reason I am saying this is that when I run a SNMPWALK against a Windows 2003 server, I get tons more data back (see attachment DAEBU40.xml).

Not sure this means anything more than that SNMP is working, but it did catch my eye.

As I did say in my first post, System Management Homepage is using SNMP as its data source on the Linux box.

Thoughts?

Re: Issues with Discovery of RedHat 5.3 Server

Tushar Bajpai — Thu, 24 Jan 2013 08:14:58 GMT

Sorry missed 1 thing, HPSIM has found SNMP on the managed system, but is complaining about the HP management Agent. Either they are not installed or not running. But in your case they are installed as you stated earlier.

Use the command to get the status: service hp-snmp-agents status |start | restart

iReasoning has the capability to store the data in XML format, I can see only MIB-2 response in that but no response from the HP management Agents. With Ent OID 1.3.6.1.4.1.232.

Re: Issues with Discovery of RedHat 5.3 Server

JDM_Nokia — Thu, 24 Jan 2013 16:45:52 GMT

Thank you again Tushar for your post.

I believe that I have a Nokia firewall (Windows firewall is off) issue. When I ran my SNMPWALK from the SIM server using the parameters .1.3.6.1.4.1.232, I received the error "No data available". I then installed the iReasoning software onto the Linux server and ran their command line SNMPWALK command, ie:

snmpwalk localhost .1.3.6.1.4.1.232

and received back all of the info that I expected to see.

I ran a traceroute between these two servers and sure enough a firewall is between the two servers. I believe that UDP 161 needs to be open. Are there any other ports that need to be opened as well?

Thanks!

Re: Issues with Discovery of RedHat 5.3 Server

JDM_Nokia — Fri, 25 Jan 2013 20:39:46 GMT

I have resolved this issue. I needed to add a line into the "/etc/snmp/snmpd.conf" file for the HP Management Agents. Specifically, I had to add the below in red. Once this was added, the MIB Browser as well as SIM was able to query data from the HP Management Agents.

I seem to recall that one of the HP Management Agent installation processes asked a bunch of SNMP-type questions. I am not sure if adding the below info to this file was one of those options.

Hopefully someone might be able to add some insight to this. I will leave this incident "open" for a few days to allow for additional comments.

     # First, map the community name "public" into a "security name"

     #       sec.name source          community
     com2sec notConfigUser default       public

     ####
     # Second, map the security name into a group name:

     #       groupName      securityModel securityName
     group   notConfigGroup v1           notConfigUser
     group   notConfigGroup v2c           notConfigUser

     ####
     # Third, create a view for us to let the group have rights to:

     # Make at least snmpwalk -v 1 localhost -c public system fast again.
     #       name           incl/excl     subtree         mask(optional)
     view    systemview    included   .1.3.6.1.2.1.1
     view    systemview    included   .1.3.6.1.2.1.25.1.1
     view    systemview    included   .1.3.6.1.4.1.232

     ####
     # Finally, grant the group read-only access to the systemview view.

     #       group          context sec.model sec.level prefix read   write notif
     access notConfigGroup ""      any       noauth    exact systemview none none