About Me

My photo
HI , this is Shivakant working in IT Infrastructure from about more than 17 years now .Implemented many small and large data centers , Executed huge Storage Migration , Implemented Backup Infrastructure for many small and Big organizations.I am a passionate learner of new technology , Love to fiddle with gadgets and read about them on internet. love to read books .

flipkart3

SNAPDEAL OFFERS

filpkartflash

Monday, July 18, 2016

CONFIGURING A ISCSI LUN ON SUSE ENTERPRISE STEP BY STEP

ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY 
 IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM, NETAPP IS REGISTERED TRADEMARK OF NETAPP 
http://aix-administration.blogspot.com/p/index-of-posts-available-in-this-blog.html

This document provides you a quick and easy way to create , map and connect a iscsi lun on a SUSE server provided from a Netapp Storage

1. Create a LUN on netapp Storage


If You need or require u may have to start iscsi on Netapp Storage

Netapp1> options iscsi
iscsi.auth.radius.enable     off
iscsi.enable                 off
iscsi.isns.rev               22
iscsi.max_connections_per_session use_system_default
iscsi.max_error_recovery_level use_system_default
Netapp1> options iscsi.enable on
Sun Jul 17 07:05:14 GMT [iscsi.service.startup:info]: iSCSI service startup
Netapp1> Sun Jul 17 07:05:21 GMT [iscsi.notice:notice]: ISCSI: New session from initiator iqn.1996-04.de.suse:01:28daa723906a at IP addr 192.168.1.201


Pretty Simple eh .

Now to configure and create a LUN in Netapp i have created a post which shows step by step command line for the same

http://aix-administration.blogspot.com/2013/12/creating-and-mapping-lun-in-netapp-ontap.html


2. Install  ISCSI client on SUSE Server.

Use yast2 to install iscsi client software , my setup consist of two nodes which are sharing a common LUN .

yast2 iscsi-client

Check for their initiator name 

suselinux1:/etc/iscsi # cat initiatorname.iscsi
##
## /etc/iscsi/iscsi.initiatorname
##
## Default iSCSI Initiatorname.
##
## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1996-04.de.suse:01:28daa723906a
suselinux1:/etc/iscsi #



suselinux2:/etc/iscsi # cat initiatorname.iscsi
##
## /etc/iscsi/iscsi.initiatorname
##
## Default iSCSI Initiatorname.
##
## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1996-04.de.suse:01:72db16323855
suselinux2:/etc/iscsi #


3.Create a IGROUP on Neatapp Storage .

The Iscsi initiator shown above will be used to create a igroup . This is a kind of access list which authorizes the use/visibility of LUNS.

Netapp1> igroup create -i -t linux suseigrp iqn.1996-04.de.suse:01:72db16323855 iqn.1996-04.de.suse:01:28daa723906a
Netapp1> lun show
        /vol/testvol/SBDlun          100m (104857600)     (r/w, online)
        /vol/testvol/clvmdlun          2g (2147483648)    (r/w, online)
        /vol/testvol/extlun1           2g (2147483648)    (r/w, online)
        /vol/testvol/ocfs2lun          2g (2147483648)    (r/w, online)



3. Map LUN to IGROUP .

Netapp1> lun map  /vol/testvol/SBDlun suseigrp
Sun Jul 17 06:49:02 GMT [lun.map:info]: LUN /vol/testvol/SBDlun was mapped to initiator group suseigrp=0

4. Configure ISCSI on SuSE Server .

Run below commands on the SUSE Servers .

iscsiadm -m discovery -t sendtargets -p 192.168.1.50
iscsiadm -m node -p 192.168.1.50 -l all


In my case target IP is 192.168.1.50

The above commands will create directories in /etc/iscsi directory

suselinux2:~ # cd /etc/iscsi/
suselinux2:/etc/iscsi # ls

For Example nodes and send_targets
ifaces  initiatorname.iscsi  iscsid.conf  lock  nodes  send_targets

In nodes directory you will find target directory and in that each associated path in each path open the file named  default and 

suselinux2:/etc/iscsi # cd nodes/
suselinux2:/etc/iscsi/nodes # ls
iqn.1992-08.com.netapp:sn.80335005
suselinux2:/etc/iscsi/nodes # cd iqn.1992-8.com.netapp\:sn.80335005/

suselinux2:/etc/iscsi/nodes/iqn.1992-08.com.netapp:sn.80335005 # ls
192.168.1.50,3260,1000  192.168.1.51,3260,1001
suselinux2:/etc/iscsi/nodes/iqn.1992-08.com.netapp:sn.80335005 #

in each directory change the line "node.startup" from manual to automatic 

change the line below as it is it is supposed to be manual just change it to automatic 

node.startup = automatic




Monday, July 11, 2016

RESIZE PV IN LINUX , HOW TO INCREASE PV SIZE AFTER INCREASING LUN AT STORAGE LEVEL , ONLINE RESIZE LINUX VOLUME

ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM, NETAPP IS REGISTERED TRADEMARK OF NETAPP
http://aix-administration.blogspot.com/p/index-of-posts-available-in-this-blog.html

STEP BY STEP TO INCREASE FILE SYSTEM SIZE WHEN THE LUN IS INCREASED AT STORAGE LEVEL 

check for pv size 
 
 TESTDEV:~ # pvs
  PV         VL     Fmt  Attr PSize   PFree
  /dev/sdc   VLBOOT lvm2 a--  280.00g 125.00g
  /dev/sdd          lvm2 a--  100.00g 100.00g
  /dev/sde   VLUSR  lvm2 a--   35.00g      0
  /dev/sdf   VLORA  lvm2 a--   30.00g      0
  /dev/sdg   VLDATA lvm2 a--  800.00g      0
  /dev/sdh   VLDUMP lvm2 a--  100.00g      0
  /dev/sdi   VLUSR  lvm2 a--   26.00g      0



 RESIZE PV WITH THE HELP OF pvresize command 

TESTDEV:~ # pvresize -v /dev/sdg
    connect() failed on local socket: No such file or directory
    Internal cluster locking initialisation failed.
    WARNING: Falling back to local file-based locking.
    Volume Groups with the clustered attribute will be inaccessible.
    Using physical volume(s) on command line
    Archiving volume group "VLDATA" metadata (seqno 5).
    Resizing volume "/dev/sdg" to 1677721600 sectors.
    Resizing physical volume /dev/sdg from 0 to 332799 extents.
    Updating physical volume "/dev/sdg"
    Creating volume group backup "/etc/lvm/backup/VLDATA" (seqno 6).
  Physical volume "/dev/sdg" changed
  1 physical volume(s) resized / 0 physical volume(s) not resized

TESTDEV:~ # pvs
  PV         VL     Fmt  Attr PSize   PFree
  /dev/sdc   VLBOOT lvm2 a--  280.00g 125.00g
  /dev/sdd          lvm2 a--  100.00g 100.00g
  /dev/sde   VLUSR  lvm2 a--   35.00g      0
  /dev/sdf   VLORA  lvm2 a--   30.00g      0
  /dev/sdg   VLDATA lvm2 a--    1.27t 500.00g
  /dev/sdh   VLDUMP lvm2 a--  100.00g      0
  /dev/sdi   VLUSR  lvm2 a--   26.00g      0



EXTEND LOGICAL VOLUME SIZE


 TESTDEV:~ # lvextend -L +120G /dev/VLDATA/VLDATA1
  Extending logical volume VLDATA1 to 320.00 GiB
  Logical volume VLDATA1 successfully resized
 


RESIZE FILE SYSTEM ONLINE

TESTDEV:~ # resize2fs /dev/mapper/VLDATA-VLDATA1
resize2fs 1.41.9 (22-Aug-2009)
Filesystem at /dev/mapper/VLDATA-VLDATA1 is mounted on /oracle/TESTDEV/data1; on-line resizing required
old desc_blocks = 13, new_desc_blocks = 20
Performing an on-line resize of /dev/mapper/VLDATA-VLDATA1 to 83886080 (4k) blocks.
The filesystem on /dev/mapper/VLDATA-VLDATA1 is now 83886080 blocks long.



 

Amazon8

Total Pageviews