Applies To:

Show Versions Show Versions

Release Note: Data Manager version 3.1.0
Release Note

Original Publication Date: 08/29/2013

Summary:

These release notes are part of the documentation for version 3.1.0 of the F5 Data Manager.

Contents:

- User documentation for this release
- Minimum system requirements and supported browsers
- Network requirements
- Supported ARX releases
- Supported file servers
- Upgrading Data Manager
- NFS Support for File System Inventory
- NFS Support for Storing Inventories
- Enhancements in version 3.1.0
- Known issues
     - File Server Discovery
     - ARX Configuration
     - Data Manager Client Access
     - File System Inventory and Reports
     - 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 Ask F5 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, F5 Networks recommends that you 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: Data Manager requires that Windows 2003 machines have Service Pack 1 (SP1) installed. This guarantees the inclusion of Microsoft Windows Installer 3.1 (MSI 3.1) or higher.

    Please see Microsoft's Support knowledge base article for details: Windows Installer 3.1


    Note: Windows 2000 is not supported for installation of Data Manager version 2.6.0 or higher.

    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. A minimum of 2 cores is required when using advanced reporting features.
  • Memory: A minimum of 2GB available RAM is required. 4GB of physical memory is recommended when using advanced features (file system inventory and advanced reporting).
  • Disk Space: 1GB for the application, configuration data, and logging. Additional space is required for file system inventories and reports. The total space required for storage of inventories and reports is based on your inventory frequency and your retention policy.

Supported browsers for accessing the Data Manager GUI:

  • Microsoft Internet Explorer®: version 8.x.
  • Internet Explorer version 8 (IE8): Disable Compatibility View for Data Manager web pages.

    Internet Explorer version 7 (IE7) is not supported for Data Manager version 3.1.0 or higher.

    Internet Explorer version 9 (IE9) is not currently supported.

  • Mozilla® Firefox® 3.x or later and other browsers that use the Mozilla engine.
  • Note that Javascript must be enabled on the web browser.

 

[ Top ]

Network requirements

When using Data Manager features:

  • For file server discovery, you need access to administrator credentials for the file server management interfaces.
  • For file server discovery, you need Telnet or SSH enabled on file servers to be discovered.
  • For RPC-based discovery on Windows, access to ADMIN$ and IPC$ shares is required.
  • 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 is required.
  • For CIFS file system inventory, you need access credentials to CIFS shares.
  • For NFS file system inventory, NFS ACLs may need to be updated root squash disabled to allow the Data Manager server access to the NFS export.
  • For file server discovery and file system inventory (highly recommended), you need network name resolution (DNS, local files).
[ Top ]

Supported ARX releases

Data Manager supports the automatic generation of configuration scripts suitable for applying to all ARX switch models. You can use the generated configuration files on switches running DMOS 3.x and above.

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. Protocol: NFS.
  • IBM 300 G02. At code levels: Windows 2000 Server, Windows 2003 Server. Protocol: CIFS.
  • IBM AIX. At code levels: AIX 5.1, 5.2, 5.3. Protocol: NFS.
  • EMC Celerra NSX. At code levels: DART 5.4.x, 5.5.x, 5.6.x, DART 6.0.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.
  • ARX Cloud Extender. At code level: 1.8.1. 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: NFSv3 and CIFS.

[ Top ]

Upgrading Data Manager

Data Manager does not support upgrading from a Beta release to an official GA release. Beta users are required to uninstall and remove their Beta database before installing the GA-released version. You may opt to keep your inventories and reports.

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 installation, 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 (i.e, for a clean install), you will have to enter your license keys again.
[ Top ]

NFS Support for File System Inventory

With v3.0.0 and higher, Data Manager includes a built-in NFS client, which provides native support for NFS inventories. Secondary NFS client packages are no longer required. The Data Manager NFS client always connects to NFS exports as root (i.e, UID=0). Verify that root requests are allowed on the export you are trying to inventory.

You may also need to update Netgroup and/or NFS ACL information to allow the Data Manager server access to the export.

[ Top ]

NFS Support for Storing Inventories

Data Manager requires NFS support on Windows platforms for optional storage of inventories and reports on NFS exports.

The following table summarizes the NFS client packages required on specific Windows platforms.

Windows Platform Windows Service Required
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 version 3.1.0

