Votos - 4, Puntuación media: 2.8
(
)
)
|
Resumen del manual
Click on the appropriate selection in the Send Trap field to Enable or Disable traps for the selected port(s). 6. Click on to save your changes; each port’s new status will be displayed in the list box. Click on to close the window. Enabling Security and Traps Security Enabling Security and Traps Appendix A Appendix A SEHI MIB Structure SEHI management information base configuration IETF MIB Support In addition to its proprietary features, the SEHI-22/24 and SEHI-32/34 currently support the following IETF MIB: • RFC 1213 MIB for Network Management of TCP/IP-based Internets: MIB-II SEHI MIB Structure Cabletron’s newer intelligent devices — like the SEHI — organize MIB data into a series of “components.” A MIB component is a logical grouping of MIB data, and each group controls a defined set of objects. For example, SEHI repeater information resides in its Repeater component; more generic device and port information resides in the SEHI Chassis MGR component. The SEHI MIB consists of five components, each of which is described below. To see the names of the MIB components in your SEHI, bring up the Community Names application, or use any SNMP Get operation that will allow you to view the contents of the chCompTable. The SEHI MIB consists of the following components: SEHI Chassis MGR The Chassis MGR MIB component contains most of the basic information about the SEHI, including: the SEHI’s MIB component information (in the chCompTable), device names, hardware revision numbers, MAC and IP addresses, the current time and date, and information related to redundancy, alarms, and TFTP download. The system, interfaces, at, ip, icmp, udp, and snmp groups from MIB-II are also included. The community names assigned to this MIB component provide the gateway that all SPMA applications use to access all information in the other components, even if those components have different 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. SEHI MIB Structure 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 pr...
Otros modelos de este manual:Equipo de red - SEHI-32/34 (775.46 kb)