Centralized User Management

Fusion has always provided a lot of value by enabling users to visualize status data from across their distributed Nagios deployments. It’s already a must-have for distributed environments and users who employ multiple Nagios Monitoring Solutions. Namely, Fusion’s ability to aggregate data from Nagios XI, Nagios Core, Nagios Log Server, and Nagios Network Analyzer systems and display it in custom dashboards and tactical displays. But one area of untapped potential has always been in serving as a platform for centralized management of other Nagios systems.

No longer is that the case! New in 2026R1 is the ability to copy users from one fused Nagios XI system to others with a few clicks, using the new Centralized Management menu. Although a humble first step, this new feature lays the foundation that will be used going forward to enable many more management capabilities in the future.

Learn more about using the Centralized User Management function:

Managing Nagios XI Users with Nagios Fusion

As an added bonus, this addition also necessitated adding a new update users’ endpoint (PUT/system/user) to the Nagios XI API, so both solutions were enhanced in the process.

System Profile

You’ll also notice a new System Profile menu, which can be used to generate and download a profile with a single click. The System Profile zip contains a wealth of data about your setup and serves as an invaluable resource for troubleshooting and support.

Fixes

Several issues were also resolved in this release to make Fusion more stable and reliable:

• Server polling interval is now being updated properly.
• The Administrator and User Guides are now being displayed correctly.
• The ssl_hostname_verify parameter is now being passed when adding a server via the API.
• Users located in AD groups will now show up in the “Add User from AD/LDAP” page.

Learn More

This article is a great resource for learning more about all of the capabilities:

If you’re not currently using Nagios Fusion and would like to take it for a spin, you can find the free, fully functional trial options:

The Admin Guide is another excellent resource for learning how to manage and get the most out of all of the capabilities:

New Monitoring Wizards

Three great new wizards join the ranks in XI 2024R2: Kubernetes, Zabbix Agent, and the Generic Plugin Wizard. We’ve also updated the NSClient++ Wizard.

Kubernetes with NCPA

This Premium wizard enables you to monitor Kubernetes clusters via the NCPA agent. Available metrics include Nodes Active, Daemon Sets, Deployments, Jobs Failed, Pod Restarts, Replica Sets, Stateful Sets, TLS, PVC, and Unbound PVS. You can learn more about the initial setup here:

Monitoring Kubernetes Clusters with Nagios XI and NCPA

Zabbix Agent

With the new Zabbix Agent Wizard, one of XI 2024R2’s Premium features, you’ll be able to leverage your existing Windows and Linux Zabbix agents to set up comprehensive monitoring in Nagios XI:

Monitoring Zabbix Agents with Nagios XI

Generic Plugin Wizard

The new Generic Plugin Wizard provides a quick way to set up monitoring using custom plugins. This enables you to create a command to execute your custom plugins, and setup a Nagios check for it without the need to go to the Core Config Manager.

This document provides step-by-step details on using the wizard:

Using the Generic Plugin Wizard in Nagios XI

NSClient++ Wizard

Also worth mentioning is that we added support for check_nrpe to the NSClient++ Wizard and updated its status from Legacy, making it once again a current wizard.

SSO

A big request we’ve seen over time from our users is an SSO option, and we’re excited to introduce Single Sign-on via Microsoft Azure Active Directory in 2024R2. You can access this feature in Admin > External Sign-On(SSO) menu and can learn more about setting it up here:

Configuring SSO in Nagios XI 2024R2

NagVis Enhancements:

• Most Map elements now have relative positioning
• The Edit Map menu can now be accessed with a right-click
• Added missing support in NagVis for Nagios custom variables with an NDO backend

Nagios Core Updated

The Nagios Core engine at the heart of Nagios XI has been updated to 4.5.9.

NCPA v3 Support for Deploy Agent

The Auto Deployment feature, which enables you to push NCPA (the Nagios Cross Platform Agent) to remote hosts right from the Nagios XI UI, previously only supported NCPA v2, an older version of the agent. Now you can also deploy NCPA v3, the latest version, with the tool. This enables you to take advantage of all of the updates that went into v3, while still leveraging the convenience and centralized control of Auto Deployment.

Introducing Premium

In Nagios XI 2024R2, we’re introducing a new Premium Features model. Premium Features are a benefit of active license Maintenance. To ensure continued access to these features, we suggest you renew your Nagios XI license annually. In the event that your license expires, simply renew your license, and the full list of Premium Features will regain functionality automatically. The Premium features include:

• Single Sign-On (SSO) via MS Azure AD
• The Remote Workers Nagios Mod-Gearman management interface
• Premium Wizards
  • Prometheus
  • vSphere
  • Oracle Tablespace, Serverspace, and Query
  • MSSQL Server, Database, and Query
  • Kubernetes
  • HyperV
  • Docker
  • Cloud VM (DigitalOcean, Google Cloud, Linode, Azure, and Rackspace)
  • Amazon EC2 and S3
  • Zabbix Agent
  • OpenAI Usage

Changelog

You can find the full Changelog here if you’d like to review all the changes, including details on bug fixes and security patches:

Nagios XI Changelog

Getting Started

If you’re new to Nagios XI and want to take 2024R2 for a spin, you’ll find the free, fully functional trial version here:

Nagios XI Downloads

Another great resource is this article, which provides tips and resources to help you make the most of your free trial:

If you’d like a guided personal tour of XI geared toward your unique requirements or a hands-on remote session with one of our techs to help you get a few things set up, we’d love to offer you a free Demo or Quickstart. To set this up, or for any other help you may need, feel free to email sales@nagios.com so we can give you a hand. Our sales and technical teams will do all they can to help you maximize your free trial!

Optimizing Port Operations: The Challenge for Hindustan Ports Pvt. Ltd.

In the bustling world of global trade and logistics, port operations are the unsung heroes, facilitating the seamless flow of goods across continents. Hindustan Ports Pvt. Ltd. (HPPL), a prominent player in India’s maritime sector, has long been at the forefront of this intricate dance, managing a vast network of terminals, cargo handling equipment, and complex IT infrastructure. For years, HPPL grappled with the inherent challenges of maintaining peak operational efficiency in a demanding 24/7 environment. Their journey towards achieving unparalleled reliability and foresight in their operations is a compelling testament to the transformative power of robust IT infrastructure monitoring, specifically through the strategic implementation of Nagios XI.

Pre-Nagios XI: The Fragmented Monitoring Landscape and Operational Hurdles

Before the advent of Nagios XI, HPPL’s IT landscape was a patchwork of disparate monitoring tools, each offering a limited view into specific silos of their infrastructure. Servers, network devices, applications, and databases were monitored in isolation, leading to a fragmented understanding of their overall health. This reactive approach meant that issues were often detected only after they had escalated, leading to costly downtime, operational bottlenecks, and, most critically, potential delays in cargo movement. The IT team, a dedicated but often overwhelmed group, spent a significant portion of their time firefighting rather than focusing on strategic initiatives. They struggled with:

• Lack of Centralized IT Visibility: No single pane of glass offered a comprehensive overview of the entire IT ecosystem.
• Reactive Problem Resolution: Alerts were often too late, indicating a problem that had already impacted operations.
• Manual Monitoring Overheads: Significant manual effort was required to check the status of various systems, leading to human error and inefficiency.
• Ineffective Capacity Planning: Without historical performance data and trend analysis, anticipating future resource needs was a shot in the dark.
• Inconsistent Performance Reporting: Generating meaningful reports for management was a cumbersome and time-consuming process.

Why Nagios XI? The Strategic Choice for Proactive IT Monitoring

Recognizing the urgent need for a unified, proactive, and intelligent monitoring solution, HPPL embarked on a thorough evaluation process. After extensive research and comparative analysis, Nagios XI emerged as the clear frontrunner. Its reputation for comprehensive monitoring capabilities, scalability, ease of use, and a vibrant community support ecosystem made it an attractive proposition. The decision was driven by Nagios XI’s ability to:

• Monitor Diverse IT Infrastructure: From Windows and Linux servers to network switches, routers, firewalls, and critical port-specific applications, Nagios XI offered a versatile monitoring framework.
• Provide Proactive Alerts: Its sophisticated alerting mechanisms promised to notify the team of potential issues before they impacted services.
• Offer Customizable Dashboards: The ability to create tailored dashboards would empower different teams with relevant, real-time insights.
• Facilitate Accurate Capacity Planning: Performance trending and historical data analysis would enable informed decisions about infrastructure scaling.
• Streamline IT Reporting: Automated reporting features would free up valuable IT resources.

Implementing Nagios XI: A Phased Approach to Comprehensive Monitoring

The implementation of Nagios XI at HPPL was a phased but meticulously planned undertaking. The initial phase focused on deploying the core Nagios XI server and integrating it with critical network devices and key operational servers. The IT team, with support from Nagios professionals, underwent intensive training to leverage the full potential of the platform. They began by defining critical service checks, setting up thresholds, and configuring notification rules.

As the team grew more proficient, the scope of monitoring expanded rapidly. They integrated:

