Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ snmpbase.dat(4M) — DG/UX R4.11MU05

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

snmpd(1M)

admsnmpuea(1M)

postmosy(1M)



info.dat(4M)                   DG/UX R4.11MU05                  info.dat(4M)


NAME
       snmpinfo.dat, snmpbase.dat, snmpuea.dat - SNMP Agent MIB object
       information file

DESCRIPTION
       This file defines the SNMP MIB objects that are manageable via SNMP.
       Each MIB object definition contains the mappings of OIDs to MIB
       object names as well as the type and access for each object.

       The /etc/snmpinfo.dat file is a compilation of SNMP MIB objects
       defined in various *.dat files located in the /etc/srconf/datinfo
       directory.  This includes the snmpbase.dat file loaded by the
       installation of DG/UX and the snmpuea.dat file maintained by the SNMP
       User Extensible Agent (UEA).

       A new /etc/snmpinfo.dat file is generated during the installation of
       DG/UX and by executing the export operation of the admsnmpuea
       command.


   File Format
       Each SNMP MIB object definition must appear on its own line with its
       different fields separated by spaces and/or tabs.  The object's
       fields must appear in the order specified.  Comment lines must be
       surrounded by "/*" and "*/ (ex. /* This is a comment line */).

       SNMP MIB object definition records have the following format:


       object-name object-id object-type object-access
       where:

       object-name    is an ASCII string of up to 64 characters (letters,
                      digits, hyphens) specifying the SNMP MIB object name.
                      Names must: 1) begin with a lowercase letter 2) not
                      end with a hyphen 3) not contain a hypen followed by
                      another hyphen 4) be unique.

       object-id      is an OID in dot notation format which specifies the
                      location of where object-name resides in the MIB tree.
                      OIDs must be in the correct format and must be unique.

       object-type    defines the object type.  Valid object types include:
                      "Null", "nonLeaf", "Aggregate", "DisplayString",
                      "OctetString", "PhysAddress", "NetworkAddress",
                      "IpAddress", "ObjectID", "TimeTicks", "INTEGER",
                      "Gauge", "Counter", "Services", "Counter32",
                      "Gauge32", "NsapAddress", "Counter64", "UInteger32",
                      "Integer32", "BitString".

       bject-access   defines the access of the object.  Valid accesses
                      include: "read-only", "read-write", "read-create",
                      "not-accessible".


SEE ALSO
       snmpd(1M), admsnmpuea(1M), postmosy(1M), snmpdfiles(4M).


Licensed material--property of copyright holder(s)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026