Feeds:
Posts
Comments

In this scenario I’m using SLES 10, Veritas Dynamic Multipathing ,Veritas Volume Manager 5 MP3 and Hitachi SAN storage.

First scan for newly provided LUNs on Linux using following command:

# for i in `seq 0 3`; do echo ” – – – ” > /sys/class/scsi_host/host$i/scan; done

Once you verify you can see newly added LUNs from “fdisk -l” , use “vxdctl enable” command to rebuild the volume device node directories and to update the DMP internal database to reflect the new state of the system.

You can also use the “vxdisk scandisks” command to scan devices in the operating system device tree, and to initiate dynamic reconfiguration of multipathed disks.

If you want VxVM to scan only new devices that have been added to the system, and not for devices that have been enabled or disabled, specify the -f option to either of the commands,

# vxdctl -f enable

# vxdisk -f scandisks

In this case disk “sdy” is a new device that have been added to the system

# vxdisk list

DEVICE       TYPE              DISK         GROUP            STATUS
sdb          auto:cdsdisk    testvg01    testvg           online nohotuse
sdc          auto:cdsdisk    testvg02    testvg           online nohotuse
sdd          auto:cdsdisk    testvg03    testvg           online nohotuse
sde          auto:cdsdisk    testvg04    testvg           online nohotuse
sdf          auto:cdsdisk     testvg05    testvg           online nohotuse
sdy          auto:none             –              –                 error

Sometimes a disk cannot be initialized if it does not have a valid useable partition table. On Linux, you can use “fdisk” command to create an empty partition table on a disk

# fdisk /dev/sdy

Command (m for help): o
Command (m for help): w

” Warning: The fdisk command can destroy data on the disk”

Use “vxdisksetup” command to configure a disk from use with Veritas Volume Manager.

# /etc/vx/bin/vxdisksetup -i sdy format=cdsdisk

Add the new LUN to the existing disk group:

# vxdg -g testvg adddisk testvg06=sdy

# vxdisk list

DEVICE       TYPE              DISK         GROUP            STATUS
sdb          auto:cdsdisk    testvg01    testvg           online nohotuse
sdc          auto:cdsdisk    testvg02    testvg           online nohotuse
sdd          auto:cdsdisk    testvg03    testvg           online nohotuse
sde          auto:cdsdisk    testvg04    testvg           online nohotuse
sdf          auto:cdsdisk     testvg05    testvg           online nohotuse
sdy          auto:cdsdisk    testvg06    testvg            online

To exclude a disk from hot-relocation use,

# vxedit -g testvg set nohotuse=on testvg

# vxdisk list

DEVICE       TYPE              DISK         GROUP            STATUS
sdb          auto:cdsdisk    testvg01    testvg           online nohotuse
sdc          auto:cdsdisk    testvg02    testvg           online nohotuse
sdd          auto:cdsdisk    testvg03    testvg           online nohotuse
sde          auto:cdsdisk    testvg04    testvg           online nohotuse
sdf          auto:cdsdisk     testvg05    testvg           online nohotuse
sdy          auto:cdsdisk    testvg06    testvg            online nohotuse

# df -h

/dev/vx/dsk/testvg/testLV
400G  159G  240G  40% /testmt

To increate a testLV Volume by 100GB use

# /etc/vx/bin/resize -b -F vxfs -g [disk_group] [volume_name] +sizeGB [media_name]

where,

volume_name: Name of the volume that needs an increment.

media_name: Name of disk to use for allocating new space for a volume. (In this case we are not specifying any)

# /etc/vx/bin/vxresize -b -F vxfs -g testvg testLV +100g

To find the WWPN and Other information of Qlogic HBAs without restarting the host, you can use any of the following methods.

for i in `seq 0 4` ;

do echo #####Host $i ######;

cat /sys/class/fc_host/host$i/port_name;

cat /sys/class/fc_host/host$i/port_state;

cat /sys/class/fc_host/host$i/port_type;

cat /sys/class/fc_host/host$i/speed;

cat /sys/class/fc_host/host$i/supported_speeds;

done

Your output may be the following,

0x2100001b32xxxxx
Online
NPort (fabric via point-to-point)
4 Gbit
1 Gbit, 2 Gbit, 4 Gbit

