IBMTCPIPMVS-MIB: View SNMP OID List / Download MIB

The number of milliseconds it takes for an icmp echo request to respond. ibmSNMPRemPing is -1 if there is an internal error, -2 if the echo request timed out, -4 if the packet size is invalid, -5 if the timeout is invalid, -6 if the IP address was not valid and -7 if the format of the MIB instance is not valid. To request the icmp response time for ip address a.b.c.d with a timeout of e and a packet size of f, send an snmp get request for ibmSNMPRemPing.f.e.a.b.c.d. For example, suppose one wanted to find out the number of milliseconds it took to ping address 9.67.30.4, with a timeout of 8 seconds, and a packet size of 94 bytes. Accordingly, ibmSNMPRemPing.94.8.9.67.30.4 would identify the number of milliseconds.

The IBM Communications Server Enterprise Specific MIB definitions for enabling management of an IBM Communications Server IP system. Licensed Materials - Property of IBM Restricted Materials of IBM 5694-A01 (C) Copyright IBM Corp. 1997, 2001 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This trap is generated when OSA/SF sends a asynch notification to the TCP/IP DPI Subagent that a PVC was created for a given OSA Port. This notification contains the corresponding ibmMvsAtmOsasfPortName instance. Representation of this will contain the aal5 layer interface ifIndex of the port, the PVC name len, and the PVC name in ASCII as 'ifIndex.pvcNameOctetCount.pvcNameInASCIINvt'.

This trap is generated when OSA/SF sends a asyn notification to the TCP/IP DPI Subagent that a PVC was deleted for a given OSA Port. This notification contains the corresponding ibmMvsAtmOsasfPortName instance. Representation of this will contain the aal5 layer interface ifIndex of the port, the PVC name len, and the PVC name in ASCII as 'ifIndex.pvcNameOctetCount.pvcNameInASCIINvt'.

This trap is generated when a dynamic VIPA is defined or its status changes on a TCP/IP stack. The ibmMvsDVIPAOrigin value indicates the reason why the DVIPA was originally defined. The instance value for the trap objects will contain the affected DVIPA IP address.

This trap is generated when a dynamic VIPA is removed from a TCP/Id stack. The ibmMvsDVIPAOrigin value indicates the reason why the DVIPA was previously defined. The ibmMvsDVIPAStatus object reflects the status before DVIPA was removed. The instance value for the trap objects will contain the affected DVIPA IP address.

This trap is generated by a Sysplex Distributor stack when it determines that a designated target stack is active. Stacks are designated as target stacks on the VIPADISTRIBUTE Profile statement. The instance value for the ibmMvsDVIPADistConfStatus object will indicate the affected DVIPA IP address, the distributed port, and the target stack's dynamic XCF IP address.

This trap is generated by a Sysplex Distributor stack when an active target stack is removed from distribution. This can occur when a VIPADISTRIBUTE DELETE Profile statement is processed, or the target stack ends. The instance value for the ibmMvsDVIPADistConfStatus object will indicate the affected DVIPA IP address, the distributed port, and the dynamic XCF IP address of the target stack that is removed from distribution. if the ALL parameter was specified on the VIPADISTRIBUTE DELETE statement, the target stack's IP address type will be unknown (0) and its IP address will be a zero-length string.

This trap is generated by a Sysplex Distributor stack when it receives notification from a target stack that a server has become active on a distributed port. The instance value for the ibmMvsDVIPADistPortReadyCount object will indicate the affected DVIPA IP address, the distributed port, and the target stack's dynamic XCF IP address.

This trap is generated by a Sysplex Distributor stack when it receives notification from a target stack that a server has ended on a distributed port. The instance value for the ibmMvsDVIPADistPortReadyCount object will indicate the affected DVIPA IP address, the distributed port, and the target stack's dynamic XCF IP address.

This trap is generated by the TCP/IP Subagent. It signifies that the Subagent, acting in a subagent role, has reinitialized itself and that its configuration may have been altered.

Defines the a remote ping table in order to use the various parameters as indeces into the table.

Defines an entry in the ibmRemotePingTable. This table does not actual exist, but is used to faciliate passing the remote ping parameters.

Specifies the packet size in octets of the PING request. Valid values for packet size are 0 or from 16 to 4096.

Specifies the time-out value, in seconds, for the actual PING request made by the remote host. Valid values for time out are 0 or 3 to 15 seconds.

Specifies the host address used on by PING request by the remote host. The host address specified is required to be an ipAddress.

The result of the PING request made by the remote host: >0 Round-trip response time in milliseconds. -1 Internal error. -2 ICMP echo request timed out. -4 Incorrect packet size. -5 Incorrect Time-out. -6 Unknown destination address. -7 Incorrect MIB instance format. The generic noSuchInstance SNMP error could also occur if the instance specified is incorrect.

Specifies the amount of time to wait for re-retrieval of specific MIB data from target. A value of 0 implies that every GET or GET-NEXT request should result in the re-retrieval of the needed data. Maximum amount of time to cache is 1 hour (3600 seconds).

IP Layer attribute, default of process redirects. current stack: IGNOREREDIRECT parm on ASSORTEDPARMS statement Enumeration: 'process': 0, 'ignore': 1.

IF Layer attribute. ARP cache timeout - ARPAGE statement; default= 1200 seconds; 60 <= ARPAGE <= 86400 (24 hours). current stack: ARPAGE statement; default= 20 minutes (1200 seconds). The value of this object is expressed in seconds.

TCP Keepalive timer, expressed in minutes. A value of 0 deactivates the timer.

TCP Receive buffer size, expressed in bytes.

TCP Send buffer size, expressed in bytes.

UDP checksum - on or off Enumeration: 'on': 1, 'off': 0.

The date and time that this TCP/IP instance was started. sysUpTime provides the time from when the SNMP Agent was started, not corresponding TCP/IP instance.

Indicates if the UDP queue limit of 163,840 bytes of UDP data per socket is in effect or not. 163,840 is equal to 8K times 20 datagrams. This limit is based on the total number of bytes, not datagrams. Enumeration: 'noQueueLimit': 1, 'queueLimit': 0.

Maximum number of socket connections.

MVS Procname of this TCP/IP instance.

MVS Address Space ID of this TCP/IP instance.

Indicates if set to true(1) that SOURCEVIPA support is enabled. This object can be changed via the ASSORTEDPARMS TCP/IP Profile statement. Enumeration: 'true': 1, 'false': 0.

Sysplex name, if unknown the value of the zero length string

OSASF Host Name, if unknown the value of the zero length string

version/release of product, if unknown the value of the zero length string

The ifIndex of the designated primary interface. A value of zero implies that this option wasn't configured.

The maximum ip reassembly size in units of octets.

Indicates if TCP low ports are restricted to authorized servers/socket applications. Enumeration: 'true': 1, 'false': 0.

Indicates if UDP low ports are restricted to authorized servers/socket applications. Enumeration: 'true': 1, 'false': 0.

The default UDP send buffer size.

The default UDP receive buffer size.

Indicates if set to true(1) that the generation of tcp/ip statistics is enabled. Statistics if enabled will be recorded at the SMF interval via SMF record subtype 5. Enumeration: 'true': 1, 'false': 0.

Indicates if set to true(1) that firewall support is enabled. This object can be changed via the IPCONFIG TCP/IP Profile statement. Enumeration: 'true': 1, 'false': 0.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of 100th of a second.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of 100th of a second.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of .0001.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of .0001.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of .0001.

If true(1) indicates that the TCP option SENDGARBAGE is enabled. Enumeration: 'true': 1, 'false': 0.

TCP Maximum Receive buffer size, expressed in bytes.

If true(1) indicates that the MULTIPATH IP option is enabled. If false(2) indicates that the MULTIPATH IP option is disabled. This object is obsolete. It has been replaced by the ibmMvsMultipathType object.

If true(1) indicates that the PATHMTUDISCOVERY IP option is enabled. If false(2) indicates that the PATHMTUDISCOVERY IP option is disabled.

The type of Multipath processing currently active. The types are defined under the MULTIPATH parameter on the IPCONFIG Profile statement. Enumeration: 'perconnection': 2, 'perpacket': 3, 'nomultipath': 0.

The indication of whether this entity is acting as an IP router in respect to the forwarding of datagrams received by, but not addressed to, this entity. If this entity is acting as a router, this object also indicates what type of forwarding is in effect. The value of this object is originally determined by the TCP/IP Profile ASSORTEDPARMS or IPCONFIG statements. A value of notForwarding(1) indicates that this entity is not forwarding datagrams. A value of forwardingNoMultipath(2) indicates that this entity is forwarding datagrams using the first available route. A value of forwardingMultipathPkt(3) indicates that this entity, when forwarding datagrams, will select a route on a round-robin basis from a multipath routing list. This object is related to the ipForwarding object from RFC2011. If ipForwarding is set to notForwarding, this object will also be set to notForwarding. If ipForwarding is set to forwarding, this object will be set to forwardingNoMultipath. If the value of this MIB object is changed, the value of ipForwarding will be changed accordingly. Enumeration: 'notForwarding': 1, 'forwardingMultipathPkt': 3, 'forwardingNoMultipath': 2.

Specifies the duration of the retry period for a failed device. TCP/IP will perform reactivation attempts at 30 second intervals during this retry period. The default duration is 90 seconds. A specification of 0 generates an infinite recovery period, meaning reactivation attempts will be performed until the device is either successfully reactivated, or manually stopped. The value of this object is originally determined by the DEVRETRYDURATION parameter on the IPCONFIG Profile statement.

The number of seconds a TCP connection should remain in the FINWAIT2 state. When this timer expires, it is reset to 75 seconds. When it expires a second time the connection is dropped.

If true(1), indicates that the TCPTIMESTAMP option was specified (or defaulted to) on the TCPCONFIG Profile statement. For active connections (TCP/IP initiates the connection) a TCP timestamp option will be sent. For passive connections (TCP/IP receives a connect request) TCP/IP will send a SYN-ACK with its own TCP timestamp option. If false(2), indicates that the NOTCPTIMESTAMP option was specified on the TCPCONFIG Profile statement. TCP/IP will not participate in TCP timestamp negotiations during connection setup or at any future time in the life of the connection.

The version/release of the TCP/IP Subagent. The actual product names associated with the values of this object are: v1r2(1) - z/OS V1R2 Communications Server Enumeration: 'v1r2': 1.

Defines the device definition known to an IBM MVS TCP/IP system. A virtual interface entry exists for every entry in this table.

Descibes a particular device definition

Indicates the device type.

If this entry is for a CTC, HCH or Vipa device then this object represents its base device number. For an LCS device this object represents the lcs address. For a CLAW device this object represents the device number of the RS/6000 device. For a CDLC device this object represents the device number. A value of 0 implies that this object is not valid for the associated device table entry.

The I/O buffersize attribute for this device definition. This is only value for a CTC Device. A reported value of -1 implies that the corresponding device doesn't not support this attribute.

A value of true indicates that this device was defined as autorestartable. False indicates that it was not. Enumeration: 'true': 1, 'false': 0.

A value of 1 indicates that this is an LCS device that was defined to support the 3172 ICP MIB. A value of 0 indicates that this is an LCS device that was not defined to support the 3172 ICP MIB. A reported value of -1 implies that this object is invalid for the corresponding device table entry.

