Checksum on Solaris OS

Here i share how to checksum file or folder on Solaris OS :
  on file

$ sum  <filename>

$sum ABC.dmp
21882 7592 ABC.dmp

 on folder

tar cf - <directory name> | sum - 

Oracle Solaris 10. UX: userdel: ERROR: Inconsistent password files. See pwconv(1M).

There is something wrong with user deleting in solaris 10, 
while you want to delete or add user, , and now you are getting following persist errors:

On USERADD : UX: userdel / useradd: ERROR: Inconsistent password files. See pwconv(1M).

Cause : in case you did manual delete entry in /etc/passwd? or something in like that way progress. 

Solution : Just make sure to remove lines relative to user you want to recreate in following files .
- /etc/opasswd
- /etc/oshadow
- /etc/passwd
- /etc/shadow
- /etc/user_attr

And remember that you should not leave blank lines in this files!!!

Setting up PostgreSQL on Solaris

Setting up PostgreSQL on Solaris

PostgreSQL is bundled with Solaris 10 and is available from the primary OpenSolaris IPS repository.

To check if PostgreSQL is installed in your Solaris instance you can use the following command:

$ svcs "*postgres*"

STATE          STIME    FMRI

disabled       Feb_16   svc:/application/database/postgresql:version_81

disabled       16:11:25 svc:/application/database/postgresql:version_82

Install Required Packages

If you don't see any PosgreSQL instance in your Solaris box then proceed and install the following packages (the list may actually change over time):

• SUNWpostgr
• SUNWpostgr-contrib
• SUNWpostgr-devel
• SUNWpostgr-docs
• SUNWpostgr-jdbc
• SUNWpostgr-libs
• SUNWpostgr-pl
• SUNWpostgr-server
• SUNWpostgr-server-data
• SUNWpostgr-tcl

Check if PostgreSQL SMF Services are Configured

After installation, SMF services should be listed by (the output may depend on the actual PostgreSQL version you installed):

$ svcs "*postgres*"

STATE          STIME    FMRI

disabled       Feb_16   svc:/application/database/postgresql:version_81

disabled       16:11:25 svc:/application/database/postgresql:version_82

On Solaris, PostgreSQL is managed by the SMF framework. If you're curious you can check the service manifest at /var/svc/manifest/application/database/postgresql.xml and the service methods at /lib/svc/method/postgresql. Many important parameters are stored in the service configuration file (postgresql.xml): if you want to change some parameters (such as PostgreSQL data directory) you must use svccfg to edit the service configuration.

PostgreSQL and RBAC

PostgreSQL on Solaris uses RBAC to give users permissions over the database instance. When you install Solaris' PostgreSQL packages an RBAC role is setup for you:

[/etc/passwd]
postgres:x:90:90:PostgreSQL Reserved UID:/:/usr/bin/pfksh

This user is setup as an RBAC role in /etc/user_attr file:

[/etc/user_attr]

postgres::::type=role;profiles=Postgres Administration,All

Permission for the Postgres Administration profiles are setup in the /etc/security/exec_attr file:

[/etc/security/exec_attr]

Postgres Administration:solaris:cmd:::/usr/postgres/8.2/bin/initdb:uid=postgres

Postgres Administration:solaris:cmd:::/usr/postgres/8.2/bin/ipcclean:uid=postgres

Postgres Administration:solaris:cmd:::/usr/postgres/8.2/bin/pg_controldata:uid=postgres

Postgres Administration:solaris:cmd:::/usr/postgres/8.2/bin/pg_ctl:uid=postgres

Postgres Administration:solaris:cmd:::/usr/postgres/8.2/bin/pg_resetxlog:uid=postgres

Postgres Administration:solaris:cmd:::/usr/postgres/8.2/bin/postgres:uid=postgres

Postgres Administration:solaris:cmd:::/usr/postgres/8.2/bin/postmaster:uid=postgres

Starting PostgreSQL

You can start PostgreSQL using the following SMF command from an account with the appropriate privileges:

$ su - postgres

$ svcadm enable svc:/application/database/postgresql:version_82

Initial Configuration

By default, PostgreSQL is configured to trust all of the local users. That's not a good practice because all your local users may connect to PostgreSQL as a superuser. The first to do is setting up a password for the postgres user:

$ psql -U postgres

