About VXassist

* Sorry ini sumbernya lupa dari mana,tapi cukup berguna buat yang saya *
General
1. Creating a Volume
1.1 Creating a Concatenated Volume
1.2 Creating a Striped Volume
1.3 Creating a RAID-5 Volume
2. Extending a Volume
2.1 Extending a volume up to certain length,
2.2 Extending by a Given Length
3. Shrinking a Volume
3.1 Shrinking to a Given Length
3.2 Shrinking by a Given Length
4. Removing a Volume
5. Mirroring a Volume
5.1 Creating & Mirroring a New Volume
5.2 Mirroring an Existing Volume
5.3 Mirroring All Volumes


6. Removing a Mirror
7. Adding a RAID-5 Log
8. Adding a DRL Log
9. Removing a RAID-5 Log
10.Preparing a Volume for Online Backup
11.Displaying Volume Configuration Information

General
The vxassist utility in Veritas Volume Manager is used to create volumes, add mirrors and logs to existing volumes, extend and shrink existing volumes, provides for the migration of data from a specified set of disks, and provides facilities for the on-line backup of existing volumes.
The default behavior of vxassist is to create volumes in the rootdg diskgroup if diskgroup is not specified . The default length is taken as number of blocks but this can be specified in Kilobytes orMegabytes or Gigabytes.

vxassist command syntax :

vxassist volume_name [attributes]

Commonly used options are given below (See man vxassist for complete list of supported options)
-g for specifying diskgroups
-b for background operation
-d file containing defaults for vxassist if not specified /etc/default/vxassist is used

Keywords used are make , mirror , move , growto ,growby ,shrintto ,shirnkby ,snapstart , snapshot ,snapwait

Attributes specify volumes layout disks controllar to include exclude etc

Device Nodes :

Default rootdg disk group.
Block Device Node /dev/vx/dsk/volume_name
Raw Device Node /dev/vx/rdsk/volume_name
Other DiskGroups
Block Device Node /dev/vx/dsk/diskgroup_name/volume_name
Raw Device Node /dev/vx/rdsk/diskgroup_name/volume_name

_______________________________________

1. Creating a Volume :

1.1 Creating a Concatenated Volume

By default, vxassist creates a concatenated volume using the space available on a disk or on the number of disks in a diskgroup if the volume size specified is more then the one available on a single disk.

Disks can be specified from a diskgroup for a volume group but if not mentioned available disks are selected by the volume manager.

Command syntax :

· vxassist make volume_name volume_length

To create a new volume appvol of 100 MB in the default disk group rootdg with available disks:

·
#vxassist make appvol 100m

To create the volume appvol of 100MB on disk03

· #vxassist make appvol 100m disk03



1.2 Creating a Striped Volume

A striped volume contains at least one plex that consists of two or more subdisks located on two or more physical disks.

Command Syntax :

· vxassist make volume_name length layout=stripe

To create a striped volume appvol2 with the default stripe unit size on the default number of disks

· #vxassist make appvol2 100m layout=stripe

To create a striped volume appvol2 100MB striped volume on three specific disks.

· #vxassist make appvol2 100m layout=stripe disk04 disk05 disk06

1.3 Creating a RAID-5 Volume

A RAID-5 volume contains a RAID-5 plex that consists of two or more subdisks located on two or more physical disks. Only one RAID-5 plex can exist per volume. A RAID-5 volume may also contain one or more RAID-5 log plexes, which are used to log information about data and parity being written to the volume.

Command Syntax :

· vxassist make volume_name length layout=raid5

To create the RAID-5 volume appvol4 with the default stripe unit size on the default number of disks with RAID-5 log,

· #vxassist make appvol4 100m layout=raid5.

2. Extending a Volume

Caution : If you plan to use volume size change (grow or shrink ) on a volume with data make sure you have the good backup of the volume available before carrying out such operation .

2.1 Extending a volume up to certain length,

Command syntax

· vxassist growto volume_name length

To extend vol3 upto 8000 sectors, type:

· #vxassist growto vol3 8000

2.2 Extending by a Given Length

Command Syntax

· vxassist growby volume_name length

To extend volapp by 1000 sectors, type:

· #vxassist growby volapp 1000

3. Shrinking a Volume

Caution - Do not shrink a volume below the size of the file system. If you have a VxFS file system, you can shrink the file system and then shrink the volume. If you do not shrink the file system first, you risk unrecoverable data loss.

Always make sure you have a good backup of the data volume to be shirnked.

3.1 Shrinking to a Given Length

Shrink a volume to a specific length as follows:

· vxassist shrinkto volume_name length

Make sure you do not shrink the volume below the current size of the file system or database using the volume. This command can be safely used on empty volumes.

To shrink volcat to 1300 sectors, type:

· #vxassist shrinkto volcat 1300

3.2 Shrinking by a Given Length

Shrink a volume by a specific length as follows:

· vxassist shrinkby volume_name length

To shrink volcat by 8000 sectors, type:

· #vxassist shrinkby volapp2 8000

4. Removing a Volume

Removing a volume requires removing all references to the volumes to be removed like unmounting the volume if mounted and removing its reference from /etc/vfstab .

An active volume has to be stopped first to stop all the activities to the volume only then it can be removed

Stopping Volume :

Command Syntax

· vxvol stop volume_name

To stop appvol1

· #vxvol stop appvol1

Removing Volume

Command Syntax

· vxedit -rf rm volume_name

To remove the volume appvol1

· #vxedit -rf rm appvol11

5. Mirroring a Volume

Mirroring allow data to be written simultaneously to two disks so that in case of failure of one disk data is available from the other mirrored disk. Boot disks can be mirriored to provide alternate booting disk .

5.1 Creating & Mirroring a New Volume

Command Syntax :

· vxassist make volume_name length layout=mirror

To create the mirrored volume, appvol22 of 100mb

· #vxassist make appvol22 100m layout=mirror

To create a volume with Dirty Region Logging enabled

· #vxassist make volume_name length layout=mirror,log

5.2 Mirroring an Existing Volume

Command syntax

· vxassist mirror volume_name

Creating a mirror of volume vol44:

· #vxassist mirror vol44

5.3 Mirroring All Volumes

To mirror all existing volumes to available disk space

· /etc/vx/bin/vxmirror -a

6. Removing a Mirror

Removing a mirror involves first dissociating the plex from its volume and then removing the plex and any associated subdisks completely.The last valid mirror plex associated with a volume cannot be removed.

Dissociate and remove the plex from its volume as follows:

· vxplex -o rm dis plex_name

vxprint -h shows the volume and associated plexes :

Disk group: rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 v volm fsgen ENABLED 10240 - ACTIVE - - pl volm-01 volm ENABLED 10240 - ACTIVE - - sd disk01-02 volm-01 - 10240 0 - - - pl volm-02 volm ENABLED 10240 - ACTIVE - - sd disk02-03 volm-02 - 10240 0 - - -

To disassociate and remove volmir-02 from volmir, type:

· #vxplex -o rm dis volm-02

The output of vxprint -h for volm now shows volume volm with only one plex::

Disk group: rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 v volm fsgen ENABLED 10240 - ACTIVE - - pl volm-01 volmir ENABLED 10240 - ACTIVE - - sd disk01-02 volmir-01 - 10240 0 - - -

7. Adding a RAID-5 Log

A RAID-5 log maintains a copy of the data and parity being written to the volume at any given time. If a system failure occurs, VxVM can replay the RAID-5 log to resynchronize the volume. This copies the data and parity that was being written at the time of failure from the log to the appropriate areas of the RAID-5 volume.

RAID-5 log plexes are used to log information about data and parity being written to the raid volume. A log plex is created for the volume by default when a raid volume is created but additional ones can be added by following command .

· vxassist addlog name_of_raid5_vol

8. Adding a DRL Log

Dirty region logging (DRL) is used with mirrored volume layouts. DRL keeps track of the regions that have changed due to I/O writes to a mirrored volume. Prior to every write, a bitmap is written to a log to record the area of the disk that is being changed. In case of system failure, DRL uses this information to recover only the portions of the volume that need to be recovered.

To put Dirty Region Logging into effect for a volume, a log subdisk must be added to that volume and the volume must be mirrored. Only one log subdisk can exist per plex.

The following example creates a log for the mirrored volume vol03:

· #vxassist addlog vol03

When vxassist is used to add a log subdisk to a volume, a log plex is also created to contain the log subdisk, by default.

Once created, the plex containing a log subdisk can be treated as a regular plex. Data subdisks can be added to the log plex. The log plex and log subdisk can be removed using the same procedures used to remove ordinary plexes and subdisks.

9. Removing a RAID-5 Log

Removing a RAID-5 log involves first dissociating the log from its volume and then removing the log and any associated subdisks completely.

Dissociate the log from its volume as follows:

· #vxplex -o rm dis plex_name

To identify the log plex, use the command:

· vxprint -ht raid5_volume_name

To disassociate the log plex volrd-02 from volrd, type:

· #vxplex -o rm dis volrd-02



The output of vxprint -h for volrd now shows:

Disk group: rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 v volrd raid5 ENABLED 32 - ACTIVE - - pl volrd-01 volrd ENABLED 32 - ACTIVE - - sd disk01-02 volrd-01 - 32 0 - - - sd disk02-03 volrd-01 - 32 0 - - -



10. Preparing a Volume for Online Backup

Volume manager provides an easy way to take backup of the online data by creating an offline snapshot mirror of the volume .

The vxassist snapstart operation creates a write-only backup mirror, which is attached to and synchronized with the volume to be backed up and later detached and made offline by vxassist snapshot command . The snapshot volume can be used by backup utilities while the original volume continues to be available for applications and users.

The volume backup method described here does not apply to RAID-5 volumes.

Backing up a volume with vxassist involves the following procedure

Create a snapshot mirror

snapstart starts creating a online snapshot mirror of the volume using the available disk space . The snapshot is completed with vxassist snapshot command when offline snapshot volume is created with a userdefined name .

Command Syntax:

* vxassist snapstart volume_name

To create a snapshot mirror of a volume called vol8, type

* #vxassist snapstart vol8

Create a snapshot volume

Command Syntax

vxassist snapshot volume_name new_volume_name

To create a snapshot volume of vol8, type:

#vxassist snapshot vol8 snapvol8

You can now back up the snapshot volume by whatever means you prefer. To avoid wasting space, you can then remove the snapshot volume, which occupies as much space as the original volume

11 Displaying Volume Configuration Information

The vxprint command can be used to display information about how a volume is configured.

Display the volume, mirror, and subdisk record information for all volumes as follows:

#vxprint -ht


Disk group: rootdg

DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
V NAME USETYPE KSTATE STATE LENGTH READPOL PREFPLEX
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE

dg rootdg 759096729.1025.tweety

dm disk10 c1t0d0s2 sliced 559 1044400 -
dm disk20 c2t0d0s2 sliced 559 1044400 -

v pubs fsgen ENABLED ACTIVE 2288 SELECT -
pl pubs-01 pubs ENABLED ACTIVE 2288 CONCAT - RW
sd disk10-01 pubs-01 disk10 0 2288 0 c0t0d0 ENA

v vol8 fsgen ENABLED ACTIVE 20480 SELECT -
pl vol8-01 vol8 ENABLED ACTIVE 20480 CONCAT - RW
sd disk10-02 vol8-0 disk10 2288 20480 0 c0t1d0 ENA

where dg is a disk group, dm is a disk, v is a volume, pl is a plex, and sd is a subdisk. The top few lines indicate the headers that match each type of output line that follows. Each volume is listed along with its associated plex(es) and subdisk(s).

Display volume-related information for a specific volume as follows:

#vxprint -t volume_name

To display information about vol8, type:

#vxprint -t vol8
Read More..

How To Install TOP Package for solaris

Studycase OS solaris 9,SUN Fire V440 :

* Download package TOP (utility for see prosess daemon/file in system)in www.sunfreeware.com

root # pkgadd -d top-3.6.1-sol9-sparc-local

The following packages are available:
1 SMCtop top
(sparc) 3.6.1

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1


Processing package instance from

top
(sparc) 3.6.1

This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.

LeFebvre et al
Using as the package base directory.
## Processing package information.
## Processing system information.
17 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

Installing top as

## Installing part 1 of 1.
[ verifying class ]

Installation of was successful.

root # /usr/local/bin/top
last pid: 19787; load avg: 0.07, 0.04, 0.04; up 191+17:57:56 11:23:44
97 processes: 96 sleeping, 1 on cpu
CPU states: 94.1% idle, 5.4% user, 0.5% kernel, 0.0% iowait, 0.0% swap
Memory: 2048M phys mem, 94M free mem, 1024M total swap, 908M free swap

PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND
13717 root 29 59 0 94M 36M sleep 498:08 4.46% java
834 root 12 21 0 60M 16M sleep 18.3H 0.99% java
1346 root 2 1 0 25M 20M sleep 54.2H 0.00% esd
5463 root 1 1 0 22M 9568K sleep 25.8H 0.00% esd
3981 smcorau 11 1 0 896M 869M sleep 21.1H 0.00% oracle
5441 root 10 21 0 3912K 2840K sleep 17.2H 0.00% picld
3983 smcorau 1 1 0 893M 858M sleep 251:48 0.00% oracle
3996 root 21 1 0 68M 18M sleep 194:15 0.00% java
5415 root 17 12 0 70M 17M sleep 148:22 0.00% java
3973 smcorau 11 1 0 894M 859M sleep 110:52 0.00% oracle
5491 root 1 1 0 16M 9072K sleep 82:39 0.00% esd
5459 root 1 1 0 7056K 5208K sleep 56:36 0.00% esd
5461 root 1 46 0 8056K 5816K sleep 44:48 0.00% esd
3975 smcorau 11 59 0 894M 859M sleep 33:36 0.00% oracle
13388 root 1 60 0 32M 25M sleep 26:42 0.00% esd
Read More..

krtld: load_exec: fail to expand cpu/$CPU

Hari ini coba install Mseries (M4000) persiapan buat instalasi di salah satu customer, Planning di customer ingin mengkloning server dari SF 890 ke M4000. Kita asumsikan sama2 menggunakan OS solaris 10. Kebetulan dikantor ada server SF V210 dengan 2 disk, diputuskan simulasi dengan server tersebut.

Pertama dibuat Flar archive dari server V120 ini diberinama FlarTest, commandnya :

bash-3.00 # flarcreate -n "FlarTest-os" -c -R / /export/home/FlarTest.flar
Full Flash
Checking integrity...
Integrity OK.
Running precreation scripts...
Precreation scripts done.
Determining the size of the archive...

setalah hampir 2 jam lebih file archive berhasil dibuat, pada saat M4000 dinyalakan dan dimasukan DVD installer solaris 10 11/06, proses boot gagal dengan output seperti berikut :

krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase
panic - boot: exitto64 returned from client program
ok

Waduh !!..googling dan nyari dokumen di sunsolve, akhirnya ketemua bahwa Mseries harus menggunakan Solaris 10 5/08 keatas, pantesan ga bisa buat boot Mseries. Download di webnya SUN.com, burning dan test buat boot ...dan berhasil. Proses instalasi menggunakan NFS dengan metode flash (flar archive).
Read More..

About file iso image in solaris

Cara membuat file iso dari cdrom
# mkisofs -r -o /tmp/disk1.iso /cdrom/cdrom0


cara mounting file iso
# /usr/sbin/lofiadm -a tmp/disk1.iso /dev/lofi/1
# mount -F hsfs -o ro /dev/lofi/1 /test

Cara unmount file iso
# umount /test
# /usr/sbin/lofiadm -d /dev/lofi/1
Read More..

Rlogin (Remote Login) in solaris

Apa itu Rlogin? menurut definisi yg saya tau sih, supaya kita bisa masuk dari system 1 ke system 2 dengan tanpa meminta password root lagi (agak riskan sih, dan sebenarnya tidak disarankan oleh audit security system) kalo menurut manual systemnya rlogin adalah

rlogin establishes a remote login session from your terminal to the remote machine named hostname. Hostnames are listed in the hosts database, which may be contained in the /etc/hosts file, the Network Information Service (NIS) hosts map, the Internet domain name server, or a combination of these. Each host has one official name (the first name in the database entry), and optionally one or more nicknames. Either official hostnames or nicknames may be specified in hostname.

Berikut langkah-langkah untuk rlogin yg dimaksud :
1. Cek Daemon rlogin,
root # more /etc/inetd.conf

+++++++++++++++++++++++++++++++++++++++++
# RLOGIND - rlogin daemon (BSD protocols)
login stream tcp6 nowait root /usr/sbin/in.rlogind in.rlogind
+++++++++++++++++++++++++++++++++++++++++

root # ps -ef | grep inetd
root 147 1 0 Aug 01 ? 0:00 /usr/sbin/inetd -s
root 24051 24027 0 12:18:00 pts/4 0:00 grep inetd

root # kill -HUP 147

root # ps -ef | grep rlogin
root 6262 178 0 11:38:54 ? 0:00 in.rlogind
root 7972 6264 0 12:21:22 pts/4 0:00 grep rlogin
root #


2. tambahkan host yang akan di rlogin
root@HOST-A # more /etc/hosts.equiv
HOST-B
+ root

root@HOST-A # ls -ltr /etc/hosts.equiv
-rw-r--r-- 1 root other 19 Aug 6 11:21 /etc/hosts.equiv
root #

root@HOST-A # more $HOME/.rhosts
HOST-B
+ root
root #

3. tambahkan host yang akan di rlogin
root@HOST-B # more $HOME/.rhosts
HOST-A
+ root
root@HOST-B #

root@HOST-B # more $HOME/.rhosts
HOST-A
+ root
root@HOST-B # more /etc/hosts.equiv
HOST-A
+ root
root@HOST-B # ls -ltr /etc/hosts.equiv
-rw-r--r-- 1 root other 17 Apr 21 2007 /etc/hosts.equiv
root@HOST-B #

*gambar diambil dari http://www.sun.com
Read More..

About SSH (Secure Sheel) in Solaris

# Solaris 9
Untuk Disable service SSH

bash # /etc/init.d/sshd stop
bash # /etc/rc3.d/S89sshd stop

Untuk Enable service SSH

bash # /etc/init.d/sshd start
bash # /etc/rc3.d/S89sshd start

Restart Service SSH

bash # kill -HUP `cat /var/run/sshd.pid`

# Solaris 10
Check service SSH

bash# svcs | grep ssh
online Jan_21 svc:/network/ssh:default

jika offline,

bash # svcadm enable -t network/ssh:default
bash # /lib/svc/method/sshd start

Disable Service SSH,

bash # svcadm disable -t network/ssh:default

Restart service SSH,

bash # svcadm restart network/ssh:default
bash # /lib/svc/method/sshd restart

Refresh service SSH,

bash # svcadm refresh network/ssh:default

Untuk user root supaya bisa gunakan SSH ketika masuk ke system

bash> vi /etc/ssh/sshd_config

[...]
# Valid options are yes, without-password, no.
PermitRootLogin no
[....]

ganti no menjadi yes
Read More..

VxVM vxassist ERROR V-5-1-334 900gb: Invalid length specification

Kemarin, pas nambah mountpoint di salah satu server ketemu error messages seperti ini

root # vxassist -g extdg make extdata66 900gb alloc=extdg09
VxVM vxassist ERROR V-5-1-334 900gb: Invalid length specification

Ceritanya, user mau nambah mounpoint /data_backup sebesar 900Gb. Filesystem dimanage oleh veritas Volume Manager (VxVM), OS yang digunakan solaris 9 type server SunFire 890. Setelah team storage confirm kalau disk baru sebesar 900gb sudah diassaign, pas dicheck disisi server ternyata sudah berhasil dikenal oleh server sebagai :

root # format
c4t50060E80042AB044d15: configured with capacity of 900.62GB
c6t50060E80042AB054d15: configured with capacity of 900.62GB

Ehm,ternyata sudah multipath disknya. pada saat prosess penambahan mounpoint itulah error messages muncul. Bolak-balik nyari solusi,searching di google, cari di www.sun.com tidak menemukan jawaban untuk case ini. Nah pas baca manual mengenail vxassist ternyata solusinya sepele saja, yaitu :

Before :
root # vxassist -g extdg make extdata66 900gb alloc=extdg09
VxVM vxassist ERROR V-5-1-334 900gb: Invalid length specification

After:

root # vxassist -g extdg make extdata66 900g alloc=extdg09

Akhirnya solve juga case ini,hal sepele tapi cukup merepotkan...
Read More..

Postingan Awal

Berhubung blog yg lama,datanya entah kemana (karena salah customize)hehehehe...maklum newbie.


Jadi sementara waktu inilah blog yg akan digunakan, akan ada beberapa kategori dalam blog ini salah satunya mengenai aktivitas termasuk trik tentang solaris. Semoga berguna
Read More..