Updated Date: 08/29/2013
This release note documents the version 4.0.1 release of the ARX software. We recommend this maintenance release for those customers who want the fixes and enhancements listed in Fixes and Enhancements in This Release.
This release is cumulative, and includes all fixes and enhancements released since version 2.6.0. You can apply the software upgrade to 2.6.0 and later. For information about installing the software, please refer to Installing the Software.
Note: F5 offers both feature releases and maintenance releases. For more information about our release policies, refer to Description of the F5 Networks software version number formats.
In addition to these release notes, the following user documentation is relevant to this release.
These manuals are available from the ARX® GUI or CLI. From the GUI, click on the Documentation link in the navigation panel. From the CLI, use the show software command for a complete listing of the ARX manuals, then use the following command to upload the manual from the ARX:
copy software manual-name destination-url
You can also find the product documentation on the AskF5 Technical Support web site, along with an extensive solutions database.
The supported browsers for the ARX GUI are:
This release supports the following hardware platforms:
There are no new Certifications for Release 4.0.1.
For Release 4.0, F5 Data Solutions tested and qualified the following 10-gigabit-networking devices with the ARX®4000:
In Release 3.0, F5 Data Solutions has certified IBM NAS 500G file servers.
An ARX volume can coordinate snapshots amongst the filers behind it. This ARX-snapshot feature supports the following filer-software releases:
All other filers not explicitly listed above are not supported. When the snapshot subsystem attempts a snapshot on an unsupported filer, the error is written to the report and the ARX syslog.
For an existing installation, you can upgrade to 4.0.1 from any of the following releases:
For installation instructions, refer to the Upgrading Software chapter in the CLI Maintenance Guide.
This release also includes a new version of firmware. You can upgrade the firmware during the software upgrade; the instructions in the above manual explain how and when to upgrade the firmware.
As mentioned above, this release includes a firmware upgrade. If you are upgrading from Release 3.0 or earlier, the new firmware supports NSM recovery and NSM binary-core files. The NSM recovery feature allows an NSM processor to recover after a failure without necessarily rebooting the entire ARX. After you upgrade the firmware, you can use the nsm recovery CLI command to enable failovers between NSM processors. Refer to the "Preparing for NSM Recovery and Diagnosis" chapter in the CLI Network Guide for full details about the NSM-recovery feature and the nsm recovery command.
Warning: You must reboot the ARX to enable the NSM-recovery feature. If you have a redundant pair of ARXes, enable NSM recovery on the backup ARX first, then enable it on the primary ARX (causing a failover to the backup) during off hours. A standalone ARX endures a longer service outage as the ARX reboots; for this reason and others, we recommend redundant ARXes for sites that support extensive client traffic.
Once you install the software, refer to the Required configuration changes section, which contains important information about changes you must make before using the new software.
This release includes the following fixes and enhancements.
Release 4.0.1 is functionally equivalent to Release 4.0. Unlike Release 4.0, this release has been fully qualified for use on the ARX®6000 as well as all the other ARX platforms.
Release 4.0.1 fixes the following software issues:
The ARX4000 allows the Control Plane to power up when the Data Plane is powered off and/or disconnected. This is an unsupported configuration that causes a software loop and prevents the ARX from fully booting.
Note: The fix for this bug does not resolve the problem for an ARX4000 that supports jumbo frames. (You can enable or disable jumbo frames with the [no] jumbo mtu CLI command.)
A managed volume prematurely disconnects from an unresponsive back-end filer. If the filer connection improves, this unnecessarily extends the time that ARX clients cannot access the filer's storage.
Downgrading from a 3.aa.bbb release to a pre-3.0 release triggers a re-import of all managed-volume shares on the ARX. This only occurs in a redundant pair of ARXes, where the peer is still running the pre-3.0 release. This can occur during an unsuccessful upgrade.
A CIFS volume may create a hidden-subshare name (for example, "_acopia_dir5_3$") on a back-end filer, and then record it incorrectly in its database. The volume is then unable to find the back-end subshare(s). This only occurs for subshares that are exported with the hidden or expose-hidden option.
If a CIFS client attempts to access "\\vip\C$\~snapshot" in a namespace that supports both Windows management (MMC) and snapshots, the namespace software fails. The "C$" share is a virtual share offered for Windows-management access (for example, through MMC). The "~snapshot" directory is a virtual directory for accessing snapshots within an actual share, but does not offer any snapshots in the virtual "C$" share.
For example, suppose the volume(s) in a CIFS namespace is/are shared through a CIFS service at 192.168.25.15 (a virtual-IP address, or VIP). If a client maps the "G" drive to \\192.168.25.15\C$ and then starts working in the "G:\~snapshot" directory, the namespace behind the 192.168.25.15 VIP fails.
The current release includes the fixes and enhancements that were distributed in prior releases, as listed below. (Prior releases are listed with the most recent first.)
This section describes the features and fixes from release 4.0. Sites that upgrade from release 3.2.0 and earlier get the benefit of all the features and fixes described here, in addition to the features and fixes described above.
Release 4.0 adds the following features:
Release 4.0 supports the new ARX®4000 hardware platform, which is a 4U device with 10-gigabit interfaces. The ARX®4000 has storage capabilities equal to the larger ARX®6000 with 2 ASMs and 2 NSMs.
The Link Aggregation Control Protocol (LACP, defined in IEEE 802.3ad) dynamically manages the member ports in a channel. For example, if a configuration change disqualifies a port for channel membership, LACP processes automatically detect the change and stop using the port in the channel. Release 4.0 supports passive LACP, which you can configure with the lacp passive CLI command. Refer to the Layer-2 chapter in the CLI Network Guide for details on LACP and LACP configuration.
Release 4.0 fixes the following software issues:
When l2 failed on the senior switch, it detected a remote metalog error and causes the junior switch to fail. Since the senior is already rebooting due to the l2 failure, this causes a dual reboot.
Remove-share nomigrate incorrectly requires "force" on failed import share. The "remove-share nomigrate" command used by the GUI and from priv-exec at the CLI required the "force" option to remove a share that failed import.
Policy is unable to move files from one share to another. When looking at the shares in the managed volume, freespace is being reported ok, yet when a place rules is enabled, policy is unable to move files.
This section describes the features and fixes from release 3.2.0. Sites that upgrade from release 3.1.0 and earlier get the benefit of all the features and fixes described here, in addition to the features and fixes described above.
Release 3.2.0 added the following features:
Microsoft Windows VSS (Previous-Versions) Support for ARX Snapshots
Windows offers an interface called Volume Shadowing Service (VSS) (called "Previous Versions" in Windows Vista) for accessing snapshots. Clients can select a file or directory from their Windows Explorer, pull up the Properties sheet, and click on the Previous Versions tab. This tab displays all snapshots for the chosen file or directory. As of Release 3.2.0, a managed volume that supports snapshots can offer them through VSS.
Automated Controls for CIFS-Accessible File/Directory Names Ending In "." (28630)
Trailing spaces and periods (for example, "myFile.txt." or "myDirectory ") are illegal for most implementations of CIFS, though they are supported by the filesystem under Windows. Some CIFS vendors convert any file or directory names with trailing periods into Filer-Generated Names (FGNs). In Release 3.2.0, a managed volume probes its back-end shares for this behavior and prevents any trailing-period names from migrating to those shares. Refer to the CLI Maintenance Guide for more information on illegal trailing characters in CIFS volumes.
ARX Secure Agent Support for 64-Bit Windows 2003 DCs
The ARX Secure Agent (ASA, described in Secure Agent Installation) now runs on 64-bit Windows 2003 DCs. There are no functional changes to the ASA.
Release 3.2.0 fixed the following software issues:
If a CIFS client joins a new Windows group while connected to an ARX-CIFS service, the client must disconnect from the ARX service and remain disconnected for at least 10 minutes to get the group's access permissions.
The snapshot manage command causes the ARX to reboot if it runs on a CIFS volume with a particular configuration issue. The issue is that the actual share name (for example, "MYSHARE") has different case from the one defined in the ARX volume (for example, "MyShare"). In the CLI, you define the share name with the gbl-ns-vol-shr filer command.
If a file-placement rule has spaces in its name, its report name does not have quotation marks ("") around it in the global-config. Without the quotation marks, the report command fails when you run the global-config in the CLI.
If you perform a no share or no filer command using the force argument and omitting the remove-file-entries option, all files on the removed share remain in the volume's metadata. This leaves the files visible to clients even though they are inaccessible.
The volume failure occurs on import if filer-subshares is already enabled before the import, or when filer-subshares is activated later on the already-running volume (for example, with the cifs export-subshares CLI command).
A CIFS managed volume with cifs path-cache enabled may create malformed Query-Path-Info packets for named streams. A CIFS client can only trigger these malformed queries in a front-end share of a subdirectory (not the root) of the ARX volume.
This section describes the features and fixes from release 3.1.0. Sites that upgrade from release 3.0 and earlier get the benefit of all the features and fixes described here, in addition to the features and fixes described above.
Release 3.1.0 added the following features:
Maximum CIFS Exports Increased from 9,000 to 16,000 (28867)
As of Release 3.1.0, the ARX can support a total of 16,000 CIFS front-end shares.
Add Drive Letter to MSRPCs that Require It (28337)
Some Microsoft Remote Procedure Calls (MSRPCs) require a file or directory path in their returns. Prior to release 3.2.0, the ARX omitted the drive letter from these returned paths; now a CIFS service includes the drive letter if it has browsing enabled.
Full NSM Core Dumps
You now have the option to enhance the core-dump files produced by a failed NSM processor. By default, a failing NSM processor produces an ASCII-text file with its current state. The new nsm binary-core-files CLI command enhances the files to a much-larger binary format, with more information that F5/Acopia® engineers can use for diagnosing the cause of the failure.
Faster Failover Times (28901)
The 3.1.0 release includes enhancements in failover times between redundant ARXes. Lab testing has shown failover times that have improved from 34 - 60%.
Enhancements to CLI "show health," GUI "Status," and E-mail Notifications (27313, 26514)
The SNMP-based indicators of ARX health now offer better support for redundancy features. New indicators notify you of NSM-core failovers, ARX failovers, and quorum-disk failures. These indicators appear in the CLI's show health command, the GUI's "Status" screen (under "System Health Information"), and in E-mail notifications.
The CLI "wait-for migration" Command is Fully Supported
The CLI command, wait-for migration, was formerly accessible only if the terminal beta flag was raised. As of release 3.1.0, this command is fully qualified, accessible, and documented.
Timeout Option for all CLI "expect" Commands (26737)
Every CLI expect command now has a timeout option, which sets a time limit on the operation. The CLI documentation contains the full syntax.
Reload Option for the CLI "clear nvr" Command (28697)
In previous releases, the clear nvr command halted the chassis at the end of the operation, so that you had to turn the power back on manually. This was designed for preparing the chassis for shipment. In 3.1.0, you have the option to reload the chassis instead of halting it.
Beta Option: Defer Setting "Trust for Delegation" During a Domain Join Operation
If an ARX-CIFS service supports Kerberos authentication, you must perform a domain-join operation to join the service to an Active-Directory domain. The CIFS Service must also have "Trust Computer for Delegation" set at the domain controller. By default, the CLI domain-join command (and its GUI equivalent) requires a username and password with sufficient credentials to set the "Trust Computer for Delegation" flag at the DC. The 3.1.0 release offers a beta option to avoid setting the flag from the ARX:
domain-join domain-name no-trust-for-delegation
You can use lesser credentials to run the command with the no-trust-for-delegation flag raised, then log onto the DC with stronger credentials and raise the flag from there.
This is a beta option that has not been fully qualified. You must use the terminal beta command from the CLI to enable this and other beta features.
Release 3.1.0 fixed the software issues below. Fixes for these issues are also included in the current release:
The show exports external-filer filer-name command defaults to a spurious IP address, 22.214.171.124, if the ARX definition for filer-name has an undefined IP address. The command should return an error instead of defaulting.
If a back-end filer uses NFS filehandles that do not align with four bytes (that is, the number of bytes is not evenly-divisible by four), the ARX may reboot repetitively. Only unsupported NFS filers, such as those from Permabit, use NFS filehandles that cause this problem.
A redundant pair of ARX6000s cannot join if the redundancy link has excessive latency; the backup switch repeatedly reboots without ever fully joining its peer.
Solution: For sites with great distances between ARX6000 peers, F5 Support can extend the redundant pair's tolerance for a long latency.
A file-placement rule stops scanning directories if a filer returns a serious scan error (such as "path too long") for a single directory.
Solution:: The rule now logs the failed directory in its show policy statistics and continues the scan. The rule retries all such failed directories after the scan is otherwise complete, and marks the rule as "failed" if the scan errors persist.
This section describes the features and fixes from release 3.0. Sites that upgrade from release 2.5.2 and earlier get the benefit of all the features and fixes described here, in addition to the features and fixes described above.
Release 3.0 provided the following features and enhancements:
Snapshot integration (CIFS only)
Release 3.0 provides the ability to manage the generation, removal, and scheduling of periodic snapshots on a per ARX virtual volume basis across heterogeneous filers. Additionally, the ARX can control access and presentation of snapshots.
Automatic Volume Sizing (AVS)
With AVS, the number of reserve files is automatically set to 4 million files when an ARX managed volume is created. The reserve file limit is automatically increased by 4 million files every time the number of available file credits falls below 2 million. AVS is automatically disabled if the new required limit exceeds the maximum number of reserve files supported within the managed volume or VPU. For information on the maximum file limits supported per ARX platform, see the Site Planning Guide.
Auto Close File Migration
Prior to 3.0, the ARX policy engine would not migrate CIFS files that remained persistently open. The policy engine attempted to migrate an open file for a fixed number of retries. If unsuccessful, the policy rule proceeded to the next file. When complete, the policy engine marked the rule as "FAILED" and generated a report indicating which files where not migrated.
With Release 3.0, you can optionally configure a file-placement rule to automatically close any file opened by a CIFS client. The policy engine holds the file closed until it has finished migrating or until the migration request is cancelled.
SNMP Traps and E-Mail Notifications
The smtp welcome command was added to send an introductory (welcome) E-mail to all members in an email-event group. The introductory message informs the recipients of the types of system events they will be receiving through E-mail.
A description field was added to the email-event command.
The warmStart trap has been modified to append the cause of reboot in the message text (traplog and email). All reboots are now recorded in the reboot history log file. The SNMP trap text has not been changed.
Robust SID Translation
Prior to 3.0, mis-translation of Security Identifiers (SIDs) could occur if local and domain groups had the same names. With V3.0, the SID translation algorithm has changed so that only locally-defined user and group SIDs are subject to translation. This enhancement permits identical user and group names to be defined both locally on a file server and within an Active Directory domain.
CIFS Sub-Share ACL improvements
Prior to V3.0, with CIFS sub-shares enabled, an ARX managed volume did not support multiple CIFS shares on the same filer. V3.0 removes this limitation, and enables migration, tiering, load balance share farms on a single file server where CIFS sub-shares are configured.
CIFS AD Forest-to-Forest Trusts
In a Windows 2003 Active Directory forest, you can link two disjoint Windows 2003 forests together to form a one-way or two-way trust relationship. A two-way forest trust is used to form a transitive trust relationship between every domain in both forests.
Forest trusts can provide the following benefits:
V3.0 allows for support for CIFS Kerberos authentication across Windows 2003 two-way (or bi-directional) forest-to-forest trusts.
CIFS AD Auto-discovery from the ARX switch
Prior to 3.0, Active Directory forest information had to be manually collected from customers and manually configured in the ARX switch.
V3.0 enables the ARX switch to perform automatic discovery of all Active Directory information. The auto-discovery feature works within a single AD forest and does not auto-discover forest-to-forest trusts. This feature greatly simplifies and makes less error prone the installation of the switch in CIFS Kerberos environments.
Deterministic directory mastership when using NSCK Rebuild
Prior to V3.0, in some configurations directory mastership was not deterministic after an nsck ... rebuild operation. After the operation dis-assembled all volumes in the namespace and re-imported them, directory mastership was distributed across all shares. In 3.0, the ARX software determines directory mastership based on configured place-rules. For example, if age-based tiering is configured, then all master directories will be assigned to tier-1 share(s).
Release 3.0 also included fixes for the following issues. Fixes for all of these issues are also inlcuded in the current release:
This section applies to installations that are upgrading from Release 2.7.0 or earlier.
Release 2.7.1 contained fixes the following issues. These fixes are also included in the current release:
NFS/TCP mounts can take several seconds on a busy ARX.
Additional Recommendation for ARX®6000 Platforms: Use the resource gateway command to dedicate two network processors to policy. See the CLI Network Guide for details on using this command.
In rare cases, a volume that failed an earlier import may cause a larger service outage for the duration of a redundant-switch upgrade. All of the volume's front-end services are inaccessible until both switches complete their upgrades. During this outage, the volume repeats the following message in the syslog:
"non-persistent database corrupted. Reinitializing volume."
This only applies to a specific and uncorrected import failure, to redundant-switch upgrades, and to upgrades from 2.7.0 (or earlier) to 2.7.1 (or later).
In a system with a large configuration (for example, hundreds of attach points in a presentation/direct volume), front-end services may not appear on the newly-active ARX after an otherwise-successful failover.
If an ARX experiences an NVRAM-hardware failure on boot-up, and an administrator allows the ARX to finish its failed boot, a rare race condition may occur between the ARX and its redundant peer. The effect of this race condition is to stop all storage services at the peer.
A presentation (or "direct") volume with more than 4,000 attach points can perform an excessive number of redundant operations. This results in excessive syslog messages and slow processing for clients.
If a directory in one CIFS share (for example, "longnameddirectory") has an alternate "8.3" name (e.g., "LONGNA~1") that collides with a directory in another CIFS share (with an actual name of "LONGNA~1"), the sync files command mistakenly assumes that all of the files in the first directory("longnameddirectory") actually reside on the other share.s directory (with the actual name of "LONGNA~1"). Clients cannot access the files unless someone runs another sync files operation.
If a volume's CIFS client attempts to set the FILE_ATTRIBUTE_OFFLINE attribute (often used in stubs for filer-ILM applications), and one of the volume's filers cannot accept it, the volume may lock out all client access.
Current Solution: Specific errors in the syslog indicate that this attribute was rejected by a particular filer, and F5/Acopia® personnel have tools to work around the issue. Contact F5 Support if a CIFS volume blocks out client access and you see any TRANFS-...-INVOFFLINE or TRANFS-...-INVPARAM errors in the syslog.
If a file or directory in a source volume is renamed between shadow copies, and the new name is different from the old name in case only (e.g., "myfile.txt" becomes "MYFILE.txt"), the later shadow copy fails with a STATUS_OBJECT_NAME_COLLISION error. This only occurs in a shadow volume that supports CIFS.
When a directory changes in a shadow-copy rule's source volume, the rule attempts to syncronize its parent directory first. If the parent-directory fails to syncronize, the rule skips the changed directory.
When a back-end directory is promoted to "master" on particular back-end share, all of its subdirectories go to the same share regardless of the constrain-directories setting for the subdirectories.
This section applies to installations that are upgrading from Release 2.6.0 or earlier.
Release 2.7.0 added three features, also included in this release:
Release 2.7.0 fixed the following issues. Fixes for these issues are also included in this release:
A place rule stops trying to migrate an open file after only five retries (two minutes and thirty seconds total); the timeout should be much longer. The solution was to increase the timeout to several hours.
The collect diag CLI command (and its GUI equivalent) includes system reports in the collected data; the diag option is supposed to omit reports, to keep the collected data at a reasonable size.
This section applies to installations that are upgrading from Release 2.4.3 or 2.05.00x.
Release 2.6.0 added two features, also included in this release:
Forest-to-Forest Trusts (Kerberos)
The ARX now supports authenticating users across multiple Win2003 Active Forests when a bi-directional trust exists between the forests. This allows clients in one of the AD forests to access a CIFS service in the other forest. In Release 2.6.0, the ARX can support these forest-to-forest trusts, allowing clients from a remote AD forest to authenticate with services in the local AD forest.
Shadow-Copy Support for CIFS Open Files
In release 2.6.0, you can use the optional allow-shared-access command to shadow-copy files that are already open for write or delete by others. By default, a shadow-copy rule blocks any writes from CIFS clients while it opens a file to copy it. No other client can write to the file or delete it in the middle of the copy operation. This prevents any corruptions in the shadow-copy of the file. However, if some other application is already holding the file open for writes before the shadow-copy rule opens it, the shadow-copy rule cannot open the file with read-only access. This can block the overall shadow-copy operation. In Release 2.6.0, you can use the optional allow-shared-access command to successfully shadow copy any such open files.
Release 2.6.0 also added fixes for the following issues:
This section applies to installations that are upgrading from Release 2.4.3 2.5.0, or 2.5.1.
Some Excel-spreadsheet Macros fail when accessing the Excel files through the ARX.
This section applies to installations that are upgrading from Release 2.4.3 or 2.5.0.
Release 2.5.1 offered these enhancements, also included in this release:
Forcing a Volume to "Take Ownership" of a Back-End Share
A managed volume can now take ownership of a filer share that is evidently (but not actually) owned by another managed volume. This is an option for the CLI command, enable, for a share (in gbl-ns-vol-shr mode); refer to the CLI documentation for use cases and other details.
Flexible Naming for CIFS Services
CIFS services now support NT domain names that do not match their AD domain names. Refer to the documentation for the CLI command, windows-domain (gbl-gs).
for removing shares from a managed volume.
Latency Statistics for Quorum Disks
The CLI command, show redundancy quorum-disk, now shows latency statistics of the quorum disk over time. This is useful for anticipating redundancy-related issues.
Time Windows for Log Collection
You can focus the collection of log messages by choosing an optional start time and end time. Refer to the documentation for the CLI command, collect logs.
Monitoring for CIFS-Client Activity
A new CLI command, show cifs-service client-activity, shows details about a CIFS-client connection to the ARX, as well as the proxy connections from the ARX to the filers behind it.
Release 2.5.1 included fixes for these issues in addition to the above enhancements:
In installations with high-numbered IP addresses (140.x.x.x or higher) and many simultaneous connections, the ARX periodically loses contact with a back-end filer.
The SSH key changes after the software upgrade, requiring administrators to update their copy of the key.
This section applies only to installations that are upgrading from Release 2.4.3.
Release 2.5.0 offered the following features, also included in this release:
Faster Imports into Managed Volumes
In previous releases, managed volumes import options were not configurable. V2.05 allows the user to select various import options such as multi-scan and protections on a per volumes basis. Additional internal architecture changes where also made to significantly improve import performance. Additionally, a managed volume does not spend time protecting its metadata during the import; metadata protection is rarely necessary until the volume is running. Both options are configurable. Managed-volume imports are significantly faster with these options enabled, along with some other internal optimizations.
Support for CIFS subshares and their ACLs
This release supports CIFS subshares and their share-level ACLs. A subshare is a CIFS share that is nested within another share. The top-level share often has a different share-level Access Control List (ACL) than each of its subshares. By default, a managed volume accesses directories through the filers top-level share, even when a client connects to a subshare on an ARX CIFS service. The managed volume connects to the top-level share, subjecting the client to the ACL there, and then descends to the desired subdirectory. With this new feature, the ARX can pass a client from a front-end subshare directly to the corresponding back-end subshare where the filer will enforce share level security.
No Client Restrictions in Multi-Protocol (NFS and CIFS) Volumes
Clients of a multi-protocol managed volume can now create directories with any name. In previous releases, volumes did not permit any names that resembled filer-generated names (FGNs, such as "myDir~1").
Ability to Migrate a Metadata Share
There is a new option to migrate a managed volume's metadata from one dedicated share to another.
You can use a new CLI command, firmware upgrade, to install any new firmware bundled with the latest software release. This command is documented in the software-upgrade chapter of the CLI Reference.
Release 2.5.0 included fixes for the following issues:
This section only applies to installations that upgraded from Release 3.0 or earlier.
Once you have installed the software, you must make the following required configuration change(s).
Upgrade Firmware and (Optionally) Set NSM Recovery
As mentioned above, Release 3.1.0 includes a firmware upgrade. This upgrade is required to support NSM recovery and NSM binary-core files. The NSM recovery feature allows an NSM processor to recover after a failure without necessarily rebooting the entire ARX. After you upgrade the firmware, you can use the nsm recovery CLI command to enable failovers between NSM processors. Refer to the "Preparing for NSM Recovery and Diagnosis" chapter in the CLI Network Guide for full details about the NSM-recovery feature and the nsm recovery command.
Warning: You must reboot the ARX to enable the NSM-recovery feature. If you have a redundant pair of ARXes, enable NSM recovery on the backup ARX first, then enable it on the primary ARX (causing a failover to the backup) during off hours. A standalone ARX endures a longer service outage as the ARX reboots; for this reason and others, we recommend redundant ARXes for sites that support extensive client traffic.
For Sites with Windows Filers, New Filer Setting Required for NTLM Connections
Before Release 3.2.0, the ARX used "non-extended security" for its NTLM-authencated connections to back-end filers. To correct Issue 27316, the ARX started to use "extended security" for its CIFS connections. However, newer Windows servers require NTLMv2 (not NTLM) for its "extended security" connections. To prepare for an upgrade to Release 3.2.0+ in an installation with Windows filers, verify that the following parameter (from the Windows security-policy UI) allows NTLM connections:
Network security: minimum session security for NTLM SSP based clients.
This policy parameter should be set to "No minimum;" none of the four flags for this parameter should be raised.
The following parameter must also be set so that it does not refuse NTLM from clients (such as the ARX). This was required for ARX Releases before 3.2.0, so you only need to investigate this for new Windows filers or new ARX installations:
Network security: LAN Manager authentication level
You must reboot the Windows server for this (or these) changes to take effect.
The following items are known issues in the current release.
The ARX4000 Data Plane (NSM side) cannot recover from a power failure until the Control Plane (ASM and SCM side) reboots. (29444)
If the Data Plane (the lower half of the chassis with the network ports) loses power independently of the Control Plane, the Data Plane cannot recover by itself. If both halves of the chassis lose power at the same time (a more-likely event), both halves reboot normally.
Best Practice: The Data Plane and Control Plane each have two power supplies. Connect one power supply from each Plane to one power source, and the other power supply from each Plane to an alternate power source.
Recovery: Stop and restart power on the Data Plane (the upper half of the ARX). This causes both modules to power up in the proper sequence.
UTF-8 Chinese characters are truncated in namespace name. (30941)
If a user enters Chinese characters that exceed the GUI's limit for any input field, the GUI will not issue an error message but instead simply truncates the input.
The GUI input fields limit input based on characters and not bytes. When entering multi-byte characters, the input may be truncated if the total number of bytes representing the characters exceed the internal byte limit.
The CLI "show clock" output does not always show the correct time after a time-zone change. (24526)
You can use the clock timezone CLI command to set the time zone of the ARX. On rare occasions, the output from the show clock command does not show the correct time after this change. For example:
ARXa500# clock set 14:43:00 01/11/2007
ARXa500# show clock
Local time: Thu Jan 11 14:43:02 2007 EST -0500 America New_York
Universal time: Thu Jan 11 19:43:02 2007 UTC
ARXa500(cfg)# clock timezone America Denver
ARXa500(cfg)# show clock
Local time: Thu Jan 11 14:43:13 2007 EST -0500 America Denver
Universal time: Thu Jan 11 19:43:13 2007 UTC
The time does not conform to the new time zone, though the correct new time zone (America Denver) does appear in the output.
Workaround: Log out of the CLI and log back in.
During the hour of transition from daylight-savings time to standard time, the clock set CLI command incorrectly interprets times in some time zones. (24709)
Times are ambiguous in the hour when daylight-savings time reverts to standard time, once per year. Suppose the transition occurs at 3 AM on the day of the daylight-savings change: time passes from 3 to 4 AM in daylight-savings time, then the clock goes back to 3 AM for standard time, and then time passes from 3 to 4 AM again. In some time zones, if you reset the clock to a time between 3 and 4 AM, the clock set command may not interpret your time correctly. If this occurs, the ARX assumes that the transition to standard time has already occurred.
This only occurs in time zones that are East of the Prime Meridian, with positive offsets from UTC.
Workaround: Avoid the clock set command during the day and hour of transition.
A client IP address remains in the output of show nfs-service mounts after the client unmounts. (24478)
The output of the show nfs-service mounts command is a table of NFS mounts from client machines. For each currently-active client mount, the table displays the Global Server, the mount point, the VIP, and the client IP address.
When the client is unmounted, there may be a slight lag in the update of table information, and a repeat of the show nfs-service mounts command may show the client still mounted.
Workaround: Retry the show nfs-service mounts command.
An ARX500 drops untagged packets on VLAN 1 (the default VLAN) after you re-play its running-config. (31435)
Replaying a running-config is a necessary final step in replacing an old ARX500 with a new one. This is only a problem if the ARX500 uses untagged layer-2 packets on the default VLAN, VLAN 1.
Recovery: Reboot the ARX after replaying the running-config. From the CLI, you can use the reload command to reboot the ARX.
The ARX cannot send E-mail messages through the out-of-band (OOB) management interface. NTP, DNS, RADIUS, and snapshot-management services (SSH and RSH) are also unsupported through the OOB interface. (24595)
All e-mail notifications from the ARX go out through an in-band (VLAN) management interface, configured with the interface vlan CLI command. At least one in-band-management interface must have a route to the E-mail server for E-mail notifications to function. The same applies to NTP, DNS, and RADIUS services, as well as SSH and RSH for managing filer snapshots.
Workaround: Use the cfg-mode ip route command (without the mgmt flag) to add a static IP route to the E-mail server(s), NTP server(s), DNS server(s), and/or RADIUS servers. All filers and file servers must have a route to be useable by the ARX at all, so this is less likely to be an issue for SSH and RSH.
The management address for an external filer cannot be on the out-of-band (OOB) management subnet for the ARX. (25487)
To support coordinated snapshots in an ARX volume, the volume requires the management-IP address for the filer. You set this with the ip address a.b.c.d management CLI command, or its GUI equivalent. This address cannot be on the same subnet as the ARX's OOB interface. This is related to issue 24595, above.
Changes to the global-config may be lost while the standby switch is still booting. (28844)
After a failover, the standby switch may take several minutes to reboot. During this time, while the active and standby switches are syncronizing their databases, it is possible for changes in the global configuration to fail with a database error.
Workaround: Wait for the standby switch to finish booting before making any changes to namespaces, policies, or other storage-related objects. In the CLI, all storage-related objects are under gbl mode.
Spurious errors appear in the syslog after an NSM failover. (25782)
NSM processors have redundant peers, even in an ARX that is not configured for overall redundancy. If an NSM processor fails, its peer processes packets for both. If nsm recovery is enabled, the failed processor comes back online and waits to take over for the running processor. The failed processor may repeatedly put the following message in the syslog:
NAT rule TCP/ip-address:port for remote action ip-address-2:port-2 type 3 not found.
This syslog message is spurious.
The show ntlm-auth-server status CLI command gets an OPEN_SSL_ERROR string if the NTLM-server password is too long. (31029)
The Acopia Secure Agent (ASA) applet and the ARX CLI allow an ASA password of up to 64 characters, but underlying encryption software supports a maximum of 22 characters.
Workaround: If you see this error, change the password so that it is 22 characters or less. This change must occur in two places: at the NTLM-Authentication Server (where the ASA is installed) and at the ARX CLI. For instructions on modifying the ASA password, both on the ASA and in the ARX CLI, refer to the Secure Agent Installation manual.
You must separately export a CIFS managed volume if you use it as a "managed volume" in a CIFS direct volume. (21231, 24359)
If a CIFS-managed volume is used as a managed volume in a CIFS-direct volume, its CIFS front-end service must export the managed volume separately. This is in addition to the export for the direct volume. (The same CIFS service must export both volumes.)
NSCK reports do not identify "marked" multi-protocol directories where you should run a sync files operation. (23891)
Some multi-protocol (NFS and CIFS) directories are "marked" for special processing. These directories contain files and/or subdirectories one of these naming issues:
If a directory is marked with one of these naming issues, the volume performs extra processing whenever a client tries to introduce an entry with the other naming issue. Depending on the outcome of the processing, the new client entry could become NFS-only (inaccessible to CIFS clients). Refer to the CLI Maintenance Guide for details.
Clients can resolve these issues by accessing the volume through its VIP and renaming the directory's entries. However, the directory mark persists after all of its child entries have been correctly renamed; you use the sync files CLI command to remove the mark.
The issue is that there are no reports that identify a directory as "marked" after its entries have been correctly renamed.
Workaround: Use sync files to clear the directory mark immediately after renaming its entries.
Under rare circumstances, an nsck ... rebuild on a shadow volume can make the volume stall in "importing" state. (18135)
If a shadow volume meets all of the following criteria when someone issues an nsck ... rebuild command, the shadow volume stays in "importing" state for a long time (perhaps hours), and is inaccessible to clients:
The root of the problem is that the .acopia_shadow directories contain millions of files, and the nsck ... rebuild must remove those directories at the beginning of its process. Clients cannot access the volume until all the filers are able to delete this directory.
If this occurs, messages appear in the syslog that describe the problem.
The ntp server command allows v1 and v2 of the NTP protocol. (30634)
v1 and v2 are not supported. Refer to the CLI Reference Guide for details.
In ssb degraded mode, slot reload does not recover the system. (30623)
Slot reload does not reset PCI link when link is already down.
Shadow Volume sync performance for ARX4000 is poor compared to ARX6000. (30406)
This issue is being actively worked. The issue is alleviated when pursuing the following Best Practice:
This will give a speedup of up-to 4x during initial treewalk vs. default settings, but ONLY with a pre-seeded target on a CIFS volume.
|F5 Online Knowledge Base:||http://support.f5.com/|
|F5 Acopia Services Support Online:||http://www.acopia.com/services-support.htm|
|F5 Online-Request Form:||https://login.f5.com/resource/login.jsp|
Follow this link for a list of international Support numbers:
For additional information, please visit http://www.f5.com.