Unix Admin Guide

UNIX Monitoring pipe activity with pv

2011-12-06T15:12:00.000+08:00

Monitoring pipe activity with pv

$ dd if=/dev/zero | pv > foo

522MB 0:00:06 [ 109MB/s] [ <=> ]

When pv is added to the pipeline, you get a continuous display of the amount of data that is being transferred between two pipe endpoints. I really dig this utility, and I am stoked that I found the catonmat website! Niiiiiiiiice!

UPDATE:

Try using pv when sending stuff over the network using dd. Neato.

[root@machine2 ~]# ssh machine1 “dd if=/dev/VolGroup00/domU2migrate”|pv -s 8G -petr|dd of=/dev/xen02vg/domU2migrate
0:00:30 [11.2MB/s] [====> ] 4% ETA :10:13

Want to rate limit the transfer so you don’t flood the pipe?

-L RATE, –rate-limit RATE
Limit the transfer to a maximum of RATE bytes per second. A suffix of “k”, “m”, “g”, or “t” can be added to denote kilobytes (*1024), megabytes, and so on.

-B BYTES, –buffer-size BYTES
Use a transfer buffer size of BYTES bytes. A suffix of “k”, “m”, “g”, or “t” can be added to denote kilobytes (*1024), megabytes, and so on. The default buffer size is the block size of the input file’s filesystem multiplied by 32 (512kb max), or 400kb if the block size cannot be determined.

Already have a transfer in progress and want to rate limit it without restarting?

-R PID, –remote PID
If PID is an instance of pv that is already running, -R PID will cause that instance to act as though it had been given this instance’s command line instead. For example, if pv -L 123k is running with process ID 9876, then running pv -R 9876 -L 321k will cause it to start using a rate limit of 321k instead of 123k. Note that some options cannot be changed while running, such as -c, -l, and -

Solaris 10: Adding a file system to a running zone

2011-12-06T14:49:00.000+08:00

Since the global zone uses loopback mounts to present file systems to zones, adding a new file system was as easy as loopback mounting the file system into the zone’s file system:

$ mount -F lofs /filesystems/zone1oracle03 /zones/zone1/root/ora03

Once the file system was mounted, I added it to the zone configuration and then verified it was mounted:

$ mount | grep ora03/filesystems/zone1oracle03 on filesystems/zone1oracle0 read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=2d9000b on Sun Apr 12 10:43:19 2009 /zones/zone1/root/ora03 on /filesystems/zone1oracle03 read/write/setuid/devices/dev=2d9000b on Sun Apr 12 10:44:07 2009

With ZFS filesystem (mountpoint=legacy):
mount -F zfs zpool/fs /path/to/zone/root/fs

Linux: remount read only file system

2011-12-06T12:13:00.000+08:00

$ mount -o remount,rw /

Once you can write to the file system you should be able to write out changes to the file system to correct the issue that prevented the server from booting. Viva la remount!

Solaris: coreadm core file management

2011-12-06T12:04:00.002+08:00

Using the Solaris coreadm utility to control core file generation

Solaris has shipped with the coreadm utiltiy for quite some time, and this nifty little utility allows you to control every facet of core file generation. This includes the ability to control where core files are written, the name of core files, which portions of the processes address space will be written to the core file, and my favorite option, whether or not to generate a syslog entry indicating that a core file was generated.

To begin using coreadm, you will first need to run it wit the “-g” option to specify where core files should be stored, and the pattern that should be used when creating the core file:

$ coreadm -g /var/core/core.%f.%p

Once a directory and file pattern are specified, you can optionally adjust which portions of the processes address space (e.g., text segment, heap, ISM, etc.) will be written to the core file. To ease debugging, I like to configure coreadm to dump everything with the”-G all” option:

$ coreadm -G all

Since core files are typically created at odd working hours, I also like to configure coreadm to log messages to syslog indicating that a core file was created. This can be done by using the coreadm “-e log” option:

$ coreadm -e log

After these settings are adjusted, the coreadm “-e global” option can be used to enable global core file generation, and the coreadm utility can be run without any arguments to view the settings (which are stored in /etc/coreadm.conf):

$ coreadm -e global

$ coreadm

global core file pattern: /var/core/core.%f.%p
     global core file content: all
       init core file pattern: core
       init core file content: default
            global core dumps: enabled
       per-process core dumps: enabled
      global setid core dumps: disabled
 per-process setid core dumps: disabled
     global core dump logging: enabled

Once global core file support is enabled, each time a process receives a deadly signal (e.g., SIGSEGV, SIGBUS, etc.):

$ kill -SIGSEGV 4652

A core file will be written to /var/core:

$ ls -al /var/core/*4652

-rw-------   1 root     root     4163953 Mar  9 11:51 /var/core/core.inetd.4652

And a message similar to the following will appear in the system log:

Mar 9 11:51:48 fubar genunix: [ID 603404 kern.notice] NOTICE: core_log: inetd[4652] core dumped: /var/core/core.inetd.4652

This is an amazingly useful feature, and can greatly simplify root causing software problems.

Solaris: killing defunct process

2011-12-06T12:00:00.000+08:00

$ ps -ef | grep defunct

root 646 426 0 - ? 0:00 '

root 1489 12335 0 09:32:54 pts/1 0:00 grep defunct
$ preap 646
646: exited with status 0

This will cause the process to exit, and the kernel can then free up the resources that were allocated by that process.

Solaris: undelete file

2011-12-06T11:46:00.002+08:00

How to undelete any open, deleted file on linux / solaris

Chris Dew wrote up a neat trick on how to recover files if deleted on Linux, yet still open by a process.

This works on Solaris as well. =)

$:~:uname -a
SunOS somehost.com 5.10 Generic_127112-11 i86pc i386 i86pc

$:~:echo “sup prefetch.net folks?” > testfile
$:~:tail -f testfile &
[1] 17134

$:~:rm testfile
$:~:ls /proc/17134/fd/
0 1 2
$:~:cat /proc/17134/fd/0
sup prefetch.net folks?
$:~:cp !$ ./testfile
cp /proc/17134/fd/0 ./testfile
$:~:cat testfile
sup prefetch.net folks?

Solaris: using samba to access windows server folder

2011-12-06T11:41:00.000+08:00

Accessing Windows shares from the Solaris/Linux command line

If Samba is installed on the system, this is easy to do with the smbclient utility. To access the Windows server named “milton” from the command line, you can run smbclient with the “-U” option, the name of the user to authenticate with, and the name of the server and share to access:

$ smbclient -U “domain\matty” //milton/foo

In this example, I am authenticating as the user matty in the domain “domain,” and accessing the share foo on the server milton. If smbclient is unable to resolve the server, you will need to make sure that you have defined a WINS server, or the server exists in the lmhosts file. To define a WINS server, you can add a line similar to the following (you can get the WINS server by looking at ipconfig /all on a Windows desktop, or by reviewing the LAN traffic with ethereal) to the smb.conf file:

wins server = 1.2.3.4

If you don’t want to use WINS to resolve names, you can add an entry similar to the following to the lmhosts file:

192.168.1.200 milton

Once you are connected to the server, you will be greeted with a “smb: \>” prompt. This prompt allows you to feed commands to the server, such as “pwd,” “dir,” “mget,” and “prompt.” To retrieve all of the files in the directory foo1, I can “cd” into the foo1 directory, use “prompt” to disable interactive prompts, and then run “mget” to retrieve all files in that directory:

smb: \> pwd
Current directory is \\server1\foo

smb: \> dir

received 10 entries (eos=1)
  .                                  DA        0  Mon May 22 07:19:21 2006
  ..                                 DA        0  Mon May 22 07:19:21 2006
  foo1                               DA        0  Sun Dec 11 04:51:12 2005
  foo2                               DA        0  Thu Nov  9 09:48:40 2006
         < ..... >

smb: \> cd foo1

smb: \foo1\> prompt
prompting is now off

smb: \foo1\> mget *

received 38 entries (eos=1)
getting file \foo1\yikes.tar of size 281768 as yikes.tar 411.3 kb/s) (average 411.3 kb/s)
    < ..... >

smb: \foo1\> exit

The smbclient manual page documents all of the available commands, and provides a great introduction to this super useful utility. If you bump into any issues connecting to a remote Windows server, you can add “-d” and a debug level (I like debug level 3) to the smbclient command line. This is perfect for debugging connectivity issues.

Solaris: free space in Veritas diskgroups

2011-12-06T11:33:00.002+08:00

Finding free space in Veritas diskgroups

The Veritas volume manager (VxVM) provides logical volume management capabilites across a variety of platforms. As you create new volumes, it is often helpful to know how much free space is available. You can find free space using two methods. The first method utilizes vxdg’s “free” option:

$ vxdg -g oradg free

GROUP        DISK         DEVICE       TAG          OFFSET    LENGTH    FLAGS
oradg        c3t20d1      c3t20d1s2    c3t20d1      104848640 1536      -
oradg        c3t20d3      c3t20d3s2    c3t20d3      104848640 1536      -
oradg        c3t20d5      c3t20d5s2    c3t20d5      104848640 1536      -
oradg        c3t20d7      c3t20d7s2    c3t20d7      104848640 1536      -
oradg        c3t20d9      c3t20d9s2    c3t20d9      104848640 1536      -

The “LENGTH” column displays the number of 512-byte blocks available on each disk drive in the disk group “oradg.”. If you don’t feel like using bc(1) to turn blocks into kilobytes, you can use vxassist’s “maxsize” option to print the number of blocks and Megabytes available:

$ vxassist -g oradg maxsize layout=concat
Maximum volume size: 6144 (3Mb)

Now to find out what to do with 3 MB of disk storage :)

Solaris: Vxvm calculate free chunk

2011-12-06T11:09:00.000+08:00

root $ sh a.sh
... Free chunk: rootmirr 25226.6 Meg
... Free chunk: rtdisk 5122.05 Meg
... Free chunk: rtdisk 0.250977 Meg
... Free chunk: rtdisk 0.255859 Meg
... Free chunk: rtdisk 2049.67 Meg
... Free chunk: rtdisk 550.151 Meg
root $ more a.sh
#! /bin/sh
vxdg -g rootdg free | nawk '
{
#if ($5/2/1024 > 100)
if ($5/2/1024 > 0)
print "... Free chunk: "$1" " $5/2/1024, "Meg"

Solaris : VXVM quick mirror

2011-12-06T11:00:00.002+08:00

VXVM quickly mirroring an empty volume

# vxassist make newvol 10m layout=concat-mirror init=active disk1 disk2

Solaris: Change NIS user password

2011-12-06T10:39:00.000+08:00

how to change nis user password

root@t47s# passwd eddccma
Enter login(NIS) password:
passwd(SYSTEM): Sorry, wrong passwd
Permission denied

...just login to nis master server
root@t47s# ypwhich -m passwd
ededuun001
root@t47s# ssh ededuun001
imhas@ededuun001 # yppasswd eddccma
New Password:
Re-enter new Password:
passwd: password successfully changed for eddccma
imhas@ededuun001 #

HPUX locating WWPN

2011-12-01T11:29:00.002+08:00

Locating the WWPN for an HP-UX host

Complete this task to locate the WWPN for a Hewlett-Packard Server host.

1. Go to the root directory of your HP-UX host.
2. Type ioscan -fnC fc| more for information on the fibre-channel adapters installed on the host.
The following is example output:

fc 0 0/2/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter /dev/td0
fc 1 0/4/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter /dev/td1
fc 2 0/6/2/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter /dev/td2

3. Look under the description for the Fibre Channel Mass Storage adapter.

For example, look for the device path name /dev/td1.
4. Type: fcmsutil /dev/td1 | grep world where /dev/td1 is the path.
The following is example output:

# fcmsutil /dev/td1 | grep World
N_Port Node World Wide Name = 0x50060b000024b139
N_Port Port World Wide Name = 0x50060b000024b138
(root@hpmain)/home/root# fcmsutil /dev/td0 | grep World
N_Port Node World Wide Name = 0x50060b000023a521
N_Port Port World Wide Name = 0x50060b000023a520
(root@hpmain)/home/root# fcmsutil /dev/td2 | grep World
N_Port Node World Wide Name = 0x50060b0000253a8f
N_Port Port World Wide Name = 0x50060b0000253a8e
(root@hpmain)/home/root#

Solaris: checking hba qlogic status

2011-12-01T11:26:00.002+08:00

checking hba on solaris qlogic
qlc(0) is the internal controllers for the dual SCSI disks or if it's
the Qlogic IPS2200 add-in card.

OS: Solaris 10 (11/06)
Kernel: 125100-07

luxadm -e port

/devices/pci-at-9,600000/SUNW,qlc-at-2/fp-at-0,0:devctl CONNECTED
/devices/pci-at-8,600000/pci-at-1/SUNW,qlc-at-4/fp-at-0,0:devctl NOT CONNECTED
/devices/pci-at-8,600000/pci-at-1/SUNW,qlc-at-5/fp-at-0,0:devctl CONNECTED

Solaris: metadb repair

2011-12-01T11:22:00.001+08:00

$ df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d100 10086628 8051562 1934200 81% /
/devices 0 0 0 0% /devices
ctfs 0 0 0 0% /system/contract
proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
swap 10513824 1072 10512752 1% /etc/svc/volatile
objfs 0 0 0 0% /system/object
/platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1
10086628 8051562 1934200 81% /platform/sun4u-us3/lib/libc_psr.so.1
/platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
10086628 8051562 1934200 81% /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
fd 0 0 0 0% /dev/fd
swap 6146048 4469136 1676912 73% /tmp
swap 10512784 32 10512752 1% /var/run
/dev/md/dsk/d102 10237036 7516386 2618280 75% /opt
/dev/md/dsk/d104 70569513 50785798 19078020 73% /opt/app
/dev/md/dsk/d103 1988623 29696 1899269 2% /var/tmp
$ uname -a
SunOS intdev02 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Fire-V240

[03:35:01] root@intdev02[1]# grep -i warn /var/adm/messages
Jun 27 21:29:32 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:37 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2 (glm0):
Jun 27 21:30:37 intdev02 glm: [ID 401478 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6018]
Jun 27 21:30:38 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2 (glm0):
Jun 27 21:30:38 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:38 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:41 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:41 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 md_stripe: [ID 641072 kern.warning] WARNING: md: d300: write error on /dev/dsk/c1t1d0s0
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:46 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:51 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 md_stripe: [ID 641072 kern.warning] WARNING: md: d300: read error on /dev/dsk/c1t1d0s0
Jun 27 21:30:56 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 md_stripe: [ID 641072 kern.warning] WARNING: md: d300: write error on /dev/dsk/c1t1d0s0
Jun 27 21:30:56 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 md_stripe: [ID 641072 kern.warning] WARNING: md: d300: read error on /dev/dsk/c1t1d0s0
Jun 27 21:30:56 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 md_stripe: [ID 641072 kern.warning] WARNING: md: d300: read error on /dev/dsk/c1t1d0s0
Jun 27 21:30:56 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 md_stripe: [ID 641072 kern.warning] WARNING: md: d300: write error on /dev/dsk/c1t1d0s0
Jun 27 21:30:56 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 md_stripe: [ID 641072 kern.warning] WARNING: md: d300: read error on /dev/dsk/c1t1d0s0
Jun 27 21:30:56 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@1,0 (sd0):
Jun 27 21:30:56 intdev02 md_stripe: [ID 641072 kern.warning] WARNING: md: d300: read error on /dev/dsk/c1t1d0s0
Jun 27 21:31:01 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd3):
Jun 27 21:31:01 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@2,0 (sd1):
Jun 27 21:31:01 intdev02 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2/sd@3,0 (sd2):
[03:35:01] root@intdev02[2]# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c1t0d0
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0
/pci@1c,600000/scsi@2/sd@1,0
2. c1t2d0
/pci@1c,600000/scsi@2/sd@2,0
3. c1t3d0
/pci@1c,600000/scsi@2/sd@3,0
Specify disk (enter its number): 1
selecting c1t1d0
[disk formatted]
/dev/dsk/c1t1d0s0 is part of SVM volume stripe:d300. Please see metaclear(1M).
/dev/dsk/c1t1d0s1 is part of SVM volume stripe:d301. Please see metaclear(1M).
/dev/dsk/c1t1d0s3 is part of SVM volume stripe:d302. Please see metaclear(1M).
/dev/dsk/c1t1d0s4 is part of SVM volume stripe:d303. Please see metaclear(1M).
/dev/dsk/c1t1d0s5 is part of SVM volume stripe:d302. Please see metaclear(1M).
/dev/dsk/c1t1d0s7 contains an SVM mdb. Please see metadb(1M).

FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
! - execute , then return
quit
format>
[03:35:01] root@intdev02[3]#
[03:35:01] root@intdev02[5]# date
Tue Jul 1 03:39:06 MEST 2008
[03:35:01] root@intdev02[6]# iostat -En | more
c1t1d0 Soft Errors: 0 Hard Errors: 21 Transport Errors: 2
Vendor: SEAGATE Product: ST373207LSUN72G Revision: 045A Serial No: 05433302ZN
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 19 No Device: 1 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
[03:35:01] root@intdev02[9]# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
W p l 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16 8192 /dev/dsk/c1t2d0s7
a p luo 8208 8192 /dev/dsk/c1t2d0s7
a p luo 16 8192 /dev/dsk/c1t3d0s7
a p luo 8208 8192 /dev/dsk/c1t3d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
[03:35:01] root@intdev02[10]#

# metadb -a c0t2d0s3 c1t1d0s3

Example 3: Deleting Two Replicas

This example shows how to delete two replicas from the sys-
tem. Assume that replicas have been set up on
/dev/dsk/c0t2d0s3 and /dev/dsk/c1t1d0s3.

# metadb -d c0t2d0s3 c1t1d0s3
[03:35:01] root@intdev02[18]# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
W p l 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16 8192 /dev/dsk/c1t2d0s7
a p luo 8208 8192 /dev/dsk/c1t2d0s7
a p luo 16 8192 /dev/dsk/c1t3d0s7
a p luo 8208 8192 /dev/dsk/c1t3d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
[03:35:01] root@intdev02[19]# metadb -d c1t1d0s7
[03:35:01] root@intdev02[20]# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t2d0s7
a p luo 8208 8192 /dev/dsk/c1t2d0s7
a p luo 16 8192 /dev/dsk/c1t3d0s7
a p luo 8208 8192 /dev/dsk/c1t3d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
[03:35:01] root@intdev02[21]# metadb -a c1t1d0s7
[03:35:01] root@intdev02[22]# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a u 16 8192 /dev/dsk/c1t1d0s7
a p luo 16 8192 /dev/dsk/c1t2d0s7
a p luo 8208 8192 /dev/dsk/c1t2d0s7
a p luo 16 8192 /dev/dsk/c1t3d0s7
a p luo 8208 8192 /dev/dsk/c1t3d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
[03:35:01] root@intdev02[23]#

Linux: Lun detection

2011-12-01T11:20:00.002+08:00

LUN detection procedures

This topic describes LUN detection procedures for the Linux host system.
If you have a Linux driver that does not automatically configure any LUNs other than LUN 0, you can manually configure the other LUNs, depending on the parameters and settings used for the SCSI mid-layer driver. Figure 1 shows an example of the /proc/scsi/scsi file for a Linux host that only configures the first LUN, LUN 0, on each host adapter port.
Figure 1. Example of a /proc/scsi/scsi file from a Linux host that only configures LUN 0

# cat proc/scsi/scsi
...
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM-PSG Model: DPSS-318350M F Rev: S9HA
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 15 Lun: 00
Vendor: IBM Model: TP4.6 V41b3 Rev: 4.1b
Type: Processor ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03

There are two ways to workaround the issue of only having LUN 0 configured:

1. Create a script to manually add devices into /proc/scsi/scsi
2. Detect LUNs automatically at system boot by modifying the initial ram-disk (initrd)

Create a script to echo the /proc filesystem

Use the scsi add-single-device command to consecutively configure all of the LUNs that are assigned to your host system. Write a script that repeats the scsi add-single-device command for each LUN on each ID for each host adapter. The script must scan all host adapter ports and identify all of the LUNs that are assigned to each port.

After you run the script, you can view all of the assigned LUNs in the /proc/scsi/scsi file.

Figure 2 shows an excerpt of an example /proc/scsi/scsi file for a Linux host after a script has configured every LUN.
Figure 2. Example of a /proc/scsi/scsi file for a Linux host with configured LUNs

# cat proc/scsi/scsi
...
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 00 Lun: 02
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 00 Lun: 03
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 00 Lun: 04
Vendor: IBM Model: 2105800 Rev: .294
Type: Direct-Access ANSI SCSI revision: 03
...

Detect LUNs automatically at system boot
The second method of configuring LUNs for a Linux system with only LUN 0 configured involves setting the parameter for the SCSI mid-layer driver that controls how many LUNs are scanned during a SCSI bus scan. The following procedure works for both 2.4 and 2.6 kernels, but it assumes the SCSI mid-layer driver is compiled as a scsi_mod module that is loaded automatically at system boot time. For Linux 2.4 kernels, to set the maximum number of disk devices under Linux to properly detect all volumes, you need to set the max_scsi_luns option for the SCSI mid-layer driver. For example, if max_scsi_luns is set to 1 this limits SCSI bus scans to only LUN 0. This value should be set to the respective maximum number of disks the kernel can support, for example, 128 or 256. In Linux 2.6 kernels, the same procedure applies, except that the parameter has been renamed from max_scsi_luns to max_luns.

1. Edit the /etc/modules.conf file.
2. Add the following line:
* options scsi_mod max_scsi_luns= (where is the total number of luns to probe.
3. Save the file.
4. Run the mkinitrd command to rebuild the ram-disk associated with the current kernel. You can use the following figures examples of what mkinitrd command to run for your operating system. refers to the ‘uname –r’ output which displays the currently running kernel level, for example:. 2.4.21-292-smp.
For SUSE distributions, use the following command:

cd /boot
mkinitrd –k vmlinuz- -i initrd-

For Red Hat distributions, use the following command:

cd /boot
mkinitrd –v initrd-.img

5. Reboot the host.
6. Verify that the boot files are correctly configured for the newly created initrd image in the /boot/grub/menu.lst file.

Solaris: calculate diff filesystem size after transfer

2011-11-23T20:36:00.001+08:00

#! /bin/sh
value1=`df -k /app/iwstoreEMEA_snap| grep snap| awk '{print $3}'`
value2=`df -k /server4_EMEA | grep _EMEA | awk '{print $3}'`
exprans=`expr $value1 - $value2`
echo "$exprans kb left"
sleep 60
value1=`df -k /app/iwstoreEMEA_snap| grep snap| awk '{print $3}'`
value2=`df -k /server_EMEA | grep _EMEA | awk '{print $3}'`
exprans1=`expr $value1 - $value2`
transfer=`expr $exprans - $exprans1`
echo "$transfer KB transferd"

$ sh a.sh

42318487 kb left

14891 KB transferd

Solaris: ssh tunnel and nc file transfer

2011-11-23T15:14:00.002+08:00

You pipe the file to a listening socket on the server machine in the same way as before. It is assumed that an SSH server runs on this machine too.

$ cat backup.iso | nc -l 3333
On the client machine connect to the listening socket through an SSH tunnel:

$ ssh -f -L 23333:127.0.0.1:3333 me@192.168.0.1 sleep 10; \
nc 127.0.0.1 23333 | pv -b > backup.iso

This way of creating and using the SSH tunnel has the advantage that the tunnel is automagically closed after file transfer finishes. For more information and explanation about it please read my article about auto-closing SSH tunnels.

Solaris: ssh and tar

2011-11-23T14:22:00.004+08:00

How to transfer directories into remote server using tar and ssh combined.

$ tar cf - mydir/ | ssh gate 'cd /tmp && tar xpvf -'

Sendmail: how to masquarate from oracle@host.domain.com to oracle@domain.com

2011-11-21T14:22:00.000+08:00

root@wbitdb1:/etc/mail # diff sendmail.cf sendmail.cf.21012008
986,987c986
< #R$* < @ *LOCAL* > $* $: $1 < @ $j . > $2
< R$* < @ *LOCAL* > $* $: $1 < @ $M . > $2
---
> R$* < @ *LOCAL* > $* $: $1 < @ $j . > $2
root@wbitdb1:/etc/mail #

add the line shown below
--------------
###################################################################
### Ruleset 94 -- convert envelope names to masqueraded form ###
###################################################################

SMasqEnv=94
#R$* < @ *LOCAL* > $* $: $1 < @ $j . > $2 <--------------- this line commented
R$* < @ *LOCAL* > $* $: $1 < @ $M . > $2 <--------------- this line added

----------
Testing masquerading
sendmail's address test mode makes it easy to test masquerading.
====================================================

# sendmail -bt
/tryflags HS (to test the header sender address; other tryflags values would be ES, HR, and ER, for envelope sender, header recipient, and envelope recipient, respectively)
/try esmtp email_address_to_test

Example:
sendmail -bt
> /tryflags ES
> /try esmtp user@host.domain.com
Trying envelope sender address user@host.domain.com for mailer esmtp

(many lines omitted)

final returns: user @ domain . com
Rcode = 0, addr = user@domain.com

Solaris: Other tunnelling tricks

2011-11-19T21:45:00.000+08:00

Connect to port 42 of host.example.com via an HTTP proxy at 10.2.3.4, port 8080.

This example could also be used by ssh(1); see the ProxyCommand directive in ssh_config(5) for more information.

$ nc -x10.2.3.4:8080 -Xconnect host.example.com 42

Solaris: simple port scanning

2011-11-19T21:38:00.005+08:00

PORT SCANNING

It may be useful to know which ports are open and running services on a target machine. The -z flag can be used to tell nc to report open ports, rather than initiate a connection. For example:

$ nc -z host.example.com 20-30
Connection to host.example.com 22 port [tcp/ssh] succeeded!
Connection to host.example.com 25 port [tcp/smtp] succeeded!

The port range was specified to limit the search to ports 20 - 30.

Alternatively, it might be useful to know which server software is running, and which versions. This information is often contained within the greeting banners. In order to retrieve these, it is necessary to first make a connection, and then break the connection when the banner has been retrieved. This can be accomplished by specifying a small timeout with the -w flag, or perhaps by issuing a "QUIT" command to the server:

$ echo "QUIT" | nc host.example.com 20-30
SSH-1.99-OpenSSH_3.6.1p2
Protocol mismatch.
220 host.example.com IMS SMTP Receiver Version 0.84 Ready

Solaris: using nc to transfer file

2011-11-19T21:32:00.001+08:00

DATA TRANSFER

The example in the previous section can be expanded to build a basic data transfermodel. Any information input into one end of the connection will be output to the other end,and input and output can be easily captured in order to emulate file transfer.
 
     Start by using nc to listen on a specific port, with output captured into
     a file:

           $ nc -l 1234 > filename.out

     Using a second machine, connect to the listening nc process, feeding it
     the file which is to be transferred:

           $ nc host.example.com 1234 < filename.in

     After the file has been transferred, the connection will close automati-
     cally.

Solaris: using nc and tar to transfer file between hosts

2011-11-19T21:31:00.001+08:00

If you can't find a way for the controllers to talk to each other (as others have mentioned), you can try doing this:

On your destination server, run the following command:

destination-server# nc -l 9999 | tar xvzf -

Then, on your source server, run the following command:

source-server# tar cvzf -  | nc destination-server-ip 9999

The advantage to this is it avoids any encryption overhead that SSH/rsync gives, so you'll get a bit of a speed boost. This also compresses and decompresses on the source and destination servers in-stream, so it speeds up the transfer process at the expense of some CPU cycles.

CLIENT/SERVER MODEL

It is quite simple to build a very basic client/server model using nc.
     On one console, start nc listening on a specific port for a connection.
     For example:

           $ nc -l 1234

     nc is now listening on port 1234 for a connection.  On a second console
     (or a second machine), connect to the machine and port being listened on:

           $ nc 127.0.0.1 1234

     There should now be a connection between the ports.  Anything typed at
     the second console will be concatenated to the first, and vice-versa.
     After the connection has been set up, nc does not really care which side
     is being used as a `server' and which side is being used as a `client'.
     The connection may be terminated using an EOF (`^D').

Solaris: rsync in parallel

2011-11-19T19:21:00.003+08:00

This does increase the amount of CPU and I/O that both your sending and receiving side use, but I’ve been able to run ~25 parallel instances without remotely degrading the rest of the system or slowing down the other RSYNC instances.

The key is to use the –include and –exclude command line switches to create selection criteria.

Example

drwxr-xr-x 2 root root 179 Jul 19 16:22 directory_a
drwxr-xr-x 2 root root 179 Aug 12 00:08 directory_b
If directory_a has 2,000,000 files underneath it. and directory_b also has 2,000,000 files, use the following idea to split them up. The –exclude option says in essence to “exclude everything that is not explicitly included”.

#!/bin/bash
rsync -av --include="/directory_a*" --exclude="/*" --progress remote::/ /localdir/ > /tmp/myoutputa.log &
rsync -av --include="/directory_b*" --exclude="/*" --progress remote::/ /localdir/ > /tmp/myoutputb.log &
The following will take about twice the amount of time gathering files than the above:

#!/bin/bash
rsync -av --progress remote::/ /localdir/ > /tmp/myoutput.log &

Unix: copy to remote via cpio example

2011-11-19T13:32:00.000+08:00

cpio code for transferring files from one system to another:
for dir in $(cat /dir.txt)#file containing ACL directories
do
cd $dir
find . -print -depth | cpio -omPv | rsh "(cd $dir; cpio -idumvP
)"
done

Solaris: Using rsync to tranfer dir between two hosts

2011-11-19T12:10:00.003+08:00

Transfer data from host3 to host4 via rsync and nfs
hostp3% more copyemea.sh
#! /bin/sh
date> copy.log
/opt/csw/bin/rsync -ar --stats /app/iwstoreEMEA_snap/ /hosta4_EMEA/ 2>&1 >>copy.log
date>> copy.log
hostp3% df -h /hosta4_EMEA
Filesystem size used avail capacity Mounted on
hosta4:/opt/app/data/iw-store/EMEA
250G 134G 116G 54% /hosta4_EMEA
hostp3%
in this case
hosta4#zfs set sharenfs=rw=153.88.177.59,root=153.88.177.59 app/iwstoreEMEA
where

153.88.177.59 is ip address of host3

on host3
host3# mount host4:/opt/app/data/iw-store/EMEA /host4_EMEA
Initial data on host4 must be empty, if not unexpected result might happens. Such as size final transfer > host3 dir

Solaris: ZFS snapshot between two hosts

2011-11-19T11:58:00.000+08:00

Send the initial snapshot and create the filesystem on the remote host

make sure that the receiving host is running Solaris updated after October 2008
make sure the filesystem you are replicating does not exist already on the receving host
zfs snapshot export/upload@zrep-00001 on the origin host
zfs send -i export/upload@zrep-00001 | ssh otherservername "cat > /export/save/upload@zrep-00001"
wait several days depending on the size of the dataset
cat /export/save/upload@rzrepl-00001 | zfs recv export/upload

Statistics: able to complete a transfer of 6.1T in 10 days. (From ms1 (Sun Fire X4500) to ms5 (Sun Fire X4540), both hosts in the same rack.)

Send incremental covering the days that the first step took

zfs snapshot export/upload@zrep-00002 on the origin host
zfs send -i export/upload@zrep-00001 export/upload@zrep-00002 | ssh otherservername "cat > /export/save/upload@zrep-00002"
cat /export/save/upload@rzrepl-00002 | zfs recv export/upload

Solaris 10: How to mount lofs from localzone

2011-11-19T10:37:00.000+08:00

Sol10: How to mount lofs from localzone

On global zone, mounted file system looks like this

/dev/md/dsk/d113 530063064 65560 524696880 1% /zones/myzone/ftp/data2

run this zonecfg command
zonecfg -z myzone
> add fs
> set dir=/ftp/data2
> set special=/zones/myzone/ftp/data2
> set type=lofs
> end
> verify
> commit
> exit

run below command to confirm
#zonecfg -z myzone info
....
fs:
dir: /ftp/data2
special: /zones/myzone/ftp/data2
raw not specified
type: lofs
options: []

....

root@myzone # mount -F lofs /ftp/data2 /ftp/data2

root@myzone # df -k /ftp/data2
Filesystem kbytes used avail capacity Mounted on
/ftp/data2 530063064 65560 524696880 1% /ftp/data2

HPUX/LINUX: NFS mounting

2011-11-19T09:39:00.003+08:00

Exporting and mounting file systems on Linux and HP-UX

If you want to use a shared file system on Linux® and HP-UX systems, you must export it from the system where it is located and mount it on every system on which you want to access it.

You must be logged on as root.

To export and mount file systems on Linux and HP-UX systems, complete these steps:

Export a file system on Linux and HP-UX systems.
1. Add the file system that you want to export to the file ⁄etc⁄exports.
2. Export all entries in the file ⁄etc⁄exports by entering the command ⁄usr⁄sbin⁄exportfs -a.
3. Verify that the file system is exported by entering the command ⁄usr⁄sbin⁄exportfs.
All shared file systems are displayed.
Mount a file system on HP-UX and Linux systems.
1. If the file system that you want to mount is remote, ensure you have the permission to mount it by entering the command⁄usr⁄sbin⁄showmount - e
  where is the name of the remote operating system.
2. Choose an empty file system that serves as the mount point for the file system that you want to mount.If an empty file system does not exist, create it by entering the command mkdir /
  where is the name of the local file system.
3. Mount the file system on your local system by entering the corresponding command.
  - On HP-UX, enter the command/usr/sbin/mount -F nfs sourcehost:/sourcedir /destinationdir
  - On Linux systems, enter the command/bin/mount -t nfs sourcehost:/sourcedir /destinationdir
  where:
  is the name of the remote operating system
  is the name of the remote file system
  is the name of the local file system

To mount the remote file system after each reboot, add it to the /etc/fstab file.For a description of the file format of /etc/fstab, enter the command
man fstab.

example fstab:

server:/mnt /mnt nfs rw,hard 0 0 #mount from server

Solaris nfs throubleshooting

2011-11-18T22:32:00.000+08:00

# showmount -a
     All mount points on local host:
     edcert20.ucs.indiana.edu:/home
     edcert21.ucs.indiana.edu:/usr/local

     # showmount -d
     Directories on local host:
     /home
     /usr/local

     # showmount -e
     Export list on local host
     /home           edcert21.ucs.indiana.edu edcert20.ucs.indiana.edu     
     /usr/local      edcert21.ucs.indiana.edu

# df -F nfs
     Filesystem                      Type  blocks     use   avail %use  Mounted on
     edcert21.ucs.indiana.edu:/home  nfs    68510   55804   12706  81%  /usr/share/help
Use the command nfsstat -s to display NFS activity on the server side. For example:
# nfsstat -s

     Server RPC:
     calls      badcalls   nullrecv   badlen     xdrcall    duphits    dupage
     50852      0          0          0          0          0          0.00    

     Server NFS:
     calls        badcalls     
     50852        0            
     null         getattr      setattr      root         lookup       readlink  
     1  0%        233  0%      0  0%        0  0%        1041  2%     0  0%  
     read         wrcache      write        create       remove       rename    
     49498 97%    0  0%        0  0%        0  0%        0  0%        0  0% 
     link         symlink      mkdir        rmdir        readdir      fsstat 
     0  0%        0  0%        0  0%        0  0%        75  0%       4  0%     
The output may be interpreted using the following guidelines.badcalls > 0 - RPC requests are being rejected by the server. This could indicate authentication problems caused by having a user in too many groups, attempts to access exported file systems as root, or an improper Secure RPC configuration.
nullrecv > 0 - NFS requests are not arriving fast enough to keep all of the nfsd daemons busy. Reduce the number of NFS server daemons until nullrecv is not incremented.
symlink > 10% - Clients are making excessive use of symbolic links that are on file systems exported by the server. Replace the symbolic link with a directory, and mount both the underlying file system and the link's target on the client.
getattr > 60% - Check for non-default attribute caching (noac mount option) on NFS clients.
On the client side use the command nfsstat -c to display the client statistics. For example:# nfsstat -c

     Client RPC:
     calls      badcalls   retrans    badxid     timeout    wait       newcred
     369003     62         1998       43         2053       0          0 

     Client NFS:
     calls        badcalls     nclget       nclsleep     
     368948       0            368948       0            
     null         getattr      setattr      root         lookup       readlink  
     0  0%        51732 14%    680  0%      0  0%        95069 25%    542  0% 
     read         wrcache      write        create       remove       rename 
     210187 56%   0  0%        2259  0%     1117  0%     805  0%      337  0%   
     link         symlink      mkdir        rmdir        readdir      fsstat    
     120  0%      0  0%        7  0%        0  0%        5510  1%     583  0% 
This output may be interpreted using the guidelines given below.timeout > 5% - The client's RPC requests are timing out before the server can answer them, or the requests are not reaching the server. Check badxid to determine the problem.
badxid ~ timeout - RPC requests are being handled by the server, but too slowly. Increase timeo parameter value for this mount, or tune the server to reduce the average request service time.
badxid ~ 0 - With timeouts greater than 3%, this indicates that packets to and from the server are getting lost on the network. Reduce the read and write block sizes (mount parameters rsize andwsize) for this mount.
badxid > 0 - RPC calls on soft-mounted file systems are timing out. If the server is running, and badcalls is growing, then soft mounted file systems should use a larger timeo or retrans value.

Solaris vxvm move a disk group to another system

2011-11-18T22:22:00.000+08:00

Move a disk group to another system

1. Unmount and stop all volumes in the disk group on the first system:

# umount /mntdir
# vxvol -g <diskgroup> stopall

2. Deport (disable all local access to) the disk group to be moved with this command:

# vxdg deport <diskgroup>

3. Import (enable local access to) the disk group and its disks from the second system with:

# vxdg import <diskgroup>

4. After the disk group is imported, start all volumes in the disk group with this command:

# vxrecover -g <diskgroup> -sb

The options here indicate that VERITAS Volume Manager will start all the disabled volumes (-s) in the background (-b).

Solaris : vxfs large file

2011-11-18T22:19:00.000+08:00

How to check for/enable largefile support on vxfs

To check if largefiles are enabled:

# /usr/lib/fs/vxfs/fsadm /mount/pointnolargefiles

Unlike ufs, you can enable vxfs largefile support on the fly with fsadm:

# /usr/lib/fs/vxfs/fsadm -o largefiles /mount/point

Remove a mirror from a volume

Dissociate and remove a mirror (plex) from a volume:

# vxplex [-g diskgroup] -o rm dis plex

This command will remove the mirror (plex) and all associated subdisks.

HPUX LVM mirror

2011-11-18T21:34:00.000+08:00

System Administration Guide for HP-UX 10.20
Part 4 - LVM Disk Mirroring

This note describes how to integrate a second disk into the system volume group and configure it as an alternative boot device, thereby providing LVM mirrored backup for the primary boot device.
Introduction

This note describes how to configure LVM mirroring of a system disk. In this particular example, the HP server is STSRV1, the primary boot device is SCSI=6 (/dev/dsk/c2t6d0) and the alternative mirrored boot device is SCSI=5 (/dev/dsk/c2t5d0). The following commands may be found in /sbin and /usr/sbin must be run as root.

Procedure - Create a System Mirror Disk

This procedure assumes that the HPUX-10.## Operating system and the HPUX LVM mirroring product has already been installed.


# ioscan -fnC disk                                         (identify mirror disk)
# pvcreate -Bf /dev/rdsk/c2t5d0                            (make a bootable physical volume)
# mkboot -l /dev/rdsk/c2t5d0                               (create LVM disk layout)
# mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c2t5d0  (-lq = switch off quorum)
# vgextend /dev/vg00 /dev/dsk/c2t5d0


# for P in 1 2 3 4 5 6 7 8 9 10
> do
> lvextend -m 1 /dev/vg00/lvol$P /dev/dsk/c2t5d0
> sleep 1
> done

Following the mirroring procedure, it is now essential to setup the critical partitions concerning root, swap and boot. It is useful to confirm the partition layout using the commands bdf and lvlnboot.


# bdf -l
# lvlnboot –v

Following changes seen under HPUX-10.20, the / (root) partition will appear first in the listings as /dev/vg00/lvol3 and the /stand (boot) partition will probably be reported as "PV Name" and /dev/vg00/lvol1. The first command below is destructive, in that it removes the "PV Name" boot entry. It should therefore be reinserted using the lvlnboot -b command below. Exercise extreme care with the following commands.


# lvlnboot -r /dev/vg00/lvol3                      (prepare a root LVM logical volume)
# lvlnboot -s /dev/vg00/lvol2                      (prepare a swap LVM logical volume)
# lvlnboot -b /dev/vg00/lvol1                      (prepare a boot LVM logical volume)
# vgcfgbackup vg00
# lifls -C /dev/rdsk/c2t5d0                        (confirms as a boot device)

Disk Crash - D-Class Procedure (Fast Recovery - Hot-Swap Disk )

The example below assumes that the system disk (/dev/dsk/c0t5d0) has crashed and has been replaced by a hot-swap disk (ie. It is not necessary to halt or boot the server). The procedure would be just the same for the mirrored disk as follows :


# pvcreate -Bf /dev/rdsk/c0td50
# vgcfgrestore -n /dev/vg00 /dev/rdsk/c0td50
# vgchange -a y /dev/vg00
# pvcreate -Bf /dev/rdsk/c2t5d0                            (make a bootable physical volume)
# mkboot -l /dev/rdsk/c2t5d0                               (create LVM disk layout)
# mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c2t5d0  (-lq = switch off quorum)
# vgsync /dev/vg00

[NB. It will only be necessary to run the mkboot commands above if it is a system disk replacement.]

When the synchronisation of the logical volumes is complete, reconfirm the following :


# lvlnboot -r /dev/vg00/lvol3                      (prepare a root LVM logical volume)
# lvlnboot -s /dev/vg00/lvol2                      (prepare a swap LVM logical volume)
# lvlnboot -b /dev/vg00/lvol1                      (prepare a boot LVM logical volume)
# vgcfgbackup vg00

Disk Crash - Night Procedure (Fast Recovery - No Disk Replacement)

The example below assumes that the system disk (/dev/dsk/c2t6d0) has crashed and has NOT been replaced. The procedure, however, would be just the same for a mirrored disk crash with the exception of the change in device name. Due to the quorum philosophy, in that half the disk space is now no longer available, it is necessary to boot up in single-user mode with the quorum argument unset as follows :

1.Escape from boot sequence
2. Choose mirrored disk (ie. P0 = /dev/dsk/c2td50)
3. Boot up in single user mode, without quorum, as follows :

... Select from menu : b P0 isl

ISL > hpux -is -lq (;0)/stand/vmunix


# init 4

Disk Crash - Day Procedure (Slow Recovery - Intrnal Disk Replacement)

The example below assumes that the system disk (/dev/dsk/c2t6d0) has crashed and been replaced. The procedure, however, would be just the same for a mirrored disk crash with the exception of the change in device name. Due to the quorum philosophy, in that half the disk space is now not available, it is necessary to boot up in single-user mode with the quorum argument unset as follows :

1. Escape from boot sequence
2. Choose mirrored disk (ie. P0 = /dev/dsk/c2td50)
3. Boot up in single user mode, without quorum, as follows :

... Select from menu : b p0 isl

ISL > hpux -is -lq (;0)/stand/vmunix


# PATH=$PATH:/sbin:/usr/sbin
# mount -a
# pvcreate -Bf /dev/rdsk/c2t6d0
# mkboot -l /dev/rdsk/c2t6d0
# mkboot -a "hpux (;0) /stand/vmunix" /dev/rdsk/c2t6d0
# vgcfgrestore -n /dev/vg00 /dev/rdsk/c2td60
# vgchange -a y /dev/vg00
# lvlnboot -r /dev/vg00/lvol3                      (prepare a root LVM logical volume)
# lvlnboot -s /dev/vg00/lvol2                      (prepare a swap LVM logical volume)
# lvlnboot -b /dev/vg00/lvol1                      (prepare a boot LVM logical volume)
# init 4

The machine will now boot up correctly and the disks will synchronize automatically. The replaced system disk will now mirror automatically from the original mirrored disk. There will be considerable disk activity at this time and the progress of the mirroring may be confirmed with :


# lvdisplay -v /dev/vg00/lvol1

This will probably show that the first volume is "current" and therefore successfully mirrored.


# lvdisplay -v /dev/vg00/lvol8

This will almost certainly show that the volume is "stale" and therefore not yet mirrored. When the disks are synchronized, reboot the machine, thereby ensuring that the future is secure and the original "primary boot path" is valid.

Procedure - Remove a Mirrored System DiskEssentially the reverse of the procedure above.


# for P in 1 2 3 4 5 6 7 8 9 10
> do
> lvreduce -m 0 /dev/vg00/lvol$P /dev/dsk/c2t5d0
> sleep 1
> done
# vgreduce /dev/vg00 /dev/dsk/c2t5d0

HPUX: Mirroring boot disks

2011-11-18T21:29:00.001+08:00

PA-RISC Mirroring procedures

Use ioscan to identify a suitable alternate boot disk. The disk should be about the same size as the primary boot disk and, preferably, on a separate I/O channel. When I do this, I typically set up variables for the character and block devices. The example commands that follow use that syntax.
Create the boot partitions on the disk. The args to ignore quorum are used on the hpux command. If you're booting off of the alternate boot disk, there's a better than even chance your primary isn't there anymore...
1. pvcreate -B ${rdsk}
2. mkboot ${rdsk}
3. mkboot -a "hpux -lq" ${rdsk}
Add the disk to vg00 - or where ever your OS is
vgextend vg00 ${dsk}
Extend the logical volumes. I typically use an inline function for this:
```
for lv in $(vgdisplay -v vg00 | grep -i 'lv name' | awk '{print $NF}')
do
    echo "#################################"
    echo ${lv}
    lvextend -m 1 ${lv} ${dsk}
done
```
NOTE: Each of the lvs can take awhile particularly if they're sizeable. I will usually create a function in another window that tells me how many logical extents are stale. Rerunning the function will hopefully show a decreasing number of extents.
```
hm()
{  lvdisplay -v $1 | sed -n -e '/Logical extents/,$p' | grep stale | wc -l
}
```

Verification:

Use setboot to verify the alternate boot or HA alternate boot, as appropriate, is set:

# setboot
Primary bootpath : 0/1/1/0.1.0
HA Alternate bootpath : 0/1/1/0.0.0
Alternate bootpath : 0/1/1/0.1.0

Autoboot is ON (enabled)

Use lvlnboot to verify the alternate boot disk is configured. Use lvlnboot -R /dev/vg00 to update.

# lvlnboot -v vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
        /dev/dsk/c2t1d0s2 (0/1/1/0.1.0) -- Boot Disk
        /dev/dsk/c2t0d0s2 (0/1/1/0.0.0) -- Boot Disk
Boot: lvol1     on:     /dev/dsk/c2t1d0s2
                        /dev/dsk/c2t0d0s2
Root: lvol3     on:     /dev/dsk/c2t1d0s2
                        /dev/dsk/c2t0d0s2
Swap: lvol2     on:     /dev/dsk/c2t1d0s2
                        /dev/dsk/c2t0d0s2
Dump: lvol2     on:     /dev/dsk/c2t1d0s2, 0

Itanium mirroring procedure

As stated previously, the ia64 mirroring procedure is quite different. Using the old disk naming schemes, you will end up creating disk partitions, ${rdsk}s2, for instance. The new naming conventions create partitions named /dev/rdisk/disk#_p#. The directions below demonstrate the legacy naming convention. The commands are the same for the new naming convention.

Use ioscan to identify a suitable alternate boot disk. The disk should be about the same size as the primary boot disk and, preferably, on a separate I/O channel. When I do this, I typically set up variables for the character and block devices. The example commands that follow use that syntax.
Create the boot partition on the disk and generate the partition device files:
1. Create the partition template:
```
 cat > /tmp/part << eof
> 3
> EFI 500MB
> HPUX 100%
> HPSP 400MB
> eof
```
2. idisk -f /tmp/part -w ${rdsk}
3. Verify the partitions: idisk ${rdsk}
4. Create the device files: insf -eH ${hw_path}
Create and populate the boot partitions:
1. pvcreate -B ${rdsk}s2 NOTE: the s2 partition
2. mkboot -e -l ${rdsk}
3. mkboot -a "boot vmunix -lq" ${dsk} NOTE: *not* rdsk
vgextend vg00 ${dsk}s2 #note the s2 partition again
Extend the logical volumes. I typically use an inline function for this:
```
for lv in $(vgdisplay -v vg00 | grep -i 'lv name' | awk '{print $NF}')
do
    echo "#################################"
    echo ${lv}
    lvextend -m 1 ${lv} ${dsk}s2 # note the s2 partition again
done
```
NOTE: Each of the lvs can take awhile particularly if they're sizeable. I will usually create a function in another window that tells me how many logical extents are stale. Rerunning the function will hopefully show a decreasing number of extents.
```
hm()
{  lvdisplay -v $1 | sed -n -e '/Logical extents/,$p' | grep stale | wc -l
}
```

Verification:

Use setboot to verify the alternate boot or HA alternate boot, as appropriate, is set:

# setboot
Primary bootpath : 0/1/1/0.1.0
HA Alternate bootpath : 0/1/1/0.0.0
Alternate bootpath : 0/1/1/0.1.0

Autoboot is ON (enabled)

Use lvlnboot to verify the alternate boot disk is configured. Use lvlnboot -R vg00 to update.

# lvlnboot -v vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
        /dev/dsk/c2t1d0s2 (0/1/1/0.1.0) -- Boot Disk
        /dev/dsk/c2t0d0s2 (0/1/1/0.0.0) -- Boot Disk
Boot: lvol1     on:     /dev/dsk/c2t1d0s2
                        /dev/dsk/c2t0d0s2
Root: lvol3     on:     /dev/dsk/c2t1d0s2
                        /dev/dsk/c2t0d0s2
Swap: lvol2     on:     /dev/dsk/c2t1d0s2
                        /dev/dsk/c2t0d0s2
Dump: lvol2     on:     /dev/dsk/c2t1d0s2, 0

Update the boot loaderThis part is still a bit confusing for me. The alternate boot option in the efi boot menu points to the right disk; however, it doesn't know about the hpux.efi boot command so it doesn't work. You'd figure HP would make that a bit more automatic.
So, note the hardware paths for the primary and alternate disks, then boot to the efi menu. Boot configuration -> Add a boot option,
Identify your new mirror disk. when it says (pun1,lun0), that's going to be c#t1d0, (pun0,lun) will be c#t0d0, etc. Highlight the suspected mirror disk and press [enter]
Assuming you got the right disk, you should be looking at something that looks like an old norton commander menu. Highlight EFI, press [enter], then highlight HPUX, press [enter], and finally, hpux.efi and (you guessed it), press [enter]. Enter a good description for the mirror disk.
If you want, move the mirror disk entry to the top using the other options in the boot options menu. Once done, select the mirror disk entry to attempt to boot from it.
Troubleshoot as necessary

Taken from:

URL:	http://olearycomputers.com/ll/hpux_mirror.html

Solaris zfs pool command example

2011-11-18T11:30:00.001+08:00

# zpool history
History for 'app':
2010-05-18.05:01:14 zpool create app c3t60060E80056F110000006F110000669Cd0
2010-05-18.05:04:04 zfs set mountpoint=/opt/app app
2010-05-18.05:05:36 zfs set mountpoint=/opt/app app
2010-05-18.05:09:55 zfs create app/iwstoreAPAC
2010-05-18.05:10:00 zfs create app/iwstoreEMEA
2010-05-18.05:10:07 zfs create app/iwstoreAmericas
2010-05-18.05:10:44 zfs set mountpoint=/opt/app/data/iw-store/APAC app/iwstoreAPAC
2010-05-18.05:10:59 zfs set mountpoint=/opt/app/data/iw-store/EMEA app/iwstoreEMEA
2010-05-18.05:11:19 zfs set mountpoint=/opt/app/data/iw-store/Americas app/iwstoreAmericas
2010-05-18.05:12:44 zfs set quota=50GB app/iwstoreAPAC
2010-05-18.05:12:55 zfs set quota=100GB app/iwstoreEMEA
2010-05-18.05:13:05 zfs set quota=200GB app/iwstoreAmericas
2010-05-18.05:14:02 zfs set quota=100GB app
2010-05-18.05:15:05 zfs destroy app/iwstoreAPAC
2010-05-18.05:15:11 zfs destroy app/iwstoreEMEA
2010-05-18.05:15:18 zfs destroy app/iwstoreAmericas
2010-05-18.05:15:53 zfs set quota=none app
2010-05-18.05:16:14 zfs create app/opt
2010-05-18.05:18:04 zfs destroy app/opt
2010-05-18.05:18:32 zfs create app/optapp
2010-05-18.05:18:49 zfs set mountpoint=/opt/app app/optapp
2010-05-18.05:19:25 zfs set mountpoint=/opt/app app/optapp
2010-05-18.05:20:02 zfs set mountpoint=none app
2010-05-18.05:20:09 zfs set mountpoint=/opt/app app/optapp
2010-05-18.05:22:31 zfs create app/optapp/iwstoreAPAC
2010-05-18.05:22:36 zfs create app/optapp/iwstoreEMEA
2010-05-18.05:22:42 zfs create app/optapp/iwstoreAmericas
2010-05-18.05:23:04 zfs set mountpoint=/opt/app/data/iw-store/APAC app/optapp/iwstoreAPAC
2010-05-18.05:23:16 zfs set mountpoint=/opt/app/data/iw-store/EMEA app/optapp/iwstoreEMEA
2010-05-18.05:23:34 zfs set mountpoint=/opt/app/data/iw-store/Americas app/optapp/iwstoreAmericas
2010-05-18.05:24:06 zfs set quota=50GB app/optapp/iwstoreAPAC
2010-05-18.05:24:18 zfs set quota=100GB app/optapp/iwstoreEMEA
2010-05-18.05:24:31 zfs set quota=200GB app/optapp/iwstoreAmericas
2010-05-18.05:24:56 zfs set quota=100GB app/optapp
2010-05-18.05:25:24 zfs set quota=200GB app/optapp/iwstoreAmericas
2010-05-18.05:26:05 zfs set quota=200GB app/optapp
2010-05-18.05:26:12 zfs set quota=200GB app/optapp/iwstoreAmericas
2010-05-18.05:29:52 zfs rename app/optapp/iwstoreAPAC app/iwstoreAPAC
2010-05-18.05:30:18 zfs rename app/optapp/iwstoreEMEA app/iwstoreEMEA
2010-05-18.05:30:42 zfs rename app/optapp/iwstoreAmericas app/iwstoreAmericas
2010-05-18.05:31:07 zfs set quota=100GB app/optapp
2010-08-02.16:11:29 zfs set quota=250G app/iwstoreEMEA
2010-08-30.14:34:21 zfs set quota=50gb app/iwstoreAmericas
2010-08-30.14:34:37 zfs set quota=100gb app/iwstoreAPAC
2011-10-27.12:35:41 zfs set sharenfs=rw=@153.88.177.59,root=@153.88.177.59 app/iwstoreAPAC
2011-10-27.12:47:57 zfs set sharenfs=rw=@153.88.177.0/24,root=@153.88.177.0/24 app/iwstoreAPAC
2011-10-27.12:54:22 zfs set sharenfs=rw=@153.88.177.0/24,root=@153.88.177.0/24 app/iwstoreAmericas
2011-10-27.12:54:37 zfs set sharenfs=rw=@153.88.177.0/24,root=@153.88.177.0/24 app/iwstoreEMEA

#

Solaris Sending a ZFS Snapshot

2011-11-18T08:43:00.000+08:00

Sending a ZFS Snapshot

You can use the zfs send command to send a copy of a snapshot stream and receive the snapshot stream in another pool on the same system or in another pool on a different system that is used to store backup data. For example, to send the snapshot stream on a different pool to the same system, use syntax similar to the following:

# zfs send tank/dana@snap1 | zfs recv spool/ds01

You can use zfs recv as an alias for the zfs receive command.

If you are sending the snapshot stream to a different system, pipe the zfs send output through the ssh command. For example:

host1# zfs send tank/dana@snap1 | ssh host2 zfs recv newtank/dana

When you send a full stream, the destination file system must not exist.

You can send incremental data by using the zfs send -i option. For example:

host1# zfs send -i tank/dana@snap1 tank/dana@snap2 | ssh host2 zfs recv newtank/dana

Solaris Remote Replication of ZFS Dat

2011-11-18T08:32:00.001+08:00

Remote Replication of ZFS Data

You can use the zfs send and zfs recv commands to remotely copy a snapshot stream representation from one system to another system. For example:

This command sends the tank/cindy@today snapshot data and receives it into the sandbox/restfs file system and also creates arestfs@today snapshot on the newsys system. In this example, the user has been configured to use ssh on the remote system.

# zfs send tank/cindy@today | ssh newsys zfs recv sandbox/restfs@today

Solaris : ZFS clone 2

2011-11-18T08:23:00.000+08:00

# zfs snapshot mypool/myfs@now
# zfs send mypool/myfs@now | zfs receive anotherpool/anotherfs
\\another fs will automatically be created. It is now copying all data. 1.5TB

1) machine0$ zfs send mypool/myfs@now | ssh machine1 zfs receive anotherpool/anotherfs@anothersnap
2) machine0$ zfs send mypool/myfs@now | zfs receive anotherpool/anotherfs@anothersnap

Solaris: zfs snapshot

2011-11-18T07:55:00.001+08:00

ZFS is a great filesystem. Amongst its many features, it has snapshots. Let’s see how to use them.

What are snapshots ?

Snapshots are instant copies of your filesystem at a fixed past time. They are designed so that they are lightning fast to create, and they use a minimal amount of disk thanks to the COW (Copy On Write) optimization.

Basically, when you take a snapshot of a ZFS filesystem, only the filesystem structure is copied, not the file data blocks. Afterwards, anytime the data of a file is going to be modified, the data block is copied first the snapshot will reference the copy instead of the current data block. This is the Copy-On-Write.

The volume occupied by the snapshot is merely the volume of the data blocks which have been modified since the snapshot was taken.

Snapshots in ZFS

To create a snapshot, issue the following command :
prodigy# zfs snapshot poolName/fileSystem@labelName

You can see that the snapshot was taken with zfs list :

# zfs list
NAME                          USED  AVAIL  REFER  MOUNTPOINT
poolName                       5.63G   141G  27.5K  /poolName
poolName/fileSystem       2.97G   141G  1.92G  /poolName/fileSystem
poolName/fileSystem@label           0      -  1.92G  -
prodigy#

To access the files of the snapshot, you can simply go in the .zfs/snapshot directory which is at the top level of your fileSystem. Take care, the .zfs directory is invisible by default.

At last, to delete the snapshot, simply use the zfs destroy command :

# zfs destroy poolName/fileSystem@label
#

The following syntax creates recursive snapshots of all home directories in the tank/home file system. Then, you can use the zfs send -R command to create a recursive stream of the recursive home directory snapshot, which also includes the individual file system property settings.

# zfs snapshot -r tank/home@monday
# zfs send -R tank/home/@monday | ssh remote-system zfs receive -dvu pool
ZFS Clone
Clones can be only created from snapshot and they are actually new FS with initial content as original FS, so they are writable. 

# zfs list
NAME                       USED  AVAIL  REFER  MOUNTPOINT
mypool                    1.49G   527M   528M  /mypool
mypool/home                993M   527M    20K  /mypool/home
mypool/home/user1          993M   527M   993M  /mypool/home/user1
mypool/home/user1@Monday      0      -   993M  -

# zfs clone mypool/home/user1@Monday mypool/home/user2

# zfs list
NAME                       USED  AVAIL  REFER  MOUNTPOINT
mypool                    1.49G   527M   528M  /mypool
mypool/home                993M   527M    20K  /mypool/home
mypool/home/user1          993M   527M   993M  /mypool/home/user1
mypool/home/user1@Monday      0      -   993M  -
mypool/home/user2             0   527M   993M  /mypool/home/user2
Once clone is created from snapshot, the snapshot can not be deleted until clone exists.  # zfs get origin mypool/home/user2
NAME               PROPERTY  VALUE                      SOURCE
mypool/home/user2  origin    mypool/home/user1@Monday  -

# zfs destroy mypool/home/user1@Monday
cannot destroy 'mypool/home/user1@Monday': snapshot has dependent clones
use '-R' to destroy the following datasets:
mypool/home/user2
ZFS Snapshot
ZFS snapshot is read-only copy of the file system. 

When taken, it consumes no additional disk space, but when data changes, snapshot is growing since references to old data (unique to snapshot), so space cannot be freed. 

Let's take snapshot of FS mypool/home/user1. Snapshot name is Monday. So you can see what's command's syntax. 

# zfs snapshot mypool/home/user1@Monday

# zfs list
NAME                       USED  AVAIL  REFER  MOUNTPOINT
mypool                    1.49G   527M   528M  /mypool
mypool/home                993M   527M    20K  /mypool/home
mypool/home/user1          993M   527M   993M  /mypool/home/user1
mypool/home/user1@Monday      0      -   993M  -   (consumes no additional data within zpool)
You even cannot destroy FS if it has any snapshot. # zfs destroy mypool/home/user1
cannot destroy 'mypool/home/user1': filesystem has children
use '-r' to destroy the following datasets:
mypool/home/user1@Monday
Let’s change some data and see now that used data of snapshot is growing. # zfs list
NAME                       USED  AVAIL  REFER  MOUNTPOINT
mypool                    1.49G   527M   528M  /mypool
mypool/home                993M   527M    20K  /mypool/home
mypool/home/user1          993M   527M   993M  /mypool/home/user1
mypool/home/user1@Monday    28K      -   993M  -
Snapshot(s) is stored in hidden directory named .zfs/snapshot/, located in the root of FS. So you can go there and restore files if needed, remember it is read-only copy of FS. # /mypool/home/user1/.zfs/snapshot> ls
total 3
dr-xr-xr-x   2 root     root           2 Nov 16 13:23 .
dr-xr-xr-x   3 root     root           3 Nov 16 13:23 ..
drwxr-xr-x   3 root     root           6 Nov 16 17:09 Monday
Beside restoring individual files from snapshot, you can roll back whole FS to previously taken snapshot. # zfs list -t snapshot
NAME                       USED  AVAIL  REFER  MOUNTPOINT
mypool/home/user1@Monday   993M      -   993M  -

# zfs rollback mypool/home/user1@Monday
And all changes since snapshot Monday has been taken up to now are deleted and FS is same as it was on that Monday.

Solaris: Rsync example

2011-11-17T23:56:00.000+08:00

Backing up data using rsync command

rsync is a great tool for backing up and restoring files. I'll use some example to explain on how it works.

Example of the remote server and folder that needs to be backup or copied:
Remote host name: server01.comentum.com
Remote folder: /home/user01/
Remote user: user01

rsync example for backing up / copying from remote server to local Linux computer:
rsync -arv user01@server01.comentum.com:/home/user01/ /home/bob/user01backup/
(/home/bob/user01backup/ is a local Linux folder path)

rsync example for backing up / copying from remote server to local Mac computer:
rsync -arv user01@server01.comentum.com:/home/user01/ /Users/bob/user01backup/
(/Users/bob/user01backup/ is a local Mac folder path)

rsync example for backing up / copying from remote server to local Mac computer and external USB drive:
rsync -arv user01@server01.comentum.com:/home/user01/ /Volumes/westerndigital-usb/user01backup/
(/Volumes/westerndigital-usb/user01backup/ is an external USB Drive path on a local Mac computer)

Here is what the "-arv" option does:
a = archive - means it preserves permissions (owners, groups), times, symbolic links, and devices.
r = recursive - means it copies directories and sub directories
v = verbose - means that it prints on the screen what is being copied

More Examples:
rsync -rv user01@server01.comentum.com:/home/user01/ /home/bob/user01backup/
(This example will copy folders and sub-folder but will not preserve permissions, times and symbolic links during the transfer)

rsync -arv --exclude 'logs' user01@server01.comentum.com:/home/user01/ /Users/bob/user01backup/
(This example will copy everything (folders, sub-folders, etc), will preserver permissions, times, links, but will exclude the folder /home/user01/logs/ from being copied)

Use of "/" at the end of path:
When using "/" at the end of source, rsync will copy the content of the last folder.
When not using "/" at the end of source, rsync will copy the last folder and the content of the folder.

When using "/" at the end of destination, rsync will paste the data inside the last folder.
When not using "/" at the end of destination, rsync will create a folder with the last destination folder name and paste the data inside that folder.

OPTIONS SUMMARY
       Here is a short summary of the options available in rsync. 

        -v, --verbose               increase verbosity
        -q, --quiet                 suppress non-error messages
            --no-motd               suppress daemon-mode MOTD (see caveat)
        -c, --checksum              skip based on checksum, not mod-time & size
        -a, --archive               archive mode; equals -rlptgoD (no -H,-A,-X)
            --no-OPTION             turn off an implied OPTION (e.g. --no-D)
        -r, --recursive             recurse into directories
        -R, --relative              use relative path names
            --no-implied-dirs       don’t send implied dirs with --relative
        -b, --backup                make backups (see --suffix & --backup-dir)
            --backup-dir=DIR        make backups into hierarchy based in DIR
            --suffix=SUFFIX         backup suffix (default ~ w/o --backup-dir)
        -u, --update                skip files that are newer on the receiver
            --inplace               update destination files in-place
            --append                append data onto shorter files
            --append-verify         --append w/old data in file checksum
        -d, --dirs                  transfer directories without recursing
        -l, --links                 copy symlinks as symlinks
        -L, --copy-links            transform symlink into referent file/dir
            --copy-unsafe-links     only "unsafe" symlinks are transformed
            --safe-links            ignore symlinks that point outside the tree
        -k, --copy-dirlinks         transform symlink to dir into referent dir
        -K, --keep-dirlinks         treat symlinked dir on receiver as dir
        -H, --hard-links            preserve hard links
        -p, --perms                 preserve permissions
        -E, --executability         preserve executability
            --chmod=CHMOD           affect file and/or directory permissions
        -A, --acls                  preserve ACLs (implies -p)
        -X, --xattrs                preserve extended attributes
        -o, --owner                 preserve owner (super-user only)
        -g, --group                 preserve group
            --devices               preserve device files (super-user only)
            --specials              preserve special files
        -D                          same as --devices --specials
        -t, --times                 preserve modification times
        -O, --omit-dir-times        omit directories from --times
            --super                 receiver attempts super-user activities
            --fake-super            store/recover privileged attrs using xattrs
        -S, --sparse                handle sparse files efficiently
        -n, --dry-run               perform a trial run with no changes made
        -W, --whole-file            copy files whole (w/o delta-xfer algorithm)
        -x, --one-file-system       don’t cross filesystem boundaries
        -B, --block-size=SIZE       force a fixed checksum block-size
        -e, --rsh=COMMAND           specify the remote shell to use
            --rsync-path=PROGRAM    specify the rsync to run on remote machine
            --existing              skip creating new files on receiver
            --ignore-existing       skip updating files that exist on receiver
            --remove-source-files   sender removes synchronized files (non-dir)
            --del                   an alias for --delete-during
            --delete                delete extraneous files from dest dirs
            --delete-before         receiver deletes before transfer (default)
            --delete-during         receiver deletes during xfer, not before
            --delete-delay          find deletions during, delete after
            --delete-after          receiver deletes after transfer, not before
            --delete-excluded       also delete excluded files from dest dirs
            --ignore-errors         delete even if there are I/O errors
            --force                 force deletion of dirs even if not empty
            --max-delete=NUM        don’t delete more than NUM files
            --max-size=SIZE         don’t transfer any file larger than SIZE
            --min-size=SIZE         don’t transfer any file smaller than SIZE
            --partial               keep partially transferred files
            --partial-dir=DIR       put a partially transferred file into DIR
            --delay-updates         put all updated files into place at end
        -m, --prune-empty-dirs      prune empty directory chains from file-list
            --numeric-ids           don’t map uid/gid values by user/group name
            --timeout=SECONDS       set I/O timeout in seconds
            --contimeout=SECONDS    set daemon connection timeout in seconds
        -I, --ignore-times          don’t skip files that match size and time
            --size-only             skip files that match in size
            --modify-window=NUM     compare mod-times with reduced accuracy
        -T, --temp-dir=DIR          create temporary files in directory DIR
        -y, --fuzzy                 find similar file for basis if no dest file
            --compare-dest=DIR      also compare received files relative to DIR
            --copy-dest=DIR         ... and include copies of unchanged files
            --link-dest=DIR         hardlink to files in DIR when unchanged
        -z, --compress              compress file data during the transfer
            --compress-level=NUM    explicitly set compression level
            --skip-compress=LIST    skip compressing files with suffix in LIST
        -C, --cvs-exclude           auto-ignore files in the same way CVS does
        -f, --filter=RULE           add a file-filtering RULE
        -F                          same as --filter=’dir-merge /.rsync-filter’
                                    repeated: --filter=’- .rsync-filter’
            --exclude=PATTERN       exclude files matching PATTERN
            --exclude-from=FILE     read exclude patterns from FILE
            --include=PATTERN       don’t exclude files matching PATTERN
            --include-from=FILE     read include patterns from FILE
            --files-from=FILE       read list of source-file names from FILE
        -0, --from0                 all *from/filter files are delimited by 0s
        -s, --protect-args          no space-splitting; wildcard chars only
            --address=ADDRESS       bind address for outgoing socket to daemon
            --port=PORT             specify double-colon alternate port number
            --sockopts=OPTIONS      specify custom TCP options
            --blocking-io           use blocking I/O for the remote shell
            --stats                 give some file-transfer stats
        -8, --8-bit-output          leave high-bit chars unescaped in output
        -h, --human-readable        output numbers in a human-readable format
            --progress              show progress during transfer
        -P                          same as --partial --progress
        -i, --itemize-changes       output a change-summary for all updates
            --out-format=FORMAT     output updates using the specified FORMAT
            --log-file=FILE         log what we’re doing to the specified FILE
            --log-file-format=FMT   log updates using the specified FMT
            --password-file=FILE    read daemon-access password from FILE
            --list-only             list the files instead of copying them
            --bwlimit=KBPS          limit I/O bandwidth; KBytes per second
            --write-batch=FILE      write a batched update to FILE
            --only-write-batch=FILE like --write-batch but w/o updating dest
            --read-batch=FILE       read a batched update from FILE
            --protocol=NUM          force an older protocol version to be used
            --iconv=CONVERT_SPEC    request charset conversion of filenames
            --checksum-seed=NUM     set block/file checksum seed (advanced)
        -4, --ipv4                  prefer IPv4
        -6, --ipv6                  prefer IPv6
            --version               print version number
       (-h) --help                  show this help (see below for -h comment)

       Rsync can also be run as a daemon, in which case the following options are accepted:
       Rsync can also be run as a daemon, in which case the following options are accepted:

            --daemon                run as an rsync daemon
            --address=ADDRESS       bind to the specified address
            --bwlimit=KBPS          limit I/O bandwidth; KBytes per second
            --config=FILE           specify alternate rsyncd.conf file
            --no-detach             do not detach from the parent
            --port=PORT             listen on alternate port number
            --log-file=FILE         override the "log file" setting
            --log-file-format=FMT   override the "log format" setting
            --sockopts=OPTIONS      specify custom TCP options
        -v, --verbose               increase verbosity
        -4, --ipv4                  prefer IPv4
        -6, --ipv6                  prefer IPv6
        -h, --help                  show this help (if used after --daemon)

Solaris: Enable Non Expiry Passwd For Uid

2011-11-16T11:51:00.000+08:00

server0084# passwd -s partsftp
partsftp PS 10/20/11 7 84 28
server0084# passwd -x -1 partsftp
passwd: password information changed for partsftp
server0084# passwd -s partsftp
partsftp PS
server0084#

server0085# id -a partsftp
uid=8457821(partsftp) gid=45046(partsftp) groups=45046(partsftp)
server0085# passwd -s partsftp
partsftp PS 10/20/11 7 84 28
server0085# passwd -x -1 partsftp
passwd: password information changed for partsftp
server0085# passwd -s partsftp
partsftp PS
server0085#

HPUX: NFS Configuration

2011-11-15T21:51:00.002+08:00

An HP-UX 10.x system is an NFS client by default. It can become as NFS server either through SAM or through modifications
to /etc/rc.config.d/nfsconf.
Set the following variable to 1:
NFS_SERVER=1 # Is this machine a server?
Set the number of nfsd processes with the NUM_NFSD and nfs bio with NUM_NFSIOD variables:
NUM_NFSD=30
NUM_NFSIO=16
NOTE: The number of nfsd processes you need depends on several factors.

The /etc/exports file is processed automatically at boot time. Entries in /etc/exports look something like this:
/reports -access=sun.ucs.indiana.edu, rw=teak.uwsg.indiana.edu /usr/man -ro,access=chrome:copper:zinc,root=chrome
If the /etc/exports file is modified the exportfs command must be run for the changes to take effect immediately.exportfs -u can be used to remove file systems from the export list.

See if the NFS client can see the exports list of the NFS Server:

# /usr/sbin/showmount -e nfs-server

For example:

# /usr/sbin/showmount -e nfs-server

To see this example, go to
ftp://ftp.hp.com/pub/enterprise/programming_code/c00867456_rpcinfo_examples.txt

Verify the export list is correct. If not, log into the server and examine the /etc/exports file. If it contains entries that you do not see in the showmount -e listing, then re-export them as follows:

# /usr/sbin/exportfs -av

For example:

# /usr/sbin/exportfs -av re-exported /home

To see the re-export example, go to
ftp://ftp.hp.com/pub/enterprise/programming_code/c00867456_exportfs_example.txt

See what files the NFS Client has mounted from the NFS Server:

NOTE: CAUTION! If you use "bdf" it causes an NFS "fsinfo" request to the NFS Server, which can cause the bdf command to hang if there are any problems! Use the "mount" command instead.

HPUX: gsp check system temperature

2011-11-11T15:56:00.003+08:00

howto check houx system tempereture
[hpserver-gsp] MP:CM> ?

HE

==== MP Help: Main Menu =======================================================

Hardware Revision a5 Firmware Revision E.03.15 Feb 18 2005,20:09:34

Integrated Lights-Out for HP Integrity and HP 9000 - Management Processor (MP)

MP Help System

Use Ctrl-B to exit MP command interface and return to the main MP menu.

Enter a command at the help prompt:
OVerview : Launch the help overview
LIst : Show the list of MP Command Menu commands
: Enter the command name for help on individual command
TOPics : Show all MP Help topics and commands
HElp : Display this screen
Q : Quit help

====
MP:HE> List
List
==== MP Help: Command Menu List =============================================

BP : Reset BMC Passwords MS : Modem Status
CA : Configure asynch/serial ports PC : Remote Power Control
DATE: Display Date PG : PaGing parameters setup
DC : Default Configuration PR : Power Restore Policy Config.
DF : Display FRU Information PS : Power management module Status
DI : DIsconnect users RB : Reset BMC
DNS : Configure DHCP and DNS RS : Reset System through RST signal
FW : Upgrade MP firmware SA : Set MP Access
HE : Display Help SO : Security Options
ID : System Information SS : System processors Status
IT : Modify MP inactivity timeouts SYSREV: Display System firmware Revs.
LC : Configure LAN, SSH and Web ports TC : Reset system via INIT
LDAP: Configure LDAP parameters TE : TEll- send a msg. to other users
LM : License Management UC : User Configuration
LOC : Locator LED display WHO : Display connected MP users
LS : LAN Status XD : Diagnostics and reset of MP
MR : Modem Reset

====
(HE for main help, enter command name, or Q to quit)
MP:HE> PS
PS

==== MP Help: Status ==========================================================

PS : Power Status- display the status of the Power Management Module

Command access level: Login access.

This command displays the following information: system power state and
temperature, status of the power supplies and fans.

Command line usage:
PS [ -nc ]

SEE ALSO: PC, SS (Power Control, System Status)

login to gsp

====
(HE for main help, enter command name, or Q to quit)
MP:HE> q
q

[hpserver-gsp] MP:CM> ps

PS
System Power state: On
Temperature : Normal

Power supplies State
-----------------------------------------------------------
Power Supply 1 Normal
Power Supply 2 Normal

Fans State
-----------------------------------------------------------
Fan1A (CPU) Normal
Fan1B (CPU) Normal
Fan2 (Memory) Normal
Fan3 (I/O) Normal
CPU0 Fan Normal
CPU1 Fan Normal

[hpserver-gsp] MP:CM>

HPUX : PCIe_SAS_SmartArray_P800_RAID_Controller_Firmware upgrade

2011-11-11T15:46:00.002+08:00

implementation step

On OS shell run command
root@hpuxserver # pwd
/root/home/root/PCIe_SAS_SmartArray_P800_RAID_Controller_Firmware

root@hpuxserver #sautil /dev/ciss2 -s
...
Firmware Revision (in ROM).......... 4.12
...

root@hpuxserver #sautil /dev/ciss2 download_ctlr_fw p400-e500-p800-522.pak
root@hpuxserver #sautil /dev/ciss2 -s
...
Firmware Revision (in ROM).......... 5.22

verify step

root@hpuxserver : /root/home/root -> sautil /dev/ciss2 -s
....
....
Firmware Revision (in ROM).......... 4.12 <---- should be 5.22
.....

before

root@hpuxserver : /root/home/root -> sautil /dev/ciss2 -s

******************************************************************************
**** ****
**** S A U T I L S u p p o r t U t i l i t y ****
**** ****
**** for the HP SmartArray RAID Controller Family ****
**** ****
**** version A.02.13 ****
**** ****
**** (C) Copyright 2003-2007 Hewlett-Packard Development Company, L.P. ****
******************************************************************************

---- DRIVER INFORMATION ------------------------------------------------------

Driver State........................ READY

---- CONTROLLER INFORMATION --------------------------------------------------

Controller Product Number........... P800
Controller Product Name............. HP PCIe SmartArray P800
Hardware Path....................... 0/7/0/0/0/0
Serial Number....................... P98690K9SW20FP
Device File......................... /dev/ciss2
Hardware Revision................... 'D'
Firmware Revision (in ROM).......... 4.12
# of Logical Drives................. 5
# of Physical Disks Configured...... 20
# of Physical Disks Detected........ 20

root@hpuxserver : /root/home/root/PCIe_SAS_SmartArray_P800_RAID_Controller_Firmware -> sautil /dev/ciss2 download_ctlr_fw p400-e500-p800-522.pak

******************************************************************************
**** ****
**** S A U T I L S u p p o r t U t i l i t y ****
**** ****
**** for the HP SmartArray RAID Controller Family ****
**** ****
**** version A.02.13 ****
**** ****
**** (C) Copyright 2003-2007 Hewlett-Packard Development Company, L.P. ****
******************************************************************************

---- DRIVER INFORMATION ------------------------------------------------------

Driver State........................ READY

---- CONTROLLER INFORMATION --------------------------------------------------

Controller Product Number........... P800
Controller Product Name............. HP PCIe SmartArray P800
Hardware Path....................... 0/7/0/0/0/0
Device File......................... /dev/ciss2

---- FIRMWARE DOWNLOAD -------------------------------------------------------

** You are downloading the firmware image "p400-e500-p800-522.pak"
** to the controller "/dev/ciss2".

Retrieving firmware image file from disk................... [Done]

Validating the file's signature and size................... [Done]

Retrieving the firmware revision string from ROM........... [Done]

Retrieving the firmware revision string from the file...... [Done]

Current Revision (in ROM)....... 4.12
New Revision (in file).......... 5.22

WARNING: The firmware download process may take several minutes to
complete. All I/O to this controller will be temporarily
halted during this time.

Are you sure you want to continue (y/n)? y

Preparing for download..................................... [Done]

Sending the new firmware to the controller................. [Done]

Activating the new firmware................................ [Done]

Resetting the controller................................... [Done]

Retrieving the firmware revision string from ROM........... [Done]

Current Revision (in ROM)....... 5.22

FIRMWARE DOWNLOAD WAS SUCCESSFUL!

******************************************************************************
**** End of SAUTIL Output ****
******************************************************************************
root@hpuxserver : /root/home/root/PCIe_SAS_SmartArray_P800_RAID_Controller_Firmware ->

Redhat: interface bonding

2011-11-11T15:38:00.000+08:00

[root@server4 network-scripts]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:25:B3:24:ED:FA
inet addr:10.2.16.21 Bcast:10.2.16.255 Mask:255.255.255.0
inet6 addr: fe80::225:b3ff:fe24:edfa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:165251 errors:0 dropped:0 overruns:0 frame:0
TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24513496 (23.3 MiB) TX bytes:20693 (20.2 KiB)
Interrupt:169 Memory:f4000000-f4012100

eth1 Link encap:Ethernet HWaddr 00:25:B3:24:ED:FC
inet addr:153.88.118.21 Bcast:153.88.118.255 Mask:255.255.255.0
inet6 addr: fe80::225:b3ff:fe24:edfc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13882 errors:0 dropped:0 overruns:0 frame:0
TX packets:9844 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2492055 (2.3 MiB) TX bytes:4312653 (4.1 MiB)
Interrupt:154 Memory:f2000000-f2012100

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:377514 errors:0 dropped:0 overruns:0 frame:0
TX packets:377514 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38182383 (36.4 MiB) TX bytes:38182383 (36.4 MiB)

[root@server4 network-scripts]#
root@server4 network-scripts]# more ifcfg-eth2
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
DEVICE=eth2
HWADDR=00:25:B3:24:ED:FE
ONBOOT=no
BOOTPROTO=dhcp
TYPE=Ethernet
[root@server4 network-scripts]# more ifcfg-eth1
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
HWADDR=00:25:B3:24:ED:FC
DEVICE=eth1
BOOTPROTO=none
BROADCAST=153.88.118.255
IPADDR=153.88.118.21
NETMASK=255.255.255.0
NETWORK=153.88.118.0
ONBOOT=yes
TYPE=Ethernet
GATEWAY=153.88.118.1
[root@server4 network-scripts]# more ifcfg-eth2
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
DEVICE=eth2
HWADDR=00:25:B3:24:ED:FE
ONBOOT=no
BOOTPROTO=dhcp
TYPE=Ethernet
[root@server4 network-scripts]#

[root@server8 network-scripts]# more ifcfg-eth1
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
HWADDR=00:24:81:E2:82:DC
DEVICE=eth1
BOOTPROTO=none
BROADCAST=153.88.118.255
IPADDR=153.88.118.22
NETMASK=255.255.255.0
NETWORK=153.88.118.0
ONBOOT=yes
TYPE=Ethernet
GATEWAY=153.88.118.1
[root@server8 network-scripts]# more ifcfg-eth2
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
DEVICE=eth2
HWADDR=00:24:81:E2:82:DE
ONBOOT=no
BOOTPROTO=dhcp
TYPE=Ethernet
[root@server8 network-scripts]#
-----------------------------------------------------------------

Please refer below

[root@server4 network-scripts]# cat ifcfg-bond0
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
NETMASK=255.255.255.0
IPADDR=153.88.118.21
GATEWAY=153.88.118.1
USERCTL=no
BONDING_OPTS="mode=1 miimon=100"
[root@server4 network-scripts]# cat ifcfg-eth1
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
DEVICE=eth1
HWADDR=00:25:B3:24:ED:FC
ONBOOT=yes
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
USERCTL=no
[root@server4 network-scripts]# cat ifcfg-eth2
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
DEVICE=eth2
HWADDR=00:25:B3:24:ED:FE
ONBOOT=yes
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
USERCTL=no
[root@server4 network-scripts]# pwd
/etc/sysconfig/network-scripts
[root@server4 network-scripts]#

[root@server4 network-scripts]# vi /etc/modprobe.conf
[root@server4 network-scripts]# more /etc/modprobe.conf
alias eth0 bnx2
alias eth1 bnx2
alias eth2 bnx2
alias eth3 bnx2
alias scsi_hostadapter cciss
alias scsi_hostadapter1 ata_piix
alias scsi_hostadapter2 qla2xxx
alias bond0 bonding
options bonding max_bonds=2
[root@server4 network-scripts]# modprobe bonding

.... network will be temporarily unavailable, try login via backup ipaddress or via other session **

[root@server4 network-scripts]#

[root@server4 ~]# service network restart //This can be done online
Shutting down interface bond0: [ OK ]
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: [ OK ]
Bringing up interface eth0: [ OK ]
[root@server4 ~]#

[root@server4 ~]# ifconfig
bond0 Link encap:Ethernet HWaddr 00:25:B3:24:ED:FC
inet addr:153.88.118.21 Bcast:153.88.118.255 Mask:255.255.255.0
inet6 addr: fe80::225:b3ff:fe24:edfc/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4167 (4.0 KiB) TX bytes:6747 (6.5 KiB)

eth0 Link encap:Ethernet HWaddr 00:25:B3:24:ED:FA
inet addr:10.2.16.21 Bcast:10.2.16.255 Mask:255.255.255.0
inet6 addr: fe80::225:b3ff:fe24:edfa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2431 (2.3 KiB) TX bytes:12330 (12.0 KiB)
Interrupt:169 Memory:f4000000-f4012100

eth1 Link encap:Ethernet HWaddr 00:25:B3:24:ED:FC
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3316 (3.2 KiB) TX bytes:6747 (6.5 KiB)
Interrupt:154 Memory:f2000000-f2012100

eth2 Link encap:Ethernet HWaddr 00:25:B3:24:ED:FC
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:851 (851.0 b) TX bytes:0 (0.0 b)
Interrupt:178 Memory:f8000000-f8012100

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:379765 errors:0 dropped:0 overruns:0 frame:0
TX packets:379765 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38407728 (36.6 MiB) TX bytes:38407728 (36.6 MiB)

[root@server4 ~]#
[root@server4 ~]# less /proc/net/bonding/bond0

Ethernet Channel Bonding Driver: v3.2.4 (January 28, 2008)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:25:b3:24:ed:fc

Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:25:b3:24:ed:fe

HPUX: pv/lv/vg tasks

2011-11-11T11:53:00.000+08:00

Adding a new PV
A disk has to be initialized before LVM can use it. The pvcreate command writes the PVRA
to the disk and such a disk is called a PV:
# pvcreate /dev/rdsk/c0t5d0
If there is a valid PVRA already on the disk (it could have been used wit LVM before) you
will get the following error message:
# pvcreate: The Physical Volume already belongs to a Volume Group
If you are sure the disk is free you can force the initialization using the -f option:
# pvcreate -f /dev/rdsk/c0t5d0
NOTE: For bootable disks you have to use the -B option additionally. This preserves the fixed 2912KB space
for the LVM header (see section LVM structural information). You can find the procedure how to make a
disk bootable in the section Mirroring the root disk later in this chapter.
To add the PV to an existing VG do:
# vgextend vg01 /dev/dsk/c0t5d0
# vgdisplay -v vg01

Adding a new VG
Here’s how to create a new VG with 2 disks:
1) initialize the disk if not yet done:
# pvcreate [-f] /dev/rdsk/c0t5d0
# pvcreate [-f] /dev/rdsk/c0t6d0
2) select a unique minor number for the VG:
# ll /dev/*/group
crw-r--r-- 1 root sys 64 0x000000 Apr 4 2001 /dev/vg00/group
crw-r--r-- 1 root sys 64 0x010000 Oct 26 15:52 /dev/vg01/group
crw-r--r-- 1 root sys 64 0x020000 Aug 2 15:49 /dev/vgsap/group
3) create the VG control file (group file):
# mkdir /dev/vgnew
# mknod /dev/vgnew/group c 64 0x030000
NOTE: Starting with LVM commands patch PHCO_24645 (UX 11.00) or PHCO_25814 (UX 11.11)
vgcreate and vgimport will check for the uniqueness of the group file's minor number.

Adding a new LV
The following creates a 500MB large LV named lvdata on any disk(s) of the VG vg01:
# lvcreate -n lvdata -L 500 vg01
You cannot specify a PV with lvcreate. If you like to place the LV on a specific PV, then first
create an LV of 0MB. It has no extents - it just exists.
# lvcreate -n lvdata vg01
Now extend the LV onto a certain disk:
# lvextend -L 500 /dev/vg01/lvdata /dev/dsk/c4t2d0
Now you can use newfs to put a FS onto the LV:
# newfs -F /dev/vg01/rlvdata
where fstype is either hfs or vxfs.
NOTE: Nowadays it is recommended to use a VxFS (=JFS) file system.

Solaris: copy or moving file using cpio

2011-11-10T15:11:00.001+08:00

Why is cpio better than tar? A number of reasons.

cpio preserves hard links, which is important if you're using it for backups.
cpio doesn't have that annoying filename length limitation. Sure, gnutar has a "hack" that allows you to use longer filenames (it creates a temporary file in which it stores the real name), but it's inherently not portable to non-gnu tar's.
By default, cpio preserves timestamps
When scripting, it has much better control over which files are and are not copied, since you must explicitly list the files you want copied. For example, which of the following is easier to read and understand?

root@server # pwd
/ftp/data/pdu-msa/EDA-SLS
root@server #

mkdir /opt/openwin
cd /usr/openwin
find . | cpio -pdumv /opt/openwin
find /usr/openwin | cpio -pdumv /opt/openwin

cd /ftp/data/pdu-msa/EDA-SLS

find . -depth -print | cpio -pudmv /ftp/data2/pdu-msa/EDA-SLS

*** using -print will get you defunct when you exit the shell, use find . only

Solaris: Using rsync to mirror or transfer data between servers

2011-11-10T14:37:00.000+08:00

A basic example being to mirror every hour on the hour:
0 * * * * rsync -e ssh -avz user@liveserver:/home/httpd /home 2>&1 > /var/log/hourly_backup.log
Then remove deleted files every night:
30 0 * * * rsync -e ssh --delete-after -avz user@liveserver:/home/httpd /home 2>&1 > /var/log/nightly_backup.log

Solaris:Transfer data using tar rsync

2011-11-05T00:36:00.001+08:00

tar cf - /source/file | (cd /target/file; tar xf -)

or

tar cf - * | ( cd /target; tar xfp -)

or

tar cvzf - my_dir | ssh server 'tar xzf -'

tar -cf - directory | ssh user@hostB "cd target_dir; tar -xf -"

rsync -aE -e ssh directory user@hostB:target_dir

Solaris : How To Grow UFS

2011-11-04T16:17:00.002+08:00

HOw to grow filesystem under disksuite without soft partiotion for concat stripe
find unused disk by #metastat | grep -i 2f5
then, use format cmd to repatition the disk
[05:58:15] root@server[31]# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c0t0d0
/pci@780/pci@0/pci@9/scsi@0/sd@0,0
1. c0t1d0
/pci@780/pci@0/pci@9/scsi@0/sd@1,0
2. c4t60060E800543BE00000043BE000000BBd0
/scsi_vhci/ssd@g60060e800543be00000043be000000bb
3. c4t60060E800543BE00000043BE000000BCd0
/scsi_vhci/ssd@g60060e800543be00000043be000000bc
4. c4t60060E800543BE00000043BE000000BDd0
/scsi_vhci/ssd@g60060e800543be00000043be000000bd
5. c4t60060E800543BE00000043BE000000BEd0
/scsi_vhci/ssd@g60060e800543be00000043be000000be
6. c4t60060E800543BE00000043BE000002F4d0
/scsi_vhci/ssd@g60060e800543be00000043be000002f4
7. c4t60060E800543BE00000043BE000002F5d0
/scsi_vhci/ssd@g60060e800543be00000043be000002f5
Specify disk (enter its number):
[05:58:15] root@server[32]#metattach d17 /dev/dsk/c4t60060E800543BE00000043BE000002F5d0s0
d107: component is attached
[05:58:15] root@server[33]# df -k /dbo
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d107 183417068 173603462 8489617 96% /dbo
[05:58:15] root@server[34]# grep dbo /etc/mnttab
/dev/md/dsk/d107 /dbo ufs rw,intr,largefiles,logging,xattr,onerror=panic,dev=154006b 1202293409
[05:58:15] root@server[35]# growfs -M /dbo /dev/md/rdsk/d107
/dev/md/rdsk/d107: 476067840 sectors in 77485 cylinders of 48 tracks, 128 sectors
232455.0MB in 4843 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
...............................................................................
.................
super-block backups for last 10 cylinder groups at:
475107488, 475205920, 475304352, 475402784, 475501216, 475599648, 475698080,
475796512, 475894944, 475993376
[05:58:15] root@server[36]# df -k /dbo
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d107 234430636 173603462 59503185 75% /dbo
[05:58:15] root@server[37]#

Solaris10: How to NFS via ZFS

2011-11-03T11:37:00.000+08:00

By default, the root user on a client machine has restricted access to an NFS-mounted share.

Here's how to grant full access to local root users to NFS mounts:

zfs set sharenfs=rw=@192.168.1.0/24,root=@192.168.1.0/24 space

This gives full access for root users on any machine in the 192.168.1.0/24 subnet to the zfs dataset "space".

serverB# zfs list
NAME USED AVAIL REFER MOUNTPOINT
app 284G 157G 18K none
app/iwstoreAPAC 51.8G 48.2G 51.8G /opt/app/data/iw-store/APAC
app/iwstoreAmericas 27.6G 22.4G 27.6G /opt/app/data/iw-store/Americas
app/iwstoreEMEA 192G 57.6G 192G /opt/app/data/iw-store/EMEA
app/optapp 12.3G 87.7G 12.3G /opt/app

for set of network
zfs set sharenfs=rw=@153.88.177.0/24,root=@153.88.177.0/24 app/iwstoreAPAC
zfs set sharenfs=rw=@153.88.177.0/24,root=@153.88.177.0/24 app/iwstoreAmericas
zfs set sharenfs=rw=@153.88.177.0/24,root=@153.88.177.0/24 app/iwstoreEMEA

or for specific ips
zfs set sharenfs=rw=153.88.177.59,root=153.88.177.59 app/iwstoreAPAC
zfs set sharenfs=rw=153.88.177.59,root=153.88.177.59 app/iwstoreAmericas
zfs set sharenfs=rw=153.88.177.59,root=153.88.177.59 app/iwstoreEMEA

On serverA
mkdir /serverB_APAC
mkdir /serverB_Americas
mkdir /serverB_EMEA

serverA# dfshares serverB
RESOURCE SERVER ACCESS TRANSPORT
serverB:/opt/app/data/iw-store/Americas serverB - -
serverB:/iwserver serverB - -
serverB:/opt/app/data/iw-store/EMEA serverB - -
serverB:/opt/app/data/iw-store/APAC serverB - -
serverA# mount serverB:/opt/app/data/iw-store/Americas /serverB_Americas
serverA# mount serverB:/opt/app/data/iw-store/EMEA /serverB_EMEA
serverA# df -k

Solaris 10: How to configure ftp with single user restricted access and other not allowed

2011-10-20T14:55:00.002+08:00

/etc/ftpd/ftpaccess example
--------------
.
.
.
. omitted

# limit-time anonymous 30
# limit anonusers 10 Wk0730-1800 /etc/ftpd/toomany.msg
# limit anonusers 50 SaSu|Any1800-0730 /etc/ftpd/toomany.msg
restricted-uid partsftp
allow-uid partsftp
deny-uid *
defumask 022
-----

ftp> ls
200 PORT command successful.
150 Opening ASCII mode data connection for /bin/ls.
total 8
-rw-r--r-- 1 partsftp partsftp 133 Oct 20 08:04 local.cshrc
-rw-r--r-- 1 partsftp partsftp 157 Oct 20 08:04 local.login
-rw-r--r-- 1 partsftp partsftp 172 Oct 20 08:04 local.profile
-rw-r--r-- 1 partsftp partsftp 207 Oct 20 08:04 .profile
226 Transfer complete.
ftp> cd ..
550 Permission denied on server. You are restricted to your account.
ftp> bye

-----------------

/var/adm/messages example

Oct 20 08:00:13 servername4 ftpd[24686]: [ID 177334 daemon.notice] FTP LOGIN REF USED (username in denied-uid) FROM abc.com.se [172.17.200 .154], username

Linux: Proliant check firmware

2011-06-21T11:50:00.002+08:00

How to check linux firmware version

hpiLO-> show /map1/firmware1
status=0
status_tag=COMMAND COMPLETED

/map1/firmware1
Targets
Properties
    version=2.01
    date=08/04/2010
Verbs
    cd version exit show load set

hpiLO-> exit

Use the following procedure:

    * Use SSH to access the iLO device
    * Log in to the iLO using administrative credentials
    * Type the following command and press enter: "load -source http://ip_address/path/imagename.bin /map1/firmware"
          o Example: "load -source http://192.168.0.1/ilo2_180.bin /map1/firmware"
    * The interface will download the new image and will reset itself
    * To check the firmware version, log in again using SSH and enter the following command: "show /map1/firmware version"

Redhat: Check mirror running on HP proliant with hpacucli

2011-05-23T16:29:00.001+08:00

[root]# hpacucli ctrl all show
No lpfc hosts found

Smart Array P400 in Slot 3 (sn: PAFGL0P9SWY1S8)

[root]#

[root]# hpacucli ctrl slot=3 pd all show status
No lpfc hosts found

physicaldrive 2I:1:1 (port 2I:box 1:bay 1, 146 GB): OK
physicaldrive 2I:1:2 (port 2I:box 1:bay 2, 146 GB): OK

[root]# hpacucli ctrl slot=3 ld all show status
No lpfc hosts found

logicaldrive 1 (136.7 GB, RAID 1): OK

[root]#

HPUX: how to reboot server

2011-05-10T16:10:00.000+08:00

root# shutdown -r -y now

SHUTDOWN PROGRAM
05/10/11 10:06:27 METDST

Broadcast Message from XXX (pts/0) Tue May 10 10:06:27...
SYSTEM BEING BROUGHT DOWN NOW ! ! !

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)

ovc instance NOT running

System shutdown in progress
___________________________

Stop Highly Available cluster ................................... N/A
Stopping Control Daemon ......................................... OK
Stopping OVTrcSrv ............................................... OK
Stoppping OVCM (radia) agent daemons ............................ OK
Stop LVM daemon ................................................. OK
Stop kwdbd ...................................................... N/A
Stopping HP-UX Apache-based Web Server .......................... OK
Stopping HP-UX Tomcat-based Servlet Engine. ..................... N/A
Stopping HP-UX Webmin-based Admin ............................... OK
Stopping the HPUX Webproxy subsystem ............................ OK
Stopping HP-UX XML Web Server Tools ............................. OK
Stop ESM network daemon ......................................... OK
Stop NFS server subsystem ....................................... OK
................................................................ OK
Collecting AVIO and VIO hba and lun inventory.. ................. OK
Shutting down CIFS Client ....................................... N/A
Stopping Event Monitoring Service ............................... OK
Stop interrupt balance daemon ................................... N/A
Shutting down the Winbind Daemon ................................ OK
Unload/Uninstall XF86 DLKM Helper Modules ....................... N/A
Stopping the gWLM Agent ......................................... OK
Stopping Data Protector services ................................ OK
Stop Workload Manager subsystem ................................. OK
Reset PRM and shut down PRM daemons ............................. OK
Shutting down the System Management HomePage server ............. OK
Shutting down Perf Agent software ............................... OK
Stopping the perfd daemon. ...................................... OK
Shutting down OSD Down Time software ............................ OK
Stopping USB hub daemon ......................................... OK
Stop auditing subsystem ......................................... OK
Stop environment monitoring daemon .............................. OK
Stop diagnostic subsystem ....................................... OK
Stop oserrlogd .................................................. OK
Stop clock daemon ............................................... OK
Stop print spooler .............................................. OK
Stop accounting ................................................. N/A
Stopping time synchronization ................................... OK
Stop vt daemon .................................................. OK
Terminating X Font Server ....................................... OK
Stop HA cluster WBEM subagent ................................... OK
Stopping HP-UX Secure Shell ..................................... OK
Stopping Instant Capacity ....................................... N/A
Stop CIM cimserver subsystem .................................... OK
Stop RPC daemon ................................................. OK
Stop DCE daemons ................................................ OK
Stop HA cluster SNMP subagent ................................... OK
Stopping OSPF MIB Network Management subAgent ................... N/A
Stopping SNMP HP-UNIX Network Management subAgent ............... OK
Stopping SNMP IPv6 Network Management subAgent .................. OK
Stopping SNMP MIB-2 Network Management subAgent ................. OK
Stopping Native Adapter Agent ................................... OK
Stopping SNMP Trap Dest Network Management subAgent ............. OK
Stopping SNMP Master Network Management daemon .................. OK
Stop HA cluster proxy daemon .................................... OK
Stopping outbound connection daemons for DDFA software .......... N/A
Stopping syslog-ng daemons ...................................... N/A
Stopping cfengine's cfservd daemon .............................. N/A
Shutting down sendmail [Done] Shutting down sm-client [Done] .... OK
Stopping IPv6 router advertisement daemon ....................... N/A
Stopping remote system status daemon ............................ N/A
Stopping RARP protocol daemon ................................... N/A
Stop PPPoE configuration ........................................ N/A
Stop PPP configuration .......................................... OK
Stopping router discover protocol daemon ........................ N/A
Stopping ramd routing daemon .................................... N/A
Stopping dynamic routing daemon ................................. N/A
Stopping Internet services daemon ............................... OK
Stopping multicast routing daemon ............................... N/A
Stop AUTOFS subsystem ........................................... OK
Stop NFS client subsystem ....................................... OK
Stop lock manager subsystem ..................................... OK
Stop NIS client subsystem ....................................... OK
Stop ldap client daemon ......................................... OK
Stop NIS/LDAP server subsystem .................................. N/A
Stop NIS server subsystem ....................................... OK
Stop NFS core subsystem ......................................... OK
Stopping name server daemon ..................................... N/A
Unconfiguring DHCPv6 Interfaces ................................. OK
Stopping DHCPv6 Server daemon ................................... N/A
Stopping sfmdb PostgreSQL daemons ............................... OK
Unconfigure LAN interfaces ...................................... OK
Unconfigure LAN interfaces for IPv6 ............................. OK
Unconfigure HP igssn Gigabit Ethernet interfaces ................ OK
Unconfigure HP gelan Gigabit Ethernet interfaces ................ OK
Unconfigure HP iether 100BT/Gigabit Ethernet interfaces ......... OK
Unconfigure HP igelan Gigabit Ethernet interfaces ............... OK
Stop ESM network daemon ......................................... OK
Stop network tracing and logging daemon ......................... OK
Stop pty allocator daemon ....................................... OK
Stop system message logging daemon .............................. OK
Stop Software Distributor agent daemon .......................... OK
Stop Essential Services monitoring daemon ....................... OK
Stopping Event Management (EVM) ................................. OK
Unconfigure Loopback interfaces (lo0) ........................... OK
Stop Utmp Daemon ................................................ OK
Stopping livedump subsystem ..................................... OK
Stop syncer daemon .............................................. OK
Killing user processes .......................................... OK
Starting the fsdaemon for transition into single-user mode ...... OK
Apply kernel configuration changes for next boot ................ OK
Unmount file systems ............................................ OK

Transition to run-level 0 is complete.
Executing "/sbin/reboot ".
Shutdown at 10:08 (in 0 minutes)

*** FINAL System shutdown message from hpfimhas@esesbux0006 ***

System going down IMMEDIATELY

System shutdown time has arrived
reboot: redirecting error messages to /dev/console
Connection to xxx closed by remote host.
Connection to xxx closed.
#

Redhat: Check NIC speed/duplex

2011-05-10T11:17:00.000+08:00

[root]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:50:56:A5:6E:28
inet addr:155.53.154.197 Bcast:155.53.155.255 Mask:255.255.254.0
inet6 addr: fe80::250:56ff:fea5:6e28/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2657820622 errors:0 dropped:0 overruns:0 frame:0
TX packets:2174534933 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3362843874812 (3.0 TiB) TX bytes:1238184921670 (1.1 TiB)
Base address:0x2000 Memory:d8920000-d8940000
[root]# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
[root]#

HPUX: check duplex on 11.0

2011-04-28T14:56:00.000+08:00

root: /root/home/root -> netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan1 1500 10.2.18.0
324582173 0 380503067 0 0
lan0 1500 153.88.127.0
343512775 0 1606306136
root: /root/home/root -> lanscan -p
0
1
900
901
902
903
904

root: /root/home/root -> lanadmin -x 0
Speed = 1000 Full-Duplex.
Autonegotiation = On.

root /root/home/root -> lanadmin -x 1
Speed = 1000 Full-Duplex.
Autonegotiation = On.

HPUX: Determine if disk is mirrored

2011-04-28T14:43:00.002+08:00

root: /opt -> lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk4_p2 -- Boot Disk
/dev/disk/disk5_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk4_p2
/dev/disk/disk5_p2
Root: lvol3 on: /dev/disk/disk4_p2
/dev/disk/disk5_p2
Swap: lvol2 on: /dev/disk/disk4_p2
/dev/disk/disk5_p2
Dump: lvol2 on: /dev/disk/disk4_p2, 0

root : /opt ->

Solaris SSH and Tar combine

2010-07-08T12:12:00.001+08:00

to push

tar czf - www.example.com/ | ssh joebloggs@otherserver.com tar xzf - -C ~/

to get

ssh username@from_server "tar czf - directory_to_get" | tar xzvf - -C

Solaris 10: Find new disk and label it

2010-07-07T12:34:00.003+08:00

#cat format.cmd
label
quit

#cat list
4B19
5B19
6B19
7B19

#! /bin/sh
echo "\n" | format > format.before
#cfgadm -al
echo "\n" | format > format.after
for i in `cat list`
do
echo $i
grep -i $i format.after| grep -i configured| awk -F: '{print $1}' > a.out
echo "format -s -f format.cmd `grep -i $i format.after| grep -i configured| awk -F: '{print $1}'`" > labeldisk.sh
done

#sh -x labeldisk.sh

REDHAT LVM determine free disk space and move LVM aroun

2010-03-23T14:48:00.000+08:00

Determine free space

# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE PV "/dev/sda" of VG "dev" [1.95 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdb" of VG "sales" [1.95 GB / 1.27 GB free]
pvscan -- ACTIVE PV "/dev/sdc" of VG "ops" [1.95 GB / 564 MB free]
pvscan -- ACTIVE PV "/dev/sdd" of VG "dev" [1.95 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sde" of VG "ops" [1.95 GB / 1.9 GB free]
pvscan -- ACTIVE PV "/dev/sdf" of VG "dev" [1.95 GB / 1.33 GB free]
pvscan -- ACTIVE PV "/dev/sdg1" of VG "ops" [996 MB / 432 MB free]
pvscan -- ACTIVE PV "/dev/sdg2" of VG "dev" [996 MB / 632 MB free]
pvscan -- total: 8 [13.67 GB] / in use: 8 [13.67 GB] / in no VG: 0 [0]

We decide to reallocate /dev/sdg1 and /dev/sdg2 to design so first we have to move the physical extents into the free areas of the other volumes (in this case /dev/sdf for volume group dev and /dev/sde for volume group ops).

Move data off the disks to be used

Some space is still used on the chosen volumes so it is necessary to move that used space off onto some others.

Move all the used physical extents from /dev/sdg1 to /dev/sde and from /dev/sdg2 to /dev/sdf

# pvmove /dev/sdg1 /dev/sde
pvmove -- moving physical extents in active volume group "ops"
pvmove -- WARNING: moving of active logical volumes may cause data loss!
pvmove -- do you want to continue? [y/n] y
pvmove -- doing automatic backup of volume group "ops"
pvmove -- 141 extents of physical volume "/dev/sdg1" successfully moved

# pvmove /dev/sdg2 /dev/sdf
pvmove -- moving physical extents in active volume group "dev"
pvmove -- WARNING: moving of active logical volumes may cause data loss!
pvmove -- do you want to continue? [y/n] y
pvmove -- doing automatic backup of volume group "dev"
pvmove -- 91 extents of physical volume "/dev/sdg2" successfully moved

Make a file system on the volume ext3

# mkfs.ext3 /dev/datavg01/datalv01
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
19660800 inodes, 39305216 blocks
1965260 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
1200 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

Mount the new volume

# mkdir -p /mnt/design/users
# mount /dev/datavg01/datalv01 /mnt/design/users/

It's also a good idea to add an entry for this file system in your /etc/fstab file as follows:

/dev/datavg01/datalv01 /mnt/design/users ext3 defaults 1 2

Multi-path Device Mapper for Linux Software - Software Installation

2010-03-23T11:12:00.001+08:00

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=115&prodSeriesId=3559651&prodTypeId=18964&objectID=c01475612

Another good redhat blog for reference

2010-03-23T11:00:00.001+08:00

http://thomasvogt.wordpress.com/2007/12/04/linux-network-bonding/

HPUX download lsof site

2010-03-05T15:46:00.002+08:00

http://hpux.connect.org.uk/hppd/hpux/Sysadmin/lsof-4.82/

REDHAT: To Test New Kernel Reboot Once

2010-03-05T11:50:00.004+08:00

We want to change default=0 to default=1 This will boot your old kernel (not the upgraded one). Grub starts at 0, which will be your new kernel. We will switch to the new kernel later.

Save and exit.

Step 3: Configure server to boot once with the new kernel.

Now we will configure the server to boot the new kernel only once in case it fails. This is the most important step, if its not done and the new kernel fails your out of luck.

Type the following from command line (one at a time):

grub
savedefault --default=0 --once
quit

Step 4 – Reboot

Then reboot the server or computer. When it comes back up run uname -a to make sure it has the new kernel. (Note: if it does not come back up, reboot it again and it will load the old kernel.)

Then switch the grub.conf to boot the new kernel permanently.

nano /boot/grub/grub.conf

change default=1 to default=0

Save and exit. Thats it you have successfully updated your kernel.

Solaris:How can I use the Solaris ?Explorer? program to collect information on my zone(s)

2010-02-09T10:54:00.001+08:00

Explorer 5.0 can be run on Solaris 10 in a global zone. It can be used to collect information on containers (non-global zones) with the -w option.

Solaris: How do I modify the network configuration of a running zone?

2010-02-09T10:41:00.002+08:00

global# ifconfig bge0 addif  192.168.200.2 zone myzone
global# ifconfig bge0 removeif 192.168.200.2

Or remove and add again interface via zonecfg -z myzone

Solaris 10 zones fatal signal 9

2009-07-30T21:44:00.001+08:00

If your zones trying to boot endlessly looping like this....

Jul 29 13:05:52 global zone last message repeated 158764 times
Jul 29 13:05:52 global zone genunix: [ID 729207 kern.warning] WARNING: init(1M) for zone localzone (pid 1800) exited on fatal signal 9: restarting automatically
Jul 29 13:11:47 global zone last message repeated 140032 times
Jul 29 13:11:52 global zone genunix: [ID 729207 kern.warning] WARNING: init(1M) for zone localzone (pid 24509) exited on fatal signal 9: restarting automatically
Jul 29 13:12:32 global zone last message repeated 15167 times
Jul 29 13:12:32 global zone genunix: [ID 729207 kern.warning] WARNING: init(1M) for zone localzone (pid 24509) exited on fatal signal 9: restarting automatically

Your library libc.so.1 might be in trouble. Try copy from global zone. and it will able to boot again.
root@globalzone # /zones/localzone/root/liblibc.so.1
-rwxr-xr-x 1 root bin 0 Jul 29 09:44 libc.so.1

see the zlogin console, localzone is booting...

Solaris How to find LUN id of disks

2009-05-12T11:19:00.002+08:00

#format ....

54. c4t50060E8003EC2D000000EC2D00001015d0
/scsi_vhci/ssd@g50060e8003ec2d000000ec2d00001015
55. c4t50060E8003EC2D000000EC2D00001017d0
/scsi_vhci/ssd@g50060e8003ec2d000000ec2d00001017
56. c4t50060E8003EC2D000000EC2D00001019d0
/scsi_vhci/ssd@g50060e8003ec2d000000ec2d00001019
[03:49:39] root@episprod[64]# luxadm probe | grep c4t50060E8003EC2D000000EC2D000 01015d0
Logical Path:/dev/rdsk/c4t50060E8003EC2D000000EC2D00001015d0s2
64 luxadm probe | grep c4t50060E8003EC2D000000EC2D00001015d0
65 luxadm display /dev/rdsk/c4t50060E8003EC2D000000EC2D00001015d0s2

[03:49:39] root@episprod[65]# k/c4t50060E8003EC2D000000EC2D00001015d0s2 <
DEVICE PROPERTIES for disk: /dev/rdsk/c4t50060E8003EC2D000000EC2D00001015d0s2
Vendor: HP
Product ID: OPEN-E -SUN
Revision: 2114
Serial Num: 0450EC2D1015
Unformatted capacity: 13893.047 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x0
Maximum prefetch: 0x0
Device Type: Disk device
Path(s):

/dev/rdsk/c4t50060E8003EC2D000000EC2D00001015d0s2
/devices/scsi_vhci/ssd@g50060e8003ec2d000000ec2d00001015:c,raw
Controller /devices/pci@8,600000/SUNW,qlc@1/fp@0,0
Device Address 50060e8003ec2d05,14 <---------- this is the LUN id in HEX
Host controller port WWN 210000e08b81fdfa
Class primary
State ONLINE
Controller /devices/pci@8,600000/SUNW,qlc@2/fp@0,0
Device Address 50060e8003ec2d15,14 <---------- this is the LUN id in HEX
Host controller port WWN 210000e08b8180fb
Class primary
State ONLINE

Solaris which disk we are booting from?

2009-05-08T16:46:00.000+08:00

root # prtpicl -v | grep disk
:disk-write-fix
disk-label (disk-label, 3a00000033)
:devfs-path /packages/disk-label
:binding-name disk-label
:_class disk-label
:name disk-label
:bootpath /pci@1c,600000/scsi@2/disk@1,0:a <----- disk1
:boot-device disk0:a
:diag-device disk0:a
:disk /pci@1c,600000/scsi@2/disk@0,0
:disk0 /pci@1c,600000/scsi@2/disk@0,0
:disk1 /pci@1c,600000/scsi@2/disk@1,0
:disk2 /pci@1c,600000/scsi@2/disk@2,0
:disk3 /pci@1c,600000/scsi@2/disk@3,0
:SlotType disk-slot
disk (fru, 3a0000b366)
:name disk
:SlotType disk-slot
disk (fru, 3a000006df)
:name disk
:SlotType disk-slot
:SlotType disk-slot
root #

HPUX check interface speed

2009-04-16T11:09:00.002+08:00

root -> lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/0 0x000D9DAEFD96 0 UP lan0 snap0 1 ETHER Yes 119
0/2/0/0 0x00306EEAE178 1 UP lan1 snap1 2 ETHER Yes 119
root -> lanadmin -x 0
Current Config = 100 Full-Duplex AUTONEG

root->

Solaris 10 HP-OPEN-V-SUN

2008-12-24T13:08:00.000+08:00

root@hostname # cfgadm -o show_FCP_dev -al
Ap_Id Type Receptacle Occupant Condition
c2 fc-fabric connected configured unknown
c2::50060e8004f25e46,0 disk connected configured unknown
c2::50060e8004f25e46,1 disk connected configured unknown
c2::50060e8004f25e46,2 disk connected configured unknown
c2::50060e8004f25e46,3 disk connected configured unknown
c2::50060e8004f25e46,4 disk connected configured unknown
c2::50060e8004f25e46,5 disk connected configured unknown
c2::50060e8004f25e46,6 disk connected configured unknown
c2::50060e8004f25e46,7 disk connected configured unknown
c2::50060e8004f25e46,8 disk connected configured unknown
c2::50060e8004f25e46,9 disk connected configured unknown
c2::50060e8004f25e46,10 disk connected configured unknown
c2::50060e8004f25e46,11 disk connected configured unknown
c2::50060e8004f25e46,12 disk connected configured unknown
c2::50060e8004f25e46,13 disk connected configured unknown
c2::50060e8004f25e46,14 disk connected configured unknown
c2::50060e8004f25e46,15 disk connected configured unknown
c2::50060e8004f25e46,16 disk connected configured unknown
c2::50060e8004f25e46,17 disk connected configured unknown
c2::50060e8004f25e46,18 disk connected configured unknown
c2::50060e8004f25e46,19 disk connected configured unknown
c2::50060e8004f25e46,20 disk connected configured unknown
c2::50060e8004f25e46,21 disk connected configured unknown
c2::50060e8004f25e46,22 disk connected configured unknown
c2::50060e8004f25e46,23 disk connected configured unknown
c2::50060e8004f25e46,24 disk connected configured unknown
c2::50060e8004f25e46,25 disk connected configured unknown
c2::50060e8004f25e46,26 disk connected configured unknown
c2::50060e8004f25e46,27 disk connected configured unknown
c2::50060e8004f25e46,28 disk connected configured unknown
c2::50060e8004f25e46,29 disk connected configured unknown
c2::50060e8004f25e46,30 disk connected configured unknown
c2::50060e8004f25e46,31 disk connected configured unknown
c2::50060e8004f25e46,32 disk connected configured unknown
c2::50060e8004f25e46,33 disk connected configured unknown
c2::50060e8004f25e46,34 disk connected configured unknown
c2::50060e8004f25e46,35 disk connected configured unknown
c2::50060e8004f25e46,36 disk connected configured unknown
c2::50060e8004f25e46,37 disk connected configured unknown
c2::50060e8004f25e46,38 disk connected configured unknown
c2::50060e8004f25e46,39 disk connected configured unknown
c2::50060e8004f25e46,40 disk connected configured unknown
c2::50060e8004f25e46,41 disk connected configured unknown
c2::50060e8004f25e46,42 disk connected configured unknown
c2::50060e8004f25e46,43 disk connected configured unknown
c2::50060e8004f25e46,44 disk connected configured unknown
c2::50060e8004f25e46,45 disk connected configured unknown
c2::50060e8004f25e46,46 disk connected configured unknown
c2::50060e8004f25e46,47 disk connected configured unknown
c2::50060e8004f25e46,48 disk connected configured unknown
c2::50060e8004f25e46,49 disk connected configured unknown
c2::50060e8004f25e46,50 disk connected configured unknown
c2::50060e8004f25e46,51 disk connected configured unknown
c2::50060e8004f25e46,52 disk connected configured unknown
c2::50060e8004f25e46,53 disk connected configured unknown
c2::50060e8004f25e46,54 disk connected configured unknown
c2::50060e8004f25e46,55 disk connected configured unknown
c2::50060e8004f25e46,56 disk connected configured unknown
c2::50060e8004f25e46,57 disk connected configured unknown
c2::50060e8004f25e46,58 disk connected configured unknown
c2::50060e8004f25e46,59 disk connected configured unknown
c2::50060e8004f25e46,60 disk connected configured unknown
c2::50060e8004f25e46,61 disk connected configured unknown
c2::50060e8004f25e46,62 disk connected configured unknown
c2::50060e8004f25e46,63 disk connected configured unknown
c2::50060e8004f25e46,64 disk connected configured unknown
c2::50060e8004f25e46,65 disk connected configured unknown
c3 fc-fabric connected configured unknown
c3::50060e8004f25e56,0 disk connected configured unknown
c3::50060e8004f25e56,1 disk connected configured unknown
c3::50060e8004f25e56,2 disk connected configured unknown
c3::50060e8004f25e56,3 disk connected configured unknown
c3::50060e8004f25e56,4 disk connected configured unknown
c3::50060e8004f25e56,5 disk connected configured unknown
c3::50060e8004f25e56,6 disk connected configured unknown
c3::50060e8004f25e56,7 disk connected configured unknown
c3::50060e8004f25e56,8 disk connected configured unknown
c3::50060e8004f25e56,9 disk connected configured unknown
c3::50060e8004f25e56,10 disk connected configured unknown
c3::50060e8004f25e56,11 disk connected configured unknown
c3::50060e8004f25e56,12 disk connected configured unknown
c3::50060e8004f25e56,13 disk connected configured unknown
c3::50060e8004f25e56,14 disk connected configured unknown
c3::50060e8004f25e56,15 disk connected configured unknown
c3::50060e8004f25e56,16 disk connected configured unknown
c3::50060e8004f25e56,17 disk connected configured unknown
c3::50060e8004f25e56,18 disk connected configured unknown
c3::50060e8004f25e56,19 disk connected configured unknown
c3::50060e8004f25e56,20 disk connected configured unknown
c3::50060e8004f25e56,21 disk connected configured unknown
c3::50060e8004f25e56,22 disk connected configured unknown
c3::50060e8004f25e56,23 disk connected configured unknown
c3::50060e8004f25e56,24 disk connected configured unknown
c3::50060e8004f25e56,25 disk connected configured unknown
c3::50060e8004f25e56,26 disk connected configured unknown
c3::50060e8004f25e56,27 disk connected configured unknown
c3::50060e8004f25e56,28 disk connected configured unknown
c3::50060e8004f25e56,29 disk connected configured unknown
c3::50060e8004f25e56,30 disk connected configured unknown
c3::50060e8004f25e56,31 disk connected configured unknown
c3::50060e8004f25e56,32 disk connected configured unknown
c3::50060e8004f25e56,33 disk connected configured unknown
c3::50060e8004f25e56,34 disk connected configured unknown
c3::50060e8004f25e56,35 disk connected configured unknown
c3::50060e8004f25e56,36 disk connected configured unknown
c3::50060e8004f25e56,37 disk connected configured unknown
c3::50060e8004f25e56,38 disk connected configured unknown
c3::50060e8004f25e56,39 disk connected configured unknown
c3::50060e8004f25e56,40 disk connected configured unknown
c3::50060e8004f25e56,41 disk connected configured unknown
c3::50060e8004f25e56,42 disk connected configured unknown
c3::50060e8004f25e56,43 disk connected configured unknown
c3::50060e8004f25e56,44 disk connected configured unknown
c3::50060e8004f25e56,45 disk connected configured unknown
c3::50060e8004f25e56,46 disk connected configured unknown
c3::50060e8004f25e56,47 disk connected configured unknown
c3::50060e8004f25e56,48 disk connected configured unknown
c3::50060e8004f25e56,49 disk connected configured unknown
c3::50060e8004f25e56,50 disk connected configured unknown
c3::50060e8004f25e56,51 disk connected configured unknown
c3::50060e8004f25e56,52 disk connected configured unknown
c3::50060e8004f25e56,53 disk connected configured unknown
c3::50060e8004f25e56,54 disk connected configured unknown
c3::50060e8004f25e56,55 disk connected configured unknown
c3::50060e8004f25e56,56 disk connected configured unknown
c3::50060e8004f25e56,57 disk connected configured unknown
c3::50060e8004f25e56,58 disk connected configured unknown
c3::50060e8004f25e56,59 disk connected configured unknown
c3::50060e8004f25e56,60 disk connected configured unknown
c3::50060e8004f25e56,61 disk connected configured unknown
c3::50060e8004f25e56,62 disk connected configured unknown
c3::50060e8004f25e56,63 disk connected configured unknown
c3::50060e8004f25e56,64 disk connected configured unknown
c3::50060e8004f25e56,65 disk connected configured unknown
root@hostname # pwd
/root/home/hpfimhas
root@hostname # cfgadm -o show_FCP_dev -al > cfgadm_o_show_FCP_dev_al.out.07112008
root@hostname # ls
cfgadm_o_show_FCP_dev_al.out.07112008 format.out.061108
df_k.out.061108 metastat_p.out.061108
root@hostname # cfg
root@hostname #
root@hostname #
root@hostname #
root@hostname #
root@hostname # uname -a
SunOS hostname 5.10 Generic_118833-36 sun4v sparc SUNW,Sun-Fire-T200
root@hostname # cfgadm -c configure c2
root@hostname # cfgadm -c configure c3
root@hostname # tail /var/adm/messages
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000dd7 (ssd22) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,9 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000dd6 (ssd23) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,8 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000dd5 (ssd24) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,7 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000dd4 (ssd25) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,6 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000719 (ssd0) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,5 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000718 (ssd1) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,4 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000717 (ssd2) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,3 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000716 (ssd3) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,2 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000715 (ssd4) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,1 is online Load balancing: round-robin
Nov 7 02:54:14 hostname genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60060e8004f25e000000f25e00000714 (ssd5) multipath status: optimal, path /pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w50060e8004f25e56,0 is online Load balancing: round-robin
root@hostname #
root@hostname # grep -i label /var/adm/messages
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:43 hostname Corrupt label; wrong magic number
Nov 7 01:56:44 hostname Corrupt label; wrong magic number
Nov 7 01:56:44 hostname Corrupt label; wrong magic number
Nov 7 01:56:44 hostname Corrupt label; wrong magic number
Nov 7 01:56:44 hostname Corrupt label; wrong magic number
root@hostname # echo "\n" | format > format.today

root@hostname # more fornat.today
Searching for disks...done

c4t60060E8004F25E000000F25E00000F0Ed0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F0Fd0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F1Ad0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F1Bd0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F1Cd0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F1Dd0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F1Ed0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F1Fd0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F10d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F11d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F12d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F13d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F14d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F15d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F16d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F17d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F18d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F19d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F20d0: configured with capacity of 25.28GB
c4t60060E8004F25E000000F25E00000F21d0: configured with capacity of 25.28GB

AVAILABLE DISK SELECTIONS:
root@hostname # more disktolabel.out
c4t60060E8004F25E000000F25E00000F0Ed0: configured with capacity of 25.28GB
38. c4t60060E8004F25E000000F25E00000F0Ed0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F0Fd0: configured with capacity of 25.28GB
39. c4t60060E8004F25E000000F25E00000F0Fd0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F1Ad0: configured with capacity of 25.28GB
40. c4t60060E8004F25E000000F25E00000F1Ad0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F1Bd0: configured with capacity of 25.28GB
41. c4t60060E8004F25E000000F25E00000F1Bd0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F1Cd0: configured with capacity of 25.28GB
42. c4t60060E8004F25E000000F25E00000F1Cd0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F1Dd0: configured with capacity of 25.28GB
43. c4t60060E8004F25E000000F25E00000F1Dd0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F1Ed0: configured with capacity of 25.28GB
44. c4t60060E8004F25E000000F25E00000F1Ed0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F1Fd0: configured with capacity of 25.28GB
45. c4t60060E8004F25E000000F25E00000F1Fd0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F10d0: configured with capacity of 25.28GB
46. c4t60060E8004F25E000000F25E00000F10d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F11d0: configured with capacity of 25.28GB
47. c4t60060E8004F25E000000F25E00000F11d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F12d0: configured with capacity of 25.28GB
48. c4t60060E8004F25E000000F25E00000F12d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F13d0: configured with capacity of 25.28GB
49. c4t60060E8004F25E000000F25E00000F13d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F14d0: configured with capacity of 25.28GB
50. c4t60060E8004F25E000000F25E00000F14d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F15d0: configured with capacity of 25.28GB
51. c4t60060E8004F25E000000F25E00000F15d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F16d0: configured with capacity of 25.28GB
52. c4t60060E8004F25E000000F25E00000F16d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F17d0: configured with capacity of 25.28GB
53. c4t60060E8004F25E000000F25E00000F17d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F18d0: configured with capacity of 25.28GB
54. c4t60060E8004F25E000000F25E00000F18d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F19d0: configured with capacity of 25.28GB
55. c4t60060E8004F25E000000F25E00000F19d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F20d0: configured with capacity of 25.28GB
56. c4t60060E8004F25E000000F25E00000F20d0 2 hd 15 sec 512>
c4t60060E8004F25E000000F25E00000F21d0: configured with capacity of 25.28GB
57. c4t60060E8004F25E000000F25E00000F21d0 2 hd 15 sec 512>
root@hostname #

------ above is done---- now need to create new metadevice concat /ftp/data2 ---
root@hostname # more checkifdiskisused.sh
#! /bin/sh
for i in `cat a.out`
do
grep -i $i metastat_p.out
done
root@hostname # sh checkifdiskisused.sh
root@hostname # more metastat_p.out
d103 -m d203 d303 1
d203 1 1 c0t0d0s4
d303 1 1 c0t1d0s4
d102 -m d202 d302 1
d202 1 1 c0t0d0s3
d302 1 1 c0t1d0s3
d101 -m d201 d301 1
d201 1 1 c0t0d0s1
d301 1 1 c0t1d0s1
d100 -m d200 d300 1
d200 1 1 c0t0d0s0
d300 1 1 c0t1d0s0
d104 3 1 /dev/dsk/c4t60060E8004F25E000000F25E00000714d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000715d0s1 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000717d0s0
d107 40 1 /dev/dsk/c4t60060E8004F25E000000F25E00000DD4d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DD5d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DD6d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DD7d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DD8d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DD9d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DDAd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DDBd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DDCd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DDDd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DDEd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DDFd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DE0d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DE1d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DE2d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DE3d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DE4d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DE5d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DE6d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000DE7d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000718d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000719d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00001130d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00001131d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000D6d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000D7d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000D8d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000D9d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000DAd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000DBd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000DCd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000DDd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000DEd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000DFd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000E0d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000E1d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000E2d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000E3d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000E4d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E000000E5d0s0
d112 1 1 /dev/dsk/c4t60060E8004F25E000000F25E00000716d0s3
d109 2 1 /dev/dsk/c4t60060E8004F25E000000F25E00000715d0s3 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000715d0s4
d110 1 1 /dev/dsk/c4t60060E8004F25E000000F25E00000716d0s0
d106 1 1 /dev/dsk/c4t60060E8004F25E000000F25E00000714d0s3
d105 1 1 /dev/dsk/c4t60060E8004F25E000000F25E00000714d0s1
d111 1 1 /dev/dsk/c4t60060E8004F25E000000F25E00000716d0s1
d108 1 1 /dev/dsk/c4t60060E8004F25E000000F25E00000715d0s0
root@hostname #
root@hostname # metastat -p | grep d113
root@hostname #

metainit d113 1 1 /dev/dsk/c4t60060E8004F25E000000F25E00000F0Ed0s0

-----

metattach d113
metattach d113 c4t60060E8004F25E000000F25E00000F0Fd0s0
metattach d113 c4t60060E8004F25E000000F25E00000F1Ad0s0
metattach d113 c4t60060E8004F25E000000F25E00000F1Bd0s0
metattach d113 c4t60060E8004F25E000000F25E00000F1Cd0s0
metattach d113 c4t60060E8004F25E000000F25E00000F1Dd0s0
metattach d113 c4t60060E8004F25E000000F25E00000F1Ed0s0
metattach d113 c4t60060E8004F25E000000F25E00000F1Fd0s0
metattach d113 c4t60060E8004F25E000000F25E00000F10d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F11d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F12d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F13d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F14d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F15d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F16d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F17d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F18d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F19d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F20d0s0
metattach d113 c4t60060E8004F25E000000F25E00000F21d0s0

+ metastat -p d113
d113 20 1 /dev/dsk/c4t60060E8004F25E000000F25E00000F0Ed0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F0Fd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F1Ad0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F1Bd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F1Cd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F1Dd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F1Ed0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F1Fd0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F10d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F11d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F12d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F13d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F14d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F15d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F16d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F17d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F18d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F19d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F20d0s0 \
1 /dev/dsk/c4t60060E8004F25E000000F25E00000F21d0s0
root@hostname #newfs -Tv /dev/md/rdsk/d113
root@hostname # newfs -Tv /dev/md/rdsk/d113
newfs: construct a new file system /dev/md/rdsk/d113: (y/n)? y
mkfs -F ufs /dev/md/rdsk/d113 1060308480 512 15 8192 8192 -1 1 90 1048576 t 0 -1 8 16 y
/dev/md/rdsk/d113: 1060308480 sectors in 138061 cylinders of 15 tracks, 512 sectors
517728.8MB in 1424 cyl groups (97 c/g, 363.75MB/g, 384 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 745504, 1490976, 2236448, 2981920, 3727392, 4472864, 5218336, 5963808,
6709280,
Initializing cylinder groups:
............................
super-block backups for last 10 cylinder groups at:
1053376544, 1054122016, 1054867488, 1055612960, 1056358432, 1057103904,
1057849376, 1058594848, 1059340320, 1060085792
root@hostname #

Solaris Moving Directories to Other Location

2008-12-13T12:04:00.003+08:00

Sometimes using tar we receive error file too large. Use cpio instead for same results
% cd /target-directory

% find . -depth -print | cpio -pudmv /dest-directory

example

#! /bin/sh
cd /ftp/data/pdu-msa/EDA-SLS
find . -depth -print | cpio -pudmv /ftp/data2/pdu-msa/EDA-SLS

Sol10: How to mount lofs from localzone

2008-11-07T16:27:00.000+08:00

Sol10: How to mount lofs from localzone
---------------------------------------
On global zone, mounted file system looks like this

/dev/md/dsk/d113 530063064 65560 524696880 1% /zones/myzone/ftp/data2

run this zonecfg command
zonecfg -z myzone
> add fs
> set dir=/ftp/data2
> set special=/zones/myzone/ftp/data2
> set type=lofs
> end
> verify
> commit
> exit

run below command to confirm
#zonecfg -z myzone info
....
fs:
dir: /ftp/data2
special: /zones/myzone/ftp/data2
raw not specified
type: lofs
options: []

....

root@myzone # mount -F lofs /ftp/data2 /ftp/data2

root@myzone # df -k /ftp/data2
Filesystem kbytes used avail capacity Mounted on
/ftp/data2 530063064 65560 524696880 1% /ftp/data2

Solaris 10 How to stop start automountd

2008-09-21T05:10:00.002+08:00

# svcs | grep auto
legacy_run Oct_24 lrc:/etc/rc2_d/S72autoinstall
online 17:31:10 svc:/system/filesystem/autofs:default
To stop
# svcadm -v disable svc:/system/filesystem/autofs:default
To start
# svcadm -v enable svc:/system/filesystem/autofs:default

HPUX GSP toggle between console and command mode

2008-09-19T14:41:00.008+08:00

CO : COnsole- leave command mode and return to console mode
This command exits the GSP command interface, and connects to the system console. All mirrored users are switched. Type CTRL-B to return to the GSP command interface.

HPUX GSP Console get write access

2008-09-19T14:41:00.006+08:00

Typing "CO" from the GSP Command interface provides a mirrored version of the OS console. All mirrored users see the same output. At any time, only one of the mirrored users has write access to the console. To get write access to the console, type CTRL-e c f (not CTRL-e CTRL-c CTRL-f).

SEE ALSO: CO (COnsole)

Solaris when LUN dynamically removed JNI

2008-09-19T14:41:00.005+08:00

When the driver dynamically removes a LUN, not all references to that
LUN are removed. This is because the file system nodes in the
/dev/dsk and /dev/rmt directories are scanned to show the devices.
However, when devices are removed dynamically via EZ Fibre or the
jnic146x_update_drv command, only the kernel device nodes are
removed. To remove the actual file system nodes, execute the
following command:

#devfsadm -C -v

Solaris verify LUN disk size

2008-09-19T14:41:00.004+08:00

Verify size of LUN.
# prtvtoc /dev/rdsk/c#t#d#s2 > vtoc.lun.out

Solaris save format output to file

2008-09-19T14:41:00.003+08:00

# echo|format > format.out

This is useful when you have new disk/lun, and lazy to find out which one is new
And make it easy if you wnat to execute command as below

#metattach d017 /dev/dsk/c6t60060E8004F25E000000F25E000009E1d0

root@hostorap1 # grep -i warning /var/adm/messages
Sep 18 10:07:28 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e00000623 (ssd34):
Sep 18 10:07:28 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e00000622 (ssd35):
Sep 18 10:07:28 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e00000621 (ssd36):
Sep 18 10:07:28 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e00000620 (ssd37):
Sep 18 10:07:28 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e0000061f (ssd38):
Sep 18 10:07:28 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e0000061e (ssd39):
Sep 18 10:07:29 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e0000061d (ssd40):
Sep 18 10:07:29 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e0000061c (ssd41):
Sep 18 10:07:29 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e0000061b (ssd42):
Sep 18 10:07:29 hostorap1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e0000061a (ssd43):
Sep 18 10:07:29 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e00000619 (ssd44):
Sep 18 10:07:29 host scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8004f25e000000f25e00000618
root@host # more format.out
Searching for disks...done

c6t60060E8004F25E000000F25E000009E1d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E000009E2d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E000009E3d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E000009E4d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E0000061Ad0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E0000061Bd0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E0000061Cd0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E0000061Dd0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E0000061Ed0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E0000061Fd0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E00000618d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E00000619d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E00000620d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E00000621d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E00000622d0: configured with capacity of 25.28GB
c6t60060E8004F25E000000F25E00000623d0: configured with capacity of 25.28GB

AVAILABLE DISK SELECTIONS:
0. c0t0d0
/ssm@0,0/pci@18,600000/pci@2/scsi@2/sd@0,0
1. c1t0d0
/ssm@0,0/pci@1c,600000/pci@2/scsi@2,1/sd@0,0
2. c6t60060E8004F25E000000F25E00000DE8d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000de8
3. c6t60060E8004F25E000000F25E00000DE9d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000de9
4. c6t60060E8004F25E000000F25E00000DEAd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000dea
5. c6t60060E8004F25E000000F25E00000DEBd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000deb
6. c6t60060E8004F25E000000F25E00000EA0d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000ea0
7. c6t60060E8004F25E000000F25E00000EA1d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000ea1
8. c6t60060E8004F25E000000F25E00000EA2d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000ea2
9. c6t60060E8004F25E000000F25E00000EA3d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000ea3
10. c6t60060E8004F25E000000F25E00000EA4d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000ea4
11. c6t60060E8004F25E000000F25E00000EA5d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000ea5
12. c6t60060E8004F25E000000F25E00000EA6d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000ea6
13. c6t60060E8004F25E000000F25E00000EA7d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000ea7
14. c6t60060E8004F25E000000F25E000004A4d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e000004a4
15. c6t60060E8004F25E000000F25E000004A5d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e000004a5
16. c6t60060E8004F25E000000F25E000004A6d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e000004a6
17. c6t60060E8004F25E000000F25E000004A7d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e000004a7
18. c6t60060E8004F25E000000F25E000009E1d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e000009e1
19. c6t60060E8004F25E000000F25E000009E2d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e000009e2
20. c6t60060E8004F25E000000F25E000009E3d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e000009e3
21. c6t60060E8004F25E000000F25E000009E4d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e000009e4
22. c6t60060E8004F25E000000F25E0000037Ad0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000037a
23. c6t60060E8004F25E000000F25E0000037Bd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000037b
24. c6t60060E8004F25E000000F25E0000037Cd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000037c
25. c6t60060E8004F25E000000F25E0000037Dd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000037d
26. c6t60060E8004F25E000000F25E0000037Ed0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000037e
27. c6t60060E8004F25E000000F25E0000037Fd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000037f
28. c6t60060E8004F25E000000F25E0000061Ad0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000061a
29. c6t60060E8004F25E000000F25E0000061Bd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000061b
30. c6t60060E8004F25E000000F25E0000061Cd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000061c
31. c6t60060E8004F25E000000F25E0000061Dd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000061d
32. c6t60060E8004F25E000000F25E0000061Ed0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000061e
33. c6t60060E8004F25E000000F25E0000061Fd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000061f
34. c6t60060E8004F25E000000F25E0000097Ad0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000097a
35. c6t60060E8004F25E000000F25E0000097Bd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000097b
36. c6t60060E8004F25E000000F25E0000097Cd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000097c
37. c6t60060E8004F25E000000F25E0000097Dd0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000097d
38. c6t60060E8004F25E000000F25E0000097Ed0
/scsi_vhci/ssd@g60060e8004f25e000000f25e0000097e
39. c6t60060E8004F25E000000F25E00000378d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000378
40. c6t60060E8004F25E000000F25E00000379d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000379
41. c6t60060E8004F25E000000F25E00000380d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000380
42. c6t60060E8004F25E000000F25E00000381d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000381
43. c6t60060E8004F25E000000F25E00000382d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000382
44. c6t60060E8004F25E000000F25E00000383d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000383
45. c6t60060E8004F25E000000F25E00000618d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000618
46. c6t60060E8004F25E000000F25E00000619d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000619
47. c6t60060E8004F25E000000F25E00000620d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000620
48. c6t60060E8004F25E000000F25E00000621d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000621
49. c6t60060E8004F25E000000F25E00000622d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000622
50. c6t60060E8004F25E000000F25E00000623d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000623
51. c6t60060E8004F25E000000F25E00000979d0
/scsi_vhci/ssd@g60060e8004f25e000000f25e00000979
Specify disk (enter its number):
root@host #

Solaris replicate copy disk structure partition

2008-09-19T14:41:00.001+08:00

Make sure disk have same geometry.
Usefull if you wnat to add new disk and lazy to repartion new disk

# prtvtoc /dev/rdsk/c?t?d?s2 | fmthard -s - /dev/rdsk/c?t?d?s2

HPUX 9000/800/rp3440 how to power off and on

2008-09-18T23:33:00.001+08:00

1- Login to the OS as root and issue #init 0
2- Login to GSP
Disable all types of remote access (see SA command)
*************************************************************************

*************************************************************************
Your Certificate is expired.
Use the SO command to generate a new certificate.
*************************************************************************

MP MAIN MENU:

CO: Console
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Log
SL: Show Event Logs
HE: Main Help Menu
X: Exit Connection

[Server-rib] MP> CM
[Server-rib] MP:CM> pc -off

PC -off

System will be powered off.

You must shut down the OS manually before this command is executed.
Failure to do this can cause problems when the OS is restarted.
Confirm? (Y/[N]): y
y

-> System is being powered off.

-> Command successful.

[Server-rib] MP:CM> PC -on

Usage: PC [ -on | -off | -cycle ] [ -nc ]
PC -?

Solaris find out what type of lun hardware and command to check it out

2008-09-17T15:57:00.006+08:00

Solaris find out what type of lun hardware and command to check it out

HDS #lunstat
format output
10. c4t98d6 DGC-RAID5-0219 cyl 40958 alt 2 hd 128 sec 10
/pci@9,600000/lpfc@1/sd@62,6

HP XP #xpinfo
format output
10. c2t4d10 HP-OPEN-E-SUN-2108 cyl 19757 alt 2 hd 15 sec 96
/pci@3,2000/fibre-channel@2/sd@4,a
To detect new luns
#cfgadm -al -o show_SCSI_LUN
#devfsadm
check messages for corrupt label, that's th new disk/lun

JNI

configuration files

/kernel/drv/

```
jnic146x.conf
```
```
jnic/conf
```
```
fcaw.conf
```
```
fca-pci.conf
```

code diag commands (from OBP)

```
fce-test - test the emerald chip
```
```
loop-init - verifies loop
```

fcd-loop - veifies loop on dual port adaper

```
prt-cfg - configure the adapters port
```

set-bootn-wwn - set the wwn of the boot disk

How to verify firmware level (from Solaris)

#prtconf -cp |grep fcode

How to verify presence of adapters in os

#prtconf -v |grep -i JNI

#prtconf -v |grep -i FCA

#modinfo | grep -i jni

---------------------------------------------------------------------------------------

Storage Systems

* Hitachi USP V, USP, NSC, AMS, WMS Series
* Hitachi Lightning™ 9900 and 9900 V Series
* Hitachi Thunder™ 9200 and 9500 V Series
* EMC Symmetrix™ 4.8, 5.0, 5.5
* EMC DMX 800, 1000, 2000, 3000
* EMC CLARiiON™ CX-Series, FC-4700
* HP XP Series 48, 128, 512, 1024, 10000, 12000
* HP EVA 3000, 4000, 5000, 6000, 8000
* HP MSA 1000, 1500
* HP HSG
* HP NAS, All-in-One Storage NAS
* HP EFS Clustered NAS Gateway
* HP ESL, EML tape libraries
* IBM DS4000 Series (Formerly FAStT Series)
* IBM DS4500, DS4800
* IBM ESS 800, F20
* IBM DS6000, DS6800, DS8000, DS8100, DS8300
* IBM 3581, 3582, 3583, and 3584 tape libraries
* LSI Engenio E2600, E4600, E5600, E6000
* NetApp FAS, V-Series, NearStore with Data ONTAP 6.5-7.1
* 3PAR InServ
* SGI InfiniteStorage TP Series
* Sun StorageTek 9900 , 9985, 9990
* Sun StorageTek 3510, 3511, 6130, 6140, 6540, 6920, 6940
* Sun StorageTek NAS 5210, 5310, 5320
* Sun (Formerly StorageTek) Flexline™ 200/300 Series
* Xiotech Magnitude 3D

Host Bus Adapters (HBAs)

Various HBA series and models from each of the following HBA vendors:

* Emulex
* HP
* IBM
* AMCC (Formerly JNI)
* LSI
* Qlogic
* Sun

Solaris 10 patching zones

2008-09-17T10:39:00.000+08:00

How to Apply a Patch to the Global Zone Only
global# patchadd -G patch_id

How to Apply a Patch to the Global Zone and All Non-Global Zones
global# patchadd patch_id

How to Apply a Patch to a Specified Non-Global Zone Only
To apply a patch to a specified non-global zone only,
the SUNW_PKG_ALLZONES package parameter for all packages
in the patch set must be set to false.

local-zone# patchadd patch_id

How to Remove a Patch From the Global Zone and All Non-Global Zones
global# patchrm patch_id

How to Remove a Patch From a Specified Non-Global Zone Only
To remove a patch from a specified non-global zone only,
the SUNW_PKG_ALLZONES package parameter for all packages
in the patch set must be set to false.

my-zone# patchrm patch_id

Solaris 10 How to Add a Package

2008-09-17T10:33:00.001+08:00

How to Add a Package to a Specified Non-Global Zone Only

local-zone# pkgadd -d /dir package_name

How to Add a Package to the Global Zone and All Non-Global Zones

global# pkgadd -d /dir package_name

How to Add a Package to the Global Zone Only

global# pkgadd -d /dir -G package_name

Solaris 10 modify the network configuration of a running zone

2008-09-17T10:14:00.000+08:00

To add:
global# ifconfig bge0 addif 192.168.200.202 zone myzone
To remove:
global# ifconfig bge0 removeif 192.168.200.202

Solaris 10 login to zone console

2008-09-16T14:14:00.001+08:00

login to global zone

# zoneadm list -vc
ID NAME STATUS PATH
0 global running /
1 zone1 running /zone/1

# zlogin -C -e\@ zone1
[Connected to zone 'zone1' console]

zone1 console login:

zone1 console login:

zone1 console login: @.
[Connection to zone 'zone1' console closed]
#

VXVM: determine current booted disk

2008-09-16T13:55:00.000+08:00

% prtconf -vp | grep bootpath

VXVM: quickly mirroring an empty volume

2008-09-16T13:45:00.000+08:00

Use the command below to create empty mirrored volume

# vxassist make newvol 10m layout=concat-mirror init=active disk1 disk2

Solaris v440 replace failed power supply

2008-09-12T08:44:00.001+08:00

Need to login to System Controller
sc>
SC Alert: PSU @ PS1 has FAILED.

sc> removefru PS1
Are you sure you want to remove PS1 [y/n]? y
sc>
SC Alert: PSU @ PS1 has FAILED.

SC Alert: PSU @ PS1 has FAILED.

SC Alert: PSU @ PS1 has FAILED.

SC Alert: PSU @ PS1 has been removed.

SC Alert: Required PSU @ PS1 is not present.

SC Alert: PSU @ PS1 has been inserted.

sc> poweron PS1
sc>

HPUX How to check if patch have been installed and install the patch

2008-09-08T10:36:00.000+08:00

let say we want to check for this patch
phkl_36745 and phne_37489

# swlist -l patch | grep -i phkl_36745
PHKL_36745.LVM-KRN 1.0 LVM.LVM-KRN applied
PHKL_36745.CORE2-KRN 1.0 OS-Core.CORE2-KRN applied
# PHKL_36745 1.0 LVM Cumulative Patch
# PHKL_36745.CORE2-KRN 1.0 OS-Core.CORE2-KRN applied
# PHKL_36745.LVM-KRN 1.0 LVM.LVM-KRN applied
# swlist -l patch | grep -i phne_37489
#

This shows that patch phkl_36745 is installed and phne_37489 is not installed yet

1. Back up your system before installing a patch.

2. Login as root.

3. Download and Copy the patch to the /tmp directory.

4. Move to the /tmp directory and unshar the patch:

cd /tmp
sh PHNE_37489

5. Run swinstall to install the patch:

swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_37489.depot

By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_37489. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:

-x patch_save_files=false

WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.

For future reference, the contents of the PHNE_37489.text file is
available in the product readme:

swlist -l product -a readme -d @ /tmp/PHNE_37489.depot

To put this patch on a magnetic tape and install from the
tape drive, use the command:

dd if=/tmp/PHNE_37489.depot of=/dev/rmt/0m bs=2k

HPUX check network interface ip and status

2008-09-05T11:39:00.002+08:00

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/1/2/0 0x00156004DF56 0 UP lan0 snap0 1 ETHER Yes 119
VLAN5001 0x00156004DF56 5001 UP lan5001 snap5001 7 ETHER Yes 119
VLAN5000 0x00156004DF56 5000 UP lan5000 snap5000 6 ETHER Yes 119
0/1/2/1 0x00156004DF57 1 UP lan1 snap1 2 ETHER Yes 119
0/5/1/0 0x00163584E02A 2 UP lan2 snap2 3 ETHER Yes 119
#
# ifconfig lan0
ifconfig: no such interface
# ifconfig lan2
ifconfig: no such interface
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan5001 1500 172.30.225.0 mama201-nb 2531362 0 18691869 0 0
lan5000 1500 142.133.20.0 mama201 1388313474 0 1440717679 0 0
lo0 4136 loopback localhost 30234682 0 30234690 0 0
# ifconfig lan5001
lan5001: flags=4000000000001843
inet 172.30.225.26 netmask ffffff00 broadcast 172.30.225.255
#j

Sudoers Example: su - root

2008-09-05T10:24:00.002+08:00

As root
#visudo
add below lines, where user123 is uid that need su - privillage
user123 ALL=(ALL) /usr/bin/su -
user124 ALL=(ALL) /usr/bin/su -
user125 ALL=(ALL) /usr/bin/su -
user126 ALL=(ALL) /usr/bin/su -
:wq!

as user123
user123% sudo su -
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these two things:

#1) Respect the privacy of others.
#2) Think before you type.

Password:

Authorized access only!

root#

Solaris VXVM grow online filesystem

2008-08-31T20:18:00.001+08:00

root# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c0t1d0s2 sliced x50008 x500 online
c0t2d0s2 sliced x50007 x500 online
c0t3d0s2 sliced x50004 x500 online
c2t0d0s2 sliced disk01 rootdg online
c2t1d0s2 sliced x50002 x500 online
c2t2d0s2 sliced x50006 x500 online spare
c2t3d0s2 sliced x50003 x500 online
c3t0d0s2 sliced x50009 x500 online
c3t1d0s2 sliced x50001 x500 online
c3t3d0s2 sliced x50005 x500 online
root# vxassist -g x500 maxsize
Maximum volume size: 156450816 (76392Mb)

root# df -k /opt/app/backup
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/x500/app-back
9654053 9149133 473813 96% /opt/app/backup
root#
root# ./vxresize -F vxfs -g x500 app-back +3g
root# df -k /opt/app/backup
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/x500/app-back
12799781 9149903 3422212 73% /opt/app/backup
root#

Solaris sar %sys cpu high

2008-07-30T22:54:00.003+08:00

How to find out which pid is consuming %usr kernel cpu resources
#prstat -m
eg.
$ prstat -m
PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/NLWP
3828 hpfimhas 24 75 1.1 0.0 0.0 0.0 0.0 0.0 0 0 87K 0 prstat/1
3812 root 0.1 0.1 0.0 0.0 0.0 0.0 100 0.0 9 0 224 0 sshd/1
3820 hpfimhas 0.0 0.0 0.0 0.0 0.0 0.0 100 0.0 38 0 128 0 sshd/1
3822 hpfimhas 0.0 0.0 0.0 0.0 0.0 0.0 100 0.0 3 0 110 0 sh/1
6105 instbas 0.0 0.0 0.0 0.0 0.0 73 27 0.0 10 0 14 0 java/48
6006 lmcbejo 0.0 0.0 0.0 0.0 0.0 87 13 0.0 23 1 16 0 java/30
13769 instbas 0.0 0.0 0.0 0.0 0.0 91 9.4 0.0 4 0 9 0 java/128
5974 instbas 0.0 0.0 0.0 0.0 0.0 84 16 0.0 16 0 10 0 java/57

For solaris 10 can use dtrace, see example below

On with the show: let's say you're looking at mpstat(1) output on your
multiuser server. You might see something like this:

CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl
12 1 27 3504 338 206 765 27 114 65 1 337 9 19 41 31
13 1 19 5725 98 68 723 22 108 120 0 692 3 17 20 61
14 0 57 3873 224 192 670 22 75 86 1 805 7 10 35 48
15 36 7 1551 42 28 689 6 68 59 0 132 2 9 35 54
16 14 7 7209 504 457 1031 37 125 244 0 459 6 30 4 60
17 5 5 4960 150 108 817 37 98 154 0 375 6 26 6 62
18 5 6 6085 1687 1661 741 60 76 248 0 434 3 33 0 64
19 0 15 10037 72 41 876 23 100 291 1 454 2 19 9 71
20 12 5 5890 746 711 992 32 122 216 2 960 10 33 4 53
21 60 5 1567 729 713 467 15 80 59 0 376 2 35 10 53
22 0 6 4378 315 291 751 17 84 142 1 312 3 16 1 80
23 0 6 12119 33 3 874 20 82 384 1 513 4 24 11 62

And well you may wonder (as perhaps you often have) -- what the hell is
causing all of those cross calls, anyway? (Cross calls appear in the "xcal"
column; see mpstat(1).)

Using DTrace, investigating this is a snap:

# dtrace -n xcalls'{@[execname] = count()}'
dtrace: description 'xcalls' matched 4 probes
[ letting this run for a few seconds ]
^C

mozilla-bin 1
lockd 1
in.mpathd 2
nsrmmd 5
grep 6
chmod 6
cat 6
nwadmin 13
ls 24
in.tftpd 28
nsrindexd 34
fsflush 38
cut 42
find 42
mkdir 66
rm 76
ipop3d 78
scp 79
inetd 96
dtrace 111
nawk 118
imapd-simmonmt 126
rmdir 132
sshd 138
rpc.rstatd 159
mv 398
save 1292
gzip 1315
get_all2 1678
sched 1712
nfsd 3709
tar 27054 <----- high usage

Solaris 10: mount a disk slice in a sub-zone

2008-07-09T15:01:00.001+08:00

Non-global zones in Solaris 10 do not have the ability to see drives or disk slices (to prove this, list the contents of /dev/dsk from within a zone). What filesystems are mounted in which zones is controlled exclusively from the global zone. This recipe describes persistently mounting a disk slice in a non-global zone.
To mount the device c0t1d0s3 in the existing zone testzone under the mount point /mnt, login to the global zone and become root or a priviledged user and complete the following steps:

zonecfg -z testzone
zonecfg:testzone> add fs
zonecfg:testzone:fs> set dir=/mnt
zonecfg:testzone:fs> set special=/dev/dsk/c0t1d0s3
zonecfg:testzone:fs> set raw=/dev/rdsk/c0t1d0s3
zonecfg:testzone:fs> set type=ufs
zonecfg:testzone:fs> end
zonecfg:testzone> verify
zonecfg:testzone> commit
zonecfg:testzone> exit

Following the commit command, the filesystem will be immediately available in the zone. Substitute the desired mount point and device name for your system. If the zone has not yet been created, you can use the 'add fs' commands when creating the zone.

Solaris SVM grow concat//stripe

2008-07-09T13:52:00.000+08:00

Solaris Netapps add new filesystem

2008-05-30T20:26:00.000+08:00

The following volume options should be configured:
Nosnap No automatic scheduled Snapshot™ duplications
Minra Minimal read ahead
Nvfail NVRAM check and behavior
sapfiler1> vol options sapdata nosnap on
sapfiler1> vol options sapdata minra on
sapfiler1> vol options sapdata nvfail on
sapfiler1> vol options saplog nosnap on
sapfiler1> vol options saplog minra on
sapfiler1> vol options saplog nvfail on
sapfiler1> qtree create /vol/sapdata/sapdata_lun
sapfiler1> qtree create /vol/saplog/saplog_lun
sapfiler1> qtree create /vol/saplog/sapmnt_lun
sapfiler1> qtree create /vol/saplog/sapusr_lun
sapfiler1> qtree create /vol/saplog/trans_lun
Create the LUNs
sapfiler1> lun create -s 30g -t solaris /vol/sapdata/sapdata_lun/sapdata
sapfiler1> lun create -s 5g -t solaris /vol/saplog/saplog_lun/saplog
sapfiler1> lun create -s 500m -t solaris /vol/saplog/sapmnt_lun/sapmnt
sapfiler1> lun create -s 500m -t solaris /vol/saplog/sapusr_lun/sapusr
sapfiler1> lun create -s 200m -t solaris /vol/saplog/trans_lun/trans
Define the initiator group
To create the initiator group you need to know the WWPN of the host, which will use these LUNs. The
WWPN can be obtained with the sanlun command on the host.
bash-2.03# sanlun fcp show adapter
lpfc0 WWPN:10000000c92d55f3
sapfiler1> igroup create -f -t solaris pp400 10:00:00:00:c9:2d:55:f3
Map the LUNs to the initiator group
sapfiler1> lun map /vol/sapdata/sapdata_lun/sapdata pp400 0
sapfiler1> lun map /vol/saplog/saplog_lun/saplog pp400 6
sapfiler1> lun map /vol/saplog/sapusr_lun/sapusr pp400 7
sapfiler1> lun map /vol/saplog/sapmnt_lun/sapmnt pp400 8
sapfiler1> lun map /vol/saplog/trans_lun/trans pp400 9

Configure persistent binding
Persistent binding is configured with the tool /usr/sbin/lpfc/lputil . To configure persistent
binding you need to know the WWNN of the filer. The WWNN can be obtained with the sysconfig
command at the filer console.
sapfiler1> sysconfig –v
…………
…………
slot 3: Fibre Channel Target Host Adapter 3a
(Dual-channel, QLogic 2312 (2342) rev. 2, 64-bit, )
Firmware rev: 3.1.15
Host Port Addr: 011000
Cacheline size: 8
SRAM parity: Yes
FC Nodename: 50:a9:80:00:02:00:88:f7 (50a98000020088f7)
FC Portname: 50:a9:80:03:02:00:88:f7 (50a98003020088f7)
Connection: PTP, Fabric
After using lputil command the lpfc.conf file has the following entry.
File /kernel/drv/lpfc.conf
…………
…………
# BEGIN: LPUTIL-managed Persistent Bindings
fcp-bind-WWNN="50a98000020088f7:lpfc0t1";
Network Appliance Inc. Proprietary
7
TECHNICAL REPORT
File /kernel/drv/lpfc.conf
…………
…………
# BEGIN: LPUTIL-managed Persistent Bindings
fcp-bind-WWNN="50a98000020088f7:lpfc0t1";
Edit entries in /kernel/drv/sd.conf
The LUN IDs that were used when mapping the LUNs to the initiator groups and the SCSI ID that was
used with the lputil command have to be used in the entries in /kernel/drv/sd.conf.
…………
…………
name="sd" parent="lpfc" target=1 lun=0;
name="sd" parent="lpfc" target=1 lun=1;
name="sd" parent="lpfc" target=1 lun=2;
name="sd" parent="lpfc" target=1 lun=3;
name="sd" parent="lpfc" target=1 lun=4;
name="sd" parent="lpfc" target=1 lun=5;
name="sd" parent="lpfc" target=1 lun=6;
name="sd" parent="lpfc" target=1 lun=7;
name="sd" parent="lpfc" target=1 lun=8;
name="sd" parent="lpfc" target=1 lun=9;

Reboot with reconfigure
After the new entries in /kernel/drv/sd.conf are edited, the host needs to be rebooted with the
reconfigure option. reboot -- -r

Configure new disks with format command
The new disks can now be configured with the format command.

VCS Adding node to the existing cluster

2008-05-30T20:10:00.000+08:00

Adding the node to the existing cluster
Perform the tasks on one of the existing nodes in the cluster.
To add the new node to the existing cluster
1 Enter the command:
# haconf -makerw
2 Add the new system to the cluster:
# hasys -add east
3 Enter the following command:
# haconf -dump
4 Copy the main.cf file from an existing node to your new node:
# rcp /etc/VRTSvcs/conf/config/main.cf east:/etc/VRTSvcs/conf/
config/
5 Start VCS on the new node:
# hastart
6 If necessary, modify any new system attributes.
7 Enter the command:
# haconf -dump -makero
Start VCS after adding the new node to the cluster and verify the cluster.
To start VCS and verify the cluster
1 From the new system, start VCS with the new system added to the cluster:
# hastart
2 Run the GAB configuration command on each node to verify that Port a and
Port h include the new node in the membership:
# /sbin/gabconfig -a
GAB Port Memberships
===================================
Port a gen a3640003 membership 012
Port h gen fd570002 membership 012

Solaris emc powerpath link problem

2008-05-30T20:02:00.000+08:00

If you boot a Solaris host with all socal host adapters to storage
system volumes disconnected or dysfunctional, PowerPath will not
configure any socal host adapter paths. After physically restoring the
socal connections, run the following commands to restore the paths
in PowerPath:

On hosts running this OS Run these commands
Solaris 7 and 8
devfsadm
powercf -q
powermt config
Solaris 2.6
drvconfig; disks; devlinks
powercf -q
powermt config