TCPIPX-MIB: View SNMP OID List / Download MIB

VENDOR: NOVELL


 Home MIB: TCPIPX-MIB
Download as:   
RFC-1212, RFC1155-SMI

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 novell 1.3.6.1.4.1.23
       mibDoc 1.3.6.1.4.1.23.2
           tcpx 1.3.6.1.4.1.23.2.29
                 tcpxTcp 1.3.6.1.4.1.23.2.29.1
                     tcpIpxConnTable 1.3.6.1.4.1.23.2.29.1.1
A table containing information specific on TCP connection over IPX network layer.
                         tcpIpxConnEntry 1.3.6.1.4.1.23.2.29.1.1.1
Information about a particular current TCP connection over IPX An object of this type is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state.
                             tcpIpxConnState 1.3.6.1.4.1.23.2.29.1.1.1.1
The state of this TCP connection. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
                             tcpIpxConnLocalAddress 1.3.6.1.4.1.23.2.29.1.1.1.2
The local IPX address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any interface, the value 00000000:000000000000 is used. See tcpUnspecConnTable for connections in the listen state which is willing to accept connects for any IP interface associated with the node.
                             tcpIpxConnLocalPort 1.3.6.1.4.1.23.2.29.1.1.1.3
The local port number for this TCP connection.
                             tcpIpxConnRemAddress 1.3.6.1.4.1.23.2.29.1.1.1.4
The remote IPX address for this TCP connection.
                             tcpIpxConnRemPort 1.3.6.1.4.1.23.2.29.1.1.1.5
The remote port number for this TCP connection.
                     tcpUnspecConnTable 1.3.6.1.4.1.23.2.29.1.2
A table containing information specific on TCP connection over unspecified network layer.
                         tcpUnspecConnEntry 1.3.6.1.4.1.23.2.29.1.2.1
Information about a particular current TCP connection over unspecified network layer. An object of this type is transient, in that it ceases to exist when the connection makes transition beyond LISTEN state, or when (or soon after) the connection makes transition to the CLOSED state,
                             tcpUnspecConnState 1.3.6.1.4.1.23.2.29.1.2.1.1
The state of this TCP connection. Since the TCP connection can belong to this table only when its state is less than SYN_SENT, only closed and listen state apply. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
                             tcpUnspecConnLocalPort 1.3.6.1.4.1.23.2.29.1.2.1.2
The local port number for this TCP connection.
                 tcpxUdp 1.3.6.1.4.1.23.2.29.2
                     udpIpxTable 1.3.6.1.4.1.23.2.29.2.1
A table containing UDP listener information.
                         udpIpxEntry 1.3.6.1.4.1.23.2.29.2.1.1
Information about a particular current UDP listener.
                             udpIpxLocalAddress 1.3.6.1.4.1.23.2.29.2.1.1.1
The local IPX address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any interface, the value 00000000:000000000000 is used. See udpUnspecTable for UDP listener which is willing to accept datagrams from any network layer.
                             udpIpxLocalPort 1.3.6.1.4.1.23.2.29.2.1.1.2
The local port number for this UDP listener.
                     udpUnspecTable 1.3.6.1.4.1.23.2.29.2.2
A table containing UDP listener information.
                         udpUnspecEntry 1.3.6.1.4.1.23.2.29.2.2.1
Information about a particular current UDP listener.
                             udpUnspecLocalPort 1.3.6.1.4.1.23.2.29.2.2.1.1
The local port number for this UDP listener.