How to apply updates to the autoconfiguration proposals

This topic explains how to work in the attended operation mode, that is, with option Show proposed definitions set to 1 (Yes) in the Discovery and Autoconfiguration Options panel shown in Figure 83.

How to work in unattended mode explains the unattended fast-path discovery.

After specifying your desired options on the Discovery and Autoconfiguration Options panel, pressing Enter starts the discovery process. HCD notifies users with the message: FABRIC discovery in progress - please wait ...

After a successful discovery, HCD displays the result in the Discovered New or Changed Controller List (Figure 84). Only discovered controllers are displaxed, which are reachable from all target systems, which are capable of discovery, and which have partitions defined in the LP group referenced by the AUTO_SUG_LPGROUP policy.

*---------- Discovered New or Changed Controller List -------*
|   Policy  Backup  Query  Help                               |
| ----------------------------------------------------------  |
|                                                 Row 1 of 12 |
| Command ===> ___________________________ Scroll ===> PAGE   |
|                                                             |
| Select one or more controllers to be defined, then press    |
| Enter.                                                      |
|                                                             |
|                  Manufacturer                               |
| /  Type   Model  Name  Plant   Serial-#     New  Processed  |
| _  2107   9A2    IBM   13      15663        Yes  No         |
| _  2107   921    IBM   13      34211        Yes  No         |
| _  2107   922    IBM   13      67884        Yes  No         |
| _  3491   A01    IBM   13      18321        Yes  No         |
| /  1750   511    IBM   13      28824        No   No         |
| _  1750   522    IBM   13      43560        No   No         |
| _  2105   F10    IBM   13      28251        No   No         |
| _  2105   F20    IBM   13      12353        No   No         |
| _  2105   800    IBM   13      17791        No   No         |
|                                                             |
|  F1=Help        F2=Split       F3=Exit        F4=Prompt     |
|  F7=Backward    F8=Forward     F9=Swap       F10=Actions    |
| F12=Cancel     F22=Command                                  |
*-------------------------------------------------------------*

This panel lists all discovered controllers which are either not yet defined in the IODF, or whose definition in the IODF is different from discovered controller characteristics.

If you selected AUTO_SS_DEVNUM_SCHEME = NONE, all control unit numbers for new controls are prefilled with 0000. You see message Assign numbers for control units or devices. Then hit Enter. Exclude all control units which should not be added, and assign control unit numbers. Pressing Enter processes the line commands or edited fields. After pressing Enter a second time with no changes on the list, you see the message Items have been processed. Review them, then press Enter. You are then in the normal process flow as if control unit numbers have been proposed.

On this dialog, using action code  / , you can select multiple controllers that you want to be defined or changed in the target IODF. HCD subsequentially processes each selected controller in the way described in the remainder of this topic.

Pressing Enter on this panel with selected controllers starts the controller discovery and definition process for the next selected controller. Users are notified with the message: CONTROLLER discovery in progress - please wait ... As a result of the discovery process, the Proposed Control Unit List offers definition proposals for the control units found in the currently processed controller.

*-------------------------- Proposed Control Unit List -----------------------*
|                                                                  Row 1 of 8 |
| Command ===> ___________________________________________ Scroll ===> PAGE   |
|                                                                             |
| Control unit type  . . : 1750 -511      Serial number  : 28824              |
|                                                                             |
| Proposed switch.ports  : B0.75 B1.75 B0.76 B1.76 B0.77 B1.77 B0.78 B1.78 +  |
|                                                                             |
| To accept the proposed values, press Enter. To modify them, edit the        |
| fields, or select one or more control units to change, exclude or include   |
| the corresponding definitions, then press Enter.                            |
|                                                                             |
|                                                                             |
|   CU   CU       # of     LPAR                                               |
| / ADD  number+  devices  Access+  New  Description                       I  |
| / 00   0130     256      ALL      Yes  ________________________________  Y  |
| _ 01   0140     96       ALL      Yes  ________________________________  Y  |
| _ 02   0150     64       ALL      Yes  ________________________________  Y  |
| _ 03   0160     64       ALL      Yes  ________________________________  Y  |
|  F1=Help        F2=Split       F3=Exit        F4=Prompt      F5=Reset       |
|  F7=Backward    F8=Forward     F9=Swap       F12=Cancel     F22=Command     |
*-----------------------------------------------------------------------------*

The panel shown in Figure 85 shows proposed definition details for existing or new control units configured in the discovered controller with the serial number  28824  displayed in the header of the panel. The indicated controller type  1750  has been determined by discovery, and is the proposed control unit type for all listed control units within the controller.

All control units are connected to the proposed switch ports as listed in the upper part of the panel. A plus sign (+) at the end of the switch port list signals, that the control units will have connections to more than eight switch ports. You can see the full list of connected switch ports for a control unit on the View Control Unit Definition dialog.

You can accept the proposed control unit definitions, or you can perform the following modifications:

• For control units showing Yes in column New (which indicates whether the control unit is not yet defined in the IODF, or is not yet connected to any of the LPARs defined in the AUTO_SUG_LPGROUP policy), you can overtype the values in column CU number.
• Also, you can overtype the values in the LPAR Access and Description fields in this dialog. Note that when changing the prefilled LP group name in the LPAR Access column, you can only replace it by the name of another LP group, which defines a subset of those logical partitions contained in the LP group used during the autoconfiguration propose step.
• With action code  /  you get an overview of available actions on the selected control units:
  • With action code  i , you can include the corresponding control unit definition into the target IODF, or with action code  e , you can exclude the control unit from being defined. Your selection is reflected in column I: Y denotes included and N denotes excluded control units.
  • Using action code  c  leads you to the Select Processor / CU panel (see Figure 54). On this window, HCD displays a list of all defined processors. You can define how the control unit is to be attached to one or more processors.

