OpenGear Console Server

[ajwusv]

I see that at one point Nagios integrated with the OpenGear SDT Connector. Is there any current information on implementing the OpenGear connector with XI?

Thanks

[scottwilkerson]

From their website
http://www.opengear.com/product-nagios.html

The Opengear console servers also embed Nagios NSCA client and NRPE server software so they can function as distributed Nagios monitoring servers

So looking at this they have NPRE pre-installed, you should be able to set them up in XI simply by using the NRPE wizard (you may need to view their documentation on setting up an allowed_from address on the device)

[anritter6281]

We are in the process of deploying OpenGear ACM5508-2-M units and have found that some of the advanced features of the nagios integration (specifically SDT integration with Nagios) are no longer developed/maintained, although they say it works with Nagios Core v3. The documentation from OpenGear regarding Nagios integration is specific to Nagios Core not NagiosXI. The config wizard the documentation speaks of is not available for download from the link the documentation mentions, but OpenGear support will provide it at customer request. Either way, the config wizard from OpenGear is a script that is designed to automate the setup and integration of OpenGear units into Nagios Core, not Nagios XI. It worked in NagiosXI but only in that you could see a monitored device in NagiosXI that you had to go into Nagios Core config files to manipulate.

The NSCA functionality of the OpenGear relative to the auto-response feature (which would be used for timely event monitoring and alarming for dry contact state changes with the EMD sensor) didn't work very well at all. This is the bigger of the two issues I am dealing with right now.

When I run the NRPE wizard against the opengear unit, it does work, but it doesn't autodetect the opengear specific items that need to be monitored.

There is a way to export the nagios config for the opengear unit, which is how their config wizard gets the monitoring config into nagios core, but it doesn't seem to work with Nagios XI.

Overall, it seems as though OpenGear has let the integration with Nagios get a little rusty to try to move customers to use their Lighthouse product offering, which is a gui (and I think possibly NagiosCore-based) centrolized management solution for OpenGear units.

[abrist]

If it works with core, it will, with most certainty, work with XI. You may have to configure the checks in the ccm by hand, referencing the devices nrpe.cfg (or at least documentation that lists the available commands).

[anritter6281]

I agree, it will work with XI. We have the sensory stuff working. Opengear treats each EMD and port like a host on the nagios instance on the opengear unit. This can get a little confusing and is not for the novice. It also causes the config change a bit when EMDs are added to the opengear. A template in Nagios doesn't work across multiple opengear units because the commands and hosts are prefaced with the hostname of the specific opengear.

I wish there was a wizard inside nagiosXI for working with OpenGear hardware.

I may sound like I am knocking, to one degree or another, OpenGear products. This is not intentional, as they are wonderful products, and I would recommend them to anyone. We have 13 units and they are great.

[abrist]

If we had more requests for an opengear wizard, it might actually be on the radar, but as of now, we get very few requests for such a wizard. You may be better off editing the scripts from opengear to meet your needs currently.

[anritter6281]

Given the following config, what is the expanded nrpe command for the check command for the host? I am at a lost as to what $ARG2$ would be. Correct me if am am wrong but the ARGn are the command arguments to be passed...and in this case, for the host check command for the host listed below (opengear-host_12im), $ARG1$ would be "check_alive" $HOSTNAME$ would be "opengear-host_12im", but what would $ARG2$ contain?

I will attach the whole config file for reference (10.12.1.35_22.cfg.txt is the file name.) The file was generated by the opengear unit, and is used by the opengear wizard as a config file include to nagios core.

define command {
command_name check_nrpe_12im
command_line $USER1$/check_nrpe -H 10.12.1.35 -p 5666 -c $ARG1$$ARG2$_$HOSTNAME$
}

define host {
use generic-host
host_name 12im
alias 12im
address 10.12.1.35
max_check_attempts 4
}

define host {
name opengear-host_12im
alias opengear-host_12im
use generic-host
check_command check_nrpe_12im!check_alive
max_check_attempts 4
parents 12im
register 0
}

[sreinhardt]

In this case $arg2$ is not used. It is simply there so that as an admin you can choose to define additional parameters if needed. For some checks you might include a timeout or string to check a website for. However leaving it blank is entirely optional as well.

Notice how the host check definition only has one !, this is how arguments are separated. Then the command definition directly applies $hostaddress$ after to complete the command

check_command check_nrpe_12im!check_alive

command turns into
check_nrpe_12im -H 10.12.1.35 -p 5666 -c check_alive [blank for $arg2$]10.12.1.35

[anritter6281]

nuts....I keep getting an NRPE error that the command is not defined. I know that NRPE is operational on the opengear. Does command name given to nrpe (with the -c argument) need to be defined on the host running the check_nrpe command? I thought it only had to be declared on the remote NRPE host.

working on setting up the opengear the the NagXI config manager, the nrpe command outputs the following in a test:

Command setup:

Code: Select all

$USER1$/check_nrpe -H 10.12.1.35 -p 5666 -c $ARG1$$ARG2$_$HOSTNAME$

Test output:

COMMAND: /usr/local/nagios/libexec/check_nrpe -H 10.12.1.35 -p 5666 -c _$HOSTNAME$
OUTPUT: NRPE: Command '_amtvnagxi.bnk.ds.atv$' not defined

amtvnagxi.bnk.ds.atv is my nagios server.

To simplify things, would it make sense to just attempt to import the raw nagios file from the opengear unit via the "NagiosXI Core Config Manager > Tools > Import Config Files" feature? And if so, I assume that I should put the file on the nagios filesystem for it to be found?

The import through that method worked...it didn't put it in the way I would have, but the service checks are working now. I am testing NSCA again now.

something with NSCA is still not working correctly. When I trip a dry contact sensor on the opengear unit, the opengear unit generates an NSCA action. When this happens, a service appears in the NagiosXI console for the opengear unit, with the name of the action as configured on the OpenGear, but the state is always pending and never changes, even when I switch the state of the dry contact back to normal (which also generates and NSCA action.) I see the NSCA action generation in the opengear log, and I see the item show up in nagiosxi, but something still isn't right.

The purpose the NSCA action is to notify, in a timely manner, that a dry contact connected to the opengear unit has changed state.

I have never worked with NSCA before. I know that at least part of the NSCA setup is up and working because the action appears in the NagiosXI server. Is there some other setup piece I am missing for NSCA?

[sreinhardt]

To verify, we are past nrpe configs now and working on passive checks with nsca? Do you see anything in the unconfigured objects list in the XI interface? Also do you have the same host name or IP and service name configured with both nagios and opengear?

Just as a side note, XI will always show pending for a passive service until it recognizes something exactly matching that check come in. Likely it is a spelling or capitalization issue more than anything.