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

Hardware Management Console Best Practices

- 34 -

• Incomplete: The HMC is unable to gather all system information from the

managed system or frame. In some cases this could be due to a network error

causing a temporary disruption to HMC–FSP interactions, or managed system

hardware configuration changes being performed from a redundant HMC. To

verify, an attempt can be made to recover from this state by using the Rebuild

Managed System GUI task, or the chsysstate command with –o rebuild

–r sys flags. Neither can be performed by task role hmcviewer. If this

does not change the state, try resetting the HMC–FSP connection (see above –

No Connection), then try rebooting the HMC if resetting does not help. If the

problem persists, gather the trace files and logs for support. More information

can be found at:

http://publib.boulder.ibm.com/infocenter/iseries/v1r2s/en_US/info/ipha5/manag

edsystemstates.htm#managedsystemstates__incompletestate

• Recovery: The save area of the FSP, where partition profile and some partition

information is kept, could be corrupted, cleared, or out-of-sync with the cached

copy the HMC maintains in its filesystem. First, it would be good to know

whether the managed system has been updated recently; firmware updates could

clear NVRAM. If no system update has been performed recently, you can

perform the Recovery Partition Data task on the managed system from the GUI.

You will be presented with two options: Restore profile data from HMC backup

data, and Initialize the managed system. The former (chsysstate –o

recover –r sys on the CLI – not as hmcviewer) will restore the save

area with the cached copy on the HMC. The latter (rstprofdata –l 4 on

the CLI – only as hmcsuperadmin or hmcoperator) will clear all

partition configuration information! Don’t use this unless you’re willing to

rebuild the partition from scratch. If neither approach works, gather trace files

and logs. For more information see:

http://publib.boulder.ibm.com/infocenter/iseries/v1r2s/en_US/info/ipha5/manag

edsystemstates.htm#managedsystemstates__recoverystate

A problem more severe than No Connection is the situation when no systems or

frames appear where they had appeared before. While there can be many reasons

for this, one common scenario observed is when a managed system or frame is

removed from the HMC. This could have been through the Remove Connection

task or rmsysconn in the CLI. When this system is then added back into the

HMC’s management domain, the HMC (as DHCP server) will not redetect it. If

you remove a managed system, and have reason to believe this HMC might again

manage it in the future, ‘mksysconn -o auto’ should be run to purge the

HMC of its management history and allow it to once again provide IP addresses

to the managed server.

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

Žádné komentáře

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