Do+Able Products 12347 Uživatelský manuál stáhnout pdf (Strana 51)

Hardware Management Console Best Practices

- 51 -

9.2 Concurrent versus Disruptive Updates

Starting with HMC V4R5, the behavior of the code update wizard on the HMC

changed. The new behavior favors concurrent updates over those requiring a

reboot. The wizard uses the name of the package to make the distinction.

Concurrent-capable update filenames differ from disruptive update filenames in

that the FFF and DDD fields are NOT equal. For example, a filename

01SF230_107_107.rpm is a disruptive code update package. An example of a

concurrent-capable code update filename would be 01SF230_165_108.rpm,

where the FFF field is 165 (the fix pack level) and the DDD field is 108 (the last

disruptive code level).

When the fully concurrent-enabled HMC performs the code update wizard

function, a filename of 01SF230_107_107.rpm and 01SF230_107_107.xml will

cause the HMC to perform a concurrent install with deferred disruptive activation.

This means that the system administrator will need to schedule a re-IPL at a

convenient time in order to bring the new code into active status. It will be applied

concurrently, but activated only after a reboot.

Since system release level 230, which came out in August 2005, power frame fix

packs (which begin with 02BP in their file names) have been concurrent with

respect to server operations. Although the Bulk Power Controllers reboot during

the process, power to the frame remains up and no interruption is required.

You can perform a concurrent update if the disruptive base is already installed

and active. For example, you can concurrently install a code update with the

filename 01SF230_165_108.rpm if the target system is already activated at the

01SF230_YYY_108 code level, where "YYY" is a number equal to or greater

than 108. This option does not apply to upgrades because upgrades are always

disruptive.

Applying the “165” level files to a system running 01SF230_105_105.rpm would

result in the need to perform a disruptive activate (requiring an outage) to get the

“108” base onto the managed system simultaneously with the “165” concurrent

update. This is why the file set is referred to as a concurrent-capable code update

file set. The code update is only

concurrent (no need to perform the re-IPL to have

the code “online”) when its last disruptive level or another concurrent level using

that base is already activated on the managed system.

File set names must follow naming rules as the HMC displays the fix pack level,

which can be seen either on the “View system information” task menu or in the

output of the lslic command entered in the restricted shell. Once a level value is

assigned to a fix pack in the “FFF” field of the filename, it must not be re-issued

to other fix packs within that release level.

1 2 ... 46 47 48 49 50 51 52 53 54 55 56 57

Žádné komentáře

Do+Able Products 12347 Uživatelský manuál Strana 51