Use the INTERFACE statement to specify an OSA-Express QDIO Ethernet interface for IPv4.
Restriction: This statement applies to IPv4 IP addresses only.
To determine the OSA-Express microcode level, use the DISPLAY TRL command. If a specific OSA-Express function is documented with a minimum microcode level, you can use this command to determine whether that function is supported. IBM® service might request the microcode level for problem diagnosis. For more information about the DISPLAY TRL command, see z/OS Communications Server: SNA Operation.
The following OSA-Express features can be defined in QDIO mode for IPv4:
When you start an IPAQENET interface (and you did not specify VMAC with ROUTEALL), TCP/IP registers all non-loopback local (home) IPv4 addresses for this TCP/IP instance to the OSA-Express feature. If you subsequently add, delete, or change any home IPv4 addresses on this TCP/IP instance, TCP/IP dynamically registers the changes to the OSA-Express feature. The OSA adapter routes datagrams destined for those IPv4 addresses to this TCP/IP instance.
If a datagram is received at the OSA adapter for an unregistered IPv4 address, then the OSA-Express feature routes the datagram to the TCP/IP instance, depending on the setting of a virtual MAC (VMAC) address or definition of an instance as PRIROUTER or SECROUTER. If the datagram is not destined for a virtual MAC address and no active TCP/IP instance using this interface is defined as PRIROUTER or SECROUTER, then the OSA-Express feature discards the datagram. See the router information in z/OS Communications Server: IP Configuration Guide for more details and primary and secondary routing in z/OS Communications Server: SNA Network Implementation Guide.
For detailed instructions on setting up an OSA-Express feature, see zEnterprise System and System z10 OSA-Express Customer's Guide and Reference.
For more information about missing interrupt handler (MIH) considerations with TCP/IP interfaces, see Missing interrupt handler factors.
Rule: Specify the required parameters and the CHPIDTYPE parameter in the order shown here. The OSD Interface Definition and OSX Interface Definition parameters can be specified in any order.
>>-INTERFace--intf_name-----------------------------------------> .-CHPIDTYPE OSD | OSD interface definition |-. >--+-DEFINE--IPAQENET--+--------------------------------------------+--| Common parameters |-+->< | '-CHPIDTYPE OSX | OSX interface definition |-' | '---DELEte--------------------------------------------------------------------------------' OSD Interface Definition |--PORTNAME portname--------------------------------------------> .-NONRouter-. >--+-IPADDR-+-ipv4_address/0-------------+-+-----------+-+------> | +-ipv4_address---------------+ +-PRIRouter-+ | | '-ipv4_address/num_mask_bits-' '-SECRouter-' | '-TEMPIP----------------------------------------------' .-INBPERF BALANCED---------------------. >--+-----------+--+--------------------------------------+------> '-VLANID id-' | .-NOWORKLOADQ-. | '-INBPERF--+-DYNAMIC-+-------------+-+-' | '-WORKLOADQ---' | +-MINCPU------------------+ '-MINLATENCY--------------' .-SMCR---. >--+---------------------------------+--+--------+--------------| | .-ROUTEALL-. | '-NOSMCR-' '-VMAC--+---------+--+----------+-' '-macaddr-' '-ROUTELCL-' OSX Interface Definition |--+-CHPID--chpid-------+---------------------------------------> '-PORTNAME--portname-' >--IPADDR ipv4_address/num_mask_bits--VLANID id-----------------> .-INBPERF DYNAMIC NOWORKLOADQ----------. >--+--------------------------------------+---------------------> '-INBPERF--+-BALANCED----------------+-' +-MINCPU------------------+ +-MINLATENCY--------------+ | .-NOWORKLOADQ-. | '-DYNAMIC-+-------------+-' '-WORKLOADQ---' .-VMAC ROUTEALL------. >--+--------------------+---------------------------------------| | .-ROUTEALL-. | '-VMAC--+----------+-' '-ROUTELCL-' Common parameters for OSD and OSX interface definitions |--+--------------------------------+--+---------+--------------> '-SOURCEVIPAINTerface -vipa_name-' '-MTU num-' .-READSTORAGE GLOBAL---. >--+----------------------+--+---------+------------------------> '-READSTORAGE--+-MAX-+-' '-IPBCAST-' +-AVG-+ '-MIN-' .-SECCLASS 255------------. .-NOMONSYSPLEX-. >--+-------------------------+--+--------------+----------------> '-SECCLASS security_class-' '-MONSYSPLEX---' .-NODYNVLANREG-. .-NOOLM-. .-NOISOLATE-. >--+--------------+--+-------+--+-----------+-------------------| '-DYNVLANREG---' '-OLM---' '-ISOLATE---'
Requirement: This name must be different than the name specified for the PORTNAME parameter.
Requirement: The portname value must be different than the name specified for intf_name.
Requirement: The IP address must be specified in dotted decimal form.
Requirement: If you are configuring multiple IPv4 VLAN interfaces to the same OSA-Express feature, then you must specify a nonzero value for the num_mask_bits variable for each of these interfaces and the resulting subnet must be unique for each of these interfaces.
Rule: If you are using OMPROUTE and OMPROUTE is not configured to ignore this interface, ensure that the subnet mask value that you define on this parameter matches the subnet mask used by OMPROUTE for this interface. The subnet mask used by OMPROUTE is the subnet mask value defined on the corresponding OMPROUTE statement (OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE) for this interface. If no OMPROUTE statement is specified for this interface, the subnet mask used by OMPROUTE is the class mask for the interface IP address.
The PRIROUTER and SECROUTER parameters interact with the VLANID parameter. See the VLANID parameter definition to understand this relationship.
For more information about VLANID parameter interactions, see z/OS Communications Server: IP Configuration Guide.
Rule: This keyword applies only to interfaces of CHPIDTYPE OSD and is ignored if the VMAC parameter is configured on the INTERFACE statement.
For more information about VLANID parameter interactions, see z/OS Communications Server: IP Configuration Guide.
Rule: This keyword applies only to interfaces of CHPIDTYPE OSD and is ignored if the VMAC parameter is configured on the INTERFACE statement.
For more information about VLANID parameter interactions, see z/OS Communications Server: IP Configuration Guide.
Rule: This keyword applies only to interfaces of CHPIDTYPE OSD and is ignored if the VMAC parameter is configured on the INTERFACE statement.
Guideline: Installation configuration on other platforms or related to Ensemble networking can limit the maximum VLANID of 4096.
The VLANID parameter interacts with the PRIROUTER and SECROUTER parameters. If you configure both the VLANID parameter and either PRIROUTER or SECROUTER parameter, then this TCP/IP instance acts as a router for this VLAN (ID) only. Datagrams that are received at this device instance for an unknown IP address and are not destined for a virtual MAC are routed only to this TCP/IP instance if it is VLAN tagged with this VLAN ID. For more information about VLANID parameter interactions, see z/OS Communications Server: IP Configuration Guide.
Rule: If you are configuring multiple VLAN interfaces to the same OSA-Express feature, then you must specify the VMAC parameter (with the default ROUTEALL attribute) on the INTERFACE statement for each of these interfaces.
Restriction: The stack supports a maximum of 32 IPv4 VLAN interfaces to the same OSA-Express port. Additional VLANID limitations might exist if this interface can be used with Shared Memory Communications over Remote Direct Memory Access (SMC-R). See VLANID considerations in z/OS Communications Server: IP Configuration Guide for details.
An optional parameter that indicates how processing of inbound traffic for the QDIO interface is performed.
There are three supported static settings that indicate how frequently the adapter should interrupt the host for inbound traffic: BALANCED, MINCPU, and MINLATENCY. The static settings use static interrupt-timing values. The static values are not always optimal for all workload types or traffic patterns, and the static values cannot account for changes in traffic patterns.
There is also one supported dynamic setting (DYNAMIC). This setting causes the host (stack) to dynamically adjust the timer-interrupt value while the device is active and in use. This function exploits an OSA hardware function called Dynamic LAN Idle. Unlike the static settings, the DYNAMIC setting reacts to changes in traffic patterns and sets the interrupt-timing values to maximize throughput. The dynamic setting does not incur additional CPU consumption that might be produced when you specify any of the static settings. In addition, the DYNAMIC setting uses the OSA Dynamic Router Architecture function to enable QDIO inbound workload queues for specific inbound traffic types.
Result: When you specify OLM on the INTERFACE statement, the INBPERF parameter is ignored and the statement takes the value DYNAMIC.
Valid values for INBPERF are:
If the DYNAMIC setting is specified for an OSA-Express adapter that does not support the dynamic LAN Idle function, the stack reverts to using the BALANCED setting.
This subparameter controls the QDIO inbound workload queueing function for the interface. QDIO inbound workload queueing is effective only for OSA-Express features in QDIO mode that support the corresponding Data Router Architecture. OSA-Express features that support workload queueing do not necessarily support workload queueing for all possible traffic types. For more information about the QDIO inbound workload queueing function and the OSA-Express features that support it, see QDIO inbound workload queueing in z/OS Communications Server: IP Configuration Guide.
If the WORKLOADQ subparameter is specified, QDIO inbound workload queueing is enabled for specific inbound traffic types. A primary input queue is reserved for all other traffic types.
Ancillary input queues (AIQs) are created for the following inbound traffic types when supported by the OSA-Express feature:
Requirement: You must specify the VMAC parameter with WORKLOADQ to enable QDIO inbound workload queueing.
If the WORKLOADQ setting is specified for an OSA-Express adapter that does not support the Data Router Architecture function, the stack reverts to using a single input queue.
| 1|1 3|3 4|
|0 5|6 1|2 7|
+----------------+----------------+----------------+
|xxxxxxUGxxxxxxxx|xxxxxxxxxxxxxxxx|xxxxxxxxxxxxxxxx|
+----------------+----------------+----------------+
Guideline: Unless the virtual MAC address representing this OSA-Express device must remain the same even after TCP/IP termination and restart, configure VMAC without a macaddr value and allow the OSA-Express device to generate it. This guarantees that the VMAC address is unique from all other physical MAC addresses and from all other VMAC addresses generated by any OSA-Express feature.
Requirement: The VIRTUAL interface must be defined prior to specifying this INTERFACE statement to the TCP/IP stack. It must either already be defined, or the INTERFACE statement (or DEVICE and LINK statements) that define the static VIPA must precede this INTERFACE statement in the profile data set.
The MTU default, which depends on the value that is supported by the device, is the following value:
The MTU default is 1492 for Fast Ethernet; otherwise, it is 8992.
Rule: If you are using OMPROUTE and OMPROUTE is not configured to ignore this interface, ensure that the MTU that you define on this parameter matches the MTU used by OMPROUTE for this interface. The MTU used by OMPROUTE is the MTU value defined on the corresponding OMPROUTE statement (OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE) for this interface. If an MTU value is not defined on the corresponding OMPROUTE statement for this interface or if no OMPROUTE statement is specified for this interface, the MTU used by OMPROUTE is the minimum MTU for IPv4 (576).
Tip: See z/OS Communications Server: IP Configuration Guide, in section Maximum transmission unit considerations, for additional information about how TCP/IP uses the MTU to determine the largest size frame to send.
Tip: See the description of the QDIOSTG VTAM start option in the z/OS Communications Server: SNA Resource Definition Reference for details about exactly how much storage is allocated by z/OS Communications Server for each of these values.
Valid security classes are identified as a number in the range 1 - 255. The default value is 255. For more information about security class values, see z/OS Communications Server: IP Configuration Guide.
The TCP/IP stack ignores this value if IPSECURITY is not specified on the IPCONFIG statement.
Restriction: The MONSYSPLEX attribute is not in effect unless the MONINTERFACE keyword is specified on the GLOBALCONFIG SYSPLEXMONITOR profile statement. The presence of dynamic routes over this interface is monitored if the DYNROUTE keyword is also specified on the GLOBALCONFIG SYSPLEXMONITOR profile statement.
Restriction: This parameter is applicable only if a VLAN ID is specified on the statement.
Dynamic registration of VLAN IDs is handled by the OSA-Express feature and the physical switch on your LAN. Therefore, in order for the DYNVLANREG parameter to be effective, both must be at a level that provides the necessary hardware support for dynamic VLAN ID registration. After the interface is active, you can view the Netstat DEvlinks/-d report output to determine whether your OSA-Express feature can support VLAN dynamic registration. This Netstat report also displays whether dynamic VLAN ID registration has been configured for the interface.
Restriction: This function is limited to OSA-Express2 or later Ethernet features in QDIO mode and running at least an IBM System z9 Enterprise Class (EC) or z9 Business Class (BC). See the 2094DEVICE, 2096DEVICE, 2097DEVICE, or 2098DEVICE Preventive Service Planning (PSP) bucket for more information.
See Summary of INTERFACE statements for modification information.
INTERFACE OSAQDIO24
DEFINE IPAQENET
PORTNAME OSAQDIO2
SOURCEVIPAINT VIPAV4
IPADDR 100.1.1.1/24