Use the IPCONFIG6 statement to update the IP layer of TCP/IP with information that pertains to IPv6.
EZZ0695I IPCONFIG6 NOT VALID - IPV6 SUPPORT IS NOT ENABLED
Tip: Specify the parameters for this statement in any order.
>>-IPCONFIG6----------------------------------------------------> .---------------------------------------------------------------------------------------------------------------------------. V | >----+-----------------------------------------------------------------------------------------------------------------------+-+->< | .-CHECKSUMOFFLoad---. | +-+-------------------+-------------------------------------------------------------------------------------------------+ | '-NOCHECKSUMOFFLoad-' | | .-DATAGRamfwd NOFWDMULTipath--------------. | +-+-----------------------------------------+---------------------------------------------------------------------------+ | +-NODATAGRamfwd---------------------------+ | | | .-NOFWDMULTipath---------. | | | '-DATAGRamfwd--+------------------------+-' | | '-FWDMULTipath PERPacket-' | | .-NODYNAMICXCF------------------------------------------------------------------------------------------------------. | +-+-------------------------------------------------------------------------------------------------------------------+-+ | | .-----------------------------------. | | | | V | .-SECCLASS 255------------. | | | '-DYNAMICXCF--+-ipv6_address------------------+----+-------------------------------+-+--+-------------------------+-' | | '-ipv6_address/prefix_route_len-' +-INTFID interface_id-----------+ '-SECCLASS security_class-' | | '-SOURCEVIPAINTerface vipa_name-' | | .-HOPLimit 255------. | +-+-------------------+-------------------------------------------------------------------------------------------------+ | '-HOPLimit hoplimit-' | | .-ICMPErrorlimit 3------------. | +-+-----------------------------+---------------------------------------------------------------------------------------+ | '-ICMPErrorlimit msgs_per_sec-' | +-+----------------+----------------------------------------------------------------------------------------------------+ | '-IGNORERedirect-' | | .-NOIGNOREROUTERHoplimit-. | +-+------------------------+--------------------------------------------------------------------------------------------+ | '-IGNOREROUTERHoplimit---' | +-+--------------------------------------------+------------------------------------------------------------------------+ | | .-OSMSECCLASS 255------------. | | | '-IPSECURITY--+----------------------------+-' | | '-OSMSECCLASS security_class-' | | .-NOMULTIPATH------------------. | +-+------------------------------+--------------------------------------------------------------------------------------+ | | .-PERConnection-. | | | '-MULTIPATH--+---------------+-' | | '-PERPacket-----' | | .-NOSEGMENTATIONOFFLoad-. | +-+-----------------------+---------------------------------------------------------------------------------------------+ | '-SEGMENTATIONOFFLoad---' | | .-NOSOURCEVIPA-. | +-+--------------+------------------------------------------------------------------------------------------------------+ | '-SOURCEVIPA---' | | .-NOTCPSTACKSOURCEVipa---------. | +-+------------------------------+--------------------------------------------------------------------------------------+ | '-TCPSTACKSOURCEVipa intf_name-' | | .-NOTEMPADDRS-------------------------------------------------------------------------------. | '-+-------------------------------------------------------------------------------------------+-------------------------' | .-PREFLIFETIME 24 VALIDLIFETIME 7*24-----------------------------------------. | '-TEMPADDRS--+----------------------------------------------------------------------------+-' | .-PREFLIFETIME 24--------------. .-VALIDLIFETIME default_valid_lifetime-. | '-+------------------------------+--+--------------------------------------+-' '-PREFLIFETIME --pref_lifetime-' '-VALIDLIFETIME valid_lifetime---------'
See Steps for modifying for information about changing this parameter while the TCP/IP stack is active. See Checksum offload in z/OS Communications Server: IP Configuration Guide for more information about the checksum offload support and for specific information about which packets can have checksum processing performed by the OSA-Express.
EZZ0699I IPV6 FORWARDING IS DISABLED
If the TCP/IP stack is also configured to be a sysplex distributor (see VIPADYNAMIC statement summary for more information), datagrams destined to a sysplex-distributed dynamic VIPA are forwarded to stacks, whether or not forwarding is enabled.
EZZ0700I IPV6 FORWARDING NOFWDMULTIPATH SUPPORT IS ENABLED
EZZ0700I IPV6 FORWARDING FWDMULTIPATH PERPACKET SUPPORT IS ENABLED
EZZ0739I IPV6 DYNAMIC XCF DEFINITIONS ARE DISABLED
When DYNAMICXCF is coded in the profile, the purpose is to generate those dynamic XCF devices or interfaces, if possible. When TCP/IP is up, but ISTLSXCF is not active, dynamic creation is deferred. Later, when a TCP/IP command such as VARY TCPIP,,OBEYFILE or VARY TCPIP,,START is executed, triggering profile processing, the stack again checks to see if ISTLSXCF is active. If ISTLSXCF is active at that time, then the dynamic XCF devices and interfaces are generated.
Dynamic XCF definitions are not generated if there is a DEVICE or INTERFACE definition with the same device or interface name that dynamic XCF would generate.
Activation of dynamic XCF links is delayed if VTAM® is not up or if OMPROUTE is not up and DELAYJOIN is coded on the GLOBALCONFIG SYSPLEXMONITOR statement. For more information about connectivity problems in a sysplex, see z/OS Communications Server: IP Configuration Guide.
When using dynamic XCF for sysplex configuration, make sure that XCFINIT=YES or XCFINIT=DEFINE is coded in the VTAM start options, or if XCFINIT=NO was specified, ensure that a VARY ACTIVATE command is issued for the ISTLSXCF major node. This ensures that XCF connections between TCP stacks on different VTAM nodes in the sysplex can be established. See z/OS Communications Server: SNA Resource Definition Reference for directions for coding the XCFINIT VTAM start option. The DISPLAY NET,VTAMOPTS command can be used to determine the XCFINIT setting.
The VTAM ISTLSXCF major node must be active for XCF dynamics to work, except for the following two scenarios:
For information about activating the ISTLSXCF major node, see z/OS Communications Server: SNA Resource Definition Reference.
Dynamic XCF can be enabled even in a single system sysplex. HiperSockets can be used between LPARs on the same central processor complex (CPC) even when MVS images in those LPARs are not defined to be part of the same sysplex. HiperSockets can also be used between LPARs even when some of those other LPARs are running Linux, as long as all of the stacks connecting to HiperSockets and needing to exchange IP packets with each other define IP addresses that are all in the same subnet (as defined by the dynamic XCF IP address and subnet mask in the IPCONFIG6 DYNAMICXCF profile statement).
A mix of static and dynamic IPv4 and IPv6 definitions for a device are not allowed. For example, if a static IUTSAMEH IPv4 device/link is defined, then the IPv6 dynamic definition for IUTSAMEH is not created. If a static IUTSAMEH IPv6 interface is defined, then the IPv4 dynamic definition for IUTSAMEH is not created. The same logic is also applied for XCF links; a mix of static and dynamic IPv4 and IPv6 definitions is not allowed for an XCF link.
See Restrictions on IPv6 addresses configured in the TCP/IP profile for a list of restrictions that must be observed when specifying this parameter.
Guideline: Configure a prefix_route_len to simplify connectivity if you use HiperSockets on the same IQD CHPID for stacks outside the sysplex or if you configure VIPAROUTE statements.
If INTFID is not coded, TCP/IP generates a random value to be used to form the link-local address.
See INTERFACE - IPAQENET6 OSA-Express QDIO interfaces statement for an explanation of restrictions that must be observed when manually specifying the INTFID parameter.
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.
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.
Restriction: This value is used only when IPSECURITY is specified on the IPCONFIG6 statement.
EZZ0739I IPV6 DYNAMIC XCF DEFINITIONS ARE ENABLED
EZZ0701I ICMPV6 REDIRECTS WILL BE IGNORED
If you are using OMPROUTE, and IPv6 interfaces are configured to OMPROUTE, and this option is not specified, IGNOREREDIRECT is enabled automatically. If you are using intrusion detection services (IDS) policy to detect and discard ICMPv6 redirect packets and this option is not specified, ICMPv6 redirect packets are discarded while the policy is active.
EZZ0720I ROUTER ADVERTISEMENT HOP LIMIT VALUES WILL NOT BE IGNORED
EZZ0719I ROUTER ADVERTISEMENT HOP LIMIT VALUES WILL BE IGNORED
EZZ0786I IPV6 SECURITY SUPPORT IS ENABLED
Restriction: IPSec functions can be activated only at initial activation of TCP/IP.
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.
EZZ0703I IPV6 MULTIPATH SUPPORT IS DISABLED
NOMULTIPATH is the default value.
EZZ0704I IPV6 MULTIPATH PERCONNECTION SUPPORT IS ENABLED
EZZ0704I IPV6 MULTIPATH PERPACKET SUPPORT IS ENABLED
EZZ0792I CANNOT ENABLE IPV6 MULTIPATH PERPACKET SUPPORT WHEN
IPV6 SECURITY IS ENABLED
EZZ0703I IPV6 MULTIPATH SUPPORT IS DISABLED
See the steps for modifying topic for information about changing this parameter while the TCP/IP stack is active. See TCP segmentation offload in z/OS Communications Server: IP Configuration Guide for more information about the TCP segmentation offload support.
EZZ0702I IPV6 SOURCEVIPA SUPPORT IS DISABLED
NOSOURCEVIPA is the default value.
Requirement: You must specify the SOURCEVIPAINTERFACE keyword on the INTERFACE statement for each interface on which you want that SOURCEVIPA to take effect.
The SOURCEVIPA parameter is confirmed by the message:EZZ0702I IPV6 SOURCEVIPA SUPPORT IS ENABLED
Tip: The use of SOURCEVIPA or TCPSTACKSOURCEVIPA 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.
If the interface 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, see the default source address selection algorithm information in z/OS Communications Server: IPv6 Network and Application Design Guide.
EZZ0760I IPV6 TCPSTACKSOURCEVIPA IS IGNORED - SOURCEVIPA IS NOT ENABLED
EZZ0821I IPV6 TEMPORARY ADDRESS SUPPORT IS DISABLED
NOTEMPADDRS
is the default value.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. See the information about default source address selection in the z/OS Communications Server: IPv6 Network and Application Design Guide .
EZZ0816I IPV6 TEMPORARY ADDRESS SUPPORT IS ENABLED
Guideline: Do not specify a small pref_lifetime value with a large valid_lifetime value. A large number of deprecated temporary addresses can have an impact on storage usage.
If dynamic XCF definitions have been enabled but a later VARY TCPIP,,OBEYFILE command contains NODYNAMICXCF, only future dynamic definitions and connectivity are affected. Existing definitions and connectivity are not affected.