Sun Fire X4540 Server Linux and Solaris OS Installation Guide Table Of ContentsPrevious ChapterNext ChapterBook Index

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 SP2) 64-bit operating system. It includes the following sections:

Overview of the DCMU for SLES 10

The Disk Control and Monitor Utility (DCMU) controls and monitors all 48-disk drives on the Sun Fire X4540 server and provides the following features:

You may access these logs individually for specific information to aid in the administration or troubleshooting of the disk array. DCMU for SLES consist of two components. Each component updates the FRU, SDR (Sensor Data Record), SEL (System Event Log) and service processor logs:

IPMItool is an additional command line component that may be used as a supplement to DCMU to access service processor sensor data, read the SEL and FRU information, and perform chassis power control operations via the server’s Service Processor.

DCMU Installation Procedure

To use Disk Control and Monitor Utility (DCMU), you must install the application. To install the application, you should perform the following steps:

Installing DCMU

The installation of DCMU consists of one step because the package is in rpm format.


procedure icon  To Install DCMU

single-step bullet  Enter the following command:

# rpm -i dcmu_sles10-1.2-0.x86_64.rpm

The following files are installed as components of the DCMU installation:

IPMI Service Must Be Running to Use DCMU

The initial installation of the DCMU components prepares the system for running the DCMU utilities described in this chapter. However, since DCMU also requires that the IPMI service is running, you have two options before you can start using DCMU: manually start the IPMI service, or reboot the server, which will automatically start diskmond and IPMI.

If rebooting the server after the initial DCMU installation is not possible, and you wish to run DCMU, 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 will start both IPMI and diskmond.

Uninstalling DCMU

To uninstall DCMU, perform the following procedure.


procedure icon  To uninstall DCMU

single-step bullet  Enter the following command:

# rpm -e dcmu_sles10-1.2-0

diskmond Command

The Disk Control and Monitor Utility (DCMU) for SLES 10 has one primary utility called diskmond. The diskmond command 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.

The diskmond command spawns one thread to monitor hot plug event, another thread to monitor pending drive failure and reports both of these events to the service processor (SP). Diskmond performs the following functions:

diskmond Command Options

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:


TABLE 7-1 diskmond Command Options

Option

Description

-h

Displays help information

-V

Displays utility version information

-D

Displays disk drive information

-t minutes

Displays polling interval information (in minutes) in the syslog.


Examples Using the diskmond Command

This section contains examples of common diskmond commands issued from the command line. For more information and options, refer to the diskmond man page.

Stating diskmond From the Command Line

To start diskmon, enter the following command:

# service diskmond start

Stopping diskmond From the Command Line

To stop diskmon, enter the following command:

# service diskmond stop

Finding the status of diskmond From the Command-line

To obtain status from diskmon, enter the following command:

# service diskmond status

cfgdisk Command

The cfgdisk command queries and provides status of all 48-disk drives located in the Sun Fire X4540 server. The cfgdisk command 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. The command line options shown in TABLE 7-2 are supported:


TABLE 7-2 cfgdisk Command Options

Option

Description

-h

Displays help information

-V

Displays utility version information

-o

Connects and disconnects disk drive(s)

-d

Displays disk drive information


Examples Using the cfgdisk Command

This section contains examples of common cfgdisk commands issued from the command line. For more information and options, refer to the cfgdisk man page.

Displaying Disk, Device Nodes, Slots and Status

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: 


Device

Slot Number

Device Node

Status

sata0/0

0

/dev/sda

Connected

sata0/1

1

/dev/sdb

Connected

sata0/2

2

/dev/sdc

Connected

sata0/3

3

/dev/sdd

Connected

sata0/4

4

/dev/sde

Connected

sata0/5

5

/dev/sdf

Connected

sata0/6

6

/dev/sdg

Connected

sata0/7

7

/dev/sdh

Connected

sata1/0

8

/dev/sdi

Connected

sata1/1

9

/dev/sdj

Connected

sata1/2

10

/dev/sdk

Connected

sata1/3

11

/dev/sdl

