setaOffice

Unix Intelligence Gathering

Archive for the ‘Hardware’ Category

« Previous Entries
Next Entries »

Problem with HMC – rebooting

Posted by Emerson Takahashi on July 29, 2010

hscroot@localhost:~> vtmenu

Retrieving name of managed system(s) . . . 10D400C

———————————————————-
Partitions On Managed System: 10D400C
———————————————————-
1) LPAR1 Not Available:
2) LPAR2 Not Available:

Enter Number of Running Partition (q to quit): q

Bye.

The server with the two LPAR partions were shut down due to a electric maintenance. I tried to start the partitions but I was having this problem:

hscroot@localhost:~> chsysstate -r lpar -m 10D400C -o on -n LPAR1
Unable to lock the Service Processor. Perform one of the following steps: (1) Check serial cable connection; (2) Check if another Console is communicating with the Service Processor; (3) Perform the Release Lock task; (4) Perform Rebuild task to re-establish the connection.

I tried again and I got a different error.

hscroot@localhost:~> chsysstate -r lpar -m 10D400C -o on -n LPAR1
Command sent to Service Processor failed. Error Response 4.

To reboot the IBM HMC, type the command below

hscroot@localhost:~> hmcshutdown -t now -r

Broadcast message from root (Sun Jun 6 08:35:38 2010):

The system is going down for reboot NOW!

I had problems with the reboot and asked to power off and power on the HMC. After that I had no more problems.

Posted in AIX, Hardware, HMC | Tagged: , | Leave a Comment »

Resetting an LPAR on a Power4 system

Posted by Emerson Takahashi on July 23, 2010

First you need to check some information for your system on the HMC. Issue the command vtmenu to get the managed system ID and the names of the partitions

hscroot@localhost:~> vtmenu

Retrieving name of managed system(s) . . . 108F19C

———————————————————-
Partitions On Managed System: 108F19C
———————————————————-
1) MANUFACTURING Running:
2) RETAIL Running:

Enter Number of Running Partition (q to quit): q

Bye.

On this example I tried to soft reset the partition called MANUFACTURING

hscroot@localhost:~> chsysstate -m 108F19C -r lpar -n MANUFACTURING -o reset

Since it didn’t work out as expected, I decided to power off the LPAR

hscroot@localhost:~> chsysstate -m 108F19C -r lpar -n MANUFACTURING -o off

hscroot@localhost:~> vtmenu

Retrieving name of managed system(s) . . . 108F19C

———————————————————-
Partitions On Managed System: 108F19C
———————————————————-
1) MANUFACTURING Ready:
2) RETAIL Running:

Enter Number of Running Partition (q to quit): q

Bye.

I turned the partition on and after that it worked flawlessly

hscroot@localhost:~> chsysstate -r lpar -m 108F19C -o on -n MANUFACTURING

hscroot@localhost:~> vtmenu

Retrieving name of managed system(s) . . . 108F19C

———————————————————-
Partitions On Managed System: 108F19C
———————————————————-
1) MANUFACTURING Starting:
2) RETAIL Running:

Enter Number of Running Partition (q to quit): q

Bye.

Posted in AIX, Hardware, HMC | Tagged: , , | Leave a Comment »

Discovering which drives the server will use to boot in a SPARC machine

Posted by Emerson Takahashi on June 28, 2010

Here is how to put more than one device on the variable devalias

root@solaris:/ # eeprom “nvramrc=devalias vx-rootdisk /pci@1c,600000/scsi@2/disk@0,0:a (press <Enter>)
> devalias vx-rootmirr /pci@1c,600000/scsi@2/disk@3,0:a” (press <Enter>)

Put more than one device to boot the system

root@solaris:/# eeprom “boot-device=vx-rootdisk vx-rootmirr”

List all the OpenBoot parameters

