Do+Able Products 12347 Manual de usuario descargar pdf (Pagina 35)

Hardware Management Console Best Practices

- 35 -

Another observed problem has been the GUI isn’t reflecting the true managed

system or frame status or configuration. The CLI can be used to see if it gives up-

to-date information. If so, this means the GUI has either stopped receiving

indication data, or no indications are being propagated to it. A Reload (F5) can

refresh the GUI in this situation. If the command line is also incorrect, the HMC

has stopped receiving event notifications from the managed system or frame. To

recovery from this situation, perform the Rebuild Managed System task.

The FSP provides the HMC with the capability to set locks on the platform. The

FSP does not interpret the locks, but rather leaves it up to the HMC functions to

do that. These locks are used for synchronization of operations from one or two

(dual) HMCs. In a dual HMC environment, situations can arise where both

HMCs perform tasks against the same managed system and require the same lock.

When HMC 2 needs to perform a task that requires a lock that HMC 1 is currently

holding, HMC 2 will wait and retry to acquire the lock. If after a few attempts it

is unsuccessful, the operation will fail and the user will be notified accordingly.

Often this blocked state can be mistaken for a “hang,” when that in fact is not the

case. However, it is possible for HMC 1 to acquire a lock and fail to release it.

Should this happen, HMC 2 can be used to disconnect HMC 1. When an HMC is

disconnected, all locks owned by the HMC are reset. To due this, any

hmcsuperadmin user can run the ‘Disconnect Another HMC’ GUI task on

HMC 2 against HMC1. This can only be done from the graphical interface. There

is no corresponding command line version of this task.

1 2 ... 30 31 32 33 34 35 36 37 38 39 40 ... 56 57

Sin comentarios

Do+Able Products 12347 Manual de usuario Pagina 35