Getting Started

After setup, logs that would typically appear in /var/log/messages will be forwarded to the Nagios Log Server R2, allowing centralized monitoring and alerting.

Automatic Setup Using a Script

The easiest way to configure log forwarding is by using the provided script. This method requires rsyslog to be installed on your CentOS 7 machine.

Steps to Run the Script:

1. Ensure Rsyslog is Installed:

sudo yum install rsyslog -y
sudo systemctl enable --now rsyslog

sudo yum install rsyslog -y
sudo systemctl enable --now rsyslog

2. Download the Script from the Nagios Log Server R2:

curl -sS -O http://192.168.1.49/nagioslogserver/scripts/setup-linux.sh

curl -sS -O http://192.168.1.49/nagioslogserver/scripts/setup-linux.sh

3. Execute the Script to Configure Rsyslog:

sudo bash setup-linux.sh -s 192.168.1.49 -p 5544

sudo bash setup-linux.sh -s 192.168.1.49 -p 5544

• Replace 192.168.1.49 with your Nagios Log Server R2’s IP address.
• The -p 5544 option specifies the port for log transmission.

Manual Setup Using Rsyslog Configuration

If you prefer manual setup or need more control over configurations, follow these steps:

1. Edit Rsyslog Configuration:

<code>sudo nano /etc/rsyslog.d/99-nagios.conf

<code>sudo nano /etc/rsyslog.d/99-nagios.conf

2. Add the following configuration:

*.* @@192.168.1.49:5544

*.* @@192.168.1.49:5544

• Replace 192.168.1.49 with the IP address of your Nagios Log Server R2.
• The @@ symbol indicates TCP transmission; use @ for UDP if needed.

3. Restart Rsyslog to Apply Changes:

sudo systemctl restart rsyslog<br>

sudo systemctl restart rsyslog<br>

4. Check Status to Ensure it’s Running:

sudo systemctl status rsyslog<br>

sudo systemctl status rsyslog<br>

Receiving Logs in Log Server

On your Log Server’s GUI, click Add Log Source.

Click Linux.

Type in your machine’s IP address to see if you are receiving logs. If it’s working, the interface will confirm that logs are being received.

Conclusion

Whether using the automatic script or manual setup, forwarding logs from CentOS 7 to Nagios Log Server R2 ensures centralized log management for better monitoring and alerting. Use the method that best fits your deployment needs.

Getting Started

After setup, logs that would typically appear in /var/log/messages will be forwarded to the Nagios Log Server R2, allowing centralized monitoring and alerting.

Automatic Setup Using a Script

The easiest way to configure log forwarding is by using the provided script. This method requires rsyslog to be installed on your CentOS 8 machine.

Steps to Run the Script:

1. Ensure Rsyslog is Installed:

sudo dnf install rsyslog -y
sudo systemctl enable --now rsyslog

sudo dnf install rsyslog -y
sudo systemctl enable --now rsyslog

2. Download the Script from the Nagios Log Server R2:

curl -sS -O http://192.168.1.49/nagioslogserver/scripts/setup-linux.sh

curl -sS -O http://192.168.1.49/nagioslogserver/scripts/setup-linux.sh

3. Execute the Script to Configure Rsyslog:

sudo bash setup-linux.sh -s 192.168.1.49 -p 5544

sudo bash setup-linux.sh -s 192.168.1.49 -p 5544

• Replace 192.168.1.49 with your Nagios Log Server R2’s IP address.
• The -p 5544 option specifies the port for log transmission.

Manual Setup Using Rsyslog Configuration

If you prefer manual setup or need more control over configurations, follow these steps:

1. Edit Rsyslog Configuration:

sudo nano /etc/rsyslog.d/99-nagios.conf

sudo nano /etc/rsyslog.d/99-nagios.conf

2. Add the Following Configuration:

*.* @@192.168.1.49:5544

*.* @@192.168.1.49:5544

• Replace 192.168.1.49 with the IP address of your Nagios Log Server R2.
• The @@ symbol indicates TCP transmission; use @ for UDP if needed.

3. Restart Rsyslog to Apply Changes:

sudo systemctl restart rsyslog

sudo systemctl restart rsyslog

4. Check Status to Ensure it’s Running:

sudo systemctl status rsyslog

sudo systemctl status rsyslog

Receiving Logs in Log Server

On your Log Server’s GUI, click Add Log Source.

Click Linux.

Type in your machine’s IP address to see if you are receiving logs. If it’s working, the interface will confirm that logs are being received.

Conclusion

Whether using the automatic script or manual setup, forwarding logs from CentOS 8 to Nagios Log Server R2 ensures centralized log management for better monitoring and alerting. Use the method that best fits your deployment needs.

Getting Started