postgres=# alter user postgres with password 'your-password';

Exit psql with the \q command and change the /var/postgres/8.2/data/pg_hba.conf file to set an appropriate authentication method and change the following line:

[/var/postgres/8.2/data/pg_hba.conf]

local all all trust

with, for example:

[/var/postgres/8.2/data/pg_hba.conf]

local all all md5

Next time you connect, PostgreSQL will be asking you for the user password. Now, let's refresh the PostgreSQL service so that PostgreSQL will receive a SIGHUP signal an re-read the pg_hba.conf file:

$ svcadm refresh svc:/application/database/postgresql:version_82

Done!

You're now running a PostgreSQL instance on your Solaris box ready to be given to your database administrator, ready for production use.

Solaris System Administrator Notes

ADD STATIC ROUTE IN UNIX SOLARIS
#route add net 28.133.0.0/18 172.24.105.1
-add the route accross reboot-
#vi /etc/rc2.d/S69static_routes

ODS

# metastat|grep -i maint
# metastat -p (to check the controller where metadevices are originally mounted)
# format (to check the current controller)
# metastat |grep -i replace (to check the metadevices to be replaced)
(and then do the replacement)
# metareplace d0 c2t0d0s0 c1t0d0s0 (note that c1 is the new controller)
# metadb -a -c3 /dev/dsk/c1t0d0s3 (create meta database for the new controller c1)
# metastat | grep resync
# while true
>do
>metastat | grep resync
>sleep 1
>done


RSH

Enable rsh in Solaris 10
# svcadm enable svc:/network/login:rlogin
# svcadm enable svc:/network/login:rlogin

Enable rsh in solaris 8
# vi /etc/inetd.conf
- uncomment
shell stream tcp nowait root /usr/sbin/in.rshd in.rshd
- restart inetd daemon
# pkill -HUP inetd

AUTOFS

- check the files /etc/auto_master and /etc/auto.dumps file
- once changes made, u need to do 'automount -v' to pickup the config files
- on the client share the filesystem
# share -F nfs -o ro /dumps
- edit /etc/dfs/dfstab
# share -F nfs -o ro /dumps
- restart nfs
# svcadm restart nfs/server
# dfshares or exportfs (to verify nfs shares)

NFS

- mount the dir
# mount -F nfs hkgfiler2:/remedy /opt/ar/directa

- edit /etc/vfstab to mount it upon boot up
hkgfiler2:/remedy - /opt/ar/directa nfs yes rw,soft



NTP

# svcadm disable ntp
# cp /etc/inet/ntp.client /etc/inet/ntp.conf (and type-in ntp servers)
e.g.

server hkgba00001
server hkgba00002

#ntpdate -d
#svcadm enable svc:/network/ntp

DU

Check for Top directory users
# du -sk /export/home/* | sort –nr

TAR

Un-tar tar.gz file IN SOLARIS
gunzip -c file_name.tar.gz |tar xvf –
or

# gzip -d snap_sol10.tar.gz
# tar xf snap_sol10.tar


Create tar file
tar cvf dir.tar

Create create .gz
#gzip dir.tar


HBA

Check HBA info:
# fcinfo hba-port

NIC

Check network interface
# cat /etc/path_to_inst
# grep bge path_to_inst
"/pci@1f,700000/network@2" 0 "bge"
"/pci@1f,700000/network@2,1" 1 "bge"
"/pci@1d,700000/network@2" 2 "bge"
"/pci@1d,700000/network@2,1" 3 "bge"

Change network interface to auto neg “on”
# vi /platform/sun4u/kernel/drv/bge.conf

Check for network collision
# netstat –i

EEPROM

Disable system check during reboot
# eeprom diag-switch? False


PKGADD

To add a package
# pkgadd –d .

REXEC

Disable rexec in Solaris 8
# vi /etc/inetd.conf
- comment out
exec stream tcp nowait root /usr/sbin/tcpd in.rexecd
exec stream tcp6 nowait root /usr/sbin/tcpd in.rexecd

- then restart inetd daemon
# pkill -HUP inetd

SWAP

- create local swap area - in kilobytes(k), blocks(b) or megabytes (m)
# mkfile 1024m /new_swap (create 1GB swap)
- activate the swap area
# swap –a /new_swap
- verify
# swap –l

LOCALE

