Subscribe

Re: Simulate ONTAP 8.1.1 withVirtualBox

This isn't really NetApp specific, its how virtualbox parses the ovf format in their implementation of the standard.

 

Inside an OVA file (which is a tar with specific constraints), you'll find the ovf, the vmdk file, a manifest file (for checksum validation), and sometimes other elements.  The ovf is an xml-like standards based way tof defining the virtual machine.  The intent of the standard is to allow VMs to be interchanged between virtualization platforms,  In practice there are a lot of rough edges.  

 

Inside the TGZ archives you'll find when you download the older simulator releases, you'll find the vmdk files, and a vmx file (among others).  These are virtual machines in a format native to VMware.  Adding an ovf to this file set just facilitates importing them into virtualbox, as a less error prone alternative to hand crafting a new vm in virtualbox and attaching the virtual disks.

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Simulate ONTAP 8.1.1 withVirtualBox

From your screenshot it looks like you imported successfully.  Now you just need to ctrl-c at the boot menu during the next reboot and pick option 4 to install Data ONTAP.

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Simulate ONTAP 8.1.1 withVirtualBox

Is there an update version of this document for Simulator ONTAP 8.3 with Virtualbox?

I was able to use same methodoly here for Simulator ONTAP 8.2 but not for Simulator ONTAP 8.3. There seem to be quite a bit of change in version 8.3. There is no longer sim. vmdk, var.vmdk, nvram.vmdk and base vmdk.

I was able to extract Sim 8.3.2 OVA file into 4 VMDK files which are supposedly similar to previous ones but with different names '*disk[1-4].vmdk'. I kept getting PANIC errors:

 

VLOADER> setenv SYS_SERIAL_NUM 4082368507
VLOADER> setenv bootarg.nvram.sysid 4082368507
VLOADER> setenv bootarg.vm.run_vmtools false
VLOADER> boot_ontap
x86_64/freebsd/image1/kernel data=0x9a17d0+0x479ab8 syms=[0x8+0x46800+0x8+0x2fc53]
x86_64/freebsd/image1/platform.ko text=0x1e5add data=0x485a0+0x42bd0 syms=[0x8+0x21780+0x8+0x175e8]
NetApp Data ONTAP 8.3.2RC1
ioapic0: Changing APIC ID to 0
Copyright (C) 1992-2015 NetApp.
All rights reserved.
*******************************
* *
* Press Ctrl-C for Boot Menu. *
* *
*******************************
^CBoot Menu will be available.

Please choose one of the following:

(1) Normal Boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
Selection (1-8)? 4
WAFL CPLEDGER is enabled. Checklist = 0x7ff841ff
PANIC : prod/common/wafl/free_cache.c:909: Assertion failure.
version: 8.3.2RC1: Thu Nov 5 01:54:42 PST 2015
conf : x86_64.sim
cpuid = 0
Uptime: 1m8s

PANIC: prod/common/wafl/free_cache.c:909: Assertion failure. in SK process wafl_hipri on release 8.3.2RC1 (C) on Thu Feb 25 15:35:13 GMT 2016
version: 8.3.2RC1: Thu Nov 5 01:54:42 PST 2015
compile flags: x86_64.sim
recursive PANIC: page_t has no physical address
cpuid = 0
Uptime: 1m8s

The operating system has halted.
Please press any key to reboot.

 

Any insight to this problem would be greatly appreciated.

 

Thanks,

Hien

 

Re: Simulate ONTAP 8.1.1 withVirtualBox

Hien -

 

The same basic steps work - but as you point out the vmdks are different for 8.3  You can generally figure out the order and which files go with which controllers by examining the vmx file describing the machine.

 

Also, in this same thread, read all the posts from Sean Hatfield.  Then check out his other posts for Simulator topics.  Good stuff.  A lot of them describe details about later versions of the simulator and the oddities that each virtualization product associates with the OVA/OVF descriptor formats.  Generally the manual steps still work but Sean has ways to update the OVF for automatic import.

 

The only issue I've found is that VBox really didn't like the vmdk's in the simulator package, at least on a Mac.  I used the VBox utility to convert to VDI's and it worked much better for me.  

 

 

Hope this helps.

 

Bob Greenwald

Lead Storage Engineer | Consilio LLC

NCIE SAN Clustered, Data Protection

 

 

