Re: [Nagios-users] Indication of dial backup?
On Tue, 7 Dec 2010 22:42:57 +, Paul Williamson pwilliam...@twgi.net wrote: How can I configure Nagios to recognize when a router is on dial backup (or connected via the non-primary link)? I have about 300 locations and would like to see when a system is not connected via the primary interface. I realize I'll probably need to define a template of some sort that all routers would fit into, but I'm not very familiar with how to indicate that the condition is good (on primary) or it is bad (on dial back up). I've looked at the Nagios Exchange and didn't find any plugin or template. Add an interface check for the dialup interface but negate the result. If the interface is down everything is OK. But if the interface is up then you should set the status to CRITICAL or WARNING. You will need to add some effort of your own into this but this would be roughly how I would add monitoring. Just considere the backup link as a service of each router and set it to CRITICAL if the dialup interface is up. Hugo. -- hvdko...@vanderkooij.org http://hugo.vanderkooij.org/ PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc -- What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] Nagios configuraion best practice
Hi all,
I'm picking up this old tread, as I'm about to start restructuring
parts of my Nagios configuration. In my current configuration I've
created host groups to which I've linked both hosts and services.
Example: I have a host group called linux-servers, to which all
linux servers are linked. A number of service checks common for all
linux servers are also linked to this host group. When adding new
linux boxes I simply link them to the linux-servers host group. In a
similar fashion I have a host-group called application-servers to
which all application servers and related service checks are linked.
When adding a new application server, I make sure it links to both
linux-server and applications-servers.
This setup works pretty well, but it really clutters up the host
groups web page. Is this the way others have structured their nagios
configuration?
Regards,
Kenneth
On Wed, Sep 17, 2008 at 2:55 PM, Kenneth Holter kenneho@gmail.com wrote:
I should have been more precise regarding the cluttering of the display - it
was the hostgroup display I was referring to. :/
Would it be an idea to as much as possible use this configuration method:
hosts --- hostgroups --- services? To elaborate some: Hosts are always
connected to host groups, and the same for services. This way one will
avoid linking services to specific hosts, making the service definitions
more clean.
Also, I'm thinking about having a host group called for example
linux-servers, to which all linux servers are linked. A number of service
checks common for all linux servers are also linked to this host group. When
adding new linux boxes I simply link them to the linux-servers host group,
and add extra services checks where needed. In a similar fashin I would
create a host-group called for example dell-servers to which all Dell
hosts and related service checks are linked. New Dell servers are then
linked to this host group.
I'm thinking this may be a good idea, but would like to hear how others have
structured their configuration and if there may be some hidden pitfalls in
my proposed configuration method.
On 9/16/08, dave stern - e-mail.pluribus.unum dit.d...@gmail.com wrote:
Not quite sure what you're trying to do. If you monitor a service,
it's going to be on the nagios
service details pagre regardless, That's the whole point. There are
some tricks to slim down
some other displays eg I define a whole bunch of services under a host
without defining the
hosts these services run on explicitly. I just feed the IP address as
part of the check_command.
This reduced the hostgroup grid page. I don't think that will work for
you.
If you're asking how to most efficiently code this in your configs,
the timesaving tips page
mentions ganging together services. ie you don't need a service stanza
for each host you want
to run this on. Rather, use a wildcard or group.
define service{
use generic
host_namehosta, hostb
hostgroup special-ones,!webguy
.
}
Run the service on hosts hosta, hostb, all hosts in the hostgroup,
special-ones but not webguy
One other thing you should consider. Where will the plugins live? The
easy answer is to put them
on an NFSmounted partition that all hosts can access and that you can
easily update. This is a
bad practise. What happens when NFS breaks? You should really copy the
plugins to each
host st they run locally.
On Tue, Sep 16, 2008 at 8:05 AM, Kenneth Holter kenneho@gmail.com
wrote:
Thanks for the reply. I'll read the documents you listed.
Meanwhile, I have a design question: What's the best way to set up a
service
check to be executed on a selected few (or maybe all for that matter)
nodes?
Say I need to monitor a particular process (lets call this service A) on
a
number of systems, how would I implement this? I guess one way would be
to
link service A to a hostgroup, say hostgroup A, and add the selected
systems
to that hostgroup. This, however, will somewhat clutter up the web
display,
so I'm looking for alternative approaches.
Any suggestions?
On 9/15/08, dave stern - e-mail.pluribus.unum dit.d...@gmail.com
wrote:
Assuming you're already familiar with nagios, I'd look at the nagios
documentation
in the following order:
Under Configuring nagios, look at Object definitions and make sure
you understand all parameters and what would make sense in your
environment
Under Advanced Topics, look at Timesaving tips for object
definitions
Under Advanced Topics, look at host and service dependancies
Under Advanced Topics, look at both Distributed Monitoring and
Redundant and
Failover Monitoring.
Finally, under Security and Performance Tuning, look at Large
Installation Tweaks
On Mon, Sep 15, 2008 at 10:23 AM, Kenneth Holter
kenneho@gmail.com
wrote:
Hello all,
I'm new to Nagios, and are
[Nagios-users] NagiosXI licence exceeded.
Hi, I run nagiosxi on CentOS. I have by mistake created more than 7 entries with the FREE Licence. I have deleted everything related to my test laptop in the directories, restarted Nagios, but I cant access anything anymore. I went to /usr/local/Nagios and grep -iR LAPTOP and erased every entry I could find.. I still cant use nagiosxi.. Is there a way to fix this? Thanks -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] Nagios configuraion best practice
I think this is more a personal (or site) preference.
But using host groups can be very useful to eg
insure that
all windows machines get thus-and-such service checks
all RedHat machines get thus-and-such service checks
etc
In other words, a wildcard or hostgroup tag for a service check
can substantially reduce the size of your config, make it
more readable and insure uniformity.
From a grouping perspective, ie if you tend to display by
hostgroups, it's often helpful to list all hosts once and only
once. However, in other environments, some find it very useful
to list some (or all ) machines in multiple groups.
This would allow you to easily view all RHEL9 hosts,
SLES10 hosts that have not yet been updated, hosts in room 123,
etc. The downside of this is when hosts go red, you'll see a lot more red...
On Wed, Dec 8, 2010 at 7:52 AM, Kenneth Holter kenneho@gmail.com wrote:
Hi all,
I'm picking up this old tread, as I'm about to start restructuring
parts of my Nagios configuration. In my current configuration I've
created host groups to which I've linked both hosts and services.
Example: I have a host group called linux-servers, to which all
linux servers are linked. A number of service checks common for all
linux servers are also linked to this host group. When adding new
linux boxes I simply link them to the linux-servers host group. In a
similar fashion I have a host-group called application-servers to
which all application servers and related service checks are linked.
When adding a new application server, I make sure it links to both
linux-server and applications-servers.
This setup works pretty well, but it really clutters up the host
groups web page. Is this the way others have structured their nagios
configuration?
Regards,
Kenneth
On Wed, Sep 17, 2008 at 2:55 PM, Kenneth Holter kenneho@gmail.com wrote:
I should have been more precise regarding the cluttering of the display - it
was the hostgroup display I was referring to. :/
Would it be an idea to as much as possible use this configuration method:
hosts --- hostgroups --- services? To elaborate some: Hosts are always
connected to host groups, and the same for services. This way one will
avoid linking services to specific hosts, making the service definitions
more clean.
Also, I'm thinking about having a host group called for example
linux-servers, to which all linux servers are linked. A number of service
checks common for all linux servers are also linked to this host group. When
adding new linux boxes I simply link them to the linux-servers host group,
and add extra services checks where needed. In a similar fashin I would
create a host-group called for example dell-servers to which all Dell
hosts and related service checks are linked. New Dell servers are then
linked to this host group.
I'm thinking this may be a good idea, but would like to hear how others have
structured their configuration and if there may be some hidden pitfalls in
my proposed configuration method.
On 9/16/08, dave stern - e-mail.pluribus.unum dit.d...@gmail.com wrote:
Not quite sure what you're trying to do. If you monitor a service,
it's going to be on the nagios
service details pagre regardless, That's the whole point. There are
some tricks to slim down
some other displays eg I define a whole bunch of services under a host
without defining the
hosts these services run on explicitly. I just feed the IP address as
part of the check_command.
This reduced the hostgroup grid page. I don't think that will work for
you.
If you're asking how to most efficiently code this in your configs,
the timesaving tips page
mentions ganging together services. ie you don't need a service stanza
for each host you want
to run this on. Rather, use a wildcard or group.
define service{
use generic
host_namehosta, hostb
hostgroup special-ones,!webguy
.
}
Run the service on hosts hosta, hostb, all hosts in the hostgroup,
special-ones but not webguy
One other thing you should consider. Where will the plugins live? The
easy answer is to put them
on an NFSmounted partition that all hosts can access and that you can
easily update. This is a
bad practise. What happens when NFS breaks? You should really copy the
plugins to each
host st they run locally.
On Tue, Sep 16, 2008 at 8:05 AM, Kenneth Holter kenneho@gmail.com
wrote:
Thanks for the reply. I'll read the documents you listed.
Meanwhile, I have a design question: What's the best way to set up a
service
check to be executed on a selected few (or maybe all for that matter)
nodes?
Say I need to monitor a particular process (lets call this service A) on
a
number of systems, how would I implement this? I guess one way would be
to
link service A to a hostgroup, say hostgroup A, and add the selected
systems
to that hostgroup. This, however, will somewhat
[Nagios-users] Set notification periods for services from host entry?
Using Nagios3 on Debian 5.0.7, hoping to disable notifications for a couple
of hosts which experience downtime (or, poor response times from my
monitoring host) during morning backups.
Have created a timeperiod to black out the backup period, and set the
notification_period on the relevant host entries. But still receiving
service alerts on the host's services.
Is there a way to override the service notification period by setting it in
the hosts entries? (this is what I expected to do, but it seems the service
takes precedence)
Is it required to configure a separate service (eg: http,
http-except-backups; smtp, smtp-except-backups) for the services?
Should this service extend the existing http service with use?
Suggestions on better ways to handle this welcome too - permitting slower
response times during the backup periods would be a good solution, as we'd
still get notified if the server *actually* fell over.
Hopefully these excerpts give all the relevant details of what I'm trying -
have left out anything which is stock (eg generic-host config which is
unchanged from OS default, 24x7 definitions etc). Aim is to receive
notifications for bar 24x7 and foo only during silent_backups.
Thanks!
# /etc/nagios3/conf.d/timeperiods_nagios2.cfg contains this
define timeperiod {
timeperiod_name silent_backups
alias 24x7 with exclusion for daily backups
sunday 00:00-05:30,07:00-24:00
monday 00:00-05:30,07:00-24:00
tuesday 00:00-05:30,07:00-24:00
wednesday 00:00-05:30,07:00-24:00
thursday00:00-05:30,07:00-24:00
friday 00:00-05:30,07:00-24:00
saturday 00:00-05:30,07:00-24:00
}
# /etc/nagios3/conf.d/hosts.cfg contains this
define host {
use generic-host;
host_name foo;
address foo.example.org;
check_period silent_backups;
}
define host {
use generic-host;
host_name bar;
address bar.example.org;
check_period 24x7;
}
# /etc/nagios3/conf.d/services_nagios2.cfg
define service {
hostgroup_name smtp-servers
service_description SMTP
check_command check_smtp
use generic-service
notification_interval 0 ; set 0 if you want to be renotified
}
define service {
hostgroup_name http-servers
service_description HTTP
check_command check_http
use generic-service
notification_interval 0 ; set 0 if you want to be renotified
}
# /etc/nagios3/conf.d/hostgroups_nagios2.cfg
# A list of your web servers
define hostgroup {
hostgroup_name http-servers
alias HTTP servers
members foo, bar
}
define hostgroup {
hostgroup_name smtp-servers
alias SMTP servers
members foo, bar
}
--
This SF Dev2Dev email is sponsored by:
WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] NagiosXI licence exceeded.
On Wed, 2010-12-08 at 14:25 -0500, Maxime Alarie wrote: I run nagiosxi on CentOS. This list is intended for the open source Nagios Core, not XI. Could you please post this on http://support.nagios.com/forum/viewforum.php?f=6 instead? -- Tony Yarusso Technical Team ___ Nagios Enterprises, LLC Email: tyaru...@nagios.com Web:www.nagios.com -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
