Wellfleet-TCP-MIB: View SNMP OID List / Download MIB

VENDOR: WELLFLEET


 Home MIB: Wellfleet-TCP-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, Wellfleet-COMMON-MIB

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
 wfTcp 1.3.6.1.4.1.18.3.5.3.3.1
     wfTcpDelete 1.3.6.1.4.1.18.3.5.3.3.1.1 integer read-write
Create/Delete parameter. Default is created. Users perform a set operation on this object in order to create/delete TCP. Enumeration: 'deleted': 2, 'created': 1.
     wfTcpDisable 1.3.6.1.4.1.18.3.5.3.3.1.2 integer read-write
Enable/Disable parameter. Default is enabled. Users perform a set operation on this object in order to enable/disable TCP. Enumeration: 'disabled': 2, 'enabled': 1.
     wfTcpState 1.3.6.1.4.1.18.3.5.3.3.1.3 integer read-only
The current state of the entire TCP. Enumeration: 'down': 2, 'init': 3, 'up': 1, 'notpresent': 4.
     wfTcpRtoAlgorithm 1.3.6.1.4.1.18.3.5.3.3.1.4 integer read-only
The algorithm used to determine the timeout value used for retransmitting unacknowledged octets. Enumeration: 'vanj': 4, 'other': 1, 'constant': 2, 'rsre': 3.
     wfTcpRtoMin 1.3.6.1.4.1.18.3.5.3.3.1.5 integer read-write
The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
     wfTcpRtoMax 1.3.6.1.4.1.18.3.5.3.3.1.6 integer read-write
The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793.
     wfTcpMaxConn 1.3.6.1.4.1.18.3.5.3.3.1.7 integer read-only
The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1.
     wfTcpActiveOpens 1.3.6.1.4.1.18.3.5.3.3.1.8 counter read-only
The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
     wfTcpPassiveOpens 1.3.6.1.4.1.18.3.5.3.3.1.9 counter read-only
The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
     wfTcpAttemptFails 1.3.6.1.4.1.18.3.5.3.3.1.10 counter read-only
The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
     wfTcpEstabResets 1.3.6.1.4.1.18.3.5.3.3.1.11 gauge read-only
The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
     wfTcpCurrEstab 1.3.6.1.4.1.18.3.5.3.3.1.12 gauge read-only
The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.
     wfTcpInSegs 1.3.6.1.4.1.18.3.5.3.3.1.13 counter read-only
The total number of segments received, including those received in error. This count includes segments received on currently established connections.
     wfTcpOutSegs 1.3.6.1.4.1.18.3.5.3.3.1.14 counter read-only
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
     wfTcpRetransSegs 1.3.6.1.4.1.18.3.5.3.3.1.15 counter read-only
The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
     wfTcpInErrs 1.3.6.1.4.1.18.3.5.3.3.1.16 counter read-only
The total number of segments received in error (e.g., bad TCP checksums).
     wfTcpOutRsts 1.3.6.1.4.1.18.3.5.3.3.1.17 counter read-only
The number of TCP segments sent containing the RST flag.
     wfTcpMaxWindow 1.3.6.1.4.1.18.3.5.3.3.1.18 integer read-write
The maximum transmit and receive window size TCP will allow for each connection measured in octets.
 wfTcpConnTable 1.3.6.1.4.1.18.3.5.3.3.2 no-access
The TCP connection table contains information about this entity's existing TCP connections.
     wfTcpConnEntry 1.3.6.1.4.1.18.3.5.3.3.2.1 no-access
A TCP Connection
         wfTcpConnDelete 1.3.6.1.4.1.18.3.5.3.3.2.1.1 integer read-write
The Delete connection attribute. Users set this attribute to a value of TCP_CONN_STATE_DELETE to delete a TCP connection. This is the only value that can be written. The instance should never get created by a user writing to this attribute. Enumeration: 'deleted': 2, 'created': 1.
         wfTcpConnState 1.3.6.1.4.1.18.3.5.3.3.2.1.2 integer read-only
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). Enumeration: 'synreceived': 4, 'established': 5, 'finwait2': 7, 'timewait': 11, 'finwait1': 6, 'lastack': 9, 'closewait': 8, 'deletetcb': 12, 'closed': 1, 'closing': 10, 'listen': 2, 'synsent': 3.
         wfTcpConnLocalAddress 1.3.6.1.4.1.18.3.5.3.3.2.1.3 ipaddress read-only
The local IP address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used.
         wfTcpConnLocalPort 1.3.6.1.4.1.18.3.5.3.3.2.1.4 integer read-only
The local port number for this TCP connection
         wfTcpConnRemAddress 1.3.6.1.4.1.18.3.5.3.3.2.1.5 ipaddress read-only
The remote IP address for this TCP connection.
         wfTcpConnRemPort 1.3.6.1.4.1.18.3.5.3.3.2.1.6 integer read-only
The remote port number for this TCP connection.
         wfTcpConnKeepAliveInterval 1.3.6.1.4.1.18.3.5.3.3.2.1.7 integer read-only
The Interval(seconds) during which no packet has been received on a session. A PROBE packet is sent to elicit an ACK. Value passed by application in tcp_open or tcp_accept.
         wfTcpConnKeepAliveRto 1.3.6.1.4.1.18.3.5.3.3.2.1.8 integer read-only
Keep Alive Retransmit timer (seconds) after which a PROBE packet is sent again if no response has been received. Value passed by application in tcp_open or tcp_accept.
         wfTcpConnKeepAliveCount 1.3.6.1.4.1.18.3.5.3.3.2.1.9 counter read-only
The current number of consecutive Keep-Alive PROBES sent.
         wfTcpConnMd5Errors 1.3.6.1.4.1.18.3.5.3.3.2.1.10 counter read-only
A count of the number of TCP packets dropped \ due to MD5 authentication errors