Judos and accepted solutions are alwys appreciated.

Re: Simulate ONTAP 8.1.1 withVirtualBox

Thanks Bob.

 

That panic looks like a RAM shortage.  Try it with 3072, 3580, or 6144.  VBox doesn't appear to provide control of PCI hole placement, and at 4-5gb it seems to be landing in an unfortunate spot in the address space.  Use 6gb+ or 3-3.5gb to work around the hole.  The old 1600mb sizing is too small for 8.3+.

 

The 8.3+ simulators are distributed as OVAs now so the vmdks are in a gz compressed sparse optimized format.  They can import on mac with the OVA adjustments.  I'll dig up a sample and post it later.

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Simulate ONTAP 8.1.1 withVirtualBox

In my case NICs on Node 2 are setup correctly just like Node 1:

 

Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 6 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0f: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 5 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0e: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 4 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0d: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 3 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0c: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 2 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0b: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 1 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0a: Link up.

 

But still cannot join Node 2 to Cluster:

 

Do you want to create a new cluster or join an existing cluster? {create, join}:
join


System Defaults:
Private cluster network ports [e0a,e0b].
Cluster port MTU values will be set to 1500.
Cluster interface IP addresses will be automatically generated.

Do you want to use these defaults? {yes, no} [yes]:

It can take several minutes to create cluster interfaces...


Step 1 of 3: Join an Existing Cluster
You can type "back", "exit", or "help" at any question.


Enter the name of the cluster you would like to join [c1]: c1

Joining cluster c1

Network set up ................Error: Remote ping test failed. Verify that this node is cabled correctly and
that the cluster interfaces are using ports on the internal cluster network.
To verify, run the ping command from the CLI. For example,
"network ping -lif clus1 -lif-owner node-01 -destination <cluster ip from cluster>
-verbose true -show-detail true".

Restarting Cluster Setup

 

Would you have any clues or insight on how you have 2-Node Cluster using Simulator 8.2 with VirtualBox?

 

Thanks,

Hien

 

Re: Simulate ONTAP 8.1.1 withVirtualBox

Thank you Bob and Sean! Setting memory to 3072MB and 6144MB work for Simulator 8.3.2 on VirtualBox. Sure it would work with 3580MB. How do I ACCEPT AS SOLUTION?

Re: Simulate ONTAP 8.1.1 withVirtualBox

Since you didn't make the thread you can't mark a solution.  Best you can do is add kudos so the helpful posts stand out.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Simulate ONTAP 8.1.1 withVirtualBox

Here's my ovf file for the 832rc1 workstation build with the virtualbox adjustments.  Untar the OVA, delete the .mf manifest, and replace the contents of the .ovf with this and it should import. Then connect the NICs to your hostonly and nat networks accordingly and power it up.  

