SNMP MIB Search

   Sample: altiga stat   Advanced Search
Donate your MIB  
Search:   
   
 
Return to vendor list
View mib
Download mib file
Mib: SMUX-MIB
Version: 1


Objects
Scalar Object
smuxPeerEntry.1.3.6.1.4.1.4.4.1.1
An entry in the SMUX peer table.
smuxTreeEntry.1.3.6.1.4.1.4.4.2.1
An entry in the SMUX tree table.
Tabular Object
smuxPindex.1.3.6.1.4.1.4.4.1.1.1
An index which uniquely identifies a SMUX peer.
smuxPidentity.1.3.6.1.4.1.4.4.1.1.2
The authoritative designation for a SMUX peer.
smuxPdescription.1.3.6.1.4.1.4.4.1.1.3
A human-readable description of a SMUX peer.
smuxPstatus.1.3.6.1.4.1.4.4.1.1.4
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.
smuxTsubtree.1.3.6.1.4.1.4.4.2.1.1
The MIB subtree being exported by a SMUX peer.
smuxTpriority.1.3.6.1.4.1.4.4.2.1.2
The SMUX peer's priority when exporting the MIB
subtree.
smuxTindex.1.3.6.1.4.1.4.4.2.1.3
The SMUX peer's identity.
smuxTstatus.1.3.6.1.4.1.4.4.2.1.4
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.
Table
smuxPeerTable.1.3.6.1.4.1.4.4.1
The SMUX peer table.
smuxTreeTable.1.3.6.1.4.1.4.4.2
The SMUX tree table.
Object Identifier
unix.1.3.6.1.4.1.4
smux.1.3.6.1.4.1.4.4
Copyright (c) Tandem Systems, Ltd., 2002-2008