Table Of Contents

Overview

Cisco NME-APA MIB Implementation

MIB-II

ENTITY-MIB

ENTITY-STATE-MIB

HOST-RESOURCES-MIB

CISCO-SYSLOG-EVENT-EXT-MIB

CISCO-ENTITY-ALARM-MIB

CISCO-CONFIG-COPY-MIB

CISCO-TELNET-SERVER-MIB

CISCO-SERVICE-CONTROL-LINK-MIB

CISCO-SERVICE-CONTROL-RDR-MIB

CISCO-SERVICE-CONTROL-SUBSCRIBERS-MIB

CISCO-SERVICE-CONTROL-TP-MIB

Overview

---

This module provides brief descriptions of individual MIB implementations

Cisco NME-APA MIB Implementation

This section provides brief descriptions of individual MIB implementations. Also included for each MIB group are the actions used to configure and manage the NME-APA device and the MIB objects associated with each action.

•MIB-II

•ENTITY-MIB

•ENTITY-STATE-MIB

•HOST-RESOURCES-MIB

•CISCO-SYSLOG-EVENT-EXT-MIB

•CISCO-ENTITY-ALARM-MIB

•CISCO-CONFIG-COPY-MIB

•CISCO-TELNET-SERVER-MIB

•CISCO-SERVICE-CONTROL-LINK-MIB

•CISCO-SERVICE-CONTROL-RDR-MIB

•CISCO-SERVICE-CONTROL-SUBSCRIBERS-MIB

•CISCO-SERVICE-CONTROL-TP-MIB

MIB-II

MIB-II defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP-based internets. MIB-II objects are used to control and monitor the management protocol operations of the SNMP agent.

Excelsior implements all required groups in the MIB-II.

---

Note The MIB-II is not documented in this manual. See RFC 1213.

---

ENTITY-MIB

ENTITY-MIB objects are used to represent multiple logical entities supported by a single SNMP agent.

The Entity-MIB contains five groups of MIB objects:

•entityPhysical group (required): objects used to represent physical system components.

The entityPhysical2 group (required) augments the entityPhysical group.

•entityLogical group (not required): objects used to represent the list of logical entities.

The entityLogical2 group augments the entityLogical group.

•entityMapping group (part of this group is required): objects used to represent the associations between multiple logical entities, physical components, interfaces, and port identifiers.

•entityGeneral group (required): objects used to represent global entity information.

•entityNotifications group (required): notifications used to indicate Entity MIB data consistency and general status information.

---

Note The ENTITY-MIB is not documented in this manual. See ENTITY-MIB

---

ENTITY-STATE-MIB

The ENTITY-STATE-MIB objects are extensions to the Entity MIB that are used to provide information about the state of physical entities.

In addition, the ENTITY-STATE-MIB defines a set of standard Textual Conventions representing various states of an entity, which can be imported and used in other MIB modules.

ENTITY-STATE-MIB provides standard definitions for the following states:

•Administrative status

•Operational status

•Usage status

•Alarm status

•Standby status

---

Note The ENTITY-STATE-MIB is not documented in this manual. See RFC 4268.

---

HOST-RESOURCES-MIB

The HOST-RESOURCES-MIB objects are used in managing host systems. It defines attributes common to all internet hosts, such as personal computers as well as Unix-based systems.

The HOST-RESOURCES-MIB contains the following groups of MIB objects:

•hrSystem group (required)

•hrStorage group (required)

•hrDevice group (required)

•hrSoftwareRunning group

•hrSoftwareInstalled group

---

Note The HOST-RESOURCES-MIB is not documented in this manual. See HOST-RESOURCES-MIB.

---

CISCO-SYSLOG-EVENT-EXT-MIB

The CISCO-SYSLOG-EVENT-EXT-MIB module extends the Cisco Syslog MIB and provides network management support to handle and process Syslog messages as device events. The objects are used to indicate the level of severity of messages that should be displayed on the following devices:

•console

•event log GUI

•HTML event log console

---

Note The CISCO-SYSLOG-EVENT-EXT-MIB is not documented in this manual. See CISCO-SYSLOG-EVENT-EXT-MIB

---

CISCO-ENTITY-ALARM-MIB

The CISCO-ENTITY-ALARM-MIB module defines the managed objects that support the monitoring of alarms generated by physical entities contained by the system, including the following:

•chassis

•slots

•modules

•ports

•power supplies

•fans

---

Note In order to monitor alarms generated by a physical entity, it must be represented by a row in the entPhysicalTable (see ENTITY-MIB).

---

---

Note The CISCO-ENTITY-ALARM-MIB is not documented in this manual. See CISCO-ENTITY-ALARM-MIB

---

CISCO-CONFIG-COPY-MIB

The CISCO-CONFIG-COPY-MIB facilitates writing of configuration files of an SNMP Agent running Cisco IOS in the following ways:

•to and from the net

•copying running configurations to startup configurations and vice-versa

•copying a configuration (running or startup) to and from the local IOS file system

---

Note The CISCO-CONFIG-COPY-MIB is not documented in this manual. See CISCO-CONFIG-COPY-MIB

---

CISCO-TELNET-SERVER-MIB

The CISCO-TELNET-SERVER-MIB objects are used for displaying and configuring Telnet related features in a device.

CISCO-SERVICE-CONTROL-LINK-MIB

The CISCO-SERVICE-CONTROL-LINK-MIB objects are used to provide information about the status and configuration of links used by service control entities.

CISCO-SERVICE-CONTROL-RDR-MIB

The CISCO-SERVICE-CONTROL-RDR-MIB objects are used to provide statistics and configuration relating to the Raw Data Record Formatter running on a service control entity.

CISCO-SERVICE-CONTROL-SUBSCRIBERS-MIB

The CISCO-SERVICE-CONTROL-SUBSCRIBERS-MIB objects are used to provide global and specific information on subscribers managed by a service control entity .

CISCO-SERVICE-CONTROL-TP-MIB

The CISCO-SERVICE-CONTROL-TP-MIB objects are used to provide information and statistics about the traffic processor(s) of a service control entity.