<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by VMware ovftool 1.0.0 (build-166674), User: nviet, UTC time: 2015-11-16T15:43:26.043808Z-->
<Envelope vmw:buildId="build-166674" xmlns="http://schemas.dmtf.org/ovf/envelope/1" xmlns:cim="http://schemas.dmtf.org/wbem/wscim/1/common" xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1" xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vmw="http://www.vmware.com/schema/ovf" xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <References>
    <File ovf:compression="gzip" ovf:href="vsim-netapp-DOT8.3.2RC1-cm-disk1.vmdk.gz" ovf:id="file1" ovf:size="557577272"/>
    <File ovf:compression="gzip" ovf:href="vsim-netapp-DOT8.3.2RC1-cm-disk2.vmdk.gz" ovf:id="file2" ovf:size="605"/>
    <File ovf:compression="gzip" ovf:href="vsim-netapp-DOT8.3.2RC1-cm-disk3.vmdk.gz" ovf:id="file3" ovf:size="612"/>
    <File ovf:compression="gzip" ovf:href="vsim-netapp-DOT8.3.2RC1-cm-disk4.vmdk.gz" ovf:id="file4" ovf:size="627"/>
  </References>
  <DiskSection>
    <Info>Virtual disk information</Info>
    <Disk ovf:allocationUnits="1048576" ovf:capacity="1943" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:populatedSize="567607296"/>
    <Disk ovf:allocationUnits="1048576" ovf:capacity="1542" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk2" ovf:fileRef="file2" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:populatedSize="65536"/>
    <Disk ovf:allocationUnits="1048576" ovf:capacity="4865" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk3" ovf:fileRef="file3" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:populatedSize="65536"/>
    <Disk ovf:allocationUnits="1048576" ovf:capacity="236231" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk4" ovf:fileRef="file4" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:populatedSize="65536"/>
  </DiskSection>
  <NetworkSection>
    <Info>The list of logical networks</Info>
    <Network ovf:name="hostonly">
      <Description>The hostonly network</Description>
    </Network>
    <Network ovf:name="nat">
      <Description>The nat network</Description>
    </Network>
  </NetworkSection>
  <VirtualSystem ovf:id="vsim_netapp-DOT8.3.2RC1-cm">
    <Info>A virtual machine</Info>
    <Name>vsim_netapp-DOT8.3.2RC1-cm</Name>
    <OperatingSystemSection ovf:id="78" vmw:osType="freebsd64Guest">
      <Info>The kind of installed guest operating system</Info>
    </OperatingSystemSection>
    <VirtualHardwareSection>
      <Info>Virtual hardware requirements</Info>
      <System>
        <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
        <vssd:InstanceID>0</vssd:InstanceID>
        <vssd:VirtualSystemIdentifier>vsim_netapp-DOT8.3.2RC1-cm</vssd:VirtualSystemIdentifier>
        <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>
      </System>
      <Item>
        <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>
        <rasd:Description>Number of Virtual CPUs</rasd:Description>
        <rasd:ElementName>2 virtual CPU(s)</rasd:ElementName>
        <rasd:InstanceID>1</rasd:InstanceID>
        <rasd:ResourceType>3</rasd:ResourceType>
        <rasd:VirtualQuantity>2</rasd:VirtualQuantity>
      </Item>
      <Item>
        <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
        <rasd:Description>Memory Size</rasd:Description>
        <rasd:ElementName>3580MB of memory</rasd:ElementName>
        <rasd:InstanceID>2</rasd:InstanceID>
        <rasd:ResourceType>4</rasd:ResourceType>
        <rasd:VirtualQuantity>3580</rasd:VirtualQuantity>
      </Item>
      <Item>
        <rasd:Address>0</rasd:Address>
        <rasd:Description>IDE Controller</rasd:Description>
        <rasd:ElementName>ideController0</rasd:ElementName>
        <rasd:InstanceID>3</rasd:InstanceID>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:Address>1</rasd:Address>
        <rasd:Description>IDE Controller</rasd:Description>
        <rasd:ElementName>ideController1</rasd:ElementName>
        <rasd:InstanceID>4</rasd:InstanceID>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>
        <rasd:Caption>floppy0</rasd:Caption>
        <rasd:Description>Floppy Drive</rasd:Description>
        <rasd:ElementName>floppy0</rasd:ElementName>
        <rasd:InstanceID>5</rasd:InstanceID>
        <rasd:ResourceType>14</rasd:ResourceType>
      </Item>
        <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:ElementName>disk1</rasd:ElementName>
        <rasd:HostResource>ovf:/disk/vmdisk1</rasd:HostResource>
        <rasd:InstanceID>6</rasd:InstanceID>
        <rasd:Parent>3</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>    
      <Item>
        <rasd:AddressOnParent>1</rasd:AddressOnParent>
        <rasd:ElementName>disk2</rasd:ElementName>
        <rasd:HostResource>ovf:/disk/vmdisk2</rasd:HostResource>
        <rasd:InstanceID>7</rasd:InstanceID>
        <rasd:Parent>3</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>    
       <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:ElementName>disk3</rasd:ElementName>
        <rasd:HostResource>ovf:/disk/vmdisk3</rasd:HostResource>
        <rasd:InstanceID>8</rasd:InstanceID>
        <rasd:Parent>4</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>1</rasd:AddressOnParent>
        <rasd:ElementName>disk4</rasd:ElementName>
        <rasd:HostResource>ovf:/disk/vmdisk4</rasd:HostResource>
        <rasd:InstanceID>9</rasd:InstanceID>
        <rasd:Parent>4</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>  
      <Item>
        <rasd:AddressOnParent>1</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>hostonly</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;hostonly&quot;</rasd:Description>
        <rasd:ElementName>ethernet0</rasd:ElementName>
        <rasd:InstanceID>10</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>2</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>hostonly</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;hostonly&quot;</rasd:Description>
        <rasd:ElementName>ethernet1</rasd:ElementName>
        <rasd:InstanceID>11</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>3</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>nat</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;nat&quot;</rasd:Description>
        <rasd:ElementName>ethernet2</rasd:ElementName>
        <rasd:InstanceID>12</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>4</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>nat</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;nat&quot;</rasd:Description>
        <rasd:ElementName>ethernet3</rasd:ElementName>
        <rasd:InstanceID>13</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
    </VirtualHardwareSection>
  </VirtualSystem>
