HTTP web access
- Several NetApp products may require an HTTP server to retrieve files for installation, setup, or configuration
- This may include installing OS upgrades, system firmware, or other essential packages
- These web servers are not owned or supported through NetApp
- Other HTTP servers exist beyond these ones that you may wish to explore
|HFS ~ HTTP File Server||Windows||https://www.rejetto.com/hfs/?f=dl|
|Mongoose Web Server||Windows, Mac, or Linux||https://mongoose.ws/|
|Abyss Web Server||Windows, Mac, or Linux||https://aprelium.com/abyssws/download.php|
- Microsoft Internet Information Services (better know as IIS) - although neither "free" nor open-source - is often already readily available in most WIndows environments. Be aware that you may need to add "*.*" (star-dot-star) to the MIME type configuration, otherwise files that lack an extension, such as "kernel" used when netbooting, will not be served. This article on stackoverflow provides some useful information.
- Also be aware that some server ports may already be in use by the OS, or administrative restrictions forbid access to privileged ports (1-1023). If that is your situation you will need to configure the web server to listen on another port (for example, 8080), and then remember to specify that port in the URL.
- When specifying the host to connect to, it is often better to specify the IP address in the URL rather than the FQDN. This will help eliminate one source of connectivity problems (DNS reachability/name resolution).