Home > DataONTAP, NetApp, Simulator > Installing & Maximising the NetApp ONTAP 8.1 Simulator

Installing & Maximising the NetApp ONTAP 8.1 Simulator

January 4th, 2012


UPDATE 7 September 2012:  NetApp has released its Virtual Storage Appliance, Data ONTAP Edge which is a licensed functional VSA.

One of the strengths of NetApp’s storage offering is that its controller operating system called Data ONTAP is the same across every NetApp Filer storage product they sell. This is hugely significant as it means if you know how to administer and configure the smallest FAS2000 Series Filers you are pretty much up to speed to administer and configure Filers up to their biggest and beefiest FAS6200 Series Filers so you don’t have to learn another management interface when you upgrade.

NetApp has also produced a Data ONTAP Simulator which in their words is a “A tool that gives you the experience of administering and using a NetApp storage system with all the features of Data ONTAP at your disposal.”

There have been various versions of the simulator over the years which initially could be installed on a simple RedHat or SuSE Linux box using emulated disks and have the same look and feel as a real NetApp Filer (without the rack space requirement or electricity bill!). Things progressed over the years and you could use more Linux distros. Nowadays there is a pre-built VMware virtual machine so you don’t have to install RedHat or SuSE beforehand.

Unfortunately the simulator is only available to existing NetApp Customers and Advantage Partners and requires a login to the NetApp Support Site, http://now.netapp.com

I was about to start a serious rant about this limited availability when surprisingly whilst writing this post Vaughn Stewart sent out a tweet that NetApp are in fact looking at the possibility of opening up access to the simulator for version 8.1 which is fantastic news.

I fiercely believe opening up access to learning and training tools allows so many more people to learn about your technology in their own time and if they know about your technology they are more likely to buy!

So, although the current status is the simulator is not available to all, hopefully this will change soon and this has saved me and you from a far longer rant!

There are however some limitations to the simulator:

  • There isn’t any official support by NetApp and it works more on a community support model using NetApp’s community support forums.
  • There is still quite a bit of configuration to do to get the simulator up and running, it’s not a plug and use VSA.
  • The simulator is limited in the number of disks it can support and the size of the disks. In previous versions of the simulator it was provided with 2 x simulated shelves of 14 x 1 GB Disks with only 20 GB usable space which with some hacking could be extended by 2 more shelves. The current version 8.1 is provided with the same disk configuration but I’ll show you how this can be changed to use up to 4 x shelves of 4 GB disks with 180 GB available space which is a vast improvement and far more usable but you will need VMware Workstation to do this as ESXi doesn’t support changing the size of IDE disks.
  • The simulator isn’t as robust as other true VSAs as it replicates a real Filer where you would have redundant PSUs so doesn’t play nicely when you just power it off! This is unfortunate as previous versions did seem to be a little more robust but the 8.1 version needs to be handled with care.
  • You can’t by default connect to multiple simulators with NetApp OnCommand System Manager as the built in serial numbers are the same and System Manager doesn’t play nicely but I’ll show you how this can be changed.
  • You can’t clone a fully configured simulator as you can’t change the serial number after the initial configuration.
  • The simulator isn’t suited to running anything that is performance heavy as it is aimed at testing the software features rather than any IOPS benchmarking.

I’m going to go though the steps to amend the simulator disk size to the maximum available disks and configure the basic simulator settings so you can use it as a VSA using the following steps:

  1. Download the Simulator
  2. Add to VMware workstation or ESX(i)
  3. Increase the simulator VM disk size
  4. Amend the default serial number
  5. Run the initial configuration
  6. Add 2 new shelves of 14 GB Disks
  7. Move the current config to the new shelves
  8. Delete the 2 x shipped 1 GB disk shelves
  9. Add 2 x 4 GB Disk shelves to replace the shipped 1 GB disk shelves

Hopefully the steps I’m going to go through in this post will one day be put into the simulator as delivered by NetApp to save you the hassle!

