Enabling communication with the HMC

ZETALY Automated Capacity© architecture sample with the HMC API

ZCASC (z/OS STC) via 1 RMF DDS per SYSPLEX or 1 BMC MVE per CPC

ZCASC

Production SYSPLEX

Development SYSPLEX

SE

SE

Customer Defines Dynamic MSU Allocation via ZCASC

Process Control

(HMC) Network

HMC

Every HMC is

HMC connected to 2 SEs

4 z/OS LPARs

5 z/OS LPARs

12 z/OS LPARs

10 z/OS LPARs

Figure 14 Architecture with ASC using HMC API

Configuring the firewall (optional)

If you plan to use the BCPII feature instead of the HMC API, skip to Chapter 6: “Enabling communication with BCPii”.

(This step is only required for SETMETHOD=HMC.)

ZETALY Automated Capacity© can communicate with the HMC using SNMP and the HMC API.

The standard port used to communicate using SNMP is port 161 with UDP protocol. The standard port used to communicate with the HMC API is port 3161 with TCP protocol.

If you use a firewall, open the following connections in your firewall:

Port 161 UDP for HMC @IP with dynamic port for the z/OS hosting ZETALY Automated Capacity© @IP Port 3161 TCP for HMC @IP with dynamic port for the z/OS hosting ZETALY Automated Capacity© @IP

Configuring the HMC API (SETMETHOD=HMC)

(This step is only required for SETMETHOD=HMC.)

For complete information look at Resource Link Documentation:

https://www-01.ibm.com/servers/resourcelink

The Console’s API configuration steps can be performed by using the Customize API Settings task of the Hardware Management Console Settings or Support Element Settings task group. This task group is found under Console Actions in the Views area.

To configure the Console for API support:

• Log on to the Console in Access Administrator mode;
• Open the Hardware Management Console Settings or the Support Element Settings task group;
• Start the Customize API Settings task;
• Tick the Enable SNMP checkbox, add a Community Name, and associated parameters;
• Then you need to restart the Console to apply the changes.

Detailed procedure to configure the console for API support

1. Log on to the Console in Access Administrator mode. User ACSADMIN. Select the Console Actions icon and double click it.

Figure 15 HMC Console Action

1. Open the Hardware Management Console Settings or the Support Element Settings (task group). Select the Hardware Management Console Settings icon and double click it.

Figure 16 Hardware Management Console Settings

1. Start the Customize API Settings task.

Select the Customize API Settings icon and double click it.

Figure 17 Customize API Settings

1. Tick the Enable SNMP checkbox and add a Community Name Select the Add icon and click it.

Figure 18 Add Community name

Enter a “Community Name” (e.g. ZCOST).

This field should be filled in with any character string. Each community name in the list must be unique. Please note that this field is case sensitive. Note the community name(s) that are to be used by applications using the Console’s APIs, since they will need to be specified on the HwmcaInitialize calls issued by those applications.

Enter Address : 0.0.0.0

Network mask / Prefix : 0.0.0.0

Access Type: Use this field to specify the type of access that is allowed for the community. The access type for the community(ies) that are to be used by applications using the Console’s APIs MUST be read/write. Select Read/write.

Click on OK.

Figure 19 Set Community Name information

Click on APPLY.

Figure 20 Validate API Settings customization

Figure 21 SNMP Configuration message

Click on OK.

Figure 22 Settings before HMC restart

Now you must restart the HMC to apply all the changes.

Testing the HMC API and communication

(This step is only required for SETMETHOD=HMC.)

You can use the TSTHMC job supplied in ZETALY Automated Capacity© SAMPLIB to test all network paths and APIs between the LPAR on which ZETALY Automated Capacity© runs and the HMC/SE. The output indicates if the communication is correct or not.

If it is correct, a list of LPARs which can be reached by ZETALY Automated Capacity© is generated. If the communication is not correct, an explanation of the problem is displayed.

Warning: when ZETALY Automated Capacity© encounters a problem with an HMC, it tries to switch to the second HMC. In this case, it is necessary that the LPAR involved in the failure can be reached through the second HMC. To avoid problems, you may verify using the test job that all the LPARs are reachable through both HMCs.

HMC communication troubleshooting

You must consider that some interfaces like WEB & login conflict with the HMC API access mode. Some of these interfaces are listed below:

• CHANGE LPAR DEFINITION on HMC or via the web interface;
• SOO mode from HMC to control the CPC;
• SERVICE MODE login on SE;
• Maintenance on HMC or SE.

To avoid problems due to HMC conflicts, you can temporarily disable ZETALY Automated Capacity© HMC actions during a planned intervention on the HMC or the SE. Use the command below:

F ZCASC,RUNMODE=MESSAGE

F ZCASC,RUNMODE=ACTIVE allows you to reactivate ZETALY Automated Capacity© actions after the planned intervention is finished.

Behavior of ZETALY Automated Capacity© during communication problem with the HMC

When a communication problem occurs, the behavior of ZETALY Automated Capacity© is the following:

Interval 1

SET LPAR1 via HMC1 --> error --> switch to HMC2 and retry setting LPAR1 via HMC2 --> error --> stop settings for interval - Error message (ASC0710W)

Interval 2

SET LPAR1 via HMC2 --> error --> switch to HMC1 and retry setting LPAR1 via HMC1 --> error --> stop settings for interval - Error message (ASC0710W)

Interval 3

SET LPAR1 via HMC1 --> error --> switch to HMC2 and retry setting LPAR1 via HMC2 --> error --> stop ZCASC with the error - message (ASC0805E)

Note: Typically, this behavior occurs when the HMC interface is used by another user during an ZAC setting request. (see chapter 7.5 “HMC communication troubleshooting”).