Server Administrator Frequently Asked Questions (FAQ) 

  1. Install/Uninstall
  2. Distributed Web Server (DWS)
  3. Events/Alerts/Protocols
  4. Management Consoles (Dell OpenManage Essentials)
  5. Login, Active-Directory and Authentication
  6. ESXi
  7. Storage Management

1. Install/Uninstall

1.1  What ports do Systems Management applications use?

The default port used by Server Administrator is 1311. These ports are configurable. For port information of a particular component, see the User Guide of that respective component at To connect to the instrumentation component installed on Citirix XenServer, you have to use port number 5986. For example: IPAddress:5986 and check ignore certificate warnings options on the DWS console on the remote system

1.2  When I run virtual media on the DRAC controller over a Wide Area Network (WAN) with low bandwidth and latency, launching Systems Management Install directly on the virtual media failed, what do I do?

Copy the web install package to the local system and then launch Systems Management Install.

1.3 Do I need to uninstall the Adaptec Fast Console application installed on the system before installing the Server Administrator Storage Management Service?

Yes, if you already have Adaptec Fast Console installed on the system, you must uninstall this application before installing the Server Administrator Storage Management Service.

1.4 How do I fix a faulty installation of Server Administrator on Microsoft Windows operating system?

You can fix a faulty installation by forcing a reinstall and then performing an uninstall of Server Administrator. To force a reinstall:

1. Find out the version of Server Administrator that was previously installed.

2. Download the installation package for that version.

3. Locate <SysMgmt or SysMgmtx64>.msi and enter the following command at the command prompt to force a reinstall.

msiexec /i <SysMgmt or SysMgmtx64>.msi REINSTALL=ALL REINSTALLMODE=vomus

4. Select Custom Setup and choose all the features that were originally installed. If you are not sure which features were installed, select all the features and perform the installation.

NOTE: If you have installed Server Administrator in a non-default directory, make sure to change it in the Custom Setup as well.

Once the application is installed, you can uninstall it from Add/Remove Programs.

1.5 When launching the Systems Management Install, an error message may display, stating a failure to load a specific library, a denial of access, or an initialization error. An example of installation failure during Systems Management Install is failed to load OMIL32.DLL. What do I do?

This is most likely due to insufficient Component Object Model (COM) permissions on the system. To resolve this situation, see the article Install may also fail, if a previous installation of Systems Management software or some other software product was unsuccessful. Delete the following temporary Windows installer registry, if present:


1.6 I get a misleading warning or error message during Systems Management installation.

If there is insufficient disk space on the Windows system drive, you may encounter misleading warning or error messages when you run Systems Management Install. Additionally, Windows installer requires space to temporarily extract the installer package to the %TEMP% folder. Ensure that you have sufficient disk space (100 MB or more) on the system drive prior to running Systems Management Install.

1.7 I am getting the following error message while launching systems management Install:

An older version of Server Administrator software is detected on this system. You must uninstall all previous versions of Server Administrator applications before installing this version

If you see this error when trying to launch Systems Management Install, it is recommended that you run the OMClean.exe program, under the SYSMGMT\srvadmin\support\OMClean directory, to remove an older version of Server Administrator installed on the system.

1.8 Do I need to uninstall previous versions of Server Administrator before installing Citrix Metaframe?

Yes. Uninstall the previous versions of Server Administrator before installing Citrix Metaframe (all versions). As errors may exist in the registry after the Citrix Metaframe installation, you must reinstall Server Administrator.

1.9 When I run Systems Management Install, I see unreadable characters on the Prerequisite Checker screen.

When you run Systems Management Install in English, German, French, or Spanish and get unreadable characters on the Prerequisite Checker screen, ensure that the web browser encoding has the default character set. Resetting the web browser encoding to use the default character set resolves the problem.

1.10 I have installed Server Administrator and Online Diagnostics in the same directory and Online Diagnostics fails to work, what do I do?

If you have installed Server Administrator and Online Diagnostics in the same directory, Online Diagnostics may fail to work. On uninstalling Server Administrator, you may also lose all Online Diagnostics files. To avoid this problem, install Server Administrator and Online Diagnostics in different directories. In general, it is recommended not to install more than one application in the same directory.

1.11 I have installed Server Administrator using remote Server Administrator deploy feature of Dell OpenManage Essentials on Windows Server 2008, I do not see Server Administrator icon on the desktop?

On an initial Server Administrator install using remote Server Administrator deploy (OMSA push) on a server running Windows Server 2008, the Server Administrator icon is not visible until the desktop is refreshed manually by pressing the <F5> key.

