Nagios Support Forum

The MPLS Trunk that the box is on is down so the Server appears Down.

It really isn't down at the site it is on dial backup line.

Is there a way I can still monitor the server with nagios through the internet?, if my direct private network with the site is down?

If So what settings would I need to modify to accomplish this?

Right now I do not believe apache is running. The servers are being monitored by nagios.

If I understand correctly, your main line failed and the server is now on a backup line? The implication being that the IP has changed.

In situations like this, passive checks (or SNMP traps, whichever you prefer) would be my recommendation. This way Nagios doesn't need a route to the server, just the other way around.

Is there a step by step way to setup snmp traps?

No the internal ip address on the server I want to monitor, has not changed, it is static

My point to point network was down, the server is on another site. Is there a way to make nagios monitor the server over the internet also?

if my mpls or vpn is down is there a nagios client that would let nagios monitor it over the internet?

Yes the External router ip, has changed not the internal server.

Thinking I need to figure out what external ip is to backup line.

We can't really walk you through setting up snmp traps on your remote devices. However we can certainly answer questions and point you towards our snmptrap documentation regarding xi.

http://assets.nagios.com/downloads/nagi ... ith_XI.pdf

On my home page it says I am running Nagios® Core™
Version 3.5.0


The instructions are for 11x. Will these instructions work with my nagios version?

If you can confirm this will work I will try.


I thought wget was for Debian? I am running OPensuse 12.3

You can still use the same commands and script, you will just not have a shiny XI interface to work inside of after you reach that point. Wget is used by a large number of distributions, in this case it is used to pull down a file that is hosted at a web address.

Does this look like it completed correctly? see below



Updating snmptt.ini

sed: can't read /etc/snmp/snmptt.ini: No such file or directory
sed: can't read /etc/snmp/snmptt.ini: No such file or directory
sed: can't read /etc/snmp/snmptt.ini: No such file or directory
sed: can't read /etc/snmp/snmptt.ini: No such file or directory
sed: can't read /etc/snmp/snmptt.ini: No such file or directory
sed: can't read /etc/snmp/snmptt.ini: No such file or directory
sed: can't read /etc/snmp/snmptt.ini: No such file or directory
sed: can't read /etc/snmp/snmptt.ini: No such file or directory

Creating snmptrapd.conf


Adding the snmptt user to the nagios and nagcmd groups

usermod: user 'snmptt' does not exist
usermod: user 'snmptt' does not exist

Modifying permissions

chown: cannot access ‘/etc/snmp/snmptt.ini’: No such file or directory
chown: cannot access ‘/etc/snmp/snmptt.conf’: No such file or directory
chmod: cannot access ‘/etc/snmp/snmptt.ini’: No such file or directory
chown: invalid user: ‘snmptt:snmptt’
chmod: cannot access ‘/var/spool/snmptt’: No such file or directory
chmod: cannot access ‘/var/log/snmptt’: No such file or directory

Adding firewall rules

grep: /etc/sysconfig/iptables: No such file or directory
WARNING: The state match is obsolete. Use conntrack instead.
service: no such service iptables

Set up the snmptt daemon to start automatically on boot
as well as starting it now

snmptt: unknown service

Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.

snmptt: unknown service
service: no such service snmptt

Set up the snmptrapd daemon to start automatically on boot
as well as starting it now


Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.

snmptrapd 0:off 1:off 2:on 3:on 4:off 5:on 6:off

========================================
SNMP Trap Support Installation Complete!
========================================

I am also assuming I cannot use the snmp trap wizard that goes to nagios 11 with core?


I also have no /etc/snmp/snmptt.conf does no exist

instead I have
ahgmonitor:/etc/snmp # ls
snmpd.conf snmptrapd.conf

snmpd.conf contains "Please see /usr/share/doc/packages/net-snmp/EXAMPLE.conf for a
# more complete example and snmpd.conf(5).
#
# Writing is disabled by default for security reasons. If you'd like
# to enable it uncomment the rwcommunity line and change the community
# name to something nominally secure (keeping in mind that this is
# transmitted in clear text).

# don't use ' < > in strings for syslocation or syscontact
# Note that if you define the following here you won't be able to change
# them with snmpset
syslocation Server Room
syscontact Sysadmin (root@localhost)
{>
# These really aren't meant for production use. They include all MIBS
# and can use considerable resources. See snmpd.conf(5) for information
# on setting up groups and limiting MIBS.
(>rocommunity public 127.0.0.1
1># rwcommunity mysecret 127.0.0.1"
~

snmptrapd.conf contains "
disableAuthorization yes
traphandle default /usr/sbin/smntptthandler

The example file contains" ahgmonitor:/usr/share/doc/packages/net-snmp # vi EXAMPLE.conf
0>############################################################################## #
#
# EXAMPLE.conf:
# An example configuration file for configuring the Net-SNMP agent ('snmpd')
# See the 'snmpd.conf(5)' man page for details
#
# Some entries are deliberately commented out, and will need to be explicitly activated
#
############################################################################## #
#
# AGENT BEHAVIOUR
#
}>
# Listen for connections from the local system only
agentAddress udp:127.0.0.1:161
# Listen for connections on all interfaces (both IPv4 *and* IPv6)
#agentAddress udp:161,udp6:[::1]:161

2>


Have to say I am a little lost. still don't really know how snmp traps will help me monitor my server when it switches to a backup line.
what would using the statement to listen for connections on all interfaces do for me? and what file should I put it in?

I believe the idea that they were getting at, is that your remote system would send traps to nagios instead of nagios being forced to check two different connections. There are ways to do this whichever you would like to do. You are correct that core cannot use wizards, however the rest of integrating snmptraps would be mostly fine, with the large exception that our script and documentation is written for Cent\RHEL systems specifically. So with that, would you like to continue down the route of setting up snmptraps to be sent from the remtoe system, or actively checking from nagios to the remote location?

somehow I want to be able to still monitor my server when my point to point connection is down.
i do nîot understand how that would be possible without either a client that communicates over the internet or a static address on my backup line.îîîîîîî

which of the two options you just mentioned is easier?î