- set system-wide locale
# vi /etc/TIMEZONE

- set user locale
# vi .profile

LVM (Logical Volume Management)

- install lvm software
- partition disks
# fdisk partition (e.g. /dev/sdb1)

- create physical volumes
# pvcreate /dev/sdb1
# pvcreate /dev/sdc1
# pvcreate /dev/sdd1
# pvscan

- create volume group and make it available
# vgcreate /dev/sdb1 /dev/sdc1 /dev/sdd1
# vgchange –a y
# vgdisplay
# lvcreate –-size 3493G –-name
# lvdisplay
# mount /dev/

- rename a logical volume group
# vgdisplay –v
# vgchange –a n /dev/
# vgrename /dev/ /dev/
# vgchange –a y /dev/
# vgdisplay –v
# vgdisplay –v ext

- rename a logical volume
# lvdisplay /dev/ext/
# lvrename /dev/ext/ /dev/ext/
# lvdisplay /dev/ext/

- make a filesystem on the disk
# mkfs.xfs –f /dev/fhome/fanhome
# mount /dev/fhome/fanhome /home
# mount –t xfs /dev/ext/nfsdata /mnt

- add a new drive to a volume group
# vgdisplay –v (check active disks)
# fdisk to create partition
# umount /bak/backups (filesystem to extend)
# pvcreate /dev/sdf1 (prepare new partition)
# vgextend bak /dev/sdf1
# lvresize –-size 5.999T /dev/shome/home (increase size)
# mount /dev/bak/backups /bak/backups
# xfs_growfs /bak/backups


ERROR/s Encountered

Error: SOLARIS box running slow

Resolution:
# mpstat 5 5 (check usr,sys usage)
# prstat -s cpu -n 5 (list by cpu usage and top 5 processes)
# prstat -s cpu -a -n 5 (list usage per user)


Error: Veritas config daemon vxconfigd not running

Resolution:
# modinfo|grep vx
If DMP is enabled the /etc/system will have the force load entries and the driver "vxdmp"
# grep vxdmp /etc/system
forceload: drv/vxdmp

# vxdctl mode
mode: enabled

Next, run vxinstall or do a vxconfigd -k -m enable

Error: Timed out while waiting for NIS to come up

Resolution:

- logon to console
- do a “send brk” to get to “ok prompt”
- boot to single user mode
Ok> boot –s
- temporarily disable RPC service or remove /etc/defaultdomain to prevent NIS from starting at system boot
# mv /etc/rc2.d/S71rpc /etc/rc2.d/NOS71rpc or
# rm /etc/defaultdomain
# or exit to continue booting to default runlevel




Error: “Umount: I/O error” or “umount: cannot unmount /mount_point”

Resolution:

# fuser –c /file_system
# kill -9 process_id (from the above fuser command)
# lsof +D /file_system
# umount –f /file_system
# mount | grep /file_sytem

Error: No directory – logged on with (/) directory

Resolution:

- restart autofs
# /etc/init.d/autofs stop; /etc/init.d/autofs start
- re-login


Error: Media Error (hard disk with bad sectors)

Resolution:

# format
- select the disk to read test
> anal (select analyze)
> read 

Go to ok prompt from ILOM of Sun T5120

Follow below procedure to get to "ok" prompt from ILOM.

1. ssh to ILOM hostname


2. From the ILOM prompt , type the below.

--> set /HOST send_break_action=break

--> start /SP/console to get to the ok prompt.


Manual system reset from the ILOM prompt.

--> set /HOST/bootmode script="setenv auto-boot? false"

--> reset /SYS

Mount USB drive in SOLARIS 10

# rmformat

Looking for devices…

1. Logical Node: /dev/rdsk/c0t1d0p0

Physical Node: /pci@0,0/pci-ide@1f,1/ide@0/sd@1,0

Connected Device: HL-DT-ST DVDRAM GSA-H42N RL00

Device Type: DVD Reader/Writer

2. Logical Node: /dev/rdsk/c4t0d0p0

Physical Node: /pci@0,0/pci8086,d605@1d,7/storage@3/disk@0,0

Connected Device: C2931006 Flash Disk 5.00

Device Type: Removable

#mount -F pcfs /dev/dsk/c4t0d0p0:c /mnt/usb
Not that the device used in mount command is “/dev/dsk/c4t0d0p0″ and not “/dev/rdsk/c4t0d0p0″

