Sponsored Content
Full Discussion: Netapp iscsi lun
Operating Systems AIX Netapp iscsi lun Post 302784041 by Padow on Thursday 21st of March 2013 11:10:01 AM
Old 03-21-2013
have you reviewed the NetApp documentation on now.netapp.com? Have you downloaded and installed the Host Attach Kit?
Padow
 

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... (3 Replies)
Discussion started by: gwhelan
3 Replies

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. (0 Replies)
Discussion started by: gwhelan
0 Replies

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... (9 Replies)
Discussion started by: bbbngowc
9 Replies

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 (6 Replies)
Discussion started by: sparcman
6 Replies

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... (2 Replies)
Discussion started by: jim mcnamara
2 Replies

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... (5 Replies)
Discussion started by: bbbngowc
5 Replies

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... (0 Replies)
Discussion started by: heman96
0 Replies

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... (2 Replies)
Discussion started by: os2mac
2 Replies

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... (4 Replies)
Discussion started by: os2mac
4 Replies

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 ... (3 Replies)
Discussion started by: fretagi
3 Replies
LIBISCSI(3)						   BSD Library Functions Manual 					       LIBISCSI(3)

NAME
libiscsi -- iSCSI network storage protocol implementation LIBRARY
iSCSI protocol library (libiscsi, -liscsi) SYNOPSIS
#include <iscsi.h> int iscsi_target_set_defaults(iscsi_target_t *target); int iscsi_target_start(iscsi_target_t *target); int iscsi_target_listen(iscsi_target_t *target); int iscsi_target_shutdown(iscsi_target_t *target); void iscsi_target_write_pidfile(const char *filename); int iscsi_target_setvar(iscsi_target_t *target, const char *name, const char *value); char * iscsi_target_getvar(iscsi_target_t *target, const char *name); int iscsi_initiator_set_defaults(iscsi_initiator_t *initiator); int iscsi_initiator_start(iscsi_initiator_t *initiator); int iscsi_initiator_discover(iscsi_initiator_t *initiator, char *x, uint64_t a, int b); int iscsi_initiator_shutdown(iscsi_initiator_t *initiator); int iscsi_initiator_setvar(iscsi_initiator_t *initiator, const char *name, const char *value); char * iscsi_initiator_getvar(iscsi_initiator_t *initiator, const char *name); DESCRIPTION
libiscsi is a library interface to the iSCSI target and initiator. This conforms to IETF RFC 3720. The corresponding command line utilities for libiscsi are iscsi-initiator(8) and iscsi-target(8). In normal operation, a process acting as a target (i.e. presenting storage to the network) will call iscsi_target_set_defaults() and will then set various values using the iscsi_target_setvar() function. The value of a variable can be retrieved at any time using the iscsi_target_getvar() function. When all of the variables have been set, the iscsi_target_start() function is called, and the block storage will be served up by the process. A useful illustration of the use of these functions can be found in the source code to the iscsi-target(8) utility. The libiscsi library also provides an implementation of the client end of the iSCSI subsystem, which is known as the initiator. The process acting as an initiator will first call the iscsi_initiator_set_defaults() function, to set default values for the initiator variables. Once all the values have been set to the user preferences using the iscsi_initiator_setvar() function, then the iscsi_initiator_start() function is called. The libiscsi library can be used to perform iSCSI device discovery by calling the iscsi_initiator_discovery() function. This will return a list of all the iSCSI targets which are serving up block storage according to the variables which have already been set. SEE ALSO
iscsi-initiator(8), iscsi-target(8) HISTORY
The libiscsi library first appeared in NetBSD 4.0. This programmatic interface to the iSCSI subsystem first appeared in NetBSD 6.0. AUTHORS
Alistair Crooks <agc@NetBSD.org>. BSD
February 19, 2011 BSD
All times are GMT -4. The time now is 05:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy