Performing firmware and OS updates for a Clustered ONTAP environment is different from performing the same tasks in a 7-Mode environment. In 7-Mode, the easiest way of uploading the necessary files to the controllers was a simple file copy via CIFS or NFS. In cDOT, you don’t have this option for the cluster. Additionally, if you have a 4-node or larger cluster, you also have the cluster interconnect switches to contend with.
The options for uploading the necessary files to the cluster are via HTTP, SFTP or SCP. Likewise, the options for uploading the necessary files to the cluster interconnect switches are via SFTP or SCP.
If you do not already have a dedicated utility system set up for HTTP/SFTP services, the following are quick methods for setting up HTTP or SFTP on your local workstation.
Microsoft users have a few options on how to set up web services. However, there are two easy, quick, simple, and more importantly, free utilities that are recommended:
- Mongoose Simple Web Server – is an utility that all you have to do is place it and the files that you want to distribute in the same directory and double-click. It will immediately open up a browser page of http://<your IP address>:8080 (8080 is the default port) and all of the files are there for retrieval. When you have finished uploaded the files needed to the cluster(s) you exit the program by clicking on the icon in the system tray and selecting exit.
- Solarwinds SFTP Server – is another utility that many network administrators have been using for years to transfer files to and from network devices.
OS X has builtin utilities for both web services and TFTP services. Here are the procedures for setting up both:
Python Simple HTTP Server
Launch the Terminal application in OS X and, from the Bash shell, change directory to your home directory, if not already there.
Create a directory called Sites.
You can now download the files you need and save to the Sites folder.
Back in the Bash shell, change directory to Sites and list the directory contents.
NOTE: You may need to change the permissions on the files within.
From within that directory, launch the Python HTTP server.
NOTE: If you are using Python3 and if you try to start the SimpleHTTPServer, then you will get the error like No module named SimpleHTTPServer. It is because it is merged with http.server module. You can use the below command to run python http server in Python 3.
The files that you have in your Sites directory are now available to be uploaded to the cDOT cluster(s) via http://<your IP address>:8080/<filename>.
Once you have completed uploading the files to the cluster(s), from the Bash shell, hit Control-C and this will stop the HTTP server.
OS X has a built-in TFTP server that can be managed either via a GUI, TFTP Server v3.5.1, or CLI. However, depending on the version of OS X you are running, the GUI front end may not work. As such, here is the process of launching it from the Terminal app and linking it to the same Sites directory that is mentioned above for the simple HTTP server.
The full procedure for setting up the TFTP server can be found here at Run a TFTP Server for Network Device Setups…on Mac OS X, however the following is an abridged version:
Launch the Terminal application and from the Bash shell, start the TFTP daemon.
This launches the TFTP daemon with the default tftpboot path of
You can confirm it is running via the
When you have finished transferring all of the files needed, unload the TFTP daemon and verify that it is not running.
The default tftpboot path (
/private/tftpboot), in earlier versions of OS X, allowed changes. However, enhanced security in OS X El Capitan, and later, makes changing the tftpboot path more difficult. By doing the following, you can create a symlink to a directory where you have full control over the files (i.e. Sites).