INTERFACE - IPAQENET6 OSA-Express QDIO interfaces statement

Use the INTERFACE statement to specify an OSA-Express QDIO Ethernet interface for IPv6.

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 IPv6:

• Fast Ethernet
• Gigabit Ethernet
• 1000BASE-T Ethernet
• 10G Ethernet

When you start an IPAQENET6 interface (and you do not specify VMAC with ROUTEALL), TCP/IP registers all non-loopback local (home) IPv6 addresses for this TCP/IP instance to the OSA-Express feature. If you subsequently add, delete, or change any home IPv6 addresses on this TCP/IP instance, TCP/IP dynamically registers the changes to the OSA-Express feature. If stateless address autoconfiguration is enabled for this interface, TCP/IP dynamically registers autoconfigured addresses to the OSA-Express feature. This includes both public and temporary autoconfigured addresses. The OSA-Express feature routes datagrams destined to those IPv6 addresses to this TCP/IP instance.

If a datagram is received by the OSA adapter for an unregistered IPv6 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 whether the definition of an instance is 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. For more details about the OSA-Express feature routing considerations, see the router information in z/OS Communications Server: IP Configuration Guide 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.

Restriction: This statement applies to IPv6 IP addresses only.

Parameters

intf_name

The name of the interface. The maximum length is 16 characters.

Requirement: This name must be different than the name specified for the PORTNAME parameter.

Restriction: Do not specify the value PUBLICADDRS or TEMPADDRS for the interface name. The values PUBLICADDRS and TEMPADDRS are keywords on the SRCIP statement. These values are not recognized if they are specified as an IPv6 interface name on an SRCIP entry.

DEFINE

Specifies that this definition is to be added to the list of defined interfaces.

DELETE

Specifies that this definition is to be deleted from the list of defined interfaces. The intf_name must be the name of an interface previously defined by an INTERFACE statement. INTERFACE DELETE deletes all home IP addresses for the interface.

CHPIDTYPE

An optional parameter indicating the CHPID type of the OSA-Express QDIO interface.

OSD

The external data network. This is the default value.

OSX

The intraensemble data network. See z/OS Communications Server: IP Configuration Guide for information about requirements necessary to make an OSX work.

Rule: You must specify an OSD interface definition to make this OSA-Express QDIO interface use Shared Memory Communications over Remote Direct Memory Access (SMC-R) for external data network communications.

IPADDR ipaddr_spec

For information about the IPv6 address restrictions, see Restrictions on IPv6 addresses configured in the TCP/IP profile.

The following value can be specified for ipaddr_spec:

ipv6_address

This parameter can be one of the following values:

• ipv6_addr (A fully qualified IPv6 address is in colon-hexadecimal format.)
• prefix/64 [The digits (in colon-hexadecimal format) before the / represent the prefix. The prefix length represents the length of the prefix in bits. If a prefix length is coded, it must be equal to 64. When a prefix is specified, TCP/IP constructs the IPv6 address by appending the interface ID to it.]

Restriction: If you code a prefix that is longer than 64 bits, it is truncated to 64 bits, and no error messages are issued.

ADDADDR ipaddr_spec

Allows the addition of IP addresses to an existing INTERFACE definition (similar to updating the HOME list with the VARY TCPIP,,OBEYFILE command) without having to delete and redefine the INTERFACE. This can be used to change the autoconfiguration state of an interface. If ADDADDR is coded and this is the first manually configured IP address for the interface, then TCP/IP disables autoconfiguration for the interface. The intf_name coded with ADDADDR must be the name of an interface previously defined by an INTERFACE statement.

Any public or temporary addresses that had previously been autoconfigured for the interface are deleted.

DELADDR ipaddr_spec

Allows you to delete IP addresses from an existing INTERFACE definition. If DELADDR is coded for the last or only manually configured IP address for an interface, then TCP/IP enables autoconfiguration for the interface. DELADDR is valid only for an IP address or prefix configured manually. The intf_name coded with DELADDR must be the name of an interface previously defined by an INTERFACE statement. DELADDR is valid only in a data set specified on a VARY TCPIP,,OBEYFILE command.

Guideline: If you specify a prefix for DELADDR, then the only IP addresses affected are those defined by way of the same prefix specified on IPADDR or ADDADDR.

DEPRADDR ipaddr_spec

The DEPRADDR keyword allows you to deprecate an IP address. This can assist with site renumbering. DEPRADDR is valid only for an IP address or prefix configured manually. If you use DEPRADDR to deprecate an IP address, you can subsequently use ADDADDR again to make that IP address preferred. For DEPRADDR, the interface_name must be the name of an interface previously defined by an INTERFACE statement. DEPRADDR is valid only in a data set specified on a VARY TCPIP,,OBEYFILE command.

Guideline: If you specify a prefix for DEPRADDR, then the only IP addresses affected are those defined by way of the same prefix specified on IPADDR or ADDADDR.

ADDTEMPPREFIX

Use the ADDTEMPPREFIX keyword to add prefixes to the temporary prefixes list of an existing INTERFACE definition without having to delete and redefine the INTERFACE statement. The temporary prefixes list limits the set of prefixes for which temporary IPv6 addresses can be generated. A temporary IPv6 address is generated when a router advertisement containing the prefix is processed, and the prefix is included in one of the prefixes in the temporary prefixes list. For example, if the temporary prefixes list for an interface contains a single prefix 2001:0db8:58cd::/48, a temporary address is generated for advertised prefix 2001:0db8:58cd:0001/64; however, a temporary address is not generated on this interface for advertised prefix 2001:0db8:5555:0001/64. The intf_name variable coded with ADDTEMPPREFIX must be the name of an interface that was previously defined by an INTERFACE statement.

prefix/prefix_length

The digits (in colon-hexadecimal format) before the slash (/) represent the prefix. The prefix_length value represents the length of the prefix in bits. Valid values for prefix_length parameter are in the range 1 - 64.

ALL

Causes temporary addresses to be generated for all prefixes that are learned over this interface by way of router advertisements.

DELTEMPPREFIX

Use the DELTEMPPREFIX keyword to delete prefixes from the temporary prefixes list of an existing INTERFACE definition. The temporary prefixes list limits the set of prefixes for which temporary IPv6 addresses can be generated. A temporary IPv6 address is generated when a router advertisement containing the prefix is processed and the prefix is included in one of the prefixes in the temporary prefixes list. The intf_name variable coded with the DELTEMPPREFIX keyword must be the name of an interface that was previously defined by an INTERFACE statement.

prefix/prefix_length

The digits (in colon-hexadecimal format) before the slash (/) represent the prefix. The prefix_length value represents the length of the prefix in bits. Valid values for the prefix_length are in the range 1 - 64. All temporary addresses for this interface whose prefix is not included in the updated temporary prefixes list are deleted.

ALL

Delete all prefixes from the temporary prefixes list, which sets the temporary prefixes list to NONE. All temporary addresses for this interface are deleted, and no more temporary addresses are generated for this interface.

IPADDR ipaddr_spec

TCP/IP always creates the link-local IPv6 address. If IPADDR is not specified, then TCP/IP enables autoconfiguration for the interface.

Tip: Autoconfiguration is enabled if there is a router or some other device that provides a router advertisement.

If no address or prefix is specified, it is obtained from a router on the LAN by way of an IPv6 stateless autoconfiguration. For more information, see z/OS Communications Server: IPv6 Network and Application Design Guide.

IPAQENET6

Indicates that the interface uses the interface based on IP assist, belongs to the QDIO family of interfaces, and uses the Gigabit Ethernet or Fast Ethernet protocol.

INTFID interface_id

An optional 64-bit interface identifier in colon-hexadecimal format. IPv6 shorthand is not allowed when specifying the interface ID. If specified, this interface ID is used to form the link-local address for the interface, and is also appended to any manually configured prefixes for the interface, to form complete IPv6 addresses on the interface. If you do not configure manual IP addresses on the interface, the INTFID value is appended to any prefixes that are learned over this interface by way of router advertisements to form public IPv6 addresses on the interface. The INTFID value is not used to form temporary IPv6 addresses. A randomly generated interface ID is appended to any learned prefixes to form temporary IPv6 addresses on the interface (if temporary addresses are enabled).

If INTFID is not coded, TCP/IP builds the Interface ID using information returned from the OSA-Express Adapter (during Interface activation). The built Interface ID value is then used to form the link-local address. This value is also used to complete the formation of other IPv6 addresses on the interface, if you choose to configure only the prefix portion of the addresses (by way of IPADDR or ADDADDR). Also, if you do not configure manual IP addresses on the interface, the built interface ID value is appended to any prefixes learned over this interface by way of router advertisements to form public IPv6 addresses on the interface. The built interface ID value is not used to form temporary IPv6 addresses. A randomly generated interface ID is appended to any learned prefixes to form temporary IPv6 addresses on the interface (if temporary addresses are enabled).

When defining the interface ID, the local/universal flag (the U bit, bit 6 shown in the following example) must be set to 0. The group/individual flag (the G bit, bit 7 shown in the following example) must also be set to 0. If either flag is set incorrectly, interface definition fails. Additionally, an interface ID value correlating to an ISATAP address or a Reserved Anycast address is not allowed. (An ISATAP Interface ID has '00005EFE'x in bits 0 - 31, and a Reserved Anycast Interface ID has 'FCFFFFFFFFFFFF8' in bits 0 - 56.)

|               1|1              3|3              4|4              6|
|0              5|6              1|2              7|8              3|
+----------------+----------------+----------------+----------------+
|xxxxxxUGxxxxxxxx|xxxxxxxxxxxxxxxx|xxxxxxxxxxxxxxxx|xxxxxxxxxxxxxxxx|
+----------------+----------------+----------------+----------------+

SOURCEVIPAINTERFACE vipa_name

SOURCEVIPAINTERFACE is optional. Use this parameter to specify which previously defined static VIPA interface is to be used for SOURCEVIPA (when IPCONFIG6 SOURCEVIPA is in effect).

Tip: The use of the SOURCEVIPAINTERFACE parameter can be overridden. See the information about source IP address selection in z/OS Communications Server: IP Configuration Guide for the hierarchy of ways that the source IP address of an outbound packet is determined.

The vipa_name is the interface name for a VIRTUAL6 interface. If the VIPA has multiple IP addresses, then the sourcevipa address for outbound packets is selected from among these addresses according to the default source address selection algorithm. For more information, seez/OS Communications Server: IPv6 Network and Application Design Guide.

Requirement: The VIRTUAL6 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 that defines it must precede this INTERFACE statement in the profile data set.

CHPID chpid

This parameter applies only to interfaces of CHPIDTYPE OSX and is used to specify the CHPID for the interface. This value is a 2-character hexadecimal value (00 - FF).

PORTNAME portname

Use this parameter to specify the PORT name contained in the TRLE definition for the QDIO interface. The TRLE must be defined as MPCLEVEL=QDIO. For details about defining a TRLE, see z/OS Communications Server: SNA Resource Definition Reference.

Requirement: The portname value must be different from the name that is specified for the intf_name value.

NONROUTER

If a datagram is received at this interface for an unknown IP address, the datagram is not routed to this TCP/IP instance. This is the default value.

PRIRouter and SECRouter parameters interact with the VLANID parameter. See the VLANID parameter 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.

PRIROUTER

If a datagram is received at this interface for an unknown IP address and is not destined for a virtual MAC, the datagram is routed to this TCP/IP instance.

Rule: This keyword applies only to interfaces of CHPIDTYPE OSD and is ignored if the VMAC parameter is configured on the INTERFACE statement.

SECROUTER

If a datagram is received at this interface for an unknown IP address and is not destined for a virtual MAC, and there is no active TCP/IP instance defined as PRIROUTER, then the datagram is routed to this TCP/IP instance.

Rule: This keyword applies only to interfaces of CHPIDTYPE OSD and is ignored if the VMAC parameter is configured on the INTERFACE statement.

DUPADDRDET count

Use this parameter to specify the number of times to attempt duplicate address detection. The minimum value is 0, maximum is 2 and default is 1. This is an optional parameter.

Guideline: A value of 0 means that TCP/IP does not perform duplicate address detection for this interface.

MTU num

The maximum transmission unit (MTU) in bytes. This value can be up to 9000. The minimum MTU for IPv6 is 1280. The stack takes the minimum of the configured value and the value supported by the device (returned by the OSA adapter).

The MTU default, which depends on value supported by device, is the following value:

• Gigabit Ethernet default MTU = 9000
• Fast Ethernet default MTU = 1500

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.

VLANID id

Specifies the decimal virtual LAN identifier to be assigned to the OSA-Express INTERFACE. This field should be a virtual LAN identifier recognized by the switch for the LAN connected to this OSA-Express. The valid range is 1 - 4094. This parameter is optional for CHPIDTYPE OSD and required for CHPIDTYPE OSX.

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 IPv6 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.

READSTORAGE

An optional parameter indicating the amount of fixed storage that z/OS® Communications Server should keep available for read processing for this adapter. The QDIOSTG VTAM® start option allows you to specify a value which applies to all OSA-Express adapters in QDIO mode. You can use the READSTORAGE keyword to override the global QDIOSTG value for this adapter based on the inbound workload you expect over this interface on this stack. The valid values are:

GLOBAL

The amount of storage is determined by the QDIOSTG VTAM start option. This is the default value.

MAX

Use this value if you expect a heavy inbound workload over this interface.

AVG

Use this value if you expect a medium inbound workload over this interface.

MIN

Use this value if you expect a light inbound workload over this interface.

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.

Rule: If you define both a LINK and INTERFACE statement for the same adapter, then the READSTORAGE value on the LINK statement must match the READSTORAGE value on the corresponding INTERFACE statement. If you define an INTERFACE statement that contains a value for READSTORAGE that conflicts with the READSTORAGE value for a previous LINK statement for the same adapter, then TCP/IP rejects the INTERFACE statement.

INBPERF

An optional parameter that indicates how processing of inbound traffic for the QDIO interface is performed.

There are three supported static settings (MINCPU, MINLATENCY, and BALANCED).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 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 at the point where throughput is maximized. 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 defaults to the value DYNAMIC.

Valid values are:

BALANCED

This setting uses a static interrupt-timing value, which is selected to achieve reasonably high throughput and reasonably low CPU consumption. This is the default value for CHPIDTYPE OSD.

DYNAMIC

This setting causes the host to dynamically signal the OSA-Express feature to change the timer-interrupt value, based on current inbound workload conditions. The DYNAMIC setting is effective only for OSA-Express2 or later features on at least an IBM System z9® that supports the corresponding Dynamic LAN Idle function. See the 2094DEVICE Preventive Service Planning (PSP) bucket and the 2096DEVICE Preventive Service Planning (PSP) bucket for more information about the level of OSA-Express2 adapter that supports this function. See the 2097DEVICE Preventive Service Planning (PSP) bucket for more information about the OSA-Express3 adapter that supports this function. The DYNAMIC setting can decrease latency and provide increases in throughput for many interactive workloads. For all other workload combinations, this setting provides performance similar to the three static settings. This is the default value for CHPIDTYPE OSX.

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.

WORKLOADQ | NOWORKLOADQ

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.

NOWORKLOADQ

Specifies that QDIO inbound workload queueing is not enabled for inbound traffic. All inbound traffic for this interface uses a single input queue. This is the default.

WORKLOADQ

Specifies that QDIO inbound workload queueing is enabled for inbound traffic.

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:

• Sysplex distributor
• Streaming workloads (for example FTP)
• Enterprise Extender (EE)

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.

MINCPU

This setting uses a static interrupt-timing value, which is selected to minimize host interrupts without regard to throughput. This mode of operation might result in minor queueing delays (latency) for packets into the host, which is not optimal for workloads with demanding latency requirements.

MINLATENCY

This setting uses a static interrupt-timing value, which is selected to minimize latency (delay), by more aggressively presenting received packets to the host. This mode of operation generally results in higher CPU consumption than the other three settings. Use this setting only if host CPU consumption is not an issue.

Rule: If you define both a LINK IPAQENET and an INTERFACE IPAQENET6 statement for the same adapter, then the following rules apply for the INBPERF parameter on these statements:

• The value on the LINK statement must match the INBPERF value on the corresponding INTERFACE statement.
• The INTERFACE statement supports the subparameters WORKLOADQ and NOWORKLOADQ for the INBPERF DYNAMIC parameter. These subparameters are associated with QDIO inbound workload queueing support and are not supported on the LINK IPAQENET statement. So, if you specify the INBPERF DYNAMIC parameter for both the LINK and the INTERFACE statements, then you must use the default or specify the NOWORKLOADQ subparameter for the INBPERF DYNAMIC parameter on the INTERFACE statement. This ensures that the INBPERF DYNAMIC setting for both statements is the same.
• If you define an INTERFACE IPAQENET6 statement that contains a value for INBPERF that conflicts with the INBPERF value for a previous LINK IPAQENET statement for the same adapter, then TCP/IP rejects the INTERFACE statement.

SECCLASS security_class

Use this parameter to associate a security class for IP filtering with this interface. In order for traffic over the interface to match a filter rule, the filter rule must have the same security class value as the interface or a value of 0. Filter rules can be specified in the TCP/IP profile or in an IP Security policy file read by the Policy Agent. Filter rules can include a security class specification on the IpService statement in an IP Security policy file or on the SECCLASS parameter on the IPSEC6RULE statement in the TCP/IP profile.

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 IPCONFIG6 statement.

MONSYSPLEX | NOMONSYSPLEX

Specifies whether or not sysplex autonomics should monitor the interface's status.

NOMONSYSPLEX

Specifies that sysplex autonomics should not monitor the interfaces's status. This is the default value.

MONSYSPLEX

Specifies that sysplex autonomics should monitor the interface's status.

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.

DYNVLANREG | NODYNVLANREG

This parameter controls whether or not the VLAN ID for this interface is dynamically or statically registered with the physical switch on the LAN.

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 which 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 if your OSA-Express feature can support VLAN dynamic registration. This Netstat report also displays whether or not dynamic VLAN ID registration has been configured for the interface.

Rule: If you define both a LINK and INTERFACE statement for the same adapter, then the dynamic VLAN ID registration parameter value on the LINK statement must match the value of this same parameter on the corresponding INTERFACE statement. If you define an INTERFACE statement that contains a dynamic VLAN ID registration parameter value that conflicts with the same parameter value for a previous INTERFACE statement for the same OSA-Express feature, then TCP/IP rejects the INTERFACE statement.

NODYNVLANREG

Specifies that if a VLAN ID is configured for this interface, it must be manually registered with the physical switches on the corresponding LAN. This is the default value. If this parameter is specified without a VLAN ID, then it is ignored.

DYNVLANREG

Specifies that if a VLAN ID is configured for this interface, it is dynamically registered with the physical switches on the corresponding LAN. If this parameter is specified without a VLAN ID, then warning message EZZ0056I is issued and the NODYNVLANREG setting is used instead.

VMAC macaddr

Specifies the virtual MAC address, which can be represented by 12 hexadecimal characters. The OSA-Express device uses this address rather than the physical MAC address of the device for all IPv6 packets to and from this TCP/IP stack. For CHPIDTYPE OSD, using a virtual MAC address is optional. For CHPIDTYPE OSX, using a virtual MAC address is required, so the VMAC parameter is the default.

