Month: February 2010

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

CA XCOM for Linux

Here is a brief document to help you install or uninstall Computer Associates XCOM Data Transport for Linux

How to install XCOM

Check if there is a group named xcomadm on your server. If not, please create it.

root@linux:~ # groupmod xcomadm
groupmod: group ‘xcomadm’ does not exist

Check if the package is not installed. The name of the package is CA_XCOM.

root@linux:~ # rpm -qi -p CA_XCOM.xclx86.k2.6.motif2.2.rpm
Name        : CA_XCOM Relocations: (not relocatable)
Version     : r11                               Vendor: (none)
Release     : 0603                          Build Date: Sat 03 Jun 2006 04:30:04 PM BRT
Install Date: (not installed)               Build Host: usprsus1.ca.com
Group       : Applications/Productivity     Source RPM: CA_XCOM-r11-0603.src.rpm
Size        : 11887644                         License: commercial
Signature   : (none)
Summary     : A file transfer program.
Description :
CA-XCOM is a general purpose file transfer program.

root@linux:~ # rpm -qa | grep CA_XCOM
root@linux:~ #

Since it is not installed, let’s install the package. If you install the package using rpm, remember to check if you have the package called openmotif22.

root@linux:/dsmc/T3/software/files/xcom-linux # yum install CA_XCOM.xclx86.k2.6.motif2.2.rpm
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.atlantic.net
* updates: centos.mirror.nac.net
* addons: centos.aol.com
* extras: mirror.nyi.net
Setting up Install Process
Parsing package install arguments
Examining CA_XCOM.xclx86.k2.6.motif2.2.rpm: CA_XCOM-r11-0603.i586
Marking CA_XCOM.xclx86.k2.6.motif2.2.rpm to be installed
Resolving Dependencies
–> Running transaction check
—> Package CA_XCOM.i586 0:r11-0603 set to be updated
–> Processing Dependency: libXm.so.3 for package: CA_XCOM
–> Running transaction check
—> Package openmotif22.i386 0:2.2.3-18 set to be updated
–> Finished Dependency Resolution
Dependencies Resolved

================================================================================

Package        Arch    Version       Repository                           Size

================================================================================

Installing:
CA_XCOM        i586    r11-0603      CA_XCOM.xclx86.k2.6.motif2.2.rpm    4.5 M
Installing for dependencies:
openmotif22    i386    2.2.3-18      base                                1.3 M

Transaction Summary

================================================================================
Install      2 Package(s)
Update       0 Package(s)
Remove       0 Package(s)

Total download size: 5.8 M
Is this ok [y/N]: y

Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing     : openmotif22                                       [1/2]
Installing     : CA_XCOM                                           [2/2]
Create Q, trusted, src, and trace directories
Make everything in /usr/spool/xcom and /usr/lib/xcom directories group xcomadm
Create the link for the program dealing with remotely initiated transfers
Set the permissions on the xcom directories /usr/spool/xcom/Q, /usr/spool/xcom/trace, /usr/spool/xcom/trusted, /usr/spool/xcom/ssl and /usr/spool/xcom/src
CA_XCOM install finished.

Installed: CA_XCOM.i586 0:r11-0603
Dependency Installed: openmotif22.i386 0:2.2.3-18
Complete!

Add the following lines to the /etc/services file

txpi              8044/tcp      # xcom
txpis             8045/tcp      # xcom (r11 only)

Create two files in /etc/xinetd.d called txpi and txpis

root@linux:~ # vi /etc/xinetd.d/txpi
# default: on
# description: The Unicenter CA-XCOM Data Transport Server.
service txpi
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/lib/xcom/xcomtcp
server_args = REMOTE 0
}

root@linux:~ # vi /etc/xinetd.d/txpis
# default: on
# description: The Unicenter CA-XCOM Data Transport Server.
service txpis
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/lib/xcom/xcomtcp
server_args = REMOTE 0 SSL
}

Start XCOM

root@linux:~ # /usr/sbin/xcomd
2008/09/28 21:01:53  PRG=xcomd PID=16368
XCOMU0088I xcomd started.

Making the daemon automatically start on startup

root@linux:~ # echo “xcom:3:once:/usr/sbin/xcomd” >> /etc/inittab
root@linux:~ # grep xcom /etc/inittab
xcom:3:once:/usr/bin/xcomd

Make xinetd reread its configuration file

root@linux:~ # pkill –HUP xinetd

Now check if there is a process listening on ports 8044 and 8045

root@linux:~ # netstat -an | grep 8044
tcp        0      0 0.0.0.0:8044                0.0.0.0:*                   LISTEN

root@linux:~ # netstat -an | grep 8045
tcp        0      0 0.0.0.0:8045                0.0.0.0:*                   EN

How to uninstall XCOM

Stop XCOM daemon

root@linux:~ # /usr/sbin/xcomd -s
XCOMU0079I xcomd: stop requested.
XCOMU0082I xcomd: stop request accepted.

