Prerequisites

Before proceeding, ensure the following requirements are met:

• A running Nagios XI server, accessible from your CentOS machine.
• A CentOS Stream 9 system with sudo or root privileges.
• A stable internet connection for downloading NCPA.
• Basic familiarity with Linux commands (optional but recommended).”

Step 1 – Download and Install NCPA

You can install NCPA on CentOS Stream 9 using either a direct RPM download or the official Nagios repository. Choose one method below:

1. Open a terminal and switch to a temporary directory:

cd /tmp

cd /tmp

2. Download the latest NCPA package:

curl -O https://assets.nagios.com/downloads/ncpa3/ncpa-latest-1.x86_64.rpm

curl -O https://assets.nagios.com/downloads/ncpa3/ncpa-latest-1.x86_64.rpm

3. IInstall the package with dnf:

sudo dnf install ./ncpa-latest-1.x86_64.rpm -y

sudo dnf install ./ncpa-latest-1.x86_64.rpm -y

Option 2: Nagios Repository

The Nagios repository provides an online installation method for NCPA and Nagios XI, ensuring access to the latest versions and updates.

1. Add the Nagios repository for CentOS Stream 9:

sudo rpm -Uvh https://repo.nagios.com/nagios/9/nagios-repo-9-2.el9.noarch.rpm

sudo rpm -Uvh https://repo.nagios.com/nagios/9/nagios-repo-9-2.el9.noarch.rpm

This configures your system to use the Nagios repo at https://repo.nagios.com/nagios, secured with public GPG keys (GPG-KEY-NAGIOS-V3 or GPG-KEY-NAGIOS-V2).

2. Install prerequisites for compatibility:

sudo yum install epel-release -y  
sudo dnf config-manager --set-enabled crb  

sudo yum install epel-release -y  
sudo dnf config-manager --set-enabled crb  

These enable the EPEL repository and the CRB (CodeReady Builder) repository, required for Nagios dependencies on CentOS Stream 9.

3. Update the package cache:

sudo yum update -y

sudo yum update -y

4. Install NCPA:

sudo yum install ncpa -y  

sudo yum install ncpa -y  

Note: To upgrade NCPA later, run sudo yum update ncpa.

Verification (Both Methods)

5. Confirm installation:

ncpa --version  

ncpa --version  

Expect output like NCPA 3.0.0 (version may vary based on the source).

Step 2 – Configure NCPA

Next, configure NCPA for secure operation:

1. Open the configuration file in a text editor:

sudo nano /usr/local/ncpa/etc/ncpa.cfg

sudo nano /usr/local/ncpa/etc/ncpa.cfg

2. Set a secure token in the [api] section:

[api] 
community_string = your_secure_token

[api] 
community_string = your_secure_token

Replace X7kP9mNq2v with your own secure token (avoid simple strings like password).

3. In the [listener] section, ensure NCPA listens on all interfaces:

[listener]  
ip = 0.0.0.0  
port = 5693  

[listener]  
ip = 0.0.0.0  
port = 5693  

4. Save (Ctrl+O, Enter, Ctrl+X in nano) and backup the original:

sudo cp /usr/local/ncpa/etc/ncpa.cfg /usr/local/ncpa/etc/ncpa.cfg.bak  

sudo cp /usr/local/ncpa/etc/ncpa.cfg /usr/local/ncpa/etc/ncpa.cfg.bak  

Step 3 – Restart NCPA

1. To ensure NCPA runs at startup, enable and start the services:

sudo systemctl enable ncpa
sudo systemctl restart ncpa

sudo systemctl enable ncpa
sudo systemctl restart ncpa

2. Verify they’re running:

sudo systemctl status ncpa

sudo systemctl status ncpa

Step 4 – Configure Firewall Rules

1. Allow NCPA traffic through the firewall and reload the firewall:

firewall-cmd --permanent --add-port=5693/tcp
firewall-cmd --reload

firewall-cmd --permanent --add-port=5693/tcp
firewall-cmd --reload

2. Confirm the rule:

sudo firewall-cmd --list-all

sudo firewall-cmd --list-all

Ensure 5693/tcp appears under ports.

Step 5 – Integrate NCPA with Nagios XI

Integrate NCPA with Nagios XI for centralized monitoring:

1. Launch the NCPA Wizard

• Log in to your Nagios XI web interface.
• Navigate to Configure > Configuration Wizards.
• Select NCPA Monitoring.