• Cargo Management Systems (CMS) Monitoring: Ensuring the availability and performance of applications crucial for tracking and managing cargo.
• Terminal Operating Systems (TOS) Health: Monitoring the health of systems that orchestrate the movement of containers and equipment within the port.
• Custom Application Performance: Developing custom plugins to monitor proprietary applications vital to HPPL’s unique operations.
• Environmental Sensor Monitoring: Even extending monitoring to environmental factors like temperature and humidity in critical data centers.

One of the most significant aspects of the implementation was the creation of highly customized dashboards. These dashboards provided different stakeholders—from network administrators to operations managers and even senior management—with a clear, concise, and real-time view of the systems relevant to their roles. A large display in the Network Operations Center (NOC) became a vibrant, dynamic representation of HPPL’s digital heartbeat, instantly highlighting any anomalies.

The Transformative Impact of Nagios XI on HPPL Operations

The impact of Nagios XI on Hindustan Ports Pvt. Ltd.’s operations was profound and immediate.

1. Enhanced Operational Uptime and Reliability

The shift from reactive to proactive monitoring was perhaps the most significant benefit. Nagios XI’s ability to detect subtle performance degradations or impending failures meant that the IT team could intervene before an outage occurred. For instance, early warnings about disk space utilization on a critical database server or high CPU load on a network switch allowed them to take corrective action, preventing what would have previously been significant downtime. This translated directly into fewer disruptions in cargo handling and smoother port operations.

2. Reduced Mean Time To Resolution (MTTR)

When issues did arise, Nagios XI’s precise alerting and detailed diagnostic information drastically reduced the time it took to identify the root cause and resolve the problem. The IT team no longer had to spend hours sifting through logs or manually checking systems; the alerts provided clear pointers, significantly cutting down MTTR and minimizing operational impact.

3. Optimized Resource Utilization and Capacity Planning

With comprehensive historical performance data at their fingertips, HPPL’s IT team gained invaluable insights into resource consumption patterns. They could identify underutilized resources, optimize existing infrastructure, and accurately forecast future capacity needs. This led to more efficient capital expenditure and avoided costly over-provisioning or under-provisioning of resources. For example, by analyzing trends in network traffic, they could strategically plan bandwidth upgrades well in advance of peak seasons.

4. Improved Security Posture

Nagios XI’s monitoring capabilities extended to security-related aspects, such as unauthorized login attempts, unusual network traffic patterns, and critical service status. While not a standalone security solution, it provided an additional layer of vigilance, alerting the team to potential security breaches or vulnerabilities that might otherwise go unnoticed.

5. Empowered Decision-Making

The customized dashboards and automated reports transformed how management viewed IT operations. They could now access real-time performance metrics and understand the direct impact of IT health on business objectives. This data-driven approach fostered better collaboration between IT and operations, leading to more informed strategic decisions.

6. Tangible Cost Savings

By preventing downtime, reducing MTTR, and optimizing resource utilization, Nagios XI delivered tangible cost savings. The indirect benefits, such as enhanced customer satisfaction due to reliable service and improved employee productivity, further amplified the return on investment.

Conclusion: Nagios XI – A Catalyst for Operational Excellence at HPPL

In conclusion, Hindustan Ports Pvt. Ltd.’s adoption of Nagios XI was not merely an IT upgrade; it was a strategic investment that fundamentally reshaped their operational resilience and efficiency. By providing a unified, intelligent, and proactive monitoring framework, Nagios XI empowered HPPL to maintain continuous vigilance over its complex infrastructure, ensuring that the wheels of global trade continue to turn smoothly. The success story of HPPL stands as a powerful testament to how a well-implemented monitoring solution can transform challenges into opportunities, paving the way for sustained growth and operational excellence in the dynamic world of port management.

In the fast-paced world of financial services, even a moment of downtime can have significant repercussions. Fidelity & Guaranty Life (F&G), a leading provider of annuity and life insurance solutions, understands this implicitly. To ensure the continuous availability and optimal performance of their critical IT infrastructure, F&G turned to Nagios, a powerful and versatile Nagios monitoring solution. This partnership has empowered F&G to proactively identify and resolve potential issues, leading to enhanced operational efficiency, improved service reliability, and ultimately, greater peace of mind.

The Challenge: Maintaining Peak Performance in a Complex IT Environment

As F&G’s business grew and their IT environment became increasingly complex, maintaining a holistic view of their infrastructure proved to be a significant challenge. Their diverse array of servers, network devices, applications, and databases generated a vast amount of data, making it difficult to pinpoint potential bottlenecks or emerging problems before they impacted critical services. The need for a centralized, comprehensive monitoring system became paramount.

The Solution: Nagios Core and Nagios Monitoring Powerhouse

