Code: Select all
define host{
name in-router
use generic-host
check_period 24x7
check_interval 5
retry_interval 1
max_check_attempts 10
check_command check-host-alive
notification_period 24x7
notification_interval 30
notification_options d,r
contact_groups admins,etest
hostgroups routers-in
register 0
}
Code: Select all
define contact{
contact_name ivan
use generic-contact
alias test
email [email protected]
}
define contactgroup{
contactgroup_name etest
alias mail proba
members ivan
}
and i just shutdown one of the ports ... then i start writing that something is wrong ... and just before i submit this ... there it is ... MAIL !
tnx to all for the help and support that you gave me !!!
now im trying to figure out what is taking nagios so long to see that something is down or critical ...
correct me if im wrong ... for example we have some Router and suddenly the port go down ... nagios knows about it or wait for the service period to check that ? and if it knows about it(immediately) then the refresh period of the nagios frontend have to be passed. If not then the service period for check have to be changed or i dont have to change nothing because it works great
My next think is how to get details about the service that is down ... for now i have just this
im trying to find out how to get for example to tell me that FastEthernet0/0 is down ...Notification Type: PROBLEM
Host: RouterCiscoTest
State: DOWN
Address: 10.20.20.56
Info: CRITICAL - Host Unreachable (10.20.20.56)
Date/Time: Wed Mar 6 09:44:41 CET 2013