Hi John!
>>> 1. Do I need to boot of the floppies again to start this procedure as we have no working OS on the filer ?
Yes. Right now we have no boot blocks, so you'll need to use them one more time going into this final operation.
>>> 2. After running the setup off the floppies, will I be able to connect to the filer_ipaddress:/etc from my windows ?
Sort of. After setup you'll have to setup cifs. This is very infrastructure specific, so the instructions I'm including below are for setting it up in the most generalized sense. I ran through it on my 960 and it worked, so it's had at least a bit of sanity checking 🙂
>>> 3. So, I just double click the 633_setup_a.exe file and that is it?
A bit more intensive than that I'm afraid,
Once the basic setup has completed (hostname, IP address, etc), you'll need to license CIFS and run 'cifs setup'. The install I ran was under 7.2.4, but it should be relatively similar (it hasn't changed much in the six years I've been using it). In step 2 below, I choose 'workgroup mode' when choosing authentication. This is going to be infrastructure dependent to your site. Choosing 'workgroup' will allow you to use the rest of the flow below to install the system files off of your laptop. For now, I would recommend going that route as you can always change it later by rerunning 'cifs setup'.
1) License cifs.
filer> license cifs=abcdefghi
A cifs license has been installed.
filer> Wed Aug 20 12:43:14 EDT [filer: rc:notice]: cifs licensed
filer>
2) Run cifs setup to enable cifs.
filer> cifs setup
This process will enable CIFS access to the filer from a Windows(R) system.
Use "?" for help at any prompt and Ctrl-C to exit without committing changes.
Your filer does not have WINS configured and is visible only to
clients on the same subnet.
Do you want to make the system visible via WINS? [n]:
This filer is currently configured as a multiprotocol filer.
Would you like to reconfigure this filer to be an NTFS-only filer? [n]:
The default name for this CIFS server is 'filer'.
Would you like to change this name? [n]:
Data ONTAP CIFS services support four styles of user authentication.
Choose the one from the list below that best suits your situation.
(1) Active Directory domain authentication (Active Directory domains only)
(2) Windows NT 4 domain authentication (Windows NT or Active Directory domains)
(3) Windows Workgroup authentication using the filer's local user accounts
(4) /etc/passwd and/or NIS/LDAP authentication
Selection (1-4)? [1]: 3
What is the name of the Workgroup? [WORKGROUP]:
CIFS - Starting SMB protocol...
Welcome to the WORKGROUP Windows(R) workgroup
CIFS local server is running.
filer>
filer> Wed Aug 20 12:46:03 EDT [filer: nbt.nbns.registrationComplete:info]: NBT: All CIFS name registrations have completed for the local server.
3) Verify that a share has been created for C$
filer> cifs shares
Name Mount Point Description
---- ----------- -----------
ETC$ /etc Remote Administration
BUILTIN\Administrators / Full Control
HOME /vol/vol0/home Default Share
everyone / Full Control
C$ / Remote Administration
BUILTIN\Administrators / Full Control
filer>
4) Map to a *drive letter* on your Windows machine using 'administrator' as your username and root's password as the 'password'
5) Verify via the net use command
Y:\>net use
New connections will not be remembered.
Status Local Remote Network
------------------------------------------------------------------------------
OK Y: \\192.168.75.10\C$ Microsoft Windows Network
6) Install system files
Double click on the 6.3.3 setup.exe file
This will bring up a WinZip self-extractor box stating that you'll need to have C$ mapped as administrator.
Click 'ok'
It will prompt you with <drive>:\etc
Replace <drive> with the drive letter you mapped C$ to. In the example above, I replace it with 'Y' so the box will read:
Unzip to folder: Y:\etc
This will unzip the system files to the /etc directory of the filer. Upon completion it may ask you if you wish to run inst_perm.bat. Click 'yes' (this will set the correct permissions on the files in /etc should they have been overwritten.
Once this operation has completed (takes roughly a minute), log into the filer and issue 'download'. This will load the boot blocks on the FCAL disks with the kernel.
filer> download
download: Reminder: upgrade both the nodes in the Cluster
download: You can cancel this operation by hitting Ctrl-C in the next 6 seconds.
download: Depending on system load, it may take many minutes
download: to complete this operation. Until it finishes, you will
download: not be able to use the console.
Wed Aug 20 12:53:47 EDT [filer: download.request:notice]: Operator requested download initiated
download: Downloading boot device
..........................................
download: Downloading boot device (Service Area)
......................................................
download: Downloading disks: .....done
download: boot blocks successfully copied to disk(s)
filer> Wed Aug 20 12:58:40 EDT [filer: download.requestDone:notice]: Operator requested download completed
7) Reboot
Once the above is complete, it is safe to reboot the filer
filer> reboot
The filer should boot back up running 6.3.3.