A non NULL OCTET STRING implies that this is the Host Claw Name for a CLAW Device definition.

A non NULL OCTET STRING implies that this is the Workstation Claw name for a CLAW Device definition.

The number of read buffers for either a CLAW RS/6000 IP or a CDLC device definition. A value of -1 implies that the value of this object is invalid.

The read buffer size for either a CLAW RS/6000 IP or a CDLC device definition. A value of -1 implies that the value of this object is invalid.

The number of write buffers for either a CLAW RS/6000 IP or a CDLC device definition. A value of -1 implies that the value of this object is invalid.

The write buffer size for either a CLAW RS/6000 IP or a CDLC device definition. A value of -1 implies that the value of this object is invalid.

A non NULL OCTET STRING implies that this is the procname for an X25NPSI, SNA LU0, or SNA LU6.2 Device definition.

This object is valid only for an ATM Device. If true then incoming SVCs will be allowed. A value of false for an ATM Device implies that incoming SVC call setup will be rejected. Enumeration: 'true': 1, 'false': 0.

A non NULL OCTET STRING implies that this is the Logical Unit name for a SNA LU0 Device definition.

This object is valid only for an MPCIPA device and reflects the specified or default parameter from the MPCIPA DEVICE Profile statement. For other devices the value will be set to -1. A value of 0 represents the NONROUTER parameter on the MPCIPA DEVICE profile statement. It indicates that the device will discard any packets received for an unknown IP address. A value of 1 represents the PRIROUTER parameter on the MPCIPA DEVICE profile statement. It indicates that the device will route inbound packets destined for an unknown IP address to this TCP/IP instance. A value of 2 represents the SECROUTER parameter on the MPCIPA DEVICE profile statement. It is similar to a value of 1 but the device will only route the packet to this TCP/IP instance if there is no TCP/IP instance registered as primary router.

This object is valid only for an MPCIPA device and is determined when the device is started. For other devices the value will be set to -1. When the device is started, the TCP/IP instance tries to set the router status to the value of the ibmMvsDeviceRouterStatus MIB object. The ibmMvsDeviceActualRouterStatus MIB object reflects the status that was sucessfully set. A value of 0 represents the NONROUTER parameter from the MPCIPA DEVICE profile statement. It indicates the device will discard any inbound packets destined for an unknown IP address. A value of 1 represents the PRIROUTER parameter from the MPCIPA DEVICE profile statement. It indicates that the device will route inbound packets destined for an unknown IP address to this TCP/IP instance. A value of 2 represents the SECROUTER parameter from the MPCIPA DEVICE profile statement. It is similar to a value of 1 but the device will only route the packet to this TCP/IP instance if there is no TCP/IP instance registered as primary router. If the MPCIPA device has not yet been started, the value will be 3, which means the router status of the device is unknown.

This object is valid only for a CLAW device and is specified on the CLAW Device definition. For other devices the value will be set to -1. A value of 1 implies that the PACKED parameter was not specified on the CLAW DEVICE Profile statement. A value of 2 implies that that the PACKED parameter was specified on the CLAW DEVICE Profile statement.

This object is valid only for a CLAW device and is determined when the device is started. For other devices the value will be set to -1. A value of 1 implies that the router for the device does not support packing mode. A value of 2 implies that the router for the device does support packing mode. If the CLAW device has not yet been started, the value will be 3, which means the packing support of the router is unknown.

Defines the link definition known to an IBM MVS TCP/IP system. A physical interface entry exists for every entry in this table.

Descibes a particular link definition

Indicates the link type.

ifIndex of corresponding DEVICE entry.

The adapter address associated with this link definition. A value of -1 indicates that this object is invalid for the corresponding link table entry.

The link number associated with this link definition. A value of -1 indicates that this object is invalid for the corresponding link table entry.

For an IBMTR LCS Link, a value of 1 implies that this link was defined with a value of CANONICAL. A value of 0 implies this link was defined with a value of NONCANONICAL. A reported value of -1 implies that the object is not supported by the associated link.

For a IBMTR LCS Link, a value of 1 implies that this link was defined with a value of ALLRINGSBCAST. A value of 2 implies this link was defined with a value of LOCALBCAST. A value of 0 implies that the link does not support broadcast. A reported value of -1 implies that the object is not supported by the associated link.

A value of true(1) indicates that the link is capable of receiving multicast datagrams. A value of false(2) indicates that either the link is not capable of receiving multicast datagrams or, the multicast capability of the link is unknown. Point-to-point links are always multicast capable. For Token Ring, Ethernet, and FDDI, the multicast capability of the link will not be known until after the link is successfully started. Multicast is not supported for ATM links.

The value of this object can vary only for MPCPTP LINK interfaces. For all other LINK interfaces the value is set to true(1). A value of true(1) indicates that an inbound checksum calculation will be performed for all packets received on this interface. A value of false(2) indicates that an inbound checksum calculation will not be performed for any packets received on this interface.

This object reflects the status of the interface's ARP support. A value of 'none' indicates that the interface does not support ARP. If the interface supports ARP but the interface is inactive, then the object will be set to a value of 'unknown'. If the interface is active and supports ARP, the object will be set to one of remaining values. A value of 'tcpipArp' indicates that the TCP/IP instance maintains the ARP cache entries and ARP counters for the interface. A value of 'offloadNoInfo' indicates that the interface maintains its ARP cache entries and ARP counters and the TCP/IP instance can not retrieve this information. A value of 'offloadArpInfo' indicates that the interface maintains its ARP cache entries and ARP counters but supports retrieval of this information by the TCP/IP instance. If the value of the MIB object is 'offloadArpInfo', then the ARP cache entries and ARP counters retrieved represent aggregated information and may reflect shared usage of the interface by more than one TCP/IP instance. Enumeration: 'offloadArpInfo': 4, 'unknown': 5, 'none': 1, 'tcpipArp': 2, 'offloadNoInfo': 3.

A 6 byte OCTET STRING which contains the configured MAC address for IPAQTR link interfaces. If the MAC address was not specified, or if the interface is not an IPAQTR link, then the value will be zeros.

The table listing those multicast groups for which an application wishes to receive multicast data. An application requests this by issuing a setsockopt() with IP_ADD_MEMBERSHIP option. An entry exists for every multicast group registered per interface.

An entry representing a multicast group on an interface.

Specifies the ipAddress of the multicast group

A count of the number of sockets that are members of this multicast group.

Reserved ports within a TCP/IP address space.

Defines a single ibmTcpipMvsPortTable entry.

Low port number of entry.

High port number of entry.

The protocol of the associating port entry. Enumeration: 'udp': 1, 'tcp': 0.

Text Name of the associating mvs procedure.

Should proc be autologged. Enumeration: 'true': 1, 'false': 0.

A value of true implies that DELAYACKS was selected for this port entry. Enumeration: 'true': 1, 'false': 0.

A value of true implies that the Optimal Maximum Segment Size option was selected for this port entry. Enumeration: 'true': 1, 'false': 0.

A value of true implies that SHAREPORT was selected for this port entry. Enumeration: 'true': 1, 'false': 0.

The IP address specified on the BIND parameter of the PORT Profile statement. If an application issues a bind() with an IP address of zeros (INADDR_ANY), the value of this MIB object will be used to replace the zero IP address. A value of 0.0.0.0 indicates that the BIND parameter was not specified for this PORT.

The SAF resource name specified on the SAF parameter of the PORT Profile statement. The value of this MIB object is appended to a security product profile name of the format: EZB.PORTACCESS.sysname.tcpname., where 'sysname' is the MVS image name, and 'tcpname' is the TCP/IP instance name. During bind() processing the security product will be invoked to verify that the user ID associated with the application has authority to the resulting security product profile name. A value of NULL indicates that the SAF parameter was not specified for this PORT.

This object only applies to TCP port entries. A value of true(1) means that the port is reusable, as if the SO_REUSEADDR socket option had been set in a socket using the port. A value of true will be set for the port if the BIND paramter was also specified on this port reservation, or if the BIND parameter was specified on another port reservation for the same port number. For UDP port entries, this value will always be false(2).

Extends ipForwardTable to support gateway semantic.

Descibes a particular gateway entry

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of 100th of a second.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of 100th of a second.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of .0001.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of .0001.

Used in the TCP/IP re-transmission time-out calculation to determine how long to wait for an acknowledgement before resending a packet. Expressed as a integer in units of .0001.

Delays transmission of acknowledgements when a packet is received with the PUSH bit on in the TCP header. The DELAYACKS parameter on the GATEWAY statement only applies to the TCP protocol and only affects acknowledgements returned to the foreign host. To delay acknowledgements on a TCP/IP port connection use the DELAYACKS parameter on the PORT statement. Enumeration: 'true': 1, 'false': 0.

Indexed by ifIndex. One entry in this table will exist per OSA-2 ATM Device Interface. If the values for objects ibmMvsAtmOsasfChannelCurLparName/Num are not the same as values for objects ibmMvsAtmOsasfChannelManParnName/Num then the OSA/SF running in the current LPAR is not the managing OSA/SF for this Device. SNMP Set commands for ibmMvsAtmOsasfPortIpAddress (to set an IP address at the ATM port) will be rejected by OSA/SF if the OSA/SF in the current LPAR is not the managing OSA/SF for the Device.

Definition of a single entry in the osasfChannelTable. Indexed by the ifIndex of the corresponding DEVICE interface.

The channel number for this interface

The value will be osa(18) for ATM OSA-2 adapters. The values of osaExp155(16) and osaExp155QDIO(17) apply only to OSA-Express ATM155 adapters. Since the channel management data for OSA-Express ATM155 adapters has moved to the osaexpChannelTable, these values will never be set for this MIB object. The value should never be other(1) for an OSA ATM adapter. Enumeration: 'osa': 18, 'osaExp155': 16, 'other': 1, 'osaExp155QDIO': 17.

Indicates how the channel is configured. The value is one of the following: -1 - Invalid 0 - Unknown 1 - Ethernet 2 - Token Ring 3 - Two Token Ring ports 4 - Token Ring and Ethernet ports 5 - Ethernet and Token Ring ports 6 - Two Ethernet ports 7 - FDDI 8 - No ports defined 9 - ATM Native or IP Forwarding 10 - One Logical Ethernet port 11 - One Logical Token Ring port 12 - ATM LAN Emulation A value of 12 applies only to OSA-Express ATM155 adapters. Since the channel management data for OSA-Express ATM155 adapters has moved to the osaexpChannelTable, this value will never be set for this MIB object. A value of -1 should not occur for this object.

Config mode of the ATM adapter. Enumeration: 'snaMode': 3, 'atmLeTcpipMode': 4, 'atmLeSnaTcpipMode': 6, 'atmNativeMode': 7, 'other': 1, 'passthruMode': 2, 'atmIpFwdMode': 8, 'atmLeSnaMode': 5.

Hardware model of the channel. The field NDModelNum contained in ibmMvsAtmOsasfChannelDeterNodeDesc is a char(3) field that contains a readable format of this object's value. The value of osaExp155(4) applies only to OSA-Express ATM155 adapters. Since the channel management data for OSA-Express ATM155 adapters has moved to the osaexpChannelTable, this value will never be set for this MIB object. Enumeration: 'osaExp155': 4, 'osa1': 1, 'undefined': 0, 'osa2Atm': 3, 'osa2': 2.

