Data ONTAP Simulator 7.3.6 – simple lab

First steps are always the most painful so today I discuss initial configuration for Data ONTAP 7-Mode in 7.3.6 version. Why so old, someone can ask. I hasten to reply, because reason is very simple. This is the last version of Data ONTAP simulator, which does not require any abstract hardware. It is sufficient for simple lab especially when you want to show some stuff about storage to not so storage audience. This simulator is still powerful in terms of connection between theory and practice. For everyone it’s a lot easier to understand fundamental concepts when they can be seen in practice.

Goal
– two instances of 7-Mode,
– 2x CentOS, one management server for simulator and the second as typical host.

Prerequisites for NetApp Simulator Lab

NetApp 7-Mode Data ONTAP 7.3.6 Simulator:
Intel® processor-based PC, network card, 128 MB main memory minimum (256 MB recommended), 250MB free hard disk space (minimum)
Data ONTAP Simulator download

CentOS 6.6
CentOS Product Specifications
CentOS 6.6 download – DVD1 is enough

And to virtualize it we use VirtualBox
Oracle VM VirtualBox download

Planning our NetApp lab environment

After all there is not much planning around here. Our lab is simplified as much as possible. Below table and schema are presented below.

Name IP address Interface Purpose
Gateway 10.1.1.2 VirtualBox Gateway
linux1 10.1.1.20 eth0 Main
10.1.1.21 eth1 For simulator
linux2 10.1.1.30 eth0 Main
10.1.1.31 eth1
fas01 10.1.1.10 ns0 Management port
10.1.1.11 ns1
fas02 10.1.2.10 ns0 Management port
10.1.2.11 ns1
ontap simulator
NetApp 7-Mode Data ONTAP Simulator schema

Bringing to life

VirtualBox

Nothing fency, but few things should be meet:
– Management server: 8GB dynamically allocated vdisk, 2GB RAM, 2x Network adapters Promiscuous Mode – that’s important.
– Desktop: 5GB dynamically allocated vdisk, 2GB RAM, 2x Network adapters.
– General Network settings: Host-Only Network adapter configured as Gateway.

Management server for NetApp simulator

Installation it’s not complicated. But you have to remember to select needed packages. During installation choose Virtual Host as option and Customize Now checkbox and add following packages:
– Compatibility libraries from Base System, because you will not run 32bit sim without that.
– iSCSI Storage Client from Base System.
– Network File System Client from Base System.

Desktop

But you have to remember to select needed packages. During installation choose Desktop as option and Customize Now checkbox and like previously make sure that you have important packages:
– Compatibility libraries from Base System, just in case.
– iSCSI Storage Client from Base System.
– Network File System Client from Base System.

Filers

Do SSH to Management Server from Desktop. Mount downloaded sim image and copy content to newly created directory.
[root@linux1 ~]# mkdir /mnt/cdrom
[root@linux1 ~]# mkdir /simpack
[root@linux1 ~]# mount /dev/sr0 /mnt/cdrom
[root@linux1 ~]# cp –r /mnt/cdrom /simpack

After that we can start with installation:
[root@linux1 ~]# cd /simpack/cdrom
[root@linux1 ~]# ./setup.sh

Initial configuration. You can safely accept default options besides those ones indicated below:
[root@linux1 ~]# cd /simpack/cdrom
[root@linux1 ~]# ./setup.sh

Now to make it easier, just copy /fas01 to /fas02
[root@linux1 ~]# cp -r /fas01 fas02

Go to fas01 and run:
./runsim.sh

and then make initial configuration of filer:

Please enter a new hostname[]: fas01
Do you want to enable IPv6? [n]: [Enter]
Do you want to configure virtual network interfaces? [n]: [Enter]
Please enter the IP address for Network Interface ns0 []: 10.1.1.10
Please enter the Netmask for Network Interface ns0 [255.0.0.0]: 255.255.0.0
Please enter media type for ns0 {100tx-fd, auto} [auto]: [Enter]
Please enter the IP address for Network Interface ns1 []: 10.1.1.11
Please enter the Netmask for Network Interface ns1 [255.0.0.0]: 255.255.0.0
Would you like to continue setup through the web interface? [n]: [Enter]
Please enter the name or IP address of the IPv4 default gateway: 10.1.1.2
Please enter the name or IP address of the administration host: 10.1.1.30
Please enter timezone [GMT]: CET
Where is the filer located? []: PWr
What language will be used for multi-protocol files (Type ? for list)?: [Enter]
Do you want to use DNS resolver? [no]: [Enter]
Do you want to run NIS client? [no]: [Enter]
Do you want to configure the Shelf Alternate Control Path Managament interface for SAS shelves? [no]: [Enter]
Setting the administrative (root) password for fas01 ...
New password: [Enter you password here]
Do you want to make the system visible via WINS? [n]: [Enter]
Select (1) Multiprotocol filer
Enter the password for the root user []: [Enter]
Keep the default name for CIFS server.
Choose (4) /etc/passwd and/or NIS/LDAP authentication.
What is the name of the Workgroup? [WORKGROUP]: [Enter]

After you login to the console halt the system.
fas01> halt

Now go to /fas02 and run:
./setup.sh
Use defaults besides simulator network interface, which should be eth2 and then go with
./runsim.sh
After you reach console halt the filer:
fas02> halt

Running NetApp simulator in virtualized environment

Steps:
1) Open Oracle VM VirtualBox manager and run the linux2 (10.1.1.30).
2) Open terminal and do ssh to linux1 (10.1.1.20) and run commands:
nohup /fas01/runsim.sh &
nohup /fas02/runsim.sh &
Now both filers running as background process at linux1.
3) From linux2 check connectivity to both filers:
ssh root@10.1.1.10
ssh root@10.1.2.10
3.1) If you have connection refused then just go to the filer from linux1 and run command:
fas01> secureadmin setup ssh
Accept all defaults. Check if below options are set-up to on:
fas01> options ssh.enable
fas01> options ssh2.enable
4) Halt filers.
5) Shutdown linux1 and linux2.
6) Do a snapshot from Oracle VM VirtualBox manager for both linux1 and linux2.

Running NetApp simulator in virtualized environment

To run in the background:
screen /fas01/runsim.sh
screen /fas02/runsim.sh

Every time before closing the system, you have to halt the filers with the halt command to avoid inconsistency.

Tip: To detach screen window just press CTRL-A + D. After that you go back to the linux console. If you want retrieve window then just type:
[root@linux1 ~]# screen -r [window-name]

Starting with system boot

Create an entry in the /etc/init.d/ folder for the correct runlevel as root.
linux:/etc/init.d/rc3.d # cat S99startsim
cd /fas01
screen ./runsim.sh
linux:/etc/init.d/rc3.d #

Leave a Reply

Your email address will not be published. Required fields are marked *