Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Dell EMC HCI Solutions for Microsoft Windows Server: Life Cycle Management Approach Comparison
Executive summary Lab setup and testing procedure Results and conclusions
Procedural steps
Attended time
Total time for maintenance window
Human error quotient
Summary
References

Human error quotient

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > White Papers > Dell EMC HCI Solutions for Microsoft Windows Server: Life Cycle Management Approach Comparison > Human error quotient

Human error quotient

  • Using the Dell EMC OpenManage Integration online catalog as the update source significantly minimizes risk related to performing the update process. It eliminates the need for installation decisions and manual data entry by an IT administrator. When you use the online catalog as the update source, you eliminate even the potential to inadvertently click the wrong button or proceed down the wrong path in an installation wizard. In addition, Dell EMC OpenManage Integration includes scripts that perform cluster health checks throughout the process that stop the update procedure if any errors are discovered. 

    Note: The online catalog method is only available if the Windows Admin Center gateway host is directly connected to the Internet.  

    The manual update method leaves far more potential for human error throughout the process that can result in workload interruption. The following table provides more details about this potential by explaining some of the riskiest steps:

    Table 6.              Manual steps with potential for human error

    Manual step

    Potential risk for human error

    Perform cluster health check.

    This step can be considered high risk because the PowerShell-based health check results can be misinterpreted. An IT operator can then unwittingly apply the updates to a cluster in a degraded state.

    Place AX node #1 into maintenance mode.

    This step is lower risk. However, IT operators must pay close attention and verify that the specific node has successfully entered maintenance mode before continuing.

    Obtain update catalog from DRM.

    This step is high risk because IT operators must select and export the catalog that is validated and certified for AX nodes. If they mistakenly select the catalog for another platform, the cluster will no longer be compliant with the support matrix, which can have severe consequences on performance and availability.

    Retrieve the list of driver versions installed on AX nodes.

    This step can be considered high risk because IT operators must analyze the list of drivers installed in the operating system and manually compare them with the drivers in the support matrix. Installing incorrect or noncertified operating system drivers places the nodes out of compliance with the support matrix, which could affect performance and availability.

    Take AX node #1 out of maintenance mode.

    This step is lower risk. However, after taking a node out of maintenance mode, IT operators must ensure that the cluster has properly rebalanced and that there are no storage jobs still in progress. If they are not paying close attention, the operators could move forward with placing the next node into maintenance mode before the cluster is healthy.