Netstat DEvlinks/-d report

INTFName/-K intfname

Filter the output of the DEvlinks/-d report using the specified interface name intfname. You can enter one filter value at a time and the specified value can be up to 16 characters in length.

The INTFName/-K filter value intfname can be one of the following values:

• The link name of a network interface that was configured on a LINK profile statement (this option selects one interface).
• The interface name of a network interface that was configured on an INTERFACE profile statement (this option selects one interface).
• The interface name of an OSAENTA trace interface, which is EZANTAportname, where the portname value is the name that is specified on the PORTNAME keyword in the TRLE for the OSA-Express port that is being traced (this option selects one interface).
• The port name of an OSA-Express feature in QDIO mode, where the port name is the name that is specified on the PORTNAME keyword in the TRLE (this option selects all interfaces that are associated with the OSA-Express port, including an OSAENTA trace interface).
• The name of a HiperSockets™ TRLE. This option selects all interfaces that are associated with the HiperSockets TRLE.

Restriction:

• The INTFName/-K filter value does not support wildcard characters.
• The INTFName/-K filter value does not display information for a device that does not have a link defined.

SMCID/-U smcid

Filter the output of the DEvlinks/-d report by using the specified SMC-R link or link group identifier smcid. You can enter one filter value at a time.

• If the filter value is an SMC-R link ID, then the report shows details about that SMC-R link and information about the SMC-R link group to which that link belongs.
• If the filter value is an SMC-R link group ID, then the report shows details about all SMC-R links in the link group and information about the SMC-R link group.
• If the filter value is an asterisk (*), then the report provides the same information that the SMC modifier provides.

Rule: If you specify the SMCID/-U filter on the command, the report is generated as if the SMC modifier was also specified. The report includes detailed information about the SMC-R link that smcid defines, regardless of whether the SMC modifier was explicitly coded.

The following examples are generated by using TSO NETSTAT command. Using the z/OS UNIX netstat command displays the data in the same format as the TSO NETSTAT command.

DevName

The device name that is configured on the DEVICE statement.

DevType

The device type that is configured on the DEVICE statement.

DevNum

The device number that is configured on the DEVICE statement. This field is significant only for device types CTC, CLAW, LCS, and CDLC.

DevStatus

The device status. You can use this field if you are having activation problems with the device or interface. Table 1 describes the possible status values:

Configured router status (CfgRouter)

The router attribute (PRIROUTER/SECROUTER/NONROUTER) that is specified on the DEVICE or INTERFACE statement. This field is significant only for MPCIPA devices and for IPAQENET and IPAQENET6 interfaces. This field is not displayed if virtual MAC (VMAC) has been configured.

Actual router status (ActRouter)

The router attribute in effect for the device or interface. It matches the configured router status unless the configured value conflicted with the configured value of another stack that is sharing the adapter. This field is significant only for MPCIPA devices and for IPAQENET and IPAQENET6 interfaces. The router attribute is determined when the device or interface starts. This field is not displayed if virtual MAC (VMAC) has been configured.

Virtual MAC address (VMACAddr)

The virtual local hardware address for this link or interface. This field is significant for the following types of devices:

• An IPAQENET link or interface, or an IPAQENET6 interface, where a virtual MAC address was configured by specifying the VMAC parameter. The value n/a is displayed if VMAC was configured but a virtual MAC address was not configured.
• An RNIC interface that is created when an IPAQENET or IPAQENET6 interface specified SMCR. The VMAC address is provided by VTAM®, and is not configured on the INTERFACE profile statement. VMACAddr is displayed for active RNIC interfaces only.

Virtual MAC origin (VMACOrigin)

Displays whether the virtual MAC address (VMACAddr) was configured on the LINK or INTERFACE statement, or was generated by OSA-Express. This field is significant only for IPAQENET links or interfaces and for IPAQENET6 interfaces for which virtual MAC (VMAC) has been configured. The following list shows the possible values:

Cfg

The virtual MAC address is configured on the LINK statement or on the INTERFACE statement.

OSA

The virtual MAC address has been generated by OSA-Express.

Virtual MAC router status (VMACRouter)

Displays the virtual MAC router attribute that was specified on the LINK or INTERFACE statement using the ROUTEALL or ROUTELCL keywords. This field is significant only for IPAQENET links or interfaces and for IPAQENET6 interfaces for which virtual MAC (VMAC) has been configured. See OSA Routing information in the z/OS Communications Server: IP Configuration Guide for more information about Virtual MAC router attributes. The following list shows the possible values:

All

Corresponds to the ROUTEALL keyword. Indicates that all IP traffic destined to the Virtual MAC is forwarded by the OSA-Express device to the TCP/IP stack

Local

Corresponds to the ROUTELCL keyword. Indicates that only traffic destined to the Virtual MAC whose destination IP address is registered with the OSA-Express device by this TCP/IP stack is forwarded by the OSA-Express device.

Configured packing status (CfgPacking)

This field is the packing attribute (Packed/None) specified on the DEVICE statement. This field is significant only for CLAW devices.

Actual packing status (ActPacking)

This field indicates the packing attribute in effect for the device. It will match the configured packing status unless packing was requested and the device does not support packing. This field is significant only for a CLAW device and is determined when the device starts.

LnkName/IntfName

This field is the link name or the interface name of the particular device or interface being displayed. If the device or interface is configured, this field is the link name configured in the LINK statement or the interface name configured in the INTERFACE statement. If the link name or interface name is dynamically generated by the TCP/IP stack, this field is the dynamically generated link name or interface name.

LnkType/IntfType

This field is the link type or the interface type of the particular device or interface being displayed. If the device or interface is configured, this field is the link type configured in the LINK statement or the interface type configured in the INTERFACE statement. If the link type or interface type is dynamically generated by the TCP/IP stack, this field is the dynamically generated link type or interface type. A 10GbE RoCE Express interface has an IntfType value equal to RNIC.

LnkStatus/IntfStatus

This field is the link or interface status. The following list describes the possible link or interface status values:

PortName

The name of the OSA-Express port. This is the value that was specified on the PORTNAME parameter on the INTERFACE statement. This field is significant only for IPAQENET and IPAQENET6 interfaces.

Datapath

The subchannel address that is associated with the TRLE definition. This value is one of the addresses that was specified on the DATAPATH parameter on the TRLE definition and is the subchannel address that VTAM assigned to this interface. If VTAM has not yet assigned a subchannel address to this interface, then this field contains the value Unknown. This field is significant only for IPAQENET, IPAQIDIO, IPAQENET6, and IPAQIDIO6 interfaces.

DatapathStatus

The datapath status. This field is significant only for IPAQENET, IPAQIDIO, IPAQENET6 , and IPAQIDIO6 interfaces. This field contains information that is useful if the interface is not activating correctly. See Table 1 for possible status values.

CHPIDType

The CHPID type that is associated with this interface. This value was specified on the CHPIDTYPE parameter on the INTERFACE statement (or was generated by the stack) for OSA-Express QDIO interfaces. This field is significant only for IPAQENET and IPAQENET6 interfaces. The possible values and meanings are:

OSD