root@solaris:/# eeprom
asr-policy=normal
test-args: data not available.
diag-passes=1
local-mac-address?=true
fcode-debug?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
output-device=ttya
input-device=ttya
auto-boot-on-error?=true
error-reset-recovery=sync
load-base=16384
auto-boot?=true
network-boot-arguments: data not available.
boot-command=boot
diag-file: data not available.
diag-device=disk0:a
boot-file: data not available.
boot-device=vx-rootdisk vx-rootmirr
use-nvramrc?=false
nvramrc=devalias vx-rootdisk /pci@1c,600000/scsi@2/disk@0,0:a
devalias vx-rootmirr /pci@1c,600000/scsi@2/disk@3,0:a
security-mode=none
security-password: data not available.
security-#badlogins=0
verbosity=normal
diag-trigger=error-reset power-on-reset
service-mode?=false
diag-script=normal
diag-level=max
diag-switch?=false

Discovering which disk is used when booting

In the case of this server, it is using vx-rootdisk and if it fails, it will use the next one, the vx-rootmirr

root@solaris:/:> eeprom | grep boot-device
boot-device=vx-rootdisk vx-rootmirr

I need to find the hardware address of these two alias

root@solaris:/:> eeprom | grep vx-root
boot-device=vx-rootdisk vx-rootmirr
nvramrc=devalias vx-rootdisk /pci@1c,600000/scsi@2/disk@0,0:a
devlias vx-rootmirr /pci@1c,600000/scsi@2/disk@3,0:a

Now with the hardware address, I invoke the format command and see that this particular system is using disks 2 and 5 to boot.

root@solaris:/:> echo | format
Searching for disks…done

AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN-StorEdge3310-413B cyl 65533 alt 2 hd 64 sec 340>
/pci@1e,600000/scsi@3/sd@0,0
1. c1t1d0 <SUN-StorEdge3310-413B cyl 65533 alt 2 hd 64 sec 340>
/pci@1e,600000/scsi@3/sd@1,0
2. c2t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@0,0
3. c2t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@1,0
4. c2t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@1c,600000/scsi@2/sd@2,0
5. c2t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@1c,600000/scsi@2/sd@3,0
Specify disk (enter its number): Specify disk (enter its number):

To create the alias as stated in the beginning of this post, it will be necessary to get the hardware address and replace “sd” for “disk”.
Also Specify which disk slice that holds the root (/) filesystem. The slice 0 is the letter a, the slice 1 is b and so on.

5. c2t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@1c,600000/scsi@2/sd@3,0

root@solaris:/:> ls -l /dev/dsk/c2t3d0s0
lrwxrwxrwx   1 root     root          43 Feb 22  2006 /dev/dsk/c2t3d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@3,0:a

To validate this hardware address use boot and specify it on the OpenBoot prompt

ok> boot /pci@1c,600000/scsi@2/disk@3,0:a

Posted in Hardware, Solaris | Tagged: , , , , | Leave a Comment »

How to replace the ball top for a bat top on a Mad Catz Street Fighter IV FightStick Tournament Edition

Posted by Emerson Takahashi on May 26, 2010

If you are looking for a video teaching how to replace the ball top of a Mad Catz Street Fighter IV FightStick Tournament Edition look no further. You’ll need a Sanwa LB-30-N Joystick Bat Top and Sanwa Joystick Adapter. I bought my parts from Lizard Lick.

To replace the ball top for a bat top, you will need to remove all the hex screws and open the top of your FightStick. On the bottom of the joystick, put a knife or a flat screwdriver and loose the ball top.

Watch the video around 4m10s to see what’s the procedure looks like.

Posted in Hardware | Tagged: , , , | Leave a Comment »

Playstation 3 version of the Street Fighter IV FightStick Tournament Edition works on a PC

Posted by Emerson Takahashi on April 21, 2010

I recently bought the Street Fighter IV FightStick Tournament Edition for the PS3. My friend asked if I tried to use in the PC because he can use his PS3 controller on the PC. I tried and the FightStick works on the PC.

Here is the official page on MadCatz FAQ that says the PC is not officially supported but won’t work on a computer that has an NVidia chipset.

Posted in Hardware | Tagged: , , , | Leave a Comment »

ALOM – SC Alert: Failed to send email alert for recent event

Posted by Emerson Takahashi on March 25, 2010

When I was in the ALOM prompt I received the following error message

sc>
SC Alert: Failed to send email alert for recent event.