Hardware channel state: online, offline, or not installed. Enumeration: 'notinst': 3, 'offline': 5, 'online': 1.

An OSA Channel can be shared across multiple LPARs. This object indicates if this channel is currently being shared. Enumeration: 'yes': 1, 'no': 0.

Number of physical ports on OSA channel.

Describes the generic node descriptor layout. This object represents the ND obtained from the CHSC instruction: /* ND Flags */ int bValidity :3; /* 1:is ND valid */ int bNodeType :1; /* 1:0=dev,1=chnlsubstm nod*/ int bInternal :1; /* internal(1)/external(0) */ int bCHPinvalid :1; /* IF =1,NDCHPID is invalid*/ int bNDRsvd1 :2; /* spare bits for alignment*/ char NDRsvd1; /* reserved by architecture*/ char NDClass; /* Class for subsystem node*/ char NDCHPID; /* CHP ID for specified int*/ char NDTypeNum 6 ; /* type number of the SDC */ char NDModelNum 3 ; /* ND model number in the form of 3 EBCDIC OCTETS */ char NDMfgr 3 ; /* ND manufacturer in the form of 3 EBCDIC OCTETS */ char NDMfgrPlant 2 ; /* ND plant of manufacture (2 EBCDIC OCTETS) */ char NDSeqNum 12 ; /* ND sequence number (12 EBCDIC OCTETS) */ char NDTag 2 ; /* ND tag */

The control unit number associated with the OSA Channel.

ibmMvsAtmOsasfChannelCodeLevel is the firmware (or micro code level) of the OSA adapter. For example, ATM OSA-2 adapter level 05.60 would be represented as 0x0560 by this object.

The Box EC Level Identifier of the OSA adapter which identifies the current Engineering Change (EC) Level of this OSA adapter (Channel).

LPAR name of the OSA/SF from which this data was retrieved from

LPAR number of the OSA/SF from which this data was retrieved

LPAR name of the OSA Support Facility managing this channel. Only one OSA/SF can manage a OSA Channel within an MVS Sysplex even though multiple OSA/SFs can retrieve information from the same OSA Channel.

LPAR number of the OSA Support Facility managing this channel (set to 0xFFFF if not being managed by a OSA/SF).

Date on this channel (set to 'NOTVALID' if there the disk serving function is not active).

Time on this channel (set to 'NOTVALID' if there the disk serving function is not active).

Flashlevel is the LAN driver level running on an OSA adapter. For OSA-1 and OSA-2, there is only 1 LAN driver. For OSA-2 ATM, you can have up to 2 LAN driver. The first driver if configured is for SNA and the second driver is for ATM LAN. FlashLevel consists of two 16 OCTET fields, one for each LAN driver. FOR example, S:05:20:A0 for SNA & A:05.60.00 for ATM. This object is not supported for OSA-Express ATM adapters, so the value will be null.

VTAM ID if in SNA mode

This table is intended to represent the ports supported (or associated) with the osasfChannelTable entries and, for OSA-Express ATM155 adapters, with the osaexpChannelTable entries. Each OSA channel has one or more OSA Ports. For an ATM OSA-2 device configured for ATM IP Forwarding mode, the following fields do not apply: - ibmMvsAtmOsasfPortMacAddrBurntIn - ibmMvsAtmOsasfPortMacAddrActive - ibmMvsAtmOsasfPortMaxPcmConnections - ibmMvsAtmOsasfPortPcmName

Describes a particular OSA port entry, index by corresponding AAL5 entry's ifIndex.

Port number, starts at 0.

For an ATM OSA-2 adapter configured for ATM native traffic, the value of this object is atm(9). For an ATM OSA-2 adapter configured for ATM LAN Emulation, the value is either ethernet(1) or tokenRing(2) and represents the configuration of the first logical port on the adapter. For an OSA-Express ATM155 adapter the value is osaExp155(41). Note that when a port is configured to be running ATM LAN Emulation then up to two logical ATM LE port entities may exist with any combination of ethernet or tokenring port types. Enumeration: 'tokenRing': 2, 'ethernet': 1, 'osaExp155': 41, 'atm': 9.

The hardware state value ranges from 0 to 6 as follows: 0 - enable 1 - disabled from host 2 - disabled from external source 3 - disabled from internal error 4 - service element control mode/disabled from host 5 - service element control mode/disabled from external source 6 - service element control mode/disabled from internal error 7 - link not operational because ATM155 adapter was unable to register with the switch (only valid for ATM155) where Host - OSA/SF or other host programming product external source - human intervention on the service element Enumeration: 'internallyDisabled': 3, 'secmInternallyDisabled': 6, 'enabled': 0, 'externallyDisabled': 2, 'secmExternallyDisabled': 5, 'hostDisabled': 1, 'secmHostDisabled': 4, 'linkMonitor': 7.

ILMI atmfPortMediaType equivalent. OSA supports types 2 and 3 Enumeration: 'coaxCable': 1, 'multimodeFiber': 3, 'unshieldedTwistedPair': 5, 'singleModeFiber': 2, 'shieldedTwistedPair': 4.

ILMI atmfAtmLayerUniType. OSA supports only 2 Enumeration: 'public': 1, 'private': 2.

ILMI atmfAtmLayerUniVersion. OSA supports only 3. This is the highest UNI version supported. Enumeration: 'version20': 1, 'version30': 2, 'version31': 3.

A unique value which identifies the UNI port for which the network prefix for ATM addresses is in effect. The value of 0 has the special meaning of identifying the local UNI. OSA currently supports only 0.

The network prefix for ATM addresses which is in effect on the user-side of the ATM UNIT port. Network prefix is defined as the ATM address, not including the ESA and SEL portions. The meaningful portion of the OCTET STRING is size 8 if it is E.164, 13 if private. In the case of E.164 the remaining 5 octets are padded with zeros.

Equivalent to the atmfNetPrefixStatus as defined in the Network Prefix Table in the ILMI Address Registration MIB. An indication of the validity of the network prefix for ATM addresses on the user-side of the UNI port. Enumeration: 'valid': 1, 'invalid': 2.

This object specifies whether the ATM code has been loaded on to the adapter. The configRejected state indicates that the ATM configuration file download via OSA/SF has been found to be incorrect. The outOfSync condition indicates that the OSA firmware and the ATM code both running on the OSA have been found to be at incompatible levels. Any state other than operational infers that the data associated with a port may be incorrect. Note: OSA/SF should only report states operational and notOperational. This object is only valid for ATM OSA-2 adapters. For other ATM adapters the value is notApplicable. Enumeration: 'notApplicable': 5, 'configRejected': 3, 'notOperational': 2, 'outOfSync': 4, 'operational': 1.

A 6 byte OCTET STRING which contains the adapter's burned in MAC address. Does not apply to ATM OSA-2 device configured for ATM IP Forwarding mode.

A 6 byte OCTET STRING which contains the current MAC address in use on the adapter. Does not apply to ATM OSA-2 device configured for ATM IP Forwarding mode.

Specifies the maximum number of connects on an OSA port which can be used for ATM exploitation purposes. It can range from 0 to the number specified by atmInterfaceMaxVccs (RFC 1695). A 0 indicates either that the connections on this port are being used by an ATM configured for LAN Emulation or ATM IP Forwarding. If the value specified here is the same as what is specified by atmInterfaceMaxVccs then all connections are allocated to ATM exploitation.

Specifies the Port Name which must also be entered at the connection manager on the host and the application. Port Name is specifed to OSA/SF as a config file parameter (PCM_NAME). This value is also specified via ILMI as the value of the atmfPortMyIfName object. Does not apply to an ATM OSA-2 adapter configured for ATM IP Forwarding mode, or an OSA-Express ATM155 adapter configured for QDIO LAN Emulation mode.

inbound packets at the corresponding AAL5 interface layer.

outbound packets at the corresponding AAL5 interface layer.

The managing IpAddress reported by the ATM port as its atmfMyIpNmAddress as specified by the ATM Forum User-NetworkInterface (UNI) specification. An SNMP Set for this object is only supported for OSA-2 ATM adapters. If the values for objects ibmMvsAtmOsasfChannelCurLparName/Num are not the same as values for objects ibmMvsAtmOsasfChannelManParnName/Num then the OSA/SF running in the current LPAR is not the managing OSA/SF for this adapter. SNMP Set commands for ibmMvsAtmOsasfPortIpAddress (to set an IP address at the ATM port) will be rejected by OSA/SF if the OSA/SF in the current LPAR is not the managing OSA/SF for the adapter.

This table is intended to represent the locally configured PVCs associated with a given OSA Port. There is a limit of 128 PVCs per Port per Channel.

This object is intended to represent a single PVC entry for the osasfPvcTable.

PVC Name

Best Effort rate. 0 indicated that best effort delivery is not desired. 1 indicates that best effort delivery is desired.

Forward peak cell rate specified as cells per second. Needed in order to set up either a best effort or a reserved bandwidth PVC. It applies to the outbound direction (OSA to network) and specifies an upper bound on the outbound traffic that can be transmitted on this PVC. This value can not exceed the the link speed of the ATM link which, currently, is 353207.

Backward peak cell rate specified as cells per second. Needed in order to set up either a best effort or a reserved bandwidth PVC. It applies to the inbound direction (network to OSA) and specifies an upper bound on the inbound traffic that can be received on this PVC. This value can not exceed the the link speed of the ATM link which, currently, is 353207.

Forward sustain cell rate specified as cells per second. If the best effort indicator is on, the value of this object is ignored. Otherwise (for a reserved bandwidth PVC) this value is utilized by OSA. A value of 0xFF indicates that this value is not being used. Forward sustain cell rate specifies the desired cell rate for outbound traffic that can be sustained for life of a connection on this PVC. This value can not exceed the link speed of the ATM port which, currently, is 353207.

Backward sustain cell rate specified as cells per second. If the best effort indicator is on, the value of this object is ignored. Otherwise (for a reserved bandwidth PVC) this value is utilized by OSA. A value of 0xFF indicates that this value is not being used. Backward sustain cell rate specifies the desired cell rate for inbound traffic that can be sustained for life of a connection on this PVC. This value can not exceed the link speed of the ATM port which, currently, is 353207.

Forward cell burst size specified as number of cells. If the best effort indicator is on, the value of this object is ignored. Otherwise (for a reserved bandwidth PVC) this value is utilized by OSA. A value of 0xFF indicates that this value is not being used. Forward cell burst size specifies the maximum number of cells that can be transmitted in the outbound direction at the peak cell rate while maintaining conformance to the PVC traffic contract.

Backward cell burst size specified as number of cells. If the best effort indicator is on, the value of this object is ignored. Otherwise (for a reserved bandwidth PVC) this value is utilized by OSA. A value of 0xFF indicates that this value is not being used. Backward cell burst size specifies the maximum number of cells that can be received in the inbound direction at the peak cell rate while maintaining conformance to the PVC traffic contract.

vpi for this PVC

vci for this PVC. This value must be greater than or equal to 32 since the first 32 vci code points have been reserved by the ATM Forum.

This field is used to setup the PVC. Units are in OCTETs and represents the largest PDU size for the AAL5 CPCS layer that can be processed in the forward direction for this PVC by the AAL5 entity. For best effort PVCs only, OSA/SF should attempt to default the value to the largest size (9188).