A CHPID with connectivity to the external data network

OSX

A CHPID with connectivity to the intra ensemble data network

OSM

A CHPID with connectivity to the intra node management network

IPAddr

The IP address and optional number of bits (leftmost significant bits), which identifies the subnet mask of the interface. This value was specified on the IPADDR parameter on the INTERFACE statement. This field is significant for IPAQENET interfaces only. If the interface is defined with the TEMPIP keyword, the IP address is 0.0.0.0.

CHPID

The CHPID value that is associated with this interface. For HiperSockets, this value was specified on the CHPID parameter on the INTERFACE statement for predefined HiperSockets interfaces or is the value obtained from VTAM for HiperSockets interfaces that are created by dynamic XCF definitions. For OSA-Express QDIO interfaces that are configured with CHPIDTYPE OSX, this value was specified on the CHPID parameter. This field is significant only for IPAQIDIO6, IPAQENET, or IPAQENET6 interfaces.

SMCR

Indicates whether this interface can be used for new TCP connections for Shared Memory Communications over Remote Direct Memory Access (SMC-R) for external data network communications. This value was specified on the SMCR or NOSMCR parameter on the INTERFACE statement for OSA-Express QDIO interfaces. This field is significant only for IPAQENET and IPAQENET6 interfaces. The possible values and meanings are:

YES

Indicates that this interface can be used for new TCP connections to communicate with other stacks on the external data network by using SMC-R.

For an inactive interface, Yes means the interface is configured for SMC-R. An interface is configured for SMC-R when the SMCR parameter was specified on the INTERFACE statement or is in effect by default.

For an active interface, Yes means the interface is enabled for SMC-R. An interface is enabled for SMCR when the following conditions are true:

• The SMCR parameter was specified on the INTERFACE statement or is in effect by default.
• The TCP/IP stack is enabled for SMC-R. A TCP/IP stack is enabled for SMC-R when the SMCR parameter was specified on the GLOBALCONFIG statement.
• A physical network ID value was configured in HCD for this interface.

NO

Indicates that this interface cannot be used for new TCP connections to communicate with other stacks on the external data network by using SMC-R. The NOSMCR parameter was specified on the INTERFACE statement.

Disabled (reason_text)

Indicates that this interface was configured to communicate with other stacks on the external data network by using SMC-R, but SMC-R cannot be used for new TCP connections because of one of the following reasons:

No PNetID

No physical network ID value was configured in HCD for this interface. The physical network ID is learned during interface activation so this reason text is only valid for an active interface.

GLOBALCONFIG NOSMCR

The TCP/IP stack was not enabled for SMC-R.

No Subnet Mask

No subnet mask was configured on the INTERFACE statement for this interface.

PFID

The Peripheral Component Interconnect Express (PCIe) function ID (PFID) value that defines an 10GbE RoCE Express feature. This value is specified on the SMCR PFID parameter of the GLOBALCONFIG TCP/IP profile statement. This field is significant only for RNIC interfaces that are created when an IPAQENET or IPAQENET6 interface specifies SMCR or takes SMCR as the default setting.

PortNum

Specifies the 10GbE RoCE Express port number that is used for the associated PFID. The PortNum value is specified with the PFID value on the SMCR parameter of the GLOBALCONFIG statement in the TCP/IP profile.

PNetID

The physical network ID value that is configured in HCD for an interface. This field is significant only for IPAQENET interfaces defined by using the INTERFACE statement, IPAQENET6 interfaces, and active RNIC interfaces.

Interface	Value
Active OSD interfaces	If a physical network ID is configured in HCD for the OSD interface, the configured value is displayed. If no physical network ID is configured in HCD for the OSD interface, the value*None* is displayed. If the OSD interface is configured to use SMCR, a value of Disabled (No PNetID) is displayed in the SMCR field.
Active OSX interfaces	The reserved value IEDN is used.
Active RNIC interfaces	The value that is configured in HCD for the RNIC interface is displayed. If no value is configured in HCD, activation of the RNIC interface fails.

TRLE

The name of the TRLE that is associated with this interface. This field is significant only for MPCPTP6, IPAQIDIO, IPAQIDIO6 and RNIC interfaces.

For MPCPTP6 interfaces

This value was specified on the TRLE parameter of the INTERFACE statement for predefined MPC interfaces or is the value obtained from VTAM for MPC interfaces that are created by dynamic XCF definitions.

For IPAQIDIO or IPAQIDIO6 interfaces

This value is obtained from VTAM for IPAQIDIO or IPAQIDIO6 interfaces that INTERFACE definitions create. This value is displayed for active interfaces only.

For RNIC interfaces

This value is obtained from VTAM for RNIC interfaces that are created for PFIDs configured on the GLOBALCONFIG statement when SMC-R is enabled. This value is displayed only when the PFIDStatus value of the interface is Starting or Ready.

PFIDStatus

This field is the RNIC interface PFID status. The following list describes several status values:

PFID status	Description
Ready	The initialization sequence with the PFID is complete. The PFID is ready.
Not Active	The PFID is not active. The PFID has never been started, or has been stopped after having been started.
Starting	A START command of the PFID has been issued, and TCP/IP has sent an Activation request to the Data Link Control (DLC) layer.
Deactivating	DLC has performed the first stage of an orderly PFID deactivation.

GidAddr

The group identifier (GID) value that is associated with the RNIC interface. This value is obtained from VTAM for RNIC interfaces that are created for PFIDs configured on the GLOBALCONFIG statement when SMC-R is enabled. This value is displayed for active RNIC interfaces only.

NetNum

The adapter number that was specified on the LINK statement. This field is significant only for CTC and LCS links.

QueSize

The queue size represents the number of outbound packets for this link or interface that are queued and waiting for ARP or neighbor resolution. This field is significant only for links on ATM and LCS devices and for IPAQENET6 interfaces.

Speed

Indicates the interface speed (in million bits per second) that is reported by the device. This field is significant only for IPAQENET links or interfaces, ATM and IPAQTR links, and IPAQENET6 interfaces, and only if the link or interface is active.

MAC address order (MacAddrOrder)

Indicates the canonical option (CANON/NONCANON) that is specified on the LINK statement. This field is significant only for token-ring links.

SrBridgingCapability

Indicates whether the link supports source route bridging. This field is significant only for token-ring links.

IpBroadcastCapability

Indicates whether the link is broadcast capable. This field is significant only for links on LCS and MPCIPA devices and IPAQENET interfaces.

ArpBroadcastType

Indicates the ARP broadcast option (ALLRINGSBCAST/LOCALBCAST) that is specified on the LINK statement. This field is significant only for token-ring links.

ArpOffload

Indicates whether ARP processing is being offloaded to the adapter. This field is significant only for active links that support ARP offload.

ArpOffloadInfo

Indicates whether the adapter reports ARP offload data to TCP/IP. If so, then the ARP cache data can be displayed with the Netstat ARP/-R report even though the ARP function is being offloaded. This field is significant only for active links that support ARP offload.

Routing Parameters

This section displays routing information for IPv4 links that are defined with the DEVICE and LINK profile statements.

MTU Size