The version 3.1.0 release provides the following enhancements to the previous release:

  • Support file server discovery of the ARX Cloud Extender (ARX-CE)
  • Data Manager now supports discovery of a Windows file server with the ARX Cloud Extender software installed. The new file server type of ARX Cloud Extender has been added to the list of available file server types. This type can be selected as the file server type when running the Discovery wizard. This discovery process currently follows the same procedures as a Microsoft Windows file server discovery.

    All existing Windows file server support including Telnet/RPC/SSH discovery, local discovery, and Windows cluster support is unchanged.

  • Configuration enhancements
    • Support for new DMOS 5.3.1 and 6.0.0 configuration enhancements
    • Volume groups. Data Manager now supports assigning volumes to volume groups. The ARX namespace functionality assigns a volume to a default volume group automatically if one is not assigned explicitly. Volume groups are a means of isolating namespaces in the ARX memory so that the failure of one namespace in one volume group does not affect the performance of namespaces in other volume groups.

      Constrained delegation. Data Manager now supports constrained delegation security, which is a configuration option in Windows 2003 and 2008 domain controllers. This option constrains the delegation privileges for a computer account to specific services (such as CIFS or HTTP) and to specific computers (such as file servers or Web servers). Constrained delegation is implemented by the Kerberos Service-For-User(S4U) protocol extension, a Microsoft extension to the Kerberos protocol. Using constrained delegation allows client NTLM authentication without the F5 Secure Agent.

    • Support for new platforms: ARX-VE, ARX-1500, ARX-2500
    • Data Manager now supports creating configurations for the ARX-VE (Virtual Edition), a software-only virtualization device, and two new hardware platforms, the ARX-1500 and the ARX-2500. For specifics on the new hardware platforms, please consult their hardware installation guides.

  • Task management and monitoring enhancements
    • Discovery task is separated from the file server object
    • Prior to version 3.1.0, the file server discovery task and discovered file server data were a single object. In version 3.1.0, these objects were separated into a discovery task object and a file server object. A discovery task is created with the Discovery wizard; none of the existing task creation steps have changed. A successful discovery task creates a file server object that is populated with the discovered configuration information.

    • New Active Tasks page
    • All running and queued tasks in the application are now displayed on a single GUI page, the Active Tasks page. From this page, the status of all running tasks are dynamically displayed, and the user can manage and monitor tasks from a single location.

  • File system reporting enhancements
    • NFS UID / GID-to-Name Translation
    • UNIX-type operating systems identify owners of files by an integer called a user identifier (UID) and groups by an integer called a group identifier (GID). Data Manager can now be configured to translate UIDs and GIDs to owner and group names in file system details pages and generated reports. Note that translation results in a change to the display of names; there is no change to the database contents.

    • Reporting total size for offline and online files.
    • Data Manager now reports on the total size for files with the offline attribute set. Shares exported by Windows OS set the offline bit for files that are archived to a private or public cloud infrastructure. Data Manager file system inventories against a cloud extender can now report on the total capacity for files that have this bit set. It also report on the total size of online files.

    • Enhancements to the File Set report
    • The File Set report (Advanced reports only) is enhanced in version 3.1.0 to include the following optional data associated with each file in the report:

      • Size (expressed in bytes)
      • Modify Time (time the file was last modified)
      • Access Time (time the file was last accessed)
      • Owner (if NFS, UID/GID translated if file uploaded)
  • Ease-of-use and customization enhancements
    • Enhanced task scheduling
    • Data Manager has been enhanced to provide an independent scheduling object for the use and reuse of inventory tasks.

    • Data tables customizations
    • The Data Manager summary data tables have been enhanced in version 3.1.0 to provide increased flexibility for displaying data. With these tables, you can:

      • View large data sets in a timely manner
      • Search for data across multiple columns
      • Change the column width
      • Change the columns that are visible or hidden
      • Filter by individual columns
      • Change the column to sort the page on
      • Change the column sort order

    In addition, the View drop-down control on the File System Inventories page provides the Rebuild Inventories List option (as well as Reset Filters and Reset Columns). If you select Rebuild Inventories List, Data Manager rescans the inventories directory. This means that any inventories added or removed manually will subsequently appear on or disappear from the page. Unless the rescan is forced with this option, the inventories directory is scanned on application start/restart and not when the page is simply refreshed or the user has logged in or out.