After setup, logs that would typically appear in /var/log/messages will be forwarded to the Nagios Log Server R2, allowing centralized monitoring and alerting.

Automatic Setup Using a Script

The easiest way to configure log forwarding is by using the provided script. This method requires rsyslog to be installed on your CentOS 10 machine.

Steps to Run the Script

Download the script from the Nagios Log Server R2:

curl -sS -O http://192.168.1.49/nagioslogserver/scripts/setup-linux.sh

curl -sS -O http://192.168.1.49/nagioslogserver/scripts/setup-linux.sh

Execute the script to configure rsyslog:

sudo bash setup-linux.sh -s 192.168.1.49 -p 5544

sudo bash setup-linux.sh -s 192.168.1.49 -p 5544

Replace 192.168.1.49 with your Nagios Log Server R2’s IP address.

The -p 5544 option specifies the port for log transmission.

Receiving Logs in Log Server

On your Log Servers GUI, click Add Log Source.

Click Linux.

Now type in your machine’s IP address to see if you are receiving logs. If it’s working, it will confirm that logs are being received.

Conclusion

Whether using the automatic script or manual setup, forwarding logs from CentOS 10 to Nagios Log Server R2 ensures centralized log management for better monitoring and alerting. Use the method that best fits your deployment needs.

Step 1: Add the Nagios Repository

First, add the Nagios repository to your system to access the NCPA package:

sudo rpm -Uvh https://repo.nagios.com/nagios/7/nagios-repo-7-4.el7.noarch.rpm

sudo rpm -Uvh https://repo.nagios.com/nagios/7/nagios-repo-7-4.el7.noarch.rpm

Step 2: Install NCPA

Once the repository is added, install NCPA with:

sudo yum install ncpa -y

sudo yum install ncpa -y

Step 3: Start and Enable NCPA Services

After installation, start and enable the NCPA services to run at boot:

sudo systemctl enable ncpa
sudo systemctl start ncpa

sudo systemctl enable ncpa
sudo systemctl start ncpa

Step 4: Configure NCPA

The main configuration file for NCPA is located at:

/etc/ncpa/ncpa.cfg

/etc/ncpa/ncpa.cfg

Before making changes, back up the original file:

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

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

Now, edit the configuration file:

sudo nano /etc/ncpa/ncpa.cfg

sudo nano /etc/ncpa/ncpa.cfg

Locate the [api] section and update the community_string value:

[api]
community_string = YourCommunity

[api]
community_string = YourCommunity

Save and exit the file, then restart the NCPA services:

sudo systemctl restart ncpa_listener
sudo systemctl restart ncpa_passive

sudo systemctl restart ncpa_listener
sudo systemctl restart ncpa_passive

Step 5: Adjust Firewall Rules

To allow NCPA traffic, open the necessary ports:

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

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

Step 6: Verify NCPA Functionality

To check if NCPA is running correctly, open a web browser and navigate to:

https://<server-ip>:5693

https://<server-ip>:5693

Log in using the community string configured earlier. If you see the NCPA web interface, the agent is working correctly.

Monitoring with Nagios

On your Nagios web GUI, click Run a wizard and find the NCPA wizard.

Type in the Address of your machine running NCPA. You can leave the Port as default. Enter the Token that you created earlier and click Next, and Finish with Defaults.

Conclusion

You have successfully installed and configured the Nagios Cross Platform Agent (NCPA) on CentOS 7. This setup allows Nagios to monitor the server efficiently, providing real-time insights into system performance and resource utilization. By integrating NCPA with Nagios, you enhance your network monitoring capabilities, ensuring proactive management of system health and performance.

Step 1: Install SNMP and Utilities

CentOS 7 uses yum as the default package manager. Install SNMP packages with:

sudo yum install net-snmp net-snmp-utils -y

sudo yum install net-snmp net-snmp-utils -y

Step 2: Start and Enable the SNMP Service

Once installed, start and enable the SNMP service so that it runs at boot:

sudo systemctl enable snmpd
sudo systemctl start snmpd

sudo systemctl enable snmpd
sudo systemctl start snmpd

Step 3: Configure SNMP

The main configuration file for SNMP is located at:

/etc/snmp/snmpd.conf

/etc/snmp/snmpd.conf

Before making changes, back up the original file:

sudo cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.conf.bak

sudo cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.conf.bak

Now, edit the configuration file:

sudo nano /etc/snmp/snmpd.conf

sudo nano /etc/snmp/snmpd.conf

Modify or add the following lines to set up SNMPv2c with a community string (replace YourCommunity with a strong name):

com2sec readonly  default  YourCommunity
group   MyROGroup v2c        readonly
view    all    included   .1
access  MyROGroup ""      any       noauth    exact  all    none   none
syslocation "Data Center"
syscontact "Admin <admin@example.com>"

