Adding disks to a Data ONTAP 8.1.1 Simulator

by New Contributor on ‎2012-06-27 08:37 AM

Instructions for adding disks to a Data ONTAP 8.1.1 Simulator


Background

Data ONTAP 8 provides a user mode system shell for rare diagnostic tasks. While most of the CPU cycles are spent in various Data ONTAP kernel modules, a user space exists and is used to run some processes and for diagnostics. The simulator takes advantage of this user space to implement simulated disks. These disks are kept as files in a special directory. The default simulator comes with 28 simulated disks of 1GB each.  It is possible to increase the simulated disk count to a maximum of 56 simulated disks. The following procedures will provide step-by-step instructions for doubling the disk count to 56 disks and making the disks available for use.

During these procedures we will unlock the diagnostic user account to gain access to the system shell, use the diag account to create the new simulated disks, and then reboot the simulator to have the new disks recognized.  The high-level process is same for both 7-Mode and Cluster-Mode, but the command syntax differs.  You can perform the procedure either through the console or through SSH.

Adding Disks to a 7-Mode Simulator

These are the steps for adding disks to a 7-Mode simulator.

1. Unlock the diag user and assign it a password:

       > priv set advanced
       *> useradmin diaguser unlock
       *> useradmin diaguser password

       Please enter a new password: <password>

       Please enter it again: <password>


2. Log in to the system shell using the diag user account:

       *> systemshell
       login: diag
       password: <password>

3. Add the directory with the simulator disk tools to the path:

       % setenv PATH "${PATH}:/usr/sbin"
       % echo $PATH

4. Go to the simulated devices directory:

       % cd /sim/dev
      
% ls ,disks/

At this point you will see a number of files which represent the simulated disks.  Notice that these files start with "v0." and "v1.". That means the disk are attached to adapters 0 and 1, and if you count the disk files you'll  see that there are 14 of them on each adapter. This is similar to the DS14 shelf topology with each shelf attached to its own adapter.

5. Add two more sets of 14 disks to the currently unused adapters 2 and 3:

       % vsim_makedisks -h
      
% sudo vsim_makedisks -n 14 -t 23 -a 2
      
% sudo vsim_makedisks -n 14 -t 23 -a 3
      
% ls ,disks/

The first invocation of the command prints usage information. The remaining two commands tell the simulated disk creation tool to create 14 additional disk ("-n 14") of type 23 ("-t 23") on adapters 2 and 3 (e.g., "-a 2"). As you can see from the output of vsim_makedisks -h, type 23 disks are 1GB disks. You can add a different size and type of disk using the number that corresponds to the disk type.  Note that Data ONTAP 8.1.1 supports simulated disks up to 9GB (type 36 and 37), but make sure you have the space to add such large disks.

6. Now we're done with the system shell. We need to reverse some of the earlier steps and reboot the simulator so that it sees the new disks:

       % exit
       *> useradmin diaguser lock
       *> priv set admin
       > reboot

7. After the reboot complete, log back in and take ownership of all the new disks:

       > disk show -n
      
> disk assign all
      
> disk show -v

You should now see 56 disks of 1GB each listed in the simulator. The new disks should be listed as already zeroed and ready to use inside an aggregate.


Adding Disks to a Cluster-Mode Simulator

These are the steps for adding disks to a single Cluster-Mode simulator.  For a system with multiple nodes, you will need to perform this sequence for each node.

1. Unlock the "diag" user and assign it a password:

       > security login unlock -username diag
       > security login password -username diag

       Please enter a new password: <password>

       Please enter it again: <password>

2. Log in to the system shell using the diag user account:

       > set -privilege advanced
       *> systemshell local
       login: diag
       password: <password>

3. Add the directory with the simulator disk tools to the path:

       % setenv PATH "${PATH}:/usr/sbin"
       % echo $PATH

4. Go to the simulated devices directory:

       % cd /sim/dev
       % ls ,disks/

At this point you will see a number of files which represent the simulated disks.  Notice that these files start with "v0." and "v1.". That means the disk are attached to adapters 0 and 1, and if you count the disk files you'll see that there are 14 of them on each adapter. This is similar to the DS14 shelf topology with each shelf attached to its own adapter.

5. Add two more sets of 14 disks to the currently unused adapters 2 and 3:

       % vsim_makedisks -h
       % sudo
vsim_makedisks -n 14 -t 23 -a 2
       % sudo
vsim_makedisks -n 14 -t 23 -a 3
       % ls ,disks/

The first invocation of the command prints usage information. The remaining two commands tell the simulated disk creation tool to create 14 additional disk ("-n 14") of type 23 ("-t 23") on adapters 2 and 3 (e.g., "-a 2"). As you can see from the output of vsim_makedisks -h, type 23 disks are 1GB disks. You can add a different size and type of disk using the number that corresponds to the disk type.  Note that Data ONTAP 8.1.1 supports simulated disks up to 9GB (type 36 and 37), but make sure you have the space to add such large disks.