1.12 I see a warning message while uninstalling Server Administrator on Windows Server 2008?

While uninstalling Server Administrator on Windows Server 2008, you may see a warning message as the installer tries to remove the shortcut. Click OK to continue the uninstallation.

1.13 Where can I find the MSI log files?

By default, the MSI log files are stored in the path defined by the %TEMP% environment variable.

1.14 I downloaded the Server Administrator files for Windows from the Dell Support website and copied it to my own media. When I tried to launch the SysMgmt.msi file, it failed. What is wrong?

The MSI file requires all installers to specify the MEDIAPACKAGEPATH property, if the MSI file does not reside on the root of the DVD. This property is set to SYSMGMT\srvadmin\windows\SystemsManagement for the Managed System software MSI package. If you want to make your own DVD you must ensure that the DVD layout stays the same. The SysMgmt.msi file must be located in the SYSMGMT\srvadmin\windows\SystemsManagement. For more detailed information, go to and search for MEDIAPACKAGEPATH Property

1.15 Does Systems Management Install support Windows Advertised installation?

No. Systems Management Install does not support Windows Advertised installation - the process of automatically distributing a program to the client computers for installation, through the Windows group policies.

1.16 How do I check the disk space availability during custom installation?

In the Custom Setup screen, click an active feature to view the hard drive space availability or to change the installation directory. For example, if Feature A is selected for installation (active), the Change and Space buttons are enabled and if you click Feature B (not active), the Change and Space buttons are disabled,. Click Change to change the installation directory or click Space to view the available disk space.

1.17 What do I do when I see the current version is already installed message is displayed?

If you upgrade from version X to version Y using MSP and then try to use the version Y DVD (full install), the prerequisite checker on the version Y DVD informs you that the current version is already installed. If you proceed, the installation does not run in Maintenance mode and you do not get the options to Modify, Repair, or Remove. Proceeding with the installation removes the MSP and creates a cache of the MSI file present in the version Y package. When you run it a second time, the installer runs in Maintenance mode.

1.18 In the Prerequisite Checker screen, I get the following message. What can I do to resolve this problem? An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly.

This error occurs when the Prerequisite Checker accesses the Systems Management script, vbstest.vbs (a Visual Basic script), to verify the installation environment, and the script fails. The possible causes are:

  • Incorrect Internet Explorer Security Settings.

Ensure that ToolsInternet OptionsSecurityCustom level…ScriptingActive scripting is set to Enable.

Ensure that ToolsInternet OptionsSecurityCustom level…ScriptingScripting of Java applets is set to Enable.

  • Windows Scripting Host (WSH) has disabled the running of VBS scripts. The WSH is installed by default during the operating system installation. On Windows 2003, WSH can be configured to prevent the running of scripts with a .VBS extension.
  • Right-click My Computer on the desktop and click OpenTools Folder Options…File Types.
  • Look for the VBS file extension and ensure that File Types is set to VBScript Script File.
  • If not, click Change and choose Microsoft Windows Based Script Host as the application that gets enabled to run the script.

WSH is the wrong version, corrupted, or not installed. Download WSH from

1.19 Can I launch the installation without running the Prerequisite Checker? How do I do that?

Yes, you can run the MSI of the managed system software, directly from SYSMGMT\srvadmin\Windows\SystemsManagement. In general, it is not recommended to bypass the Prerequisite Checker as there could be important information that you would not know otherwise.

1.20 Do I need to reboot the system after upgrading Systems Management?

Upgrade may require a reboot, if the files to be upgraded are in use. This is a typical Windows installer behavior. It is recommended that you reboot the system when prompted.

1.21 Where can I see the Server Administrator features that are currently installed on my system?

Browse to the Windows Control Panel and double-click Add/Remove Programs to view the Server Administrator features that are currently installed.

1.22 What are the names of all the Systems Management features under Windows?

The following table lists the names of all systems management features and their corresponding names in Windows.

  • Server Administrator Instrumentation Service: DSM SA Data Manager, DSM SA Event Manager
  • Server Administrator: DSM SA Connection Service, DSM SA Shared Services
  • Server Administrator Storage Management Service: Mr2kserv
  • Remote Access Controller Console (DRAC 4): Remote Access Controller 4 (DRAC 4)

1.23 After installing Server Administrator on Red Hat Enterprise Linux/SUSE Linux Enterprise Server operating system, I cannot log in.

