You can refer to this documentation for full details:

• How To Use the Linux Server (Legacy) Configuration Wizard in Nagios XI

Prerequisites

• Linux: root or sudo access
• Windows Server 2019/2022: local administrator
• Internet connectivity
• Zabbix server/proxy IP (e.g., 192.168.1.100)

Part 1: Install Zabbix Agent on Linux

1. Update system.

sudo dnf update -y

sudo dnf update -y

2. Add Zabbix repository.

Choose your distribution/version here: Zabbix Linux downloads.

sudo rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/9/x86_64/zabbix-release-7.0 1.el9.noarch.rpm 
sudo dnf clean all

sudo rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/9/x86_64/zabbix-release-7.0 1.el9.noarch.rpm 
sudo dnf clean all

3. Install agent.

sudo dnf install -y zabbix-agent2

sudo dnf install -y zabbix-agent2

4. Configure agent.
Edit /etc/zabbix/zabbix_agent2.conf and set:

Server=192.168.1.100 
ServerActive=192.168.1.100 
Hostname=LinuxServer01

Server=192.168.1.100 
ServerActive=192.168.1.100 
Hostname=LinuxServer01

5. Start and enable service.

sudo systemctl enable --now zabbix-agent2

sudo systemctl enable --now zabbix-agent2

6. Open firewall.

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

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

Part 2: Install Zabbix Agent on Windows

1. Download agent.

• Visit the Zabbix downloads page and get the latest Windows installer here: Zabbix Windows agents

2. Run installer.

• Double-click the downloaded .exe to launch the Wizard
• Click Next to continue

3. Accept License Agreement.

4. Choose installation folder.

5. Configure during setup.

• Server IP: 192.168.1.100
• Active checks: 192.168.1.100
• Hostname: WindowsServer01
• Enable the check box for Add agent location to the PATH
• Click Install, then Finish

6. Verify service.

sc query "Zabbix Agent 2"

sc query "Zabbix Agent 2"

7. Allow firewall.

• Open Windows Defender Firewall → Inbound Rules → New Rule → Port → TCP 10050 → Allow → All profiles → Name: Zabbix Agent 2

Verification & Troubleshooting

You’re all set! Your system is now ready to be monitored with Nagios XI. To learn more about the Zabbix Agent Wizard, take a look at this article: How to Use the Zabbix Agent Wizard in Nagios XI.

Prerequisites

Ensure you have the following:

• An AlmaLinux 9 server with root or sudo access
• A running Nagios Log Server 2024R2 instance
• Network connectivity between the AlmaLinux server and Log Server (default port 5544 open)
• SELinux disabled or properly configured for rsyslog

Step 1: Access Log Source Setup in Nagios Log Server

1. Log into your Nagios Log Server web interface.

2. Click the + button in the left sidebar and the one at the bottom.

Step 2: Run the Auto-Configuration Script on AlmaLinux 9

1. Copy the setup script command shown in the Nagios interface. It looks similar to:

curl -sS -O http://<logserver-ip>/nagioslogserver/scripts/setup-linux.sh
sudo bash setup-linux.sh -s <logserver-ip> -p 5544

curl -sS -O http://<logserver-ip>/nagioslogserver/scripts/setup-linux.sh
sudo bash setup-linux.sh -s <logserver-ip> -p 5544

• Replace <logserver-ip> with the IP or DNS name of your Nagios Log Server.

2. Example Output:

curl -sS -O http://192.168.1.123/nagioslogserver/scripts/setup-linux.sh 
sudo bash setup-linux.sh -s 192.168.0.31 -p 5544

curl -sS -O http://192.168.1.123/nagioslogserver/scripts/setup-linux.sh 
sudo bash setup-linux.sh -s 192.168.0.31 -p 5544

3. Confirm the script output shows successful configuration:

• “Detected rsyslog…”
• “rsyslog configuration check passed.”
• “rsyslog is running with the new configuration.”