Connected

sata1/4

12

/dev/sdm

Connected

sata1/5

13

/dev/sdn

Connected

sata1/6

14

/dev/sdo

Connected

sata1/7

15

/dev/sdp

Connected

sata2/0

16

/dev/sdq

Connected

sata2/1

17

/dev/sdr

Connected

sata2/2

18

/dev/sds

Connected

sata2/3

19

/dev/sdt

Connected

sata2/4

20

/dev/sdu

Connected

sata2/5

21

/dev/sdv

Connected

sata2/6

22

/dev/sdw

Connected

sata2/7

23

/dev/sdx

Connected

sata3/0

24

/dev/sdy

Connected

sata3/1

25

/dev/sdz

Connected

sata3/2

26

/dev/sdaa

Connected

sata3/3

27

/dev/sdab

Connected

sata3/4

28

 

Disconnected or not present

sata3/5

29

 

Disconnected or not present

sata3/6

30

 

Disconnected or not present

sata3/7

31

/dev/sdaf

Connected

sata4/0

32

 

Disconnected or not present

sata4/1

33

/dev/sdah

Connected

sata4/2

34

 

Disconnected or not present

sata4/3

35

/dev/sdaj

Connected

sata4/4

36

/dev/sdak

Connected

sata4/5

37

/dev/sdal

Connected

sata4/6

38

/dev/sdam

Connected

sata4/7

39

 

Disconnected or not present

sata5/0

40

 

Disconnected or not present

sata5/1

41

 

Disconnected or not present

sata5/2

42

/dev/sdaq

Connected

sata5/3

43

 

Disconnected or not present

sata5/4

44

 

Disconnected or not present

sata5/5

45

 

Disconnected or not present

sata5/6

46

 

Disconnected or not present

sata5/7

47

 

Disconnected or not present

Disconnecting a Disk Using cfgdisk

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 to disconnect the disk: 


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

Connecting a Disk Using cfgdisk

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.

Displaying cfgdisk Help Information

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.

Viewing System and Service Processor Logs Using IPMItool

This section describes how to view individual log file information from the command line using the IPMItool.

Obtaining and Installing the IPMItool

The IPMItool is a command line utility that reads the sensor data repository (SDR) and displays sensor values, System Event Log (SEL), Field Replaceable Unit (FRU) inventory information, gets and sets LAN configuration parameters, and performs chassis power control operations via the server’s Service Processor.

For your convenience, this tool is available as an installable rpm (x86 64-bit version) on your server’s Tools and Drivers CD, or as a downloadable package from the Sun software download site:

http://www.sun.com/servers/x64/x4540/downloads.jsp

For information about using the IPMItool, refer to your Sun Integrated Lights Out Manager 2.0 User’s Guide (820-1188)

Viewing the SDR log

The following commands show how view the SDR log file, either at the server:

# ipmitool -I open sdr elist

or over the network:

# 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.

Viewing the FRU log

The following commands show how view the FRU log file, either at the server:

# ipmitool -I open fru

or over the network:

# 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.


Note - When viewing the FRU log of a server running Linux, hard disk drive FRU information stored in the Service Processor FRU log might display a Product Name attribute. This attribute is meaningless, and should be ignored. Here’s an example of what you might see when viewing logged FRU data (via the ipmitool command or the server’s management tool) if this erroneous attribute were present:

FRU Device Description : hdd40.fru (ID 58)
Product Manufacturer : HITACHI
Product Name : 232VDDF12872G-40 <--ignore this line
Product Part Number : HDS7225SBSUN250G
Product Version : V44OA81A
Product Serial : VDK41BT4CAD0GE

Viewing the SEL log

The following commands show how view the SEL log file, either at the server:

# ipmitool -I open sel elist

or over the network:

# 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.

Viewing the System log

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.



Sun Fire X4540 Server Linux and Solaris OS Installation Guide 820-4893-13 Table Of ContentsPrevious ChapterNext ChapterBook Index

Copyright © 2009 Sun Microsystems, Inc. All rights reserved.