Configuring network features
This chapter explains how to configure network to your z14 ZR1. It includes the following sections:
6.1 Preparation for defining and customizing OSA-Express
To define OSA-Express to your I/O configuration, you need following information:
•OSA operation mode (CHPID type)
•PCHID of OSA-Express and the CHPID number that is associated with that PCHID
•CHPID access list and candidate list within the LCSS
•CNTLINIT number and IODEVICE number
For more information about these operations, see Chapter 13, “Adding network devices” on page 293.
Depending on your network configuration and environment, you can perform OSA-Express customization by using OSA Advanced facilities. OSA advanced facilities are used for customizing the following settings:
•OSA Address Table (OAT) and SNA timer
•Physical port speed
•MAC address
For more information about these settings, see 6.3, “Customizing OSA-Express using OSA Advanced facilities” on page 127.
6.2 Defining OSA Express to your I/O configuration
Defining the OSA-Express involves the following high-level steps:
6.2.1 Choosing the OSA-Express CHPID type
Before OSA-Express is used, you must choose the CHPID type. The CHPID types that are supported in z14 ZR1 are listed in Table 6-1. For more information, see the Open Systems Adapter-Express Customer's Guide and Reference, SA22-7935, and IBM Z Connectivity Handbook, SG24-5444.
Table 6-1 OSA-Express CHPID types that are supported in z14 ZR1
|
CHPID type
|
OSA-Express operation mode
|
|
OSE
|
Non-Queued Direct Input/Output mode for SNA and TCP/IP networking
|
|
OSD
|
Queued Direct Input/Output mode for TCP/IP networking
|
|
OSC
|
OSA Integrated Console Controller
|
|
OSX
|
OSA Express for Intraensemble Data Network (IEDN)
|
|
OSM
|
OSA Express for Intraensemble Management Network (INMN)
|
|
Note: CHPID type OSN is not supported in z14 ZR1.
|
6.2.2 Defining the OSA-Express to IO configuration
You must define the CHPID, CNTLUNIT, and IODEVICE parameters for using OSA-Express. For more information about how to define I/O configuration using HCD, see Chapter 13, “Adding network devices” on page 293.
6.2.3 Confirm your OSA-Express IO definition
You can confirm your definition by using the following z/OS command:
DISPLAY M=CHP(xx)
You can confirm the CHPID path status by using the command that is shown in Figure 6-1.
|
D M=CHP(B9)
IEE174I 14.25.14 DISPLAY M 744
CHPID B9: TYPE=11, DESC=OSA DIRECT EXPRESS, ONLINE
DEVICE STATUS FOR CHANNEL PATH B9
0 1 2 3 4 5 6 7 8 9 A B C D E F
01B9 + + + + + + + + + + + + . . . +
SWITCH DEVICE NUMBER = NONE
PHYSICAL CHANNEL ID = 016C
PNETID 1 = PERFNET
************************ SYMBOL EXPLANATIONS ************************
+ ONLINE @ PATH NOT VALIDATED - OFFLINE . DOES NOT EXIST
* PHYSICALLY ONLINE $ PATH NOT OPERATIONAL
|
Figure 6-1 OSD D M=CHP
Confirm the channel path to a device by using the following command:
DISPLAY M=DEV(xxxx)
The node descriptor information that is returned includes the emulated control unit 1730.008 and 1732.001, which are used for the OSA-Express6S port. Also included is the 3907 machine type and serial number, as shown in Figure 6-2.
|
D M=DEV(1B90)
IEE174I 14.39.13 DISPLAY M 751
DEVICE 01B90 STATUS=ONLINE
CHP B9
ENTRY LINK ADDRESS ..
DEST LINK ADDRESS 0D
PATH ONLINE Y
CHP PHYSICALLY ONLINE Y
PATH OPERATIONAL Y
MANAGED N
CU NUMBER 1B90
INTERFACE ID 6C00
MAXIMUM MANAGED CHPID(S) ALLOWED: 0
DESTINATION CU LOGICAL ADDRESS = 00
SCP CU ND = 001730.008.IBM.02.390700007A88.B900
SCP TOKEN NED = 001730.008.IBM.02.390700007A88.B900
SCP DEVICE NED = 001732.001.IBM.02.390700007A88.B900
|
Figure 6-2 The OSD M=DEV command
Confirm the device number and the status by using the following command:
DISPLAY U
The device number and type of device that is defined are shown in Figure 6-3.
|
D U,,,1B90,1
IEE457I 14.42.59 UNIT STATUS 753
UNIT TYPE STATUS VOLSER VOLSTATE SS
1B90 OSA A-BSY 0
D U,,,1B9F,1
IEE457I 14.45.21 UNIT STATUS 755
UNIT TYPE STATUS VOLSER VOLSTATE SS
1B9F OSAD O-RAL 0
|
Figure 6-3 The OSD D U,,,device command
6.3 Customizing OSA-Express using OSA Advanced facilities
OSA Advanced facilities is a tool that is integrated in the HMC. To start OSA Advanced facilities, log in to the HMC with the correct authority, and select the CPC that requires OSA customization. Then, select Operational Customization → OSA Advanced Facilities (see Figure 6-4).
Figure 6-4 HMC OSA Advanced facility selection
The OSA Advanced Facilities window that is shown in Figure 6-5 opens.
Figure 6-5 OSA Advanced Facilities initial window
6.3.1 Configuring OAT and SNA LLC2 timer for OSE channel
When you define OSA-Express as OSE channel (non-QDIO mode), you must customize OSA Address Table (OAT) except for the following uses:
•Use only the default OAT and do not use (require) port sharing.
•OSA-Express Direct SNMP subagent.
For more information, see Open Systems Adapter-Express Customer's Guide and Reference, SA22-7935.
You can edit OAT with Open Systems Adapter/Support Facility (OSA/SF). OSA/SF is a tool for customizing OSA-Express. From zEC12 GA2, the OSA/SF tool is available on HMC. It is included as a submenu of the OSA Advanced facilities.
You must use OSA/SF on the HMC to define OSA Address Table (OAT) and SNA definition for OSA-Express5S/6S. You can still use OSA/SF running on z/OS for OSA-Express4S, but generally migrate to OSA/SF on HMC.
The OSA/SF tool capabilities are compared in Table 6-2.
Table 6-2 OSA/SF comparison
|
Type of OSA/SF
|
Supported OSA Express
|
|
On HMC
|
OSA Express-4S/5S/6S
|
|
On z/OS, z/VM
|
OSA Express-4S
|
For other CHPID types, OSA/SF is not required. If you need to change the port speed or the Media Access Control (MAC) address, you can configure it from the OSA Advanced Facility. The OSA CHPID type and OSA/SF requirements are listed in Table 6-3.
Table 6-3 OSA/SF and OSA CHPID reference
|
OSA CHPID type
|
OSA/SF
|
|
OSE
|
Required
|
|
OSD
|
Not required
|
|
OSC
|
Not supported
|
|
OSX
|
Not supported
|
|
OSM
|
Not supported
|
|
Note: OSN channel is not supported on z14.
|
When you use SNA network with OSE CHPID type and need to change SNA timer (SNA LLC2 parameter), you must customize the parameters in OSA/Advanced facilities. For more information, see Open Systems Adapter-Express Customer's Guide and Reference, SA22-7935.
If you are upgrading from z13s to z14 ZR1, and your configuration uses the OSA Express-5S 1000Base-T feature, your OSE configuration is automatically migrated. After this process is complete, check the configuration in OSA/SF on the HMC.
Customizing OAT and SNA timer
|
Note: Before you customize OAT and SNA timer with OSA/AF on the HMC, see Open Systems Adapter/Support Facility on the Hardware Management Console, SC14-7580. This publication is available for download from IBM Resource Link.
|
To customize OAT and SNA time for OSE channel, complete the following steps:
1. Start OSA Advanced facilities.
2. The OSA Advanced Facilities window opens (see Figure 6-6). Select the OSE channel PCHID that you want to customize. In this example, we selected PCHID 0174. Then, select Select Action → Card specific advanced facilities, as shown in Figure 6-6.
Figure 6-6 Entering OSA/SF on the HMC
3. The Advanced Facilities window opens (see Figure 6-7). To edit OAT and SNA timer entries, select Panel configuration options and click OK.
Figure 6-7 OSA/SF on the HMC Panel configuration options
4. The Panel Configuration Options window opens (see Figure 6-8). You can define the following options:
Edit OAT entries By selecting this option, you can edit the OAT and SNA definition. An OAT entry defines the data path between an OSA feature port and an LPAR image.
Edit SNA timers By selecting this option, you can enter SNA timer values.
Figure 6-8 OSA/SF on the HMC: Configuration file options
5. Choose Edit OAT entries, and the Edit OSA Address Table (OAT) Entries window opens, (see Figure 6-9).
Figure 6-9 OSA/SF on HMC: Edit OSA Address Table (OAT) Entries window
6. To edit, select the device in the left column, as shown in Figure 6-10. Click Select Action and choose Edit as TCP/IP entry or Edit as SNA entry for the selected device.
Figure 6-10 OSA/SF on the HMC: Select Action for Edit OSA Address Table (OAT) Entries window
7. Select Edit as SNA Entry, and the OSA Address Table (OAT) Entry window that is shown in Figure 6-11 opens. Select the correct SNA entry and click OK.
Figure 6-11 OSA/SF on the HMC: Edit SNA entry window
8. Select Edit as TCP/IP Entry, and the Edit OSA Address Table (OAT) Entry that is shown in Figure 6-12 opens. Enter and select the appropriate TCP/IP parameters here. Then, click OK.
Figure 6-12 OSA/SF on the HMC: Edit TCP/IP entry window
9. After editing TCP/IP entry or SNA entry, the Edit OSA Address Table (OAT) Entries window opens again. Confirm that your entries are displayed in this window. Figure 6-13 shows that the TCP/IP entry and SNA entry can be confirmed. Click Save to save the configuration.
Figure 6-13 OSA/SF on the HMC: Edit OSA Address Table (OAT) Entries window after editing
10. Select Edit SNA timers in the Panel Configuration Options window to change the SNA timer setting. Figure 6-14 shows the window in which you can edit the values. You can set the parameters for port 0 and 1 individually.
Figure 6-14 OSA/SF on the HMC: Edit SNA Timers window
11. When you complete editing the OAT entries or SNA timer, the Panel Configuration Options window is displayed again. To activate the settings, you must validate them by selecting Validate panel values. Then, click OK (see Figure 6-15).
Figure 6-15 OSA/SF on the HMC: Validate panel values
12. If all of the parameters are entered correctly, a window as shown in Figure 6-16 is displayed.
Figure 6-16 OSA/SF on HMC: Validate window value with success
If any of the entered parameters are incorrect, a window with ACT20425 message opens. To identify the error, select Display validate panel errors, and correct the error. Then, validate the panel values again until the error is fixed.
13. To activate your OSA configuration, select Activate configuration from the Advanced Facilities window, and click OK (see Figure 6-17).
Figure 6-17 OSA/SF on the HMC: Activate configuration
Figure 6-18 OSA/SF on the HMC: Confirm activation
15. When the activation is successfully, the window that is shown in Figure 6-19 is displayed. Click OK to complete the process.
Figure 6-19 OSA/SF on the HMC: message when activation completed
16. To effective the changes, you must bring the CHPID OFFLINE from all the LPARs that share the OSA CHPID, and then back ONLINE.
17. If you select Manual configuration options (see Figure 6-7 on page 129), the window that is shown in Figure 6-20 opens. In this window, you can import or export the source file of OAT by using a USB device or FTP, create a configuration file in the editor on HMC, and edit the source file. For more information, see Open Systems Adapter/Support Facility on the Hardware Management Console, SC14-7580.
Figure 6-20 OSA/SF on the HMC: Manual Configuration options
6.3.2 Setting OSA parameters using OSA Advanced Facilities
If you want to change the port speed or MAC address of an OSA-Express feature, you can use the OSA Advanced Facilities. Normally, changing MAC address is required for SNA networks.
|
Port speed: You can change only the port speed to OSA-Express5S/6S 1000BASE-T. Other OSA features do not include this capability.
You cannot set port speed to 1000 Mbps for OSA-Express5S/6Sress4S 1000BASE-T. If you want to set the port speed to 1000 Mbps, you must select Auto Negotiate.
|
Setting the OSA port speed
To change port speed, complete the following steps:
1. Log on to the HMC, select the CPC you want to operate, and then, click Open OSA Advanced Facilities.
2. Select the PCHID of the OSA channel for which you need to set the card mode. Select Card specific advanced facilities and click OK.
Figure 6-21 Selecting Card Mode definition
4. The Set Card Mode or Speed window opens (see Figure 6-22). Select the correct port speed from the Speed/Mode list. You can set the speed of port 0 and 1 individually. Click OK.
Figure 6-22 Set card mode or speed
5. To effect the changes, you must configure CHPID OFFLINE and ONLINE from every LPAR where this CHPID is defined.
Changing OSA MAC address
To change the MAC address, complete the following steps:
1. Log on to the HMC.
2. Open OSA Advanced Facilities, and select the PCHID that you want to customize.
3. The Advanced Facilities window opens (see Figure 6-23). Select Display or alter MAC address and then, click OK.
Figure 6-23 Display or alter MAC address
4. The Display or alter MAC address window opens (see Figure 6-24). Set the MAC address that you want and then, click OK.
Figure 6-24 Display or alter MAC address values
5. To reflect the modification, you must configure CHPID OFFLINE and ONLINE from every LPAR where this CHPID is defined.
6.3.3 Confirming your OSA customization
To confirm your customization on the OSA Advanced Facility, open OSA Advanced Facility again and confirm whether your definitions are reflected correctly. Also, check the device status from your networking software, such as TCP/IP and VTAM.
6.4 Shared Memory Communications (SMC-R and SMC-D)
For more information about how to configure Shared Memory Communications over RDMA (SMC-R), see 10.4, “Shared Memory Communications over RDMA (SMC-R)” on page 257.
For more information about how to configure Shared Memory Communications - Direct Memory Access (SMC-D), see 10.5, “Shared Memory Communications - Direct Memory Access” on page 261.
6.5 Channel-To-Channel connection
This section describes the configuration steps for channel-to-channel connections (CTC).
6.5.1 FICON CTC: Preparing
If your system requires CTC connection for programs, such as VTAM or GRS, FICON CTC (FCTC) links must be configured. Because ESCON channels are not supported on zEC12 and later IBM Z servers, the only available option is to implement FICON CTC.
The FICON CTC does not require that you explicitly define the CTC control unit function to one channel side or the other. The channel decides which side contains the control unit function. Therefore, both sides of an FCTC connection use an FC channel path that is defined to one or more FCTC control units that represent the target systems for the CTC connections.
A logical address is required when the FC channel path is attached to a shared FC channel path to identify the logical partition with which to communicate. When attached to an unshared FC channel path, the logical address must be zero or not specified. For more information, see the CTC Definitions for z Systems web page.
FICON CTC communication within a single processor complex can be accomplished with a single FC channel path that is connected to an FC switch. That is, both sides of the CTC connection are represented by the same single FC channel path. This configuration results in the following advantages:
•Reducing the number of channels required
•Simplified configuration design and definition
6.5.2 FICON CTC: Implementation
To define FICON CTC, the following considerations apply to all FICON CTC configurations:
•The server at each end of an FICON CTC connection uses a FICON native (CHPID type FC) channel.
•The FICON native channel at each end of the CTC connection features a defined FICON CTC control unit.
•The FICON CTC devices on the FCTC control unit are defined as type FCTC.
•The FCTC control function on the IBM Z platform can communicate with an FCTC control unit that is defined on a FICON native channel on any server that supports FICON.
•The FICON native channel at each end of the FICON CTC connection supports the FCTC control units. It also communicates with other FICON native control units, such as disk and tape.
In a FICON CTC configuration, FICON CTC control units are defined at each end, but only one end provides the FICON CTC control unit function. During initialization of the logical connection between two ends of a FICON CTC connection, the channel that provides the FICON CTC control unit function is determined by using an algorithm. This process results in balancing the number of FCTC CU functions that each end of the logical connection is providing. The algorithm uses the channel with the lower FC worldwide name (WWN) to provide the FICON CTC control unit function.
The FICON native channel CTC communication does not require a pair of channels because it can communicate with any FICON native channel that includes a defined corresponding FCTC control unit. This configuration means that FICON CTC communications can be provided by using only a single FICON native channel per server.
For more information about how to implement FICON CTC, see the following publications:
•FICON CTC Implementation, REDP-0158
•FICON Planning and Implementation Guide, SG24-6497
•I/O Configuration Using z/OS HCD and HCM, SG24-7804
6.5.3 FICON CTC: Management
After activating the new FICON CTC configuration and all cables are connected, verify whether the CHPIDs are online and operating by using z/OS or the Support Element (SE) windows:
•Checking status by using z/OS commands. If you are interested in checking the status of CHPIDs 44 and 45, issue D M=CHP(44) and D M=CHP(45) commands, as shown in Figure 6-25.
|
D M=CHP(44)
IEE174I 16.42.20 DISPLAY M 081
CHPID 44: TYPE=1B, DESC=FICON SWITCHED, ONLINE
DEVICE STATUS FOR CHANNEL PATH 44
0 1 2 3 4 5 6 7 8 9 A B C D E F
04A1 + + + + . . . . . . . . . . . .
SWITCH DEVICE NUMBER = 0001
DEFINED ENTRY SWITCH - LOGICAL SWITCH ID = 01
ATTACHED ND = 008960.F64.IBM.CA.1000010546MH
PHYSICAL CHANNEL ID = 0175
FACILITIES SUPPORTED = ZHPF
************************ SYMBOL EXPLANATIONS ************************
+ ONLINE § PATH NOT VALIDATED - OFFLINE . DOES NOT EXIST
* PHYSICALLY ONLINE $ PATH NOT OPERATIONAL
D M=CHP(45)
IEE174I 16.43.04 DISPLAY M 083
CHPID 45: TYPE=1B, DESC=FICON SWITCHED, ONLINE
DEVICE STATUS FOR CHANNEL PATH 45
0 1 2 3 4 5 6 7 8 9 A B C D E F
04A1 . . . . . . . . + + + + . . . .
SWITCH DEVICE NUMBER = 0002
DEFINED ENTRY SWITCH - LOGICAL SWITCH ID = 02
ATTACHED ND = 008960.F64.IBM.CA.1000010546MD
PHYSICAL CHANNEL ID = 0115
FACILITIES SUPPORTED = ZHPF
************************ SYMBOL EXPLANATIONS ************************
+ ONLINE § PATH NOT VALIDATED - OFFLINE . DOES NOT EXIST
* PHYSICALLY ONLINE $ PATH NOT OPERATIONAL
|
Figure 6-25 DISPLAY FCTC on system SC03
•Checking status by using SE windows:
– From the HMC, select the CEC (under Systems Management) from where the CHPID/PCHID you want to verify is stored and click Single Object Operations (under the Recovery task options).
– On the Support Element, select the same CEC and click Channels. Look for the PCHID of which you are interested in checking the status. The result is shown in Figure 6-26.
Figure 6-26 Using the SE to verify channel FCTC using the CEC view
– For more information about the PCHID, click the PCHID to open the details window, see shown in Figure 6-27.
Figure 6-27 FCTC PCHID details
– The status also can be checked from the LPAR view. Select the LPAR and then the CHPIDs option under that LPAR. You can look for the CHPID and check the status as shown in Figure 6-28.
Figure 6-28 Verifying channel FCTC using LPAR view
– For more information, click the CHPID, as shown in Figure 6-29.
Figure 6-29 FCTC CHPID details
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.