Download the Simulator

The simulator can be downloaded from http://now.netapp.com/NOW/download/tools/simulator/ontap/8.0/ (you will need a NetApp login which is only available if you are a Customer or Advantage Partner)

Check that you can meet the hardware and software requirements listed on the download page.

I am going to set up and configure the 7-mode version rather than the cluster mode and on VMware workstation but you can upload the VM to ESX(i) but only after the disk size has been amended as you can’t amend an IDE disk in ESX(i).

Download the 7-mode version which is a .ZIP file either for VMware Workstation, VMware Player and VMware Fusion or the version for VMware ESX(i).

Add to VMware workstation or ESX(i)

Extract the .ZIP file. Copy the extracted files to a folder on your workstation or upload them to a datastore if you are going to be using it on ESX(i) but remember the issue with increased an IDE disk on ESX(i).

Double click on the .vmx file to add to VMware Workstation or browse the ESX(i) datastore and add to inventory.

You should now have a new VM called vsim-7m.


Rename the VM to what you will ultimately call your simulator to avoid confusion.


Edit the VM Settings.

As this is a testing simulator for a virtual hosting environment I am going to only have 1 network card as I don’t need to test any network failover configuration but if you do need some more network functionality leave them in and configure them as you would a physical filer.

Set the Network Adapter to a Network connection or port group on your network.


Increase the simulator VM disk size

The shipped VM comes with a 48 GB VM disk which needs to be expanded to accommodate the new data in the emulated simulator disks when you write data to them.

You need to increase the VM disk size and then extend the partitions and also slices within the simulator to take advantage of the increased VM disk space.

The current 48 GB VM Disk contains 28 x emulated 1 GB disks and then has another 20 GB so if we are going to have 56 x emulated 4 GB disks + 20 GB then we will need a 244 GB VM Disk. I’m not sure if this is actually the correct figure but it works for me. You can make this VM disk thin-provisioned so you don’t have to have all 244 GB available until you write to it.

Edit the VM Settings and increase the HardDisk from 48 GB to 244 GB.


If you want to run the simulator on ESX(i) you can now upload it from VMware workstation with the amended IDE disk size.

The simulator VM runs on FreeBSD and uses the UFS file system.  Unfortunately the usual Linux partition manager GParted can’t see UFS partitions so it isn’t much help so you need to use a FreeBSD boot disk.

I downloaded the FreeBSD 8.2 i386 LiveFS .ISO from freebsd.org.


Edit your simulator VM settings and add a new CD/DVD Drive as the simulator doesn’t come with one.

Attach the FreeBSD LiveFS .ISO

View the console so you can see the simulator boot process.

Boot the VM and change the BIOS boot order to boot first from CD-ROM.


Press Enter to Boot FreeBSD [default].


Select your country and press Enter.


Select your keyboard layout if prompted and press Enter.


Enter F and Enter to launch the Fixit repair mode option.


Select CDROM/DVD and press Enter.


You will now enter “fixit” mode.

Find the VM disk files:

dmesg | grep VMware

You will see there are two VMware Virtual IDE Hard Drive disks, ad0 which is 249856 MB and ad1 which is 1024 MB.


So, ad0 is the disk which is 244 GB.

To view the partitions on the disk:

fdisk ad0

You will see that partition 4 which is 44007 MB must be the partition which holds the emulated simulator disks and this is the partition that needs to be extended.


To extend the partition using the interactive slice editing process:

fdisk –u ad0

Press Enter to not change the BIOS info.


Press Enter to bypass editing the partitions until you get to partition 4 then type Y.

Press Enter to keep the default “sysid”.

Press Enter to keep the default “start”.

Now you need to enter the new sector size. I have worked out what the number needs to be in a completely non-scientific way using a whole host of different boot disks and a million different options! If someone else knows how to work this out in a far better way I would love to know how!

Enter 507513006 as the “size” and press Enter.

Press Enter to skip beg/end address.