This ALOM card was set up to send emails but it was not configured to send the email to any particular host

sc> showsc
Advanced Lights Out Manager v1.5.4
parameter                value
———                —–
if_network               true
if_modem                 false
if_emailalerts           true
sys_autorestart          xir
sys_bootrestart          none
sys_bootfailrecovery     none
sys_maxbootfail          3
sys_xirtimeout           900
sys_boottimeout          900
sys_wdttimeout           60
netsc_tpelinktest        true
netsc_dhcp               false
netsc_ipaddr             148.95.150.176
netsc_ipnetmask          255.255.255.0
netsc_ipgateway          148.95.150.1
mgt_mailhost
mgt_mailalert
sc_customerinfo
sc_escapechars           #.
sc_powerondelay          true
sc_powerstatememory      false
sc_clipasswdecho         true
sc_cliprompt             sc
sc_clitimeout            0
sc_clieventlevel         2
sc_backupuserdata        true
sys_eventlevel           2
ser_baudrate             9600
ser_parity               none
ser_stopbits             1
ser_data                 8
netsc_enetaddr           00:03:ba:a3:3d:c4
sys_hostname             solaris9
sys_enetaddr             00:03:ba:a3:3d:bb

To set the if_emailalerts property to false, I typed the command below

sc> setsc if_emailalerts false

sc> showsc
Advanced Lights Out Manager v1.5.4
parameter                value
———                —–
if_network               true
if_modem                 false
if_emailalerts           false
sys_autorestart          xir
sys_bootrestart          none
sys_bootfailrecovery     none
sys_maxbootfail          3
sys_xirtimeout           900
sys_boottimeout          900
sys_wdttimeout           60
netsc_tpelinktest        true
netsc_dhcp               false
netsc_ipaddr             148.95.150.176
netsc_ipnetmask          255.255.255.0
netsc_ipgateway          148.95.150.1
mgt_mailhost
mgt_mailalert
sc_customerinfo
sc_escapechars           #.
sc_powerondelay          true
sc_powerstatememory      false
sc_clipasswdecho         true
sc_cliprompt             sc
sc_clitimeout            0
sc_clieventlevel         2
sc_backupuserdata        true
sys_eventlevel           2
ser_baudrate             9600
ser_parity               none
ser_stopbits             1
ser_data                 8
netsc_enetaddr           00:03:ba:a3:3d:c4
sys_hostname             solaris9
sys_enetaddr             00:03:ba:a3:3d:bb

And no more related error messages was shown after this

Posted in ALOM, Hardware, Solaris | Tagged: , | Leave a Comment »

Checking Disk Array status in AIX

Posted by Emerson Takahashi on March 5, 2010

This AIX server has a disk array connected.

root@aix:/ # lscfg -vl hdisk2
hdisk2           U0.1-P2-I3/Z3-A0  SCSI RAID 5 Disk Array

The array has 7 physical disks
root@aix:/ # lsdev -C | grep pdisk

pdisk0         Available 1A-08-01-0,0  Physical SCSI Disk Drive
pdisk1         Available 1A-08-01-1,0  Physical SCSI Disk Drive
pdisk2         Available 1A-08-01-2,0  Physical SCSI Disk Drive
pdisk3         Available 1A-08-01-3,0  Physical SCSI Disk Drive
pdisk4         Available 1A-08-01-4,0  Physical SCSI Disk Drive
pdisk5         Available 1A-08-01-5,0  Physical SCSI Disk Drive
pdisk6         Available 1A-08-01-6,0  Physical SCSI Disk Drive

Connected through a PCI-X SCSI RAID adapter
root@aix:/ # lscfg -vl sisioa0

sisioa0          U0.1-P2-I3  PCI-X Dual Channel U320 SCSI RAID Adapter
PCI-X Dual Channel Ultra320 SCSI RAID Adapter:
Part Number……………..97P3960
FRU Number………………97P3960
Serial Number……………YL10C4077074
Manufacture ID…………..000C
EC Level………………..0
ROM Level.(alterable)…….0709000c
Product Specific.(Z0)…….5703
Product Specific.(Z1)…….1
Device Specific.(YL)……..U0.1-P2-I3

When we checked the status we saw that the array was running in degraded state.
root@aix:/ #sisraidmgr -L -j1 -l sisioa0

————————————————————————
Name      Location      State       Description        Size
————————————————————————
sisioa0   1A-08         Available   PCI-X Dual Channel U320 SCSI RAID Adapter
scsi2    1A-08-00-07,0 NoLink      No remote adapter target
scsi3    1A-08-01-07,0 NoLink      No remote adapter target
hdisk2    1A-08-ff-0,0  Degraded RAID 5 Array     428.0GB
pdisk0   1A-08-01-0,0  Active      Array Member      71.4GB
pdisk1   1A-08-01-1,0  Active      Array Member      71.4GB
pdisk2   1A-08-01-2,0  Active      Array Member      71.4GB
pdisk3   1A-08-01-3,0  Active      Array Member      71.4GB
pdisk4   1A-08-01-4,0  Active      Array Member      71.4GB
pdisk5   1A-08-01-5,0  Active      Array Member      71.4GB
pdisk6   1A-08-01-6,0  Active      Array Member      71.4GB
hdisk0    1A-08-00-10,0 Available   16 Bit LVD SCSI  146.8GB
hdisk1    1A-08-00-11,0 Available   16 Bit LVD SCSI  146.8GB

Posted in AIX, Hardware | Tagged: , , | Leave a Comment »

AIX – Some tape commands

Posted by Emerson Takahashi on March 4, 2010

Getting information about the tape drive.

root@aix:/ # lscfg -vpl rmt0
rmt0             U787E.001.AAA2714-P2-C1-T2-L0-L0  4.0 GB 4mm Tape Drive
Manufacturer…………….ARCHIVE
Machine Type and Model……IBM4326NP/RP  !D
Device Specific.(Z1)……..5ALG
Serial Number……………DR0N6QG 0011
Load ID…………………0011
Part Number……………..21H5154
FRU Number………………59H3481
EC Level………………..E30312
Device Specific.(Z0)……..0180020283000018
Device Specific.(Z3)……..L1
PLATFORM SPECIFIC
Name:  st
Device Type:  byte

Getting information about the tape. It is using compression and a variable length block size.

root@aix:/ # tctl -f /dev/rmt0 status
rmt0 Available 06-08-01-0,0 4.0 GB 4mm Tape Drive
ttribute  value description                          user_settable
block_size 0     BLOCK size (0=variable length)       True
compress   yes   Use data COMPRESSION                 True
mode       yes   Use DEVICE BUFFERS during writes     True
ret_error  no    RETURN error on tape change or reset True

Rewinding tape drive

root@aix:/ # tctl -f /dev/rmt0 rewind

Reading tape and redirecting output to a file. In this case, the operating system showed that the tape itself is damaged.

root@aix:/ # tctl -f /dev/rmt0 read > /tmp/testtape
tctl: 0511-578 Cannot read 512 bytes: The media surface is damaged.

Posted in AIX, Hardware | Tagged: , , | Leave a Comment »

Fujitsu hardware running Solaris

Posted by Emerson Takahashi on February 28, 2010

Fujitsu made some SPARC machines sold under the brand PRIMEPOWER. It runs Solaris but to see the hardware information you need to use some specific tools that Fujitsu developed.

How to list hardware status

root@solaris8-fujistu:/ # /opt/FJSVmadm/sbin/hrdconf -l

Machine Administration tool is an interactive tool that can also be used to display hardware status

root@solaris8-fujistu:/ # /opt/FJSVmadm/sbin/madmin

If you need to run the equivalent of the Sun Explorer, you’re looking for fjsnap. First, check if you have it installed.

root@solaris8-fujistu:/ # pkginfo -l FJSVsnap
PKGINST:  FJSVsnap
NAME:  System Information Output Tool
CATEGORY:  application
ARCH:  all
VERSION:  2.5,REV=2005.01.1100
BASEDIR:  /
VENDOR:  FUJITSU/PFU LIMITED
DESC:  System Extensive Data & Information Output Tool
PSTAMP:  flicker120050419161312
INSTDATE:  Nov 27 2006 18:22
STATUS:  completely installed
FILES:      182 installed pathnames
3 shared pathnames
14 directories
147 executables
1437 blocks used (approx)

Then run it with /opt/FJSVsnap/bin/fjsnap -a <filename>

root@solaris8-fujistu:/ # /opt/FJSVsnap/bin/fjsnap -a /tmp/`hostname`.tar
<<< fjsnap * START !! >>>
<<< Path-name check * START !! >>>
<<< Path-name check *  END  !! >>>
<<< File-size check * START !! >>>
<<< File-size check *  END  !! >>>
<<<  needed tmp-space size  >>>
12806 MB is left in /var/tmp
143 MB is needed
<<< Copy to tmp-dir * START !! >>>
<<< Copy to tmp-dir *  END  !! >>>
<<< Output * START !! >>>
/usr/sbin/tar cfb /tmp/solaris8-fujistu.tar
<<< Output *  END  !! >>>
<<< fjsnap *  END  !! >>>

To get the machine model you can check

root@solaris8-fujistu:/ # /opt/FJSVhwr/sbin/prtdiag
System Configuration:  Fujitsu  sun4us Fujitsu PRIMEPOWER650 1-slot 4x SPARC64 V

root@solaris8-fujistu:/ # /opt/FJSVhwr/sbin/getmodelcode
650

How to get Primepower server serial number from the system console:
For PRIMEPOWER 250, PRIMEPOWER 450, PRIMEPOWER 650 and PRIMEPOWER 850

root@solaris8-fujitsu:/ # /opt/FJSVmadm/sbin/serialid -a
serialid: 6J123456,123456

For PRIMEPOWER 900, PRIMEPOWER 1500 and PRIMEPOWER 2500

root@solaris8-fujitsu:/ # /opt/FJSVcsl/bin/serialid -m machine_name -a
serialid: 6J123456,123456

The serial number starts with 6J or 6B

Posted in Hardware, Solaris | Tagged: , , , , , , | Leave a Comment »

Discovering new disks in a Solaris server with QLogic HBA

Posted by Emerson Takahashi on February 20, 2010

This server is using the QLogic’s FC driver and not the usual Sun’s driver.

root@solaris9:~ # modinfo | grep ql
25  12beb8f  83803 281   1  qla2300 (QLogic FC Driver v4.18)
307 7876c000  17e6f 280   1  qlog (VxQLOG 4.1_REV-4.1B18_sol_GA_s1)

To discover the new LUNs attached, use the qlreconfig utility

root@solaris9:~ # /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig -d qla2300 -v

*****                     *****
*****    W A R N I N G    *****
*****                     *****

PLEASE READ THE DOCUMENTATION BEFORE USING THIS UTILITY

This utility updates the driver configuration parameters
on an live system.  Extreme care MUST be taken to insure
that the specified parameters are correct for this system.
Failure to do so may render this system unusable, and/or
panic the system.

This utility utilizes the devfsadm utility, which depending on
the system and the number of devices, may take some time to
complete.

Do you wish to continue (y/n)? y
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: starting execution
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: utility verson is: 1.01
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: driver version: 4.18
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: os level is: 9
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: system call checks done
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: Found qla2300 driver ioctl device path at: ‘/devices/pci@1e,600000/SUNW,qlc@2:devctl’
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: buffer allocated and populated
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished with /usr/bin/pkill call
Dec 16 14:50:47  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: calling driver ioctl
Dec 16 14:50:48  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: ioctl OK — status is: 0; detail status is 0
Dec 16 14:50:48  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished with driver call
Dec 16 14:50:48  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: starting /usr/sbin/devfsadm call
Dec 16 14:51:15  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished with /usr/sbin/devfsadm call
Dec 16 14:51:15  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: starting /usr/sbin/update_drv call
Dec 16 14:51:25  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished with /usr/sbin/update_drv call
Dec 16 14:51:25  /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished

Posted in Hardware, QLogic, Solaris | Tagged: , , , | Leave a Comment »

« Previous Entries
Next Entries »
 
Follow

Get every new post delivered to your Inbox.

Join 250 other followers