Dell OMSA - Linux Servers

Dell EMC’s OpenManage Server Administrator (OMSA) application is a free tool which Dell provide, enabling Dell PowerEdge users to have greater control over their server remotely. OMSA is downloadable through Dell’s support website and is compatible with most Operating Systems and with most PowerEdge chassis. OMSA compatibility is based on the Dell PowerEdge server’s generation and the version of Linux installed onto the server. See below to find what generation of Dell PowerEdge servers Vs. what Operating System OMSA supports.

Compatibility with OS	Compatible with Dell PE 11th Gen (R_10)	Compatible with Dell PE 12th Gen (R_20)	Compatible with Dell PE 13th Gen (R_30)
CentOS 6	Yes	Yes	Yes
CentOS 7	Yes (No*)	Yes	Yes
Ubuntu 14	Yes	Yes	Yes
Ubuntu 16	Yes	Yes	Yes
Debian 7	Yes	Yes	Yes
Debian 8	Yes	Yes	Yes
Debian 9	Not Supported**	Not Supported**	Not Supported**
* OMSA is not compatible with CentOS 7 on a Dell PE R210 II chassis.
** There is no officially supported version of OMSA for Debian 9. However, using the guide below, you are able to download the Debian 8 version of OMSA onto a Debian 9 OS. Please note, compatibility issues may arise from doing this. Also, iomart (or any company within the iomart group) are not responsible for any issues caused by performing this action, and Dell EMC would advise not to perform this task.

Please note that OpenManage Server Administrator is a free piece of software supplied by Dell EMC. As such, iomart (and any company within the iomart group; including RapidSwitch and Redstation) are not responsible for this software, nor are they responsible for any effects downloading, installing or using this software may have on your platform. We can only advise you to use OMSA and provide you with advice on how to do so; the choice to download, install and use the software must be your own. Also, as a managed infrastructure provider, we do not officially support OMSA; as such we will not be able to install, use or configure this software.

How you install OMSA onto a Linux server depends on the version of Linux you are using. Please see below how to install OSMA for each version of Linux (which we install and which is supported by OMSA).

Downloading and installing OpenManage Server Administrator (OMSA) onto a CentOS 6 or CentOS 7 server involves issuing commands which download the necessary files, start and then enable the OMSA services.

First, you need to log into the server’s root account. Once you are logged in, to install OMSA onto your CentOS server, please issue the following commands one after the other, waiting for each task to complete before proceeding with the next command:

Command 1
Command Description	Issue the following command to download and install the Dell Repository to your server.
Command	wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash
Image of Command being Run
Image of a Successful Result of Command
Command 2
Command Description	Issue the following command to install the base utilities and storage
Command	yum install srvadmin-base srvadmin-storageservices -y
Image of Command being Run
Image of a Successful Result of Command
Command 3
Command Description	Issue the following command to start the OMSA service
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh start
Image of Command being Run
Image of a Successful Result of Command
Command 4
Command Description	Run this command to enable the OMSA services
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh enable
Image of Command being Run
Image of a Successful Result of Command

Dell EMC’s OpenManage System will now be installed on your server. You can then use this software to manage and monitor the hardware within this server. Before you can access and use OMSA, you will have to logout of the server and close any SSH shell, and then re-login.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

Downloading OpenManage Server Administrator (OMSA) onto a server with Ubuntu 14 installed involves issuing commands which download the necessary repository files and keys, install the required utilities, then start and enable the OMSA services.

First, you need to log into the server’s root account. Once you are logged in, to install OMSA onto your Ubuntu 14 server, please issue the following commands one after the after, waiting for each task to complete before proceeding with the next command:

Command 1
Command Description	Issue this command to download and create the repository file
Command	echo 'deb http://linux.dell.com/repo/community/ubuntu trusty openmanage' > /etc/apt/sources.list.d/linux.dell.com.sources.list (Please note that each command is one line)
Image of Command being Run
Image of a Successful Result of Command
Command 2
Command Description	Issue this command to download the repository key
Command	gpg --keyserver hkps.pool.sks-keyservers.net --recv-key 1285491434D8786F
Image of Command being Run
Image of a Successful Result of Command
Command 3
Command Description	Run this command to import the key into APT
Command	gpg -a --export 1285491434D8786F | apt-key add -
Image of Command being Run
Image of a Successful Result of Command
Command 4
Command Description	Run this command to let the APT know there’s a new repository.
Command	apt update -y
Image of Command being Run
Image of a Successful Result of Command
Command 5
Command Description	Issue this command to install the required utilities
Command	apt install srvadmin-base srvadmin-omcommon srvadmin-storageservices -y
Image of Command being Run
Image of a Successful Result of Command
Command 6
Command Description	Issue the following command to start the OMSA service
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh start
Image of Command being Run
Image of a Successful Result of Command
Command 7
Command Description	Run the following command to enable the OMSA service
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh enable
Image of Command being Run
Image of a Successful Result of Command

Dell EMC’s OpenManage System will now be installed on your server. You can then use this software to manage and monitor the hardware within this server. Before you can access and use OMSA, you will have to logout of the server and close any SSH shell, and then re-login.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

Downloading OpenManage Server Administrator (OMSA) onto a server with Ubuntu 16 installed involves issuing commands which download the necessary repository files and keys, installing the required utilities, then starting and enabling the OMSA services.

First, you need to log into the server’s root account (or an account that is a member of sudoers). Once you are logged in, to install OMSA onto your Ubuntu 16 server, please issue the following commands one after the other, waiting for each task to complete:

Command 1
Command Description	Issue this command to download and create the repository file.
Command	echo 'deb http://linux.dell.com/repo/community/ubuntu xenial openmanage/840' > /etc/apt/sources.list.d/linux.dell.com.sources.list (please note that each command is one line)
Image of Command being Run
Image of a Successful Result of Command
Command 2
Command Description	Issue this command to download the repository key.
Command	gpg --keyserver hkps.pool.sks-keyservers.net --recv-key 1285491434D8786F
Image of Command being Run
Image of a Successful Result of Command
Command 3
Command Description	Run this command to import the key into APT.
Command	gpg -a --export 1285491434D8786F | apt-key add -
Image of Command being Run
Image of a Successful Result of Command
Command 4
Command Description	Run this coomand to let the APT kknow there’s a new repository.
Command	apt update -y
Image of Command being Run
Image of a Successful Result of Command
Command 5
Command Description	Issue this command to install the required utilities.
Command	apt install srvadmin-base srvadmin-omcommon srvadmin-storageservices -y
Image of Command being Run
Image of a Successful Result of Command
Command 6
Command Description	Issue the following command to start the OMSA service.
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh start
Image of Command being Run
Image of a Successful Result of Command
Command 7
Command Description	Run the following command to enable the OMSA service.
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh enable
Image of Command being Run
Image of a Successful Result of Command

Dell EMC’s OpenManage System will now be installed on your server. You can then use this software to manage and monitor the hardware within this server. Before you can access and use OMSA, you will have to logout of the server and close any SSH shell, and then re-login.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

Downloading OpenManage Server Administrator (OMSA) onto a server with Debian 7 installed, involves issue commands which download the necessary repository files and keys, installing the required utilities, then starting and enabling the OMSA services.

First, you need to log into the server’s root account. Once you are logged in, to install OMSA onto your Debian 7 server, please issue the following commands one after the after, waiting for each task to complete:

Command 1
Command Description	Issue this command to download and create the repository file.
Command	echo 'deb http://linux.dell.com/repo/community/debian wheezy openmanage' > /etc/apt/sources.list.d/linux.dell.com.sources.list (each command is one line)
Image of Command being Run
Image of a Successful Result of Command
Command 2
Command Description	Issue this command to download the repository key.
Command	gpg --keyserver hkps.pool.sks-keyservers.net --recv-key 1285491434D8786F
Image of Command being Run
Image of a Successful Result of Command
Command 3
Command Description	Run this command to import the key into APT.
Command	gpg -a --export 1285491434D8786F | apt-key add -
Image of Command being Run
Image of a Successful Result of Command
Command 4
Command Description	Run this coomand to let the APT know there’s a new repository.
Command	apt-get update -y
Image of Command being Run
Image of a Successful Result of Command
Command 5
Command Description	Issue this command to install the required utilities.
Command	apt-get install srvadmin-base srvadmin-omcommon srvadmin-storageservices –y
Image of Command being Run
Image of a Successful Result of Command
Command 6
Command Description	Issue the following command to start the OMSA service.
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh start
Image of Command being Run
Image of a Successful Result of Command
Command 7
Command Description	Run the following command to enable the OMSA service.
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh enable
Image of Command being Run
Image of a Successful Result of Command

Dell EMC’s OpenManage System will now be installed on your server. You can then use this software to manage and monitor the hardware within this server. Before you can access and use OMSA, you will have to logout of the server and close any SSH shell, and then re-login.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

Downloading OpenManage Server Administrator (OMSA) onto a server with Debian 8 installed, involves issue commands which download the necessary repository files and keys, install the required utilities, then start and enable the OMSA services.

First, you need to log into the server’s root account. Once you are logged in, to install OMSA onto your Debian 8 server, please issue the following commands one after the after, waiting for each task to complete before proceeding:

Command 1
Command Description	Issue this command to download and create the repository file.
Command	echo 'deb http://linux.dell.com/repo/community/debian jessie openmanage' > /etc/apt/sources.list.d/linux.dell.com.sources.list (Each command is one line)
Image of Command being Run
Image of a Successful Result of Command
Command 2
Command Description	Issue this command to download the repository key.
Command	gpg --keyserver hkps.pool.sks-keyservers.net --recv-key 1285491434D8786F
Image of Command being Run
Image of a Successful Result of Command
Command 3
Command Description	Run this command to import the key into APT.
Command	gpg -a --export 1285491434D8786F | apt-key add -
Image of Command being Run
Image of a Successful Result of Command
Command 4
Command Description	Run this coomand to let the APT kknow there’s a new repository.
Command	apt-get update -y
Image of Command being Run
Image of a Successful Result of Command
Command 5
Command Description	Issue this command to install the required utilities.
Command	apt-get install srvadmin-base srvadmin-omcommon srvadmin-storageservices -y
Image of Command being Run
Image of a Successful Result of Command
Command 6
Command Description	Issue the following command to start the OMSA service.
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh start
Image of Command being Run
Image of a Successful Result of Command
Command 7
Command Description	Run the following command to enable the OMSA service.
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh enable
Image of Command being Run
Image of a Successful Result of Command

Dell EMC’s OpenManage System will now be installed on your server. You can then use this software to manage and monitor the hardware within this server. Before you can access and use OMSA, you will have to logout of the server and close any SSH shell, and then re-login.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

There is no officially supported version of OpenManage Server Administrator (OMSA) for Debian 9. However, using the guide below, you are able to download the Debian 8 version of OMSA onto a Debian 9 OS.

Please note that there may be compatibility issues and iomart (and any company within the iomart group) are not responsible for any issues performing this action may cause. Also, please note that Dell EMC would advise not to install this version of OMSA onto a Debian 9 server.

If you do with to install OMSA onto a Debian 9 server, using a Debian 8 version of the software, see below how to perform this task.

Downloading OpenManage Server Administrator (OMSA) onto a server with Debian 9 installed, involves issue commands which download the necessary repository files and keys, install the required utilities, then start and enable the OMSA services.

First, you need to log into the server’s root account. Once you are logged in, to install OMSA onto your Debian 9 server, please issue the following commands one after the after, waiting for each task to complete before proceeding with the next command:

Command 1
Command Description	The following four commands are to configure your server so that the Debian 8 version of OMSA can be installed onto Debian 9. Please note that there may be compatibility issues and iomart (and any company within the iomart group) are not responsible for any issues performing this action may cause. Also, please note that Dell EMC would advise not to do this.
Command	wget -q -O /tmp/libssl1.0.0_1.0.1t-1+deb8u9_amd64.deb (please note, this and all commands are one continuous line)
Image of Command being Run
Image of a Successful Result of Command
Command 2
Command	dpkg -i /tmp/libssl1.0.0_1.0.1t-1+deb8u9_amd64.deb
Image of Command being Run
Image of a Successful Result of Command
Command 3
Command	apt-get update
Image of Command being Run
Image of a Successful Result of Command
Command 4
Command	apt-get install dirmngr* -y
Image of Command being Run
Image of a Successful Result of Command
Command 5
Command Description	Issue the following command to create the repository file, using the Jessie repo, because the Strech one is not compatible.
Command	echo 'deb http://linux.dell.com/repo/community/debian jessie openmanage' > /etc/apt/sources.list.d/linux.dell.com.sources.list (please note, this and all commands are one continuous line)
Image of Command being Run
Image of a Successful Result of Command
Command 6
Command Description	Run this command to download the repostiroy key.
Command	gpg --keyserver hkps.pool.sks-keyservers.net --recv-key 1285491434D8786F
Image of Command being Run
Image of a Successful Result of Command
Command 7
Command Description	Run this comand to import the key into APT.
Command	gpg -a --export 1285491434D8786F | apt-key add -
Image of Command being Run
Image of a Successful Result of Command
Command 8
Command Description	Run the bellow command to let APT know there is a new repository.
Command	apt-get update -y
Image of Command being Run
Image of a Successful Result of Command
Command 9
Command Description	Issue the following command to install the required utilities.
Command	apt-get install srvadmin-base srvadmin-omcommon srvadmin-storageservices –y
Image of Command being Run
Image of a Successful Result of Command
Command 10
Command Description	Issue the below command to start the OMSA service.
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh start
Image of Command being Run
Image of a Successful Result of Command
Command 11
Command Description	Now run this command to enable the OMSA service.
Command	/opt/dell/srvadmin/sbin/srvadmin-services.sh enable
Image of Command being Run
Image of a Successful Result of Command

Dell EMC’s OpenManage System will now be installed on your server. You can then use this software to manage and monitor the hardware within this server. Before you can access and use OMSA, you will have to logout of the server and close any SSH shell, and then re-login.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

When Dell OpenManage Server Administrator (OMSA) is installed on a Linux server, the OMSA product is accessible through the server’s operating system, through the command line interface.

Simply access your server remotely in the normal manor and log into your server’s root account. You can then issue a command through the server’s operating system to find what information you need. Some example of commands can be found through our FAQ section on MyServers. Additional commands and information can be found online through Dell EMC’s and Linux’s support websites, and through community pages.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

One of the main features of Dell’s OpenManage Server Administrator tool (OMSA) is that it allows you to check for any errors that may have occurred with the server’s hardware and allows you to check the current status of several components. Due to the nature of hardware, we recommend checking the status of the server’s hardware on a regular basis.

To check the current state of the server and to check the error log, you should run the following command:

Command 1
Command Description	The following command shows the current status of the server and displays the server’s alert log, as monitored by OMSA.
Command	omreport system alertlog
Image of Command being Run
Image of a Successful Result of Command

The above command will show the log of all errors with the server hardware monitored by OMSA. You can use this information to see if there are currently any errors with the server that may need investigation. An example of an error would be the following:

As you can see from this example, there is currently an error with the storage of this server. The severity of the error is also shown. There are four statuses within OpenManage:

Status	Description
OK	The component is working as normal and is healthy.
Non-Critical Warning	These errors normally indicate a problem which is not service impacting, but still require prompt attention.
Failed / Critical Warning	The component has either failed or has a critical warning. If a critical error occurs, there error must be addressed as soon as possible.
Unknown Status	The status of this component is unknown.

To find out more specific details about errors relating to hardware and to check the current status of specific pieces of hardware, you need to run the specific OMSA command in the server’s root account’s command line interface.

Some examples of commands can be found below; additional commands and information can be found online through Dell EMC’s and Linux’s support websites, and through community pages.

When storage is mentioned in Dell EMC OpenManage (OMSA), this is referring to the RAID controller (if a RAID controller is present), all the physical drives, and all the virtual drives (or RAID arrays). When an error occurs related to storage, this would normally mean that there is an error with a physical drive, which has then effected the RAID array it is configured within. This is for the majority of cases; however, there can be other issues related to storage, which can cause errors.

To check for errors relating to storage, run the following command:

Command 1
Command Description	The following command shows the current status of the server and displays the server’s alert log, as monitored by OMSA.
Command	omreport system alertlog
Image of Command being Run
Image of a Successful Result of Command

This command will list all the errors with the server; including errors relating to storage. In my example, you can see that there are several errors relating to storage; all caused by Physical Disk 0:1:3 being missing/removed.

You can use the information in the log to identify which Controller, Connector, Virtual Disk (VD) and Physical Disk (PD) the errors relate to.

With this information, you can find out more details about the physical drive that has failed. Run the following command, inputting the controller number from your error:

Command 2
Command Description	The following command lists all the Physical Disks attached to the controller you specify; and all the Physical Disk’s details.
Command	omreport storage pdisk controller=[Insert Controller Number]
Image of Command being Run
Image of a Successful Result of Command

Here you will now be able to see a list of Physical Disks attached to this controller. You will also be able to see any errors and the state of each Physical Disk.

At this point, it is good to know what the configuration of your server should be, especially related to RAID arrays and disk configuration. As an example, the server below is meant to have 4x Physical Disks attached to the RAID controller, however, only 3 are listed. This is normally caused by a drive completely failing; causing it to disappear from the monitoring. The monitoring may not show this, but by comparing your knowledge of the server’s configuration to what components are currently listed, you can see a drive is missing.

These details can be used to identify any drives that may have an error, may be fault, or may be missing from OMSA’s monitoring; and can help locate a drive for it to be replaced.

You can use this information to decide what you wish to do next. If you do encounter any drives with an error and wish for this drive to be replaced, please see the section on having a disk replaced using OMSA for more details.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

Due to the nature of hardware, it is good practice to regularly check the status of your server’s hardware, and specifically to check the status of the storage within the server for any errors. Dell EMC’s OpenManage Server Administrator (OMSA) application allows you to check the current status of each RAID array (or Virtual Disk) configured on your server and the status of each physical drive.

First, you should check the status of each Virtual Disk (VD). To do this, run the following commands:

Command 1
Command Description	Run the following command to list all the Virtual Disks configured within this server. You also will be presented with the VDs’ details and statuses.
Command	omreport storage vdisk
Image of Command being Run
Image of a Successful Result of Command

You will now be presented with a list of Virtual Disks configured within the server, their details, their current status and their ID number. In my example below, you can see I have one RAID array which is degraded.

You should now know if there is an error with any of the RAID arrays (or VDs) within the chassis. If there is an error with an array, this is normally caused by a Physical Disk (PD) within this array also having an error, or failing. However, other problems can occur, which can cause an error with a Virtual Disk.

If there is an error with a Virtual Disk or not, you should also check the status of all the Physical Disks within the server. To do this, you first need to identify how many RAID controllers are within this server and the ID number of these RAID controllers. Once you have identified this information, you can use the RAID controllers’ ID number(s) to list all the physical disks connected to these controllers.

Run the following two commands; using the ID number(s) from Command 2 below, to fill in the blank in command 3. Run command 3 once for each controller:

Command 2
Command Description	The following command lists all the RAID controllers within the chassis. You need this information (identified in my results example, with a red box) for command 3.
Command	omreport storage controller
Image of Command being Run
Image of a Successful Result of Command
Command 3
Command Description	Run the following command, using the controller’s ID number from Command 2, to list all the Physical Disks within this server. You will also be able to see their details and statuses.
Command	omreport storage pdisk controller=[insert controller number]
Image of Command being Run
Image of a Successful Result of Command

Repeat Command 3 for every controller found in the results of Command 2.

In my example above, and with most of our dedicated servers we provide, there is normally only one controller with an ID of 0; however, some servers maybe configured with more than one. Once you have run the above two commands (for every controller within the chassis), you will have a clear idea of the status of every physical disk within the chassis, and you should be able to identify if any drives currently have an error. In my example below, you can see drive 0:1:3 currently has a critical error, and its state is removed.

At this point, it is good to know what the configuration of your server should be, especially related to RAID arrays and disk configuration. If a drive completely fails, it can sometimes not show in OMSA at all, opposed to showing as having an error. As an example, the server below is meant to have 4x Physical Disks attached to the RAID controller, however, only 3 are listed. This is normally caused by a drive completely failing; causing it to disappear from the monitoring. The monitoring may not show this, but by comparing your knowledge of the server’s configuration to what components are currently listed, you can see a drive is missing.

Once you have a list of each physical drives configured within the server, you should be able to identify any drives with any errors or if any drives are missing from the OMSA monitoring. You can now use this information to inform your decision on what to do next.

If you wish to have a drive replaced, please see the section on our FAQ on how to go about getting a technician to perform this action, using the information form OMSA. If you do wish for a drive to be replaced, you will need to provide the details found on the physical drive’s information page, as shown in the examples above. This will aid the on-site technician in identifying the faulty drive, during the drive swap process.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

Due to the nature of hardware, it is good practice to check the status of your server’s hardware on a regular basis, to check for any errors or failed components. Dell EMC’s OpenManage Server Administrator (OMSA) application allows you to check the current status of several sub-components of the server.

To check for any errors, simply run the command to show the error log, as shown below:

Command 1
Command Description	The following command shows the current status of the server and sow the server’s alert log, as monitored by OMSA.
Command	omreport system alertlog
Image of Command being Run
Image of a Successful Result of Command

This will provide you with a list of any errors related to hardware monitored by OMSA. You can use this to see if any component monitored by OMSA currently has an error. If you do encounter any errors, you should use OMSA’s commands to find out more details about the component and its error. Please see below how to do this for some of the main components. For other components, commands can be found online through Dell’s and Linux’s support websites.

You can also run commands to check the current status and configuration of specific pieces of hardware and to look at any errors in more detail. It is good practice to do this on a regular basis, as running the above command may not list a completely failed piece of hardware; so you should check each main hardware type to identify if any piece of hardware has completely failed and is missing. There are specific commands for different pieces of hardware monitored by OMSA. See below for examples of the main components monitored by OMSA and the commands that are used to check their status (excluding components related to storage).

Memory

The memory component refers to all the RAM within the chassis. You can use OMSA to check how many RAM sticks are configured within the server, their details, their status and what DIMM slot they are using on the server’s motherboard.

To check on the status of the memory within the chassis, you need to run the following command:

RAM - Command 1
Command Description	Run the following command to bring up a list of what RAM stick are configured within the chassis, their status, and their details.
Command	omreport chassis memory
Image of Command being Run
Image of a Successful Result of Command

You can use the results of this command to check the status of your system’s memory. If a stick of RAM ever does become faulty, you will be able to find the details of the faulty RAM here which our technicians would need to replace the faulty stick. You can also use this page to identify if a RAM stick has become completely failed and is now missing from OMSA.

If you wish for a faulty stick of RAM to be replaced, please let us know all the details found through OMSA, so we can easily identify the faulty stick of RAM. If possible, a screenshot of this page would also be helpful. Please see the section on getting faulty RAM replaced using OMSA for more details.

Processors

You can use OMSA to list the processors (or CPUs) configured within your server. To find out more details about the processors in your server and their current status, run the following command.

Processor (CPU) - Command 1
Command Description	Run the following command to bring up a list of what Processors are configured within the chassis, their status and their details.
Command	omreport chassis processors
Image of Command being Run
Image of a Successful Result of Command

If an error does ever occur with a processor within a server, please feel free to get in touch and we will be happy to investigate this for you. If there is more than one processer installed in your server, please provide us with the Connector Name of the faulty CPU, so our technicians can easily identify which processor needs replacing. For more details on getting a faulty CPU replaced, please see the section on getting a CPU replaced using OMSA.

Network

You can use OMSA to lists all the network ports attached to the server. You can also see the NIC interface’s index, name, details and status. To find these details, run the following command:

Network - Command 1
Command Description	Run the following command to bring up a list of network ports within the chassis.
Command	omreport chassis nics
Image of Command being Run
Image of a Successful Result of Command

You can use the above information to identify if any of the network ports have encounter an error.

The above commands, provided by OMSA, allows you to check the status of several components and to check for errors. This information allows you decide on what action you wish to be taken on the server and allows you to effectively troubleshoot any hardware related issues.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

If you do encounter a physical drive with an error and you wish for this drive to be replaced, you will need to provide as much of the following information about the failed drive as possible to our support team, to allow our technicians to correctly identify which drive needs replacing:

1. Serial number

2. Type of drive (e.g. SSD, SATA HDD, SAS HDD, etc.)

3. Capacity

4. Product ID

5. Physical Drive Bay Number

This information will aid the technician in locating the failed drive and swapping it with the correct replacement drive. You can use Dell EMC’s OpenManage Server Administrator (OMSA) application to find this information.

To find this information, you must first be logged into the server’s root account, then have identify a drive with an error/that has failed. Please see the sections on accessing OMSA and then the section on locating a drive with an error, if you are un-sure how to do this. To locate a drive with an error/which has failed, you should have run the following command:

Command 1
Command Description	The following command lists all the Physical Disks attached to the controller you specify; and all the Physical Disk’s details. Within the command, you must insert the controller number, for the controller you wish to check the status of the physical disks for. You should be able to find this number from the resulting message of commands shown in the identifying storage errors section of the FAQ: omreport storage controller.
Command	omreport storage pdisk controller=[Insert Controller Number]
Image of Command being Run
Image of a Successful Result of Command

Once you have found the physical drive with the error and run the above command, you should be able to identify details about the drive with the error, including the details required by our technicians to locate the drive. See the image below as an example of how to find the necessary information.

If you wish for the drive to be replaced, please supply all the necessary information in a support ticket, requesting for the faulty drive to be replaced, and we will be happy to help. You can also supply a screenshot of the results of the above command.

To work out the drive’s physical bay number, you can use the ID of this drive in conjunction with all the other physical disks’ ID numbers. After running the command above you will be able to see the ID number of all the Physical Disks attached to this controller, which you can use to identify the bay number of the faulty drive. Using the example below, the drive I wish to be replaced is disk 0:1:3, the first drive in the server is disk 0:1:0 and the last drive is 0:1:3. When asking the technicians to replace this disk, simply inform them of the failed drive’s ID number (e.g. 0:1:3) and inform them of the drive’s ID counting format (e.g. 0:1:0 to 0:1:3), as they can use this to locate the physical disk.

In addition to providing the information above, OMSA on most servers will also allow you to set the drive to ‘blink’, which will also help our technician locate the appropriate drive. To get the drive to blink, run the following command. You will need to know the controller’s ID number, for the controller the drive is attached to, and the drive’s ID number, for the drive you wish to blink.

Command 1
Command Description	The following command sets the LED on the drive bay, for the inputted drive, to blink. You need to input the controller ID number and the Physical Disk ID number for the drive you wish to blink.
Command	omconfig storage pdisk action=blink controller=[Insert Controller ID#] pdisk=[Insert PD ID#]
Image of Command being Run
Image of a Successful Result of Command

If you have been able to set the drive to blink, please inform the technicians in the support ticket that you have done so. If you cannot set the drive bay to blink, this is most likely not a hot-swappable chassis, meaning this is not required.

When the technicians have completed any drive swap, you should run the following command to set the drive to ‘un-blink’, to stop the drive bay blinking. It is important to do so, to make sure this drive bay isn’t still blinking while any further drive changes at a later date are taking place, as this may lead to some confusion.

Command 1
Command Description	The following command sets the LED on the drive bay, for the inputted drive, to stop blinking. You need to input the controller ID number and the Physical Disk ID number for the drive you wish to blink.
Command	omconfig storage pdisk action=unblink controller=[Insert Controller ID#] pdisk=[Insert PD ID#]
Image of Command being Run
Image of a Successful Result of Command

Once you provide all this information in a support ticket and set the drive bay to blink (if possible), the local technicians will be able to look into swapping the failed drive.

If the drive is missing from the OMSA monitoring, opposed to having an error, then you will not be able to provide the necessary information listed above to get the drive replaced, nor set the drive bay to blink. Instead, you can provide the information on all the drives that are still present on OMSA and their details in a support ticket, so that by process of elimination the technicians can replace the missing drive.

Once you have provided all the information from the drives that are still present, the technicians should be able to identify the missing drive and replace it.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

If you do encounter an error related to the server’s memory (RAM) and you wish for a RAM stick to be replaced, you will need to provide as much of the following information as possible to our support team, to allow the technicians to correctly identify which RAM stick needs replacing:

1. The failed RAM stick’s DIMM slot number (i.e. the Connector Name)

2. The failed RAM stick’s size

3. The failed RAM stick’s type

You can use Dell EMC’s OpenManage Server Administrator (OMSA) application to find this information. You must first be logged into the server’s root account and have located the RAM stick with the error. Please see the sections on accessing OMSA if you are unsure on how to access it. To find the details about the memory configured in the server, run the following command:

Command 1
Command Description	Run the following command to bring up a list of what RAM sticks are configured within the chassis, their status and their details.
Command	omreport chassis memory
Image of Command being Run
Image of a Successful Result of Command

Here you will be able to see a list of the RAM sticks attached to the motherboard, their statuses, their connector names, their type and their size. If a stick of RAM appears with an error and you wish for it to be replaced, you will need to supply all the information about this stick of RAM shown in the results, in a support ticket, so that the technician can identify the failed DIMM and replace it. You can also supply a screenshot of this page.

Occasionally, if a RAM stick completely fails, it may not appear on this page with an error, but might actually be missing from this page all together. As an example, the server below is meant to be configured with 4x 16GB RAM sticks (or 64Gb of memory in total), but only 3x 16GB RAM sticks are appearing. If this is the case, it is quite likely that a stick has completely failed and needs replacing. If this has happened you will not be able to find the required information above on the failed RAM stick to get it replaced. Instead, you can provide the information on all the other RAM sticks that are still present, so the technicians can locate the failed DIMM through a process of elimination. You can also supply a screenshot of this page.

Once you have provided all the above information in a support ticket, the technicians should be able to locate and replace the faulty RAM stick.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.

If you do encounter an error related with a server’s CPU (Processor) and you wish for it to be replaced, and if there is more than one CPU in this server, you will need to provide as much of the following information as possible about the faulty CPU, to allow our technicians to correctly identify which CPU needs replacing:

1. The failed CPU’s slot number (i.e. the Connector Name)

2. The failed CPU’s Make and Model (i.e. Processor Brand information)

If your server only has one CPU installed, we do not require this information to locate and replace the CPU. Please feel free to raise a support ticket and we will be happy to help.

If you do have more than one CPU in the server, this information will aid the technician in locating the failed CPU and swapping it with the correct replacement CPU. You can use Dell EMC’s OpenManage Server Administrator (OMSA) application to find this information.

To find this information, you must first be logged into the server’s root account and you must have located the CPU with the error. Please see the sections on accessing OMSA if you are unsure on how to access OMSA. To find the details about the processors configured in the server, run the following command:

Processor (CPU) - Command 1
Command Description	Run the following command to bring up a list of what Processors are configured within the chassis, their status and their details.
Command	omreport chassis processors
Image of Command being Run
Image of a Successful Result of Command

Here you will be able to see a list of the CPUs installed in the server, their make and model, their connector name and their specifications. If a CPU appears with an error and you wish for this CPU to be replaced, you will need to supply all the information about this CPU that appears in the results from this command in a support ticket, so that our technician can identify the failed processor and replace it. You can also supply a screenshot of this page.

Occasionally, if a CPU completely fails, it may not appear on this page with an error, but might actually be missing from this page all together. If this is the case, then you will not be able to find the information above on the failed CPU, to get it replaced. Instead, you can provide the information on all the CPUs that are present, so the technicians can locate the failed processor through a process of elimination. You can also supply a screenshot of this page.

Once you have provided all the above information in a support ticket, the technicians should be able to locate and replace the faulty CPU.

If you have any further questions about OMSA, please look through our FAQ section. If our FAQ page does not have the answer, please feel free to raise a support ticket, and we will be happy to help.