When the controller discovery returns control units and devices, HCD checks the discovered switch ports (Figure 85) for existing definitions in the target IODF to match the existing control unit/device numbers with the proposed ones and proceeds like follows:

1. Rules for discovered control units: 

• For each discovered control unit that is already defined with the same CUADD value, the existing control unit definition is checked for the same serial number. If the serial numbers match, or the IODF definition does not contain a serial number, the control unit number of the existing control unit is used and updated with the serial number of the discovered control unit. If the serial numbers do not match, a warning message is given, and the discovered control unit is proposed to be newly defined with a new serial number. It is, however, recommended that the serial numbers match, or the serial number of the defined control unit should be blank.
• For each discovered control unit that is not yet defined in the IODF, a new control unit number is proposed.
• When a new control unit number is proposed, its value is taken from the preferred range specified by policy AUTO_SUG_CU_RANGE. If there is no free control unit number in the IODF within that range, a warning message indicates that the policy could not be followed, and a free control unit number outside of the range is proposed.
• Proposed existing control units are updated with the discovered serial number. If the type of a discovered control unit differs from its definition in the IODF, the definition is updated.
• Some controllers may respond indicating over-defined unit address configurations. In these situations, devices are included in the proposal for unit addresses that are not configured on the controller. You can leave these devices in the configuration, or you can remove them from the proposal.

2. Rules for discovered devices: 

• For each discovered device that is already defined with the same unit address on an existing control unit, the existing device number is proposed. In that case, the definition may differ from the specified policy, for example for the subchannel set number.

  For non-existing devices on the control unit, the existing device numbering scheme is applied if possible.

• For new devices on new or existing control units where the existing device number scheme could not be applied, the device numbers are determined based on policies AUTO_SUG_DEV_RANGE and AUTO_MATCH_CU_DEVNUM. For PAV alias devices the numbers are additionally determined based on policies AUTO_SS_ALTERNATE and AUTO_SS_DEVNUM_SCHEME. If a policy could not be applied because no free numbers are available for the active LP group and OS groups, a warning message is given and free device numbers outside the policies may be used.

You can now apply desired modifications and press Enter after you are finished, or you can accept the proposed definitions without changes and press Enter. In both cases, HCD now displays the Proposed Control Unit / Device List.

                     Proposed Control Unit / Device List            Row 1 of 8
Command ===> _______________________________________________ Scroll ===> PAGE

Control unit type  . . : 1750-511       Serial number  : 28824

To accept the proposed values, press Enter. To modify them, edit the
fields, or select one or more device ranges to change, exclude or include
the corresponding definitions, then press Enter.

  ------Device----- S CU   UA    OS
/ Number   Type+    S Num  Range Access+  N Description                      I

_ 6300,128 3390B    0 0130 00-7F ALL      N ________________________________ Y
_ 6380,128 3390A    1 0130 80-FF ALL      N ________________________________ Y
_ 6400,32  3390B    0 0140 00-1F ALL      N ________________________________ Y
_ 6420,64  3390A    1 0140 20-5F ALL      N ________________________________ Y
_ 6500,16  3390B    0 0150 00-0F ALL      Y ________________________________ Y
_ 6510,48  3390A    1 0150 10-3F ALL      Y ________________________________ Y
_ 6600,16  3390B    0 0160 00-0F ALL      Y ________________________________ Y
_ 6610,48  3390A    1 0160 10-3F ALL      Y ________________________________ Y
******************************* Bottom of data ********************************

This list proposes definition details for existing or new devices accessible by the currently processed discovered control units (0130 - 0160 from Figure 86). In the header of this panel, you can see the control unit type and serial number of the discovered controller.

If you selected AUTO_SS_DEVNUM_SCHEME = NONE, all device numbers for new devices are prefilled with 0000. You see a message Assign numbers for control units or devices. Then hit Enter. Exclude all devices which should not be added, and assign device numbers. Pressing Enter processes the line commands or edited fields. After pressing Enter a second time with no changes on the list, you see the message Items have been processed. Review them, then press Enter. You are then in the normal process flow as if device numbers have been proposed.

You can accept the proposed device definitions without changes by pressing Enter. Also, you can narrow by overtyping one or more of the device ranges, but only those with a Y in column N (abbreviation for New), which indicates that the device range is not yet defined in the IODF.

Furthermore, for one or more of the listed device ranges with Y in column N, you can change the OS Access and the Description fields by overtyping the values in the panel. Again, a changed OS group must be a subset of the initial OS group.

For further available actions on devices, select one or more devices using action code  / :

• By selecting action code  i , you can include, or with action code  e , you can exclude the corresponding devices from autoconfiguration.
• Using action code  c  leads you to the Device / Processor Definition panel (see Figure 60). On this panel, HCD displays a list of all defined processors that have one or more channel paths to the control unit to which the device being added or changed is attached. Here you can select the processor/CSS(s) for which you want to change the device-to-processor definition.

In both cases, either with modifications applied or with accepting the unchanged proposals, pressing Enter lets you return to the Discovered New or Changed Controller List. For each successfully handled controller, its Processed field is now turned to Yes (see Figure 84).

You can select the next controller for being auto-configured, or you can exit the dialog. Exiting the dialog saves all applied configuration changes in the target IODF.

For documenting the progress of your configuration actions, and for later reference, you can save the lists from Figure 84, Figure 85, and Figure 86 in a data set using the SAVE command as described in How to print list panels.