Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Configure outbound checks with Nagios

by | May 12, 2021

Wondering how to Configure outbound checks with Nagios? We can help you.

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

Today, let us see how our Support Techs configure outbound checks with Nagios.

Configure outbound checks with Nagios

 

Today, let us see how to configure outbound checks in Nagios XI.

Outbound Transfer APIs

Basically, there are two different APIs for handling outbound check transfers (passive checks) in Nagios XI:

  •  NRDP
  • Nagios Remote Data Processor
  • A modern web-based API that operates over port 80 (HTTP) or port 443 (HTTPS)
  •  HTTPS enables flexible security and encryption
  •  NSCA
  • Nagios Service Check Acceptor
  • Operates over TCP port 5667
  •  Historically used for passive check results

 

Accessing Transfer Settings

Generally, The outbound check transfer settings page allows to configure both the NSCA and NRDP APIs.

 

Enabling Outbound Transfers

Outbound check transfers are disabled by default.

In order to enable outbound checks using either the NRDP or NSCA APIs, we must first enable outbound transfers.

To do this, check the Enable Outbound Transfers option and click the Update Settings button.

We can optionally prevent some checks from being transferred by using the global data filters option.

 

NRDP Configuration

In order to, enable outbound checks using the NRDP API, we must:

  • Firstly, check the Enable NRDP Output option
  • Then, specify the IP Address and Authentication Token for the remote host that is accepting check results using NRDP
  • Finally, the authentication token we specify must be the same authentication token specified on the target host or the check results will be ignored.

We can configure Nagios XI to send passive check results to up to three remote servers using the NRDP API.

Finally, click the Update Settings button to save the NRDP settings.

 

NSCA Configuration

In order to, enable outbound checks using the NSCA API, we must:

  • Firstly, check the Enable NSCA Output option
  • Then, specify the IP Address, Encryption Method and Password for the remote host that is accepting check results using NSCA
  • Next, the encryption method and password we specify must match the decryption method and password specified on the target host or the check results will be ignored.

We can configure Nagios XI to send passive check results to up to three remote servers using the NSCA API.

Finally, click the Update Settings button to save the NSCA settings.

 

Firewall Configuration

Usually, modification of firewall settings between the remote data sinks and the Nagios XI server may be required in order to allow outbound check results to be sent from Nagios XI.

The NRDP API works on TCP port 80 using the HTTP protocol or TCP port 443 using the HTTPS protocol.

NSCA uses a custom protocol that runs on TCP port 5667.

At the end, firewalls must be configured to allow inbound and outbound traffic over the ports used by the API(s) we choose to utilize for handling outbound checks.

 

[Need any further assistance to fix CyberPanel errors? – We’re available 24*7]

Conclusion

In short, we can easily Configure outbound checks with Nagios. Today we saw how our Support Engineers perform this task.

PREVENT YOUR SERVER FROM CRASHING!

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

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

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

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

Reviews

Privacy Preference Center

Necessary

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

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

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

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

Statistics

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

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

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

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

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

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

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

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

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

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

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

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

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