About Us

RSInfoMinds, a web based IT Training and Consultancy firm. It is established with high dreams in training people in IT Infrastructure Field. We provide Online and Class Room training in various fields of IT Infrastructure Management.

Join Us: http://www.facebook.com/RSInfoMinds
Mail Us: rsinfominds@gmail.com
Twitter: @RSInfoMinds

We are specialized in the below courses:

Redhat Linux Admin Redhat Linux Cluster
Redhat Virutualization IBM AIX Admin
IBM AIX Virtualization IBM AIX Cluster
HP Unix Admin HP Unix Cluster
HP Unix Virtualization Shell Scripting
Veritas Volume Manager Veritas Cluster
Oracle Core DBA VMWare


We provide training in such a way, So that you get in depth knowledge on the Courses you look for.

And we ensure you are very confident from each and every Techincal aspect that the IT Industry needs and expects from you.

We also conduct Workshops on the latest technology and the real time faculties sharing their work experiences to make you the best.

Sunday 18 May 2014

VERITAS Volume Manager on RHEL 6

VxVM is already installed on the machine and below procedure will describe adding disk to VERITAS volume manager and provisioning storage for usage.  In this scenario attached disks are local SCSI disks.
Procedure:
1)    List the available disk using vxdisk command.
[root@node1 /]# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
sda          auto:none       -            -            online invalid
sdb          auto:LVM        -            -            LVM
sdc          auto:none       -            -            online invalid
sdd          auto:none       -            -            online invalid
sde          auto:none       -            -            online invalid
sdf          auto:none       -            -            online invalid
sdg          auto:none       -            -            online invalid
[root@node1 /]#
Note:  
online invalid in the STATUS line indicates that a disk has yet to be added or initialized for VxVM control.
2)    Initialize the disks using vxdisksetup command.
[root@node1 /]# vxdisksetup -i sdc
[root@node1 /]# vxdisksetup -i sdd
3)    Verify that disks are got initialized using vxdisk command.
[root@node1 /]# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
sda          auto:none       -            -            online invalid
sdb          auto:LVM        -            -            LVM
sdc          auto:cdsdisk    -            -            online
sdd          auto:cdsdisk    -            -            online
sde          auto:none       -            -            online invalid
sdf          auto:none       -            -            online invalid
[root@node1 /]#
Note:  
Disks that are listed as online are initialized and the part of VxVM.  
4)    Add the desired disk to disk group using vxdg command. In this scenario we are creating disk group named ITOCDG and adding disk sdc to diskgroup.
[root@node1 /]# vxdg init ITOCDG disk1=sdc
[root@node1 /]# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
sda          auto:none       -            -            online invalid
sdb          auto:LVM        -            -            LVM
sdc          auto:cdsdisk    disk1        ITOCDG       online
sdd          auto:cdsdisk    -            -            online
sde          auto:none       -            -            online invalid
sdf          auto:none       -            -            online invalid
[root@node1 /]#
Note :
we can use vxdg with adddisk switch to add new disks to disk group.
[root@node1 /]# vxdg -g ITOCDG adddisk disk2=sdd
[root@node1 /]# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
sda          auto:none       -            -            online invalid
sdb          auto:LVM        -            -            LVM
sdc          auto:cdsdisk    disk1        ITOCDG       online
sdd          auto:cdsdisk    disk2        ITOCDG       online
sde          auto:none       -            -            online invalid
sdf          auto:none       -            -            online invalid
[root@node1 /]#

5)    To list disk group properties we can use following command.
[root@node1 /]# vxdg list ITOCDG
Group:     ITOCDG
dgid:      1334435551.48.node1.redhat.com
import-id: 1024.47
flags:     cds
version:   170
alignment: 8192 (bytes)
ssb:            on 
autotagging:    on
detach-policy: global
dg-fail-policy: obsolete
copies:    nconfig=default nlog=default
config:    seqno=0.1030 permlen=51360 free=51356 templen=2 loglen=4096
config disk sdc copy 1 len=51360 state=clean online
config disk sdd copy 1 len=51360 state=clean online
log disk sdc copy 1 len=4096
log disk sdd copy 1 len=4096
[root@node1 /]#
6)     Create volume on the disk group with desired size. In this example we are creating volume VOL1 with size 100MB
[root@node1 /]# vxassist -g ITOCDG make VOL1 100m
7)    To list volume details we can use vxlist volume command
   [root@node1 /]# vxlist volume
TY   VOLUME   DISKGROUP        SIZE STATUS    LAYOUT   LINKAGE
vol  VOL1     ITOCDG        100.00m healthy   concat   -

8)    Create file system on the volume using mkfs command, in this example we are creating VXFS file system
[root@node1 /]# mkfs -t vxfs /dev/vx/rdsk/ITOCDG/VOL1
    version 9 layout   
    204800 sectors, 102400 blocks of size 1024, log size 1024 blocks
    rcq size 1024 blocks
    largefiles supported
Note :
/dev/vx/rdsk/ITOCDG/VOL1 is the device file for volume VOL1. For verifying file system we can use fstyp command.
[root@node1 /]# fstyp /dev/vx/dsk/ITOCDG/VOL1
9)    Create a mount point and mount the file system using mount command.
[root@node1 /]# mkdir /veritas1
[root@node1 /]# mount -t vxfs /dev/vx/dsk/ITOCDG/VOL1 /veritas1/
10)  Verify the mounted file system using mount command or df command
[root@node1 /]# mount
/dev/mapper/vg_node1-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)

devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
none on /dev/odm type vxodmfs (rw,smartsync)
/dev/sr0 on /repo type iso9660 (ro)
/dev/sr1 on /media/201204090917 type iso9660 (ro,nosuid,nodev,uhelper=udisks,uid=0,gid=0,iocharset=utf8                                ,mode=0400,dmode=0500)
/dev/vx/dsk/ITOCDG/VOL1 on /veritas1 type vxfs (rw, delaylog, largefiles,ioerror=mwdisable)
Note:
df displays the amount of disk space available on the file system .
[root@node1 /]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_node1-lv_root
                      8.5G  4.5G  3.6G  57% /
tmpfs                 499M  208K  499M   1% /dev/shm
/dev/sda1             485M   32M  429M   7% /boot
/dev/sr0              3.4G  3.4G     0 100% /repo
/dev/sr1              927M  927M     0 100% /media/201204090917
/dev/vx/dsk/ITOCDG/VOL1
                      100M  3.2M   91M   4% /veritas1

[root@node1 /]#

Kernel Build

1. Take a backup of the current runnig kernel.

# cp /boot/initrd-$(uname -r).img /boot/initrd-$(uname -r).img.bak

2.     Rebuild the Initrd image using mkinitrd command


# mkinitrd -f -v /boot/initrd-$(uname -r).img $(uname -r)