Menu
▾
▴
devmon-support
|
From: netz-haut - s. s. <s....@ne...> - 2011-09-26 21:25:59
|
Hi there, I've made a template to monitor the Areca ARC-1680 sas/sata controller. For that particular controller it works quite well. My current problem is, the monitored infrastructure consists of some more Areca controllers (starting from some ARC-11xx up to the recent 1880) which have all (slightly) different MIB, but all of them are reporting "Raid Subsystem V1.00" as sysdesc value. Is there any configuration possible to distinguish the controllers in ./templates/[...]/desc by any other OID? Thanks for any suggestions! -- Stephan Seitz Senior System Administrator netz-haut GmbH multimediale kommunikation Zweierweg 22 97074 Würzburg Telefon: 0931 2876247 Telefax: 0931 2876248 Web: www.netz-haut.de Amtsgericht Würzburg – HRB 10764 Geschäftsführer: Michael Daut, Kai Neugebauer |
|
From: <kco...@ry...> - 2011-09-26 21:57:39
|
Just had this issue, drove me nuts.... Create/copy a new template and in the specs file change the model to something slightly different but unique. Then in you hosts file add the following after the DEVMON tag: :model(<vendor from specs file>;<model from specs file>) Ken Connell Intermediate Network Engineer Computer & Communication Services Ryerson University 350 Victoria St RM AB50 Toronto, Ont M5B 2K3 416-979-5000 x6709 -----Original Message----- From: netz-haut - stephan seitz <s....@ne...> Date: Mon, 26 Sep 2011 23:25:49 To: <dev...@li...> Reply-to: dev...@li... Subject: [Devmon] different templates for hardware reporting identical sysdesc Hi there, I've made a template to monitor the Areca ARC-1680 sas/sata controller. For that particular controller it works quite well. My current problem is, the monitored infrastructure consists of some more Areca controllers (starting from some ARC-11xx up to the recent 1880) which have all (slightly) different MIB, but all of them are reporting "Raid Subsystem V1.00" as sysdesc value. Is there any configuration possible to distinguish the controllers in ./templates/[...]/desc by any other OID? Thanks for any suggestions! -- Stephan Seitz Senior System Administrator netz-haut GmbH multimediale kommunikation Zweierweg 22 97074 Würzburg Telefon: 0931 2876247 Telefax: 0931 2876248 Web: www.netz-haut.de Amtsgericht Würzburg – HRB 10764 Geschäftsführer: Michael Daut, Kai Neugebauer ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Devmon-support mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devmon-support |
|
From: Jeremy L. <jla...@re...> - 2011-09-27 03:35:42
|
On Tue, Sep 27, 2011 at 7:56 AM, <kco...@ry...> wrote: > Just had this issue, drove me nuts.... > Likewise. Don't forgot to re-run "devmon --readbbhosts" manually if it's not run from cron. > Create/copy a new template and in the specs file change the model to > something slightly different but unique. > I create symlinks for all tests that are the same, pointing to the "official" version. Then I can keep them upgraded without having to re-copy them into the cloned version. In the spec file, you can only match on the sysdesc string. So presently, there's no way of being more selective except for mapping on a per-host basis, as Ken described. What would be really useful is to be able to specify the device matching in the spec file more precisely. For example, it would be neat to be able to add one of these into the spec file: oid-exists : 1.3.6.1.4.1.232.3.2.4.1.1.1 oid-exists : tcpConnLocalPort.127.0.0.1.25.0.0.0.0.0 oid-value : 1.3.6.1.4.1.232.3.2.4.1.1.1 > 0 oid-value : sysLocation =~ /Site2/ (The OID used here refers to the HP/Compaq drive hot-spare count.) Cheers Jeremy |
|
From: <kco...@ry...> - 2011-09-27 11:37:06
|
As Jeremy said, don't forget to "readbbhosts"....but on a side note because cron was mentioned..... I actually cron mine to "readbbhosts" once a day in the wee hours....this just makes things seamless for the others in my group who add to the hosts file but don't really know what Devmon is or how to make it do its magic ;) Ken Connell Intermediate Network Engineer Computer & Communication Services Ryerson University 350 Victoria St RM AB50 Toronto, Ont M5B 2K3 416-979-5000 x6709 -----Original Message----- From: Jeremy Laidman <jla...@re...> Date: Tue, 27 Sep 2011 13:28:37 To: <dev...@li...> Reply-to: dev...@li... Subject: Re: [Devmon] different templates for hardware reporting identical sysdesc On Tue, Sep 27, 2011 at 7:56 AM, <kco...@ry...> wrote: > Just had this issue, drove me nuts.... > Likewise. Don't forgot to re-run "devmon --readbbhosts" manually if it's not run from cron. > Create/copy a new template and in the specs file change the model to > something slightly different but unique. > I create symlinks for all tests that are the same, pointing to the "official" version. Then I can keep them upgraded without having to re-copy them into the cloned version. In the spec file, you can only match on the sysdesc string. So presently, there's no way of being more selective except for mapping on a per-host basis, as Ken described. What would be really useful is to be able to specify the device matching in the spec file more precisely. For example, it would be neat to be able to add one of these into the spec file: oid-exists : 1.3.6.1.4.1.232.3.2.4.1.1.1 oid-exists : tcpConnLocalPort.127.0.0.1.25.0.0.0.0.0 oid-value : 1.3.6.1.4.1.232.3.2.4.1.1.1 > 0 oid-value : sysLocation =~ /Site2/ (The OID used here refers to the HP/Compaq drive hot-spare count.) Cheers Jeremy ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Devmon-support mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devmon-support |
|
From: Buchan M. <bg...@st...> - 2011-09-27 10:39:54
|
On Monday, 26 September 2011 23:25:49 netz-haut - stephan seitz wrote: > Hi there, > > I've made a template to monitor the Areca ARC-1680 sas/sata controller. > For that particular controller it works quite well. > My current problem is, the monitored infrastructure consists of some more > Areca controllers (starting from some ARC-11xx up to the recent 1880) > which have all (slightly) different MIB, but all of them are reporting > "Raid Subsystem V1.00" as sysdesc value. sysdescr is not a very good choice for identifying appliances (see for example how many Linux-based appliances can't be distinguished from each other, or from OEM servers from HP or Dell running the OEM's management software). > Is there any configuration possible to distinguish the controllers in > ./templates/[...]/desc by any other OID? IMHO, your best option is currently to specify the model option in the DEVMON tag in the bb-host or hosts.cfg file. Regards, Buchan |
|
From: Buchan M. <bg...@st...> - 2011-09-27 11:23:44
|
On Tuesday, 27 September 2011 05:28:37 Jeremy Laidman wrote: > What would be really useful is to be able to specify the device matching in > the spec file more precisely. Well, sysDescr use isn't a great idea, and I was considering using sysObjectId, as that will (at least for devices that support it) be the easiest to use to identify the device without requiring access to all the devices for which templates exist. However, this is only sufficient to identify the base device/appliance, not any optional features it may support (e.g. feature blades on modular chassis such as a load balancer in a Cisco 6500/7600 or more modern replacements). sysORID may help somewhat here to identify standards-based MIBs the device supports, but not any vendor-specific MIBs. Some of this work may be done more efficiently with better MIB support, and requires changes to how templates are handled, so I think some more experimentation needs to be done here, and most likely in a new branch or release series. So, I would really like to get the 0.3.1 release out of the way before starting work on any of these issues. > For example, it would be neat to be able to > add one of these into the spec file: > > oid-exists : 1.3.6.1.4.1.232.3.2.4.1.1.1 > oid-exists : tcpConnLocalPort.127.0.0.1.25.0.0.0.0.0 To identify a server with a running MTA? What would the value here be? > oid-value : 1.3.6.1.4.1.232.3.2.4.1.1.1 > 0 > oid-value : sysLocation =~ /Site2/ > > (The OID used here refers to the HP/Compaq drive hot-spare count.) Yes, I guess that could be useful to distinguish the hot-spare vs no-hot-spare case. But, I don't know if separate templates is the best fix for this issue, or if instead empty tables should be ignored totally. I will try and look at solutions for this problem in October or November. Regards, Buchan |
|
From: Jeremy L. <jla...@re...> - 2011-10-11 05:28:23
|
On Tue, Sep 27, 2011 at 9:24 PM, Buchan Milne <bg...@st...>wrote: > > oid-exists : tcpConnLocalPort.127.0.0.1.25.0.0.0.0.0 > > To identify a server with a running MTA? What would the value here be? > I might want to create a template that's specific to my mail servers. For instance, I might want to count/graph the number of MTA-type processes, perhaps alarming when the number drops to zero. Or, for a different port, I might know that only my HP RHELv5 servers are running HPOV software brand listening on port 55123, and on that basis, I know that they're HP Linux servers rather than any other type of Linux servers. These aren't very good examples, and I'm not suggesting that they would actually get used as they are, but I think the flexibility to do this kind of thing by testing OID existence/value would be a useful way to prevent template collisions. Cheers Jeremy |
|
From: Mark J. <mj...@mn...> - 2011-09-27 16:37:23
|
We have a device that allows us to poll for current levels on various breakers. Unfortunately the oids are in one large branch. So the first 42 oids in the branch may be names then the next 42 could be volts then the next 42 could volts and so forth up to a few thousand oids. Any ideas how I might monitor this setup with devmon? Mark Jones Operations Managed Network Systems London Desk 519-679-5207 Windsor Desk 519-258-2333 x8417 Cell 519-521-8222 |
|
From: Buchan M. <bg...@st...> - 2011-10-07 22:31:48
|
On Tuesday, 27 September 2011 18:20:31 Mark Jones wrote: > We have a device that allows us to poll for current levels on various > breakers. Unfortunately the oids are in one large branch. So the first 42 > oids in the branch may be names then the next 42 could be volts then the > next 42 could volts and so forth up to a few thousand oids. Hmm, I have a device which does something similar, except that x*4-3 is the voltage of one phase, same for x*4-2 and x*4-3, and x*4 is the frequency, where x ranges from 1 to 10. At least my names are in a separate branch. IMHO, this indicates a badly designed MIB. At present there is no real support for such crazy MIBs. I guess we could have some kind of operator to make some more sane 'column' OIDs out of every Nth leaf of the branch ... Regards, Buchan |
Thanks for helping keep SourceForge clean.
X