After a thorough evaluation of various monitoring solutions, F&G selected Nagios for its proven reliability, extensive feature set, and active community support. They implemented a combination of Nagios Core, the open-source foundation, and Nagios XI, the enterprise-grade interface, to create a unified monitoring powerhouse tailored to their specific requirements.

• Comprehensive Monitoring: Nagios provides F&G with real-time monitoring of all critical infrastructure components, including servers (physical and virtual), network devices (routers, switches, firewalls), operating systems, applications, databases, and services.
• Proactive Alerting: The sophisticated alerting system in Nagios notifies F&G’s IT teams immediately when potential issues are detected, allowing them to take proactive steps before outages occur. Customizable escalation rules ensure the right personnel are informed at the right time.
• Centralized Visibility: Nagios XI’s intuitive web interface provides a single pane of glass view of the entire IT environment, making it easy for F&G’s teams to understand the health and performance of their systems at a glance.
• Performance Nagios Monitoring and Capacity Planning: Nagios tracks key performance indicators (KPIs) such as CPU utilization, memory usage, disk I/O, and network traffic, enabling F&G to identify performance bottlenecks and plan for future capacity needs.
• Customization and Flexibility: Nagios’ open architecture and extensive plugin ecosystem allow F&G to monitor virtually any aspect of their IT environment, including custom applications and in-house developed services.
• Reporting and Analytics: Nagios XI provides detailed reports and historical data, enabling F&G to analyze trends, identify recurring issues, and demonstrate compliance with internal and external regulations.

The Results: Enhanced Reliability and Operational Efficiency

The implementation of Nagios has yielded significant benefits for Fidelity & Guaranty Life:

• Reduced Downtime: Proactive monitoring and alerting have enabled F&G to identify and resolve potential issues before they escalate into service-impacting outages, significantly reducing downtime.
• Improved Service Reliability: By ensuring the continuous availability and optimal performance of their IT infrastructure, F&G has enhanced the reliability of their critical services for customers and partners.
• Increased Operational Efficiency: Centralized visibility and automated alerting have streamlined IT operations, freeing up valuable time and resources for F&G’s IT teams to focus on strategic initiatives.
• Faster Problem Resolution: Real-time alerts and detailed performance data enable F&G’s teams to quickly diagnose and resolve issues when they do occur, minimizing the impact on business operations.
• Enhanced Capacity Planning: Trend analysis and performance data provided by Nagios allow F&G to make informed decisions about capacity upgrades and resource allocation, ensuring they are well-prepared for future growth.

Looking Ahead: A Continued Partnership for IT Excellence

Fidelity & Guaranty Life’s success story with Nagios is a testament to the power of proactive and comprehensive IT monitoring. By leveraging Nagios’ robust features and flexibility, F&G has built a resilient and high-performing IT environment that supports their commitment to providing exceptional service. As F&G continues to grow and evolve, their partnership with Nagios will remain a crucial element in their strategy for achieving and maintaining IT excellence.

To learn about more ways Nagios can solve real life problems, check out our other Nagios Success Stories.

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.

Before starting, ensure you have:

• A macOS system running macOS 12 Monterey or later on Apple Silicon.
• Administrator privileges (sudo access).
• An active Nagios Core or Nagios XI server to receive monitoring data.
• Basic familiarity with the terminal and command-line tools.

Step 1: Verify SNMP Availability

macOS includes a built-in SNMP daemon (snmpd), but it’s not enabled by default. You don’t need to install it separately—only configure and activate it.

1.1 Check SNMP Version
Open Terminal and verify that SNMP tools are present:

snmpd --version

snmpd --version

You should see output like NET-SNMP version: 5.x.x. If not, macOS Monterey includes it natively, and we’ll proceed to configure it.

Step 2: Configure SNMP on macOS

The SNMP configuration file is located at /etc/snmp/snmpd.conf, but it may not exist yet. We’ll create and edit it.

2.1 Create or Edit the SNMP Configuration File
Run the following command to edit the configuration file:

sudo mkdir -p /etc/snmp
sudo nano /etc/snmp/snmpd.conf

sudo mkdir -p /etc/snmp
sudo nano /etc/snmp/snmpd.conf

2.2 Add Basic Configuration
Paste the following minimal configuration into /etc/snmp/snmpd.conf:

# Set a read-only community string (replace "public" with a secure value)
rocommunity Str0ngC0mmunity!

# Restrict access to your Nagios server's IP
rocommunity Str0ngC0mmunity! <Nagios_IP_address>

# Define system information
sysLocation "Your Location"
sysContact "Your Name <your.email@example.com>"
sysName "YourMacHostname"

