TCP/IP subagent: Management data supported

The following items are the main areas of the TCP/IP stack for which MIB data is supported:

IP/ICMP/Route MIB data
The subagent supports IP/ICMP MIB data from the IP-MIB in RFC 4293, and some additional IP counters from the Enterprise-specific MIB. The subagent supports Route MIB data from the IP-FORWARD-MIB in RFC 4292, and from the TCP/IP Enterprise-specific MIB.
Interface MIB data
The subagent supports interface (IF) MIB data from the IF-MIB in RFC 2233. The TCP/IP Enterprise-specific MIB defines the following additional MIB data:
- Information from the DEVICE, LINK, and INTERFACE profile statements.
- Multicast group information per interface.
- Packet trace parameters per interface
- ibmMvsTcpipIntfUp and ibmMvsTcpipIntfDown notifications, which include the name of the interface whose state is changing.
Although the subagent supports interface state change notifications, these notifications are not created for VIPA interfaces (static or dynamic). This is because VIPA interfaces do not change operational state. If they are successfully defined, then they are always active and they cannot be stopped by using the VARY TCPIP,,STOP command. This affects the following interface state change notifications:
- The linkup and linkdown notifications from the IF-MIB
- The ibmMvsTcpipIntfUp and ibmMvsTcpipIntfDown notifications from the TCP/IP Enterprise-specific MIB
Proprietary status change notifications are still created for dynamic VIPA interfaces. See SNMP Enterprise-specific trap types for more information about these notifications.
TCP MIB data
The subagent supports the TCP MIB data from the TCP-MIB in RFC 4022. The TCP global counters in the TCP-MIB reflect both IPv4 and IPv6 processing. The Enterprise-specific MIB augments the standard IPv4-only and version-neutral TCP connection table; provides a TCP Listener table with server MIB data; and provides additional TCP stack counters.
UDP MIB data
The subagent supports the UDP MIB data from the UDP-MIB in RFC 4113. The UDP global counters in the UDP-MIB reflect both IPv4 and IPv6 processing. The Enterprise-specific MIB augments the standard UDP listener table (IPv4-only) and the version-neutral UDP endpoint table, and also provides multicast information.
TCP/IP stack configuration data
The TCP/IP Enterprise-specific MIB defines MIB objects that support the following configuration data:
- Data from Profile configuration statements such as IPCONFIG, IPCONFIG6, SACONFIG, TCPCONFIG, and UDPCONFIG
- TCP/IP stack name
- MVS™ image name
- XCF group name used by the stack when joining the sysplex