System setup can create the cluster, but because the sims on your laptop are not capable of forming an HA pair you can only create a single node cluster. The disks aren't shared, there's no HA interconnect, etc. This is more like the old version of that lab, where system setup created a single node cluster.
... View more
In Clustered Data ONTAP we can issue systemshell commands from the cluster shell at the diag priviledge level. So adding disks only takes 3 commands: set diag
systemshell local "cd /sim/dev;sudo vsim_makedisks -t 35 -n 14 -a 2"
reboot local In this example, I've added 14 (-n 14) 500MB SSDs (-t 35) on adapter 2 (-a 2). There are 4 adapters numbered 0-3, but 0 and 1 are fully populated by default. That leaves adapters 2 & 3 available for more disks or SSDs, each of which can take up to 14 disks. If your simulated cluster has more than one node, replace 'local' with '-node <node name>' to make sure the disks are created on the correct node. To get a list of valid disk types: set diag
systemshell local vsim_makedisks -h The reboot is inconvenient, but avoidable. Hot adding disks takes a few more steps. More on that later.
... View more
Its in the install guide, which is one of the links you scroll past on the download page before you get to the license aggreement: http://mysupport.netapp.com/NOW/download/software/nfs_plugin_vaai/1.0.21/
... View more
This will list all the vservers and tell you which ones have it disabled: vserver nfs show -fields vstorage Then turn it on where appropriate: vserver nfs mod -vstorage enabled -vserver <vserver name>
... View more
Network adapter and Network adapter 2 correspond to e0a and e0b, which will be used for the cluster network. These should be "host-only" since they are internal to the cluster. Network adapter 3 and Network adapter 4 correspond to e0c and e0d. These could be bridged, depending on what (if any) network your computer is connected to. I would use the "nat" network, and assign IP address from the nat VM network to node management and cluster management. You can get these by looking at your IP settings for VMNET8 in ifconfig/ipconfig on the host. If you use bridged, assign address from the network you are bridged to. Both nodes should be identically configured from a network standpoint.
... View more
There is a procedure to recover from that scenario. It involves setting a hidden option to reenable the aggr destroy command in the nodeshell. Try KB 1013046
... View more
That could be interesting. I don't run a blog though. Maybe I should start. It would probably take a series of posts. To get through it you need an ESX server, an NFS server, and a pretty good comfort level in the systemshell.
... View more
No documentation that I could find. To get it working I had to solve a few puzzles. How to make NVRam persist accross reboots, how to get 2 VMs shared access to the simdisks, and how to get NVRam mirroring working accross nodes. More accurately, I had to figure out how they solved them. Ultimately it involved moving the simdisks to an nfs share, a number of settings in the vloader, and using the VMCI bus to simulate RDMA. Its a complex config, and it only works on certain versions of VMware.
... View more
The default vmdk on which the sim disks reside is 250gb. If you want more than ~220gb of sim disks you need to use a larger vmdk. Then you can build it with a bunch of 9GB drives and max out the capacity at ~500GB.
... View more
Th cluster management and node management IP addresses are for management only. Only data lifs belonging to the SVM can be used for data access, and they can only access data on that SVM.
... View more
if you mean the alpha numeric platform key, the model is derived from the key, so probably not. Edge-T and Edge_cmode are different models/products/platform keys.
... View more
Serial over Network is possible for Fusion. Its not in the GUI, so you have to edit the .vmx after import. serial0.present = "TRUE" serial0.fileType = "network" serial0.fileName = "telnet://0.0.0.0:2300" serial0.network.endPoint = "server" serial0.startConnected = "TRUE" Then telnet local host on port 2300.
... View more
Procedurally it's the same. 7MTT, etc to move the data from the 7mode controller to the cluster mode controller. The pain point is the license. Unlike physical controllers which can be switched between modes, the VSA mode is model dependent so it requires a different platform key. They'll need to buy new licenses and build up new edge controllers, then execute a 7toC migration.
... View more