Filter
Top Products
14 November 2003 8000-A2-GB30-10
3. Standards Compliance to SNMP MIBs
This section describes the standards compliance and any special operational
features/options for the SNMP MIBs supported on the GranDSLAM R3.2 product. The
term NO_SUCH_NAME_ERROR will be used to say that either:
a) a whole table does not exist in the MIB tree or
b) a particular object does not exist in the MIB tree
Mandatory groups will be supported as is. If a value can not be determined for an
mandatory object, a default value (defined in the MIBWG guidelines) will be assigned
and will be specified in this document. However, this SNMP agent is not required to
support optional groups. The agent will return the value NO_SUCH_NAME_ERROR for
a get request of the objects contained in any optional group not supported. Network
Management Systems must be able to handle this situation better known as sparse tables.
An exception to the later is the ifTable. The ifTable will not be a sparse table and will be
fully supported.
When a particular enumeration for a particular object is not available, attempt to write it by
a management entity will result in a failure of BAD_VALUE or GENERAL_ERROR.
The following diagram may be useful in visualizing the interfaces on the product.