0x2101001b32xxxxx
Online
NPort (fabric via point-to-point)

4 Gbit
1 Gbit, 2 Gbit, 4 Gbit

0x2100001b32xxxxx
Online
NPort (fabric via point-to-point)unknown

4 Gbit
1 Gbit, 2 Gbit, 4 Gbit

0x2101001b32xxxxx
Online
NPort (fabric via point-to-point)
4 Gbit
1 Gbit, 2 Gbit, 4 Gbit

0x2100001b32xxxxx
Online
NPort (fabric via point-to-point)
4 Gbit
1 Gbit, 2 Gbit, 4 Gbit

You can also use systool to find Port_name

$ systool -av -c fc_host
Class = “fc_host”

Class Device = “host0”
Class Device path = “/sys/class/fc_host/host0”
fabric_name         = “0x2000001b32xxxxx”
issue_lip           = <store method only>
node_name           = “0x2000001b32xxxxx”
port_id             = “0x000000”
port_name           = “0x2100001b32xxxxx”
port_state          = “Online”
port_type           = “NPort (fabric via point-to-point)”
speed               = “4 Gbit”
supported_classes   = “Class 3”
supported_speeds    = “1 Gbit, 2 Gbit, 4 Gbit”
tgtid_bind_type     = “wwpn (World Wide Port Name)”
uevent              = <store method only>

Device = “host0”
Device path = “/sys/devices/pci0000:00/0000:00:04.0/0000:17:00.0/0000:18:01.0/0000:25:00.0/host0”
optrom_ctl          = <store method only>
uevent              = <store method only>

Class Device = “host1”
Class Device path = “/sys/class/fc_host/host1”
fabric_name         = “0x2001001b32xxxxx”
issue_lip           = <store method only>
node_name           = “0x2001001b32xxxxx”
port_id             = “0x000000”
port_name           = “0x2101001b32xxxxx”
port_state          = “Online”
port_type           = “NPort (fabric via point-to-point)”
speed               = “4 Gbit”
supported_classes   = “Class 3”
supported_speeds    = “1 Gbit, 2 Gbit, 4 Gbit”
tgtid_bind_type     = “wwpn (World Wide Port Name)”
uevent              = <store method only>

Device = “host1”
Device path = “/sys/devices/pci0000:00/0000:00:04.0/0000:17:00.0/0000:18:01.0/0000:25:00.1/host1”
optrom_ctl          = <store method only>
uevent              = <store method only>

Class Device = “host2”
Class Device path = “/sys/class/fc_host/host2”
fabric_name         = “0x2000001b32xxxxx”
issue_lip           = <store method only>
node_name           = “0x2000001b32xxxxx”
port_id             = “0x000000”
port_name           = “0x2100001b32xxxxx”
port_state          = “Online”
port_type           = “NPort (fabric via point-to-point)”
speed               = “4 Gbit”
supported_classes   = “Class 3”
supported_speeds    = “1 Gbit, 2 Gbit, 4 Gbit”
tgtid_bind_type     = “wwpn (World Wide Port Name)”
uevent              = <store method only>

Device = “host2”
Device path = “/sys/devices/pci0000:00/0000:00:04.0/0000:17:00.0/0000:18:02.0/0000:22:00.0/host2”
optrom_ctl          = <store method only>
uevent              = <store method only>

Class Device = “host3”
Class Device path = “/sys/class/fc_host/host3”
fabric_name         = “0x2001001b32xxxxx”
issue_lip           = <store method only>
node_name           = “0x2001001b32xxxxx”
port_id             = “0x000000”
port_name           = “0x2101001b32xxxxx”
port_state          = “Online”
port_type           =  “NPort (fabric via point-to-point)”
speed               = “4 Gbit”
supported_classes   = “Class 3”
supported_speeds    = “1 Gbit, 2 Gbit, 4 Gbit”
tgtid_bind_type     = “wwpn (World Wide Port Name)”
uevent              = <store method only>

Device = “host3”
Device path = “/sys/devices/pci0000:00/0000:00:04.0/0000:17:00.0/0000:18:02.0/0000:22:00.1/host3”
optrom_ctl          = <store method only>
uevent              = <store method only>

Class Device = “host4”
Class Device path = “/sys/class/fc_host/host4”
fabric_name         = “0x2000001b32xxxxx”
issue_lip           = <store method only>
node_name           = “0x2000001b32xxxxxx”
port_id             = “0x65b913”
port_name           = “0x2100001b32xxxxxx”
port_state          = “Online”
port_type           = “NPort (fabric via point-to-point)”
speed               = “4 Gbit”
supported_classes   = “Class 3”
supported_speeds    = “1 Gbit, 2 Gbit, 4 Gbit”
tgtid_bind_type     = “wwpn (World Wide Port Name)”
uevent              = <store method only>

Device = “host4”
Device path = “/sys/devices/pci0000:00/0000:00:04.0/0000:17:00.0/0000:18:09.0/0000:1c:00.0/host4”
optrom_ctl          = <store method only>
uevent              = <store method only>

There are also other ways to find the WWPNs of HBAs, Please follow the link

http://linuxshellaccount.blogspot.com/2008/09/how-to-easily-find-wwns-of-qlogic-hba.html

http://publib.boulder.ibm.com/infocenter/dsichelp/ds8000ic/index.jsp?topic=/com.ibm.storage.ssic.help.doc/f2c_loclinux_192wga.html

I’m using openssl-devel-0.9.7d-15.21 and openssl-0.9.7d-15.21 version to generate the key and the CSR for vsftpd FTP SSL connection on SLES9 SP3 and SP4. To do this I did the following

openssl req -x509 -nodes -days 365 -newkey rsa:1024 -keyout /etc/vsftpd.key -out /etc/vsftpd.pem

and gave me following error saying

Unable to load config info
Generating a 1024 bit RSA private key
….++++++
…………………………………….++++++
writing new private key to ‘/etc/vsftpd.key’
—–
unable to find ‘distinguished_name’ in config
problems making Certificate Request
29524:error:0E06D06A:configuration file routines:NCONF_get_string:no conf or environment variable:conf_lib.c:325:

When I checked the config file , I could still see it’s under /etc/ssl/openssl.cnf but standard location for openssl.cnf is /usr/local/ssl which doesn’t exist on SLES 9. So I created a symbolic link to openssl.cnf and boom it’s working again

#mkdir /usr/local/ssl ; cd /usr/local/ssl

#ln -s /etc/ssl/openssl.cnf

# openssl req -x509 -nodes -days 365 -newkey rsa:1024 -keyout /etc/vsftpd.key -out /etc/vsftpd.pem
Generating a 1024 bit RSA private key
..++++++
………++++++
writing new private key to ‘/etc/vsftpd.key’
—–
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter ‘.’, the field will be left blank.
—–
Country Name (2 letter code) [AU]:
State or Province Name (full name) [Some-State]:
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []:
Email Address []:

# cat /proc/driver/cciss/cciss0
cciss0: HP Smart Array 5i Controller
Board ID: 0x40800e11
Firmware Version: 2.66
IRQ: 10
Logical drives: 3
Current Q depth: 0
Current # commands on controller: 0
Max Q depth since init: 128
Max # commands on controller since init: 128
Max SG entries since init: 31

Sequential access devices: 0

cciss/c0d0:       69.45GB       RAID 1(0+1)
cciss/c0d1:       69.45GB       RAID 1(0+1)
cciss/c0d2:       69.45GB       RAID 1(0+1)

 

Download

HP Array Configuration Utility for Linux

Hp Array Configuration Utility CLI for Linux

HP Array Diagnostics Utility for Linux

HP System management HomePage for Linux (x86)

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3291842&prodTypeId=15351&prodSeriesId=396616&swLang=8&taskId=135&swEnvOID=1097#7832

 

Install the System management Homepage

# rpm -ivh hpsmh-< version >.linux.i386.rpm

To run HPSMH

#/etc/init.d/hpsmhd start

 

Install HP Array Configuration Utility for Linux

# rpm -ivh cpqacuxe-8.25-5.noarch.rpm

The software resides in /usr/lib, /opt/compaq/cpqacuxe and the executable name is cpqacuxe which is located in /usr/sbin.

The password resetting utility is hphmmopasswd that is located in /opt/compaq/cpqacuxe/bld.

 

Running the Array Configuration Utility

Use “cpqacuxe” for the local access only or

