Licensed Machine Code
This chapter describes considerations that relate to the planning and installation of new Licensed Machine Code (LMC) bundles on the IBM DS8900F. The overall process for the DS8900F is the same as for previous models. However, several enhancements to IBM Power firmware updates are described.
This chapter covers the following topics:
11.1 How new Licensed Internal Code is released
Most of the hardware components within the DS8900F system can be updated with new firmware when it is available:
•Device adapters (DAs)
•Host adapters
•Power subsystems:
 – Intelligent Power Distribution Units (iPDUs)
 – Rack power control
 – Fibre Channel Interface Cards (FCICs)
In addition, the Licensed Internal Code (LIC) and internal operating system (OS) that run on the Hardware Management Consoles (HMCs) and each central processor complex (CPC) can be updated. As IBM continues to develop the DS8900F, new features are released through new LIC levels.
When IBM releases new LIC for the DS8900F, it is released in the form of a bundle. The term bundle is used because a new code release can include updates for various DS8900F components. These updates are tested together, and then the various code packages are bundled together into one unified release. Components within the bundle each include their own revision levels.
For more information about a DS8900F cross-reference table of code bundles, see DS8900F Code Bundle Information.
The cross-reference table shows the levels of code for released bundles. The cross-reference information is updated as new code bundles are released.
In addition to keeping your LIC up to date, make sure to maintain a current version of the Data Storage Command-line Interface (DS CLI).
The DS8900F uses the following naming convention for bundles: PR.MM.FFF.EEEE, where the components are:
•P: Product (8 = DS8000)
•R: Release Major (X, 9 = DS8900F)
•MM: Release Minor (xx)
•FFF: Fix Level (xxx)
•EEEE: Fix Level (0 is base, and 1..n is the interim fix build that is later than the base level.)
This naming convention is shown in Example 11-1.
Example 11-1 Bundle level information
For BUNDLE 89.30.68.0 :
Product DS8000
Release Major 9
Release Minor 30
Fix Level 68
EFIX level 0
The 9.30 in Example 11-1 stands for the Release 9.3 without a Service Pack.
If DS CLI is used, you can obtain the CLI and LMC code level information by using the ver command, as shown in Example 11-2. The ver command uses the following optional parameters and displays the versions of the CLI, Storage Manager, and LMC:
-s (optional) The -s parameter displays the version of the CLI program. You cannot use the -s and -l parameters together.
-l (optional) The -l parameter displays the versions of the CLI, Storage Manager, and LMC. You cannot use the -l and -s parameters together.
-cli (optional) Displays the version of the CLI program. Version numbers are in the format version.release.modification.fixlevel.
-stgmgr (optional) Displays the version of the Storage Manager.
This ID is not for the GUI (Storage Manager GUI). This ID relates to HMC code bundle information.
-lmc (optional) Displays the version of the LMC.
Example 11-2 Output of the DS CLI ver -l command
dscli> ver -l
Date/Time: June 28, 2022 12:10:08 PM CEST IBM DSCLI Version: 7.9.30.154 DS: -
DSCLI 7.9.30.154
StorageManager 0.0.0.0
HMC DSCLI 7.9.30.154
================Version=================
Storage Image LMC Bundle Version
==========================================
IBM.2107-75HAL91 7.9.30.154 89.30.68.0
The Bundle version (Release) also can be retrieved from the DS Storage Manager by clicking Actions → Properties from the Dashboard window, as shown in Figure 11-1.
Figure 11-1 Bundle version under DS Storage Manager
11.2 Bundle installation
 
Important: The LMC is usually provided by and installed by IBM Remote Support Personnel, or by an IBM Systems Service Representative (IBM SSR). With the release of R9.3, the customer may manage the entire process from the DS8000 Storage Manager GUI. When this process is handled by the IBM SSR or IBM Remote Support Personnel, they review the “Prerequisites” section or “Attention Must Read” section in the LIC update instructions, and inform the customer during the planning phase if any prerequisites must be considered.
The bundle package contains the following new levels of updated code:
•HMC code levels:
 – HMC OS and managed system base
 – DS Storage Manager
 – IBM Copy Services Manager
•Managed system code levels
•Interim fix code levels
•Storage facility image (SFI) code levels
•Host adapter code levels
•DA code level
•I/O enclosure code level
•Power code levels
•Rack power control card (RPCC) code level
•Flash Drive Enclosure Service Module (ESM) interface card code levels
•Flash Drive enclosure power supply unit (PSU) code levels
•Flash drive module firmware code level
The code is either updated remotely or locally at the HMC by an IBM SSR. Upgrading the code remotely can be done by IBM through Remote Code Load (RCL) or by the client through the DS8000 Storage Manager GUI. RCL is the default method. If the client wants the code updated by the local IBM SSR onsite, then the Feature Code for remote code exception must be ordered with the system.
 
Note: When the customer does not opt for Expert Care Premium, Customer Code Load is the default on the DS8900F system.
Other than the actions of acquiring the microcode, the process of distribution and activation is the same.
The Code Distribution and Activation (CDA) software preinstall is the method that is used to run the concurrent code load (CCL) distribution. By using the CDA software preinstall, the
IBM SSR performs every non-impacting CCL step for loading code by inserting the physical media into the primary HMC or by running a network acquisition of the code level that is needed. The IBM SSR can also download the bundle to their Notebook and then load it on the HMC by using a service tool, or download the bundle from IBM Fix Central on the HMC for RCL.
After the CDA software preinstallation starts, the following steps occur automatically:
1. The release bundle is downloaded from either the DVD or network to the HMC hard disk drive (HDD).
2. The HMC receives any code update-specific fixes.
3. Code updates are distributed to the logical partition (LPAR) and staged on an alternative base operating system (BOS) repository.
4. Scheduled precheck scans are performed until the distributed code is activated by the user. After 30 days without activation, the code expires and is automatically removed from the alternative BOS.
Anytime after the software preinstallation completes, when the user logs in to the primary HMC, the user is guided automatically to correct any serviceable events that might be open, update the HMC, and activate the previously distributed code on the storage facility. The overall process is also known as CCL.
The code installation process performs the following actions:
1. Updates code on the primary HMC (HMC1).
2. If a dual-HMC configuration is used, the code is acquired from the primary HMC (HMC1) and copied to the secondary HMC (HMC2).
3. Performs updates to the CPC OS and the internal LMC, which are performed individually. To update each CPC, the logical subsystem (LSS) fails over to the alternative CPC. This process updates the firmware that is running on each DA that is owned by that CPC.
4. Performs updates to the host adapters. For DS8900F host adapters, the impact of these updates on each adapter is less than 2.5 seconds and they do not affect connectivity. If an update takes longer, the multipathing software on the host or the control-unit initiated reconfiguration (CUIR) directs I/O to another host adapter. If a host is attached with only a single path or through multipathing to different ports on the same host adapter, connectivity is lost. For more information about host attachment, see 3.3.2, “Host connections” on page 82.
5. New power supply and RPCC firmware are periodically released. New firmware can be loaded into each RPCC directly from the HMC. For more information, see 3.6, “RAS on the power subsystem” on page 97.
During the RPCC firmware update, RPC0 is first placed into Service Mode while updated and verified, then resumed, and then the alternative card RPC1 completes.
6. New firmware for the hypervisor, service processor, system board, and I/O enclosure boards are periodically released. This firmware can be loaded into each device directly from the HMC. Activation of this firmware might require a shutdown and restart of each CPC individually. This process causes each CPC to fail over its LSSs to the alternative CPC. Certain updates do not require this step, or it might occur without processor restarts. For more information, see 3.2, “CPC failover and failback” on page 78.
7. Maintain the latest flash drive firmware because enhancements for efficiency, performance, and reliability are released often. A flash drive firmware update is a concurrent process in the DS8900F series family. Direction to update the firmware by using Install Corrective Service (ICS) can be found in the code installation instructions.
Although the microcode installation process might seem complex, it does not require significant user intervention. IBM Remote Support Personnel normally start the CDA process and then monitors its progress by using the HMC. The customer’s experience with upgrading the code of the DS8000 is the same.
 
