NCDA Lab Configuration Part 3: ONTAP Simulator VMs

As I previously discussed, to download the ONTAP Simulator you’ll need to have a NOW account.  Here’s hoping that they’ll open this up for all so that other people can take a look at the ONTAP software and try it out. It comes in both 7-mode and Cluster mode versions.  The ONTAP Simulator that we’ll be using is the ONTAP 8.1.1 7-mode simulator.  Each simulator comes with 28 drives in 2, 14 drive shelves with each drive equal to 1GB each with the ability to expand to 56 drives. 

I’m not going to go through how to download and add the simulator to Workstation.  That should be pretty straightforward.  Let’s list out the changes that need to take place to setup the ONTAP simulator.  
  • Boot up the ONTAP Simulator and login to the device
  • The ONTAP Simulator has one very clear flaw.  The System ID is always the same.  This comes into play when you want to use replication technologies like SnapMirror.  SnapMirror will not work if both of the Simulators have the same System ID.  So we’ll have to change it when we build the second simulator.  I just took the first simulators System ID and incremented it by 1.  Note:  you only need to perform this step on the second Simulator. 
  • Zero the current disks and configure the system
  • Verify connectivity and check disks
  • Configure appropriate network connectivity for lab
Simulator Configuration
Before starting the VM, change NIC1 and NIC2 to use the same VM network (most likely for VIF configurations in later labs)
  • Boot VM
  • When prompted to access the Boot menu press CTRL+C
  • Press 4 to Zeroize and clean drives (the link suggests that you need to assign ownership.  What I’ve found is that that is the case if you’re not setting up the simulator from scratch.  If you have an existing simulator that is already configured and usable, you need to perform the disk assign –o <simulator name> commands. 
  • Confirm with y
  • Confirm with y
  • System will reboot
Allow the wipe and disk assign process to take place.  When the system finishes zeroizing the disks and assigning ownership, it will then move into configuration mode. 
  • Enter the hostname of the simulator (I named mine ONTAP1/2)
  • Take default on IPv6 of no
  • Take default on interface groups of no
  • Enter the IP address of the e0a interface of 192.168.175.10
  • Enter the Subnet Mask of 255.255.255.0
  • Take default on media type of auto
  • Take default on flow control of full
  • Take default on jumbo frames of no
  • Enter the IP address of the e0b interface of 192.168.175.11
  • Enter the Subnet Mask of 255.255.255.0
  • Take default on media type of auto
  • Take default on flow control of full
  • Take default on jumbo frames of no
  • Don’t enter an IP for e0c
  • Don’t enter an IP for e0d
  • Take the default on web interface setup of no
  • Enter the IP address of the default gateway of 192.168.175.51(our router’s IP address)
  • Don’t enter the IP address for an administrative host
  • Enter the hours of the timezone from GMT of -6 (Chicago)
  • Enter the name of where the filer is located of Chicago
  • Take the default for root directory of /vol/vol0/home/http
  • Take the default of DNS resolver of no
  • Take the default of NIS client of no
  • Press Enter
  • Take the default for ACP of no
  • Allow VM to finish configuration
Once I’ve established an IP address that I can connect to on the VM, I switch from the VMware console window over to an SSH client.  It provides more screen room to work with when running commands.  
The second shelf of disks will be unassigned.  At this point there’s no real need to assign them to the aggregate that’s currently there.  When we get to disk assignment during labbing, this will come in handy as good practice to expand an aggregate from both the CLI and from OnCommand System Manager.  To configure the second VM, simply perform the same steps above and use IP addresses similar to the ones above but on the 10.10.10.x network.  You’ll need to make sure to follow the steps below for changing the System ID as well.  
System ID Change (Only necessary on the second simulator)
After you’ve added the ONTAP Simulator to VMware Workstation, boot the machine.  When the VM boots, you’ll be presented with a dialogue to boot or any key for a command prompt. Hit CTRL+C so we can boot into the loader and change the System ID.   Again, you only need to perform these steps on the second simulator.  The first simulator will always be System ID 4061490311.  Following this link, we change the System ID.  
  • Run the command – set SYS_SERIAL_NUM=4061490312
  • Run the command – set bootarg.nvram.sysid=4061490312
  • Run the command – boot
  • Proceed with the same steps as above for configuration

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s