Applies To:

Show Versions Show Versions

Release Note: Data Manager version 2.6.1
Release Note

Software Release Date: 02/02/2010
Updated Date: 02/03/2010


These release notes document version 2.6.1 of the F5 Data Manager.


- User documentation for this release
- Minimum system requirements and supported browsers
- Network requirements
- Supported ARX releases
- Supported file servers
- Upgrading Data Manager
- NFS Support on Windows platforms
- Enhancements in v2.6.1
- Enhancements in v2.6.0
- General notes
- Known issues
     - File Server Discovery
     - Data Manager Client Access
     - NFS Support
     - File System Inventory
     - Installation
     - Miscellaneous
- 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.
[ Top ]

Minimum system requirements and supported browsers

Data Manager will run on a general-purpose server; however, take care to select a server that is not overburdened with applications and users. In particular, note the following requirements and recommendations.

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 (XP, Vista, Windows 7, 2003 Server, 2003 R2 Server, 2008 Server, 2008 R2 Server).

    Note that Windows 2000 is not supported for installation of Data Manager v2.6.0 or later.

    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, French, Spanish.

  • CPU: Pentium 4 or equivalent. Dual-core server is recommended.
  • Memory: 1GB free RAM. (2GB is recommended.)
  • Disk Space: 1GB for the application, data, and logging.

Supported browsers for accessing the Data Manager GUI:

  • Microsoft Internet Explorer®, version 6.x or 7.x.

    Internet Explorer version 8 (IE8) is not fully supported and should be avoided at this time. If necessary, using compatibility view can reduce issues. For more information on compatibility view, click:

    Internet Explorer 8: Features and then click Compatibility View in the navigation panel on the left.

  • Mozilla® Firefox® 2.x or higher and other browsers that use the Mozilla engine. (v3.x is recommended.)

    Note that Javascript must be enabled on the web browser.


[ Top ]

Network requirements

During the process of using Data Manager features, you will need the following:

  • For file server discovery, access to administrator credentials for the file server management interfaces.
  • For file server discovery, TELNET or SSH enabled on file servers to be discovered.
  • For RPC-based discovery on Windows, access to ADMIN$ and IPC$ shares.
  • For file server discovery and file system inventory, verified network connectivity to the file server(s) with which the Data Manager or the ARX will be communicating.
  • For file system inventory, access credentials to CIFS shares and NFS exports.
  • Highly recommended for file server discovery and file system inventory, network name resolution (DNS, local files).
[ Top ]

Supported ARX releases

Data Manager supports the automatic generation of configuration scripts suitable for applying 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.

[ Top ]

Supported file servers

