This is the MIB module for objects used to manage the cisco TCP/IP stack running on the Cisco Mainframe Channel Connection (CMCC) board.
The First application to use this stack is the IBM TCP-Offload feature. The main idea with this application is to replace the TCP/IP stack on the IBM host with a protocol requiring lower host CPU utilization, and have the TCP/IP processing done on the router.
There are multiple sets of MIB-II statistics stored by the TCP/IP implementation. Each instance of the MIB-II objects corresponds to an instantiation of the TCP/IP stack which is based on the IP address of the stack.
The IP routing table is not supported here.
This table contains a list of parameters and statistics pertaining to each IP stack. Rows are dynamically added to this table via CMCC TCP application MIBS (ie. CISCO-TCPOFFLOAD-MIB).
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
The indication of whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host).
Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to change this object to an inappropriate value.
cipIpDefaultTTL
1.3.6.1.4.1.9.9.32.1.1.1.1.3
INTEGER (1..255) · Integer32
The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.
cipIpInReceives
1.3.6.1.4.1.9.9.32.1.1.1.1.4
Counter32
The total number of input datagrams received from interfaces, including those received in error, for this IP Address instance.
cipIpInHdrErrors
1.3.6.1.4.1.9.9.32.1.1.1.1.5
Counter32
The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
cipIpInAddrErrors
1.3.6.1.4.1.9.9.32.1.1.1.1.6
Counter32
The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
cipIpForwDatagrams
1.3.6.1.4.1.9.9.32.1.1.1.1.7
Counter32
The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the Source- Route option processing was successful.
cipIpInUnknownProtos
1.3.6.1.4.1.9.9.32.1.1.1.1.8
Counter32
The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
cipIpInDiscards
1.3.6.1.4.1.9.9.32.1.1.1.1.9
Counter32
The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.
cipIpInDelivers
1.3.6.1.4.1.9.9.32.1.1.1.1.10
Counter32
The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
cipIpOutRequests
1.3.6.1.4.1.9.9.32.1.1.1.1.11
Counter32
The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
cipIpOutDiscards
1.3.6.1.4.1.9.9.32.1.1.1.1.12
Counter32
The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
cipIpOutNoRoutes
1.3.6.1.4.1.9.9.32.1.1.1.1.13
Counter32
The number of IP datagrams discarded because no route could be found to transmit them to their destination. Note that this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion. Note that this includes any datagrams which a host cannot route because all of its default gateways are down.
cipIpReasmTimeout
1.3.6.1.4.1.9.9.32.1.1.1.1.14
Integer32
The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
cipIpReasmReqds
1.3.6.1.4.1.9.9.32.1.1.1.1.15
Counter32
The number of IP fragments received which needed to be reassembled at this entity.
cipIpReasmOKs
1.3.6.1.4.1.9.9.32.1.1.1.1.16
Counter32
The number of IP datagrams successfully re- assembled.
cipIpReasmFails
1.3.6.1.4.1.9.9.32.1.1.1.1.17
Counter32
The number of failures detected by the IP re- assembly algorithm (for whatever reason: timed out, errors, etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
cipIpFragOKs
1.3.6.1.4.1.9.9.32.1.1.1.1.18
Counter32
The number of IP datagrams that have been successfully fragmented at this entity.
cipIpFragFails
1.3.6.1.4.1.9.9.32.1.1.1.1.19
Counter32
The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set.
cipIpFragCreates
1.3.6.1.4.1.9.9.32.1.1.1.1.20
Counter32
The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
cipIpRoutingDiscards
1.3.6.1.4.1.9.9.32.1.1.1.1.21
Counter32
The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing entries.
cipTcpStackTable
1.3.6.1.4.1.9.9.32.1.2.1
Index: ifIndex · cipIpAddress
This table contains a list of parameters pertaining to each TCP stack. Rows are dynamically added to this table via CMCC TCP application MIBS (ie. CISCO-TCPOFFLOAD-MIB).
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
cipTcpRtoMin
1.3.6.1.4.1.9.9.32.1.2.1.1.2
Integer32 · milliseconds
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.
cipTcpRtoMax
1.3.6.1.4.1.9.9.32.1.2.1.1.3
Integer32 · milliseconds
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.
cipTcpMaxConn
1.3.6.1.4.1.9.9.32.1.2.1.1.4
Integer32
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.
cipTcpActiveOpens
1.3.6.1.4.1.9.9.32.1.2.1.1.5
Counter32
The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
cipTcpPassiveOpens
1.3.6.1.4.1.9.9.32.1.2.1.1.6
Counter32
The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
cipTcpAttemptFails
1.3.6.1.4.1.9.9.32.1.2.1.1.7
Counter32
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.
cipTcpEstabResets
1.3.6.1.4.1.9.9.32.1.2.1.1.8
Counter32
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.
cipTcpCurrEstab
1.3.6.1.4.1.9.9.32.1.2.1.1.9
Gauge32
The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.
cipTcpInSegs
1.3.6.1.4.1.9.9.32.1.2.1.1.10
Counter32
The total number of segments received, including those received in error. This count includes segments received on currently established connections.
cipTcpOutSegs
1.3.6.1.4.1.9.9.32.1.2.1.1.11
Counter32
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
cipTcpRetransSegs
1.3.6.1.4.1.9.9.32.1.2.1.1.12
Counter32
The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
cipTcpInErrs
1.3.6.1.4.1.9.9.32.1.2.1.1.13
Counter32
The total number of segments received in error (e.g., bad TCP checksums).
cipTcpOutRsts
1.3.6.1.4.1.9.9.32.1.2.1.1.14
Counter32
The number of TCP segments sent containing the RST flag.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
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).
cipTcpConnInHCBytes
1.3.6.1.4.1.9.9.32.1.2.2.1.5
Counter64 (0..18446744073709551615) · octets
The number of bytes sent for this TCP connection.
NOTE: This is a 64 bit (High Capacity)
version of the cipCardCsnaStatsBytesTxd counter for use with SNMP Version 2 Managers
cipTcpConnInBytes
1.3.6.1.4.1.9.9.32.1.2.2.1.6
Counter32 · octets
The number of bytes sent for this TCP connection.
NOTE: To support SNMP Version 1
Managers, this variable is supplied as a 32 bit value which can wrap very frequently.
cipTcpConnOutHCBytes
1.3.6.1.4.1.9.9.32.1.2.2.1.7
Counter64 (0..18446744073709551615) · octets
The number of bytes received for this TCP connection.
NOTE: This is a 64 bit (High Capacity)
version of the cipCardCsnaStatsBytesTxd counter for use with SNMP Version 2 Managers
cipTcpConnOutBytes
1.3.6.1.4.1.9.9.32.1.2.2.1.8
Counter32 · octets
The number of bytes received for this TCP connection.
NOTE: To support SNMP Version 1
Managers, this variable is supplied as a 32 bit value which can wrap very frequently.
cipIcmpTable
1.3.6.1.4.1.9.9.32.1.3.1
Index: ifIndex · cipIpAddress
This table contains a list of parameters pertaining to each ICMP stack. Rows are dynamically added to this table via CMCC TCP application MIBS (ie. CISCO-TCPOFFLOAD-MIB).
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
cipIcmpInMsgs
1.3.6.1.4.1.9.9.32.1.3.1.1.1
Counter32
The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.
cipIcmpInErrors
1.3.6.1.4.1.9.9.32.1.3.1.1.2
Counter32
The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
cipIcmpInDestUnreachs
1.3.6.1.4.1.9.9.32.1.3.1.1.3
Counter32
The number of ICMP Destination Unreachable messages received.
cipIcmpInTimeExcds
1.3.6.1.4.1.9.9.32.1.3.1.1.4
Counter32
The number of ICMP Time Exceeded messages received.
cipIcmpInParmProbs
1.3.6.1.4.1.9.9.32.1.3.1.1.5
Counter32
The number of ICMP Parameter Problem messages received.
cipIcmpInSrcQuenchs
1.3.6.1.4.1.9.9.32.1.3.1.1.6
Counter32
The number of ICMP Source Quench messages received.
cipIcmpInRedirects
1.3.6.1.4.1.9.9.32.1.3.1.1.7
Counter32
The number of ICMP Redirect messages received.
cipIcmpInEchos
1.3.6.1.4.1.9.9.32.1.3.1.1.8
Counter32
The number of ICMP Echo (request) messages received.
cipIcmpInAddrMaskReps
1.3.6.1.4.1.9.9.32.1.3.1.1.9
Counter32
The number of ICMP Address Mask Reply messages received.
cipIcmpOutMsgs
1.3.6.1.4.1.9.9.32.1.3.1.1.10
Counter32
The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
cipIcmpOutErrors
1.3.6.1.4.1.9.9.32.1.3.1.1.11
Counter32
The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value.
cipIcmpOutDestUnreachs
1.3.6.1.4.1.9.9.32.1.3.1.1.12
Counter32
The number of ICMP Destination Unreachable messages sent.
cipIcmpOutEchos
1.3.6.1.4.1.9.9.32.1.3.1.1.13
Counter32
The number of ICMP Echo (request) messages sent.
cipIcmpOutEchoReps
1.3.6.1.4.1.9.9.32.1.3.1.1.14
Counter32
The number of ICMP Echo Reply messages sent.
cipIcmpOutTimestamps
1.3.6.1.4.1.9.9.32.1.3.1.1.15
Counter32
The number of ICMP Timestamp (request) messages sent.
cipIcmpOutTimestampReps
1.3.6.1.4.1.9.9.32.1.3.1.1.16
Counter32
The number of ICMP Timestamp Reply messages sent.
cipIcmpOutAddrMasks
1.3.6.1.4.1.9.9.32.1.3.1.1.17
Counter32
The number of ICMP Address Mask Request messages sent.
cipIcmpOutAddrMaskReps
1.3.6.1.4.1.9.9.32.1.3.1.1.18
Counter32
The number of ICMP Address Mask Reply messages sent.
cipUdpTable
1.3.6.1.4.1.9.9.32.1.4.1
Index: ifIndex · cipIpAddress
This table contains a list of parameters pertaining to each UDP stack. Rows are dynamically added to this table via CMCC TCP application MIBS (ie. CISCO-TCPOFFLOAD-MIB).
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
cipUdpInDatagrams
1.3.6.1.4.1.9.9.32.1.4.1.1.1
Counter32
The total number of UDP datagrams delivered to UDP users.
cipUdpNoPorts
1.3.6.1.4.1.9.9.32.1.4.1.1.2
Counter32
The total number of received UDP datagrams for which there was no application at the destination port.
cipUdpInErrors
1.3.6.1.4.1.9.9.32.1.4.1.1.3
Counter32
The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
cipUdpOutDatagrams
1.3.6.1.4.1.9.9.32.1.4.1.1.4
Counter32
The total number of UDP datagrams sent from this entity.
cipUdpListenersTable
1.3.6.1.4.1.9.9.32.1.4.2
Index: ifIndex · cipIpAddress · cipUdpLocalPort
This table contains a list of parameters pertaining to the listeners for a particular UDP stack.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.