CISCO-CIPTCPIP-MIB

All MIBs › CISCO-CIPTCPIP-MIB

Organization: cisco IBM engineering Working Group

Last Updated: 1998--0-1-

Category: Cisco Devices, SNA and Legacy Protocols

Description: Manages TCP/IP offload and channel operations on the Cisco CIP, tracking connections between mainframe applications and IP networks.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-CIPTCPIP-MIB?

CISCO-CIPTCPIP-MIB manages the TCP/IP protocol stack running on the Cisco Mainframe Channel Connection (CMCC) board, part of Cisco's Channel Interface Processor (CIP) product line for connecting IBM mainframes to IP networks. It exposes a MIB-II-style table of IP layer statistics per stack instance, including addressing, forwarding, and error/discard counters for datagrams processed by the offloaded TCP/IP implementation. It supports software status monitoring by tracking protocol-level health: rising cipIpInDiscards or cipIpInHdrErrors indicates the CMCC board's TCP/IP stack is encountering malformed or unprocessable traffic, while cipIpInReceives and cipIpForwDatagrams show throughput being handled by the offload engine. It deliberately mirrors and depends on the structure of the standard IP group from MIB-II (RFC 1213). It is deployed in mainframe data centers using Cisco CIP/CMCC hardware, where the CISCO-CIPTCPIP-MIB MIB is used to offload IBM TCP/IP processing from the host to the router.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-CIPTCPIP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco Mainframe Channel Connection (CMCC) board
Cisco Channel Interface Processor (CIP)

Monitoring Examples

An admin would poll cipIpTable, keyed by cipIpAddress, watching cipIpInDiscards and cipIpInAddrErrors to detect the CMCC's offloaded TCP/IP stack dropping or misrouting datagrams intended for the mainframe host. Comparing cipIpInReceives against cipIpInDelivers over time reveals whether packets are being successfully passed up to the offload application. A rising cipIpInUnknownProtos count would indicate unexpected protocol traffic reaching the CIP board's IP stack.

What Can Be Monitored

IP datagram receive/forward counts
header and address error counts
discarded datagram count
per-instance IP stack statistics

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From IF-MIB

ifIndex

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Gauge32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

How to Use in IPNetwork Monitor

Example using cipIpInReceives OID:

Select a Cisco CMCC/CIP mainframe channel connection board (legacy) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cipIpInReceives into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The total number of input datagrams received from interfaces, including those received in error, for this IP Address instance. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
cipIcmpEntry	1.3.6.1.4.1.9.9.32.1.3.1.1		not-accessible	A list of ICMP values.
C32 cipIcmpInAddrMaskReps	1.3.6.1.4.1.9.9.32.1.3.1.1.9	Counter32	read-only	The number of ICMP Address Mask Reply messages received.
C32 cipIcmpInDestUnreachs	1.3.6.1.4.1.9.9.32.1.3.1.1.3	Counter32	read-only	The number of ICMP Destination Unreachable messages received.
C32 cipIcmpInEchos	1.3.6.1.4.1.9.9.32.1.3.1.1.8	Counter32	read-only	The number of ICMP Echo (request) messages received.
C32 cipIcmpInErrors	1.3.6.1.4.1.9.9.32.1.3.1.1.2	Counter32	read-only	The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
C32 cipIcmpInMsgs	1.3.6.1.4.1.9.9.32.1.3.1.1.1	Counter32	read-only	The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.
C32 cipIcmpInParmProbs	1.3.6.1.4.1.9.9.32.1.3.1.1.5	Counter32	read-only	The number of ICMP Parameter Problem messages received.
C32 cipIcmpInRedirects	1.3.6.1.4.1.9.9.32.1.3.1.1.7	Counter32	read-only	The number of ICMP Redirect messages received.
C32 cipIcmpInSrcQuenchs	1.3.6.1.4.1.9.9.32.1.3.1.1.6	Counter32	read-only	The number of ICMP Source Quench messages received.
C32 cipIcmpInTimeExcds	1.3.6.1.4.1.9.9.32.1.3.1.1.4	Counter32	read-only	The number of ICMP Time Exceeded messages received.
cipIcmpObjects	1.3.6.1.4.1.9.9.32.1.3
C32 cipIcmpOutAddrMaskReps	1.3.6.1.4.1.9.9.32.1.3.1.1.18	Counter32	read-only	The number of ICMP Address Mask Reply messages sent.
C32 cipIcmpOutAddrMasks	1.3.6.1.4.1.9.9.32.1.3.1.1.17	Counter32	read-only	The number of ICMP Address Mask Request messages sent.
C32 cipIcmpOutDestUnreachs	1.3.6.1.4.1.9.9.32.1.3.1.1.12	Counter32	read-only	The number of ICMP Destination Unreachable messages sent.
C32 cipIcmpOutEchoReps	1.3.6.1.4.1.9.9.32.1.3.1.1.14	Counter32	read-only	The number of ICMP Echo Reply messages sent.
C32 cipIcmpOutEchos	1.3.6.1.4.1.9.9.32.1.3.1.1.13	Counter32	read-only	The number of ICMP Echo (request) messages sent.
C32 cipIcmpOutErrors	1.3.6.1.4.1.9.9.32.1.3.1.1.11	Counter32	read-only	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.
C32 cipIcmpOutMsgs	1.3.6.1.4.1.9.9.32.1.3.1.1.10	Counter32	read-only	The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
C32 cipIcmpOutTimestampReps	1.3.6.1.4.1.9.9.32.1.3.1.1.16	Counter32	read-only	The number of ICMP Timestamp Reply messages sent.
C32 cipIcmpOutTimestamps	1.3.6.1.4.1.9.9.32.1.3.1.1.15	Counter32	read-only	The number of ICMP Timestamp (request) messages sent.
cipIcmpTable	1.3.6.1.4.1.9.9.32.1.3.1		not-accessible	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).
IP cipIpAddress	1.3.6.1.4.1.9.9.32.1.1.1.1.1	IpAddress	not-accessible	The IP address for this IP stack.
INT cipIpDefaultTTL	1.3.6.1.4.1.9.9.32.1.1.1.1.3	INTEGER	read-write	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.
cipIpEntry	1.3.6.1.4.1.9.9.32.1.1.1.1		not-accessible	A list of IP stack values.
INT cipIpForwarding	1.3.6.1.4.1.9.9.32.1.1.1.1.2	INTEGER	read-write	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.
C32 cipIpForwDatagrams	1.3.6.1.4.1.9.9.32.1.1.1.1.7	Counter32	read-only	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.
C32 cipIpFragCreates	1.3.6.1.4.1.9.9.32.1.1.1.1.20	Counter32	read-only	The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
C32 cipIpFragFails	1.3.6.1.4.1.9.9.32.1.1.1.1.19	Counter32	read-only	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.
C32 cipIpFragOKs	1.3.6.1.4.1.9.9.32.1.1.1.1.18	Counter32	read-only	The number of IP datagrams that have been successfully fragmented at this entity.
C32 cipIpInAddrErrors	1.3.6.1.4.1.9.9.32.1.1.1.1.6	Counter32	read-only	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.
C32 cipIpInDelivers	1.3.6.1.4.1.9.9.32.1.1.1.1.10	Counter32	read-only	The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
C32 cipIpInDiscards	1.3.6.1.4.1.9.9.32.1.1.1.1.9	Counter32	read-only	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.
C32 cipIpInHdrErrors	1.3.6.1.4.1.9.9.32.1.1.1.1.5	Counter32	read-only	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.
C32 cipIpInReceivesEx	1.3.6.1.4.1.9.9.32.1.1.1.1.4	Counter32	read-only	The total number of input datagrams received from interfaces, including those received in error, for this IP Address instance.
C32 cipIpInUnknownProtos	1.3.6.1.4.1.9.9.32.1.1.1.1.8	Counter32	read-only	The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
cipIpObjects	1.3.6.1.4.1.9.9.32.1.1
C32 cipIpOutDiscards	1.3.6.1.4.1.9.9.32.1.1.1.1.12	Counter32	read-only	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.
C32 cipIpOutNoRoutes	1.3.6.1.4.1.9.9.32.1.1.1.1.13	Counter32	read-only	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.
C32 cipIpOutRequests	1.3.6.1.4.1.9.9.32.1.1.1.1.11	Counter32	read-only	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.
C32 cipIpReasmFails	1.3.6.1.4.1.9.9.32.1.1.1.1.17	Counter32	read-only	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.
C32 cipIpReasmOKs	1.3.6.1.4.1.9.9.32.1.1.1.1.16	Counter32	read-only	The number of IP datagrams successfully re- assembled.
C32 cipIpReasmReqds	1.3.6.1.4.1.9.9.32.1.1.1.1.15	Counter32	read-only	The number of IP fragments received which needed to be reassembled at this entity.
I32 cipIpReasmTimeout	1.3.6.1.4.1.9.9.32.1.1.1.1.14	Integer32	read-only	The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
C32 cipIpRoutingDiscards	1.3.6.1.4.1.9.9.32.1.1.1.1.21	Counter32	read-only	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.
cipIpTable	1.3.6.1.4.1.9.9.32.1.1.1		not-accessible	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).
C32 cipTcpActiveOpens	1.3.6.1.4.1.9.9.32.1.2.1.1.5	Counter32	read-only	The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
C32 cipTcpAttemptFails	1.3.6.1.4.1.9.9.32.1.2.1.1.7	Counter32	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.
cipTcpConnEntry	1.3.6.1.4.1.9.9.32.1.2.2.1		not-accessible	A list of TCP connection values.
C32 cipTcpConnInBytes	1.3.6.1.4.1.9.9.32.1.2.2.1.6	Counter32	read-only	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.
C64 cipTcpConnInHCBytes	1.3.6.1.4.1.9.9.32.1.2.2.1.5	Counter64	read-only	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
INT cipTcpConnLocalPort	1.3.6.1.4.1.9.9.32.1.2.2.1.1	INTEGER	not-accessible	The local port number for this TCP connection.
C32 cipTcpConnOutBytes	1.3.6.1.4.1.9.9.32.1.2.2.1.8	Counter32	read-only	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.
C64 cipTcpConnOutHCBytes	1.3.6.1.4.1.9.9.32.1.2.2.1.7	Counter64	read-only	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
IP cipTcpConnRemAddress	1.3.6.1.4.1.9.9.32.1.2.2.1.2	IpAddress	not-accessible	The remote IP address for this TCP connection.
INT cipTcpConnRemPort	1.3.6.1.4.1.9.9.32.1.2.2.1.3	INTEGER	not-accessible	The remote port number for this TCP connection.
INT cipTcpConnState	1.3.6.1.4.1.9.9.32.1.2.2.1.4	INTEGER	read-write	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).
cipTcpConnTable	1.3.6.1.4.1.9.9.32.1.2.2		not-accessible	This table contains a list of parameters pertaining to the connections for a particular TCP Offload stack.
G32 cipTcpCurrEstab	1.3.6.1.4.1.9.9.32.1.2.1.1.9	Gauge32	read-only	The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.
C32 cipTcpEstabResets	1.3.6.1.4.1.9.9.32.1.2.1.1.8	Counter32	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.
C32 cipTcpInErrs	1.3.6.1.4.1.9.9.32.1.2.1.1.13	Counter32	read-only	The total number of segments received in error (e.g., bad TCP checksums).
C32 cipTcpInSegs	1.3.6.1.4.1.9.9.32.1.2.1.1.10	Counter32	read-only	The total number of segments received, including those received in error. This count includes segments received on currently established connections.
cipTcpIpObjects	1.3.6.1.4.1.9.9.32.1
I32 cipTcpMaxConn	1.3.6.1.4.1.9.9.32.1.2.1.1.4	Integer32	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.
cipTcpObjects	1.3.6.1.4.1.9.9.32.1.2
C32 cipTcpOutRsts	1.3.6.1.4.1.9.9.32.1.2.1.1.14	Counter32	read-only	The number of TCP segments sent containing the RST flag.
C32 cipTcpOutSegs	1.3.6.1.4.1.9.9.32.1.2.1.1.11	Counter32	read-only	The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
C32 cipTcpPassiveOpens	1.3.6.1.4.1.9.9.32.1.2.1.1.6	Counter32	read-only	The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
C32 cipTcpRetransSegs	1.3.6.1.4.1.9.9.32.1.2.1.1.12	Counter32	read-only	The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
INT cipTcpRtoAlgorithm	1.3.6.1.4.1.9.9.32.1.2.1.1.1	INTEGER	read-only	The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
I32 cipTcpRtoMax	1.3.6.1.4.1.9.9.32.1.2.1.1.3	Integer32	read-only	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.
I32 cipTcpRtoMin	1.3.6.1.4.1.9.9.32.1.2.1.1.2	Integer32	read-only	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.
cipTcpStackEntry	1.3.6.1.4.1.9.9.32.1.2.1.1		not-accessible	A list of TCP stack values.
cipTcpStackTable	1.3.6.1.4.1.9.9.32.1.2.1		not-accessible	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).
cipUdpEntry	1.3.6.1.4.1.9.9.32.1.4.1.1		not-accessible	A list of UDP stack values.
C32 cipUdpInDatagrams	1.3.6.1.4.1.9.9.32.1.4.1.1.1	Counter32	read-only	The total number of UDP datagrams delivered to UDP users.
C32 cipUdpInErrors	1.3.6.1.4.1.9.9.32.1.4.1.1.3	Counter32	read-only	The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
cipUdpListenersEntry	1.3.6.1.4.1.9.9.32.1.4.2.1		not-accessible	A list of UDP listener values.
cipUdpListenersTable	1.3.6.1.4.1.9.9.32.1.4.2		not-accessible	This table contains a list of parameters pertaining to the listeners for a particular UDP stack.
INT cipUdpLocalPort	1.3.6.1.4.1.9.9.32.1.4.2.1.1	INTEGER	read-only	The local port number for this UDP listener.
C32 cipUdpNoPorts	1.3.6.1.4.1.9.9.32.1.4.1.1.2	Counter32	read-only	The total number of received UDP datagrams for which there was no application at the destination port.
cipUdpObjects	1.3.6.1.4.1.9.9.32.1.4
C32 cipUdpOutDatagrams	1.3.6.1.4.1.9.9.32.1.4.1.1.4	Counter32	read-only	The total number of UDP datagrams sent from this entity.
cipUdpTable	1.3.6.1.4.1.9.9.32.1.4.1		not-accessible	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).
ciscoCipTcpIpGroup	1.3.6.1.4.1.9.9.32.2.2.1			A collection of objects providing information for the CMCC TCP/IP protocol stacks.
ciscoCipTcpIpMIB	1.3.6.1.4.1.9.9.32			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.
ciscoCipTcpIpMibCompliance	1.3.6.1.4.1.9.9.32.2.1.1			The compliance statement for the CMCC TCP/IP Stack.
ciscoCipTcpIpMibCompliances	1.3.6.1.4.1.9.9.32.2.1
ciscoCipTcpIpMibConformance	1.3.6.1.4.1.9.9.32.2
ciscoCipTcpIpMibGroups	1.3.6.1.4.1.9.9.32.2.2

RFC description

Manages TCP/IP stack on Cisco mainframe channel cards enabling TCP offload and protocol processing from host systems.

Start monitoring Cisco CMCC/CIP mainframe channel connection board (legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-CIPTCPIP-MIB