About shatfield

shatfield · ‎2014-07-17

There are several sets posted on the simulator download page. Collect the license files for 8.2 and 8.2.1 in both 7 mode and C mode and you should have 9 sets to play with.

shatfield · ‎2014-07-16

Something is wrong with that instance. Probably best to start over clean from the original .tgz file. If it happens again from a clean start tell me what you are doing step by step. Reproducing that could be interesting.

shatfield · ‎2014-07-15

The simulator ships with the equivalent of blank hard drives, so you have to install ONTAP. (Boot menu, option 4). Shipping it that way minimizes the size of the download and makes it easier to customize, but I wish they would disable autoboot in the stock ENV file. On actual hardware that would usually be performed by the factory but its good to know how to do it. Its all explained pretty well in the documentation which you can find on the Simulate ONTAP download page, or here: http://mysupport.netapp.com/knowledge/docs/simulate_ontap/Simulate_ONTAP_8.2.1_Installation_and_Setup_Guide.pdf

shatfield · ‎2014-07-11

From the bash shell or the dvadmin cli, type exit to get back to the login script. From the login script, ctrl C to get back to bash.

shatfield · ‎2014-07-10

Picking through the vmx could identify device 16. Sometimes the serial ports cause cloning problems. Try removing them. I posted instruction some time ago for creating a new clean vmx file. Its a pretty basic freebsd plus a handful of advanced configuration parameters in the vmx. Its not a good vm from a linked clone perspective. The longer its on the bigger the delta disks will get until it fills the -sim.vmdk on each clone. Here are the instructions for building a new vmx: 1. Create a new VM, of type FreeBSD (x64), 2vCPUs, 1600MB RAM, 6 NICs, and NO Hard drives 2. Add the DataONTAP.vmdk on IDE 0:0 3. Add the DataONTAP-var.vmdk on IDE0:1 4. Add the DataONTAP-vnvram.vmdk on IDE1:0 5. Add the DataONTAP-sim.vmdk on IDE1:1 6. Add the following options to the .vmx file by hand, or as configuration parameters in ESX (vm-editsettings->options->Advanced/general->Configuration Parameters->Add row: monitor_control.pseudo_perfctr = "TRUE" pciHole.start = "3072" timeTracker.forceMonotonicTTAT = "TRUE" monitor_control.disable_tsc_offsetting = "TRUE" monitor_control.disable_rdtscopt_bt = "TRUE"

shatfield · ‎2014-07-10

I would have at least one per vcenter, although you could just use one. You would probably be better off with one per location. The actual ontap-v ovf file is embedded in the installer, which gets pushed out during the vm setup wizard.

shatfield · ‎2014-07-08

This sort of thing seems to come up repeatedly, so I wrote a doc: https://communities.netapp.com/docs/DOC-33502

shatfield · ‎2014-07-07

Interesting things happen during the first boot. Some of it happens in /var, which persists across a 4/4a. A bootmenu->wipeconfig may clear it out. But you'd be better off starting clean. Change the serial & sysid first (very first boot), then go into the systemshell and change the disk population. The easy way though is to catch the first boot, set the mode, set the serial, set the sysid, arm vdevinit with the desired disk population, then let it boot.

shatfield · ‎2014-07-02

SNMP is not enabled by default in CDOT. Use the admin credentials to add it to system manager. Use a 3.x release of system manager. Once in you can enable snmp and drop in your community strings and trap hosts from the gui. CLI is always an option as well.

shatfield · ‎2014-07-02

That is not an eval license, that is a permanent license for the 7 mode simulators. Are you trying to put the simulator in evaluation mode, or are you looking for a CIFS eval key for some really old gear?

shatfield · ‎2014-07-02

Depends on where the eval came from and which version of ONTAP its running. The public eval is keyed differently than other 7mode systems, and it only takes eval keyes cut for the eval build of edge. Your partner or netapp SE should be able to help you out.

shatfield · ‎2014-06-30

Can you run an upgrade in the sim? Yes, if you can get an appropriate image.tgz file. The regular q_image.tgz works on 8.2RC1 and later, but the v_image.tgz is a better fit if you have an edge entitlement. Is there a lot of value in it from a training perspective? Not so much. Since the vsims are non-ha, running an NDU scenario isn't possible. All the associated steps, firmware upgrades, bios updates, SP updates, etc don't apply to a sim. A single node 7mode upgrade is 3 commands, and only slightly more interesting in Cmode. Its still useful form a testing perspective. You could apply a specific version to replicate an issue, or to test a version specific feature or fix.

shatfield · ‎2014-06-25

Were they ever powered on before the 2nd step 5? (hoping for a no) Also step 6 needs to come before the 2nd step 5.

shatfield · ‎2014-06-18

Thats exactly right. The VM requirements are fixed, the server minimums include the extra overhead needed for the hypervisor and the dvadmin tool used in the non-eval version.

shatfield · ‎2014-06-18

The resource requirements are very specific. It must have 2 vCPU and 4GB of ram assigned to the VM. No more, no less. The production Edge models are the same. 7 mode Edge/Edge-T/Edge Premium are 2vCPU/4GB, The Clustered Ontap model requires 2vCPU/8GB.

shatfield · ‎2014-06-17

Thats a little light, even for the eval. Edge fully consumes 2 cores and 4gb of ram, and the host needs some overhead. You really need 4 cores and 8gb ram in the host for Edge to run optimally. Edge does not issue CPU HLT instructions on idle, so it is expected that the CPU cores used by the edge vCPUs will sit at 100%. In the non-eval version, 2 full cores of CPU cycles are reserved for Edge during install, along with a 4G RAM reservation (8GB for CDOT). DVadmin will also refuse to initialize the VM if power management is not disabled on the host. To get the best sense of how edge will perform it would be a good idea to replicate these conditions in the eval, and run it on a host with a supported raid controller and local disk configuration.

shatfield · ‎2014-06-16

I couldn't get mine to panic, but its CDOT8.2.2RC1. What mode/version are you running?

shatfield · ‎2014-06-13

Hard to say, really. Leaving it trimmed to 512 may give ontap more ram for caching which should help performance Leaving it trimmed to 512 may cause additional swap activity which should hurt performance All the jumbo 4gb vSIMs I've seen have it set to 760.

shatfield · ‎2014-06-13

If you gave your vsim 4gb, you can set that value to 760 or just unset it. It restricts the ram available to the bsd environment to keep ontap functional when its only got the default 1600mb to work with.

shatfield · ‎2014-06-05

vSIM HA is not supported. NetApp has it working internally, but they've never published how to set it up. To get it working you would need: -Persistent VNVRAM -Shared access to the disks from both VMs -An RDMA HA interconnect between the VMs The first is easy, the second is complicated, and the third I have no idea how to do.

shatfield · ‎2014-05-29

Whats the output of: options snmp.enable system snmp show system services firewall policy show -policy * -service snmp Strange things also happen when root gets full so check these too: df -h storage aggregate show

shatfield · ‎2014-05-27

Convert the vmdk before adding the vmx to inventory.

shatfield · ‎2014-05-07

When you change the serial number on the second node, be sure to change it to one of the serial numbers listed in one of the 8.2.x simulator license files. Multiple simulators are absolutely possible, you just have to use serial numbers with published license key sets. There are at least 9 sets available, more if you've been paying attention to the RCs. You can use serials/keys from both the 7mode and Cmode list. The feature keys are node-locked to a serial number. They aren't really 7mode/Cmode specific, except for the cluster base key which doesn't apply to 7mode anyway.

shatfield · ‎2014-05-03

Sure, but some hand editing of the vmx is required. To add more nics, you need more PCI slots. To get more PCI slots, you need a PCI bridge. Add the following snippet to your .vmx file. pciBridge0.present = "TRUE" pciBridge4.present = "TRUE" pciBridge4.virtualDev = "pcieRootPort" pciBridge4.functions = "8" pciBridge5.present = "TRUE" pciBridge5.virtualDev = "pcieRootPort" pciBridge5.functions = "8" pciBridge6.present = "TRUE" pciBridge6.virtualDev = "pcieRootPort" pciBridge6.functions = "8" pciBridge7.present = "TRUE" pciBridge7.virtualDev = "pcieRootPort" pciBridge7.functions = "8" This works best on a clean never-booted vmx file. If you get PCI slot errors after adding this code, change the slot number of the problematic devices to -1, which tells the hyper visor to pick an open slot at boot.

shatfield · ‎2014-04-30

The 7.x simulator was a completely different architecture. The 7.x sim runs both instances of ontap as separate processes on a single linux system. It was able to simulate HA because both processes can share the same disks and both have access to the same ram so spoofing RDMA with DMA wouldn't have been a big challenge. In 8.x the simulator is based on DataONTAP-v, so each instance runs it its own VM without the layer of linux underneath. Its a much more realistic simulation but makes HA more challenging to pull off. What that means for you, is you need to read the 7.x simulator install guide so you can build a linux VM to run it on. Its didn't ship as a standalone VM, so you have to build your own.

Re: Simulator 8.2.1 License required

Re: Unable to launch simulator 8.2.1

Re: Unable to launch simulator 8.2.1

Re: How Do You Switch Dvadmin Shells?

Re: Create linked clone from Simulator VM

Re: Can You Have Just One Instance of the Data OnTAP-v Installer VM?

Re: Cannot join node to cluster

Re: Cannot join node to cluster

Re: Simulator cant send SNMP requests back to system manager 2.1 on the same subnet

Re: CIFS license for Ontap 7.3

Re: Can You Run SnapDrive in the Evaluation Version?

Re: Data ONTAP Simulator - testing DOT upgrades

Re: Cannot join node to cluster

Re: High CPU with Data OnTAP EDGE

Re: High CPU with Data OnTAP EDGE

Re: High CPU with Data OnTAP EDGE

Re: bootarg.init.low_mem

Re: bootarg.init.low_mem

Re: bootarg.init.low_mem

Re: 8.2 7 mode HA mode query

Re: Simulator 8.2.1 snmp.enable changed to off after reboot

Re: ONTAP Simulator Fixes - MEGA Thread

Re: 8.2.x licenses in 7-mode bound to serial number

Re: Add more network interfaces to simulator

Re: Can 7.3.6 simulator be used under ESXi?