Uninstall XCOM package

root@linux:~ # rpm -e CA_XCOM
Test if xcomd is running
xcomd not running, proceeding with uninstall.
Remove the program dealing with remotely initiated transfers
Remove the xcom directories
CA_XCOM uninstall finished.

How to discover the version of Veritas Explorer currently installed

To discover the version, simply run the tool with the -help flag.

root@solaris:/opt/VRTSspt/VRTSexplorer # ./VRTSexplorer -help
VRTSexplorer: version 4.0i
Usage: VRTSexplorer [ help | -help ] | [+v] [ module … ] | [+v] [ -module … ]
list of modules:  vxvm vxfs fw vxld dbed edition.dro edition.sybed vcs visnS visnC spc txpt vsap vrtsisp isis gcm vmsa vras vfr ndmp samba spnas vnas glm dbac td web lic vlic vrw picd nbu cca cpi vxat vxaz ccs

Discovering new disks in a Solaris server with QLogic HBA

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

Resetting a RSC / ALOM Card from Solaris

Here an RSC card wasn’t responding so my colleague decided to reboot the card.

root@solaris9:/ # /usr/platform/`uname -i`/rsc/rscadm shownetwork
rscadm: RSC firmware not responding~

When you pass the flag -s you try a soft reset in the card.

root@solaris9:/ # /usr/platform/`uname -i`/rsc/rscadm resetrsc -s
Are you sure you want to reboot RSC (y/n)?  y
rscadm: RSC firmware not responding

Here is the how to perform the hard reset

root@solaris9:/ # /usr/platform/`uname -i`/rsc/rscadm resetrsc
Are you sure you want to reboot RSC (y/n)?  y

If you need to reset the ALOM card, use scadm with the same parameters as above

root@solaris9:/ # /usr/platform/`uname -i`/sbin/scadm resetrsc -s

Unfortunately, resetting the card didn’t solve the problem.

Couldn’t mount AIX file system. First information says that media is not formatted

I had a problem mounting a file system after the server rebooted. At first it reported that the logical volume wasn’t formatted or the format is incorrect. Then it asked to run fsck.

root@aix5:/ # mount /fallback
Replaying log for /dev/fallback.
mount: 0506-324 Cannot mount /dev/fallback on /fallback: The media is not formatted or the format is not correct.
0506-342 The superblock on /dev/fallback is dirty.  Run a full fsck to fix.

I just ran fsck on the logical volume and then mounted the file system.

root@aix5:/ # fsck /dev/fallback

****************
The current volume is: /dev/fallback
**Phase 1 – Check Blocks, Files/Directories, and Directory Entries
**Phase 2 – Count links
**Phase 3 – Duplicate Block Rescan and Directory Connectedness
**Phase 4 – Report Problems
**Phase 5 – Check Connectivity
**Phase 7 – Verify File/Directory Allocation Maps
**Phase 8 – Verify Disk Allocation Maps
15728640 kilobytes total disk space.
63 kilobytes in 30 directories.
7664455 kilobytes in 438 user files.
8061172 kilobytes are available for use.
File system is clean.
Superblock is marked dirty; FIX? y
All observed inconsistencies have been repaired.

root@aix5:/ # mount /fallback

root@aix5:/ # df -g /fallback
Filesystem    GB blocks      Free %Used    Iused %Iused Mounted on
/dev/fallback      15.00      7.69   49%      470     1% /fallback

Login denied by eTrust Security solutions : User Inactivity Time

When you receive the error message “Login denied by eTrust Security solutions : User Inactivity Time”, you need to reenable the user with the senable command

emerson@192.168.1.50’s password:
Login denied by eTrust Security solutions : User Inactivity Time
Connection to 192.168.1.50 closed.

root@solariswithetrust:/ # /usr/seos/bin/senable emerson
senable: user emerson was not revoked by local serevu.
senable: Checking if user emerson is disabled on localhost in UNIX.
senable: User emerson already enabled.
senable: Checking if user emerson is disabled on localhost in eTrust database.
senable: User emerson is already resumed in eTrust.
(localhost)
Successfully connected
INFO: Target host’s version is 5.10b (5.14)
Unix OS info: solariswithetrust SunOS 5.8 11 Feb 2010 14:58:42 BRST
(localhost)
Successfully updated USER emerson

(localhost)
Successfully connected
INFO: Target host’s version is 5.10b (5.14)
Unix OS info: solariswithetrust SunOS 5.8 11 Feb 2010 14:58:43 BRST
(localhost)
Unix :
======
Successfully updated USER emerson

User emerson enabled on localhost.
emersoneTrust sepass v5.10b (5.10) – password replacement
Portions of this product Copyright (c) 1999-2001 Computer Associates International, Inc.
Portions of this product Copyright (c) 1995-2001 Memco Software Ltd., a CA company. All rights reserved.

Changing password for emerson
Enter yours or emerson’s password:
Enter new password:
Verify new password:
Local password updated successfully.