Conditions
Certain MIBs require the Layer 2 switch IP address to be configured and the controller rebooted before they will work on a CXi or MXe.
Values of type Counter64 can only be retrieved with the SNMP management system in V2 mode.
The SNMP agent supports GET-BULK PDUs in V2 mode. If the management system can be configured to use GET-BULK instead of GET it should be as this will result in less network traffic and quicker data retrieval.
Some of the objects will never change—that is, they are "hard coded" and "not supported".
Writing to the standard MIB objects (RFCs) using SET is not supported and the agent will reply with the error status readOnly.
Some generic MIB browsers present MIB objects which do not have any ACCESS or MAX-ACCESS clause (such as group identifiers, trap OIDs, etc.). Both HP Openview and Adventnet (Mitel Enterprise Manager) fall into this category. An attempt to retrieve data from these objects, or to walk the tree below a node containing only these kinds of objects will fail (the agent will respond noSuchName/noSuchInstance).
When the end of MIB view is encountered the agent will return endOfMib as an error status. Often generic MIB browsers will not handle this correctly or will not display it in a nice fashion. mitelBCMChipType is currently the last OID in the MIB view. If a MIB walk traverses this OID in adventnet browser (EMgr) it will report an error. This can be misleading, allowing the user to form a conclusion that a problem exists where there is none.
If the user generates a request that could take a long time to satisfy (for example a GET-BULK request with a large number of OIDs and/or repeaters), the user must also increase the timeout to allow the 3300 ICP enough time to formulate the response.
Attempts to retrieve data about interfaces (especially Layer 2 switched interfaces) early in the system startup sequence may return noSuchName or noSuchInstance while the hardware is starting up and the tables are being populated. This is normal. Ideally, one should wait for the RFC1215 restart trap before trying to retrieve data from the 3300 ICP.
When loading MIB files, MIB dependencies may be an issue. Generic MIB browsers vary in their strictness with respect to dependencies. HP Openview, for example, can load all the MIBs currently supported; the only dependency is RFC1213. Adventnet, by comparison, has complex dependencies; however, if the right-click menu of a 3300 ICP icon (or the action menu item) Browse MIBs is used, the MIBs are all loaded in the correct order and the MIB browser will remember the dependencies in the future).