Continuing on from
the previous post - How
to Setup NetApp SnapDrive for Windows with VMware VMDKs on NFS Datastores
- we extend this to
NFS datastores presented from a vFiler. Also, here we are not using RPC since
our vFiler is not domain joined (cifs setup has not been run - but we do have
DNS configured!)
Part 1: Our
vFiler Configuration
# Creating the
vFiler
vol create v_vflonntp01_01 -s none aggr0 100g
vfiler create vflonntp01 -i 10.0.1.125 /vol/v_vflonntp01_01
# Changing to the
vFiler context
vfiler context vflonntp01
## All the
following bits are done in the vfiler context
##
vflonntp01@LONNTP01>
# Creating a
Qtree and export to our VMware Hosts
qtree create /vol/v_vflonntp01_01/q_vflonntp01_01
exportfs -p rw=10.0.0.0/16 /vol/v_vflonntp01_01/q_vflonntp01_01
# We will
configure vFiler access over HTTP* in SDW
options httpd.admin.enable on
# Create a user
useradmin user add local_sdw_svc -g Administrators
# This next bit
is only to enable SSH (PuTTY) access to our vFiler so we can test our
credentials
options ssh2.enable off
secureadmin setup ssh
options ssh2.enable on
*vFiler access is
only possible over HTTP in the vFiler context - HTTPS is not an option. Why?
options httpd.admin.ssl.enable is only an option in the vfiler0 context!
Part 2:
Configuration of the VSC
The vFiler has already been added to DNS. We add the
vFiler as a new storage system in the ‘Virtual Storage Console - Backup and
Recovery’ section using its DNS name as below:
Image: vfiler
(vflonntp01) added to SMVI/VSC
Part 3:
Configuration of SnapDrive for Windows
Not that it is absolutely necessary (but useful practice)
- here we have created a local administrator account on our server called ‘local_sdw_svc’
with the same password as we configured when running the useradmin user add
local_sdw_svc command earlier. The SnapDrive and SnapDrive Management Services
are set to use the local account as below.
Image: SDW services
using local admin account with same name as account created on vFiler
In the SnapDrive for Windows MMC, and Transport Protocol
Settings:
Default tab -
unticked ‘Enable’
Storage Systems
tab - added in our vFiler using HTTP and the local account credentials
Image: SDW Transport
Protocol Settings - Default tab with ‘Enable’ unchecked
Image: SDW Transport
Protocol Settings - Storage Systems tab
And proof that our VMDKs on NFS datastores presented by a
vFiler are showing in SnapDrive for Windows!
Image: SDW - VMDKs
on NFS via a vFiler
A Question
Q: If it possible
to use RPC with a vFiler?
A: Yes. If cifs setup has been run on the vFiler as in the preceeding
post here,
then RPC will work with a vFiler in just the same way. With DNS resolution
etcetera … all configured correctly, there is no need to specify the vFiler as
a Storage System under Transport Protocol Settings, and the Default ‘Use RPC’
can be enabled.
An Error
Not the most useful insightful error! The below error was received whilst
I was playing around with RPC and HTTPS to my vFiler (without having CIFS setup
run, so the RPC was always doomed!) The error message could just say ‘Please
use HTTP!’
Image: Error “Unable to
modify or add transport protocol. Failed to get Data ONTAP version …”
Comments
Post a Comment