Netapp iscsi lun Post: 302776099

10 More Discussions You Might Find Interesting

1. Solaris

Netapp filer LUN Resize. Commands to run on Solaris afterwards.

Hi, I need to increase a veritas filesystem I have currently mounted on a Solaris 10 server. We can resize the LUN on the NetApp filer no problem. What I need to know is what do I do next on the Solaris 10 server I have so that it will see the increase in size. Do I run 'devfsadm' to...

2. Solaris

Can't see Netapp LUN on Solaris using LPFC after reboot.

Hi, I've just edited this post. I found the solution for this. Thanks.

3. AIX

Help growing iscsi lun

Hi, I have an iSCSI LUN of 200GB. I increased it to 250GB and when I try to increase the size of the vg, I'm getting an error that none of the volumes have increased in size. How can I get the OS to see the additional 50GB? ---------- Post updated at 03:22 PM ---------- Previous update...

4. Solaris

Set up iscsi LUN on solaris 9?

Hi, I need to set up iscsi LUN on Solaris 9. I've done it on Solaris 10 with iscsiadm. How do you do it on Solaris 9 though? Currently using Solaris 9 update 2. Your help is appreciated. Thanks, Sparcman

5. Solaris

Solaris10 -> iscsi -> equiliogic lun

We "lose" the iscsi device after a reboot - i.e., it appears in /dev/rdsk and /dev/dsk but format cannot find it. Obviously, it won't mount either. This happens for two separately defined luns. We must be missing a step in iscsiadm. The luns are defined as targets, we can see them in...

6. AIX

Any tips to grow iSCSI LUN

Hi, I have an iSCSI LUN attached to an AIX 5.3 box. It's initial size is 250GB, I just grew it on the SAN to 300GB, but AIX is not seeing the change. Right now I have some processes going and it's eating up the disk space. I need to grow this lun by atleast 30GB otherwise the process with bomb...

7. Red Hat

DM multipath :iscsi lun shows by diff names on two server where its exported

Hi, I am trying to setup multipathing (using DM multipath) for a redhat cluster setup ...all setup is done but issue is : node 1 shows the shared iscsi lun as sdc node 2 shows the same as sdg (changes on reboots) Due to this (i guess) i get i/o error & i can not read files created by...

8. Solaris

Make an iSCSI LUN clone bootable

trying to do this for a DR situation. I've cloned an iSCSI LUN to another server. I've created an LDOM on it. set the LDOM to auto-boot=false and exported the LUN as a raw disk to the new LDOM. After starting the LDOM and telnetting to it. I can get to the OK prompt and see the disk but when I try...

9. Solaris

Restore of Netapp FC lun targets used as the disks for a zpool with exported zfs file systems

So, We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the...

10. Linux

Identify newly attached LUN from NetApp

Hi I need to identify a newly attached LUN from NetApp on a linuxserver running uname -o GNU/Linux I have first run the df -h and got the following: df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_outsystemdb-lv_root 50G 2.7G 45G ...

LEARN ABOUT SUSE

tgt-admin

TGT-ADMIN(8)						      TGT Configuration Tool						      TGT-ADMIN(8)

NAME

       tgt-admin - Linux SCSI Target Configuration Tool.

SYNOPSIS

       tgt-admin -[OPTION]...

DESCRIPTION

       tgt-admin is a utility which allows a persistent configuration of targets and luns.
       It uses tgtadm commands to create, delete and show targets.

OPTIONS

       -e, --execute

       read /etc/tgt/targets.conf and execute tgtadm commands.
       if target already exists it will be deleted and a new instance will be created with the new parameters instead.

       -d, --delete

       delete all the targets

       -s, --show

       show all the targets

       -f, --force

       don't exit on tgtadm errors

       -p, --pretend

       only print tgtadm options

       -v, --verbose

       increase verbosity (no effect in "pretend" mode)

       -c, --conf <conf_file>

       specify an alternative configuration file instead of /etc/tgt/target.conf, which is the default.

       -h, --help

       display a list of available options and exits

CONFIGURATION FILE SYNTAX

       The defualt configuration file is: /etc/tgt/target.conf. It defines all the targets and their properties.
       The  configuration  file is in XML format and uses tags.  Configuration file contains several target blocks, where each block contains tar-
       get's proerties such as storage devices, initator ACL and authorization information. You can include other config files using:
       include /etc/tgt/xen/*.conf.

       There are 2 types of storage devices:

       backing-store - defines a virtual device on the target.

       direct-store  - defines a direct mapped device with the same properties as the physical device (such as VENDOR_ID , SERIAL_NUM, etc.)

       initiator-address - allows connections only from the specify IP address. defaults to ALL if no "initiator-address" is specified

       incominguser - define iscsi incoming authentication setting. if no "incominguser" is specified, it is not used.

       outgoinguser - define iscsi outgoing authentication setting. if no "outgoinguser" is specified, it is not used.

       example for a configuration file:
       <target iqn.2007-04.com.example:san.monitoring>
	  backing-store /dev/san/monitoring

	  # if no "incominguser" is specified, it is not used
	  incominguser backup secretpass12

	  # defaults to ALL if no "initiator-address" is specified
	  initiator-address 192.168.1.2 </target>

       <target iqn.2007-02.com.example:san.xen1>
	  backing-store /dev/san/xen1-disk1 # LUN1
	  direct-store /dev/san/xen1-disk2 # LUN2

	  initiator-address 192.168.1.2     # Allowed IP
	  initiator-address 192.168.5.6     # Allowed IP

	  incominguser user1 secretpass12
	  incominguser user2 secretpass23

	  outgoinguser userA secretpassA </target>

       <target iqn.2007-02.com.example:san.xen2>
	  backing-store /dev/san/xen2 </target>

       <target iqn.2007-06.com.example:san.vmware1>
	  backing-store /dev/san/vmware1 </target>

FILES

       /etc/tgt/target.conf
	      Configuration file for tgt-admin.

SEE ALSO

       tgtadm(8)

REPORTING BUGS

       Report bugs to <stgt-devel@lists.berlios.de>

TGT Configuration Tool						    2008-07-21							      TGT-ADMIN(8)