Category: Hardware

Acessing a console of a domain in a Sun Enterprise 10K

Here is the procedure to reset a domain in a Sun E10K. I don’t know if there is some detail missing but here is what was done with help of my friend at work.

To access the console of a domain hosted in a Sun E10K, first you need to know which number is this domain. I grepped the /etc/hosts to find out

root@ssp:/ # grep -i e10kdomain1 /etc/hosts
192.168.8.35 e10kdomain1 dom07 # 10.10.12.17 SB 06

Become the user ssp and enter the domain hostname

root@ssp:/ # su – ssp
Use of this network is restricted to authorized users only. User activity may be monitored and/or recorded. Anyone using this network expressly consents to such monitoring and/or recording. BE ADVISED: if possible criminal activity is detected, these records, along with certain personal information, may be provided to law enforcement officials.

Please enter SUNW_HOSTNAME: dom07

Use netcon to connect to the console

ssp:dom07% netcon
trying to connect…
connected.
Unlocked write permission is granted.

I connected to the domain’s console and the domain is locked. To reset it, you’ll need to know the system board to turn it off. Run domain_status and check the last column

ssp:dom07% domain_status
DOMAIN TYPE PLATFORM OS SYSBDS
dom07 Ultra-Enterprise-10000 OnDemand02 5.8 6
dom10 Ultra-Enterprise-10000 OnDemand02 5.8 9
dom15 Ultra-Enterprise-10000 OnDemand02 5.8 14
dom09 Ultra-Enterprise-10000 OnDemand02 5.8 8
dom01 Ultra-Enterprise-10000 OnDemand02 5.8 0
dom02 Ultra-Enterprise-10000 OnDemand02 5.8 1
dom05 Ultra-Enterprise-10000 OnDemand02 5.8 4

To power down you issue bringup -A off and the system board that the domain is running on

ssp:dom07% bringup -A off SB 6
Trying to get bringup.lock lock… OK
Checking that all other domains are down……… NO
Bringing up domain dom07
WARNING: Host is active; filesystems may be corrupted.
Do you really wish to continue (y/n)? y
Is this command executed because of a “Hung” Host (y/n)? y
Starting: hpost
Opening SNMP server library…

Significant contents of /export/home/ssp/.postrc:
#
logfile

Using blacklist file /var/opt/SUNWssp/etc/OnDemand02/blacklist
#=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
proc 12.2 12.3
Reading centerplane asics to obtain bus configuration…
Bus configuration determined to be 3F.
phase cplane_isolate: CP domain cluster mask clear…
phase init_reset: Initial system resets…
phase jtag_integ: JTAG probe and integrity test…
phase mem_probe: Memory dimm probe…
phase iom_probe: I/O module type probe…
phase jtag_bbsram: JTAG basic test of bootbus sram…
phase proc1: Initial processor module tests…
phase pc/cic_reg: PC and CIC register tests…
phase dtag: CIC DTAG tests…
phase mem: MC register and memory tests…
phase io: I/O controller tests…
phase procmem2: Processor vs. memory II tests…
phase lbexit: Centerplane connection tests…
phase npb_mem: Non-Proc Board MC and memory tests…
phase npb_iopc: Non-Proc Board IOPC register tests…
phase npb_io: Non-Proc Board I/O controller tests…
phase npb_cplane: Non-Proc Board centerplane connection tests…
phase nmb_procmem2: Non-Mem Board Proc vs. memory II tests…
phase final_config: Final configuration…
Configuring in 3F, FOM = 8192.00: 4 procs, 4 Scards, 4096 MBytes.
Creating OBP handoff structures…
Configured in 3F with 4 processors, 4 Scards, 4096 MBytes memory.
Interconnect frequency is 99.902 MHz, from SNMP MIB.
Processor external frequency is 199.805 MHz, from SNMP MIB.
Processor internal frequency is 399.610 MHz, from proc clk_mode probe.
Boot processor is 6.0 = 24
POST (level=16, verbose=20) execution time 4:03
Boot processor 24 written to /var/opt/SUNWssp/etc/OnDemand02/dom07/bootproc
Updating domain dom07 with bootproc 24 domainInstance 0 and interrupt vector MIB… OK
Starting obp_helper -m 24 -A off… OK
Starting netcon_server -p 24 … OK

Power on the domain with bringup -A on. No need to specify the system board this time

brsbssp02:dom07% bringup -A on
Trying to get bringup.lock lock… OK
Checking that all other domains are down……… NO
Bringing up domain dom07
Starting: hpost
Opening SNMP server library…

