Cabletron Systems SEHI-22/24 - Manual (Page 84)

SEHI MIB Structure
A-2 SEHI MIB Structure
community names; the Chassis MGR community names are the same as those
assigned via Local Management.
SEHI LIM
The SEHI LIM, or Local Management, component contains the objects that
provide out-of-band management via the Console port on the SEHI’s front panel.
No objects from this component are used for remote management.
Repeater One
The Repeater MIB component controls all repeater functionality on the SEHI.
These functions include port count, port enable/disable, port status, board
number, repeater statistics (packets, bytes, collisions, errors, etc.), protocol counts,
and frame sizes; also included are the alarm, redundancy, source addressing, and
trap functions. Note that the default community names for the Repeater MIB
component will always be different from the default names assigned to all the
other components.
SEHI Host Services
The Host Services MIB component contains the objects that provide the SEHI with
its IP functionality — essentially, those functions which allow the SEHI to operate
over a network — including functions such as ping, Telnet, and TFTP.
SEHI IP Services
The IP Services MIB component is not currently used by the SEHI, but is reserved
for future use.
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
SEHI’s multiple Network MIB components, each of which must have a unique set
of community names).
NOTE
The set of community names you assign via Local Management are those which apply to
the Chassis MGR
MIB component.