com2sec readonly  default  YourCommunity
group   MyROGroup v2c        readonly
view    all    included   .1
access  MyROGroup ""      any       noauth    exact  all    none   none
syslocation "Data Center"
syscontact "Admin <admin@example.com>"

Save and exit the file, then restart the SNMP service:

sudo systemctl restart snmpd

Step 4: Adjust Firewall Rules

To allow SNMP traffic, open the necessary UDP port (161):

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

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

Step 5: Verify SNMP Functionality

Test if SNMP is working correctly with:

snmpwalk -v2c -c YourCommunity -O e 127.0.0.1

snmpwalk -v2c -c YourCommunity -O e 127.0.0.1

If you see output with system information, SNMP is working correctly.

Step 6: Open Firewall for SNMP

If you want to allow SNMP traffic from remote machines, open the firewall to allow SNMP traffic:

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

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

This command opens port 161 (the default SNMP port) for UDP traffic, allowing SNMP queries from remote systems.

Step 7: Test SNMP from a Remote System

Finally, to ensure SNMP is accessible remotely, test it from another system using snmpwalk:

snmpwalk -v2c -c YourCommunityString <server-ip>

snmpwalk -v2c -c YourCommunityString <server-ip>

Replace <server-ip> with the IP address of your CentOS 7 server. If SNMP is correctly configured, you will receive SNMP data from the remote server.

Monitoring with Nagios XI

In Nagios XI, navigate to Run a Wizard and click on the SNMP wizard.

• Add your Host Name and type in the SNMP Community string that you created.
• Pick the SNMP Services that you want to monitor and then click Next and Finish with Defaults.

Conclusion

You have successfully installed and configured SNMP on CentOS 7. 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. 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.

Step 1: Install SNMP and Utilities

CentOS 8 uses dnf as the default package manager. Install SNMP packages with:

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

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

Step 2: Start and Enable the SNMP Service

Once installed, start and enable the SNMP service so that it runs at boot:

sudo systemctl enable --now snmpd

sudo systemctl enable --now snmpd

Step 3: Configure SNMP

The main configuration file for SNMP is located at:

/etc/snmp/snmpd.conf

/etc/snmp/snmpd.conf

Before making changes, back up the original file:

sudo cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.conf.bak

sudo cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.conf.bak

Now, edit the configuration file:

sudo nano /etc/snmp/snmpd.conf

sudo nano /etc/snmp/snmpd.conf

Modify or add the following lines to set up SNMPv2c with a community string (replace YourCommunity with a strong name):

com2sec readonly  default  YourCommunity
group   MyROGroup v2c        readonly
view    all    included   .1
access  MyROGroup ""      any       noauth    exact  all    none   none
syslocation "Data Center"
syscontact "Admin <admin@example.com>"

com2sec readonly  default  YourCommunity
group   MyROGroup v2c        readonly
view    all    included   .1
access  MyROGroup ""      any       noauth    exact  all    none   none
syslocation "Data Center"
syscontact "Admin <admin@example.com>"

Save and exit the file, then restart the SNMP service:

sudo systemctl restart snmpd

sudo systemctl restart snmpd

Step 4: Adjust Firewall Rules

To allow SNMP traffic, open the necessary UDP port (161):

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

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

Step 5: Verify SNMP Functionality

Test if SNMP is working correctly with:

snmpwalk -v2c -c YourCommunity -O e 127.0.0.1

snmpwalk -v2c -c YourCommunity -O e 127.0.0.1

If you see output with system information, SNMP is working correctly.

Step 6: Open Firewall for SNMP

If you want to allow SNMP traffic from remote machines, open the firewall to allow SNMP traffic:

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

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

This command opens port 161 (the default SNMP port) for UDP traffic, allowing SNMP queries from remote systems.

Step 7: Test SNMP from a Remote System

Finally, to ensure SNMP is accessible remotely, test it from another system using snmpwalk:

snmpwalk -v2c -c YourCommunityString

snmpwalk -v2c -c YourCommunityString

Replace <server-ip> with the IP address of your CentOS server. If SNMP is correctly configured, you will receive SNMP data from the remote server.

Monitoring with Nagios XI

On Nagios XI navigate to Run a Wizard and click on the SNMP wizard

Add your Host Name and type in the SNMP Community string that you created.

Pick the SNMP Services that you want to monitor and then click Next and Finish with Defaults.

Conclusion

You have successfully installed and configured SNMP on CentOS 8. 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. 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.

Prerequisites

• A CentOS 8 system with root or sudo privileges
• Access to the internet
• A running Nagios server

Step 1: Update System Packages

Before installing any software, it’s best to update your system:

sudo dnf update -y

