- User documentation for this release
- Minimum system requirements and supported browsers
- Network requirements
- Supported ARX releases
- Supported file servers
- Upgrading Data Manager
- Installing Data Manager in an alternate path
- NFS Support from Windows SFU
- Enhancements in v2.5.1
- Enhancements in v2.5.0
- General notes
- Known issues
- Contacting F5 Networks
User documentation for this release
The documentation is available from the following locations:
- From the Data Manager GUI navigation panel Documentation link.
- On the AskF5 Technical Support web site, along with an extensive solutions database.
- In the root directory of the product CD-ROM.
Minimum system requirements and supported browsers
You can install and run Data Manager on any Microsoft® Windows® platform that meets the following set of minimum requirements:
- Operating System: Windows operating system (2000, XP, Vista, or 2003 Server)
If you are installing on Windows 2000, it is especially important to read these Release Notes thoroughly. They discuss additional prerequisites for the successfull installation and running of Data Manager on Windows2000.
Microsoft provides localized versions of its Windows operating system. For Data Manager, each distribution must be qualified separately. Currently, Data Manager provides explicit support for the following language distributions: Japanese, Simplified Chinese, Korean, German, Czech, Russian.
- CPU: Pentium 4 or equivalent
- Memory: 1Gb available RAM
Supported browsers for accessing the Data Manager GUI:
- Access to administrator credentials for the file server management interfaces.
- TELNET or SSH enabled on file servers to be discovered.
- For RPC-based discovery on Windows, access to ADMIN$ and IPC$ shares.
- Verified network connectivity to the file server(s) that the ARX will be communicating with.
- Access credentials to CIFS shares and NFS exports (for the File System Inventory Module).
Supported ARX releases
Data Manager supports the automatic generation of configuration files suitable for uploading to all F5 ARX switch models. You can use the generated configuration files on switches running DMOS 3.x and above. DMOS 3.x is required because the generated Data Manager configuration files implement support for the following DMOS 3.x features:
- CIFS Share-ACLs
- Auto-volume file credits
- Active Directory auto-discovery
- Local group SID translation enhancements
Using the File System Inventory Module, you can inventory an ARX VIP running any DMOS version.
Supported file servers
Data Manager supports discovery of configuration information on the following file servers:
- IBM N Series. At code levels: ONTAP 6.5.7, 7.0.x, 7.1.x, 7.2.x, 7.3.x. Protocols: CIFS, NFS. F5 Data Manager v2.0.1 supports the discovery of N-Series Vfilers.
- IBM 500 G. At code levels: AIX 5L, 5.2B. Data Manager supports discovery of configuration information and NFS exports.
- IBM 300 G02. At code levels: Windows 2000 Server, Windows 2003 Server.Data Manager supports discovery of configuration information and CIFS shares.
- IBM AIX. At code levels: AIX 5.1, 5.2, 5.3. Data Manager supports discovery of NFS exports.
- EMC Celerra NSX. At code levels: DART 5.4.x, 5.5.x, 5.6.x. Protocols: NFS, CIFS.
- NetApp FAS. At code levels: ONTAP 6.5.7, 7.0.x, 7.1.x, 7.2.x, 7.3.x. Protocols: CIFS, NFS. F5 Data Manager v2.0.1 supports the discovery of NetApp Vfilers.
- Linux Intel-based. At code levels: Redhat Enterprise 3.x, 4.x, 5.x. Protocol: NFS.
- Solaris. At code levels Solaris 8, 9, 10. Protocol: NFS.
- Microsoft Windows. At code levels: Vista, Windows 2000 (non-clustered), Windows XP, Windows 2003 (clustered and non-clustered), Windows 2008 (non-clustered). Protocol: CIFS.
Microsoft 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.
Data Manager supports inventorying file system shares/exports on file servers that support the following protocols: NFSv2, NFSv3, CIFS, Samba.
Upgrading Data Manager
When upgrading Data Manager, consult the F5 Data Manager Installation Guide which contains troubleshooting information as well as general installation guidance.
If you upgrade your trialware version and time has not expired on the initial trialware version, you must save your database or you will invalidate the remainder of your trial period.
The Data Manager base module formerly included the Discover File Server module and the ARX Configuration module. It now includes the Discover File Server module and ARX ROI Calculator. If you find that you are suddenly missing functionality connected with ARX Configuration module, you must purchase one or more ARX model licenses. For assistance, see your SE or consult the Data Manager User's Guide section on adding or removing licenses.
Installing Data Manager in an alternate path
When upgrading to a new version of Data Manager and installing the new version in a different path, follow these steps:
- Uninstall the current version of Data Manager.
- From the Start menu, click Programs > F5 Networks > Data Manager > Uninstall Data Manager.
- When the screen appears asking which items to retain, leave all the checkboxes checked. In other words, retain everything.
These items are saved in their current location; for example: <application-root-dir>\db
- Install the new release of Data Manager.
- Stop the Data Manager service.
- From the Start menu, click Programs > F5 Networks > Data Manager > Stop Data Manager.
- Copy the files you retained in step #1b to the new location; for example, the default location which is:
C:\Program Files\F5 Networks\Data Manager
- Start Data Manager.
- From the Start menu, click Programs > F5 Networks > Data Manager > Start Data Manager.
NFS Support from Windows SFU
- To support NFS, customers must install Microsoft Windows Services for UNIX (SFU). To better detect issues where customers do not install or configure SFU correctly, the collect-diags capability has been enhanced to save selected output.
- Data Manager requires that you install Microsoft SFU to inventory NFS file systems. If SFU is not installed, Data Manager disables NFS inventory options in the GUI which, in effect, prevents the user from attempting an NFS inventory before installing SFU.
Enhancements in v2.5.1
Release 2.5.1 is a minor release that includes the following feature improvements and fixes. No new features have been added in this release.
- Internationalization support improvements during the installation process.
- Overall application performance enhancements.
- NIS Netgroup resolution fixes.
- Trialware added to full version upgrade support.
- Diagnostic capture improvements.
- File server shell prompt discovery improvements.
Enhancements in v2.5.0
Release v2.5.0 contains the enhancements discussed in the following sections.
File System Inventory
- Scan time performance enhancements. Increased overall speed when collecting statistics and reduced load on file servers.
- Scan time throttle control. During inventory, Data Manager performs a treewalk on one or more subdirectories of the share/export to gather data. This can place an additional load on file servers. If users are concerned about this additonal load, they can now select a speed slower than the default.
- Inventory by hostname. Users can now discover a file server by entering either an IP address or a hostname. The hostname can be either a single name (suffixed with the DNS search order of the DM server) or a fully qualified domain name.
File Server Discovery
- Discovery by hostname.
- RPC support for Windows remote discovery users.
- Support for Windows 2008 file server discovery (non-clustered servers).
- Enforcement of ARX licenses.
- At least one Configuration Support License key is required to enable Configuration Assistant functionality.
- ARX Configurations Summary page and the ARX Configurations page hidden unless the customer has at least one cluster key.
- On an upgrade, if a customer does not have the Configuration Support Licenses, access is disallowed to the Configuration Assistant functionality.
Common Operations Page
- New category labeled Base Module. Data Manager always displays this category which includes the Discover File Server button.
- The ARX Configuration Assistant Module category includes the Create ARX Configuration button only. Data Manager displays the button only if at least one Configuration Support License is present and enabled; for example: ARX-4000 Configuration Support License.
- Save chart and graphic images in black-and-white.
- Batch Summary reports. Select multiple inventories and then run the Report wizard once to generate individual reports for each inventory.
- Automatically create Summary reports after an inventory task completes.
- Include up to 500 inventory files in Cumulative reports and up to 12 inventories for Delta reports.
- Increase limits in Delta reports to allow for graphing the 100 top items, a maximum of 10 data points in each chart, and a maximum of 10 charts.Increase limits for graphing top data elements (top extensions, top paths, top owners).
- Limit reported data to a specified list of top extensions, top paths, or top owners.
- Customize graphics displayed in reports (top of cover, bottom of cover, logo, copyright information).
- ROI reports showing in detail storage infrastructure and costs with and without an ARX.
- The trial version's trial period has been extended to 90 days.
- The current collect-diags facility gathers all information, including all inventory files. These files or the collection of these files may be large. To facilitate small collections, the collect facility has been enhanced to allow users some choice as to what is collected.
- Data Manager ships on a CD with the serial number attached to the jewel case. However, the F5 support model relies on the customer?s having a serial number in hand when creating a support case. When customers call in and have forgotten where the CD case is located and cannot provide a serial number, problems can ensue. To provide a more streamlined support process, the installation process now requires customers to enter the serial number and other identifying information which is subsequently stored in the Data Manager database and automatically collected as part of the collect-diags operation. The information is also displayed when you click "!" (the About button) in the Data Manager GUI.
- A new "Check for Updates" button has been added to the Gui Maintenance page. When the user clicks this button, version and update information is displayed.
- Data Manager finds and reports on certain conditions in the user environment that are not ideal for or are incompatible with an ARX installation. In v2.5.0, Data Manager can now find and report on certain "problematic" or "special" files (busy files, roaming profiles, FGNs, 8.3 names, etc.) in log files that are available from the GUI Inventories page.
- Data Manager enables users to list directories to be skipped (or "ignored") during file system inventory. Different file server types require different that different directories be ignored and Data Manager automatically fills in the correct default ignore directories for the specified file server. In addition, Data Manager saves the ignore directory list in the inventory files and displays it in the File System Inventory Details page (General tab). The ARX snapshot directory is always part of the default ignore list. You can edit the default list.
- Inventories and reports can consume large amounts of space, and you may want to change the default locations where these files are stored. Data Manager has been enhanced to enable users to store inventories and/or reports on an alternate local (physically-attached) drive or on a remote share located on the network.
- When cutting in an ARX. it is important to know how much space to reserve for metadata. Data Manager computes this amount of space (Approximate ARX Metadata Size) and displays it in reports (in the section "ARX Metadata Information"). This information also appears in the Inventory Details page under the Files/Dirs tab.
RPC-Based Windows Server Discovery
To perform RPC-based discovery on Windows servers, you must use a local or domain administrator account with "Log on as a service" privilege. This privilege is not granted by default. For details, see the F5 Data Manager User's Guide section on Performing RPC-Based Discovery on Windows.
Connecting to F5DM service if there is another service already running using port 443 (31815)
You cannot connect to Data Manager if there is another service already running on the machine and that service is using port 443.
If Data Manager has installed successfully, troubleshoot as follows:
- Verify that the Apache Tomcat F5DM service has started by checking Administrative Tools > Services.
- Find out which service is using port 443 from Administrative Tools > Services.
- Terminate that service.
- Restart the F5DM service.
If performing inventories on Windows 2000, dbghelp.dll is required. (30727)
If Data Manager is installed on Windows 2000, the correct version of dbghelp.dll is required. Otherwise, inventories may fail with the following error message when viewing reports or inventories:
Windows dll dbgHelp must be installed on Windows 2000 to run inventory modules.
You can obtain dbghelp.dll as a part of the user mode process dumper tools provided by Microsoft:
User Mode Process Dumper Version 8.1
The file that you download is a self-extracting zip file. Locate dbghelp.dll and copy it to:
You do not need any other files from the downloaded zip file.
When performing discovery on an EMC Celerra, be sure the shell prompt is displaying correctly.
If you are having difficulty discovering an EMC Celerra file server, it may be due to an issue with the shell prompt. Data Manager assumes a default end character prompt of $ (dollar sign). Log in to the file server and note the shell prompt. If it does not end in $, change the .bash_profile so that the prompt does end with a $ and attempt the discovery again.
When discovering Windows servers with TELNET, be sure it is not authenticating with NTLM.
To ensure that TELNET is not authenticating with NTLM:
- On the Windows server from a DOS prompt (as administrator), enter the tlntadmn command to view the current settings.
- Review the output.
- The setting Authentication Mechanism : NTLM, Password indicates authentication using NTLM.
- If the Authentication Mechanism lists NTLM, enter the following command to remove NTLM as an authentication mechanism:
tlntadmn config sec=-NTLM
- If the configuration mode is Console, enter the following command to change the configuration mode from console to stream:
tlntadmn config mode=stream
- To have these changes take effect, restart TELNET by clicking the Windows Start button and then clicking:
Programs > Administrative Tools > Services
- In the Windows Services GUI in the Name column, select Telnet and then click the restart link.
The following items are known issues in the current release. For issues that are being tracked on the F5 internal database, note the tracking numbers that appear in parentheses.
Configuration: The script that recovers NFS exports is missing ACLs for generated names (35334).
As part of the virtualization backout procedure, scripts are generated to return the environment to its original state. However, the configuration script used to recover the original NFS exports and ACLs contains an error for generated export paths.
When an NFS configuration selects an import level that causes the NFS export path to be generated (the import is the parent of the original NFS export), then the script to recover the NFS exports is missing the ACL after the path. Further, the path is for the generated import, not the original export.
Workaround: Edit the configuration script to add the ACL(s).
Local discovery of Windows servers may fail if the Local Discovery script is not same version as Data Manager (34905)
To guarantee a successful local discovery:
- Download the Local Discovery script from the Documentation page of the currently-running version of Data Manager.
- Execute the local discovery or rediscovery as appropriate. (File Servers > File Server Summary > Add/Rediscover).
File System Inventory:The task of inventorying a Windows 2003 share from Data Manager (installed on a Windows 2003 server) fails, but succeeds after reboot (34173)
You encounter this connection error on a Windows 2000 server when trying to inventory a remote system due to problems with an unknown username or password (as indicated in the inventory log). Repeated attempts result in failure with the same error message, even though you specify the correct credentials. Should you encounter this connection error, check for the following problems which can cause problems connecting to a remote share:
- Persistent network connection with an invalid password.
- Service using a user account with an invalid password.
- Trust relationship has been broken.
- Network error reaching domain controller. (Can you reach anything else in the same domain?)
- DNS server connection issue.
- Permissions have changed on the share.
- Date skew on the local machine. (Possibly the password has expired.)
Workaround: Rebooting clears this issue. For more information, see the Microsoft article, Troubleshooting Unwanted "Access Denied" Messages in Domain-Based Networks (Windows NT 3.x and 4.0).
Installer: During installation of Data Manager on Windows 2000, a dialog pops up stating "LogonUser (1314): a required privilege is not held by the client" (34661)
Installing on Windows 2000 requires the privilege of "acting as part of the operating system." This issue does not occur on later versions of Windows operating systems.
Workaround: Temporarily grant an administrator the privilege of "acting as part of the operating system" using the following procedure.
- From the Start button, click Programs > Administrative Tools > Local Security Policy.
- In the navigation pane, click Local Policies.
- In the content pane, double-click User Rights Assignment.
- Right-click Act as part of the operating system.
- Select Security. The Local Security Policy dialog for "Act as part of the operation system" is displayed.
- Click Add.
- Change the Look in dropdown so that it shows the area (local host or domain) from which you'll be adding users/groups.
- Select Administrator and/or Administrators from the list of users and groups.
- Click Add.
- In the Add dialog, click OK.
- In the Local Security Policy dialog, click OK.
- Right-click Act as part of the operating system.
- Select Security The Local Security Policy dialog for "Act as part of the operation system" is displayed.
- Verify that the local policy setting check boxes and the effective policy check boxes are both checked for the new users and groups that you've added.
- Log out and log back in to make changes to the "Effective settings" of the "Act as part of the the operating system" policy effective.
Long multibyte character report name wraps on front page of report, causing the front page to increase to two pages (34755)
When generating batch Summary reports, enter short names for the report because the inventory name gets appended to the report name and if the report name is too long, it will wrap to a second line, causing the front page to increase to two pages. This issue occurs only for batch Summary reports. In the Reports wizard, the user is constrained to a maximum number of characters allowed in the report name field (UI) to 40. Both single byte and multibyte characters fit in one line.
Report Summary: Cannot open report with multibyte character filename (34779)
If you use more than 28 multibyte characters to name a report file, you can encounter problems when trying to open that file through the link on the Report Summary page when using Firefox or any Mozilla-based browser. No issues have been seen when using IE 7.
Workaround: Open the file outside the browser. The file is located in the Reports directory. You can view the path to the Reports directory on the File System Inventory Module Settings page.
NFS ACL warnings appear in the discovery log as "not supported." (30927)
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.
Compressed files may cause capacity inventoried to appear greater than total/used space. (32378)
If you have compressed files (CIFS only) and then inventory the file system containing the compressed files, you may see the reported total capacity inventoried as greater than both the used space and total space of the file system. This occurs because Data Manager defines capacity inventoried as the total uncompressed size of all files inventoried. You can see capacity inventoried in the Capacity tab:
Statistics Files > File System Statistics File Details > Capacity tab > Total Disk Capacity
File System Inventory Wizard: Section selection does not work for summary report in RTF format. (32576)
If you generate a summary report and choose the Customize option on the first page of the Inventory wizard and then select only the first sections for inclusion in the report (General Information, Files And Directory Information, Capacity, CIFS Information) and, finally, select RTF for the report format, the result is a complete summary report including ALL sections and not just the selected sections.
If you upgrade your trialware version and time has not expired, save your database. (33839)
If you upgrade your trialware version and time has not expired on the initial trialware version, you must save your database or you will invalidate the remainder of your trial period.
Windows SSH file server discovery does not time out. (29570)
If you have tried to cancel a file server discovery and the operation does not terminate after 60 seconds, stop and then restart the FFNM service using the application links under the Microsoft Windows(TM) Start menu.
Corrupt ffnm.zip is created when memory usage of the Web application is high. (30735)
If you attempt to collect diagnostics and the ffnm.zip file is corrupted, it may be because memory usage on the Data Manager server is high (more than 260 M). Restart Data Manager and you should be able to collect diagnostics successfully.
File System Inventory Report:Owner appeared as "Everyone" for NFS shares inventoried over Windows SFU (33758)
Prior releases of Data Manager may have had the appearance of collecting owner and link information for NFS shares inventoried over Windows Services for UNIX (SFU). The owner would appear as S-1-1-0, which equates to "Everyone." This data is not collected as SFU is not capable of delivering it to Data Manager.
Discovery and configuration: DM does not handle an EMC share explicitly assigned to multiple CIFS servers (31366)
Data Manager misses a CIFS server assignment on a share when the share is configured in the GUI for multiple CIFS servers.
Verify permissions before and after using rmtshare. The script that grants proxy-user share-level access uses rmtshare which overwrites existing permissions. (32280)
This note is a warning about rmtshare behavior when adding access to share ACLs.
If you follow the current virtualization workflow (non-subshare case), new hidden shares are created on the ARX (using rmtshare) and then existing permissions are copied from the original shares to the new shares. Then, a separate script is run to grant the proxy-user access to the shares.
In sporadic cases, rmtshare overwrites any existing share permissions, leaving only the proxy-user with access. Be sure to verify access lists before and after using rmtshare to add proxy-user access.
Discovery: RPC-based discovery is not compatible with Simple File Sharing (33945)
RPC-based discovery does not succeed on a Windows system that has Simple File Sharing enabled. When Simple File Sharing is enabled, remote users authenticate as Guest and Guest accounts do not have administrative rights which are required to execute a successful remote discovery.
Can't inventory an NFS export called "/" (32916)
This is a Windows Services for UNIX (SFU) limitation. SFU doesn't support inventorying "/".
File System Inventory: When inventorying NFS exports on Linux kernel 2.6.9, you may encounter skipped directories (32430)
When running an inventory over an SFU mount point that is located on a Redhat Enterprise 4 (or any Linux using kernel 2.6.9), you may encounter an error in the logs:
Import: Internal directory error encountered. Skipping directory tree
The directory path is included in the error message. This error is caused by variable length file handles used by the kernel, which Microsoft's SFU is unable to process correctly. The inventory proceeds normally from that point, but the results will miss the directory in question.
Windows 2003 R2 NFS client (32397)
If using Windows 2003 R2 NFS Client for Windows (NFSClient) for NFS inventory, you may receive the following error messages:
- Network Error 53
- The data area passed to a system call is too small
- Unknown Error
The NFS client included with Windows Server 2003 R2 (NFSClient) can return a variety of errors when trying to access NFS exports on UNIX-based NFS servers. The exact wording of the error message may vary depending on your environment. You might get one or more like the ones mentioned above. It is also possible that SFU 3.5 Client for NFS may work fine.
If you analyze the network traffic, you may see MOUNT commands or NFS calls being "rejected for security reasons (5)."
NFSClient uses high ports (>1024) to connect to NFS servers and that's known to cause errors such as those listed above. Use one of the following methods to fix the problem:
- Change how your NFS servers export the NFS shares and enable them to accept connections from high ports.
- Add UseReservedPorts DWORD value under HKLM\Software\Microsoft\Client for NFS\CurrentVersion\Default and set it to 1.
Restart NFSClient to allow the change to take effect.
Hard links are not reported for the Windows shares (30730)
The user can create hard links on Windows and they behave as they do in UNIX, but the Report function does not recognize them. This appears to be an OS/network problem. According to Microsoft, referring to the call made by Data Manager: "Depending on the underlying network components of the operating system and the type of server connected to, the function may fail, return partial information, or full information for the given file."
Cannot inventory mapped drives using using the local drive/path method (30526)
When attempting to inventory a mapped drive (non-local), Data Manager reports that the path is not found. Data Manager cannot inventory mapped drives through the "local drive" method.
Contacting F5 Networks
||Contact your local Sales Engineer.
For additional information, please visit http://www.f5.com.