Mib Archive; Snmp - Cisco SRST - 881 EN Security Router Wireless Manual

Chapter 1 Cisco SRST SNMP MIB Support
•
•
The following is an example of a MIB object:
tpTDMIfCollectTimeInterval OBJECT-TYPE
This object shows measurement time interval seconds.
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on CCO at
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.

MIB Archive

Cisco MIBs are archived in the Cisco FTP server and are accessible by anonymous FTP at the following
location:

SNMP

Cisco MIB variables are accessible through SNMP, which is an application-layer protocol designed to
facilitate the exchange of management information between network devices.
Instead of defining a large set of commands, SNMP places all operations in a get-request,
get-next-request, or set-request format. For example, an SNMP manager can get a value from an SNMP
agent or store a value in that SNMP agent. The SNMP manager can be part of an NMS, and the SNMP
agent can reside on a networking device such as a router. You can compile the Cisco MIB with your
network management software. If SNMP is configured on a Catalyst Switch, the SNMP agent can
respond to MIB-related queries being sent by the NMS.
An example of an NMS is the CiscoWorks network management software. CiscoWorks uses the Cisco
MIB variables to set device variables and to poll devices on the internetwork for specific information.
The results of a poll can be displayed as a graph and analyzed for the troubleshooting of internetwork
problems. Results can also be used to increase network performance, verify the configuration of devices,
monitor traffic loads, and so on.
OL-7959-01
Read-write—Indicates that instance of the object may be read or written, but not created
–
Read-only—Indicates that instances of the object may be read but not written or created
–
Accessible-for-notify—Indicates that instances of the object may only appear in notifications
–
Not-accessible—Indicates that instances of the object may not be directly read, written, or
–
created
Status—The status of a managed object can be:
Mandatory—Indicates that the definition is required and should be implemented
–
Current—Indicates that the definition is current
–
Deprecated—Indicates that the definition will soon be made obsolete and need no longer be
–
implemented
Obsolete—Indicates that managed nodes should not implement the object
–
Description—Provides a textual description of the managed object
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
::= {tpTDMIfStatTableEntry 1}
ftp://ftpeng.cisco.com/pub/mibs
Cisco SRST SNMP MIB Release 3.4 Guide
SNMP
1-29