Software Technical Solution

To install / remove JDK on SuSE Linux

2018-12-28T11:29:00.002+05:30

1. On new installation Java rpms not exists on SuSE Linux. To verify run below command:
# rpm -qa | grep java
libjavascriptcoregtk-4_0-18-2.12.5-1.12.x86_64

2. Check openjdk package in repository:
# zypper se openjdk-
Loading repository data...
Reading installed packages...

S | Name | Summary | Type
--+-----------------------------+-----------------------------------------------------+--------
| java-1_7_0-openjdk-demo | OpenJDK 7 Demos | package
| java-1_7_0-openjdk-devel | SUSE's implementation of the OpenJDK 7 Developmen-> | package
| java-1_7_0-openjdk-headless | OpenJDK 7 runtime environment without X, audio an-> | package
| java-1_8_0-openjdk-demo | OpenJDK 8 Demos | package
| java-1_8_0-openjdk-devel | OpenJDK 8 Development Environment | package
| java-1_8_0-openjdk-headless | OpenJDK 8 Runtime Environment | package

3. Check openjdk package with version:
# zypper se -s openjdk-
Loading repository data...
Reading installed packages...

S | Name | Type | Version | Arch | Repository
--+-----------------------------+---------+----------------+--------+------------------
| java-1_7_0-openjdk-demo | package | 1.7.0.141-42.1 | x86_64 | SLES12-SP3-12.3-0
| java-1_7_0-openjdk-devel | package | 1.7.0.141-42.1 | x86_64 | SLES12-SP3-12.3-0
| java-1_7_0-openjdk-headless | package | 1.7.0.141-42.1 | x86_64 | SLES12-SP3-12.3-0
| java-1_8_0-openjdk-demo | package | 1.8.0.131-26.3 | x86_64 | SLES12-SP3-12.3-0
| java-1_8_0-openjdk-devel | package | 1.8.0.131-26.3 | x86_64 | SLES12-SP3-12.3-0
| java-1_8_0-openjdk-headless | package | 1.8.0.131-26.3 | x86_64 | SLES12-SP3-12.3-0

4. Check Java Package information:
# zypper info java-1_8_0-openjdk-devel
Loading repository data...
Reading installed packages...

Information for package java-1_8_0-openjdk-devel:
-------------------------------------------------
Repository : SLES12-SP3-12.3-0
Name : java-1_8_0-openjdk-devel
Version : 1.8.0.131-26.3
Arch : x86_64
Vendor : SUSE LLC <https://www.suse.com/>
Support Level : Level 2
Installed Size : 21.4 MiB
Installed : No
Status : not installed
Source package : java-1_8_0-openjdk-1.8.0.131-26.3.src
Summary : OpenJDK 8 Development Environment
Description :
The OpenJDK 8 development tools.

5. Check below folders:
# ls /usr/lib64/java
ls: cannot access '/usr/lib64/java': No such file or directory

# ls /usr/lib64/jvm
ls: cannot access '/usr/lib64/jvm': No such file or directory

6. Check environment Setting:
# env | grep -i java
#

7. Now install openjdk rpms by "zypper" command:
# zypper in java-1_8_0-openjdk-devel
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 5 NEW packages are going to be installed:
java-1_8_0-openjdk java-1_8_0-openjdk-devel java-1_8_0-openjdk-headless javapackages-tools
libgif6

5 new packages to install.
Overall download size: 65.9 MiB. Already cached: 0 B. After the operation, additional 105.9 MiB
will be used.
Continue? [y/n/...? shows all options] (y): y
Retrieving package javapackages-tools-2.0.1-6.10.x86_64 (1/5), 50.8 KiB (129.9 KiB unpacked)
Retrieving package libgif6-5.0.5-12.1.x86_64 (2/5), 21.0 KiB ( 35.4 KiB unpacked)
Retrieving package java-1_8_0-openjdk-headless-1.8.0.131-26.3.x86_64
(3/5), 48.7 MiB ( 83.8 MiB unpacked)
Retrieving package java-1_8_0-openjdk-1.8.0.131-26.3.x86_64
(4/5), 289.2 KiB (565.7 KiB unpacked)
Retrieving package java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64
(5/5), 16.8 MiB ( 21.4 MiB unpacked)
Checking for file conflicts: ............................................................[done]
(1/5) Installing: javapackages-tools-2.0.1-6.10.x86_64 ..................................[done]
(2/5) Installing: libgif6-5.0.5-12.1.x86_64 .............................................[done]
(3/5) Installing: java-1_8_0-openjdk-headless-1.8.0.131-26.3.x86_64 .....................[done]
Additional rpm output:
update-alternatives: using /usr/lib64/jvm/jre-1.8.0-openjdk/bin/java to provide /usr/bin/java (java) in auto mode
update-alternatives: using /usr/lib64/jvm/jre-1.8.0-openjdk to provide /usr/lib64/jvm/jre-openjdk (jre_openjdk) in auto mode
update-alternatives: using /usr/lib64/jvm/jre-1.8.0-openjdk to provide /usr/lib64/jvm/jre-1.8.0 (jre_1.8.0) in auto mode

(4/5) Installing: java-1_8_0-openjdk-1.8.0.131-26.3.x86_64 ..............................[done]
(5/5) Installing: java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64 ........................[done]
Additional rpm output:
update-alternatives: using /usr/lib64/jvm/java-1.8.0-openjdk/bin/javac to provide /usr/bin/javac (javac) in auto mode
update-alternatives: using /usr/lib64/jvm/java-1.8.0-openjdk to provide /usr/lib64/jvm/java-openjdk (java_sdk_openjdk) in auto mode
update-alternatives: using /usr/lib64/jvm/java-1.8.0-openjdk to provide /usr/lib64/jvm/java-1.8.0 (java_sdk_1.8.0) in auto mode

8. Now Java rpms exists:
# rpm -qa | grep -i java
java-1_8_0-openjdk-headless-1.8.0.131-26.3.x86_64
typelib-1_0-JavaScriptCore-4_0-2.12.5-1.12.x86_64
java-1_8_0-openjdk-1.8.0.131-26.3.x86_64
javapackages-tools-2.0.1-6.10.x86_64
libjavascriptcoregtk-4_0-18-2.12.5-1.12.x86_64
java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64

9. Have not set Java environment, /usr/lib64/java folder has created, /usr/lib64/jvm created and have no. of link files and folders:

# env | grep -i java

# ls -l /usr/lib64/java
total 0

# ls -l /usr/lib64/jvm
total 4
lrwxrwxrwx 1 root root 26 Oct 29 17:21 java -> /etc/alternatives/java_sdk
lrwxrwxrwx 1 root root 32 Oct 29 17:21 java-1.8.0 -> /etc/alternatives/java_sdk_1.8.0
lrwxrwxrwx 1 root root 24 Oct 29 17:21 java-1.8.0-openjdk -> java-1.8.0-openjdk-1.8.0
drwxr-xr-x 7 root root 4096 Oct 29 17:21 java-1.8.0-openjdk-1.8.0
lrwxrwxrwx 1 root root 34 Oct 29 17:21 java-openjdk -> /etc/alternatives/java_sdk_openjdk
lrwxrwxrwx 1 root root 21 Oct 29 17:21 jre -> /etc/alternatives/jre
lrwxrwxrwx 1 root root 27 Oct 29 17:21 jre-1.8.0 -> /etc/alternatives/jre_1.8.0
lrwxrwxrwx 1 root root 28 Oct 29 17:21 jre-1.8.0-openjdk -> java-1.8.0-openjdk-1.8.0/jre
lrwxrwxrwx 1 root root 29 Oct 29 17:21 jre-openjdk -> /etc/alternatives/jre_openjdk

10. Now all java command is coming:
# java (Press Tab to check)
java javac javadoc javah javap

11. Now if need to remove openjdk rpms, follow below steps:

# rpm -qa | grep java-1_8_0-openjdk-devel
java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64

# rpm -ev java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64
Preparing packages...
java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64
update-alternatives: warning: alternative /usr/lib64/jvm/java-1.8.0-openjdk/bin/javac (part of link group javac) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/javac is dangling; it will be updated with best choice
update-alternatives: warning: alternative /usr/lib64/jvm/java-1.8.0-openjdk (part of link group java_sdk_openjdk) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/java_sdk_openjdk is dangling; it will be updated with best choice
update-alternatives: warning: alternative /usr/lib64/jvm/java-1.8.0-openjdk (part of link group java_sdk_1.8.0) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/java_sdk_1.8.0 is dangling; it will be updated with best choice

# rpm -qa | grep java-1_8_0-openjdk-devel
#

12. After removing now list of link file is less as compared to above:
# ls -l /usr/lib64/jvm
total 4
drwxr-xr-x 3 root root 4096 Oct 29 17:25 java-1.8.0-openjdk-1.8.0
lrwxrwxrwx 1 root root 21 Oct 29 17:21 jre -> /etc/alternatives/jre
lrwxrwxrwx 1 root root 27 Oct 29 17:21 jre-1.8.0 -> /etc/alternatives/jre_1.8.0
lrwxrwxrwx 1 root root 28 Oct 29 17:21 jre-1.8.0-openjdk -> java-1.8.0-openjdk-1.8.0/jre
lrwxrwxrwx 1 root root 29 Oct 29 17:21 jre-openjdk -> /etc/alternatives/jre_openjdk

13. Now other java command is not exist like above:
# java (Press tab key)
.cache. .config. .dbus. .gnupg. .targetcli. bin. inst-sys.

14. After installing openjdk again all folders, files and symbolic link come:

# zypper se java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64
Loading repository data...
Reading installed packages...

S | Name | Type | Version | Arch | Repository
--+--------------------------+---------+----------------+--------+------------------
| java-1_8_0-openjdk-devel | package | 1.8.0.131-26.3 | x86_64 | SLES12-SP3-12.3-0

# zypper in java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
java-1_8_0-openjdk-devel

1 new package to install.
Overall download size: 16.8 MiB. Already cached: 0 B. After the operation, additional 21.4 MiB
will be used.
Continue? [y/n/...? shows all options] (y): y
Retrieving package java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64
(1/1), 16.8 MiB ( 21.4 MiB unpacked)
Checking for file conflicts: ............................................................[done]
(1/1) Installing: java-1_8_0-openjdk-devel-1.8.0.131-26.3.x86_64 ........................[done]
Additional rpm output:
update-alternatives: using /usr/lib64/jvm/java-1.8.0-openjdk/bin/javac to provide /usr/bin/javac (javac) in auto mode
update-alternatives: using /usr/lib64/jvm/java-1.8.0-openjdk to provide /usr/lib64/jvm/java-openjdk (java_sdk_openjdk) in auto mode
update-alternatives: using /usr/lib64/jvm/java-1.8.0-openjdk to provide /usr/lib64/jvm/java-1.8.0 (java_sdk_1.8.0) in auto mode

15. Now all java command is available:
# java (Press tab key)
java javac javadoc javah javap

Note : After reboot the server all Java Environment automatically set by /etc/profile.d/alljava.sh:

# env | grep -i java
JRE_HOME=/usr/lib64/jvm/java/jre
JAVA_BINDIR=/usr/lib64/jvm/java/bin
JAVA_HOME=/usr/lib64/jvm/java
SDK_HOME=/usr/lib64/jvm/java
JDK_HOME=/usr/lib64/jvm/java
JAVA_ROOT=/usr/lib64/jvm/java

# cat /etc/profile.d/alljava.sh
#
# /etc/profile.d/alljava.sh
#
# send feedback to http://bugs.opensuse.org

#
# This script sets some environment variables for default java.
# Affected variables: JAVA_BINDIR, JAVA_HOME, JRE_HOME,
# JDK_HOME, SDK_HOME
#

for JDIR in /usr/lib64/jvm /usr/lib/jvm /usr/java/latest /usr/java; do

if ! test -d $JDIR; then
continue
fi

for JPATH in $JDIR $JDIR/java `ls -I 'java' -I 'jre' -d $JDIR/* 2>/dev/null` $JDIR/jre; do

if ! test -x $JPATH/bin/java; then
continue
fi

export JAVA_BINDIR=$JPATH/bin
export JAVA_ROOT=$JPATH
export JAVA_HOME=$JPATH
unset JDK_HOME
unset SDK_HOME

case "$JPATH" in
*jre*)
[ -z "$JRE_HOME" ] && export JRE_HOME=$JPATH
;;

*)
[ -z "$JRE_HOME" ] && export JRE_HOME=$JPATH/jre
# it is development kit
if [ -x $JPATH/bin/javac ] ; then
export JDK_HOME=$JPATH
export SDK_HOME=$JPATH
unset JPATH
break 2; # we found a JRE + SDK -- don't look any further
fi
;;
esac

done
unset JPATH

done
unset JDIR
#

To reduce / extend LV on SuSE / Red Hat Linux

2017-11-13T08:48:00.000+05:30

Steps to reduce /home file system:

1. Take backup of Filesystem before going to start LV reduce activity

For example if you want to reduce /home file system
# mkdir /var/tmp-bkp-home <-- to make temporary folder for backup as per disk space availability
# cd /var/tmp-bkp-home
# tar -cf home-bkp-7th-July-2015.tar /home
# ls -lh home-bkp-7th-July-2015.tar

2. Take pre-check before starting the activity
# df -h /home
# vgdisplay VolGroup00
# lvdisplay /dev/VolGroup00/LogVol03 <-- is for /home file system

3. Unmount the /home file system
# umount /home
umount: /home: device is busy
umount: /home: device is busy

If get device busy error check user/process that is still using file system
# lsof /home
# fuser -cu /home
/home: 24551c(sharmaxx) 26948c(root)
# fuser -ck /home
/home: 24551c 26948c
Hangup

Kill process to release the /home file system

# kill -9 24551
# kill -9 26948

Check "open" option in lvdisplay command
# lvdisplay /dev/VolGroup00/LogVol03
# open 0 <-- it should be zero means this LV is free to unmount

if still facing issue REBOOT is one more option if file is locked by any process or try,
# umount -f /usr/local/nete
# umount -l /usr/local/nete
# umount -lf /usr/local/nete

Make confirmation by running
# df -h /home

4. Run e2fsck to check file system
# e2fsck -f /dev/mapper/VolGroup00-LogVol03

5. Suppose size of /home is 14 GB and you want to reduce it by 4GB, then the new size will be 10GB
for than run below command:
# resize2fs /dev/mapper/VolGroup00-LogVol03 10g

6. Run LV reduce command
lvreduce -L 10GB /dev/mapper/VolGroup00-LogVol03

7. Again Run e2fsck to check file system
e2fsck -f /dev/mapper/VolGroup00-LogVol03

8. Check size of lv and vg
# vgdisplay VolGroup00
# lvdisplay /dev/VolGroup00/LogVol03 <-- is for /home file system

9. Mount file system
# mount /home

10. Finaly check file system
# df -hT /home

Steps to extend /root File System

1. Take pre-check before scanning the disk:
# vgdisplay VolGroup00
# lvdisplay /dev/VolGroup00/LogVol00
# lsscsi
# lsblk
# blkid

2. Scan new disk:
# echo "- - -" > /sys/class/scsi_host/host0/scan
# echo "- - -" > /sys/class/scsi_host/host1/scan

Alternativily you can also scan / rescan by
# ls /sys/class/scsi_host/ | while read host ; do echo "- - -" > /sys/class/scsi_host/$host/scan ; done

2. Check newly added disk:
# lsscsi
# lsblk
# blkid
# ls -lhtr /dev/disk/by-path/

3. Suppose you got new disk like /dev/sdn then, create PV:
# pvcreate /dev/sdn

4. Extend VG:
# vgextend VolGroup00 /dev/sdn

5. Extend LV:
# lvextend -L +50G /dev/VolGroup00/LogVol00

6. Run resize2fs command to resize LV online:
# resize2fs /dev/VolGroup00/LogVol00

Note : resize2fs also work for ext4 file system

For older version of Linux OS you can resize file system by
# ext2online /dev/VolGroup00/LogVol00

7. Check VG, LV and file system size:
# vgdisplay VolGroup00
# lvdisplay /dev/VolGroup00/LogVol00
# df -hT /root

Enable Iptables logging in RHEL5

2016-01-12T18:50:00.002+05:30

Environment : RHEL 5.6 2.6.18-348.el5-x86_64

1. Take backup of /etc/syslog.conf:
     # cp /etc/syslog.conf /etc/syslog.conf.bak

2. Add below line in /etc/syslog.conf:
    kern.warning /var/log/iptables

3. Reload syslog service:
    #service syslog reload

4. Check iptables log:
    #tail -f /var/log/iptables

5. Run below command
     #iptables -I INPUT -p tcp --dport 10000:10500 -j LOG --log-level 4

6. Add the prefix "#### Firewall ####"
    # iptables -I INPUT -p icmp --icmp-type ping -j LOG --log-prefix "#### Firewall ####"

7.   Disable the iptables logging:
     #service iptables restart

ISCSI Server & Client Installation/Configuration on RHEL 5.9 64bits

2015-12-24T17:36:00.001+05:30

Table of Contents

Environment Details

Installation of ISCSI Target on Master server

Installation of ISCSI imitator on Client Server

Configuration of multipath on Client

Creating pv, vg & lvm

Adding 5GB Disk Space on master & Configure as target server

New Disk add on client machine

Extend (resize) disk on master

Scan newly updated size on client machine

Environment Details

Master Server

192.168.144.136 imastiscsi.example.com mastiscsi

192.168.144.155

Client Server

192.168.144.153 iscsiclient.example.com iscsiclient

192.168.144.154

Installation of ISCSI Target on Master server

1. Checking Disk Space

[root@mastiscsi ~]# fdisk -l

Disk /dev/sda: 42.9 GB, 42949672960 bytes

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 32 257008+ 83 Linux

/dev/sda2 33 5221 41680642+ 8e Linux LVM

Disk /dev/sdb: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

2. Mount RHEL 5.9 DVD for configuration of Yum Server

[root@mastiscsi ~]# mount /dev/cdrom /mnt/rhel5/

mount: block device /dev/cdrom is write-protected, mounting read-only

[root@mastiscsi ~]# cat /etc/yum.repos.d/rhel5-media.repo

[cd-media]

name=rhel5.9-media

baseurl=file:///mnt/rhel5/Server

gpgcheck=1

enabled=1

gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

3. Download below rmps and copy into root folder

[root@mastiscsi ~]# ls

perl-Config-General-2.52-31.1.x86_64.rpm

scsi-target-utils-1.0.14-2.el5.x86_64.rpm

4. Install below software & its dependencies

[root@mastiscsi ~]# rpm -ivh perl-Config-General-2.52-31.1.x86_64.rpm

warning: perl-Config-General-2.52-31.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID dcef338c

Preparing... ########################################### [100%]

1:perl-Config-General ########################################### [100%]

[root@mastiscsi ~]# yum install libibverbs*

Installed:

libibverbs.i386 0:1.1.6-3.el5 libibverbs.x86_64 0:1.1.6-3.el5

libibverbs-devel.i386 0:1.1.6-3.el5 libibverbs-devel.x86_64 0:1.1.6-3.el5

libibverbs-static.x86_64 0:1.1.6-3.el5 libibverbs-utils.x86_64 0:1.1.6-3.el5

Dependency Installed:

libnes.x86_64 0:1.1.3-1.el5 openib.noarch 0:1.5.4.1-4.el5

[root@mastiscsi ~]# yum install librdmacm*

Installed:

librdmacm.i386 0:1.0.15-2.el5 librdmacm.x86_64 0:1.0.15-2.el5

librdmacm-devel.i386 0:1.0.15-2.el5 librdmacm-devel.x86_64 0:1.0.15-2.el5

librdmacm-static.x86_64 0:1.0.15-2.el5 librdmacm-utils.x86_64 0:1.0.15-2.el5

[root@mastiscsi ~]# rpm -ivh scsi-target-utils-1.0.14-2.el5.x86_64.rpm

warning: scsi-target-utils-1.0.14-2.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID e8562897

Preparing... ########################################### [100%]

1:scsi-target-utils ########################################### [100%]

5. Check NetworkManager and off by chkconfig command

[root@mastiscsi ~]# chkconfig --list | grep Netwo

NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off

6. Check and start tgtd service

[root@mastiscsi ~]# chkconfig --list | grep tgtd

tgtd 0:off 1:off 2:off 3:off 4:off 5:off 6:off

[root@mastiscsi ~]# service tgtd start

Starting SCSI target daemon: Starting target framework daemon

[root@mastiscsi ~]# chkconfig tgtd on

[root@mastiscsi ~]# chkconfig --list | grep tgt

tgtd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

7. Take backup of /etc/tgt/targets.conf file and start service

[root@mastiscsi ~]# cp -p /etc/tgt/targets.conf /etc/tgt/targets.conf.bkp

[root@mastiscsi ~]# vi /etc/tgt/targets.conf

backing-store /dev/sdb

</target>

[root@mastiscsi ~]# service tgtd restart

Stopping SCSI target daemon: Stopping target framework daemon [ OK ]

Starting SCSI target daemon: Starting target framework daemon

8. Check lun & target details

[root@mastiscsi ~]# tgt-admin -s

Target 1: iqn.2015-08.com.example:mastiscsi.disk1

System information:

Driver: iscsi

State: ready

I_T nexus information:

LUN information:

LUN: 0

Type: controller

SCSI ID: IET 00010000

SCSI SN: beaf10

Size: 0 MB, Block size: 1

Online: Yes

Removable media: No

Readonly: No

Backing store type: null

Backing store path: None

Backing store flags:

LUN: 1

Type: disk

SCSI ID: IET 00010001

SCSI SN: beaf11

Size: 4295 MB, Block size: 512

Online: Yes

Removable media: No

Readonly: No

Backing store type: rdwr

Backing store path: /dev/sdb

Backing store flags:

Account information:

ACL information:

ALL

9. Check & disable iptables & selinux

[root@mastiscsi ~]# service iptables status

Firewall is stopped.

[root@mastiscsi ~]# getenforce

Disabled

Installation of ISCSI imitator on Client Server

1. Check installed iscsi-initiator rpm

[root@iscsiclient ~]# rpm -qa | grep iscsi

iscsi-initiator-utils-6.2.0.872-16.el5

2. Check & modify initiator name

[root@iscsiclient ~]# cat /etc/iscsi/initiatorname.iscsi

InitiatorName=iqn.2015-08.com.example:mastiscsi

Above mastiscsi is master server hostname

3. Start iscsi service and make it permanent

[root@iscsiclient ~]# /etc/init.d/iscsid restart

Stopping iSCSI daemon: [ OK ]

Starting iSCSI daemon: [ OK ]

[root@iscsiclient ~]# chkconfig --list | grep scsi

iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off

iscsid 0:off 1:off 2:off 3:on 4:on 5:on 6:off

4. Discover iscsi server by two IPs of Master Server

[root@iscsiclient ~]# iscsiadm -m discoverydb -t st --portal 192.168.144.136:3260 --discover

192.168.144.136:3260,1 iqn.2015-08.com.example:mastiscsi.disk1

[root@iscsiclient ~]# iscsiadm -m discoverydb -t st --portal 192.168.144.155:3260 --discover

192.168.144.155:3260,1 iqn.2015-08.com.example:mastiscsi.disk1

5. Login Master server with both IPs

[root@iscsiclient ~]# iscsiadm -m node --portal 192.168.144.136:3260 -T iqn.2015-08.com.example:mastiscsi.disk1 -l

Logging in to [iface: default, target: iqn.2015-08.com.example:mastiscsi.disk1, portal: 192.168.144.136,3260] (multiple)

[root@iscsiclient ~]# iscsiadm -m node --portal 192.168.144.155:3260 -T iqn.2015-08.com.example:mastiscsi.disk1 -l

Logging in to [iface: default, target: iqn.2015-08.com.example:mastiscsi.disk1, portal: 192.168.144.155,3260] (multiple)

6. Check Disk Space

[root@iscsiclient ~]# fdisk -l

Disk /dev/sda: 42.9 GB, 42949672960 bytes

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 32 257008+ 83 Linux

/dev/sda2 33 5221 41680642+ 8e Linux LVM

Disk /dev/sdb: 4294 MB, 4294967296 bytes

133 heads, 62 sectors/track, 1017 cylinders

Units = cylinders of 8246 * 512 = 4221952 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 4294 MB, 4294967296 bytes

133 heads, 62 sectors/track, 1017 cylinders

Units = cylinders of 8246 * 512 = 4221952 bytes

Disk /dev/sdc doesn't contain a valid partition table

Configuration of multipath on Client

Multipath configuration is required to configure on Client Machine only. It is not require on Master Server

1. Check below rpms:

[root@iscsiclient ~]# rpm -qa | grep device-mapper

device-mapper-1.02.67-2.el5

device-mapper-multipath-0.4.7-54.el5

device-mapper-event-1.02.67-2.el5

device-mapper-1.02.67-2.el5

2. Check if kernel is loaded with multipath module

[root@iscsiclient ~]# lsmod | grep multipath

dm_multipath 58969 0

scsi_dh 42561 1 dm_multipath

dm_mod 102417 15 dm_multipath,dm_raid45,dm_snapshot,dm_zero,dm_mirror,dm_log

3. Check current mapper device

[root@iscsiclient ~]# ls -l /dev/mapper/

total 0

crw------- 1 root root 10, 60 Aug 27 17:30 control

brw-rw---- 1 root disk 253, 2 Aug 27 17:31 vg0-home

brw-rw---- 1 root disk 253, 0 Aug 27 17:31 vg0-root

brw-rw---- 1 root disk 253, 3 Aug 27 17:30 vg0-swap

brw-rw---- 1 root disk 253, 1 Aug 27 17:31 vg0-var

4. Comment default blacklist detail

[root@iscsiclient ~]# vi /etc/multipath.conf

#blacklist {

# devnode "*"

5. Start multipathd service and make it permanent

[root@iscsiclient ~]# service multipathd start

Starting multipathd daemon: [ OK ]

[root@iscsiclient ~]# chkconfig multipathd on

6. Check current multipath details

[root@iscsiclient ~]# multipath -ll

mpath0 (1IET_00010001) dm-4 IET,VIRTUAL-DISK

[size=4.0G][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 31:0:0:1 sdb 8:16 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 32:0:0:1 sdc 8:32 [active][ready]

7. Now check Disk Details

[root@iscsiclient ~]# fdisk -l

Disk /dev/sda: 42.9 GB, 42949672960 bytes

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 32 257008+ 83 Linux

/dev/sda2 33 5221 41680642+ 8e Linux LVM

Disk /dev/sdb: 4294 MB, 4294967296 bytes

133 heads, 62 sectors/track, 1017 cylinders

Units = cylinders of 8246 * 512 = 4221952 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 4294 MB, 4294967296 bytes

133 heads, 62 sectors/track, 1017 cylinders

Units = cylinders of 8246 * 512 = 4221952 bytes

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/dm-4: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-4 doesn't contain a valid partition table

8. Check new mapper device

[root@iscsiclient ~]# ls -l /dev/mapper/

total 0

crw------- 1 root root 10, 60 Aug 27 17:30 control

brw-rw---- 1 root disk 253, 4 Aug 27 18:17 mpath0

brw-rw---- 1 root disk 253, 2 Aug 27 17:31 vg0-home

brw-rw---- 1 root disk 253, 0 Aug 27 17:31 vg0-root

brw-rw---- 1 root disk 253, 3 Aug 27 17:30 vg0-swap

brw-rw---- 1 root disk 253, 1 Aug 27 17:31 vg0-var

9. Format new Disk

[root@iscsiclient ~]# fdisk /dev/mapper/mpath0

Command (m for help): p

Disk /dev/mapper/mpath0: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

Command (m for help): n

Command action

e extended

p primary partition (1-4)

Partition number (1-4): 1

First cylinder (1-522, default 1): <Enter>

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-522, default 522): <Enter>

Using default value 522

Command (m for help): p

Disk /dev/mapper/mpath0: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath0p1 1 522 4192933+ 83 Linux

Command (m for help): t

Selected partition 1

Hex code (type L to list codes): 8e

Changed system type of partition 1 to 8e (Linux LVM)

Command (m for help): p

Disk /dev/mapper/mpath0: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath0p1 1 522 4192933+ 8e Linux LVM

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.

The kernel still uses the old table.

The new table will be used at the next reboot.

Syncing disks.

10. Check & make new partition kernel readable

[root@iscsiclient ~]# fdisk -l /dev/mapper/mpath0

Disk /dev/mapper/mpath0: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath0p1 1 522 4192933+ 8e Linux LVM

[root@iscsiclient ~]# partprobe /dev/mapper/mpath0

[root@iscsiclient ~]# fdisk -l

Disk /dev/sda: 42.9 GB, 42949672960 bytes

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 32 257008+ 83 Linux

/dev/sda2 33 5221 41680642+ 8e Linux LVM

Disk /dev/sdb: 4294 MB, 4294967296 bytes

133 heads, 62 sectors/track, 1017 cylinders

Units = cylinders of 8246 * 512 = 4221952 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 4294 MB, 4294967296 bytes

133 heads, 62 sectors/track, 1017 cylinders

Units = cylinders of 8246 * 512 = 4221952 bytes

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/dm-4: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/dm-4p1 1 522 4192933+ 8e Linux LVM

11. New partition is now visible on reaming disks as per above output so it is require to reboot machine

[root@iscsiclient ~]# reboot

Broadcast message from root (pts/0) (Thu Aug 27 19:01:54 2015):

The system is going down for reboot NOW!

[root@iscsiclient ~]#

12. After reboot the machine now new partition is visible on remaining disk

[root@iscsiclient ~]# fdisk -l

Disk /dev/sda: 42.9 GB, 42949672960 bytes

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 32 257008+ 83 Linux

/dev/sda2 33 5221 41680642+ 8e Linux LVM

Disk /dev/sdb: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdb1 1 522 4192933+ 8e Linux LVM

Disk /dev/sdc: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdc1 1 522 4192933+ 8e Linux LVM

Disk /dev/dm-4: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/dm-4p1 1 522 4192933+ 8e Linux LVM

Disk /dev/dm-5: 4293 MB, 4293563904 bytes

255 heads, 63 sectors/track, 521 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-5 doesn't contain a valid partition table

Note: After reboot machine above /dev/dm-5 has additionally added. But it is useless.

Creating pv, vg & lvm

1. We should not create physical volume with /dev/dm-4p1. It will show error like below

[root@iscsiclient ~]# pvcreate /dev/dm-4p1 -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Device /dev/dm-4p1 not found (or ignored by filtering).

Note : Also not create Physical volume with /dev/sdb1 and /dev/sdc1

2. List current Device

[root@iscsiclient ~]# ls -l /dev/mapper/

total 0

crw------- 1 root root 10, 60 Aug 27 19:03 control

brw-rw---- 1 root disk 253, 4 Aug 27 19:04 mpath0

brw-rw---- 1 root disk 253, 5 Aug 27 19:04 mpath0p1

brw-rw---- 1 root disk 253, 2 Aug 27 19:03 vg0-home

brw-rw---- 1 root disk 253, 0 Aug 27 19:03 vg0-root

brw-rw---- 1 root disk 253, 3 Aug 27 19:03 vg0-swap

brw-rw---- 1 root disk 253, 1 Aug 27 19:03 vg0-var

3. Now Create Physical Volume

[root@iscsiclient ~]# pvcreate /dev/mapper/mpath0p1

Writing physical volume data to disk "/dev/mapper/mpath0p1"

Physical volume "/dev/mapper/mpath0p1" successfully created

[root@iscsiclient ~]# pvdisplay /dev/mpath/mpath0p1

"/dev/mpath/mpath0p1" is a new physical volume of "4.00 GB"

--- NEW Physical volume ---

PV Name /dev/mpath/mpath0p1

VG Name

PV Size 4.00 GB

Allocatable NO

PE Size (KByte) 0

Total PE 0

Free PE 0

Allocated PE 0

PV UUID TLgOgU-8PF6-8x95-3Yqv-vVc2-6soy-wSuEkc

4. Create Volume Group

[root@iscsiclient ~]# vgcreate wasvg /dev/mpath/mpath0p1

Volume group "wasvg" successfully created

[root@iscsiclient ~]# vgdisplay wasvg

--- Volume group ---

VG Name wasvg

System ID

Format lvm2

Metadata Areas 1

Metadata Sequence No 1

VG Access read/write

VG Status resizable

MAX LV 0

Cur LV 0

Open LV 0

Max PV 0

Cur PV 1

Act PV 1

VG Size 4.00 GB

PE Size 4.00 MB

Total PE 1023

Alloc PE / Size 0 / 0

Free PE / Size 1023 / 4.00 GB

VG UUID VigepC-As6r-9q1d-NLlv-gMiK-hJr9-kGNFFt

5. Create Logical Volume

[root@iscsiclient ~]# lvcreate -L 4GB -n wasvg-datalv wasvg -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Volume group "wasvg" has insufficient free space (1023 extents): 1024 required.

[root@iscsiclient ~]# lvcreate -L 3GB -n wasvg-datalv wasvg

Logical volume "wasvg-datalv" created

[root@iscsiclient ~]# lvdisplay /dev/wasvg/wasvg-datalv

--- Logical volume ---

LV Name /dev/wasvg/wasvg-datalv

VG Name wasvg

LV UUID aaT8Df-2U6T-Eh98-YLks-Q1YI-EWQN-oaF6lf

LV Write Access read/write

LV Status available

# open 0

LV Size 3.00 GB

Current LE 768

Segments 1

Allocation inherit

Read ahead sectors auto

- currently set to 256

Block device 253:6

Adding 5GB Disk Space on master & Configure as target server

1. Check disk space before scanning new disk without reboot the machine

[root@mastiscsi ~]# fdisk -l

Disk /dev/sda: 42.9 GB, 42949672960 bytes

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 32 257008+ 83 Linux

/dev/sda2 33 5221 41680642+ 8e Linux LVM

Disk /dev/sdb: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdb1 1 522 4192933+ 8e Linux LVM

2. Scan new Disk on Master Server and new disk space

[root@mastiscsi ~]# echo "- - -" > /sys/class/scsi_host/host0/scan

[root@mastiscsi ~]# fdisk -l /dev/sdc

Disk /dev/sdc: 5368 MB, 5368709120 bytes

255 heads, 63 sectors/track, 652 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdc doesn't contain a valid partition table

[root@mastiscsi ~]#

3. Create LVM to export disk as target

[root@mastiscsi ~]# pvcreate /dev/sdc -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Writing physical volume data to disk "/dev/sdc"

Physical volume "/dev/sdc" successfully created

[root@mastiscsi ~]# pvcreate /dev/sdc

Writing physical volume data to disk "/dev/sdc"

Physical volume "/dev/sdc" successfully created

[root@mastiscsi ~]# vgcreate multivg /dev/sdc -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Volume group "multivg" successfully created

[root@mastiscsi ~]# vgcreate multivg /dev/sdc

Volume group "multivg" successfully created

[root@mastiscsi ~]# lvcreate -L 800MB -n multilv multivg -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Logical volume "multilv" created

[root@mastiscsi ~]# lvcreate -L 800MB -n multilv multivg

Logical volume "multilv" created

4. Check newly created PV, VG ad LVM

[root@mastiscsi ~]# pvdisplay /dev/sdc

--- Physical volume ---

PV Name /dev/sdc

VG Name multivg

PV Size 5.00 GB / not usable 4.00 MB

Allocatable yes

PE Size (KByte) 4096

Total PE 1279

Free PE 1079

Allocated PE 200

PV UUID Un9URB-fgvf-SBAP-AeAN-7J0I-sLWw-KIWBzI

[root@mastiscsi ~]# vgdisplay multivg

--- Volume group ---

VG Name multivg

System ID

Format lvm2

Metadata Areas 1

Metadata Sequence No 2

VG Access read/write

VG Status resizable

MAX LV 0

Cur LV 1

Open LV 0

Max PV 0

Cur PV 1

Act PV 1

VG Size 5.00 GB

PE Size 4.00 MB

Total PE 1279

Alloc PE / Size 200 / 800.00 MB

Free PE / Size 1079 / 4.21 GB

VG UUID pkBZxW-DM3m-a1dz-9MCM-gKd8-DXpr-i2cEMG

[root@mastiscsi ~]# lvdisplay /dev/multivg/multilv

--- Logical volume ---

LV Name /dev/multivg/multilv

VG Name multivg

LV UUID vlK9G8-E8lS-bEwX-2w6Z-fAFO-3Rsi-971joA

LV Write Access read/write

LV Status available

# open 0

LV Size 800.00 MB

Current LE 200

Segments 1

Allocation inherit

Read ahead sectors auto

- currently set to 256

Block device 253:4

[root@mastiscsi ~]#

5. Add disk into /etc/tgt/targets.conf file

[root@mastiscsi ~]# vi /etc/tgt/targets.conf

backing-store /dev/sdb

</target>

backing-store /dev/multivg/multilv

</target>

6. Reload the tgtd service for exporting newly added disk

[root@mastiscsi ~]# /etc/init.d/tgtd reload

Updating target framework daemon configuration

New Disk add on client machine

1. Discovery disk on master server with both IPs

[root@iscsiclient ~]# iscsiadm -m discoverydb -t st --portal 192.168.144.136:3260 --discover

192.168.144.136:3260,1 iqn.2015-08.com.example:mastiscsi.disk1

192.168.144.136:3260,1 iqn.2015-08.com.example:mastiscsi.disk2

[root@iscsiclient ~]# iscsiadm -m discoverydb -t st --portal 192.168.144.155:3260 --discover

192.168.144.155:3260,1 iqn.2015-08.com.example:mastiscsi.disk1

192.168.144.155:3260,1 iqn.2015-08.com.example:mastiscsi.disk2

2. Login into newly added disk on master server with both IPs

[root@iscsiclient ~]# iscsiadm -m node --portal 192.168.144.136:3260 -T iqn.2015-08.com.example:mastiscsi.disk2 -l

Logging in to [iface: default, target: iqn.2015-08.com.example:mastiscsi.disk2, portal: 192.168.144.136,3260] (multiple)

[root@iscsiclient ~]# iscsiadm -m node --portal 192.168.144.155:3260 -T iqn.2015-08.com.example:mastiscsi.disk2 -l

Logging in to [iface: default, target: iqn.2015-08.com.example:mastiscsi.disk2, portal: 192.168.144.155,3260] (multiple)

[root@iscsiclient ~]#

3. Check newly disk add by multipath command

[root@iscsiclient ~]# multipath -ll

mpath1 (1IET_00020001) dm-7 IET,VIRTUAL-DISK

[size=800M][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 33:0:0:1 sdd 8:48 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 34:0:0:1 sde 8:64 [active][ready]

mpath0 (1IET_00010001) dm-4 IET,VIRTUAL-DISK

[size=4.0G][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 31:0:0:1 sdb 8:16 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 32:0:0:1 sdc 8:32 [active][ready]

[root@iscsiclient ~]#

4 Check disk space newly added and visible on multipath output

[root@iscsiclient ~]# fdisk -l

Disk /dev/sda: 42.9 GB, 42949672960 bytes

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 32 257008+ 83 Linux

/dev/sda2 33 5221 41680642+ 8e Linux LVM

Disk /dev/sdb: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdb1 1 522 4192933+ 8e Linux LVM

Disk /dev/sdc: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdc1 1 522 4192933+ 8e Linux LVM

Disk /dev/dm-4: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/dm-4p1 1 522 4192933+ 8e Linux LVM

Disk /dev/dm-5: 4293 MB, 4293563904 bytes

255 heads, 63 sectors/track, 521 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-5 doesn't contain a valid partition table

Disk /dev/sdd: 838 MB, 838860800 bytes

26 heads, 62 sectors/track, 1016 cylinders

Units = cylinders of 1612 * 512 = 825344 bytes

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/dm-7: 838 MB, 838860800 bytes

255 heads, 63 sectors/track, 101 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-7 doesn't contain a valid partition table

Disk /dev/sde: 838 MB, 838860800 bytes

26 heads, 62 sectors/track, 1016 cylinders

Units = cylinders of 1612 * 512 = 825344 bytes

Disk /dev/sde doesn't contain a valid partition table

[root@iscsiclient ~]#

5. List current device mapper

[root@iscsiclient ~]# ls -l /dev/mapper/

total 0

crw------- 1 root root 10, 60 Aug 27 19:03 control

brw-rw---- 1 root disk 253, 4 Aug 27 19:04 mpath0

brw-rw---- 1 root disk 253, 5 Aug 27 19:39 mpath0p1

brw-rw---- 1 root disk 253, 7 Aug 27 21:30 mpath1

brw-rw---- 1 root disk 253, 2 Aug 27 19:03 vg0-home

brw-rw---- 1 root disk 253, 0 Aug 27 19:03 vg0-root

brw-rw---- 1 root disk 253, 3 Aug 27 19:03 vg0-swap

brw-rw---- 1 root disk 253, 1 Aug 27 19:03 vg0-var

brw-rw---- 1 root disk 253, 6 Aug 27 19:44 wasvg-wasvg--datalv

6. Now partition the newly added disk

[root@iscsiclient ~]# fdisk -l /dev/mapper/mpath1

Disk /dev/mapper/mpath1: 838 MB, 838860800 bytes

255 heads, 63 sectors/track, 101 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mapper/mpath1 doesn't contain a valid partition table

[root@iscsiclient ~]# fdisk /dev/mapper/mpath1

Command (m for help): p

Disk /dev/mapper/mpath1: 838 MB, 838860800 bytes

255 heads, 63 sectors/track, 101 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

Command (m for help): n

Command action

e extended

p primary partition (1-4)

Partition number (1-4): 1

First cylinder (1-101, default 1): <enter>

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-101, default 101): <enter>

Using default value 101

Command (m for help): p

Disk /dev/mapper/mpath1: 838 MB, 838860800 bytes

255 heads, 63 sectors/track, 101 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath1p1 1 101 811251 83 Linux

Command (m for help): t

Selected partition 1

Hex code (type L to list codes): 8e

Changed system type of partition 1 to 8e (Linux LVM)

Command (m for help): p

Disk /dev/mapper/mpath1: 838 MB, 838860800 bytes

255 heads, 63 sectors/track, 101 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath1p1 1 101 811251 8e Linux LVM

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.

The kernel still uses the old table.

The new table will be used at the next reboot.

Syncing disks.

[root@iscsiclient ~]# fdisk -l /dev/mapper/mpath1

Disk /dev/mapper/mpath1: 838 MB, 838860800 bytes

255 heads, 63 sectors/track, 101 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath1p1 1 101 811251 8e Linux LVM

[root@iscsiclient ~]# partprobe /dev/mapper/mpath1

[root@iscsiclient ~]# partprobe /dev/mapper/mpath1p1

7. Create PV, VG and LVM on new partition

[root@iscsiclient ~]# pvcreate /dev/mapper/mpath1p1 -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Writing physical volume data to disk "/dev/mapper/mpath1p1"

Physical volume "/dev/mapper/mpath1p1" successfully created

[root@iscsiclient ~]# pvcreate /dev/mapper/mpath1p1

Writing physical volume data to disk "/dev/mapper/mpath1p1"

Physical volume "/dev/mapper/mpath1p1" successfully created

[root@iscsiclient ~]# vgcreate mpath1vg /dev/mapper/mpath1p1 -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Volume group "mpath1vg" successfully created

[root@iscsiclient ~]# vgcreate mpath1vg /dev/mapper/mpath1p1

Volume group "mpath1vg" successfully created

[root@iscsiclient ~]# lvcreate -L 600M -n mpath1-lv mpath1vg -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Logical volume "mpath1-lv" created

[root@iscsiclient ~]# lvcreate -L 600M -n mpath1-lv mpath1vg

Logical volume "mpath1-lv" created

8. Display PV, VG and LVM

[root@iscsiclient ~]# pvdisplay /dev/mapper/mpath1p1

--- Physical volume ---

PV Name /dev/mapper/mpath1p1

VG Name mpath1vg

PV Size 792.24 MB / not usable 243.00 KB

Allocatable yes

PE Size (KByte) 4096

Total PE 198

Free PE 48

Allocated PE 150

PV UUID PvY0Jc-LWfy-Cz9F-93v4-8a8T-GRCc-72wkHd

[root@iscsiclient ~]# vgdisplay mpath1vg

--- Volume group ---

VG Name mpath1vg

System ID

Format lvm2

Metadata Areas 1

Metadata Sequence No 2

VG Access read/write

VG Status resizable

MAX LV 0

Cur LV 1

Open LV 0

Max PV 0

Cur PV 1

Act PV 1

VG Size 792.00 MB

PE Size 4.00 MB

Total PE 198

Alloc PE / Size 150 / 600.00 MB

Free PE / Size 48 / 192.00 MB

VG UUID 33jdf6-tP2I-pXm6-kioh-OWvm-fL69-mnswiQ

[root@iscsiclient ~]# lvdisplay /dev/mpath1vg/mpath1-lv

--- Logical volume ---

LV Name /dev/mpath1vg/mpath1-lv

VG Name mpath1vg

LV UUID L1ZDxM-WTwI-792x-qU1e-hFmi-8SP1-jGoqXe

LV Write Access read/write

LV Status available

# open 0

LV Size 600.00 MB

Current LE 150

Segments 1

Allocation inherit

Read ahead sectors auto

- currently set to 256

Block device 253:9

[root@iscsiclient ~]#

9. Create File System on newly added disk

[root@iscsiclient /]# mkfs -t ext3 /dev/mpath1vg/mpath1-lv

mke2fs 1.39 (29-May-2006)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

76800 inodes, 153600 blocks

7680 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=159383552

5 block groups

32768 blocks per group, 32768 fragments per group

15360 inodes per group

Superblock backups stored on blocks:

32768, 98304

Writing inode tables: done

Creating journal (4096 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 34 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

10. Mount file system and check

[root@iscsiclient /]# mount -t ext3 /dev/mpath1vg/mpath1-lv /mpath1-lv/

[root@iscsiclient /]# df -h

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/vg0-root 20G 3.1G 16G 17% /

/dev/mapper/vg0-var 9.7G 222M 9.0G 3% /var

/dev/mapper/vg0-home 992M 34M 908M 4% /home

/dev/sda1 244M 14M 218M 6% /boot

tmpfs 500M 0 500M 0% /dev/shm

/dev/mapper/mpath0p1 4.0G 73M 3.7G 2% /datalv

/dev/mapper/mpath1vg-mpath1--lv

591M 17M 545M 3% /mpath1-lv

[root@iscsiclient /]#

11. Creating file in newly created file system

[root@iscsiclient /]# ls -l > /mpath1-lv/ls-l.txt

[root@iscsiclient /]# ls -l /mpath1-lv/

total 20

drwx------ 2 root root 16384 Aug 29 15:22 lost+found

-rw-r--r-- 1 root root 1245 Aug 29 15:23 ls-l.txt

[root@iscsiclient /]#

Extend (resize) disk on master

1. View Current disk space on Master Server

[root@mastiscsi ~]# pvdisplay /dev/sdc

--- Physical volume ---

PV Name /dev/sdc

VG Name multivg

PV Size 5.00 GB / not usable 4.00 MB

Allocatable yes

PE Size (KByte) 4096

Total PE 1279

Free PE 1079

Allocated PE 200

PV UUID Un9URB-fgvf-SBAP-AeAN-7J0I-sLWw-KIWBzI

[root@mastiscsi ~]# vgdisplay multivg

--- Volume group ---

VG Name multivg

System ID

Format lvm2

Metadata Areas 1

Metadata Sequence No 2

VG Access read/write

VG Status resizable

MAX LV 0

Cur LV 1

Open LV 0

Max PV 0

Cur PV 1

Act PV 1

VG Size 5.00 GB

PE Size 4.00 MB

Total PE 1279

Alloc PE / Size 200 / 800.00 MB

Free PE / Size 1079 / 4.21 GB

VG UUID pkBZxW-DM3m-a1dz-9MCM-gKd8-DXpr-i2cEMG

[root@mastiscsi ~]# lvdisplay /dev/multivg/multilv

--- Logical volume ---

LV Name /dev/multivg/multilv

VG Name multivg

LV UUID vlK9G8-E8lS-bEwX-2w6Z-fAFO-3Rsi-971joA

LV Write Access read/write

LV Status available

# open 0

LV Size 800.00 MB

Current LE 200

Segments 1

Allocation inherit

Read ahead sectors auto

- currently set to 256

Block device 253:4

[root@mastiscsi ~]#

2. Extend LVM on Master server

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

[root@mastiscsi ~]# lvextend -L +100MB /dev/multivg/multilv -t

[root@mastiscsi ~]# lvextend -L +100MB /dev/multivg/multilv

Extending logical volume multilv to 900.00 MB

Logical volume multilv successfully resized

[root@mastiscsi ~]# lvdisplay /dev/multivg/multilv

--- Logical volume ---

LV Name /dev/multivg/multilv

VG Name multivg

LV UUID vlK9G8-E8lS-bEwX-2w6Z-fAFO-3Rsi-971joA

LV Write Access read/write

LV Status available

# open 1

LV Size 900.00 MB

Current LE 225

Segments 1

Allocation inherit

Read ahead sectors auto

- currently set to 256

Block device 253:4

[root@mastiscsi ~]#

2. Show target details

[root@mastiscsi ~]# tgtadm --op show --mode target

Target 1: iqn.2015-08.com.example:mastiscsi.disk1

System information:

Driver: iscsi

State: ready

I_T nexus information:

I_T nexus: 7

Initiator: iqn.2015-08.com.example:mastiscsi

Connection: 0

IP Address: 192.168.144.153

I_T nexus: 10

Initiator: iqn.2015-08.com.example:mastiscsi

Connection: 0

IP Address: 192.168.144.153

LUN information:

LUN: 0

Type: controller

SCSI ID: IET 00010000

SCSI SN: beaf10

Size: 0 MB, Block size: 1

Online: Yes

Removable media: No

Readonly: No

Backing store type: null

Backing store path: None

Backing store flags:

LUN: 1

Type: disk

SCSI ID: IET 00010001

SCSI SN: beaf11

Size: 4295 MB, Block size: 512

Online: Yes

Removable media: No

Readonly: No

Backing store type: rdwr

Backing store path: /dev/sdb

Backing store flags:

Account information:

ACL information:

ALL

Target 2: iqn.2015-08.com.example:mastiscsi.disk2

System information:

Driver: iscsi

State: ready

I_T nexus information:

I_T nexus: 8

Initiator: iqn.2015-08.com.example:mastiscsi

Connection: 0

IP Address: 192.168.144.153

I_T nexus: 9

Initiator: iqn.2015-08.com.example:mastiscsi

Connection: 0

IP Address: 192.168.144.153

LUN information:

LUN: 0

Type: controller

SCSI ID: IET 00020000

SCSI SN: beaf20

Size: 0 MB, Block size: 1

Online: Yes

Removable media: No

Readonly: No

Backing store type: null

Backing store path: None

Backing store flags:

LUN: 1

Type: disk

SCSI ID: IET 00020001

SCSI SN: beaf21

Size: 839 MB, Block size: 512

Online: Yes

Removable media: No

Readonly: No

Backing store type: rdwr

Backing store path: /dev/multivg/multilv

Backing store flags:

Account information:

ACL information:

ALL

3. Delete logical unit 1 and target 2 temporarily, it will not effect on client side

[root@mastiscsi ~]# tgtadm --op delete --mode logicalunit --tid=2 --lun=1

4. View exported target backup-store path

[root@mastiscsi ~]# more /etc/tgt/targets.conf

backing-store /dev/sdb

</target>

backing-store /dev/multivg/multilv

</target>

5. Again add new logical unit 1 and target 2

[root@mastiscsi ~]# tgtadm --op new --mode logicalunit --tid=2 --lun=1 --backing-store /dev/multivg/multilv

6. Check newly updated size

[root@mastiscsi ~]# tgtadm --op show --mode target

Target 2: iqn.2015-08.com.example:mastiscsi.disk2

System information:

Driver: iscsi

State: ready

I_T nexus information:

I_T nexus: 8

Initiator: iqn.2015-08.com.example:mastiscsi

Connection: 0

IP Address: 192.168.144.153

I_T nexus: 9

Initiator: iqn.2015-08.com.example:mastiscsi

Connection: 0

IP Address: 192.168.144.153

LUN information:

LUN: 0

Type: controller

SCSI ID: IET 00020000

SCSI SN: beaf20

Size: 0 MB, Block size: 1

Online: Yes

Removable media: No

Readonly: No

Backing store type: null

Backing store path: None

Backing store flags:

LUN: 1

Type: disk

SCSI ID: IET 00020001

SCSI SN: beaf21

Size: 944 MB, Block size: 512

Online: Yes

Removable media: No

Readonly: No

Backing store type: rdwr

Backing store path: /dev/multivg/multilv

Backing store flags:

Account information

ACL information:

ALL

[root@mastiscsi ~]#

Same output can also be check by below command

[root@mastiscsi ~]# tgt-admin -s

Target 2: iqn.2015-08.com.example:mastiscsi.disk2

System information:

Driver: iscsi

State: ready

I_T nexus information:

I_T nexus: 8

Initiator: iqn.2015-08.com.example:mastiscsi

Connection: 0

IP Address: 192.168.144.153

I_T nexus: 9

Initiator: iqn.2015-08.com.example:mastiscsi

Connection: 0

IP Address: 192.168.144.153

LUN information:

LUN: 0

Type: controller

SCSI ID: IET 00020000

SCSI SN: beaf20

Size: 0 MB, Block size: 1

Online: Yes

Removable media: No

Readonly: No

Backing store type: null

Backing store path: None

Backing store flags:

LUN: 1

Type: disk

SCSI ID: IET 00020001

SCSI SN: beaf21

Size: 944 MB, Block size: 512

Online: Yes

Removable media: No

Readonly: No

Backing store type: rdwr

Backing store path: /dev/multivg/multilv

Backing store flags:

Account information:

ACL information:

ALL

[root@mastiscsi ~]#

Scan newly updated size on client machine

1. Check current disk size

[root@iscsiclient ~]# multipath -ll

mpath1 (1IET_00020001) dm-5 IET,VIRTUAL-DISK

[size=800M][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 34:0:0:1 sdc 8:32 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 33:0:0:1 sdd 8:48 [active][ready]

mpath0 (1IET_00010001) dm-4 IET,VIRTUAL-DISK

[size=4.0G][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 31:0:0:1 sdb 8:16 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 32:0:0:1 sde 8:64 [active][ready]

2. Scan block device

[root@iscsiclient ~]# echo 1 > /sys/block/sdc/device/rescan

[root@iscsiclient ~]# echo 1 > /sys/block/sdd/device/rescan

3. Check disk but not update

[root@iscsiclient ~]# multipath -ll

mpath1 (1IET_00020001) dm-5 IET,VIRTUAL-DISK

[size=800M][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 34:0:0:1 sdc 8:32 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 33:0:0:1 sdd 8:48 [active][ready]

mpath0 (1IET_00010001) dm-4 IET,VIRTUAL-DISK

[size=4.0G][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 31:0:0:1 sdb 8:16 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 32:0:0:1 sde 8:64 [active][ready]

4. Resize map by multipathd command

[root@iscsiclient ~]# multipathd -k'resize map mpath1'

Note: above space between –k and 'resize map mpath1' NOT allow

5. Check disk, now size updated

[root@iscsiclient ~]# multipath –ll

mpath1 (1IET_00020001) dm-5 IET,VIRTUAL-DISK

[size=900M][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 34:0:0:1 sdc 8:32 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 33:0:0:1 sdd 8:48 [active][ready]

mpath0 (1IET_00010001) dm-4 IET,VIRTUAL-DISK

[size=4.0G][features=0][hwhandler=0][rw]

\_ round-robin 0 [prio=1][active]

\_ 31:0:0:1 sdb 8:16 [active][ready]

\_ round-robin 0 [prio=1][enabled]

\_ 32:0:0:1 sde 8:64 [active][ready]

[root@iscsiclient ~]#

6. Check disk space

[root@iscsiclient /]# fdisk -l /dev/mapper/mpath1

Disk /dev/mapper/mpath1: 943 MB, 943718400 bytes

255 heads, 63 sectors/track, 114 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath1p1 1 101 811251 8e Linux LVM

7. Make disk partition for extending LVM

[root@iscsiclient /]# fdisk /dev/mapper/mpath1

Command (m for help): p

Disk /dev/mapper/mpath1: 943 MB, 943718400 bytes

255 heads, 63 sectors/track, 114 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath1p1 1 101 811251 8e Linux LVM

Command (m for help): n

Command action

e extended

p primary partition (1-4)

Partition number (1-4): 2

First cylinder (102-114, default 102): <enter>

Using default value 102

Last cylinder or +size or +sizeM or +sizeK (102-114, default 114): <enter>

Using default value 114

Command (m for help): p

Disk /dev/mapper/mpath1: 943 MB, 943718400 bytes

255 heads, 63 sectors/track, 114 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath1p1 1 101 811251 8e Linux LVM

/dev/mapper/mpath1p2 102 114 104422+ 83 Linux

Command (m for help): t

Partition number (1-4): 2

Hex code (type L to list codes): 8e

Changed system type of partition 2 to 8e (Linux LVM)

Command (m for help): p

Disk /dev/mapper/mpath1: 943 MB, 943718400 bytes

255 heads, 63 sectors/track, 114 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/mapper/mpath1p1 1 101 811251 8e Linux LVM

/dev/mapper/mpath1p2 102 114 104422+ 8e Linux LVM

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.

The kernel still uses the old table.

The new table will be used at the next reboot.

Syncing disks.

[root@iscsiclient /]# partprobe /dev/mapper/mpath1

device-mapper: remove ioctl failed: Device or resource busy

Warning: parted was unable to re-read the partition table on /dev/mapper/mpath1 (Device or resource busy). This means Linux won't know anything about the modifications you made.

device-mapper: create ioctl failed: Device or resource busy

device-mapper: remove ioctl failed: Device or resource busy

[root@iscsiclient /]# partprobe /dev/mapper/mpath1p2

Note: above both commands (partprobe /dev/mapper/mpath1 & partprobe /dev/mapper/mpath1p2) require to run. Error comes on first command. It is ok

8. Check new device mapper list

[root@iscsiclient /]# ls -l /dev/mapper/

total 0

crw------- 1 root root 10, 60 Aug 28 18:37 control

brw-rw---- 1 root disk 253, 4 Aug 28 18:37 mpath0

brw-rw---- 1 root disk 253, 7 Aug 29 14:58 mpath0p1

brw-rw---- 1 root disk 253, 5 Aug 29 15:35 mpath1

brw-rw---- 1 root disk 253, 6 Aug 29 14:54 mpath1p1

brw-rw---- 1 root disk 253, 9 Aug 29 15:36 mpath1p2

brw-rw---- 1 root disk 253, 8 Aug 29 15:22 mpath1vg-mpath1--lv

brw-rw---- 1 root disk 253, 2 Aug 28 18:37 vg0-home

brw-rw---- 1 root disk 253, 0 Aug 28 18:37 vg0-root

brw-rw---- 1 root disk 253, 3 Aug 28 18:37 vg0-swap

brw-rw---- 1 root disk 253, 1 Aug 28 18:37 vg0-var

[root@iscsiclient /]#

9. Create PV and extend VG & LVM

[root@iscsiclient /]# pvcreate /dev/mapper/mpath1p2 -t

[root@iscsiclient /]# pvcreate /dev/mapper/mpath1p2

[root@iscsiclient /]# vgextend mpath1vg /dev/mapper/mpath1p2 -t

[root@iscsiclient /]# vgextend mpath1vg /dev/mapper/mpath1p2

[root@iscsiclient /]# lvextend -l +100%FREE /dev/mpath1vg/mpath1-lv -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Extending logical volume mpath1-lv to 892.00 MB

Logical volume mpath1-lv successfully resized

[root@iscsiclient /]# lvextend -l +100%FREE /dev/mpath1vg/mpath1-lv

Extending logical volume mpath1-lv to 892.00 MB

Logical volume mpath1-lv successfully resized

Note: for specific size run below command

[root@iscsiclient /]# lvextend -L +500M /dev/mpath1vg/mpath1-lv

10. Resize file system

[root@iscsiclient /]# resize2fs /dev/mpath1vg/mpath1-lv

resize2fs 1.39 (29-May-2006)

Filesystem at /dev/mpath1vg/mpath1-lv is mounted on /mpath1-lv; on-line resizing required

Performing an on-line resize of /dev/mpath1vg/mpath1-lv to 228352 (4k) blocks.

The filesystem on /dev/mpath1vg/mpath1-lv is now 228352 blocks long.

11. Check disk space

[root@iscsiclient /]# df -h

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/vg0-root 20G 3.1G 16G 17% /

/dev/mapper/vg0-var 9.7G 222M 9.0G 3% /var

/dev/mapper/vg0-home 992M 34M 908M 4% /home

/dev/sda1 244M 14M 218M 6% /boot

tmpfs 500M 0 500M 0% /dev/shm

/dev/mapper/mpath0p1 4.0G 73M 3.7G 2% /datalv

/dev/mapper/mpath1vg-mpath1--lv

879M 17M 820M 2% /mpath1-lv

[root@iscsiclient /]#

How to enable kdump on on RHEL 7.1

2015-12-24T16:38:00.001+05:30

Find below steps to enable "kdump" on RHEL 7.1 (3.10.0-229.el7.x86_64)

1. Check & install kexec-tools-2.0.7-19.el7.x86_64:
# rpm -q kexec-tools
kexec-tools-2.0.7-19.el7.x86_64

2. Add memory option "crashkernel=auto" in grub:
# cat /etc/default/grub
GRUB_CMDLINE_LINUX="rd.lvm.lv=rootVG/swap crashkernel=auto rd.lvm.lv=rootVG/root rhgb quiet"

3. Regenerate grub configuration:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-229.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-229.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-67139936cbf84fe784a0953eb1e18aec
Found initrd image: /boot/initramfs-0-rescue-67139936cbf84fe784a0953eb1e18aec.img
done

4. Verify below parameters in /etc/kdump.conf file:
# cat /etc/kdump.conf
path /var/crash
core_collector makedumpfile -l --message-level 1 -d 31

5. Check & enable the kdump service
# systemctl status kdump.service
kdump.service - Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; disabled)
Active: inactive (dead)

# systemctl enable kdump.service
ln -s '/usr/lib/systemd/system/kdump.service' '/etc/systemd/system/multi-user.target.wants/kdump.service'

6. Reboot the server
# reboot

7. Check status of kdump service:
# systemctl status kdump.service
kdump.service - Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)
Active: active (exited) since Wed 2015-12-23 14:48:14 IST; 54s ago
Process: 1895 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS)
Main PID: 1895 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/kdump.service

Dec 23 14:48:04 test1.example.com systemd[1]: Starting Crash recovery kernel arming...
Dec 23 14:48:14 test1.example.com kdumpctl[1895]: kexec: loaded kdump kernel
Dec 23 14:48:14 test1.example.com kdumpctl[1895]: Starting kdump: [OK]
Dec 23 14:48:14 test1.example.com systemd[1]: Started Crash recovery kernel arming.

How to test kdump Configuration

1. Test the kdump configuration after reboot check service running status:
# systemctl is-active kdump
active

2. Run following commands at a shell prompt:
# echo 1 > /proc/sys/kernel/sysrq
# echo c > /proc/sysrq-trigger

Above commands will force the Linux kernel to crash, and the address-YYYY-MM-DD-HH:MM:SS/vmcore file will be copied to the location you have selected in the configuration (that is, to /var/crash/ by default).

Online add space in existing disk by PVRESIZE command in RHEL

2015-11-26T15:00:00.000+05:30

Step 1) scan disk
# fdisk -l | grep -i Disk | grep -i dev
Disk /dev/sdb: 42.9 GB, 42949672960 bytes
Disk /dev/sda: 64.4 GB, 64424509440 bytes

Scan scsi disk:
# ls /sys/class/scsi_host/
host0 host1
# echo "- - -" > /sys/class/scsi_host/host0/scan
# echo "- - -" > /sys/class/scsi_host/host1/scan

or, scan block disk if require
# echo 1 > /sys/block/sdb/device/rescan

# fdisk -l | grep -i Disk
Disk /dev/sdb: 64.4 GB, 64424509440 bytes
Disk /dev/sda: 64.4 GB, 64424509440 bytes

Step 2) resize physical disk
# pvresize /dev/sdb
Physical volume "/dev/sdb" changed
1 physical volume(s) resized / 0 physical volume(s) not resized

# pvs
PV VG Fmt Attr PSize PFree
/dev/sdb vg_xxxxxxxx lvm2 a-- 60.00g 20.00g

Now additional disk is visible by vgdisplay command
# vgdisplay
Format lvm2
VG Access read/write
VG Status resizable
VG Size 60.00 GiB <--------
PE Size 4.00 MiB
Total PE 15359
Alloc PE / Size 10239 / 40.00 GiB
Free PE / Size 5120 / 20.00 GiB <--------

Step 3) Extend existing volume
# lvextend -L +20G /dev/vg_xxxxxxxx/lv_xxxxxxxx -t
TEST MODE: Metadata will NOT be updated and volumes will not be (de)activated.
Size of logical volume vg_xxxxxxxx/lv_xxxxxxxx changed from 40.00 GiB (10239 extents) to 60.00 GiB (15359 extents).
Logical volume lv_xxxxxxxx successfully resized

or, you can extend 100% disk space
#/usr/sbin/lvextend -l +100%FREE /dev/vg_xxxxxxxx/lv_xxxxxxxx -t

# lvextend -L +20G /dev/vg_xxxxxxxx/lv_xxxxxxxx
Size of logical volume vg_xxxxxxxx/lv_xxxxxxxx changed from 40.00 GiB (10239 extents) to 60.00 GiB (15359 extents).
Logical volume lv_xxxxxxxx successfully resized

# resize2fs /dev/vg_xxxxxxxx/lv_xxxxxxxx
resize2fs 1.41.12 (17-May-2010)
Filesystem at /dev/vg_xxxxxxxx/lv_xxxxxxxx is mounted on /xxxxxxxx; on-line resizing required
old desc_blocks = 3, new_desc_blocks = 4
Performing an on-line resize of /dev/vg_xxxxxxxx/lv_xxxxxxxx to 15727616 (4k) blocks.
The filesystem on /dev/vg_xxxxxxxx/lv_xxxxxxxx is now 15727616 blocks long.

Step 4) Check file system
# df -h

/var/spool/clientmqueue contains number of files

2015-11-25T14:45:00.000+05:30

Check the contents of /var/spool/clientmqueue:

# ls -ltr /var/spool/clientmqueue | more
# more /var/spool/clientmqueue/filename

If it is all unwanted email, the below procedure will remove the files:

# cd /var/spool/clientmqueue
# find . -type f -exec rm {} \;

Note : If the email is important, then configure sendmail correctly to deliver this mail.

Generate SSH (.ppk) keys and connect user account with Putty on Windows

2014-05-12T15:25:00.001+05:30

Step 1: Download “puttygen.exe” and run to generate public/private ssh (.ppk) key file.

Step 2: Launch the “puttygen” on windows, keep all default settings:

Step 3: Now click on “Generate” button to create key.

Note: Move your mouse around within the blank space during the key generation process.

Step 4: Once the generator is complete, you will see a windows with your new public key and key fingerprint:

Step 5: You can change the “Key comment” like hostname or any other remarks as you want

Step 6: if you want, you can fill the “key passphrase” and “confirm passphrase” fields.

Step 7: Select the contents of public key in that large text field and copy the entire content (CTRL+C) into clipboard.

Note: Do not quit puttygen.exe at this time.

ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAIEAhCdDMhGHdaw1uj9MH2xCB4jktwIgm4Al7S8rxvovMJBAuFKkMDd0vW5gpurUAB0PEPkxh6QFoBNazvio7Q03f90tSP9qpJMGwZid9hJEElplW8p43D3DdxXykLays2M8V2viYGLbiXvAbOECzwD4IaviOpylX0PaFznSR4ssXd0= my-workstation-home

Step 8: Now open up Notepad and paste (CTRL + V) the content into a new file. Save file with “.txt” extension, like publickey.txt.

Note: The public key is what will be put on your server.

Step 9: Go back to PuttyGen and click on the “Save private key” button on the main window under the “Save the generated key” section. You can call that file “privatekey” or “privatekey.ppk”

Note: The private key remains private and should never be given to anyone. It does not go on your site account; it stays on your workstation. Keep this file safe or else you will need to re-do everything if the private key is ever lost.

Step 10: Now you have a public and private key file saved on your workstation. You can quit out of PuTTYGen now.

Step 11: Login to site via SSH, you can install your public key: Category à Connection àSSH à Auth à click on browse button and find the private key generated previously and click the “Open” button to load it.

Step 12: In Category section à select Session” à fill hostname / ip-address à click on “Open” button and then you will get prompt for username and password.

Step 13: Type the following command at the prompt and press enter key:

$ mkdir ~/.ssh; touch ~/.ssh/authorized_keys; chmod 700 ~/.ssh; chmod 600 ~/.ssh/authorized_keys

Step 14: open the “authorized_keys” file in command line and use nano here:

$ nano ~/.ssh/authorized_keys

Note : Once you have made your changes, you can exit “nano” by pressing “Ctrl+X”, then press “Y”, and finally “enter” to confirm the overwrite/filename.

Step 15: After entering passphrase you should be logged into your account via SSH

Authenticating with public key "my-workstation-home"

Passphrase for key "my-workstation-home":

Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon’ is loaded, or, Failed to open device “/dev/vmci”: No such file or directory. Please make sure that the kenel module ‘vmci’ is loaded. Module Device PowerOn power on failed

2014-04-21T15:41:00.001+05:30

Solution:

Step 1) Check current version & other details like:

o Version: Workstation 6.5 virtual machine

o Guest OS: Red Hat Enterprise Linux 5

o Configuration files & Snapshot, etc.

Step 2) Check current running process, Ram & Disk Status:

# top

# free –m

# ps –ef | grep vmware

Step 3) Check current loaded module for error:

# lsmod | grep vm

Module vmmon loaded

Module vmnet not loaded

Step 4) For rectifying the above issue runs command to load VM modules:

# /etc/init.d/vmware restart

Stopping VMware services:

Virtual machine communication interface[ OK ]

Virtual machine monitor[ OK ]

Blocking file system[ OK ]

Starting VMware services:

Virtual machine monitor[ OK ]

Virtual machine communication interface[ OK ]

Blocking file system[ OK ]

Virtual ethernet[ OK ]

Shared Memory Available[ OK ]

Step 5) To start VMware services automatically while rebooting the server, run below command:

# chkconfig --list | grep vm

vmware 0:off 1:off 2:off 3:off 4:off 5:off 6:off

# chkconfig vmware on

# chkconfig vmware on--list | grep vm

vmware 0:off 1:off 2:on 3:on 4:on 5:on 6:off

Step 6) Now check current running processes:

# top

# ps –ef | grep vmware

Configuring the TSM Backup Agent Web client on Unix/Linux Operating System

2013-09-19T16:04:00.003+05:30

To configure the Web client from the command line, perform the following steps:

Step 1) If MANAGEDServices scheduler is set, specify “MANAGEDServices webclient scheduler” in the dsm.sys file.

Step 2) Ensure that you specify “passwordaccess generate” in the dsm.sys file.

Step 3) Generate the Tivoli Storage Manager password; start the backup-archive client by entering the following command:

#dsmc query session

When prompted, enter your user ID and password.

Step 4) Start the client acceptor daemon (CAD) by entering the following command:

#dsmcad

Step 5) Access the Web client, enter the following URL from any supported browser, where your_machine_name is the host name of the machine running the Web client:

http://your_machine_name:1581

Step 6) Run the schedule service in the background:

# nohup dsmc schedule 2> /dev/null &

Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration

2013-07-18T09:10:00.004+05:30

Problem:

# tail -f ../logs/error.log

[Tue Jul 09 13:32:24 201x] [alert] [client 10.26.45.83] /folder1/folder2/.htaccess: Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration
[Tue Jul 09 13:32:25 201x] [alert] [client 10.26.45.83] /folder1/folder2/.htaccess: Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration

Solution:

Step 1: Enable header module

# vi httpd.conf

LoadModule headers_module modules/mod_headers.so

Step 2: Restart the http server

# service httpd configtest

# service httpd restart

Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist

2013-07-12T11:22:00.001+05:30

Problems:

130702 12:48:19 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
130702 12:48:19 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Solution:

Step 1 Change “datadir” option to new directory i.e. /abcdb

# vi /etc/my.cnf

[mysqld]

datadir=/abcdb

socket=/var/lib/mysql/mysql.sock

user=mysql

symbolic-links=0

[mysqld_safe]

log-error=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

Step 2 Change ownership “mysql” of “/abcdb” directory.

Step 3 Disable selinux

Step 4 Run below command:

#mysql_install_db -user=mysql -ldata=/abcdb

Step 5 Restart the mysqld service

Large memory usage problem in Red Hat 6.x

2013-07-01T18:39:00.000+05:30

Step 1: Check memory usages

# free -m

total used free shared buffers cached

Mem: 16081 15848 232 0 379 13846

Still memory utilization is very high.

Step 2: Check value of ‘vm.vfs_cache_pressure’

# sysctl -a | grep vfs_cache_pressure

vm.vfs_cache_pressure = 100

Step 3: Change 1000 instead of 100

# vi /etc/sysctl.conf

vm.vfs_cache_pressure = 1000

Step 4: Make value effective

# sysctl -p

vm.vfs_cache_pressure = 1000

Set /proc/sys/vm/vfs_cache_pressure at 1000, memory usage would usually hover around 700-900MB, but if anything needs lots of memory (e.g. copying lots amount of data to tmpfs) it's usage would drop back to around 100-130MB mark.

Step 5: Check memory usages

# free -m

total used free shared buffers cached

Mem: 16081 15884 197 0 379 13850

Step 6: Run below command again

# sync && echo 3 > /proc/sys/vm/drop_caches

Meaning of above command parameters

echo 1 > /proc/sys/vm/drop_caches # free pagecache, [OR]

echo 2 > /proc/sys/vm/drop_caches # free dentries and inodes, [OR]

echo 3 > /proc/sys/vm/drop_caches # free pagecache, dentries and inodes

sync # forces the dump to be destructive

Step 7: Check memory usages

# free -m

total used free shared buffers cached

Mem: 16081 1166 14915 0 4 149

Steps to take DB backup in TSM 6.3

2013-06-29T09:32:00.001+05:30

Step 1: Create folder where you want to store the DB backup

mkdir E:\dbbackup

Step 2: update the device class ‘maximum volume capacity’ and ‘path to store files’

UPDATE DEVCLASS FILEDEV1 DIR=E:\DBBACKUP MAXCAP=50G SHARED=YES

Step 3: Take full backup of DB

backup db type=full devclass=filedev1

Error will generate:

ANR2590E BACKUP DB failed - SET DBRECOVERY command has not been issued.
ANS8001I Return code 3.

Step 4: Set device class for automatic DB backup to FILEDEV1

set dbrecovery filedev1

Step 5: Again take full backup of DB

backup db type=full devclass=filedev1

Now process will start and at the end it will show message like “Database Backup running in the BACKGROUND completed with completion state SUCCESS at xx:xx:xx.”

There are following types of backup you can run. This parameter is optional. The default is

INCREMENTAL.

a) Incremental

An incremental (or cumulative) backup image contains a copy of all database data that has changed since the last successful full backup operation was performed.

b) Full

To run a full backup of the Tivoli Storage Manager database.

c) DBSnapshot

To run a full snapshot database backup. The entire contents of a database are copied and a new snapshot database backup is created without interrupting the existing full and incremental backup series for the database.

Step 6: Take backup of Server sequential volume history information file

backup volhist f=e:\dbbackup\volhist.out wait=yes

Step 7: Take backup of Server device configuration information file

backup devconfig f=e:\dbbackup\devconfig.out wait=yes

Step 6: Delete sequential volume history entries

delete volhist t=dbb todate=today-2 wait=yes

Administrator user management in TSM 6.x

2013-06-28T17:36:00.000+05:30

1. Create a new TSM administrator ‘john’ with password ‘john123’
register admin john john123

2. Assign ‘policy’ privilege to new administrator

grant authority john classes=policy

There are following types of privileges:

        -          System
        -          Policy
        -          Storage
        -          Operator
        -          Node

3.    Check admin
        query admin
        query admin john f=d

4. Remove privilege of administrator

        revoke authority john

5.    Remove administrator
        remove admin john
                 Confirm deletion of administrator by typing ‘yes’

How to set password expiration period in TSM 6.x ?

2013-06-27T14:38:00.000+05:30

Step 1: Login through TSM Admin user

Step 2: Check current password expiration period

tsm> q stat
Password Expiration Period: 90 Day(s)

Step 3: Run below command to set expiry period:

tsm> set passexp 9999
ANR2092I Password expiration period set to 9999 days.

Step 4: Check again current status

tsm> q stat
Password Expiration Period: 9,999 Day(s)

Step 5: Logout from TSM Admin user

How to change Date & Time in Solaris 10 OS?

2013-06-26T14:34:00.002+05:30

# date –u 010100302000

(01-MM; 01-DD; 00-TT; 30-MINUTES; 2000- Year) – 1^st January 2000 12:30 AM

# date 033117152006

(03-MM; 31-DD; 17-TT; 15-MIN; 2006-Year) – 31^st March 2006 5:15 PM

warning: include(): Unable to allocate memory for pool.

2013-06-25T18:12:00.000+05:30

Problem: warning: require_once(): Unable to allocate memory for pool

Solution:

Add these lines to the end of your php.ini file

[xdebug]

apc.enabled=1
apc.shm_segments=1
apc.shm_size=128M
apc.cache_by_default=1
apc.stat=1
apc.rfc1867=1
apc.stat=0

So the trick to change 32M to 128M and the apc.stat=7200 to = 0.

Restart the web server.

How to change Date & Time in Red Hat Linux 5.x?

2013-06-23T14:40:00.002+05:30

# date --set=”9 AUG 2011 12:50:00”

# date

How to start TSM client schedule in Linux environment?

2013-06-22T17:39:00.001+05:30

1. Change to the Tivoli Storage Manager Installation directory and enter the following command:
$ dsmc schedule

Note : When you start the client scheduler, it runs continuously until you close the window, end the process, or log off your system.

2. If the Tivoli Storage Manager client executable directory is not in your PATH environment variable, change to the installation directory and enter the following command:

$ ./dsmc schedule

3. To run the schedule command in the background and to keep the client scheduler running, even if you log off your system, enter the following:

$ nohup dsmc schedule 2> /dev/null &

How take DB2 database backup, setup in Linux environment?

2013-06-21T14:13:00.001+05:30

Check DB directory list

[db2inst1@nodexxxx ~]$ db2 list db directory
System Database Directory
Number of entries in the directory = 1
Database 1 entry:
Database alias                       = DBXXX
Database name                        = DBXXX
Local database directory             = /home/db2inst1
Database release level               = b.00
Comment                              =
Directory entry type                 = Indirect
Catalog database partition number    = 0
Alternate server hostname            =
Alternate server port number         =

[db2inst1@nodexxxx ~]$ ls -l

drwxr-xr-x 2 db2inst1 db2grp1 4096 Feb 15 15:35 backup_store

[db2inst1@nodexxxx ~]$ cd backup_store/

[db2inst1@nodexxxx backup_store]$ db2 backup db DBXXX compress

SQL1035N The database is currently in use. SQLSTATE=57019

[db2inst1@nodexxxx backup_store]$ db2 force application all

DB20000I The FORCE APPLICATION command completed successfully.
DB21024I This command is asynchronous and may not be effective immediately.

[db2inst1@nodexxxx backup_store]$ db2 backup db DBXXX compress

Backup successful. The timestamp for this backup image is : 20130218184329

[db2inst1@nodexxxx backup_store]$ ls -l

total 353652
-rw-r----- 1 db2inst1 db2grp1 361779200 Feb 18 18:46 DBXXX.0.db2inst1.NODE0000.CATN0000.20130218184329.001

How to define daily/weekly schedule in Tivoli Storage Manager 6.3?

2013-06-20T09:33:00.000+05:30

Define selective schedule (win-test-bkp) backup to take WEEKLY backup of windows base BA client:
tsm: SRV1>DEF SCH STANDARD win-test-bkp TYPE=CLIENT ACTION=SELECTIVE OBJECTS="c:\bkptest\*" OPTIONS=-subdir=yes STARTDATE=06/18/2013 STARTTIME=22:30:00 DAYOFWEEK=SAT PRIORITY=5 DURATION=15 DURUNITS=MINUTES

Define incremental schedule (daily_increment_bkp) backup to take DAILY backup of Linux base BA client:
tsm: SRV1>DEFINE SCHEDULE STANDARD daily_increment_bkp TYPE=CLIENT ACTION=INCREMENTAL OBJECTS="/xyz/*" OPTIONS=-subdir=yes SCHEDSTYLE=ENHANCED STARTDATE=06/17/2013 STARTTIME=23:40:00 DAYOFWEEK=TUE,WED,THU,FRI,SAT PRIORITY=5 DURATION=15 DURUNITS=MINUTES

Define association of schedule (win-test-bkp) backup with specific client node (baclxxxx):

tsm: SRV1>DEFINE ASSOCIATION STANDARD win-test-bkp baclxxxx

Update schedule (daily_increment_bkp) start date & time:

tsm: SRV1>UPDATE SCHEDULE STANDARD daily_increment_bkp STARTDATE=06/18/2013 STARTTIME=00:00:00

Check schedule (win-test-bkp) status:

tsm: SRV1>QUERY EVENT * *
tsm: SRV1>QUERY SCHEDULE STANDARD f=d
tsm: SRV1>QUERY ASSOCIATION
tsm: SRV1>QUERY ASSOCIATION STANDARD win-test-bkp

Update schedule (daily_increment_bkp) backup:

tsm: SRV1>UPDATE SCHEDULE STANDARD daily_increment_bkp SCHEDSTYLE=CLASSIC PERIOD=1 PERUNITS=days DAYOFWEEK=ANY
tsm: SRV1>UPDATE SCHEDULE STANDARD daily_increment_bkp SCHEDSTYLE=ENHANCED DAYOFWEEK=MON,TUE,WED,THU,FRI WEEKOFMONTH=ANY MONTH=ANY

Delete schedule (win-test-bkp):

tsm: SRV1>DELETE SCHEDULE STANDARD win-test-bkp

Backup-Archive (BA) & Oracle Tivoli Data Protection (TDP) Configuration on Linux 5.x base OS

2013-06-19T14:19:00.000+05:30

Software details:

OS - Redhat Linux 5.3 64 bits
DB - Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit
BA - TIVsm-BA-6.3.0-0
API - TIVsm-API64-6.3.0-0
TDP - TDP-Oracle-5.5.1-0

For BA configuration

[root@oraxxxx ~]# ls -l /opt/tivoli/tsm/client/ba/bin/

-rw-r--r-- 1 root root 20 Feb 14 16:54 dsm.opt
-rw-r--r-- 1 root root 381 Jun 14 17:34 dsm.sys

[root@oraxxxx ~]# cat /opt/tivoli/tsm/client/ba/bin/dsm.opt

SERVERNAME ORAXXXX

[root@oraxxxx ~]# cat /opt/tivoli/tsm/client/ba/bin/dsm.sys

SERVERNAME oraxxxx
   COMMMethod         TCPip
   TCPPort            1500
   NODENAME         oraxxxx
   TCPSERVERADDRESS tsmservx.abctest.com
   passwordaccess       generate

SERVERNAME oraxxxxtsm
   COMMMethod         TCPip
   TCPPort            1500
   NODENAME         oraxxxx_tdp
   TCPSERVERADDRESS tsmservx.abctest.com
   passworddir /home/oracle
   passwordaccess       generate

For API Configuration

[root@oraxxxx ~]# ls -l /opt/tivoli/tsm/client/api/bin64/

-r--r--r-- 1 root root 809 Feb 19 16:11 dsm.opt
-rw-r--r-- 1 root root 388 Feb 19 16:12 dsm.sys

[root@oraxxxx ~]# cat /opt/tivoli/tsm/client/api/bin64/dsm.opt

SErvername oraxxxxtsm

[root@oraxxxx ~]# cat /opt/tivoli/tsm/client/api/bin64/dsm.sys

SERVERNAME oraxxxxtsm
   COMMMethod         TCPip
   TCPPort            1500
   NODENAME         oraxxxx_tdp
   TCPSERVERADDRESS tsmservx.abctest.com
   passworddir /home/oracle

For TDP Configuration

[root@oraxxxx ~]# ls -l /opt/tivoli/tsm/client/oracle/bin64/

-r--r--r-- 1 oracle root    808 Feb 12 16:34 dsm.opt
-r--r--r-- 1 oracle root    968 Feb 12 16:11 dsm.sys
-rwxr-xr-x 1 root   root 507072 Mar 28 2008 tdpoconf
-rwxr-xr-x 1 oracle root    707 Feb 18 17:02 tdpo.opt

[root@oraxxxx ~]# cat /opt/tivoli/tsm/client/oracle/bin64/dsm.opt

SErvername oraxxxxtsm

[root@oraxxxx ~]# cat /opt/tivoli/tsm/client/oracle/bin64/dsm.sys

SErvername      oraxxxx
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tsmservx.abctest.com

[root@oraxxxx ~]# cat /opt/tivoli/tsm/client/oracle/bin64/tdpo.opt

DSMI_ORC_CONFIG /opt/tivoli/tsm/client/oracle/bin64/dsm.opt
DSMI_LOG /opt/tivoli/tsm/client/oracle/bin64

TDPO_FS /adsmorc

TDPO_NODE          oraxxxx_tdp
TDPO_OWNER         oracle
TDPO_PSWDPATH      /opt/tivoli/tsm/client/oracle/bin64

TDPO_DATE_FMT 1

TDPO_NUM_FMT 1
TDPO_TIME_FMT 1

TDPO_MGMT_CLASS_2 mgmtclass2

TDPO_MGMT_CLASS_3 mgmtclass3
TDPO_MGMT_CLASS_4 mgmtclass4

[root@oraxxxx ~]# /opt/tivoli/tsm/client/oracle/bin64/tdpoconf password

***************************************************************

* IBM Tivoli Storage Manager for Databases Utility
* Password file initialization/update program
***************************************************************

Please enter current password:

Please enter new password:

Please reenter new password for verification:

ANU0260I Password successfully changed.

[root@oraxxxx ~]# /opt/tivoli/tsm/client/oracle/bin64/tdpoconf showenv

Data Protection for Oracle Information

Version:              5
Release:              5
Level:                1
Sublevel:             0
Platform:             64bit TDPO LinuxAMD64

Tivoli Storage Manager Server Information

Server Name:          ORAXXXXTSM
Server Address:       TSMSERVX.ABCTEST.COM
Server Type:          Windows
Server Port:          1500
Communication Method: TCP/IP

Session Information
Owner Name:           oracle
Node Name:            oraxxxx_tdp
Node Type:            TDPO LinuxAMD64
DSMI_DIR:             /opt/tivoli/tsm/client/api/bin64
DSMI_ORC_CONFIG:      /opt/tivoli/tsm/client/oracle/bin64/dsm.opt
TDPO_OPTFILE:         /opt/tivoli/tsm/client/oracle/bin64/tdpo.opt
Password Directory:   /opt/tivoli/tsm/client/oracle/bin64
Compression:          FALSE

License Information: License file exists and contains valid license data.

Check above configuration

[root@oraxxxx ~]# dsmc

IBM Tivoli Storage Manager
Command Line Backup-Archive Client Interface
Client Version 6, Release 3, Level 0.0
Client date/time: 06/17/2013 14:39:31
(c) Copyright by IBM Corporation and other(s) 1990, 2011. All Rights Reserved.

Node Name: ORAXXXX

Session established with server SMBACKPHY01_SERVER1: Windows
Server Version 6, Release 3, Level 0.0
Server date/time: 06/17/2013 02:28:02 Last access: 06/14/2013 05:45:12
tsm> quit

[root@oraxxxx ~]# dsmc -servername=oraxxxxtsm

IBM Tivoli Storage Manager
Command Line Backup-Archive Client Interface
Client Version 6, Release 3, Level 0.0
Client date/time: 06/17/2013 14:40:30
(c) Copyright by IBM Corporation and other(s) 1990, 2011. All Rights Reserved.

Node Name: ORAXXXX_TDP

Session established with server SMBACKPHY01_SERVER1: Windows
Server Version 6, Release 3, Level 0.0
Server date/time: 06/17/2013 02:29:01 Last access: 06/17/2013 02:20:43
tsm> quit

ANS1126E (RC27) The file space cannot be deleted because this node does not have permission to delete archived or backed up data.

2013-06-18T10:56:00.000+05:30

Problem:

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on sbt1 channel at 06/17/2013 16:40:49
ORA-19509: failed to delete sequential file, handle="/orcl/bk_152_1_818350547", parms=""
ORA-27027: sbtremove2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1126E (RC27) The file space cannot be deleted because this node does not have permission to delete archived or backed up data.

Solution:

Check output of node details on TSM Server:

tsm:SRV1>q node oraxxxx_tdp f=d

Backup Delete Allowed?: No

Update backup Delete option ‘yes’:

tsm: SRV1>update node oraxxxx_tdp backdelete=yes

ANR2063I Node ORAXXXX_TDP updated.

Again check output of node option:

tsm:SRV1>q node oraxxxx_tdp f=d

Backup Delete Allowed?: Yes

Now start RMAN script to take backup of Oracle Database through TSM Server on DB Server

[oracle@oraxxxx ~]$ ./rman.sh

piece handle=/orcl/bk_164_1_818356487 tag=TAG20130617T171447 comment=API Version 2.0,MMS
piece handle=/orcl/bk_165_1_818356974 tag=TAG20130617T171447 comment=API Version 2.0,MMS
piece handle=/orcl/al_166_1_818356993 tag=TAG20130617T172313 comment=API Version 2.0,MMS
piece handle=/orcl/al_167_1_818357109 tag=TAG20130617T172313 comment=API Version 2.0,MMS
piece handle=/orcl/cntrl_168_1_818357204 tag=TAG20130617T172644 comment=API Version 2.0,MMS
released channel: sbt1
Recovery Manager complete.

[oracle@oraxxxx ~]$

Check Oracle DB backup status on TSM Server

tsm:SRV1>q cont E:\TIVOLI\TSM\SERVER1\DISK1.DSM node=oraxxxx_tdp

Node Name        Type Filespace   FSID Client's Name for File
                             Name
--------------- ---- ---------- ---- --------------------------------------
ORAXXXX_TDP     Bkup /adsmorc       1 ///orcl/bk_164_1_818356487
ORAXXXX_TDP     Bkup /adsmorc       1 ///orcl/bk_165_1_818356974
ORAXXXX_TDP     Bkup /adsmorc       1 ///orcl/al_166_1_818356993
ORAXXXX_TDP     Bkup /adsmorc       1 ///orcl/al_167_1_818357109
ORAXXXX_TDP     Bkup /adsmorc       1 ///orcl/cntrl_168_1_818357204
tsm:SRV1>

tsm:SRV1>q occupancy oraxxxx_tdp

Node Name Type Filespace FSID Storage      Number of    Physical     Logical
                Name            Pool Name        Files       Space       Space
                                                         Occupied    Occupied
                                                              (MB)        (MB)
---------- ---- ---------- ---- ---------- ----------- ----------- -----------
ORAXXXX_- Bkup /adsmorc      1 DISKPOOL            17   10,104.37   10,104.37
TDP
tsm:SRV1>quit

RMAN Script for taking backup of Oracle Database through TSM 6.x

2013-06-17T17:18:00.000+05:30

[oracle@oraxxxx ~]$ ls -l
-rwxr--r-- 1 oracle oinstall 460 Feb 18 16:03 rman_bkp.sh
-rwxr-xr-x 1 oracle oinstall 106 Feb 13 16:49 rman.sh

[oracle@oraxxxx ~]$ cat rman.sh

export ORACLE_BASE=/u01/app/oracle/product/11.2.0/db_1
export ORACLE_SID=orcl
rman target / @rman_bkp.sh

[oracle@oraxxxx ~]$ cat rman_bkp.sh

run
{
allocate channel sbt1 type sbt parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
crosscheck archivelog all;
BACKUP FORMAT '/orcl/bk_%s_%p_%t'
    DATABASE;
    sql 'alter system archive log current';
BACKUP
filesperset 20
   FORMAT '/orcl/al_%s_%p_%t'
   ARCHIVELOG ALL;
BACKUP
    FORMAT '/orcl/cntrl_%s_%p_%t'
    CURRENT CONTROLFILE;
delete noprompt expired archivelog all;
delete noprompt obsolete;
RELEASE CHANNEL sbt1;
}

[oracle@oraxxxx ~]$ ./rman.sh

:
:
sql statement: alter system archive log current
released channel: sbt1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 06/17/2013 15:39:20
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
ORA-01109: database not open

Note: Database is not open. Check & Correct as below.

[oracle@oraxxxx ~]$ sqlplus "/ as sysdba"

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> shutdown immediate

ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.

SQL> startup

ORACLE instance started.
Total System Global Area 1052233728 bytes
Fixed Size                  2220032 bytes
Variable Size             792723456 bytes
Database Buffers          251658240 bytes
Redo Buffers                5632000 bytes
Database mounted.
Database opened.

SQL> quit