c4t0d0p1:c” here the “:c” means Windows C Drive like access.

Solaris Flash Archives

Flash images or flar image is very useful in situations where you need cloning/imaging or crashed server recovery. The flarcreate command creates a flash archive. A flash archive can be created on a system that is running a UFS root file system or a ZFS root file system. A flash archive of a ZFS root pool contains the entire pool hierarchy except for the swap and dump volumes and any excluded datasets. The swap and dump volumes are created when the flash archive is installed.


NOTE: By default, the flarcreate command ignores items that are located in "swap" partitions.

Let's see how we can work with flar image creation.

Create the archive:


For UFS:

# flarcreate -n "Solaris 10 10/09 build" -S -c -x /var/tmp/ /var/tmp/S10-1009.ufs.archive.sun4u-`date +'%Y%m%d%H%M'`

For ZFS:

# flarcreate -n "Solaris 10 10/09 build" -S -c /var/tmp/S10-1009.zfs.archive.sun4u-`date +'%Y%m%d%H%M'`


Where -


The "-n Solaris 10 10/09 build" implants a name into the FLAR image. The name should be something unique and meaningful to better identify it as the FLAR image for the system.

The "-x /var/tmp/" option causes the /var/tmp/ directory and its contents to be excluded from the FLAR image since it will not be needed in the FLAR image.

-S option causes to skip the disk space check and do not write archive size data to the archive. Without -S, flarcreate builds a compressed archive in memory before writing the archive to disk, to determine the size of the archive. The result of the use of -S is a significant decrease in the time it takes to create an archive.

-c Tells flar to compress the archive as it's writing it.


E.g. -


# time flarcreate -n "Solaris 10 10/09 build" -S -c /var/tmp/S10-1009.zfs.archive.sun4u-`date '+%m-%d-%y'`


Full Flash
Checking integrity...
Integrity OK.
Running precreation scripts...
Precreation scripts done.
Creating the archive...
Archive creation complete.
Running postcreation scripts...
Postcreation scripts done.


Running pre-exit scripts...
Pre-exit scripts done.


real 19m58.57s
user 13m42.99s
sys 1m55.48s



# ls -l /var/tmp/S10-1009.zfs.archive.sun4u*
-rw-r--r-- 1 root root 5339709933 Oct 14 04:54 /var/tmp/S10-1009.zfs.archive.sun4u-10-14-10


# flar info /var/tmp/S10-1009.zfs.archive.sun4u-10-14-10
archive_id=2f27a01690ce4fcaf398e638fcdcb66e
files_archived_method=cpio
creation_date=20101014093417
creation_master=XXXXXX
content_name=Solaris 10 10/09 build
creation_node=XXXXXXXX
creation_hardware_class=sun4u
creation_platform=SUNW,Sun-Fire-V240
creation_processor=sparc
creation_release=5.10
creation_os_name=SunOS
creation_os_version=Generic_142900-09
rootpool=rpool
bootfs=rpool/ROOT/s10s_u8wos_08a_Pre-patch
snapname=zflash.101014.04.10
files_compressed_method=compress
content_architectures=sun4c,sun4d,sun4m,sun4u,sun4s,sun4us
type=FULL


Also we can have a small shell script to create flar image -


#!/bin/sh
echo
echo Enter image name, i.e. Solaris build e.g. S10-1009.ufs.archive.sun4v
read ANS
echo "Image Name: ${ANS}" > /etc/image_catalog
echo "Image Created on: `date`" >> /etc/image_catalog
echo "Image Created by: `/usr/ucb/whoami` on `hostname`" >> /etc/image_catalog

#
# Clean up wtmpx so that new machine won't have last logins
#
cat /dev/null > /var/adm/wtmpx
#
# Now create flar, excluding -x /var/tmp/
#
flarcreate -n ${ANS} -c -a `/usr/ucb/whoami` -x /var/tmp/ /var/tmp/${ANS}_`date +'%Y%m%d%H%M'`

Log all Telnet and FTP Connections to a Solaris Machine

By default, the solaris inetd deamon does not log the IP address of the machines that are connecting to Solaris Server. To enable the logging of all the IP addresses of machines connecting to the server and the connection time, the following script can be used.

1. cd /etc/init.d
2. vi inetsvc
3. Change the last line in the file, ie
/usr/sbin/inetd -s &
to /usr/sbin/inetd -s -t &
4. Stop and Start that script
./inetsvc stop
./inetsvc start
5. vi /etc/syslog.conf
6 . Add the following line
deamon.notice /var/adm/name_of_log_file ( the two fields should be seperated by tabs )
7. touch /var/adm/name_of_log_file
8. kill -HUP syslogd
After these changes, all connections started through the inetd deamon such as Telnet and FTP will be logged to the new file created.
This is also very useful for auditing purposes with NTP protocol enabled. This gives a consistent time throughout the enterprise and accountability can be implemented in the organization.

How to Capture Network Packets in Solaris

How to Capture Network Packets in Solaris  

# snoop -h

snoop: illegal option -- h

Usage:  snoop

        [ -a ]                  # Listen to packets on audio

        [ -d device ]           # Listen on interface named device

        [ -s snaplen ]          # Truncate packets

        [ -c count ]            # Quit after count packets

        [ -P ]                  # Turn OFF promiscuous mode

        [ -D ]                  # Report dropped packets

        [ -S ]                  # Report packet size

        [ -i file ]             # Read previously captured packets

        [ -o file ]             # Capture packets in file

        [ -n file ]             # Load addr-to-name table from file

        [ -N ]                  # Create addr-to-name table

        [ -t  r|a|d ]           # Time: Relative, Absolute or Delta

        [ -v ]                  # Verbose packet display

        [ -V ]                  # Show all summary lines

        [ -p first[,last] ]     # Select packet(s) to display

        [ -x offset[,length] ]  # Hex dump from offset for length

        [ -C ]                  # Print packet filter code

        [ -q ]                  # Suppress printing packet count

        [ -r ]                  # Do not resolve address to name

        [ filter expression ]

Example:

        snoop -o saved  host fred

        snoop -i saved -tr -v -p19

Show DHCP packets :

# snoop |grep -i dhcp

Using device igb0 (promiscuous mode)

   50.17.0.1 -> NTU-HQ-GLOBAL DHCP/BOOTP DHCPDISCOVER

NTU-HQ-GLOBAL -> 50.17.0.1    DHCP/BOOTP DHCPOFFER

   50.17.0.1 -> NTU-HQ-GLOBAL DHCP/BOOTP DHCPDISCOVER

Show UDP packets :

# snoop |grep -i udp

Using device igb0 (promiscuous mode)

  172.16.0.1 -> 50.200.0.229 UDP D=1728 S=37628 LEN=32

  172.16.0.1 -> 50.17.0.41   UDP D=1728 S=37628 LEN=32

  172.16.0.1 -> 50.210.0.214 UDP D=1728 S=37628 LEN=32

Verbose packet display:

# snoop -v

ETHER:  ----- Ether Header -----

ETHER:

ETHER:  Packet 182 arrived at 15:37:15.74365

ETHER:  Packet size = 66 bytes

ETHER:  Destination = 0:0:5e:0:1:64, U.S. Department of Defense (IANA)

ETHER:  Source      = 0:21:28:d2:88:8c,

ETHER:  Ethertype = 0800 (IP)

^CETHER:

IP:   ----- IP Header -----

IP:

IP:   Version = 4

IP:   Header length = 20 bytes

IP:   Type of service = 0x00

IP:         xxx. .... = 0 (precedence)

IP:         ...0 .... = normal delay

IP:         .... 0... = normal throughput

IP:         .... .0.. = normal reliability

IP:         .... ..0. = not ECN capable transport

IP:         .... ...0 = no ECN congestion experienced

IP:   Total length = 52 bytes

IP:   Identification = 36051

IP:   Flags = 0x4

IP:         .1.. .... = do not fragment

IP:         ..0. .... = last fragment

IP:   Fragment offset = 0 bytes

IP:   Time to live = 255 seconds/hops

IP:   Protocol = 17 (UDP)

IP:   Header checksum = 0000

IP:   Source address = 172.16.0.1, 172.16.0.1

IP:   Destination address = 50.78.0.6, 50.78.0.6

IP:   No options

IP:

UDP:  ----- UDP Header -----

UDP:

UDP:  Source port = 37628

UDP:  Destination port = 1728

UDP:  Length = 32