Data Manager supports a full 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.
  • 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.
  • 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, Windows XP, Windows 2003 (clustered and non-clustered), Windows 2008 (clustered and 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, French, Spanish.

You can perform a partial discovery that includes CIFS shares and NFS exports on file servers that are not listed above. (For details, see Generic discovery.)

Data Manager supports inventorying file system shares/exports on file servers that support the following protocols: NFSv2, NFSv3, CIFS, Samba.

[ Top ]

Upgrading Data Manager

When upgrading Data Manager, consult the F5 Data Manager Installation Guide which contains troubleshooting information as well as general installation guidance.

Special Considerations

  • 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.
  • Data Manager stores licenses in its database so if you remove your database, you will have to enter your license keys again.
[ Top ]

NFS Support on Windows platforms

Data Manager requires NFS support on Windows platforms in the following cases:

  • For generic file server discoveries (for file servers that support NFS)
  • For file system inventory of NFS file systems

If the correct NFS client package is not installed, Data Manager disables NFS inventory options.

The following table summarizes the NFS client packages required on specific Windows platforms. For details, see the appendix in the User's Guide, Using UNIX Services on Microsoft Windows.

Windows Platform Windows Service Required
Windows 2000 Windows Services for UNIX (SFU).
XP Windows Services for UNIX (SFU).
Windows Server 2003 Microsoft Services for NFS or Windows Services for UNIX (SFU).
Windows Server 2003 R2 (64 bit) Microsoft Services for NFS. You cannot install SFU on a 64-bit OS.
Windows Vista Ultimate and Enterprise Microsoft Services for NFS. Do NOT install SFU.
Windows Server 2008 Services for NFS (Client for NFS). Do NOT install SFU.
Windows 7 Services for NFS (Client for NFS). Do NOT install SFU.
[ Top ]

Enhancements in v2.6.1

The v2.6.1 release is a maintenance release addressing, among others, the following issues:

Improper assignment of VPU/Domains to ARX volumes during the initial ARX configuration creation (37162)

Previously, Data Manager had improperly assigned VPU/Domains to ARX volumes during the initial ARX configuration creation.

This issue resulted in ARX configuration scripts that could not be successfully applied to the ARX. During application of the deployment scripts, the ARX would report these errors as the commands were being issued by the user. The initial remedy was to edit the VPU/Domain assignments manually for these misassigned volumes, prior to executing the deployment scripts on the ARX. In v2.6.1 the issue causing the misassignment was rectified. In v2.6.1, the assignment algorithm was enhanced and a user entry field was added to properly account for pre-existing volumes that may already be defined on the ARX.

Users upgrading from previous versions of Data Manager, with configurations that spanned multiple VPU domains, should recreate their configurations and deployment scripts to take advantage of the new assignment rules.

Incorrect "Clustered" setting value (37426)

The release corrects an issue with the value of the storage path's "Clustered" setting on the Imported File System page. It was displayed incorrectly.

Discovering Windows 2000 cluster hosts (37388)

The release corrects issues with discovering Windows 2000 cluster hosts.

New Site Survey spreadsheet (37501)

The release includes a new Site Survey spreadsheet.

Issues with saved report templates after upgrade (37390)

After an upgrade to v2.6.0, previously-saved report templates could not be used. This fix correctly converts these report templates into the new format.

[ Top ]

Enhancements in v2.6.0

The v2.6.0 release is intended to support ARX pre-qualification use case and to enhance existing functionality. It does not add new functional modules.

New report: File Server Scale

In v2.6.0, Data Manager introduces a new report, the File Server Scale report. This report expedites the process of sizing an environment for an ARX installation by including in one report summary and cumulative statistics about one or more file servers. SEs no longer need to copy and paste multiple Discovery reports into Excel in order to build a table representing the entire environment.

Enhanced discovery

  • Generic file server discovery. Data Manager now discovers shares/exports from any CIFS/NFS file server including ARX. You can now use Data Manager discovery to get the list of CIFS shares and NFS exports and enumerate them in the File Server Detail page.
  • Support for Windows 2008 clusters
  • Automatic discovery of Netapp vFilers, EMC PDMs, and Windows cluster nodes
  • Additional discovery information, including:
    • Support for discovering ABE
    • Object total counts (share/export counts for example)
    • Print services
    • Quotas
    • File system capacity
    • Capture of the output of several CLI commands regarding file server performance statistics

Support for the new ARX2000 platform

Data Manager now lets you create configurations tailored toward an ARX2000.

Enhanced ARX Configuration Assistant

  • "Expert Mode"added, which allows for building ARX configurations that import at the NetApp volume level.
  • Configurations for Windows 2008 clusters added.
  • The commands for enabling volumes/shares have been removed from the virtualization scripts and placed in separate scripts.
  • Non-default NetApp root volumes filtered from configurations.
  • ABE configuration control in generated ARX configurations.
  • Changing of CIFS volume options allowed.

Report changes

During v2.6.0, the reports in Data Manager were changed so that their names more closely reflect the contents and usage of the reports.

  • Discovery report. This report, generated as part of the file server discovery process, was previously named Discovery log or Discovery Task log.

    This report includes warnings and other information obtained during a file server discovery. After the discovery completes, click the link in the File Server Summary page (Status column) to display this report. You can also save these reports.

  • File Server Detail report.

    This report includes all of the details about one or many file servers and can be generated, viewed, and saved from the File Server Report page. Previously, the report covered a single server only and could be viewed only (not saved).

  • File Server Scale report. New with this release.

    This report includes a summary (and cumulative statistics) about one or more file servers and can be generated from the File Server Report page.

  • File System Detail report. This report was previously named the Summary report.

    This report is comprised of all file system metadata collected for a share or export, including directory structure and capacity information. This report can be generated from the the following locations: the Common Operations page, the Report Summary page, the Inventories page, and the File System Inventory Details page.

  • File System Trend report. This report was previously named the File System Delta report.

    This report presents changes over time in a single share/export from a single file server. This type is useful for tracking capacity and file counts over time for capacity planning purposes. This report can be generated from the the following locations: the Common Operations page, the Report Summary page, the Inventories page, and the File System Inventory Details page.

  • File System Cumulative report. This report has not been renamed.

    This report adds all the data from two or more file system inventories from the same share/exports and outputs the data in text and/or graphical format. This report can be generated from the the following locations: the Common Operations page, the Report Summary page, the Inventories page, and the File System Inventory Details page.

Changed location of Discovery reports

In v2.6.0, the location of the Discovery reports was changed. By default, the Discovery reports are now located in the following directory:

<application-root-dir>\Data Manager\diags\File System Stats\Default

Also, you can view these reports from the Report Summary page.

Support for discovering ABE

During discovery, Data Manager can query file servers to determine whether or not ABE (Access-Based Enumeration) is enabled. If ABE is enabled, special considerations need to be taken when generating the ARX configuration. Data Manager supports ABE discovery for the following file server types: Windows Server 2003, Windows 2003 R2, Windows Server 2008 R2, NetApp, and EMC. In NetApp environments, Data Manager can determine whether ABE is enabled by examining the NetApp configuration. In other file server environments, the file server is queried using the abecmd.exe utility.

You must install the abecmd.exe executable in a directory in the PATH variable where the Data Manager server is running and the Data Manager user must be able to execute it. The abecmd.exe utility is available from Microsoft for Windows 2003 Server SP1 at the following location:

Once you install the abecmd.exe utility on a Windows 2003 Server, you can copy the executable to other Windows OS platforms (XP, 2008, and so on).

Installation on Windows 7 and Windows 2008

You can now install Data Manager on Windows 7 and Windows 2008 (Standard, Enterprise, and Datacenter editions).

[ Top ]

General notes

Import of the local discovery data for Windows servers may fail if the Local Discovery script that generated it is not same version as the Data Manager server.

Local discovery files (named *.dsc) are temporary and are not meant to be forward-compatible with new versions of Data Manager.

To guarantee a successful local discovery:

  1. Download the Local Discovery script from the Documentation page of the currently-running version of Data Manager.
  2. Execute the local discovery script on the Windows file server. (File Servers > File Server Summary > Add/Rediscover).
  3. Import the discovery data.

For details on local discovery, see the User's Guide, Performing Local Discovery for Windows File Servers.

RPC-Based Windows Server Discovery

To perform RPC-based discovery on Windows servers, you must use a local or domain administrator account that has "Log on as a service" privilege on the remote machine. 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.

F5DM service is running but you cannot connect to it through a web browser (31815)

You cannot connect to Data Manager if there is another service/application using the same port as Data Manager. (By default, the ports that Data Manager uses are 443 and 8005.)

If Data Manager has installed successfully, troubleshoot using the instructions in the troubleshooting chapter of the User's Guide.

When discovering 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 on the Celerra control workstation 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:

  1. On the Windows server from a DOS prompt (as administrator), enter the tlntadmn command to view the current settings.
  2. Review the output.
  3. The setting Authentication Mechanism : NTLM, Password indicates authentication using NTLM.
  4. If the Authentication Mechanism lists NTLM, enter the following command to remove NTLM as an authentication mechanism: tlntadmn config sec=-NTLM
  5. If the configuration mode is Console, enter the following command to change the configuration mode from console to stream: tlntadmn config mode=stream
  6. To have these changes take effect, restart TELNET by clicking the Windows Start button and then clicking: Programs > Administrative Tools > Services
  7. In the Windows Services GUI in the Name column, select Telnet and then click the restart link.
[ Top ]

Known issues

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.

File Server Discovery

Discovery: Starting ABE discovery (37146)

If ABE is enabled for discovery and the user had provided the correct credentials but discovery was unable to resolve the DNS entries for some of the CIFS servers from the desktop (the Data Manager server), discovery will fail. The Discovery report tells you what fails, but the fact that is is related to ABE and that you can rediscover with ABE discovery turned off is not provided to the user or to Support in an easy way.

In the Discovery report, search for the following message:

Authenticating CIFS IPC Credentials

The lines following this message will provide more information on the failure.

GenericDiscovery: Not discovering CIFS shares on an NTAP file server from a Data Manager server installed on Windows 7 (37078)

Generic discovery of a CIFS-capable file server fails with the message, "The stub received bad data".

Data Manager servers running on Microsoft Windows 7 and Windows 2008 R2 (64bit) server may see issues discovering older CIFS-capable file servers using the generic file server type in the Data Manager Discovery wizard. The generic file server type discovery uses the MS Windows native "net view" command. The "net view" command will execute successfully on Windows XP, Windows 2003, and other Windows OS versions.

Looking at the resulting capture files from failed discovery task, you will see

$ net view \\<File Server>

System error 1783 has occurred.

The stub received bad data.

You will see the following in the File Server Discovery report:

Discovering CIFS Shares

Warning: The discovery of CIFS shares for file server failed:

System error 1783 has occurred.

Warning: The discovery of CIFS shares for file server failed:

The stub received bad data.

The only known workaround is to discover the file server from a Windows server that can successfully execute the "net view" command against it.

Discovery: Discovery of Window servers with ABE discovery enabled fails due to CIFS IPC authentication failure (37084)

During discovery of Windows servers, if ABE discovery is enabled, the process must be able to resolve the NetBIOS name of the file server being discovered. If it cannot, then the ABE discovery phase will fail and if the ABE discovery phase fails, the entire discovery task will fail.

Workaround: On the Data Manager server, edit the hosts file so that the Data Manager server can resolve hostnames when unable to communicate with the DNS server in the data center environment. The default location of the hosts file is C:\Windows\System32\drivers\etc\hosts.

Windows Discovery: Windows file system capacities in cluster resource groups are marked as 0 (35621)

Data Manager cannot discover the capacity for a disk that is not currently mounted on the discovered node. Hence, some file systems are marked as having 0 capacity. Data Manager discovers capacity accurately for cluster resource groups that are currently active on the node.

Windows Discovery: Quotas not discovered properly for some clustered file systems (35622)

Data Manager does not discover quotas accurately for the file systems (disks) that are not active on the node. Data Manager does discover quotas accurately for the file systems (disks) that are discovered in cluster resource groups that are currently active on the node.

Thus, you should discover all nodes in the cluster and compare the discovered quota data.

Discovered Windows server share names containing question marks. (36461)

In share names discovered using TELNET, SSH, or RPC discovery methods, Data Manager renders the Unicode characters that are not part of target system's OEM code page as question marks.

For example, if the share name on the target server is currency-€, the share appears in Data Manager as currency-?.

This could result in confusion if there is another share on the target named, for example, currency-元, which would also appear in Data Manager as currency-?.

This issue is not exclusive to English language systems but can be observed on any system where a share name contains a character that is not available in the target's OEM code page.

To determine if a share name contains any characters affected by this issue:

  1. Open a Windows command shell.
  2. CD into the parent of the suspect directory.
  3. Execute the DIR command and examine the listing for share names containing question marks.

Workaround: Use the local discovery method, which renders share names correctly.

Discovery: Selecting the wrong IP address for local Windows cluster file import throws off the CIFS server assignments (36027)

It is important to enter (as the primary service address) the IP address associated with the physical node. Do not select an IP address associated with a cluster resource group when importing the local discovery file.

You can obtain the correct IP address from the discovery file (*.dsc) by entering a type command from the DOS prompt. In the following examples, substitute your .dsc filename in place of "file.dsc."

To list the file server IP addresses, enter:

>type file.dsc | findstr /R /C:"IP Address. . . . . . . . . . . . :"

To list the resource IP addresses, enter:

>type file.dsc | findstr /R /C:"Address                          [0-9]"

Then, note an IP address from the first list which is not in the second list.

Discovery: If the cluster service is unreachable, Windows cluster discovery fails to assign shares to the correct resource groups (36380)

If cluster services become unavailable, Data Manager is unable to gather the cluster resource group assignment information necessary to display the allocation of resources (shares) to resource groups (virtual CIFS servers). In these cases, any resources (shares) that are currently active on the node being discovered appear as if they are assigned to that physical node.

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.

NFS ACL warnings appear in the Discovery report as "not supported." (30927)

ACL warnings appear in the Discovery report 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.

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 Data Manager using the application links under the Microsoft Windows(TM) Start menu.

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 using the Celerra GUI for multiple CIFS severs.

Data Manager Client Access

Internet Explorer 8 support (36719)

Internet Explorer 8 (IE8) is not officially supported; use it at your own risk. If using IE8, enable compatibility view. For more information, click:

Internet Explorer 8: Features and then click Compatibility View in the navigation panel on the left.

NFS Support

NFS Inventory:Can't execute an NFS inventory from a Windows 2003 64-bit machine running Microsoft Services for NFS (37111)

Attempting to mount a drive with invalid credentials produces error 21 (device not ready) rather than an error message indicating that the failure is due to a problem with credentials. In any case, the mount fails and the attempt never reaches the file server. Verify your credentials, re-enter them and try the inventory again.

NFS inventories on Windows Server 2008, Windows 7, and Windows Vista Ultimate and Enterprise

On Windows Server 2008, Windows 7, and Windows Vista Ultimate and Enterprise, do not install SFU Version 3.5 or later. To run NFS inventories on these platforms, enable NFS Client Services, which is part of the Windows OS base distribution. No additional CD or download is required. For more information, see the User's Guide

User Mapping in Windows Vista, Windows 7, and Windows 2008

You cannot set up user name mapping in Windows Vista, Windows 7, or Windows 2008 if you don't have SFU v3.5 or Windows 2003 R2 machines on the network running the User Name Mapping service.

You must map to root. See the following procedure for details on modifying the Registry to map to root.

  1. Start the Registry Editor.
  2. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default
  3. Create two DWORD values: AnonymousUid and AnonymousGid
  4. Set these values to a UID of 0 and a GID of 0.
  5. Restart the Client for NFS service using the Microsoft Services for NFS MMC snap-in.

If you mount shares on this machine, the Client for NFS driver will send those values as the UID and GID to the NFS server. Also, you can use the mount command without any parameters to verify whether these values are being used.

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.

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. 

File System Inventory

NFS Inventory: Issues resolving symbolic links in NFS file systems (32983)

The Data Manager inventory process reports on symbolic links. Unfortunately SFU doesn't give Data Manager any indicator that these items are links, and they look like files and directories. For example, Data Manager counts the following as a directory: lib\jvm\java-1.6.0-openjdk

SFU doesn't provide any indication that these items are symbolic links. Also, Data Manager will report some directory links as files - if the directory is a leaf node.

File system scanning process takes too long or never finishes

If you have shares that appear to contain recursive loops so that a scanning process never finishes, even after the size and file count are well above the actual numbers, the problem could be caused by one of the following:

  • Snapshot directories. You have not instructed Data Manager to ignore snapshot directories during the inventory process.

    The Inventory wizard lets you specify a list of directories to be ignored during the inventory process. The snapshot directories are not included in the default list and if not explicitly excluded, Data Manager will inventory through all retained snapshots.

  • NFS environment containing circular symlinks. Data Manager cannot address this issue because the inventory uses SFU which identifies the link as a directory.

    In most cases, you can look in the resulting inventory log (RTF) and identify the circular path. Then, you may be able to update the exclude path to exclude the circular link. To review the inventory RTF file:

    1. Stop the inventory.
    2. Edit the inventory task.
    3. Enable debug.
    4. Restart the inventory task and allow it to run to completion.
    5. Review the inventory log from the Data Manager navigation panel by clicking:

      File System Inventory > File System Inventory Task Details > Last Completed Log File

      In the inventory log, look for very long directory names that seem to repeat portions of their path.

  • CIFS environment containing reparse points. In CIFS environments, Data Manager inventories follow reparse points, not shortcuts. You can disable this behavior through an option in the Inventory wizard. If you have circular links, you may want to change the Inventory setting to avoid following reparse points.

File System Inventory Wizard: Section selection does not work for File System Detail report in RTF format. (32576)

If you generate a File System Detail 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.

The section selection is not supported in RTF format.

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 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.

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.

File System Inventory: The task of inventorying a Windows share from Data Manager fails, but succeeds after reboot (34173)

You encounter this connection error on a Windows server when trying to inventory a remote system due to problems with an unknown username or password error (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).

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 (or use IE7). 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.

Compressed files may cause capacity inventoried to appear greater than total/used space. (32378)

You can see Total of all inventoried file sizes in the Capacity tab:

File System Inventory > Inventories > File System Inventory Details > Capacity tab > Disk Capacity Information > Total of all inventoried file sizes

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.


Installer: Data Manager requires uninstall of old software before installation of new software. (34777)

Currently, the Installer informs you that a previous version of Data Manager is installed and instructs you to uninstall it manually before you can proceed with a new installation.

Installer: Data Manager user is removed, but directory is left behind (35946)

During the uninstall process, Data Manager attempts to remove the Data Manager user and the Data Manager user�s profile. In some instances, Windows requires a reboot to remove the directories associated with an active profile. If the Data Manager user directory is left behind, you can reboot your system and then remove the directory manually at your convenience.

If you upgrade your trialware version and time has not expired, you must 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.


Corrupt is created when memory usage of the Web application is high. (30735)

If you attempt to collect diagnostics and the 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.

Script (rmtshare) that grants proxy user share-level access uses rmtshare which could overwrite existing permissions. (32280)

This note is a warning about rmtshare behavior.

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 rmtshare is run to grant the proxy user access to the shares.

The script rmtshare sometimes overwrites any existing share permissions, leaving only the proxy user having access.

[ Top ]

Contacting F5 Networks

  Phone: Contact your local Sales Engineer.
Fax: (206) 272-6802

For additional information, please visit

Was this resource helpful in solving your issue?

NOTE: Please do not provide personal information.

Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)