You will now see a summary of the partition changes that fdisk will apply.

Press Y to be happy with the entry.

Press Enter to not change the active partition.


You will see a summary of the new partition table showing the new size of 247809 MB.


Press Y to write the new partition table.

You may get a message fdisk: Class not found but this can be ignored.

You then need to extend the slice in the partition.

To view the slices use:

gpart list

You can then find the index of the partition in the slice. You can see under the Geom name: ad0s4 that ad0s4b is the slice which is 39 GB and that corresponds to index 2.


gpart by default will make the partition use all the available space. –i is the index number.

Extend the slice with the following command:

gpart resize –i 2 ad0s4


The disk, partition and slice has now been extended and you can disconnect the mounted .ISO from the VM and shut down the simulator.

Amend the default serial number

Boot the simulator again.

When you see Hit [Enter] to boot immediately, or any other key for command prompt, hit Ctrl-C.

You will then enter the SIMLOADER prompt.

I’ve used the same steps and number scheme from this NetApp Communities post.

Enter the following commands to set your unique serial number. (I’ve used 1111111101 – That’s 8 x 1s + 01)

set bootarg.nvram.sysid=1111111101
set SYS_SERIAL_NUM=1111111101


Run the initial configuration

The simulator will continue to boot.

When you see Press Ctrl-C for Boot Menu, hit Ctrl-C.

Enter option (4) Clean configuration and initialize all disks.


When the simulator says Zero disks, reset config and install a new file system, type Y.

Type Y to confirm erasing all the data on the disks.

The simulator will set up the disks and reboot.

Once it has rebooted the configuration will continue.


When prompted enter the new hostname. Mine is lonfiler01.

Press Enter to accept the default [n] for IPv6.

Press Enter to not configure interface groups.

Enter the IP address for your network.

Enter the Subnet Mask.

Press Enter to accept the default media type.

Press Enter to accept the default flow control.

Press Enter to accept the default of no jumbo frames.

Press Enter to not continue setup through the web interface.

Enter the default gateway IP Address.

Press Enter to bypass configuring an administrative host.

Enter a timezone.

Enter a location name.

Press Enter to accept the default HTTP root file directory.

Press Enter to not run the DNS resolver.


Press Enter to not run the NIS client.

Press Enter to continue, auto support will be turned off later.

Press Enter to not run the Shield Alternate Control Path Management interface for SAS shelves.

Enter and confirm the root password.

The initial configuration will continue. Once complete, press Enter to bring up a login prompt and enter the root password you had entered.

It’s now best to continue configuration through an SSH connection with Putty so you can copy and paste the configuration commands.

Some of the ONTAP functions are licensed already in the simulator but some aren’t so you may as well add all the options that aren’t added from this list.

license add BSLRLTG #iscsi
license add BQOEAZL #nfs
license add ANLEAZL #flex_clone
license add DFVXFJJ #snapmirror
license add DNDCBQH #snaprestore
license add JQAACHD #snapvalidator
license add BCJEAZL #snapmanagerexchange
license add RKBAFSN #smdomino
license add ZOJPPVM #snaplock
license add PTZZESN #snaplock_enterprise
license add PDXMQMI #sv_ontap_sec
license add RIQTKCL #syncmirror_local

Add 2 new shelves of 14 GB Disks

Now you are ready to add the new shelves.

Enter advanced mode and unlock the diagnostic user. Enter a password and confirm.

priv set advanced
useradmin diaguser unlock
useradmin diaguser password

Launch the systemshell and login as diag and enter the password you have just set.



The next step will use the makedisks script to add 14 x 4 GB disks as shelf 2 and 3 of type 31 which is:

31     NETAPP__ VD-4000MB-FZ-520 4194,304,000 B 4289,192,960 B     Yes     520

setenv PATH "${PATH}:/sim/bin"
cd /sim/dev
sudo makedisks.main -n 14 -t 31 -a 2
sudo makedisks.main -n 14 -t 31 -a 3


