Author: Emerson .

Growing a soft partition and resizing filesystem in Solaris Volume Manager

I need to increase the filesystem called /bkp

root@solaris:~ # df -h /bkp
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d51 44G 26G 18G 60% /bkp

It’s mounted on a soft partition

root@solaris:~ # metastat d51
d51: Soft Partition
Device: d5
State: Okay
Size: 93298688 blocks (44 GB)
Extent Start Block Block count
0 20981760 10485760
1 54536288 82812928

d5: Concat/Stripe
Size: 143349312 blocks (68 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t2d0s2 0 No Okay Yes

Device Relocation Information:
Device Reloc Device ID
c1t2d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZ9R8BN00007523GZY7

Here I attach a LUN to metadevice d5

root@solaris:~ # metattach d5 /dev/rdsk/emcpower33c
d5: component is attached

Now d5 have an internal disk and a LUN from storage

root@solaris:~ # metastat -p d5
d5 2 1 c1t2d0s2 \
1 /dev/dsk/emcpower33c

Here is the command to increase the soft partition

root@solaris:~ # metattach d51 10g
d51: Soft Partition has been grown

After you increase the soft partition, you need to increase the filesystem with growfs

root@solaris:~ # growfs -M /bkp /dev/md/rdsk/d51
/dev/md/rdsk/d51: Unable to find Media type. Proceeding with system determined parameters.
Warning: 5376 sector(s) in last cylinder unallocated
/dev/md/rdsk/d51: 116367360 sectors in 11436 cylinders of 24 tracks, 424 sectors
56820,0MB in 1144 cyl groups (10 c/g, 49,69MB/g, 6016 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 919760,
Initializing cylinder groups:
………………….
super-block backups for last 10 cylinder groups at:
115401920, 115504112, 115606304, 115708496, 115810688, 115912880, 116015072,
116117264, 116219456, 116321648

root@solaris:~ # df -h /bkp
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d51 55G 26G 28G 48% /bkp

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 file system type and resizing VXFS filesystem on Solaris

Here is the filesystem that I wish to expand

root@solaris:/ # df -h /filestorage
Filesystem             size   used  avail capacity  Mounted on
/dev/vx/dsk/datadg/datastore
2.1T 2.1T    16G   100%    /filestorage

Checking the filesystem type

root@solaris:/ # fstyp /dev/vx/dsk/datadg/datastore
vxfs

Resizing the vxfs filesystem

root@solaris:/ # vxresize -g datadg -F vxfs datastore +208309m

Expanded 200 GB (208,309 MB)

root@solaris:/ # df -h /filestorage
Filesystem             size   used  avail capacity  Mounted on
/dev/vx/dsk/datadg/datastore
2.3T 2.1T   207G    92%    /filestorage

Install Chromium web browser on Fedora

Tom ‘spot‘ Callaway created a repository for the Chromium, the open source version of the Google Chrome web browser

To install, first create a file called /etc/yum.repos.d/chromium.repo with the following information

[fedora-chromium]
name=Chromium web browser and deps
baseurl=http://repos.fedorapeople.org/repos/spot/chromium/fedora-$releasever/$basearch/
enabled=1
gpgcheck=0

[fedora-chromium-source]
name=Chromium web browser and deps – Source
baseurl=http://repos.fedorapeople.org/repos/spot/chromium/fedora-$releasever/SRPMS/
enabled=0
gpgcheck=0

Then you run yum install -y chromium

root@shellcore:~ # yum install -y chromium
Loaded plugins: presto, refresh-packagekit
Setting up Install Process
Resolving Dependencies
–> Running transaction check
—> Package chromium.x86_64 0:5.0.355.0-0.1.20100315svn41615.fc12 set to be updated
–> Processing Dependency: chromium-libs = 5.0.355.0-0.1.20100315svn41615.fc12 for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libutility.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libbrowser.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libinstaller_util.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libchrome_gpu.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libdebugger.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libbase_i18n.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libbase.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libcommon_constants.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libipc.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libprofile_import.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libsyncapi.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libprinting.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: liballocator.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libapp_base.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: librenderer.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libglue.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libsandbox.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libworker.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libcommon.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libplugin.so()(64bit) for package: chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Running transaction check
—> Package chromium-libs.x86_64 0:5.0.355.0-0.1.20100315svn41615.fc12 set to be updated
–> Processing Dependency: v8 >= 2.1.4-1.20100315svn4129 for package: chromium-libs-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libv8.so.2()(64bit) for package: chromium-libs-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libGLEW.so.1.5()(64bit) for package: chromium-libs-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Processing Dependency: libminizip.so.1()(64bit) for package: chromium-libs-5.0.355.0-0.1.20100315svn41615.fc12.x86_64
–> Running transaction check
—> Package glew.x86_64 0:1.5.1-3.fc12 set to be updated
—> Package minizip.x86_64 0:1.2.3-23.fc12 set to be updated
—> Package v8.x86_64 0:2.1.4-1.20100315svn4129.fc12 set to be updated
–> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package        Arch    Version                                 Repository
Size
================================================================================
Installing:
chromium       x86_64  5.0.355.0-0.1.20100315svn41615.fc12     chromium  2.1 M
Installing for dependencies:
chromium-libs  x86_64  5.0.355.0-0.1.20100315svn41615.fc12     chromium   14 M
glew           x86_64  1.5.1-3.fc12                            fedora    109 k
minizip        x86_64  1.2.3-23.fc12                           fedora     24 k
v8             x86_64  2.1.4-1.20100315svn4129.fc12            chromium  895 k

Transaction Summary
================================================================================
Install       5 Package(s)
Upgrade       0 Package(s)

Total download size: 17 M
Downloading Packages:
Setting up and reading Presto delta metadata
Processing delta metadata
Package(s) data still to download: 17 M
(1/5): chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_ | 2.1 MB     00:13
(2/5): chromium-libs-5.0.355.0-0.1.20100315svn41615.fc12 |  14 MB     01:18
(3/5): glew-1.5.1-3.fc12.x86_64.rpm                      | 109 kB     00:02
(4/5): minizip-1.2.3-23.fc12.x86_64.rpm                  |  24 kB     00:00
(5/5): v8-2.1.4-1.20100315svn4129.fc12.x86_64.rpm        | 895 kB     00:06
——————————————————————————–
Total                                           164 kB/s |  17 MB     01:44
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing     : v8-2.1.4-1.20100315svn4129.fc12.x86_64                   1/5
Installing     : glew-1.5.1-3.fc12.x86_64                                 2/5
Installing     : minizip-1.2.3-23.fc12.x86_64                             3/5
Installing     : chromium-libs-5.0.355.0-0.1.20100315svn41615.fc12.x86_   4/5
Installing     : chromium-5.0.355.0-0.1.20100315svn41615.fc12.x86_64      5/5

Installed:
chromium.x86_64 0:5.0.355.0-0.1.20100315svn41615.fc12

Dependency Installed:
chromium-libs.x86_64 0:5.0.355.0-0.1.20100315svn41615.fc12
glew.x86_64 0:1.5.1-3.fc12
minizip.x86_64 0:1.2.3-23.fc12
v8.x86_64 0:2.1.4-1.20100315svn4129.fc12

Complete!

The browser is installed and is located on /usr/bin/chromium-browser. On Gnome it’s located under Internet.

You can also go to google.com/chrome and download a rpm file to your system.

Reinstaling Tivoli Data Protection for Oracle on Solaris SPARC

root@sol10sparc:~ # pkginfo -l TDPOrc64
PKGINST:  TDPOrc64
NAME:  IBM Tivoli Storage Manager for Databases – Oracle 64-bit Solaris 8/9/10
CATEGORY:  application
ARCH:  sparc
VERSION:  Version 5 Release 3 Level 3
BASEDIR:  /opt/tivoli/tsm/client
VENDOR:  IBM Tivoli
PSTAMP:  2006.167.17:10:16
INSTDATE:  Oct 09 2008 22:09
STATUS:  completely installed
FILES:        8 installed pathnames
2 shared pathnames
3 directories
4 executables
4420 blocks used (approx)

When you remove the Tivoli Data Protection for Oracle using pkgrm and you try to reinstall, you’ll notice that it will say that the install size will be 11 MBs but in reality it installs only 6 MBs. You need to uninstall it using a uninstaller script that comes with the package. After you run the uninstall script, you can run the installer script and it will install the 11 MBs.

root@sol10sparc:~ # /opt/tivoli/tsm/client/oracle/_uninst/uninstaller.bin

Building XML::Simple from Perl CPAN

Download XML::Simple from CPAN and then decompress and untar the downloaded file.

root@linux:/tmp # gunzip XML-Simple-2.18.tar.gz
root@linux:/tmp # tar xvf XML-Simple-2.18.tar
XML-Simple-2.18/
XML-Simple-2.18/t/
XML-Simple-2.18/t/1_XMLin.xml
XML-Simple-2.18/t/lib/
XML-Simple-2.18/t/lib/TagsToUpper.pm
XML-Simple-2.18/t/B_Hooks.t
XML-Simple-2.18/t/6_ObjIntf.t
XML-Simple-2.18/t/1_XMLin.t
XML-Simple-2.18/t/srt.xml
XML-Simple-2.18/t/4_MemShare.t
XML-Simple-2.18/t/3_Storable.t
XML-Simple-2.18/t/7_SaxStuff.t
XML-Simple-2.18/t/A_XMLParser.t
XML-Simple-2.18/t/0_Config.t
XML-Simple-2.18/t/subdir/
XML-Simple-2.18/t/subdir/test2.xml
XML-Simple-2.18/t/2_XMLout.t
XML-Simple-2.18/t/5_MemCopy.t
XML-Simple-2.18/t/8_Namespaces.t
XML-Simple-2.18/t/test1.xml
XML-Simple-2.18/t/desertnet.src
XML-Simple-2.18/t/9_Strict.t
XML-Simple-2.18/Changes
XML-Simple-2.18/MANIFEST
XML-Simple-2.18/lib/
XML-Simple-2.18/lib/XML/
XML-Simple-2.18/lib/XML/Simple/
XML-Simple-2.18/lib/XML/Simple/FAQ.pod
XML-Simple-2.18/lib/XML/Simple.pm
XML-Simple-2.18/META.yml
XML-Simple-2.18/maketest
XML-Simple-2.18/README
XML-Simple-2.18/Makefile.PL

root@linux:/tmp # cd XML-Simple-2.18
root@linux:/tmp/XML-Simple-2.18 # ls
Changes lib Makefile.PL maketest MANIFEST META.yml README t

Execute the script Makefile.PL to write the makefile

root@linux:/tmp/XML-Simple-2.18 # perl Makefile.PL
Checking installed modules …
XML::SAX is installed, it will be used by the test suite
Checking if your kit is complete…
Looks good
Writing Makefile for XML::Simple

Run make

root@linux:/tmp/XML-Simple-2.18 # make
cp lib/XML/Simple/FAQ.pod blib/lib/XML/Simple/FAQ.pod
cp lib/XML/Simple.pm blib/lib/XML/Simple.pm
Manifying blib/man3/XML::Simple::FAQ.3pm
Manifying blib/man3/XML::Simple.3pm

If you wish, you can skip to make install. Here I check if make test throw any error messages to my screen

root@linux:/tmp/XML-Simple-2.18 # make test
PERL_DL_NONLAZY=1 /usr/bin/perl “-MExtUtils::Command::MM” “-e” “test_harness(0, ‘blib/lib’, ‘blib/arch’)” t/*.t
# Package Version
# perl 5.8.5
# XML::Simple 2.18
# Storable 2.13
# XML::Parser 2.34
# XML::SAX 0.12
# XML::NamespaceSupport 1.08
# XML::SAX::PurePerl 0.90
# XML::LibXML::SAX::Parser 1.50
# XML::LibXML::SAX 1.00 (default parser)
t/0_Config……..ok
t/1_XMLin………ok
t/2_XMLout……..ok
1/201 skipped: Tie::IxHash not installed
t/3_Storable……ok
t/4_MemShare……ok
t/5_MemCopy…….ok
t/6_ObjIntf…….ok
t/7_SaxStuff……ok
t/8_Namespaces….ok
t/9_Strict……..ok
t/A_XMLParser…..ok
t/B_Hooks………ok
3/12 skipped: Tie::IxHash not installed
All tests successful, 4 subtests skipped.
Files=12, Tests=496, 12 wallclock secs ( 1.75 cusr + 0.41 csys = 2.16 CPU)

Then I install the files

root@linux:/tmp/XML-Simple-2.18 # make install
Installing /usr/lib/perl5/site_perl/5.8.5/XML/Simple.pm
Installing /usr/lib/perl5/site_perl/5.8.5/XML/Simple/FAQ.pod
Installing /usr/share/man/man3/XML::Simple::FAQ.3pm
Installing /usr/share/man/man3/XML::Simple.3pm
Writing /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi/auto/XML/Simple/.packlist
Appending installation info to /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/perllocal.pod

Testing Solaris IPMP failover

In an IPMP configuration, you set the IP addresses at the configuration file named after your network card. One of the configuration files you insert two IP addresses and one of them will be the one that can be failover to the other card in case of network failure.

root@solaris10:~ # cat /etc/hostname.ce0
solaris-ce0 netmask + broadcast + group asm_ipmp -failover deprecated up \
addif solaris netmask + broadcast + up

root@solaris10:~ # cat /etc/hostname.ce4
solaris-ce4 netmask + broadcast + group asm_ipmp deprecated -failover standby up

root@solaris10:~ # grep solaris /etc/hosts
130.175.216.183 solaris-ce4
130.175.216.184 solaris-ce0
130.175.216.155 solaris

root@solaris10:~ # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
inet 130.175.216.184 netmask ffffff80 broadcast 130.175.216.255
groupname asm_ipmp
ether 0:14:4f:43:94:2c
ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 130.175.216.155 netmask ffffff80 broadcast 130.175.216.255
ce2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.102.20 netmask ffffff00 broadcast 192.168.102.255
ether 0:14:4f:43:94:2e
ce4: flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 1500 index 4
inet 130.175.216.183 netmask ffffff80 broadcast 130.175.216.255
groupname asm_ipmp
ether 0:14:4f:3b:51:62

This command I will test the failover of the IP 130.175.216.155 to ce4.

root@solaris10:~ # if_mpadm -d ce0
Feb 13 06:24:57 solaris10 in.mpathd[428]: Successfully failed over from NIC ce0 to NIC ce4

root@solaris10:~ # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=89040842<BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,OFFLINE> mtu 1500 index 2
inet 130.175.216.184 netmask ffffff80 broadcast 130.175.216.255
groupname asm_ipmp
ether 0:14:4f:43:94:2c
ce2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.102.20 netmask ffffff00 broadcast 192.168.102.255
ether 0:14:4f:43:94:2e
ce4: flags=29040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY> mtu 1500 index 4
inet 130.175.216.183 netmask ffffff80 broadcast 130.175.216.255
groupname asm_ipmp
ether 0:14:4f:3b:51:62
ce4:1: flags=21000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,STANDBY> mtu 1500 index 4
inet 130.175.216.155 netmask ffffff80 broadcast 130.175.216.255

Returning the IP to ce0

root@solaris10:~ # if_mpadm -r ce0
Feb 13 06:25:35 solaris10 in.mpathd[428]: Successfully failed back to NIC ce0

root@solaris10:~ # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
inet 130.175.216.184 netmask ffffff80 broadcast 130.175.216.255
groupname asm_ipmp
ether 0:14:4f:43:94:2c
ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 130.175.216.155 netmask ffffff80 broadcast 130.175.216.255
ce2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.102.20 netmask ffffff00 broadcast 192.168.102.255
ether 0:14:4f:43:94:2e
ce4: flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 1500 index 4
inet 130.175.216.183 netmask ffffff80 broadcast 130.175.216.255
groupname asm_ipmp
ether 0:14:4f:3b:51:62

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

AIX – Some tape commands

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.

Fujitsu hardware running Solaris

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