This value is determined in one of the following ways:

• If you are using OMPROUTE and the link is defined to OMPROUTE, the value might have been specified on the MTU parameter on the OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE statement for the link. If one of these OMPROUTE statements was specified for the link but the MTU parameter was not specified, OMPROUTE sets the MTU Size value to 576.
• If you are using OMPROUTE, the link is not defined to OMPROUTE, and OMPROUTE is not configured to ignore undefined links, OMPROUTE sets the MTU Size value to 576.
• If you are not using OMPROUTE (or if the link is not defined to OMPROUTE), OMPROUTE is configured to ignore undefined links, and a BSDROUTINGPARMS profile statement was specified for the link, then the MTU Size value is configured using the BSDROUTINGPARMS profile statement MTU parameter.
• If none of the previously described methods provides an MTU Size value or if the MTU Size parameter does not apply to this link, then the value n/a is displayed.

To determine the MTU Size value that is being used by the stack for a link, see the ActMtu field for the link. To determine the MTU Size value that is being used for a route over this link, see the MTU field on the Netstat ROUTe/-r report.

Metric

The routing metric that is associated with the link. This value is determined in one of the following ways:

• If you use OMPROUTE and the link is defined to OMPROUTE using the OSPF_INTERFACE statement, then the Metric value is configured using the Cost0 parameter on the OSPF_INTERFACE statement. If the Cost0 parameter is not specified, then OMPROUTE sets the value to 1.
• If you use OMPROUTE and the link is defined to OMPROUTE using the RIP_INTERFACE statement, then the Metric value is configured using the In_Metric parameter on the RIP_INTERFACE statement. If the In_Metric parameter is not specified, then OMPROUTE sets the value to 1.
• If you use OMPROUTE and the link is defined to OMPROUTE using the INTERFACE statement or if the link is not defined to OMPROUTE and OMPROUTE is not configured to ignore undefined links, then OMPROUTE sets the Metric value to 0.
• If you are not using OMPROUTE (or if the link is not defined to OMPROUTE) and OMPROUTE is configured to ignore undefined links, the Metric value is configured in one of the following ways:
  • For dynamic XCF links, the Metric value is configured using the cost_metric value of the DYNAMICXCF parameter on the IPCONFIG profile statement.
  • If a BSDROUTINGPARMS profile statement was specified for the link, the Metric value is configured using the cost_metric parameter of BSDROUTINGPARMS profile statement.
• If none of the previously described methods provided a Metric value, the stack sets the value to 0

DestAddr

The destination address applies to point-to-point links only and is the IP Address of the other side of the point-to-point link. This value is determined in one of the following ways:

• If you are using OMPROUTE and the link is defined to OMPROUTE, then the value is configured using the Destination_Addr parameter on the OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE statement. If the Destination_Addr parameter is not specified, then OMPROUTE sets the value to 0.
• If you are using OMPROUTE but the link is not defined to OMPROUTE and OMPROUTE is not configured to ignore undefined links, then OMPROUTE sets the value to 0.
• If you are not using OMPROUTE (or if the link is not defined to OMPROUTE), OMPROUTE is configured to ignore undefined links, and a BSDROUTINGPARMS profile statement was specified for the link, then the value is configured using the dest_addr parameter for this statement.
• If none of these methods has provided a destination address value, then the stack sets a default value in one of the following ways:
  • For links other than point-to-point links, the value is set to 0.
  • For point-to-point links, the value is set as follows:
    • If routes are defined over the link, then the stack sets the value using the gateway address of an indirect route or the destination address of a direct host route.
    • If no routes are defined over the link, then the value is set to 0.

SubnetMask

The subnet mask that is associated with the link. This value is determined in one of the following ways:

• If you are using OMPROUTE and the link is defined to OMPROUTE, then the value is configured using the Subnet_Mask parameter on the OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE statement.
• If you are using OMPROUTE, the link is not defined to OMPROUTE, and OMPROUTE is not configured to ignore undefined links, then OMPROUTE assigns a value based on the IP address that is assigned to the link.
• If you are not using OMPROUTE (or if the link is not defined to OMPROUTE) and OMPROUTE is configured to ignore undefined links, then the value is assigned in one of the following ways:
  • For dynamic XCF links, the value is configured using the subnet_mask or num_mask_bits value of the DYNAMICXCF parameter on the IPCONFIG profile statement.
  • For dynamic VIPA links, the value is configured using the address_mask parameter on the VIPADEFINE, VIPABACKUP, or the VIPARANGE profile statement.
  • If a BSDROUTINGPARMS profile statement was specified for the link, the value is configured using the subnet_mask parameter for the BSDROUTINGPARMS profile statement.
• If none of the previously described methods provides a subnet mask value, then the stack assigns a value based on the IP address that is assigned to the link.

Packet trace settings

Use the PKTTRACE statement to control the packet tracing facility in TCP/IP. You can use this statement to select IP packets as candidates for tracing and subsequent analysis. An IP packet must meet all of the conditions specified on the statement for it to be traced.

Protocol

The protocol number from the PROT keyword of the PKTTRACE command or * if not specified.

TrRecCnt

The number of packets traced for this PKTTRACE command.

PckLength

The value of the ABBREV keyword of the PKTTRACE command or FULL to capture the entire packet.

SrcPort

The port number from the SRCPORT parameter of the PKTTRACE command or profile statement. If an asterisk (*) is displayed, then either a port number was not specified for the SRCPORT parameter, or the PORTNUM parameter was also specified. If both the SrcPort and PortNum fields contain a value *, then the IP packets are not being filtered by the source port.

DestPort

The port number from the DESTPORT parameter of the PKTTRACE command or profile statement. If an asterisk (*) is displayed, then either a port number was not specified for the DESTPORT parameter, or the PORTNUM parameter was also specified. If both the DestPort and PortNum fields contain an asterisk (*), then the IP packets are not being filtered by destination port.

PortNum

The port number from the PORTNUM parameter of the PKTTRACE command or profile statement. If an asterisk (*) is displayed, then either a port number was not specified for the PORTNUM parameter, or the DESTPORT or SRCPORT parameters were also specified. If the PortNum, SrcPort, and DestPort fields all contain an asterisk (*), then the IP packets are not being filtered by port.

Discard

The value specified for the PKTTRACE DISCARD parameter. A numerical value is a discard reason code. The value NONE, which is the default, indicates that only packets that were delivered are being traced. The value ALL indicates that only discarded IP packets are being traced. The value asterisk (*) indicates that discarded IP packets and delivered IP packets are being traced.

IpAddr

The IP address from the IPADDR keyword of the PKTTRACE command or asterisk (*) if not specified.

SubNet

The IP subnet mask from the SUBNET keyword of the PKTTRACE command or asterisk (*) if not specified.

ATM Specific

This section contains information about ATM links:

ATM PortName

The PORTNAME value specified on the DEVICE statement.

For an ATM link configured as a Permanent Virtual Circuit (PVC), the following additional fields are displayed:

ATM PVC Name

The name of the PVC specified on the ATMPVC statement.

PVC Status

This field can have the following values:

ATM PVC status	Description
Not Active	The PVC is not active. There is no command to start a PVC; PVC activation is normally attempted during START device processing. A PVC is marked Not Active when: The device has not yet been started. The remote side of the PVC is not active. A failure has been encountered during the PVC activation phase. (Such a failure produces an error message to the operator.)
Ready	The initialization sequence for the PVC is complete. The PVC is now ready for use.

For an ATM link configured as a Switched Virtual Circuit (SVC), the following additional fields are displayed:

ATM LIS Name

The name of the ATM Logical IP Subnet (LIS) specified on the ATMLIS statement.

SubnetValue

The subnet_value specified on the ATMLIS statement.

SubnetMask

The subnet_mask specified on the ATMLIS statement.

DefaultMTU

The DFLTMTU value specified on the ATMLIS statement.

InactvTimeOut

The INACTVTO value specified on the ATMLIS statement.

MinHoldTime

The MINHOLD value specified on the ATMLIS statement.

MaxCalls

The maximum number of SVCs that can be active for this ATMLIS.

CachEntryAge

The CEAGE value specified on the ATMLIS statement.

ATMArpReTry

The ARPRETRIES value specified on the ATMLIS statement.

ATMArpTimeOut

The ARPTO value specified on the ATMLIS statement.

PeakCellRate

The PEAKCR value specified on the ATMLIS statement.

NumOfSVCs

The number of currently active SVCs for this ATMLIS.

BearerClass

The BEARERCLASS value specified on the ATMLIS statement.

For an ATM SVC link that is configured with an ATM ARP server, the following additional fields are displayed:

ATMARPSV Name

The name of the ATM ARP server specified on the ATMARPSV statement.

VcType

Indicates whether the ATM ARP server connection is a PVC or an SVC. This value comes from the ATMARPSV statement.

ATMaddrType

The ATM address type specified on the ATMARPSV statement. The only supported value is NSAP.

ATMaddr

The ATM address of the ATM ARP server. If the connection to the ATM ARP server is an SVC, then this is the physical_addr value specified on the ATMARPSV statement. For a PVC connection to the ATM ARP server, this is the remote ATM address learned by TCP/IP when the PVC was activated.

IpAddr

The IP address of the ATM ARP server. If the connection to the ATM ARP server is an SVC, then this is the ip_addr value specified on the ATMARPSV statement. For a PVC connection to the ATM ARP server, this is the remote IP address learned by TCP/IP when the PVC was activated.

Multicast Specific

This section displays multicast information for the link or interface.

Multicast Capability

Indicates whether the link or interface is multicast capable.

• For point-to-point interfaces, the value of this field is always Yes.
• For LCS and MPCIPA links and IPAQENET, IPAQENET6, IPAQIDIO, and IPAQIDIO6 interfaces, the multicast capability is known only after the link or interface is active. If the link or interface is not active, the multicast capability value is Unknown.
• For IPAQIQDX6 interfaces, the value of this field is always ND only, the interface is multicast capable but multicast processing is used only for neighbor discovery.

If the link or interface is multicast capable then the following additional fields are displayed for each multicast group for which the link or interface is receiving data. There is no limit to the number of multicast groups for which a link or interface can receive data. For IPAQIQDX6 interfaces, the multicast groups indicate only neighbor discovery processing.

Group

The multicast group address for which this link or interface is receiving data.

RefCnt

The number of applications that are receiving data for this multicast group.

SrcFltMd

The source filter mode indicates the type of multicast source IP address filtering that has been configured at the interface. Source IP address filtering can be done by either an IGMPv3 or MLDv2-capable multicast router on a per interface basis or by the host on a per socket basis. The host provides its source filter mode and source IP address filter list for each multicast group that an application has joined on the interface with any IGMPv3 and MLDv2-capable multicast routers that are connected to the interface. This permits IGMPv3-capable and MLDv2-capable multicast routers to send only multicast packets that have been requested by at least one host on the subnet to which the interface is connected. If the multicast packets are not filtered by an IGMPv3-capable or MLDv2-capable multicast router (for example the router does not support IGMPv3 or MLDv2), or if there are multiple hosts on the local area network that have either a different source filter mode or a different source IP address filter list for a given multicast group, the host uses the source IP address filter information to ensure that each application receives only packets that it has requested.

The value is either Include or Exclude. A source filter applies only to incoming multicast data. The source filter applies to all the IP addresses in the SrcAddr fields for the associated multicast group address and the link or the interface. The source filter mode and the corresponding source filter IP addresses are configured by applications for their UDP or RAW sockets that have joined the multicast group for this interface. See the information about Designing multicast programs in the z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference for details about how applications configure these values for a socket.

Include

Indicates that the interface or link receives only multicast datagrams that have a source IP address that matches an IP address indicated in the SrcAddr field.

Exclude

Indicates either that the source filter function is not active or that the interface or link receives only multicast datagrams that have a source IP address that does not match an IP address indicated in the SrcAddr field. If the source filter function is not active or if the source filter function is active but no SrcAddr value is set, the SrcAddr field contains the value None.

SrcAddr

Source address information for the socket.

ipaddr

The source IP address that is used in conjunction with the SrcFltMd value to determine which incoming multicast datagrams are received by the interface.

None

This value is displayed only when the source filter function is not configured for the interface or when the source filter mode is Exclude but there was no intersection of excluded source IP addresses among the sockets for the same multicast group address and interface.

Source VIPA interface (SrcVipaIntf)

The name of the VIPA that is used for this interface if source VIPA is in effect. This is the value that was specified on the SOURCEVIPAINTERFACE parameter on the INTERFACE statement. This field is significant only for IPAQENET, IPAQENET6, IPAQIDIO6, and MPCPTP6 interfaces.

Duplicate address detection (DupAddrDet)

The DUPADDRDET value specified on the INTERFACE statement. This field is significant only for IPAQENET6 interfaces.

Interface ID (IntfID)

The INTFID value specified on the INTERFACE statement. This field is significant only for IPAQENET6, IPAQIDIO6, and MPCPTP6 interfaces.

MAC address (MacAddress)

The local hardware address for this link or interface. This field is significant only for links on LCS devices and for IPAQENET6 interfaces. This field is displayed only if the link or interface is active and if virtual MAC (VMAC) is not configured.

Router Hop Limit (RtrHopLimit)

The value that is placed in the Hop Count field of the IP header for outgoing IP packets. This value was obtained from a received router advertisement and is significant only for IPAQENET6 interfaces. This field is displayed only when a nonzero hop limit value was received in a router advertisement over this interface and IGNOREROUTERHOPLIMIT is not configured on the IPCONFIG6 profile statement.

CfgMtu

The MTU value that was configured on the INTERFACE statement (or None if an MTU value was not configured). This field is significant only for IPAQENET, IPAQENET6, or IPAQIDIO interfaces.

ActMtu

The largest MTU that is supported by an active link or interface. If the link or interface is inactive, then this field displays Unknown. This field is significant for all links and interfaces except virtual ones.

VLANid

This field is significant only for IPAQENET links or interfaces, IPAQIDIO links, or IPAQENET6 and IPAQIDIO6 interfaces. This field indicates whether a virtual LAN ID was configured on the VLANID parameter on the LINK or INTERFACE profile statement. The following values can be displayed in this field:

None

This value indicates that the VLANID parameter was not specified on the LINK or INTERFACE profile statement for the interface. For an IPAQIDIO link or IPAQIDIO6 interface that is dynamically generated as part of dynamic XCF HiperSockets processing, this value indicates that the IQDVLANID parameter was not specified on the GLOBALCONFIG profile statement.

n/a

This value indicates that the VLANID parameter was specified on the LINK or INTERFACE profile statement, but the interface does not support VLAN IDs.

vlanid

If an OSA-Express device is active and supports virtual LAN IDs, this field indicates that all IP packets through this OSA-Express link or interface from this stack are being tagged with this VLAN ID. For an active HiperSockets link or interface that supports virtual LAN IDs, this field indicates that all IP packets through this HiperSockets link or interface from this stack are associated with this VLAN ID.

VLANpriority

This field is significant only for active IPAQENET links or interfaces or IPAQENET6 interfaces. This field indicates whether all IP packets through this OSA-Express link or interface from this stack are being tagged with a VLAN priority. The possible values are:

Enabled

Indicates that all IP packets through this OSA-Express link or interface are being tagged with a VLAN priority. See z/OS Communications Server: IP Configuration Reference for information about the SetSubnetPrioTosMask statement and details about how to configure VLAN priorities.

Disabled

Indicates that the OSA-Express link or interface supports VLAN priority, but currently no VLAN priority values are defined. If the VLANid field displays None or n/a, all IP packets through this OSA-Express link or interface are not VLAN tagged. All other values indicate that all IP packets are VLAN tagged, but only with VLAN IDs, not with VLAN priority.

Unknown

Indicates that the VLAN priority tagging support for the OSA-Express is unknown because the link or interface is not yet active.

DynVLANRegCfg

This field is significant only for IPAQENET links or interfaces and IPAQENET6 interfaces. This field is displayed only under the following conditions:

• The link or interface is not yet active and a VLAN ID was specified.
• The link or interface is active, a VLAN ID value was specified, and the OSA-Express feature has accepted the VLAN ID value.

This field indicates whether dynamic VLAN ID registration was configured on the LINK or INTERFACE statement. The possible values are:

Yes

Indicates that the DYNVLANREG parameter was specified on the LINK or INTERFACE statement.

No

Indicates that the NODYNVLANREG parameter was specified on the LINK or INTERFACE statement or is in effect by default.

DynVLANRegCap

This field indicates whether the OSA-Express feature that is represented by the LINK or INTERFACE statement is capable of supporting dynamic VLAN ID registration.

This field is significant only for IPAQENET links or interfaces and IPAQENET6 interfaces. This field is displayed only under the following conditions:

• The link or interface is not yet active and a VLAN ID was specified.
• The link or interface is active, a VLAN ID value was specified, and the OSA-Express feature has accepted the VLAN ID value.

The possible values are:

Yes

Indicates that the OSA-Express feature is capable of supporting dynamic VLAN ID registration.

No

Indicates that the OSA-Express feature is not capable of supporting dynamic VLAN ID registration.

Unknown

Indicates that the dynamic VLAN ID registration capability of the OSA-Express feature is unknown because the link or interface is not yet active.

ChecksumOffload

This field is significant only for active IPAQENET and IPAQENET6 links or interfaces. This field indicates whether the checksum offload support is in effect and is displayed only when the link or interface is active. The possible values are:

Yes

Indicates that the checksum offload function is enabled on the adapter for this interface.

No

Indicates that the checksum offload function is not enabled on the adapter for this interface.

Unsupported

Indicates that the checksum offload function is not supported on the adapter for this interface.

SegmentationOffload

This field is significant only for active IPAQENET and IPAQENET6 links or interfaces. This field indicates whether the TCP segmentation offload support is in effect and is displayed only when the link or interface is active. Possible values are:

Yes

Indicates that the segmentation offload function is enabled on the adapter for this interface.

No

Indicates that the segmentation offload function is not enabled on the adapter for this interface.

Unsupported

Indicates that the segmentation offload function is not supported on the adapter for this interface.

SecClass

This field identifies the security class value for IP filtering. This field applies to all IPv4 and IPv6 interfaces except virtual and loopback, but the value is in effect only if the IPSec function is active for the applicable IP version. You can use the Netstat CONFIG/-f command to determine whether IPSec is active. Valid security class values are in the range 1 - 255. The displayed value was defined by one of the following methods:

• By the SECCLASS parameter on the LINK or INTERFACE profile statement
• For dynamic XCF interfaces, by the DYNAMICXCF SECCLASS subparameter on the IPCONFIG or IPCONFIG6 profile statement
• For OSM interfaces, by the TCP/IP stack's automatic configuration of the interface, or by the IPSECURITY OSMSECCLASS subparameter on the IPCONFIG6 profile statement

MonSysplex

Indicates whether the status of this link or interface is being monitored by Sysplex Autonomics. This field is significant for all IPv4 links or interfaces except virtual, loopback, and all dynamically configured links, and for all IPv6 interfaces except virtual, loopback, and all dynamically configured interfaces.

Yes

Indicates that the status of this link or interface is being monitored by Sysplex Autonomics. It is configured by specifying the MONSYSPLEX keyword on the LINK or INTERFACE profile statement and specifying the MONINTERFACE keyword for the SYSPLEXMONITOR parameter on the GLOBALCONFIG profile statement. If DYNROUTE keyword is also coded on the GLOBALCONFIG SYSPLEXMONITOR profile statement, then the presence of dynamic routes over this link or interface is also monitored.

Configured

Indicates that this link or interface was configured to be monitored by Sysplex Autonomics. It was configured by specifying the MONSYSPLEX keyword on the LINK or INTERFACE profile statement, but the link or interface is not currently being monitored because the MONINTERFACE keyword was not specified on the SYSPLEXMONITOR parameter on the GLOBALCONFIG profile statement.

No

Indicates that the status of this link or interface is not being monitored by Sysplex Autonomics because the MONSYSPLEX keyword was not specified on the LINK or INTERFACE profile statement.

Isolate

This field is significant only for IPAQENET interfaces (defined using the INTERFACE statement) and for IPAQENET6 interfaces. This field ndicates whether the OSA-Express device is prevented from routing packets directly to another stack that is sharing the OSA-Express connection. For more details, see OSA-Express connection isolation information in z/OS Communications Server: IP Configuration Guide.

No

Indicates that this interface is eligible for OSA-Express direct routing. Therefore, the OSA-Express device can route packets directly to another stack that is sharing the OSA-Express connection (as long as the interface from the other stack is also eligible for direct routing).

Yes

Indicates that this interface is not eligible for OSA-Express direct routing. Therefore, the OSA-Express device cannot routing packets directly to another stack that is sharing the OSA-Express connection.

OptLatencyMode

This field is significant only for IPAQENET interfaces (defined using the INTERFACE statement) and for IPAQENET6 interfaces. The field indicates whether optimized latency mode (OLM) was configured for this OSA-Express interface. For more information about optimized latency mode, see optimized latency mode information in z/OS Communications Server: IP Configuration Guide. Possible values are:

No

Indicates that the OSA-Express interface is not configured with optimized latency mode.

Yes

Indicates that the OSA-Express interface is configured with optimized latency mode. Optimized latency mode optimizes interrupt processing for both inbound and outbound data.

Disabled

Indicates that the OSA-Express interface was configured with optimized latency mode, but the function could not be enabled when the interface was activated. The most likely reason is that the OSA-Express interface does not support this function.

IQDMultiWrite

This field is significant only for active HiperSockets devices or interfaces. This field indicates whether the HiperSockets multiple write facility is currently being used for the device or interface. To configure the stack to use the HiperSockets multiple write facility, specify the IQDMULTIWRITE parameter on the GLOBALCONFIG profile statement. The possible values are:

Enabled

Indicates that the HiperSockets multiple write facility is currently being used for the device or interface.

Enabled (ZIIP)

Indicates that the HiperSockets multiple write facility is currently being used for the device or interface. Additionally, CPU cycles that are associated with the HiperSockets multiple write facility are to be displaced to an available zIIP.

Disabled

Indicates that the HiperSockets multiple write facility is not currently being used for the device or interface.

Unsupported

Indicates that the IBM® System z® environment does not support the HiperSockets multiple write facility.

ReadStorage

This field is significant only for active IPAQENET and IPAQIDIO links or interfaces, IPAQTR links, and for IPAQIDIO6 and IPAQENET6 interfaces. This field indicates the amount of storage (in kilobytes) that is being used for read processing.

InbPerf

This field is significant only for IPAQENET links or interfaces, IPAQTR links, and IPAQENET6 interfaces. This field indicates how frequently the adapter interrupts the host. This field indicates how the processing of inbound traffic is performed. If the interface is not active, then this field shows the configured value. If the interface is active, then this field shows the value that is in effect. The possible values are:

Balanced

Indicates that the adapter is to use a static interrupt-timing value that strikes a balance between MinCPU and MinLatency.

Dynamic

This setting is significant only for IPAQENET links, and IPAQENET and IPAQENET6 interfaces. It indicates that the stack and the adapter are to dynamically update the frequency with which the adapter interrupts the host for inbound traffic.

WorkloadQueueing

This field is displayed only for IPAQENET and IPAQENET6 interfaces. It indicates whether QDIO inbound workload queueing is enabled. Possible values are:

Yes

QDIO inbound workload queueing is in effect. The QDIO interface is defined using the INTERFACE statement with INBPERF DYNAMIC WORKLOADQ specified.

No

QDIO inbound workload queueing is not in effect. The QDIO interface is defined using the INTERFACE statement with INBPERF DYNAMIC or INBPERF DYNAMIC NOWORKLOADQ specified.

Unsupported

QDIO inbound workload queueing was requested on the INTERFACE statement but the OSA-Express interface does not support it. QDIO inbound workload queueing is supported on OSA-Express3 or later features on an IBM System z10™ GA3 or later CPC.

MinCPU

Indicates that the adapter is to use a static interrupt-timing value that minimizes host interrupts, and therefore minimizes host CPU consumption.

MinLatency

Indicates that the adapter is to use a static interrupt-timing value that minimizes latency delay by more aggressively presenting received packets to the host.

TempPrefix

This field is significant only for IPAQENET6 interfaces with stateless address autoconfiguration enabled. One or more TempPrefix fields are displayed. Together the TempPrefix fields indicate the set of prefixes for which temporary IPv6 addresses can be generated, if temporary addresses are enabled on the IPCONFIG6 statement. The set of prefixes is specified on the TEMPPREFIX parameter on the INTERFACE statement. The possible values displayed are:

All

IPv6 temporary addresses are generated for all prefixes that are learned from a router advertisement over this interface. This is the default.

Disabled

Autoconfiguration of temporary addresses for the interface is disabled because duplicate addresses were detected. Temporary addresses are not generated for this interface.

None

Temporary addresses are not generated for this interface.

IPv6 prefix/prefix length

IPv6 temporary addresses are generated for all prefixes that are learned from a router advertisement over this interface and that are included in one of the prefixes in this prefix list.

Link/Interface Statistics

This section is significant for all links and interfaces except virtual ones. The following statistical information is displayed:

BytesIn

Number of bytes received over an interface.

Inbound Packets

The number of unicast inbound packets received over an interface. This value applies to all links and interfaces except for RNIC interfaces.

Inbound Packets In Error

Number of inbound packets discarded because of an error validating the packet. This value applies to all links and interfaces except for RNIC interfaces.

Inbound Packets Discarded

Number of inbound packets discarded because of an out-of-storage condition. This value applies to all links and interfaces except for RNIC interfaces.

Inbound Packets With No Protocol

Number of inbound packets discarded because of an unknown protocol type. This value applies to all links and interfaces except for RNIC interfaces.

BytesOut

Number of bytes transmitted over an interface.

Outbound Packets

The number of unicast outbound packets transmitted over an interface. This value applies to all links and interfaces except for RNIC interfaces.

Outbound Packets In Error

Number of outbound packets discarded because of errors other than an out-of-storage condition. This value applies to all links and interfaces except for RNIC interfaces.

Outbound Packets Discarded

Number of outbound packets discarded because of an out-of-storage condition. This value applies to all links and interfaces except for RNIC interfaces.

Inbound Operations

Number of Remote Direct Memory Access (RDMA) inbound operations processed across this interface. This value applies to RNIC interfaces only.

Outbound Operations

Number of RDMA outbound operations processed across this interface. This value applies to RNIC interfaces only.

SMC Links

Current number of SMC-R links between this stack and other stacks across this interface. This value applies to RNIC interfaces only.

TCP Connections

Number of TCP connections across all the SMC-R links that are associated with this interface. One or more TCP connections can use the same SMC-R link. This value applies to RNIC interfaces only.

Intf Receive Buffer Inuse

Amount of RMB storage in use by the TCP connections that are using the SMC-R links associated with this interface. This value applies to RNIC interfaces only.

IPv4 LAN Group Summary

The IPv4 LAN group summary lists links or interfaces that are takeover candidates for each other. The stack creates a LAN group when it detects redundant connectivity to a LAN. For each link or interface in the LAN group, this summary displays which link or interface owns ARP responsibility for that link or interface. The summary also displays which link or interface owns the ARP responsibility in the LAN group for any VIPAs.

IPv6 LAN Group Summary

The IPv6 LAN group summary lists interfaces that are takeover candidates for each other. The stack creates a LAN group when it detects redundant connectivity to a LAN. For each interface in the LAN group, this summary displays which interface owns neighbor discovery (ND) address resolution responsibility for that interface. The summary also displays which interface owns the ND Address Resolution responsibility in the LAN group for any VIPAs.

LanGroup

Identifies the LAN group. This identifier is assigned by the stack and represents a group of interfaces on the same LAN. This identifier is not a VLAN ID.

Name