6. Now we're done with the system shell. We need to reverse some of  the earlier steps and reboot the simulator so that it sees the new disks:

       % exit
      
*> security login lock -username diag
       *> system node reboot local

       Warning: Are you sure you want to reboot the node? {y|n}: y

7. After the reboot completes, log back in and take ownership of all the disks.The example below is for a brand new system where all but disks in the root aggregate are currently unowned.

Substitute the name of the node for <nodename> in the commands below:

       > storage disk show
      
> storage disk modify -disk <nodename>:v4.* -owner <nodename>

       14 entries were modified.
       > storage disk modify -disk <nodename>:v5.* -owner <nodename>
       14 entries were modified.

       > storage disk modify -disk <nodename>:v6.* -owner <nodename>
       14 entries were modified.

       > storage disk modify -disk <nodename>:v7.* -owner <nodename>
       14 entries were modified.

       > storage disk show

You should now see 56 disks of 1GB each listed in the simulator. The disks should be listed as already zeroed and ready to use inside an aggregate.

Comments

Thanks, I've always wondered if I could do this!

Is there any way to remove disks from simulator after they have been added?

New Contributor

Yes, you can remove a disk.

1. Remove the simulated disk from Data ONTAP by entering the command "disk simpull <disk_name>".  For example:

        user-vsim1> disk simpull v5.32

2. Delete the disk file from the FreeBSD directory “/sim/dev/,disks/”.

  a. Follow the steps to log into the system shell using the diag user account.

  b. From "/sim/dev" enter "ls ,disks/,pulled/" to view all the disks that have been pulled. For example:

        % ls ,disks/,pulled/

         v1.32:NETAPP__:VD-1000MB-FZ-520:14143313:2104448

  c. To remove the disk file that corresponds to Data ONTAP disk "v5.32", subtract "4" from the first number; so that would be

      "v1.32....".  That is the disk file you need to delete. For example:

         % sudo rm ,disks/,pulled/v1.32:NETAPP__:VD-1000MB-FZ-520:14143313:2104448

3. Follow the steps to return to the Data ONTAP prompt.

Thanks!

Very good.. thank you!

Is this the same simpull command in cluster mode? I will try later to see if an equivalent command.

New Contributor

Something like "run -node {nodename} disk simpull" or "system node run -node {nodename} disk simpull".

Very good. Same command to the dblade. Makes sense. Thank you.

Sent from my iPhone 4S

vinith Former NetApp Employee

Hello, Thanks for the share, do you know how we can add the same in C-mode Simulator? Adding disks to a C-mode Simulator?

New Contributor

This document has a section for 7-Mode and for C-Mode already.  Please take a look at the 2nd part of the document for C-Mode instructions.

vinith Former NetApp Employee

Hello,

I have a C-mode Vsim running on Vmware, i need to enable the 4th disk shelf which shows 250GB disk, can you let me know how to do that?

enablediskshelf.png

New Contributor

I don't know how to help out with that.  Hopefully someone else can help you.

By the way, the Simulate ONTAP manuals says "Each simulated drive is limited to 9 GB.  The simulator image comes pre-configured with 28 1 GB disks; 14 each on simulated disk shelves 0 and 1. Simulated disk shelves 2 and 3 are not populated. You can configure up to a maximum of 220 GB total space for each Simulate ONTAP node.". So I don't know whether this 250 GB disk you are asking about will cause an issue.

Tom

There's no "4th disk shelf". That VMDK is where all your disks are kept. BTW this is on the 8.2 simulator (Maybe the 8.1.3? not sure..). Prior to the simulator shipping with a larger VMDK, you had to do all sorts of steps to expand the VMDK first before you could add larger disks. (The 8.1 simulator for 7 mode only has 47GB).

Basically you have 250GB to play with. The simulator ships with 32 1 GB disks (so 32GB is used, leaving 218GB ). You can add a maximum of 32 more disks, up to a total size of 218. If you add 16 9GB disks on shelf 3, then you're down to 74GB. Keep in mind that there is some overhead in that VMDK, so I wouldn't try to max it out.

Hi all I want to add disks on DOT 8.2 simulator type 23 is 1 GB capacity but we can use 9 GB capacity, what is the disk type to use ?

Thanks bro

in cDOT 8.3 Simulater

must use "set -privilege diagnostic"

 

in cDOT 8.3 Simulator

to assign the drives, i had to enter

storage disk assign -disk <drive name> (ie NET-1.13) -owner <node-name>

shatfield

or:

run * disk assign all

 

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.