next up previous
Next: 4 Implementing the optimized Up: 3.2 Steps for optimizing Previous: 3.2.4 Reality compliant Modeling

3.2.5 New Types for Variables with restricted Value Ranges

 

The final optimization step deals with the problem that the ranges of attribute data types resulting from the automatic translation are in general too broad for our purposes. The attribute OpState from the Processor object class may only take two values in the SNMP MIB: 1 (for enabled) or 2 (for disabled). Due to the lack of more appropriate data types in the Internet management information model it has been defined as integer. Our object model gives us the possibility of defining an enumeration data type which shows immediately the operational state of a device.
Another example is the attribute AdminState (the former AdState has been renamed for easier understanding). Here, we defined an enumeration type with four values, namely unknown, unlocked, locked and shutting down.



Copyright Munich Network Management Team