DataMuseum.dk

Presents historical artifacts from the history of:

DKUUG/EUUG Conference tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about DKUUG/EUUG Conference tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download
Index: T v

⟦5acbedb0f⟧ TextFile

    Length: 2850 (0xb22)
    Types: TextFile
    Names: »variables.5«

Derivation

└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit
    └─⟦6311a4dba⟧ »EurOpenD3/network/snmp/cmu-snmp1.0.tar« 
        └─⟦this⟧ »man/variables.5« 

TextFile

.\* /***********************************************************
.\" 	Copyright 1988, 1989 by Carnegie Mellon University
.\" 
.\"                       All Rights Reserved
.\" 
.\" Permission to use, copy, modify, and distribute this software and its 
.\" documentation for any purpose and without fee is hereby granted, 
.\" provided that the above copyright notice appear in all copies and that
.\" both that copyright notice and this permission notice appear in 
.\" supporting documentation, and that the name of CMU not be
.\" used in advertising or publicity pertaining to distribution of the
.\" software without specific, written prior permission.  
.\" 
.\" CMU DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
.\" ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL
.\" CMU BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR
.\" ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
.\" WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
.\" ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
.\" SOFTWARE.
.\" ******************************************************************/
.TH VARIABLES 5 "17 September 1989"
.UC 4
.SH NAME
    variables - Format of specifying variable names to SNMP tools.
.SH SYNOPSIS
    system.sysdescr.0
.SH 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.
.br
If there is no leading "." in the variable name, the name will be formed
as if having been preceded with "iso.org.dod.internet.mgmt.mib.".  A "." must
be placed before the first variable if the user is to fully specify the name.
For example:
.PP
.I 1.1.0  system.sysDescr.0 and 1.sysDescr.0
.PP
all refer to the same variable name.  Likewise:
.PP
.I .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
.PP
All refer to the same variable name.
.PP
The description of the variables in the MIB is given in a file named
.I "mib.txt"
in the current directory or in a file named in the environment variable
.I "MIBFILE" or in
.I "/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.
.SH "SEE ALSO"
RFC 1065, RFC 1066, RFC 1067, ISO IS 8824(ASN.1)
.SH BUGS
The parser of the
.I "mib.txt"
file is not expected to handle bizarre (although correct) interpretations of the ASN.1 notation.