Start a Conversation

Unsolved

This post is more than 5 years old

1086365

December 1st, 2011 09:00

How to configure OMSA/SNMP on Linux

There have been some questions on how to check that your server is properly set up to use SNMP with OME.  Linux is a bit more complicated than Windows.  Some info below.

Rob

EDIT below: Note trapsink should be lower case :)

Trapsink

trapsink

 

----

Linux Configuration for SNMP and OMSA

Overview
This tutorial will guide you through the steps required to install Dell OpenManage Server Administrator (OMSA) and configure SNMP on Linux servers. These components are required for OpenManage Essentials to properly discover, inventory, and receive alerts from your Linux servers.

You will need to complete the following steps for all your Linux servers:

1. Install Net-SNMP for your specific version of Linux
2. Install OMSA dependencies
3. Install OMSA
4. Verify OMSA SNMP settings
5. Install Inventory Collector on 64-bit servers
6. Configure the SNMP Community string
7. Configure trap destinations
8. Enable SNMP Access for remote hosts (SUSE Linux only)
9. Configure Linux firewall settings

Install Net-SNMP
You must install the Net-SNMP agent that is provided with your Linux distribution prior to installing OMSA. Otherwise, you will need to manually update the snmpd.conf file or reinstall OMSA after the SNMP install.

Make sure the SNMP service is started:
/etc/init.d/snmpd


Install OMSA Dependencies
Note: OMSA is supported only on Red Hat Enterprise Linux and SUSE Linux Enterprise. Please review the latest Dell OpenManage Software Support Matrix for supported Linux operating systems. You can install OMSA on all Linux systems even if the server is not supported, however complete functionality is not guaranteed.
OMSA requires several dependency RPMs for remote enablement support. Ensure these RPMs are installed prior to installing OMSA. The RPMs are available in the following directory:
linux\RPMS\supportRPMS\opensourcecomponents\ \

Follow the sequence below to install the required RPMs:
rpm -ivh libcmpiCppImpl0-x.x.x.rpm
rpm –ivh libwsman1-x.x.x.rpm
rpm -ivh sblim-sfcb-x.x.x.rpm
rpm -ivh sblim-sfcb-x.x.x.rpm

NOTE: Install the libwsman and openwsman client RPMs simultaneously as they have cyclic dependency:
rpm -ivh libwsman1-x.x.x.rpm openwsman-clientx.x.x.rpm
rpm -ivh openwsman-server-x.x.x.rpm

NOTE: You might be required to install the following RPM from your Linux distribution media:
rpm –ivh libxslt-1.x.x.x.rpm


Install OMSA from the Internet
The following steps require internet access on each Linux server:

Yum Setup (RHEL5, RHEL 6)

1. Set up the Dell OpenManage Repository:
wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash

2. Install OpenManage Server Administrator:
yum install srvadmin-all


Zypper Setup (SLES 11 or greater)

1. Set up the Dell OpenManage Repository:
wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash

2. Install OpenManage Server Administrator:
zypper install srvadmin-all


Rug Setup (SLES 10)

1. Set up the Dell OpenManage Repository:
wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash

2. Install OpenManage Server Administrator:
rug install srvadmin-base
rug install srvadmin-webserver
rug install srvadmin-storageservices

NOTE: If you want to install srvadmin-all, 'setserial' must be installed.

After installation, make sure to start the applicable services by running the following command:
sh linux/supportscripts/srvadmin-services.sh start


Install OMSA Locally (Alternative)
The following steps require internet access from one server on your network only.
First, download the install package using the following steps:

1. Go to support.dell.com.
2. Choose your server model and Linux OS.
3. Scroll down to Systems Management and select OpenManage Server Administrator Managed Node.
4. Click the 'Download Now' link to download the file that is for your specific Linux distribution.
5. Download the file to a directory on your hard drive.
6. Copy over the file to your Linux server using WinSCP or similar utilty.
7. Browse to the location where you copied the file and unzip the package using the following command:
gunzip xxxx.tar.gz

8. Untar the package using the following command:
tar –xvf xxxx.tar


Next Install OMSA using the following steps:

1. Change the current directory to the location where the files were extracted.
2. Run the following command to perform an express install:
sh linux/supportscripts/srvadmin-install.sh –express


After installation, make sure to start the applicable services by running the following command:
sh linux/supportscripts/srvadmin-services.sh start


Verify OMSA SNMP Settings
If OMSA was installed after SNMP, these changes should have already been made by the OMSA installer. The changes setup OMSA communication with the SNMP agent and give read-only access to the entire MIB tree to the public community. This is required for OMSA and OME to work properly.
1. Open the file for editing:
/etc/snmp/snmpd.conf

2. Verify the following 3 lines exist or add/modify them to the below if they do not:
view all included .1
access notConfigGroup "" any noauth exact all none none
smuxpeer .1.3.6.1.4.1.674.10892.1


Install Inventory Collector on 64-bit Servers
Inventory Collector is required for systems update on Linux servers. Currently it is available only as a 32-bit version and must be installed separately for 64-bit systems.
For all 64-bit supported Linux operating systems you must complete the following steps:

1. Install the 32-bit version of zlib and compat-libstdc++ libraries.
2. Install the srvadmin-cm package from:
/linux/RPMS/supportRPMS/srvadmin


Configure the SNMP Community String
The community string is a password which must match for the querying server and all devices which it queries.

To modify the community string:
1. Open the file for editing:
/etc/snmp/snmpd.conf

2. Copy the line that reads:
com2sec publicsec default public

or
com2sec notConfigUser default public
3. Edit the copied line to replace ‘public’ with the new community string:
com2sec publicsec default

or
com2sec notConfigUser default
4. To enable the changes, restart the SNMP agent:
/etc/init.d/snmpd restart

Note – this step is only needed once after all configuration changes are completed.

Configure SNMP Trap Destinations
For OpenManage Essentials to display alerts for a device, you must configure the device to send traps to the OpenManage Essentials server.

To configure a trap destination:
1. Open the file for editing:
/etc/snmp/snmpd.conf

2. Add the following line to the file:
Trapsink

3. To enable the changes, restart the SNMP agent:
/etc/init.d/snmpd restart

Note – this step is only needed once after all configuration changes are completed.

Enabling SNMP Access for Remote Hosts (SUSE Linux only)
The default SNMP configuration on SUSE Linux versions does not allow remote access. You must enable remote access for the OpenManage Essentials server to manage the system.

To enable SNMP access for the OpenManage Essentials server:
1. Open the file for editing:
/etc/snmp/snmpd.conf

2. Copy the line that reads:
rocommunity public 127.0.0.1

3. Edit the copied line to replace the IP address with the OME server’s IP address:
rocommunity public

Alternatively, to enable SNMP access for all remote hosts, the new line should read:
rocommunity public

Note – this is not recommended for security purposes.

4. To enable the changes, restart the SNMP agent:
/etc/init.d/snmpd restart

Note – this step is only needed once after all configuration changes are completed.

Firewall Configuration
If the firewall was enabled during the Linux installation, it will close the SNMP port blocking all external connections by default. Server Administrator will detect this and log a warning message to the system event log.

You must open the SNMP port on the server for OpenManage Essentials to communicate with it or else this will block OME from discovering, inventorying, and receiving alerts for the server.

Please refer to your specific Linux distribution for configuring firewall settings. You will need to configure your IPTABLES to allow access to UDP Port 161 and 162 for SNMP communication and TCP Port 1311 for OMSA.

September 26th, 2012 05:00

Our Linux admin is asking where exactly do we find the RPM dir: linux\RPMS\supportRPMS\opensourcecomponents\ \ that is mentioned in the article. I've checked our OMSA and OME DVDs but to no avail. Any direction would be greatly appreciated.

Community Manager

 • 

711 Posts

September 26th, 2012 07:00

Hi,

The path listed is for OMSA DVD. Which version of OMSA are you using? Did you download OMSA ISO or are you using the DVD which came with the server? What is the name on the DVD?

Regards

Abhijit

Community Manager

 • 

711 Posts

September 26th, 2012 13:00

