Licensed machine code
This chapter describes considerations that relate to the planning and installation of new licensed machine code (LMC) bundles on the IBM DS8880. The overall process for the DS8880 is the same as for previous models. However, several enhancements to power system firmware updates are described.
This chapter covers the following topics:
13.1 How new Licensed Internal Code is released
Most of the hardware components within the DS8880 system can be updated with new firmware when it is available:
Device adapters (DAs)
Host adapters (HAs)
Power subsystems:
 – Direct current uninterruptible power supply (DC-UPS)
 – Rack power control (RPC)
 – Fibre Channel Interface Cards (FCICs)
In addition, the Licensed Internal Code (LIC) and internal operating system that run on the Hardware Management Consoles (HMCs) and each central processor complex (CPC) can be updated. As IBM continues to develop the DS8880, new features are released through new LMC levels.
When IBM releases new LIC for the DS8880, it is released in the form of a bundle. The term bundle is used because a new code release can include updates for various DS8880 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 DS8880 cross-reference table of code bundles, see this website:
The cross-reference table shows the levels of code for currently released bundles. The cross-reference information is updated as new code bundles are released. It is important to maintain a current version of the data storage command-line interface (DS CLI).
The DS8880 uses the following naming convention for bundles: PR.MM.FFF.EEEE, where the components are:
P: Product (8 = DS8880)
R: Release Major (X)
MM: Release Minor (xx)
FFF: Fix Level (xxx)
EEEE: EFIX Level (0 is base, and 1.n is the interim fix build that is later than the base level)
The naming convention is shown in Example 13-1.
Example 13-1 BUNDLE level information
For BUNDLE 88.1.23.0 :
Product DS8880
Release Major 8
Release Minor 1
Fix Level 23
EFIX level 0
A release major/minor naming convention, such as 8.0, which is shown in Example 13-1 on page 378, stands for Release 8.01.
If DS CLI is used, you can obtain the CLI and LMC code level information by using the ver command. The ver command uses the following optional parameters and displays the versions of the CLI, Storage Manager, and licensed machine code:
-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 licensed machine code. You cannot use the -l and -s parameters together. See Example 13-2.
-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 graphical user interface (GUI) (Storage Manager GUI). This ID relates to HMC code bundle information.
-lmc (Optional): Displays the version of the LMC.
Example 13-2 Output of DS CLI ver -l command
dscli> ver -l
Date/Time: 29 April 2016 2:15:48 PM IBM DSCLI Version: 7.8.1.53 DS: -
DSCLI 7.8.1.53
StorageManager 8.8.2.0.20151021.1
HMC DSCLI 7.8.1.53
================Version==================
Storage Image LMC Bundle Version
=========================================
IBM.2107-75DMC11 7.8.1.53 88.1.23.0
The LMC level also can be retrieved from the DS Storage Manager by clicking Actions → Properties. See Figure 13-1.
Figure 13-1 LMC level under DS Storage Manager
13.2 Bundle installation
 
Important: The LMC is always provided by and installed by an IBM service support representative (IBM SSR). Installing a new LMC is not the client’s task. Read the Prerequisites section or Attention Must Read section in the Licensed Internal Code update instructions. Your IBM SSR will inform you during the planning phase if any prerequisites need to be considered.
The bundle package contains the following new levels of updated code:
HMC code levels:
 – HMC OS/managed system base
 – DS Storage Manager
 – Common Information Model (CIM) agent version
Managed system code levels
Program temporary fix (PTF) code levels
Storage facility image (SFI) code levels
HA code levels
DA code level
I/O enclosure code level
Power code levels
Fibre Channel interface card (FCIC) code levels
Storage enclosure power supply unit code levels
Disk drive module (DDM) firmware code level
The Code Distribution and Activation (CDA) software Preload is the current method that is used to run the concurrent code load distribution. By using the CDA software Preload, the IBM SSR performs every non-impacting concurrent code load 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 SSRs can also download the bundle to their notebook and then load it on the HMC by using a service tool. After the CDA Preload software starts, the following steps are performed automatically:
1. Downloads or acquires the release bundle from either the DVD or network to the HMC hard disk drive (HDD).
2. Prepares the HMC with any code update-specific fixes.
3. Distributes the code updates to the logical partition (LPAR) and stages them on an alternate base operating system (BOS) repository.
4. Performs scheduled precheck scans until the distributed code is activated by the user for up to 11 days.
5. After 11 days without Activation, the code expires and is automatically removed from the alternate BOS.
Any time after the software preload 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 concurrent code load (CCL).
The code installation process involves the following stages:
1. Update 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. Perform updates to the CPC operating system (currently AIX V7.x), and updates to the internal LMC, which are performed individually. To update each CPC, the logical subsystem fails over to the alternate CPC. This process updates the firmware that is running on each device adapter that is owned by that CPC.
4. Perform updates to the host adapters. For DS8880 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 attachments, see 3.3.2, “Host connections” on page 72.
5. New DC-UPS and RPC firmware is periodically released. New firmware can be loaded into each RPC card and DC-UPS directly from the HMC. The DS8880 includes the following enhancements about the power subsystem LIC update for DC-UPS and RPC cards. For more information, see 3.6, “RAS on the power subsystem” on page 86.
 – During the DC-UPS firmware update, the current power state is maintained so the DC-UPS remains operational during a LIC update.
 – During the RPC firmware update, RPC0 is first placed into Service Mode while updated and verified, then resumed and the alternate card RPC1 is completed.
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 logical subsystems 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 67.
7. It is important to maintain the latest DDM firmware because enhancements for efficiency, performance, and reliability are often delivered. DDM firmware update is a concurrent process in the DS8880 series family. Direction to update the DDM 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. The IBM SSR normally starts the CDA process and then monitors its progress by using the HMC. From bundle 88.0.x.x, power subsystem firmware update activation (RPC cards and DC-UPSs) is included in the same general task that is started at CDA. In previous bundles, it was necessary to start a power update from an option in the HMC when the other elements were already updated. This option remains available when only a power subsystem update is required.
 
 
Important: For the DS8880 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 DS8000 models in the environment as well. For more information, see the Release Notes or consult your local SSR.
13.3 Code updates
The LIC currently running on the HMC is updated as part of a new code bundle installation. The HMC can hold up to six older 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.
 
Preferred practice: Many clients with multiple DS8000 systems follow the updating 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) might not be able to be run until the SFI is updated to the same level of the HMC. Your IBM SSR can assist you in this situation.
Before you update the CPC operating system 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 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 consult with your IBM SSR about proposed code load schedules. Code bundle preferences are listed on the following website:
Additionally, check multipathing drivers and storage area network (SAN) switch firmware levels for their current levels at regular intervals.
13.4 Host adapter firmware updates
One of the final steps in the concurrent code load process is updating the host adapters. Normally, every code bundle contains new host adapter firmware. For DS8880 Fibre Channel cards, regardless of whether they are used for open systems (FC) attachment or IBM z Systems (Fibre Channel connection (FICON)) attachment, the update process is concurrent to the attached hosts. The Fibre Channel cards use a technique that is known as adapter fast-load, which is the default option for updating. This technique allows the cards 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 HA also can be enabled if you want to control the host path manually. If so, before the HA cards 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.
13.4.1 Light-on fastload firmware update
Light-on fastload firmware update is a new DS8880 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 DS8880 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 enabled, by default, for DS8880 16 Gbps host adapters. It can also be enabled on 8 Gbps host adapters if you want to use this new feature. Contact your IBM SSR for more information about how to enable this function.
13.4.2 Remote Mirror and Copy path considerations
No special considerations are required for Remote Mirror and Copy paths that use Fibre Channel ports. The ability to perform a fast load means that no interruption occurs to the Remote Mirror operations.
13.4.3 Control-unit initiated reconfiguration
CUIR prevents the loss of access to volumes in the IBM z Systems environments because of incorrect or wrong path handling. This function automates channel path management in z Systems environments in support of selected DS8880 service actions. CUIR is available for the DS8880 when the DS8880 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 DS8880 service actions.
CUIR allows the DS8880 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 DS8880 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 DS8880.
13.5 Loading the code bundle
The DS8880 code bundle installation is performed by the IBM SSR. Contact your IBM SSR to review and arrange the required services.
13.6 Fast path concurrent code load
DS8880 supports concurrent code load (CCL). CCL in DS8880 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 robustness and reduce activation durations. A faster, more fault-tolerant code load method is known as Fast Path CCL (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.
For Release 8, the FPCCL requirements are 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):
 – SCSI Enclosure Services (SES) processor firmware
 – Power supply unit (PSU) firmware
HA firmware
AIX PTF
Power firmware for DC-UPS and RPC cards
 
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 DS8880 system can continue with the code update with tolerable errors. The DS8880 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 DS8880 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 keeps improving with the introduction of new technology. With the latest DS8880 firmware, the LIC preload can be arranged before your code update service window achieves the code activation, distribution, and HMC update. The activation times of various components are greatly reduced.
13.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 of the 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 Fix Central from the following websites:
 
2. Verify the connectivity from each DS CLI workstation to the DS8880.
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 DS8880.
5. Verify the DS Storage Manager connectivity from Copy Services Manager (CSM) to the DS8880.
6. Verify the connectivity from the DS8880 to all IBM Security Key Lifecycle Manager servers in use.
13.8 Summary
IBM might release changes to the DS8880 Licensed Machine Code. These changes might include code fixes and feature updates that relate to the DS8880.
These updates and the information about them are documented in the DS8880 Code cross-reference website. You can find this information for a specific bundle under the Bundle Release Note information section on the website.
 
..................Content has been hidden....................

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