C H A P T E R 7 |
Disk Control and Monitor Utility (DCMU) for SLES 10 |
This chapter describes how to use the Disk Control and Monitor Utility (DCMU) on a SUSE Linux Enterprise Server 10 (SLES 10) 64-bit operating system. It includes the following sections:
The Disk Control and Monitor Utility (DCMU) controls and monitors all 48-disk drives on the Sun Fire X4500 server and provides the following features:
To use Disk Control and Monitor Utility (DCMU), you must install the application. To install the application, you should perform the following steps:
The installation of DCMU consists of one step because the package is in rpm format. The DCMU package comes with two rpm files. One is the source rpm and other is the binary rpm.
To Install DCMU |
# rpm -ivh dcmu-1.3-7.x86_64.rpm
The following files are installed as components of the DCMU installation:
The initial installation of the DCMU components prepares the system for running the DCMU utilities described in this chapter. However, since the DCMU utilities also require that the IPMI service is running, you have two options before you can start using the DCMU utilities: manually start the IPMI service, or reboot the server (which automatically starts diskmond and IPMI).
If rebooting the server after the initial DCMU installation is not possible, and you wish to run DCMU utilities, you must first start the IPMI service by entering the following command:
# service ipmi start
Note - After the initial installation of DCMU, rebooting the server starts both IPMI and diskmond. |
To uninstall DCMU, perform the following procedure.
To uninstall DCMU |
# rpm -e dcmu-1.3-7
The Disk Control and Monitor Utility (DCMU) for SLES 10 has one primary utility called diskmond. diskmond is started at boot time with default polling interval of 60 minutes. It updates the FRU (Field Replacable Units), SDR (Sensor Data Record), SEL (System Event Log) and service processor logs.
diskmond spawns one thread to monitor hotplug event, another thread to monitor pending drive failure and reports both of these events to the service processor (SP). Diskmond performs the following functions:
Use the diskmond command to connect, disconnect, and determine disk drive status by using the parameters shown in TABLE 7-1. The following options are supported for the functions shown:
Displays polling interval information (in minutes) in the syslog. |
This section contains examples of common diskmond commands issued from the command line. For more information and options, refer to the diskmon man page.
To start diskmon, enter the following command:
# service diskmond start
To stop diskmon, enter the following command:
# service diskmond stop
To obtain status from diskmon, enter the following command:
# service diskmond status
cfgdisk queries and provides status of all 48-disk drives located in the Sun Fire X4500 server. cfgdisk also allows you to connect and disconnect disk drives from the OS while also allowing you to monitor disks connected to the server.
Use the cfgdisk command to connect, disconnect, and determine disk drive status by using the parameters shown in TABLE 7-2. The following options are supported for the functions shown:
This section contains examples of common cfgdisk commands issued from the command line. For more information and options, refer to the cfgdisk man page.
The following command displays a map of all disk drives:
# cfgdisk
Here is an example of cfgdisk command output listing physical slot number, logical name, and status information:
Use the cfgdisk command to disconnect a disk before performing the hot plug event of physically removing it. The following command shows an example of how to use cfgdisk to disconnect a disk drive.
# cfgdisk -o disconnect -d sata5/1
The command returns the following prompts; enter Y at both:
Are you sure (y/n)? y Are you sure sata5/1 device is not in use(y/n)? y Device sata5/1 has been successfully disconnected |
After performing the hot plug event of physically adding a disk into the system, use the cfgdisk command to connect it. The following command shows an example of how to use cfgdisk to connect a disk drive.
# cfgdisk -o connect -d sata5/1
The command returns the following:
Command has been issued to connect sata5/1 device, it may take few seconds to connect sata5/1,check status by re-running ’cfgdisk’ command. |
The following command shows how to use the cfgdisk command to display help information:
# cfgdisk -h
For additional information about cfgdisk or diskmond, refer to the man pages.
As described above, dcmu monitors hotplug events and pending drive failures, controlled connect/disconnect events and logs these events in syslog and, more importantly, in the service processor logs (SDR, FRU, SEL). You may access these logs individually for specific information to aid in the administration or troubleshooting of the disk array. This section describes how to view individual log file information from the command line.
The following commands show how view the SDR log file, either at the server:
# ipmitool -I open sdr elist
# ipmitool -I lan -H SP-IP -U root -P SP-password sdr elist
Where SP-IP represents the IP address of the service processor and SP-password represents the password for the service processor.
The following commands show how view the FRU log file, either at the server:
# ipmitool -I open fru
# ipmitool -I lan -H SP-IP -U root -P SP-password fru
Where SP-IP represents the IP address of the service processor and SP-password represents the password for the service processor.
The following commands show how view the SEL log file, either at the server:
# ipmitool -I open sel elist
# ipmitool -I lan -H SP-IP -U root -P SP-password sel elist
Where SP-IP represents the IP address of the service processor and SP-password represents the password for the service processor.
All events and error information from DCMU are logged in syslog (default: /var/log/messages). These include hard drive hotplug events, drive disconnect and connect events, and drive fault polling events.
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.