This field is used to setup the PVC. Units are in OCTETs and represents the largest PDU size for the AAL5 CPCS layer that can be processed in the backward direction for this PVC by the AAL5 entity. For best effort PVCs only, OSA/SF should attempt to default the value to the largest size (9188).

This table is intended to represent the data that is available from an OSA Port that is running SNA LAN Emulation mode. An entry in this table is indexed by a LAN Emulation ifIndex. An ifEntry who's ifType is either aflane802.3 (59) or aflane802.5 (60) will have a corresponding entry in this table.

Describes a particular OSA SNA LAN Emulation entry, index by corresponding LAN Emulation ifIndex.

The inactivity timer. An enabled inactivity timer (Ti) periodically tests the viability of the network media. The timer setting applies to all the clients on the target LAN, not to individual clients. The timer interval indicates how quickly a failure of the network media can be detected when the connection is quiescent. If the Ti timer times out, a supervisory poll frame is sent over the connection. The T1 response, or reply, timer clocks the supervisory poll. If the T1 timer times out, the supervisory poll is retransmitted. OSA can retransmit a supervisory poll up to 8 times. If no response is received after the last retransmission, the link is declared inoperative, and the S/390 program issues a message. The value is represented in ticks. The value will either be zero, or in the range of 2 to 750. Each tick equals .12 of a second.

The response timer. The T1 timer clocks link events that require responses from clients on the network. These link events include SABME/UA exchanges, I-frame link protocol data unit (LPDU) transmissions, and supervisory polls. The value is represented in ticks. Each tick equals .2 of a second.

The acknowledgement timer. An OSA starts the T2 timer when it receives an I-format LPDU and stops when it sends an acknowledgement. An acknowledgement is sent either when an outgoing I frame is sent, which acts as the acknowledgement, or when N3 number of I-format LPDUs has been received. If the T2 timer times out, the OSA must send an acknowledgement. The value is represented in ticks. Each tick equals .08 of a second.

The maximum number of connections (PUs) supported by an OSA for this port. This object is not supported for OSA-Express ATM so the value will be set to zero.

The maximum number of service access points (SAP) supported by an OSA for this for this port. This object is not supported for OSA-Express ATM so the value will be set to zero.

Maximum I frames before ACK (N3). The maximum number of I-format link protocol data units (LPDUs) that can be received by an OSA before it sends an acknowledgement (N3 count). It is also called the receive window count.

SNA maximum transmit window (TW). The maximum number of outstanding I-format link protocol data units (LPDUs). It is also called the maximum transmit window count or the maximum window out count. The TW count allows the sender to transmit frames before that sender is forced to halt and wait for an acknowledgement. Therefore, the receiver should be able to absorb that number of frames, either in its service access point (SAP) buffers or within the buffers in workstation memory.

This field contains the active Group Addresses. An individual Group Address is 6 bytes long. Therefore, this field is actually 32 times (OCTET STRING(SIZE(6)) + 2 bytes of padding) long.

This field contains a character string of user data that can be used to further describe this port.

This object describes the state of the specified LAN Emulation Port. notDefined implies that the port is not defined in the configuration file. lecActivating indicates the port is in the process of being enabled. There are for possible reasons that the port could be diabled as implied by the enumeration list. Enumeration: 'internalFailureDisabled': 4, 'unknown': 8, 'enabled': 3, 'physicalPortDisabled': 5, 'osasfDisabled': 6, 'notDefined': 1, 'lecActivating': 2, 'externalDisabled': 7.

This object is the signaling parameter that should be used by the LEC when setting up all best effort VCCs. This parameter applies to the forward and backward direction on a per best effort VCC basis. Thus a 155 Mb adapter may be configured to send best effort traffic at 25.6 Mb (per VCC), but with a total adapter bandwidth of up to 155 Mb. Since this parameter has an integer value the unis are 10xMbits/sec.

This object specifies the maximum number of connections on an OSA port which can be used for LAN Emulation purposes. It can range from 0 to the number specified by atmInterfaceMaxVccs. 0 would indicate that the connections on this port are only being used by ATM Exploitation. If the value of this parameter was equal to atmInterfaceMaxVccs then all connections are allocated to LAN Emulation. Note that this number is the same for all LECs. It is NOT defined on a per LEC basis.

Load balancing control used to enable the load balancing option.

Load balancing factor. Specifies whether this port will be delayed and, if so, by how much time, in establishing a session. This factor is related to the number of connections (PUs) through the OSA port, not the type nor the amount of work that is being done on those connections.

Session delay is specified to delay the response of this port to a new session request and by the specified length of time. By establishing a longer session delay timeout for this port copmpared with another port in the same set, this port serves as a backup for another port in an overflow condition.

This table is intended to represent the data that is available from an OSA Port that is running LAN Emulation mode. An entry in this table is indexed by a LAN Emulation ifIndex. An ifEntry who's ifType is either aflane802.3 (59) or aflane802.5 (60) will have a corresponding entry in this table. This table is modeled after the LEC Config Table from the LAN Emulation MIB defined by the ATM Forum.

Describes a particular ATM Lec Config Table entry, index by either a aflan802.3 or a aflane802.5 ifEntry's ifIndex.

Indicates whether this LAN Emulation Client should auto-configure the next time it is (re)started. In automatic (1) mode, a client uses a LAN Emulation Configuration Server to learn the ATM address of its LAN Emulation Server, and to obtain other parameters. lecConfig (LanType, MaxDataFrameSize, LanName) are used in the configure request. lecConfigLesAtmAddress is ignored. In manual (2) mode, management tells the client the ATM address of its LAN Emulation Server and the value of the other parmeters. lecConfig (LanType, MaxDataFrameSize, LanName) are used in the Join request. lecConfigLesAtmAddress tells the client which LES to call. Enumeration: 'manual': 2, 'automatic': 1.

The data frame format which this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their configure requests. Manually configured clients use it in their joint requests. Enumeration: 'tokenRing': 3, 'ethernet': 2, 'unspecified': 1.

The maximum data frame size (in bytes) which this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their configure requests. Manually configured clients use it in their joint requests. Enumeration: 'f4544': 3, 'f18190': 5, 'f1516': 2, 'unspecified': 1, 'f9234': 4.

The ELAN Name this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their configure requests. Manually configured clients use it in their joint requests.

The LAN Emulation Server which this client will use the next time it is started in manual configuration mode. When lecConfigMode is 'automatic', there is no need to set this address, Address) and no advantage to doing so. The client will use the LECS to find a LES, putting the auto-configured address in lecActualLesAtmAddress while leaving lecConfigLesAtmAddress alone. Corresponds to Initial State Parameter C9. In LAN Emulation MIB, the OCTET STRING has length 0 or 20. For OSA, the length shall be 20, with the value 0 defined to mean that lecConfigMode is 'automatic'.

Control Time-out. Time out period used for timing out most request/response control frame interactions, as specified elsewhere in the LAN Emulation specification. This time value is expressed in seconds. Corresponds to Initial State Parameter C7.

Maximum Unknown Frame Count. See the description of lecMaxUnknownFrameTime below. Corresponds to Initial State Parameter C10.

Maximum Unknown Frame Time. Within the period of time defined by the Maximum Unknown Frame Time, a LE Client will send no more than Maximum Unknown Frame Count frames to the BUS for a given unicast LAN Destination, and it must also initiate the address resolution protocol to resolve that LAN Destination. This time value is expressed in seconds. Corresponds Initial State Parameter C11.

VCC Time-out Period. A LE Client SHOULD release any Data Direct VCC that it has not used to transmit or receive any data frames for the length of the VCC Time-out Period. This parameter is only meaningful for SVC Data Direct VCCs. This time value is expressed in seconds. The default value is 20 minutes. A value of 0 seconds means that the timeout period is infinite. Negative values will be rejected by the agent. Corresponds to Initial State Parameter C12.

Maximum Retry Count. A LE CLient MUST not retry a LE_ARP_REQUEST for a given frame's LAN destination more than Maximum Retry Count times, after the first LE_ARP_REQUEST for that same frame's LAN destination. Corresponds to Initial State Parameter C13.

Aging Time. The maximum time that a LE Client will maintain an entry in its LE_ARP cache in the absence of a verification of that relationship. This time value is expressed in seconds. Corresponds to Initial State Parameter C17.

Forward Delay Time. The maximum time that a LE Client will maintain an entry for a non-local MAC address in its LE_ARP cache in the absence of a verification of that relationship, as long as the Topology Change flag C19 is true. lecForwardDelayTime SHOULD BE less than lecAgingTime. When it is not, lecAgingTime governs LE_ARP aging. This time value is expressed in seconds. Corresponds to Initial State Parameter C18.

Expected LE_ARP Reponse Time. The maximum time that the LEC expects an LE_ARP_REQUEST/LE_ARP_RESPONSE cycle to take. Used for retries and verifies. This time value is expressed in Time) seconds. Corresponds to Initial State Parameter C20.

Flush Time-out. Time limit to wait to receive a LE_FLUSH_RESPONSE after the LE_FLUSH_REQUEST has been sent before taking recovery action. This time value is expressed in seconds. Corresponds to Initial State Parameter C21.

Path Switching Delay. The time since sending a frame to the BUS after which the LE Client may assume that the frame has been either discarded or delivered to the recipient. May be used to bypass the Flush protocol. This time value is expressed in seconds. Corresponds to Initial State Parameter C22.

Local Segment ID. The segment ID of the emulated LAN. This is only required for IEEE 802.5 clients that are Source Routing bridges. Corresponds to Initial State Parameter C23.

Multicast Send VCC Type. Signalling parameter that SHOULD be used by the LE Client when establishing the Multicast Send VCC. This is the method to be used by the LE Client when specifying traffic parameters when it sets up the Multicast Send VCC for this emulated LAN. Corresponds to Initial State Parameter C24. Enumeration: 'constantBitRate': 3, 'variableBitRate': 2, 'bestEffort': 1.

Multicast Send VCC AvgRate. Signalling parameter that SHOULD be used by the LE Client when estabishing the Multicast Send VCC. Forward and Backward Sustained Cell Rate to be requested by LE Client when setting up Multicast Send VCC, if using Variable bit rate codings. Corresponds to Initial State Parameter C25.

Multicast Send VCC PeakRate. Signalling parameter that SHOULD be used by the LE Client when establishing the Multicast Send VCC. Forward and Backward Peak Cell Rate to be requested by LE Client when setting up the Multicast Send VCC when using either Variable or Constant bit rate codings. Corresponds to Initial State Parameter C26.

Connection Complete Timer. Optional. In Connection Establish ment this is the time period in which data or a READY_IND message is expected from a Calling Party. This time value is expressed in seconds. Corresponds to Initial State Parameter C28.

Specifies the Port Name for the logical port. This object only applies to OSA-Express ATM155 adapters configured for QDIO LAN Emulation mode. For ATM OSA-2 adapters, or OSA-Express ATM155 adapters configured for non-QDIO mode, the value will be null.

This table is intended to represent the data that is available from an OSA Port that is running LAN Emulation mode. An entry in this table is indexed by a LAN Emulation ifIndex. An ifEntry who's ifType is either aflane802.3 (59) or aflane802.5 (60) will have a corresponding entry in this table. This table is modeled after the LEC Status Table from the LAN Emulation MIB defined by the ATM Forum.

Describes a particular ATM Lec Status Table entry, indexed by either a aflan802.3 or a aflane802.5 ifEntry's ifIndex.

LE Client's ATM Addresses. The primary ATM address of this LAN Emulation Client. This address is used to establish the Control Direct and Multicast Send VCCs, and may also be used to set up Data Direct VCCs. A client may have additional ATM addresses for use with Data Direct VCCs. These addresses are readable via the lecAtmAddressTable. Corresponds to Initial State Parameter C1.

LE Client Identifier. Each LE Client requires a LE Client Identifier (LECID) assigned by the LE Server during the Join phase. The LECID is placed in control requests by the LE Client and MAY be used for echo suppression on multicast data frames sent by that LE Client. This value MUST NOT change without terminating the LE Client and returning to the Initial state. A valid LECID MUST be in the range X'0001' through X'FEFF'. The value of this object is only meaningful for a LEC that is connected to a LES. For a LEC which does not belong to an emulated LAN, the value of this object is defined to be 0. Corresponds to Initial State Parameter C14.

The current state of the LAN Emulation Client. Note that 'ifOperStatus' is defined to be 'up' when, and only when, lecInterfaceState' is 'operational'. Enumeration: 'join': 4, 'configure': 3, 'busConnect': 6, 'initialState': 1, 'lecsConnect': 2, 'initialRegistration': 5, 'operational': 7.

Status code from the last failed Configure response or Join response. Failed responses are those for which the LE_CONFIGURE_RESPONSE / LE_JOIN_RESPONSE frame contains a non-zero code, or fails to arrive within a timeout period. If none of this client's requests have failed, this object has the value 'none'. If the failed response contained a STATUS code that is not defined in the LAN Emulation specification, this object has the value 'undefinedError'. The value 'timeout' is self explanatory. Other failure codes correspond to those defined in the specification, although they may have different numeric values. Enumeration: 'invalidRequestParameters': 5, 'none': 1, 'leConfigureError': 14, 'insufficientInformation': 15, 'versionNotSupported': 4, 'noConfiguration': 13, 'duplicateLanDestination': 6, 'invalidAtmAddress': 12, 'insufficientResources': 8, 'duplicateAtmAddress': 7, 'timeout': 2, 'undefinedError': 3, 'invalidRequesterId': 10, 'invalidLanDestination': 11, 'accessDenied': 9.

The state this client was in when it updated the 'lecLastFailureRespCode'. If 'lecLastFailureRespCode' is 'none', this object has the value initialState(1). Enumeration: 'join': 4, 'configure': 3, 'busConnect': 6, 'initialState': 1, 'lecsConnect': 2, 'initialRegistration': 5, 'operational': 7.

The LAN Emulation protocol which this client supports, and specifies in its LE_JOIN_REQUESTs.

The LAN Emulation protocol version which this client supports, and specifies in its LE_JOIN_REQUESTs.

Topology Change. Boolean indication that the LE Client is using the Forward Delay Time C18, instead of the Aging Time C17, to age non-local entries in its LE_ARP cache C16. For a client which is not connected to the LES, this object is defined to have the value 'false'. Corresponds to Initial State Parameter C19. Enumeration: 'false': 2, 'true': 1.

The ATM address of the LAN Emulation Configuration Server (if known) or the 0 (otherwise). In LAN Emulation MIB, the OCTET STRING is either 0 length or 20 octets. For OSA-ATM, this Address) has been changed to a constant 20 octets, with the value 0 equivalent to the 0 length OCTET STRING.

Indicates whether this LAN Emulation Client used the LAN Emulation Configuration Server, and, if so, what method it used to establish the Configuration Direct VCC. Enumeration: 'didNotUseLecs': 4, 'gotAddressViaIlmi': 1, 'usedWellKnownAddress': 2, 'usedLecsPvc': 3.

The data frame format that this LAN Emulation Client is using right now. This may come from lecConfigLanType, the LAN Emulation Configuration Server, or the LAN Emulation Server. This value is related to 'ifMtu' and 'ifType'. See the LEC management specification for more details. Corresponds to Initial State Parameter C2. Enumeration: 'tokenRing': 3, 'ethernet': 2, 'unspecified': 1.

Maximum Data Frame Size. The maximum data frame size that this LAN Emulation client is using right now. This may come from lecConfigMaxDataFrameSize, the LAN Emulation Configuration Server, or the LAN Emulation Server Corresponds to Initial State Parameter C3. Enumeration: 'f4544': 3, 'f18190': 5, 'f1516': 2, 'unspecified': 1, 'f9234': 4.

ELAN Name. The identity of the emulated LAN which this client last joined, or wishes to join. This may come from lecConfigLanName, the LAN Emulation Configuration Server, or the LAN Emulation Server. Corresponds to Initial State Parameter C5.

LE Server ATM Address. The LAN Emulation Server address currently in use or most recently attempted. If no LAN Emulation Server attachment has been tried, this object's value is zero. Corresponds to Initial State Parameter C9. In LAN Emulation MIB, the OCTET STRING is 0 to 20 octets in length. For OSA-ATM, this has been changed to a constant 20 octets, with the value 0 equivalent to the 0 length OCTET STRING.

Indicates whether this client is acting as a proxy. Proxy clients are allowed to represent unregistered MAC addresses, and receive copies of LE_ARP_REQUEST frames for such addresses. Corresponds to Initial State Parameter C4. Enumeration: 'false': 2, 'true': 1.

This table is intended to represent the data that is available from an OSA Port that is running LAN Emulation mode. An entry in this table is indexed by a LAN Emulation ifIndex. An ifEntry who's ifType is either aflane802.3 (59) or aflane802.5 (60) will have a corresponding entry in this table. This table is modeled after the LEC Statistics Table from the LAN Emulation MIB defined by the ATM Forum.

Describes a particular ATM Lec Statistics Table entry, indexed by either a aflan802.3 or a aflane802.5 ifEntry's ifIndex.

The number of LE_ARP_REQUESTs sent over the LUNI by this LAN Emulation Client.

The number of LE_ARP_REQUESTs received over the LUNI by this LAN Emulation Client. Requests may arrive on the Control Direct VCC or on the Control Distribute VCC, depending upon how the LES is implemented and the chances it has had for learning. This counter covers both VCCs.

The number of LE_ARP_RESPONSEs sent over the LUNI by this LAN Emulation Client.

The number of LE_ARP_RESPONSEs received over the LUNI by this LAN Emulation Client. This count includes all such replies, whether solicited or not. Replies may arrive on the Control Direct VCC or on the Control Distribute VCC, depending upon how the LES is implemented. This counter covers both VCCs.

The total number of control packets sent by this LAN Emulation Client over the LUNI.

The total number of control packets received by this LAN Emulation Client over the LUNI.

The total number of outgoing LAN Emulation SVCs which this client tried, but failed, to open; incoming LAN Emulation SVCs which this client tried, but failed to establish; and incoming LAN Emulation SVCs which this client rejected for protocol or security reasons.

This table is intended to represent the data that is available from an OSA Port that is running LAN Emulation mode. An entry in this table is indexed by a LAN Emulation ifIndex. An ifEntry who's ifType is either aflane802.3 (59) or aflane802.5 (60) will have a corresponding entry in this table. This table is modeled after the LEC Server Table from the LAN Emulation MIB defined by the ATM Forum.

Describes a particular ATM Lec Server Table entry, indexed by either a aflan802.3 or a aflane802.5 ifEntry's ifIndex.

The interface associated with the Configuration Direct VCC. If no Configuration Direct VCC exists, this object has the value 0. Otherwise, the objects ( lecConfigDirectInterface, lecConfigDirectVPI, lecConfigDirectVCI ) identify the circuit.

If the Configuration Direct VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Configuration Direct VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Control Direct VCC. If no Control Direct VCC exists, this object has the value 0. Otherwise, the objects ( lecControlDirectInterface, lecControlDirectVPI, lecControlDirectVCI ) identify the circuit.

If the Control Direct VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Control Direct VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Control Distribute VCC. If no Control Distribute VCC has been set up to this client, this object has the value 0. Otherwise, the objects ( lecControlDistributeInterface, lecControlDistributeVPI, lecControlDistributeVCI ) identify the circuit.

If the Control Distribute VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Control Distribute VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object contains the value 0.

The interface associated with the Multicast Send VCC. If no Multicast Send VCC exists, this object has the value 0. Otherwise, the objects ( lecMulticastSendInterface, lecMulticastSendVPI, lecMulticastSendVCI ) identify the circuit.

If the Multicast Send VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Multicast Send VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Multicast Forward VCC. If no Multicast Forward VCC has been set up to this client, this object has the value 0. Otherwise, the objects ( lecMulticastForwardInterface, lecMulticastForwardVPI, lecMulticastForwardVCI ) identify the circuit.

If the Multicast Forward VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Multicast Forward VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

This table is intended to represent the data that is available from an OSA Port that is running LAN Emulation mode. An entry in this table is indexed by a LAN Emulation ifIndex. An ifEntry who's ifType is either aflane802.3 (59) or aflane802.5 (60) will have a corresponding entry in this table. This table is modeled after the LEC MAC Address Table from the LAN Emulation MIB defined by the ATM Forum.

Describes a particular ATM Lec Mac Address Table entry, indexed by either a aflan802.3 or a aflane802.5 ifEntry's ifIndex.

A unicast MAC address which the LE client denoted by 'lecIndex' has registered with its LE Server. This value is expressed in canonical form for Ethernet.

Extends tcpConnTable to provide additional TCP connection information.

Descibes a particular tcp connection entry.

The number of 100ths of seconds since this entry was last used.

The number of bytes received from IP for this connection.

The number of bytes sent to IP for this connection.

The number of times that this connection has made a direct transition to the SYN-RCVD state from the listen state.

Type of Service (tos) in effect for this tcpConnTable entry. Currently not supported and should return a zero.

IP options (see RFC 791)

Number of outgoing bytes buffered

Sequence number of next byte for user

Sequence number of next byte for TCP

Sequence number of sent/unacked byte

Sequence number of last pushed byte

Sequence number of last urg byte

Last sequence number in snd window

Last sequence number used, win update

Last Ack number used, win update

Number of incoming bytes buffered

Sequence number of next byte for TCP

Sequence number of next byte for user

Sequence number of last pushed byte

Sequence number of 'urgent' byte received

Last sequence number in receive window

Total number of retransmissions for this connection.

Maximum send window seen

Number of times the current segment has been retransmitted.

Congestion window

Slow start threshold

The amount of time that has elapsed, measured in milliseconds, from when the last TCP segment was transmitted by the TCP Stack until the ACK was received.

Round trip time variance.

Initial Send Sequence Number

Initial Receive Sequence Number

Maximum Segment Size we can send

Sequence of last window

Ack of last window

Send Window size

TCP non_block read flag

Receive buffer size

Resource Name is the text identification of this resource. It represents the user who opened the socket and is updated again during the bind processing.

The subtask ID represents the task that opened the socket and is updated again during bind processing. It is actually the TCB address.

Resource ID is the numeric identification of this resource.

flag for socket options (1 byte hex value) -bit(1) = Sockets SO_REUSEADDR option -bit(2) = SO_OOBINLINE option -bit(3) = SO_LINGER option -bit(4) = T_MSGDONTROUTE -bit(5) = No delay (Nagle off) option -bit(6) = SO_Keepalive option -bit(7) = Currently timing linger -bit(8) = Currently timing keep alive

flag for TCP timers (1 byte hex value) -bit(1) = Currently timing round trip -bit(2) = Currently timing rexmt -bit(3) = Currently timing window probe -bit(4) = Dally timer currently set -bit(5) = Max Seg Lifetime timer set -bit(6) = T_ORDREL_IND is pending -bit(7) = Blocked for writing -bit(8) = Need to send a FIN

1 byte hex flag for TCP signals -bit(1) = Signal urgent data -bit(2) = Signal normal data -bit(3) = Signal timing finwait2 -bit(4) = -bit(5) = -bit(6) = Window scale option was received -bit(7) = Tcb on accept queue -bit(8) = Socket OPTMSS option

TCP select flag byte for TCP select conditions. It is mapped as follows: -bit(1) = ON if active open, off passive -bit(2) = ON means timestamp option supported -bit(3) = ON when select for read issued -bit(4) = ON when select for write -bit(5) = ON when select for exception -bit(6) = ON means this is controlling -bit(7) = ON if accept in progress -bit(8) = ON means we are at OOB mark

4 byte value for the TCP sequence number

The value of this object will always be zero since it currently isn't reported.

This flag will hold special TCP protocol conditions: - bit(1) = Delay Acks requested on PORT/PORTRANGE - bit(2) = Delay Acks requested on GATEWAY - bit(3) = Use default round trip parms - bit(4) = Connection is one hop away - bit(5) = Optimal max segment size request on PORT/PORTRANGE - bit(6) = FRCA conn deleted - bit(7) = PASCAL Multi Client - bit(8) = Load Balancing child

This flag will indicates the following TCP poll conditions: - bit(1) = High priority data received - bit(2) = - bit(3) = Written Normal - bit(4) = - bit(5) = Reading Normal - bit(6) = - bit(7) = - bit(8) =

When the corresponding TCP connection is for a 3172 Telnet session then this object contains the Target VTAM Application name.

When the corresponding TCP connection is for a 3172 Telnet session then this object contains the VTAM LU name.

When the corresponding TCP connection is for a 3172 Telnet session then this object contains the Client's userid.

When the corresponding TCP connection is for a 3172 Telnet session then this object contains the LOG Mode.

This flag will indicates the following Telnet modes: -bit(1 - 5) = -bit(6) = TN3270 mode -bit(7) = TN3270E mode -bit(8) = line mode

Number of duplicate ACKs received for this connection.

Optimal maximum segment size. The range of this value is from 0 to 65535.

This flag contains sysplex cluster connection types for this connection: -bit(1) = getsockopt(clusterconntype) requested -bit(2 - 4) = -bit(5) = cluster internal -bit(6) = same image -bit(7) = same cluster -bit(8) = none

The number of segments received from IP for this connection.

The number of segments sent to IP for this connection.

The Differentiated Services field value in effect for this tcpConnTable entry. The value may be one of the following: - If there is a Service Policy Agent policy in effect for this entry, the value will be either: - The IPv4 TOS value defined by RFC 791 and 1349 - The Differentiated Services field value defined by RFC 2474 - If there is no Service Policy Agent policy in effect for this entry, the value will be 0.

Send buffer size

The total number of connections accepted by this listener. Applies only to listener entries.

The total number of connections dropped by this listener due to backlog exceeded. Applies only to listener entries.

The current number of connections in backlog. Applies only to listener entries.

The maximum number of connections allowed in backlog at one time. Applies only to listener entries.

If true(1), the TCP window scale option is active for this connection. If false(2), the TCP window scale option is not active.

If true(1), the TCP timestamp option is active for this connection. If false(2), the TCP timestamp option is not active.

The numeric identification of the server (i.e. listener connection) associated with this client connection. This value only applies to load balancing servers which have bound to a port number for which SHAREPORT was specified on the PORT/PORTRANGE Profile statement. This value will be zero for client connections to servers which are not load balancing servers. The value of this object can be used to retrieve the listener entry from the ibmTcpipMvsTcpListenerTable.

Number of TCP connections that have corresponding sockets closed.

Number of passive connection requests discarded.

Number of TCP connections in the TIMEWAIT state that have been reused for connections in the SYN-RCVD state.

Number of inbound TCP acknowledgements with successful header prediction.

Number of inbound TCP data segments with successful header prediction.

Number of inbound duplicate TCP acknowledgements.

Number of inbound TCP segments discarded due to bad checksum.

Number of inbound TCP segments discarded due to bad header len.

Number of inbound TCP data segments discarded due to data length shorter than segment length.

Number of inbound TCP data segments discarded due to old timestamp.

Number of inbound TCP data segments with all data before current TCP window.

Number of inbound TCP data segments with some data before current TCP window.

Number of inbound TCP data segments with all data after current TCP window.

Number of inbound TCP data segments with some data after current TCP window.

Number of inbound TCP data segments that did not contain the next expected sequence number (ie. out-of-order).

Number of inbound TCP data segments received after corresponding sockets have been closed.

Number of inbound TCP segments processed while current receive window size is zero.

Number of inbound TCP segments that only change receive window size.

Number of outbound TCP segments that only change receive window size.

Number of delayed outbound TCP acknowledgements.

Number of outbound window probe requests.

Number of TCP retransmit timer pops.

Number of TCP connections dropped due to retransmit threshold exceeded.

Number of outbound TCP segments retransmitted due to path MTU discovery.

Number of TCP connections that exceeded path MTU discovery retransmit threshold.

Number of TCP connections dropped due to no response while sending window probe requests.

Number of keepalive probe requests.

Number of TCP connections dropped due to no response while sending keepalive probe requests.

Number of TCP connections dropped due to FINWAIT2 timer expiring prior to receiving FIN segment.

Provides TCP connection information for connections in Listen state. Connections in this state are assumed to be servers so only server MIB objects are supported.

Descibes a particular tcp listener entry.

Resource ID is the numeric identification of this resource. This value is also known as the connection ID.

The IP address type of the ibmMvsTcpListenerLocalAddr object.

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.

The local port number for this TCP connection.

The IP address type of the ibmMvsTcpListenerRemoteAddr object.

The remote ip address for this TCP connection.

The remote port number for this TCP connection.

The total number of connections accepted by this listener.

The total number of connections dropped by this listener due to backlog exceeded.

The current number of connections in backlog.

The maximum number of connections allowed in backlog at one time.

Resource Name is the text identification of this resource. It represents the user who opened the socket and is updated again during the bind processing.

Extends udp table to support additional UDP listener information.

Descibes a particular udp entry.

The amount of time that has elapsed since the corresponding entry has had any activity. Measured in hundreds of seconds.

The type of service in effect for this entry. Currently, not supported and will return a zero when retrieved.

IP Options (see RFC 791)

Number of received datagrams.

Number of bytes received.

Number of send datagrams.

Number of bytes sent.

Resource Name is the text identification of this resource. It represents the ?itName value of the associating resource's relationship with the UDP Stack.

4 bytes hex decimal

Resource ID is the numeric identification of this resource.

flag for socket options (1 byte hex valuel) -bit(1) = allow broadcast address -bit(2) = allow loopback of datagrams -bit(3) = bypass normal routing -bit(4) = forward ICMP message (Pascal) -bit(5) = outgoing multicast datagrams -bit(6) = incoming multicast datagrams -bit(7) = -bit(8) =

maximum transmit datagram size

maximum received datagram size

A entry's state will always be active unless it is to be deleted. This is accomplished by setting this object to delete. A set of active is invalid. Enumeration: 'active': 1, 'delete': 2.

Time-to-live value for a multicast datagram.

If true(1), indicates that loopback is enabled for outbound multicast datagrams. If false(2), indicates either that loopback is disabled for outbound multicast datagrams or that the socket is not processing outgoing multicast datagrams. The value of object ibmMvsUdpSockOpt will indicate whether or not the socket is processing outgoing multicast datagrams.

IP address of the interface used for outbound multicast datagrams.

The Differentiated Services field value in effect for this udpTable entry. The value may be one of the following: - If there is a Service Policy Agent policy in effect for this entry, the value will be either: - The IPv4 TOS value defined by RFC 791 and 1349 - The Differentiated Services field value defined by RFC 2474 - If there is no Service Policy Agent policy in effect for this entry, but the entry is being used for an Enterprise Extender connection, the value will be one of the following VTAM IP Type of Service values in hexadecimal. See the SNA Network Implementation Guide for a descripton of VTAM IP Type of Service): 20 - Low 40 - Medium 80 - High C0 - Network - If neither of the above are true, then this value will be 0.

The table listing UDP sockets that receive multicast data. The table is ordered by the interface being used by the socket for incoming datagrams, the UDP socket (local IP address and port), and the mulitcast group to which the socket is registerd.

Entry defining a UDP socket that receives multicast data.

The local IP address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any IP interface associated with the node, the value 0.0.0.0 is used.

The local port number for this UDP listener.

Specifies the IP address of the multicast group

The IP address of the interface used for incoming packets for this multicast group on this socket.

Number of times the inbound TCP/IP Data Path has received control from the Device Layer. This counter may be less than the number of packets received (ipInReceives), as a single inbound call may process several inbound packets.

Number of times a received frame could not be unpacked into its consistuent datagrams, resulting in packet loss. A non-zero value in this counter may be evidence of a buffer-formatting problem within a device.

Number of inbound packets discarded due to a CSM storage shortage.

Number of outbound packets discarded due to a synchronous error in the Data Link Control. Synchronous DLC errors are detected on the interface between TCP/IP and VTAM, and are typically not related to channel or device errors.

Number of outbound packets discarded due to an asynchronous error in the Data Link Control. Asynchronous DLC errors may occur for a variety of reasons, including channel/device errors, incorrectly formatted data, or storage shortage within VTAM.

Number of outbound packets discarded due to a CSM storage shortage.

One entry in this table will exist per OSA-Express Device Interface. If the values for objects ibmMvsOsaExpCurLparName/Num are not the same as the values for objects ibmMvsOsaExpManLparName/Num then the OSA/SF running in the current LPAR is not the managing OSA/SF for this Device. The utilization object values will be reset when the CHPID is reset. The processor utilization objects are the sum of the per LPAR processor utilization values in the corresponding osaexpPerfTable entries for the adapter.

Definition of a single entry in the osaexpChannelTable. Indexed by the ifIndex of the corresponding DEVICE interface.

The channel number for this interface.

For OSA-Express adapters supporting QDIO mode, the value will be osd(17). For OSA-Express adapters supporting non-QDIO mode, the value will be ose(16). Enumeration: 'ose': 16, 'osd': 17.

Indicates how the channel is configured. Enumeration: 'twoLogicalEthPorts': 9, 'oneLogicalEthPort': 7, 'atmNative': 4, 'unknown': 1, 'oneLogicalTokenRingPort': 8, 'fastEthernet': 3, 'logicalEthernetAndTokenRingPorts': 11, 'logicalTokenRingAndEthPorts': 12, 'atmLanEmulation': 5, 'gigabit': 2, 'twoLogicalTokenRingPorts': 10, 'noPortsDefined': 6.

Configured mode of the OSA-Express adapter. This value will be set to nothingConfigured(1) for QDIO adapters that are not configured for LAN Emulation. Enumeration: 'snaMode': 3, 'nothingConfigured': 1, 'passthruAndSna': 4, 'atmNative': 8, 'atmLePassthruAndSna': 7, 'passthruMode': 2, 'atmLePassthr': 5, 'atmLeSna': 6, 'atmLe': 9.

Hardware channel state: online, not installed, or offline. Enumeration: 'notinst': 3, 'offline': 5, 'online': 1.

An OSA-Express Channel can be shared across multiple LPARs. This object indicates if this channel is currently being shared. Enumeration: 'yes': 1, 'no': 0.

Number of ports on the OSA-Express adapter. For non-ATM adapters, the value reflects the number of physical ports. For ATM adapters the value reflects the number of logical ports. For ATM155 Native mode adapters, the value should be 1. For ATM155 QDIO LAN Emulation mode adapters, the value can be 1 or 2 depending on the number of logical ports configured.

Describes the generic node descriptor layout. This object represents the ND obtained from the CHSC instruction: /* ND Flags */ int bValidity :3; /* 1:is ND valid */ int bNodeType :1; /* 1:0=dev,1=chnlsubstm nod*/ int bInternal :1; /* internal(1)/external(0) */ int bCHPinvalid :1; /* IF =1,NDCHPID is invalid*/ int bNDRsvd1 :2; /* spare bits for alignment*/ char NDType; /* reserved by architecture*/ char NDClass; /* Class for subsystem node*/ char NDCHPID; /* CHP ID for specified int*/ char NDTypeNum 6 ; /* type number of the SDC */ char NDModelNum 3 ; /* ND model number in the form of 3 EBCDIC OCTETS */ char NDMfgr 3 ; /* ND manufacturer in the form of 3 EBCDIC OCTETS */ char NDMfgrPlant 2 ; /* ND plant of manufacture (2 EBCDIC OCTETS) */ char NDSeqNum 12 ; /* ND sequence number (12 EBCDIC OCTETS) */ char NDTag 2 ; /* ND tag */

The control unit number associated with the OSA-Express Channel.

ibmMvsOsaExpChannelCodeLevel is the firmware (or micro code level) of the OSA adapter. For example, OSA adapter level 05.60 would be represented as 0x0560 by this object.

LPAR name of the OSA/SF from which this data was retrieved.

LPAR number of the OSA/SF from which this data was retrieved.

LPAR name of the OSA Support Facility managing this channel. Only one OSA/SF can manage a OSA-Express Channel within an MVS Sysplex even though multiple OSA/SFs can retrieve information from the same OSA-Express Channel.

LPAR number of the OSA Support Facility managing this channel (set to 0xFFFF if not being managed by a OSA/SF).

The average, over a 1 minute interval, of the percentage of time that the PCI bus was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

The average, over a 1 minute interval, of the percentage of time that the CHPID Processor was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

The average, over a 5 minute interval, of the percentage of time that the PCI bus was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

The average, over a 5 minute interval, of the percentage of time that the CHPID Processor was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

The average, over an hour interval, of the percentage of time that the PCI bus was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

The average, over an hour interval, of the percentage of time that the CHPID Processor was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

This table provides performance information per each LPAR's utilization of an OSA-Express adapter. The values will be reset when the adapter CHPID is reset.

Definition of a single entry in the osaexpPerfTable. Indexed by the ifIndex of the corresponding DEVICE interface and the LPAR number.

LPAR number of the LPAR to which the performance objects apply.

The average, over a 1 minute interval, of the percentage of time that the CHPID Processor was utilized to transfer data for a specific LPAR. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

The average, over a 1 minute interval, of the number of inbound kilobytes processed for a specific LPAR. When the ibmMvsOsaExpPerfProcessorUtil1Min object for a specific LPAR has a value of -1, then the interval data could not be retrieved from the adapter and this object will have a value of zero.

The average, over a 1 minute interval, of the number of outbound kilobytes processed for a specific LPAR. When the ibmMvsOsaExpPerfProcessorUtil1Min object for a specific LPAR has a value of -1, then the interval data could not be retrieved from the adapter and this object will have a value of zero.

The average, over a 5 minute interval, of the percentage of time that the CHPID Processor was utilized to transfer data for a specific LPAR. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

The average, over a 5 minute interval, of the number of inbound kilobytes processed for a specific LPAR. When the ibmMvsOsaExpPerfProcessorUtil5Min object for a specific LPAR has a value of -1, then the interval data could not be retrieved from the adapter and this object will have a value of zero.

The average, over a 5 minute interval, of the number of outbound kilobytes processed for a specific LPAR. When the ibmMvsOsaExpPerfProcessorUtil5Min object for a specific LPAR has a value of -1, then the interval data could not be retrieved from the adapter and this object will have a value of zero.

The average, over an hour interval, of the percentage of time that the CHPID Processor was utilized to transfer data for a specific LPAR. It does not include idle time or time used by routine maintenance tasks. The range of valid values for this object is 0 to 100%. A value of -1 indicates that the value could not be retrieved from the adapter.

The average, over an hour interval, of the number of inbound kilobytes processed for a specific LPAR. When the ibmMvsOsaExpPerfProcessorUtilHour object for a specific LPAR has a value of -1, then the interval data could not be retrieved from the adapter and this object will have a value of zero.

The average, over an hour interval, of the number of outbound kilobytes processed for a specific LPAR. When the ibmMvsOsaExpPerfProcessorUtilHour object for a specific LPAR has a value of -1, then the interval data could not be retrieved from the adapter and this object will have a value of zero.

This table is intended to represent the ethernet Ports associated with the osaexpChannelTable entries for ethernet adapters. Each OSA-Express Channel has one or more Ports.

Definition of a single entry in the osaexpEthPortTable. Indexed by the ifIndex of the corresponding LINK interface.

Port number, starts at 0.

The physical port type. Enumeration: 'gigabitEthernet': 65, 'fastEthernet': 81.

The hardware state of the port: 1 - Unknown port hardware state. 2 - OSA has detected a loss of signal on the link. (A likely cause of this condition is an improperly installed or missing cable connection on the port). For OSA-Express ATM, this condition can also be caused by registration failure. 3 - Port is disabled. The reason for the port being disabled is set in object ibmMvsOsaExpEthPortDisabledStatus. 4 - Port is enabled. Enumeration: 'disabled': 3, 'unknown': 1, 'enabled': 4, 'linkFailure': 2.

Enumeration: 'nonserviceMode': 0, 'serviceMode': 1.

When the value of ibmMvsOsaExpEthPortHardwareState is disabled(3), this object explains the reason for the disabled state. The value for this object may be a combination of the following: 0x0001 Disabled internal port failure 0x0002 Disabled service processor request 0x0004 Disabled network request 0x0008 Disabled OSA/SF request 0x0010 Disabled configuration change 0x0020 Disabled link failure threshold exceeded 0x0040 Disabled port temporarily disabled When the value of ibmMvsOsaExpEthPortHardwareState is not disabled(3), the value of this object will be zero.

Configuration name.

The configured port speed. For OSA-Express Gigabit Ethernet adapters the port speed can not be configured so the value of this object will be 1000MbFullDuplex(7). Enumeration: 'fullDuplex100Mb': 4, 'halfDuplex10Mb': 1, 'halfDuplex100Mb': 3, 'autoNegotiate': 0, 'fullDuplex1000Mb': 7, 'fullDuplex10Mb': 2.

The actual port speed. Enumeration: 'fullDuplex100Mb': 4, 'halfDuplex10Mb': 1, 'halfDuplex100Mb': 3, 'unknown': 0, 'fullDuplex1000Mb': 7, 'fullDuplex10Mb': 2.

A 6 byte OCTET STRING which contains the current MAC address in use on the adapter.

A 6 byte OCTET STRING which contains the adapter's burned in MAC address.

Configured port description.

The count of the total number of packets transmitted from this port. A CHPID reset will cause this value to be reset to zero.

The count of the total number of packets received by this port. A CHPID reset will cause this value to be reset to zero.

The count of the total number of group frames received by this port. A CHPID reset will cause this value to be reset to zero.

The count of the total number of broadcast frames received by this port. A CHPID reset will cause this value to be reset to zero.

Specifies the Port Name which must also be entered at the connection manager on the host and the application. Port Name is specifed to OSA/SF as a config file parameter (PCM_NAME). This value is also specified via ILMI as the value of the atmfPortMyIfName object. Does not apply to an ATM OSA-2 adapter configured for ATM IP Forwarding mode, or an OSA-Express ATM155 adapter configured for QDIO LAN Emulation mode.

The count of the total number of packets that were discarded because they did not have a matching IP address and there was no primary nor secondary router default defined. This object is not supported for Fast Ethernet adapters so the value will be zero.

This field contains the active Group Addresses. An individual Group Address is 6 bytes long. Therefore, this field is actually 32 times (OCTET STRING(SIZE(6)) + 2 bytes of padding) long.

This table is intended to represent the data that is available from an OSA-Express ethernet Port that is running in SNA mode. An entry in this table is associated with the osaexpEthPortTable entries.

Definition of a single entry in the osaexpEthSnaTable. Indexed by the ifIndex of the corresponding LINK interface.

The inactivity timer. An enabled inactivity timer (Ti) periodically tests the viability of the network media. The timer setting applies to all the clients on the target LAN, not to individual clients. The timer interval indicates how quickly a failure of the network media can be detected when the connection is quiescent. If the Ti timer times out, a supervisory poll frame is sent over the connection. The T1 response, or reply, timer clocks the supervisory poll. If the T1 timer times out, the supervisory poll is retransmitted. OSA can retransmit a supervisory poll up to 8 times. If no response is received after the last retransmission, the link is declared inoperative, and the MVS program issues a message. The value will either be zero, or in the range of 24 to 9000 in units of 100th of a second.

The response timer. The T1 timer clocks link events that require responses from clients on the network. These link events include SABME/UA exchanges, I-frame link protocol data unit (LPDU) transmissions, and supervisory polls. The value is expressed as an integer in units of 10th of a second.

The acknowledgement timer. An OSA starts the T2 timer when it receives an I-format LPDU and stops when it sends an acknowledgement. An acknowledgement is sent either when an outgoing I frame is sent, which acts as the acknowledgement, or when N3 number of I-format LPDUs has been received. If the T2 timer times out, the OSA must send an acknowledgement. The value is expressed as an integer in units of 100th of a second.

Maximum I frames before ACK (N3). The maximum number of I-format link protocol data units (LPDUs) that can be received by an OSA before it sends an acknowledgement (N3 count). It is also called the receive window count.

SNA maximum transmit window (TW). The maximum number of outstanding I-format link protocol data units (LPDUs). It is also called the maximum transmit window count or the maximum window out count. The TW count allows the sender to transmit frames before that sender is forced to halt and wait for an acknowledgement. Therefore, the receiver should be able to absorb that number of frames, either in its service access point (SAP) buffers or within the buffers in workstation memory.

Each entry in this table represents a Dynamic VIPA (DVIPA) interface configured to this stack, and supports DVIPA status information.

Definition of a single entry in the ibmMvsDVIPATable.

The IP address type of the ibmMvsDVIPAIpAddr object.

The dynamic VIPA IP address.

The IP address type of the ibmMvsDVIPAMaskAddr object This object will be set to unknown(0) for entries whose ibmMvsDVIPAOrigin value is backup(2).

The address mask. This object will be set to a zero-length string for entries whose ibmMvsDVIPAOrigin value is backup(2).

The status of this DVIPA on the stack. A status of unknown(1) should not occur and represents an error. Enumeration: 'active': 2, 'unknown': 1, 'moving': 4, 'quiescing': 5, 'backup': 3.

The origin of how this DVIPA came to be configured to the stack. A value of backup(2) or define(3) indicates which VIPADYNAMIC Profile statement was used to configure the DVIPA to the stack. A value of rangeBind(4) indicates that the DVIPA was dynamically defined when an application issued a BIND function call. A value of rangeIoctl(5) indicates that the DVIPA was dynamically defined when an application issued the SIOCSVIPA IOCTL function call. A value of target(6) indicates that the DVIPA was dynamically defined on the stack because this stack is a target stack for the Sysplex Distributor function. A status of unknown(1) should not occur and represents an error. Enumeration: 'rangeBind': 4, 'target': 6, 'unknown': 1, 'rangeIoctl': 5, 'backup': 2, 'define': 3.

This stack's rank in the chain of backup stacks for a given dynamic VIPA. For entries whose ibmMvsDVIPAOrigin value is not backup(2) or define(3), this object does not apply and will be set to -1.

The status of this DVIPA on the stack in relation to the Sysplex Distributor function. A value of none(1) indicates that the DVIPA is not participating in the Sysplex Distributor function. A value of distributor(2) indicates that the stack is a distributor for this DVIPA. A value of target(3) indicates that the stack is a target stack for this DVIPA. A value of distributorAndTarget(4) indicates that the stack is both a distributor and a target stack for this DVIPA. Enumeration: 'distributor': 2, 'disgtributorAndTarget': 4, 'none': 1, 'target': 3.

The manner in which a dynamic VIPA IP address should be moved to another stack. A value of none(1) indicates that moveable status does not apply to this DVIPA. This value would be set for entries where backup is set as the value for the ibmMvsDVIPAOrigin and ibmMvsDVIPAStatus objects. For DVIPA IP addresses activated as the result of a VIPADEFINE configuration statement, a value of immediate(2) means that this dynamic VIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by executing a VIPADEFINE for the same dynamic VIPA. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new owning stack. A value of whenIdle(3) means that this dynamic VIPA can be moved to another stack when there are no connections for this dynamic VIPA on this stack. While there are existing connections, any new connection requests will continue to be directed to this stack. For DVIPA IP addresses activated as the result of a VIPARANGE configuration and a subsequent SIOCSVIPA IOCTL or BIND, a value of nonDisruptive(4) means that this DVIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by creating the same DVIPA via a subsequent BIND or SIOCSVIPA IOCTL. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new stack. A value of disruptive(5) means that one of two different behaviors will occur: - In the case of a subsequent BIND by an application on another stack, no movement of the DVIPA will occur the second application will presumably be disrupted because the BIND fails. (The first application is unaware that another BIND occurred.) - In the case of a subsequent SIOCSVIPA IOCTL, the DVIPA will move to another stack but connections to the DVIPA on this stack will be broken. Enumeration: 'none': 1, 'nonDisruptive': 4, 'whenIdle': 3, 'immediate': 2, 'disruptive': 5.

The status of this DVIPA on the stack in relation to the Service Manager function. A value of true(1) indicates that the DVIPA is participating in the Service Manager function. A value of false(2) indicates that the DVIPA is not participating in the Service Manager function.

Each entry in this table represents a subnet defined by the VIPARANGE Profile statement in which requests for activating a DVIPA via a BIND or SIOCSVIPA IOCTL, will be honored.

Definition of a single entry in the ibmMvsDVIPARangeConfTable.

The IP address type of the ibmMvsDVIPARangeConfIpAddr object.

The dynamic VIPA IP address.

The IP address type of the ibmMvsDVIPARangeConfMaskAddr object.

The dynamic VIPA IP address.

The manner in which a dynamic VIPA IP address defined by a VIPARANGE statement, should be moved to another stack. A value of nonDisruptive(1) means that this DVIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by creating the same DVIPA via a subsequent BIND or SIOCSVIPA IOCTL. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new stack. A value of disruptive(2) means that one of two different behaviors will occur: - In the case of a subsequent BIND by an application on another stack, no movement of the DVIPA will occur the second application will presumably be disrupted because the BIND fails. (The first application is unaware that another BIND occurred.) - In the case of a subsequent SIOCSVIPA IOCTL, the DVIPA will move to another stack but connections to the DVIPA on this stack will be broken. Enumeration: 'nonDisruptive': 1, 'disruptive': 2.

This object allows entries to be created and deleted in the ibmMvsDVIPARangeConfTable. Note that an attempt to set any read-create object defined within an ibmMvsDVIPARangeConfEntry while the value of ibmMvsDVIPARangeConfStatus is active(1) should result in an inconsistentValue error.

Each entry in this table represents a dynamic VIPA and port for which connection requests are to be distributed to other stacks as defined by the VIPADISTRIBUTE Profile statement.

Definition of a single entry in the ibmMvsDVIPADistConfTable.

The IP address type of the ibmMvsDVIPADistConfIpAddr object.

The dynamic VIPA IP address.

The dynamic VIPA distributed port.

The IP address type of the ibmMvsDVIPADistConfTargetDynXcfIpAddr object. If the ALL parameter was specified on the VIPADISTRIBUTE Profile statement, this object will be set to unknown(0).

The dynamic XCF IP address of the target stack. If the ALL parameter was specified on the VIPADISTRIBUTE Profile statement, this object will be set to a zero-length string.

This object allows entries to be created and deleted in the ibmMvsDVIPADistConfTable.

Each entry in this table represents a dynamic VIPA TCP connection. Entries will be supported in the table for all dynamic VIPA interfaces for which MOVEABLE IMMEDIATE or NONDISRUPTIVE was specified. On a Sysplex Distributor routing stack, there will be an entry in this table for every connection being routed through the distributor. On a stack taking over a dynamic VIPA, there will be an entry in this table for every connection to the dynamic VIPA. On a Sysplex Distributor target stack or a stack which is in the process of giving up a dynamic VIPA, there will be an entry in this table for every connection for which the stack is an endpoint.

Definition of a single entry in the ibmMvsDVIPAConnRoutingTable.

The dynamic VIPA port.

The IP address type of the ibmMvsDVIPAConnRemIpAddr object.

The remote IP address for this TCP connection.

The remote port for this TCP connection.

The IP address type of the ibmMvsDVIPAConnDynXcfIpAddr object.

The dynamic XCF IP address of the Sysplex Distributor target stack, or stack which is the endpoint of the connection.

The Service Policy Agent Policy Rule name that the connection maps to. If the Service Policy Agent is not active or the connection does not map to a policy, this object will be set to the string value *NONE*.

The Service Policy Agent Policy Action name that the connection maps to. If the Service Policy Agent is not active or the connection does not map to a policy, this object will be set to the string value *NONE*.

An entry exists in this table for every target stack per distributed dynamic VIPA and port. This table is supported only by stacks which are distributing connection requests as part of the Sysplex Distributor function. This table is not supported by stacks which are only targets of the Sysplex Distributor function.

Definition of a single entry in the ibmMvsDVIPADistPortTable.

The dynamic VIPA distributed port.

The IP address type of the ibmMvsDVIPADistPortTargetDynXcfIpAddr object.

The dynamic XCF IP address of the target stack.

The number of servers ready at the port on the target stack, to service connection requests.

The total number of connections for the dynamic VIPA IP address and port which have been distributed to the target stack.

The Workload Manager weight value for the MVS system on which the target stack is located. The value is normalized such that the lowest value is 1. This weight value is an indication of the MVS system's available CPU capacity. The lower the value the lower the capacity.

The IP address type of the ibmMvsDVIPAServMgrMulticastIpAddr object.

The type of multicast IP address that will be used for communications between the Sysplex Distributor and the routers acting as Forwarding Agents. This object reflects values from the VIPASMPARMS Profile statement for the Sysplex Distributor Service Manager function.

The type of multicast IP address that will be used for communications between the Sysplex Distributor and the routers acting as Forwarding Agents. This object reflects values from the VIPASMPARMS Profile statement for the Sysplex Distributor Service Manager function.

Indicates whether a password value was specified on the VIPASMPARMS Profile statement for the Sysplex Distributor Service Manager function. A value of true(1) indicates that a password was specified. A value of false(2) indicates that a password was not specified. The password enables MD5 encryption for all communications between the Sysplex Distributor function and routers acting as Forwarding Agents. This password must match configured on the Forwarding Agents.

The value of this object determines which traps will be generated for all dynamic VIPA events. The value of this object is initialized to dvipaStatusChange(0) and dvipaRemoved(1) so that only those traps will be automatically generated. The following values are only applicable to Sysplex Distributor distributing stacks: - targetAdded(2) - targetRemoved(3) - targetServerStarted(4) - targetServerEnded(5) The following traps are generated when the corresponding bit value for this object is set: BIT value Trap --================================== dvipaStatusChange(0) ibmMvsDVIPAStatusChange dvipaRemoved(1) ibmMvsDVIPARemoved targetAdded(2) ibmMvsDVIPATargetAdded targetRemoved(3) ibmMvsDVIPATargetRemoved targetServerStarted(4 ) ibmMvsDVIPATargetServerStarted targetServerEnded(5) ibmMvsDVIPATargetServerEnded Bits: 'targetRemoved': 3, 'targetServerStarted': 4, 'targetAdded': 2, 'dvipaRemoved': 1, 'dvipaStatusChange': 0, 'targetServerEnded': 5.

The compliance statement for the IBM Communications Server product.

Defines the objects that are argumented to the tcpConnTable

This group defines those objects that are augmented to a udp listen table entry.

This group comprises those objects that are related to atm support.

This group comprises those objects that are obsolete.

This group comprises those objects that are related to atm support.

This group comprises those objects that are related to interface entries in the IF-MIB.

This group comprises those objects that are related to ATM LAN Emulation support.

This group comprises those objects that represent the current set of PORT and PORTRANGE definitions for this TCP/IP instance.

This group comprises the TCP/IP retransmission parms that are in effect for a locally configured route entry.

Defines the objects that are augmented to the tcpConnTable

This group comprises those objects that are related to atm support.

This group comprises those objects that are related to interface entries in the IF-MIB.

This group defines those objects that are argumented to a udp listen table entry.

This group comprises those objects that are related to interface entries in the IF-MIB.

Defines the objects that are augmented to the tcpConnTable

Defines the objects that are augmented to the tcpConnTable

This group comprises those objects that are related to atm support.

This group comprises those objects that are related to interface entries in the IF-MIB.

This group comprises those objects that represent the current set of PORT and PORTRANGE definitions for this TCP/IP instance.

This group comprises those objects that are related to atm support.

Defines the objects that are augmented to the tcpConnTable

This group defines those objects that are augmented to a udp listen table entry.

This group comprises those objects that are related to ATM LAN Emulation support.

Defines objects that are augmented to the tcpConnTable and statistical objects for TCP entities.

This group defines statistical objects for IP entities.

This group comprises those objects that are related to OSA-Express adapter support.

This group comprises those objects that are related to interface entries in the IF-MIB.

This group comprises those objects that are related to Dynamic VIPA interfaces.

This group comprises those notification objects that are related to Dynamic VIPA support.

This group comprises those notification objects that are related to the MVS System group.