> If you want the switches to let you know when something
> happens, use traps. If you want to pull data at regular
> intervals, use polling.
>
> There's nothing to stop you from doing both.
We use both, although not on precisely this hardware. On our foundry load
balancer and SAN, for exampl
Traps and polling via SNMP are generally used for two very different
purposes, and which is appropriate really depends what you mean by
"present and correct."
If you want the switches to let you know when something happens, use
traps. If you want to pull data at regular intervals, use polling.
T
Dear Folks,
We like many others have happily deployed the Cisco 370 stackable
switch/routers in stacked
configurations.
Please would anyone with experience of monitoring these units with
Nagios comment on
how best to monitor the performance of the internals.
I am particuarly interested in checki
> Anyone like to share how they monitor switch ports?
Here, we use MRTG to graph the switch ports, and the routers2 frontend to
MRTG to make it pretty. Also, the routers2 frontend has a Nagios plugin to
allow the Nagios data to be displayed as well -- and a portstatus plugin to
show the current i
> > I'm running Nagios is a distributed environment which is working very
> > well. I would like to add a little redundancy to the
> picture now that I have everything working. ;-)
...
> > It seems that a secondary "cold spare" might be the best solution.
> > Then there are maintenance issues wit
I have services groups for notification intervals and host groups
for locations.
Is there a way I can use both hostgroup_name and servicegroup_name
in a serviceescalation object?
Basically, I want an intersect of a hostgroup and a servicegroup.
define serviceescalation{
hostgroup_name