The link name configured on the LINK statement or the interface name configured on the INTERFACE statement.

Status

The link or interface status. Valid values are Active or Not Active.

ArpOwner

The link or interface name that owns ARP responsibility for this link or interface in the LAN group. An active link or interface owns its ARP responsibility.

NDOwner

The interface name that owns neighbor discovery (ND) responsibility for this interface in the LAN group. An active interface owns its ND responsibility.

VipaOwner

Indicates whether the link or interface owns the ARP or ND responsibility for the VIPAs in the LAN group.

Associated IQDX Interface

The name of the Internal Queued Direct I/O extensions function (IQDX) interface that is associated with this OSX interface. This section is significant for OSX interfaces that use an IQDX interface for intraensemble data network (IEDN) connectivity. The following information is displayed:

IQDX Status

The status of the IQDX interface. See the description of the LnkStatus/IntfStatus field for the possible interface status values.

BytesIn

The number of bytes that have been received over the associated IQDX interface.

Inbound Packets

The number of unicast inbound packets that have been received over the associated IQDX interface.

BytesOut

The number of bytes that have been transmitted over the associated IQDX interface.

Outbound Packets

The number of unicast outbound packets that have been transmitted over the associated IQDX interface.

Associated RNIC Interface

The dynamic interface name that is generated for 10GbE RoCE Express interface that this stack uses for SMC-R communications. This field is significant only for active IPAQENET and IPAQENET6 interfaces that specify SMCR or take SMCR as the default value.

SMC Link Information

The SMC link information. This section is displayed for each RNIC interface only when the SMC modifier or the SMCID/-U filter is specified. The following fields and statistics are displayed.

Guideline: An SMC-R link is uniquely identified by the combination of the VLAN number, local GID, local VMAC address, local QP number, remote GID, remote VMAC address, and remote QP number.

LocalSMCLinkId

The SMC-R link identifier that this TCP/IP stack dynamically creates to represent the link.

RemoteSMCLinkId

The SMC-R link identifier that the remote peer uses to represent the link. The value is provided to this TCP/IP stack during link activation.

SMCLinkGroupId

The group identifier that this TCP/IP stack dynamically creates to represent the SMC-R link group that includes this individual link.

VLANid

The virtual LAN ID for this SMC-R link. The value None is displayed if a virtual LAN ID has not been configured.

MTU

The negotiated MTU size that is used for this SMC-R link.

LocalGid

The local GID value that is associated with this SMC-R link. This is the same information that is displayed in the GidAddr field.

LocalMACAddr

The local virtual MAC address that is associated with this SMC-R link.

LocalQP

The local queue pair (QP) value that is associated with this SMC-R link.

RemoteGid

The peer GID value that is associated with this SMC-R link.

RemoteMACAddr

The peer virtual MAC address that is associated with this SMC-R link.

RemoteQP

The peer QP value that is associated with this SMC-R link.

SMCLinkBytesIn

Number of inbound data bytes transferred across this SMC-R link.

SMCLinkInOperations

Number of Remote Direct Memory Access (RDMA) inbound operations processed across this SMC-R link.

SMCLinkBytesOut

Number of outbound data bytes transferred across this SMC-R link.

SMCLinkOutOperations

Number of RDMA outbound operations processed across this SMC-R link.

TCP Connections

Number of TCP connections across this SMC-R link.

Link Receive Buffer Inuse

Amount of RMB storage in use by the active TCP connections that are associated with this SMC-R link.

32K Buffer Inuse

Amount of 32K RMB storage in use by the active TCP connections that are associated with this SMC-R link.

64K Buffer Inuse

Amount of 64K RMB storage in use by the active TCP connections that are associated with this SMC-R link.

128K Buffer Inuse

Amount of 128K RMB storage in use by the active TCP connections that are associated with this SMC-R link.

256K Buffer Inuse

Amount of 256K RMB storage in use by the active TCP connections that are associated with this SMC-R link.

Other Buffer Inuse

For RMB storage that is allocated as buffers larger than 256K, the amount of these other buffers that are in use by the active TCP connections that are associated with this SMC-R link. If no buffers larger than 256K are allocated, this information is not displayed.

OSA-Express Network Traffic Analyzer Information

This section displays all currently defined OSA interfaces that are dynamically created by VARY TCPIP,,OSAENTA commands or OSAENTA PROFILE statements.

OSA PortName

The port name value of the OSA that is currently defined for performing the OSA-Express network traffic analyzer (OSAENTA) function. This value was specified on the PORTNAME parameter of a VARY TCPIP,,OSAENTA command or on an OSAENTA PROFILE statement. The following information is specific to this PortName value.

OSA DevStatus

The device status. The following list shows the possible values:

Starting

An OSAENTA ON command or statement has been processed and TCP/IP has sent an activation request to the data link control (DLC) layer.

Sent SETUP

DLC has acknowledged the TCP/IP activation request and TCP/IP has requested that DLC perform the initial I/O sequence with the device.

Enabling

DLC has acknowledged the TCP/IP activation request and TCP/IP has requested that DLC allow data connections to be established for the device.

Connecting

DLC has accepted the initial I/O sequence request.

Negotiating

The initial I/O sequence with the device is complete and TCP/IP is performing additional link-layer initialization.

Ready

The initialization sequence with the device is complete. The device is now ready.

Deactivating

DLC has performed the first stage of an orderly device deactivation.

Not Active

The device is not active. (The device has never been started or has been stopped after having been started.)

OSA IntfName

The name of the interface that is dynamically created to communicate with the OSA Express2 adapter.

OSA IntfStatus

The trace collection interface status. The following list shows the possible values:

Ready

The OSA interface used for OSAENTA is accepting all trace requests from the host.

Not Active

The OSA interface that is used for OSAENTA is not active. Either trace collection is disabled or else an error occurred during activation of the OSA interface that is to be used for trace collection. Such an error condition generates an error message on the operator console.

OSA Speed

The speed reported by the interface (in millions of bits per second).

OSA Authorization

The value of the OSA HMC authorization parameter. Possible values are Disabled, Logical Partition, PORT, CHPID, or UNKNOWN. The value is set to UNKNOWN until the first OSAENTA ON command has completed.

Disabled

The OSA does not allow the NTA function to trace any frames for the OSA.

Logical Partition

The OSA allows the NTA function to trace frames only for the current logical partition.

PORT

The OSA allows the NTA function to trace frames for all stacks that share this OSA port.

CHPID

The OSA allows the NTA function to trace frames for all stacks that share the OSA.

UNKNOWN

The NTA trace interface has not been activated.

OSAENTA Cumulative Trace Statistics

Statistics accumulated for all frames that have been traced since the OSAENTA interface was first activated. These values are not reset by the OSAENTA ON command or statement.

DataMegs

The number of bytes of trace data (in megabytes) that have been received.

Frames

The total number of frames that have been traced.

DataBytes

The number of bytes of trace data that have been received.

FramesDiscarded

The number of frames that were traced but that the OSA device was not able to either forward to a host image or deliver outbound. These packets are available for formatting in the CTRACE SYSTCPOT component, but have not been delivered to any user.

FramesLost

