How to use iDRAC to Exabytes ID servers

This part will explain how to use iDRAC to all our Exabytes ID servers. Basically all our data centre Exabytes ID located on Cyber 2 Tower 2nd floor, under NEX data centre. Operated by CBN Internet Provider.

We use iDRAC whenever :

• Server got down and need to troubleshoot quickly.
• Reinstall process of OS server
• Monitor certain server remotely from office
• etc

This iDRAC only can be accessed by using Exabytes VPN and should connect to certain controller server to remote.

Search which server that need to be remote first

We assume the server is down and need to be check asap. ie. siabuh server. How we find which server and which rack?

Go to racktable and find the server name by using search function.

Then the search result will showing these images below. Click on DS – siabuh.id to know which Rack this server is.

After clicked, it is showing Rack number and which rows. Now what we have to remember is NF3-01-03 and row 13. You will see some different colour as highlight from racktable index.

Click the server to know which iDRAC IP address we should connect to. And which password of iDRAC we should enter. You can follow this page about reference which server that can be use for iDRAC controller.

Now we know that NF3-01-03 is the rack location and it is under row 13. Now refer to Johan’s email (IDRAC login information)about credential user that need to be used. Refer to this below, we shall use Shield03 server.

Shield01 ( NF3-01-07 ) ( Firefox ):
IP : 103.82.240.12
Username : administrator
Password : xxxx

Shield02 ( NF3-01-06 ) IPMIView :
IP : 103.82.240.162
Username : administrator
Password : xxxx

Shield03 ( NF3-01-03 ) ( Firefox ) :
IP : 103.82.243.105
Username : administrator
Password : xxxx

Login to iDRAC

Next part, login to iDRAC. After logged in into Shield03 server, now go to browser and open iDRAC IP address. The IP should be 192.168.x.x.

Enter username password iDRAC

When asking username and password of iDRAC, fill this :
username : exabytesIDadmin
password : 1Q2w3e4r0001

Check the Environment

Now we need to know whether the server is actually powered ON or switched OFF. See the status information below.

Based on image above, the server actually ON. But why it is appeared on Nagios as down? Let’s take a look deeper.

Launch Console

Launch console as above and click Launch.

Now you logged in into console server. Since the server siabuh is Windows, we need to use macros to enable function ctrl-alt-del to show login interface of Windows users.

Then you entered current username and password of particular server. Then troubleshoot and identify what is the root cause(s).

Let say you have done your job and managed to identify the root cause. Close the console window and make sure you Logout from the iDRAC panel.

Fin.