Sponsored Content
Full Discussion: Changing AIX LUN paths
Operating Systems AIX Changing AIX LUN paths Post 302994008 by rbatte1 on Friday 17th of March 2017 11:37:55 AM
Old 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

AIX vpath lun

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

AIX not detecting LUN

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 LUN ID, how to find disk relate to that LUN ID?

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

Mount a SAN LUN which contains clone copy - AIX 6.1

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

Increase LUN size in AIX with VIOS and HACMP

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

Mpathadm showing no paths to 1 lun, others luns are fine

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

Add new LUN in 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

AIX help -reconnect EMC lun

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

How to avoid seeing various paths to just one LUN?

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

AIX server do not detect LUN from HP storage

ssssssssssss (0 Replies)
Discussion started by: sampathenjoy
0 Replies
iobind(1M)																iobind(1M)

NAME
iobind - bind a driver to a device SYNOPSIS
instance] DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it. As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware paths. The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The optional forces the binding to occur at the next reboot if it cannot be done online. The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The user is given the option to proceed or not. If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown by the command: The specified driver was successfully bound to the hardware path. The specified driver cannot be used to claim the hardware at the specified hardware path. The device at the address is responding, but it is in an error state. The device at the specified hardware path is no longer responding. The specified hardware path is locked. Try again later. The driver failed. Options recognizes the following options: Force the binding even though a driver does not support online unbinding and binding or the device is in use. In this case, the binding will take effect at the next reboot. The LUN hardware path of a device must be of the form 64000/0x/0x. The instance number to be assigned to the device. The name of the driver that the LUN and legacy hardware paths are to be bound to. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class. Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot. WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If this happens, must be executed again to bind the desired driver. may be executed only by the superuser. SEE ALSO
ioscan(1M), intro(7). iobind(1M)
All times are GMT -4. The time now is 01:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy