The z/VM virtual switch is enhanced to transparently bridge a guest virtual machine network connection on a HiperSockets LAN segment. This bridge allows a single HiperSockets guest virtual machine network connection to also directly communicate with the following:

• Other guest virtual machines on the virtual switch
• External network hosts through the virtual switch OSA UPLINK port

z/VM CP APAR VM65042, TCP/IP APAR PM46988, and Perfkit APAR VM65044 are required for this support. For more information see Virtual switch HiperSockets bridge

z/VM V6.2 implements multisystem virtualization using a z/VM single system image (SSI) cluster composed of up to four z/VM systems. This multisystem virtualization technology for the mainframe extends the z/VM virtualization technology to a new level, allowing members of the cluster to share resources and synchronize with other nodes, together presenting the appearance of a single system.

All members of a cluster share LAN segments and IP subnets. The concept of a global virtual switch provides identical network connectivity across all active members within a cluster.

z/VM enables access to the IBM zEnterprise System intranode management network (INMN) and intraensemble data network (IEDN) through the real and virtual networking capabilities of z/VM. As a result, the deployment and management of z/VM network topology is integrated into the zEnterprise environment and can be managed by the Unified Resource Manager. When connected to a z196 or z114 through the INMN, the resources of the zBX are viewed as a logical extension of the z196 or z114. These resources are then controlled and managed through the Hardware Management Console (HMC) and Support Element (SE) of the z196 or z114. The INMN requires an OSA-Express3 1000BASE-T, while the IEDN requires a port on two separate OSA-Express3 or OSA-Express4S 10 GbE features. Managing z/VM V6.2 from the Unified Resource Manager requires the z196 or z114 to be at driver level 93.

z/VM now provides the ability for a guest to have multiple unique access ports connected to the same virtual switch instance. Each access port has its own attributes (promiscuous and OSDSIM authority) and VLAN ID. Methods to associate guest NICs and VSWITCH ports are also provided. With this support, configuring a server to provide connectivity to multiple VLANs is easier because the guest does not need to be VLAN-aware. In addition, customers can choose which port numbers will be used. Because the mapping of systems to switch ports is known ahead of time, SNMP monitoring of the switch status is more useful, allowing virtual switches to be monitored and managed more like real switches.

The z/VM TCP/IP NETSTAT command has been enhanced with an option to display information such as IP addresses and MAC addresses from the OSA Address Table (OAT) for OSA devices and virtual switch controllers. Installation of OSA/SF to satisfy diagnostic requirements in service situations is no longer necessary for OSA-Express3 or OSA-Express4S devices.

1. New VLAN AWARE and NATIVE NONE operands and attributes
2. New Uplink NIC selection
3. New MAC address assignment and usage enforcement