Open Systems Adapter-Express
This chapter describes the IBM Open Systems Adapter-Express features. These features provide connectivity to other servers and clients in 1000BASE-T Ethernet (10, 100, and 1000 Mbps), Gigabit Ethernet (GbE), and 10-Gigabit Ethernet environments.
|
Terminology: If not stated otherwise, the term OSA applies to all OSA-Express features throughout this book.
|
The following topics are covered in this chapter:
|
Statement of Direction: This chapter makes references to IBM Statements of Direction (SoDs). All statements regarding IBM plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these SoDs is at the relying party's sole risk and will not create liability or obligation for IBM.
|
5.1 Functional description
The six generations of the OSA-Express features (OSA-Express, OSA-Express2, OSA-Express3, OSA-Express4S, OSA-Express5S, and OSA-Express6S) integrate several hardware features and support many networking transport protocols. Every new OSA-Express feature provides enhancements in the areas of function, connectivity, bandwidth, data throughput, network availability, reliability, and recovery.
5.1.1 Operating modes
The integration of a channel path with network ports makes the OSA a unique channel or CHPID type, which is recognized by the hardware I/O configuration on a port-by-port basis as one of the following types:
•Queued Direct Input/Output (OSD)
•Non-Queued Direct Input/Output (OSE)
•OSA Integrated Console Controller (OSC)
•Open Systems Adapter for Network Control Program (OSN)
•OSA-Express for zEnterprise BladeCenter Extension (OSX)
•OSA-Express for Management of an ensemble (OSM)
•OSA-Express for Dynamic Partition Manager (OSM)
Not all features support all CHPID types. Table 5-1 provides an overview of the type of traffic that is supported. It also indicates whether the Open Systems Adapter Support Facility (OSA/SF) is required to configure the OSA-Express6S, OSA-Express5S, or OSA-Express4S ports that are based on the supported modes of operation (CHPID types).
OSA and Dynamic Partition Manager
OSM channel type can support Dynamic Partition Manager and Ensemble Management. Both functions can be configured and ordered, but they cannot be enabled at the same time on the system. Dynamic Partition Manager requires two OSA-Express 1000BASE-T Ethernet features for primary and backup connectivity. The OSA-Express5S 1000BASE-T Ethernet or OSA-Express6S 1000BASE-T Ethernet features cannot be shared and must be dedicated for usage by Dynamic Partition Manager when configured. The OSA-Express5S 1000BASE-T Ethernet or OSA-Express6S 1000BASE-T Ethernet features cannot be shared and must be dedicated for usage only by Dynamic Partition Manager or only by Ensemble Membership (depending on which function is enabled on the system).
Table 5-1 Supported CHPID types
|
CHPID
type
|
Feature
|
SNA/APPN/HPR traffic
|
IP traffic
|
TN3270E traffic
|
OSA/SF
|
|
OSD
|
OSA-Express6S 10 GbE
OSA-Express5S 10 GbE
OSA-Express4S 10 GbE
OSA-Express3 10 GbE
OSA-Express6S GbE
OSA-Express5S GbE
OSA-Express4S GbE
OSA-Express3 GbE
OSA-Express6S 1000BASE-T
OSA-Express5S 1000BASE-T
OSA-Express4S 1000BASE-T
OSA-Express3 1000BASE-T
|
|
Yes
|
No
|
Optional
|
|
OSE
|
OSA-Express6S 1000BASE-T
OSA-Express5S 1000BASE-T
OSA-Express4S 1000BASE-T
OSA-Express3 1000BASE-T
|
Yes
|
Yes
|
No
|
Required
|
|
OSC3
|
OSA-Express6S 1000BASE-T
OSA-Express5S 1000BASE-T
OSA-Express4S 1000BASE-T
OSA-Express3 1000BASE-T
|
No
|
No
|
Yes
|
N/A
|
|
OSM
|
OSA-Express6S 1000BASE-T
OSA-Express5S 1000BASE-T
OSA-Express4S 1000BASE-T
OSA-Express3 1000BASE-T
|
No
|
Yes
|
No
|
N/A
|
|
OSX
|
OSA-Express6S 10 GbE
OSA-Express5S 10 GbE
OSA-Express4S 10 GbE
OSA-Express3 10 GbE
|
No
|
Yes
|
No
|
N/A
|
1 SNA over IP with the use of Enterprise Extender or TN3270. See 5.2.17, “Enterprise Extender” on page 94 and 5.2.18, “TN3270E Server” on page 94.
2 Layer 2 support allows for non-IP protocols, such as SNA. See 5.2.13, “Layer 2 support” on page 88.
3 OSA-ICC (OSC Channel) now supports Secure Sockets Layer for z14, z13, and z13s. See the IBM Z HMC driver level for feature support.
Open Systems Adapter Support Facility
OSA/SF is a host-based tool that is used to customize and manage all OSA features:
•OSA/SF is not required for the OSA feature that is configured for the QDIO mode or the default IP Passthru non-QDIO mode. However, it can be used for problem determination purposes.
•OSA/SF is not required for OSA port CHPID type OSN, although information about channel use can be displayed through OSA/SF for OSN CHPIDs.
•OSA/SF is a required facility when the OSA feature is being configured for shared non-QDIO mode and where SNA definitions are involved.
•With the z14, z13, z13s, zEC12, and zBC12, OSA/SF, the HMC is enhanced to provide configuration, validation, activation, and display support for the OSA-Express6S, OSA-Express5S, and OSA-Express4S features:
– OSA/SF on the HMC is required for OSA-Express6S and OSA-Express5S features.
– Either OSA/SF on the HMC or the OSA/SF in the operating system component can be used for the OSA-Express4S feature.
One OSA/SF application can communicate with all OSA features in an IBM Z platform. OSA/SF communicates with an OSA feature through a device (type OSD) defined by using HCD/IOCP. For more information, see 5.1.5, “OSA/SF support” on page 79.
QDIO versus non-QDIO
Figure 5-1 illustrates the much shorter I/O process when in QDIO mode rather than non-QDIO mode. I/O interrupts and I/O path-lengths are minimized, resulting in improved performance versus non-QDIO mode, reduced system assist processor (SAP) use, improved response time, and reduced system use.
Figure 5-1 Non-QDIO data path versus QDIO data paths
OSA-Express3, OSA-Express4S, OSA-Express5S, and OSA-Express6S features use direct memory access (DMA) and a data router model to eliminate store and forward delays that might occur with the OSA-Express21 features when in QDIO mode.
Also, in QDIO mode, all OSA features dynamically receive configuration information from the host. This process reduces configuration and setup time, eliminates duplicate data entry, and reduces the possibility of data entry errors and incompatible definitions.
5.1.2 QDIO mode
QDIO is a highly efficient data transfer mechanism that dramatically reduces system overhead and improves throughput by using system memory queues and a signaling protocol to directly exchange data between the OSA microprocessor and network software. QDIO is the interface between the operating system and the OSA hardware.
The following components make up QDIO:
•Direct memory access (DMA)
•Data router
•Priority queuing
•Dynamic OSA address table building
•LPAR-to-LPAR communication
•Internet Protocol (IP) Assist functions
QDIO supports IP and non-IP traffic with the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features. These features support two transport modes:
•Layer 2 (Link Layer) for IP (IPv4, IPv6) and non-IP (AppleTalk DECnet, IPX, NetBIOS, or SNA) traffic
•Layer 3 (Network Layer) for IP traffic only
A more detailed description of the Layer 2 support is provided in 5.2.13, “Layer 2 support” on page 88.
Direct memory access
OSA and the operating system share a common storage area for memory-to-memory communication, reducing system overhead, and improving performance. Data can move directly from the OSA microprocessor to system memory and vice versa by using a store-and-forward technique in DMA. There are no read or write channel programs for data exchange. For write processing, no I/O interrupts must be handled. For read processing, the number of I/O interrupts is minimized.
Data router
With OSA-Express4S, OSA-Express5S, and OSA-Express6S, what was previously done in Licensed Internal Code (LIC) is now performed on hardware. Additional logic has been added in the IBM ASIC processor of the OSA feature to handle packet construction, inspection, and routing. This feature allows packets to flow between host memory and the LAN at line speed without firmware intervention. With the data router, the store and forward technique in DMA is no longer used, which enables a direct host memory-to-LAN flow and avoids a hop. It reduces latency and increases throughput for standard frames (1492 bytes) and jumbo frames (8992 bytes).
Priority queuing
Priority queuing is supported by the QDIO architecture and introduced with the Service Policy Server (for z/OS environments only). It sorts outgoing IP message traffic according to the service policy that is set up for the specific priority that is assigned in the IP header.
This capability is an alternative to the best-effort priority assigned to all traffic in most IP networks. Priority queuing allows the definition of four different priority levels for IP network traffic through the OSA features defined for QDIO. For example, the highest priority can be granted to interactive communications, and the lowest can be granted to batch traffic, with two more categories in between, perhaps based on particular user groups or projects.
QDIO uses four write (outbound) queues and one read (inbound) queue for each IP network stack that is sharing the OSA feature.
OSA signals the z/OS Communications Server when there is work to do. z/OS Communications Server puts outbound packets in one of the four queues, based on priority settings.
At a certain time, z/OS Communications Server signals the OSA feature that there is work to do. The OSA feature searches the four possible outbound queues by priority and sends the packets to the network, giving more priority to queues 1 and 2, and less priority to queues 3 and 4. For example, if there is data on every queue, queue 1 is served first, then portions of queue 2, then fewer portions of queue 3, then even fewer portions of queue 4, and then back to queue 1. This process means that four transactions are running across the four queues. Over time, queue 1 finishes first, queue 2 finishes second, and so on.
|
Note: With OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3, priority queuing is enabled by default. This feature reduces the total number of supported IP network stacks and devices (see “Maximum IP network stacks and subchannels” on page 78).
|
Dynamic OSA Address Table update
With QDIO, the dynamic OSA Address Table (OAT) update process simplifies installation and configuration tasks. The definition of IP addresses is done in one place, the IP network profile, thus removing the requirement to enter the information into the OAT by using the OSA/SF.
The OAT entries are dynamically built when the corresponding IP device in the IP network stack is started.
At device activation, all IP addresses contained in the IP network stack’s IP HOME list are downloaded to the OSA port. Corresponding entries are built in the OAT. Subsequent changes to these IP addresses cause an update of the OAT.
LPAR-to-LPAR communication
Access to an OSA port can be shared among the system images that are running in the logical partitions to which the channel path is defined to be shared. Also, access to a port can be shared concurrently among IP network stacks in the same logical partition or in different logical partitions.
When sharing ports, an OSA port operating in QDIO mode can send and receive IP traffic between logical partitions without sending the IP packets to the LAN and then back to the destination logical partition.
For outbound IP packets, the OSA port uses the next-hop IP address within the packet to determine where it is sent. If the next-hop IP address was registered by another IP network stack that is sharing the OSA port, the packet is sent directly to that IP network stack, not onto the LAN. This feature makes the forwarding of IP packets possible within the same host system.
Internet Protocol Assist functions
OSA QDIO helps IP processing and offloads the IP network stack functions for the following processes:
•Multicast support (see “IP network multicast and broadcast support” on page 85)
•Broadcast filtering (see “IP network multicast and broadcast support” on page 85)
•Building MAC and LLC headers
•Address Resolution Protocol (ARP) processing (see “Address Resolution Protocol cache management” on page 86)
•Checksum offload (see “Checksum offload support for z/OS and Linux on z Systems” on page 87)
QDIO functions
The QDIO functions that are discussed in this section are supported on z14, z13, z13s, zEC12, and zBC12.
IP network functions
These are IP network functions:
•Large send for IP network traffic for OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 (see “Large send for IP network traffic” on page 82)
•640 IP network stacks (see “Maximum IP network stacks and subchannels” on page 78)
Hardware assists
Complementary virtualization technology is available that includes these capabilities:
•QDIO Enhanced Buffer-State Management (QEBSM). Two hardware instructions help eliminate the overhead of hypervisor interception.
•Host Page-Management Assist (HPMA). An interface to the IBM z/VM operating system main storage management function to allow the hardware to assign, lock, and unlock page frames without z/VM hypervisor assistance.
These hardware assists allow a cooperating guest operating system to start QDIO operations directly to the applicable channel, without interception by z/VM, which helps improve performance. Support is integrated in IBM Z Licensed Internal Code.
QDIO Diagnostic Synchronization for z/OS
QDIO Diagnostic Synchronization is exclusive to IBM Z, and the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features when configured as CHPID type OSD (QDIO). It provides the system programmer and network administrator with the ability to coordinate and simultaneously capture both operating system (software) and OSA (hardware) traces at the same instance of a system event.
This process allows the host operating system to signal the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features to stop traces and capture the current trace records. Using existing tools (traps) and commands, the operator can capture both hardware and software traces at the same time and then correlate the records during post processing.
OSA-Express Network Traffic Analyzer for z/OS
The OSA-Express Network Traffic Analyzer is exclusive to IBM Z and the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features when configured as CHPID type OSD (QDIO). It allows trace records to be sent to the host operating system to improve the capability to capture data for both the system programmer and the network administrator. This function allows the operating system to control the sniffer trace for the LAN and capture the records in host memory and storage. It uses existing host operating system tools to format, edit, and process the sniffer records.
5.1.3 Non-QDIO mode
Similar to any other channel-attached control unit and device, an OSA port can run channel programs (CCW chains) and present I/O interrupts to the issuing applications. For non-QDIO mode, the OSA ports are defined as channel type OSE. The non-QDIO mode requires the use of the OSA/SF for setup and customization of the OSA features.
The 1000BASE-T features support non-QDIO mode. This mode supports SNA, APPN, HPR, and IP network traffic simultaneously through the OSA port. This section discusses the non-QDIO mode types.
IP network Passthru
In IP network Passthru mode, an OSA feature transfers data between an IP network stack to which it is defined and clients on an Ethernet 10/100/1000 Mbps LAN. The LAN is attached to the port on a 1000BASE-T feature and supports one of the following frame protocols:
•Ethernet II using the DEC Ethernet V 2.0 envelope
•Ethernet 802.3 using the 802.2 envelope with SNAP
For IP network Passthru mode, the default OAT can be used. In that case, no configuration or setup is required.
SNA/APPN/HPR support
In this mode, an OSA feature acts as an SNA Passthru agent to clients that use the SNA protocol on the LAN that is directly attached to the OSA. If an OSA feature is running in the SNA mode, it is viewed by IBM VTAM® as an external communication adapter (XCA) that can use either switched or non-switched lines of communication.
5.1.4 OSA addressing support
This section describes the maximum number IP addresses, MAC addresses, and subchannels that are supported by the OSA features.
Maximum IP addresses per OAT
The OAT is a component of an OSA feature’s configuration. An OAT entry defines the data path between an OSA feature port and a logical partition (LP) and device unit address. That is, it manages traffic through the OSA CHPID.
OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features support up to 4096 IP addresses per port.
When the OSA port is defined in QDIO mode, the OAT table entries are built and updated dynamically.
Maximum number of MAC addresses
When configured as an OSD CHPID type, up to 2048 (up to 4096 for the z14) Media Access Control (MAC) or virtual MAC (VMAC) addresses are supported for each port of the OSA feature. Included in the maximum number of MAC addresses is the “burned-in” MAC address of the OSA port.
The MAC or VMAC addresses are added to the Layer 2 table of the OAT when the IP network stacks (in which the addresses are defined) are started.
For more information, see 5.2.13, “Layer 2 support” on page 88 and 5.2.16, “Layer 3 VMAC for z/OS” on page 93.
Maximum IP network stacks and subchannels
A subchannel is a logical representation of a device. One subchannel is assigned for each device that is defined to the logical partition. Therefore, if an OSA CHPID is being shared across 15 LPARs and one device is defined, that device uses 15 subchannels.
These are the maximum number of supported IP network stacks and subchannels:
•OSA port in non-QDIO mode (CHPID type OSE)
An OSA port in non-QDIO mode can support up to 120 IP network stacks and 240 subchannels for all IBM Z platforms.
•OSA port in QDIO mode (CHPID type OSD)
The OSA features support 640 IP network stack connections per dedicated CHPID, or 640 total stacks across multiple logical partitions when defined as a shared or spanned CHPID. The maximum number of subchannels that are allowed is 1920 (1920 subchannels / 3 = 640 stacks).
|
Note: By default, OSA-Express6S, OSA-Express6S, OSA-Express4S, and OSA-Express3 have multiple priorities for outbound queues enabled (four QDIO priorities). Therefore, the maximum number of supported subchannels is reduced to 480 (1920 subchannels / 4 = 480 subchannels), which reduces the total number of supported IP network stacks to 160 (480 subchannels / 3 = 160 stacks). Priority queues can be disabled through HCD or IOCP. For example, in IOCP use the CHPARM=02 value to disable priority queuing.
|
5.1.5 OSA/SF support
OSA/SF includes a graphical user interface (GUI) that is based on Java to support the client application. The Java GUI is independent of any operating system or server, and is expected to operate wherever the current Java runtime support is available.
Use of the GUI is optional. A REXX command interface is also included with OSA/SF. OSA/SF is integrated in z/OS, z/VM, and z/VSE, and runs as a host application. For OSA/SF, Java GUI communication is supported through IP networks only. This version of OSA/SF is not being offered as a separately licensed product.
Starting with driver 22 installed on z13 and with next driver up to 32 on z14 server, the HMC is enhanced to use OSA/SF function for the OSA-Express6S, OSA-Express5S, and OSA-Express4S features. Either OSA/SF on the HMC or the OSA/SF in the operating system component can be used for the OSA-Express4S features. For the OSA-Express6S and OSA-Express5S features, OSA/SF on the HMC is required.
OSA/SF is used primarily for the following purposes:
•Manage all OSA ports.
•Configure all OSA non-QDIO ports.
•Configure local MAC addresses.
•Display registered IPv4 addresses (in use and not in use). This display is supported on IBM Z platforms for QDIO ports.
•Display registered IPv4 or IPv6 Virtual MAC and VLAN ID associated with all OSA Ethernet features configured as QDIO Layer 2.
•Provide status information about an OSA port and its shared or exclusive use state.
This support is applicable to all OSA features on IBM Z platforms.
OSA/SF is not always required to customize an OSA feature. However, it can be used to gather operational information, to help on problem determination, to monitor, and to control ports. The OSA/SF Query function provides performance information about the OSA CHPIDs. As shown in Table 5-1 on page 72, OSA/SF is not required to configure the OSA features in any operating modes except OSE.
5.2 OSA capabilities
This section describes the capabilities that use the OSA-Express6S, OSA-Express5S, and OSA-Express4S features.
5.2.1 Virtual IP address
In the IP network environment, virtual IP address (VIPA) frees IP network hosts from dependence on a particular network attachment, allowing the establishment of primary and secondary paths through the network. VIPA is supported by all of the OSA features.
An IP address traditionally ties to a physical link at one end of a connection. If the associated physical link goes down, it is unreachable. The virtual IP address exists only in software and has no association to any physical link. The IP network stack is the destination IP address rather than the network attachment.
VIPA provides for multiple IP addresses to be defined to an IP network stack, allowing fault-tolerant, redundant backup paths to be established. Applications become insensitive to the condition of the network because the VIPAs are always active. This configuration enables users to route around intermediate points of failure in the network.
VIPA takeover and takeback
Because a VIPA is associated with an IP network stack and not a physical network attachment, it can be moved to any IP network stack within its network. If the IP network stack that the VIPA is on fails (because of an outage), the same VIPA can be brought up automatically on another IP network stack (VIPA takeover). This process allows users to reach the backup server and applications. The original session between the user and original server is not disrupted. After the failed IP network stack is restored, the same VIPA can be moved back automatically (VIPA takeback).
5.2.2 Primary/secondary router function
The primary/secondary router function enables an OSA port to forward packets with unknown IP addresses to an IP network stack for routing through another IP network interface, such as IBM HiperSockets or another OSA feature.
For an OSA port to forward IP packets to a particular IP network stack for routing to its destination, the PRIRouter must be defined on the DEVICE statement in the IP network profile.
If the IP network stack that has an OSA port that is defined as PRIRouter becomes unavailable, the following process occurs: A second IP network stack that is defined as the secondary router (SECRouter on the DEVICE statement in the IP network profile) receives the packets for unknown IP addresses.
For enhanced availability, the definition of one primary router and multiple secondary routers for devices on an OSD-type CHPID is supported. However, only one secondary router is supported for devices on an OSE-type CHPID.
|
Important: Sharing a single OSA port (with a single MAC address) can fail in load-balancing solutions. A workaround is to use generic routing encapsulation (GRE) or network address translation (NAT), which can have a negative effect on performance. Layer 3 virtual MAC is a function available on IBM Z platforms with OSA features that allows multiple MAC addresses on a single OSA port. For more information, see 5.2.16, “Layer 3 VMAC for z/OS” on page 93.
|
5.2.3 IPv6 support
Internet Protocol version 6 (IPv6) is supported by the OSA features when configured in QDIO mode. IPv6 is the protocol that is designed by the Internet Engineering Task Force (IETF) to replace Internet Protocol version 4 (IPv4). IPv6 provides improved traffic management in the following areas:
•128-bit addressing
This improvement eliminates all practical limitations on global address ability. Private address space, along with the NATs used between a private intranet and the public internet, are no longer needed.
•Simplified header formats
This improvement allows for more efficient packet handling and reduced bandwidth cost.
•Hierarchical addressing and routing
This feature keeps routing tables small and backbone routing efficient by using address prefixes rather than address classes.
•Improved support for options
This improvement changes the way IP header options are encoded, allowing more efficient forwarding and greater flexibility.
•Address auto-configuration
This change allows stateless IP address configuration without a configuration server. In addition, IPv6 brings greater authentication and privacy capabilities through the definition of extensions, and integrated quality of service (QoS) through a traffic class byte in the header.
5.2.4 Large send for IP network traffic
Large send (also referred to as TCP segmentation offload) can improve performance by offloading TCP packet processing from the host to the OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 features that are running in QDIO mode. Offload allows the host to send large blocks of data (up to 64 KB) directly to the OSA. The OSA then fragments those large blocks into standard Ethernet frames (1492 bytes) to be sent on the LAN (Figure 5-2).
Figure 5-2 Large send versus standard Ethernet and jumbo frame sizes
Large send support reduces host processor use, so it returns processor cycles for application use and increases network efficiencies. For OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features, large send supports outbound IPv4 traffic only and applies solely to unicasts. Large send support for IPv6 packets applies to the OSA-Express6S, OSA-Express5S, and OSA-Express4S features (CHPID types OSD and OSX) available on z14, z13, z13s, zEC12, and zBC12.
|
Note: Large send for IPv6 packets is not supported for LPAR-to-LPAR packets.
|
5.2.5 VLAN support
Virtual local area network (VLAN) is supported by the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features when configured in QDIO mode. This support is applicable to z/OS, z/VM, and Linux on z Systems environments.
The IEEE standard 802.1q describes the operation of virtual bridged local area networks. A VLAN is defined to be a subset of the active topology of a local area network. The OSA features provide for the setting of multiple unique VLAN IDs per QDIO data device. They also provide for both tagged and untagged frames to flow from an OSA port. The number of VLANs supported is specific to the operating system.
VLANs facilitate easy administration of logical groups of stations, which can communicate as though they were on the same LAN. They also facilitate easier administration of moves, adds, and changes in members of these groups. VLANs are also designed to provide a degree of low-level security by restricting direct contact with a server to only the set of stations that comprise the VLAN.
With IBM Z platforms where multiple IP network stacks exist and potentially share one or more OSA features, VLAN support provides a greater degree of isolation (Figure 5-3).
Figure 5-3 VLAN support
VLAN support for z/OS
Full VLAN support is offered for all OSA Ethernet features that are available on IBM Z platforms. The IBM z/OS Communications Server supports virtual local area network Identifications (VLAN IDs). With z/OS version 13.1, support is offered for up to 32 global VLAN IDs per OSA port for IPv4 and IPv6.
VLAN support for z/VM
z/VM uses the VLAN technology and conforms to the IEEE 802.1q standard. Support is offered for one global VLAN ID per OSA port for IPv4 and IPv6. Each port can be configured with a different VLAN ID.
VLAN support for Linux on z Systems
VLAN support in a Linux on z Systems environment is available for the OSA Ethernet features that operate in QDIO mode.
VLAN support of GARP VLAN Registration Protocol
Generic Attribute Registration Protocol (GARP) VLAN Registration Protocol (GVRP) is defined in the IEEE 802.1p standard for the control of IEEE 802.1q VLANs. It can be used to simplify networking administration and management of VLANs.
With GVRP support, an OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 port can register or unregister its VLAN IDs with a GVRP-capable switch and dynamically update its table as the VLANs change (see Figure 5-4).
Figure 5-4 GVRP support
Support of GVRP is exclusive to IBM Z. It is applicable to all of the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features when in QDIO mode (CHPID type OSD), and is supported by z/OS and z/VM.
5.2.6 SNMP support for z/OS and Linux on z Systems
SNMP is supported for all of the OSA features when configured in the QDIO mode (CHPID type OSD). The OSA features LIC includes the following support for the OSA SNMP subagent:
•Get and GetNext requests
This support applies to all OSA features supported on IBM Z platforms.
•dot3StatsTable
Ethernet data for dot3StatsTable applies to all of the Ethernet features that are supported on IBM Z platforms. It implements the SNMP EtherLike Management Information Base (MIB) module in RFC 2665, which provides statistics for Ethernet interfaces. These statistics can help in the analysis of network traffic congestion.
•Performance data
This support applies to all of the OSA features supported on IBM Z platforms. The performance data reflects the OSA use.
•Traps and Set
This support applies to all of the OSA features supported on IBM Z.
SNMP support for LAN channel station (LCS) applies to all of the OSA features that are supported on IBM Z, along with IP network applications only. It supports the same SNMP requests and alerts that are offered in QDIO mode (Get, GetNext, Trap, and Set) and is exclusive to the z/OS environment.
|
Tip: You can subscribe to the “OSA-Express Direct SNMP MIB module” document through Resource Link to receive email notifications of document changes.
|
OSA/SF is not required to manage SNMP data for the OSA features. An SNMP subagent exists on an OSA feature, which is part of a direct path between the z/OS or Linux on IBM Z master agent (IP network stacks) and an OSA-Express MIB.
The OSA features support an SNMP agent by providing data for use by an SNMP management application, such as IBM Tivoli NetView® for z/OS. This data is organized into MIB tables that are defined in the IP network enterprise-specific MIB and standard RFCs. The data is supported by the SNMP IP network subagent (Figure 5-5).
Figure 5-5 SNMP support, z/OS example
5.2.7 IP network multicast and broadcast support
Multicast and broadcast support are part of the Internet Protocol Assist (IPA) function of the OSA feature.
Multicast support
For sending data to multiple recipients, OSA features support IP multicast destinations only in QDIO or IP Passthru mode.
IP network broadcast support for z/OS, z/VM, and Linux on z Systems
Broadcast support is included for all of the OSA features when configured in QDIO mode and supporting the Routing Information Protocol (RIP) version 1. Broadcast is also supported for all of the OSA features when carrying IP network traffic and configured in the non-QDIO mode (LAN Channel Station in LCS mode).
A broadcast simultaneously transmits data to more than one destination. Messages are transmitted to all stations in a network (for example, a warning message from a system operator). The broadcast frames can be propagated through an OSA feature to all IP network applications that require broadcast support, including applications that use RIP V1.
5.2.8 Address Resolution Protocol cache management
The query and purge Address Resolution Protocol (ARP) enhancements are supported for all OSA features when configured in QDIO mode. The OSA feature maintains a cache of recently acquired IP-to-physical address mappings (or bindings). When the binding is not found in the ARP cache, a broadcast (an ARP request: “How can I reach you?”) to find an address mapping is sent to all hosts on the same physical network. Because a cache is maintained, ARP does not have to be used repeatedly, and the OSA feature does not have to keep a permanent record of bindings.
Query ARP table for IPv4 for Linux on z Systems
The Query ARP table is supported by using Internet Protocol version 4 (IPv4). The IP network stack already has an awareness of Internet Protocol version 6 (IPv6) addresses.
Purge ARP entries in cache for IPv4 for z/OS and Linux on z Systems
Purging of entries in the ARP cache is supported by using IPv4. The IP network stack already has an awareness of IPv6 addresses.
ARP takeover
ARP takeover provides the capability of switching OSA port operations from one OSA to another OSA running in the same mode in z/OS environments.
When a z/OS IP network is started in QDIO mode, it downloads all of the home IP addresses in the stack and stores them in each OSA feature to which it has a connection. This is a service of the QDIO architecture and occurs automatically only for OSD channels. For OSA ports set up as OSE channels (non-QDIO), multiple IP addresses must be defined in the OAT by using OSA/SF. The OSA then responds to ARP requests for its own IP address and for VIPAs.
If an OSA feature fails and a backup OSA available on the same network or subnetwork, IP network informs the backup OSA which IP addresses (real and VIPA) to take over, and the network connection is maintained. For this technique to work, multiple paths must be defined to the IP network stack. For example, MULTIPATH must be defined to the IPCONFIG statement of the IP network profile in z/OS.
ARP statistics
QDIO includes an IPA function, which gathers ARP data during the mapping of IP addresses to Media Access Control (MAC) addresses. CHPIDs that are defined as OSD maintain ARP cache information in the OSA feature (ARP offload). This data is useful in problem determination for the OSA feature.
5.2.9 IP network availability
There are several ways to ensure network availability if failure occurs at either the logical partition or the network connection level. Port sharing, redundant paths, and the use of primary and secondary ports all provide some measure of recovery. A combination of these can ensure network availability, regardless of the failing component.
5.2.10 Checksum offload support for z/OS and Linux on z Systems
z/OS and Linux on z Systems environments provide the capability of calculating and validating the Transmission Control Protocol/User Datagram Protocol (TCP/UDP) and IP header checksums. Checksums are used to verify the contents of files when transmitted over a network, such as these examples:
•OSA validates the TCP, UDP, and IP header checksums for inbound packets.
•OSA calculates the TCP, UDP, and IP header checksums for outbound packets.
Checksum offload is supported by all OSA Ethernet features when operating in QDIO mode.
By offloading checksum processing to the supporting OSA features, host system cycles are reduced, which can result in improved performance for most IPv4 packets.
|
Note: Linux on z Systems supports only inbound checksum offload (inbound packets).
|
When checksum is offloaded, the OSA feature calculates the checksum. For OSA-Express3 feature, this function applies only to packets that go onto the LAN or come in from the LAN. When multiple IP stacks share an OSA port and an IP stack sends a packet to a next-hop IP address that is owned by another IP stack that shares the same OSA port, OSA sends the IP packet directly to the other IP stack without placing it on the LAN. Checksum offload does not apply to such IP packets.
Starting with OSA-Express4S, the checksum offload is performed for IPv6 packets and IPv4 packets. This process occurs regardless of whether the traffic goes to the LAN, comes in from the LAN, or flows from one logical partition to another logical partition through OSA-Express6S, OSA-Express5S, or OSA-Express4S.
Checksum offload for IPv6 packets is exclusive to OSA-Express6S, OSA-Express5S, and OSA-Express4S features (CHPID types OSD and OSX) on the z14, z13, z13s, zEC12, and zBC12. Checksum offload for LPAR-to-LPAR traffic in the z/OS environment is included in the OSA-Express5S and OSA-Express4S design for both IPv4 and IPv6 packets.
Checksum offload support is available with z/OS and z/VM. For more information, see 5.3.3, “Software support” on page 116.
5.2.11 Dynamic LAN idle for z/OS
Dynamic LAN idle is exclusive to IBM Z platforms and applies to the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features (QDIO mode). It is supported by z/OS.
Dynamic LAN idle reduces latency and improves networking performance by dynamically adjusting the inbound blocking algorithm. When enabled, the z/OS IP network stack adjusts the inbound blocking algorithm to best match the application requirements.
For latency-sensitive applications, the blocking algorithm is modified to be latency sensitive. For streaming (throughput sensitive) applications, the blocking algorithm is adjusted to maximize throughput. In all cases, the z/OS IP network stack dynamically detects the application requirements and makes the necessary adjustments to the blocking algorithm. The monitoring of the application and the blocking algorithm adjustments are made in real time, so they dynamically adjust the application’s LAN performance.
System administrators can authorize the z/OS IP network stack to enable a dynamic setting, which was previously a static setting. The z/OS IP network stack dynamically determines the best setting for the current running application, based on system configuration, system, inbound workload volume, processor use, traffic patterns, and related items.
5.2.12 QDIO optimized latency mode
QDIO optimized latency mode (OLM) can help improve performance for applications that have a critical requirement to minimize response times for inbound and outbound data.
OLM optimizes the interrupt processing according to direction:
•For inbound processing, the IP network stack looks more frequently for available data to process. This feature ensures that any new data is read from the OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 without requiring more program-controlled interrupts (PCIs).
•For outbound processing, the OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 also look more frequently for available data to process from the IP network stack. Therefore, a Signal Adapter instruction (SIGA) is not required to determine whether more data is available.
OLM is supported by the Communications Server for z/OS with any OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 feature on z14, z13, z13s, zEC12, and zBC12.
5.2.13 Layer 2 support
The OSA Ethernet features on IBM Z platforms can support two transport modes of the OSI model:
•Layer 2 (Link Layer or MAC Layer)
•Layer 3 (Network Layer)
The Layer 2 transport mode allows for communication with IP and non-IP protocols. OSA works with either z/VM IP network or Linux on z Systems Layer 2 support that is running in a logical partition or as a z/VM guest.
The z/VM virtual switch can also be used to enable Layer 2 function for guest systems (Figure 5-6).
Figure 5-6 Layer 2 support for OSA
The virtual switch uses both Layer 2 and Layer 3 support in the z/VM Control Program. For Layer 2 support, the z/VM Control Program owns the connection to the OSA feature and manages the MAC addresses and VLAN connectivity of the attached guest systems. The virtual switch automatically generates the MAC address and assignment to ensure that the z/VM guest systems are unique. MAC addresses can also be locally administered.
The virtual switch uses each guest system’s unique MAC address to forward frames. Data is transported and delivered within Ethernet frames. This process provides the ability to transport both IP and non-IP frames (for example, NetBIOS and SNA) through the fabric that the virtual switch supports. Through the address-resolution process, each guest system’s MAC address becomes known to hosts on the physical side of the LAN segment. All inbound or outbound frames that pass through the OSA port have the guest system’s corresponding MAC address as the source or destination address.
The OSA Ethernet features can filter inbound frames by virtual local area network identification (VLAN ID, IEEE 802.1q), the Ethernet destination MAC address, or both. Filtering can reduce the amount of inbound traffic that is being processed by the operating system, which reduces processor use. Filtering by VLAN ID or MAC address can also enable you to isolate portions of your environment that have sensitive data to provide a degree of low-level security.
Link aggregation for z/VM in Layer 2 mode
Link aggregation is exclusive to IBM Z and is applicable to the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features in Layer 2 mode when configured as CHPID type OSD (QDIO). Link aggregation is supported by z/VM.
z/VM virtual switch-controlled (VSWITCH-controlled) link aggregation (IEEE 802.3ad) allows you to do the following when the port is participating in an aggregated group and is configured in Layer 2 mode:
•Dedicate an OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 port to the z/VM operating system
•Share an OSA-Express6S, OSA-Express5S, or OSA-Express4S port within a z/VM operating system
•Share an OSA-Express6S, OSA-Express5S, or OSA-Express4S port between any z/VM operating system that is running on the CPC
Link aggregation (trunking) allows you to combine multiple physical OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 ports into a single logical link. This configuration allows increased throughput and nondisruptive failover if a port becomes unavailable.
Link aggregation for z/VM in Layer 2 mode functions in these ways:
•Aggregated links are viewed as one logical trunk and contain all of the VLANs that are required by the LAN segment.
•Link aggregation is between a VSWITCH and the physical network switch.
•Load balance communications are across multiple links in a trunk to prevent a single link from being overrun.
•Up to eight OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 ports are supported in one aggregated link.
•OSA ports can be added or removed to provide on-demand bandwidth.
•It operates in full-duplex mode (send and receive) for increased throughput.
|
Note: Target links for aggregation must be of the same type (for example, Gigabit Ethernet to Gigabit Ethernet).
|
5.2.14 QDIO data connection isolation for z/VM
The QDIO data connection isolation function provides a higher level of security when sharing a OSA-Express port and virtual switch (VSWITCH) across multiple z/VM guest systems. The VSWITCH is a virtual network device that provides switching between OSA-Express ports and the connected guest systems.
Two modes allow for connection isolation: Port isolation and Virtual Ethernet Port Aggregator (VEPA). Port isolation and VEPA are mutually exclusive.
Port isolation
z/VM allows you to disable guest system-to-guest system communication through a virtual switch, preserving each guest system’s ability to communicate with hosts or routers in the external network. When a virtual switch is defined to be isolated, all communication between the guest systems’ ports on that virtual switch (VSWITCH) are disabled.
An isolated virtual switch is unable to communicate directly with other logical partitions that share the OSA-Express port. Communications must be relayed through another network-based device, such as a router or firewall, in the external network.
As shown in Figure 5-7, when in isolation mode, data traffic that is destined for a guest system port in the VSWITCH is blocked. However, traffic that is going to an external network device is sent to the OSA-Express port for delivery. The isolation options (ON or OFF) can be set by using the SET VSWITCH ISOLATION command.
Figure 5-7 VSWITCH port isolation
Virtual Ethernet Port Aggregation
VEPA is part of the IEEE 802.1Qbg standard. It provides the capability of sending all attached guest systems’ data traffic to an external Ethernet switch for further processing. This mode does not allow any direct guest system-to-guest system communications through the VSWITCH. In tandem with the VSWITCH, the OSA-Express feature prevents any data traffic between the VSWITCH and any connected systems that share that OSA-Express port. Hence, the isolation is provided within both the VSWITCH and the OSA-Express feature. However, VEPA mode does allow data traffic from a guest system to be sent to a router or similar network-based devices and come back through the same VSWITCH to another guest system. This is known as hairpinning.
For a VSWITCH to enter VEPA mode, the external Ethernet switch must be in Reflective Relay mode.
As shown in Figure 5-8, when in VEPA mode, data traffic that is destined for a guest system in the VSWITCH is forced to go to an external Ethernet switch through an OSA-Express port for further processing. VEPA mode (ON or OFF) can be set by using the SET VSWITCH VEPA command.
Figure 5-8 VSWITCH in VEPA mode
QDIO data connection isolation is supported by all OSA-Express6S features on z14 and, subsequently, all OSA-Express5S features on the z13, all OSA-Express4S features on the z13 and zEnterprise CPCs, and all OSA-Express3 features on the zEnterprise CPCs.
5.2.15 QDIO interface isolation for z/OS
Some environments require strict controls for routing data traffic between systems or nodes. In certain cases, the LPAR-to-LPAR capability of a shared OSA port can prevent such controls from being enforced. With interface isolation, internal routing can be controlled on an LPAR basis. When interface isolation is enabled, the OSA discards any packets that are destined for a z/OS LPAR that is registered in the OAT as isolated.
For example, in Figure 5-9, LPAR 1 has interface isolation enabled. Therefore, data traffic from LPAR 2 that is destined for LPAR 1 is dropped by the OSA.
Figure 5-9 QDIO interface isolation
QDIO interface isolation is supported by the Communications Server for z/OS with OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features on z14, z13, z13s, zEC12, and zBC12.
5.2.16 Layer 3 VMAC for z/OS
To help simplify the infrastructure and provide load balancing when a logical partition is sharing an OSA MAC address with another logical partition, each operating system instance can now have its own unique VMAC address. All IP addresses associated with an IP network stack are accessible by using their own VMAC address rather than sharing the MAC address of an OSA port. This applies to Layer 3 mode and to an OSA port shared among logical partitions.
This support has several benefits:
•Improves IP workload balancing
•Dedicates a Layer 3 VMAC to a single IP network stack
•Removes the dependency on GRE tunnels
•Improves outbound routing
•Simplifies configuration setup
•Allows z/OS to use a standard interface ID for IPv6 addresses
•Allows IBM WebSphere® Application Server content-based routing to support an IPv6 network
•Eliminates the need for PRIROUTER/SECROUTER function in z/OS
OSA Layer 3 VMAC for z/OS is applicable to OSA Ethernet features when configured as CHPID type OSD (QDIO).
|
Note: OSA layer 3 Virtual MAC support was first introduced with z/VM V4.4
|
5.2.17 Enterprise Extender
The Enterprise Extender (EE) function of z/OS Communications Server allows you to run SNA applications and data on IP networks and IP-attached clients. It can be used with any OSA feature that is running IP traffic. EE is a simple set of extensions to the open High-Performance Routing technology that integrates HPR frames into UDP/IP packets, which provide these advantages:
•SNA application connectivity by using an IP backbone support for:
– SNA-style priority
– SNA Parallel Sysplex
•Improved throughput and response times
•Compatible support for TCP and UDP traffic on the IP portion of the application traffic path (SNA/HPR and UDP/IP traffic can coexist on an EE connection)
The EE function is an IP network encapsulation technology. It carries SNA traffic from an endpoint over an IP network (for example, through the OSA port to the Communications Server) to another endpoint where it is de-encapsulated and presented to an SNA application.
EE requires APPN/HPR at the endpoints. To enable EE, you must configure the IP network stack with a virtual IP address and define an XCA major node. The XCA major node is used to define the PORT, GROUP, and LINE statements for the EE connections.
See the Enterprise Extender Implementation Guide, SG24-7359, for more information.
5.2.18 TN3270E Server
The TN3270E Server is supported by z/OS. It allows desktop users to connect through an IP network directly to SNA applications.
The following support is provided:
•Secure access using SSL and Client Authentication by using IBM Resource Access Control Facility (IBM RACF®)
•Over 64,000 sessions per server when using multiple ports
•Over 2000 transactions/second with subsecond response time
•Reconnect 16,000 sessions in less than a minute by using VIPA takeover support
•IP QoS using Service Policy server
•Host Print support
•Tivoli support provides IP visibility to VTAM
•Manage with your data center resources
•More robust than external TN3270 servers
z/OS Communications Server also supports a secure, RACF-based single sign-on logic called Express Logon Facility (ELF). ELF works with IBM TN3270 clients to securely authenticate the client, acquire a pass token, and then pass it on to the TN3270E server for replacement or submission to the application.
5.2.19 Adapter interruptions for QDIO
Linux on z Systems and z/VM work together to provide performance improvements by using extensions to the QDIO architecture. Adapter interruptions, which were first added to IBM z/Architecture with HiperSockets, provide an efficient, high-performance technique for I/O interruptions. This technique reduces path lengths and overhead in both the host operating system and the adapter when using type OSD CHPID.
In extending the use of adapter interruptions to OSD (QDIO) channels, the programming overhead to process a traditional I/O interruption is reduced. This technique benefits OSA IP network support in Linux on z Systems, z/VM, and z/VSE.
Adapter interruptions apply to all of the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features on a z14, z13, z13s, zEC12, and zBC12 when in QDIO mode (CHPID type OSD).
5.2.20 Inbound workload queuing
Inbound workload queuing (IWQ) helps reduce overhead and latency for inbound z/OS network data traffic and implements an efficient way for initiating parallel processing. This goal is achieved by using an OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 feature in QDIO mode (CHPID types OSD and OSX) with multiple input queues and by processing network data traffic that is based on workload types.
Figure 5-10 illustrates the IWQ concept of using multiple inbound queues for different types of workloads (T1 through T4) compared to a single inbound queue.
Figure 5-10 Single inbound queue versus multiple inbound queues
The data from a specific workload type is placed in one of four input queues, and a process is created and scheduled to run on one of multiple processors, independent from the three other queues. This process greatly improves performance because IWQ can use the symmetric multiprocessor (SMP) architecture of z14, z13, z13s, zEC12, and zBC12 systems.
A primary objective of IWQ is to provide improved performance for business-critical interactive workloads by reducing contention that is created by other types of workloads. These types of z/OS workloads are identified and assigned to unique input queues:
•z/OS Sysplex Distributor traffic
Network traffic that is associated with a distributed VIPA is assigned to a unique input queue, allowing the Sysplex Distributor traffic to be immediately distributed to the target host.
•z/OS bulk data traffic
Network traffic that is dynamically associated with a streaming (bulk data) TCP connection is assigned to a unique input queue. This technique allows most of the data processing to be assigned the appropriate resources and isolated from critical interactive workloads.
•Enterprise Extender traffic
Inbound Enterprise Extender traffic is differentiated and separated to a new input queue. This separation and processing provides improved scalability and performance for Enterprise Extender. It is supported on the z14, z13, z13s, zEC12, and zBC12 with OSA-Express6S, OSA-Express5S, OSA-Express4S, or OSA-Express3 features.
IPSec traffic on OSA-Express6S
OSA Express6S provides new support for Inbound Workload Queuing for IPSec, which allows OSA to separate inbound IPSec packets, enabling z/OS Communication Server to optimize the related software processing.
The supported IWQ IPSec traffic applies to protocols:
•Encapsulated Security Payload (ESP)
•Authentication Header (AH) protocol
•UDP protocol + port (NAT Traversal)
Users already using IWQ should be aware that each IWQ workload type that applies to their z/OS environment (for example, Sysplex distributor, Enterprise Extender) is automatically enabled when IWQ is enabled. Each unique input queue consumes extra fixed ECSA memory (approximately 4 MB per input queue per OSA interface).
5.2.21 Network management: Query and display OSA configuration
As complex functions have been added to OSA, the job of the system administrator to display, monitor, and verify the specific current OSA configuration unique to each operating system has become more complex. The operating system can directly query and display the current OSA configuration information (similar to OSA/SF). z/OS and z/VM use this OSA capability with an IP network operator command, which allows the operator to monitor and verify the current OSA configuration. This feature improves the overall management, serviceability, and usability of the OSA features.
Display OSAINFO is possible on OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 (CHPID types OSD, OSM, and OSX).
5.3 Connectivity
The transmission medium and cabling requirements for the OSA ports depend on the OSA feature, OSA port type, and LAN. Acquiring cables and other connectivity items is the IBM client’s responsibility.
|
Removal of support for IEEE 802.3 Ethernet frame types: The zEC12 and zBC12 were the last IBM Z platforms to support IEEE 802.3 Ethernet frame types on OSA-Express QDIO interfaces in Layer 3 mode.
This statement applies to CHPID types OSD and OSX when they are used in Layer 3 mode. These OSA-Express CHPID types in Layer 3 mode are planned to support Ethernet DIX version 2 (DIX V2) exclusively on future IBM Z platforms.
OSA-Express non-QDIO (CHPID type OSE) supporting SNA, APPN, HPR with Link Station Architecture (LSA), TCP/IP Passthru environments with LAN channel station (LCS), and QDIO CHPID types OSD and OSX running in Layer 2 mode are not affected by this change.
|
OSA devices
The different types of OSA channels (CHPID types) require the following device types:
•OSA devices for QDIO (OSD) and non-QDIO (OSE) CHPID types
•3270-X and 3287 devices (consoles) for the OSA-ICC (OSC) CHPID type
•OSA devices for ensemble network connectivity (OSX) and ensemble management (OSM) CHPID types
OSA/SF requires one device (defined through HCD) to be associated with the OSA CHPID as device type OSAD (UNITADD=FE). OSA/SF uses this device to communicate with the OSA feature.
The OSA-Express Network Traffic Analyzer for z/OS requires one or more data paths devices for the OSAENTA trace interface, depending on the configuration.
Multiple image facility
Multiple image facility (MIF) enables OSA ports that are installed on IBM Z platforms to be shared across logical partitions. For more information, see Chapter 2, “Channel subsystem overview” on page 15.
Spanned channels
Spanning is the ability to configure channels to multiple channel subsystems. When defined that way, the channels can be transparently shared by any or all of the configured logical partitions, regardless of the channel subsystem to which the logical partition is configured.
OSA ports can be spanned across multiple channel subsystems (CSSes) on IBM Z platforms. See 2.1.2, “Multiple CSS concept” on page 17, for more information about spanned channels.
5.3.1 OSA features
Table 5-2 lists the OSA-Express6S, OSA-Express5S, OSA-Express4S, and OSA-Express3 features that are supported on IBM Z platforms along with the maximum number of OSA ports that are supported by each system. For all optical links, the connector type is LC duplex unless otherwise specified. The electrical Ethernet cable for the OSA connectivity is through an RJ 45 jack. Details for each feature that is supported on z14, z13, zEC12, and zBC12 are provided in subsequent sections.
Table 5-2 IBM Z OSA features
|
Feature name
|
Feature code
|
Cable type
|
Maximum unrepeated distance1
|
System
|
|
OSA-Express6S GbE LX
|
0422
|
SM 9 µm
|
10 km
|
z14
|
|
OSA-Express6S GbE SX
|
0423
|
MM 50 µm
|
550 m (500)
|
z14
|
|
MM 62.5 µm
|
275 m (200)
220 m (160)
|
|||
|
OSA-Express6S 10 GbE LR
|
0424
|
SM 9 µm
|
10 km
|
z14
|
|
OSA-Express6S 10 GbE SR
|
0425
|
MM 50 µm
|
550 m (500)
|
z14
|
|
MM 62.5 µm
|
275 m (200)
220 m (160)
|
|||
|
OSA-Express6S 1000BASE-T
|
0426
|
UTP Cat5 or 6
|
100 m
|
z14
|
|
|
|
|||
|
OSA-Express5S
GbE LX
|
0413
|
SM 9 µm
|
5 km
|
z13, z13s, zEC12, zBC12
|
|
MCP2
|
550 m (500)
|
|||
|
OSA-Express5S
GbE SX
|
0414
|
MM 50 µm
|
550 m (500)
|
z13, z13s, zEC12, zBC12
|
|
MM 62.5 µm
|
275 m (200)
220 m (160)
|
|||
|
OSA-Express5S 10 GbE LR
|
0415
|
SM 9 µm
|
10 km
|
z13, z13s, zEC12, zBC12
|
|
OSA-Express5S 10 GbE SR
|
0416
|
MM 50 µm
|
550 m (500)
|
z13, z13s, zEC12, zBC12
|
|
MM 62.5 µm
|
275 m (200)
220 m (160)
|
|||
|
OSA-Express5S 1000BASE-T
|
0417
|
UTP Cat5 or 6
|
100 m
|
z13, z13s, zEC12, zBC12
|
|
OSA-Express4S
GbE LX
|
0404
|
SM 9 µm
|
5 km
|
|
|
MCPb
|
550 m (500)
|
|||
|
OSA-Express4S
GbE SX
|
0405
|
MM 50 µm
|
550 m (500)
|
|
|
MM 62.5 µm
|
275 m (200)
220 m (160)
|
|||
|
OSA-Express4S 10 GbE LR
|
0406
|
SM 9 µm
|
10 km
|
|
|
OSA-Express4S 10 GbE SR
|
0407
|
MM 50 µm
|
300 m (2000)
82 m (500)
|
|
|
MM 62.5 µm
|
33 m (200)
|
|||
|
OSA-Express4s 1000BASE-T
|
0408
|
UTP Cat5 or 6
|
100 m
|
|
|
OSA-Express3
GbE LX
|
3362
|
SM 9 µm
|
5 km
|
|
|
MCPb
|
550 m (500)
|
|||
|
OSA-Express3
GbE SX
|
3363
|
MM 50 µm
|
550 m (500)
|
|
|
MM 62.5 µm
|
275 m (200)
220 m (166)
|
|||
|
OSA-Express3-2P
GbE SX
|
3373
|
MM 50 µm
|
550 m (500)
|
zBC12c
|
|
MM 62.5 µm
|
275 m (200)
220 m (166)
|
|||
|
OSA-Express3 10
GbE LR
|
3370
|
SM 9 µm
|
10 km
|
|
|
OSA-Express3 10
GbE SR
|
3371
|
MM 50 µm
|
300 m (2000)
82 m (500)
|
|
|
MM 62.5 µm
|
33 m (200)
|
|||
|
OSA-Express3 1000BASE-T
|
3367
|
UTP Cat5 or 6
|
100 m
|
|
|
OSA-Express3-2P 1000BASE-T
|
3369
|
UTP Cat5 or 6
|
100 m
|
zBC12c
|
1 Minimum fiber bandwidth in MHz/km for multimode fiber optic links is included in parentheses where applicable.
2 Mode-conditioning patch (MCP) cables enable the 1 Gbps single mode features to connect to multimode fiber.
3 Available on carry-forward only.
On a z14 system, the maximum number of OSA-Express6S features is 48 with any mix of OSA-Express6S and OSA-Express5S features.
On a z13 system, the maximum number of OSA-Express5S features is 98, and the maximum number of OSA-Express4S features (carry-forward only) is 48.
On a z13s system, the maximum number of OSA-Express5S and OSA-Express4S combined features (carry-forward only) is 48.
On a zEC12, the maximum OSA-Express3, OSA-Express4S, and OSA-Express 5S features depends on the mix of those features. On a zEC12, the maximum number of OSA-Express3 features is 24 (carry forward only). The maximum number of OSA-Express4S features alone is 48. The maximum number of OSA-Express3, OSA-Express4S, and OSA-Express5S that are mixed is determined based on a maximum of 48 PCHIDs.
On a zBC12, the maximum number of OSA-Express3 features is 8 (carry forward only) or 16 with RPQ 8P2733 for the second I/O drawer (carry forward only). The maximum OSA-Express4S (carry forward only) and OSA-Express5S features is 48.
Table 5-3 shows the numbers of I/O features supported on zEC12 systems.
Table 5-3 z14 supported I/O features
|
I/O feature
|
Ports per feature
|
Ports per CHPID
|
Max. number of
|
CHPID definition
|
|
|
Ports
|
I/O slots
|
||||
|
OSA-Express6S
GbE LX/SX
|
2
|
2
|
96
|
48
|
OSD
|
|
OSA-Express6S
10 GbE LR/SR
|
1
|
1
|
48
|
48
|
OSD, OSX
|
|
OSA-Express6S
1000BASE-T
|
2
|
2
|
96
|
48
|
OSE, OSD, OSC, OSM
|
|
OSA-Express5S
GbE LX/SX
|
2
|
2
|
96
|
48
|
OSD
|
|
OSA-Express5S
10 GbE LR/SR
|
1
|
1
|
48
|
48
|
OSD, OSX
|
|
OSA-Express5S
1000BASE-T
|
2
|
2
|
96
|
48
|
OSE, OSD, OSC, OSM
|
|
OSA-Express4S 1000BASE-T
|
2
|
2
|
96
|
48
|
OSE, OSD, OSC, OSM
|
Table 5-4 shows the number of I/O features supported on z13 systems.
Table 5-4 z13 and z13s systems supported I/O features
|
I/O feature
|
Ports per feature
|
Ports per CHPID
|
Maximum number1 of
|
CHPID definition
|
|
|
Ports
|
I/O Slots
|
||||
|
OSA-Express4S
GbE LX/SX
|
2
|
2
|
96
|
48
|
OSD
|
|
OSA- Express4S
10 GbE LR/SR
|
1
|
1
|
48
|
48
|
OSD, OSX
|
|
OSA-Express4S 1000BASE-T
|
2
|
2
|
96
|
48
|
OSE, OSD, OSC2, OSN, OSM
|
|
OSA-Express5S
10 GbE LR/SR
|
1
|
1
|
48
|
48
|
OSD, OSX
|
|
OSA-Express5S
GbE LX/SX
|
2
|
2
|
96
|
48
|
OSD
|
|
OSA-Express5S
1000BASE-T
|
2
|
2
|
96
|
48
|
OSE, OSD, OSCb, OSN, OSM
|
1 The maximum number OSA-Express4S that are mixed is determined based on a maximum of 48 PCHIDs.
2 OSA-ICC (OSC Channel) now supports Secure Sockets Layer (z13s and z13 GA2). Up to 48 secure sessions per CHPID are supported (the overall maximum of 120 connections is unchanged).
OSA-Express6S 10-Gigabit Ethernet Long Reach (GbE LR) feature
Feature code 0424 is supported exclusively on the z14 server and can be installed only in the PCIe I/O drawer. It occupies one slot and has one port with an SFP transceiver and an LC duplex receptacle. This feature connects to a 10 Gbps Ethernet LAN through a 9-micron single mode fiber optic cable that is terminated with an LC duplex connector and supports an unrepeated maximum distance of 10 km (6.2 miles). The SFP allows a concurrent repair or replace action.
The OSA-Express6S 10 GbE LR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express6S 10 GbE LR supports 64b/66b encoding, whereas GbE supports 8b/10 encoding, making auto-negotiation to any other speed impossible.
The one port of the OSA-Express6S 10 GbE LR feature has one CHPID assigned, and can be defined as type OSD or OSX. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-LR (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing
•DIX version 2
OSA-Express6S 10-Gigabit Ethernet Short Reach (GbE SR) feature
Feature code 0425 is supported exclusively on the z14 server and can be installed only in the PCIe I/O drawer. It occupies one slot and has one port with a small form-factor pluggable (SFP) transceiver and an LC duplex receptacle. This feature connects to a 10 Gbps Ethernet LAN through a 62.5-micron or 50-micron multimode fiber optic cable that is terminated with an LC duplex connector.
The following are the maximum supported unrepeated distances:
•33 meters (108 feet) on a 62.5 micron multimode (200 MHz) fiber optic cable
•82 meters (269 feet) on a 50-micron multimode (500 MHz) fiber optic cable
•300 meters (984 feet) on a 50-micron multimode (2000 MHz) fiber optic cable
The SFP allows a concurrent repair or replace action.
The OSA-Express6S 10 GbE SR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express5S 10 GbE SR supports 64b/66b encoding, whereas GbE supports 8b/10 encoding, which makes auto-negotiation to any other speed impossible.
The one port of the OSA-Express6S 10 GbE SR feature has one CHPID assigned, and can be defined as type OSD or OSX. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-SR (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3).
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing.
•DIX version 2.
OSA-Express6S Gigabit Ethernet Long Wavelength (GbE LX) feature
Feature code 0422 is supported on the z14 server and can be installed only in the PCIe I/O drawer. It occupies one slot and has two ports with an SFP transceiver and an LC duplex receptacle. This feature connects to a 1 Gbps Ethernet LAN through a 9-micron single mode fiber optic cable that is terminated with an LC duplex connector, supporting an unrepeated maximum distance of 5 km (3.1 miles).
A multimode (62.5- or 50-micron) fiber optic cable can be used with these features. The use of these multimode cable types requires an MCP cable at each end of the fiber optic link (see Table E-1 on page 194). Use of the single mode to multimode MCP cables reduces the supported distance of the link to a maximum of 550 meters (1084 feet). The SFP allows a concurrent repair or replace action.
The two ports of the OSA-Express6S GbE LX feature share a channel path identifier (CHPID type OSD exclusively). The use of both ports on a two-port CHPID requires support by the operating system. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The OSA-Express6S GbE LX feature does not support auto-negotiation to any other speed and runs in full duplex mode only.
The following Ethernet standards are applicable for the 1000BASE-LX (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-Express6S Gigabit Ethernet short wavelength (GbE SX) feature
Feature code 0423 is supported on the z14 and can be installed only in the PCIe I/O drawer. It occupies one slot and has two ports with an SFP transceiver and an LC duplex receptacle. This feature connects to a 1 Gbps Ethernet LAN through a 50-micron or 62.5-micron multimode fiber optic cable. The cable is terminated with an LC duplex connector over an unrepeated distance of 550 meters (for 50 µm fiber) or 220 meters (for 62.5 µm fiber). The SFP allows a concurrent repair or replace action.
The two ports of the OSA-Express6S GbE SX feature share a channel path identifier (CHPID type OSD exclusively). The use of both ports on a two-port CHPID requires support by the operating system. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The OSA-Express6S GbE SX feature does not support auto-negotiation to any other speed and runs in full duplex mode only.
The following Ethernet standards are applicable for the 1000BASE-SX (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-Express6S 1000BASE-T Ethernet feature
Feature code 0426 is exclusive to the z14 server and can be installed only in the PCIe I/O drawer. It occupies one slot in the PCIe I/O drawer and has two ports that connect to a 1000 Mbps (1 Gbps) or 100 Mbps Ethernet LAN. Each port has a Small Form-factor Pluggable (SFP) transceiver with an RJ-45 receptacle for cabling to an Ethernet switch. The SFP allows concurrent repair or replacement on each SFP. The RJ-45 receptacle must be attached by using EIA/TIA category 5 or 6 unshielded twisted pair (UTP) cable with a maximum length of 100 meters (328 feet).
The two ports of the OSA-Express6S 1000BASE-T feature have one CHPID assigned, so the two ports share one CHPID number. The use of both ports on a two-port CHPID requires support by the operating system.
The OSA-Express6S 1000BASE-T Ethernet feature supports auto-negotiation when attached to an Ethernet router or switch. If you allow the LAN speed to default to auto-negotiation, the OSA port and the attached router or switch auto-negotiate the LAN speed between them and connect at the highest common performance speed of interoperation. If the attached Ethernet router or switch does not support automatic negotiation, the OSA port examines the signal that it is receiving and connects at the speed and full-duplex mode of the device at the other end of the cable.
You can choose any one of the following settings for the OSA-Express6S 1000BASE-T Ethernet feature port:
•Auto-negotiate
•100 Mbps full-duplex
•1000 Mbps full-duplex
If you are not using auto-negotiate, the OSA port attempts to join the LAN at the specified speed. If this setting does not match the speed and duplex mode of the signal on the cable, the OSA port does not connect.
LAN speed can be set explicitly by using OSA/SF or the OSA Advanced Facilities function of the HMC. The explicit settings override the OSA feature port’s ability to auto-negotiate with its attached Ethernet switch.
Each OSA-Express6S 1000BASE-T CHPID can be defined as CHPID type OSD, OSE, OSC, or OSM. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for this feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-Express5S 10-Gigabit Ethernet Long Reach (GbE LR) feature
Feature code 0415 is supported on the z13, z13s, zEC12, and zBC12, and can be installed only in the PCIe I/O drawer. It occupies one slot and has one port with an SFP transceiver and an LC duplex receptacle. This feature connects to a 10 Gbps Ethernet LAN through a 9-micron single mode fiber optic cable that is terminated with an LC duplex connector and supports an unrepeated maximum distance of 10 km (6.2 miles). The SFP allows a concurrent repair or replace action.
The OSA-Express5S 10 GbE LR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express5S 10 GbE LR supports 64b/66b encoding, whereas GbE supports 8b/10 encoding, making auto-negotiation to any other speed impossible.
The one port of the OSA-Express5S 10 GbE LR feature has one CHPID assigned and can be defined as type OSD or OSX. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-LR (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing
•DIX version 2
OSA-Express5S 10-Gigabit Ethernet Short Reach (GbE SR) feature
Feature code 0416 is supported on the z13, z13s, zEC12, and zBC12, and can be installed only in the PCIe I/O drawer. It occupies one slot and has one port with an SFP transceiver and an LC duplex receptacle. This feature connects to a 10 Gbps Ethernet LAN through a 62.5-micron or 50-micron multimode fiber optic cable that is terminated with an LC duplex connector.
The following are the maximum supported unrepeated distances:
•33 meters (108 feet) on a 62.5 micron multimode (200 MHz) fiber optic cable
•82 meters (269 feet) on a 50-micron multimode (500 MHz) fiber optic cable
•300 meters (984 feet) on a 50-micron multimode (2000 MHz) fiber optic cable
The SFP allows a concurrent repair or replace action.
The OSA-Express5S 10 GbE SR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express5S 10 GbE SR supports 64b/66b encoding, whereas GbE supports 8b/10 encoding, which makes auto-negotiation to any other speed impossible.
The one port of the OSA-Express5S 10 GbE SR feature has one CHPID assigned and can be defined as type OSD or OSX. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-SR (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing
•DIX version 2
OSA-Express5S Gigabit Ethernet Long Wavelength (GbE LX) feature
Feature code 0413 is supported on the z13, z13s, zEC12, and zBC12, and can be installed only in the PCIe I/O drawer. It occupies one slot and has two ports with an SFP transceiver and an LC duplex receptacle. This feature connects to a 1 Gbps Ethernet LAN through a 9-micron single mode fiber optic cable that is terminated with an LC duplex connector, supporting an unrepeated maximum distance of 5 km (3.1 miles).
A multimode (62.5- or 50-micron) fiber optic cable can be used with these features. The use of these multimode cable types requires an MCP cable at each end of the fiber optic link (see Table F-1 on page 204). Use of the single mode to multimode MCP cables reduces the supported distance of the link to a maximum of 550 meters (1084 feet). The SFP allows a concurrent repair or replace action.
The two ports of the OSA-Express5S GbE LX feature share a channel path identifier (CHPID type OSD exclusively). The use of both ports on a two-port CHPID requires support by the operating system. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The OSA-Express5S GbE LX feature does not support auto-negotiation to any other speed and runs in full duplex mode only.
The following Ethernet standards are applicable for the 1000BASE-LX (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-Express5S Gigabit Ethernet short wavelength (GbE SX) feature
Feature code 0414 is supported on the z13, z13s, zEC12, and zBC12, and can be installed only in the PCIe I/O drawer. It occupies one slot and has two ports with an SFP transceiver and an LC duplex receptacle. This feature connects to a 1 Gbps Ethernet LAN through a 50-micron or 62.5-micron multimode fiber optic cable. The cable is terminated with an LC duplex connector over an unrepeated distance of 550 meters (for 50 µm fiber) or 220 meters (for 62.5 µm fiber). The SFP allows a concurrent repair or replace action.
The two ports of the OSA-Express5S GbE SX feature share a channel path identifier (CHPID type OSD exclusively). The use of both ports on a two-port CHPID requires support by the operating system. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The OSA-Express5S GbE SX feature does not support auto-negotiation to any other speed and runs in full duplex mode only.
The following Ethernet standards are applicable for the 1000BASE-SX (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-Express5S 1000BASE-T Ethernet feature
Feature code 0417 is exclusive to the z13, z13s, zEC12, and zBC12, and can be installed only in the PCIe I/O drawer. It occupies one slot in the PCIe I/O drawer and has two ports that connect to a 1000 Mbps (1 Gbps) or 100 Mbps Ethernet LAN. Each port has an SFP transceiver with an RJ-45 receptacle for cabling to an Ethernet switch. The SFP allows concurrent repair or replacement on each SFP. The RJ-45 receptacle must be attached by using EIA/TIA category 5 or 6 UTP cable with a maximum length of 100 meters (328 feet).
The two ports of the OSA-Express5S 1000BASE-T feature have one CHPID assigned, so the two ports share one CHPID number. The use of both ports on a two-port CHPID requires support by the operating system.
The OSA-Express5S 1000BASE-T Ethernet feature supports auto-negotiation when attached to an Ethernet router or switch. If you allow the LAN speed to default to auto-negotiation, the OSA port and the attached router or switch auto-negotiate the LAN speed between them and connect at the highest common performance speed of interoperation. If the attached Ethernet router or switch does not support automatic negotiation, the OSA port examines the signal that it is receiving and connects at the speed and full-duplex mode of the device at the other end of the cable.
You can choose any one of the following settings for the OSA-Express5S 1000BASE-T Ethernet feature port:
•Auto-negotiate
•100 Mbps full-duplex
•1000 Mbps full-duplex
If you are not using auto-negotiate, the OSA port attempts to join the LAN at the specified speed. If this does not match the speed and duplex mode of the signal on the cable, the OSA port does not connect.
LAN speed can be set explicitly by using OSA/SF or the OSA Advanced Facilities function of the HMC. The explicit settings override the OSA feature port’s ability to auto-negotiate with its attached Ethernet switch.
Each OSA-Express5S 1000BASE-T CHPID can be defined as CHPID type OSD, OSE, OSC, OSN, or OSM. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for this feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-ICC (CHPID type OSC) SSL Support
TLS/SSL with Certificate Authentication was added3 to the OSC CHPID to provide a secure and validated method for connecting clients to the IBM Z host. Up to 48 secure sessions per CHPID can be defined (the overall maximum of 120 connections is unchanged).
OSA-Express4S 10-Gigabit Ethernet Long Reach (10 GbE LR) feature
Feature code 0406 is supported on the zEnterprise CPCs and on z13 and z13s as a carry-forward. It can be installed only in the PCIe I/O drawer. It occupies one slot and has one port that connects to a 10 Gbps Ethernet LAN through a 9-micron single mode fiber optic cable. The cable is terminated with an LC duplex connector and supports an unrepeated maximum distance of 10 km (6.2 miles).
The OSA-Express4S 10 GbE LR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express4S 10 GbE LR supports 64B/66B encoding, whereas GbE supports 8B/10 encoding, making auto-negotiation to any other speed impossible.
The one port of the OSA-Express4S 10 GbE LR feature has one CHPID assigned and can be defined as type OSD or OSM. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-LR (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3).
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing.
•DIX version 2.
OSA-Express4S 10-Gigabit Ethernet Short Reach (10 GbE SR) feature
Feature code 0407 is supported on the zEnterprise CPCs and on the IBM z13 and z13s as a carry-forward. It can be installed only in the PCIe I/O drawer. It occupies one slot and has one port that connects to a 10 Gbps Ethernet LAN through a 62.5-micron or 50-micron multimode fiber optic cable that is terminated with an LC duplex connector. The following are the maximum supported unrepeated distances:
•33 meters (108 feet) on a 62.5-micron multimode (200 MHz) fiber optic cable
•82 meters (269 feet) on a 50-micron multimode (500 MHz) fiber optic cable
•300 meters (984 feet) on a 50-micron multimode (2000 MHz) fiber optic cable
The OSA-Express4S 10 GbE SR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express4S 10 GbE SR supports 64B/66B encoding, whereas GbE supports 8B/10 encoding, making auto-negotiation to any other speed impossible.
The one port of the OSA-Express4S 10 GbE SR feature has one CHPID assigned and can be defined as type OSD or OSM. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-SR (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3).
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing.
•DIX version 2.
OSA-Express4S Gigabit Ethernet Long Wavelength (GbE LX) feature
Feature code 0404 is supported on the zEnterprise CPCs and as a carry-forward on the z13 and z13s. It can be installed only in the PCIe I/O drawer. It occupies one slot and has two ports that connect to a 1 Gbps Ethernet LAN through a 9-micron single mode fiber optic cable. The cable is terminated with an LC duplex connector, supporting an unrepeated maximum distance of 5 km (3.1 miles). A multimode (62.5-micron or 50-micron) fiber optic cable can be used with these features. The use of these multimode cable types requires an MCP cable at each end of the fiber optic link (Table F-1 on page 204). Use of the single mode to multimode MCP cables reduces the supported distance of the link to a maximum of 550 meters (1084 feet).
The two ports of the OSA-Express4S GbE LX feature share a channel path identifier (CHPID type OSD, exclusively). The use of both ports on a two-port CHPID requires support by the operating system. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The OSA-Express4S GbE LX feature does not support auto-negotiation to any other speed and runs in full duplex mode only.
The following Ethernet standards are applicable for the 1000BASE-LX (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX Version 2
OSA-Express4S 10-Gigabit Ethernet Short Reach (10 GbE SR) feature
Feature code 0407 is supported on the zEnterprise CPCs and on the IBM z13 and z13s as a carry-forward. It can be installed only in the PCIe I/O drawer. It occupies one slot and has one port that connects to a 10 Gbps Ethernet LAN through a 62.5-micron or 50-micron multimode fiber optic cable that is terminated with an LC duplex connector. The following are the maximum supported unrepeated distances:
•33 meters (108 feet) on a 62.5-micron multimode (200 MHz) fiber optic cable
•82 meters (269 feet) on a 50-micron multimode (500 MHz) fiber optic cable
•300 meters (984 feet) on a 50-micron multimode (2000 MHz) fiber optic cable
The OSA-Express4S 10 GbE SR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express4S 10 GbE SR supports 64B/66B encoding, whereas GbE supports 8B/10 encoding, making auto-negotiation to any other speed impossible.
The one port of the OSA-Express4S 10 GbE SR feature has one CHPID assigned and can be defined as type OSD or OSM. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-SR (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3).
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing.
•DIX version 2.
OSA-Express4S Gigabit Ethernet Long Wavelength (GbE LX) feature
Feature code 0404 is supported on the zEnterprise CPCs and as a carry-forward on the z13 and z13s. It can be installed only in the PCIe I/O drawer. It occupies one slot and has two ports that connect to a 1 Gbps Ethernet LAN through a 9-micron single mode fiber optic cable. The cable is terminated with an LC duplex connector, supporting an unrepeated maximum distance of 5 km (3.1 miles). A multimode (62.5-micron or 50-micron) fiber optic cable can be used with these features. The use of these multimode cable types requires an MCP cable at each end of the fiber optic link (Table F-1 on page 204). Use of the single mode to multimode MCP cables reduces the supported distance of the link to a maximum of 550 meters (1084 feet).
The two ports of the OSA-Express4S GbE LX feature share a channel path identifier (CHPID type OSD, exclusively). The use of both ports on a two-port CHPID requires support by the operating system. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The OSA-Express4S GbE LX feature does not support auto-negotiation to any other speed and runs in full duplex mode only.
The following Ethernet standards are applicable for the 1000BASE-LX (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX Version 2
OSA-Express4S 1000BASE-T Ethernet feature
Feature code 0408 is exclusive to the zEC12 and can be installed only in the PCIe I/O drawer. It is supported on the z13 and z13s systems as carry-forward only and occupies one slot in the PCIe I/O drawer and has two ports that connect to a 1000 Mbps (1 Gbps), 100 Mbps, or 10 Mbps Ethernet LAN. Each port has an RJ-45 receptacle for cabling to an Ethernet switch. The RJ-45 receptacle must be attached by using EIA/TIA category 5 or 6 UTP cable with a maximum length of 100 meters (328 feet).
The two ports of the OSA-Express4S 1000BASE-T feature have one CHPID assigned, so the two ports share one CHPID number. The use of both ports on a two-port CHPID requires support by the operating system.
The OSA-Express4S 1000BASE-T Ethernet feature supports auto-negotiation when attached to an Ethernet router or switch. If you allow the LAN speed and duplex mode to default to automatic negotiation, the OSA port and the attached router or switch automatically negotiate the LAN speed and duplex mode settings. They connect at the highest common performance speed and duplex mode of interoperation. If the attached Ethernet router or switch does not support auto-negotiation, the OSA port examines the signal that it is receiving and connects at the speed and duplex mode of the device at the other end of the cable.
You can choose any one of the following settings for the OSA-Express4S 1000BASE-T Ethernet feature port:
•Auto-negotiate
•10 Mbps half-duplex
•10 Mbps full-duplex
•100 Mbps half-duplex
•100 Mbps full-duplex
•1000 Mbps full-duplex
|
Statement of Direction: The OSA-Express4S 1000BASE-T Ethernet feature is the last copper Ethernet feature to support half-duplex operation and a 10 Mbps link data rate. Any future 1000BASE-T Ethernet feature will support only full-duplex operation and auto-negotiation to 100 or 1000 Mbps exclusively.
|
If you are not using auto-negotiate, the OSA port attempts to join the LAN at the specified speed and duplex mode. If this does not match the speed and duplex mode of the signal on the cable, the OSA port does not connect.
LAN speed and duplex mode can be set explicitly by using OSA/SF or the OSA Advanced Facilities function of the HMC. The explicit settings override the OSA feature port’s ability to auto-negotiate with its attached Ethernet switch.
Each OSA-Express4S 1000BASE-T CHPID can be defined as CHPID type OSD, OSE, OSC, OSN, or OSM. See 5.1.1, “Operating modes” on page 72, for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for this feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX Version 2
OSA-ICC (CHPID type OSC) SSL Support
STLS/SSL with Certificate Authentication was added4 to the OSC CHPID to provide a secure and validated method for connecting clients to the IBM Z host. Up to 48 secure sessions per CHPID can be defined. The overall maximum of 120 connections is unchanged.
OSA-Express3 10-Gigabit Ethernet Long Reach (10 GbE LR) feature
Feature code 3370 is supported on the zEnterprise CPCs. It occupies one slot in the I/O cage or I/O drawer and has two ports that connect to a 10 Gbps Ethernet LAN through a 9-micron single-mode fiber optic cable. The cable is terminated with an LC duplex connector and supports an unrepeated maximum distance of 10 km (6.2 miles).
The OSA-Express3 10 GbE LR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express3 10 GbE LR supports 64B/66B encoding, whereas GbE supports 8B/10 encoding, making auto-negotiation to any other speed impossible.
The two ports of the OSA-Express3 10 GbE LR feature have two CHPIDs assigned and can be defined as type OSD or OSX. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-LR (standard transmission scheme):
•IEEE 802.3 (ISO/IEC 802.3).
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing.
•DIX Version 2.
OSA-Express3 10-Gigabit Ethernet Short Reach (10 GbE SR) feature
Feature code 3371 is supported on the zEnterprise CPC. It occupies one slot in the I/O cage or I/O drawer and has two ports that connect to a 10 Gbps Ethernet LAN through a 62.5-micron or 50-micron multimode fiber optic cable that is terminated with an LC duplex connector. The following are the maximum supported unrepeated distances:
•33 meters (108 feet) on a 62.5-micron multimode (200 MHz) fiber optic cable
•82 meters (269 feet) on a 50-micron multimode (500 MHz) fiber optic cable
•300 meters (984 feet) on a 50-micron multimode (2000 MHz) fiber optic cable
The OSA-Express3 10 GbE SR feature does not support auto-negotiation to any other speed and runs in full duplex mode only. OSA-Express3 10 GbE LR supports 64B/66B encoding, whereas GbE supports 8B/10 encoding, making auto-negotiation to any other speed impossible.
The two ports of the OSA-Express3 10 GbE SR feature have two CHPIDs assigned and can be defined as type OSD or OSX. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 10GBASE-SR (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3).
•Ethernet V2.0, including jumbo frames (those larger than 1518 bytes). Larger frame sizes increase efficiency for data intensive applications by reducing frame transmission processing.
•DIX Version 2.
OSA-Express3 Gigabit Ethernet Long Wavelength (GbE LX) feature
Feature code 3362 is supported on the zEnterprise CPCs. It occupies one slot in the I/O cage or I/O drawer and has four ports that connect to a 1 Gbps Ethernet LAN through a 9-micron single mode fiber optic cable. The cable is terminated with an LC duplex connector, supporting an unrepeated maximum distance of 5 km (3.1 miles). A multimode (62.5-micron or 50-micron) fiber optic cable can be used with this feature. The use of these multimode cable types requires an MCP cable at each end of the fiber optic link (see Table F-1 on page 204). Use of the single mode to multimode MCP cables reduces the supported distance of the link to a maximum of 550 meters (1084 feet).
The four ports of the OSA-Express3 GbE LX feature have two CHPIDs assigned, so two corresponding ports share one CHPID number. The use of both ports on a two-port CHPID requires support by the operating system.
The OSA-Express3 GbE LX feature does not support auto-negotiation to any other speed and runs in full duplex mode only.
Each OSA-Express3 GbE LX port can be defined as CHPID type OSD or OSN. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for the 1000BASE-LX (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-Express3 Gigabit Ethernet short wavelength (GbE SX) feature
Feature code 3363 is supported on the zEnterprise CPCs. It occupies one slot in the I/O cage or I/O drawer and has four ports that connect to a 1 Gbps Ethernet LAN through a 50-micron or 62.5-micron multimode fiber optic cable. The cable is terminated with an LC duplex connector over an unrepeated distance of 550 meters (for 50 µm fiber) or 220 meters (for 62.5 µm fiber).
The four ports of the OSA-Express3 GbE SX feature have two CHPIDs assigned, so two corresponding ports share one CHPID number. The use of both ports on a two-port CHPID requires support by the operating system.
The OSA-Express3 GbE SX feature does not support auto-negotiation to any other speed and runs in full duplex mode only.
Each OSA-Express3 GbE SX port can be defined as CHPID type OSD or OSN. See 5.1.1, “Operating modes” on page 72 for more about modes of operation and traffic types.
The following Ethernet standards are applicable for the 1000BASE-SX (standard transmission scheme) feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-Express3 1000BASE-T Ethernet feature
Feature code 3367 is supported on the zEnterprise CPCs. It occupies one slot in the I/O cage or I/O drawer and has four ports that connect to a 1000 Mbps (1 Gbps), 100 Mbps, or 10 Mbps Ethernet LAN. Each port has an RJ-45 receptacle for cabling to an Ethernet switch. The RJ-45 receptacle must be attached by using EIA/TIA Category 5 or 6 UTP cable with a maximum length of 100 meters (328 feet).
The four ports of the OSA-Express3 1000BASE-T feature have two CHPIDs assigned, so two corresponding ports share one CHPID number. Use of both ports on a two-port CHPID requires operating system support. When a CHPID is defined as OSM, only port 0 is usable.
The OSA-Express3 1000BASE-T Ethernet feature supports auto-negotiation when attached to an Ethernet router or switch. If LAN speed and duplex mode are allowed to default to auto-negotiation, the OSA port and the attached router or switch auto-negotiate the LAN speed and duplex mode settings between them. They connect at the highest common performance speed and duplex mode of interoperation. If the attached Ethernet router or switch does not support auto-negotiation, the OSA port examines the signal that it is receiving and connects at the speed and duplex mode of the device at the other end of the cable.
You can choose any one of the following settings for the OSA-Express3 1000BASE-T Ethernet feature port:
•Auto-negotiate
•10 Mbps half-duplex
•10 Mbps full-duplex
•100 Mbps half-duplex
•100 Mbps full-duplex
•1000 Mbps full-duplex
If auto-negotiate is not being used, the OSA port attempts to join the LAN at the specified speed and duplex mode. If this does not match the speed and duplex mode of the signal on the cable, the OSA port does not connect.
LAN speed and duplex mode can be set explicitly by using OSA/SF or the OSA Advanced Facilities function of the HMC. The explicit settings override the OSA feature port’s ability to auto-negotiate with the attached Ethernet switch.
Each OSA-Express3 1000BASE-T port can be defined as CHPID type OSD, OSE, OSC, OSN, or OSM. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for this feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
OSA-Express3-2P 1000BASE-T Ethernet feature
Feature code 3369 is supported on the zBC12 and occupies one slot in the I/O drawer. It has two ports that connect to a 1000 Mbps (1 Gbps), 100 Mbps, or 10 Mbps Ethernet LAN. Each port has an RJ-45 receptacle for cabling to an Ethernet switch. The RJ-45 receptacle must be attached by using EIA/TIA category 5 or 6 UTP cable with a maximum length of 100 meters (328 feet).
The two ports of the OSA-Express3-2P 1000BASE-T feature have one CHPID assigned, so the two ports share one CHPID number. The use of both ports requires support by the operating system.
The OSA-Express3-2P 1000BASE-T feature supports auto-negotiation when attached to an Ethernet router or switch. If you allow the LAN speed and duplex mode to default to auto-negotiation, the OSA port and the attached router or switch auto-negotiate the LAN speed and duplex mode settings between them. They connect at the highest common performance speed and duplex mode of interoperation. If the attached Ethernet router or switch does not support auto-negotiation, the OSA port examines the signal that it is receiving and connects at the speed and duplex mode of the device at the other end of the cable.
You can choose any one of the following settings for the OSA-Express3-2P 1000BASE-T feature port:
•Auto-negotiate
•10 Mbps half-duplex
•10 Mbps full-duplex
•100 Mbps half-duplex
•100 Mbps full-duplex
•1000 Mbps full-duplex
If auto-negotiate is not being used, the OSA port attempts to join the LAN at the specified speed and duplex mode. If this does not match the speed and duplex mode of the signal on the cable, the OSA port does not connect.
LAN speed and duplex mode can be set explicitly by using OSA/SF or the OSA Advanced Facilities function of the HMC. The explicit settings override the OSA-Express3-2p 1000BASE-T feature port’s ability to auto-negotiate with its attached Ethernet switch.
Each OSA-Express3-2P 1000BASE-T port can be defined as CHPID type OSD, OSE, OSC, or OSN. See 5.1.1, “Operating modes” on page 72 for details about modes of operation and supported traffic types.
The following Ethernet standards are applicable for this feature:
•IEEE 802.3 (ISO/IEC 802.3)
•DIX version 2
5.3.2 OSA function support
Table 5-5 lists the functions that are supported based on the OSA feature.
Table 5-5 OSA function support
|
Function
|
OSA-Express4S and OSA-Express5S
|
OSA-Express6S
|
||||
|
10 GbE
|
GbE
|
1000BASE-T
|
10 GbE
|
GbE
|
1000BASE-T
|
|
|
Jumbo frame support (8992-byte frame size)
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Network Traffic Analyzer for z/OS1
|
x
|
x
|
x
|
x
|
x
|
x
|
|
QDIO Diagnostic Synchronization for z/OSa
|
x
|
x
|
x
|
x
|
x
|
x
|
|
640 IP network (with priority queues disabled)a
|
x
|
x
|
x
|
x
|
x
|
x
|
|
Virtual IP address (VIPA)
|
x
|
x
|
x
|
x
|
x
|
x
|
|
Primary/secondary router function
|
x
|
x
|
x
|
x
|
x
|
x
|
|
Internet Protocol version 6 (IPv6)
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Large send support for IPv4
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Large send support for IPv6
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
VLAN (IEEE 802.1q)
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
VLAN support of GVRP (IEEE 802.1 p)a
|
x
|
x
|
x
|
x
|
x
|
x
|
|
SNMP support for z/OS and
Linux on z Systemsa |
x
|
x
|
x
|
x
|
x
|
x
|
|
Multicast and broadcast support
|
x
|
x
|
x
|
x
|
x
|
x
|
|
ARP cache management
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
ARP statisticsa
|
x
|
x
|
x
|
x
|
x
|
x
|
|
ARP takeover
|
x
|
x
|
x
|
x
|
x
|
x
|
|
IP network availability
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Checksum offload support for IPv4
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Checksum offload support for IPv6
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Dynamic LAN Idle for z/OSa
|
x
|
x
|
x
|
x
|
x
|
x
|
|
QDIO optimized latency mode
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Layer 2 support
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Link aggregation for z/VM Layer 2 modea
|
x
|
x
|
x
|
x
|
x
|
x
|
|
QDIO data connection isolation for z/VM
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
QDIO interface isolation for z/OS
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Layer 3 VMAC for z/OSa
|
x
|
x
|
x
|
x
|
x
|
x
|
|
Enterprise Extender
|
x
|
x
|
x
|
x
|
x
|
x
|
|
TN3270E server for z/OS
|
x
|
x
|
x
|
x
|
x
|
x
|
|
OSA for NCP support2
|
n/a
|
n/a
|
x
|
n/a
|
n/a
|
x
|
|
Adapter interruptions for QDIOa
|
x
|
x
|
x
|
x
|
x
|
x
|
|
Inbound workload queuing (IWQ)
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
Query and display OSA configuration
|
x
|
x
|
xa
|
x
|
x
|
xa
|
|
OSA-Express for IEDN connectivity
|
x
|
n/a
|
n/a
|
x
|
n/a
|
n/a
|
|
OSA-Express for INMN connectivity
|
n/a
|
n/a
|
x
|
n/a
|
n/a
|
x
|
1 Only in QDIO mode (CHPID type: OSD)
2 All IBM products supporting CHPID type OSN were withdrawn from marketing on March 9, 2015.
5.3.3 Software support
For more information about the operating systems that are supported on IBM Z platforms go to this website:
|
Note: Certain functions might require specific levels of an operating system, program temporary fixes (PTFs), or both. That information is provided when necessary within this chapter.
|
Consult the appropriate Preventive Service Planning (PSP) buckets (3906DEVICE, 2964DEVICE, 2965DEVICE, 2828DEVICE, and 2827DEVICE) before implementation.
5.3.4 Resource Measurement Facility
Resource Measurement Facility (RMF) reporting (z/OS only) supports the OSA features. It can capture performance data for these features:
•Microprocessor use (per logical partition image, if it applies)
•Physical Peripheral Component Interconnect (PCI) bus use
•Bandwidth per port (both read and write directions) per logical partition image
For example, with this support, possible bandwidth bottlenecks and root causes can be analyzed.
5.4 Summary
OSA features provide direct LAN connectivity as integrated features of the IBM Z platforms. This feature brings the strengths of IBM Z and z/Architecture to the modern network environment.
Table 5-6 summarizes the OSA features for the different modes of operation and maximum addressing ranges that are supported by IBM Z platforms.
Table 5-6 OSA modes of operation and addressing support
|
Addresses
|
|
|
IP addresses per channel path (IPv4, IPv6, VIPA)
|
4096
|
|
Multicast addresses (IPv4 + IPv6)
|
16384
|
|
ARP table size
|
16384
|
|
MAC addresses
|
20481
|
|
Non-QDIO (OSE)2
|
|
|
Subchannels per IP network link
|
2
|
|
IP network stacks per channel path
|
120
|
|
SNA PUs per port
|
4096
|
|
Subchannels per channel path
|
240
|
|
CUs per channel path
|
1
|
|
QDIO (OSD)
|
|
|
Subchannels per IP network link
|
3
|
|
IP network stacks per channel path
|
6403
|
|
Subchannels per channel path
|
1920c
|
|
CUs per channel path
|
16
|
1 4096 on the z14.
2 1000BASE-T feature only.
3 If multiple priority for queues is enabled, the maximum is reduced to 160 IP network stacks/480 devices.
5.5 References
For more information about the OSA features and configuration, see:
•Open Systems Adapter-Express Customer’s Guide and Reference, SA22-7935
•OSA-Express Implementation Guide, SG24-5948
•Communications Server: SNA Network Implementation Guide, SC31-8563
•Communications Server: IP Configuration, SC31-8513
•Resource Measurement Facility Report Analysis, SC28-1950
•IBM Communication Controller Migration Guide SG24-6298
•IBM Communication Controller for Linux on System z V1.2.1 Implementation Guide, SG24-7223
•Enterprise Extender Implementation Guide, SG24-7359
1 The OSA-Express2 and OSA-Express3 features are not supported on z14, z13, z13s, zEC12, and zBC12 systems.
2 All IBM products supporting CHPID Type OSN are withdrawn from marketing as of 9 March 2015.
3 Supported on z14, z13, and z13s. See the latest HMC driver level for feature support.
4 Supported on z14, z13, and z13s. See the latest HMC driver level for feature support.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.