Ok this might sound to be a silly task, but when you need to perform it, you might get frustrated. Actually several times we had to move or reassign disks to a different node/filer in our IBM Nseries Cluster. If you are not aware of the IBM Nseries then all I need to tell you its a Netapp box oemed as IBM. So again this post apply to N-Series as well Netapp clustered filers.
You might want to reassign a disk to a different N-Series Controller or Netapp filler what ever your vendor want to call it as long its running a data Ontap then the procedure is the same. When I first thought of this, I thought it will be something like disk unassign on the filler to remove the disk from. Then assign it on the other filer. Though it seems no command disk unassign is there. Trying all around the place then calling the IBM support we figured out the following is what need to be done.
On the filer or the gateway to remove the disk or the LUNs from run the below command:
disk remove -w <Disk Name>
Then on the filer or the gateway to add the disk or the LUN to run the below command:
Disk Assign <disk name>
Ah I hope this help some one avoid having too look for so long for how to do this tedius task
.
Please leave a comment if this work for you, as we like to hear your success stories or let us know if for some reason it did not work with the certain model or Ontap version you are running.
Subscribe RSS 2.0 feed. Leave a response, or Trackback from your own site.
Best Deal Ads :
4 Responses to 'Netapp / Nseries How to assign disks to a different filer in a cluster'
Leave a Reply
- Blades (2)
- IBM Blades (2)
- EMC (1)
- VPLEX (1)
- How to (1)
- Management Software (4)
- Problem resolutions (0)
- Storage (18)
- Tips & Tricks (7)
- Tivoli (22)
- FlashCopy Manager (19)
- TSM (3)
- TSM 6.1.x.x (2)
- Tutorials (11)
- VMware (4)
- admin: As long both of them reside on the DS8000 it should be possible to acheive
- HAMAYUN ALI SHAH: HELLO I want to copy/backup DS8000′s volumes on a Windows Server 2003 machine, and not from...
- Kamesh: Really Useful!!!
- Shaamil Thorne: Hi There, Do you perhaps know how to do this on a DS4000/5000 storage subsystem. Using a Windows...
- joe: a 30 Days testversion can be downloaded from the IBM FTP Server. Note that the files will only be released there...
- IBM Tivoli Storage Manager Guru Blog: TSM
- How to Videos: Install IBM Systems Director 6 Common Agent on AIX | How to Install IBM Systems Director 6 Common...
- 8.3. Microsoft vShadow Transaction Consistent Database Cloning to a different server: Back to: IBM Tivoli Storage...
- 8.2. IBM TFCM Transaction Consistent Database Cloning to the same server: Back to: IBM Tivoli Storage FlashCopy...
- 8.1. IBM DS8000 Boot from SAN Operating System Cloning: Back to: IBM Tivoli Storage FlashCopy Manager Tutorial Index
- VMware ThinAPP Antivirus Best Practices
- IT Solutions LIVE WEBINARs Page
- New StarWind iSCSI SAN v5.8 and Hyper Backup Plug-in are a New Level of Data Protection
- IBM XIV, IBM SVC, IBM Storwize V7000 support VAAI is here & DS8000 is on the way
- The first VMware vSphere Metro Storage Cluster (vMSC) Supported with EMC VPLEX
- HP Storage P4000 Virtual Storage Appliance installation on vSphere 5
- Why Use IBM Tivoli Storage Manager?
- Format Completed with Return Code 499
- How do you remove a server instance without uninstalling the TSM server?
- IBM 000-206 High-End Disk Solutions for Open Systems Version 1






This didn’t work for me. In fact, it marked the disk as “failed” when I ran the “disk assign” part.
I recovered from that by going into Advanced mode (priv set advanced) and then using “disk unfail “.
From there, to unassign the disk, I used “disk remove_ownership “. Then I went back to normal mode with “priv set admin”.
Thanks for your feed back. It would be nice if you could supply your Data ontap version. As that command had perfectly worked for me on Data Ontap 7.2.3. We are upgrading soon to 7.2.6.1. I will update this post, when I get to try this command on new release.
To remove drive assignment in Data OnTap use:
To unassign:
disk assign 0b.30 0b.29 0b.28 0b.27 -s unowned -f
Run that for whatever disks you are trying to remove assignment for (do it from the head that currently owns the disk).
Many thanks N Lyne, that worked a treat for me on an IBM N6040, I had to also issue the command “options disk.auto_assign off” as they were re-aquired by the same controller before I got chance to assign them to he other one … whoops. Thanks again.