Cabletron Systems SEHI-22/24, Руководство пользователя

Страница: 85 / 90

SEHI MIB Structure A-3
SEHI MIB Structure
Newer versions of devices with this component-based MIB architecture have
been simplified somewhat; these devices support a single, global set of community
names, with small modifications added automatically to accommodate multiple
instances of the same MIB component (as occurs with the SEHI’s Network
components). Again, defining your device icon or launching a management
application with one of these global community names gives SPMA access to all
MIB information.
Where community names may become an issue, however, is when you are using
the MIBTree or any similar MIB-based tool (such as those provided by SunNet
Manager or HP Network Node Manager) to access MIB information. For these
kinds of tools, you must supply the precise community name assigned to the
component that contains the information you want. For devices which support
the original component-based MIB architecture, this means you must use the
exact community name you have assigned to a specific component to access that
component’s MIB information. (Again, note that the SEHI’s Network components
always have unique community names.) For devices which support the new
global community names, you must make note of the automatic modifications
that are made for network components, and use those specific community names
when trying to access information stored in those components.
The MIB component descriptions provided above will serve as a roadmap for
determining where the information you’re interested in is located; you can use the
SPMA Community Names tool (described in Chapter 3 of the SPMA Tools Guide)
to determine whether your version of firmware supports the original component-
based MIB architecture, or the new global community names. The Community
Names tools also allows you to both view and set the community names which
apply to your device.