sudo dnf update -y

Step 2: Download NCPA Package

The official NCPA package for CentOS 8 is available on the Nagios website. You can download it using wget:

wget https://assets.nagios.com/downloads/ncpa/ncpa-latest.el8.x86_64.rpm

wget https://assets.nagios.com/downloads/ncpa/ncpa-latest.el8.x86_64.rpm

Step 3: Install NCPA

Use the dnf package manager to install the downloaded RPM package:

sudo dnf install -y ncpa-latest.el8.x86_64.rpm

sudo dnf install -y ncpa-latest.el8.x86_64.rpm

This command installs NCPA along with its dependencies.

Step 4: Configure NCPA

The main configuration file for NCPA is located at:

/etc/ncpa/ncpa.cfg

/etc/ncpa/ncpa.cfg

Open the file with a text editor, such as nano:

sudo nano /etc/ncpa/ncpa.cfg

sudo nano /etc/ncpa/ncpa.cfg

Set the api_token value to a secure string, as it is required for communication between NCPA and the Nagios server:

api_token = YOUR_SECURE_API_TOKEN

api_token = YOUR_SECURE_API_TOKEN

Save the file and exit.

Step 5: Start and Enable NCPA Service

Once configured, start the NCPA services and enable them to run at boot:

sudo systemctl enable --now ncpa_listener
sudo systemctl enable --now ncpa_passive

sudo systemctl enable --now ncpa_listener
sudo systemctl enable --now ncpa_passive

Step 6: Configure Firewall Rules (If Applicable)

If you have firewalld enabled, allow NCPA through the firewall:

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

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

Step 7: Verify NCPA Installation

To check if NCPA is running, use the following command:

sudo systemctl status ncpa_listener ncpa_passive

sudo systemctl status ncpa_listener ncpa_passive

Additionally, you can test API access via curl:

curl https://localhost:5693/api --insecure

curl https://localhost:5693/api --insecure

If everything is set up correctly, you should receive a JSON response.

Monitoring with Nagios

On your Nagios web GUI, click Run a wizard and find the NCPA wizard.

Type in the Address of your machine running NCPA. You can leave the Port as default. Enter the Token that you created earlier and click Next, and Finish with Defaults.

Conclusion

You have successfully installed and configured NCPA on CentOS 8. This agent allows you to monitor system performance and services using Nagios. Want Nagios notifications in Slack or Discord? Click to find out how.

Prerequisites

• A system running CentOS Stream 10
• Root or sudo privileges
• Internet connectivity to download necessary packages

Step 1: Update Your System

Before installing NCPA, update your system to ensure all packages are up to date.

sudo yum update -y

sudo yum update -y

Then navigate to the /tmp directory

cd /tmp

cd /tmp

Step 2: Enable the Nagios Repository

To install NCPA, you need to add the Nagios repository.

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

After adding the repository, update your system again:

sudo yum update -y

sudo yum update -y

Step 3: Install NCPA

Download and install the latest version of NCPA for CentOS Stream 10 (which aligns with EL9 packages):

sudo yum install ncpa -y

sudo yum install ncpa -y

This will install the NCPA agent along with its dependencies.

Step 4: Configure NCPA

Once installed, update the configuration file to set the authentication token. Open the NCPA configuration file:

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

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

Locate the following section and change mytoken to a secure token of your choice:

[api]
community_string = <your-secure-token>

[api]
community_string = <your-secure-token>

Save the file and exit the editor.

Step 5: Start and Enable the NCPA Service

Start the NCPA listener service and enable it to start on boot:

sudo systemctl start ncpa_listener
sudo systemctl enable ncpa_listener

sudo systemctl start ncpa_listener
sudo systemctl enable ncpa_listener

Verify that the service is running:

sudo systemctl status ncpa_listener

sudo systemctl status ncpa_listener

Step 6: Open Firewall Ports for NCPA

If your system has a firewall enabled, open the necessary port (default: 5693) to allow incoming connections:

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

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

Step 7: Verify NCPA Installation

Test if NCPA is running correctly by accessing its web interface. Open a browser and navigate to:

https://<server-ip>:5693

https://<server-ip>:5693

Log in using the authentication token you set earlier.

Monitoring With Nagios XI

Now that you have configured NCPA, monitoring with Nagios XI will be easy! Navigate to the Nagios web GUI and click Run a Wizard.

Click the NCPA wizard.

Enter the IP Address of your machine. You can leave the Port as default. Then pick the Token that you set earlier. Click Next, and Finish with Defaults.

Conclusion

You have successfully installed and configured the Nagios Cross-Platform Agent (NCPA) on CentOS Stream 10. Your system can now be monitored using Nagios XI, providing detailed insights into system performance and resource usage.

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.