The macaddr value is optional for CHPIDTYPE OSD and cannot be specified for CHPIDTYPE OSX. If the macaddr value is not coded, then the OSA-Express device generates a virtual MAC address. If the macaddr is coded, it must be defined as a locally administered individual MAC address. This means the MAC address must have bit 6 (the universal or local flag U bit) of the first byte set to 1 and bit 7 (the group or individual flag G bit) of the first byte set to 0. The second hexadecimal character must be 2, 6, A or E. The bit positions within the 12 hexadecimal characters are indicated as follows:

|               1|1              3|3              4|
|0              5|6              1|2              7|
+----------------+----------------+----------------+
|xxxxxxUGxxxxxxxx|xxxxxxxxxxxxxxxx|xxxxxxxxxxxxxxxx|
+----------------+----------------+----------------+

Rules:

• The same virtual MAC address generated by the OSA-Express device at interface activation remains in effect for this OSA-Express for this TCP/IP stack, even if the interface is stopped or becomes inoperative (INOPs). A new Virtual MAC address is generated only if the INTERFACE statement is deleted and redefined, or if the TCP/IP stack is recycled.
• The NONROUTER, PRIROUTER, and SECROUTER parameters are ignored for an OSA-Express interface if the VMAC parameter is configured on the INTERFACE statement.

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 burned-in MAC addresses and from all other VMAC addresses generated by any OSA-Express feature.

ROUTEALL

Specifies that all IP traffic destined to the virtual MAC is forwarded by the OSA-Express device to the TCP/IP stack. This is the default value. See the router information in z/OS Communications Server: IP Configuration Guide for more details.

ROUTELCL

This specifies that only traffic destined to the virtual MAC and whose destination IP address is registered with the OSA-Express device by this TCP/IP stack is forwarded by the OSA-Express. See the router information in z/OS Communications Server: IP Configuration Guide for more details.

SMCR | NOSMCR

Specifies whether this interface can be used with Shared Memory Communications over Remote Direct Memory Access (SMC-R) for external data network communications.

NOSMCR

Specifies that this interface cannot be used for new TCP connections with SMC-R for external data network communications.

SMCR

Specifies that this interface can be used for new TCP connections with SMC-R for external data network communications. This is the default setting.

Rules:

• SMCR and NOSCMR are valid with CHPIDTYPE OSD definitions only.
• SMCR has no effect unless at least one Peripheral Component Interconnect Express® (PCIe) function ID (PFID) value is specified by using the PFID subparameter of the SMCR parameter on the GLOBALCONFIG statement.

OLM| NOOLM

An optional parameter indicating whether an OSA-Express adapter operates in optimized latency mode.

OLM

Specifies that the OSA-Express adapter operates in optimized latency mode (OLM). Optimized latency mode optimizes interrupt processing for both inbound and outbound data. Use this mode for workloads that have demanding latency requirements. Because this mode can provide significant increases of throughput, this mode is particularly suited for interactive, non-streaming workloads. For more information about OLM, see the optimized latency mode topic in z/OS Communications Server: IP Configuration Guide.

NOOLM

Specifies that the OSA-Express adapter should not operate in optimized latency mode. This is the default value.

Guidelines:

• Because of the operating characteristics of optimized latency mode, you might need to change configuration to direct traffic to particular OSA-Express write priority queues and to limit the number of concurrent users sharing an OSA-Express adapter configured for OLM. See the optimized latency mode topic in z/OS Communications Server: IP Configuration Guide. for more information.
• The optimized latency mode function targets a z/OS environment with high-volume interactive workloads. Although optimized latency mode can compensate for some mixing of workloads, an excessive amount of high-volume streaming workloads, such as bulk data or file transfer, can result in higher CPU consumption.

Restrictions:

• This function is limited to OSA-Express3 or later Ethernet features in QDIO mode that are running with an IBM System z10™ or later. See the 2097 DEVICE Preventive Service Planning (PSP) bucket for more information.
• For an OSA-Express configured to use optimized latency mode, the stack ignores the configured or default INBPERF setting and uses the value DYNAMIC.

NOISOLATE | ISOLATE

Specifies whether packets should be directly routed between TCP/IP stacks that share the OSA adapter.

NOISOLATE