Then exit the systemshell and lock the diaguser.

useradmin diaguser lock

Set admin mode.

priv set admin

Reboot the filer.


Once the filer has come back up, connect and login again.

Assign all the disks that are unowned to the filer.

disk assign all

Move the current config to the new shelves

We will move the current root volume vol0 to a new aggregate and new root volume on the new shelves.

First, create a new aggregate with the new shelves. Turn of checking for spare disks (which will still error in the logs but at least allow you to create a bigger aggregate) and set the raid group size to 28.

options disk.maint_center.spares_check off
aggr create aggr1 -r 28 28@4G

Wait until the aggregate has been created and then create a new flexible volume vol1 on aggregate aggr1 of size 850Mb.

vol create vol1 aggr1 850m

Then we need to ndmp copy the contents of the old root volume into the new root volume.

ndmpd on
ndmpcopy /vol/vol0 /vol/vol1

Wait until the ndmp copy has finished.

Set the new volume as the root volume.

vol options vol1 root

Reboot the filer.


Once the filer has come back connect with Putty and login again.

Something seems to go funny with the SSL certificates so you cannot also connect with OnCommand System Manager. The easiest way is to just recreate them.

options ssl.enable off
secureadmin setup ssl

Enter Y to proceed and then you can just accept all the defaults or if you are more security minded you can enter more accurate values for your certificate requirements.

Then turn back on SSL.

options ssl.enable on


Delete the 2 x shipped 1 GB disk shelves

Now we can remove the old vol0 and aggr0 as they are no longer holding the root volume.

vol offline vol0
vol destroy vol0

Y to confirm deletion.

aggr offline aggr0
aggr destroy aggr0

Y to confirm deletion.

Now we can remove the old disks and shelves.

options disk.auto_assign off
priv set advanced
disk remove_ownership v5.*

Y to Confirm.

disk remove_ownership v4.*

Y to Confirm.

We may as well rename the root volume and aggregate back to what they were originally just to keep things clearer.

Rename the existing root volume.

vol rename vol1 vol0

Rename the existing aggregate.

aggr rename aggr1 aggr0

Add 2 x 4 GB Disk shelves

Now we can go ahead and add 2 more 4 GB disk shelves to replace the 2 x 1 GB Disk shelves that have just been removed.

Enter advanced mode and unlock the diagnostic user. Enter a password and confirm.

Launch the systemshell and login as diag and enter the password you previously set.

useradmin diaguser unlock


Now we need the remove the old simulated disks from shelf 0 and 1.

setenv PATH "${PATH}:/sim/bin"
cd /sim/dev/,disks
sudo rm v0*
sudo rm v1*
sudo rm ,reservations

Again use the makedisks script to add 14 x 4 GB disks as shelf 0 and 1 of type 31 which is:

31 NETAPP__ VD-4000MB-FZ-520 4194,304,000 B 4289,192,960 B Yes 520

cd /sim/dev
sudo makedisks.main -n 14 -t 31 -a 0
sudo makedisks.main -n 14 -t 31 -a 1

Then exit the systemshell.


Lock the diaguser and set admin mode.

useradmin diaguser lock
priv set admin

Reboot the filer.


Once the filer has come back connect and login again.

You may as well turn off the pesky autosupport warnings and then assign all the new disks that are unowned to the filer.

options autosupport.support.enable off
options autosupport.enable off
options disk.auto_assign on
disk assign all

You can now add these disks to the existing aggregate.

aggr add aggr0 28@4G

Y to Confirm adding the disks and again for the low spare warning.

You now have an aggregate spanning 4 x simulated shelves of 14 x 4 GB disks giving you 180.97 GB remaining available disk space after the root volume which is much better than the 20 GB you had initially!

Now is a good time to halt the filer and take a snapshot so you can easily revert if you have an issue.

You can also now go ahead and create your volumes and exports, LUNs, CIFS shares or whatever you want to use your simulator to test.

