Power Supply MIB - Early Warning
dan@lannet.com (Dan Romascanu) Mon, 31 August 1992 12:31 UTC
Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA16808; Mon, 31 Aug 92 08:31:20 -0400
Received: from port7.x25.psi.net by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA16762; Mon, 31 Aug 92 08:30:53 -0400
Received: from moon.lannet.com ([149.49.50.12]) by lannet.com (4.1/3.1.090690-Lannet Data Communications) id AA17077; Mon, 31 Aug 92 13:44:34 IDT
Received: by moon.lannet.com (4.1/SMI-4.1) id AA18314; Mon, 31 Aug 92 13:46:30 IDT
Date: Mon, 31 Aug 1992 13:46:30 -0000
Message-Id: <9208311046.AA18314@moon.lannet.com>
From: dan@lannet.com
To: chassismib@cs.utk.edu, rlstewart@eng.xyplex.com
Subject: Power Supply MIB - Early Warning
Hi,
Your proposal seems OK to me, untill we get to this:
> Now we get really fancy. A table of environmental statuses, indexed by power
> supply index and (shudder) an OID. Standard OIDs provided for humidity,
> temperature, and fan. An implementation may omit entries with status
> "unknown" and thus could have an empty table. Each entry contains:
> status - unknown, bad, warning, good.
> warnings - number of times status has gone to warning.
> failures - number of times status has gone to bad.
The idea is good, but indexing to power supply index would not fit into
models where the different sensors related to humidity, temperature, fans,
etc. I would sugest instead:
- an environmentIndex, not related to the PS.
- add a textual description variable.
- The whole stuff should be put under a separate group, paralel
to the power supply SNMP group.
dan@lannet.com
Dan Romascanu
LANNET Data Communications
Tel Aviv, Israel
Voice: 972-3 6458414
Fax: 972-3-5447146
- Power Supply MIB - Early Warning Bob Stewart
- re: Power Supply MIB - Early Warning gallagher
- Re: Power Supply MIB - Early Warning Bob Stewart
- Power Supply MIB - Early Warning Dan Romascanu
- Re: Power Supply MIB - Early Warning Bob Stewart