Menu
▾
▴
devmon-support
|
From: Stef C. <ste...@do...> - 2010-03-10 09:29:14
|
Hi,
I'm making a template for a brocade SAN switch. I can monitor the sensors,
but I want to skip some absent sensors.
I tried to define a clear message for the absent sensons in the thresholds
files. But this causes the check to be dropped by devmon. I was hoping that I
was able to put a clear bullet next to the absent sensors.
I also tried to define an exception rules, but this is ignored by devmon.
Stef
oids
sensorType : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2 : branch
sensorStatus : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3 : branch
sensorValue : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.4 : branch
sensorMessage : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.5 : branch
exceptions
sensorStatus : ignore : 6
transforms
sensorStatus2 : SWITCH : {sensorStatus} 1 = unknown , 2 = faulty , 3 =
below-min , 4 = nominal , 5 = above-max , 6 = absent
thresholds
sensorStatus2 : red : faulty, below-min, above-max, offline : Errors detected
sensorStatus2 : clear : absent
sensorStatus2 : green : online, nominal : No errors detected
message
TABLE:
Sensor status | Sensor message | Sensor value
{sensorStatus2.color} {sensorStatus2}|{sensorMessage}|{sensorValue}
|
|
From: Buchan M. <bg...@st...> - 2010-03-10 10:49:46
|
On Wednesday, 10 March 2010 10:05:58 Stef Coene wrote:
> Hi,
>
> I'm making a template for a brocade SAN switch. I can monitor the sensors,
> but I want to skip some absent sensors.
Do you prefer them to be visible (and clear or green), or not visible.
> I tried to define a clear message for the absent sensons in the thresholds
> files. But this causes the check to be dropped by devmon. I was hoping
> that I was able to put a clear bullet next to the absent sensors.
There is some special handling of the clear status, I will look into this ...
> I also tried to define an exception rules, but this is ignored by devmon.
AFAIK this only works on the "primary repeater" at present. See below for
changes that should make this (skip absent sensors in the table) work.
>
>
> Stef
>
>
> oids
> sensorType : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2 : branch
> sensorStatus : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3 : branch
> sensorValue : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.4 : branch
> sensorMessage : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.5 : branch
>
> exceptions
Change this line:
> sensorStatus : ignore : 6
to:
sensorStatus2: ignore : absent
>
> transforms
> sensorStatus2 : SWITCH : {sensorStatus} 1 = unknown , 2 = faulty , 3 =
> below-min , 4 = nominal , 5 = above-max , 6 = absent
>
> thresholds
> sensorStatus2 : red : faulty, below-min, above-max, offline : Errors
> detected
Remove this line:
> sensorStatus2 : clear : absent
> sensorStatus2 : green : online, nominal : No errors detected
>
> message
> TABLE:
> Sensor status | Sensor message | Sensor value
> {sensorStatus2.color} {sensorStatus2}|{sensorMessage}|{sensorValue}
Regards,
Buchan
|
|
From: Patrick N. <pn...@gm...> - 2010-03-10 12:48:07
|
I'd be interested in the template when you get it squared away.
On Wed, Mar 10, 2010 at 4:05 AM, Stef Coene <ste...@do...> wrote:
> Hi,
>
> I'm making a template for a brocade SAN switch. I can monitor the sensors,
> but I want to skip some absent sensors.
>
> I tried to define a clear message for the absent sensons in the thresholds
> files. But this causes the check to be dropped by devmon. I was hoping that I
> was able to put a clear bullet next to the absent sensors.
>
> I also tried to define an exception rules, but this is ignored by devmon.
>
>
> Stef
>
>
> oids
> sensorType : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2 : branch
> sensorStatus : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3 : branch
> sensorValue : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.4 : branch
> sensorMessage : .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.5 : branch
>
> exceptions
> sensorStatus : ignore : 6
>
> transforms
> sensorStatus2 : SWITCH : {sensorStatus} 1 = unknown , 2 = faulty , 3 =
> below-min , 4 = nominal , 5 = above-max , 6 = absent
>
> thresholds
> sensorStatus2 : red : faulty, below-min, above-max, offline : Errors detected
> sensorStatus2 : clear : absent
> sensorStatus2 : green : online, nominal : No errors detected
>
> message
> TABLE:
> Sensor status | Sensor message | Sensor value
> {sensorStatus2.color} {sensorStatus2}|{sensorMessage}|{sensorValue}
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>
|
|
From: Stef C. <ste...@do...> - 2010-03-10 13:10:44
|
On Wednesday 10 March 2010, Patrick Nixon wrote: > I'd be interested in the template when you get it squared away. Ok, I will keep the list informed. I have a sensor and status check for brocade SAN switchen. What's the best place to post new templates ? Stef |
|
From: Buchan M. <bg...@st...> - 2010-03-10 15:18:25
|
On Wednesday, 10 March 2010 14:10:23 Stef Coene wrote: > On Wednesday 10 March 2010, Patrick Nixon wrote: > > I'd be interested in the template when you get it squared away. > > Ok, I will keep the list informed. > I have a sensor and status check for brocade SAN switchen. > > What's the best place to post new templates ? Tracker item (preferably logged with an sf user account, not anonymous) with category "template", attach svn diff or tarball. This allows tracking contributions, feedback/questions about the template. Once all issues are resolved, I will commit to svn, and all users can get it there until a new template release is made Regards, Buchan |
|
From: Buchan M. <bg...@st...> - 2010-03-10 15:20:23
|
On Wednesday, 10 March 2010 14:09:06 Stef Coene wrote: > On Wednesday 10 March 2010, you wrote: > > AFAIK this only works on the "primary repeater" at present. See below for > > changes that should make this (skip absent sensors in the table) work. > > Ok, it's working. The absent lines are gone. > Still, the clear or blue status can be handle. I don't want the message to > go clear of blue, but just that we can add a clear of blue button. Feel free to log a feature request tracker item, and then I will be reminded to look at it whenever I go through the tracker. Regards, Buchan |
|
From: Stef C. <ste...@do...> - 2010-03-10 15:39:55
|
On Wednesday 10 March 2010, Patrick Nixon wrote: > I'd be interested in the template when you get it squared away. See attached file. If you test this template and everything is ok, let me know. I tested it against 4 or 5 different models. For SAN switches in blade centers, I had to force the model/type in bb-hosts. So add DEVMON:model(brocade;SANswitch) in stead of DEVMON. This template gives you a report on the overal SAN switch status and a list of sensors and status. Stef |
|
From: Stef C. <ste...@do...> - 2010-03-10 16:11:14
|
On Wednesday 10 March 2010, Stef Coene wrote: > On Wednesday 10 March 2010, Patrick Nixon wrote: > > I'd be interested in the template when you get it squared away. > > See attached file. The attaced file is stiped by the mail daemon. You can download if from www.docum.org/temp/brocade.tar Stef |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X