[ 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

RPC-based Windows server discovery requires special privileges (359453)

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.

When discovering UNIX/Linux-based file servers where the shell prompt has been customized, you must inform Data Manager of the customized prompt. (359454)

If you are having difficulty discovering UNIX/Linux-based file servers, it may be due to an issue with the shell prompt. Data Manager assumes a default prompt of $ (dollar sign). Log in to the file server and note the shell prompt. If it does not end in $, you must inform Data Manager of the customization in the Discover File Server wizard. Attempt the discovery again. In the wizard Shell Prompt field, type the customized character.

The prompt is associated with these specific UNIX/Linux-based file servers only. It is used for the current discovery and saved for rediscoveries. It does not effect the default settings for UNIX/Linux-based file servers.

When using Telnet to discover Windows servers, be sure Telnet is not using NTLM for authentication. (359456)

To ensure that Telnet is using NTLM to authenticate:

  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.

File server discovery fails for EMC Celerra file server. Data Manager reports error when waiting for prompt (359560)

If you are having difficulty discovering EMC Celerra file servers, it may be due to an issue with the shell prompt. Data Manager assumes a default prompt of $ (dollar sign). Log in to the file server and note the shell prompt. If it does not end in $, you must temporarily change it to end with a $ (dollar sign). After updating the prompt, attempt the discovery again.

On the Reports page, the File Server column lists the file server�s hostname, but the File Server Discovery report specifies the virtual server name in the report name. (359050)

When the user enables the Discover all file servers option in the discovery wizard, the resulting file server Discovery report generated will contain the virtual file server name in the report name. When the Discover all file servers option is not used, the report name will include the file server name that the user provided during the File Server Discovery wizard. For reference, each Discovery report is listed along with the FQDN of the associated file server.

The physical file server discovery report generated for a NetApp file server will be named vfiler0 when the discovery task is discovering all virtual file servers. On the Reports page when filtering on the File Server column, Data Manager provides the physical file server's fully qualified DNS name.

File server discovery task fails after Authenticating CIFS IPC Credentials phase (37146)

If a file server discovery task fails and the error identified in the discovery task report is immediately following the Authenticating CIFS IPC Credentials phase, this means that it is the ABE discovery phase that failed.

Workaround: Validate the credentials used for ABE discovery and if the failure persists, disable the ABE portion of the discovery process in the discovery wizard.

Data Manager fails to discover Windows 2000 servers when using the RPC method (347834)

RPC discovery is not supported on Windows 2000 file servers. Use a non-Microsoft Telnet server (or SSH server) or local discovery instead.

Asynchronous output from a NetApp file server is corrupting NFS exports output for the discovered file server. This causes an exception running a File Server Scale report and ARX Configuration wizard (342626)

The output from the asynchronous messages to the console are mistakenly being interpreted as legitimate command output and being inserted into the discovered file server configuration data. When a follow-on activity (reporting, configuration) is attempted, these processes are unable to handle the erroneous data.

Workaround: Check the NetApp console for asynchronous messages. If the console is quiet, then perform discovery again.

File Server Details page: On navigation back to CIFS/DFS tab, the columns lose their default width (351446)

When viewing the tables on the File Server Details page, if you are running IE and re-size the browser window, the columns may appear compressed. Or, use the Reset Columns menu action.

Click the column header as if to sort. The columns will be restored to their original size.

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 (358533)

When using Windows local discovery, make sure you are using the local discovery script that comes with your version of Data Manager.

Local discovery files (named *.dsc) are temporary and are not meant to be compatible between 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 section Performing Local Discovery for Windows File Servers.

Windows behavior affects spelling of discovered OS version name. (343201)

After discovering a Windows 2008 server, Data Manager displays the OS version with an extra r after the word Microsoft and after the word Server, as seen below:

Microsoftr Windows Serverr 2008 Enterprise

This behavior is not exhibited after discovery of a Windows 2008 R2 server.

File servers that asynchronously log messages to the console could cause discovery to fail. (30868)

File servers that allow messages to be streamed to the console asynchronously, run the risk of interrupting the Data Manager file server discovery process. Data Manager recognizes the prompt characters and uses them to identify the completion of discovery commands. If console messages corrupt the prompt string, Data Manager will fail to recognize the completion of the command.

If this is a chronic issue with the file server, due to the logging level or environmental issues, you may need to disable console messages during the discovery process.

If a discovery failed, then the Discovery report is not accessible from the Reports Summary page. (37225)

If a file server discovery fails, then the user can access the report by clicking on the discovery status link on the file server summary page. The problem that remains is that the Reports Summary page also has a row dedicated to this failed task, but you cannot access the report from this page.

Not discovering CIFS shares using Generic discovery on a NetApp 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.

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. 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, and therefore could not enforce these options after virtualization.

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 ARX clients and the ARX appears to the filer as a single client. So, both ARX clients will get the same option setting.

Discovery of Window servers with ABE discovery enabled fails if the NetBIOS name of the server cannot be resolved. (37084)

During discovery of Windows servers, if ABE discovery is enabled, the process on the Data Manager server 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.


Windows file system capacities in cluster resource groups are marked as 0 on the inactive node. (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 target node.

Quotas not discovered properly for Windows clustered file systems on the inactive node. (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 target 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.

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 the following commands 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.

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.

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

For details on disabling simple file sharing, please see Microsoft's Support knowledge base article: How to disable simple file sharing and how to set permissions on a shared folder in Windows XP


 

 

ARX Configuration

CfgWiz: Wizard gets stuck on the Volume Assignment page and the white text area changes to the Import Selection page (359209)

In the Create ARX Configuration wizard, the wizard can get stuck on the Volume Assignment page. You will see the text in the white box at the top of the page change to the text for the Import Selection page. If this happens, click the Cancel button and restart the wizard. This action should clear the issue.

CfgWiz: Can't create a configuration from a failed file server (that was previously discovered. successfully) (35387)

In 3.1.0, the discovery task was separated from the file server object. If a re-discovery of a file server fails, you cannot create an ARX configuration from that file server. Because of the failed task, the file server data is thought to be stale and, therefore, not usable for ARX configurations. You must re-discover the file server successfully to create a configuration.

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.

Add share scripts do not create clustered shares for Windows Cluster Server. (30638)

Data Manager currently uses rmtshare.exe for all share creation in the scripts. This works for Windows Cluster Server but Data Manager does not add the new share to the corresponding resource group.

After completing the execution of the ARX script, you must manually modify your cluster configuration to include the appropriate shares.

Recover NFS exports script is missing ACLs for generated names. (35334)

When an NFS simple 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. In addition, the path defined in the script is for the generated import, not the original export.

The virtualization backout process should reset the file server to the original state which means that it should not include Data Manager-generated share names. The process should tell you to remove the generated share/export names.

Data Manager 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 includes a Compatibility View option which is designed for Web applications developed for older browsers. Data Manager does not support Compatibility View and it must be disabled when viewing Data Manager pages. When Compatibility View is enabled, pages are not displayed properly.

 

 

File System Inventory and Reports

File System Inventory service has high memory utilization and inventory tasks failing (359503)

For some file system structures, Data Manager can scan the file servers faster than it can write the received data into the inventory database. The scanned data is staged in cache before it is written to the database. Data Manager attempts to optimize the balance between scanning and writing, but could exhaust available memory while waiting for write access. This temporary memory exhaustion could cause an inventory task to timeout and fail.

Workaround: If this happens, reduce the number of concurrent inventory tasks and reduce the relative speed of the inventories to better balance performance and resource utilization.

Data Manager supports up to a maximum of unique 250,000 extensions per file system inventory (359501)

Data Manager supports up to a maximum of 250,000 unique extensions per file system inventory. If more than 250,000 unique extensions are discovered, the Top-N table for extensions is dropped, but the list of the first 250,000 extensions is maintained. Files whose extensions are not in the list of 250,000 will have an extension index of -1 in the InventoryExtensions table.

Reports: Case-sensitive character comparisons are used when evaluating file extension and file name criteria against NFS inventories. (341847)

Data Manager uses case-sensitive character comparisons when evaluating file extension and file name criteria against NFS inventories.

Reports: Detail report for local inventory lists number of directories reported more than inventoried in the files and directory section (338590)

Data Manager counts the root as a directory as part of the inventory process. Directory counts include the root directory, as stated in the documentation, tooltips and Help.

Error Handling for NFS and CIFS Inventories: NFS retries and TCP default behavior (358273)

Data Manager uses the following procedure to handle errors with NFS inventories.

NFS TCP is the default protocol. If TCP is not available, Data Manager will revert to using NFS UDP. Data Manager times out each NFS RPC after 30 seconds. After timing out, Data Manager will retry RPCs for up to 3 times (90 seconds). If it does not receive a response to an RPC after 90 seconds, the inventory fails. If the NFS TCP connection itself is terminated, Data Manager will retry the connection 1 time per RPC. If the TCP connection fails more than once for an RPC, the inventory fails.

Data Manager uses the following procedure to handle error with CIFS inventories.

Data Manager uses the built-in Microsoft CIFS client which is TCP-only. Data Manager initially attempts to create a CIFS connection using a hostname (if provided). If connection using the hostname fails, it will attempt to connect with an IP address (assuming the hostname can be resolved). If during a CIFS inventory, the CIFS connection is terminated/reset, the inventory will fail.

Inventory task fails trying to connect to remote CIFS file server. Data Manager log messages indicate that: The account is not authorized to log in from this station. (340922)

To resolve: Review the SMB signing security policies on the Data Manager server and the security policies on the file server and verify that their settings match appropriately.

Also for Kerberos-only environments, review the inventory command lines listed in the f5dm.log file and verify that the appropriate CIFS Kerberos service principals have been configured for the host designation (FQDN, IP or hostname) listed in the inventory command line.

File System Inventory Details page: A chart on a subtab does not display initially. (339777)

If on the File System Inventory Details page, you encounter this issue where a chart is not being displayed, click away from the subtab and then click on the subtab again. The chart should display properly.

Uploading an MS Excel-created File Criteria CSV file into Data Manager may not succeed. (38224)

To correctly create the CSV file in Microsoft Excel, do the following:

  1. In Excel, ensure all the columns are formatted for text:
    1. Select all columns, then right-click to display the menu.
    2. In the menu, click on Format Cells, then select text.
  2. When entering values in each cell:
    1. Start each entry with two single quotes.
    2. End each entry with a single quote.
  3. The following example shows how to create a file criteria that can be used to identify files that are less than 1 week old.
  4. Enter the following in the first three cells of the first row.

    In cell 1, type: ' 'File Group 1'
    In cell 2, type: ' 'OneWeekOld'
    In cell 3, type: ' 'RM<(1.0 weeks)'

CIFS inventory cannot recognize a directory with a . (dot) at the end of its name. (39748)

Some file servers generate special names for directories and end these directory names with a . (dot).

Directories ending with a dot come across to Data Manager as ending in a tilde (~) followed by a number. Because Data Manager has not received the directory name information correctly, it cannot report it correctly. If the file server creates filer-generated-names (FGN) for these directories, they don't show up in the count of Directory Names Ending in '.' in the File System Inventory Details page (Files/Dirs tab, General subtab, Special Files section).

CIFS inventory not detecting files with named streams on NetApp with UNIX security file system. (39393)

When completing an inventory on a discovered NetApp file server CIFS share, if the discovered CIFS Shares have a file system type of UNIX, Data Manager will fail to correctly identify files that have named streams attached to them. Currently, there is no workaround.

For more information on files/directories with named streams, consult the Data Manager User's Guide.

Data Manager reports output in XLS format cause Excel to display warnings about file's format. (338331)

When Data Manager reports are saved in XLS format and users double-click on the files to open them, Excel starts, but a warning message is displayed, stating that the files do not appear to be in Excel format and warning the user about proceeding. If the user agrees to proceed, the files are displayed correctly.

User should accept the warning and proceed.

File system inventory does not work on shares that are a DFS root. (38649)

Note that Data Manager does not support inventorying shares with remote redirects.

File system inventory task takes too long or never finishes.

If you have inventories that never seem to finish, 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.
  • Workaround: The Inventory wizard lets you specify a list of directories to be ignored during the inventory process. If the File Server Type was not selected, the snapshot directories are not included in the default ignore list and if not explicitly excluded, Data Manager will inventory through all retained snapshots.

  • CIFS environment containing circular reparse points. In CIFS environments, Data Manager inventories follow reparse points.

    Workaround: You can disable this behavior through an option in the Inventory wizard to avoid following reparse points.

Section selection does not work for a standard File System Detail report in RTF format. (32576)

If you generate a standard 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. Based on research on 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."

Mapped drives on Data Manager server cannot be (locally) inventoried. (30526)

When attempting to inventory a mapped drive (non-local drive), Data Manager reports that the path is not found. Data Manager cannot inventory mapped drives through the "local drive" method.

The task of inventorying a Windows CIFS share from Data Manager fails, but succeeds after reboot. (34173)

You encounter this connection error on a Windows server when trying to inventory a CIFS share 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 or expired password.
  • Service using a user account with an invalid or expired password.
  • Trust relationship has been broken.
  • Network error reaching domain controller. (Attempt to mount a domain from a different server in the same domain.)
  • DNS server connection issue.
  • Permissions have changed on the share.
  • Date/time skew on the local machine.
  • Account has been suspended or locked out.

Workaround: Rebooting the data Manager server clears some of 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.

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

Workaround: Open the file outside the browser (or use Internet Explorer). The file is located in the Reports directory. You can view the path to the Reports directory on the Settings page, Reports tab.

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

You can see Total of all inventoried file sizes on the Storage tab (Capacity subtab). In the Data Manager GUI, click:

Inventories > File System Inventory Details > Storage tab > Capacity subtab > Disk Capacity Information table > 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.

 

 

Installation

Data Manager will not install on a domain controller. (336481)

In Data Manager v3.0.0 and above, the user will receive an error dialog during the installation process stating that Data Manager cannot be installed on an Active Directory domain controller. Installing on a domain controller is not supported.

Data Manager creates a backup of the installation database as part of the upgrade procedure. (337238)

During the upgrade procedure, Data Manager creates a backup.zip file in the db directory that contains the original database before upgrade occurs, not the upgraded database.

Data Manager requires uninstall of old version before installation of new version. (34777)

If you attempt to install Data Manager while it is currently installed, the installer informs you that a previous version of Data Manager is installed and instructs you to uninstall that version manually before you can proceed with a new installation. For details on this process, see the Data Manager Installation Guide.

Never install a Trial version over a Full version (359451)

A Trial version of Data Manager should never be installed over a Full version. Data Manager will not allow this operation in the installer. For more information on installation issues and details, consult the Data Manager Installation Guide.

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.

 

 

Miscellaneous

NFS Details Page for a file server shows all columns as two characters wide and with lots of empty space (358011)

When viewing file server details using IE8, you may find the columns become compressed if you swap between the various tabs.

Workaround: Should this occur, just reset the columns by clicking on this option under the View menu item.

If users attempt to upgrade from 3.00.00x to 3.1.0 while exceeding the 3.1.0 limit of 100 schedules, they will see a status of Unknown (351681)

During an upgrade from a pre-existing version of Data Manager to 3.1.0, Data Manager will create unique schedule objects for any existing inventory task.

Data Manager version 3.1.0 supports a maximum of 100 uniquely-named schedules. After upgrading the application, if the inventory task displays an error of unknown status with the date in parenthesis, this indicates there are tasks that could not have a schedule associated with them in version 3.1.0 because it would exceed the maximum for schedule objects.

Workaround: One workaround is to review schedules to find duplicates (for example, schedules with the same interval) and consolidate them into a single schedule. A second workaround is to replace schedules for tasks with unknown status with an existing schedule object.

If the application port setting has changed, users may have to logoff current sessions to refresh URL links. (28676)

When the application port setting is changed, the acopia.url file is updated. Data Manager uses this file to direct the desktop icon and "Launch Data Manager" programs item to open a Web browser to the Data Manager application.

If the application does not launch after these settings are changed, you may have to log off and log in to the Windows OS to clear any cached file data.

Regardless, for the new port setting to take effect, you must first manually restart Data Manager using the Data Manager Control Panel.

Corrupt f5dm.zip is created when system memory usage too is high. (30735)

If you attempt to collect diagnostics and the f5dm.zip file is corrupted, it may be because memory usage on the Data Manager server is high. Stop non-essential applications and stop all inventory tasks or restart Data Manager and you should be able to collect diagnostics successfully.

[ Top ]

Contacting F5 Networks

F5 Networks Online Knowledge Base: http://support.f5.com

F5 Networks Services Support Online: https://websupport.f5.com

Support telephone numbers: http://www.f5.com/training-support/customer-support/contact/

For additional information, please visit http://www.f5.com.


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)