# Set a read-only community string (replace "public" with a secure value)
rocommunity Str0ngC0mmunity!

# Restrict access to your Nagios server's IP
rocommunity Str0ngC0mmunity! <Nagios_IP_address>

# Define system information
sysLocation "Your Location"
sysContact "Your Name <your.email@example.com>"
sysName "YourMacHostname"

• Replace Str0ngC0mmunity! with a secure community string (like a password for SNMP).
• Replace <Nagios_IP_address> with the IP of your Nagios server.
• Customize sysLocation, sysContact, and sysName as needed.

Save and exit (Ctrl+X, then Y, then Enter).

2.3 Set Permissions
Ensure the file is readable by the SNMP daemon:

sudo chmod 600 /etc/snmp/snmpd.conf

sudo chmod 600 /etc/snmp/snmpd.conf

Step 3: Enable SNMP Service

macOS uses launchd to manage services, including snmpd. The SNMP daemon is pre-installed but disabled by default.

3.1 Locate the SNMP Daemon
The SNMP service is controlled by /System/Library/LaunchDaemons/org.net-snmp.snmpd.plist. You don’t need to create this file—it’s already present.

3.2 Enable the SNMP Service
Load and start the service:

sudo launchctl list | grep snmpd

sudo launchctl list | grep snmpd

You should see org.net-snmp.snmpd listed with a PID (process ID).

Step 4: Test SNMP Locally

4.1 Test SNMP Queries
Use the snmpwalk command to verify that SNMP is working locally:

snmpwalk -v2c -c Str0ngC0mmunity! localhost

snmpwalk -v2c -c Str0ngC0mmunity! localhost

• Replace Str0ngC0mmunity! with your community string.
• You should see a list of SNMP data (e.g., system info). If you get a timeout or error, check your configuration and ensure snmpd is running.

4.2 Check Listening Port
SNMP uses UDP port 161. Verify it’s listening:

sudo netstat -an | grep 161

sudo netstat -an | grep 161

You should see output like udp4 0 0 *.161 *.*.

Step 5: Allow SNMP Through Firewall (Optional)

If macOS Monterey’s firewall is enabled, you need to allow SNMP traffic.

5.1 Open Firewall Settings
Go to System Preferences > Security & Privacy > Firewall, unlock it, and click Firewall Options.

5.2 Add SNMP Exception
Add /usr/sbin/snmpd to the list of allowed applications, or manually allow UDP port 161 via Terminal:

sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/sbin/snmpd

sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/sbin/snmpd

Step 6: Test from Nagios Server

From your Nagios server, test connectivity:

snmpwalk -v2c -c Str0ngC0mmunity! <your_mac_ip>

snmpwalk -v2c -c Str0ngC0mmunity! <your_mac_ip>

Replace Str0ngC0mmunity! with your community string and <your_mac_ip> with your macOS system’s IP.

If successful, you’ll see SNMP data returned.

Step 7: Add SNMP to Nagios

On your Nagios XI web GUI:

• Navigate to Configure > Configuration Wizards.

• Select SNMP (or Network Device if no specific SNMP wizard exists).
• Enter the following:
• IP Address: Your macOS system’s IP.

• Community String: Str0ngC0mmunity! (or your custom value).
• Follow the wizard to select metrics (e.g., CPU, memory, disk usage).

• Click Finish to complete the setup.

For Nagios Core, edit your configuration files (e.g., /usr/local/nagios/etc/objects/) manually:

define host {
    use             generic-host
    host_name       macos-monterey
    alias           MacOS Monterey
    address         <your_mac_ip>
}

define service {
    use                 generic-service
    host_name           macos-monterey
    service_description CPU Usage
    check_command       check_snmp!-C Str0ngC0mmunity! -o .1.3.6.1.4.1.2021.11.10.0
}

define host {
    use             generic-host
    host_name       macos-monterey
    alias           MacOS Monterey
    address         <your_mac_ip>
}

define service {
    use                 generic-service
    host_name           macos-monterey
    service_description CPU Usage
    check_command       check_snmp!-C Str0ngC0mmunity! -o .1.3.6.1.4.1.2021.11.10.0
}

Adjust OIDs (Object Identifiers) for specific metrics as needed.

Conclusion

By following these steps, you’ve successfully enabled and configured SNMP on macOS Monterey for Apple Silicon. Your Nagios monitoring server can now collect system metrics via SNMP in real time.

For further support, refer to:

• Nagios Support Forum: https://support.nagios.com/forum/
• Nagios Knowledge Base: https://support.nagios.com/kb/
• macOS SNMP Documentation: man snmpd in Terminal