12-18-2008
It should be off by changing mpxio-disable to yes for iSCSI. It's set in /kernel/drv/iscsi.conf
10 More Discussions You Might Find Interesting
1. IP Networking
I've setup Solaris IP Multipathing under Solaris whenever the hardware to do so was available. I find it amazing though that so few places I've worked at don't use it until I arrive. I wanted to find out if I'm running into all the exceptions, or is it really not being used? ... (3 Replies)
Discussion started by: kduffin
3 Replies
2. Solaris
All -
would you please some one help me to disable telnet on Solaris?
/etc/inetd.conf
Thanks :confused: (11 Replies)
Discussion started by: March_2007
11 Replies
3. Solaris
I have solaris 10 sparc. I installed a Qlogic hba card.
This card is connected on a brocade switch and the brocade is connected on 2 different controllers on a Hitachi disk bay.
I formated 2 luns. On my solaris system, i have 4 disk.
How to configure solaris 10 to fix the dual disk view.
... (4 Replies)
Discussion started by: simquest
4 Replies
4. Solaris
Hello All,
I work for a Health care company at a local trauma hospital. I maintain a Picture Archiving and Communication System (PAC's). Basically, any medical images (X-Ray, CT, MRI, Mammo, etc) are stored digitally on the servers for viewing and dictation from diagnostic stations. I took over... (10 Replies)
Discussion started by: mainegeek
10 Replies
5. Solaris
Hi,
I saw your post on the forums about how to setup IP multipathing. I wanted your help on the below situation .
I have 2 servers A and B . Now they should be connected to 2 network switches . S1 and S2.
Now is it possible to have IP Multipathing on each of the servers as follows ?
... (0 Replies)
Discussion started by: maadhuu
0 Replies
6. Solaris
Hai
we using emc storage which is conneted to M5000 through san switch.
we asign 13 luns but in server it is showing 22 luns.
i enable the solaris multipathing (MPxIO)
#more /kernel/drv/fp.conf in that file
MPxio-disable=no
#mpathadm list lu
it shows ... (2 Replies)
Discussion started by: joshmani
2 Replies
7. Solaris
Hi
Is there anyway to disable all logs/logging (lastlog, sulog, messages etc.) in Solaris 9&10? I know this is not recommended but i just want to know if this is possible.
TIA
Reddy (8 Replies)
Discussion started by: reddyr
8 Replies
8. Solaris
I've new installed Solaris 11 on Sparc T4-1.
I'd like to disable IPv6 but with no luck.
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
net0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 2
inet... (6 Replies)
Discussion started by: samer.odeh
6 Replies
9. Solaris
hi,
just installed solaris 11.1 (11.1.9.5.1) on a sun7410 ZFSSA (x4440 + j4400), but when I enable multipathing with "stmsboot -e", only the 1TB SATA drives inside the j4400 are configured as multipathed vhci / mpxio devices, but the logzillas / ZeusIOPS drives are skipped. the server is... (0 Replies)
Discussion started by: pressy
0 Replies
10. Solaris
hello all
i have an issue about a solaris V440 cpu, im logged in the Ok prompt i can't disable a CPU3, i can't see it in dev list, i see only the cpu3-bank0 to cpu-bank4
please help me to disable it
thank youuu (3 Replies)
Discussion started by: walidadam
3 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