Updated Date: 07/07/2009
This Release Note documents version 2.0.1 of the F5 Data Manager.
The documentation is available from the following locations:
You can install and run Data Manager on any Microsoft® Windows® platform that meets the following set of minimum requirements:
Supported browsers for accessing the Data Manager GUI:
Data Manager supports the automatic generation of configuration files suitable for uploading to all F5 Acopia switch models. You can use the configuration files generated on switches running FFNOS 3.x and above. FFNOS 3.x is required because the generated Data Manager configuration files implement support for the following FFNOS 3.x features:
The File System Inventory Module may be used to inventory an ARX VIP from any FFNOS version.
Using SSH and TELNET, Data Manager supports discovery of configuration information and use of the File System Inventory Module on the following file servers:
Protocols: NFS, CIFS.
Protocols: CIFS, NFS.
F5 Data Manager v2.00.001 supports the discovery of NetApp Vfilers.
F5 Data Manager v2.00.001 provides enhanced support for Microsoft Windows Clustered File Servers. In addition, Data Manager v2.00.001 provides enhanced support for localized Microsoft Windows distributions. Microsoft Windows provides localized versions of its Windows operating system. For Data Manager, each distribution must be qualified separately. Currently, Data Manager provides support for the following language distributions: Japanese, Simplified Chinese, Korean, German, Czech, Russian.
When upgrading to a new version of Data Manager, follow these steps:
C:\Program Files\F5 Networks\Data Manager
Since Data Manager starts as a system service, it does not have access to drive mounts by a user account. If space on the local Data Manager machine is inadequate for storing the statistics files and report files that result from file system inventories, you will need to store these files in a separate location.
Workaround: Use the following procedure to change the default location for storing these files:
The next time you save a statistics or report file from Data Manager, the file should be stored in the new location.
Note that if you reboot your system or restart Data Manager through the Start menu, you will need to readjust the Log On credentials as outlined above.
In the second page of the Create ARX Configuration wizard, the user is asked to select protocols for the configuration about to be created (NFS, CIFS, NFS and CIFS, or Multi-protocol). The wizard is asking for the user's intent. The protocols selected then drive what the wizard shows in subsequent pages (import paths, AD credentials, ARX configuration options).
ACL warnings appear in the discovery log as "not supported." The customer receives these warnings even though the storage can be mounted and accessed from an ARX.
For most of the NFS ACL option warnings there is a general explanation. Many of these flagged options are associated with changing the filer's behavior on a per client basis and are not associated with client authorization and access. These behavioral options are not implemented on the ARX and therefore will not be enforced by the ARX. Secondly, since the ARX is acting as a proxy between the file server and the client machine, the file server cannot distinguish between different client machines.
For example, suppose there are 2 different clients for an NFS export, 1 client has an option and the other does not. The ARX as a proxy does not distinguish between those clients and appears to the filer as a single client. So, both clients will get the same option setting.
To provide increased security, Data Manager now requires SSL. When you open a browser and enter a URL, be sure to specify a secure HTTP connection in the following format:
<IP-ADDRESS> is either the full IP address or hostname of the host where Data Manager is running (localhost if you are running Data Manager on your local host).
<PORT-#> is the application port number assigned to Data Manager during the installation process (default: 443).
The default URL is HTTPS://localhost:443.
You can specify an alternative port number during the installation process or from the General Settings page. If you change the port number, change your URL accordingly:
In addition, although Data Manager does not ship with a keystore file, it generates one on installation by invoking the following command.
"%JAVA_HOME%"\bin\keytool.exe -genkey -alias tomcat -keyalg RSA -dname "CN=%COMPUTERNAME%" -keypass changeit -storepass changeit -keystore "%FFNM_INSTALL%"\tomcat\conf\.keystore -validity 360
You can learn more about keytool at: Key and Certificate Management Tool documentation.
The command relies on you having defined the following environment variables:
On installation, Data Manager creates a basic certificate that lasts 360 days. You can use this certificate to get started using Data Manager securely. You can replace the Data Manager certificate with your own self-signed certificate which you can either add to the existing keystore or add to your own newly-created replacement keystore. If you do not create your own certificate and allow the default Data Manager certificate to expire, you will need to generate a new certificate or reinstall Data Manager.
As part of the installation procedure, you can set the password for logging in to F5 Data Manager and you can also change the default port number. The default password is password and the default port number is 443.
The following items are known issues in the current release. For issues that are being tracked on the F5 Acopia internal database, note the tracking numbers that appear in parentheses.
Some file servers may not automatically prompt for a username during a TELNET or SSH connection attempt. Entering a username when using the Data Manager Discovery wizard will cause the discovery to fail.
Workaround: If this occurs when performing a discovery of these file servers using the File Server Discovery wizard, leave the username field blank and simply specify the password.
In some cases when using SSH to discover a Network Appliance file server, the discovery can take longer than normal. This is because F5 Data Manager is issuing connection retries for a particular class of connection issues. (The default connection timeout is 60 seconds.).
For EMC file servers, F5 Data Manager will not discover partially configured CIFS servers. The discovery report will report these partial configurations as warnings.
The ARX FFNOS does not support importing at the volume level if any qtree under the volume has a different security mode from the parent volume. F5 Data Manager enforces this rule by making it impossible to select the volume when using the Create ARX Configuration wizard.
When the application port setting is changed, the F5 Data Manager URL file is updated. This file directs the desktop icon and "Launch F5 Data Manager" to open a web browser to the F5 Data Manager application.
Workaround:If your web browser does not successfully connect to F5 Data Manager after these settings are changed, you may have to log off and log in again to the operating system to clear any file data cached in the web browser.
If the machine you are running F5 Data Manager on is low in disk space and memory, the inventory tasks may crash, creating incomplete statistics files or failing to create statistics files at all. If memory is sufficiently low, F5 Data Manager may not be able to create dump files or diagnostic files. (The f5dm.zip file created will be corrupt.)
File servers that allow messages to be streamed to the console asynchronously, run the risk of interrupting the F5 Data Manager file server discovery process. F5 Data Manager recognizes the prompt character and uses it to identify the completion of discovery commands. If console messages corrupt the prompt string, F5 Data Manager will fail to recognize the completion of the command.
Workaround: Due to the logging level, environmental issues, or a chronic issue with the file server, you may need to disable console messages during the discovery process.
When preparing to execute a local discovery, do not attempt to open the discovery.wsf script from the browser. Always save the script first to a shared storage location on your network where the script can be accessed by you, the F5 Data Manager server, and all the file servers that you need to discover.
Windows 2000 does not come with the correct version of dbghelp.dll needed by Inventory and Report. You can acquire dbghelp.dll as a part of the user mode process dumper tools provide by Microsoft. You can download these tools from: User Mode Process Dumper Version 8.1.
The downloaded file will be a self extracting zip file. Locate the dbghelp.dll and copy to the Program Files\F5 Networks\Data Manager\bin directory. (You do not need anything else from the downloaded files). Alternatively it could be copied to the Windows\system32 directory if it does not already exist there (Windows may over-write this newer copy if it an older copy is already there).
We have successfully installed the product and verified that the Apache Tomcat F5DM service has started by checking Administrative Tools -> Services. In addition, the command netstat -an shows that TCP port 443 in the following output:
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
However, the user cannot launch the login web page because there is another service already running on the machine and port 443 is being used by the other service instead of Data Manager. Commonly, all the server editions of OS like 2000 or 2003 Window's web server could already running causing the F5DM service to start in a bad state.
Workaround: Find out which service is using port 443 from Administrative Tools -> Services. If the user has not installed any web server then it could be World Wide Web Publishing Service running on the server edition of OS which can be turned off by stopping the IIS Admin Service. Then, restart the F5DM service.
On installation and in addition to the base product license, the user is now provided with the following licenses:
NFS Inventory tasks require that the NFS file system be mounted to the F5 Data Manager Server. If you have many simultaneous NFS inventories running, you may run out of available drive letters. If an NFS inventory task fails, attempt the task again, when the current list of running NFS inventory tasks has diminished. If NFS inventories continue to fail, verify that the system has not exhausted its list of available drive letters. To verify the availability of drive letters for the system services, execute the following command in a windows command shell:
at <time> /interactive cmd.exe
where <time> is some time in the near future.
When the command window is displayed, execute the "mount" command to see the list of currently used drive letters and mounted file systems. Next, compare this list of file systems to those of running File System Inventory tasks. If any drive letter is attached to a file system that is not connected to a running task, you should consider running the "unmount" command to unmount that file system and free that drive letter.
|Phone:||Contact your local Sales Engineer.|
For additional information, please visit http://www.f5.com.