Cisco Cisco UCS C22 M3 Rack Server Guia De Resolução De Problemas
Contents
Introduction
Prerequisites
Terminating USRM/VRSM instances before disabled Consistency check
Downloading the utility.
Commands for RedHat/Linux
ESXi Instructions
Installation on VMware ESXi 5.x
Commands for VMware Vsphere
Introduction
This document describes the steps to disable the Redundant Array of Individual Disks (RAID)
controller Consistency Check on LSI RAID Controllers which can negatively impact some
applications with strict Input/Output (I/O) requirements. Once such group of applications
with demanding I/O requirements is Universal Session and Resource Manager / Videoscape
Session Resource Manager (USRM/VSRM). Due to the potential I/O wait impact to these
applications that can occur while consistency checks are running, it is recommended to disable
Consistency Checks on all virtual drives/raid volumes. See
controller Consistency Check on LSI RAID Controllers which can negatively impact some
applications with strict Input/Output (I/O) requirements. Once such group of applications
with demanding I/O requirements is Universal Session and Resource Manager / Videoscape
Session Resource Manager (USRM/VSRM). Due to the potential I/O wait impact to these
applications that can occur while consistency checks are running, it is recommended to disable
Consistency Checks on all virtual drives/raid volumes. See
Prerequisites
Cisco Unified Computing System (UCS) M3 Rack servers with LSI 92XX model Raid controllers.
Disabling Consistency Check will require a maintenance window for the USRM/VSRM
application.
application.
Terminating USRM/VRSM instances before disabled Consistency check
There are up to 8 instances of USRM/VSRM on a UCS C220. Each instance will need to be
terminated prior to executing the procedure for disabling Consistency Check. When the
Consistency Check procedure is complete each instance will have to be restarted manually.
terminated prior to executing the procedure for disabling Consistency Check. When the
Consistency Check procedure is complete each instance will have to be restarted manually.
Note: The 2 processes below should be included in a high level Method of Procedure (MOP)
written for the individual customer systems / requirements. For example: the MOP will include
coordination of server failover and failback to minimize customer impact. Each customer may
have different requirements that are addressed in the MOP.
written for the individual customer systems / requirements. For example: the MOP will include
coordination of server failover and failback to minimize customer impact. Each customer may
have different requirements that are addressed in the MOP.
To Terminate the USRM/VSRM software follow these steps. Note: These steps need to be
completed for each instance of USRM/VSRM.
completed for each instance of USRM/VSRM.
Open the USRM/VSRM Web User Interface (UI) in a Browser
1.
Navigate to the Reset Page
2.
Set ServerState to “Terminate” using the drop down box.
3.
Click the Commit Changes button.
4.
Result: The USRM/VSRM software will Terminate and not restart.