This article enhance a little more idea of lab presented here Data ONTAP Simulator 7.3.6. The main difference is that now we try reflect (at least reach a concept) production environment, where we have Active Directory domain and data served to hosts through CIFS, NFS, iSCSI protocols.
Goal
– 2x 7-Mode 8.2.3
– Linux CentOS 7.0 (at least one)
– Windows Server 2008 R2
Prerequisites for NetApp Simulator Lab
NetApp 7-Mode Data ONTAP 8.2.3 Simulator
- Dual core 64-bit Intel® architecture laptop or desktop
- Simulate ONTAP 8.2.x or lower: 2 GB RAM for one instance, 3 GB for two instances.
- 40 GB free disk space per instance of simulator
- Hosts running a 32-bit OS require VT support for Intel® based systems or AMD-V (SVM) for AMD® based systems. The feature must also be enabled in the BIOS if not enabled by default.
- VT support for Intel® based systems
Windows Server 2008 R2
Windows Server 2008 System Requirements
Windows Server 2008 R2 – Download 180 days Trial
CentOS 7.0
CentOS Product Specifications
CentOS 7.0 download
Hypervisor VMware Workstation 11
VMware Workstation 11
Planning our NetApp lab environment
As always solid plan let you do everything smoothly. At below table network configuration is presented. For now we can leave unconfigured intefaces other than e0a
| Name | IP address | Interface | Purpose |
| Gateway | 10.2.0.2 | Vmware | Gateway |
| dc.regmen.com | 10.2.0.40 | local | Windows 2008 Domain Controller, DNS server |
| linux1 | 10.2.0.50 | vif_lin1 | Management server |
| 10.2.0.51 | eno16777736 | “Physical interface” | |
| fas01 | 10.2.0.20 | e0a | NetApp 7-Mode |
| tba | e0b | ||
| tba | e0c | ||
| tba | e0d | ||
| fas02 | 10.2.0.30 | e0a | NetApp 7-Mode |
| tba | e0b | ||
| tba | e0c | ||
| tba | e0d |
Network configuration for VMware Workstation 11
Simple as that.
Windows Server 2008 initial configuration for NetApp 7-Mode lab purpose
For this lab purpose we need to install and configure two roles
- DNS server.
- Active Directory Domain Services.
Network adapter aka Local Area Connection should be configured as static
DNS server installation
DNS server installation is very simple. Just add role, choose DNS Server and push Next. After DNS server and Active Directory Domain Services roles installation, DNS server should be configured for the lab purpose. Check the step after AD installation.
Active Directory Domain Services installation
Below images are presenting installation Active Directory Domain Services role in 6 steps. It’s not require any additional comments. After installation there is no need to make any additional configuration.
DNS server configuration
We can distinguish two common types of zones in DNS server which is forward lookup zone and reverse lookup zone. The first one is responsible for translation from DNS domain names to IP addresses. A concept for reverse lookup zone is quite similar – mapping is organized from IP addresses to DNS domain names.
For our lab you should configure forward lookup zone accordingly. To achieve it look for New Host (A or AAAA)… from context menu at forward lookup zone and enter desired host and its IP address. Make sure you also have checked Create associated pointer (PTR) record for reverse lookup.
Linux CentOS 7.0 installation and configuration – adding linux to Active Directory domain
Fortunately installation is very typical and server version without GUI with CIFS/NFS/iSCSI features should be consider as the most suitable choice.
List of packages that are crucial for laboratory
For network configuration:
NetworkManager.x86_64 1:0.9.9.1-13.git20140326.4dba720.el7 NetworkManager-glib.x86_64 1:0.9.9.1-13.git20140326.4dba720.el7 NetworkManager-tui.x86_64 1:0.9.9.1-13.git20140326.4dba720.el7
CIFS and NFS:
cifs-utils.x86_64 6.2-6.el7 @anaconda libnfsidmap.x86_64 0.25-9.el7 @anaconda nfs-utils.x86_64 1:1.3.0-0.el7 @anaconda nfs4-acl-tools.x86_64 0.3.3-13.el7 @anaconda
iSCSI:
iscsi-initiator-utils.x86_64 6.2.0.873-21.el7 @anaconda iscsi-initiator-utils-iscsiuio.x86_64 6.2.0.873-21.el7 @anaconda libiscsi.x86_64 1.9.0-6.el7 @anaconda lsscsi.x86_64 0.27-3.el7 @anaconda
Active Directory addon:
realmd.x86_64 0.14.6-6.el7 @base
Network configuration
Network configuration should be reflection of planned earlier configuration – host Linux1 and its IP address.
If you didn’t set-up any network during installation – now it is the time. For this purpose we use fantastic NetworkManager CLI/GUI.
Required information:
| Name | IP address |
| Physical interface (eno16777736) | 10.2.0.51 |
| Logical interface (vif_lin1) | 10.2.0.51 |
| Gateway | 10.2.0.2 |
| DNS | 10.2.0.40 |
NetworkManager as nmtui
If you don’t like type too much, then just use nmtui. It brings old fashion graphical interface, where you can easily make required changes.
[linux1 ~]$ nmtui
NetworkManager as nmcli
If you don’t have proper packages so far, now it is the time to install:
yum -y install realmd sssd oddjob oddjob-mkhomedir adcli samba-common
Setup new connection:
[linux1 ~]$ nmcli c a type ethernet con-name vif_lin1 ifname eno16777736 ip4 10.2.0.50/16 gw4 10.2.0.2
Adding DNS:
[linux1 ~]$ nmcli c modify "vif_lin1" ipv4.dns 10.2.0.40
As always to make changes you need restart interface:
[linux1 ~]$ nmcli c down "vif_lin1"; nmcli c up "vif_lin1" Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)
After:
[root@linux1 ~]# nmcli d show GENERAL.DEVICE: eno16777736 GENERAL.TYPE: ethernet GENERAL.HWADDR: 00:0C:29:6B:64:29 GENERAL.MTU: 1500 GENERAL.STATE: 100 (connected) GENERAL.CONNECTION: vif_lin1 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/7 WIRED-PROPERTIES.CARRIER: on IP4.ADDRESS[1]: ip = 10.2.0.50/16, gw = 10.2.0.2 IP4.DNS[1]: 10.2.0.40 IP6.ADDRESS[1]: ip = fe80::20c:29ff:fe6b:6429/64, gw = ::
Joining Linux to Active Directory
First thing is to check whether we can find desired Active Directory domain, so we need discover our domain:
[root@linux1 ~]# realm discover regmen.com regmen.com type: kerberos realm-name: REGMEN.COM domain-name: regmen.com configured: no server-software: active-directory client-software: sssd required-package: oddjob required-package: oddjob-mkhomedir required-package: sssd required-package: adcli required-package: samba-common
When we successfully discovered domain, then it is time to join host to Active Directory domain:
[root@linux1 ~]# realm join regmen.com -v * Resolving: _ldap._tcp.regmen.com * Performing LDAP DSE lookup on: 10.2.0.40 * Successfully discovered: regmen.com * Required files: /usr/sbin/oddjobd, /usr/libexec/oddjob/mkhomedir, /usr/sbin/sssd, /usr/sbin/adcli * LANG=C /usr/sbin/adcli join --verbose --domain regmen.com --domain-realm REGMEN.COM --domain-controller 10.2.0.40 --login-type computer --no-password * Using domain name: regmen.com * Calculated computer account name from fqdn: LINUX1 * Using domain realm: regmen.com * Sending netlogon pings to domain controller: cldap://10.2.0.40 * Received NetLogon info from: dc.regmen.com * Wrote out krb5.conf snippet to /var/cache/realmd/adcli-krb5-BZw733/krb5.d/adcli-krb5-conf-ynGMUJ ! Couldn't authenticate as machine account: LINUX1: Preauthentication failed adcli: couldn't connect to regmen.com domain: Couldn't authenticate as machine account: LINUX1: Preauthentication failed ! Unable to automatically join the domain Password for Administrator: * Required files: /usr/sbin/oddjobd, /usr/libexec/oddjob/mkhomedir, /usr/sbin/sssd, /usr/bin/net * LANG=C LOGNAME=root /usr/bin/net -s /var/cache/realmd/realmd-smb-conf.KT5U0X -U Administrator ads join regmen.com Enter Administrator's password:DNS update failed: NT_STATUS_INVALID_PARAMETER Using short domain name -- REGMEN Joined 'LINUX1' to dns domain 'regmen.com' No DNS domain configured for linux1. Unable to perform DNS Update. * LANG=C LOGNAME=root /usr/bin/net -s /var/cache/realmd/realmd-smb-conf.KT5U0X -U Administrator ads keytab create Enter Administrator's password: * /usr/bin/systemctl enable sssd.service ln -s '/usr/lib/systemd/system/sssd.service' '/etc/systemd/system/multi-user.target.wants/sssd.service' * /usr/bin/systemctl restart sssd.service * /usr/bin/sh -c /usr/sbin/authconfig --update --enablesssd --enablesssdauth --enablemkhomedir --nostart && /usr/bin/systemctl enable oddjobd.service && /usr/bin/systemctl start oddjobd.service * Successfully enrolled machine in realm
Simple check to verify connection between linux host and AD domain:
[root@linux1 ~]# id Regmen\\Administrator uid=1740600500(administrator@regmen.com) gid=1740600513(domain users@regmen.com) groups=1740600513(domain users@regmen.com),1740600520(group policy creator owners@regmen.com),1740600518(schema admins@regmen.com),1740600572(denied rodc password replication group@regmen.com),1740600519(enterprise admins@regmen.com),1740600512(domain admins@regmen.com)
Make a switch to Active Directory domain user:
[root@linux1 ~]# su - Regmen\\Administrator Creating home directory for administrator@regmen.com. [administrator@regmen.com@linux1 ~]$ pwd /home/regmen.com/administrator
That is all for now from Linux host perspective. It is time to configure both Data ONTAP Simulator 8.2.3
7-Mode Data ONTAP 8.2.3 Simulator – first look
First of all you have to distinguish two simulators to use different pipes. NetApp Data ONTAP Simulator treat this as serial connection to the device console. Also path of this pipe is related to directory where you unpack Data ONTAP Simulator.
In our case we unpack our simulators, where one is located in fas01 and the other one is in fas02 directory.
- \\.\pipe\fas01-cons
- \\.\pipe\fas02-cons
Installation shouldn’t be a trouble. After you start your Data ONTAP simulator, wait for prompt Press CTRL+C for Boot Menu. When you press requested combination your eyes will see Boot Menu, from which one you should choose option 4 stands for:
4) Clean configuration and initialize all disks.
The rest of configuration is on example FAS02 Data ONTAP simulator instance.
The setup command will rewrite the /etc/rc, /etc/exports,
/etc/hosts, /etc/hosts.equiv, /etc/dgateways, /etc/nsswitch.conf,
and /etc/resolv.conf files, saving the original contents of
these files in .bak files (e.g. /etc/exports.bak).
Are you sure you want to continue? [yes] yes
NetApp Release 8.2.3 7-Mode: Thu Jan 15 21:30:45 PST 2015
System ID: 4082368508 (fas02)
System Serial Number: 4082368-50-8 (fas02)
System Storage Configuration: Multi-Path
System ACP Connectivity: NA
slot 0: System Board
Model Name: SIMBOX
Processors: 2
Memory Size: 1599 MB
Memory Attributes: None
slot 0: 10/100/1000 Ethernet Controller V
e0a MAC Address: 00:0c:29:94:78:d7 (auto-1000t-fd-up)
e0b MAC Address: 00:0c:29:94:78:e1 (auto-1000t-fd-up)
e0c MAC Address: 00:0c:29:94:78:eb (auto-1000t-fd-up)
e0d MAC Address: 00:0c:29:94:78:f5 (auto-1000t-fd-up)
Please enter the new hostname [fas02]:
Do you want to enable IPv6? [n]:
Do you want to configure interface groups? [n]:
Please enter the IP address for Network Interface e0a [10.2.0.30]:
Please enter the netmask for Network Interface e0a [255.255.0.0]:
Please enter media type for e0a {100tx-fd, tp-fd, 100tx, tp, auto (10/100/1000)} [auto]:
Please enter flow control for e0a {none, receive, send, full} [full]:
Do you want e0a to support jumbo frames? [n]:
Please enter the IP address for Network Interface e0b [10.2.0.31]: 0.0.0.0
Please enter the IP address for Network Interface e0c [10.2.0.32]: 0.0.0.0
Please enter the IP address for Network Interface e0d [10.2.0.33]: 0.0.0.0
Please enter the name or IP address of the IPv4 default gateway [10.2.0.40]: 10.2.0.2
The administration host is given root access to the filer's
/etc files for system administration. To allow /etc root access
to all NFS clients, enter 'all' below.
Please enter the name or IP address of the administration host [linux1]:
Please enter the IP address for linux1 [10.2.0.50]:
Please enter timezone [CET]:
Where is the filer located? [Wroclaw]:
Enter the root directory for HTTP files [/vol/vol0/home/http]:
Do you want to run DNS resolver? [y]:
Please enter DNS domain name [dc.regmen.com]: regmen.com
You may enter up to 3 nameservers
Please enter the IP address for first nameserver [10.2.0.40]:
Do you want another nameserver? [n]:
Do you want to run NIS client? [n]:
The Shelf Alternate Control Path Management process provides the ability
to recover from certain SAS shelf module failures and provides a level of
availability that is higher than systems not using the Alternate Control
Path Management process.
Do you want to configure the Shelf Alternate Control Path Management interface for SAS shelves [n]:
The initial aggregate currently contains 3 disks; you may add more
disks to it later using the "aggr add" command.
After configuration you can login to the simulator with password that you established. To the same for both Data ONTAP simulator instances.
Building lab – next steps?
After all above steps, you have configured clean environment, where you can practice many concepts. In next articles you find explanation about several ONTAP features and learn what concepts can be practiced at presented lab.