Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_telnet
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Primary uses:
1) check telnet banner for a matching return string.
2) log in via telnet and run specified command, check output for string.
Handy for:
-Screen scraping last console output from Cyclades ACS (or any console server supporting terminal buffering) for automatic inclusion in crash report, Nagios alert email, etc.
-Periodically checking to make sure serial console is still attached/working... for when you DO need it.
-Using in a custom host check, to determine if host is _really_ down and not responding on serial console.
-Last-ditch eventhandler usage, for starting SSH if dead (or any other arbitrary thing... as long as you can still log in via console).
/ command run/output example:
root@monitor02 libexec# ./check_telnet.pl -H deathstar1001-console -C 'date --iso-8601' -user username -password 'password'
date --iso-8601
2006-12-15
/ testing console login banner:
root@monitor02 libexec# ./check_telnet.pl -H deathstar1001-console -M deathstar1001
OK: host (deathstar1001) matches login banner.
root@monitor02 libexec# ./check_telnet.pl -H deathstar1001-console -M deathstar1002
CRITICAL: host (deathstar1002) did not match login banner.
1) check telnet banner for a matching return string.
2) log in via telnet and run specified command, check output for string.
Handy for:
-Screen scraping last console output from Cyclades ACS (or any console server supporting terminal buffering) for automatic inclusion in crash report, Nagios alert email, etc.
-Periodically checking to make sure serial console is still attached/working... for when you DO need it.
-Using in a custom host check, to determine if host is _really_ down and not responding on serial console.
-Last-ditch eventhandler usage, for starting SSH if dead (or any other arbitrary thing... as long as you can still log in via console).
/ command run/output example:
root@monitor02 libexec# ./check_telnet.pl -H deathstar1001-console -C 'date --iso-8601' -user username -password 'password'
date --iso-8601
2006-12-15
/ testing console login banner:
root@monitor02 libexec# ./check_telnet.pl -H deathstar1001-console -M deathstar1001
OK: host (deathstar1001) matches login banner.
root@monitor02 libexec# ./check_telnet.pl -H deathstar1001-console -M deathstar1002
CRITICAL: host (deathstar1002) did not match login banner.
Reviews (0)
Be the first to review this listing!