Remember, never just power off the simulator as you will land up with complicated wafl consistency issues which are difficult and sometimes impossible to fix.

Hopefully all these steps will be redundant when NetApp publicly release their simulator with the maximum possible disk size already configured and available as a simple to import virtual appliance.

  1. January 4th, 2012 at 10:55 | #1

    Excellent write up, with a great focus on the low level details !!!
    Now I seriously need to find the time to setup a ONTAP simulator 🙁

  2. martin
    January 4th, 2012 at 13:12 | #2

    can you make netap simulator 8.1 7 mode work in HA pair?

  3. WoodITWork
    January 4th, 2012 at 20:49 | #3
  4. tom miller
    January 5th, 2012 at 04:04 | #4

    What a great technical write-up, clear, to the point, and you explain what we are doing. How you know this is beyond me but thanks so much. I’ve been using SIM 8.01 for vSphere5 and SRM5 testing so I can be better prepared when in the field for the real deal. Even when hacking 8.01 you only get about 48GB of space. Just not enough to test SRM with all the snapshot and reserve space required. Hopefully SIM 8.1 works the the latest NetApp SRA.

    Thanks again. I’ve added your site to my RSS feeds.

  5. martin
    January 5th, 2012 at 08:44 | #5


    I have read that post 🙂 But when i was looking on this post i tough you will be able to do some magic 🙂

  6. David Muegge
    January 7th, 2012 at 11:36 | #6

    I have been trying to figure out this process. Thanks for filling in the blanks. Much appreciated!


  7. Dmitry
    January 9th, 2012 at 14:32 | #7

    Simulate ONTAP does not support the following features:
    • High Availability (CFO/SFO)
    • Fibre channel and SAN connectivity
    • RLM (Remote LAN Module)
    • CFE, BIOS, shelf FW, and so on
    • Multipathing

  8. January 10th, 2012 at 10:32 | #8

    Great post Julian!

    Like you I believe Netapp should make the simulator available to anyone – they’re one of the only storage vendors that don’t provide something for free to the community. It’s a shame it’s so convoluted to setup (although in fairness it’s much simpler if the default storage is sufficient) as that’ll discourage people from trying it out. I’ve been testing various VSAs in my home lab but I’ve not used Netapp because it’s too limited – and given that I use Netapp’s at work that should have been my first choice!

  9. Luke Munro
    January 10th, 2012 at 21:45 | #9

    Nice Post,

    I was getting this error when originally trying to change sysids on the simulator. I followed your instructions but still get it. Did you ever get this after changing the sysid?

    WARNING: System id mismatch. this usually occurs when replacing CF or NVRAM cards!

    When pressing N the sim reboots, when pressing y you can get further after selecting option 4 to clear config and initialize disks but then it panics.

    I was stuck at this stage when the 8.1 sim came out.

  10. Luke Munro
    January 11th, 2012 at 06:46 | #10

    Figured it out, My Sim was a template which I had already run through option 4 on. After uploading straight from the zip extract and configuring it worked fine.

  11. January 20th, 2012 at 16:46 | #11

    Very good post.
    Regarding the number 507513006; the formula to calculate this is:

    Rsize = H * S * int{ int( Vreal / B ) / ( H * S ) } – PartitionStartValue

    See: http://cosonok.blogspot.com/2012/01/formulas-to-calculate-dimensionless.html

  12. Darkstar
    January 26th, 2012 at 13:29 | #12

    An easy way to find the size is to use the tool “sade” to inspect the partitions. It is available in FixIt mode and shows you the current size of the partition and the size of the free area afterwards. Just add these two together and then you have the size you want/need.

    Note that fdisk may prompt you that “partition does not end on a cylinder boundary”, you can then type “y” to have this fixed automatically (it subtracts a few sectors from your size)

    Much easier than using the formula above 🙂


  13. Geoff Baldry
    February 11th, 2012 at 09:28 | #13

    A very good write-up indeed. Just used it to maximise my simulator, and worked 1st time. If you have a mac to run yourr simulator, you can do the IDE disk expansion in VMware Fusion too.

  14. tom miller
    February 11th, 2012 at 16:38 | #14

    I see NetApp released a new SIM – vsim-DOT810RC2-7m-esx. In the netapp forums I’ve posted kernel panic errors with the 8.1 SIM along with others having the same issue. Trying to use the new release RC2 but I’m not able to expand the disk to 244GB before moving it to esxi5. Error message is disk needs repair when trying to expand. Any thoughts?

    Thanks again for this great write-up. Just wish the SIM would keep running in order to run repeatable SRM5 test plans. Get everything working then the next day the SIM is in a kernel panic.

  15. tom miller
    February 11th, 2012 at 21:35 | #15

    Fixed the expand error above by simply letting VMware WKS power on the SIM, letting it repair the disk then quickly powering off. I could then expand the disk to 244GB before moving it to esxi5. Your process above works with the new SIM rc2 as well. Hopefully the new SIM does not kernel panic. I’ll know tomorrow if it acts like 8.1.

  16. tom miller
    February 14th, 2012 at 19:56 | #16

    Well after running three days on the new SIM it has gone to kernel panic mode again.

  17. Ab Thor
    February 22nd, 2012 at 13:57 | #17


    I have a question about the resized disk. When i login to Ontap and check for the disk sizes they still show as 1G and not 4G. 🙁

  18. kev g
    February 28th, 2012 at 15:49 | #18

    Ab, reboot between deleting the old disks and assigning the new ones.. the OS remembers the old disk type…

  19. Ruben R
    March 3rd, 2012 at 09:22 | #19

    This post really helped me out. I’m new to NetApp and this gave me good insight. I was wondering if you could do the same thing for Cluster Mode? This works pretty easy for 7-Mode but trying to do this in Cluster Mode is challenging. Some of the commands have different syntax which I’ve been able to find however I’m having trouble creating a new volume. When I try this command “vol create -vserver -volume vol1 -aggregate aggr1 -size 850MB” I get Error: command failed: This operation is not supported on 7-mode volume ‘vol1’. So I cannot move the root volume. All the other stuff has worked excet that. Any help you could offer would be great.

  20. Phil
    March 12th, 2012 at 22:33 | #20

    Excellent walkthrough, you have saved me a lot of time. If you’re ever in Wellington NZ you have a coffee and/or beer owed.


  21. Kurt
    March 14th, 2012 at 15:55 | #21


    When trying to add the disks I get the following error message:
    OntapSim1% cd /sim/dev
    OntapSim1% setenv PATH “${PATH}:/sim/bin”
    cd /sim/dev
    sudo makedisks.main -n 14 -t 31 -a 2
    sudo makedisks.main -n 14 -t 31 -a 3OntapSim1% cd /sim/dev
    OntapSim1% sudo makedisks.main -n 14 -t 31 -a 2
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v2.49:NETAPP__:VD-4000MB-FZ-520:44384128:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v2.50:NETAPP__:VD-4000MB-FZ-520:44384229:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v2.51:NETAPP__:VD-4000MB-FZ-520:44384230:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.16:NETAPP__:VD-4000MB-FZ-520:44384231:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.17:NETAPP__:VD-4000MB-FZ-520:44384232:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.18:NETAPP__:VD-4000MB-FZ-520:44384233:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.19:NETAPP__:VD-4000MB-FZ-520:44384234:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.20:NETAPP__:VD-4000MB-FZ-520:44384235:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.21:NETAPP__:VD-4000MB-FZ-520:44384236:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.22:NETAPP__:VD-4000MB-FZ-520:44384237:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.24:NETAPP__:VD-4000MB-FZ-520:44384238:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.25:NETAPP__:VD-4000MB-FZ-520:44384239:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.26:NETAPP__:VD-4000MB-FZ-520:44384240:8248448
    /libexec/ld-elf.so.1: Shared object “libc.so.7” not found, required by “makespare”
    Creating ,disks/v3.27:NETAPP__:VD-4000MB-FZ-520:44384241:8248448
    Shelf file Shelf:DiskShelf14 updated

    Any idea?

    Love your post!!!

    Best regards,

  22. James Shelton
    March 22nd, 2012 at 15:22 | #22

    @tom miller Yes…I don’t think this process produces a stable 8.1 SIM in any way. Almost guaranteed panic due to underlying space issues after doing any sort of real work with it…

  23. danny
    April 15th, 2012 at 02:07 | #23

    arg, crashed on me too. is there no stable version of the sim available?

  24. Jason
    April 16th, 2012 at 23:24 | #24

    same problem here. After using the modified sim, the space issues cause it to eventually dump…

  25. Diego
    May 5th, 2012 at 00:14 | #25

    Im waiting for a free version of 8.1 x64 for a while. So…
    If you mount /dev/ad1 and copy the 81_q_image.tgz content to /x86_64/freebsd/image1/ and change to correct serial and sys_model in /env/env plus disable simlator setenvs … or PANIC: SIMBOX is not a supported platform

    But if you just need space, you can del /dev/ad0s4b/dev/,disks and edit makedisks.main to get all space you want in 32bit f*$# kernel

    If you look kernel and platform.ko (81_q_image.tgz) you can see those serial and model checking…

    Anyway, there is a lot of Fujitsu and IBM Netapp VSAs running ESX, Im looking for serial and sysmodel. Anyone?

  26. Pete
    May 13th, 2012 at 18:04 | #26

    Thanks for the write up. After following all the steps I ran into this error when after i pressed 4 to zero the disks:
    PANIC: Can’t find the device with WWN 0x134751488. Remove ‘/sim/dev/,disks/,reservations’ and restart. in SK process vha_disk_resv on release 8.1X47

  27. Shankar
    March 15th, 2013 at 09:43 | #27

    Hi All ,

    I am facing an issue after installing the netapp stimulator in my VM .
    I am not able to connect with my filer from VM ,

    Please suggest an solution .

    Note : i Have changed the network setting to bridged netwrok in VM and netapp stimaulator

  28. end user
    April 14th, 2013 at 21:42 | #28

    Hi, can you help me where I can find “makedisks.main” script. Probably I’ve lost same step.
    Many thanks in advance

  29. ThanksfortheTips
    May 16th, 2013 at 20:48 | #29

    Thanks for the example WoodITWork!

    As a response to “end user”, it appears that Netapp changed the script name to make disks in the newer versions of the simulator. I was able to use the command “vsim_makedisks” with the same options above to create the disks.

  30. Janis
    August 14th, 2013 at 09:43 | #30

    Im doing test for 2nd line position and one of tasks is:

    “You will need 2 netapp simulators set up as an HA pair running Ontap 8.1”

    As I understand Simulator doesnt support HA pairs or something have changed?

  31. Sam
    August 29th, 2013 at 01:48 | #31

    First of all thank you for writing great blog.
    Now after I expand the VmdK file and all the steps before To view the slices use:gpart list
    Im geeting this error message

    GEOM_LABEL: Label ufsid/4b60blahblah

    Index also shows “1” instead of 2 ?
    Any idea what i not followed?

    Thank you

  32. Tammar
    September 5th, 2014 at 18:21 | #32

    Thanks for the great info, one thing to add is the “new sector size” (Enter 507513006 as the “size” and press Enter), in Ubuntu, fdisk -l report “total 524288000 Sectors”, i will try to use this number instead (to gain more space :)), will update my post if no error were reported.

  33. December 29th, 2016 at 11:05 | #33

    Great post on how to install and optimize the NetApp simulator thanks.

    I’ve posted an update to cover the ONTAP 9 simulator here:


  1. No trackbacks yet.
Comments are closed.