08-28-2009
Quote:
Originally Posted by
DukeNuke2
Am using the most recent driver for the iSCSI adapters and they are fine, otherwise I wouldn't be able bind to the iSCSI targets on the SAN.
The part of the manual you posted basically applies when using iSCSI over the regular NICs. The scenario as described doesn't really apply in my case. E.g. IPMP is no option in my case since the NIC is integrated on the adapter and kinda behind the controller on the same adapter. Therefor the IP configured on the adapter will not show when using "ifconfig -a"
The only thing I consider possible is using the wrong symmetric option in the scsi_vhci.conf file.
In case you wonder why using this specific adapter. It wasn't my choice. The system is from one of our customers who asked us to help them out.
10 More Discussions You Might Find Interesting
1. Solaris
hi,
I have installed Solaris 10 10/08 on sparc machine. I would like to configure iSCSI on that to mount SAN Volumes. Is there any need to install any additional patches for iSCSI to work.
Thanks,
Prashant. (4 Replies)
Discussion started by: prashantbhushan
4 Replies
2. Solaris
Hello!
I have several disks discovered using iscsi protocol.
There disks are represented in OS like c2txd0 .
logs:
Is it possible to change drive path, for example, from c2t6d0 to c2t7d0?
It's important for me because I have to install oracle RAC on RAW devices.
NIck (0 Replies)
Discussion started by: skelet
0 Replies
3. UNIX for Advanced & Expert Users
I am running Solaris 10 on a V490. I have Dell EqualLogic SAN attached.
I would like to take full advantage of the iSCSI initiator.
I have a primary network interface and IP addresses for all four SAN ports. Since the four ports are SUN GigaSwift (legacy), I cannot utilize dladm, so I downloaded... (2 Replies)
Discussion started by: KSFlyer
2 Replies
4. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
5. Solaris
I have been running some tests with solaris mpxio, dual-pathed to HDS SAN storage.
When I take a path offline, Solaris recognised this and a path is shown as offline in luxadm display <device>. However, it does not recover on reinstatement of the path until I run cfgadm -al.
Any ideas?
Phil (3 Replies)
Discussion started by: UKPhil
3 Replies
6. Solaris
Im not able to turn the multipath off on the solaris s10 X86...since im on FC boot..
if i disable multipath , from /kernel/drv/iscsi.conf then im not able to boot the machine.:wall:
Is there any other go or any suggestions . (2 Replies)
Discussion started by: gowtham.varma
2 Replies
7. Solaris
Hi,
I have an Oracle/Sun T3-2 Server with a duel SAS controller Fujitsu DX60 array attached.
I have 2 x SAS HBA's in the T3-2. One HBA cabled to CM0 and one HBA cabled to CM1 of the array.
The array is setup with one RAID GROUP and one VOLUME and one LUN
In Solaris I can see one device... (4 Replies)
Discussion started by: general_lee
4 Replies
8. Solaris
hi to all
i've done that steps, but i was not completely successful:
sudo pkg install group/feature/storage-server
sudo svcadm enable stmf
sudo zfs create -V 1g rpool/LUN1
sudo stmfadm create-lu /dev/zvol/rdsk/rpool/LUN1
sudo stmfadm list-lu ... (4 Replies)
Discussion started by: jm83
4 Replies
9. Solaris
Hi Community,
I am facing one issue related storage accessing from solaris 10 machine(M5000). it was working fine then we shifted to another site. the only change on that site is FC switch.
The issue i am facing is from solaris machine i can able to see the LUN, it;s only a test lun of 30... (17 Replies)
Discussion started by: bentech4u
17 Replies
10. Solaris
Hi Community,
i have one issue with 10 fiber ethernet adapter.
here is my details:
root@new-bpel.example.com #dladm show-dev
bge0 link: unknown speed: 0 Mbps duplex: unknown
bge1 link: up speed: 1000 Mbps duplex: full
qlge2 link:... (4 Replies)
Discussion started by: bentech4u
4 Replies
LEARN ABOUT NETBSD
libiscsi
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