Step 3: Verify Logs Are Reaching Nagios Log Server

1. In the Nagios Log Server web UI, enter the AlmaLinux server’s IP under Verify Incoming Logs.

2. Alternatively, go to Dashboards > Nagios Log Server Search and run:

host.ip:<AlmaLinux-IP>

host.ip:<AlmaLinux-IP>

3. To test log transmission, run:

logger This is a test log entry

logger This is a test log entry

4. Verify the entry appears in the Nagios Log Server interface.

Optional: Manual rsyslog Configuration (Advanced)

If you prefer not to use the script, follow these steps:

1. Create a custom rsyslog config file:

sudo nano /etc/rsyslog.d/.conf

sudo nano /etc/rsyslog.d/.conf

2. Add the following content (replace IP and port as needed):

# ### begin forwarding rule ### NAGIOSLOGSERVER
$WorkDirectory /var/lib/rsyslog
$ActionQueueFileName fwdRule1
$ActionQueueMaxDiskSpace 1g
$ActionQueueSaveOnShutdown on
$ActionQueueType LinkedList
$ActionResumeRetryCount -1
*.* @@192.168.1.123:5544
# ### end of the forwarding rule ###

# ### begin forwarding rule ### NAGIOSLOGSERVER
$WorkDirectory /var/lib/rsyslog
$ActionQueueFileName fwdRule1
$ActionQueueMaxDiskSpace 1g
$ActionQueueSaveOnShutdown on
$ActionQueueType LinkedList
$ActionResumeRetryCount -1
*.* @@192.168.1.123:5544
# ### end of the forwarding rule ###

3. Restart rsyslog:

sudo systemctl restart rsyslog

sudo systemctl restart rsyslog

4. Verify logs are received as in Step 3.

Step 4: Adding More Log Sources

Use the + Add Log Source button to configure:

• Network Device
• Application Logs
• Archived logs

Conclusion

You’ve successfully configured AlmaLinux 9 to send logs to Nagios Log Server 2024R2. Whether using the automatic script or manual configuration, this setup allows centralized logging, simplifying monitoring and analysis. For advanced use cases, explore custom filtering, alerting, and integrations in the Nagios Log Server interface.

Resource

• Nagios Log Server Knowledgebase
• Nagios Support Forum
• AlmaLinux Documentation

Prerequisites

Ensure you have:

• A Pop!_OS 24.04 LTS system with sudo privileges
• An operational Nagios XI server
• Network connectivity between Pop!_OS and Nagios XI (Port 5693 open)
• Stable internet access for downloading required packages

Step 1: Install NCPA Using DEB Package

Since Pop!_OS is Ubuntu-based, the DEB package method is recommended:

cd /tmp
wget https://assets.nagios.com/downloads/ncpa3/ncpa-latest.amd64.deb
sudo dpkg -i ncpa-latest.amd64.deb

cd /tmp
wget https://assets.nagios.com/downloads/ncpa3/ncpa-latest.amd64.deb
sudo dpkg -i ncpa-latest.amd64.deb

Resolve dependency issues if encountered:

sudo apt-get install -f

sudo apt-get install -f

Step 2: Configure NCPA Token

NCPA requires an authentication token (community string):

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

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

Modify the line:

community_string = mytoken

community_string = mytoken

to a secure, unique token:

community_string = Str0ngT0k3n2025

community_string = Str0ngT0k3n2025

Save the file and exit (Ctrl+O, Enter, Ctrl+X).

Step 3: Restart NCPA Service

Apply the new configuration:

sudo systemctl restart ncpa
sudo systemctl status ncpa

sudo systemctl restart ncpa
sudo systemctl status ncpa

Ensure the service shows as active (running).

Step 4: Configure Firewall

Allow NCPA communication on port 5693:

sudo ufw allow 5693/tcp
sudo ufw reload

sudo ufw allow 5693/tcp
sudo ufw reload

Step 5: Test NCPA Interface

Open your browser and navigate to:

https://<PopOS-IP>:5693/

https://<PopOS-IP>:5693/

Accept SSL warnings (self-signed certificate). Login using your token (Str0ngT0k3n2025) to access the NCPA dashboard.

Step 6: Integrate Pop!_OS Host into Nagios XI

1. Log into Nagios XI.
2. Navigate to Configure > Configuration Wizards.
3. Select NCPA from the wizard list.
4. Input the following details:
   • Host IP: Your Pop!_OS machine’s IP
   • Token: Str0ngT0k3n2025
   • Port: 5693
5. Select desired metrics for monitoring (CPU, Memory, Disk, Processes).
6. Complete the wizard and apply the configuration.

Verify the host addition by navigating to Monitoring > Hosts.

Troubleshooting

• NCPA not running:

sudo systemctl restart ncpa
sudo systemctl status ncpa

sudo systemctl restart ncpa
sudo systemctl status ncpa

• Firewall Issues:

sudo ufw status | grep 5693

sudo ufw status | grep 5693

• Token mismatch:

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

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

Confirm your token matches the Nagios XI configuration.

• Checking logs:

cat /usr/local/ncpa/var/log/ncpa.log

cat /usr/local/ncpa/var/log/ncpa.log

Conclusion

You have successfully configured NCPA on Pop!_OS 24.04 LTS and integrated it with Nagios XI. This setup ensures proactive monitoring and quick troubleshooting of system performance and health issues. For more advanced capabilities, explore passive checks and custom plugins available through the Nagios Knowledgebase and the NCPA documentation.

Prerequisites

Before you begin:

• A Clear Linux system updated with sudo swupd update
• Sudo or root access on the Clear Linux system
• Nagios XI installed and reachable
• Network connectivity between Clear Linux and Nagios XI (UDP port 161 open)

Step 1: Install SNMP Tools on Clear Linux

Clear Linux doesn’t include SNMP utilities by default. Install them:

sudo swupd bundle-add net-tools
sudo swupd bundle-add sysadmin-basic

sudo swupd bundle-add net-tools
sudo swupd bundle-add sysadmin-basic

Then install SNMP manually:

sudo swupd bundle-add package-utils
curl -O https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/Packages/n/net-snmp-5.7.2-49.el7.x86_64.rpm
rpm2cpio net-snmp-5.7.2-49.el7.x86_64.rpm | cpio -idmv
sudo cp -r ./usr/* /usr/

sudo swupd bundle-add package-utils
curl -O https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/Packages/n/net-snmp-5.7.2-49.el7.x86_64.rpm
rpm2cpio net-snmp-5.7.2-49.el7.x86_64.rpm | cpio -idmv
sudo cp -r ./usr/* /usr/

Note: Use the latest compatible SNMP RPM or build from source if preferred.

Step 2: Configure SNMP

SNMP v2c Configuration

1. Create a new config file:

sudo mkdir -p /etc/snmp
echo 'rocommunity Str0ngC0mmunity 10.25.5.12' | sudo tee /etc/snmp/snmpd.conf

sudo mkdir -p /etc/snmp
echo 'rocommunity Str0ngC0mmunity 10.25.5.12' | sudo tee /etc/snmp/snmpd.conf

2. Start SNMP (foreground):

sudo /usr/sbin/snmpd -f -Lo

sudo /usr/sbin/snmpd -f -Lo

To run it as a background process, remove -f.

SNMP v3 Configuration (Optional)

SNMP v3 requires a more complex setup. Use net-snmp utilities to create a user:

sudo net-snmp-create-v3-user -ro -a SHA -A Str0ng@uth3ntic@ti0n -x AES -X Str0ngPriv@cy nagios

sudo net-snmp-create-v3-user -ro -a SHA -A Str0ng@uth3ntic@ti0n -x AES -X Str0ngPriv@cy nagios

This may require additional scripting or compiling from source.

Step 3: Open the SNMP Port (UDP 161)

Clear Linux typically uses iptables. Allow SNMP traffic:

sudo iptables -I INPUT -p udp --dport 161 -j ACCEPT
sudo iptables-save > /etc/iptables/rules.v4

sudo iptables -I INPUT -p udp --dport 161 -j ACCEPT
sudo iptables-save > /etc/iptables/rules.v4

Verify:

sudo iptables -L -n | grep 161

sudo iptables -L -n | grep 161

Step 4: Test SNMP Communication

From your Nagios XI server:

SNMP v2c:

snmpwalk -v2c -c Str0ngC0mmunity <clearlinux-ip>

snmpwalk -v2c -c Str0ngC0mmunity <clearlinux-ip>

SNMP v3:

snmpwalk -v3 -u nagios -l authPriv -a SHA -A Str0ng@uth3ntic@ti0n -x AES -X Str0ngPriv@cy <clearlinux-ip>

snmpwalk -v3 -u nagios -l authPriv -a SHA -A Str0ng@uth3ntic@ti0n -x AES -X Str0ngPriv@cy <clearlinux-ip>

Expected Output:

iso.3.6.1.2.1.1.1.0 = STRING: "Linux clearlinux ..."

iso.3.6.1.2.1.1.1.0 = STRING: "Linux clearlinux ..."

Step 5: Add Host in Nagios XI Using SNMP Wizard

1. Log into Nagios XI
2. Navigate to Configure > Run a configuring wizard
3. Select Linux SNMP
4. Enter the Clear Linux IP and SNMP credentials
5. Choose metrics (CPU, memory, disk, etc.)
6. Apply and save configuration

Troubleshooting Tips

• SNMP Daemon Not Running: ps aux | grep snmpd
• Firewall Blocking Traffic: Ensure port 161 is open and rules are persistent
• Permission Issues: Verify snmpd.conf is readable and SNMP is correctly installed

Conclusion

Clear Linux can be monitored via SNMP with a few workarounds despite its stateless design. Once configured, Nagios XI provides deep insight into your system using lightweight, agentless checks.

Resources:

• Nagios SNMP Guide
• Net-SNMP Docs
• Nagios Knowledgebase

Prerequisites

Ensure:

• A NixOS system (updated with sudo nix-channel --update && sudo nixos-rebuild switch) with sudo or root access.
• A running Nagios XI instance (latest version recommended).
• Network connectivity between NixOS and Nagios XI (UDP port 161 open).
• Access to edit /etc/nixos/configuration.nix.

Step 1: Install SNMP Packages

Option 1: Imperative Installation (For Testing)

nix-env -iA nixos.net-snmp

nix-env -iA nixos.net-snmp

Verify:

snmpd --version

snmpd --version

Option 2: Declarative Installation (Recommended)

Add to /etc/nixos/configuration.nix:

environment.systemPackages = with pkgs; [ net-snmp ];

environment.systemPackages = with pkgs; [ net-snmp ];

Apply changes:

sudo nixos-rebuild switch

sudo nixos-rebuild switch

Verify:

/run/current-system/sw/bin/snmpd --version

/run/current-system/sw/bin/snmpd --version

Step 2: Configure SNMP Access

Option 1: SNMP v2c

sudo mkdir -p /etc/snmp
sudo cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.bak 2>/dev/null || true
echo "rocommunity Str0ngC0mmunity <Nagios-XI-IP>" | sudo tee /etc/snmp/snmpd.conf

sudo mkdir -p /etc/snmp
sudo cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.bak 2>/dev/null || true
echo "rocommunity Str0ngC0mmunity <Nagios-XI-IP>" | sudo tee /etc/snmp/snmpd.conf

Replace <Nagios-XI-IP> with your Nagios XI server IP (e.g., 10.25.5.12).

Option 2: SNMP v3 (Secure)

sudo systemctl stop snmpd.service
sudo net-snmp-create-v3-user -ro -a SHA -A Str0ng@uth3ntic@ti0n -x AES -X Str0ngPriv@cy nagios
sudo mkdir -p /etc/snmp
echo "rouser nagios authPriv" | sudo tee /etc/snmp/snmpd.conf

sudo systemctl stop snmpd.service
sudo net-snmp-create-v3-user -ro -a SHA -A Str0ng@uth3ntic@ti0n -x AES -X Str0ngPriv@cy nagios
sudo mkdir -p /etc/snmp
echo "rouser nagios authPriv" | sudo tee /etc/snmp/snmpd.conf

Step 3: Configure Firewall

Declarative Method (Recommended)

Add to /etc/nixos/configuration.nix:

networking.firewall.allowedUDPPorts = [ 161 ];

networking.firewall.allowedUDPPorts = [ 161 ];

Apply changes:

sudo nixos-rebuild switch

sudo nixos-rebuild switch

Verify:

sudo iptables -L -n | grep 161

sudo iptables -L -n | grep 161

Imperative Method (Temporary)

sudo iptables -I INPUT -p udp --dport 161 -j ACCEPT
sudo mkdir -p /etc/iptables
sudo iptables-save > /etc/iptables/rules.v4

sudo iptables -I INPUT -p udp --dport 161 -j ACCEPT
sudo mkdir -p /etc/iptables
sudo iptables-save > /etc/iptables/rules.v4

Step 4: Enable SNMP Daemon on Boot

Add to /etc/nixos/configuration.nix:

systemd.services.snmpd = {
  description = "SNMP Daemon";
  after = [ "network.target" ];
  wantedBy = [ "multi-user.target" ];
  serviceConfig = {
    ExecStart = "${pkgs.net-snmp}/bin/snmpd -c /etc/snmp/snmpd.conf";
    Restart = "on-failure";
  };
};

systemd.services.snmpd = {
  description = "SNMP Daemon";
  after = [ "network.target" ];
  wantedBy = [ "multi-user.target" ];
  serviceConfig = {
    ExecStart = "${pkgs.net-snmp}/bin/snmpd -c /etc/snmp/snmpd.conf";
    Restart = "on-failure";
  };
};

Apply changes:

sudo nixos-rebuild switch

sudo nixos-rebuild switch

Verify:

sudo systemctl status snmpd.service

sudo systemctl status snmpd.service

Step 5: Test SNMP Communication

Install SNMP tools on Nagios XI (if needed):

sudo dnf install net-snmp-utils -y

sudo dnf install net-snmp-utils -y

SNMP v2c

snmpwalk -v2c -c Str0ngC0mmunity <NixOS-IP>

snmpwalk -v2c -c Str0ngC0mmunity <NixOS-IP>

SNMP v3

snmpwalk -v3 -u nagios -l authPriv -a SHA -A Str0ng@uth3ntic@ti0n -x AES -X Str0ngPriv@cy <NixOS-IP>

snmpwalk -v3 -u nagios -l authPriv -a SHA -A Str0ng@uth3ntic@ti0n -x AES -X Str0ngPriv@cy <NixOS-IP>

Expected output:

iso.3.6.1.2.1.1.1.0 = STRING: "Linux nixos-<hostname> <version> x86_64"

iso.3.6.1.2.1.1.1.0 = STRING: "Linux nixos-<hostname> <version> x86_64"

Step 6: Add Host to Nagios XI Using SNMP Wizard

1. Log into Nagios XI
2. Navigate to Configure > Configuration Wizards
3. Select Linux SNMP
4. Configure Host:
   • IP: 192.168.0.31
   • SNMP Version: v2c or v3
   • v2c Community: Str0ngC0mmunity
   • v3 Username: nagios, Auth Protocol: SHA, Auth Password: Str0ng@uth3ntic@ti0n, Privacy Protocol: AES, Privacy Password: Str0ngPriv@cy
5. Click Next, select metrics (CPU, memory, disk, etc.)
6. Click Finish and apply
7. Verify monitoring in Monitoring > Hosts

Troubleshooting

SNMP Not Responding

sudo systemctl status snmpd
ps aux | grep snmpd
sudo systemctl restart snmpd

sudo systemctl status snmpd
ps aux | grep snmpd
sudo systemctl restart snmpd

Firewall Issue

sudo iptables -L -n
sudo nc -zu <NixOS-IP> 161

sudo iptables -L -n
sudo nc -zu <NixOS-IP> 161

Log SNMP Output

sudo /run/current-system/sw/bin/snmpd -f -Lo -c /etc/snmp/snmpd.conf

sudo /run/current-system/sw/bin/snmpd -f -Lo -c /etc/snmp/snmpd.conf

Conclusion

You’ve configured SNMP on NixOS and integrated it with Nagios XI for agentless, real-time monitoring as of March 28, 2025. NixOS’s declarative nature requires explicit setup for SNMP, but this approach ensures reliability. For long-term stability, maintain all configurations (packages, firewall, services) in /etc/nixos/configuration.nix. Explore further customization in the Nagios SNMP Guide, Net-SNMP Documentation, or NixOS Manual.

Step 1: Add a Log Source in Nagios Log Server

1. Log in to Nagios Log Server.
2. Click + Add Log Source.
3. Select Linux as the source type.

Step 2: Run the Auto-Configuration Script on openSUSE

1. Copy the script command from the Linux Source Setup page.
2. On the openSUSE server, run:

curl -sS -O http://<NagiosLogServerIP>/nagioslogserver/scripts/setup-linux.sh sudo bash setup-linux.sh -s <NagiosLogServerIP> -p 5544

This sets up rsyslog to forward logs to the Log Server.

Step 3: Verify Logs are Received

• Return to the setup page in Nagios Log Server.
• Enter the openSUSE server’s IP in the Verify Incoming Logs section.
• Or run a host query from Dashboards > Search:

host.ip:<openSUSE-IP>

• To test manually, run:

logger "This is a test log entry"

Step 4: (Optional) Manual Configuration

1.Check the rsyslog work directory:

ls -d /var/lib/rsyslog || ls -d /var/spool/rsyslog

2.Manually create or edit the forwarding config:

sudo vi /etc/rsyslog.d/99-nagioslogserver.conf

Add the following line:

*.* @<NagiosLogServerIP>:5544;RSYSLOG_SyslogProtocol23Format

3.Restart rsyslog:

sudo systemctl restart rsyslog.service

Step 5: Link to Nagios XI

• Utilize queries and alert conditions in Nagios Log Server to trigger alerts in Nagios XI via API or event handlers.
• Integrate log monitoring with service checks for a comprehensive system overview.

Final Notes

• Logs are forwarded over port 5544; ensure openSUSE’s firewall allows outbound traffic on this port.
• The + Add Log Source feature in Nagios Log Server allows you to add additional log sources as needed.
• Regularly review logs in Nagios Log Server to detect system anomalies and security threats.

Conclusion

By following this guide, you can successfully monitor and analyze openSUSE 15 logs with Nagios Log Server 2024R2 in Nagios XI. This setup ensures proactive issue detection and enhances overall system observability. For best results, maintain regular log audits and optimize alert configurations to capture critical events.

Step 1: Install SNMP on openSUSE 15

As root, run:

sudo zypper install net-snmp net-snmp-tools

sudo zypper install net-snmp net-snmp-tools

Step 2: Configure SNMP v2c Access

1. Backup the default configuration:

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

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

2. Replace the configuration with:

 echo 'rocommunity Str0ngC0mmunity <Nagios-XI-IP>' | sudo tee /etc/snmp/snmpd.conf

 echo 'rocommunity Str0ngC0mmunity <Nagios-XI-IP>' | sudo tee /etc/snmp/snmpd.conf

3. Restart SNMP:

sudo systemctl restart snmpd.service

sudo systemctl restart snmpd.service

Step 3: Open Firewall Port 161/UDP

sudo firewall-cmd --zone=public --add-port=161/udp
sudo firewall-cmd --zone=public --add-port=161/udp --permanent

sudo firewall-cmd --zone=public --add-port=161/udp
sudo firewall-cmd --zone=public --add-port=161/udp --permanent

Step 4: Enable SNMP on Boot

sudo systemctl enable snmpd.service

sudo systemctl enable snmpd.service

Step 5: Test SNMP Connectivity

From your Nagios XI server:

cd /usr/local/nagios/libexec
./check_snmp_storage.pl -H <openSUSE-IP> -C Str0ngC0mmunity -m "^/$" -w 2 -c 4

cd /usr/local/nagios/libexec
./check_snmp_storage.pl -H <openSUSE-IP> -C Str0ngC0mmunity -m "^/$" -w 2 -c 4

You should receive disk usage output. If not, review SNMP and firewall settings.

Step 6: Use the Linux SNMP Wizard in Nagios XI

1. Go to Configure > Run a Configuration Wizard > Linux SNMP.
2. Enter the openSUSE server’s IP and SNMP community string.
3. Select the metrics you want (disk usage, processes, etc.).
4. Adjust thresholds as needed.
5. Finish the wizard to apply the configuration.

Final Notes

• openSUSE uses the same net-snmp tools as other Linux distributions.
• Port 161/UDP must be open to receive SNMP queries.
• SNMP v3 setup is also supported if stronger security is required.

Conclusion

By configuring SNMP on openSUSE 15 and integrating it with Nagios XI, you gain detailed visibility into system performance without installing additional agents. Regularly reviewing Nagios XI dashboards and refining SNMP configurations ensures optimal monitoring and proactive issue resolution.

Step 1: Install NCPA on openSUSE 15

Option 1: Using Nagios Repository (Recommended)

• Add the Nagios repository for SUSE 15+ (available from https://repo.nagios.com).
• Run:

 sudo zypper install ncpa

 sudo zypper install ncpa

Option 2: Manual RPM Installation

• Run the following:

cd /tmp wget https://assets.nagios.com/downloads/ncpa3/ncpa-<version>.rpm sudo rpm -ivh ncpa-<version>.rpm

cd /tmp wget https://assets.nagios.com/downloads/ncpa3/ncpa-<version>.rpm sudo rpm -ivh ncpa-<version>.rpm

Step 2: Configure NCPA

1. Edit the configuration file:

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

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

2. Set a secure token by modifying:

community_string = Str0ngT0k3n

community_string = Str0ngT0k3n

3. Save and exit (:wq).

Step 3: Restart the NCPA Service

sudo systemctl restart ncpa

sudo systemctl restart ncpa

Step 4: Allow NCPA Port Through the Firewall

sudo firewall-cmd --zone=public --add-port=5693/tcp
sudo firewall-cmd --zone=public --add-port=5693/tcp --permanent

sudo firewall-cmd --zone=public --add-port=5693/tcp
sudo firewall-cmd --zone=public --add-port=5693/tcp --permanent

Step 5: Verify the NCPA Web Interface

1. Open a web browser and go to:

https://<openSUSE-IP>:5693

https://<openSUSE-IP>:5693

2. Accept any SSL warnings.

3. Log in using your configured token.

Step 6: Add the Host in Nagios XI

1. Log in to Nagios XI.
2. Navigate to Configure > Monitoring Wizard > NCPA.
3. Enter your openSUSE IP and token.
4. Select services (CPU, memory, etc.) to monitor.
5. Complete the wizard to apply monitoring.

Final Tip

• NCPA listens on TCP port 5693.
• Use a strong token to prevent unauthorized access.
• The NCPA web interface includes built-in help and endpoint documentation.

Conclusion

By following this guide, you can successfully monitor openSUSE 15 with Nagios XI using NCPA. This setup allows you to track essential system metrics efficiently and receive alerts on performance issues. Regularly check Nagios XI dashboards to ensure accurate data collection and troubleshoot any connectivity issues by reviewing firewall rules and service statuses.

This guide details how to install NCPA on Clear Linux and configure it for monitoring within Nagios XI, adapting to Clear Linux’s unique environment.

Prerequisites

Ensure:

• A Clear Linux system (updated with sudo swupd update) with sudo access.
• A running Nagios XI instance (latest version recommended).
• Network connectivity between Clear Linux and Nagios XI (port 5693 open).
• Basic utilities installed: curl, rpm2cpio, cpio, and python3 (Clear Linux includes Python by default).

Step 1: Install Required Tools

Clear Linux doesn’t include rpm2cpio or cpio by default. Install them:

sudo swupd bundle-add dev-utils

Verify:

rpm2cpio --version
cpio --version

Step 2: Download and Extract NCPA

Since Clear Linux doesn’t support RPM packages natively, extract the NCPA RPM manually:

1. Create a Working Directory:

mkdir -p ~/ncpa && cd ~/ncpa

2. Download the Latest-1 NCPA RPM:

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

3. Extract the RPM:

rpm2cpio ncpa-latest.el9.x86_64.rpm | cpio -idmv

Step 3: Deploy NCPA Files

Move the extracted files to their appropriate system locations:

sudo cp -r ./usr/* /usr/
sudo cp -r ./etc/* /etc/
sudo cp -r ./var/* /var/

Step 4: Configure the NCPA Token

1. Edit the Config File:

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

2. Set a Secure Token:

community_string = Str0ngT0k3n2025

Step 5: Start the NCPA Listener

Option 1: Manual Start

sudo /usr/local/ncpa/ncpa_listener &

Option 2: Create a Systemd Service

1. Create a service file:

sudo nano /etc/systemd/system/ncpa.service

2. Add:

[Unit]
Description=NCPA Listener Service
After=network.target

[Service]
Type=simple
ExecStart=/usr/local/ncpa/ncpa_listener
Restart=on-failure

[Install]
WantedBy=multi-user.target

3. Enable and start:

sudo systemctl daemon-reload
sudo systemctl enable ncpa
sudo systemctl start ncpa

4. Verify:

sudo systemctl status ncpa

Step 6: Configure the Firewall

1. Add Rule:

sudo iptables -I INPUT -p tcp --dport 5693 -j ACCEPT

2. Persist the Rule:

sudo mkdir -p /etc/iptables sudo iptables-save > /etc/iptables/rules.v4

3. Verify:

sudo iptables -L -n | grep 5693

Step 7: Test NCPA Locally

1. Access the NCPA Web Interface:

https://<ClearLinux-IP>:5693/

2. Accept Certificate

3. Log In:

• Use the token (e.g., Str0ngT0k3n2025) to access the dashboard.

Step 8: Integrate with Nagios XI

1. Log into Nagios XI
2. Run the NCPA Wizard
3. Configure the Host:
   • IP Address: Clear Linux IP
   • Port: 5693
   • Token: Str0ngT0k3n2025
4. Apply Configuration
5. Verify Monitoring

Troubleshooting Tips

• NCPA Not Running:

ps aux | grep ncpa_listener
sudo systemctl status ncpa
cat /usr/local/ncpa/var/log/ncpa.log

• Port Blocked:

sudo nc -zv <ClearLinux-IP> 5693

• Nagios XI Issues:
  • Verify token and IP
  • Check Nagios log: /usr/local/nagiosxi/var/ncpa.log

Conclusion

You’ve manually installed NCPA on Clear Linux and integrated it with Nagios XI. While Clear Linux lacks official NCPA support, this workaround enables robust monitoring. For stability, maintain the systemd service and firewall persistence. Explore passive checks via NRDP or custom plugins.

Resources:

• Nagios NCPA Project
• Nagios Support Forum
• Nagios Knowledgebase