The number of frames that could not be recorded by TCP/IP in the SYSTCPOT buffers.

OSAENTA Active Trace Statistics

Statistics that have accumulated since the OSAENTA ON command or statement was last issued.

DataMegs

The number of bytes of trace data (in megabytes) that have been collected.

Frames

The total number of frames that have been collected.

DataBytes

The number of bytes of trace data that have been collected.

FramesDiscarded

The number of frames that were collected but that the OSA device was not able to either forward to a host image or deliver outbound. These packets are available for formatting in the CTRACE SYSTCPOT component, but have not been delivered to any user.

FramesLost

The number of frames that were not collected by TCP/IP in the SYSTCPOT buffers.

TimeActive

The number of minutes that have elapsed since the last OSAENTA ON command or statement.

OSAENTA Trace Settings

The current trace settings that are in effect for this OSAENTA interface.

Status

The current trace status. Possible values are:

ON

Tracing is enabled.

OFF

Tracing is disabled.

DataMegsLimit

The amount of data (in megabytes) to be collected before the trace is automatically stopped. This value was specified on the DATA parameter.

FramesLimit

The number of frames to be collected before the trace is automatically stopped. This value was specified on the FRAMES parameter.

TimeLimit

The amount of time (in minutes) that data is collected before the trace is automatically stopped. This value was specified on the TIME parameter.

Abbrev

The size limit for the frames (in bytes) that are to be traced. This value was specified on the ABBREV parameter. This value can be modified to reflect the size limit set by the OSA.

Discard

Identifies which frames being discarded by the OSA-Express device are to be traced. This value was specified on the DISCARD parameter. Possible values are:

All

All frames discarded by the OSA-Express device are traced.

Exception

Frames discarded by the OSA-Express device for exception conditions are traced.

None

No discarded frames are traced.

list

A list of from one to eight values, that indicate the type of discarded frames that are to be traced by the OSA-Express device. This list includes decimal discard codes and the keyword parameter EXCEPTION.

OSAENTA Trace Filters

The values of the current accumulated filter variables from OSAENTA commands or statements for this OSA. If a filter variable has not been specified using OSAENTA commands or statements, then an asterisk is shown.

Nofilter

The filtering behavior when all filters (DEVICEID, MAC, ETHTYPE, VLANID, IPADDR, PROTOCOL, and PORTNUM) have been cleared or are inactive. This behavior applies when no filters have been specified, if the CLEARFILTER parameter is specified, or when the current setting for every filter is an asterisk (*). This filtering behavior applies only to packets that were not discarded by the OSA-Express device. This value was specified on the NOFILTER parameter. Possible values are:

All

All frames are traced.

None

No frames are traced.

DeviceID

Up to eight hexadecimal device identifiers that are specified on the DEVICEID keyword of an OSAENTA command or statement. The value is an asterisk (*) if no device identifiers were specified.

Mac

Up to eight hexadecimal MAC addresses that are specified on the MAC keyword of an OSAENTA command or statement. The value is an asterisk (*) if no MAC addresses were specified.

VLANid

Up to eight decimal VLAN identifiers that are specified on the VLANID keyword of an OSAENTA command or statement. The value is an asterisk (*) if no VLAN identifiers were specified.

ETHType

Up to eight hexadecimal Ethernet types that are specified on the ETHTYPE keyword of an OSAENTA command or statement. The value is an asterisk (*) if no Ethernet types were specified. The name of the Ethernet type filter is displayed for commonly used Ethernet types, such as ARP, IPv4, IPv6, and SNA.

IPAddr

Up to eight dotted decimal IPv4 IP addresses and up to eight colon hexadecimal IPv6 IP addresses that are specified on the IPADDR keyword of an OSAENTA command or statement. The value is an asterisk (*) if no IP addresses were specified.

Protocol

Up to eight decimal protocol identifiers that are specified on the PROTOCOL keyword of an OSAENTA command or statement. The value is an asterisk (*) if no protocol identifiers were specified. The name of the protocol filter is displayed for commonly used protocols, while the protocol number is displayed for all others.

PORTNum

Up to eight decimal port numbers that are specified on the PORTNUM keyword of an OSAENTA command or statement. The value is an asterisk (*) if no port numbers were specified.

SMC Link Group Information

The information of the SMC link group. This section is displayed for each RNIC interface only when the SMC modifier or the SMCID/-U filter is specified. The following fields are displayed:

SMCLinkGroupId

The group identifier that this TCP/IP stack dynamically creates to represent the SMC-R link group that includes this individual link.

PNetID

The physical network ID value that is configured in HCD for this SMC-R link group.

Redundancy

The recovery and load balancing capabilities of the link group. The following list shows the possible values:

Full

The link group has redundant active SMC-R links. Both the local and remote stacks have full failover capability. The z/OS® server performs load balancing of TCP connections across the SMC-R links that are members of the link group.

Partial (Single local internal path)

The link group has redundant active SMC-R links. Both the local and remote stacks have failover capability. The z/OS server performs load balancing of TCP connections across the SMC-R links that are members of the link group. However, the links on the local stack have the same internal path.

Partial (Single local PCHID, unique ports)

The link group has redundant active SMC-R links. Both the local and remote stacks have failover capability. The z/OS server performs load balancing of TCP connections across the SMC-R links that are members of the link group. However, the links on the local stack have the same PCHID with unique ports.

Partial (Single local PCHID and port)

The link group has redundant active SMC-R links. Both the local and remote stacks have failover capability. The z/OS server performs load balancing of TCP connections across the SMC-R links that are members of the link group. However, the links on the local stack have the same PCHID and port.

Partial (Single local RNIC)

The link group has multiple active SMC-R links and the remote stack has full failover capability, but the local stack has no failover capability. The z/OS server does not perform load balancing of TCP connections.

Partial (Single remote RNIC)

The link group has multiple active SMC-R links and the local stack has full failover capability, but the remote stack has no failover capability. The z/OS server does not perform load balancing of TCP connections.

None (Single local and remote RNIC)

The link group has a single active SMC-R link. Neither the local stack nor the remote stack has failover capability. The z/OS server cannot perform load balancing of TCP connections.

Link Group Receive Buffer Total

Amount of remote memory buffer (RMB) storage that is assigned to this SMC-R link group.

32K Buffer Total

Amount of 32K RMB storage that is assigned to this SMC-R link group.

64K Buffer Total

Amount of 64K RMB storage that is assigned to this SMC-R link group.

128K Buffer Total

Amount of 128K RMB storage that is assigned to this SMC-R link group.

256K Buffer Total

Amount of 256K RMB storage that is assigned to this SMC-R link group.

Other Buffer Total

For RMB storage that is allocated as buffers larger than 256K, the amount of these other buffers that are assigned to this SMC-R link group. If no buffers larger than 256K are allocated, this information is not displayed.

LocalSMCLinkId

The link identifier this TCP/IP stack dynamically creates to represent the SMC-R link in this SMC-R link group.

RemoteSMCLinkId

The SMC-R link identifier that the remote peer uses to represent the link in this SMC-R link group. The value is provided to this TCP/IP stack during link activation.