Log out and then log in again to access the Server Administrator Command Line Interface (CLI).

1.24 I see the following message when I try to install Server Administrator on a guest Linux operating system. ./ line 2295 : [: ==: unary operator expected.

When installing Systems Management components on a guest Linux operating system, the warning message may be displayed. However, the installation continues and completes without any loss of functionality.

1.25 I manually installed my Red Hat Enterprise Linux 4 (64-bit) operating system and can see RPM dependencies while installing Server Administrator. Where can I find these dependent RPM files?

For Red Hat Enterprise Linux, the dependent RPM files are on the Red Hat Enterprise Linux installation media. All other RPMs are available in the /SYSMGMT/srvadmin/linux/RPMS/supportRPMS\opensource-components directory. To install or update all the dependent RPM files execute the following command:

rpm –ivh /SYSMGMT/srvadmin/linux/RPMS/ supportRPMS/opensource-components

You can then continue with the Server Administrator installation.

1.26 I have performed a non-default install of the Linux operating system using the Linux operating system media, I see missing RPM file dependencies while installing Server Administrator?

Server Administrator is a 32-bit application. When installed on a system running a 64-bit version of Red Hat Enterprise Linux operating system,  Server Administrator remains a 32-bit application, while the device drivers installed by Server Administrator are 64-bit. If you attempt to install Server Administrator on Red Hat Enterprise Linux (versions 5 and version 6) for Intel EM64T, ensure that you install the applicable 32-bit versions of the missing RPM file dependencies.

The 32-bit RPM versions always have i386 in the file name extension. You may also experience failed shared object files (files with so in the file name extension) dependencies. In this case, you can determine which RPM is needed to install the shared object, by using the RPM --whatprovides switch. For example: rpm -q --whatprovides

An RPM name such as pam-0.75-64 could be returned, so obtain and install the pam-0.75-64.i386.rpm. When Server Administrator is installed on a system running a 64-bit version of Linux operating system, ensure that the compat-libstdc++-<version>.i386.rpm RPM package is installed. You need to resolve the dependencies manually by installing the missing RPM files from the Linux operating system media.

NOTE: If you are using later versions of supported Linux operating systems and the RPM files available in the directory SYSMGMT/srvadmin/linux/RPMS/supportRPMS on the DVD are incompatible, use the latest RPMs from the operating system media.

1.27 Where can I find the source packages for Open Source RPMs?

Source packages for Open Source RPMs are available on a DVD image that can be ordered.

1.28 What do I do when management station RAC utility installation fails due to missing RPM file?

During the installation of the management station RAC utility (mgmtst-racadm RPM under /SYSMGMT/ManagementStation/linux/rac directory on the Systems Management Tools and Documentation DVD), the installation may fail due to missing RPM file dependencies on libraries. Install the compat-libstdc++ RPM provided in the same directory to resolve the dependency and retry the installation.

1.29 When using the rpm -e 'rpm -qa | grep srvadmin' command to remove Systems Management software, some RPM utility versions may schedule an uninstallation in an incorrect order, which results in users encountering misleading warning or error messages. What is the solution?

The solution is to use the systems management uninstall script, provided on the DVD.

1.30 What do I do when I am asked to authenticate using the root user account?

Systems Build and Update Utility adds a script to the .bash_profile file of the root user that prompts for the installation of Systems Management software. This script may interfere with remote client applications that authenticate using the root user account on the system, but do not have a means to handle user prompts. To remedy this limitation, edit the .bash_profile file and comment the line [ ${SHLVL}....

During uninstallation, error: %preun(srvadmin-NAME-X.Y.Z-N.i386) scriptlet failed, exit status 1 error message is displayed.

There may be problems uninstalling Server Administrator after an unsuccessful upgrade during a manual RPM upgrade.

The following error message is displayed:

error: %preun(srvadmin-NAME-X.Y.Z-N.i386) scriptlet failed, exit status 1

In this case, NAME is a feature name, for example omacore. X.Y.Z-N is the version and build number of the feature. Some possible solutions to rectify this problem:

1. Attempt to uninstall again. For example, use the following command:

 rpm -e srvadmin-NAME-X.Y.Z-N.i386

2. Delete the upgrade.relocation=bad line, if present in the /etc/omreg.cfg file and attempt to uninstall again.

1.31 Why am I getting a warning concerning the RPM package key during installation?

The RPM files are signed with a digital signature. To avoid this warning, you should mount the media or package, and import the key using a command such as the following:

 rpm --import /mnt/dvdrom/SYSMGMT/srvadmin/linux/RPM-GPG-KEY

1.32 What are the names of all the Systems Management features under Red Hat Enterprise Linux or SUSE Linux Enterprise Server?

The following table lists the names of all systems management features and their corresponding init script names under Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems.

DSM SA Device Drivers:


DSM SA Data Engine Service:


DSM SA Shared Service:


DSM SA Connection Service:


DSM SM LSI Manager:


Remote Access Controller (DRAC 4):


Integrated Remote Access Controller (iDRAC):


Remote Access Controller (DRAC 5):


1.33 What are the additional components that can be installed on a system that already has Server Administrator installed?

There are a few additional components that can be installed on a system that already has Server Administrator installed. For example, you can install Online Diagnostics on a system that has previously been installed with managed system software. On such a system, while uninstalling Server Administrator, only those RPM packages that are not required by any of the newly installed components are uninstalled. In the example above, Online Diagnostics requires packages such as - srvadmin-omilcore-X.Y.Z-N and srvadmin-hapi-X.Y.Z-N. These packages are not uninstalled during an uninstallation of Server Administrator.

In this case, if you try to install Server Administrator later by running the sh command, the following message is displayed:

Server Administrator version X.Y.Z is currently installed.

Installed components are:

  • srvadmin-omilcore-X.Y.Z-N
  • srvadmin-hapi-X.Y.Z-N

Do you want to upgrade Server Administrator to X.Y.Z? Press (y for yes| <Enter> to exit):

On pressing <y>, only those Server Administrator packages (in the example above), srvadmin-omilcore-X.Y.Z-N and srvadmin-hapi-X.Y.Z-N residing on the system are upgraded.

If you have to install other Systems Management components as well, sh command has to be performed again.

1.34 What happens if I install the RPM package on an unsupported system or on an unsupported operating system?

If you try to install the RPM packages on an unsupported system or an unsupported operating system, you may see unpredictable behavior during the install, uninstall, or during use of the RPM package. Most of the RPM packages have been written and tested for supported systems and the Linux versions listed in the readme.

1.35 Can I install Server Administrator on Fedora, College Linux, Mint, Ubuntu, Sabayon or PClinux?

No, Server Administrator does not support these operating systems.

 1.36 What is the minimum permission level required to install Server Administrator?

To install Server Administrator, you must have Administrator level privileges. Power Users and Users do not have permission to install Server Administrator.

1.37 Is there an upgrade path required to install Server Administrator?

For systems that are running Server Administrator version 4.3, you must upgrade to a 6.x version and then to version 7.x. For systems running a version prior to 4.3, you must upgrade to version 4.3, then to a 6.x version, and then to version 7.x (x indicates the version of Server Administrator you want to upgrade to).

1.38 How do I determine what is the latest version of Server Administrator available for my system?

Refer to the Server Administrator Manuals page at The latest documentation version reflects the version of OpenManage Server Administrator available.

1.39 How do I know what version of Server Administrator is running on my system?

After logging in to Server Administrator, browse  to PropertiesSummary. You can find the version of Server Administrator installed on your system in the Systems Management column.

You can also find the version information from the Add/Remove Programs (for Windows) or the About dialog box once logged in to Server Administrator console.

1.40 Are there other ports users can use apart from 1311?

Yes, you can set your preferred https port. Browse to Preferences General SettingsWeb ServerHTTPS Port. Instead of the Use default option, select the Use radio button to set your preferred port.

Note: Changing the port number to an invalid or in-use port number may prevent other applications or browsers from accessing Server Administrator on the managed system. For the list of default ports, see the Dell OpenManage Installation and Security User's Guide.

1.41 What all Operating systems are supported for Server Administrator Install?

VMware vSphere (ESX/ESXi), Citirix XenServer , Red Hat Enterprise Linux , SUSE Linux Enterprise Server  and various Microsoft Windows operating system flavors. For details, refer to the Dell Systems Management - OpenManage Software

Support Matrix  at

1.42 What all Server Administrator components are not installed on ESXi/XenServerXEN?

Web Server and CLI components are not installed on ESXi and XenServer operating system(s). This means omreport or omconfig and such commands are not available for Server Administrator installed on these operating system(s).

1.43 How can I see the Server Administrator console for ESXi/XenServer?

You will have to use Distributed Web Server (DWS) component installed on any other system to access these OS instrumented details.

1.44 Can I upgrade an already installed Server Administrator version on ESXi and XenServer?

No. The upgrade path is not supported for these operating systems.

1.45 What is the Server Administrator install folder location on ESXi?

It’s different from ESXi and can be found under: /usr/lib/ext/dell/srvadmin/sbin

1.46 How to install Server Administrator on XenServer?

Refer to chapter 7 in the Server Administrator Installation Guide. To know about the supported XenServer version, refer the Dell Systems Management - OpenManage Software Support Matrix .

2. Distributed Web Server

2.1 What is Distributed Web-Server (DWS)?

DWS is a Server Administrator Web-based Systems Management functionality, and one of the management interfaces that allows you to manage systems locally or remotely. Install only if you want to remotely monitor the managed system. You need not have physical access to the managed system. You will require Remote Enablement installed on the required system.

If you are installing Server Administrator on an unsupported system, the installer displays only the Server Administrator Web Server option.

DWS can be launched using the desktop icon (For example: on systems running the Windows operating system) and it is not the same as launching the browser and directly using the remote IP address and port number.

2.2 Where can I use Distributed Web-Server (DWS)?

To access instrumentation details (server/storage information) from Server Administrator  installed on the ESXi. You can install DWS on a remote system, install Server Administrator VIB on the ESXi, launch DWS and provide the ESXi IP and credentials to connect to the Server Administrator instrumentation agent present on the ESXi operating system.

Same use case for  XenServer. Please note, the default port on XenServer is 5986.

You can use this for any Red Hat Enterprise Linux/ SUSE Linux Enterprise Server or any Windows system as well and reduce the Server Administrator instrumentation footprint on the servers. DWS can be installed on a  common system and you can connect to all those servers where only from Server Administrator instrumentation component is installed. Ensure the Remote enablement component is installed and configured on the target systems.

2.3 What do I do when the creation of WinRM listener fails with the following error message?

The CertificateThumbprint property must be empty when the SSL configuration is shared with another service. This error occurs when the Internet Information Server (IIS) is already installed and configured for HTTPS communication.

Details about coexistence of IIS and WinRM is available at In this case, use the following command to create a HTTPS Listener with the CertificateThumbprint empty:

winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="<host_name>";CertificateThumbprint=""}

2.4 What is the firewall-related configuration that needs to be done for WinRM?

With firewall turned ON, WinRM must be added to the firewall exclusion list to allow TCP port 443 for HTTPS traffic. 

3. Events/Alerts

3.1 Can Server Administrator send e-mails when there is a problem?

No, Server Administrator is not designed to send e-mails when there is a problem. You can use Dell OpenManage Essentials to monitor these Dell systems and configure the alert action.

3.2 What are all the protocols Server Administrator supports?

The protocols that Server Administrator supports are:

  • Simple Network Management Protocol (SNMP) - Server and Storage information
  • Windows Management Instrumentation (WMI) - only Server information

3.3 Which version of SNMP is supported?

SNMP v1/v2

3.4 Does Server Administrator support SNMPv3?


3.5 Does Server Administrator support WMI Events?


3.6 Does Server Administrator support WSMAN?

WSMAN is used by the Distributed Web Server of Server Administrator to connect to the instrumentation service on the remote system. This WSMAN interface is internal to the Server Administrator components and cannot be used by any third party consoles to fetch hardware information using WSMAN.

3.7 How can I receive Server Administrator (Server/Storage and hardware alerts) in my Dell OpenManage Essentials (OME) console?

You have to ensure SNMP trap service is running on the system where Server Administrator is installed and  the server IP of OME is set as a SNMP trap destination.

4. Management Consoles (Dell OpenManage Essentials)

4.1 Is SNMP required for Dell OpenManage Essentials (OME) discovery, inventory, and software updates on PowerEdge systems? Can Common Information Model (CIM)/WMI be used by itself for discovery, inventory, and updates or is SNMP required?

OME with Remote Linux systems:

SNMP is required on systems running the  Linux operating system for discovery, status polling, and inventory.

Software updates are done through an SSH session and secure FTP. You will require the system credentials for Software updates. Refer for more details.

OME with Remote Windows systems:

For servers (systems running the Windows Server operating systems), the system may be configured with either or both of SNMP and CIM for discovery by OME. 

5. Login, Active-Directory and Authentication


5.1 What are the tasks that need to be performed after adding a VMware ESX 4.0 U3 or ESX 4.1 U2 operating system to the Active Directory domain?

After adding a VMware ESX 4.0 U3 and ESX 4.1 U2 operating system to the Active Directory domain, an Active Directory user must:

  1. Log in to Server Administrator on the system running the VMware ESX 4.0 U3 and ESX 4.1 U2 operating system and restart the DSM SA Connection Service.
  2. Log in to the Remote Node while using the VMware ESX 4.0 U3 and ESX 4.1 U2 operating system as a Remote Enablement Agent. Wait for approximately 5 minutes for the sfcbd process to add the permission to the new user.

5.2 Does an Underscore character in the domain name cause Server Administrator login issues?

Yes, an underscore character in the domain name is invalid. All other special characters (except the hyphen) are invalid too. Use case-sensitive alphabets and numerals only.

5.3 How does selecting/deselecting Active Directory on the login page of Server Administrator impact privilege levels?

If you do not select the Active Directory check box, you will only have access that is configured in the Microsoft Active Directory. You cannot log in using the Extended Schema Solution in Microsoft Active Directory. This solution enables you to provide access to Server Administrator; allowing you to add/control Server Administrator users and privileges to existing users in your Active Directory software. For more information, see Using Microsoft Active Directory in the Server Administrator Installation Guide.

5.4 What actions do I follow while performing Kerberos authentication and trying to login from Web server?

For authentication, the contents of the files /etc/pam.d/openwsman and /etc/pam.d/sfcb, on the Managed Node, must be replaced with:

For 32-bit:

auth required service=system-auth auth required /lib/security/ account required service=system-auth

For 64-bit:

auth required service=system-auth auth required /lib64/security/ account required service=system-auth

6. ESXi

6.1 Why does ESXi 4.x (4.0 U3) and ESXi 5.x host rebooting functionality fail from Server Administrator?

This issue is due to VMware stand-alone license (SAL) key. For more information, see the knowledge base article at


7. Storage Management

7.1 Why Is A Rebuild Not Working?

For more information, refer the Rebuild Does Not Work section in the Server Administrator Storage Management User’s Guide.

 7.2 How to avoid removing the wrong disk?

You can avoid removing the wrong disk by blinking the LED display on the disk that you want to remove. For information on blinking the LED display, refer to the Server Administrator Storage Management User’s Guide.

 7.3 How can I safely remove or replace a physical disk?

The following sections provide information related to safely removing a healthy physical disk:

For disks that reside in an enclosure, use the Preparing To Remove A PCIeSSD task to locate the disk within the enclosure and deactivate it prior to removal.

For physical disks included in a virtual disk, use the Offline task to deactivate the disk prior to removal. If you need help locating the disk within the enclosure, you can blink LED on the disk.

7.4 How Do I recover from removing the wrong physical disk?

Refer to the Recovering From Removing The Wrong Physical Disk section in the Storage Administrator User’s Guide.

7.5 How do I identify the controller firmware version that is installed?

The properties information of the controller displays the firmware version that is installed on the controller. To view the firmware version of all controllers:

  1. Select the Storage object in the tree view.
  2. Click Information/Configuration sub-tab. The Firmware version column on the Information/Configuration sub-tab displays the firmware version for all controllers attached to the system.

7.6 How do I know which controllers I have in the server?

Each controller attached to the system is displayed under the Storage object in the tree view.

In addition, the Storage Health and Information/Configuration pages display information for each controller. To identify the controllers attached to the system:

  1. Select the Storage tree view object. The Health page displays the name and status for each controller attached to the system.
  2. Click Information/Configuration subtab to display more information for each controller.

To display more information about a particular controller including its tasks, click the controller name in the Name column on the Information/Configuration sub-tab. This action displays the controller's Information/Configuration sub-tab. The Information/Configuration sub-tab displays information about the controller's components and enables you to execute the controller tasks.

7.7 How do I turn off an alarm?

Some storage components have alarms to indicate error conditions. For more information on turning off the alarm, see following sections in Storage Management user guide:

  • Turning Off The Controller Alarm
  • Disabling The Controller Alarm
  • Disabling The Enclosure Alarm

7.8 Which RAID level is best for me?

For more information, see Choosing RAID Levels and Concatenation and Comparing RAID Level and Concatenation Performance sections in the Server Administrator Storage Management User’s Guide.

7.9 How to Add HDD to an existing RAID?

For more information, see Reconfiguring Or Migrating Virtual Disks, under Virtual Disks section in the Server Administrator Storage Management User’s Guide.

7.10 How to create RAID using OMSA?

For more information, see Creating Virtual Disks, under Virtual Disks in to the Server Administrator Storage Management User’s Guide