Additional Egp Objects; Transmission Group; Snmp Group - Cisco MCS-7825-H3-IPC1 Service Manual

Chapter 8 Industry-Standard Management Information Base

Additional EGP Objects

egpAs OBJECT-TYPE

Transmission Group

Based on the transmission media underlying each interface on a system, the corresponding portion of the
Transmission group is mandatory for that system. When Internet-standard definitions for managing
transmission media are defined, the transmission group is used to provide a prefix for the names of those
objects. Typically, such definitions reside in the experimental portion of the MIB until they are proven,
then as a part of the Internet standardization process, the definitions are accordingly elevated and a new
object identifier, under the transmission group is defined. By convention, the name assigned is: type
OBJECT IDENTIFIER ::= { transmission number } where type is the symbolic value used for the media
in the ifType column of the ifTable object, and number is the actual integer value corresponding to the
symbol.

SNMP Group

Implementation of the SNMP group is mandatory for all systems which support an SNMP protocol
entity. Some of the objects defined below will be zero-valued in those SNMP implementations that are
optimized to support only those functions specific to either a management agent or a management
station. In particular, it should be observed that the objects below refer to an SNMP entity, and there
may be several SNMP entities residing on a managed node (e.g., if the node is hosting acting as a
management station).
snmpInPkts OBJECT-TYPE
OL-22523-01
A control variable used to trigger operator-initiated Start and Stop events. When read, this variable
always returns the most recent value that egpNeighEventTrigger was set to. If it has not been set
since the last initialization of the network management subsystem on the node, it returns a value of
stop. When set, this variable causes a Start or Stop event on the specified neighbor, as specified on
pages 8-10 of RFC 904. Briefly, a Start event causes an Idle peer to begin neighbor acquisition and
a non-Idle peer to reinitiate neighbor acquisition. A stop event causes a non-Idle peer to return to
the Idle state until a Start event occurs, either via egpNeighEventTrigger or otherwise.
::= { egpNeighEntry 15 }
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
The autonomous system number of this EGP entity.
::= { egp 6 }
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
Cisco Unified Communications Manager Managed Services Guide
RFC1213-MIB (MIB-II)
8-67