Route packets directly between TCP/IP stacks that share the OSA adapter. In this mode, if the next hop address was registered by another stack that is sharing the OSA, then OSA-Express routes the packet directly to the sharing stack without putting the packet on the external LAN.

ISOLATE

Prevent OSA-Express from routing packets directly to another TCP/IP stack that is sharing the OSA adapter. In this mode, OSA-Express discards any packets when the next hop address was registered by another stack that is sharing the OSA adapter. In this mode, packets can flow between two stacks that share the OSA adapter only by first going through a router on the LAN. For more details, see OSA-Express connection isolation information in z/OS Communications Server: IP Configuration Guide.

Tips:

• If you isolate an INTERFACE, that action might have an adverse effect on latency.
• You can selectively apply OSA-Express connection isolation to individual virtual LANs.
• OSA-Express requires that both stacks sharing the port be non-isolated for direct routing to occur. Therefore, for traffic between two stacks sharing the OSA adapter, as long as at least one of the stacks is isolated, connection isolation is in effect for traffic in both directions between these stacks.

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 2094, 2096, 2097, or 2098 DEVICE Preventive Service Planning (PSP) and the 2096DEVICE Preventive Service Planning (PSP) buckets for more information.

TEMPPREFIX

TEMPPREFIX specifies the set of prefixes for which temporary IPv6 addresses can be generated. A temporary IPv6 address is generated when a router advertisement containing a prefix is processed and the prefix is included in one of the prefixes in the temporary prefix list. For example, if TEMPPREFIX 2001:0db8:58cd::/48 is specified for an interface, a temporary address is generated for advertised prefix 2001:0db8:58cd:0001/64; however, a temporary address is not generated for advertised prefix 2001:0db8:5555:0001/64.

ALL

Generate temporary addresses for all prefixes that are learned over this interface by way of router advertisements. ALL is the default.

NONE

No IPv6 temporary addresses are generated for this interface.

prefix/prefix_length

The digits (in colon-hexadecimal format) before the slash (/) represent the prefix. The prefix_length value represents the length of the prefix, in bits. Valid values for prefix_length are in the range 1 - 64.

Rules:

• Temporary addresses are generated only on an interface that is enabled for stateless address autoconfiguration.
• Temporary addresses are generated only when the TEMPADDRS keyword is specified on the IPCONFIG6 statement.

Requirement: You must specify the job name of an application in the SRCIP statement block with a value of TEMPADDRS to cause a temporary IPv6 address to be preferred over a public IPv6 address as the source IP address for the application; otherwise, the default source address selection algorithm prefers public IPv6 addresses over temporary addresses. For more information, see the information about the default source address selection algorithm in z/OS Communications Server: IPv6 Network and Application Design Guide.

Steps for modifying

See Summary of INTERFACE statements for modification information.

Usage notes

Restriction: For each interface, the PRIROUTER and SECROUTER attributes can be in effect for only one TCP/IP instance within a central processor complex (CPC). If PRIROUTER is specified for an IPAQENET6 interface, but the IPv6 primary router attribute is already in effect on another TCP/IP instance for the same OSA-Express, then TCP/IP issues a warning message during interface activation and ignores the PRIROUTER parameter. Therefore, only one TCP/IP instance can be the primary router for the OSA-Express. Depending on the level of OSA-Express being started, either only one or multiple TCP/IP instances can be allowed to have SECROUTER specified. If OSA-Express allows only one secondary router, any TCP/IP instance subsequently starting that interface with SECROUTER receives a warning message during START processing for the interface. If OSA-Express allows multiple secondary routers, then OSA-Express can select any TCP/IP instance which specifies SECROUTER as the secondary router. There is no requirement that the same TCP/IP instance be specified PRIROUTER or SECROUTER for all OSA-Express adapters attached to the CPC.

Related topics

• BEGINROUTES statement
• DEVICE and LINK — MPCIPA OSA-Express QDIO devices statement
• GLOBALCONFIG statement
• INTERFACE - IPAQENET OSA-Express QDIO interfaces statement
• START statement
• STOP statement