Welcome, Register for free! or Login below:
EduGeek.net RSS Feeds Register FAQ Members Social Groups User Map Calendar Search Today's Posts Mark Forums Read

*nix

*nix forum sponsored by
*nix Forum Sponsored by Navaho

Powering the backend of many of our networks, unbeknown to many. Linux, Solaris, Unix...

Go Back   EduGeek.net Forums > Technical > *nix
Reply
 
LinkBack Thread Tools Search Thread Language
Sponsored Links
Old 16-08-2008, 08:09 PM   #1
 
alienux's Avatar
 
Join Date: Aug 2008
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Rep Power: 0 alienux is an unknown quantity at this point
Default Nagios argument with HP ProCurve switch memory

I'm configuring Nagios to monitor my HP ProCurve switches. I found excellent command and service definitions at NagiosExchange and all is working wonderfully except for the service that monitors free memory.

The definitions that I'm using are copied and pasted directly from the above-mentions site. They are:

command in commands.cfg:

Code:
define command{ 
  command_name check_hpmemoryfree 
  command_line $USER1$/check_snmp -H $HOSTADDRESS$ -C $ARG1$ -o .1.3.6.1.4.1.11.2.14.11.5.1.1.2.1.1.1.6.1 -t 5 -w $ARG2$ -c $ARG3$ -u bytes -l free 
 }
service in switch.cfg:

Code:
# Service definition MEM-FREE
define service{
	use				generic-service		; Name of service template to use

	host_name			Switch_MDF-1
	service_description		MEM-FREE
	is_volatile			0
	check_period			24x7
	max_check_attempts		3
	normal_check_interval		5
	retry_check_interval		1
	notification_interval		240
	notification_period		24x7
	notification_options		c,r
	check_command			check_hpmemoryfree!nagios!2000:30000000!1000:30000000
The switches list about 150MB of total memory, with about 109MB free when I view status from the switch console itself. Nagios is correctly reporting the free 109MB, but is showing the state as critical.

I've done a good bit of googling to try to understand how the "2000:30000000" and "1000:30000000" sections work. I realize that those are ARG2 and ARG3, and that ARG2 is the warning level and ARG3 is the critical level. What I don't understand is how to adjust those numbers to get the levels that I want to give warning and critical status on my particular switches. I've found info that states that two numbers followed by a colon are a range, and other info that says they are a less-than:higher-than definition for when to return the state defined by the command.

What I'd like is to have the following:

-Up to 60MB of free memory = OK
-Between 60MB and 40MB of free memory = Warning
-Less than 40MB of free memory = Critical

I will likely adjust those values once I get a better idea of memory usage under different loads.

I'd like to understand how to adjust the numbers in the service definition so that my service monitors will work as listed above. Can someone explain this, or point me to a resource that helps explain what the colon separated numbers mean on this particular command? I haven't had any luck in my searching, but I'm continuing to try to find as much information as I can to understand this.
  Reply With Quote
Old 16-08-2008, 08:21 PM   #2
 
ChrisH's Avatar
 
Join Date: Jun 2005
Location: East Lancs
Posts: 3,846
uk uk lancashire
Thanks: 2
Thanked 32 Times in 26 Posts
Rep Power: 19 ChrisH has a spectacular aura aboutChrisH has a spectacular aura about
Default

Looking at other examples on the wiki
Nagios it looks like the arguements are in KB.
  Reply With Quote
Old 16-08-2008, 08:42 PM   #3
 
alienux's Avatar
 
Join Date: Aug 2008
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Rep Power: 0 alienux is an unknown quantity at this point
Default

Thanks for the link, that provides some helpful information.

I think in this case its bytes b/c of the "-u bytes" in the command definition. What I'm not understanding is what the colon does in the argument.

I think I've narrowed it down to meaning that anything outside the range of 2000 - 3000000 (lower than 2000 or higher than 30000000) would cause a warning state, and anything lower than 1000 or higher than 30000000 would cause a critical state.

So, I modified my config to use the following:

Code:
check_command			check_hpmemoryfree!nagios!60000000:150000000!40000000:150000000
and now the status is showing OK, and again is showing the correct amount of free memory. The switch CLI shows 109,254,008 free as does the nagios service monitor. I'm just not positive that I have the correct values on either side of the colons yet.
  Reply With Quote
Reply

Register now for FREE and post messages!


Username: Password: Confirm Password: E-Mail: Confirm E-Mail:
Birthday:      
Image Verification
  I agree to forum rules 

Similar Threads
Thread Thread Starter Forum Replies Last Post
Nagios - do you use it? somabc *nix 20 20-08-2008 08:19 PM
[CLOSED] Missing Content: Invalid argument supplied .... pooley EduGeek.net Site Problems 4 17-06-2008 04:00 PM
for the sake of argument...(licensing question) kennysarmy Windows 11 31-03-2008 08:48 AM
HP ProCurve Switch 4104GL - WRONG DATE SHOWING mattx Networks 8 17-08-2007 09:53 AM
Changing port vLANs on an HP ProCurve switch MrDylan Hardware 6 09-03-2006 04:13 PM



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search Thread
Search Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT +1. The time now is 06:37 AM.
Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0 ©2008, Crawlability, Inc.
Copyright EduGeek.net