“cpqacuxe -R” for remote access

 

Type "http://SERVERNAME:2301" into the url field. The servername should 
be the IP address or server name of the host on which the ACU server
is running.
Use root Username and Password for login

Supported Controllers

  Smart Array 5312 Controller
  Smart Array 5302 Controller
  Smart Array 5304 Controller
  Smart Array 532 Controller
  Smart Array 5i Controller
  Integrated Smart Array Controller
  Smart Array 4200 Controller
  Smart Array 4250ES Controller
  Smart Array 431 Controller
  Smart Array 3200 Controller
  MSA500 Controller
  MSA1000 Controller
  Smart Array 641 Controller
  Smart Array 642 Controller
  Smart Array 6400 Controller
  Smart Array 6400 EM Controller
  Smart Array 6i Controller
  MSA500 G2 Controller
  MSA1500 CS Controller
  MSA20 Controller
  Smart Array P600 Controller
  Smart Array P400 Controller
  Smart Array P400i Controller
  Smart Array E200 Controller
  Smart Array E200i Controller
  Smart Array P800 Controller
  Smart Array E500 Controller

EMC INQ utility

The Inquiry utility (INQ) is a command-line troubleshooting utility that displays
information on storage devices, typically Symmetrix. By default, INQ
returns the device name, Symmetrix ID, Symmetrix LUN, and capacity. This
utility will operate independently of any other EMC software. Use the INQ
Utility to collect system information to provide to EMC Global Services
for problem troubleshooting.

Download INQ utility from EMC support site below

ftp://ftp.emc.com/pub/symm3000/inquiry/ 

 

Running EMC inq utility on Solaris

 

# ./inq.sol64
Inquiry utility, Version V7.3-891 (Rev 2.0)      (SIL Version V6.5.2.0 (Edit Level 891)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

 

——————————————————————————————–
DEVICE                                               :VEND      :PROD            :REV   :SER NUM        :CAP(kb)
——————————————————————————————–
/dev/rdsk/c1t0d0s2                           :FUJITSU :MAW3073NCSUN72G :1703  :070029a0N7 :    71687369
/dev/rdsk/c1t1d0s2                           :FUJITSU :MAW3073NCSUN72G :1703  :070032a0NF :    71687369
/dev/rdsk/c3t50060E800544C808d0s2 :HITACHI :OPEN-V          :6003  :50 044D8   :    14227200
/dev/rdsk/c3t50060E800544C808d1s2 :HITACHI :OPEN-V*7        :6003  :50 044D8   :    99590400
/dev/rdsk/c3t50060E800544C848d0s2 :HITACHI :OPEN-V          :6003  :50 044D8   :    14227200
/dev/rdsk/c3t50060E800544C848d1s2 :HITACHI :OPEN-V*7        :6003  :50 044D8   :    99590400
/dev/rdsk/c4t50060E800544C810d0s2 :HITACHI :OPEN-V          :6003  :50 044D8   :    14227200
/dev/rdsk/c4t50060E800544C810d1s2 :HITACHI :OPEN-V*7        :6003  :50 044D8   :    99590400
/dev/rdsk/c4t50060E800544C850d0s2 :HITACHI :OPEN-V          :6003  :50 044D8   :    14227200
/dev/rdsk/c4t50060E800544C850d1s2 :HITACHI :OPEN-V*7        :6003  :50 044D8   :    99590400
/dev/vx/rdmp/Disk_0s2                     :FUJITSU :MAW3073NCSUN72G :1703  :080029c0N8 :    71687369
/dev/vx/rdmp/Disk_1s2                     :FUJITSU :MAW3073NCSUN72G :1703  :080032c0NG :    71687369
/dev/vx/rdmp/Disk_2s2                     :HITACHI :OPEN-V          :6003  :50 044C8   :    14227200
/dev/vx/rdmp/Disk_3s2                     :HITACHI :OPEN-V*7        :6003  :50 044C8   :    99590400

 

# ./inq.sol64 -hba
Inquiry utility, Version V7.3-891 (Rev 2.0)      (SIL Version V6.5.2.0 (Edit Level 891)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

—————————————————
HBA name:           QLogic Corp.-QLA2462-0
host WWN:           0000000000000000
vendor name:        QLogic Corp.
model:              QLA2462
firmware version:   4.0.27
driver version:     20070212-2.19
serial number:      0402G00-0722265734
vendor code:        0x0
HBA type:           Fibre Channel
port count:         2

port number:                 1
    port WWN:                     2100001B32183B60
    Port OS name:                 /dev/cfg/c3
    port type:                    NPORT
    port speed:                   2GBIT
    supported speed:              4GBIT
    port state:                   ONLINE
    port FCID:                    0x627513
    port supported COS:           0x10000000
    port supported FC4 types:     0x0000000000000000000000000000000000000000000000000000000000000000
    port active FC4 types:        0x0000010000000000000000000000000000000000000000000000000000000000
    max frame size:               2048

port number:                 2
    port WWN:                     2101001B32383B60
    Port OS name:                 /dev/cfg/c4
    port type:                    NPORT
    port speed:                   2GBIT
    supported speed:              4GBIT
    port state:                   ONLINE
    port FCID:                    0x617513
    port supported COS:           0x10000000
    port supported FC4 types:     0x0000000000000000000000000000000000000000000000000000000000000000
    port active FC4 types:        0x0000010000000000000000000000000000000000000000000000000000000000
    max frame size:               2048

Here are other options you can try with inq utility

# ./inq.sol64 -h
Inquiry utility, Version V7.3-891 (Rev 2.0)      (SIL Version V6.5.2.0 (Edit Level 891)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

Usage: inquiry <options>

    display types:
       -h               : display this help screen
       -et              : display emulation and type info   (Symmetrix only)
       -ckd             : display CKD device info           (Symmetrix only)
       -page0           : display detailed page0 (only valid with -dev option)
       -pagec0          : display detailed pagec0 (only valid with -dev option
                          and on CLARiiON devices)
       -parent          : display both PowerPath and OS device relationships
       -celerra         : display Celerra lable devices
       -sid             : display Symmetrix Serial Number
       -sym_wwn         : display Symmetrix device wwn and Serial Number
       -clariion        : display CLARiiON device information
       -clar_wwn        : display CLARiiON WWN and Serial Number
       -showvol         : display Symmetrix Volume Number.
       -compat          : display old format
       -btl             : display Bus Target and Lun
       -sw_wwn          : display StorageWorks WWN and Serial Id
       -hds_wwn         : display HDS WWN and Serial Id
       -s80_wwn         : display S80 WWN and Serial Id
       -invista_wwn     : display Invista WWN and Serial Id
       -shark_wwn       : display IBM Shark WWN and Serial Id
       -compaq_wwn      : display Compaq WWN and Serial Id
       -netapp_wwn      : display Netapp WWN and Serial Id
       -hba             : display HBA info only. See options below
       -identifier <device_name | nice_name | hp_id | vms_id>
                        : display device identifier info (EMC devices only)
       -mapinfo         : display target mapping information

    filter options:
       -no_filters      : show every device even if no data available
       -f_powerpath     : filter –  only powerpath devices
       -f_pseudo        : filter –  only pseudo devices
       -f_real          : filter –  only real devices
       -f_emc           : filter –  only EMC devices
       -f_ckd           : filter –  only ckd devices
       -f_celerra       : filter –  only Celerra devices
       -f_4k            : filter –  only Symmetrix volumes < 4096
       -f_clariion      : filter –  only CLARiiON devices
       -f_storwrks      : filter –  only Compaq StorageWorks devices
       -f_hds           : filter –  only Hitachi HDS devices
       -f_s80           : filter –  only Fujitsu Siemens S80 devices
       -f_invista       : filter –  only EMC Invista devices
       -f_shark         : filter –  only IBM SHARK devices
       -f_size <size>   : filter –  only show devices with <= size in kbytes

    query options:
       -skipread        : do not request Read Capacity
       -skipinq         : do not request Inquiry data
       -skipboth        : do not request Read Capacity or Inquiry data

    device options:
       -dev  <device>   : do inquiry on specified device
       -symmvol <vol#>  : show devices with Symm HEX volume #= <vol#>
       -clar_file <file-name>: show clariion devices in file

    other options:
       -no_dots         : do not display status dots
       -sortoff         : do not perform ANY sorting
       -sortsymm        : sort by Symmetrix serial number   (Symmetrix only)

    sym_wwn options:
       -sid_wwn <sid>   : the 12 digit SID of the symm for which you want wwn’s
       -symdev  <dev>   : the device for which you want the wwn

    HBA specific options:
       -hba               : display HBA info only
       -fibre             : display FC HBA info only
       -iscsi             : display ISCSI HBA info only
       -scsi              : display SCSI HBA info only
       -hba_file <file>   : external HBA file to use. -fibre only
       -create            : create external HBA file specified by -hba_file
      Usage :
       inquiry -hba [-fibre [-hba_file <file>] [-create]] [-scsi] [-iscsi]

Release notes:
     Only options listed above are supported, although other options
     may continue to work, they are subject to change or removal.

     the following parameter changes have occurred
       -nodots              ->  -no_dots
       -c                   ->  -ckd
       -v                   ->  -page0
       -r <devicename>      ->  -dev <devicename>
       -s SymmVolumeNumber  ->  -symmvol SymmVolumeNumber
       -xr                  ->  -f_pseudo
       -xps                 ->  -f_real
       -system              ->  no longer exists

Veritas Netbackup version

Find the Netbackup version

bash-3.00# /opt/openv/netbackup/bin/admincmd/bpgetconfig | grep VERSIONINFO
VERSIONINFO = “SunOS” “5.10” “Unknown” “NetBackup” “6.5” 650000

 

bash-3.00# cat /usr/openv/netbackup/version
HARDWARE SOLARIS
VERSION NetBackup 6.5.3
RELEASEDATE Fri Oct 31 00:23:11 CDT 2008
BUILDNUMBER 20081030

 

bash-3.00# cat /usr/openv/netbackup/bin/version
NetBackup-Solaris10 6.5.3

OpenIPMI is an effort to create a full-function IPMI system to allow full access to all IPMI information on a server and to abstract it to a level that will make it easy to use.

The Open IPMI Linux device driver is designed as a full-function IPMI device driver with the following features:

  • Allows multiple users.
  • Allows multiple interfaces.
  • Allows both kernel and userland things to use the interface.
  • Fully supports the watchdog timer.
  • It works like IPMI drivers are supposed to. It tracks outgoing messages and matches up their responses automatically. It automatically fetches events, received messages, etc.
  • It supports interrupts (I have tested them now).
  • It has backwards-compatability modules for supporting the Radisys IPMI driver and the Intel IMB driver.
  • It’s modular. You don’t have to have the standard userland interface. You don’t have to have the watchdog. Etc.
  • It supports generating an event on a panic.

 

Download OpenIPMI from http://openipmi.sourceforge.net/

Intel source http://www.intel.com/design/servers/ipmi/index.htm

IBM also now supports OpenIPMI drier beginning with the following version of servers.

The OpenIPMI driver ships with these and later operating systems and IBM’s applications will talk directly to the OpenIPMI driver without requiring a mapping layer.These operating systems also ship with an OS Watchdog application, which interfaces to the OpenIPMI driver, so that native watchdog application should be used in place of IBM’s Automatic Server Restart-IPMI application on these and later operating systems.

  • Red Hat Enterprise Linux 3.7
  • Red Hat Enterprise Linux 4.3
  • Red Hat Enterprise Linux 5
  • SUSE Linux Enterprise Server 9.3
  • SUSE Linux Enterprise Server 10
  • VMware ESX Server 2.5.4 (32-bit operating system)
  • VMware ESX Server 3 (32-bit operating system)

IBM Source: http://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-66668&brandind=5000008

# rpm -qa | grep -i ipmi
OpenIPMI-1.4.19-1.8
OpenIPMI-devel-1.4.19-1.8
ipmitool-1.8.2-0.5

ipmitool download: http://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5069538&brandind=5000008

http://ipmitool.sourceforge.net

ipmitool – utility for controlling IPMI-enabled devices

You can use IPMItool to configure and manage devices that support the Intelligent Platform Management Interface versions 1.5 and 2.0. IPMItool provides a simple, command-line interface to the Baseboard Management Controller, featuring the ability to read the sensor data repository (SDR) and print sensor values, display the contents of a system event log, print field-replaceable unit inventory information, read and set LAN configuration parameters, and perform remote chassis power control.

To check the Management Controller status and global enables using ipmitool utility

# ipmitool mc info
Device ID                 : 32
Device Revision           : 0
Firmware Revision         : 3.10
IPMI Version              : 2.0
Manufacturer ID           : 2
Product ID                : 251 (0x00e8)
Device Available          : yes
Provides Device SDRs      : no
Additional Device Support :
    Sensor Device
    SDR Repository Device
    SEL Device
    FRU Inventory Device
    IPMB Event Receiver
    IPMB Event Generator
    Chassis Device
Aux Firmware Rev Info     :
    0x5a
    0x53
    0x42
    0x54

Use sensor option to Print detailed sensor information

# ipmitool sensor
Ambient Temp     | 16.000     | degrees C  | ok    | 64.000    | na        | 64.000    | -128.000  | na        | na
Fan 1 Tach       | 2888.000   | RPM        | ok    | 760.000   | 1976.000  | 1976.000  | na        | na        | na
Fan 2 Tach       | 2888.000   | RPM        | ok    | 760.000   | 1976.000  | 1976.000  | na        | na        | na
Fan 3 Tach       | 2618.000   | RPM        | ok    | 770.000   | 2002.000  | 2002.000  | na        | na        | na
Fan 4 Tach       | 2541.000   | RPM        | ok    | 770.000   | 2002.000  | 2002.000  | na        | na        | na
Fan 5 Tach       | 2888.000   | RPM        | ok    | 760.000   | 1976.000  | 1976.000  | na        | na        | na
Fan 6 Tach       | 2964.000   | RPM        | ok    | 760.000   | 1976.000  | 1976.000  | na        | na        | na
Fan 7 Tach       | 2541.000   | RPM        | ok    | 770.000   | 2002.000  | 2002.000  | na        | na        | na
Fan 8 Tach       | 2618.000   | RPM        | ok    | 770.000   | 2002.000  | 2002.000  | na        | na        | na
CPU 1 Temp       | 31.000     | degrees C  | ok    | na        | na        | na        | 85.000    | na        | 95.000
Fan 1 Presence   | 0x0        | discrete   | 0x0280| na        | na        | na        | na        | na        | na
Fan 2 Presence   | 0x0        | discrete   | 0x0280| na        | na        | na        | na        | na        | na
Fan 3 Presence   | 0x0        | discrete   | 0x0280| na        | na        | na        | na        | na        | na
Fan 4 Presence   | 0x0        | discrete   | 0x0280| na        | na        | na        | na        | na        | na
Fan 5 Presence   | 0x0        | discrete   | 0x0280| na        | na        | na        | na        | na        | na
Fan 6 Presence   | 0x0        | discrete   | 0x0280| na        | na        | na        | na        | na        | na
Fan 7 Presence   | 0x0        | discrete   | 0x0280| na        | na        | na        | na        | na        | na
Fan 8 Presence   | 0x0        | discrete   | 0x0280| na        | na        | na        | na        | na        | na

…. truncated

Some available options for ipmitool util

# ipmitool help
Commands:
        raw           Send a RAW IPMI request and print response
        i2c           Send an I2C Master Write-Read command and print response
        lan           Configure LAN Channels
        chassis       Get chassis status and set power state
        event         Send pre-defined events to MC
        mc            Management Controller status and global enables
        sdr           Print Sensor Data Repository entries and readings
        sensor        Print detailed sensor information
        fru           Print built-in FRU and scan SDR for FRU locators
        sel           Print System Event Log (SEL)
        pef           Configure Platform Event Filtering (PEF)
        sol           Configure IPMIv2.0 Serial-over-LAN
        isol          Configure IPMIv1.5 Serial-over-LAN
        user          Configure Management Controller users
        channel       Configure Management Controller channels
        session       Print session information
        sunoem        OEM Commands for Sun servers
        exec          Run list of commands from file
        set           Set runtime variable for shell and exec

Find the following link to set up the IPMI watchdog Timer , Turning off the Watchdog and additional commands for Watchdog Timer administration

http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/liaai/ipmi/liaaiipmisetupwatchdog.htm&tocNode=toc%3Afront%2Ffront.cmb%2F0%2F2%2F7%2F5%2F5%2F0%2F