2. Enter Connection Details

• Input the CentOS server’s IP address (e.g., 192.168.1.100).
• Enter the API token from ncpa.cfg (e.g., X7kP9mNq2v).
• Set the port to 5693.
• Click Next.

3. Choose Metrics

• Select services to monitor (e.g., CPU Usage, Memory Usage, Disk Space, Network Statistics).
• Customize thresholds if needed, then click Next.

4. Apply and Verify

• Finish the wizard and apply the configuration.
• Check Core Config Manager > Monitoring > Service Status to confirm data is flowing.

Troubleshooting Common NCPA Issues

Resolve common NCPA setup problems with these tips:

1. NCPA Services Won’t Start
   • Symptom: systemctl status ncpa_listener shows Active: failed.
   • Fix: Check logs (journalctl -u ncpa_listener), ensure /usr/local/ncpa/etc/ncpa.cfg syntax is correct, or reinstall (e.g., sudo yum reinstall ncpa for repo method).
2. Nagios XI Shows No Data
   • Symptom: No metrics in Service Status.
   • Fix: Test connectivity (curl -k https://<server-ip>:5693 from Nagios XI), verify token and port match ncpa.cfg.
3. Firewall Blocks Access
   • Symptom: Connection timeouts from Nagios XI.
   • Fix: Confirm 5693/tcp is open (sudo firewall-cmd –list-all); reapply rules if needed.

Conclusion

By following this guide, you have successfully installed NCPA on CentOS Stream 9 and integrated it with Nagios XI. This setup allows comprehensive system monitoring and ensures proactive alerting for critical system metrics.

For further details, refer to the official NCPA documentation.

Requirements

Before starting, ensure you have:

• A CentOS Stream 9 system with sudo or root privileges
• A stable internet connection to download required packages
• An operational Nagios XI server (accessible from the CentOS machine)
• Optional: Basic familiarity with Linux command-line operations”

Step 1: Installing SNMP Packages

To begin, install the core SNMP packages on your CentOS Stream 9 system:

sudo dnf install -y net-snmp net-snmp-utils

sudo dnf install -y net-snmp net-snmp-utils

This command installs the SNMP daemon and utilities required to interact with SNMP-enabled devices.

Verification

After installation, confirm the SNMP daemon is installed by checking its version:

snmpd -v

snmpd -v

Step 2: Enabling and Starting SNMP Service

Next, enable and start the SNMP service to ensure it runs automatically on boot:

sudo systemctl enable snmpd  
sudo systemctl start snmpd

sudo systemctl enable snmpd  
sudo systemctl start snmpd

The enable command configures the service for automatic startup, while start launches it immediately.

Step 3: Verifying SNMP Status

Verify that the SNMP service is operational:

sudo systemctl status snmpd

sudo systemctl status snmpd

Look for Active: active (running) in the output to confirm the service is functioning. If it’s inactive or failed, review the logs with journalctl -u snmpd for troubleshooting.

Step 4: Configuring SNMP for Secure Access

The SNMP configuration file needs to be modified for proper security settings. Open the file:

sudo nano /etc/snmp/snmpd.conf

sudo nano /etc/snmp/snmpd.conf

Find the com2sec directive (or add it if missing) and configure it as follows:

com2sec readonly 192.168.1.0/24 MySecureCommunity

com2sec readonly 192.168.1.0/24 MySecureCommunity

• Replace MySecureCommunity with a unique, strong community string (e.g., X7kP9mNq2v). Avoid easily guessable values like public.
• The 192.168.1.0/24 subnet restricts queries to this network. Adjust it to match your environment (e.g., 10.0.0.0/24).

Save the file (Ctrl+O, Enter, Ctrl+X in nano), then restart the service:

sudo systemctl restart snmpd

sudo systemctl restart snmpd

Step 5: Testing SNMP on the Local Machine

Test SNMP functionality locally with:

snmpwalk -v2c -c MySecureCommunity localhost

snmpwalk -v2c -c MySecureCommunity localhost

This queries the SNMP daemon using SNMP v2c and your custom community string. A successful response will display system details (e.g., OID data like sysDescr.0). If you receive a timeout or error, ensure the service is running and the community string matches your configuration.

Step 6: Configuring Firewall Rules for Remote Access

Enable remote SNMP access by updating the firewall:

sudo firewall-cmd --permanent --add-port=161/udp
sudo firewall-cmd --reload

sudo firewall-cmd --permanent --add-port=161/udp
sudo firewall-cmd --reload

Port 161/UDP is the default for SNMP. Verify the rule is active:

sudo firewall-cmd --list-all

sudo firewall-cmd --list-all

Look for 161/udp under ports in the output. If it’s missing, recheck your commands.”

Step 7: Testing SNMP Remotely

From a remote machine, test SNMP connectivity:

snmpwalk -v2c -c MySecureCommunity <server-ip>

snmpwalk -v2c -c MySecureCommunity <server-ip>

Substitute <server-ip> with your CentOS Stream 9 server’s IP (e.g., 192.168.1.100). A successful query returns system data. If it fails, verify network reachability (ping <server-ip>), firewall settings, and the community string.”

Additional Testing

You can also use snmpget for targeted queries:

snmpget -v2c -c MySecureCommunity <server-ip> sysName.0

snmpget -v2c -c MySecureCommunity <server-ip> sysName.0

This retrieves the system hostname (e.g., SNMPv2-MIB::sysName.0 = STRING: centos9-server).

Monitoring with Nagios XI

Step 1: Open the SNMP Wizard

• Log in to Nagios XI.
• Navigate to Configure > Run a Configuration Wizard.
• Select SNMP Monitoring Wizard.

Step 2: Add Your Host

• Enter your Host Name and type in the SNMP Community string you created.
• Select SNMP v2c unless using SNMP v3.

Step 3: Select SNMP Services

• Choose the SNMP services you want to monitor (e.g., CPU Load, Memory Usage, Network Interfaces).
• Click Next, then Finish with the default settings.

Troubleshooting Common SNMP Issues

Here are solutions to three frequent issues you might face during SNMP setup:

1. “Timeout: No Response” During snmpwalk

• Symptom: snmpwalk -v2c -c MySecureCommunity localhost or remote tests return a timeout.
• Possible Causes: SNMP service isn’t running, firewall blocking port 161/UDP, or incorrect community string.
• Fixes:
  • Check service status: sudo systemctl status snmpd (start with sudo systemctl start snmpd if stopped).
  • Verify firewall: sudo firewall-cmd --list-all (add 161/udp with sudo firewall-cmd --permanent --add-port=161/udp and sudo firewall-cmd --reload if missing).
  • Ensure the community string matches /etc/snmp/snmpd.conf and the querying IP is in the allowed subnet (e.g., 192.168.1.0/24).

2. SNMP Service Fails to Start

• Symptom: sudo systemctl status snmpd shows Active: failed.
• Possible Cause: Syntax error in /etc/snmp/snmpd.conf or package corruption.
• Fixes:
  • Review logs: journalctl -u snmpd for errors (e.g., “invalid token”).
  • Restore the backup: sudo cp /etc/snmp/snmpd.conf.bak /etc/snmp/snmpd.conf, then sudo systemctl restart snmpd.
  • Reinstall: sudo dnf reinstall net-snmp net-snmp-utils.

3. Nagios XI Shows “Connection Refused” or No Data

• Symptom: Nagios XI can’t connect to the server or shows no SNMP metrics.
• Possible Causes: Network issue or mismatched SNMP settings.
• Fixes:
  • Test connectivity: From Nagios XI, run ping <server-ip> and snmpwalk -v2c -c MySecureCommunity <server-ip>.
  • Confirm Nagios XI settings (community string, v2c, IP) match your SNMP config.
  • Check Nagios logs: Admin > System Information > View Log Files for clues.

Quick Tip

• Use journalctl -xe or tail -f /var/log/messages to dig deeper into any issue.

Conclusion

You have successfully installed and configured SNMP on CentOS Stream 9. This setup allows your server to be monitored remotely, enhancing network management capabilities. You also configured SNMP monitoring with Nagios XI, which provides a powerful interface for tracking system performance and network activity.

Next Steps

• Implement SNMP v3 for enhanced security.
• Set up SNMP traps in Nagios XI to receive alerts on critical events.
• Use custom SNMP queries to monitor specific system parameters.

By adding your SNMP-enabled server to Nagios XI, you can gain deeper insights into system health, set up alerts, and optimize network monitoring for better performance.

If you want the full wizard walkthrough (v2c/v3 + what each service means), see our doc – How to Use the Linux SNMP Wizard in Nagios XI.