Bobcares

Install SNMP on RHEL/CentOS/Fedora – How to perform it

by | Jan 24, 2022

Wondering how to Install SNMP on RHEL? We can help you.

We can use Simple Network Management Protocol (SNMP) to get information about the current status of servers, network equipment, printers, or other IP devices.

As part of our Server Management Services, we assist our customers with several RHEL queries.

Today, let us see how to install an SNMP (and SNMP v3) agent on a Linux host running CentOS, RHEL, or Fedora.

 

How to Install SNMP on RHEL

With SNMP, we get different metrics. For example, CPU utilization, the number of processes, state of services, etc.

Its major advantage includes, it is supported by almost any device. In addition, it does not require the installation of a separate monitoring system agent.

 

Install SNMP Agent and Diagnostic Tools on Linux

Before we proceed with SNMP packages, we install the latest updates on the server using dnf (yum):

# dnf update -y

Then we install the SNMP agent and additional tools from the base repository:

# dnf install net-snmp net-snmp-utils -y

Enable and Configure SNMP Agent on Linux

Prior to SNMP configuration, we create a copy of the original config file:

# mv /etc/snmp/snmpd.conf /etc/snmp/snmpd.conf.orig

Then we edit the SNMP agent settings:

# nano /etc/snmp/snmpd.conf

Here, we add the following lines:

rocommunity public
syslocation GE-DC2
syscontact gedc2-admins@bobcares.com

The above are three basic SNMP parameters.

Eventually, we save the file. Our Support Techs recommend entering a correct location and a valid email address.

Then we enable the snmpd service and start it:

# systemctl enable snmpd.service
# systemctl start snmpd

To ensure the service is running, we use:

# systemctl status snmpd

Install SNMP on RHEL

In case we use a firewall on the server, we allow connections to TCP/UDP ports 161 and 162.

To open SNMP ports in firewalld, we run:

# firewall-cmd –zone=public –add-port=161/udp –permanent
# firewall-cmd –zone=public –add-port=161/tcp –permanent
# firewall-cmd –zone=public –add-port=162/udp –permanent
# firewall-cmd –zone=public –add-port=162/tcp –permanent
# firewall-cmd –reload

Poll SNMP Agent Using Snmpwalk

To poll the SNMP agent, we use the snmpwalk tool.

We then check the service locally using the SMMPv2 protocol:

# snmpwalk -v 2c -c public -O e 127.0.0.1

If the SNMP configuration is correct, we will receive a set of SNMP data from the agent.

Once we set the configuration file and run a test command, we may receive:

Timeout: No Response from localhost

We can fix this error by clearing the configuration file and adding only the lines specified above.

Since the service starts without any problems, but it is not working, we check everything specifically.

We also query our server locally using:

# snmpwalk -v2c -c public localhost system

SNMPv2-MIB::sysDescr.0 = STRING: Linux server1.test.com 4.18.0-147.8.1.el8_1.x86_64 #1 SMP Thu Apr 9 13:49:54 UTC 2020 x86_64
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (106564) 0:17:45.64
SNMPv2-MIB::sysContact.0 = STRING: gedc2-admins@bobcares.com
SNMPv2-MIB::sysName.0 = STRING: server1.test.com
SNMPv2-MIB::sysLocation.0 = STRING: GE-DC2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SNMPv2-MIB::sysORUpTime.6 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.7 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.8 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.9 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.10 = Timeticks: (0) 0:00:00.00

We ensure that our SNMP agent is available remotely.

In addition, on another server (install snmp tools prior to doing it) we run:

# snmpwalk -v2c -c public 192.168.20.105 system

Since the remote server receives the information from the server over SNMP, we can add the server to any SNMP monitoring system.

 

 

Configure SNMPv3 on Linux CentOS/RHEL/Fedora

SNMPv3 is a newer and more secure version of the protocol with support for authentication and encryption.

In order to configure SNMPv3, we create a user with a password, set an encryption password, access rights, and an encryption algorithm (MD5 or SHA).

To create a user for SNMPv3, we stop the snmpd daemon:

# systemctl stop snmpd

Then we can create a user:

# net-snmp-create-v3-user -ro -A o2ps2w0dD -a SHA -X r30svV33 -x AES snmpuser

The syntax of net-snmp-create-v3-user is:

net-snmp-create-v3-user [-ro] [-A authpass] [-a MD5|SHA] [-X privpass][-x DES|AES] [username]
  • -ro – user has read-only privileges
  • Authpass -authentication password
  • Privpass – private key

Once done, it will create a user with the specified password and key.

Then we start the service:

# systemctl start snmpd

Eventually, we try to poll the SNMP agent using snmpwalk.

Make note that to poll over SNMPv3, we must specify the username, the password, and the key.

# snmpwalk -v3 -a SHA -A o2ps2w0dD -x AES -X r30svV33 -l authPriv -u snmpuser 192.168.20.105 | head

[Need help with the installation? We’d be happy to assist you]

 

Conclusion

In short, we saw how our Support Techs install and configure SNMP on RHEL.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF