03-17-2017
Thanks for your reply. I tried the menthod I listed and that didn't work. Turns out, AIX set the paths to each disk, since the disk is going over iSCSI, the disk attributes has the iSCSI target name in the connection so it didn't work.
I'll seek out the EMC connectivity guide and give that a go.
Thanks.
If anyone else has done this, I'd be interested in hearing.
10 More Discussions You Might Find Interesting
1. AIX
Hi everyone,
how can I check if I have LUNs in a server and the LUNīs vpath in AiX?
thx (5 Replies)
Discussion started by: jcpetela
5 Replies
2. AIX
Hello All,
Really hoping someone can help. We have an AIX server connected to a Quantum SDLC sitting in front of an S10K library. The library has 3 logical partitions (two LTO4, one LTO3), so it requires 3 distinct medium changers. The SDLC presents the 3 luns (which are the medium... (1 Reply)
Discussion started by: jwholey
1 Replies
3. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
4. AIX
Hello Everyone,
Can someone help me to mount a SAN hdisk which contains a clone data copy(san) of the remote server to the another machine. Both servers are running in AIX.
Thanks in advance !
Regards,
Gowtham.G (3 Replies)
Discussion started by: gowthamakanthan
3 Replies
5. AIX
Hello!
I have this infraestructure:
- 1 POWER7 with single VIOS on Site A.
- 1 POWER6 with single VIOS on Site B.
- 1 LPAR called NodeA as primary node for PowerHA 6.1 on Site A.
- 1 LPAR called NodeB as secondary (cold) node for PowerHA 6.1 on SiteB.
- 1 Storage DS4700 on Site A.
- 1... (8 Replies)
Discussion started by: enzote
8 Replies
6. Solaris
Hi,
I've noticed that mpathadm states that one of our luns has no active paths:
/dev/rdsk/c6t60000970000298700009533031324333d0s2
Total Path Count: 4
Operational Path Count: 4
/dev/rdsk/c6t60000970000298700009533031333037d0s2
... (3 Replies)
Discussion started by: badoshi
3 Replies
7. AIX
Hello all!
I have not so much experience with AIX
We have test p5 server. On server was deployed VIOS + 3 LPAR + AIX6.1
There is a test HACMP cluster of two nodes, the cluster is identical to production cluster (all clusters and hosts have been configured by specialist of integrator company and... (3 Replies)
Discussion started by: Ravil Khalilov
3 Replies
8. AIX
we have an old AIX system with important data on an EMC LUN. the AIX server crashed and we had to rebuild it with the old AIX os 5.8. how do we reconnect the EMC LUN without losing the data? (15 Replies)
Discussion started by: jhudson12
15 Replies
9. Solaris
Hi
I have a server running solaris 10 in which the NetAppadmin has just presented one LUN of 200Gb, but when running:
bash-3.2# format
Searching for disks...done
c3t500A09828DE3E799d1: configured with capacity of 199.94GB
c3t500A09829DE3E799d1: configured with capacity of 199.94GB
... (5 Replies)
Discussion started by: fretagi
5 Replies
10. Post Here to Contact Site Administrators and Moderators
ssssssssssss (0 Replies)
Discussion started by: sampathenjoy
0 Replies
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