z/VM IPv6 Support


IPv6 support was first introduced in z/VM starting with z/VM Release 4.4. This web page and associated links documents the z/VM IPv6 support that is currently available in CMS, CP and TCP/IP.


IPv6 support in CMS

  • Starting in z/VM Release 5.1 and above:
    • The set of C and C++ language functions that are part of the OpenExtensions sockets and resolver interfaces were updated or extended to support IPv6. These interfaces are documented in the C/C++ for z/VM Run-Time Library Reference (SC09-7624).
    • A subset of the OpenExtensions callable services which are callable from Assembler and REXX were updated to support IPv6. These callable services are documented in the OpenExtensions Callable Services Reference (SC24-6105).
  • Starting in z/VM Release 6.1 and above:
    • C and OpenExtensions sockets were updated to supported scope based routing. z/VM Release 6.1 requires APAR PM06209 for this support.
  • Starting in z/VM Release 6.2 and above:
    • The SENDFILE command was updated to support IPv6.
    • The NOTE command was updated to support IPv6.
  • Starting in z/VM Release 6.4 and above:
    • The resolver can now be configured to communicate with a DNS server using an IPv6 address
  • Details of IPv6 support in CMS


IPv6 support in CP

  • Starting in z/VM Release 4.4 and above, guests on a QDIO Guest LAN were able to define and use simulated OSA-Express devices supporting IPv6.
  • Starting in z/VM Release 5.1 and above, IPv6 networks are possible with the ETHERNET (Layer 2) VSWITCH support. Guests on IP-type VSWITCHes can also send IPv6 traffic but only to other guests (it won't flow out the RDEV connection to the real hardware network). z/VM Release 5.1 requires CP APAR VM63538 and TCP/IP APAR PQ98202 for this support.
  • Starting in z/VM Release 5.2 and above, guests on a HiperSockets Guest LAN were able to define and use simulated HiperSockets devices supporting IPv6. z/VM Release 5.2 requires APAR VM63850 for this support.
  • z/VM Virtual Networking


IPv6 support in TCP/IP

  • Starting in z/VM Release 5.1 and above:
    • The TCP/IP stack can be configured for IPv6 networks connected through OSA-Express operating in QDIO Ethernet mode. The stack can be configured to provide static routing of IPv6 packets and to send IPv6 Router Advertisements. The native z/VM TCP/IP applications that have been enhanced to support IPv6 are IFCONFIG, IPWIZARD, NETSTAT, PING, and TRACERTE.
  • Starting in z/VM Release 5.2 and above:
    • The TCP/IP stack can be configured to provide static routing of IPv6 packets and send IPv6 Router Advertisements for HiperSockets QDIOIP link types. z/VM Release 5.2 requires APAR PK14010 for this support.
    • The MPROUTE server was updated to support the IPv6 RIP and OSPF protocols.
  • Starting in z/VM Release 5.3 and above:
    • The failover support in the TCP/IP stack for QDIO Ethernet devices configured for IPv6 has been improved.
    • Virtual IP address support in the TCP/IP stack has been extended to support IPv6 addresses.
  • Starting in z/VM Release 6.2 and above
    • The FTP server was updated to support IPv6.
    • The FTP client was updated to support IPv6.
    • The SMTP server was updated to support IPv6
  • Starting in z/VM Release 6.3 and above
    • The SSL server was updated to support IPv6.
    • The FTP client was updated to support secure IPv6 connections.
    • The FTP server was updated to support secure IPv6 connections.
    • The Telnet client was updated to support secure IPv6 connections.
    • The Telnet server was updated to support secure IPv6 connections.
    • The SMTP server was updated to support secure IPv6 connections.
  • Details of IPv6 support in TCP/IP

Please direct questions, comments and feedback regarding z/VM's IPv6 support or any of the information on this page to:

Miguel Delapaz
z/VM Development
migueld@us.ibm.com

Note: **
All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on this Statement of Direction is at the relying party's sole risk and will not create any liability or obligation for IBM.