1) AIX Supports iSCSI. If FreeNAS utilizes the iSCSI protocol, than it can be used.
2) see first answer
3) check your system to see if the iscsi drivers are installed, if they are not you can install them from CD or download them from IBM's website.
I have a standard template I deploy for each of my AIX servers. It's in a mksysb format which I pulled via the nim server after I originally set it up.
I'm trying to restore this mksysb over the wire to a remote system. The remote system is an lpar running under vio (no HMC attached). The disk... (1 Reply)
Can you have a Dynamic LPAR without VIO and if yes is there a benefit to having both? I am attempting to implement VIO and Resource pooling at my company and want to understand the limitations.
Also, I have been told the managing and allocation of the Logical Volumes is a time consuming task as... (0 Replies)
We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
VIO Server is managing both AIX Clients and Linux Clients. For AIX Clients, we could do a disk mapping from slot numbers to VIO and also uname -L to determine the lparid and serial number frame its running on.
From a Linux Client,
How do I know which IBM frame its running on? Any command to... (4 Replies)
I am wondering if there is a command I can run from **with-in** LPAR server (server01) to find out the hostname or IP address or other parameters for VIO server in charge of server01? (1 Reply)
Just a question which may seem dumb to some out there, but then again I am not a super technie so that's my excuse.
Is it possible to say provision a test AIX LPAR (has a 10gb boot lun and 20gb data) under a VIO which has connectivity to SAN Array A so it can see the disks provisioned to it,... (2 Replies)
Previous forum threads have noted that AIX cannot use iSCSI disks because it fails when trying to add them to a volume group using mkvg. The failure is caused by AIX's use of the SCSI "WRITE AND VERIFY"(0x2e) command which some iSCSI targets do not support.
We experienced the same problem using... (1 Reply)
Hi All,
I've been trying to create a new LPAR for some days now but I can't get the VIO server to recognize the new LPAR. This is what I did:
On HMC create new LPAR
On HMC create new virtual scsi adapter for LPAR in VIO profile
On HMC add new virtual scsi adapter for LPAR with DLPAR... (6 Replies)
I am using Windows Server 2008R2 as a domain controller to 2 other servers and would like to use my Dell Powervault 770N as my NAS for data storage. I have FC that I would like to implement between the servers and the NAS (as an iSCSI target). I am brand new to this world; is this possible? I am... (2 Replies)
:wall::wall::wall:
1. I have created an LPAR in the HMC.
2. I have allocated the storage from an Hitachi AMS2500 and assigned it to the host group.
3. I have zoned the LPAR and Storage on a Brocade 5100. (The zone sees the AMS)
Next I activated the LPAR in the HMC, SMS mode for the mksysb... (3 Replies)
Discussion started by: Dallasguy7
3 Replies
LEARN ABOUT NETBSD
iscsi-target
ISCSI-TARGET(8) BSD System Manager's Manual ISCSI-TARGET(8)NAME
iscsi-target -- service remote iSCSI requests
SYNOPSIS
iscsi-target [-46DV] [-b block length] [-f configuration file] [-p port number] [-s maximum number of sessions] [-t target name]
[-v verbose arg]
DESCRIPTION
iscsi-target is the server for iSCSI requests from iSCSI initiators. iscsi-target listens for discovery and login requests on the required
port, and responds to those requests appropriately.
Options and operands available for iscsi-target:
-4 iscsi-target will listen for IPv4 connections, and respond back using IPv4. This is the default address family.
-6 iscsi-target will listen for IPv6 connections, and respond back using IPv6.
-b blocksize
Specify the underlying block size for iSCSI storage which will be served. The possible sizes are: 512, 1024, 2048, and 4096 bytes,
with the default being 512 bytes.
-D When this option is specified, iscsi-target will not detach itself from the controlling tty, and will not become a daemon. This can
be useful for debugging purposes.
-f configfile
Use the named file as the configuration file. The default file can be found in /etc/iscsi/targets. See targets(5) for more informa-
tion.
-p port number
Use the port number provided as the argument as the port on which to listen for iSCSI service requests from initiators.
-s maximum number of sessions
Allow the maximum number of sessions to be initiated when connecting to the target.
-t filename
The target name (as it appears to the iSCSI initiator) can be specified using this flag.
-V iscsi-target will print the utility name and version number, and the address for bug reports, and then exit.
-v argument
The amount of information shown can be varied by using this command. Possible values of argument are net to show network-related
information, iscsi to show iSCSI protocol-related information, scsi to show SCSI protocol information, and all to show information
from all of the above arguments.
FILES
/etc/iscsi/targets the list of exported storage
/var/run/iscsi-target.pid the PID of the currently running iscsi-target
SEE ALSO targets(5)HISTORY
The iscsi-target utility first appeared in NetBSD 4.0.
BSD May 27, 2006 BSD