</Envelope>                                                                                                                  
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Simulate ONTAP 8.1.1 withVirtualBox

Has anyone has success in setting up 2nd node using Simulator 8.2.2 or 8.3.2 on VirtualBox?

 

I had success in setting the 1st node repeatedly but failed on joining 2nd node to the cluster all the times so far. Kept getting the following errors:

 

Enter the name of the cluster you would like to join [c1]: c1

Joining cluster c1

Network set up ................Error: Remote ping test failed. Verify that this node is cabled correctly and
that the cluster interfaces are using ports on the internal cluster network.
To verify, run the ping command from the CLI. For example,
"network ping -lif clus1 -lif-owner node-01 -destination <cluster ip from cluster> -verbose true -show-detail true".

Restarting Cluster Setup

 

When trying network ping command as suggested above, it failed miserably:

 

c1::> network ping -lif clus1 -lif-owner c1-01 -destination 10.10.1.80 -verbose true -show-detail true -count 3
PING 10.10.1.80 (10.10.1.80) from 169.254.17.11: 56 data bytes

--- 10.10.1.80 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

 

 

Is there any requirement for Cluster hearbeat interfaces [e0a,e0b] to be on the same network as the other NICs? In my case I have the followings. Should all NICs be on same network?

 

NIC # 1 --> e0a --> Host-only Adapter --> DHCP (Cluster Heartbeat)

NIC # 2 --> e0b --> Host-only Adapter --> DHCP (Cluster Heartbeat)

NIC # 3 --> e0c --> Host-only Adapter # 2 --> Assigned IP (Cluster Management)

NIC # 4 --> e0d --> Host-only Adapter # 2 --> Open

NIC # 5 --> e0e --> Host-only Adapter # 2 --> Open

NIC # 6 --> e0f --> Host-only Adapter # 2 --> Assigned IP (Node Management)

 

Double and triple check network settings which appear to be fine:

 

Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 6 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0f: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 5 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0e: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 4 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0d: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 3 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0c: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 2 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0b: Link up.
Feb 23 17:12:36 [localhost:snmp.link.up:info]: Interface 1 is up
Feb 23 17:12:36 [localhost:netif.linkUp:info]: Ethernet e0a: Link up.

 

vsim822-c1n1.PNG

 

c1::> net int show

(network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
c1
            cluster_mgmt up/up    10.10.1.80/24      c1-01         e0c     true
c1-01
            clus1        up/up    169.254.17.11/16   c1-01         e0a     true
            clus2        up/up    169.254.210.87/16  c1-01         e0b     true
            mgmt1        up/up    10.10.1.81/24      c1-01         e0f     true
vs1
            c1-01_iscsi_lif_1
                         up/up    10.10.1.85/24      c1-01         e0c     true
            c1-01_iscsi_lif_2
                         up/up    10.10.1.86/24      c1-01         e0d     true
            vs1_admin_lif1
                         up/up    10.10.1.84/24      c1-01         e0e     true
7 entries were displayed.

c1::> net port show
(network port show)
                                      Auto-Negot  Duplex     Speed (Mbps)
Node   Port   Role         Link MTU   Admin/Oper  Admin/Oper Admin/Oper
------ ------ ------------ ---- ----- ----------- ---------- ------------
c1-01
       e0a    cluster      up   1500  true/true   full/full  auto/1000
       e0b    cluster      up   1500  true/true   full/full  auto/1000
       e0c    data         up   1500  true/true   full/full  auto/1000
       e0d    data         up   1500  true/true   full/full  auto/1000
       e0e    data         up   1500  true/true   full/full  auto/1000
       e0f    node-mgmt    up   1500  true/true   full/full  auto/1000
6 entries were displayed.

 

Any insight would be very much appreciated.

 

Thanks,

Hien