03-17-2017
The LUN that AIX recognises will be based on the serial number it is presented with. I no longer have AIX available, but I think you can see it in the Z00 or Z01 line in lscfg -vl hdisk7 or whatever.
You should be able to add the new links in from the SAN and get wider output from lsvpcfg
If you can, then you can delete the old hdisks and remove the old SAN definitions. This way, you don't need to take them offline.
Obviously, don't start removing things until you are certian that the new hdisks (discovered with cfgmgr -S) are merged into the existing vpaths.
Make sure that you remove the old hdisks before you try to remove the LUN at the SAN end or you will get lots of hardware failure messages.
I hope that this helps.
Robin
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 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