HP ProLiant BL660c HP BladeSystem c-Class Onboard Administrator Failover - Page 3

subsequent OA failover. As a result, VCM may process incomplete or inconsistent information from

Get HP ProLiant BL660c PDF manuals and user guides View all HP ProLiant BL660c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 3 highlights

When an OA failover occurs, there is a period of time where Virtual Connect Manager (VCM) is not able to communicate with the OA. It is strongly advised not to perform any VCM maintenance tasks during OA failover testing. When VCM re-establishes communication with the OA, it executes an Enclosure Recovery process. VCM reads the enclosure data and validates that this enclosure information is consistent with the information in the existing VCM database. If no changes are seen, a checkpoint (copying of the VCM Domain configuration) is performed in the backup VCM module, and the recovery from the OA failover is complete. This operation occurs very quickly after the OA failover is complete. If the enclosure data is not consistent with the VCM database, VCM will reinitialize the VC parameters associated with changes identified. This full recovery may take several minutes depending on the actual configuration changes identified. The user can monitor the Checkpoint Pending status (Figure 1) to determine when recovery is complete. If multiple OA failovers are initiated too rapidly, the VCM may not complete all of the recovery steps prior to a subsequent OA failover. As a result, VCM may process incomplete or inconsistent information from the OA. If VCM determines a change has occurred in the database during an Enclosure Recovery process, VCM will attempt to rewrite VC Server profile parameters. If the Server is powered up, VCM will place the Profile associated with this Server into a Profile Pending state and wait for a power off event to occur (VC parameters cannot be written to the server if it is powered up). In VC firmware prior to v3.30, server connectivity will be disconnected in the Profile Pending state. In the VC firmware v3.30 or later, Profile Pending state will not affect connectivity. Servers in the Pofile Pending state must be power cycled in order to restore the VC profile. Figure 1: VC Manager - Checkpoint Pending Note the yellow „Checkpoint Pending‟ - warning symbol 3

  • 1
  • 2
  • 3
  • 4
  • 5
3
When an OA failover occurs, there is a period of time where Virtual Connect Manager (VCM) is not able to
communicate with the OA. It is strongly advised not to perform any VCM maintenance tasks during OA failover
testing. When VCM re-establishes communication with the OA, it executes an Enclosure Recovery process.
VCM
reads the enclosure data and validates that this enclosure information is consistent with the information in the existing
VCM database.
If no changes are seen, a checkpoint (copying of the VCM Domain configuration) is performed in
the backup VCM module, and the recovery from the OA failover is complete.
This operation occurs very quickly after
the OA failover is complete.
If the enclosure data is not consistent with the VCM database, VCM will reinitialize the VC parameters associated
with changes identified.
This full recovery may take several minutes depending on the actual configuration changes
identified.
The user can monitor the Checkpoint Pending status (Figure 1) to determine when recovery is complete.
If multiple OA failovers are initiated too rapidly, the VCM may not complete all of the recovery steps prior to a
subsequent OA failover. As a result, VCM may process incomplete or inconsistent information from the OA. If VCM
determines a change has occurred in the database during an Enclosure Recovery process, VCM will attempt to
rewrite VC Server profile parameters. If the Server is powered up, VCM will place the Profile associated with this
Server into a Profile Pending state and wait for a power off event to occur (VC parameters cannot be written to the
server if it is powered up).
In VC firmware prior to v3.30, server connectivity will be disconnected in the Profile Pending state. In the VC
firmware v3.30 or later, Profile Pending state will not affect connectivity. Servers in the Pofile Pending state must be
power cycled in order to restore the VC profile.
Figure 1:
VC Manager
–
Checkpoint Pending
Note the yellow
„Checkpoint Pending‟
–
warning symbol