Table of Contents
Advertisement
Most Annex parameters do not map to standard MIB objects. Instead, they
map to MIB objects in a proprietary (or private enterprise) MIB specific to
the Annex. The private MIB also contains objects that provide status and
statistics information to the network manager.
This section explains the relationship between Annex Manager and
standard MIBs, listing the exceptions and restrictions placed on standard
MIBs by the Annex SNMP agent. This section includes:
MIB Object Hierarchy
Describing and Naming Objects
Trap Hosts and Traps
Annex Restrictions on Standard MIBs
MIB Object Hierarchy
MIBs define the hierarchy of managed objects. MIB objects represent data
that the Annex can retrieve or configuration information that it can modify.
Annex Manager manages Annexes by retrieving or changing the value of
MIB objects. Some MIB objects represent actions that the Annex will
perform when Annex Manager sets certain values in those objects (e.g.,
when an Annex boots or resets).
Describing and Naming Objects
RFC 1155 ( Structure and Identification of Management Information for
TCP/IP-based internets ) describes the layout and encoding of exchanged
data objects.
The SMI (Structure of Management Information) uses the ISO standard
ASN.1 (Abstract Syntax Notation One) to define a method for describing a
hierarchical name space for managed information. Each object has:
A name (also referred to as an Object Identifier (OID)).
A syntax and an encoding. In addition to the basic integer and
octet string data types, several special types are defined (e.g,
IP Address
(Concise MIB Definitions) is an easier-to-read form used in
CSMIM/Micro-CS Management Application Guide
,
,
Network Address
,
,
Counter
Gauge
TimeTicks
Standard MIB Support
). RFC 1212
18-5
Advertisement
Table of Contents
