HP Insight Orchestration 6.3 User Guide

The above are hpio.properties entries that Self Service Portal, Designer and the IO console
in SIM read directly.
Integrity firmware blade corruption during provisioning of the following Integrity blades: BL870c,
BL870c i2, BL890c, or BL860c i2.
Issue
Insight Orchestration issues power cycle operations during provisioning and deprovisioning when
deploying Integrity blades. If a power cycle operation happens before the boot process completes,
the blade HBA firmware could become corrupted.
Possible cause
Power cycle time requirement is measured as the time from power-on until the EFI shell prompt
appears.
For physical provisioning to perform correctly, Insight Orchestration and Logical Server Management
must be configured to wait the appropriate length of time for the slowest server blade to complete
booting.
Action
• In Insight Orchestration, the ..\Program Files\HP\Insight Orchestration\conf\
hpio.properties file, the serverboot.physical.wait.seconds attribute must
be increased.
• In Logical Server Management, the ..\Program Files\HP\Virtual Server
environment\conf\lsa\lsa.properties file, the INTEGRITY_POWERON_WAITTIME
attribute must be increased.
Following are recommended minimums. Depending on the size of memory and number of HBA
cards on each server blade, the values may need to be greater than the minimums.
• Integrity BL860c and BL860c i2 blades:
◦ For Insight Orchestration serverboot.physical.wait.seconds, use the default minimum
of 360 seconds.
◦ For LSM INTEGRITY_POWERON_WAITTIME, use the default minimum of 360000 milliseconds.
• BL870c and BL870c i2 blades:
For Insight Orchestration serverboot.physical.wait.seconds, use the default minimum
of 540 seconds.
◦
◦ For LSM INTEGRITY_POWERON_WAITTIME, use the default minimum of 540000 milliseconds.
• BL890c and BL890c i2 blades:
◦ For Insight Orchestration serverboot.physical.wait.seconds, use the default minimum
of 1080 seconds.
◦ For LSM INTEGRITY_POWERON_WAITTIME, use the default minimum of 1080000
milliseconds.
Blades that are not in use are shown in Insight Orchestration server pools, but Insight Orchestration
does not allocate the blades for provisioning.
Issue
—Possible cause
Run the command sbapi GetServerPools and check the isValidTarget value for the blade.Action
• If IsValidTarget=true, refresh the Servers view and try again.
• If IsValidTarget=false, the blade cannot be used for provisioning. Possible causes:
1. The blade has a hardware problem
2. The blade enclosure is in maintenance mode (verify via VCEM)
3. The blade is no longer in its enclosure (verify via OA)
4. The VC domain group is deleted (verify via VCEM)
If a blade is not expected to ever be available again for provisioning (especially under actions 3
and 4 in the preceding issue), it can be moved to another server pool created especially for
unavailable servers (IO contains the built-in Maintenance pool).
Miscellaneous issues 111