Significant contents of /export/home/ssp/.postrc:
#
logfile

Using blacklist file /var/opt/SUNWssp/etc/OnDemand02/blacklist
#=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
proc 12.2 12.3
Reading centerplane asics to obtain bus configuration…
Bus configuration determined to be 3F.
phase cplane_isolate: CP domain cluster mask clear…
phase init_reset: Initial system resets…
phase jtag_integ: JTAG probe and integrity test…
phase mem_probe: Memory dimm probe…
phase iom_probe: I/O module type probe…
phase jtag_bbsram: JTAG basic test of bootbus sram…
phase proc1: Initial processor module tests…
phase pc/cic_reg: PC and CIC register tests…
phase dtag: CIC DTAG tests…
phase mem: MC register and memory tests…
phase io: I/O controller tests…
phase procmem2: Processor vs. memory II tests…
phase lbexit: Centerplane connection tests…
phase npb_mem: Non-Proc Board MC and memory tests…
phase npb_iopc: Non-Proc Board IOPC register tests…
phase npb_io: Non-Proc Board I/O controller tests…
phase npb_cplane: Non-Proc Board centerplane connection tests…
phase nmb_procmem2: Non-Mem Board Proc vs. memory II tests…
phase final_config: Final configuration…
Configuring in 3F, FOM = 8192.00: 4 procs, 4 Scards, 4096 MBytes.
Creating OBP handoff structures…
Configured in 3F with 4 processors, 4 Scards, 4096 MBytes memory.
Interconnect frequency is 99.902 MHz, from SNMP MIB.
Processor external frequency is 199.805 MHz, from SNMP MIB.
Processor internal frequency is 399.610 MHz, from proc clk_mode probe.
Boot processor is 6.0 = 24
POST (level=16, verbose=20) execution time 4:02
Boot processor 24 written to /var/opt/SUNWssp/etc/OnDemand02/dom07/bootproc
Updating domain dom07 with bootproc 24 domainInstance 0 and interrupt vector MIB… OK
Starting obp_helper -m 24 -A on boot SB 6… OK
Starting netcon_server -p 24 … OK

Follow the console with netcon

ssp:dom07% netcon -g
trying to connect…
connected.
Unlocked write permission is granted.

How to connect to a Cyclades console server

Here I have a Cyclades AlterPath ACS16 Console Server. To connect to a serial port, first I need to login to the Cyclades

emerson@shellcore:~ $ ssh root@192.85.176.210
Password:

[root@cyclades011 root]#

To connect to a serial port, type the corresponding port on the ts_menu utility

[root@cyclades011 root]# ts_menu
Serial Console Server Connection Menu for your Master Terminal Server

1 0C-21-EFP01 2 0C-21-EFP02 3 0C-21-EFP03 4 0C-21-EFP04
5 0C-21-EFP05 6 0C-21-EFP06 7 0C-21-EFP07 8 0C-21-EFP08
9 0C-21-EFP09 10 0C-21-EFP10 11 0C-21-EFP11 12 0C-21-EFP12
13 0C-21-EFP13 14 0C-21-EFP14 15 0C-21-EFP15 16 0C-21-EFP16

Type ‘q’ to quit, a valid option[1-16], or anything else to refresh : 12

s_evt@cyclades011 2010-6-3T22:35:43Z 192.85.176.210 EVT[5]: Serial session started. User: root. Port name: 0C-21-EFP12. Port Number: 12. Session Type: 1.
solaris06 console login:

Please login:

I logged out of the ALOM and I didn’t have the password for it. Happily it timed out and I was back on the ALOM.

Serial line login timeout, returns to console stream.

Enter #. to return to ALOM.

To quit, press CTRL + \

solaris06 console login: (CTRL + \) Quit
[root@usplgmcylts011 root]# s_evt@usplgmcylts011 2010-6-3T22:51:50Z 192.85.176.210 EVT[6]: Serial session stopped. User: root. Port name: 0C-21-EFP12. Port Number: 12. Session type: 1.
s_evt@usplgmcylts011 2010-6-3T22:51:50Z 192.85.176.210 EVT[6]: Serial session stopped. User: root. Port name: 0C-21-EFP12. Port Number: 12. Session type: 1.

[root@cyclades011 root]#

Problem with HMC – rebooting

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

Resetting an LPAR on a Power4 system

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.

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

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

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

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.

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

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.

Update: Does my Mad Catz Tournament Edition Arcade Stick for PS3 works on PC / PS4 / Street Fighter 5?

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

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

Checking Disk Array status in AIX

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