Important: For the DS8900F models, DS CLI should be maintained at a current level. Matching the version to the storage facility is not required if the DS CLI version is at a higher level. The higher level can be used to support all other IBM DS8000 models in the environment. For more information, see the release notes or speak to your IBM SSR.
Automatic Code Management
New since Release 9.2 is an optional automatic acquire and preinstallation feature for LIC. This feature automatically downloads the recommended “go to” level of LIC to the HMC, and then it performs an automated preinstallation. This preinstallation reduces the code load time because this level is preinstalled at the beginning of the code load window. You can view the recommended level of LIC by going to DS8000 Code Recommendation.
 
Important: The default setting for this feature is off, but can be enabled in the Storage Manager GUI. For more information, contact your IBM SSR.
To enable this feature, log in to the Storage Manager GUI, select Settings → System → Advanced, and select Automatic code management, as shown in Figure 11-2.
Figure 11-2 Advanced Settings menu: Automatic code management
HMC Code Image Server
When several DS8000 storage systems in the same data center must be updated, acquiring a code bundle from IBM Fix Central individually for each storage system can be a time-consuming process.
To address this situation, a new HMC Code Image Server function was introduced in DS8000 Release 9.0. With the HMC Code Image Server function, a single HMC in the customer data center can acquire code from IBM Fix Central. One HMC sends those images to other HMCs by using the client Ethernet network. The advantage of this approach is that there is no need to download the image from IBM Fix Central multiple times, and the code bundles can be copied locally by using that download.
The HMC Code Image Server function works with bundle images and other updates, such as ICS Images. HMC Recovery Images are performed if they are available on the source HMC.
Figure 11-3 shows the two new menu options in the Updates menu of the service console Web User Interface (WUI).
Figure 11-3 Updates menu: HMC Code Image Server
At the site where the code bundle was acquired and downloaded, the HMC Code Image Server function must be enabled. The target site then uses the Remote File Download function to copy the available code bundles to a local repository. All images on the source HMC are copied to the target HMC.
This process copies only the update image files to the local /extra/BundleImage/ directory on the target HMC. Then, the normal acquisition step still must be performed, and the local directory on the target HMC must be selected, as shown on Figure 11-4.
Figure 11-4 Acquiring from the HMC Directory
After the acquisition is complete, the normal code load process proceeds with the CDA software preinstallation.
 
Note: Bundles that were acquired from physical DVD media cannot be served by the HMC Code Image Server function because they are imported directly to the HMC software library and are not available as single bundle image afterward.
Figure 11-4 on page 411 also shows that it is possible to acquire a bundle from the storage system LPAR. Every IBM Fix Central acquired image is copied to the HMC and the LPARs of the storage system and then imported into the HMC library. Because there is a copy on the LPAR, the partner HMC can now use the LPAR as a source for the acquisition step. This action can be done on both HMCs on the same storage system because only these HMCs have access to the internal network to copy the files from the LPARs. Copying from the LPARs does not require using the HMC Code Image Server function.
11.2.1 Remote Code Load
With RCL, you have an efficient and secure method to update the DS8000 systems microcode in a concurrent way without interrupting business operations.
RCL is supported by DS8870, DS8880, and DS8900F systems.
RCL is a trusted process where an IBM Remote Support engineer securely connects to a DS8000 system, enables the remote acquisition, and performs the distribution and activation of LIC bundles and ICS images.
The RCL process is concurrent, that is, it can be run without interruptions to business operations. This process consists of the following steps, as illustrated in Figure 11-5.
Figure 11-5 Remote Code Load process
1. IBM Remote Support Personnel work with IBM Technical Advisors to plan the microcode update to ensure that the client’s environment is in the planning phase.
2. When an RCL is agreed on and scheduled, IBM Remote Support Personnel in the
IBM Support Center initiate a session with the target HMC.
3. During the agreed on maintenance window, IBM Remote Support Personnel direct the HMC to acquire the code images from the IBM Fix Central repository and prepare for code activation.
4. During the customer maintenance window, IBM Remote Support Personnel initiate the activation request and update the HMCs and DS8000 to the new target microcode level.
RCL requires port 443 access to the following servers:
•esupport.ibm.com: 129.42.54.189
•esupport.ibm.com: 129.42.56.189
•esupport.ibm.com: 129.42.60.189
•eccgw01.boulder.ibm.com: 207.25.252.197
•eccgw02.rochester.ibm.com: 129.42.160.51
Code bundles are pulled to the HMC. They are not pushed.
11.2.2 Customer Code Load
With Release 9.3, the DS8000 introduces a new feature that clients can use to perform an upgrade of the DS8000 storage systems by themselves. This option provides some benefits for clients that prefer having full control of the entire process to plan, schedule, and perform the code upgrade. The process is entirely handled by the customer, and IBM Remote Support Personnel are not required to perform this task.
 
Note: Customer Code Load runs the same background processes as the RCL.
The process is split into two parts:
1. The user performs the download and acquires the new DS8000 code bundle.
2. The user activates the code bundle.
There is a 30-day countdown between these two parts of the upgrade in which the client can decide when to proceed with the second part. During the 30 days, the system stores the downloaded code bundle, and it can be activated at any point.
A new menu option is available under Settings → Support → Update System, as shown in Figure 11-6.
Figure 11-6 Storage Manager GUI: Update System menu
Figure 11-6 shows the Update System menu when there are no code bundles downloaded to the DS8000 storage system. The Health Check and Activate option is enabled after the download of the microcode completes.
 
Important: The storage system must be in a healthy hardware status to avoid issues during the code upgrade process. For that reason, at any point in time, the client can select the option Health Check to confirm whether the system is ready for the upgrade.
Customer Code Load process
To use the Customer Code Load process, complete the following steps:
1. To download the microcode, select Download Code Level from the window that is shown Figure 11-6, which immediately begins a microcode bundle query of IBM Fix Central for a list of codes that the customer can select. This query displays only higher or equal microcode levels compared to the currently installed level on the DS8000 system. After the query completes, a new window opens in the Storage Manager GUI, as shown in Figure 11-7 on page 415.
Figure 11-7 Microcode level query
2. After the code level is selected, the process downloads the new code bundle to the DS8000 Hardware Management Console, and then distributes the separate firmware packages to each internal component in the DS8000 system.
3. The user can monitor the process until completion. After the download completes, click Close Status, as shown in Figure 11-8.
Figure 11-8 Microcode download complete message
4. After closing the window, the option Health Check and Activate is available. Also, you can see and confirm which code level was downloaded, and how many days are left before the code expires, as shown in Figure 11-9.
 
Note: After completing this step, the Health Check option still is available, but it is not mandatory to select it before proceeding with the code activation. A health check still is performed before and after the activation when the user selects Health Check and Activate.
Figure 11-9 Update System: Ready for Activation
5. To activate the code, select Health Check and Activate. A new attention message appears in the Storage Manager GUI and notifies you about the actions that are about to be performed, as shown in Figure 11-10 on page 417. To start, click Yes.
Figure 11-10 Code Activation Message
6. The code activation progress can be tracked in the Storage Manager GUI until the end. After it completes, it displays a message confirming that the activation is complete (see Figure 11-11).
Figure 11-11 Code Activation Complete
If there is any unexpected situation such as hardware failure or code upgrade failure during the process, the customer is notified in the window that is shown in Figure 11-11. There will be a case number in that notification, which can be used as a reference for when the client engages IBM Remote Support.
11.3 Code updates
The LIC running on the HMC is updated as part of a new code bundle installation. The HMC can hold up to six previous versions of code in the Code Library. Each CPC can hold three versions of code (the previous version, the active version, and the next version). Most organizations plan for two code updates each year.
 
Best practice: Many clients with multiple DS8000 systems follow the update schedule that is detailed in this chapter. In this schedule, the HMC is updated a day or two before the rest of the bundle is applied. If a large gap exists between the present and destination level of bundles, certain DS CLI commands (especially DS CLI commands that relate to IBM Copy Services (CS)) might not be able to be run until the SFI is updated to the same level of the HMC. Your IBM SSR or IBM Technical Advisor or Technical Account Manager can help you in this situation.
Before you update the CPC OS and LIC, a pre-verification test is run to ensure that no conditions exist that prohibit a successful code load. The HMC code update installs the latest version of the pre-verification test. Then, the newest test can be run.
If problems are detected, one or two days are available before the scheduled code installation window date to correct them. This procedure is shown in the following example:
•Thursday:
a. Acquire the new code bundle and send them to the HMCs.
b. Update the HMCs to the new code bundle.
c. Run the updated pre-verification test.
d. Resolve any issues that were identified by the pre-verification test.
•Saturday :
Update (Activate) the SFI code.
The average code load time varies depending on the hardware that is installed, but 2.5 - 4 hours is normal. Always speak with your IBM SSR about proposed code load schedules.
Code recommendations are listed at DS8000 Code Recommendation.
Additionally, check multipathing drivers and storage area network (SAN) switch firmware levels for their current levels at regular intervals.
11.4 Host adapter firmware updates
One of the final steps in the CCL process is updating the host adapters. Normally, every code bundle contains new host adapter firmware. For DS8900F Fibre Channel (FC) adapters, regardless of whether they are used for open systems (FC) attachment or IBM Z system (Fibre Channel connection (IBM FICON)) attachment, the update process is concurrent with the attached hosts. The FC adapters use a technique that is known as adapter fast-load, which is the default option for updating. This technique allows the adapters to switch to the new firmware in less than 2 seconds.
This fast update means that single path hosts, hosts that boot from SAN, and hosts that do not have multipathing software do not need to be shut down during the update. They can keep operating during the host adapter update because the update is so fast. Also, no Subsystem Device Driver (SDD) path management is necessary.
Interactive host adapters also can be enabled if you want to control the host path manually. If so, before the host adapters are updated, a notification is sent and a confirmation is needed. You can then take the corresponding host paths offline and switch to other available paths.
11.4.1 Light-on fastload firmware update
Light-on fastload firmware update is a DS8900F feature that allows a host adapter to perform a fastload firmware update without dropping light to hosts and SAN switches. It decreases generated registered state change notification (RSCN) messages in SAN fabrics. It also eliminates warning messages or problems that are generated because of the light-off action of a traditional fastload. In addition, this feature shortens the duration of host I/O interrupts during the host firmware update because the DS8900F host ports stay in login states without extra SAN fabric communication actions, such as a login back to the connected SAN switch.
This function is usually enabled by default. For more information about how to enable this function, contact your IBM SSR.
11.4.2 Remote Mirror and Remote Copy path considerations
No special considerations are required for Remote Mirror and Remote Copy paths that use FC ports. The ability to perform a fast load means that no interruption occurs to the Remote Mirror operations.
11.4.3 Control-unit initiated reconfiguration
CUIR prevents the loss of access to volumes in IBM Z system environments because of incorrect or wrong path handling. This function automates channel path management in
IBM Z environments in support of selected DS8900F service actions. CUIR is available for the DS8900F when the DS8900F is operated in the z/OS and z/VM environments. The CUIR function automates channel path vary on and vary off actions to minimize the manual operator intervention during selected DS8900F service actions.
CUIR allows the DS8900F to request that all attached system images set all paths that are required for a particular service action to the offline state. System images with the correct level of software support respond to these requests by varying off the affected paths. The image then notifies the DS8900F subsystem that the paths are offline or that it cannot take the paths offline. CUIR reduces manual operator intervention and the possibility of human error during maintenance actions.
CUIR also reduces the time that is required for the maintenance window. This feature is useful in environments in which many systems are attached to a DS8900F.
11.5 Loading the code bundle
The DS8900F code bundle installation can be performed in different ways. The preferred method is through the IBM RCL process, where IBM Remote Support Personnel download the microcode bundle remotely from IBM Fix Central and then activate it remotely.
Starting with Release 9.3, loading the microcode can now be performed entirely by the client. The microcode is downloaded from IBM Fix Central, and the client can perform all the steps by using the DS8000 Storage Manager GUI. For more information, see 11.2.2, “Customer Code Load” on page 413.
The microcode also can be loaded by an IBM SSR onsite. To review and arrange the required services, contact your IBM SSR or your IBM Technical Account Manager.
11.6 Fast path concurrent code load
DS8900F supports CCL. CCL in DS8900F is basically the same as previous generations of DS8000. CCL is referred to as traditional CCL. DS8000 development always strives to improve the code load function’s robustness and reduce activation durations. A faster, more fault-tolerant code load method is known as fast path concurrent code load (FPCCL).
FPCCL is automatically set as the preferred code load function, assuming that the requirements of the bundle to be activated satisfy the requirements for FPCCL.
The FPCCL requirements were expanded to include the following features. The delta of the “coming from” level and the “go to” level consists of these elements.
•SFI code:
 – LPAR code
 – DA
•High-Performance Flash Enclosure (HPFE):
 – Small Computer System Interface (SCSI) Enclosure Services (SES) processor firmware
 – PSU firmware
•Host adapter firmware
•AIX interim fix
•IBM Power firmware for iPDUs and RPCCs
 
Important: The code load function reverts to traditional CCL if any additional components, other than the components that are listed previously, are included in the update.
FPCCL includes an autonomic recovery function, which means that FPCCL is far more tolerant to temporary non-critical errors that might surface during the activation. During the FPCCL, if an error is posted, the LIC automatically analyzes the error and evaluates whether CCL can continue. If it cannot, the LIC suspends the CCL and calls for service. The DS8900F system can continue with the code update with tolerable errors. The DS8900F FPCCL update is more robust with a much shorter duration. After the code update completes, your IBM SSR works to resolve any of the problems that were generated during the code update at a convenient time, allowing DS8900F clients to schedule the code update in a controlled manner.
During an update, a system is under less redundant conditions because certain components are undergoing a firmware update. With FPCCL, firmware activation time is drastically reduced. Therefore, system redundancy is improved with less exposure to non-redundant durations. In addition, firmware distribution time is also minimized because fewer components are involved in the code update.
The CCL duration of the DS8000 family continues to advance with the introduction of new technology. With the latest DS8900F firmware, the LIC preinstall can be arranged before your code update service window performs the code activation, distribution, and HMC update. The activation times of various components are greatly reduced.
11.7 Postinstallation activities
After a new code bundle is installed, you might need to complete the following tasks:
1. Upgrade the DS CLI of external workstations. For most new release code bundles, a corresponding new release of the DS CLI is available. The LMC version and the DS CLI version are usually identical. Ensure that you upgrade to the new version of the DS CLI to take advantage of any improvements.
A current version of the DS CLI can be downloaded from IBM Fix Central.
2. Verify the connectivity from each DS CLI workstation to the DS8900F.
3. Verify the DS Storage Manager connectivity by using a supported browser.
4. Verify the DS Storage Manager connectivity from IBM Spectrum Control to the DS8900F.
5. Verify the DS Storage Manager connectivity from IBM Copy Services Manager to the DS8900F.
6. Verify the connectivity from the DS8900F to all IBM Security Guardium Key Lifecycle Manager instances, or other servers in use.
11.8 Summary
IBM might release changes to the DS8900F LMC. These changes might include code fixes and feature updates that relate to the DS8900F.
These updates and the information about them are documented in the DS8900F Code cross-reference website. You can find this information for a specific bundle under the Bundle Release Note information section in DS8000 Code Recommendation.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.129.22.164