golden hour

/opt/alt/net-snmp11/usr/share/snmp/mibs

File/Folder	Size	Actions
AGENTX-MIB.txt	17.05 KB
BRIDGE-MIB.txt	49.75 KB
DISMAN-EVENT-MIB.txt	66.51 KB
DISMAN-SCHEDULE-MIB.txt	24.04 KB
DISMAN-SCRIPT-MIB.txt	62.8 KB
EtherLike-MIB.txt	82.51 KB
HCNUM-TC.txt	4.55 KB
HOST-RESOURCES-MIB.txt	51.31 KB
HOST-RESOURCES-TYPES.txt	10.33 KB
IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt	6.56 KB
IANA-LANGUAGE-MIB.txt	4.28 KB
IANA-RTPROTO-MIB.txt	4 KB
IANAifType-MIB.txt	34.55 KB
IF-INVERTED-STACK-MIB.txt	4.95 KB
IF-MIB.txt	70.01 KB
INET-ADDRESS-MIB.txt	16.39 KB
IP-FORWARD-MIB.txt	45.2 KB
IP-MIB.txt	181.32 KB
IPV6-FLOW-LABEL-MIB.txt	1.98 KB
IPV6-ICMP-MIB.txt	20.56 KB
IPV6-MIB.txt	55.14 KB
IPV6-TC.txt	3.08 KB
IPV6-TCP-MIB.txt	8.65 KB
IPV6-UDP-MIB.txt	5.56 KB
LM-SENSORS-MIB.txt	5.79 KB
MTA-MIB.txt	41.38 KB
NET-SNMP-AGENT-MIB.txt	15.53 KB
NET-SNMP-EXAMPLES-MIB.txt	8.95 KB
NET-SNMP-EXTEND-MIB.txt	9.11 KB
NET-SNMP-MIB.txt	1.99 KB
NET-SNMP-PASS-MIB.txt	3.64 KB
NET-SNMP-TC.txt	4.7 KB
NETWORK-SERVICES-MIB.txt	20.51 KB
NOTIFICATION-LOG-MIB.txt	24.12 KB
RFC-1215.txt	1.15 KB
RFC1155-SMI.txt	3 KB
RFC1213-MIB.txt	77.8 KB
RMON-MIB.txt	144.36 KB
SCTP-MIB.txt	44.26 KB
SMUX-MIB.txt	4.54 KB
SNMP-COMMUNITY-MIB.txt	15.13 KB
SNMP-FRAMEWORK-MIB.txt	21.82 KB
SNMP-MPD-MIB.txt	5.37 KB
SNMP-NOTIFICATION-MIB.txt	19.54 KB
SNMP-PROXY-MIB.txt	8.89 KB
SNMP-TARGET-MIB.txt	22.24 KB
SNMP-TLS-TM-MIB.txt	42.9 KB
SNMP-TSM-MIB.txt	8.7 KB
SNMP-USER-BASED-SM-MIB.txt	38.28 KB
SNMP-USM-AES-MIB.txt	2.15 KB
SNMP-USM-DH-OBJECTS-MIB.txt	20.61 KB
SNMP-USM-HMAC-SHA2-MIB.txt	4.3 KB
SNMP-VIEW-BASED-ACM-MIB.txt	33.36 KB
SNMPv2-CONF.txt	8.07 KB
SNMPv2-MIB.txt	28.62 KB
SNMPv2-SMI.txt	8.71 KB
SNMPv2-TC.txt	37.14 KB
SNMPv2-TM.txt	5.64 KB
TCP-MIB.txt	27.89 KB
TRANSPORT-ADDRESS-MIB.txt	16.03 KB
TUNNEL-MIB.txt	27.17 KB
UCD-DEMO-MIB.txt	2.11 KB
UCD-DISKIO-MIB.txt	4.85 KB
UCD-DLMOD-MIB.txt	3.01 KB
UCD-IPFWACC-MIB.txt	7.93 KB
UCD-SNMP-MIB.txt	51.58 KB
UDP-MIB.txt	20.39 KB

Edit: SMUX-MIB.txt

SMUX-MIB DEFINITIONS ::= BEGIN

IMPORTS
        enterprises
                FROM RFC1155-SMI
        DisplayString
                FROM SNMPv2-TC
        OBJECT-TYPE
                FROM RFC-1212;

unix    OBJECT IDENTIFIER ::= { enterprises 4 }

smux    OBJECT IDENTIFIER ::= { unix 4 }

smuxPeerTable   OBJECT-TYPE
        SYNTAX  SEQUENCE OF SmuxPeerEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
            "The SMUX peer table."
        ::= { smux 1 }

smuxPeerEntry   OBJECT-TYPE
        SYNTAX  SmuxPeerEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
            "An entry in the SMUX peer table."
        INDEX   { smuxPindex }
        ::= { smuxPeerTable 1}

SmuxPeerEntry ::=
    SEQUENCE {
        smuxPindex
            INTEGER,
        smuxPidentity
            OBJECT IDENTIFIER,
        smuxPdescription
            DisplayString,
        smuxPstatus
            INTEGER
    }

smuxPindex      OBJECT-TYPE
        SYNTAX  INTEGER
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
            "An index which uniquely identifies a SMUX peer."
        ::= { smuxPeerEntry 1 }

smuxPidentity   OBJECT-TYPE
        SYNTAX  OBJECT IDENTIFIER
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
            "The authoritative designation for a SMUX peer."
        ::= { smuxPeerEntry 2 }

smuxPdescription OBJECT-TYPE
        SYNTAX  DisplayString (SIZE (0..255))
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
            "A human-readable description of a SMUX peer."
        ::= { smuxPeerEntry 3 }

smuxPstatus     OBJECT-TYPE
        SYNTAX  INTEGER { valid(1), invalid(2), connecting(3) }
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
            "The type of SMUX peer.

Setting this object to the value invalid(2) has
            the effect of invaliding the corresponding entry
            in the smuxPeerTable.  It is an implementation-
            specific matter as to whether the agent removes an
            invalidated entry from the table.  Accordingly,
            management stations must be prepared to receive
            tabular information from agents that correspond to
            entries not currently in use.  Proper
            interpretation of such entries requires
            examination of the relative smuxPstatus object."
        ::= { smuxPeerEntry 4 }

smuxTreeTable   OBJECT-TYPE
        SYNTAX  SEQUENCE OF SmuxTreeEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
            "The SMUX tree table."
        ::= { smux 2 }

smuxTreeEntry   OBJECT-TYPE
        SYNTAX  SmuxTreeEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
            "An entry in the SMUX tree table."
        INDEX   { smuxTsubtree, smuxTpriority }
        ::= { smuxTreeTable 1}

SmuxTreeEntry ::=
    SEQUENCE {
        smuxTsubtree
            OBJECT IDENTIFIER,
        smuxTpriority
            INTEGER,
        smuxTindex
            INTEGER,
        smuxTstatus
            INTEGER
    }

smuxTsubtree    OBJECT-TYPE
        SYNTAX  OBJECT IDENTIFIER
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
            "The MIB subtree being exported by a SMUX peer."
        ::= { smuxTreeEntry 1 }

smuxTpriority OBJECT-TYPE
        SYNTAX  INTEGER (0..'07fffffff'h)
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
            "The SMUX peer's priority when exporting the MIB
            subtree."
        ::= { smuxTreeEntry 2 }

smuxTindex OBJECT-TYPE
        SYNTAX  INTEGER
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
            "The SMUX peer's identity."
        ::= { smuxTreeEntry 3 }

smuxTstatus     OBJECT-TYPE
        SYNTAX  INTEGER { valid(1), invalid(2) }
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
            "The type of SMUX tree.

Setting this object to the value invalid(2) has
            the effect of invaliding the corresponding entry
            in the smuxTreeTable.  It is an implementation-
            specific matter as to whether the agent removes an
            invalidated entry from the table.  Accordingly,
            management stations must be prepared to receive
            tabular information from agents that correspond to
            entries not currently in use.  Proper
            interpretation of such entries requires
            examination of the relative smuxTstatus object."
        ::= { smuxTreeEntry 4 }

END