Netapp iscsi lun Post: 302784041

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 FREEBSD

iscsi

ISCSI(4)						   BSD Kernel Interfaces Manual 						  ISCSI(4)

NAME

     iscsi -- iSCSI initiator

SYNOPSIS

     To compile this driver into the kernel, place the following line in the kernel configuration file:

	   device iscsi

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   iscsi_load="YES"

DESCRIPTION

     The iscsi subsystem provides the kernel component of an iSCSI initiator.  The initiator is the iSCSI client, which connects to an iSCSI tar-
     get, providing local access to a remote block device.  The userland component is provided by iscsid(8) and both the kernel and userland are
     configured using iscsictl(8).  The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol.

SYSCTL VARIABLES

     The following variables are available as both sysctl(8) variables and loader(8) tunables:

     kern.iscsi.ping_timeout
	     The number of seconds to wait for the target to respond to a NOP-Out PDU.	In the event that there is no response within that time
	     the session gets forcibly restarted.

     kern.iscsi.iscsid_timeout
	     The number of seconds to wait for ctld(8) to establish a session.	After that time iscsi will abort and retry.

     kern.iscsi.login_timeout
	     The number of seconds to wait for a login attempt to succeed.  After that time iscsi will abort and retry.

     kern.iscsi.maxtags
	     The maximum number of outstanding IO requests.

     kern.iscsi.fail_on_disconnection
	     Controls the behavior after an iSCSI connection has been dropped due to network problems.	When set to 1, a dropped connection causes
	     the iSCSI device nodes to be destroyed.  After reconnecting, they will be created again.  By default, the device nodes are left
	     intact.  While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished.

SEE ALSO

     iscsi.conf(5), iscsictl(8), iscsid(8)

HISTORY

     The iscsi subsystem first appeared in FreeBSD 10.0.

AUTHORS

     The iscsi subsystem was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation.

BSD
								September 11, 2014							       BSD