UDP:  Checksum = DE96

UDP:

Display information on host 172.16.0.1 using summary verbose mode:

# snoop -V 172.16.0.1

To enable data captures from the snoop output without losing packets (while writing to the screen)by sending the snoop output to a file (snooper) :

# snoop -o /tmp/snooper -V 172.16.0.1

Show broadcast packets:

# snoop -d igb0 broadcast

Using device igb0 (promiscuous mode)

50.17.0.1   -> (broadcast)  ARP C Who is 172.16.0.8, sys13 ?

Enable FTP service on Solaris 10

Enable ftp service:

bash-3.2# vi /etc/ftpd/ftpusers

Comment required user to connect through ftp...

Eg:

#

#  List of users denied access to the FTP server, see ftpusers(4).

#

#sol
root

daemon

bin

sys

adm

lp

uucp

nuucp

smmsp

#

/etc/ftpd/ftpusers - User ID’s that you are trying to use to login must not be there in this file.

/etc/ftpd/ftphosts - this is used to specifically dis allow ftp access to a login ID from a particular host.

By using following commands verify weather ftp service is running.

# inetadm |grep -i ftp

enabled   online         svc:/network/ftp:default

# svcs |grep -i ftp

online         Feb_08   svc:/network/ftp:default

# cat /etc/services |grep -i ftp

ftp-data        20/tcp

ftp             21/tcp

tftp            69/udp

# netstat -an |grep -i *.21

      *.21       *.*    0      0 49152      0 LISTEN

      *.21       *.*    0      0 49152      0 LISTEN

#

If ftp service is offline use following command to enable ftp server

#svcadm enable ftp

How to view history of user access logs /system uptime and administration information on Solaris 10

View history of user access logs:

We can use last command for that,

The last command looks in the /var/adm/wtmpx file, which records all logins and logouts, for information about a user, a terminal, or any group of users and terminals.

SYNOPSIS

     last [-a] [-n number | -number]  [-f filename] [name |  tty]

The following options are supported:

-a                                             

Displays the hostname in the last column.

 -f filename                    

 Uses filename as the name of the accounting file instead of /var/adm/wtmpx.

 -n number|-number               

limits the number of entries displayed to that specified by number. These options are identical;    the    -number option is provided as   a transition tool only and is removed in future releases.

Eg:

#last –a

How to open live-updating log in terminal

tail [options]

#tail -f [your log file]

It's updating live feed in the terminal

# tail -f /var/adm/messages
Jun  3 12:26:00 WOMFDRC         /scsi_vhci/ssd@g600a0b800056393e000008fc4c8ee089 (ssd4): Command Timeout on path /ssm@0,0/pci@1d,600000/SUNW,qlc@2/fp@0,0 (fp2)
Jun  3 12:39:44 WOMFDRC scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Jun  3 12:39:44 WOMFDRC         /scsi_vhci/ssd@g600a0b800056393e000009024c8ee138 (ssd2): Command Timeout on path /ssm@0,0/pci@1d,600000/SUNW,qlc@2/fp@0,0 (fp2)
Jun  3 12:58:26 WOMFDRC scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Jun  3 12:58:26 WOMFDRC         /scsi_vhci/ssd@g600a0b800056393e000009024c8ee138 (ssd2): Command Timeout on path /ssm@0,0/pci@1d,600000/SUNW,qlc@2/fp@0,0 (fp2)
Jun  3 13:04:01 WOMFDRC ufs: [ID 845546 kern.notice] NOTICE: alloc: /BACKUP_NEW: file system full
Jun  4 00:00:05 WOMFDRC sendmail[21823]: [ID 801593 mail.crit] r53H052E021821: SYSERR(root): womfdrc.wom.co.id. config error: mail loops back to me (MX problem?)
Jun  5 00:00:03 WOMFDRC sendmail[5766]: [ID 801593 mail.crit] r54H03Ff005764: SYSERR(root): womfdrc.wom.co.id. config error: mail loops back to me (MX problem?)
Jun  5 04:22:25 WOMFDRC scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Jun  5 04:22:25 WOMFDRC         /scsi_vhci/ssd@g600a0b800056393e000008ec4c8ede1d (ssd23): Command Timeout on path /ssm@0,0/pci@1d,600000/SUNW,qlc@2/fp@0,0 (fp2)