| HP has really done a nice job with MIBs. They build a unique mib for
each 'global entity varient', use 'include' files to add things like
MIB2, experimental MIBs and such, and then has a object file that gets
used for each varient. They also collect comments from the MIB file
and have a 'describe' function that will show you the data type, OID,
description, and if a table, valid attributes. At hot staging for
Interop, they compiled our DECbridge MIB, and we were trying to do a
SET (didn't work cause agent doesn't support it). Since we thought
that maybe the value we were trying to set the attribute to (line
state) was wrong, the HP guy used the describe function to pull up the
valid values - and we then knew we were attempting a valid number. I
almost fell over at seeing such a useful feature. The MSU folks saw it
too, and between September and November when they shipped, the feature
had been put in and is now part of their V1.1.
HP and MSU also have a MIB editor. This comes in handy when the
vendor's MIB compiles, but you get garbage when trying to read an
attribute. With a MIB editor, you can quickly change the data type to
something else and try it...
These features have been mentioned to the SNMP AM group - and are high
on their list of priorities.
bill
|
| Re .1
>HP and MSU also have a MIB editor. This comes in handy when the
>vendor's MIB compiles, but you get garbage when trying to read an
>attribute. With a MIB editor, you can quickly change the data type to
>something else and try it...
>
>These features have been mentioned to the SNMP AM group - and are high
>on their list of priorities. any news on MIB editor for DECmcc ?
Will the MIB editor be avaiable for DECmcc and when ?
We're under strong pressure, because our cutomers are comparing network
Mgmt products for especially SNMP management. The MIB editor has a high
impact on the product decision made by most customers.
Best regards Uwe
|