I just confirmed this. All of the dependencies are available as part of the base OS and can normally be installed using normal OS yum install commands.

Regards

Abhijit

Community Manager

 • 

711 Posts

September 26th, 2012 13:00

Thanks for the updates. Since the post above is generic, it is possible that the libraries (which are mentioned to be in the sub directory) may be part of base OS distribution. I'll check further on this. Meanwhile, you can try following the next step and install OMSA.

Regards

Abhijit

September 26th, 2012 13:00

So I found the subdir in question from a file I downloaded from Dell\Support\Drivers & Downloads\ for RHEL 6: OM-SrvAdmin-Dell-Web-LX-7.1.0-5304.RHEL6.x86_64_A00.tar.gz. The only problem is that the subdir (\\linux\RPMS\supportRPMS\opensource-components\RHEL6) is actually empty. Nada, zip, zilch. The other RHEL6-related subdirs ("metaRPMS" and "srvadmin") in the download have content but that particular one does not (and this is the one specified in the directions above in the "Install OMSA Dependencies" subheader). Any ideas? All feedback is welcome and greatly appreciated (thank you, Abhijit).

Community Manager

 • 

711 Posts

September 27th, 2012 08:00

Thanks for the update Scott. Do let us know if you have any additional feedback for OME.

Regards

Abhijit

September 27th, 2012 08:00

Good Day Abhijit,

That is correct; my RHEL admin did indeed find the files there and used yum to install the OMSA dependencies. I'm now in the process of figuring out how to push OMSA from OME to the RHEL server.

Thank you again for your help, it is greatly appreciated!

Scott

September 28th, 2012 05:00

Good Day Abhijit,

Do you know what kind of permissions are required for OME to push OMSA to a Linux server? Does it require ROOT? If so, does it still use the ROOT account post-install to do anything? My Nix admins are trying to prevent the use of ROOT where possible.

Much obliged,

Scott

Community Manager

 • 

711 Posts

September 28th, 2012 07:00

Hi Scott,

OME does use root account to push OMSA to Linux servers. Post-install it may need root account for sending firmware/BIOS updates or running command line tasks. For future version of OME we are looking at adding sudo support. Till then we are dependent on root accounts to do system management functionalities.

Regards

Abhijit

October 2nd, 2012 08:00

Good Day Abhijit,

We're attempting to push a fresh install of the Linux OMSA agent to a server but the client is responding with the following error: "Results: omexec must be installed on the remote node for the task. Ensure remote node requirements are met before executing the task."

As far as I've been told, the pre-reqs listed under "Install OMSA Dependencies" have been completed; we've also turned off the local firewall to rule that out. What else are we missing?

Kind regards,

Scott

Community Manager

 • 

711 Posts

October 2nd, 2012 09:00

Hi Scott,

omexec is part of Pre-install package and it needs the below RPMS. Can you grep each rpm and verify these RPMS and the dependent RPMS are installed correctly. Note that these are 32-bit RPMS.

RHEL

compat-libstdc++-33.i686

libxml2.i686

pam.i686

glibc.i686

zlib.i686

libgcc.i686

Regards

Abhijit

October 5th, 2012 06:00

Good morning Abhijit,

My Nix admin sent back the following as installed:

compat-libstdc++-33.i686

libxml2.i686

pam.i686

glibc.i686

zlib.i686

libgcc.i686

All versions installed are x86_64 and the install of compat-libstdc++-33.i686 also installed the glibc and libgcc i686 versions.

I'm still getting the same omexec error. Are these the correct versions?

Much obliged (and Happy Friday),

Scott

8 Posts

April 21st, 2013 21:00

Hi followed this guide, I discovered and inventoried a C6145 and R815 servers (RHEL 6). However, I found that in OME, all processor and memory info are missing (they present in server's OMSA though).

Am I missing something?

Cheers,

Derrick

8 Posts

April 22nd, 2013 01:00

i deleted and re discovered and inventoried, now it displays full details as it is in OMSA. cheers,

2.8K Posts

April 22nd, 2013 07:00

Hi Derrick, thanks for posting an update to your question.

Let us know how it goes.

Regards,

Rob

No Events found!

Top