SNMP_OID(3)SNMP_OID(3)NAMEsnmp_oid - Format of specifying variable names to SNMP tools.
SYNOPSIS
system.sysdescr.0
DESCRIPTION
Variable names are in the format of Object Identifiers (ASN.1). There
are several methods of representation. Each variable name is given in
the format of A.B.C.D..., where A, B, C, and D are subidentifiers in
one of two forms of notation. Each subidentifier may be encoded as a
decimal integer, or a symbol as found in the RFC1066 MIB. The case of
the symbols is not significant.
If there is no leading "." in the variable name, the name will be
formed as if having been preceded with "iso.org.dod.inter‐
net.mgmt.mib.". A "." must be placed before the first variable if the
user is to fully specify the name. For example:
1.1.0 system.sysDescr.0 and 1.sysDescr.0
all refer to the same variable name. Likewise:
.1.3.6.1.2.1.1.1.0 .iso.org.dod.internet.mgmt.mib.system.sysdescr.0
.1.3.6.1.2.1.1.sysdescr.0
All refer to the same variable name.
The description of the variables in the MIB is given in a file named
mib.txt in the current directory or in a file named in the environment
variable MIBFILE or in /etc/mib.txt . These files are searched in the
above order. The files are in the ASN.1 notation and use the OBJECT
TYPE macro defined in RFC 1065. Most of the file describing the RFC
1066 MIB is pulled out of RFC 1066 without change.
BUGS
The mibfile parser is not expected to handle bizarre (although correct)
interpretations of the ASN.1 notation.
RFCS
Related RFCs: 1065, 1066, 1067
Related SNMPv2 RFCs: 1901, 1902, 1902, 1904, 1905, 1906, 1907, 1908,
1909
RELATED URLS
CMU Networking Group: http://www.net.cmu.edu/
CMU SNMP Home Page: http://www.net.cmu.edu/projects/snmp
SEE ALSOsnmp_api(3), snmp_api_errors(3), snmp_client(3), snmp_coexistance(3),
snmp_error(3), snmp_extra(3), snmp_mib(3), snmp_mibii(3),
snmp_mini_client(3), snmp_msg(3), snmp_packet_dump(3), snmp_pdu(3),
snmp_sess_api(3), snmp_vars(3), snmp_version_info(3), snmp_oid(5)snmp(3)4th Berkeley Distribution Tue Sep 24 11:13:15 2002SNMP_OID(3)