TRMMIM MIB Structure
RMON
The RMON, or Remote Network Monitoring, MIB component contains the statistics, history, alarm, event, and Token Ring groups from the RMON MIB (RFC 1271 and 1757).
Telnet
The Telnet component provides a means by which you can remotely access the TRMMIM’s Local Management screens, including MIB Navigator — a command set from which you can configure and manage your TRMMIM by viewing and modifying the objects in the device’s MIB. Local management and the MIB Navigator are accessible through SPMA via the Telnet application; see the SPMA Tools Guide and/or your TRMMIM hardware manual for more information.
A Brief Word About MIB Components and Community Names
In the original version of the component MIB architecture, each MIB component is protected by its own set of user-configurable Read-Only, Read/Write, and Super- User community names. These names determine the level of access that will be granted to the information controlled by each individual component. For these devices, the central point of access for remote management is provided by the Chassis MGR MIB component — that is, if you define your device icon or launch a management application using the read-only, read/write, or super-user community name assigned to the Chassis MGR MIB component, your SPMA application is granted the appropriate level of access (read-only, read/write, or super-user) to all of that device’s MIB information — even if the other MIB components have different community names (as will occur of necessity with the TRMMIM’s multiple Network MIB components, each of which must have a unique set of community names).
The set of community names you assign via Local Management are those which apply to the Chassis MGR MIB component.
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 TRMMIM’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
