Here is what I've got working so far:
---
--- Sensor Devices
---
opsSrenaSensorTable OBJECT-TYPE
SYNTAX SEQUENCE OF OpsSrenaSensorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of sensor devices."
::= { opsSrenaMIB 71 }
opsSrenaSensorEntry OBJECT-TYPE
SYNTAX OpsSrenaSensorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular sensor device."
INDEX { opsSrenaSensorIndex }
::= { opsSrenaSensorTable 1 }
OpsSrenaSensorEntry ::= SEQUENCE {
opsSrenaSensorIndex Integer32,
opsSrenaSensorActive INTEGER,
opsSrenaSensorType DisplayString,
opsSrenaSensorPort Integer32,
}
opsSrenaSensorIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Index for this sensor. This value is unique
within the
system."
::= { opsSrenaSensorEntry 1 }
opsSrenaSensorActive OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Enabled or Disabled"
::= { opsSrenaSensorEntry 2 }
opsSrenaSensorType OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Type of sensor attached."
::= { opsSrenaSensorEntry 3 }
opsSrenaSensorPort OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Index into opsSrenaPortTable."
::= { opsSrenaSensorEntry 4 }
---
--- Channels off Sensors
---
opsSrenaSensorChannelTable OBJECT-TYPE
SYNTAX SEQUENCE OF OpsSrenaSensorChannelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of channels on sensors."
::= { opsSrenaMIB 72 }
opsSrenaSensorChannelEntry OBJECT-TYPE
SYNTAX OpsSrenaSensorChannelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular sensor channel."
INDEX { opsSrenaSensorChannelIndex }
::= { opsSrenaSensorChannelTable 1 }
OpsSrenaSensorChannelEntry ::= SEQUENCE {
opsSrenaSensorChannelIndex Integer32,
opsSrenaSensorChannelSensor INTEGER,
opsSrenaSensorChannelDescription
DisplayString,
opsSrenaSensorChannelValue DisplayString
}
opsSrenaSensorChannelIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Index for this channel. This value is unique
within the
system."
::= { opsSrenaSensorChannelEntry 1 }
opsSrenaSensorChannelSensor OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Index into the sensor table channel belongs
to."
::= { opsSrenaSensorChannelEntry 2 }
opsSrenaSensorChannelDescription OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Description of channel."
::= { opsSrenaSensorChannelEntry 3 }
opsSrenaSensorChannelValue OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Value of sensor attached to channel."
::= { opsSrenaSensorChannelEntry 4 }
On Mon, 2005-11-21 at 10:35 -0800, David T. Perkins wrote:
> HI,
>
> Sorry, I wasn't clear in what I was suggesting.
>
> I should have said, "why don't you send us
> a copy of the MIB definitions"
>
> Regards,
> /david t. perkins
>
> On Mon, 21 Nov 2005, Chris Fowler wrote:
>
> > Here is an example of one sensor:
> >
> > [EMAIL PROTECTED] show sensor 1
> > ###################################################
> > # Sensors #
> > ###################################################
> > # Sensor: 1
> > set sensor 1 active enabled
> > set sensor 1 type 533 # Temperature only
> > set sensor 1 port 3
> > set sensor 1 channel 1 description "<none>"
> > set sensor 1 channel 1 alarm 1 activate 45.00C # 113.00F
> > set sensor 1 channel 1 alarm 1 clear 40.00C # 104.00F
> > set sensor 1 channel 1 alarm 2 activate 29.44C # 84.99F
> > set sensor 1 channel 1 alarm 2 clear 26.67C # 80.01F
> >
> > Sensors can have multiple channels depending on type. And channels can
> > have up to 4 configurable alarms.
> >
> >
> > On Mon, 2005-11-21 at 09:28 -0800, David T. Perkins wrote:
> > > HI,
> > >
> > > Your terminology below leaves lots of important details out.
> > >
> > > Why don't you just send a copy of the relevant definitions.
> > >
> > > Regards,
> > > /david t. perkins
> > >
> > > On Mon, 21 Nov 2005, Chris Fowler wrote:
> > >
> > > > Thanks Rob and Dave. This clears it up nicely.
> > > >
> > > > I'll have to create 3 tables then and have variables pointing to the
> > > > indexes of the tables they belong to.
> > > >
> > > >
> > > >
> > > > sensors
> > > >
> > > > channels
> > > > sensor id -> sensors
> > > >
> > > > alarms
> > > > channel id -> channels
> > > >
> > > >
> > > > On Mon, 2005-11-21 at 16:48 +0000, Dave Shield wrote:
> > > > > On Mon, 2005-11-21 at 11:37 -0500, Robert Story wrote:
> > > > > > Your enterprise branch can contain other branches. Just not off of
> > > > > > any kind of
> > > > > > OBJECT-TYPE. Just OBJECT-IDENTIFIERS. Since a table is composed of
> > > > > > OBJECT-TYPES, it cannot have internal branches (eg sub-tables).
> > > > >
> > > > > Like the man said.
> > > > >
> > > > > Remember, that SNMP is (at least nominally) the *Simple*
> > > > > Network Management Protocol. One of the places where this
> > > > > bites is in the structure of management information.
> > > > >
> > > > > The SNMP SMI is a simplification of the capabilities of
> > > > > full ASN.1, which is why some SNMP experts (who shall remain
> > > > > nameless - <waves at David>) are very firm in their statement
> > > > > that SMI is not the same thing as ASN.1.
> > > > >
> > > > > Dave
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
> > > > Register for a JBoss Training Course. Free Certification Exam
> > > > for All Training Attendees Through End of 2005. For more info visit:
> > > > http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
> > > > _______________________________________________
> > > > Net-snmp-coders mailing list
> > > > [email protected]
> > > > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
> > > >
> >
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
