version 5.6.42.5

1

The EMC Celerra Network Server is a network-attached storage (NAS) server. It enables clients on a network to store and retrieve files over the network. These release notes contain information about version 5.6.42.5 of Celerra Network Server.

◆ New features and changes ...................................................................... 2◆ Known problems and limitations ........................................................ 18◆ Problem prevention................................................................................ 39◆ Technical notes ........................................................................................ 45◆ Environment and system requirements .............................................. 65◆ Documentation ....................................................................................... 66◆ Installation and upgrades ..................................................................... 80◆ Bug fixes................................................................................................. 123

Version 5.6.42.5 ............................................................................. 125Version 5.6.40.3 ............................................................................. 164Version 5.6.39.5 ............................................................................. 199Version 5.6.38.2 ............................................................................. 240Version 5.6.37.6 ............................................................................. 272

◆ Troubleshooting and getting help ...................................................... 307

Check Powerlink, http://Powerlink.EMC.com for updates to this document. Updates are made when a new version or patch is released, or when new information is discovered.

CelerraNetwork Server

Version 5.6.42.5

Release NotesP/N 300-004-151

Rev A08

December 10, 2008

2 Celerra Network Server Release Notes

New features and changes


Version 5.6.42.5

FTP Securefunctionality

Celerra Network Server V5.6.42.5 supports FTP Secure (FTPS) connections. FTPS connections enable FTP traffic to be sent with SSL (Secure Socket Layer). SSL provides encryption and authentication capabilities. This release simplifies the configuration and management of the FTP server by using the server_ftp command. The modifications done by the server_ftp command take effect when the FTP daemon is restarted. The Data Mover does not need to be rebooted for the changes to take effect.

The Using FTP on EMC Celerra Network Server technical module provides detailed information about the FTPS feature. The Command Reference Manual also contains information about setting FTPS.

Replicator V2 -disable CRC option

was removed

In this version of Celerra Network Server, the option to disable CRC (cyclic redundancy check) error correction for Replication V2 sessions has been removed. This change is intended to ensure data integrity during transfer from one Data Mover to another. Existing interconnects will have CRC automatically enabled on the first boot. The CRC option was removed from the nas_cel –inter connect command. Scripts and procedures that specify the CRC option should be modified accordingly.

Share names andQuotas - multi-byteCLI and XML API v2

support

Multi-byte support provides the ability to input, store, and display multi-byte characters. This enables the users to input and view Celerra object fields in their native language. This feature applies to CIFS share name, CIFS share comment, tree quota path, and the tree quota comment parameters. All characters from the Unicode 3.0 standard are supported.

Prior to this release, this feature was only supported when using the Celerra Manager.

The Using International Character Sets technical module contains detailed information about multi-byte character support. The Celerra XML API Programmer’s Reference also provides additional information.

Celerra Network Server Release Notes 3


SMB2 Protocol Support In version 5.6.42.5, Celerra Network Server supports Microsoft’s new SMB2 protocol. SMB is the underlying protocol used by CIFS to request files, print, and communicate from a server over a network through TCP ports. The SMB2 protocol supports all characters from the Unicode 3.0 standard on Microsoft Windows 2008 servers and Microsoft Windows Vista systems.

The Managing EMC Celerra for the Windows Environment technical module provides detailed information on managing SMB protocol.

SnapSure - writablecheckpoints

You can create a checkpoint of a Celerra FileMover-enabled file system. The FileMover configuration and connections for the checkpoint are inherited from the production file system and cannot be changed. Because a checkpoint is read-only, any attempt to access a stub file contained within the checkpoint causes the file data to be read from the secondary storage by using the passthrough option. The file content is not recalled from the secondary storage in response to the client request.

Celerra FileMover configuration information is stored in a Celerra FileMover file system. Restoring from a checkpoint restores the configuration to the last checkpoint taken. Any subsequent modifications that occurred after the checkpoint was taken are lost.

As of this release, for writable checkpoints, FileMover works as described above, except that the Data Mover always uses the passthrough option to read data from secondary storage. To archive files out of a writable checkpoint, you must first configure FileMover on the production file system, create the baseline read-only checkpoint, and then create the writable checkpoint.

The Using SnapSure on EMC Celerra technical module, available on Powerlink, contains detailed information about writable checkpoints.

VDM one-to-manyand cascade support

The 5.6.42.5 release of Celerra Replicator (V2) supports one-to-many and cascade replication configurations for VDM objects. Prior to this release, only file system and iSCSI LUN objects were supported for these configuration. VDM replication involves the replication of VDM root file system contents of a source VDM to a destination VDM. In VDM one-to-many configurations, a given source VDM can be involved in replicating up to four destination VDMs concurrently.

If a VDM is a destination object for a replication session, it can be a source for up to three other replications. A VDM would be therefore involved in a maximum of four replications, with a maximum of 1 replication as a destination and a maximum of four replications as a source.



A VDM acting as both a source and a destination object for multiple replications results in a cascade replication configuration.

This forms a chain of VDMs, with replications propagating the data along the chain (Source VDM --> Destination VDM 1 --> Destination VDM 2). In a VDM cascade configuration, each replication session functions independently of the other replications. Cascade is supported for two network hops.

VSS Provider for iSCSI In version 5.6.42.5, Celerra VSS Provider for iSCSI is supported on Windows Server 2003 x86-64 (64-bit) and x86 (32-bit) and Windows Server 2008 x86-64 (64-bit) versions.

Celerra VSS Provider for iSCSI runs as a Windows service and provides the interface between the Microsoft Volume Shadow Copy Service (VSS) and the iSCSI snapshot capabilities of the Celerra Network Server. Celerra VSS Provider for iSCSI enables VSS requestor applications, such as VSS-enabled backup applications, to make shadow copies of Celerra iSCSI LUNs.

Prior to this release, Celerra VSS Provider for iSCSI was supported only on Windows Server 2003 (32-bit).

Version 5.6.41.2 Release 5.6.41.2 was only intended for users of the new hardware platforms listed below.

Version 5.6.41.2 introduced support for the following new hardware platforms:

Integrated NS-120The Integrated NS-120 consists of a complete Celerra Network Server and a CLARiiON CX4-120 storage system in a single, compact system. The NS-120 supports a single Control Station and is available with single or dual blades.

Integrated NS-480The Integrated NS-480 consists of a complete Celerra Network Server and a CLARiiON CX4-480 storage system in a single, compact system. The NS-480 supports a single Control Station and is available with dual blades.

Integrated NS-120FCThe Integrated NS-120FC consists of a complete Celerra Network Server and a CLARiiON CX4-120 storage system in a single, compact system.



The NS-120FC supports a single Control Station and is available with single or dual blades. The Fibre Channel (FC) option provides 8 FC ports to share the captive storage array with additional hosts.

Integrated NS-480FCThe Integrated NS-480FC consists of a complete Celerra Network Server and a CLARiiON CX4-480 storage system in a single, compact system. The NS-480FC supports a single Control Station and is available with dual blades. The Fibre Channel (FC) option provides 8 FC ports to share the captive storage array with additional hosts.

Integrated NS-120iSThe Integrated NS-120iS consists of a complete Celerra Network Server and a CLARiiON CX4-120 storage system in a single, compact system. The NS-120is supports a single Control Station and is available with single or dual blades. The iSCSI (iS) option provides 8 iSCSI ports for Multi-Path File Sharing (MPFS) over iSCSI.

Integrated NS-480iSThe Integrated NS-480iS consists of a complete Celerra Network Server and a CLARiiON CX4-480 storage system in a single, compact system. The NS-480iS supports a single Control Station and is available with dual blades. The iSCSI (iS) option provides 12 iSCSI ports for Multi-Path File Sharing (MPFS) over iSCSI.

Version 5.6.40.3 The following new features were supported as of Celerra Network Server version 5.6.40.3.

Oracle Direct NFSparameter

This release introduces the NFS transChecksum parameter. This parameter specifies whether the Data Mover supports Oracle Direct NFS (DNFS) for clients that use Oracle Database 11g with NFSv3. When support is enabled, the Data Mover ensures that each transaction carries a unique ID and avoids the possibility of conflicting IDs that result from the reuse of relinquished ports. By default, DNFS is not supported. Note that when using Secure NFS, DNFS support should be disabled.

Share names andQuotas - multi-byte

support

Multi-byte support in the Celerra Manager interface provides the ability to input, store, and display multi-byte characters. This enables the users to input and view Celerra object fields in their native language. All characters from the Unicode 3.0 standard are supported.

In this release, this feature supports CIFS share names, CIFS share comment, tree quota path, and tree quota comment.



STIG support The Celerra Network Server now supports a nas_stig command. STIG (Security Technical Implementation Guide) defines a configuration and maintenance standard for computer deployments required by the US Department of Defense (DoD) Information Assurance (IA) program. These guidelines are designed to enhance security settings and configuration options before systems are connected to a network. More information about the various STIGs is available at http://iase.disa.mil/stigs/index.html. The Celerra command nas_stig initiates a script that changes Control Station settings according to the Linux STIG. The nas_stig command provides a simple and automated mechanism to apply these changes. These changes can also be undone if there is a requirement to do so at a later date (that is, to troubleshoot an operational issue). The nas_stig command is available in the /nas/tools directory. You must be logged in as root user to execute this command.

Using the Celerra nas_stig Utility Technical Note describes the nas_stig command and provides detailed information about the changes the nas_stig script makes to Control Station settings.


CSA for MPFS Version 5.6.39.5 integrated MPFS installation and configuration steps and modules into the Celerra Startup Assistant (CSA), Powerlink landing page and install guides. This integration will add to the ease of use for MPFS.The CSA with MPFS feature applies to the following platforms:

◆ NS40 for MPFS (iSCSI) - This is the integrated NS40 with additional storage system iSCSI ports. Prior to this release, the "NS40 for MPFS (iSCSI)" platform did not ship with a CSA or an install guide, and did not have a landing page on Powerlink. Celerra Network Server V5.6.39.3 introduces these collaterals for the NS40 for MPFS. In addition to the current functionality, the CSA for this platform now configures the storage system iSCSI ports, authenticate CHAP, and starts the MPFS service.

◆ NS20/NS40 FC - This is the integrated NS20/40 with additional storage system FC ports. The NS20/NS40 FC platforms previously shipped with a CSA and install guide, and had a landing page available on Powerlink. Some of the existing CSA screens have been updated to include MPFS, and new screens have been added to the CSA. As of this release, the CSA for the NS20/NS40 FC also start the MPFS service.



Email notifications The Email User tab on Celerra Manager is used to configure email notifications for serious system events, eliminating the need for configuring multiple notifications with the same email recipients. Email notifications can also be configured through the CLI by using the nas_emailuser command. To configure email notifications, you must be logged in as a user with root or nasadmin privileges. Users without root or nasadmin privileges can only view email notification configuration but cannot modify it. If DNS is not configured on the Control Station, email notifications will not be delivered.The Configuring Celerra Naming Services technical module provides information about configuring DNS.

Large Receive Offload(LRO)

Large Receive Offload (or LRO) is a technique for increasing in-bound network throughput via aggregation of multiple incoming packets. In this technique, multiple incoming packets are aggregated into fewer but large packets. LRO provides the upper network layers, i.e., TCP / IP, the same amount of data but in bigger "chunks".Reducing the number of incoming packets that needs to be processed by TCP / IP lowers the load on CPU by reducing the number of locks, buffer allocations, creation of DLPI headers, etc. This results in increased throughput of the system. However, as a result of coalescing, latency of packet increases as well, which has detrimental effect on performance. Using LRO, the net positive effect on performance is dependent on specific workloads that have long-lived, high-bandwidth, low packet loss connections. In DART, therefore, this feature will be disabled, by default, and needs to be enabled on a case basis to avoid any detrimental effect on performance. LRO is a stateless offload. It can be implemented in hardware as well as software. This feature was implemented in software at the data-link layer and affects all TCP applications.

LDAP-based directoryserver support

This release supports an additional LDAP-based directory server — Active Directory with Microsoft Windows Services for UNIX (SFU) or Identity Management for UNIX (IdMU). Active Directory with SFU or IdMU provides a UNIX environment on Windows and is especially useful for managing user mapping in multiprotocol environments. SFU/IdMU enables you to consolidate user and group information in a single location that can be easily retrieved by the Data Mover. In addition to user mapping, SFU/IdMU provides the Data Mover with a mechanism for looking up user and system information, including usernames, passwords, home directories, groups, hostnames, IP addresses, and netgroup definitions.



The Configuring EMC Celerra Naming Services technical module describes how to configure a Data Mover as an LDAP-based directory service client.

The Configuring EMC Celerra User Mapping technical module describes how to select and configure a user mapping method. There is no Celerra Manager support for this feature.

New Control Station A new Control Station type is being introduced with the NX4 platform which is intended for use on single Control Station NS20 and low-end NS40 systems.

The new Control Station has 2 GB of memory and four network interfaces, and is functionally equivalent to the existing Control Stations. It has dual serial ports, however, the console port is located on the rear of the unit, which is a change from previous Control Stations. This Control Station does not have a floppy drive as part of its configuration, therefore, the CD installation media must be booted from the DVD drive.

NS20 to 40 upgrade The NS20 to NS40 upgrade allows a Data-In-Place upgrade. These upgrades are supported by swapping the back-end storage processors. Upgrades are not allowed on NS20 systems that use SATA in the Vault Disk Array Enclosures (DAE).

NS20 90-drive support With the upgrade to FLARE Release 26 .016, the NS20 platform supports adding up to 90 drives as part of the configuration. Navisphere Service Taskbar Release 28 is also required as part of the ADD-A-DAE procedure.

NX4 platform NX4 is a new low-end Celerra multi-protocol platform. It supports 1 or 2 blades, a single Control Station and 4 to 60 drives. NX4 also supports SAS and SATA drives, and allows mixing of drive types in the same enclosure. The NX4 platform supports the new Email Customer functionality to allow customer maintenance of the hardware.

SCSI PersistentReservation support

This release supports SCSI persistent reservation (PR) commands, which are used by a cluster management subsystem, such as Microsoft Windows Server 2008, to define exclusive or restricted access to iSCSI LUNs for client nodes in a shared disk environment.

A new server parameter, EnableAptpl, enables or disables Activate Persist Through Power Loss (APTPL) support for all targets on a Data Mover. When APTPL support is enabled, the server supports requests from a cluster to maintain persistent reservation information on nonvolatile storage. By default, APTPL support is disabled.



Securecommunications for

the CLARiiON CX4series

The new CX4 series (CX4-120, CX4-240, CX4-480, CX4-960) CLARiiON hardware runs on FLARE R28 software and supports Celerra CNS, CFS, and NS gateway systems. The R28 software has secure communications. This means that when you set up the CLARiiON using Navisphere Manager or Navisphere CLI, you must configure a CLARiiON username with administrative privileges and password. This is performed prior to adding the CLARiiON to the Celerra gateway system. When adding the CLARiiON array to the Celerra system, you will be asked for the username and password.

Version 5.6.38.2 The following new feature was supported as of Celerra Network Server version 5.6.38.2

Symmetrix virtualprovisioning

The Celerra NS/Gateway systems now support the Symmetrix Enginuity 5773 code release. Features of particular interest to Celerra users include the support for flash drives and virtual provisioning in the DMX-4 platform.

Restrictions◆ Celerra virtually-provisioned objects (either iSCSI LUNs or file

systems) are not supported with Symmetrix virtually-provisioned devices.

◆ A single file system should not span virtual and standard Symmetrix volumes.

The Managing Celerra Volumes and File Systems with Automatic Volume Management technical module contains detailed information about virtual provisioning.

Version 5.6.37.6 The following new features were supported as of Celerra Network Server version 5.6.37.6

SSD drive support Celerra® Network Server version 5.6.37.6 supports solid state disk (SSD) drives for the 5773 Enginuity release of DMX-4.

The 5773 Enginuity release for DMX-4 supports SSD drives by defining a new tier 0 storage layer. Celerra identifies the tier 0 layer with SSD and prevents the storage objects built on SSDs from being mixed with storage objects built from other disk technologies like Fibre Channel, SATA, and SAS.

The SSD disk type can be configured in 3+1 RAID 5 or 7+1 RAID 5 configurations. The new system-defined storage pool symm_ssd is not greedy and has the slice flag on by default. The symm_ssd pool allows striping and has a default stripe size of 32 K. SSD drives are not supported with TimeFinder/FS and SRDF.




Celerra EventPublishing Agent

(CEPA)

Celerra Event Publishing Agent (CEPA) is the new, EMC-provided agent that runs on a Windows server. It provides content/quota management applications with notification and optional control of changes made by CIFS clients in file systems on the Celerra Network Server in real time.Using CEPA, clients can register to receive event notification and context from Celerra. CEPA delivers to the consuming application both event notification and associated context (file/directory metadata) in one message.

The Using Celerra Event Publishing Agent technical module contains detailed information about this feature.

Celerra Replicator(V2)

Celerra Network Server version 5.6.36.4 introduces the latest version of replication, Celerra Replicator™ (V2). This version of replication enables you to create and manage replication sessions, each producing a read-only, point-in-time copy of a given source object at a designated destination.

Replicator (V2) sessions, which can be created by using the command line interface (CLI) or Celerra Manager, are characterized by an architecture based on snapshot/checkpoint technology, asynchronous transfer to the destination, and support for file system, Virtual Data Mover (VDM), and iSCSI LUN source object types.

The Using Celerra Replicator (V2) technical module provides more detailed information about establishing file system, VDM, and iSCSI LUN replication in the Celerra environment.

Celerra Replicator(V1) and (V2)

comparison

Table 1 on page 11 lists the major differences between Celerra Replicator (V1) and Celerra Replicator (V2).



Table 1 Differences between Replicator (V1) and Replicator (V2) (Sheet 1 of 2)

Celerra Replicator (V1) Celerra Replicator (V2)

Underlying interconnect support for iSCSI replication only, without explicit interconnect configuration. No interconnect concept for file system and VDM replication.

Required Data Mover-to-Data Mover interconnect (one per Data Mover pair) for all types of replication sessions, including copy sessions. Interconnect must establish a connection between a source Data Mover and a destination Data Mover (same Data Mover, different Data Mover in cabinet, or remote Data Mover).

fs_replicate command for file system and VDM replicationnas_replicate command for iSCSI only

Unified CLI configuration with nas_replicate command now has large set of options and applies to three types of source objects: a file system, VDM, or iSCSI LUN. The output from the -list and -info forms of the command changes to reflect the different source objects.A -delete option replaces the -abort option used previously by iSCSI; -abort is supported only for backward compatibility. In addition, the new -failover option replaces the previous fs_replicate -failover -now and the new -switchover replaces the previous failover -sync

Setup and start operations require multiple CLI setup procedures beyond fs_replicate -start, including multiple fs_copy commands.Celerra GUI configuration involves fewer steps.

Both CLI and Celerra GUI can set up and create a replication session with fewer steps. CLI and GUI offer the same options.In CLI, a single nas_replicate -create sets up the replication environment and starts the replication session.

The fs_copy command is key to setting up the replication environment.

New command, nas_copy, is used for one-time copy of a read-only file system or a checkpoint file system.

Restartable checkpoints are required. No need for restartable checkpoints.



Control Stationmanagement of iSCSI

LUN snapshots

The CLI command server_iscsi supports a new option, -snap, which can be used to create, list, and delete snapshots of iSCSI LUNs, and modify associated application data.

Management of iSCSI LUN snapshots via the Control Station CLI allows for central administration of all iSCSI LUN snapshots and the creation of crash consistent snapshots where application integration is not required.

Required use of replicator SavVol and checkpoint SavVol and monitoring of SavVol size. Could manipulate replicator SavVol size with parameter. A playback service is needed to play back the changes.

Architecture simplifies SavVol use; now, there is only the one checkpoint SavVol. The SavVol will auto-extend; if you want to control the percent full, you can use the fs_ckpt command to specify the size when you create or modify a checkpoint. Checkpoint creation and refresh run indefinitely, without a timeout. To track progress, you can use nas_replicate -info. No playback service applies. As a result, the destination object is updated when data is transferred to the destination site.

Update policy is set by using timeout and high water mark (HWM) values. The HWM values applied to the replication SavVol.

Update policy is set by using the -max_ time_out_of_sync option of the nas_replicate command in the range 1 to 1440 minutes. There is no HWM set; there is no replication SavVol.

User sets bandwidth limit by using a QoS option available with the fs_replicate command. A QoS value of 0 means unlimited bandwidth.QoS was configured separately for each replicated file system.

User can create a bandwidth schedule in Kb/s to control the bandwidth limit for certain time periods by using nas_cel -interconnect command. The limit applies to all sessions associated with a Data Mover interconnect. A bandwidth limit of 0 means no data is sent over the interconnect.

Replication session did not require users to reverse the direction when restarting after a failover operation.

After failover, user must start the session with the -reverse option to change the session direction and then perform a reverse operation to return to the original session configuration.

Replication tasks managed by using fs_replicate and fs_copy.

A new nas_task command used to manage (view, abort, delete) in-progress or completed tasks.

Table 1 Differences between Replicator (V1) and Replicator (V2) (Sheet 2 of 2)

Celerra Replicator (V1) Celerra Replicator (V2)



CLI snapshot management can also be incorporated into scripts to provide application consistency snapshot management if that is desired. The option also allows a snapshot to be promoted for use as a temporary LUN and then demoted. In addition, the content of a production LUN can be restored from a suitable snapshot.

The Celerra Network Server Command Reference Manual and the technical module Configuring iSCSI Targets on Celerra provide information about using the -snap option to create and manage snapshots from the Control Station.

IBM AIX iSCSI softwareinitiator Support

This release supports the IBM AIX iSCSI software initiator version 5.2 or 5.3. The EMC Host Connectivity Guide for IBM AIX (available on Powerlink®) provides additional information about system requirements and how to obtain the most recent ODM fileset.

The technical module Installing Celerra iSCSI Host Components provides instructions for setting up the initiator and configuring LUNs as disk drives on the AIX host.

IPv6 support This release supports the following IPv6 features and provides the ability to:◆ Configure IPv6 addresses on an interface and ensure connectivity◆ Configure name services (local file, Domain Name System (DNS)

and Network Information Service (NIS)) ◆ Export a file system to perform basic NFSv2/v3 operations

IPv6 is configured by means of the command line interface (CLI); there is no Celerra Manager support.

Note: IPv6 is currently available through the RPQ Request for Price Quotation (RPQ) process only.

OpenLDAP support OpenLDAP is an open-source directory server based on the Lightweight Directory Access Protocol (LDAP). OpenLDAP support extends the existing Celerra directory service to the iPlanet/SunOne directory server. Its functionality is similar to that of iPlanet. Managing OpenLDAP client configuration on the Celerra is almost identical to managing the OpenLDAP client configuration on any open system platform (e.g., Linux/UNIX), using the CLI command server_ldap. There is no Celerra Manager support.

LDAP over SSL increases client/server application security by protecting your LDAP traffic to LDAP-based directory servers.



ProvisioningMonitoring

Provisioning Monitoring improves how storage containers such as storage pools and file systems are monitored. Provisioning Monitoring enables a Celerra administrator to better monitor the use of space for file systems and storage pools, particularly for auto-extending file systems and virtually provisioned (sparse) iSCSI LUNs.

In addition, this feature enhances usage notifications by adding support for notifications based on storage pool usage and by better integrating file system and storage pool automatic extension and virtually provisioned (sparse) iSCSI LUNs.

Security features Strong system security features are increasingly necessary to comply with new regulations and ensure greater protection against system attacks. Version 5.6.36.4 introduced a variety of security features that better enable the Celerra to control access and protect data.

To protect system resources against unauthorized access, Celerra supports strict user identification and authentication, customer-defined password policies, secure logon procedures, and role-based administrative access. To protect data, Celerra supports encryption algorithms and public key certificate management solutions.

More information about how to use the new security features can be found in the Celerra Security Configuration Guide and in the Celerra Manager online help.

Enhancements to existing features

Celerra Manager Modifying CIFS Server properties The CIFS server properties NetBIOS alias, NetBIOS name, and the Interface list are modifiable. The NetBIOS alias and NetBIOS name on the CIFS Server properties page now appear in the Celerra Manager as modifiable text boxes.

The Interfaces field appears with modifiable checkboxes that list all the non-default interfaces. User can select/clear interfaces from the available list of interfaces. NetBIOS name, NetBIOS alias, and Interface list can also be modified via the CLI.

../../TechnicalModulesHTML/ConfWindows/index.htm



Celerra Time Services Setting the time zone using the Linux methodThis method helps you update the time zone information on the Data Mover, using simple and decipherable strings, corresponding to the time zones available in the Control Station. It also updates the daylight savings time in the Data Mover for the specified time zone.

Control Station Creating link between Control StationsThe nas_cel -create command is used to create a link between the Control Stations and replaces the nas_rdf -init command.

FileMover FileMover HTTPS support The FileMover HTTPS connection allows encryption of data transfer between the Data Mover and HTTP-based secondary storage and the authentication of HTTP-based secondary storage servers. It also qualifies the additional functionality provided by the Data Mover internal feature for HTTP support to allow transport of commands over SSL, and enable stronger authentication of the policy and archiving application when sending FileMover API calls to the Data Mover.

Protection of stub fileCelerra FileMover has been enhanced so to allow a policy and archiving application to instruct the Celerra to prevent modification and deletion of a stub file that represents an archived file. This is useful when file data is archived to a secondary storage location that provides retention period style protection of the archived data. By using this aspect of FileMover the policy and migration application ensure that the stub file on the Celerra is protected for the same period that the data on the archive storage is protected.

GUI usability Celerra administrators now have the ability to modify the following additional properties of CIFS servers:◆ Interface list — User can add new interfaces to the list or delete the

existing interfaces from the list.◆ NetBIOS aliases◆ NetBIOS name — In case of Windows NT and standalone CIFS

servers.

SnapSure Administrative roles and privilegesSnapSure checkpoint schedule management from the Celerra Control Station CLI via the nas_ckpt_schedule command is now restricted depending on administrative roles and privileges. Administrative roles that have read-only privileges can only list and view checkpoint schedules.



Roles with modify privileges can list, view, change, pause, and resume checkpoint schedules, and roles with full-control privileges can create and delete checkpoint schedules in addition to all other options.

Checkpoint savvol managementThe fs_ckpt command supports the following new option:fs_ckpt -modify {<fs_name> | id=<fs_id>} [%full=<value>] [maxsavsize=<MB>]

This option specifies a limit to which SavVol can automatically extend. The <fs_name> | id=<fs_id> is the file system name or ID on which checkpoints are created, %full is the percentage threshold permitted for SavVol, and maxsavesize is the maximum value in MB for the SavVol size.

Writable checkpointA writable checkpoint is a read-write, logical image of a PFS created from a read-only checkpoint. The read/write file system provides the writable checkpoint view that supports incremental changes on the read-only (baseline) checkpoint. When clients write to a writable checkpoint, SnapSure saves the incremental changes in the SavVol. When reading a writable checkpoint, SnapSure queries the checkpoint's blockmap and the corresponding blocks in the SavVol that saved the incremental changes to provide a complete view of the PFS.

SnapSure supports only one writable checkpoint per read-only (baseline) checkpoint and a maximum of 16 writable checkpoints can exist concurrently per PFS.

SnapSure supports the following checkpoint operations:◆ Restore — Restores a PFS by using a writable checkpoint◆ Mount — Mounts a writable checkpoint as a read-only or

read/write file system◆ Delete — Deletes a writable checkpoint

Writable checkpoints do not support the following features:◆ CDMS◆ File system extension◆ MirrorView/SRDF◆ iSCSI◆ VTLU



User Mapping ntxmapThe EMC Celerra ntxmap feature provides some static rules which describe explicit mapping between Microsoft Windows and UNIX usernames. With ntxmap, you can create a mapping configuration that describes the relationship between users’ Window and UNIX/Linux usernames.

RestrictionThe ntxmap.conf file uses a text file that is sequentially parsed. If the number of ntxmap user mapping entries exceeds 1000, it might add latency to authentication requests.

Usermapper andsecmap

In Celerra Network Server version 5.6.36.4, Usermapper and secmap were reimplemented to use a more efficient database for maintaining mapping information. The new database implementation reduces inode consumption and provides better consistency and recoverability with the support of database transactions.

There is no change in the tools used to manage Usermapper and secmap, all existing tools have been migrated to use the more efficient database implementation.

Report secmap statusThere is now a way to query the status of the secmap. Detailed information about the command syntax can be found in the Managing Secmap section of the Configuring Celerra User Mapping technical module.

XML API EventManagement

Celerra XML API v2 provides a public interface for Celerra events. This interface allows querying Celerra events that have occurred in the past and subscribing to receive event indications as new events occur.

Event queries include filtering in an allowed combination of time interval, severities, facilities or sets of events. XML API v2 also provides a complete catalog of all events in the form of enumerations in W3c XML schema. Responses to event queries or indications will contain message IDs, arguments, and formatted brief or long descriptions of the event in the specified locale.

XML API FileMoverSupport

In Celerra Network Server 5.6.36.4, XML API v2 supports configuring the Celerra FileMover functionality. Pre-5.6 versions supported FileMover operations only through the CLI.


Known problems and limitations


CFS-14 hardware restrictions

The following hardware restrictions apply:

◆ Data Mover model 514 is supported in Celerra Network Server version 5.1 or later.

◆ Data Mover model 514T is supported in Celerra Network Server version 5.3 or later.

Spanning disks

CAUTION!EMC does not recommend spanning a file system across multiple storage systems.

Although the Celerra Network Server can support a heterogeneous backend set, it is not recommended for file systems (including checkpoint file systems) to span more than one storage system.

This is primarily due to the high-availability concern, as one storage system could fail while the other continues, making failover difficult, because the targets might not be consistent in this case. In addition, a spanned file system is subject to any performance and feature set differences between storage systems.

Control LUN requirements enforced

There is strict enforcement of the control LUN size and HLU numbers for fresh installations. Control LUNs 0 and 1 must be at least 11 GB each, and control LUNs 2, 3, 4, and 5 must be at least 2 GB each.

In the past, if you had six control LUNs and they were not assigned the correct HLUs, the installation may have succeeded. Now, an exact match between the LUN capacity and the correct HLU value is strictly enforced. Mismatches will generate a "Control LUN Check Failed" error message during installation. You must correct the control LUNs before installation can complete successfully.

Table 2 Supported Data Movers

Data Mover model Celerra version supported

514 Version 5.1 or later

514T Version 5.3 or later



Automatic File System Extension and virtual provisioning

Note the following restrictions and limitations when using Automatic File System Extension and virtual provisioning:

◆ You can create replicated copies of extendible file systems, but to do so EMC recommends that you use slice volumes (slice=y). In the Replicator V1 initial setup procedure, if Automatic File System Extension occurs while full fs_copy is running without replication service, the extension operation only extends the source file system. In this case, when replication service starts, it fails because the source file system and the destination file system sizes are different. Replication service must be running when the file system is extended. The Using Celerra Replicator technical module contains information about extending the destination file system manually to keep file system sizes identical.

Celerra iSCSI

AIX A known problem with SMIT (System Management Interface Tool) in AIX versions 5.2 and 5.3 prevents it from creating and handling compliant IQN names for iSCSI nodes. As a workaround, manually edit the file /etc/iscsi/targets to enter or modify IQN names. Check the IBM support website for additional information.

Celerra VSS Providerfor iSCSI issues

This section contains information about patches you may need to install to use VSS on your Windows Server 2003 machines.

Apply Microsoft hotfixesTo support VSS and the Celerra VSS Provider for iSCSI, you must apply the following Microsoft hotfixes to your Windows iSCSI hosts:

◆ Hotfix 887827 and 833167 — Volume Shadow Copy Service update.

Microsoft included both of these hotfixes in Windows Server 2003 Service Pack 1.

◆ Hotfix 883646 — Updated Support Storage driver.◆ Hotfix 831112 — Cannot import transportable shadow volumes.

In addition, if you use shadow copies with Microsoft Exchange 2003, you must apply hotfix 838864.

All of these hotfixes are available from Microsoft Product Support Services. To obtain detailed information about these hotfixes, go to the Microsoft Knowledge Base at http://support.microsoft.com and search for the appropriate hotfix number.



Apply patches and hotfixes for Veritas applicationsCelerra VSS Provider for iSCSI has been tested with Veritas Backup Exec and Veritas NetBackup. The following hotfixes and patches should be applied to these applications:

◆ For Veritas Backup Exec — There is a problem with the Veritas Volume Snapshot Provider (VSP) and VSS that causes volumes to be marked as read-only after creating shadow copies. In order to avoid this problem, you must apply the Veritas hotfix 9.1.4691 VSP 1.04 - Advanced Open File Option.

You can find installation instructions for this fix on the Veritas website. To find the fix, go to the Veritas Knowledge Base at http://support.veritas.com and search for document ID 272771.

◆ For Veritas NetBackup — You should apply Maintenance Pack 4 to NetBackup. The latest MP4 patch is available from http://support.veritas.com.

iSCSI configurations Celerra iSCSI configurations in the backend replication environment do not support TimeFinder®/FS, NearCopy, and FarCopy.

Preventing possible Windows NT File System inconsistency If you use iSCSI with SRDF® or MirrorViewTM/S and plan to activate a failover or perform a restore operation, try to use the following procedure for your iSCSI hosts to prevent possible Windows NT File System (NTFS) inconsistency:

1. Stop all Windows applications on the iSCSI hosts (that is, all applications that use the Celerra iSCSI LUNs).

2. From the iSCSI Initiator Properties dialog box, navigate to the target properties and log off from the iSCSI initiator session to clear the session information.

You can now proceed to activate a failover or perform a restore.

If you use iSCSI with one of the backend replication products and need to activate a failover in response to a disaster scenario, attempt to perform these steps, then use the Windows chkdsk utility to check NTFS-level file system consistency once the failover activation is complete. Consult Microsoft for detailed information about recovering data and the chkdsk utility.

Microsoft iSCSIInitiator support

EMC Celerra iSCSI supports the most current version of the Microsoft iSCSI Software Initiator, which is available as a free download from Microsoft’s website (search for iSCSI initiator). This section contains known issues with the Microsoft iSCSI Software Initiator.



Initiator uses only the first network portal of a targetAn iSCSI target on the Celerra Network Server may have multiple network portals configured for it; however, the Microsoft iSCSI initiator GUI uses only the first network portal of a target.

Applies only to Microsoft iSCSI Software Initiator versions before 2.0.

Workaround: Use the Microsoft initiator CLI to access other portals.

Host connectivityissues

In addition to the issues contained in these release notes, you should also check the following guides for other issues related to the Microsoft initiator, QLogic HBAs, and compatibility with the Windows operating system:◆ Host Connectivity Guide for Windows◆ Host Connectivity Guide for Linux

These guides are available from Powerlink® (http://Powerlink.EMC.com).

To locate these guides: 1. Log in to Powerlink.2. Select Home > Support > Technical Documentation and

Advisories > Host Connectivity/HBAs.3. Select Installation/Configuration.4. Locate the host connectivity guides for Windows and Linux.

Replication This release uses the interconnect framework for authentication between Data Movers. Earlier releases used DIC alias records. After an upgrade to version 5.6.36.4, any alias records created in an earlier release continue to exist until a new interconnect is created for a source/destination Data Mover pair.

Some operations, such as validate, should continue to function if the local Data Mover has an interconnect and the remote Data Mover has a DIC alias.

RM or CBMCLI configurationsWhen configured through RM or CBMCLI, a replication session for an iSCSI LUN is limited to one destination on a given Data Mover. An attempt to replicate a LUN to multiple destinations on a single Data Mover will receive an error message, but the message does not correctly identify the problem (Session Stopped).

Any such replication session configured before version 5.6 will continue to function, but cannot be re-created if it is deleted. Replication sessions created through the Control Station (nas_replicate) are not affected by this limitation.



When configuring a replication session through RM or CBMCLI in this release, you must specify a preferred LUN if you want to specify the optional preferred target IQN. If you do not specify a preferred LUN, the preferred target IQN is ignored. This restriction does not apply to sessions created in an earlier release.

Celerra Manager The following notes apply to Celerra Manager.

Browsers In this release, EMC requires the use of one of the following browsers to run Celerra Manager:◆ Internet Explorer 6.0 SP2, 6.2.3 through 7.x.; Internet Explorer 7.1

is recommended. Internet Explorer 8.0 is not supported.◆ Netscape 6.2.3 or later. ◆ Firefox 1.5 or later.

Changes from otheruser interfaces

Any changes made to the network server using another user interface such as the Celerra CLI are not automatically shown in the Celerra Manager. Refresh the browser to see these changes.

Checkpointscheduling

If you plan to use the automated checkpoint (task) scheduling feature in Celerra Network Server version 5.6.36.4 or later, and you have previously created a checkpoint schedule in version 5.1 or version 5.2, the old schedule format is automatically translated into the version 5.6 schedule format during the upgrade. However, if the version 5.1 schedule (which was created with the Celerra Native Manager) has irregular monthly refreshes scheduled (for example, January, March, and August), or if you have created schedules using version 4.2, these schedules do not automatically translate upon upgrade, and you must re-create them using the Checkpoint Schedules tab of the version 5.6.36.4 Celerra Manager interface.

End on dateWhen creating an automated checkpoint schedule using the Celerra Manager > Checkpoints > Schedule page, the online help states that you can change the End On date after the schedule completes, and the schedule begins to run again as scheduled. The ability to change to End On date once the schedule completes is not available in version 5.6.36.4.

Creating an iSCSI LUNwizard

When displaying available file systems for a new iSCSI LUN, the wizard omits file systems of 5 MB or less because they might not provide enough space for a minimum-sized iSCSI LUN.



Although a minimum-sized iSCSI LUN is only 3 MB, the LUN in fact requires about 4 MB because of overhead. Because of its own overhead, a file system of 5 MB might provide less than 4 MB of available space.

If you use the wizard to create a file system for the LUN, specify at least 6 MB for the file system.

The Enable Multiple Access option on the LUN Masking page allows more than one initiator to be given access to the same set of LUNs. This option should be used only within a clustered environment. Under normal circumstances, a LUN should grant access to only one initiator.

Data updateproblems on pages

Because a Celerra Manager operation can involve several internal steps and requires internal communication of statuses over a network, you may not see data on a page updated immediately as you expect.

If you do not see data updated on a page as you expect, try these corrective steps:

1. In the same browser session, select and open another Celerra Manager page, and then select and re-open the page on which you want to see updated data. The updated data should appear as you expect. If not, go to step 2.

2. Wait a short time (15 to 30 seconds), and then click the Celerra Manager Refresh button one time to update the page. This update may take significant time, because it refreshes all data on the page. Avoid clicking Refresh several times, because each click sends another complete update request. If this does not seem to work, go to step 3.

3. Check the Task Status page to see if the operation status is recorded there. The progress of long-running operations and operations on multiple objects (such as deletions of many file systems) is recorded on the Task Status page. If you do not see the operation listed on this page, go to step 4.

4. There may be problems preventing the operation from running. Click the Celerra Network Server name in the navigation pane to open the Celerra Home: Status page, and check the hardware statuses and software alerts on the page for issues that could be preventing the operation from running.



Failover/failback In some cases after a failover in a two-node Windows cluster (node A fails over to node B), a subsequent event that should cause fail back (node B fails over to node A) does not do so as expected. As a result, the quorum disk does not come online and information for the active node is not updated. As a workaround, shut down and then restart the cluster. Microsoft has opened support incident SRX080617601800 for this issue.

Java console When using Celerra Manager, some versions of the Sun Java Runtime Environment (JRE) may report the exception below in the Java console. The exception is benign, and can be safely ignored.java.lang.InternalError: obsolete interface usedat sun.java2d.NullSurfaceData.getRaster(Unknown Source)at sun.java2d.loops.OpaqueCopyAnyToArgb.Blit(Unknown Source)at sun.java2d.loops.GraphicsPrimitive.convert-From(Unknown Source)at sun.java2d.loops.MaskBlit$General.MaskBlit(Unknown Source)at sun.java2d.loops.Blit$GeneralMaskBlit.Blit(Unknown Source)at sun.java2d.pipe.DrawImage.blitSurfaceData(Unknown Source)at sun.java2d.pipe.DrawImage.renderSurfaceData(Unknown Source)at sun.java2d.pipe.DrawImage.copyImage(Unknown Source) ... trace back continues

Length limits for filesystem name and

custom mountpointpath

Celerra Manager limits the maximum length of a file system name and custom mountpoint path to 240 characters. The interface pages will not allow entry of a name or path longer than 240 characters.

Remote replication The recommended Java version for use with Celerra Manager is Java 1.5 version 12 (available at http://java.sun.com/products/archive/). If Java 1.6 version 5 or 6 is used, problems could be encountered on some screens (checkpoints and replication are two examples). The possible symptoms include blank drop down boxes and in some cases the window will stop responding.

SPS warning The Celerra Manager subsystem fails to suppress warnings associated with a single SPS (standby power supply) in some models where a single SPS is a valid configuration. As a result, the Celerra Manager home page reports a persistent warning indicating that SPS B is missing. A single SPS system will operate normally despite this warning.



Storage capacity fornew and extended file

systems

When you create a new file system or extend an existing file system, you enter the desired storage capacity in megabytes. However, the available storage for the selected storage profile is displayed in megabytes (MB), gigabytes (GB), or terabytes (TB).

To convert gigabytes to megabytes, multiply gigabytes by 1024. To convert terabytes to gigabytes, multiply terabytes by 1024. For example, if the selected storage profile has 450 GB available, and you want to create a file system that uses all of the available space, enter 460800 in the storage capacity text box.

CLARiiON upgrades Occasionally, CLARiiON® storage connected to a Celerra Network Server requires a software upgrade. When upgrading CLARiiON software, do not run heavy loads on the Celerra, as operations may be extremely slow or interrupted.Notes◆ CLARiiON array software cannot be upgraded unless the Celerra

Control Station software is upgraded first. Ignoring this rule may make the CLARiiON unmanageable by the Celerra.

◆ Incremental CLARiiON arrays cannot be added to systems running older Celerra software unless they are running a compatible release of CLARiiON software.

◆ A warning will appear when you upgrade the Celerra software if the CLARiiON software needs to be updated. If you receive this warning, finish upgrading the Celerra software and then upgrade the CLARiiON software as soon as possible to avoid compatibility issues.

Consult the E-LabTM Interoperability Navigator at http://Powerlink.EMC.com for all software interdependencies.

Reserved disks EMC reserves LUN numbers 0-15 (from the Data Mover perspective) on the first storage system configured on the Celerra (the Celerra boot storage). If a CLARiiON is misconfigured prior to 5.3 it was possible for the administrator to create volumes/file systems on these disks. Starting with NAS V5.5, you will be prevented from allocating volumes/file systems for user data on these disks. Any attempt to allocate this storage will result in Error 3147: volume <disk-id> resides on a reserved disk. If a reserved disk is already used in an AVM storage pool, no additional storage will be allocated from the volume built on the reserved disk.This restriction affects only new space allocation. Existing file systems will continue to function normally. If you see this error, contact your EMC Customer Support representative so corrective action can be taken.



Storage system statusproperties

On Celerra systems with CLARiiON backend storage where one of the CLARiiON storage processors is down, some of the storage system status properties displayed by the Celerra management interfaces for that storage system may be stale. In particular, the write cache state may display "Enabled" when in fact it would be "Disabled" without both storage processors being active. Other properties such as failed_over and any status may also be inaccurate.

Celerra Replicator When using Celerra Replicator (V1) with version 5.6, the fs_replicate -refresh command does not create a new delta set until the production file system (PFS) is updated. Consequently, policy values for time-out, high water mark (HWM), auto-freeze, auto readonly, and so on that are modified using the fs_replicate -modify or fs_replicate -refresh command remain ineffective until a new delta set is created.

In versions prior to 5.6, the fs_replicate -refresh command creates a new delta set even if no updates are made to the PFS.

Control Station

Non-ASCII characters The Control Station cannot handle non-ASCII characters for shares, NetBIOS names, domain names, and passwords. When creating these names and when issuing commands to the Control Station, be sure to use only alphanumeric ASCII characters.

FLARE operating environment

The backend storage requirements check during upgrade may fail because the version found on an array is 0.0 and Is_Flare_Commited as False, as follows:========================================================13:22 [ 4/70 ] Run Pre Upgrade Health Check 3 minutes...Storage System : Checking if FLARE is supported .................. Fail..Storage System: Check if FLARE is supportedSymptom: ^GBackend Storage Requirements Check Failed:REQUIREMENT: CX700_Software >= 2.06 AND CX700_Software <

2.08ID: APM00034000062 FOUND: 0.0 STATUS: FAILEDREQUIREMENT: Is_Flare_Committed = TrueID: APM00034000062 FOUND: False STATUS: FAILED



Action : The software running on the Storage System has not been qualified with the NAS Storage API included in this NAS package. Finish upgrading the Celerra software and then upgrade the Storage System software as soon as possible to avoid compatibility issues.--------------------------------------------------------Do you wish to continue with this upgrade? [yes or no]:

MPD translation of read-only file systems

For each of the following MPD examples, later read-write mounts of read-only file systems will not automatically translate them. Although not required, these file systems can be manually translated by following the procedure documented in the Using Multi-Protocol Directories with Celerra technical module.◆ Automatic translation of directories from non-MPD (compat) to

MPD (DIR3) format cannot occur, or even be scheduled. Non-MPD directories are left in a readable but obsolete format. Inability to schedule MPD Translation at upgrade time may result in an upgrade error message. This error message is informational only, and does not impact the upgrade.

◆ Root fs, if read-only, will not be translated, but operates properly in compat mode.

◆ If an un-translated checkpoint is ever restored (disaster recovery for instance), it does not automatically get translated to MPD format, but operates properly in compat mode. If the PFS is already translated, more recent checkpoints taken from it are already in the MPD format. New file systems are created in MPD format, so there is no translation required.

NDMPCAUTION!Not all NDMP vendor versions support this version of Celerra Network Server. For the latest NDMP Vendors/Versions/Patches and restrictions supported in this version of Celerra Network Server, refer to the Backup section of the E-Lab Interoperability Navigator.

Backups in ASCIImode

If a Data Mover is in ASCII mode and you back up a file system with asciifilter off, the filename with international characters cannot be recovered if the asciifilter it turned on during the restore.

EMC recommends all Data Movers be configured to use UNICODE rather than ASCII mode. The Managing Celerra for the Windows Environment technical module contains detailed information on how to check and change the Data Mover mode.



Changes whencreating an NDMP

account

As of Celerra Network Server version 5.6.40.3, the NDMP local user account will enable MD5 encrypted password by default (parameter NDMP.md5 = 1). If you did not use MD5 encryption previously, when the NDMP user account was created, backups may fail after upgrading to NAS code 5.6.40.3 or later. If this occurs, you can either change the md5 parameter value to "0", or create the NDMP user account with the md5 password option.

The EMC Celerra Network Server Parameters Guide provides detailed information about the NDMP.md5 parameter.

Legato backupsoftware

When configuring NDMP backups using Networker (formerly Legato) backup software, if the variables DIRECT=y and RECURSIVE=n are specified, the Legato indexed restore does not recover directory permissions or backup date/time.

To restore permissions and backup date/time for directories, proceed as follows:

On the Legato backup host (UNIX/Linux), in .profile or .login, depending on shell, add:NSR_NDMP_RECOVER_DIR=yes export NSR_NDMP_RECOVER_DIR

On the Legato backup host (Windows):

Click My Computer> Properties, and then click the Advanced tab.

Click Environment Variable, and then enter the environment variable, as shown below, and click OK. Then click OK again.



nas_fsck -aclchkcommand

The NDMP backup process must be stopped on the Data Mover before you can use the nas_fsck -aclchk command.

rawfs to uxfsconversion

You cannot convert a file system created as rawfs to a uxfs type unless you first perform a full destructive restore to the rawfs.

Symbolic links NDMP does not follow symbolic links among file systems. Therefore, an NDMP backup does not include a symbolic link's target file system. For more information on symbolic links, refer to the Managing Celerra for a Multi-Protocol Environment technical module.

Using IBM Tivoli andNDMP Backups to Disk

When using IBM Tivoli and NDMP Backups to Disk (NDMPB2D) with Celerra Network Server version 5.6, note the following:◆ When creating new storage, always specify barcode prefix in

uppercase

VTLU (Virtual TapeLibrary Unit)

Celerra VTLU is supported for NDMP backup of Celerra file systems to the Celerra VTLU only. The Celerra VTLU cannot be used as a target for non-Celerra host backup.

NFSCached files If a client mounts exported parent and child paths of the same file

system, it is possible to access the same file from two different mount points. If client side caching is enabled, the client may end up maintaining two different versions of a cached file.

NFSv4 Access Control Lists (ACLs)

If ACLs have been set on a file accessed with Linux over NFSv4, they are displayed correctly as they were set ("getfacl") from a Linux or Solaris machine. If the same file is queried from Windows (via the security tab of the file properties through Explorer), you will receive a security message indicating the permissions are incorrectly ordered and offering to sort the permissions correctly. If you choose to allow Windows Explorer to sort the ACEs, Linux and Solaris may not be able to display the ACL afterwards.

This is merely an error in reporting and does not represent an exposure in terms of how access control to file-system objects is performed and the actual access permissions, based on the original settings of the ACL, are applied normally.

Celerra DataMigration System

Access to online migration file systems while using CDMS is not supported by NFSv4 clients until migration completes.

When NFSv4 is used, it triggers directory migration of subdirectories and requires global lock for the entire Data Mover. Therefore, the Data Mover will be inaccessible during the migration.



Delegations Under rare circumstances, a race condition can occur that can block access to a single file. This issue only occurs in NFSv4 environments with delegation enabled. If the condition occurs, the workaround is to disable delegation in NFSv4.

To learn how to disable delegations, refer to the Configuring NFS on Celerra technical module.

NS20 and NS40 NS20 and NS40 require external IP addresses for the SPs.

During the installation of the Celerra NS20/NS20FC/NS40/NS40FC systems, you are prompted during the Celerra Startup Assistant for the external IP addresses for SP A and SP B. You must assign those values to correctly configure Proxy ARP on the system. If the SPs do not have external IP addresses you will not be able to use the Navisphere® Service Taskbar. For an NS20FC and NS40FC system, you will not be able to use Navisphere without those external IP addresses set.

QuotasCreating and

modifying explicituser/group quotas

When you create a new, explicit user/group quota, or modify an existing user/group quota, the quota will not appear in the quota list if the user/group has no usage on the disk and you set the quotas as follows:

Storage hard limit: 0Storage soft limit: 0File count hard limit: (blank)File count soft limit: (blank)

Note: In the CLI, the limits are entitled "block" (not storage), and inode (not file count), but the same behavior applies.

When using the Celerra Manager to modify a user/group quota under the above conditions, and clicking Apply, a non manageable page appears. Click Back to return to the previous page in the Manager.

Restrictions for listinguser/group/tree

quotas

Due to memory restrictions, the following behavior may result when listing file system quotas on the Celerra Network Server:

◆ The Celerra Manager's File System Quotas > Users and File System Quotas > Group pages may not display in a timely manner when a large number of users and groups is associated with a file system. Lists in excess of 10,000 users and groups may time out due to an out of memory condition.



The Control Station's nas_quotas -tree -list command takes considerable time, or times out, when attempting to produce a list of more than 2,000 quota trees. Similarly, the Celerra Manager's File System Quotas > Tree page may not display in a timely manner when a large number (typically more than 2,000) of quota trees is associated with a file system.

Soft quota limits Soft quotas are always set lower than hard quotas. When users try to store files that exceed the hard quota limit and the deny disk space flag is set to yes, the Data Mover returns an error and does not store the file. The behavior of soft quotas depends on the type of client. For example, Microsoft Windows (CIFS) users receive a pop-up warning message when they exceed a soft quota (if configured). UNIX users never receive a message when they exceed a soft quota (only the hard quota). In both cases, a server_log message is generated. All users can exceed the soft quota for a configurable grace period before they are blocked from saving files.

Replicator V2Enable Replicator V2

on NS series with dualControl Stations

Use this procedure if you have not enabled ReplicatorV2 on the Celerra Home License tab:◆ And you do not have configured replications for file systems

and/or VDMs◆ Or you only have iSCSI replications

Note: Once you enable the Replicator V2 license, you cannot disable this license and enable Replicator V1.

To enable Celerra Replicator V2:1. Close all open Celerra Manager browser sessions.

2. To verify the Replicator status, at the CLI, log in as a Celerra user, su to root, and type:$ /nas/sbin/deploy_replication -status -verbose

3. If the status returned is 'replicator' license is enabled, at the CLI, type:$ nas_license -delete replicator

4. To verify the Replicator status, at the CLI, type: $ /nas/sbin/deploy_replication -status -verbose

5. If the status returned is System is in V1 ready state, at the CLI on the primary Control Station (slot 0), type:$ /nas/sbin/deploy_replication -v2



6. Open your Web browser and log in to Celerra Manager with your administrative username and password.

7. Select Celerras > [Celerra_name]. The "Celerra Home: Status tab" appears.

8. Click the Licenses tab to display the license list for the server. The "Celerra Home: License tab" appears.

9. Select ReplicatorV2 Licensed.

10. Click Apply. The Confirm Apply screen appears.

11. Click OK. The "Celerra Home: License tab" appears, and the Replicator v2 license is selected.

12. To enable Replicator V2 on the secondary Control Station, initiate a failover by typing:$ cs_standby -failoverThe Control Station in slot 1 is now the primary.

13. Log in to the Control Station in slot 1 as the root user and type:$ /nas/sbin/deploy_replication -v2

14. Repeat steps 6 through 11.

15. To return the Control Station in slot 0 to primary, initiate a failover by typing:$ cs_standby -failoverThe Control Station in slot 0 is the primary again.

The Celerra Manager GUI reflects Replicator V2 and the CLI commands are nas_cel (new version for interconnect) and nas_replicate (new version). If the server appears in other instances of Celerra Manager in other browsers, the navigation pane subtree for the server in those browsers will not update until the next status update or an explicit refresh.

Replication List Replicator (V2) List output displays the Data Mover names associated with a replication session. To change the name of a Data Mover in a remote Celerra, you must rename the Data Mover before you create the Data Mover interconnect for that replication session.

If you rename the Data Mover after you create the Data Mover interconnect, the Replication List output will contain the Data Mover name that existed at the time you created the Data Mover interconnect.



To resolve this issue and rename a destination Data Mover that is currently involved in a replication session, fail over the replication session, delete the Data Mover interconnect, and then create a new Data Mover interconnect for the replication session. You can then return the replication session to its previous state.

Replicator V1Replication sessions Before running replication sessions, make sure you have the same

Celerra version on both the source and destination Celerra Network Servers. For remote replication, the version of the destination site must be the same as the version of the source site.

VDM displays status of"temporarily

unloaded"

When replicating CIFS environments, a VDM being configured for replication (as the destination) displays a status of "temporarily unloaded" from the time that it is created/mounted until replication begins. The VDM displays as temporarily unloaded because the rootfs is a rawfs file system type and only after it is converted to uxfs will the VDM state change to "mounted."

SnapSureCheckpoint name While using SnapSure, do not use the extension .ckpt to name a

checkpoint file system. This extension (.ckpt) is used as a virtual directory entry to enable NFS or CIFS client access to online checkpoints in the production file system’s name space, and it can be used for this purpose only.

SnapSure allows the same checkpoint name to be used when creating different checkpoint schedules of the same PFS and of different PFS. No alert or error message is provided. Avoid using the same checkpoint names when creating multiple schedules. Using SnapSure's default checkpoint names avoids this problem.

Checkpointscheduling

EMC recommends that you do not schedule checkpoint creation/refreshes of the same PFS to occur within 15 minutes of each other. This includes checkpoints in the same schedule or between schedules running on the same PFS. Always specify schedule checkpoint times that are more than 15 minutes apart when scheduling checkpoints using the Celerra Manager. (The 15-minute restriction does not apply to creating/refreshing checkpoints using the command line interface).

Data migration Do not perform data migration tasks (using a feature such as the Celerra Data Migration Service) while SnapSure is active. Since migration activity produces significant changes in the data environment, it is best to complete migration tasks before using SnapSure to create and manage checkpoints.



This avoids consuming SnapSure resources to capture information that is unnecessary to checkpoint.

File systemenvironment

All parts of a production file system (PFS), including all parts of its associated checkpoint (SavVol), must reside on the same storage array.

Parameter file Do not insert a new-line character at the end of a nas_param file (/nas/site/ or /nas/sys/). The empty line causes fs_ckpt to return an encodeable.extract error.

Writable checkpointsoperations

Writable checkpoints do not support the following operations and features:◆ Checkpoint refresh ◆ Checkpoint schedule◆ Celerra replication◆ CDMS◆ File-level retention◆ File system extension◆ iSCSI◆ MirrorView/SRDF◆ Replication◆ TimeFinder/RDF◆ VTLU

Replicator Writable checkpoints cannot be created on Replicator V1 and V2 internal checkpoints. These checkpoints are identified by the following naming conventions:

Replicator V1 internal checkpoints:◆ root_restart_ckpt.*◆ root_suspend_ckpt.*◆ .*_repl_restart_[12] (prefix is {src_fs})◆ root_new_ckpt.*◆ root_restore_ckpt.*

Replicator V2 internal checkpoints are identified by the name prefixed with the string "root_rep_ckpt".

SavVol system spaceconsumption

Writable checkpoints share the same SavVol space as read-only checkpoints. When NFS or CIFS clients write to a writable checkpoint, SnapSure saves the changes to SavVol. If SavVol becomes full, space is made available through automatic or manual SavVol extension.



CAUTION!Handle applications that write large amounts of data to a writable checkpoint with caution to prevent automatic extension of SavVol. Once extended, SavVol cannot be shrunk without loss of data.

Checkpoint inactivationIf the system space quota for SavVols exceeds and auto extension fails, SnapSure attempts to keep checkpoints active by using other methods. First, SnapSure uses the remaining SavVol space for the checkpoint.

One example is the remaining 10 percent of the space when a HWM of 90 percent is reached. Next, SnapSure starts inactivating older checkpoints. Inactivating older checkpoints involves unmounting the checkpoint file systems and marking them as deleted. Checkpoint inactivation can be triggered either by a client write operation on the PFS or a writable checkpoint, or by a checkpoint restore operation.

If the inactivation is triggered by a restore operation, checkpoint inactivation depends on whether the checkpoint is older or newer than the restore source checkpoint. For checkpoints that are older than the restore source checkpoint, SnapSure inactivates any existing writable checkpoint of the oldest read-only checkpoint followed by the oldest read-only checkpoint. If further space is required, SnapSure inactivates checkpoints newer than the restore source checkpoint.

For newer checkpoints, SnapSure inactivates writable checkpoints, one at a time, starting with the oldest. Then, SnapSure inactivates the restore backup checkpoint, followed by the read-only checkpoints. Note that the restore operation will complete successfully even when the restore source checkpoint is inactivated.

Note: EMC recommends that you handle applications writing large amounts of data to a writable checkpoint with caution to prevent automatic inactivation of read-only checkpoints.

If SnapSure uses up all possible space it can find to keep a checkpoint active, all PFS checkpoints, including the newest checkpoint and the checkpoint from which the PFS is being restored, if applicable, become inactive and the data is lost.



SRDF/SSSD drives not

supportedSRDF/S does not support solid state disk (SSD) drives. If you attempt to configure an SSD drive with SRDF/S, Celerra health check operations reject the device as an unsupported storage.

Nas_rdf –initcommand fails with

"Unable to setupremote devices"

Problem: During the SRDF discover remote storage devices process, the nas_rdf -init command fails and returns the following error: "Unable to setup remote devices".Workaround: Delete the device group for R2 devices using /nas/symcli/bin/symdg delete <DgName> -force. For example: /nas/symcli/bin/symdg delete 1R2_500_13 –force. Then run nas_rdf –init, to re-create the R2 device group.

Task Scheduler The Task Scheduler runs in a separate thread, but in the same process domain as the Task Manager. The easiest way to determine if the scheduler is running is to check the number of threads in the apl_task_mgr daemon. In NFS version 5.3 and later, the apl_task_mgr daemon should have four threads running. The Linux command ps axfw | less will show the list of processes in a tree form with child processes hanging off of their parent processes.

Other restrictions

CAUTIONS!◆ Do not install Linux non-Celerra applications on the Control

Station. Doing so consumes resources and might adversely affect system operation. Celerra Control Station is a dedicated controller and not an applications platform.

◆ Do not manually edit the nas_db database without consulting EMC Customer Service. Any changes to these file could cause problems with your Celerra installation.

cifssyncwrite The cifssyncwrite option was added to the server_mount command to enhance support for CIFS on the Celerra. This special mount option guarantees that any write to the file server is done synchronously. In Windows CIFS environments, it is important to make sure this option is specified if the Celerra will be used to store certain database files. This is recommended to avoid chances of data loss or file corruption across various failure scenarios, for example, loss of power.



Command line scripts The NAS database stores specific information required for each Data Mover. The Celerra Network Server automatically performs a backup of the entire database every hour and saves it to a file named nasdb_backup.1.tar.gz. These backups start one minute after the hour. EMC recommends that you check your scripts to make sure they are not scheduled to start at the same time as the backups. During backup, the database becomes locked or inaccessible, and some commands that rely on the database might fail.

Performance statistics If you are running release 5.6.38.2 or 5.6.39.5, the command "server_stats", which provides performance statistics, will fail to function correctly if the primary server has at one point failed over to the secondary. During failover the "statmonService" will fail to start on the server taking the place as the original primary. Refer to Primus solution emc198023 on Powerlink for additional information.

Problem with InternetExplorer back button

When clicking between the links too fast or using the back button of IE to go back to the previous screen during the processing, the contents of IFrame are not displayed. The following message is displayed in place of IFrame contents:This application does not support refreshing independently or loading separately the contents of a list. Please try your operation again by refreshing the entire page or by going through <<https://192.24.168.141/action/networkServersDisplay>> or <<https://192.24.168.141>>

Solution: If you click any link on the left navigation pane, you should be able to view the contents properly. You can do one of the following things after you encounter this exception:

Click any of the links as suggested on the IFRAME page. (<<https://192.24.168.141/action/networkServersDisplay>> or <<https://192.24.168.141>>) in this case.

Click the link in the left navigation pane to go to the same page.

Schedules duringupgrades

As part of the upgrade procedure, schedules that run between midnight and 1:00 A.M. may lose those run times. This affects only schedules that run every X hours of the day, (X being from 1 through 12), and not schedules that run at specific hours of the day. This is a known problem and can be corrected by modifying the affected schedules after the upgrade using Celerra Manager.

secmap The server_cifssupport server_x -secmap -import -file command doesn't import anything in the secmap database. The command fails with the error message :



Error 5005 : server_3 : Unexpected MAPPING_RECORD element in Import request.

Import records are read from the specified import file, but are not sent to the Celerra. Only empty record elements are sent.

This operation does not change the secmap database. After the import, the displayed secmap list is empty. This will be fixed in a future release.

server_cpu The server_cpu ALL -halt now command does not complete when using Celerra NSX Network Servers. This is because the NSX needs at least one Data Mover to be up in order to access its NAS partitions through NBS.

server_exportpathname limitation

If the Data Mover has ASCII mode for CIFS, when creating a share using the server_export command, the share name cannot exceed 12 characters.

server_http The server_http command fails if you issue it on a Data Mover while running fsck. Other commands (including FileMover API) may not work until fsck completes.

server_sysconfig If you use the option string of server_sysconfig, the entire string must be enclosed by double quotes. Currently, the command does not return an error message indicating a failure.

UNIX UserManagement

Celerra UNIX User Management snap-in, Celerra UNIX Attributes Migration tool, and Celerra UNIX Users and Groups property page extensions in Active Directory Users and Computers modify the schema by adding attributes and classes to it. These changes to Active Directory are permanent, and uninstalling the snap-in will not remove them.

The Celerra UNIX User tab and the Celerra UNIX Group tab do not appear on the Properties page if you select Action-Find menu to locate a user or group in the Active Directory Users and Computers console.

If you want to assign, remove, or modify UNIX attributes for a user or group in the Active Directory Users and Computers console, scroll through the list of users and groups and select the one you want to view, or use the Celerra UNIX User Management snap-in found in the Celerra Management Console.

Virtual device naming When creating virtual devices, such as Fail-Safe Network (FSN) devices, Ethernet channels, and link aggregations, do not use the following names as the name of the device:


Problem prevention

Problem prevention The EMC Customer Service center has reported a number of calls concerning the following issues. Please take a moment to familiarize yourself with these potential issues.

Administrative activities

Log in as nasadmin As with any UNIX-based operating system, refrain from performing normal administrative activities as Root user. Log in using the administrative user account instead.

Shutting down a DataMover or deleting an

internal interface

Shutting down a Data Mover or deleting an internal interface will prevent you from issuing any server_ commands against that Data Mover. Whenever you issue any command on the Celerra Control Station CLI server, the command is sent to and executed by a Data Mover. If that Data Mover is down or unreachable, the command will fail.

Celerra AntiVirus Agent (CAVA)AntiVirus (AV) threads If a large number of files need to be checked at the same time, the

CAVA file checking process may be slow depending on number of threads configured, number of CAVA servers, and speed of the CAVA servers.

amgr http mac pfkey spstream tcprpc

blksrvi82596

meshforwarder pipe ssl tftp

client icmp nd pmap sslpipe toeframechk

cmfap icmp6 nfs rcp statd upd

dep ip nfsPrimary rfa StreamHead udpnfsmesh

dfe ip6 nwh scsicfg tcp

echo lockd pax smb tcpnfsmesh

escon lpfn pcnfs smpte tcprpc


Problem prevention

If the CAVA servers cannot process file checks quickly enough, then all AntiVirus (AV) threads will become busy and the AV “collector queue” will increase, indicating that file check requests are queueing up. Increasing the number of AV threads (10 by default) will allow more files to be checked in parallel and may improve performance. However, the number of CAVA engines may need to be increased to satisfy a heavy load.

Number of CAVAengines

It is possible to configure your EMC Celerra installation with only one Celerra AntiVirus Agent (CAVA) engine. However, this non-high-availability configuration can make your installation susceptible to data unavailability in the event that the CAVA engine goes offline for any reason. The best method for preventing this type of outage is to increase the number of available CAVA engines.

Additional information for configuring the Celerra AntiVirus Agent can be found in the Using Celerra Anti Virus Agent technical module. This document describes the parameter setting that will specify shutdown actions to take when no servers are available.

Removing AV userfrom Data Mover

password file

If you remove an AV user from the Data Mover password file, CAVA will not work. Depending on the setting you have on CIFS, you could use up all the CIFS threads because they are used for virus checking or it will shut down CIFS altogether.

CIFSDeleting machine

account from activedirectory

Deleting a machine account from active directory will result in loss of access to the CIFS server and its resources. Deleting the computer account of any CIFS server, including a Celerra Data Mover, from the domain of which it is a member will prevent that CIFS server from being able to authenticate both itself and users attempting to connect to it with the domain. This will mean that users will not be able to access data hosted by the CIFS server.

Deleting server out ofthe domain

Deleting a server out of the domain will result in shares associated with the server to be unavailable. The same applies to deleting the machine account.

Naming CIFS shares Do not name your CIFS share "all" or you risk deleting all of your shares when trying to delete it.

NetBIOS nameconflict

Instead of destroying the conflicting NetBIOS, simply rename it using the existing server_cifs <server_x> -rename -netbios <oldname> <newname> command. Changing a NetBIOS name using this command will update the share and local group and enable you to reuse it.


Problem prevention

LGDB and ShareDB information associated with the server are persistent. If the target name of a rename conflicts with LGDB or ShareDB information, re-create the old server and rename it to a name that will not conflict with your naming structure to free the old slot.

Control StationApplications The Control Station’s primary function is to manage the Celerra. The

use of applications that do not come installed on the Control Station is not recommended. The Celerra Control Station is not tested or certified with any of these applications and there could be issues with memory usage or CPU time that may affect normal operation.

Dual Control Stations If you have dual Control Stations on either (CFS/CNS/NSxxx) and they concurrently try to access the /nas file systems, the nasdb may become corrupted and the Data Movers will be unable to communicate with the Control Station.

Control Station zoning The Control Station must only be zoned to a single Symmetrix FA or CLARiiON fibre port. The Control Station Fibre Channel WWN must be present in only one zone.

In an environment with more than one Symmetrix or CLARiiON, the Control Station must be in a zone that contains only one Symmetrix or CLARiiON.

File System

Deleting files fromData Mover or file

system

Files that you delete will be permanently lost unless you have a backup copy. Files can be backed up and restored through the Celerra SnapSure, TimeFinder/FS, Replicator or by using standard tape backup methods.

Deleting file systems File systems that you delete will be permanently lost unless you have a backup copy. Backups can be created via TimeFinder/FS, Replicator or other backup methods.

File system full Insufficient space in a file system will prevent users from writing to that file system. In addition to monitoring file system usage, set an event notification for file system full condition and enable automatic file system extension with a conservative threshold.

Refer to the Configuring Celerra Events and Notifications technical module for more information.


Problem prevention

Mounting file systemto /tmp

Some variants of UNIX or Linux periodically delete some or all of the files under the /tmp directory. If you mount a file system under /tmp you risk having the contents of that file system deleted by the automatic cleanup process.

Splitting BCVs When a production file system (PFS) is mounted in a read/write fashion to a Data Mover and has BCVs established, the command to split (or mirror -off) the BCVs from the PFS volumes must be initiated using the Celerra fs_timefinder command. The fs_timefinder command ensures consistency of the BCV snapshot by managing file system access and Data Mover log operations when the volumes are split. These additional considerations are not available directly from Solution Enabler commands (symmir).

Name ResolutionSunOne/iPlanet When using SunOne/iPlanet, make sure that the defaultServerList

attribute on the LDAP server is set to use IP addresses and not host names. If hostnames are specified and the Celerra is configured to use SunOne/iPlanet for host resolution, a deadlock can occur.

NetworkingChanging an IP

addressChanging an IP address on a Data Mover can result in a naming (DNS/NIS) mismatch and render the IP address inaccessible.

Changing orremoving DNS settings

When you make changes to the DNS server, such as IP addresses, make sure you reflect those changes in the Data Mover. Failure to do so may result in accessibility issues.Removing the DNS server will prevent the CIFS server from communicating with the domain. Any CIFS server, including those configured on a Celerra Data Mover that is a member of a Windows 2000 or later domain, will use DNS to locate the Windows domain controllers that it needs to communicate with to operate. Disabling DNS in such an environment will prevent the CIFS server from locating Windows domain controllers. This will prevent the CIFS server from authenticating users attempting to connect to it. This will mean that users will be unable to access the data hosted by the CIFS server.

Connecting aninternal switch to an

outside network

The internal networks in the Celerra are designed to provide private communication paths between Data Movers and the Control Station. If that network is connected to an external network it is likely that the resulting routing, addressing issues, and/or volume of network traffic will disrupt the communications between the Data Movers and Control Station, which will in turn disrupt the operation of the Celerra.


Problem prevention

Duplicate IP Duplicating an IP address on two Data Mover interfaces will have the same result as duplicating IP addresses on any two machines in a network. The network will either be unable to determine which location it should deliver packets to or block all traffic to both machines on the assumption that one of them is attempting to gain unauthorized access to information by impersonating the other.

FSN devices Create Fail-Safe Network (FSN) devices on multiple network interface cards (NICs) to ensure connectivity in the event of a hardware failure.

Incorrectly addingnetwork route

Incorrectly adding a network route will cause network access to be limited to the same subnet/broadcast domain. The default gateway, or route, address tells any network client, including a Celerra Data Mover or Control Station, where to send IP packets that are outside its local subnet. If the default gateway is misconfigured, the network client will not be able to contact any host that is not within its local subnet. If the Celerra relies on hosts, such as domain controllers, outside its local subnet, it may not be able to offer service.

Parameters

Changing parameters Changing parameters could significantly affect the function of the Celerra Network Server. Take the following precautions before you make changes to Celerra parameters: ◆ Do not change system parameters without first consulting with

EMC Customer Service.◆ Change server parameters one at a time, in small increments,

preferably in a non production environment. Be sure to thoroughly test each change before making additional changes.

◆ Keep a detailed log of which server parameters you changed and the reason for the change. This information will be useful if a problem arises because of the change.

Managingparameters

EMC recommends using the server_param command or the Celerra Manager to manage parameters. If you manually edit the param file, note the following:◆ Parameters are case-sensitive and must be entered exactly as

described in the Celerra Network Server Parameters Guide. A typographical error, the omission of a dot, incorrect capitalization, or a value out of range could result in adverse effects.


Problem prevention

Replicationpasswd file When configuring interconnect security for remote iSCSI Replication

V1 or Replicator V2, an entry for the interconnect passphrase is added to the passwd file for the Data Mover. Do not delete these entries, otherwise authentication between Data Movers will fail.

Replicator V1 For full file system and iSCSI replication and file system copy functionality, the source and destination systems must be using the same major version of Celerra Network Server software, for example 5.5 or 5.6.

StorageMultiple LUN 0s Assigning multiple LUN 0s will result in Data Movers being unable

to boot successfully.

Powering down allSAN Switches

The Celerra does not store any user data itself. All data is stored on the Symmetrix or CLARiiON disk array(s) that the Celerra is attached to. With a Celerra gateway model the Celerra is attached to the disk array(s) it uses via a Fibre Channel SAN. If that SAN is unavailable then the Celerra will not be able to access the disk array(s) it relies on and hence will not be able to offer normal service.

Reassigning volumeswith SDDR or making

fibre changes

Like any host of a Fibre Channel SAN or array, the Celerra will remember the address of the LUNs that it uses in the attached disk arrays. Any change in the identity or location of those LUNs without a corresponding reconfiguration of the Celerra may result in the Celerra being unable to access the LUNs it needs to provide normal service.

Reassigning CelerraLUN with Navi

Same as Reassigning volumes with SDDR or making Fibre changes.

Unbinding/rebindingLUNs

Same as Reassigning volumes with SDDR or making Fibre changes above.

Write disabling R1 andR2

In SRDF configurations, setting R2 disks to "read only" will cause R1 disks to become "read only" as well, and cause access issues.


Technical notes

Technical notes

Configuration guidelines

The values listed in this section represent the highest or lowest values tested by EMC. In some cases, actual capacities may exceed the capacities tested by EMC. Theoretical means in theory, not always practical. Refer to the E-Lab Interoperability Navigator for the most up-to-date information regarding these guidelines.

Table 3 CIFS guidelines

Guideline/specificationMaximum

tested value Comment

CIFS TCP connection 64K (default and theoretical max.),20K (max. tested)

Param tcp.maxStreams sets the maximum number of TCP connections a Data Mover can have. Maximum value is 64K, or 65535. TCP connections (streams) are shared by other components and should be changed in monitored small increments.

Share name length 80 characters (Unicode).

12 chars (ASCII)

Unicode: The maximum length for a share name with Unicode enabled is 80 characters.ASCII: In ASCII mode, the maximum share length is 12 characters.

Number of CIFS shares 10,000 per Data Mover40,000 per Celerra

You may notice a performance impact when managing a large number of shares.

Number of NetBIOS names/compnames per Data Mover

509 (max.) Limited by the number of network interfaces available on the Data Mover. From a local group perspective, the number is limited to 509. NetBIOS and compnames must be associated with at least one unique network interface.

NetBIOS name length 15 NetBIOS names are limited to 15 characters (Microsoft limit) and cannot begin with an@ (at sign) or - (dash) character. The name also cannot include white space, tab characters, or the following symbols: / \ : ; , = * + | [ ] ? < > “. If using compnames, the NetBIOS form of the name is assigned automatically and is derived from the first 15 characters of the <comp_name>.

Comment (ASCII chars) for NetBIOS name for server

256 Limited to 256 ASCII characters. • Restricted Characters: You cannot use double quotation ("), semi-colon (;), accent (`), and comma (,) characters within the body of a comment. Attempting to use these special characters results in an error message. You can only use an exclamation point (!) if it is preceded by a single quotation mark (’).• Default Comments: If you do not explicitly add a comment, the system adds a default comment of the form EMC-SNAS:T<x.x.x.x> where <x.x.x.x> is the version of the NAS software.


Technical notes

Compname length 63 bytes In a Windows 2000 or Windows Server 2003-compatible CIFS server, the CIFS server computer name length can be up to 21 characters when UTF-8 (3 bytes char) is used.

Number of domains 10 tested 512 (theoretical max.)

The maximum number of Windows domains a Data Mover can be a member of. To increase the max default value from 32, change param cifs.lsarpc.maxDomain. The Parameters Guide contains more detailed information about this parameters.

Block size negotiated 64 KB Maximum buffer size that can be negotiated with Microsoft Windows clients. To increase the default value, change param cifs.W95BufSz, cifs.NTBufSz or cifs.W2KBufSz. The Parameters Guide contains more detailed information about these parameters.

Number of simultaneous requests per CIFS session (maxMpxCount)

127 This value is fixed and defines the number of requests a client is able to send to the Data Mover at the same time, (for example, a change notification request). To increase this value, change the maxMpxCount parameter. The Parameters Guide contains more detailed information about this parameters.

Total number files/directories opened per Data Mover

200,000 (NS350/500/700, NSX,

NS40, NS80)

A large number of open files could require high memory usage on the Data Mover and potentially lead to out-of-memory issues.

Number of Home Directories supported

20,000

Number of Windows/UNIX users

20,000 2 billion - 1 max value of UID. If NIS is used, there is a limitation of 64,000 entries in the password config file on particular UNIX machines. If using Usermapper or Secmap, you are limited by the number of inodes available on root file system.

Number of users per TCP connection

16K (default), 64K (max)

To increase the default value, change param cifs.listBlocks (default 64, max 255). The value of this parameter times 256 = max number of users.Note: TID/FID/UID shares this param and cannot be changed individually for each ID. Use caution when increasing this value as it could lead to an out-of-memory condition. Refer to the System Parameters Guide for parameter information

Number of CIFS threads 96 (1GB memory)256 (>1 GB memory)

Number of threads for CIFS users (if there is 1 GB of memory on the Data Mover, the default is 96 threads; however, if there is over 1 GB of memory, the default number of threads is 256).

Table 3 CIFS guidelines (continued)




Technical notes

Number of CIFS connections (share accessed) per TCP connection


To increase the default value, change param cifs.listBlocks (default 64, max 255). The value of this parameter times 256 = max number of connection.Note: TID/FID/UID shares this param and cannot be changed individually for each ID. Refer to the System Parameters Guide for parameter information. Use caution when increasing this value as it could lead to an out-of-memory condition.

Number of files/directories opened per CIFS connection


To increase the default value, change param cifs.listBlocks (default 64, max 255). The value of this parameter times 256 = max number of files/directories opened per CIFS connection.Note: TID/FID/UID shares this param and cannot be changed individually for each ID. Use caution when increasing this value as it could lead to an out-of-memory condition. Be sure to follow the recommendation for total number of files/directories opened per Data Mover. Refer to the System Parameters Guide for parameter information.

Number of VDMs per Data Mover

29 Note: The total number of VDMs, file systems, and checkpoints across a whole cabinet cannot exceed 2048.

number of ntxmap User Mapping entries

1000

Table 3 CIFS guidelines (continued)



Table 4 FileMover



Max connections to secondary storage per primary (Celerra) file system

1024

Number of HTTP threads for servicing FileMover API requests per Data Mover

64 Number of threads available for recalling data from secondary storage is half the number of whichever is the lower of CIFS or NFS threads. 16 (default), can be increased using server_http command, max (tested) is 64.


Technical notes

Table 5 File systems guidelines



Mount point name length 240 bytes (ASCII) The "/" is used when creating the mount point and is equal to one character. If exceeded, Error 4105: Server_x:path_name: invalid path specified is returned.

File system name length 240 bytes (ASCII)19 chars display for list

option

For nas_fs list, the name of a file system will be truncated if it is more than 19 characters. To display the full file system name, use the –info option with a file system ID (nas_fs -i id=<fsid>).

Filename length 255 bytes (NFS), 255 characters (CIFS)

With Unicode enabled in an NFS environment, the number of characters that can be stored depends on the client encoding type such as latin-1. For example: With Unicode enabled, a Japanese UTF-8 character may require three bytes.1 With Unicode enabled in a CIFS environment, the maximum number of characters is 255. For filenames shared between NFS and CIFS, CIFS allows 255 characters. NFS truncates these names when they are more than 255 bytes in UTF-8, and manages the file successfully.

Pathname length 1,024 bytes Note: Make sure the final path length of restored files is less than 1024 bytes. For example, if a file is backed up which originally had path name of 900 bytes, and it is restoring to a path with 400 bytes, the final path length would be 1300 bytes and would not be restored. 1

Directory name length 255 bytes. This is a hard limit and is rejected on creation if over 255 limit.The limit is bytes for UNIX names, Unicode characters for CIFS. 1

Subdirectories (per parent directory)

65,533 This is a hard limit, code will prevent you from creating more than 65,533 directories.

Number of file systems per Celerra

4096 (NSX, NS40 & NS80)

2048 (All other models)

This max number includes VDM and checkpoint file systems.

Number of file systems per Data Mover

2048 Mount operation will fail when the number of file systems reaches 2048 with an error indicating maximum number of file systems reached. This max number includes VDM and checkpoint file systems.

Maximum Disk Volume Size

2TB minus 2 MB


Technical notes

Total storage for a Data Mover (Fibre Channel Only)

NS10 TB =NS350, NS50016 TB =NS70024 TB =NS4032 TB =NS80 32 TB =NSX

CNS8 TB =514/514T DM

These total capacity values represent Fibre Channel disk maximum with no ATA drives. Fibre Channel capacity will change if ATA is used.Note: On a per-Data-Mover basis, the total size of all file systems, and the size of all SavVols used by SnapSure, and the size of all SavVols used by the Celerra Replicator V1 feature, must be less than the total supported capacity. Exceeding these limit can cause out of memory panic.

Refer to the Celerra Capacity Limits tables for more information, including mixed disk type configurations.

File system size See right column for TB information per Data Mover

16 TB (hard limit, enforced) NS700, NSX, NS40, NS8010 TB NS350, 8 TB NS500 and 514/514T Data Mover

When planning a file system, with respect to maximum desired size, be sure to factor in the time required for FSCK, ACL checks, file system build & restore.This guideline applies to both Fibre Channel and ATA drives.

File size 16 TB (4 TB with file size policy of quota)

This hard limit is enforced and cannot be exceeded.

Number of directories supported per file system

Same as number of inodes in file system. Each 8 KB of space = 1 inode.

Number of files per directory

500,000 Exceeding this number will cause performance problems.

1 All other industry-standard caveats, restrictions, policies, and best practices prevail. This includes, but is not limited to, FSCK times (now made faster through multi-threading), backup and restore times, number of objects per file system, snapshots, file system replication, VDM replication, iSCSI LUN replication, performance, availability, extend times, and layout policies. Proper planning and preparation should occur prior to implementing these guidelines

Table 6 iSCSI guidelines



LUN size Minimum: 3 MBMaximum: 2 TB less 1

MB

Because an iSCSI LUN requires overhead, you cannot create a LUN size equal to the total available space; the maximum size for a LUN is slightly less (typically 1 MB less) than the amount of available space in the file system.

Table 5 File systems guidelines (continued)




Technical notes

LUNs per target 256 Each target can have as many as 256 LUNs (numbered 0 through 255). Windows, however, limits each target to 255 LUNs (numbered 0 through 254). To comply with the Windows limitation, Windows-- compatible mode, which is enabled by default on the Data Mover, limits the number of LUNs to 255.If you use a non-Windows iSCSI initiator, you can disable Windows-- compatible mode by modifying the iscsi.WinCompat parameter. Refer to the System Parameters Guide for parameter information.

LUN extension size Minimum: 8 MB Maximum: same as

LUN size

Due to a volume formatting limitation on Microsoft platforms, when extending a LUN, the total LUN size after extension must be greater than 129 MB.

Target alias 255 bytes This name is an alias for the formal iSCSI name. The alias is an alphanumeric string of as many as 255 characters. The alias can include Unicode characters in UTF-8 encoding. Because the alias is the key field in the Celerra Network Server’s iSCSI databases, each alias must be unique on a given Data Mover. 1

iSCSI qualified name (IQN)

223 characters EMC strongly recommends you leave this field empty and let the Celerra Network Server generate a legal iSCSI name.If you type a name, be sure it is globally unique and in either IQN or EUI format. An IQN can have as many as 223 characters. The Celerra Network Server converts all uppercase characters in an IQN or EUI to lowercase characters. Only letters, numbers, "-", ".", and ":" are allowed in iSCSI IQN names.

CHAP secret 255 characters CHAP secrets must be a minimum of 12 characters and a maximum of 255 characters. Microsoft iSCSI initiator supports CHAP secrets of 12 to 16 characters.

Snapshots per LUN 2000 Maximum includes temporary writable snapshots.

Replication session alias 64 characters

Replication application label

128 characters

Replication attached comment text or binary data

4096 bytes

Configured replication sessions per Data Mover

1024

Table 6 iSCSI guidelines (continued)




Technical notes

Concurrent active replication sessions per Data Mover

256 (theoretical max) Number of configured iSCSI replication V1 and V2 replication sessions that can be actively transferring data at one time.

Destinations per source file system

4 Exceeding this number may cause performance implications on the source file system.

iSCSI timeout See comments EMC recommends client iSCSI initiator timeout be longer than failover time.Note: MS iSCSI Initiator has a default timeout of 1 minute.

Table 6 iSCSI guidelines (continued)



Table 7 Naming Services guidelines



Number of DNS domains 3 - WebUIunlimited - CLI

Three DNS servers per Data Mover is the limit if using WebUI. There is no limit when using the CLI (command line interface).

Number of NIS Servers per Data Mover

10 You can configure up to 10 NIS servers in a single NIS domain on a Data Mover.Note: A Data Mover supports only one NIS domain. Each time you configure a NIS domain and specify the servers, it overwrites the previous configuration.

NIS record capacity 1004 bytes A Data Mover can read 1004 bytes of data from a NIS record.

Number of DNS servers per DNS domain

3

Table 8 NFS guidelines



Number of NFS exports 2,048 per Data Mover tested

Unlimited theoretical max.

You may notice a performance impact when managing a large number of exports using Celerra Manager.


Technical notes

Number of concurrent NFS clients

64K with TCP (theoretical)

Unlimited with UDP (theoretical)

Limited by TCP connections.

Number of Windows/UNIX users

4 billion max value of UID. If NIS is used, there is a limitation of 64,000 entries in the password config file on particular UNIX machines. If using Usermapper or Secmap, you are limited by the number of inodes available on root file system.

Netgroup line size 16383 The maximum line length that the Data Mover will accept in the local netgroup file on the Data Mover or the netgroup map in the NIS domain that the Data Mover is bound to.

Number of UNIX groups supported

64K 2 billion max value of any GID. The maximum number of GIDs is 64K, but an individual GID can have an ID in the range of 0- 2147483648

Table 8 NFS guidelines (continued)



Table 9 Networking guidelines



Link aggregation/ether channel

8 ports (ether channel)12 ports (link

aggregation (LACP)

Ether channel: the number of ports used must be a power of 2 (2, 4, or 8). Link aggregation: any number of ports can be used. All ports must be the same speed. Mixing different NIC types (i.e., copper and fibre) is not recommended.

Number of VLANs supported

4094 IEEE standard.

Number of interfaces per Data Mover

45 tested Theoretically 509.

Number of FTP connections

Theoretical value 64K By default the value is (in theory) 0xFFFF, but it is also limited by the number of TCP streams that can be opened. To increase the default value, change param tcp.maxStreams (set to 0x00000800 by default). If you increase it to 64K before you start TCP, you will not be able to increase the number of FTP connections. Refer to the System Parameters Guide for parameter information.


Technical notes

Table 10 Quotas guidelines



Number of Tree Quotas 2047 Per file system

Max size of Tree Quotas 4 TB

Max number of unique groups

64K Per file system

Table 11 Replicator V1 guidelines



Number of Replication sessions per Celerra

64 (NSX/ NS80 ) (other platforms): 32

VDM replication sessions must be included, assuming adequate resources are available.Note: For best performance, do not use timeouts less than 5 minutes or high water mark less than 128 MB on Celerra Replicator. Delta sets should not be created faster than every five minutes in most environments.

Table 12 Replicator V2 guidelines



Number of Replication sessions per Celerra

1365 (NSX/NS80) (other platforms): 682

Max number of Replication sessions per Data Mover

1024 This enforced limit includes all configured file system, VDM, and iSCSI replication sessions as well as copy sessions

Max number of local and remote file system and VDM replication sessions per Data Mover

682

Max number of loopback file system and VDM replication sessions per Data Mover

341

The max number of iSCSI LUN replication sessions per Data Mover is the difference between the max number of replication sessions (1024) minus the number of configured file systems and VDM replication sessions per Data Mover.


Technical notes

On systems with Unicode enabled, a character may require between 1 and 3 bytes, depending on encoding type or character used. For example, a Japanese character typically uses 3 bytes in UTF-8. ASCII characters require 1 byte.

Table 13 SnapSure guidelines



Number of checkpoints per file system

96 Up to 96 checkpoints per file system are supported.

Table 14 Virus Checking guidelines



Virus checker file pending 90% of available VNODES in system

The percentage of total cached open files available in the system that can be pending on Virus Checking. An event is sent to the Control Station when the maximum is reached. To change the default value, modify param viruschk.vnodeMax(default=2000) and/or param viruschk.vnodeHWM(default=0x5a(90%). Refer to the System Parameters Guide for parameter information.


Technical notes

Capacity guidelinesCelerra CapacityLimits - NS Series

Table 15 lists the versions 5.5 and 5.6 Celerra Capacity limits for the NS Series.

Table 15 Celerra NS capacity limits

NS350 NS500 NS600 NS700

DART Version 5.5 5.6 5.5 5.6 5.5 5.5 5.6

FC Limit (TB) per DM/Blade 10 10 10 10 6 16 16

FC+ATA Limit (TB) per DM/Blade 10(FC max10)

161(FC max 10)

16 (FC max 10)

321

(FC max 10) 6

(FC max 6)16 321

Maximum captive array usable capacity (TB) available to Celerra and non- Celerra systems 2

14 (FC)or

27 (ATA)2

14 (FC)or

27 (ATA)2

N/A N/A N/A N/A N/A

B2D w/ATA Limit (TB)per DM/Blade

10 16 32 32 < 4 32 32

Max FS Size (TB)

10 10 8 8 8 16 16

Max # FS per DM/Blade 2048 2048 2048 2048 2048 2048 2048

Max # FS per cabinet 2048 2048 2048 2048 2048 2048 2048

Max configured replication sessions per cabinet for Replication V1

32 32 32 32 32 32 32

Max configured replication sessions per DM/Blade for Replication V2 3

N/A 1024 N/A 1024 N/A N/A 1024

Max # of checkpointsper PFS4

96 96 96 96 96 96 96

1 When using Replicator, to achieve replication storage capacities beyond DART 5.5 limits, Replicator V2 is required.

2 Supported by those Celerra integrated platforms having optional FC option enablement for connecting Windows and UNIX servers. Note that these limits are system capacity, not per-blade capacity.

3 A maximum of 256 concurrently transferring sessions are supported per Data Mover

4 PFS is Production File System.


Technical notes

Table 16Celerra NS capacity limits (continued)

NX-4 NS20 NS40NS80

(XB-60 or XB-65)NSX

(XB-60 or XB-65)

DART Version 5.6 5.5 5.6 5.5 5.6 5.5 5.6 5.5 5.6

FC Limit (TB) per DM/Blade Refer to

the E-Lab interoper-

ability Navigator

on Powerlink

for this info.

16 16 20 241

1 When using Replicator, to achieve storage capacities beyond DART 5.5 limits, Replicator V2 is required.

24 321 24 321

FC+ATA Limit (TB) per DM/Blade

16(FC max16)

481 (FC max 16)

20 641 24 641 24 641

Maximum captive array usable capacity (TB) available to Celerra and non- Celerra systems 2

2 Supported by those Celerra integrated platforms having optional FC option enablement for connecting Windows and UNIX servers. Note that these limits are system capacity, not per-blade capacity.

17 (FC)or

42 (ATA)2

17 (FC)or

42 (ATA)2

68 (FC)or

165 (ATA)2

68 (FC)or

165 (ATA)2

N/A 136 (FC)or

330 (ATA)2

N/A N/A

B2D w/ATA Limit (TB)per DM/Blade

32 48 1,3

3 Snapshots and Replication supported

32 641,5 32 641,5 32 641,5

Max FS Size (TB)

16 16 16 16 16 16 16 16 16

Max # FS per DM/Blade 2048 2048 2048 2048 2048 2048 2048 2048 2048

Max # FS per cabinet 4096 4096 4096 4096 4096 4096 4096 4096 4096

Max configured replication sessions per cabinet for Replication V1

32 32 32 32 32 64 64 64 64

Max configured replication sessions per DM/Blade for Replication V24

4 A maximum of 256 concurrently transferring sessions are supported per Data Mover.

1024 N/A 1024 N/A 1024 N/A 1024 N/A 1024

Max # of checkpointsper PFS5

5 PFS is Production File System.

96 96 96 96 96 96 96 96 96


Technical notes

Control Station zoning requirements

The Control Station must only be zoned to a Single Symmetrix FA or CLARiiON Fibre port. The Control Station Fibre Channel WWN must be present in only one zone. In an environment with more than one Symmetrix or CLARiiON, the Control Station must be in a zone that contains only one Symmetrix or CLARiiON.

iSCSI Replication with Replication Manager

For detailed information about iSCSI disaster recovery procedures when using Replication Manager (RM), refer to the iSCSI Disaster Recovery Solution Implementation Guide, available on Powerlink.

Table 17 Celerra CNS capacity limits

CNS (514 Data Mover)

DART Version 5.5 5.6

FC Limit (TB) per DM/Blade 8 8

FC + ATA Limit (TB) per DM/Blade 16 321

1 To achieve storage capacities beyond DART 5.5 limits, Replicator V2 is required.

B2D w/ ATA Limit (TB) per DM/Blade) 32 32

Max FS Size (TB) 8 8

Max # FS per DM/Blade 2048 2048

Max # FS per Cabinet 2048 2048

Max Replication Sessions per DM/Blade for Replication V1

32 32

Max Replication Sessions per DM/Blade for Replication V22

2 A maximum of 256 concurrently transferring sessions are supported per Data Mover.

NA 1024

Max # Checkpoints per PFS3

3 PFS is Production File System

96 96


Technical notes

Mapping between network ports and software device names

On some NS700 Data Movers, the network ports are labeled 11 through 16 and correspond to software device names cge0 through cge5. These ports support 10 Mb, 100 Mb, or 1 Gb operation and are connected to your LAN.

The network port that is labeled 01 corresponds to the software device fxp0. The fxp0 device is reserved for the internal network and is connected to the switch inside the cabinet. Some NS700 Data Movers are marked with actual port names (cge0, and so on).

Refer to the Configuring and Managing Celerra Networking technical module for more information on networking ports.

Celerra scripting guidelines

The following table lists guidelines to keep in mind when creating Celerra command scripts.

Table 18 Scripting guidelines

Issue Action

Scheduling NAS Database Backups:The Celerra Network Server backs up the NAS database that stores specific configuration information required for each Data Mover every hour, at one minute after the hour. During part of the backup, the database is locked, and some commands that rely on the database might not have access. EMC recommends that command scripts avoid starting at one minute after the hour. Note that scripts with complex commands that run for an extended period may overlap the backup period.The duration of the backup may vary. Use the following Linux command to check the state of the backup process prior to executing scripts: ps -ef | grep nasdb_backup. If a lock condition occurs, wait a few minutes and retry.

Replication:If you are using the Celerra Replicator V1 restartable checkpoint feature to protect from out-of-sync issues, please be aware that the system uses a CRON job to determine if a restartable checkpoint needs to be refreshed at 25 minutes after the hour. This process may generate a checkpoint refresh, depending on the state of the replication session. During a checkpoint refresh, the database is locked. If another operation requires a conflicting lock, it receives an "unable to acquire locks" error. If this occurs, wait a few minutes and retry.In version 5.4, the checkpoint refresh process is sequential and may impact performance. Version 5.5 and later support concurrent checkpoint refreshes, which are less resource-intensive.

Command sequencing Some commands must lock the database in order to execute. If multiple user-entered commands or scripts are active at the same time, some of these commands may lock the database and prevent other commands from executing. To avoid this, you should sequence commands whenever possible.


Technical notes

Scripting examples The RECOVERABLE variable contains the following errors to retry on:◆ Unable to acquire lock◆ Resource temporarily unavailable◆ Unable to connect to host◆ Socket: All ports in use◆ Database resource vanished ◆ Connection timed out◆ NAS_DB locked object is stale

Following is an example of what the RECOVERABLE variable looks like:

RECOVERABLE="unable to acquire lock|Resource temporarily unavailable|unable to connect to host|socket: All ports in use|database resource vanished|Connection timed out|NAS_DB locked object is stale".

The res variable contains the command output.

#!/bin/sh ######################################################### File: nas_cmdrcvr.sh# Created by: NAS Engineering# Date: Thursday, May 25, 2006# Version: 1.0# Notes:# 1) script will retry commands for specified period of time

Sleep statements Some processes within a script can take time to complete. Use proper timing and adequate sleep statements to prevent timing-related issues.

Pipe and grep Piping script outputs through grep is a helpful tool to check the status of the script. Use periodic checks to grep for file or database locked messages, timeouts, resource unavailable warnings, and other failure or success messages, and use this information to check status, pause the script, or halt it.

Return code check All commands return a UNIX-style return code (for example: 0 for success or 1 for failure) or a text-based status code (for example, done) that can be used to help determine if the command completed or if there was an error or a conflict with the NAS database backup, or other commands being run. If a lock condition occurs, wait a few minutes and retry. If you create and run scripts, be sure to incorporate return code checks and verify for proper return codes from individual operations.

Table 18 Scripting guidelines (continued)

Issue Action


Technical notes

#2) script will log messages to file only if there's available disk space########################################################NAS_DB=/nasexport NAS_DBPATH=$PATH:$NAS_DB/bin:$NAS_DB/sbin:/usr/sbin:.export PATHRETRIES=60SLEEPTIME=30LOGDIR="/home/nasadmin"LOGFILE="$0.log"LOGLAST="$0.last"DISKFULL=98RECOVERABLE="Resource temporarily unavailable|\unable to acquire lock|\unable to connect to host|\socket: All ports in use|\database resource vanished|\Connection timed out|\NAS_DB locked object is stale"

## function to log messages to a file#nas_log(){DISKCHK=`df -k $LOGDIR|awk 'NR>1{print $5}'|sed 's/\%//'`# if there's enough free disk space, append to logif [ $DISKCHK -lt $DISKFULL ]; thenTDSTAMP=`date +%Y-%m-%d' '%T`echo $TDSTAMP: $LOGMSG >> $LOGDIR/$LOGFILEfi# regardless of available space, always write last errorecho $TDSTAMP: $LOGMSG > $LOGDIR/$LOGLAST}

## function to execute (and potentially retry) commands#nas_cmd(){# initialize variable(s)retry_count=0# loop until either successful of retry count exceededwhile [ $retry_count -le $RETRIES ]; do# execute command and gather responseRES=`$CMD 2>&1`# check if response means command is recoverableif [ `echo "$RES"|egrep -c "$RECOVERABLE"` -ne 0 ]; then# check retry countif [ $retry_count -ne $RETRIES ]; then# retry count has not been exceeded


Technical notes

LOGMSG="Command ($CMD) failed with ($RES)...retrying in $SLEEPTIME s"nas_logsleep $SLEEPTIMEelse# retry count has been exceededLOGMSG="Command ($CMD) failed with ($RES)...exiting (retry count of $RETRIES exceeded)"nas_logexit 1fielse# command was either successful or failed for an unknown reasonLOGMSG="Command ($CMD) successful with ($RES)"nas_logretry_count=$RETRIESexit 0fi#increment counter for retriesretry_count=`expr $retry_count + 1`done}

## main#CMD="nas_volume -d mtv1"nas_cmd

Using the NASdatabase and query

facility

EMC has partially changed the layout or format of Celerra internal databases. This change can impact the use of awk or grep utilities when used in scripts that assume specific positions of fields in databases.

To enable searching of the NAS database, Celerra has developed a new query subsystem that appears as a hidden option on some of the nas_commands. This query subsystem enables you to specify the information you are interested in, allows you to format the output, and is independent of the database format.

CAUTION!Do not use grep and awk to scan the database files. Database positions may change and substrings may return false matches for database objects.


Technical notes

Following is an example of a query to view unused disks:nas_disk -query:inuse==n -format:'%s\n' -Fields:Id

To filter root disks, refer to the List all non-root disks that are not in use in Table 10.

ExamplesUse the following commands to view the tags (fields) that you can query:nas_disk –query:tagsnas_fs –query:tagsnas_volume –query:tagsnas_slice -query:tags

Table 19 contains a list of examples to help you get started. Note that these commands can be run on the Control Station CLI, so the hardcoded values can be replaced with shell script variables.

Table 19 Task and query examples

Task Example

Query the ID of a named file system nas_fs -query:Name==RLL_fs10 -format:'%s\n' -Fields:Id

Query the ID of a named file system without the new line

nas_fs -query:Name==RLL_fs10 -format:'%s' -Fields:Id

Query the name of a file system ID that corresponds to a particular ID

nas_fs -query:id==20 -format:'%s\n' -Fields:Name

List of all server IDs nas_server -query:* -format:'%s\n' -Fields:Id

List of all server names nas_server -query:* -format:'%s\n' -Fields:Name

List of all the checkpoint file systems nas_fs -query:type==ckpt -fields:name -format:"%s\n"

List type of file system with ID 20 nas_fs -query:id==20 -format:'%s\n' -Fields:Type

List the file systems that are in use nas_fs -query:inuse==y -format:'%s\n' -Fields:Nameornas_fs -query:inuse==y -format:'%s\n' -Fields:Id

Identify file system of which file system ID 28 is a backup

nas_fs -query:id==28 -format:'%s' -Fields:BackupOf

List the name of the server with ID 2 nas_server -query:id==2 -format:'%s\n' -fields:name`"

View which volume file system is built on nas_fs -query:Name==my_fs -format:%d -fields:VolumeID


Technical notes

Query operators Use these operators when building your queries:

View the block count of meta volume nas_volume -query:Name==my_meta3 -format:%d -fields:Blocks

View the block size of meta volume nas_volume -query:Name==JAH_meta3 -format:%d -fields:BlockSize

Find which server IDs use fs123 nas_fs -query:name==fs123 -format:'%s\n' -fields:ServersNumeric

List all non-root disks that are not in use nas_disk -query:inuse==n:IsRoot==False -format:"%s\n" -fields:name

List unused volumes that contain “dc” in the volume name

nas_volume

-query:inuse==n:IsRoot==False:name=dc -for-

mat:"%s\n" -fields:name

List all available disks on a particular storage device (symm_id is a script/env variable)

nas_disk -query:inuse==n:Sym-

mID==$symm_id:IsRoot==False -format:"%s\n"

-fields:name

Table 19 Task and query examples (continued)

Task Example

Table 20 Operator definitions

Operator Definition

= Having the pattern (sub-string match)

== Exact string match

=- Integer Minimum (not less than)

=+ Integer Maximum (not more than)

=* Any

=^ NOT having the pattern

=^= NOT an exact match

=^- NOT Integer Minimum (is less than)

=^+ NOT Integer Maximum (is more than)

=^* NOT Any (None)


Environment and system requirements

Environment and system requirements

Microcode The minimum required microcode levels supported by Celerra Version 5.6.42.5 are listed below. Refer to the E-Lab Interoperability Navigator for the latest microcode information.

Symmetrix◆ 5568.56.22

Symmetrix DMX/DMX2◆ 5670.27.29◆ 5671.31.35

Symmetrix DMX3◆ 5771.68.75

Symmetrix DMX4◆ 5772.55.51

Celerra Gateway systemsCelerra Gateway systems attach to a variety of EMC Symmetrix and CLARiiON storage systems. Refer to the eLab Interoperability Navigator for a complete list of the available options

The supported releases of CLARiiON are FLARE 19 (CX400/CX600 only), FLARE 24, FLARE 26, and FLARE 28. If you are running an older release, you must upgrade the CLARiiON. You will receive a warning during the upgrade if the CLARiiON software is not up to proper revision.

Celerra internal private subnet has changed

The Celerra internal private subnet configuration has changed on all Celerra integrated systems (NS350/NS20/NS40/NS80) that are pre-installed by manufacturing. This change was necessary because the software default values based on the 192.168 subnets were increasingly conflicting with customer’s networks. The new internal private subnet configuration is in the 128.221 subnet. This is an EMC-specific subnet and should never be encountered in a customer network. Refer to ETA emc173555 for more detailed information. This change supersedes all documentation that identifies the internal private IP addresses as being on the 192.168 subnet.

Centera FileArchiver not supported

The Centera® FileArchiver policy engine is not supported when using Celerra Network Server version 5.6.36.6 or later.


Documentation

System requirements for SnapSure and Replicator V1

On a per-Data-Mover basis, the total size of all file systems, and the size of all SavVols used by SnapSure, and the size of all SavVols used by the Celerra Replicator V1 feature, must be less than 16 TB.

To view the size of a file system or a SnapSure SavVol, use the nas_fs -size command. To view the size of a Replicator SavVol, use the fs_replicate -info command.

In-family upgradeswith existing Celerra

Replicator (V2)sessions

No action needs to be taken related to any existing Celerra Replicator (V2) replication sessions when performing an in-family 5.6 upgrade (from a 5.6 version to a newer one). Also, you do not need to upgrade the sites involved in a Celerra Replicator (V2) environment in any particular order.

Documentation

Documentation corrections

In the Using EMC Celerra Event Publishing Agent technical module, P/N 300-006-003 rev A02, the Create the cepp.conf file section, page 9, step 3, the following information:

<cifsserver> = name of CIFS server used by CEPA to access the files in the Celerra Network Server.

should be<cifsserver> = name of CIFS server used by CEPA to access the files in the Celerra Network Server . If you do not include this option, the default CIFS server will be used.

If you include this option, the server specified must be a physical Data Mover, not a Virtual Data Mover, in order for the CEPA service to start on the Data Mover.

Documentation CDNew browser window If you have Autorun enabled and want the Celerra Network Server

Documentation CD to open in a new browser window instead of replacing an open browser window, modify your browser's options for opening new windows or tabs. Refer to your browser's online help for details.

External links To select hyperlinks to external sources on the Documentation CD, right-click and select Open in New Window from the context menu in Internet Explorer or Open Link in New Window from the context menu in Netscape Navigator.


Documentation

Using Celerra features The Celerra Network Server Version 5.6 Documentation CD provides online HTML guides, a set of Adobe Portable Document Format (PDF) technical documents, a copy of the online help systems for the Celerra Network Server’s management applications, and EMC Customer Support contact information.

EMC recommends that you read the document associated with a Celerra feature to familiarize yourself with the concepts, options, and best practices designed to optimize functionality before beginning the installation or setup procedures.

Celerra NetworkServer training

EMC Customer Education Courses are designed to help you learn how EMC storage products work together and integrate within your environment in order to maximize your entire infrastructure investment. EMC Customer Education features online and hands-on training in state-of-the-art labs conveniently located throughout the world. EMC customer training courses are developed and delivered by EMC experts. For course information and registration, refer to the EMC Powerlink website: http://Powerlink.EMC.com.

Celerra Network Server Version 5.6 documentation

This section lists the complete set of user documentation for version 5.6 software. All components of this set, unless otherwise indicated, reside on the Celerra Network Server Version 5.6 Documentation CD.

You can also download the documents from the EMC Powerlink website at http://powerlink.emc.com.

Documentation kitcontents

The EMC Celerra Network Server Version 5.6 user documentation kit contains the following.

Getting started Table 21 lists getting started information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD, online help, or in hard-copy format.

Kit Contents

Item Part Number

Celerra Network Server Version 5.6 Documentation CD 053-002-082

http://powerlink.EMC.com

http://powerlink.EMC.com


Documentation

Celerra management Table 22 lists the Celerra management information described in technical modules and online help on the Celerra Network Server Version 5.6 Documentation CD or in the application’s online help.

Table 21 Getting started

Part number Name Description

300-004-151 Celerra Network Server Release Notes

Contains new announcements, updates, requirements, and precautions related to software installation or upgrades, as well as a list of known issues and bug fixes. You can obtain the latest release notes on EMC Powerlink.

Online Learning about Celerra A feature of the Celerra Network Server Version 5.6 Documentation user interface, the Learning about Celerra topic introduces you to the EMC Celerra Network Server models and their components. Includes a high-level conceptual overview of Celerra Network Server networking, volumes and file systems, file access protocols, iSCSI support, and business continuance features, such as high availability and data protection.

Online Getting started with Celerra topic on the Celerra Network Server Version 5.6 Documentation CD and in Celerra Manager online help

A feature of the CD user interface and Celerra Manager online help. Getting started with Celerra provides a high-level outline of essential Celerra management tasks that includes links and references to Celerra Manager documentation, Celerra command line interface documentation, and Celerra Wizards that help you perform the tasks.

300-004-136 Configuring Celerra Describes the steps required to configure a Celerra Network Server using the Set Up Celerra wizard in Celerra Manager.

300-004-161 Celerra Network Server System Operations

Explains how to power up and power down the Celerra cabinet, perform an emergency shutdown, halt and reboot the Control Station, Data Movers and blades, manage the Control Station using CLI commands, and use preventive troubleshooting to maintain system operation.

Table 22 Celerra management


300-004-140 Installing Celerra Management Applications

Provides a brief description of, and explains how to access or install, the Celerra Network Server’s management and monitoring applications and interfaces, including Celerra Monitor and Celerra management snap-ins and tools.

Online Help Celerra Manager Provides guidance as you use the Celerra Web Manager to perform Celerra administrative tasks from a remote computer with a supported browser and network connection to the Celerra Control Station. Helps you manage and configure Celerra file systems, Data Movers, networks, hosts, volumes, and storage systems.


Documentation

Online Help Celerra Monitor Provides guidance as you use the Celerra Monitor, a Java-based client/server application software package, to monitor Symmetrix performance and any Data Movers mounted on the Celerra Network Server. Celerra Monitor allows you to observe system operation, performance, configuration, and statistics; check Symmetrix error logs; and control access and polling of monitored data.

Online Help Celerra Data Mover Security Settings

Explains how to manage audit policy by selecting which Data Mover security events are logged into the Windows Security log, and how to manage user rights by selecting which users and groups can log in to or execute tasks on a Data Mover.

Online Help Celerra Home Directory Management

Explains how to enable home directories on Celerra.

Online Help Celerra UNIX Property Page Extensions in Active Directory Users and Computers

Explains how to modify the Celerra UNIX user and group attributes using property page extensions in Active Directory Users and computers.

Online Help Celerra UNIX Attributes Migration Tool

Explains how to migrate UNIX attributes from the NIS server or UNIX password and group files, or remove user and group attributes from the Active Directory.

Online Help Celerra UNIX User Management Explains how to view and modify Celerra UNIX user and group attributes.

Online Help Celerra AntiVirus Management Explains how to modify CAVA virus-checking configuration parameters on a Celerra Data Mover from a Windows 2000 or NT server.

300-004-167 Configuring Celerra Events and Notifications

Describes how to configure the Celerra Network Server to record and display various system events, such as errors, alerts, and commands to facilitate system administration and troubleshooting.

300-004-186 Configuring Standbys on Celerra Describes Control Station and Data Mover failover, and how to implement a standby Control Station or standby Data Mover(s) on the Celerra Network Server.

300-004-145 Using Quotas on Celerra Explains how to configure and manage disk usage limits (quotas) for users, groups, and trees within a file system, and users and groups within a tree, on the Celerra Network Server.

300-004-189 Celerra Security Configuration Guide

Describes the security features available on the Celerra Network Server to secure the Celerra's infrastructure, control access, and protect data. These features include settings in both the Control Station and Data Movers that can be used to tighten the operation of the Celerra system, strict user identification and authentication, customer-defined password policies, secure logon procedures, role-based administrative access, encryption algorithms, and public key certificate management.

Table 22 Celerra management (continued)



Documentation

Networking Table 23 lists networking information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

Volumes and filesystems

Table 24 lists the file system information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

300-004-175 Controlling Access to Celerra System Objects

Explains the Celerra Network Server's access control lists (ACLs) and describes how to implement them to control the level of user access to system objects.

300-004-579 Managing Celerra Statistics Provides an overview of the performance statistics facility used to monitor system statistics for the EMC Celerra Network Server.

Table 22 Celerra management (continued)


Table 23 Networking


300-004-166 Configuring and Managing Celerra Networking

Describes how to configure and manage a Celerra network, including network devices and interfaces, address resolution, routing, and virtual local area networks (VLANs). It also provides reference information on Packet Reflect mode and configuring Linux service on Celerra.

300-004-165 Configuring and Managing Celerra Network High Availability

Explains how to configure a Celerra Network Server to enable high-availability network communications links. High-availability network configurations allow a Data Mover to respond to a failed link in a virtual device (an Ethernet channel or link aggregation), or the failure of all links in virtual device, by automatically rerouting traffic to the available links (virtual device failover) or to the available component devices (Fail-Safe Networking). Topics also include how to manage and troubleshoot a high-availability network environment.

300-004-168 Configuring Celerra Time Services

Explains how to use Time Services, including the Network Time Protocol (NTP) and Simple Network Time Protocol (SNTP) functions, to synchronize the Data Movers with a network time source.

300-004-169 Using FTP on Celerra Network Server

Describes the File Transfer Protocol (FTP) function, and how to configure FTP on Celerra Network Server to enable the transfer of files from one machine to another.

300-004-170 Using TFTP on Celerra Network Server

Describes the Trivial File Transfer Protocol (TFTP) function, and how to configure TFTP on Celerra Network Server to enable the transfer of files from one machine to another.


Documentation

Table 24 Volumes and file systems


300-004-141 Using International Character Sets with Celerra

Describes when and how to enable a variety of international character sets (also known as I18N) on the Celerra Network Server to serve local language requirements. Topics include: • How to configure the Celerra Network Server to store one or more

international character sets • How to enable international character support for a newly installed Celerra

Network Server• How to upgrade an existing system to support international characters,

including file and directory name conversion

300-004-164 Managing Celerra Volumes and File Systems Manually

Provides an overview of Celerra volumes and file systems. Contains planning consideration information and explains the procedures to manually create, configure, and manage Celerra volumes and file systems (including nested mount file systems). Provides instructions for performing basic Celerra file system administration tasks.

300-004-148 Managing Celerra Volumes and File Systems with Automatic Volume Management

Explains how to configure disk volumes and create and extend file systems with Automatic Volume Management (AVM). Provides a comprehensive explanation of how AVM works with Automatic File System Extension. Also provides planning consideration information and procedures for managing AVM storage pools and other related file system administration tasks.

300-004-145 Using Quotas on Celerra Explains how to configure and manage disk usage limits (quotas) for users, groups, and trees within a file system, and users and groups within a tree, on the Celerra Network Server.

300-004-175 Controlling Access to Celerra System Objects

Explains the Celerra Network Server's access control lists (ACLs) and describes how to implement them to control the level of user access to system objects.

300-004-134 Celerra File Extension Filtering Describes how Windows users can control the types of files that are saved to a CIFS share or a Data Mover.

300-004-162 Using Celerra FileMover Explains how to enable FileMover on the Celerra Network Server to automatically migrate infrequently used files to slower, less-expensive storage devices. Discusses planning considerations, file migration and retrieval processes, and procedures for performing administration tasks on FileMover-enabled file systems.

300-004-163 Using File-Level Retention on Celerra

Provides an overview of File-Level Retention (FLR) storage technology. It explains how to manage files in an FLR file system to create a permanent, unalterable set of files and directories.


Documentation

Copying file systems Table 25 lists the Celerra backup protection information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

300-004-160 Using TimeFinder/FS, NearCopy, and FarCopy with Celerra*

Explains how to use TimeFinder/FS to create a snapshot (point-in-time copy) of a production file system based on local volumes, or how to use TimeFinder/FS NearCopy or FarCopy to create a snapshot of a file system that resides on a remote Celerra Network Server. You can export this read-only copy from a Data Mover on the remote Celerra Network Server and use it for backup and application testing. TimeFinder/FS NearCopy can work with SRDF/Synchronous (SRDF/S); TimeFinder/FS FarCopy can work with SRDF adaptive copy write pending mode.

300-004-184 Using Celerra Replicator (V1) Describes how to create and manage a point-in-time, read-only, copy of a production (source) file system on a Celerra Network Server that can be used by a Data Mover in the same cabinet or a Data Mover at a remote site. This copy can be used for backup, data recovery, and application testing without interrupting the processing of client transactions to and from the source file system.

300-004-188 Using Celerra Replicator (V2) Describes how to perform a one-time copy of a source file system that is• mounted read-only• checkpoint mounted read-only• writable checkpoint mounted read-only.This copy can be used for backup, data recovery, and application testing without interrupting the processing of client transactions to and from the source file system.

300-004-155 Using Celerra Replicator for iSCSI (V1)

Describes how to set up a Celerra Network Server for asynchronous replication of iSCSI LUNs, and covers iSCSI replication management functions performed on the Celerra Network Server.

Table 24 Volumes and file systems (continued)


Table 25 Copying file systems


300-004-160 Using TimeFinder/FS, NearCopy, and FarCopy with Celerra*

Explains how to use TimeFinder/FS to create a snapshot (point-in-time copy) of a production file system based on local volumes, or how to use TimeFinder/FS NearCopy or FarCopy to create a snapshot of a file system that resides on a remote Celerra Network Server. You can export this read-only copy from a Data Mover on the remote Celerra Network Server and use it for backup and application testing. TimeFinder/FS NearCopy can work with SRDF/Synchronous (SRDF/S); TimeFinder/FS FarCopy can work with SRDF adaptive copy write pending mode.


Documentation

User management Table 26 lists user management information described in technical modules and online help on the Celerra Network Server Version 5.6 Documentation CD or in the application’s online help.

300-004-184 Using Celerra Replicator (V1) Describes how to create and manage a point-in-time, read-only, copy of a production (source) file system on a Celerra Network Server that can be used by a Data Mover in the same cabinet or a Data Mover at a remote site. This copy can be used for backup, data recovery, and application testing without interrupting the processing of client transactions to and from the source file system.



300-004-188 Using Celerra Replicator (V2) Describes how to perform a one-time copy of a source file system that is• mounted read-only• checkpoint mounted read-only• writable checkpoint mounted read-only.This copy can be used for backup, data recovery, and application testing without interrupting the processing of client transactions to and from the source file system.

300-004-179 Using SnapSure on Celerra Explains how to create and manage read-only, point-in-time, logical images (checkpoints) of a production file system, and restore a PFS from a checkpoint.

*Celerra TimeFinder/FS and Celerra TimeFinder/FS NearCopy and FarCopy are supported only on a Celerra Network Server attached to a Symmetrix system.

Table 25 Copying file systems


Table 26 User management


Online Help Celerra UNIX Attributes Migration Tool

Explains how to migrate UNIX attributes from the NIS server or UNIX password and group files, or remove user and group attributes from the Active Directory.

Online Help Celerra UNIX User Management Explains how to view and modify Celerra UNIX user and group attributes.

300-004-172 Configuring Celerra Naming Services

Explains how to use Naming Services, including local files, the Network Information Service (NIS), Domain Name System (DNS), and the Sun Java System Directory Server (iPlanet). OpenLDAP provides secure LDSP over SSL communication.


Documentation

CIFS configuration Table 27 lists the Microsoft Windows-based product configuration and support information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

300-004-174 Configuring Celerra User Mapping

Describes how to configure and manage Windows user ID mapping using methods and tools such as Usermapper, MMC snap-ins, local files, and NIS. Recommends the technique to use based on whether you have a Windows-only or multiprotocol environment.

300-004-178 Using NTMigrate with Celerra Describes how to configure and manage NTMigrate, a tool that adds Windows users to an existing UNIX UID/GID database.

300-006-209 Using ntxmap for Celerra CIFS User Mapping

Describes how to configure and manage CIFS user mapping in an environment where the users are identified differently on Windows and UNIX platforms.

Table 26 User management (continued)


Table 27 CIFS configuration


300-004-137 Configuring CIFS on Celerra Describes how to configure CIFS support on the Celerra Network Server for Windows environments using the Celerra Manager and the command line interface (CLI).

300-004-135 Managing Celerra for a Multiprotocol Environment

Describes how to manage CIFS support on the Celerra Network Server for mixed Windows and UNIX environments.Note: To configure NFS services for file systems, refer to the Configuring NFS on Celerra technical module.

300-004-138 Managing Celerra for the Windows Environment

Describes how to manage CIFS support on the Celerra Network Server for Windows environments.

300-004-174 Configuring Celerra User Mapping

Describes how to configure and manage Windows user ID mapping using methods and tools such as Usermapper, MMC snap-ins, local files, and NIS. Recommends the technique to use based on whether you have a Windows-only or multiprotocol environment.

300-004-178 Using NTMigrate with Celerra Describes how to configure and manage NTMigrate, a tool that adds Windows users to an existing UNIX UID/GID database.

300-004-143 Using EMC Utilities for the CIFS Environment

This technical module describes how to use EMC Windows utilities, which you install on a Windows server from the Celerra Network Server Applications and Tools CD, to facilitate the migration of files and directories from a Windows server to the Celerra Network Server.

300-004-134 Celerra File Extension Filtering Describes how Windows users can control the types of files that are saved to a CIFS share or a Data Mover.


Documentation

NFS configuration Table 28 lists NFS information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

High availability Table 29 lists the high availability information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

300-004-185 Configuring Virtual Data Movers for Celerra

Describes how to configure and manage a Virtual Data Mover (VDM), which enables you to administratively separate CIFS servers and their associated resources, like file systems, into virtual containers, or VDMs. VDMs allow administrative separation between groups of CIFS servers, enable replication of CIFS environments, and allow the movement of CIFS servers from Data Mover to Data Mover.

300-004-183 Replicating Celerra CIFS Environments

Describes the planning and configuration tasks required to use the Celerra functionality to deliver asynchronous data recovery for your CIFS environments by leveraging Celerra Replicator.

300-004-139 Using Windows Administrative Tools with Celerra

Contains instructions for using Microsoft Windows tools to perform the following administrative tasks on a Celerra Network Server configured with the CIFS protocol:• Create shares and groups on the Data Mover• Configure access policy for shares and groups on the Data Mover• Monitor Data Mover attributes at the session, share, and file level• Audit the CIFS users and objects

300-006-209 Using ntxmap for Celerra CIFS User Mapping

Describes how to configure and manage CIFS user mapping in an environment where the users are identified differently on Windows and UNIX platforms.

Table 27 CIFS configuration (continued)


Table 28 NFS configuration


300-004-152 Configuring NFS on Celerra Provides an overview of the Celerra NFS environment and explains how to mount, export, and manage access to NFS file systems on the Celerra Network Server. Note: The Managing Celerra for a Multiprotocol Environment technical module provides information about configuring the Celerra Network Server to support both NFS and CIFS; the Configuring CIFS on Celerra technical module provides information about CIFS only.


Documentation

Replication This table list the Celerra replication information described in technical modules in the Celerra Network Server V5.6 documentation CD.

Table 29 High availability


300-004-165 Configuring and Managing Celerra Network High Availability

Explains how to configure a Celerra Network Server to enable high-availability network communications links. High-availability network configurations allow a Data Mover to respond to a failed link in a virtual device (an Ethernet channel or link aggregation), or the failure of all links in virtual device, by automatically rerouting traffic to the available links (virtual device failover) or to the available component devices (Fail-Safe Networking). Topics also include how to manage and troubleshoot a high-availability network environment.

300-004-158 Using SRDF/S with Celerra for Disaster Recovery*

Explains how to configure source and destination Celerra Network Servers for Symmetrix Remote Data Facility/Synchronous (SRDF/S), a limited-distance data replication facility that provides complete disaster recovery.

300-004-157 Using SRDF/A with Celerra* Explains how to configure source and destination Celerra Network Servers for Symmetrix Remote Data Facility/Asynchronous (SRDF/A), an extended-distance asynchronous data replication facility that provides continuous availability of file systems.

300-004-186 Configuring Standbys on Celerra Describes Control Station and Data Mover failover, and how to implement a standby Control Station or standby Data Mover(s) on the Celerra Network Server.

* Celerra SRDF is supported only on a Celerra Network Server attached to a Symmetrix system.

Table 30 Replication


300-004-184 Using Celerra Replicator (V1)

Describes how to create and manage a point-in-time, read-only, copy of a production (source) file system on a Celerra Network Server that can be used by a Data Mover in the same cabinet or a Data Mover at a remote site. This copy can be used for backup, data recovery, and application testing without interrupting the processing of client transactions to and from the source file system.

300-004-188 Using Celerra Replicator (V2) Describes how to create and manage replication sessions, each producing a read-only, point-in-time copy of a given file system, VDM, or iSCSI LUN at a designated destination.

300-004-183 Replicating Celerra CIFS Environments

Describes the planning and configuration tasks required to use the Celerra functionality to deliver asynchronous data recovery for your CIFS environments by leveraging Celerra Replicator.


Documentation

Backup Table 31 lists the Celerra backup protection information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

Celerra iSCSI Table 32 lists the Celerra iSCSI information described in technical modules and online help on the Celerra Network Server Version 5.6 Documentation CD or in the application’s online help.



Table 30 Replication (continued)


Table 31 Backup


300-004-180 Configuring NDMP Backups to Disk on Celerra

Describes how to create, configure, and manage a virtual tape library unit (VTLU) on the Celerra Network Server. VTLUs allow you back up data to disk-based storage by means of the Network Data Management Protocol (NDMP).

300-004-181 Configuring NDMP Backups on Celerra

Describes how to configure and manage the Celerra Network Server for Network Data Management Protocol (NDMP) backups, and how to configure your backup software for the Celerra Network Server.

300-004-182 Using the Celerra server_archive Utility

Describes how to use the server_archive utility to perform manual, local backup and restore operations, and to copy directories. As a backup option, server_archive is for local, low-capacity backups.

Table 32 Celerra iSCSI


300-004-154 Installing Celerra iSCSI Host Components

Describes how to install Celerra VSS Provider for iSCSI on iSCSI hosts. The technical module also covers installing the Microsoft iSCSI Software Initiator and configuring Celerra iSCSI LUNs as disk devices in Windows, Linux and IBM AIX.

300-004-153 Configuring iSCSI Targets on Celerra

Describes how to configure iSCSI on the Celerra Network Server and covers the creation of targets, LUNs, LUN masks, and snapshots of iSCSI LUNs.


This technical module describes how to set up a Celerra Network Server for asynchronous replication of iSCSI LUNs, and covers iSCSI replication management functions performed on the Celerra Network Server.


Documentation

Celerra Event Enabler Table 33 lists information for antivirus protection described in technical modules and online help on the Celerra Network Server Version 5.6 Documentation CD or in the application’s online help.

Celerra MPFS(formerly HighRoad)

Table 34 lists the Celerra MPFS (MultiPath File System) information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

Data migration Table 35 lists the Celerra data migration information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

Table 33 Antivirus


Online Help CAVA Calculator Describes using the CAVA Calculator sizing tool to estimate the number of CAVAs required to provide a user-defined level of performance in a CAVA pool, based upon user information.

Online Help Celerra AntiVirus Management Explains how to modify CAVA virus-checking configuration parameters on a Celerra Data Mover from a Windows 2000 or NT server.

300-004-144 Using Celerra AntiVirus Agent Describes how to install and configure Celerra AntiVirus Agent (CAVA), which provides an antivirus solution to clients using an EMC Celerra Network Server in a Microsoft Windows Server 2003, Windows 2000, or Windows NT domain. CAVA uses third-party antivirus software to identify and eliminate known viruses before they infect files on the storage system.

300-006-002 Using Celerra Event Enabler Describes how to install and configure the Celerra Event Enabler Framework software which provides a working environment for the CAVA and CEPA facilities.

300-006-003 Using Celerra Event Publishing Agent

Describes how to create a CEPA configuration file, issue CEPA commands using the CLI, assign the EMC Event Notification Bypass privilege to suppress 3rd party application events.

Table 34 Celerra MPFS


300-004-187 Using MPFS on Celerra This technical module explains how to provide EMC HighRoad MPFS clients with access to Celerra file systems using the Celerra HighRoad feature. Originating with metadata requests through the Celerra Network Server to the storage device, MPFS delivers requested data over direct Fibre Channel or iSCSI connections to the client.


Documentation

Troubleshooting Table 36 lists troubleshooting information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

Reference Table 37 lists reference information described in technical modules on the Celerra Network Server Version 5.6 Documentation CD.

Table 35 Data migration


300-004-171 Celerra CDMS Version 2.0 for NFS and CIFS

Describes the planning considerations and procedures required to migrate data to the Celerra Network Server in a CIFS or NFS environment.

300-004-143 Using EMC Utilities for the CIFS Environment

Describes how to use EMC Windows utilities, which you install on the a Windows server from the Celerra Network Server Version 5.6 Applications and Tools CD-ROM, to facilitate the migration of files and directories from a Windows server to the Celerra Network Server. The utilities are: • LGDUP.exe — duplicates the local groups database• EMCOPY.exe — duplicates a directory tree from one server to another

with Windows security intact• EMCACL.exe — modifies all the security properties of existing files and

directories on a Celerra Network Server• SHAREDUP.exe — duplicates the shares from one Windows server to

another with the Windows security intact

Table 36 Troubleshooting


300-004-149 Celerra Problem Resolution Roadmap

Provides a generic description of how to troubleshoot Celerra system problems and guidelines to use when contacting EMC Customer Support.

300-004-167 Configuring Celerra Events and Notifications

Describes how to configure the Celerra Network Server to record and display various system events, such as errors, alerts, and commands to facilitate system administration and troubleshooting.


Installation and upgrades

Installation and upgradesEMC or its partners performs the installation of Celerra Network Server hardware and software for all platforms except for NS20 and NS40. Please contact your EMC Support Representative for detailed information about the installation procedure.

Celerra installation process

This section lists some facts you should know about the Celerra

Network Server and the installation and configuration process before proceeding further.

How to prepare forCelerra installation

To prepare for Celerra installation and configuration, complete the following tasks:

1. Perform the pre-site installation tasks as required by EMC to complete the installation and connectivity of the Celerra Network Server. Tasks include preparing electrical facilities, wiring the network, adding a telephone line, checking environmental conditions and related requirements, as stated in the Professional Services Statement of Work (PSSOW).

Table 37 Reference


300-004-156 Celerra Network Server Command Reference Manual

Details the command set, including the command function, storage application, syntax, usage prerequisites, and precautions. This manual is also available in hard copy in the product kit, and its command reference information is available online as man pages that you can access from the CLI.

300-004-150 Celerra Network Server Parameters Guide

Lists and describes specific system attributes that are set up by default in the Celerra Network Server software. Describes how to establish, modify, or override some of these attributes for the entire Celerra Network Server or for a specific Data Mover.

300-004-146 Celerra Glossary This is a glossary of network-attached storage (NAS) terminology used in reference to the Celerra Network Server. Terms that are specific to a particular product are designated as such in the definition.

300-004-149 Celerra Problem Resolution Roadmap

Provides a generic description of how to troubleshoot Celerra system problems and guidelines to use when contacting EMC Customer Service.



For a copy of the PS-SOW document, contact your Professional Services Account Team. For examples of Celerra network topologies, refer to the Configuring and Managing Celerra Networking technical module on the Celerra Network Server Version 5.6 Documentation CD.

2. Configure your environment for UNIX clients, Microsoft Windows clients, or a combination of Windows and UNIX clients, as applicable.

3. Complete network assessment to ensure proper performance and protocol configurations. (Optional EMC services can be ordered to assist with this process.)

Celerra NetworkServer installation and

configuration

EMC Customer Service installs the Celerra Network Server hardware—a process that includes the physical setup, cabling, power application, and diagnostic testing of the Celerra Network Server.Next, EMC Professional Services or an EMC partner might configure and integrate the Celerra Network Server. For example, for a Celerra Network Server with a Symmetrix system, this process typically includes the following tasks:◆ Coordinating the activities to enable installation, cabling, and

connectivity to system cabinets◆ Loading and configuring the Celerra Network Server software ◆ Creating, mounting, and exporting file systems◆ Configuring network protocols◆ Integrating with a supported, existing user authentication

environment◆ Configuring standby Data Mover(s), if applicable◆ Configuring and demonstrating system management and

administration toolsEMC Professional Services can perform additional Celerra Network Server configuration tasks, such as host provisioning (with Celerra MPFS), backup protection, and network connectivity, depending on the individual EMC customer agreement defined in the PSSOW. These services are part of the EMC Network-Attached Storage Design and Implementation service offering, which is designed to provide continuous technical expertise as you manage your organization’s growing network storage needs. For more information about this service offering, contact your EMC Customer Support representative.

After EMC installs, configures, and tests the Celerra Network Server, it is fully operational and ready to support networked storage operations.



Celerra upgradesNAS and FLARE

upgradesEMC recommends that NAS upgrades be performed before FLARE is upgraded on any attached CLARiiON. The reason for this is to maintain compatibility between the storage API (NAVI) on the Control Station and the FLARE on the CLARiiON. The API is built in as part of the NAS management software and is used to gather data about the backend such as statistics, health, and configuration.

If the FLARE is upgraded first, the API may encounter issues while communicating with the new FLARE. Upgrading the NAS first allows the API to have limited backward compatibility with the FLARE code. After any NAS upgrade, nas_checkup should be run to validate compatibility with the running FLARE code.

Replicator V2upgrade

Upgrading to CNS version 5.6 does not automatically upgrade the Replicator to V2. That is, Replicator V1 will continue to be in use until an ad hoc upgrade to Replication V2 is performed. Upgrading to Celerra Replicator Version 2, which is part of this release, should be managed independently of the CNS V5.6 software upgrade.

Contact your EMC Customer Support representative for CNS V5.6 and Replicator V2 upgrade planning.

Reboot required atupgrade

CNS software The CNS software is comprised of two installation components, a Linux package and a CNS software package. The software currently running on the Celerra and the CNS upgrade software versions determine the number of Control Station and Data Mover reboots required and whether Data Mover reboots can be scheduled to a later time after the upgrade is complete.

The DART software runs on the Data Movers and is part of the CNS software package. The new version of DART is loaded and run on the Data Movers only after a Data Mover boot.

Control Station rebootingWhen upgrading CNS software, if either of the first two digits of the new version number change (for example, 5.5.x to 5.6.x), the Control Station requires rebooting.

At the beginning of upgrade, the system information section lists whether or not the Control Station reboot is mandatory. Note that this initial output is long and may scroll off the screen. You will be prompted whether to continue the upgrade after all the upgrade information is displayed.



If you enter no, the upgrade stops, and you are returned to the command prompt.

========System Information========Install Manager Version: 5.6.36-4Install Manager Command: /mnt/cdrom/EMC/nas/install_mgrStarts at: Wed Mar 5 13:22:25 2008From version: 5.4.17-5To: 5.6.36-4Dual Control Stations: noSlot: slot_0Data mover slot(s): 2 , 3Cabinet family: NSCabinet type: NS-IPDARTControl Station reboot: multiple (mandatory)Data Mover reboot: 1 time (mandatory)Total number of attempts: 0============================= ..< other information is posted here> .Do you wish to continue with the upgrade now [ yes or no ]? > yes

Data Mover rebootingThe Data Movers require a reboot in order to run the new version of DART. When upgrading CNS software, if either of the first two digits of the new version number change (i.e., 5.5.x to 5.6.x).

The system information screen is the same as the information in the Control Station rebooting screen.

Limited scheduling of the Data Mover reboot exists. An estimated time for when the Data Mover reboot will happen is shown at the beginning of upgrade:

==============Estimated Time for Services ===============Current Time: 13:22Estimated Time when NAS service will be stopped: 13:28Estimated Time when Data Movers will be reset: 14:28Estimated Time when NAS service will be restarted: 14:39Estimated Time when upgrade will be complete: 14:50==================================================

The Upgrade Data Movers task prompts before it reboots the Standby Data Movers. It then provides a menu to reboot the Primary Data Movers similar to the following:==================================================



14:47 [ 46/70 ] Upgrade Data Movers 7 minutesStart at: Wed Mar 5 14:47:38 2008All servers must now be rebooted.Ready to reboot the Standby Data Mover (3). Press the ENTER key to begin...The following server(s) need to be rebooted to run the new release:2 ) server_2Enter slot number(s) or ALL to select server(s) for reboot: ==================================================

When upgrading DART, if both of the first two digits of the new version of software remain the same (for example, 5.5.x to 5.5.y), you may delay the rebooting of the Data Movers.

The system information screen is the same as the information in the Control Station rebooting example except for the following: Data Mover reboot: 1 time (advisory)

The Upgrade Data Movers task asks if you wish to reboot the Data Movers. If you enter yes, you will be prompted to press ENTER to reboot the standby data movers, then prompted to reboot the primary Data Movers. If you enter no, the Data Movers continue running the current (pre-upgrade) version of CNS software until they are rebooted.=================================================

15:18 [ 44/67 ] Upgrade Data Movers 7 minutesAll servers need to be rebooted to run the new release.

Do you wish to reboot them now? [yes or no]: Ready to reboot the Standby Data Mover (3). Press the ENTER key to begin...

The following server(s) need to be rebooted to run the new release:

2 ) server_2

Enter slot number(s) or ALL to select server(s) for reboot: Waiting for ping response from server_2 ... :up (0 secs)=================================================

Upgrades fromprevious versions

Due to technical limitations, upgrades from versions prior to 5.4 require a two-step upgrade process. You must upgrade to version 5.4 first, and then upgrade to version 5.6.36.4.

Upgraderequirements

Existing read/write-able file system must have 128K minimum free space prior to upgrading to CNS V5.6.



Licensing terms

Apache License,Version 2.0

Copyright © 1999-2006, Apache Software Foundation.Licensed under the Apache License, Version 2.0.

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

Definitions"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship.

For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.



"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

Grant of Copyright LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted.

If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.



Redistribution You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

◆ You must give any other recipients of the Work or Derivative Works a copy of this License; and

◆ You must cause any modified files to carry prominent notices stating that You changed the files; and

◆ You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

◆ If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third- party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License.

◆ You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

◆ You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

Submission of ContributionsUnless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.



Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

TrademarksThis License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

Disclaimer of WarrantyUnless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON- INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

Limitation of LiabilityIn no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

Accepting Warranty or Additional LiabilityWhile redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License.

However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.



Ganymed Copyright (c) 2005 - 2006 Swiss Federal Institute of Technology (ETH Zurich), Department of Computer Science (http://www.inf.ethz.ch), Christian Plattner. All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:a.) Redistributions of source code must retain the above copyright

notice, this list of conditions and the following disclaimer.b.) Redistributions in binary form must reproduce the above copy-

right notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

c.) Neither the name of ETH Zurich nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The Java implementations of the AES, Blowfish and 3DES ciphers have been taken (and slightly modified) from the cryptography package released by "The Legion Of The Bouncy Castle".Their license states the following: Copyright (c) 2000 - 2004 The Legion Of The Bouncy Castle (http://www.bouncycastle.org)Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:



The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON- INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

GNU GENERAL PUBLICLICENSE

Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USAEveryone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

PreambleThe licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.

This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.



For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps:(1) copyright the software, and (2) offer you this license which gives you legal permission to copy,

distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION0. This License applies to any program or other work which

contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License.

The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.



1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a. You must cause the modified files to carry prominent notices

stating that you changed the files and the date of any change. b. You must cause any work that you distribute or publish, that in

whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c. If the modified program normally reads commands inter- actively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.



Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this license.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-

readable source code, which must be distributed under theterms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine- readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.



4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.



It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.



NO WARRANTY11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE,

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHAN- TABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.

SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONSHow to Apply These Terms to Your New ProgramsIf you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found on-line to give the program's name and an idea of what it does.

Copyright (C) yyyy name of author



This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 f the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than ̀ show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary.

Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.

signature of Ty Coon, 1 April 1989

Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License.



GNU LESSER GENERALPUBLIC LICENSE

Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc.51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]

PreambleThe licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.



We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.

When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.

We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries.



In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.

In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.



Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.

1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: "a) The modified work must itself be a software library. "b) You must cause the files modified to carry prominent notices

stating that you changed the files and the date of any change. "c) You must cause the whole of the work to be licensed at no

charge to all third parties under the terms of this License. "d) If a facility in the modified Library refers to a function or a

table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)



These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.

Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.



If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License.



If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:

a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.)

b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.

c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.

d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.

"e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.



It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system.

Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: "a) Accompany the combined library with a copy of the same

work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.

"b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions.



You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.

11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.



13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number.

If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE,

THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL



DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONSHow to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License).

To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

one line to give the library's name and an idea of what it does.

Copyright (C) year name of author

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names:



Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker.

signature of Ty Coon, 1 April 1990Ty Coon, President of Vice

Microsoft In addition to the license terms for the software (as defined below) in your agreement with EMC or its authorized reseller, the following additional terms and conditions shall be applicable to any Microsoft Corporation software or intellectual property that may be included with the software. You hereby agree to these following terms and conditions by installing and/or using the software.

You may install and use this EMC software (hereinafter the "software") only as a file server as specified in the documentation accompanying this software, and only to interoperate or communicate with native Microsoft Windows 2000 Professional or Windows XP Home or Professional client operating systems (or any successors thereto). You may not install or use this software on a personal computer under any circumstances. For purposes of the foregoing, a “personal computer” means any computer configured so that its primary purpose is for use by one person at a time and that uses a video display and keyboard.

You hereby agree that Microsoft Corporation, as a licensor of intellectual property that may be included in the software, is intended to be a third party beneficiary (only to the extent permitted by applicable law) of this agreement with rights to enforce any terms herein that affect any included Microsoft intellectual property that may be included in the software or other Microsoft interest related to this agreement.

You may install the software on a server that (a) contains not more than four (4) processors, which processor has a maximum of thirty-two (32) bits and less than or equal to four (4) gigabytes of RAM, and (b) is not capable of having memory added, changed or removed without the requirement that the server on which it is running be rebooted (“hot swapping capabilities”).

You may not use the software in conjunction with any software that supports hot swapping capabilities or clustering capabilities, where “clustering capabilities” means the ability to allow a group of servers (e.g. host servers) to function as a single high-availability platform for running applications using application failover between server nodes in the group.



You may not use the software in conjunction with any software that supports hot swapping capabilities, where “hot swapping capabilities” means the ability to have memory added, changed or removed without the requirement that the server on which it is running be rebooted.

Hardware or software that reduces the number of electronic devices directly accessing or using services provided by the software does not reduce the number of devices deemed to be concurrently accessing or using services provided by the software. The number of electronic devices accessing or using the software is equal to the number of devices that access or use, either directly or through a multiplexing device, services provided by the software.

As used here, a “multi-plexing device” means any hardware or software that provides or obtains access, directly or indirectly, to services provided by the software to or on behalf of multiple other devices concurrently through a reduced number of connections to such software.

You must acquire and dedicate a separate Windows CAL for each electronic device that is accessing or using, either directly or through or from a multiplexing device, services provided by the software. A “Windows CAL” means a Windows device Client Access License (“CAL”), or a Windows user CAL, in either case for a Microsoft Windows Server 2003 (Standard Edition, Enterprise Edition, or Data- center Edition) server operating system product (“Windows Server 2003”); or (b) a Microsoft core CAL that provides an individual person or electronic device with rights to access and use Windows Server 2003, in either of (a) or (b) above that you have acquired for use with one or more such Microsoft Windows Server 2003 operating system products or electronic device and that is used on a per user or per device basis.

In the event the software is being used as part of an evaluation, you may install and use the software solely for the purposes of testing and evaluation for time period specified below. Your right to use the software shall be effective from the date you first install any portion of the software on any server for a period of one hundred twenty (120) days.

You may install the Software on a server that (a) contains only one (1) processor, which processor has a maximum of thirty-two (32) bits and five hundred twelve (512) megabytes of RAM, (b) contains a network interface card with a maximum throughput of one hundred (100) megabits per second, and (c) is not capable of having memory added, changed or removed without the requirement that the server on which it is running be rebooted (hot swapping capabilities).



You may not use the software in conjunction with any software that supports hot swapping capabilities or clustering capabilities, where “clustering capabilities” means the ability to allow a group of servers to function as a single high-availability platform for running applications using application failover between Server nodes in the group.

Open Source InitiativeOSI - Common

Development andDistribution License

(CDDL)

Copyright © 1994-2007 by Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, California, 94303, U.S.A. All Rights Reserved.

1. Definitions1.1. Contributor means each individual or entity that creates or

contributes to the creation of Modifications.

1.2. Contributor Version means the combination of the Original Software, prior Modifications used by a Contributor (if any), and the Modifications made by that particular Contributor.

1.3. Covered Software means(a) the Original Software, or (b) Modifications, or (c) the combination of files containing Original Software with files

containing Modifications, in each case including portions thereof.

1.4. Executable means the Covered Software in any form other than Source Code.

1.5. Initial Developer means the individual or entity that first makes Original Software available under this License.

1.6. Larger Work means a work which combines Covered Software or portions thereof with code not governed by the terms of this License.

1.7. License means this document.

1.8. Licensable means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein.

1.9. Modifications means the Source Code and Executable form of any of the following:a. Any file that results from an addition to, deletion from or

modification of the contents of a file containing Original Software or previous Modifications;

b. Any new file that contains any part of the Original Software or previous Modification; or

c. Any new file that is contributed or otherwise made available under the terms of this License.



1.10. Original Software means the Source Code and Executable form of computer software code that is originally released under this License.

1.11. Patent Claims means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor.

1.12. Source Code means (a) the common form of computer software code in which

modifications are made and (b) associated documentation included in or with such code.

1.13. You (or Your) means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License. For legal entities, You includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, control means

(a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or

(b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. License Grants2.1. The Initial Developer Grant.

Conditioned upon Your compliance with Section 3.1 below and subject to third party intellectual property claims, the Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license:(a) under intellectual property rights (other than patent or

trademark) Licensable by Initial Developer, to use, reproduce, modify, display, perform, sublicense and distribute the Original Software (or portions thereof), with or without Modifications, and/or as part of a Larger Work; and

(b) under Patent Claims infringed by the making, using or selling of Original Software, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Software (or portions thereof).

(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial Developer first distributes or otherwise makes the Original Software available to a third party under the terms of this License.



(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code that You delete from the Original Software, or (2) for infringements caused by: (i) the modification of the Original Software, or (ii) the combination of the Original Software with other software or devices.

2.2. Contributor GrantConditioned upon Your compliance with Section 3.1 below and subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:(a) under intellectual property rights (other than patent or

trademark) Licensable by Contributor to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof), either on an unmodified basis, with other Modifications, as Covered Software and/or as part of a Larger Work; and

(b) under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or portions thereof); and (2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination).

(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first distributes or otherwise makes the Modifications available to a third party.

(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any code that Contributor has deleted from the Contributor Version; (2) for infringements caused by: (i) third party modifications of Contributor Version, or (ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or (3) under Patent Claims infringed by Covered Software in the absence of Modifications made by that Contributor.

3. Distribution Obligations3.1. Availability of Source Code.

Any Covered Software that You distribute or otherwise make available in Executable form must also be made available in Source Code form and that Source Code form must be distributed only under the terms of this License.



You must include a copy of this License with every copy of the Source Code form of the Covered Software You distribute or otherwise make available. You must inform recipients of any such Covered Software in Executable form as to how they can obtain such Covered Software in Source Code form in a reasonable manner on or through a medium customarily used for software exchange.

3.2. ModificationsThe Modifications that You create or to which You contribute are governed by the terms of this License. You represent that You believe Your Modifications are Your original creation(s) and/or You have sufficient rights to grant the rights conveyed by this License.

3.3. Required Notices.You must include a notice in each of Your Modifications that identifies You as the Contributor of the Modification. You may not remove or alter any copyright, patent or trademark notices contained within the Covered Software, or any notices of licensing or any descriptive text giving attribution to any Contributor or the Initial Developer.

3.4. Application of Additional Terms.You may not offer or impose any terms on any Covered Software in Source Code form that alters or restricts the applicable version of this License or the recipients rights hereunder. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Software. However, you may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear that any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer an every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer.

3.5. Distribution of Executable Versions.You may distribute the Executable form of the Covered Software under the terms of this License or under the terms of a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable form does not attempt to limit or alter the recipients rights in the Source Code form from the rights set forth in this License.



If You distribute the Covered Software in Executable form under a different license, You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or Contributor.You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer.

3.6. Larger WorksYou may create a Larger Work by combining Covered Software with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Software.

4. Versions of the License4.1. New Versions.

Sun Microsystems, Inc. is the initial license steward and may publish revised and/or new versions of this License from time to time. Each version will be given a distinguishing version number. Except as provided in Section 4.3, no one other than the license steward has the right to modify this License.

4.2. Effect of New Versions.You may always continue to use, distribute or otherwise make the Covered Software available under the terms of the version of the License under which You originally received the Covered Software.

If the Initial Developer includes a notice in the Original Software prohibiting it from being distributed or otherwise made available under any subsequent version of the License, You must distribute and make the Covered Software available under the terms of the version of the License under which You originally received the Covered Software. Otherwise, You may also choose to use, distribute or otherwise make the Covered Software available under the terms of any subsequent version of the License published by the license steward.

4.3. Modified Versions.When You are an Initial Developer and You want to create a new license for Your Original Software, You may create and use a modified version of this License if You:(a) rename the license and remove any references to the name of

the license steward (except to note that the license differs from this License); and



(b) otherwise make it clear that the license contains terms which differ from this License.

5. DISCLAIMER OF WARRANTYCOVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN AS IS BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PAR- TICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

6. TERMINATION

6.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive.

6.2. If You assert a patent infringement claim (excluding declaratory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You assert such claim is referred to as Participant) alleging that the Participant Software (meaning the Contributor Version where the Partici- pant is a Contributor or the Original Software where the Participant is the Initial Developer) directly or indirectly infrin- ges any patent, then any and all rights granted directly or indirectly to You by such Participant, the Initial Developer (if the Initial Developer is not the Participant) and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively and automatically at the expiration of such 60 day notice period, unless if within such 60 day period You withdraw Your claim with respect to the Participant Software against such Participant either unilaterally or pursuant to a written agreement with Participant.



6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user licenses that have been validly granted by You or any distributor hereunder prior to termination (excluding licenses granted to You by any distributor) shall survive termination.

7. LIMITATION OF LIABILITYUNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DIS- TRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUEN- TIAL DAMAGES OF ANY CHARACTER INCLUDING, WITH- OUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

8. U.S. GOVERNMENT END USERSThe Covered Software is a commercial item, as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of commercial computer software (as that term is defined at 48 C.F.R. 252.227-7014(a)(1)) and commercial computer software documentation as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Software with only those rights set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes, any other FAR, DFAR, or other clause or provision that addresses Government rights in computer software under this License.

9. MISCELLANEOUSThis License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable.



This License shall be governed by the law of the jurisdiction specified in a notice contained within the Original Software (except to the extent applicable law, if any, provides otherwise), excluding such jurisdictions conflict-of-law provisions. Any litigation relating to this License shall be subject to the jurisdiction of the courts located in the jurisdiction and venue specified in a notice contained within the Original Software, with the losing party responsible for costs, including, without limitation, court costs and reasonable attorneys fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. You agree that You alone are responsible for compliance with the United States export administration regulations (and the export control laws and regulation of any other countries) when You use, distribute or otherwise make available any Covered Software.

10. RESPONSIBILITY FOR CLAIMSAs between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability.

Sun Microsystems Copyright (c) 2005 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A.

Sun Microsystems, Inc. Binary Code License Agreement for the JAVA 2 PLATFORM STANDARD EDITION RUNTIME ENVIRONMENT 5.0

SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASE READ THE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THIS SOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT. INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT" BUTTON AT THE BOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY ALL THE TERMS, SELECT THE "DECLINE"



BUTTON AT THE BOTTOM OF THE AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT CONTINUE.

1. DEFINITIONS. "Software" means the identified above in binary form, any other machine readable materials (including, but not limited to, libraries, source files, header files, and data files), any updates or error corrections provided by Sun, and any user manuals, programming guides and other documentation provided to you by Sun under this Agreement. "Programs" mean Java applets and applications intended to run on the Java 2 Platform Standard Edition (J2SE platform) platform on Java-enabled general purpose desktop computers and servers.

2. LICENSE TO USE. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of the Supplemental License Terms, Sun grants you a non-exclusive, non-transferable, limited license without license fees to reproduce and use internally Software complete and unmodified for the sole purpose of running Programs. Additional licenses for developers and/or publishers are granted in the Supplemental License Terms.

3. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software.

You acknowledge that Licensed Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement. Additional restrictions for developers and/or publishers licenses are set forth in the Supplemental License Terms.

4. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing, Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. Any implied



warranties on the Software are limited to 90 days. Some states do not allow limitations on duration of an implied warranty, so the above may not apply to you. This limited warranty gives you specific legal rights. You may have others, which vary from state to state.

5. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

6. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you, whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose.

Some states do not allow the exclusion of incidental or consequential damages, so some of the terms above may not be applicable to you.

7. TERMINATION. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement.

Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right. Upon Termination, you must destroy all copies of Software.

8. EXPORT REGULATIONS. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other



countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.

9. TRADEMARKS AND LOGOS. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.

10. U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4

(for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).

11. GOVERNING LAW. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.

12. SEVERABILITY. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate.

13. INTEGRATION. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order, acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party.



SUPPLEMENTAL LICENSE TERMSThese Supplemental License Terms add to or modify the terms of the Binary Code License Agreement. Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Binary Code License Agreement . These Supplemental Terms shall supersede any inconsistent or conflicting terms in the Binary Code License Agreement, or in any license contained within the Software.

A. Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software "README" file incorporated herein by reference, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce internally and use internally the Software complete and unmodified for the purpose of designing, developing, and testing your Programs.

B. License to Distribute Software. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce and distribute the Software, provided that (i) you distribute the Software complete and unmodified and only bundled as part of, and for the sole purpose of running, your Programs, (ii) the Programs add significant and primary functionality to the Software, (iii) you do not distribute additional software intended to replace any component(s) of the Software, (iv) you do not remove or alter any proprietary legends or notices contained in the Software, (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement, and (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.

C. Java Technology Restrictions. You may not create, modify, or change the behavior of, or authorize your licensees to create, modify, or change the behavior of, classes, interfaces, or sub packages that are in any way identified as "java", "javax", "sun" or


Bug fixes

similar convention as specified by Sun in any naming convention designation.

D. Source Code. Software may contain source code that, unless expressly licensed for other purposes, is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement.

E. Third Party Code. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME.txt file. In addition to any terms and conditions of any third party opensource/freeware license identified in the THIRDPARTYLICENSEREADME.txt file, the disclaimer of warranty and limitation of liability provisions in paragraphs 5 and 6 of the Binary Code License Agreement shall apply to all Software in this distribution.

F. Termination for Infringement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right.

G. Installation and Auto-Update. The Software's installation and auto-update processes transmit a limited amount of data to Sun (or its service provider) about those specific processes to help Sun understand and optimize them. Sun does not associate the data with personally identifiable information.

You can find more information about the data Sun collects at http://java.com/data/.

For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A.

Bug fixesIssue Tracker available on Powerlink

The Issue Tracker contains a list of bugs, similar to Release Notes, for select EMC products. This tool allows you to search on keyword fields to find particular bugs and identify the software release in which the bugs were identified/fixed. This tool can be used to check if a bug was fixed in a revision that was suggested to you. It can also be used if you're upgrading and you want to know about the revision you're going to. This is not, however, a problem or status tracking system.


Bug fixes

Fixed bug categories The following table explains the category of the bug fixes.Category Meaning

CDMS Celerra Data Migration Service

Celerra Management Applications

Celerra Monitor, Celerra Manager, Celerra Startup Assistant, MMC snap-ins, Web UI

CFS Celerra File System

CIFS Common Internet File System (Quotas, Usermapper, etc.)

Control Station Celerra Control Station, Celerra Startup Assistant

CORE Celerra Data Movers

FileMover Celerra FileMover

Hardware Hardware

MPFS (HighRoad) Multi-Path File System (HighRoad)

Installation Celerra installs, Callhomes

Internationalization Internationalization (I18N)

NDMP/Backup Network Data Management Protocol and/or Backup

Networking Networking issues

NFS Network File System

Replication Celerra Replicator, SnapSure, Checkpoint

Security LDAP

SRDF Symmetrix Remote Data Facility

Tools EMCOPY, EMCACL, LGDUP, SHAREDUP

UFS UNIX File System


Version 5.6.42.5

Version 5.6.42.5


The following are fixed problems related to the Celerra Management Applications, i.e., Celerra Monitor, Celerra Manager, WebUI, or Celerra MMC Snap-ins:

Impact Level Severity 2

Symptom Description

While using Celerra Manager, the interface tab was blank after upgrading from version 5.3 to a higher version.

Fix This problem was due to obsolete files from 5.3. Deleting those files during the upgrade process resolved this issue.

Service Request No. 17512606

Fixed in version 5.6.42.0


Symptom Description

In Celerra Manager, the ‘New replications’ page was listing files systems that were already used as destinations (for which file system type was not root). If a new replication was created with that file system, it failed.

Fix An additional check for ‘replicationState’ was added to exclude the already used destinations from the destinations list APL response.



Symptom Description

While using Celerra Manager, clicking on a folder in the left hand navigation tree, such as File Systems, did not display the page in the right hand part of the browser. The title bar was displayed, but the list portion of the page was blank.

Fix Additional handling was added to catch certain classes of exceptions caused by configuration or transient runtime environment issues.



Version 5.6.42.5


Symptom Description

When using Celerra Manager, the the nas_replicate or nas_copy command resulted in 'Error 14764015618: Unable to find _______.' The blank was filled in with the name of a checkpoint, file system, or other element that did exist. The element that could not be found was created shortly before executing the nas_replicate or nas_copy command.

Fix This cache sychronization issue has been addressed.



Symptom Description

In the Celerra Manager, on the Start replication page, if the reverse option was selected, the peer interconnect was not automatically selected. The Celerra default Interconnect displayed was the wrong interconnect.

Fix If you choose to reverse the session direction, the peer Data Mover interconnect is now automatically selected with the corresponding default source and destination interfaces. You can choose a different interconnect if the source or destination has been moved to a different Data Mover.



Symptom Description

The following error message was displayed in the Celerra Manager when accessing CIFS Shares page: User is not allowed to perform this operation due to the advancedmanager license not being enabled.” This problem occurred when using the Basic Edition of Celerra Manager. When displaying all shares, migration file systems are being queried, and this requires a Celerra Manager Advanced Edition license.

Fix The code was changed in such a way that migration file systems will not be queried when Celerra manager Basic Edition license is enabled.




Version 5.6.42.5


Symptom Description

When modifying a user quota from Celerra Manager, if only a hard limit existed, the following error was displayed: Service Temporarily Unavailable.

Fix Modifying user quotas with only a hard limit set now works correctly.




Symptom Description

Celerra Manager constructs and sends its own e-mail notifications. If a multi-byte character was used in a file system or storage pool name and its notification was set, then the email sent by Celerra Manager contained the multi-byte characters in an unrecognizable format.

Fix Added multibyte character support into the email header to support multi-byte international encoding.



Symptom Description

Using the Celerra Manager in 5.6, user could only create checkpoints on the same storage system as that of the file system. If a file system was created in a storage pool on a particular storage system, then user could not create a new checkpoint for that file system on a storage pool that resided on a storage system different from that of the file system.

Fix If the storage system name is not known to the checkpoint creation command, it assumes that the storage pool on which the checkpoint is being created is on the same storage system as that of the file system. The Data Mover now communicates to the Control Station, the storage system name of the storage pool on which the checkpoint is being created. After sending this information, user can create a checkpoint on a different storage system using the Celerra Manager.



Version 5.6.42.5


Symptom Description

Using the Celerra Management MMC snap-in to specify a user home directory (HomeDir) the path components were limited to a maximum of 20 characters.

Fix The path components for a user home directory can now be up to 255 characters.




Symptom Description

The time of the Data Mover seen on its properties page in the Celerra Manager was different from that displayed by the CLI.

Fix The Data Mover properties page displayed incorrect Data Mover time. The Data Mover sent the time in GMT time zone to its clients. This time value didn't contain the zone indicator, so the time was interpreted to be in the local time zone by the Celerra Manger. After adding the zone indicator 'Z' for GMT, the correct time is displayed in the GUI.



Symptom Description

User created a new file system using the file system wizard with an existing storage pool. In the “Enter File System Info” screen, user was able to input invalid characters in the “enter the name” field. When the user submitted the name, he got the following error: Invalid file system name. This issue only affected the Celerra Manager, the CLI worked as expected.

Fix Now, if the user tries to input disallowed characters, the user cannot type them in the field and he gets a warning sound that lets him know it is an illegal character. Periods (.), backslashes (\), spaces (‘ ’), and colons (‘:’) are not allowed. This is standard for all of our wizards when you input illegal characters.



Version 5.6.42.5

CIFS The following entries describe fixed Common Internet File System problems:


Symptom Description

When an invalid SMTP primary address was entered in the EMAIL-SMTP Primary/Secondary field in the ConnectHome page and then the focus was changed, an error dialog was displayed saying "Invalid Primary Email-SMTP Address" . If user tried to close the error pop up window by clicking on OK button, another pop up window was displayed. After closing this pop up, one more pop up window was displayed when the main window was minimized.

Fix Code was changed to ensure that error pop up will appear only on clicking the Apply or Test button.



Symptom Description

Under some conditions when Data Mover memory statistics were unavailable, the Data Mover List Page did not display correctly. The page was reached from the left-hand navigation tree, clicking on the Data Mover folder. The page title bar and tabs were displayed, but some or all of the contents was missing.

Fix Code was added to handle a boundary condition where Data Mover memory statistics are unavailable. The list of the Data Movers will now display correctly.



Symptom Description

The server_http command no longer accepted the SSL protocol 'ssl3' and 'tls1'. The usage of this command indicated incorrect keywords. Celerra Network Server version 5.6.42.0 supported only the keywords 'sslv3' and 'tlsv1' instead of those above. This issue was related to the implementation of the new command server_ftp, which supports the same arguments and the same keywords.

Fix The server_http command was fixed to accept the previous and the new keywords. This command now supports the following: "ssl3", "sslv3", "tls1" and "tlsv1".



Version 5.6.42.5


Symptom Description

When a CIFS appplication changed a file's allocation size, Celerra changed the end of file as well. This caused the file to consume more space than intended.

Fix In cases where file allocation size is greater than the file size itself, the logic now extends a file's allocation size without increasing usage space (the end of file position). If the file allocation is smaller than the file size, the file will be shrinked.




Symptom Description

NAS code upgrade from 5.5 to 5.6 failed at "Check dbms migration status" task when secmap was disabled. In this case, secmap was intentionally disabled by setting param cifs secmap.enable=0.

Fix For Data Movers/VDMs with CIFS enabled, code now checks the boot.cfg for physical Data Mover. If cifs secmap.enable=0 is included, code skips the DM/VDM for secmap backup and later migration status checking.




Symptom Description

When a network interface is disabled using the server_ifconfig command, a CIFS compname using this interface should not show this interface in the used interface list. The interface list of the compname was not updated as expected and showed disabled interfaces.

Fix The interface list now shows only enabled interfaces and ignores disabled interfaces.



Version 5.6.42.5


Symptom Description

When the parameter cifs.acl.unixCheckAcl is set and the access policy is UNIX, it should only be checking mode bits. In the case of creation or deletion, CIFS access was checking both mode bits and ACL.

Fix The behavior is now consistent: when the access policy is UNIX and the parameter cifs.acl.unixCheckAcl is set to 0, ACLs are always ignored.



Symptom Description

Users were unable to access CIFS shares when logging in using usernames with UPN suffixes (e.g. <username@UPNdomainName>) from client machines that were not part of a domain. This problem was caused by an invalid handling of UPN usernames by a Data Mover that was implemented in NAS v5.6. The UPN username was incorrectly converted to <UPNdomainName\username> format, which caused Domain Controller to refuse authentication.

Fix The fix for this issue was to revert back to the correct mechanism of handling UPN suffixes that was used in NAS v5.5 where the username is not converted to <UPNdomainName\username> format.




Symptom Description

In certain configuration it was possible that any regular Windows user could change UNIX permissions (mode bits), the owner and primary group on a file system from a Windows client. In order for this problem to occur the following parameters needed to be set:cifs.acl.extacl=2cifs.acl.unixChackAcl=1cifs.acl.retrictedTakeOwnership=1

Fix The fix for this issue enforces the UNIX semantic for changing permissions, owner and primary group. Only owner or root user (uid=0) can change these settings from a Windows client.



Version 5.6.42.5


Symptom Description

Users were unable to access CIFS shares when logging in using usernames with UPN suffixes (e.g. <username@UPNdomainName>) from client machines that were not part of a domain. This problem was caused by an invalid handling of UPN usernames by a Data Mover that was implemented in NAS v5.6. The UPN username was incorrectly converted to <UPNdomainName\username> format, which caused Domain Controller to refuse authentication.

Fix The fix for this issue was to revert back to the correct mechanism of handling UPN suffixes that was used in NAS v5.5 where the username is not converted to <UPNdomainName\username> format.




Symptom Description

When trying to write an unknown SID in a file security descriptor (SD), the Data Mover panicked with the following DART panic/fault message: >>PANIC in file:../ at line: 1477 : bad SD storage size. The stack trace showed: 0xbfa4bc70: 0x13d890 waitForReboot+0x90 0xbfa4bc90: 0x13da8d fault_dump+0x67 0xbfa4bcb0: 0x13d98d PANIC+0x29 0xbfa4bcc0: 0x9b8301

_ZN7CIFS_SD12writeStorageEPS_P13smb_threadCtxm 0xbfa4bde0: 0x9b34ce

_ZN13smb_threadCtx7ntSetSDEP15File_NamingNodeP 0xbfa4beb0: 0x9b30fb

_ZN13smb_threadCtx16callTransNTSetSDEP17smb_tr 0xbfa4bef0: 0x9b15fc

_ZN13smb_threadCtx12replyTransNTEP4msgb+0x1a4 0xbfa4bf30: 0x91776d _ZN13smb_threadCtx7processEP4msgbi+0x957 This happened because an unknown SID of the owner group part of the security descriptor was incorrectly identified as a well-known SID, causing the following setSD request to fail.

Fix The code was changed to reject any mal-formed SID when handling setSD requests.




Version 5.6.42.5


Symptom Description

From a Microsoft Vista client, an authorized user could not delete a directory if it had the read-only attribute set. The following message was displayed: STATUS_ACCESS_DENIED.

Fix A directory delete will now succeed for an authorized user from a Vista client even if the read-only attribute is set.




Symptom Description

When doing a robocopy from a Celerra file system to a local host tape device using Windows OS, there was a condition during the internal delete file auditing where a string with a NULL pointer was referenced which causing the Data Mover to panic with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: cb4a5b Err code: 0 Target addr: 0 **. The stack trace showed: 0x1cbbfbc: 0x13eec4 waitForReboot+0x90 0x1cbbfdc: 0x13f0c1 fault_dump+0x67 0x1cbbffc: 0x1387a0 handle_fatal_fault+0xa 0x1cbc020: 0x6401e8

_ZN15File_NamingNode17auditObjectDeleteEPK18Fil 0xe226d9f0: 0x604c67

_ZN12File_DirNode12removeLockedEPK18File_NameC 0xe226dbb0: 0x736213

_ZN26passthroughShadowDirectory6removeEPtm13Fi 0xe226dcb0: 0xaef02c

_ZN8AppLibNT5closeEP8fid_infoiR11File_StatusP1 0xe226def0: 0xa3e3d9

_ZN13smb_threadCtx10replyCloseEP4msgb+0x1e1

Fix Code now checks for NULL pointer and dismisses execution of the internal delete file auditing if NULL.




Version 5.6.42.5

Control Station The following entries describe fixed problems related to the Celerra Control Station:


Symptom Description

User could not create a virtual machine with Microsoft Windows 2008 Hyper-V. The error The security ID structure is invalid was returned.

Fix Virtual machine can now be created without any error.



Symptom Description

When using quotas and exceeding a hard quota, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../sched.cxx at line: 819 : SYSTEM WATCHDOG. The stack trace showed: 0xdc721cb4: 0x13d810 waitForReboot+0x900xdc721cd4: 0x13da0d fault_dump+0x670xdc721cf4: 0x13d90d PANIC+0x290xdc721d04: 0x13f669 system_watchdog+0x770xdc721d14: 0x13768d _t_nmi+0x630xdc721d80: 0x621322

_ZN9UFS_Vnode17readIndirectBlockElRP13Buffer_C0xdc721db0: 0x6219f2 _ZN9UFS_Vnode4bmapElRlPiS1_+0x1e80xdc721e10: 0x62514d

_ZN9UFS_Vnode5breadEjR11File_Statusi+0xc1

Fix Code was taking a lock after a function call. The order of events has been reversed to avoid the condition that led to the panic.




Version 5.6.42.5


Symptom Description

When the nas_rdf –restore command on a CNS system was executed form a destination Control Station, a source Control Station was stuck in reboot process due to a reboot command executing as a background process. The stuck Control Station required a hard reset to recover the situation.

Fix Code has been modified to run the reboot command as a foreground process to eliminate this issue.



Symptom Description

Users could create i18n characters in share name comment or tree quota comment even on an ASCII Data Mover. This should not be allowed.

Fix The fix prevents i18n characters from being used on an ASCII Data Mover. The following message is printed in CLI output. It is also printed in GUI CCMD. [nasadmin@eng17344 ~]$ server_export server_3 -n ???? /test

server_3 :

Error 13431603211: server_3 : ?: Invalid CIFS Share name character. A CIFS share name on a Data Mover that does not have Unicode enabled must use ASCII characters only.

[nasadmin@eng17344 ~]$.



Symptom Description

In a Replication V1 environment, when the Control Station on the source Celerra was not available, the "Refresh", "Suspend", "Restart", "Reverse" and "Failover" buttons were all greyed out in the Replications tab in the destination Celerra's WebUI. Therefore if the source Celerra was down or the source Control Station was unavailable, failover was only possible through the CLI.

Fix The destination Control Station now uses the local information in the destination database to manage failover of the file systems.




Version 5.6.42.5


Symptom Description

When trying to list group quotas on a file system with path “/” using CLI command, the command failed.$ nas_quotas -group -report -fs <fs> -path /Error 12040: /: A tree quota path that a single forward slash is not valid. You must specify a directory name after the forward slashThe problem was that the command did not accept the single forward slash as a valid path.

Fix The code was updated so the command will accept the single forward slash “/” as a valid path.



Symptom Description

If the Control Station rebooted, and a dial-in to the Control Station was attempted before the nas services was started, the dial-in failed due to files necessary to configure the modem not being accessible.

Fix This issue was resolved by making the files required to setup dial-in independent of nas services.



Symptom Description

The nas_storage –check –all command failed with the following error trace if a CLARiiON DAE with a configured RAID group was powered down: Execution failed: have_spindles: Precondition violated. [DISK_GROUP.spindle_type]. This error did not give any information as to why the command was failing.

Fix With the fix, the nas_storage –check –all command will now display the following error (on the console) under these conditions: Faulted/removed.



Version 5.6.42.5


Symptom Description

On Celerras that have been originally fresh installed with the 5.6 release, when an administrator tried to enable UNICODE to use CIFS on a Data Mover that was converted from a standby to a primary nas server, the /nas/bin/server_setup server_3 -type nas command failed with:Error 10314: server_3 : Failed to apply Unicode fonts when server server_3 was being converted to type "nas".

Fix In fresh installs, the internationalization setup code was reordered to occur when all Data Movers are of type nas and before the standby Data Mover is assigned. Upgrades are unaffected. Also, added code to create the /.etc_common Data Mover directory whenever setup_slot is run except during installs.



Symptom Description

The /nas/sbin/nas_rdf -activate command succeeded and the expected error occurred against server_2 where non-rdf'd file systems were mounted to an rdf protected Data Mover. The following error was seen by the user: server_2 : server_2 : going offlinerdf : going activereplace in progress ...failedfailover activity completereplace_storage: replace_volume: volume is unreachable d607,d608,d609,d610,d611,d612,d613,d614,d615,d616,d617,d618,d619,d620,d621,d622,d623,d624,d625,d626,...

The work-around was followed. The documented procedure is to unmount the local file systems and rerun the server_standby command against the Data Mover. The server_umount command failed with the following error: # server_umount server_2.faulted.rdf -p ipcam_nr_01 server_2.faulted.rdf : Error 10281: server_2.faulted.rdf : ipcam_nr_01 : unable to unmount. Cannot determine file system status from the server.

Fix The nas_rdf -activate command now skips mounting of non-SRDF'd (local) file systems, and continues the activation of the disaster recovery Data Mover.




Version 5.6.42.5

CORE The following entries describe fixed problems related to Celerra Data Movers:


Symptom Description

When trying to extend a file system with a TimeFinder mirror, the extend failed with the following error:Execution failed: has_disk_type: Precondition violated. [VOLUME_TRANSACTION.make_duplicate]

Fix Changed the way the BCV volume used for the mirror extension is selected. It will now just use the same disk type of the existing mirror.



Symptom Description

When using a write-only CIFS workload to generate load on a system, user had 16 threads writing to each file system simultaneously, and was scaling up the number of file systems in use. When user reached 252 file systems or beyond, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../bufpool.cxx at line: 340 : couldn't get a free page. The stack trace showed:0x91b65bb0: 0x146344 waitForReboot+0x900x91b65bd0: 0x146557 fault_dump+0x670x91b65bf0: 0x146441 PANIC+0x290x91b65c00: 0x197e89

_ZN18Buffer_Cached_Pool17makeCachedBuffersEi+00x91b65c30: 0x13fc65

_ZN19Memory_AddressSpace16makeCachedBufferEv+00x91b65c50: 0x1977a1

_ZN18Buffer_Cached_Pool15getAnyCachedBufEji+0x0x91b65c80: 0x733ed2

_ZN16File_WriteSource11createBlockEmjRmR11File0x91b65cb0: 0x7376cd

_ZN13File_OpenFile9writeDataEymR11File_StatusP

Fix The fix introduces a scaling mechanism to control the amount of outstanding I/O to a file which triggers a flush to disk. By default up to 256k of a write I/O to a file from a client can remain in memory before it is flushed to disk. This is controlled by the asynchthreshold parameter. This fix adds a monitor for free memory to that calculation. When free memory on the drops below 50%, the asyncthreshold value is dynamically dropped from 256k (32 * 8k) to 128k (16 * 8k). This means that the Data Mover is freeing up memory by flushing any pending data over 128k instead of waiting for 256k. If free memory drops below 45%, then the threshold is reduced to 64k, if free memory drops below 40% the threshold is reduced 32k, and the lower limit is at 35% of memory available when the threshold is set to 16k (2 blocks). When free memory starts increasing the sequence reverses.



Version 5.6.42.5

FileMover The following entries describe fixed issues related to the Celerra FileMover:


Symptom Description

A power outage condition with ES104M McData Switch caused an environmental issue which resulted in a Data Mover panic with the following panic header: >>PANIC in file: ../dskdump.cxx at line: 1835 : hba2 offline online after datacenter power outage.

Fix Error condition handling was enhanced to avoid the panic caused by the environmental issue. Data Mover will now attempt to recover connectivity to the switch.




Symptom Description

There was window where file system unmount thread could change fsState to VFS_Unmounting and file sytem thaw thread could find asyncDB vnode NULL. This caused a Data Mover panic with the following DART panic/fault message: *** GP exception. Virt ADDRESS: 8b0389. Err code: 0 ***. The stack trace showed: 0x23603a8: 0x146bbc waitForReboot+0x90 0x23603c8: 0x146dcf fault_dump+0x67 0x23603e8: 0x13c59c handle_fatal_fault+0xa 0x2360450: 0x89309a

_ZN9UFS_Vnode8blkatoffEyRPvRP13Buffer_Cachedi14 0xbc251e20: 0x86e542

_ZN9UFS_Vnode17readMetaFileBlockElRP13Buffer_C 0xbc251f40: 0x8e2d65

_ZN14UFS_FileSystem17resumeAsyncDeleteEv+0x17f 0xbc251f80: 0x775a83 _ZN11ResumeEvent11handleEventEv+0x17 0xbc251fa0: 0x19166f

_ZN17SvcThread_InitialIS_I15Sthread_InitialEE5

Fix We eliminated this window by releasing useMutex after dispatching event for resumeAsyncDelete which will prevent file system from unmounting.



Version 5.6.42.5


Symptom Description

When user changed the cifsclient.timeout parameter to increase the timeout value to 120 from its default of 20 seconds, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../dskdump.cxx at line: 1450 too many cons. The stack trace showed: 0xeb483a80: 0x13d05b waitForReboot+0x8b 0xeb483aa0: 0x13d263 fault_dump+0x67 0xeb483ac0: 0x13d163 PANIC+0x2b 0xeb483ad0: 0x844880 _Z11paniccfgcmdR6Option+0x178 0xeb483c10: 0x1617d9

_ZN11cfgcmd_desc6invokeEPKcPP11CCMDMessageii+0 0xeb483c80: 0x1fe152 _Z10xml_cfgcmdP7macDataRP8CCMD_Msg+0x30e

Fix The issue was due to the fact that the check to see whether the offline I/O thread count limit has been crossed was done after grabbing the pause lock and the naming node lock. In several situations since the thread(s) were blocked while trying to acquire the locks the check was too late. Code now performs the checks prior to grabbing the locks.




Symptom Description

While using Symantec Enterprise Vault Policy Engine (PE) servers, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 1a7505 Err code: 0 Target addr: 0 **. The stack trace showed: 0x1cbc294: 0x13eec4 waitForReboot+0x90 0x1cbc2b4: 0x13f0c1 fault_dump+0x67 0x1cbc2d4: 0x1387a0 handle_fatal_fault+0xa 0x1cbc300: 0x23d80b

_Z18dhsm_xml_get_attrsP10DHSM_replyP14XmlElemen 0xd805bda0: 0x23e78b

_Z15dhsm_XMLHandlerP13logObject_XMLPKcP4msgb+0 0xd805bdd0: 0x11303a5

_ZN13XmlHandler_DB6invokeEPKcP13logObject_XML This was happening during File Archiving operations when the PE used an uncommon syntax.

Fix The Data Mover was not handling FileMover API syntax correctly. The code has been fixed to handle this condition preventing the panic.




Version 5.6.42.5

Install/Config/ Upgrades

The following entries describe fixed issues related to installations, configurations and upgrades:


Symptom Description

After a Data Mover was recently replaced, numerous dial-homes were generated stating that Enclosure 0/1 Blade 1 was removed. Jul 29 22:09:19 2008:CS_PLATFORM:BoxMonitor:CRITICAL:500:: ::1217362159:Enclosure 0 compute blade B has been removed.Jul 29 22:14:49 2008:CS_PLATFORM:BoxMonitor:CRITICAL:500::::1217362489:Enclosure 0 compute blade B has been removed.Jul 30 00:56:20 2008:CS_PLATFORM:BoxMonitor:CRITICAL:500:: ::1217372180:Enclosure 1 compute blade B has been removed.Jul 30 01:43:58 2008:CS_PLATFORM:BoxMonitor:CRITICAL:500::::1217375038:Enclosure 0 compute blade B has been removed.Jul 30 01:52:57 2008:CS_PLATFORM:BoxMonitor:CRITICAL:500::::1217375577:Enclosure 1 compute blade B has been removed.This event only occurred on multiple enclosure systems that did not have the same physical presence configuration for each enclosure.

Fix The cause of the blades appearing and disappearing was a result of incorrectly using the status flags of enclosure 0 for enclosure 1. The fix was an enhancement to packet sequence checking in the NAS Control Station software to verify the the correct packet was received in the event of a system resources error.




Symptom Description

If none of the Data Movers were up and running, the callhome delivery with dial-up or email transport mechanisms failed.

Fix The dial-up and email configuration files are now saved on both the Control Station local disk and the backend disk. Even without any Data Movers up and running, the ConnectEMC module can still retrieve the configuration files and send out the callhome files.



Version 5.6.42.5

iSCSI The following fixed problems are related to Internet Small Computer Storage Interface (iSCSI):


Symptom Description

When performing proxy_arp setup (either through CSA or via the command-line using clariion_mgmt), the operation failed because certain critical sections were not performed.

Fix Additional timeouts and status checking were added to verify the integrity of system components before allowing the proxy_arp setup operation to continue.



Symptom Description

The server_setup server_x -P cifs -o start command was removed from the netd file during the NAS code upgrade when CIFS was stopped. The command should have been put back following the command timeouts during the UserMapper and secmap upgrades but wasn't. Later the upgrade restarted CIFS, but never updated the netd. When the Data Mover was rebooted, CIFS did not start.

Fix Added code to check "cifs start" in boot.cfg file during the upgrade for physical Data Movers. If missing, restarting CIFS will automatically add "cifs start" into the boot.cfg file.




Symptom Description

When performing Data Mover failover using server_standby command, the command appeared as hung and it took more than 4 minutes to complete a Data Mover failover. The same behavior occurred when trying to shut down the Data Mover using the server_cpu command.The problem occurred only when iSCSI service was started and iSCSI LUNs existed. This happened because of a resource that was left open during Data Mover start up. During shutdown/failover, the Data Mover waited for the resource to be closed and timed out after 4 minutes.

Fix The code was changed to correctly close the resource when it is not needed prior to shutdown.




Version 5.6.42.5


Symptom Description

During ISCSI List processing on the Control Station, there was a race condition which was not being handled correctly. The condition arose when the List functionality was waiting for a Data Mover to respond, but the Data Mover was offline. If the list request was aborted by the user, the communication channel which was used to respond to the user was closed. However when the timeout occured it tried to send back a response on the channel, but failed to confirm if the channel was still available to accept transmissions. As a result, the code seg faulted and the master control deamon restarted the mgmtd. When the mgmtd came back up, its task recovery code tried to send back the response from the expired timer. This code then failed with a segmentation violation faults because the channel was gone. The mgmtd then ended up in a rolling panic scenerio.

Fix Code now verifies the channel is available before trying to send the response. If the channel is not available then the response is dropped.




Symptom Description

When user deleted a LUN along with all it's snaps, he first deleted all the snaps, and then deleted the LUN. When attempting to delete the LUN, the asynchronous deletion of the last snap was still running in the background which caused the LUN delete command to fail. A side effect of this error is that although it will look like the LUN is gone, its storage is leaked and the user will have no way to clean it up. In addition, if the user then tries to create the same LUN # again on the same FS, they will encounter a failure since the remnants of the old LUNs storage will conflict with the creation of the new LUN.

Fix Code now provides an asynchronous mechanism to delete the version file of an iSCSI LUN. The LUN delete operation may fail if the block ownership is still being processed from the last deleted snap. In this case, we move the version file to a temporary directory via a hard link, cleanup the versionset directory, kick-off a retry mechanism to delete the version file from the temporary directory, and return success to the user for the LUN delete operation.



Version 5.6.42.5

MirrorView The following entries describe fixed MirrorView issues:

:


Symptom Description

If the CLARiiON backend was failed over, the nas_mview -activate command hung while the code waited for the Consistency Group to become synchronized. # /nas/sbin/nas_mview -activate Sync with CLARiiON backend ...... done Validating mirror group configuration ...... done Is source site tribute ready for complete shut down (power

OFF)? [yes or no] Yes Contacting source site tribute, please wait... done Waiting for device group ready to failover ......

Fix Code no longer waits on Consistency Group status if backend is already failed over.



Symptom Description

CLARiiON no longer allows MirrorView/S consistency group promotion from the “consistent” state. This resulted in an error during activation if the consistency group had not yet reached the synchronized state. MirrorView activation failed with the following error:......STARTING an MV 'FAILOVER' operation.Device group: <device-group-name> ............The MV 'FAILOVER' operation FAILED.Error 3501: Storage API code=1: <device-group-name>:

SYMAPI_C_FAILThe function call failed

Fix Code now waits for Mirrorview device group to be synchronized before starting the failover process.



Version 5.6.42.5

MPFS The following entries describe fixed issues pertaining to Multi-Path File System:


Symptom Description

When the user tried to mount a CIFS share over the MPFS server, if the file system was corrupted, the Data Mover panicked with the following DART panic/fault message: *** GP exception. Virt ADDRESS: 7e90fe. Err code: 0 ***. The stack trace showed: 0x249cdf8: 0x147f7c waitForReboot+0x900x249ce18: 0x14818f fault_dump+0x670x249ce38: 0x13ced0 handle_fatal_fault+0xa0x249ce80: 0x9fa2e1

_Z18fmp_releasewrite_3P9writeArgsP7svc_reqPP11F0x8de159b0: 0x9f1699

_ZN26fmp_IterSvc_Parent_InitialC1EP16Rpc_Svc_A0x8de15a40: 0x50c29f

_ZN21Rpc_Svc_Child_Initial13svc_getreqsetEP7rp0x8de15c30: 0x50ff7c

_ZN25Rpc_IterSvc_Child_Initial7svc_runEv+0x2100x8de15fd0: 0x50fd61

_ZN25Rpc_IterSvc_Child_Initial5startEv+0x19

Fix Added proper checks in the MPFS server to fail the CIFS share mounting operation when the file system is corrupted.



Symptom Description

After creating files on a file system mounted over MPFS, if user mounted the same file system over NFS, data integrity was compromised when accessing those file. The same data inconsistencies also occurred if a file system was mounted NFS first and then mounted MPFS. This was due to the HVM (Hierarchical Volume Management) feature turned on by default as of release 5.6.39.5

Fix The HVM is now turned off by default and a parameter mpfs useHVM was added to turn it back on. This fixes the 32-bit rounding problem in slice offsets.




Version 5.6.42.5

NDMP The following entries describe fixed issues related to Network Data Management Protocol and/or Backup:


Symptom Description

During an NDMP backup, using VBB, the Data Mover panicke with the following when a NULL ACL pointer was encountered. The Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: fde735 Err code: 0 Target addr: 0 **. The stack trace showed: 0x1cbc4f4: 0x13eec4 waitForReboot+0x900x1cbc514: 0x13f0c1 fault_dump+0x670x1cbc534: 0x1387a0 handle_fatal_fault+0xa0x1cbc5b0: 0xfe188f

_ZN14ProcessDirTask12processInodeEP6dinodemRii+0x3e2aff10: 0xfe1526

_ZN26AllocatedInodeIteratorTask16traverseInode0x3e2aff90: 0xfe12cd

_ZN26AllocatedInodeIteratorTask3runEv+0xbb0x3e2affc0: 0xff3005

_ZN24vbbProjectMember_Initial5startEv+0x1b0x3e2affe0: 0x143644 Sthread_startThread_internal+0xe

Fix The error check is now processed earlier in the code so warnings will be logged and the backup will continue.




Symptom Description

When a VBB session was aborted immediately after it was started, the Data Mover panicked with the following DART panic/fault message: *** GP exception. Virt ADDRESS: fd35eb. Err code: 0 *** . The stack trace showed: 0x1c8c2a8: 0x13e694 waitForReboot+0x90 0x1c8c2c8: 0x13e891 fault_dump+0x67 0x1c8c2e8: 0x138768 handle_fatal_fault+0xa 0x1c8c380: 0xfd30bd _ZN10vbbSession5startEv+0xdf 0xde9effe0: 0x142e3c Sthread_startThread_internal+0xe When the session is aborted during VBB initialization, access to the deleted sessionApi caused this panic.

Fix Code now checks the session abortFlag before doing any VBB initialization, and the panic no longer occurs.



Version 5.6.42.5

Network The following entries describe fixed Network-related issues:


Symptom Description

When powering up an NS20/NS40 single Data Mover system, code incorrectly reported that it was unable to communicate with a non present switch. Users saw the following message upon reboot: Enclosure 0 management switch A RS-232, no peer traffic. <<<<< Aug 6 20:17:47 2008:96108478965::Enclosure 0 compute blade A has been detected.

Fix The error is now correctly masked when a peer management switch is not present.




Symptom Description

When the system tried to allocate a stream for a TCP connection, if the opened failed, the counter used to track open TCP connections was still incremented. The close path for the error condition never decremented this counter. This led to requests for new TCP connections not being serviced due to the the system thinking that the maximum number of TCP streams were already in use.

Fix The counter is now decremented when an error occurs during the open and therefore does not get out of sync.



Symptom Description

When using FTP or TFTP, if there was a symbolic link to a file, user could ''get'' the file directly, but could not ''get'' the file through the symbolic link regardless of how the symbolic link was created (relative path or absolute path).

Fix Code was modified and symbolic link files can now be opened.




Version 5.6.42.5

NFS The following entries describe fixed issues related to Network File Systems:


Symptom Description

User was unable to browse a directory with Internet Explorer via FTP when this directory had more than 100 subdirectories. The problem occurred because the Data Mover incorrectly formed a reply to the FTP LIST request when the number of subdirectories was greater than 100, it overflowed into the UNIX permissions column without the ASCII space delineator. This caused the Internet Explorer to incorrectly interpret the directory listing.

Fix Changed the FTP code to construct the reply to LIST command correctly by adding a space between the directory rights (drwxr-xr-x) and the link count.




Symptom Description

The 10Gb Neterion adapter can encounter memory errors when receiving specific data patterns resulting in data retransmissions.

Fix A modication was made to the adapter driver to change the signal termination used and eliminate the memory errors.




Symptom Description

When using the server_nfs <dm> -v4 command, the NFSv4 domain name was not displayed.

Fix The NFSv4 domain name is now displayed.



Version 5.6.42.5

Replication The following entries describe fixed problems encountered while using Celerra Replicator, SnapSure or Checkpoints:


Symptom Description

When the length for the NFS export list exceeded 2048 characters, the server_export command succeeded, allowing unauthorized hosts (not in the export list) to have access to exported file system on Celerra.

Fix Code has been modified to check the length of NFS export list and if the limit is reached, the command fails with the following error: Export Error: rw= or root= for options too long.




Symptom Description

When evaluating mount requests from NFS clients, Celerra accepted NFS MOUNT requests from TCP or UDP ports in the “non-privileged” (above 1024) range. In some environment, this made it easier for non-system administrators to create a program that contacts Celerra pretending to have a different UID or GID. The NFS client would have to be given access to Celerra in the first place, and would not be possible when using Secure NFS.

Fix Added the capability to turn on NFS MOUNT port checking, which rejects requests from clients if the requests come from a TCP or UDP port over 1024 (non-privileged ports). This capability can be turned on by enabling the parameter “mount.checkPort”.



Symptom Description

While using Replication V2, and executing a nas_task -abort <taskId> command, the modify operation task showed an error status after aborting the task- DpRequest_AbortInProgress in the task info even if the task was aborted successfully.

Fix Code now sends a correct status as a final response to Control Station (instead of DpRequest_AbortInProgress).



Version 5.6.42.5

:


Symptom Description

If user created a checkpoint for a file system which was the destination file system of a replication and the replication was in progress of creation, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../addrspac.cxx at line: 282 : Out of memory. The stack trace showed: 0xfece3c80: 0x13eec4 waitForReboot+0x900xfece3ca0: 0x13f0c1 fault_dump+0x670xfece3cc0: 0x13efc1 PANIC+0x290xfece3cd0: 0x13a2be

_ZN19Memory_AddressSpace10allocPagesEi12Memory0xfece3cf0: 0x1a3c30 _Z11more_memoryjP9free_list+0x500xfece3d10: 0x1a3cee malloc+0x980xfece3d40: 0x1a447d _Znwm+0x150xfece3d50: 0x1a44aa _Znam+0xc The problem occurred because of a deadlock in the system and also high memory utilization.

Fix Fixed the internal deadlock and the memory utilization problems. The Data Mover will no longer panic under this condition.



Symptom Description

While setting up replication on a production NS600, user specified a max bandwidth of 10KB/sec using the Celerra Manager. The replication start was OK, however the inital copy (fs_copy) took up a lot of the bandwidth and ignored the max bandwidth specified. This caused performance issues during production, user reported seeing close to 8MB/sec of transfering rate.

Fix The field QOS for defining the bandwidth for the replication is applicable for the remote replication only, not for local/loopback in Celerra Manager. While creating a remote replication, the information (source, destination, highwatermark, etc.) including QOS is sent to the APL layer to execute/start the replication. Previously APL did not use provided 'QOS' value in fs_copy, instead APL used Maximum available bandwidth. User specified qos/kbps value was used only in the 'fs_replicate' command. Code has been fixed to use the 'QOS' value specified by user, in the fs_copy command.




Version 5.6.42.5


Symptom Description

If a Data Mover was rebooted while aborting a Repv2 local copy operation, copy related task and internal checkpoint were not cleaned up.

Fix This problem was fixed, all related tasks and internal checkpoint for copy operation will now be recovered and completed after the Data Mover is rebooted.



Symptom Description

If a loopback replication session was aborted while the full copy was still in progress, the internal replication checkpoints on the secondary file system were not deleted and some tasks remained in an orphaned state on the Data Mover.

Fix For loopback replication sessions, the Control Station converts the abort into a full abort, thus deleting the internal checkpoints and tasks for both source and destination file systems.



Symptom Description

When user aborted a modify task that had gone into continuous retries due to an error on modifying the replication, the Data Mover panicked with the following DART panic message: *** Page Fault Interrupt. Virt ADDRESS: f5694f Err code: 0 Target addr: 394 **. The stack trace showed: 0x1cdf694: 0x13eec4 waitForReboot+0x90 0x1cdf6b4: 0x13f0c1 fault_dump+0x67 0x1cdf6d4: 0x1387a0 handle_fatal_fault+0xa 0x1cdf730: 0xf562a0

_ZN23CmdReplicatev2ModifyPri9modifySLAEv+0x55c 0xdf98ff30: 0xf556ca

_ZN23CmdReplicatev2ModifyPri14handleFsmEventEP 0xdf98ff60: 0xf555c3

_ZN23CmdReplicatev2ModifyPri11handleEventEP11s 0xdf98ff80: 0xf35e98

_ZN19CmdReplicatev2Event11handleEventEv+0x7e 0xdf98ffa0: 0x179d49

_ZN17SvcThread_InitialIS_I15Sthread_InitialEE5

Fix Fixed a typo that was in the modify task abort code and caused this issue.



Version 5.6.42.5


Symptom Description

During a Repv2 copy session data transfer, the task status showed "Transfer done" in the field of "Current Activity" for the nas_task -info command.

Fix Changed "Current Activity" of "Transfer Done" to "Transfering data" for nas_task -info of copy operation .



Symptom Description

The CLI nas_replication -info command incorrectly showed a current transfer rate after a transfer was done. The Celerra Manager replication property page was correct and didn't show a current transfer rate after the transfer was done.

Fix The code was changed to ensure that the nas_replicate -info command now displays current transfer rate only when transfer is in progress.



Symptom Description

When user issued a nas_replicate -modify iscsi_svr2fs3_svr3fs4 -name iscsi_svr2fs3_svr2fs2 command to modify a replication session name, if the replication session name already existed on the same Data Mover, the command returned OK but the name change was not reflected.

Fix If the replication session name already exists on the same Data Mover, the following error is now returned: Error [13160415247]: DpRequest_DuplicateAlias



Version 5.6.42.5


Symptom Description

A task remained hung on the Control Station on the destination side of a Replication V2 pair. The NAS code upgrade could not complete because this task was still running. The task could not be aborted because no peer task could be found on the source side Control Station.

Fix This fix allows the nas_task -abort to complete against a task that has no peer task running on the peer Data Mover.




Symptom Description

Attempts to abort a switchover task following a Data Mover failover did not succeed. The switchover completed, but the tasks remained hung.

Fix Added handling of a nas_task local abort when replication is in tranferring and registering states.




Symptom Description

The user started a loopback replication session to an existing destination file system. During the full copy, the user tried to delete the replication session. Before the replication delete completed, the user rebooted the Data Mover. This left the delete task on the Control Station and the internal replication checkpoints on the Data Mover.

Fix The checkpoint and the replication layers now maintains the status of the delete operation across reboots.




Version 5.6.42.5


Symptom Description

If the Data Mover rebooted during the reverse operation of a loopback replication, the task was stuck at 80% complete status.

Fix If the Data Mover reboots at a stage where the primary side of a loopback replication is stopped, after the reboot, the secondary side of the loopback replication can now stop itself successfully. This enables the reverse task to eventually complete.



Symptom Description

If an LDAP Result response received from an external LDAP server is corrupted during transmission, it is remotely possible for the result to be interpreted as a Sequence with less than 3 entries. The code incorrectly assumes there will always be at least 3 entries in the Sequence (for an LDAP Result), and the system panics when it tries to access an out-of-range entry; e.g., the third entry when only 2 entries exist.

Fix Code now checks to make sure there are at least 3 entries in the sequence, before processing the LDAP result. addition, added the following error message when less than 3 entries are returned: Received incomplete/corrupted LDAP Result message.




Symptom Description

The nas_replicate –info command output for Next Transfer Size showed Kb instead of KB.

Fix The nas_replicate –info command output for Next Transfer Size has been changed to correctly show KB.



Version 5.6.42.5


Symptom Description

The column header under fs_ckpt <fs_name> -list was "ckpt_usage_on_savvol" and nas_fs -size gave the parameter name as "ckpt_usage_on_savevol". The spelling of the word "SavVol" was inconsistent.

Fix Column/field header for ckpt_usage_on_SavVol for nas_fs and fs_ckpt did not match. Spelling for "savevol" has been corrected to "savvol".



Symptom Description

If a Data Mover reboot occurred during a Replication V2 create/start/copy operation and the operation encountered an internal error (such as replica start error), the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: f2d7e0 Err code: 0 Target addr:0 **. The stack trace showed: 0x1cdf754: 0x13eec4 waitForReboot+0x900x1cdf774: 0x13f0c1 fault_dump+0x670x1cdf794: 0x1387a0 handle_fatal_fault+0xa0x1cdf7d0: 0xf2d268 _ZN14CmdCommonEvent11handleEventEv+0x600xdf689fa0: 0x179d49

_ZN17SvcThread_InitialIS_I15Sthread_InitialEE50xdf689fe0: 0x143644 Sthread_startThread_internal+0xe

Fix This problem is resolved and the Data Mover can now recover from an internal error during the create/start/copy operation.



Symptom Description

The Data Mover connects to the Windows Active Directory (on a domain controller) for a number of features. If the domain controller currently being used becomes unavailable (either through network issues or the domain controller fails), the LDAP code that access the Active Directory continues to try to connect to the 'failed' domain controller, even if other domain controllers are available. This can result in (at least) failed GPO updates, and loss of CIFS access by clients if user mapping is enabled.

Fix If an LDAP connection to a domain controller fails, the Data Mover will get a list of available domain controllers from DNS, and use another domain controller (instead of the one that failed).



Version 5.6.42.5

Security The following entries describe fixed issues related to security:


Symptom Description

SASL External authentication; i.e., the client certificate is used to authenticate the LDAP bind, after the SSL connection is established. This authentication method requires the LDAP Server to be configured with the client certificate, during the SSL Handshake. However, if the LDAP Server was not configured to require the client certificate, then the subsequent LDAP bind failed. This is expected behavior, but the resulting error messages in the server log were confusing 2008-04-08 14:49:54: LDAP: 3: LdapClient::connect: ldap server 192.168.76.29: error message: SASL(-4): no mechanism available:(error code 7)

Fix Added a new error message that clearly describes the issue, and the recommended action; e.g., Reconfigure the LDAP Server to require the client certificate. LDAP SASL bind using the SSL client certificate for authentication failed".



Symptom Description

The Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../malloc.cxx at line: 213 : malloc() - incorrect size - not a positive value. An LDAP connection to an LDAP server can be shared by multiple threads. When there is an intermittent network connection or a significant delay in receiving LDAP responses, the LDAP connection may start to shut down. The panic occurred when another thread was accessing an LDAP connection while it was in the process of shutting down.

Fix The code was updated to prevent the panic when a thread is trying to access the LDAP connection that is in process of shutting down.




Symptom Description

When an LDAP connection attempt failed, the error message in the server log indicated "...using SSL" regardless of whether SSL was enabled or not.

Fix The error message in the server log now indicates "...using SSL" only when SSL is enabled.



Version 5.6.42.5

UFS The following entries describe fixed UNIX File System issues:


Symptom Description

User reported slow CIFS user connection performance when using LDAP in environments with big directories (more than 10,000 users and groups). This problem occurred because of a lengthy method of encoding LDAP search requests on a Data Mover.

Fix The method of encoding LDAP search requests was changed to greatly improve the connection performance. The fix also resolves a lock issue in LDAP cache that caused delays of up to 10 seconds for each deadlock (that could occur if the same entry was queried more than once simultaneously).




Symptom Description

When doing a CIFS query on a checkpoint directory named .ckpt, if a file in that directory had a M83 name that was NULL, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 737863 Err code: 2 Target addr: 0 **. The stack trace showed: 0x1cbbee4: 0x13eec4 waitForReboot+0x90 0x1cbbf04: 0x13f0c1 fault_dump+0x67 0x1cbbf24: 0x1387a0 handle_fatal_fault+0xa 0x1cbc0c0: 0xaf4bb2

_ZN8AppLibNT11getMatchEntEP15ShadowDirectoryPtS 0xb8bbbc90: 0xa32039

_ZN11smb_Context9nextEntryEP15smb_TransManageR 0xb8bbbdb0: 0xa39231 _ZN19smb_Trans2FindFirst7doFirstEv+0x201 0xb8bbbe20: 0xa38a40

_ZN13smb_threadCtx19callTrans2FindFirstEP4msgb 0xb8bbbe50: 0xa483f4

_ZN13smb_threadCtx10execTrans2EP4msgbPcS2_+0x1

Fix The fix was to add a test for a NULL m83name before assigning a value to it.




Version 5.6.42.5

:


Symptom Description

If a file system's gid_map file was larger than 256KB, the file system was not mounted after a Data Mover reboot, and entries similar to the following were seen in the server_log:2008-06-10 10:27:54: 26042433536: UFS: 6: starting gid map

file processing.2008-06-10 10:27:54: 150596485127: UFS: 3: checkGidMapFile:

Fsid 172: Incorrect size 524288 for gid_map file.2008-06-10 10:27:54: 150596485133: UFS: 3: Fsid 172: Gidmap

file and its backup are corrupted or missing.2008-06-10 10:27:54: 13157531648: UFS: 3: initFS failed:

GidMap on fs 172 returned status InternalError2008-06-10 10:27:54: 86171975688: UFS: 4: 8: File system 172

will remain un-mounted due to GID Map corruption

Fix This issue has been fixed; the code now truncates the gid_map files to 256K and continues to mount the file system.




Symptom Description

When file system extend and checkpoint refresh operations were run in parallel, the Data Mover panicked with the following DART panic/fault message: finishTake: bad magic in CG The stack trace showed:0xc48fd710: 0x13e6c4 waitForReboot+0x90 0xc48fd730: 0x13e8c1 fault_dump+0x67 0xc48fd750: 0x13e7c1 PANIC+0x29 0xc48fd760: 0x68c5e6

_ZN14UFS_FileSystem28markCorruptedFsForUnmount 0xc48fd8e0: 0x69fab0 _ZN14UFS_CgBlkEntry10finishTakeEv+0x1f0 0xc48fd940: 0x6a08f0

_ZN14UFS_CgBlkEntry11preAllocBlkEP20UFS_Update 0xc48fd9a0: 0x694bc8

_ZN14UFS_FileSystem9hashallocEP20UFS_UpdateDes 0xc48fd9e0: 0x6947cc

_ZN14UFS_FileSystem8allocBlkEP20UFS_UpdateDesc

Fix We have synchronized the file system extend and checkpoint refresh operations to prevent this panic.



Version 5.6.42.5


Symptom Description

The sequence of the file systems in the mount file allowed a file system to be mounted on an NMFS file system before the NMFS file system was mounted. When the NMFS file system was mounted after its component file systems, the Data Mover panicked since the mountpoint inode was already in use. VFS_Vnode::release - releasing pinned node

Fix If this situation is detected, the Data Mover now rejects the mount of the NMFS file system and the user file system will remain mounted. The condition can be avoided by ensuring the NMFS file system is mounted before any of it's nested file systems.




Symptom Description

If a file system's gid_map file was larger than 256KB, the file system was not mounted after a Data Mover reboot, and entries similar to the following were seen in the server_log:2008-06-10 10:27:54: 26042433536: UFS: 6: starting gid map

file processing.2008-06-10 10:27:54: 150596485127: UFS: 3: checkGidMapFile:

Fsid 172: Incorrect size 524288 for gid_map file.2008-06-10 10:27:54: 150596485133: UFS: 3: Fsid 172: Gidmap

file and its backup are corrupted or missing.2008-06-10 10:27:54: 13157531648: UFS: 3: initFS failed:

GidMap on fs 172 returned status InternalError2008-06-10 10:27:54: 86171975688: UFS: 4: 8: File system 172

will remain un-mounted due to GID Map corruption

Fix This issue has been fixed; the code now truncates the gid_map files to 256K and continues to mount the file system.




Version 5.6.41.2

Version 5.6.41.2



Symptom Description

Certain kind of corruption to the system files, such as asyncDB and ACL database files, could result in FSCK aborting, leaving the file system inconsistent and unmountable.

Fix FSCK will make the asyncDB and ACL database files consistent to the point where FSCK can complete and the file system can be mounted. This does not mean that FSCK is fixing those files or recovering lost data from those files, but it will bring the file system to a point where any recoverable data can be accessed.




Symptom Description

When trying to rename a symbolic link from a CIFS client, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 73bec0 Err code: 0 Target addr: 9 **. The stack trace showed: 0x1cdfc74: 0x13f158 waitForReboot+0x900x1cdfc94: 0x13f355 fault_dump+0x670x1cdfcb4: 0x138a34 handle_fatal_fault+0xa0x1cdfe50: 0xaf92e8

_ZN8AppLibNT11getMatchEntEP15ShadowDirectoryPtS0xb884fd20: 0xaf61f4

_ZN8AppLibNT6renameEPtS0_iR11File_StatusR10ext0xb884fed0: 0xa394e8

_ZN13smb_threadCtx11replyRenameEP4msgb+0x11c0xb884ff40: 0x9c00e1 _ZN13smb_threadCtx7processEP4msgbi+0xc510xb884ffa0: 0x9b510c _ZN13smb_threadCtx5startEv+0x644The panic occurred because the code was trying to access a non-initialized value (null pointer).

Fix The code now checks the variable to see whether or not it was initialized before trying to access it, therefore preventing the panic.




Version 5.6.41.2



Symptom Description

The Data Mover panicked with the following panic message: DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 9c6583 Err code: 0 Target addr: 10 **. The panic occurred because of mal-formed data in CIFS session set up request. The problem only occurred when using non-Microsoft client that sends empty ImPassword during NTLM authentication.

Fix The code was changed to prevent the panic when CIFS session set up request is mal-formed, and return logon failure response.




Symptom Description

CIFS clients issuing a NetShareGetInfo call (AS400 systems for instance) were unable to connect to shares.

Fix The NetShareGetInfo request is now properly handled and clients can connect to shares.




Symptom Description

When using the server_export command to export a path, the command failed with the following message, but the path was exported successfully: Execution failed: Segmentation fault: Operating system signal. [STRING.append]. This happened when trying to export a path which was a symbolic link to a file system. This failure occurred because the Control Station did not have a way to determine the file system ID from the export path.

Fix The code was changed to make the file system ID optional. When exporting a path represented by a symbolic link, the command will now succeed without a file system ID value.




Version 5.6.41.2

CSA The following entries describe fixed problems related to the Celerra Startup Assistant:


Symptom Description

When all Data Movers were primary type (no standby Data Mover assigned yet), user could succesufully enable UNICODE on server_2, but when user tried to enable UNICODE on server_3, a message stated that UNICODE was enabled. However when user refreshed the page or navigated into the Data Mover properties page, he observed that UNICODE was not enabled on server_3.

Fix In fresh installs, reordered the internationalization setup code to occur when all Data Movers are of type NAS and before the standby Data Mover is assigned. Upgrades are unaffected. Also, added code to create the /.etc_common Data Mover directory whenever the setup_slot command is run except during installs.



Symptom Description

If a failure occurred during a CSA with the fibre connection checks, a generic error ERR 1000999999: "An unrecoverable management switch error has occurred". was being reported which provided little informative information.

Fix Check was enhanced to be more specific and print a more detailed error page that occurs when the fibre cable are incorrectly cabled. For example: ERR 1000021034: "Blade 2 Port BE 0 is not connected, but it should be connected to SP A I/O Module A0 Port 2 Fibre."



Symptom Description

The cable check portion of CSA was taking over a minute to complete.

Fix Additional enhancements were made to fibre cable checks to speed up these operations. These checks now perform about 30 seconds faster (depending on the configuration).



Version 5.6.41.2




Symptom Description

When performing an NDMP backup of the destination file system in a Replicator (v1 and v2) environment, backup may fail. NDMP backup creates an automatic checkpoint of the file system that is getting backed up. In this case, it failed to create a checkpoint on the Replication destination file system, because during the process of checkpoint creation, Replication service tried to freeze the file system.

Fix This problem was eliminated by fixing the file system reference mechanism in NDMP backup code. With the fix the Replication service will wait to freeze the file system until the checkpoint is created successfully.




Symptom Description

When many CRC errors were encountered on the destination during Replication V2 transfer, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 10bf2dd Err code: 2 Target addr: f4 **. The stack trace showed: 0x1cbc554: 0x13eec4 waitForReboot+0x900x1cbc574: 0x13f0c1 fault_dump+0x670x1cbc594: 0x1387a0 handle_fatal_fault+0xa0x1cbc5d0: 0x10bd5f7 _ZN12RcpTransport11closeStreamEv+0x410xfee99f30: 0xf09da7

_ZN16DpCopierReceiver15signalTransportEv+0x1810xfee99f50: 0xf098ed

_ZN40DpCopierReceiverRestartCleanupDeltaState10xfee99f70: 0xf086b4

_ZN16DpCopierReceiver11handleEventE22copierRec

Fix CRC errors detected by replication are now properly handled and the panic no longer occurs. CRC errors detected by replication are now properly handled to eliminate the panic. When the stream is closed due to an error it is done under a lock to eliminate a race condition.




Version 5.6.40.3

Version 5.6.40.3




Symptom Description

Once performance logging was activated, the logs should have displayed page IDs for each entry in the logs. Entries did not have page IDs in the performance logs. Example: Proper ID entry: [email protected] 1219828231305 pageID=1219823555481 pageClassName=navigationApplet event=end,navigation servlet

Improper ID - nonexistent: < [email protected] 1219828246508 pageID= pageClassName= event=start,wizard servlet command=list&object=capability&properties=capable&optionalArg=object=filesystem$action=new

Fix Code was modified to properly display the page ID for each entry in the log. The ID variable was not exclusive to the function displaying the IDs. The variable name was changed to a unique name and code paths were created exclusively for passing the ID to the proper attribute.



Symptom Description

User received inaccurate reports for NAS space usage for all his SavVols via StorageScope. The SavVol capacity was being calculated incorrectly. Jserver was not reporting checkpoints usage on a SavVol. Celerra’s XHMP Application Programming Interface (API) did not provide the SavVol numbers to ECC.

Fix A new property to report checkpoint SavVol usage in megabytes was added in Jserver response to report the checkpoint usage on SavVol via the API.




Version 5.6.40.3



Symptom Description

In Celerra Manager->Security->Administrators->Domain Settings, the test button was disabled after focus was shifted to the "Group Search Path" box. The only way to re-enable it is to refresh the screen. The problem was seen with most, if not all of the text boxes on the screen. This happened even when there were no changes made in the text boxes...all that it takes is for focus to shift to the text box. Until changes are made the Test button should be left enabled.

Fix Modified the GUI such that the test button now turns on and off correctly.



Symptom Description

The Control Center issues XML requests to Jserver for backend port information. Jserver returned incorrect port information which caused the Control Station configuration output to be incorrect.

Fix Jserver behavior was changed to receive the correct port number.



Symptom Description

During a virus outbreak where clients were repeatedly rewriting the same infected file, CIFS clients lost access. The deadlock was the result of the virus checker server trying to verify that the infected file was deleted but the same file was being rewritten in the meantime by another client.

Fix This scenario of an infected file being deleted and at the same time being rewritten is now handled correctly.




Version 5.6.40.3


Symptom Description

The gid_map file became out of sync or even corrupted when mounting a file system. This led to a Data Mover panic with the following panic string "Assertion failure: 'recNode != NULL' on line 1060 in file '../ufsacl.cxx'". The stack trace showed: 0x3e655a0: 0x13eec4 waitForReboot+0x900x3e655c0: 0x13f0c1 fault_dump+0x670x3e655e0: 0x13efc1 PANIC+0x290x3e655f0: 0x1a4d11 _assert+0x510x3e65610: 0x6bffee

_ZN9UFS_Vnode12doReleaseAclEP20UFS_UpdateDescri0x3e65680: 0x6bfe7b

_ZN9UFS_Vnode12doReleaseAclEP20UFS_UpdateDescri0x3e656c0: 0x71d088

_ZN20UFS_UpdateDescriptor8completeE11File_Statu0x3e65790: 0x693ae2

_ZN9UFS_Vnode8inactiveEPvi11File_Statusii+0x51a

Fix Defensive code was added to handle access to the ACL subsystem before the ACL subsystem is initialized more gracefully.




Symptom Description

The parameter cifs.acl.sortAce didn’t work in Windows 2000 and Windows 2003 environments. If this parameter was set; when viewing the security tab in the folder properties the user received the following popup: The permissions are incorrectly ordered which may cause some entries to be ineffective.

Fix The permissions are now correctly ordered, and a popup is no longer generated.




Version 5.6.40.3


Symptom Description

DFS could not be managed from a VISTA/Windows 2008 client MMC, only the command line could be used.

Fix DFS can now be managed with the MMC from a VISTA/Windows 2008 client.



Symptom Description

Under heaver load, some CEPA (Celerra Events Publishing Agent) events were incorrectly reported as "FAIL".

Fix Increased RPC timeout and put all post events synchronous to prevent this condition and ensure CEPA events are reported correctly.



Symptom Description

Interfaces which went off-line were not listed in the list of CIFS interfaces.

Fix CIFS is now able to list the interfaces including the off-line ones.




Symptom Description

Usermapper did not provide mappings for domain names that were not in the same case as the configuration file description.

Fix Code no longer requires domain names to be in the same case as the configuration file description.



Version 5.6.40.3


Symptom Description

The Data Mover queries the Windows domain controller using LDAP. By default, the messages are signed and require signature verification when the query response is received. The entire signed (or encrypted) query response must be in a single contiguous memory buffer, for signature verification or decryption. Normally, LDAP query responses are small, in the range of a few hundred to several thousand bytes. However, some domain configurations may result in query responses in the range of hundreds of thousands of bytes. If the Data Mover had been running for a long time (months), the system memory was fragmented to the point that a large contiguous memory buffer was not available, and the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../addrspac.cxx at line: 275 : Out of memory. The stack trace showed: 0xa8fe1e50: 0x13d664 waitForReboot+0x90; 0xa8fe1e70: 0x13d861 fault_dump+0x67; 0xa8fe1e90: 0x13d761 PANIC+0x29; 0xa8fe1ea0: 0x13953a

_ZN19Memory_AddressSpace10allocPagesEi12Memory; 0xa8fe1ec0: 0x1882fe _Z11more_memoryiP9free_list+0x4e; 0xa8fe1ee0: 0x1883b4 malloc+0x92; 0xa8fe1f10: 0x188af9 _Znwm+0x15; 0xa8fe1f20: 0x188b26 _Znam+0xc

Fix The LDAP message processing code has been updated to use memory allocation calls that fail gracefully (i.e., not panic the system), if there is not enough contiguous memory available at the moment it is requested.




Symptom Description

Usermapper rejected user/group/domain names longer than 256 bytes. This caused issues when Unicode names were translated into UTF8.

Fix Code now allows mapping user/group/domain names larger than 256 bytes. User/group names and domains strings sent to Usermapper can not be longer than 256 characters, or 1536 bytes.




Version 5.6.40.3


Symptom Description

When a file with no DACL (Discretionary Access Control List) had its owner changed using a UNIX client, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 6272a4 Err code: 0 Target addr: 4 **.

The stack trace showed: 0x1cdfa74: 0x13f158 waitForReboot+0x900x1cdfa94: 0x13f355 fault_dump+0x670x1cdfab4: 0x138a34 handle_fatal_fault+0xa0x1cdfb70: 0x5fa435

_ZN15File_NamingNode7setAttrEP5vattrP17Access_C0xc97afdb0: 0x57b139

_ZN16worldAccess_List16printWorldAccessEP9secF0xc97afee0: 0x57853c _ZN17nfs_serverInitial5startEv+0xac20xc97affe0: 0x1438d8 Sthread_startThread_internal+0xeA file could have no DACL due to the use of the utility emcsetsd with the remove option.

Fix When changing the owner of a file, the DACL is now verified to be present before it is used.




Symptom Description

When the tree quota path was more than 255 characters long, the Data Mover panicked with the following DART panic/fault message: Assertion failure: 'h->magic == MagicInUse' on line 343 in file '../malloc.cxx' >>PANIC in file: ../assert.c at line: 26 : assert failed. The stack trace showed: 0xa3c0b380: 0x146e88 waitForReboot+0x90 0xa3c0b3a0: 0x14709b fault_dump+0x67 0xa3c0b3c0: 0x146f85 PANIC+0x29 0xa3c0b3d0: 0x1de279 _assert+0x51 0xa3c0b3f0: 0x1d9d14 free+0x4e 0xa3c0b430: 0x1db30c _ZdlPv+0x10 0xa3c0b440: 0x7d342e

_Z17File_QuotaControlR6OptionP18VFS_FileSystem 0xa3c0bc50: 0x7da873 _ZN12filecmd_desc6invokeER6Option+0x6d

Fix This was a buffer overflow issue. Increased the buffer size to 1024, i.e. File_MaxPathNameLength, and check the maximum length to prevent this condition.



Version 5.6.40.3


Symptom Description

Using Celerra Management Snap-In (MMC) to query the CIFS Server and having machine account password age enabled on Celerra Data Mover resulted in a Data Mover panic with: DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 19ec3f Err code: 0 Target addr: 5a **. The stack trace showed: 0x1cac2e4: 0x13e6c4 waitForReboot+0x90 0x1cac304: 0x13e8c1 fault_dump+0x67 0x1cac324: 0x138798 handle_fatal_fault+0xa 0x1cac3a0: 0x19d012

_ZN18Stdio_AbstractFile7vprintfEPKcPc+0x1a 0xe0635d80: 0x1e7b09

_ZN16logObject_Memory7logvmsgE11logFacility11l 0xe0635db0: 0x1adb29 _ZN13logObject_XML5replyEPKcz+0x63 0xe0635de0: 0xb6ce3f

_Z20get_gpo_server_entryP13logObject_XML+0x38b This occurred because an incorrect format for account password age was used in GPO query.

Fix Code has been fixed to use integer instead of a string format in GPO query preventing the issue.




Symptom Description

When running the server_ldap command, if SSL-specific options (e.g., enable/disable SSL, set or clear the persona or cipher list) were used by themselves (e.g., with only the domain specified), the configuration was not updated.

Fix The code has been changed so that any SSL-specific option will result in the LDAP service configuration being updated.



Symptom Description

In a non-English Windows environment, the GPO was not updated because the CIFS client couldn't connect using full unicode names (In this case Japanese).

Fix The CIFS client now support connection using full unicode user name and GPO updates successfully.



Version 5.6.40.3


Symptom Description

When the root file system of a VDM was too big (more than 2 TB), some Data Mover services that use root file system failed with a message similar to the following in the server_log: Cannot get or create Mapping table (No space left on device ).These errors also appeared during an upgrade to 5.6 and prevented upgrade from continuing. The problem was that some Data Mover services check root file system size before writing to it, and a 32 bit variable was used for the size. When VDM file system was bigger than 2 TB, the 32 bit variable was overflowing and therefore reporting incorrect file system size.

Fix The code was changed to correctly report VDM root file system size.




Symptom Description

Under very infrequent condition, user experienced a CIFS outage after attempting to create a server or moving an interface from one server to another. This could happen when using Celerra Manager or running server_cifs commands.

Fix This was due to a race condition causing a deadlock. This condition has been fixed.




Symptom Description

A file system crossed a threshold value, data was then deleted so that the file system threshold dropped. A threshold dropped message was displayed, but it had a severity of "WARNING".

Fix A severity of INFO is now displayed with threshold dropped messages.



Version 5.6.40.3



Symptom Description

When two network interfaces on the Data Mover were in the same subnet, and the VLAN id of one of them was changed, users lost network access to the Data Mover. The problem was that there should not be two interfaces in the same subnet with different nonzero VLAN id.

Fix Validation checks are now performed when user tries to set a non-zero VLAN id, and the command will now fail. VLAN id set must match that of other interfaces in the same subnet.




Symptom Description

If more than 64 routes were configured using the server_date command, the server_route –list command showed only 64 entries and truncated the rest without notifying the user. Depending on the order, it may have truncated the output for the default gateway. This happened because of the response size limit in communication protocol that was used by the server_route command.

Fix The code was changed to return a warning message whenever route table entries are truncated by the server_route –list command. Alternatively, the server_netstat –r command can be used to display all entries.




Symptom Description

After extending a file system which was replicated with Replication V2, the destination side did not automatically extend. This occurred because code was checking the available pool size instead of the extend size.

Fix The fix ensures that the destination Celerra is checking that the specified pool has enough space to satisfy the extension size, rather than the new total size of the file system.




Version 5.6.40.3


Symptom Description

When adding new disks to Celerra, the server_devconfig –c –s –d command failed with the following message: Execution failed: new_cluster: Routine failure. [NAS_META_ITEM.register_cluster]

This issue occurred when LUN migration was performed, and that LUN consisted of two disks belonging to two different pools, and had a file system built on top, and the migration was performed into a new pool, different than the original two. Because the disks were in 2 different pools, two transactions were performed during the migration process resulting in incorrect entries in the NAS database, and therefore server_devconfig command failure.

Fix The code was changed to handle correctly the migration process.




Symptom Description

The server_vtlu command failed when run against a standby Data Mover. The following error was generated:SVTL: 3: mkDir(/svtl/locks/libraries) failed: IO_ErrorSVTL: 3: SvtlServer() -->

pTlusMutex->Init(/svtl/locks/libraries) SVTL_STATUS_ERRORSVTL: 4: SvtlServer::Alloc(): SVTL_STATUS_ERRORSVTL: 3: Command failed: tlusInfo The server_vtlu command should not be allowed to run on the standby Data Mover.

Fix The server_vtlu command is blocked on standby servers. The command server_vtlu ALL now omits standby servers from the servers list.




Version 5.6.40.3

CORE The following entries describe fixed problems related to Celerra Data Movers:


Symptom Description

1. While converting a Data Mover from type standby to type NAS, user may see a message "Failed to apply unicode fonts"

2. While doing a fresh install of version 5.6.36.0, if one of the Data Movers was up and running in min boot.cfg mode, the following message was displayed "Failed to copy files into /.etc_common/xlt subdirectory"

Fix A fresh install of version 5.6.40 or above will no longer display these error messages. Also, the conversion of Data Mover from type standby to NAS will now succeed.



Symptom Description

Running a custom script to collect Data Mover statistics caused Data Mover to panic with the following DART panic/fault message: >>PANIC in file: ../sched.cxx at line: 822 : SYSTEM WATCHDOG. The stack trace showed: 0x3655f34: 0x13d1e0 waitForReboot+0x900x3655f54: 0x13d3e9 fault_dump+0x670x3655f74: 0x13d2e9 PANIC+0x2b0x3655f84: 0x13ee0c system_watchdog+0x7c0x3655f94: 0x137279 _t_nmi+0x630x3655fe0: 0x1406f8 Sthread_startThread_internal+0xe

Fix Watchdog panic occurred due to corruption in the mblk where the mblk was pointing to itself. To avoid this panic, all debug log messages in the PCI error path have been removed.




Version 5.6.40.3


Symptom Description

When using iSCSI or 10GB interfaces using jumbo frames, a Data Mover panicked with one of the following types of exceptions : Memory corrupt or Invalid Opcode.

Fix Corrected the reclaim_space algorithm to insure logical contiguous memory region are mapped to physical contiguous memory regions to prevent this panic.




Symptom Description

When using NMFS and unmounting one of the underlying file systems, a race condition occurred with the following panic: NMFS_FileSystem::getMountPointNodes() NMFS_FileSystem::getMountPointNodes() { DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: f96533 Err code: 0 Target addr: 4 **. The stack trace showed: 0x1ca90b4: 0x13e694 waitForReboot+0x90 0x1ca90d4: 0x13e891 fault_dump+0x67 0x1ca90f4: 0x138768 handle_fatal_fault+0xa 0x1ca9150: 0xf957c4

_ZN15NMFS_FileSystem7getStatEP6statfsP17Access_ 0xc6783ad0: 0x5f4b04

_ZN15File_NamingNode9getFSStatEP6statfsP17Acce 0xc6783af0: 0x65ab08 _Z12mac_getStatsPcPyS0_S0_i+0xc8 0xc6783bb0: 0x22f45a

_Z10mac_df_allRP13ncStringArrayS1_RP7ncArrayIy 0xc6783c50: 0x2300b9 _Z12xml_df_tableP7macData+0x169

Fix Code has been fixed to prevent this race condition and eliminate this Data Mover panic.



Version 5.6.40.3



Symptom Description

Concurrent accesses to the same file where one client brings a file online through a write operation while another reads the same file (or tries to write) created a condition where a Data Mover hung or appeared to hang because it was progressing very slowly. The following messages indicated that services had stalled for a time. Later the messages started over, indicating that the condition cleared and then reappeared.ThreadsServicesSupervisor: Service:NFSD Pool:NFSD_Exec PENDING

for 238 secondsThreadsServicesSupervisor: Service:NFSD Pool:NFSD_Exec PENDING


for 358 secondsThreadsServicesSupervisor: Service:NFSD Pool:NFSD_Exec BLOCKED

for 418 seconds: Server operations may be impacted ThreadsServicesSupervisor: Service:NFSD Pool:NFSD_Exec PENDING



for 181 secondsThreadsServicesSupervisor: Service:NFSD Pool:NFSD_Exec BLOCKED

for 360 seconds: Server operations may be impacted ThreadsServicesSupervisor: Service:CIFS Pool:SMB PENDING for

268 secondsThreadsServicesSupervisor: Service:CIFS Pool:SMB PENDING for

328 secondsThreadsServicesSupervisor: Service:CIFS Pool:SMB BLOCKED for

388 seconds: Server operations may be impacted ThreadsServicesSupervisor: Service:NFSD Pool:NFSD_Exec BLOCKED

for 1259 seconds: Server operations may be impacted ThreadsServicesSupervisor: Service:CIFS Pool:SMB BLOCKED for

1288 seconds: Server operations may be impacted

Fix This locking issue caused by a race condition when an offline file is transitioning to online has been fixed.




Version 5.6.40.3


Symptom Description

MacCom class uses a HashMap to store macAddresses and its corresponding IpConfigObject found after the mac search. But this map was not cleared before every search, initiated by the user clicking the retry button. Hence the old values were retained and getting populated in the combobox even after the machine was disconnected from the subnet.

Fix MAC Addresses for system no longer connected are not shown in the drop down box after they are disconnected.



Symptom Description

When using NAS 5.6.39 or later, during CSA installation, the MAC address field was populated with the first discovered Control Station address. Code did not check if the CSA and NAS versions were compatible and enabled the "Next" button which allowed the installation to continue. The check for CSA and NAS compatibility was running only upon selecting the MAC address from the list.

Fix Code has been fixed to first check that MAC address(es) are available and then checks for compatibility and enable/disable the "Next" button, preventing the issue.



Symptom Description

The prompts on the Celerra Startup Assistant (CSA) Initialization screen which allows default passwords to be changed on the Control Station and on the backend array was misleading. The prompt stated: Control Station password. However, when changing the password for nasadmin on the CSA configuration screen for the Control Station, this not only affected the Control Station but also the storage array's security account.

Fix Wording was changed from Control Station password to Control Station password (will also be used for array).



Version 5.6.40.3



Symptom Description

When a FileMover connection was lost, RPC requests were not delivered due to the lost connection and the following messages were logged in the server logs: KERNEL:3:1 Slot 8: 1199293713: ThreadsServicesSupervisor: Service:CIFS Pool:SMB PENDING for 204 seconds: Server operations may be impacted

Fix This was due to the TCP queue getting full and not sending the requests. RPC client code now handles TCP flow control issues correctly.




Symptom Description

When an attempt was made by FileMover/DHSM to get the attributes of a symlink using the CIFS path, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 735256 Err code: 0 Target addr: 9 **. The stack trace showed: 0x1cbbfe4: 0x13eec4 waitForReboot+0x900x1cbc004: 0x13f0c1 fault_dump+0x670x1cbc024: 0x1387a0 handle_fatal_fault+0xa0x1cbc0d0: 0x736ee1

_ZN26passthroughShadowDirectory10lookupFileEPtm0xb9b31b10: 0x23c73b

_Z12dhsm_get_fnnP13logObject_XMLPcS1_R11File_S0xb9b31c40: 0x23d6b7

_Z18dhsm_xml_get_attrsP10DHSM_replyP14XmlEleme0xb9b31da0: 0x23e78b

_Z15dhsm_XMLHandlerP13logObject_XMLPKcP4msgb+00xb9b31dd0: 0x11303a5

_ZN13XmlHandler_DB6invokeEPKcP13logObject_XML

Fix Symlinks are now correctly handled when encountered in a CIFS path by FileMover/DHSM.




Version 5.6.40.3


Symptom Description

When the FileMover/DHSM secondary server was no longer available and accesses were made which required offline files, CIFS clients lost access. The server log showed messages like: ThreadsServicesSupervisor: Service:CIFS Pool:SMB BLOCKED for 5034 seconds: Server operations may be impacted.

Fix When the secondary server is not available, attempts to reconnect to it will no longer tie up threads for long periods of time.




Symptom Description

During CDMS migration or FileMover recall, if the file system had millions of inodes, memory utilization grew to the point where the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../addrspac.cxx at line: 275 : Out of memory. The stack trace showed: 0xd8bfd700: 0x13d1e0 waitForReboot+0x90 0xd8bfd720: 0x13d3e9 fault_dump+0x67 0xd8bfd740: 0x13d2e9 PANIC+0x2b 0xd8bfd750: 0x13918c

_ZN19Memory_AddressSpace10allocPagesEi12Memory 0xd8bfd770: 0x1879ea _Z11more_memoryiP9free_list+0x4e 0xd8bfd790: 0x187a97 malloc+0x89 0xd8bfd7c0: 0x3a98dc xdr_bytes+0x62 0xd8bfd7e0: 0xb95b6e

_Z14xdr_READ3resokP4XDR_P10READ3resok+0x70

Fix Code was updated to be less memory intensive during the file system walk operation during CDMS migration or FileMover recall.




Version 5.6.40.3




Symptom Description

When using FileMover in passthrough mode, performance was slower than when using full mode. For a recall of 150MB, it took 14 minutes in passthrough mode and only 2 minutes in full mode.

Fix Passthrough mode was using an 8K read size. This has been fixed to now use 32K read size, which is the same as full mode.




Symptom Description

If a file system full condition occurred during an upgrade from version 5.4 to 5.5, iSCSI LUN corruption occurred. All file systems that contain iSCSI LUNs need at least 100MB of free disk space for the upgrade to complete successfully.

Fix A new PUHC (Pre Upgrade Health Check) has been created to detect this condition and prevent upgrades from continuing and generate the following ERROR level message if the check fails. File system <name> with iSCSI LUN(s) has less than 100 MB of free space; it has <available_space> bytes of free space. The iSCSI conversion process requires that a new directory is created for each iSCSI LUN, and a new hard link is created in each directory. You must have at least 100 MB of free space to upgrade. For more information, search the Knowledgebase on Powerlink as follows:1. Log in to http://powerlink.emc.com and go to Support > Knowledgebase Search > Support Solutions

Search.2. Use ID emc141515 to search




Version 5.6.40.3


Symptom Description

The nas_halt command did not do a complete Control Station shutdown.

Fix Added -p (power off) and -I (bring down interface) flags to the nas_halt command to ensure the Control Station shuts down completely. The EMC Celerra Network Server System Operations technical module, P/N 300-004-161, provides detailed information about the shut down procedure and is available on Powerlink.




Symptom Description

Setup_clariion reported the error “disk::get_disk_technology, no disk argument supplied” when encountering a DAE (disk array enclosure) with no disks installed.

Fix Setup_clariion will now identify the enclosure as invalid for configuring and will skip it.



Symptom Description

Dialhome did not work if the environment required a dialout prefix which included * or #.

Fix Dialout prefix containing * and # can now be used in the phone number.




Version 5.6.40.3


Symptom Description

When running version 5.6.38 or higher, the statistic monitor service did not run on the standby server. If the primary server failed over, this service did not start on the newly-appointed primary server after failover. This prevented statistical information from being generated for the server.

Fix The statistic monitoring service will now run on the standby server at all times. So if the primary server should failover, it will already be started.



Symptom Description

For NX4 systems, an alert message generated by “CLARiiON SFP removal” did not indicate which SP (A/B).

Fix Added SPA/SPB to the error message.



Symptom Description

During an upgrade, Celerra service enabler task prompts user whether or not to install the Celerra service. If user answered no to this prompt, the upgrade did not continue.

Fix The prompt "The requested package(s) will be installed. Do you wish to proceed? : (y/n)?" is no longer displayed.



Symptom Description

PUHC (Pre Upgrade Health Check) showed results as PASS or FAIL when some FAILs were really warnings or info items. These FAIL levels can be misleading, some should appear as warnings or info.

Fix Nas_checkup now returns WARN or INFO instead of FAIL when a warning or information level check fails. This clearly separates the issues that need to be fixed from those that are just advisory or proactive.



Version 5.6.40.3




Symptom Description

iSCSI replication sessions went inactive intermittently when in use with RM/SE. Messages similar to the following were seen in /nas/log/sys_log:DPSVC:4:6 Slot 2: 1191483866: DpPolicy for id:fs26_T1_LUN0 _CK200063400108_0000_fs52_T8_LUN0_ CK200063600110_0000 has become inactive, status:DpRequest_vs_BusyThe nas_replicate –i output showed messages similar to: replicationdestination: dst_target_name = iqn.1992-05.com.emc :ck2000636001100000-9 dst_LUN_number = 0 name = fs53_T9_LUN0_ CK200063600110_0000 playback_state = WaitingForRequest

Fix A new error code is returned to RM/SE, so that the application knows to alert the user that the replication failure is caused by destination file system out of disk space, and once the problem is fixed, RM/SE will recheck the replication status, and then resume replication session.




Symptom Description

When an MPFS client sent a request with a null NFS file handle, the Data Mover panicked with DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 64ee8a Err code: 0 Target addr: 0 **. The stack trace showed: 0x1cabc50: 0x13e6c4 waitForReboot+0x900x1cabc70: 0x13e8c1 fault_dump+0x670x1cabc90: 0x138798 handle_fatal_fault+0xa0x1cabcc0: 0x64ef65

_ZN14VFS_FileSystem12fsFromHandleERK11File_Hand0xe2dd16a0: 0x5f334d

_ZN15File_NamingNode14nodeFromHandleEPK11File_0xe2dd16e0: 0x7929a4

_Z8fhsToFnnP13fileHandleSrcP7svc_reqRP15File_N0xe2dd18a0: 0x78ccd1

_Z10fmp_open_3P8openArgsP7svc_reqPP11FreeResul

Fix When a null NFS file handle is encountered, the panic will not happen and a message will be logged in the server log.




Version 5.6.40.3


Network The following entries describe fixed Network-related issues:


Symptom Description

When performing a 3-way NDMP restore of a top level directory that contained hard links to an alternate location, the following error message was displayed in the server_log: NDMP: 4: Unable to link /fs1/dir1/hardlinks/link1 to /restore/dir1/plainfile . No such file or directory .The problem occurred because of an incorrect interpretation of the destination file path by the Data Mover.

Fix The code was changed to interpret the destination file restore path correctly, so the hard link will be created successfully.



Symptom Description

When using some Data Management Applications (DMA), for example, Oracle Secure Backup 10.2, to perform NDMP restore to an alternate location, if the destination path was at top level, the restore failed. The server_log displayed the error: Permission denied to restore on Root fs. The problem occurred because of incorrect interpretation of the requested destination path by the Data Mover from some DMA applications.

Fix The code was changed to interpret the requested destination restore path correctly.



Symptom Description

Intermittent errors encountered by the 10Gb Neterion adapter were not properly handled by Celerra.

Fix The adapter driver for the 10Gb Neterion adapter now handles intermittent errors encountered on the adapter, and the data is now retransmitted.




Version 5.6.40.3


Symptom Description

When using SAP file adapter FTP client to query the Celerra via FTP, if trying to list files that didn't exist, the Celerra returned a "file*.**: No such file or directory" message. This was not compliant with RFC 959 which states nothing should be return if no files are present. The SAP client saw the "file*.**" message and thought this was a file it could download, causing it to fail.

Fix When doing a wild card search, if no entry is found, code now returns no data instead of an error.




Symptom Description

The Data Mover did not always send as much data as is permitted by the FACK (Fast Recovery) algorithm during TCP "fast recovery". This resulted in possibly unnecessary expiration of the TCP retransmission time-out interval or unnecessary delays until the generation of delayed acknowledgments by the Windows TCP implementation.

Fix Changed the TCP fast recovery code to resolve this issue.




Symptom Description

When using Data Movers with TCP-offload-engine (TOE) interfaces on a quiet and lossy network, the following device message was logged to syslog: slicNicDevice: TOE (aceX) panic detected. Saving TOE core image to '/slicdump'. Any TCP connections which were off-loaded to the TOE device at the time of the panic were lost and had to be re-established after the device was auto-restarted.

Fix Celerra's watchdog timeout for the TOE device was increased from 5 to 65 seconds. This allows the device time to finish its retries before determining whether it has a problem and needs to be reset.




Version 5.6.40.3



Symptom Description

CNS systems containing an Alacritech TOE (TCP Offload Engine) network controller could experience a system watchdog/panic when network workloads were large and system memory resources were scarce and heavily fragmented.

Fix The buffer replenish mechanism for the Alacritech TOE network device has been adjusted such that receive buffer replenishments are smaller and more frequent.




Symptom Description

When a 10 GB interface was stopped, the Data Mover panicked with the following DART panic/fault message: Assertion failure: 'db_ref > 0' on line 951 in file '../include/stream.hxx' >>PANIC in file: ../assert.c at line: 26 : assert failed. The stack trace showed: 0xbac69a60: 0x13d890 waitForReboot+0x900xbac69a80: 0x13da8d fault_dump+0x670xbac69aa0: 0x13d98d PANIC+0x290xac69ab0: 0x188c3d _assert+0x510xbac69ad0: 0x161128 _ZN5datab7freeRefEv+0x420xbac69af0: 0x259b62 _Z14s2io_card_downP8s2io_nic+0x1aa0xbac69b40: 0x252c46 _ZN13xenanicDevice4stopEPv+0xd20xbac69b70: 0x2531dc _Z12xena_commandR6Option+0x506

Fix Code now prevents the double free of a message during the stop process.




Version 5.6.40.3



Symptom Description

An ACL modified by a NFSV4 client using standard commands cannot be read by a Windows client. This was due to extra DENY ACE (Access Control Entries) added by the server when the ACL is read by the client.

Fix Code no longer generates an extra ACE when an ACL is read. ACL can now be handled by Windows and NFSV4 without any problems.




Symptom Description

When a file or directory was created in a directory with inheritable ACL, its ACL was inherited from the parent directory in NFSV3; but with NFSV4, an ACL was created from the mode bits. There was an inconsistency between NFSV4 and NFSV3 in the way the inheritance functionality was managed.

Fix Code has been fixed to ensure that inheritance for file systems mounted with mixed access policy in NFSV4 works in the same way as it does for NFSV3.




Symptom Description

Performing VBB backup of a checkpoint file system containing the socket type file(s) caused an inability to unmount and delete that checkpoint. This was due to the extra reference on the file system for each socket file which wasn't released upon backing up those files.

Fix Code was fixed to properly handle socket type files, eliminating the issue.




Version 5.6.40.3


Symptom Description

A delta number was not stamped on a checkpoint when the replication session was inactivated. The refresh_ckpt script wasn't handling the condition and after 2 cycles, refreshed both restart checkpoints so there was no longer a usable one.

Fix Refresh of well known checkpoints <fsname>_restart_1 and <fsname>_restart_2 is now rejected if a replication session is inactive.




Symptom Description

The Data Mover panicked during replication switchover/failover/reverse operation if a user issued the server_umount command on the replication file system. DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 1a7389 Err code: 0 Target addr: 0 **. The stack trace showed:0x1cbc29c: 0x13eec4 waitForReboot+0x900x1cbc2bc: 0x13f0c1 fault_dump+0x670x1cbc2dc: 0x1387a0 handle_fatal_fault+0xa0x1cbc300: 0x1a75c5 strdup+0xf0xc552dce0: 0x65049e

_ZN14VFS_FileSystem29doUnmountWithReplicationC0xc552dd10: 0x65d885 _Z17vfs_UnmountByFsidi+0x330xc552dd40: 0x21e7d7 _Z13macthr_umountP4msgb+0x26d0xc552dfa0: 0x20f982 _ZN11Mac_Initial5startEv+0x3e0

Fix The problem is fixed. User can issue the server_umount command on the replication file system while replication is running on the file system.



Symptom Description

When a destination replication received an abort request from an inactive state, it did not do restore on a destination file system which led to file system corruption on the destination file system .

Fix Modified the destination replication state machine to do restore when it gets an abort request from any state.



Version 5.6.40.3


Symptom Description

A Replication V2 create operation or reverse operation of a file system mounted on a VDM, with FileMover enabled, resulted in the following panic when a CIFS client attempts to connect to a share on the file system. DART panic/fault message: >>PANIC in file: ../vdm_thrd.cxx at line: 89 : Missing thread inheritance from vdm_thread. The stack trace showed: 0xb95f56c0: 0x13e6c4 waitForReboot+0x900xb95f56e0: 0x13e8c1 fault_dump+0x670xb95f5700: 0x13e7c1 PANIC+0x290xb95f5710: 0x20a1f2 _Z11isVdmThreadv+0x880xb95f5730: 0xb86a6d _ZN15SmbRemoteServer4sendEP4msgb+0x150xb95f5770: 0xb8504a _ZN6SmbMsg4sendEi+0x1e6

Fix The Data Mover no longer panics under this condition.



Symptom Description

A panic occurred when rebooting a Data Mover that had a file system whose newest checkpoint was created or refreshed with 5.6 code, while all the other checkpoints on that file system were created or last refreshed with 5.5 code. DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: dd6c67 Err code: 0 Target addr: 0 **. The stack trace showed: 0x1cbc4b4: 0x13eec4 waitForReboot+0x90 0x1cbc4d4: 0x13f0c1 fault_dump+0x67 0x1cbc4f4: 0x1387a0 handle_fatal_fault+0xa 0x1cbc540: 0xdbfe1d _ZN19PoolManagedDeltaVol23AllocDataBlockUpdateL 0xc3a7ff60: 0xdc660c _ZN19PoolManagedDeltaVol23AllocDataBlockUpdate 0xc3a7ff90: 0xdb1e52 _ZN19DeltaIO_SnapBase_CB8allocateEv+0x3a 0xc3a7ffb0: 0xde3379 _ZN21ckptBlockAllocatorThr5startEv+0x129 0xc3a7ffe0: 0x143644 Sthread_startThread_internal+0xe

Fix The issue happened when the newest checkpoint is a 5.6 checkpoint and the next checkpoint is a 5.5 checkpoint. The panic was fixed by correcting the chunk bitmap handling code which is used during the merge operation in these conditions.




Version 5.6.40.3


Symptom Description

On a heavily-loaded system with many replication sessions running, a race condition in handling the fs_replicate -refresh command internal network retry between the source and the destination caused the destination panic. DART panic message: Assertion failure: 'pSessCtx != __null' on line 1981 in file '../CmdRequestQueue.cxx' >>PANIC in file: ../assert.c at line: 26 : assert failed. The stack trace showed: 0x9f21dee0: 0x146b8c waitForReboot+0x900x9f21df00: 0x146d9f fault_dump+0x670x9f21df20: 0x146c89 PANIC+0x290x9f21df30: 0x1d2119 _assert+0x510x9f21df50: 0x1360c94 _ZN25CmdIntRequestQueueManager22AckUnregister0x9f21df80: 0x135ee75 _ZN20CmdEventRequestQueue11handleEventEv+0xcd0x9f21dfa0: 0x1912e7 _ZN17SvcThread_InitialIS_I15Sthread_InitialEE50x9f21dfe0: 0x14d3ec Sthread_startThread_internal+0xe

Fix Fixed a race condition in the replication internal network retry.



Symptom Description

While remounting a file system when a replication session was stopped, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 1e2bc1 Err code: 0 Target addr: 0 **. The stack trace showed: 0x2395d58: 0x146bf4 waitForReboot+0x90 0x2395d78: 0x146e07 fault_dump+0x67 0x2395d98: 0x13c5d4 handle_fatal_fault+0xa 0x2395dc0: 0x1290d15

_ZN9DpService22getReplicaStateAndTypeEPKcR10Re 0x959c3b30: 0x1291c7b

_ZN9DpService23IsFsMountRemountAllowedEPKcRi+ 0x959c3b90: 0x1291ac1

_ZN9DpService23IsFsMountRemountAllowedERK6Opt 0x959c3bc0: 0x7d984f

_Z23File_ServerMountCommandR6OptionP18VFS_File 0x959c3bf0: 0x7da1ff _ZN12filecmd_desc6invokeER6Option+0x6d

Fix Modified replication code to add NULL pointer check when remounting a file system to ensure it remounts successfully.



Version 5.6.40.3


Symptom Description

Fields in Celerra Manager containing information about the rates of network transfer pertaining to Data Mover interconnects were mislabeled.

Fix Labels reporting units of measurement on the network transfer rates of Data Mover interconnects in Celerra Manager have been corrected. KB/sec was replaced with Kb/sec.



Symptom Description

While trying to upgrade to version 5.6.37.6 or later using the CD-ROM, the upgrade failed due to running tasks reported by PUHC (Pre Upgrade Health Check). However, when user tried to abort and delete any of the running tasks using the nas_task -delete command, the following error was generated: Error 13160415238: The request is not supported. User then tried rebooting the Data Movers and the Control Station to get by this issue, but the reboots did not alleviate the PUHC errors.

Fix Previously, there is no way to abort a Delete task for loopback replication. With this change, code accepts the abort (not normally accepted for local/remote repl) and moves forward just like local abort on the primary and secondary.



Symptom Description

The Data Mover panicked with header: >>PANIC in file: ../assert.c at line: 26 : assert failed. The panic occurred when file system replication was setup, but the data had not yet been copied to destination file system, and the nas_replicate -reverse command was executed. This happened because the common base had not yet been established between source and destination.

Fix The code was changed to successfully execute reverse command if destination side is empty and no common base is found.



Version 5.6.40.3


Symptom Description

When the Celerra was restarted after a controlled shutdown using the nas_halt command, the replication V1 sessions had to be restarted.

Fix The nas_halt command now makes sure that the replication sessions are properly handled so they will continue running after the system is back up without any intervention.




Symptom Description

The nas_task -info command displayed erroneous value for field of "Estimated End Time" as Wed Dec 31 19:00:00 EST 1969. This problem occurred because the code had not provided the Estimated End Time value resulting in the display of a default time.

Fix The code was changed to provide the correct value of Estimated End Time for the output of nas_task -info command.



Symptom Description

In replication v2, when a file system (with the name “pfs”, mounted on the VDM) was replicated (with the destination create option), the destination file system (with the name “pfs_replica1”) was mounted on mountpoint “/pfs_replica1” file system. When VDM was failed over in a CIFS environment, all the clients accessing the source file system (/pfs) were required to have the destination mount with the same mount path.

Fix In this scenario, the file system will be mounted on mountpoint “/pfs”. If such mountpoint is not available on the destination VDM, then replication create will fail.



Version 5.6.40.3


Symptom Description

The nas_copy –abort command hung when trying to perform a local abort of a file system copy from checkpoint. The command hung if the local abort was issued on the source side first. The problem was a deadlock in source replication service abort and destination local abort.

Fix The code was changed to avoid a deadlock when local abort is issued from source side first.




Symptom Description

Replication alias name was not displayed in the sys_log event message when a replication session that had been stopped or failed over was aborted.--------------------Command:nas_replicate -abort id=<session_id> [-local]

Sys_log event message:RepSessionName=fs23_T18_LUN147_000190100583_0080_fs28_T5_LUN176_000190100485_0070(alias=), DpRequest_Replica_Abort ok.) ----------------------

Fix Code now gets the alias name from the replication config signature if the session is stopped and displays the alias in the sys_log messages.



Symptom Description

The events/alerts which are posted by the scheduler of a replication session did not contain any session names.

Fix Scheduler will now query replica to get session alias name by session ID and include the name when it posts an alert/event.



Version 5.6.40.3

Security The following entries describe fixed issues related to security:

SRDF The following entries describe fixed issues pertaining to Symmetrix Remote Data Facility:


Symptom Description

During file system extension, a checkpoint refresh/create request failed. In this particular case, user had four replications created for four 4TB file systems that were being filled by an external VJTREE process from a Solaris client. The source file systems had auto-extension enabled with a HWM of 50%.

Fix Modified the scheduler state machine to retry refreshing a checkpoint during file system extension.



Symptom Description

Performing security vulnerability scans revealed that FTP on a Data Mover was vulnerable to FTP bounce attack even when ftpd.bounceAttackChk parameter to was set to 1 (protecting FTP on Data Movers from FTP bounce attacks). This issue occurred only when anonymous FTP was enabled on the Data Mover.

Fix The code has been fixed to secure Data Mover from FTP bounce attacks even when anonymous FTP is enabled on Data Mover eliminating the vulnerability.




Symptom Description

RDF failover was successful, but RDF failback failed as a result of the RDF script trying to failback the device group twice. CRITICAL FAULT: SRDF restore failed for 1R2_500_1.

Fix The nas_rdf -restore process will now continue without this error.




Version 5.6.40.3


Symptom Description

A nas_rdf -restore operation failed because the R2 device group being failed back was already in the failed back state. An error in the nas_rdf script caused the Control Station to issue the symcli failback command twice against the same device group. The failure of the second instance of the command resulted in the overall nas_rdf script failing.

Fix The fix ensures that the script is running commands against unique instances of device groups.




Symptom Description

When the command nas_rdf -init was run on the source of an active-passive RDF configuration, the discovery of remote control volumes were identified by polling all SCSI chains of the Data Mover. If there are devices available at address 0/9 (or 0/6) on non-boot chains, "nas_rdf -init" was failing with the following: CRITICAL FAULT: Unable to start nbs device for /dev/ndj1 /dev/ndg1. Please ensure remote Nas software has installed, R2 volumes are synchronized, stop and re-start nbs device for /dev/ndj1 /dev/ndg1 before the nas_rdf -init is run.

Fix Code will now probe only SCSI boot chains, eliminating the polling of data volume chains.




Symptom Description

When performing SRDF activate or restore, the Data Mover failover failed with the following error message in server_log: DPSVC: 6: DpInit::initDatabase() failed:9 to be initialize. The failover failed because dpinit service on standby Data Mover was started during the RDF activate process and tried to access the root file system, which was not mounted on standby Data Mover.

Fix Code was modified to not start dpinit service on RDF standby Data Mover to prevent this condition.



Version 5.6.40.3

Storage The following entries describe storage-related fixed issues:


Symptom Description

On a Celerra system connected to a Symmetrix backend, after a Non-Destructive Upgrade of the Symm backend, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../BVolumeIrp.cxx at line: 323 : IO failure on Vol:206, blkNo:3528992, SKey:0x629. The stack trace showed: 0x3887e80: 0x13d890 waitForReboot+0x90 0x3887ea0: 0x13da8d fault_dump+0x67 0x3887ec0: 0x13d98d PANIC+0x29 0x3887ed0: 0x779edf

_ZN8SgIO_IRP9irpFailedE14BlockIO_Statusy+0x30f 0x3887f20: 0x80eb86

_ZN14CamDisk_Device8completeEP10ccb_header+0xe6 0x3887f70: 0x78d69a _ZN8Scsi_Xpt16processCallbacksEv+0x3c2 0x3887fd0: 0x78d6d2 _ZN18Scsi_serverInitial5startEv+0x6 0x3887fe0: 0x14105c Sthread_startThread_internal+0xe

Fix This problem was due to the 90 second default time out the Data Mover had before trying I/O to a Symm backend. This timeout was not giving the Symm backend enough time to stabilize. The fix increases the default timeout from 90 to 240 seconds.




Symptom Description

During a user I/O to a file system or a system I/O to one of the command LUNs, the Data Mover panicked with the following DART panic/fault message: >>PANIC: I/O not progressing LastVol touched NBS5 Kind 0 (ptr=0xdbbccc04). The stack trace showed: 0xdba85e90: 0x13e6c4 waitForReboot+0x900xdba85eb0: 0x13e8c1 fault_dump+0x670xdba85ed0: 0x13e7c1 PANIC+0x290xdba85ee0: 0x79908c _ZN9RawIO_IRP13checkProgressEv+0x11a0xdba85fd0: 0x798f68 _ZN17IrpProgressThread5startEv+0x60xdba85fe0: 0x142e6c Sthread_startThread_internal+0xe

Fix The constructor for the TaskEntry class had an error that caused a sign extension that resulted in the entry having a timeout way into the future. This resulted in an I/O not progressing panic. The fix makes all the types consistent.




Version 5.6.40.3


Symptom Description

Unable to mange replication sessions when the Symm volume ID had 4 digits or the label was changed so it no longer matched the ID. The nas_replicate commands returned "Error 13428850703: Invalid replication ID" in this instance.

Fix Celerra now uses a consistent mechanism to generate and check replication V2 session IDs.




Symptom Description

When setting up CLARiiON array security on an Integrated Celerra, multiple steps were required.

Fix Security can now be enabled using a single command: nas_storage -modify id=x -security -username <username> -password <password>.




Symptom Description

If an integrated or gateway CLARiiON storage system had a MirrorView/A license installed but no MirrorView/S license, the nas_storage -sync and nas_storage -failback commands failed with the following error: Error 3502: <storage-system-id>: Storage API code=1: SYMAPI_C_FAIL. The function call failed.The following message found in the /nas/log/symapi.log file is indicative of this situation:2008-07-09 19:01:00.790 28817 1 EMC:Celerra CS User Generated c_clar_mg_cache_sync:<storage-system-id>:SYMAPI_C_FAIL The function call failed

Fix Code has been fixed so that the “nas_storage –sync” and “nas_storage –failback” commands can succeed with a single MirrorView license.



Version 5.6.40.3



Symptom Description

When auto FSCK tried to run on a MGFS file system, the Data Mover panicked with the following DART panic/fault message: Assertion failure: '0' on line 389 in file '../gssapi/krb5/gssapi_krb5.cxx' >>PANIC in file: ../assert.c at line: 23 : assert failed. Code incorrectly called a function that disconnects CIFS MGFS connection, and triggering this panic.

Fix Code has been fixed to ensure FSCK uses proper call to disconnect CIFS MGFS connection.




Symptom Description

File name creation occasionally failed in directories with more than 10000 names where the directory has been populated by older dart releases. Subsequent attempts to create same name succeed.

Fix The Data Mover could not generate an M8.3 format name in the directory for the file name being created because the possible names already existed in the directory. The code has been changed not to use UxFS inode number in generating M83name, instead, uses Data Mover CPU ticks with a hash to generate a randomized M83name. Once the randomized number is determined and if the number is already in use by the existing M83name, it proceeds to add 1 to it until an unused name is found. The code retries for maximum 10,000 times when all in use then the M83name will fail to create.




Symptom Description

SMB was not adhering to protocol standard for filename case preservation. This case applies only to Mac users using CIFS file system.

Fix Filename case preservation mechanism has been changed to return filename from disk rather than using filename from SMB request.




Version 5.6.39.5

Version 5.6.39.5




Symptom Description

User was unable to create a new checkpoint schedule from Celerra Manager. Tasks hung and never completed. The apl_sched.log was flooded with the following messages which could fill Control Station file systems.2008-02-07 15:37:56.982 Terminating Task Scheduler2008-02-07 15:37:56.983 Terminating Task Scheduler2008-02-07 15:37:56.985 Terminating Task Scheduler

Fix This problem occurred while creating a schedule with a setting which led to first execution time that was non-existent (e.g., Feb 30, 2008). This problem no longer occurs.




Symptom Description

When an attempt to setup V1 file system replication using the UI failed, the task status indicated it was actually successful.

Fix The task status will now correctly report the task has failed when it is not able to complete successfully.



Symptom Description

When a user created a new CIFS shares, it did not show in the file system name in the web interface.

Fix The display code was using a sequential search to display the CIFS share instead of a property of the share. The fix includes using the share property: 'item' interface of the table holding the share names instead of a sequential search.




Version 5.6.39.5


Symptom Description

When the creation of an administrative user failed, the password of this user was displayed in clear text in the log file /nas/log/webui.

Fix The layer responsible for transferring the password was fixed to only store the password encrypted in a file and not in clear text on the command line.




Symptom Description

If iSCSI properties were being queried against a standby Data Mover, when the iSCSI tab was selected in Celerra Manager, the following error was displayed: Invalid action response from Celerra Manager agent for task Query iSCSI Luns All:All:All.

Fix Code now checks for the type of Data Mover for which iSCSI LUN/Target/Mask properties are being queried. APL will not query for the properties if the Data Mover is of the type 'standby'.




Symptom Description

Virtual Data Movers were not listed in the CIFS share tab on Celerra Manager. Also, files in the /nas/jserver directory were continuously growing larger.

Fix The buffer containing all devices connected to the Celerra was overflowing because the data being passed was larger than the allocated buffer size. The buffer overflow occurred because both used and unused devices were passed. Code now only transfers the used devices into the buffers for reporting, and virtual Data Movers are correctly listed in Celerra Manager.




Version 5.6.39.5


Symptom Description

User saw the following error messages in the task list and task properties page when Replication v1 or Replication v2 license was not enabled: 1) You do not have appropriate privilege to perform this operation. Please contact System Administrator. 2) User is not allowed to perform this operation due to the replicator license not being enabled.

Fix Code now displays the Celerra Network Server information in the task list and task properties page only when the Replication v1 or Replication v2 license is enabled.



Symptom Description

If user had a Replication v1 license, the copy button was available in the file system list page. When selecting that button to copy the file system, user was unable to copy the file system as it requires a Replication v2 license to perform this operation. The following message was displayed: User is not allowed to perform this operation due to the replicatorV2 license not being enabled.

Fix When a R/O mounted file system is selected, the Copy button is now only enabled if a Replication v2 license is enabled. When a R/W mounted file system is selected, the Copy button is now only enabled if both the Replication v2 and Snapsure licenses are enabled.



Symptom Description

When DNS facility event 1 occurred for a client being unable to connect to a particular name server, several events were generated each second resulting in duplicate events. Since alerts were also generated for these events, duplicate alerts were generated. Only a single copy of the alert was displayed in Celerra Manager at one time, so it took several passes of accepting or deleting the alerts to get through all of the duplicates.

Fix This was fixed by applying a threshold mechanism to the alert to eliminate duplicates and limit the number of alerts that are posted to one every 6 hours until the problem is resolved. Events will still be logged in /nas/log/sys_log at the original rate.



Version 5.6.39.5


Symptom Description

Although the storage admin was defined with readonly privilege to the Data Mover, user was able to change the following properties: Name, Time Zone, Time, NTP Server, Failover Policy and StandbyMovers .

Fix Problem was in the looking up mechanism of object. APL has been modified to look for the whole object name match while listing capability and not the pattern search as one object name can have subset of other object name.



Symptom Description

While using Celerra Manager, when errors occurred in the cable check screen, clicking “detail” resulted in a pop up which showed error numbers without a corresponding error message. For example: # 1006999999, # 1001050300, # 1005001001

Fix Fixed the coding in cable check area to properly show the error number and the corresponding error message. The following messages are now displayed for these numbers: # 1006999999 :SPS check has encountered an unrecoverable error#1001050300 :Blade 3 is not cabled#1005001001 : The control station is unable to ping SPA



Symptom Description

While using Celerra Manager, when there were internal communication issues between services, such as APL went down, no information was displayed to the user.

Fix A message is now logged to syslog indicating the communication issue.The communication issue is temporary in nature. If the request is retried it should succeed. The log message is added to help anyone looking into the failure to determine what happened.



Version 5.6.39.5


Symptom Description

A user tried to create a new Replication (V1 replication), with the option "Set up and start replication using the disk/tape physical transport method. May be used for user file system Replications only." User selected the option "Complete disk/tape physical transport set up using the following checkpoint name:" in the Set Up A File System Replication Using Physical Transport Method field and entered an existing checkpoint name in the text box provided. When he clicked on the continue button, the page went blank.

Fix The page will no longer go blank and will display the "Complete Disk/Tape Physical Transport Set Up" page.



Symptom Description

If a user clicked the details link on a CCMD message in one system to open a CCMD pop up from one Celerra on a multi-Celerra setup, then clicked the details link on a CCMD message on a second system in the multi-Celerra setup, the window from the first CCMD popup was reloaded. Each system should have its own CCMD pop up, the message from one system should not replace the message from a second system in the same window.

Fix The window that was open is now given a name that is the current date in milliseconds, so that each CCMD popup will be opened into a new window to ensure previous message windows are not overwritten with new messages.



Symptom Description

If the user did not have a SnapSure license enabled and he visited the list pages of File System Mount, CIFS or NFS export, the following error message was displayed on top of the list pages "You do not have appropriate privilege to perform this operation. Please contact System Administrator."

Fix After the fix, the user no longer sees the privilege error on the list pages of File System Mount, CIFS or NFS export.



Version 5.6.39.5

CFS The following entries describe fixed Celerra File System problems:



Symptom Description

The following characters ")", "(", """, ">", "'", "`" were invalid for LDAP, but they could be entered by the user in the Celerra Manager.

Fix Modified the code to prevent these characters from being entered by the user.



Symptom Description

When a user set the allow monitoring with expired sessions and/or idle session timeout values in Celerra Manager, the values were reset when the Celerra was upgraded.

Fix This fix allows those values to persist through upgrades so they are not reset.



Symptom Description

When user mounted the component file system on the NMFS, the server_mount command failed with the error "No space left on device". This error occurred even if there was enough space on the backend.

Fix Fixed the inode allocation logic to ensure the command succeeds, and this error is no longer returned if inodes are available on the NMFS.



Version 5.6.39.5


Symptom Description

When using Celerra AntiVirus Agent and none of the virus checker servers were available, CIFS clients lost access. This occurred if the configuration was set to continue working with virus checking and CIFS when all virus checkers were offline.

Fix The CIFS threads which are waiting for files to be checked are now freed when the client times out and aborts the TCP connection. This prevents all of the CIFS threads from getting tied until one of the virus checker servers is back online.



Symptom Description

A race condition caused the modify date to intermittently change to current date when copying CIFS files in a Windows environment.

Fix Code now modifies date to be updated at the end of close operation with the value specified by a CIFS Set File Info request.




Symptom Description

Tree quota check tool did not count device special files. Any special device were not counted if they existed in the tree prior to the check tool running. This caused the tree quota report to show the wrong number of inodes used.

Fix This has been fixed so the check tool now checks for device special files and includes them in the calculation.




Version 5.6.39.5


Symptom Description

A user may access a Data Mover CIFS share using Kerberos credentials. If they are associated with a large number of groups, the encrypted portion of the credential may be quite large. When the Data Mover decrypted the received credential, it allocated a single, contiguous memory buffer for all the data to be decrypted. If the Data Mover has been running for a long time (months), the system memory was fragmented to the point that a large contiguous memory buffer was not available, and the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../addrspac.cxx at line: 275 : Out of memory. The stack trace showed:0xd8a4d700: 0x13d85c waitForReboot+0x90 0xd8a4d720: 0x13da59 fault_dump+0x67 0xd8a4d740: 0x13d959 PANIC+0x29 0xd8a4d750: 0x139732

_ZN19Memory_AddressSpace10allocPagesEi12Memory 0xd8a4d770: 0x18852e _Z11more_memoryiP9free_list+0x4e 0xd8a4d790: 0x1885e4 malloc+0x92 0xd8a4d7c0: 0x4961b9

_Z16krb5_rc4_decryptPK17krb5_enc_providerPK18k 0xd8a4d890: 0x48f015 krb5_c_decrypt+0x9d.

Fix The decryption code has been updated to use memory allocation calls that fail gracefully (i.e., not panic the system), if there is not enough contiguous memory available at the moment it's requested.




Symptom Description

When virus checking was enabled on a Data Mover, if there was a virus detected and the client that introduced the virus had exited and was no longer connected when the popup message was sent, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 9b224c Err code: 0 Target addr: 28c **. The stack trace showed: 0x1c8d264: 0x13e6c4 waitForReboot+0x900x1c8d284: 0x13e8c1 fault_dump+0x670x1c8d2a4: 0x138798 handle_fatal_fault+0xa0x1c8d360: 0xb22a14 _ZN10checkEvent14postProcessingEv+0x4600xdf54dfb0: 0xb218cf _ZN13check_initial5startEv+0x1e70xdf54dfe0: 0x142e6c Sthread_startThread_internal+0xe

Fix Code now verifies that the client has not exited before the PopUp message is sent to prevent this panic.




Version 5.6.39.5


Symptom Description

If a user attempted to use the “emcsetsd” tool to change ACLs from an NFS client, and the file or directory had no ACL and no new Security Descriptor was specified in the command, the Data Mover panicked with the DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: ca8c8f Err code: 2 Target addr: 14 **. The stack trace showed: 0x1c8cac4: 0x13e6c4 waitForReboot+0x90 0x1c8cae4: 0x13e8c1 fault_dump+0x67 0x1c8cb04: 0x138798 handle_fatal_fault+0xa 0x1c8ccc0: 0xca9a58 _ZN14set_celerra_sd7processEv+0x2d0 0xe23fb960: 0xca9ccd

_Z21cifs_set_celerra_sd_1P27cifs_set_celerra_s 0xe23fb990: 0xcacd8b

_ZN29xattrp_IterSvc_Parent_InitialC1EP16Rpc_Sv 0xe23fba40: 0x3f68ea

_ZN21Rpc_Svc_Child_Initial13svc_getreqsetEP7rp0xe23fbc30: 0x3f974f

_ZN25Rpc_IterSvc_Child_Initial7svc_runEv+0x10b

Fix The code attempted to use a buffer that had been allocated as zero bytes. This has been corrected.




Symptom Description

When virus checking was enabled on a Data Mover, if there was a virus detected and the client that introduced the virus had exited and was no longer connected when the popup message was sent, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 9b224c Err code: 0 Target addr: 28c **. The stack trace showed: 0x1c8d264: 0x13e6c4 waitForReboot+0x900x1c8d284: 0x13e8c1 fault_dump+0x670x1c8d2a4: 0x138798 handle_fatal_fault+0xa0x1c8d360: 0xb22a14 _ZN10checkEvent14postProcessingEv+0x4600xdf54dfb0: 0xb218cf _ZN13check_initial5startEv+0x1e70xdf54dfe0: 0x142e6c Sthread_startThread_internal+0xe

Fix Code now verifies that the client has not exited before the PopUp message is sent to prevent this panic.




Version 5.6.39.5


Symptom Description

After upgrading to 5.6 from an earlier code family, additional tree quotas created on file systems were not seen in quota reports. This happened on file systems which already contained tree quotas prior to upgrade.

Fix The tree quota db files created from a previous code family are now properly handled, and all of the tree quotas can be viewed in the tree quota reports.




Symptom Description

During checkpoint inactivation, the replication playback generated an I/O on the SFS that triggered smartsnap operations on the checkpoints. If the delta volume release occurred before smartsnap accessed the delta volume structure, the Data Mover panicked with the following DART panic/fault message: ** GP exception. Virt ADDRESS: b715f5. Err code: 0 ***. The stack trace showed: 0x1706058: 0x13d810 waitForReboot+0x90 0x1706078: 0x13da0d fault_dump+0x67 0x1706098: 0x137abc handle_fatal_fault+0xa 0x17060e0: 0xb7b095

_ZN15snapshotContext10BlockInUseEP8DeltaVolyP8S 0x65f8bbe0: 0xb6752a

_ZN19PoolManagedDeltaVol18writeBlockFilteredEP 0x65f8bc90: 0xb767b6

_ZN10SnappedVol18writeBlockFilteredEP10DiskIO_ 0x65f8bcb0: 0xb76771

_ZN10SnappedVol18writeBlockInternalEP10DiskIO_ 0x65f8bcd0: 0x72a39b

_ZN11HyperVolume18writeBlockInternalEP10DiskIO

Fix Code was modified to suspend all smartsnap operations on checkpoints that are subject to inactivation, and the Data Mover will no longer panic.




Version 5.6.39.5


Symptom Description

After setting the parameter cifs.acl.extacl=4 to allow backup and restore of UNIX attributes through Windows ACLs, UNIX SUID & SGID bits were not restored.

Fix Now the SUID & SGID bits are correctly restored.



Symptom Description

User could not see exactly how much space within the SavVol a checkpoint (RO or RW) was using.

Fix The user can now see output changes in "fs_ckpt" and "nas_fs -size". In the CLI for fs_ckpt, a new column was added to show the usage of particular checkpoint on SavVol. For "nas_fs -size" the ckptfs row is extended to show the usage of a particular checkpoint on a SavVol.Celerra Manager does not support this at this time.



Symptom Description

When CIFS Domain Controller became unavailable for a long time, the Data Mover consumed all of its network TCP resources retrying to connect to them. The CIFS clients received error: "network path not available".

Fix Code now releases all TCP resources associated with an unresponsive system when a TCP connection to it is not possible.



Symptom Description

Shares containing % characters were not rejected. This caused some unpredictable format issues such as a share not being accessible.

Fix Share names containing \ and % are now rejected.



Version 5.6.39.5


Symptom Description

When the NetBIOS name contained I18N characters as the string, the name could not be correctly translated. The Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: e14be5 Err code: 0 Target addr: 0 ** The stack trace showed: 0x2339bc4: 0x146bbc waitForReboot+0x900x2339be4: 0x146dcf fault_dump+0x670x2339c04: 0x13c59c handle_fatal_fault+0xa0x2339c30: 0xe14a62 _ZN14netbios_stringC2EPKci+0x36 0xa6ded8f0: 0xbe3b69

_ZN10smb_server16findServerByNameERPcR11cRefer 0xa6ded940: 0xe38e3f

_ZN12virusChecker13setCIFSserverEP6OptionRP8CC 0xa6ded9a0: 0xe3b249

_ZN12virusChecker11parseConfigERiRP8CCMD_Msgi+ 0xa6deda00: 0xe4b9f2

_ZN12virusChecker14checkAntivirusEP13CSanityRe

Fix Code now uses XLT to translate the incoming string and correctly handle the specified NetBIOS name.



Symptom Description

While using VDM, checkpoint and replication, a race condition occurred which led to a Data Mover panic with the following DART panic/fault message: ** Page Fault Interrupt. Virt ADDRESS: 93c1c0 Err code: 0 Target addr: 0 **. The stack trace showed:0x1cbae54: 0x13eec4 waitForReboot+0x900x1cbae74: 0x13f0c1 fault_dump+0x670x1cbae94: 0x1387a0 handle_fatal_fault+0xa0x1cbaee0: 0x93b5b1 _ZN10smb_server8cifsInitEv+0x2f0xc4ee5ab0: 0x93ed08 _ZN10smb_server5mountEv+0x180xc4ee5ad0: 0x20a0d6 _ZN3vdm13mountServicesEv+0x200xc4ee5af0: 0x20994e _ZN3vdm11finishMountEv+0x140xc4ee5b10: 0x209825

_ZN3vdm5mountEP14VFS_FileSystemPcPP8CCMD_Msg+0

Fix There was a race condition when one thread was constructing the registry and another thread was querying the registry. Code was fixed to ensure that only one thread accesses the registry database at a time.



Version 5.6.39.5


Symptom Description

User was unable to unmount a root file system, the following error message was displayed: Error 10281: server_2 : root_fs_2 : unable to unmount. Cannot determine file system status from the server.

Fix This issue was caused by taking two references to the same object within Berkley DB on the file system. Code was fixed to ensure only one reference will be taken to any objects within the file system, eliminating the issue.



Symptom Description

The server_usermapper command timed out on a large usermapper database. In this particular case, there were 1269528 inodes used in /, so one can presume that there were ~200,000 users and groups mapped on this older CNS running 514 Data Movers.

Fix Increased server_usermapper command RPC timeout value from 4 minutes to 10 minutes.




Symptom Description

The order of the name parameter and the domain parameter were not order independent when requesting the mapping of a user within a domain. In other words, if the name and the domain were switched, the command didn't work and produced a usage output. For example :Server_cifssuport server_x –usrmap –list –name<myName> -domain <myDomain>was accepted and successful. Server_cifssuport server_x –usrmap –list -domain <myDomain> –name<myName>Was rejected, and the usage message was displayed.

Fix Code was fixed to accept the command regardless of the position of domain and name in the command.



Version 5.6.39.5



Symptom Description

While creating a standalone CIFS Server, the user input workgroup, NetBIOS, password and other IP details. Execution failed stating "you must enter the name of CIFS Server".

Fix Disabled Server name while the workgroup option is selected. The server name is not required to create stand-alone (workgroup) CIFS servers. If the workgroup option is selected, the validation for server name is removed.



Symptom Description

After a Virtual Data Mover (VDM) was configured with a 2 user file system replication session, the VDM was stopped along with the replication sessions. An attempt was made to move the source VDM to another server which caused an "Input/Output error". This issue was due to the inability of the VDM's move command to lock the replication internal checkpoints on the file systems.

Fix The move command was changed so that the file system would handle the mount/unmount operation of the internal checkpoints. This removes the process of having the VDM move command lock the replication internal checkpoints on the file systems.



Symptom Description

Users with read-only admin role login credentials were able to issue XML management requests (via the WebUI or XML API interfaces) and have those requests perform either modify or create operations successfully. These operations are not permitted for read-only accessed users and should have been refused, but the middleware software was failing to enforce the appropriate read-only restrictions.

Fix The Control Station's mgmtd has an admin role cache which performs the security checks to determine if a user has the correct privileges to perform an operation. There was a logic error that was permitting the read-only users to perform read-write operations. This has been fixed.



Version 5.6.39.5


Symptom Description

A Control Station running 5.6 could not dial out or in through the modem after a reboot.

Fix Changed the code to start up modem device correctly after a Control Station reboot.



Symptom Description

CLARiiON defaults the value of the system wide arraycommpath and failovermode settings to 1 to be compatible with EMC PowerPath software. Celerra requires arraycommpath and failovermode be set to 0 on integrated Celerras which don’t use Access Logix. Celerra installation software was inadvertently setting the default value for arraycommpath and failovermode to 0 for Integrated and Gateway systems which use Access Logix.

Fix Fix prevents changing the default CLARiiON values for arraycommpath and failovermode on systems using Access Logix and will set those to 0 for each initiator record registered and associated with the Celerra storage group.



Symptom Description

A server_dbms command against an unloaded VDM failed with different error messages depending on the state of the root file system of the VDM. The command failed with the error message Error 4032 : VDM is not loaded when the root file system of the VDM was not mounted.The command failed with the unexpected message Error 4019: <VDM name> : failed to complete command when the root file system of the VDM was mounted.

Fix The server_dbms command against an unloaded VDM is always rejected with the error message : Error 4032 : VDM is not loaded regardless of the mounted status of the root file system of the VDM.



Version 5.6.39.5


Symptom Description

Storage system events were not reported on NX4 platforms.

Fix The CLARiiON fix for this issue has been incorporated into naviseccli. The error message will now be displayed with complete storage system information.



Symptom Description

Various countries changed their Daylight Savings Time (DST). Without the fix, the time on the Control Station and on the Data Mover remained at the previously specified time.

Fix Code was fix to pick up the new Linux tzdata rules file along with updates from Java to address DST changes for Cuba, Syria, Iraq, Pakistan and Morocco.



Symptom Description

When using Celerra Network Server version 5.6.38.2, when an XML request was sent to the middleware software within the Control Station, the mgmtd daemon's Admin Role Cache issued requests to the apl_task_mgr to obtain Admin Role based information that is required to allow Admin Roles security checks to be performed on incoming XML requests. If the apl_task_mgr was not up and running at the time the requests were sent, the Admin Roles Cache received a timeout event and requests were not retried.

Fix The Admin Role Caches retry mechanism was broken and events were not being processed during communication timeout. Altered code so these events were correctly handled.



Version 5.6.39.5



Symptom Description

On an SRDF system, the non-rdf protected source server's ACL was changed to 0 during installation and upgrade. The ACL could not be reset to 1000 using the nas_rdf -init command.

Fix Fixed the bug to detect MirrorView system and prevent the Data Mover ACL value from changing to 0 during the upgrade.



Symptom Description

When installing a new version of CSA and another version was already on the system, the maintenance wizard was displayed with options modify and repair, even though these options were not valid.

Fix Options modify and repair did not apply to this installation and have been removed from the wizard. Now under this condition, only the remove option is present.



Symptom Description

When NAS Service is not running, CSA reported:Tomcat and Apache (web servers) were not started.

Fix The fix is to add a proper error message when NAS Service is not running. The new message is:Brief = Timed out waiting for NAS services to run.Detail = NAS services need to run completely for Apache and Tomcat to start.Action = NAS services could fail to run for various reasons. The system log on the Control Station will provide more information on why NAS services could not start. Please refer to the system log or contact EMC Support.



Version 5.6.39.5


Symptom Description

If an error message occurred in the Health Check screen of the CSA, the message continued to be displayed on other screens after clicking the Back button or Next button.

Fix The error messages are now cleared after clicking on the Back button or Next button.



Symptom Description

When user provided different domain extension between the name specified and domain specified, Proxy ARP failed because user entered a hostname including domain which could not be resolved to an IP. This resulted in a backend IP setup failure on the Pre-configuration Apply screen.

Fix The changes for this issue includes: 1. Disabled Back and Next button when processes in Pre-configuration Apply are running. This helps to

prevent unnecessary error, resulted from the communication between CSA and control station when performing services check. It also prevents the failure in killing previous thread.

2. Changed the flow by running software services check and proxy arp at the same time and waiting until proxy arp is done before running the rest of the configuration setups.



Symptom Description

When using the CSA from the Apps & Tools CD on a new factory install of 5.6.36.4, the CSA hung during the Pre-Configuration phase, reported the following application error.CSA SCREEN ERROR ON PRE-CONFIGURATION SCREEN. NBS volumes are not available. This occurs when a user tries to break into the Control Station by typing ‘L’. A cable check script renamed a file that CSA uses before CSA used the file. This file is needed to reboot the Control Station.

Fix When a user types ‘L’, the file used will not be removed or renamed. Hidden files are now created and the hang is diverted.



Version 5.6.39.5


Symptom Description

When a user was asked to select a Celerra to connect to in the Celerra Startup Assistant, the area where user selects a Celerra MAC address was not clearly labeled.

Fix Provide a new label to display Select a MAC Address. If a MAC address is found, CSA displays the first MAC address in the list. If the MAC address is not found the field displayed is now empty.



Symptom Description

While using Celerra Startup Assistant, if the user encountered an error ending in "9999" on the Health Check screen, no error message was displayed.

Fix Error messages are now provided for the error codes ending with 9999. Error codes that end with 9999 are unrecoverable / unknown error. The recommended action is to contact your EMC Customer Support representative.



Symptom Description

While running CSA, after cable check completed successfully, the Health Check screen message displayed Please wait while the CSA checks if NAS services are started. If NAS services had not started, this message stayed on the screen with the activity bar scanning back & forth for ~ 30 minutes before timing out and posting the message, "ERROR: Software services are not running". The additional detail message The web servers are not running.provided no real guidance to the user: This problem applied to all the CSA-supported Celerra models.

Fix Changed the timeout from 30 minutes to 5 minutes. Enhanced the error message to indicate the reason and action. The following message is now displayed: ERROR: The required services are not running. Reboot the Control Station then restart CSA again.



Version 5.6.39.5


Symptom Description

While creating a standalone CIFS Server, the user input workgroup, NetBIOS, password and other IP details. Execution failed stating "you must enter the name of CIFS Server".

Fix Disabled Server name while the workgroup option is selected. The server name is not required to create stand-alone (workgroup) CIFS servers. If the workgroup option is selected, the validation for server name is removed.



Symptom Description

When the user changed the default password of either nasadmin or root user on the Change Password Screen of CSA, the new password was accepted without any validation. When an attempt was made later after navigating through a few screens to set the Control Station password with the newly entered password, the user received the following message Password does not conform to the policy if the new password did not conform to the password policy. The user had to go back several screens to enter a new password.

Fix Password validation is now done on the Change Password Screen where it allows users to change the password. The user is allowed to go the next screen only if the new password conforms to the password policy. If the password does not conform to the password policy, the error message Password does not conform to the password policy is now displayed on the Change Password screen.



Symptom Description

When doing a cable check in the Celerra Startup Assistant and hitting the Back button, the previous thread running the cable check was not stopped. This caused undesirable consequences, such as having multiple threads running cable checks and all simultaneously sending results to the screen with multiple results being reported for the same checks. This interfered with speed and flow of going back and performing other tasks as well.

Fix The Back button failed to stop previous thread performing health check. This was fixed by disabling the Back and Next button when cable check is running.



Version 5.6.39.5


Symptom Description

During the "Celerra Registration Wizard" process, after inputting the IP address for the Control Station, the Celerra Startup Assistant Registration Wizard hung after successfully connecting to the Control Station.

Fix Due to the volume of information returned to a function which Registration uses, a new flag was created to restrict the amount of payload data returned to registration wizard.



Symptom Description

When authenticating passwords for root or nasadmin using the Celerra Startup Assistant, if there was a failure, the following error was displayed: Authorization failed for root or nasadmin user accounts. This message did not indicate which user had the faulty password.

Fix The error message now indicates which user this issue applies to.



Symptom Description

The dial-in modem telephone number on the Celerra Startup Assistant initialization screen was not validated. This caused inconsistency with other features, and the Registration wizard.

Fix To ensure consistency with ConnectEMC and Registration wizard, the dial in number is now validated.



Symptom Description

CSA tool tip messages were displayed for only five seconds, after which they went away. This made it difficult to read the tool tips.

Fix Extended the tool tip display timeout to 20 seconds.



Version 5.6.39.5





Symptom Description

The creation of a FileMover (DHSM) connection on Data Mover failed with Error 5005: failed to complete command, preventing subsequent attempt for configuring DHSM connection.

Fix Failure in a name resolution during DHSM connection creation caused a DHSM reference leak resulting in other subsequential attempts to fail. Code now handles this condition correctly, and the issue has been eliminated.



Symptom Description

Dialhome did not work if the environment required a dialout prefix which included * or #.

Fix Dialout prefix containing * and # can now be used in the phone number.




Symptom Description

NAS code upgrade failed at task [31/70] with navicli port -list failed error message if the name of a storage group contained spaces. Spaces are allowed in the storage group name and the command should have succeeded.

Fix Code was fixed to only trim leading and trailing spaces in storage group names and to leave embedded valid spaces alone.




Version 5.6.39.5


Symptom Description

Toward the end of a fresh install, nas_checkup performs a health check. In this case, it generated the following info level message:Storage System: Check if backend zone correctSymptom: You have not set up fiber switch information for this check, therefore zoning cannot be checked.Action : Run "/celerra/backendmonitor/backend_change_monitor - addentry <IP address> <switch model> <SNMP community>" command to add a switch to be monitored. The switch should be the one used by the Data Movers and the storage systems. Use IP address to avoid any name resolution issue. Currently the check only works with McData, Cisco, or Brocade switches. The query is done via SNMP, therefore SNMP community string has to be specified, and the community has to allow READ access.However, for integrated system, there is no switch information.

Fix This message only applies to gateway systems. This message is no longer logged for an integrated system.



Symptom Description

When running /nas/sbin/model on an NS40 Integrated with a CX3-40c BE for use with MPFS, the command returned NS40. The command should return NS40-AUX-C.

Fix The model command /nas/sbin/model -x now returns a value of NS40-AUX-C when run on an integrated NS40 system that has a CX3-40c storage system.



Symptom Description

When a system had a large number of remote IP Replication sessions setup, the pre-upgrade health check for IP Replication took a long time to complete. This happened because the health check was using a query that was not efficient for this particular check because it queries for many other details that were not needed for this health check.

Fix To improve the time it takes to run pre-upgrade health check for IP Replication, the query that provides necessary details about replication session was replaced with a much more efficient one.



Version 5.6.39.5


Symptom Description

If a system was installed with a single Data Mover, the procedure to add more Data Movers failed. Messages similar to the following were displayed: Mount root filesystem root_fs_3 on server_3 server_3 : Error 16: server_3 : Device or resource busy mount uxfs rw / 14=3 rw server_3 : Error 22: server_3 : Invalid argument CRITICAL FAULT: Failed to complete fs_mount task

Fix Code was fixed to resolve the failure and allow the addition of Data Movers to complete.



Symptom Description

After an upgrade to Celerra Network Server version 5.6.36.4 or later, /etc/motd and some other files were replaced with default files. Other files that are affected: the sshd_config files were replaced, the motd file was overwritten, the acls set on the Data Mover was set back to 1000 UI timeouts was reset. Users with permission such as creating new file system were no longer able to do so.

Fix Code was fixed to prevent any file overwrites during upgrades.



Symptom Description

The Pre Upgrade Health Check script was not giving useful information when navicli commands failed because security was not setup on the backend. The error information was not shown to the user.

Fix PUHCs now return the proper messages, similar to the following: Warning: Storage System: Check if FLARE is supportedSymptom: Backend Storage Requirements Check Failed: navicli failed with following output: CLARiiON Flare R28 requires security. Please refer to EMC Knowledgebase number emc168569. Failed: Unable to determine if the Storage System software is qualified with this version of NAS.Action : Check the messages above to determine the problem, fix it, then run "check_nas_upgrade -pre" to verify that the problem has been fixed.



Version 5.6.39.5



Symptom Description

After a NAS install, during the Linux boot process, there was a delay of about 3 minutes while starting sendmail service.

Fix When the Control Station was coming up, the steps to send mail and client setup were taking a long time and were timing out because the hosts file on the Control Station did not have the FQDN (fully qualified domain name) for the Control Station internal interface entry. The fix for this issue was to add FQDN for the Control Station's internal interface entry in the /etc/hosts file.



Symptom Description

During installation, "Is this a dual CS configuration? [yes or no]:" question was asked repeatedly during EMC NAS Factory installation.

Fix Fixed the issue of "is_dual_cs" prompt which was being asked multiple times during installation. The prompt will now ask the question only once.



Symptom Description

The following text appears on console during CS recovery: cp: cannot stat `/nas/site/user_bak_db': No such file or directory."

Fix Code was fixed to pick up the correct (/nas/site/passwd_bak_db) file which eliminates the error message.



Version 5.6.39.5


Symptom Description

iSCSI services failed to start after failback of the Data Mover. ISNS (iSCSI name service) failed to restart as ISNS heartbeat listener port was incorrectly chosen. The following error was displayed in the server log: 2008-04-15 11:58:02: IP: 3: TPI error ack, tpi error = 8, errno = Address already in use

Fix Disabled the ISNS heartbeat listener port as it is currently not supported by Microsoft's iSNS server.

Service Request Number

23191700



Symptom Description

After demoting a local LUN using snaptest, Windows didn't reflect the device change. Although Disk Management showed the device as removed, it could still be seen in the devices list in the iSCSI initiator, and if mounted could be seen in My Computer. A manual disk scan from Disk Management refreshed the device list.

Fix An Async event is now sent to the Windows initiator after the demote operation to indicate the change in the iSCSI LUN configuration which immediately removes the iSCSI LUN from the Windows host.



Symptom Description

When using iSCSI replication, user did not specify the source Data Mover IP but only specified the destination Data Mover IP. In this case, replication was configured using a source Data Mover IP that was not present in the interconnects. This caused the iSCSI replication validation to fail, and thus, configure replication failed with the following: Validating destination...replication destination invalid: NBS_DPRQST_ReverseInterconnectNotConfigured: The reverse interconnection is not configured.

Fix Replication code was fixed such that when user does not specify source Data Mover IP, it now picks up an address from the relevant interconnect.



Version 5.6.39.5

MirrorView The following entries describe fixed issues related to MirrorView:



Symptom Description

In rare cases, Celerra systems configured for RDF or MirrorView/S DR failed to restore if a tape existed on the target system on a chain occupied by a disk on the source system. This tape configuration was inadvertently being treated as a gatekeeper device causing a command failure with error: precondition violated [ DISK_ENTRY.symmetrix].

Fix The code will now properly skip these devices when looking for gatekeeper devices.




Version 5.6.39.5


Symptom Description

In an MPFS environment, when the file system became full or hit its high water mark, two different panics occurred. One was due to the file system full condition and had the following footprint: DART panic/fault message: getOneFreeDiskBlock failed: file system full. The stack trace showed: 0x184275d0: 0x13d810 waitForReboot+0x900x184275f0: 0x13da0d fault_dump+0x670x18427610: 0x13d90d PANIC+0x290x18427620: 0x618a7e

_ZN14UFS_FileSystem28markCorruptedFsForUnmount0x184276a0: 0x67dc04

_ZN17UFS_MemoryFileMap19getOneFreeDiskBlockElP0x184276d0: 0x67b7d7

_ZN17UFS_MemoryFileMap18allocFileSpaceListEyyP0x184277a0: 0x623cba

_ZN9UFS_Vnode10allocSpaceEmmRP11extentEntryRy+0x18427830: 0xbb6ca0

_ZN10DHSM_Vnode10allocSpaceEmmRP11extentEntryR

The other panic was due to a counter out of sync condition: DART panic/fault message: getOneFreeDiskBlock failed: counters out of sync. The stack trace showed: 0xbb9a35d0: 0x13d890 waitForReboot+0x900xbb9a35f0: 0x13da8d fault_dump+0x670xbb9a3610: 0x13d98d PANIC+0x290xbb9a3620: 0x61a538

_ZN14UFS_FileSystem28markCorruptedFsForUnmount0xbb9a36a0: 0x67f858

_ZN17UFS_MemoryFileMap19getOneFreeDiskBlockElP0xbb9a36d0: 0x67d42b

_ZN17UFS_MemoryFileMap18allocFileSpaceListEyyP0xbb9a37a0: 0x625816

_ZN9UFS_Vnode10allocSpaceEmmRP11extentEntryRy+

Fix Fixed a 32-bit rounding error in the counter that was causing both of these issues depending on which edge condition was hit first.



Version 5.6.39.5



Symptom Description

User issued the following command before starting the MPFS service and specified a number of threads that brought the total number of threads over the maximum allowed of 128: server_mpfs server_2 -add 128. The command completed and added the amount of threads specified. After this was done, when user tried to start the MPFS service, the command failed. $ server_setup server_2 -Protocol mpfs -option start

server_2 : Error 4020: server_2 : failed to complete command. The server log showed: 2007-12-12 18:40:13: FMP: 4: Currently available 16 threads. 2007-12-12 18:40:13: FMP: 4: Cannot add more than 112 threads 2007-12-12 18:40:13: ADMIN: 3: Command failed: mpfs set Threads=144

Fix FMP can be started, stopped, and started again using a legal number of threads. If user tries to set an illegal thread count, the following error is returned "Cannot add more than x threads" and that FMP service can still be restarted.



Symptom Description

While using NDMP, if user aborted a running incremental backup of a large directory, the Data Mover panicked with the following DART panic/fault message: *** Watch Point exception. Virt ADDRESS: 84058e ***. The stack trace showed: 0xbb0c5f3c: 0x13d890 waitForReboot+0x90 0xbb0c5f5c: 0x13da8d fault_dump+0x67 0xbb0c5f7c: 0x137b3c handle_fatal_fault+0xa 0xbb0c5fd0: 0x80d00f _ZN15Uthread_Initial5startEv+0x11 0xbb0c5fe0: 0x141024 Sthread_startThread_internal+0xe

Fix Code now prevents accessing a NULL pointer and this panic no longer occurs.




Version 5.6.39.5


Symptom Description

While running NDMP backup, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../bufpool.cxx at line: 322 : couldn't get a free page. The stack trace showed: 0x254efbc0: 0x13d810 waitForReboot+0x90 0x254efbe0: 0x13da0d fault_dump+0x67 0x254efc00: 0x13d90d PANIC+0x29 0x254efc10: 0x167af7

_ZN18Buffer_Cached_Pool17makeCachedBuffersEi+0 0x254efc40: 0x13a5fd

_ZN19Memory_AddressSpace16makeCachedBufferEv+0 0x254efc60: 0x167685

_ZN18Buffer_Cached_Pool15getAnyCachedBufEji+0x 0x254efc90: 0x736a50

_ZN17UnCachedIO_Object9readBlockEym16BlockIO_P

Also in the server_log the following messages were displayed:2008-04-23 09:29:24: NDMP: 4: cifs_ea new count: 971482292,

delete count: 971482293, freeListCount: 36069 2008-04-24 09:35:47: NDMP: 4: cifs_ea new count: 972016990,

delete count: 972016991, freeListCount: 36713 The indication of a problem is that the “delete count” number in these messages is greater than “new count” number.

Fix This issue has been fixed and code prevents double deletion of cifs_ea which caused memory leak or memory corruption in this case.




Symptom Description

While using NDMP, the VBB restore failed because the metadata file was empty. The following errors were generated in the server_log: "VBB: 3: No data in Metadata file " and "VBB: 3: Error reading mapping "

Fix When VBB restores an empty incremental backup - a clear message stating that there is no metadata in backup is now logged to the DMA (Data Management Application).



Version 5.6.39.5



Symptom Description

While doing DUMP type backup of file systems with file filters as namedpipe, chardevice, blockdevice failed in Netbackup with NBU code 249. But Celerra server logs show successful completion of the same. In case of tar type backup with the same filters, backup process completed successfully but those files were not filtered.

Fix The function that sends file-history for dump backup has been modified to make sure that we filter out only regular files (not character devices and other special files).



Symptom Description

While doing a VBB backup, the VBBSession thread in its initial processing did not check to make sure that the HIST environmental variable was not NULL. This caused the Data Mover to panic with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: fd3776 Err code: 0 Target addr: 0 **. The stack trace showed: 0x1c8c2a4: 0x13e694 waitForReboot+0x900x1c8c2c4: 0x13e891 fault_dump+0x670x1c8c2e4: 0x138768 handle_fatal_fault+0xa0x1c8c380: 0xfd30bd _ZN10vbbSession5startEv+0xdf 0x82b27fe0: 0x142e3c Sthread_startThread_internal+0xe

Fix VBB now checks to make sure that the HIST env var is not NULL. Code now avoids dereferencing when the pointer is NULL to prevent this panic.



Symptom Description

The user found that entries in the Data Mover's "groups" file were ignored if the line exceeded 1000 characters. The following message was logged in the server_log: SECURITY: 3: 2: Line too long in group file: <line greater than 1000 characters.

Fix Though this is needed only in rare occasions, the maximum size that can be supported per-line in the group file has been increased to 3000 characters.



Version 5.6.39.5



Symptom Description

A Data Mover panicked as a result of memory being corrupted. The function "xdrString testtag(char *)" made a temporary copy of an xdrstring without properly verifying the xdrsting length and allocating the appropriate amount of memory. DART panic/fault message: Assertion failure: 'verifyMessage(reply)' on line 771 in file '../nfsv4_thrd.cxx' >>PANIC in file: ../assert.c at line: 27 : assert failed. The stack trace showed:fbec00: 0x245b6b _assert+0x63 fbec30: 0x7d75e1 _Z19nfsv4_clientdisplayj+0x105f fbee10: 0x79bda0 _ZN17nfs_serverInitial5startEv+0x1c82 fbefd0: 0x175bf5 Sthread_startThread_internal+0x7

Fix This problem occurred if an NFSv4 message was received without correct XDR encoding. Code has been updated to correctly verify incoming messages and reject them if needed.



Symptom Description

If an ACL for a file or directory contained an entry for CIFS-only well-known groups, NFSv4 users were unable to modify the ACL of the file. This is blocked intentionally, since NFSv4 clients could replace the CIFS-only ACE with an invalid entry, but there was no indication why the user couldn’t change the ACL.

Fix When this occurs, the following message is now logged in the server_log: nfs4_checkSpecialAce: SID <SID> cannot be translated to NFSV4 : ACL can't be modified.




Version 5.6.39.5


Symptom Description

When user aborted a replication session, the following event was sent to Control Station in log message in server logs: VolID:volid Last DeltaSet Replayed:0 created on Primary at:01/01/1970 00:00:00.

Fix This issue was hit when replication had started and some deltasets had been scanned on secondary side but not yet played back. Code no longer sends any event in this case as there is no deltaset replayed back on secondary file system.



Symptom Description

When using Replicator v1 and either the save or config volumes could not be recovered, the replication session became inactive but no message was logged indicating this.

Fix Changed the return status which is sent to replica/playback functions so that if save volume/config volume is not recovered, code returns FALSE so that in server logs we print correct log message saying replica/playback start failed.



Symptom Description

After SavVol corruption, the Data Mover entered a rolling panic situation from which it could not recover automatically. The panic type could vary, but occurred while the system attempted to parse contents of the SavVol, which was unrecoverable. The Data Mover needed manual intervention to become stable again.

Fix If unrecoverable SavVol corruption is detected, the system now marks the SavVol as unusable instead of attempting to re-use the Savvol. Messages are logged in the server_log indicating that this has happened. Any checkpoints or replication sessions using this SavVol will become inactive, though this was unavoidable before the fix as well. The system now automatically marks them as unavailable without needing manual intervention to stabilize the system.



Version 5.6.39.5


Symptom Description

After attempting to stop a nas_copy session on either the source or destination using nas_replicate -stop, the task could not be aborted.

Fix The correct way to stop/abort a nas_copy session is using nas_task -abort. Now an attempt to use nas_replicate -abort on a nas_copy session will error with: Error 13160415804:This operation is not allowed because the replication session is a copy session.



Symptom Description

If a user configured a bandwidth schedule with a bandwidth of 0 to temporarily stop data transfer, transfer did not resume after the bandwidth schedule expired.

Fix The problem occurs because the resume time was not being captured when the replication was suspended. The fix captures that resume time and resumes the replication at that time.



Symptom Description

The Replication V1 to V2 conversion command's default action was to run a pre-conversion check, and then start the conversion process. This could lead to a possible unintentional replication conversion if the user issued the /nas/sbin/upgrade_repv1_to_repv2 command .

Fix A -start option was added to the conversion command. Now if the user types in the /nas/sbin/upgrade_repv1_to_repv2 command, the command will return a usage statement. Users can issue a -check or a -start argument based on whether they want to run the pre-conversion check (-check), or if they want to run the actual conversion (-start) Such as:/nas/sbin/upgrade_repv1_to_repv2 -check/nas/sbin/upgrade_repv1_to_repv2 -start NOTE -- The pre-conversion check will automatically run prior to the actual conversion when the -start argument is issued.



Version 5.6.39.5


Symptom Description

If copy session was in progress of data transfer, aborting the copy task didn't abort the data transfer immediately. It waited for the data transfer to complete and did cleanup. The copy session was displayed on the Replication List page, the copy task displayed : Transfer Done.

Fix If copy is in progress of data transfer, aborting the copy task will abort the data transfer and the copy session will be cleaned up immediately.



Symptom Description

For all the Replication V2 related actions, the Task messages generated were of the type Action along with the Replication name to keep track of the task. But most of the time, the replication name was not available and the Task could not be tracked uniquely.

Fix This problem was fixed by putting the replication ID along with the name such that even if the replication name does not exist, the task can be uniquely tracked by its replication ID.



Symptom Description

In the Celerra Manager file system copy page and the file system copy screen, writable checkpoints and internal replication checkpoints were displayed. User could accidentally choose one of these checkpoints and try to copy it to a file system, which would be an invalid operation and it would ultimately fail.

Fix Celerra Manager no longer presents the writable and internal checkpoints to the user as options to perform a file system copy. These checkpoints now are filtered out.



Version 5.6.39.5


Symptom Description

User created a VDM from the VDM list page, and immediately right-clicked the VDM just created and selected "New Replication". The new replication page loaded but with the following error message on top of the screen: "Selected vdm <vdm name> is not available for replication".

Fix Users need to wait for few seconds before selecting "New Replication" on the just created VDM. Users will now get the following message: The Virtual Data Mover ${vdmName} cannot be used as a source for this Virtual Data Mover replication because it is either unloaded, its Data Mover is not available, it has already been replicated, or its status is not OK or Info. <Recommended Action> Retry the operation after a few seconds, otherwise choose a different Virtual Data Mover to create the replication. Make sure the VDM you select is in an unloaded state, its Data Mover is available, the VDM has not already been replicated, and its status is OK or Info.



Symptom Description

User could not perform a "Delete" or "Stop" operation when some of the columns in the replication list page were still loading.

Fix GUI will display the following error message asking the users to wait till the list page loads completely before performing "System is still trying to determine the role types for all the selected replications".



Symptom Description

The failover from secondary side completed and the failover background task was still running. At that point, the correct ckpt/snap information was not available in memory, and the delete operation failed with "Error 13160415656: Invalid snap information found."

Fix Fixed the problem with Delete operation retrieving the ckpt/snap information from disk.



Version 5.6.39.5


Symptom Description

The following symptoms were reported:1) User was logged-in to Celerra Manager and had Rep1 enabled. Then he did the migration from v1 to v2 (from the CLI). In the GUI, the various RepV2 actions cannot be performed. The action buttons are disabled (except New). 2) User enabled the SnapSure license using the nas_license command from the CLI and then used the /nas/bin/nas_ckpt_schedule to perform an action on the checkpoint and got a " You do not have appropriate privilege to perform this operation." error. 3) User logged in to Celerra Manager. System was in V2 ready state (i.e. Rep V2 license was not enabled yet). User enabled the RepV2 license from the CLI using the nas_license command. Then user visited the Wizards page in Celerra Manager and found that the button to create a new replication was still disabled. This should have been enabled because now RepV2 is enabled. 4) In general for Celerra Manager, whenever a license was changed from the CLI, user was required to refresh the GUI by pressing the refresh button in the tool bar. Otherwise the functionality dependent on that license was not accessible.

Fix Code now propagates the license changes from the CLI to the GUI to enable the GUI to respond to the license changes and correctly display the dependent functionality.



Symptom Description

The default for Checkpoint Storage Pool drop-down on the New File System Replication page was displaying "Select a pool" instead of displaying the pool that will be used if the user doesn’t change it.

Fix The GUI will attempt to select the same pool as the one used by the corresponding file system. If that pool is not a valid pool (based on space checks) then the GUI will pick the 1st pool available in the list. If GUI cannot find any pools that meet the space check, then it will display the following: Brief Description: There are no storage pools available for the source side checkpoint storage. Full Description: There are no storage pools available for the source side checkpoint storage because they either do not exist or the existing pools do not have enough storage space. Recommended Action: Add storage pools or clean up the existing storage pools used for checkpoint storage.



Version 5.6.39.5


Symptom Description

During an upgrade from 5.5 to 5.6, the user_db and group_db files are copied into the /nas/site directory. The script that performs the copy performs other tasks and took different amounts of time to begin the copy operation. The upgrade was not waiting for these files to be copied before it started the mgmtd and allowed requests. When the first request was processed, the Controls Station's mgmtd daemon attempted to read these files so that it may perform the Admin Roles security checks. When it discovered the files were missing, it got an error response. Unfortunately, these files were not re-read when such an error had occurred. This prevented the Admin Roles cache from being constructed and therefore any further requests were stuck waiting for the Admin Role cache to be constructed.

Fix The Control Station's, mgmtd daemon Admin Role Cache was altered to constantly retry reading the user_db and group_db files, until successfully read.



Symptom Description

If the replication task was in "replication pass through abort command sent" state when attempting to abort a replication session, the task on the Data Mover finished but the corresponding task on the Control Station remained and could not be aborted manually. This resulted in the task hanging on the Control Station.

Fix The code has been changed to allow a task in this state be aborted manually.



Symptom Description

If previous IP replication failover operation encountered an error on the source side, the destination did not retry. Subsequent start operations failed with "Error 13160415307: The object is not in right state for replication."

Fix The problem has been fixed, and failovers on the destination side now retry on source side.



Version 5.6.39.5



Symptom Description

User created a local file system replication and issued the nas_replicate -stop command on the destination side. The command hung and the following error was displayed:Brief Description = The system is performing cleanup on the secondary Data Mover. Full Description = The primary Data Mover has signaled the secondary Data Mover to clean up and is waiting for its response. Recommended Action = No action is required.

Fix Code now distinguishes between local and full stop and when a registration error occurs handles the rollback correctly.



Symptom Description

When user selected a read/write file system on the File System list page in Celerra Manager and click the Copy button, the Copy File System page was displayed. Once on the Copy File System page, user was presented with a Choose a Checkpoint drop-down that included all the checkpoints that have been created on that file system. If user selected a checkpoint from the drop-down (instead of accepting the one displayed by default), the page was redisplayed but nothing else on the page changed.

Fix Modified the code to not redisplay the Copy File System page when the checkpoint dropdown was changed, as this was not necessary.



Version 5.6.39.5

SRDF The following entries describe fixed issues pertaining to Symmetrix Remote Data Facility:


Symptom Description

During SP failover testing on the CLARiiON, the Data Mover panicked because of I/Os not completing. Investigation showed that three LUNs did not trespass when the SP was failed over. DART panic/fault message: >>PANIC in file: ../BVolumeIrp.cxx at line: 354: IO failure on Vol:278, blkNo:145, SKey:0x54. The stack trace showed:0x3ea9eb0: 0x13e6c4 waitForReboot+0x900x3ea9ed0: 0x13e8c1 fault_dump+0x670x3ea9ef0: 0x13e7c1 PANIC+0x290x3ea9f00: 0x809521

_ZN8SgIO_IRP9irpFailedE14BlockIO_Statusy+0x405 0x3ea9f60: 0x89fac8

_ZN14CamDisk_Device8completeEP10ccb_header+0xe6

Fix When a HLU (Host LUN Unit) number is 128 or larger (0x80, high order bit set), sign extension caused the number to be stored as 0xFF80 (decimal 65408 and above). This incorrect value was then sent as the HLU to be trespassed to the SPs - i.e. the code did not trespass the correct HLU. The code now uses unsigned values, which prevents this issue. Note, ALU (Array LUN Unit) numbers larger than 128 are not an issue.




Symptom Description

RDF failover was successful, but RDF failback failed as a result of the RDF script trying to failback the device group twice. CRITICAL FAULT: SRDF restore failed for 1R2_500_1.

Fix The nas_rdf -restore process will now continue without this error.




Version 5.6.39.5



Symptom Description

During the discovery of the remote Celerra devices process that occurs in the SRDF initialization phase, the corresponding devices could not be identified because the return values from SYMAPI had changed between SYMAPI versions. The nas_rdf -init command failed with "Unable to setup remote devices" .

Fix This has been corrected, and the nas_rdf -init command will now succeed.



Symptom Description

On a CNS model Celerra system configured for DR using SRDF, when the internal IP addresses used different subnets on the source Celerra than on the target Celerra, an error condition occurred during the SRDF restore, in which the Data Mover's configuration was not entirely restored.

Fix Code has been modified to ensure the Data Mover's configuration is restored correctly when internal IP addresses use different subnets.



Symptom Description

The unmount of file systems took over 2 minutes to complete. As a side effect, checkpoint deletes and other commands timed out and failed. The issue was caused by using single thread approach to scan the list of open objects within the file system prior to the unmount which was taking 2 minutes of Control Station timeout for any commands and resulting in the above behavior.

Fix Code has been fixed to use multiple threads to scan list of open objects which improved the file system unmount performance and eliminated the problem.



Version 5.6.38.2

Version 5.6.38.2

CDMS The following entries describe fixed problems pertaining to Celerra Data Migration Service:




Symptom Description

While migrating data to a Celerra with CDMS over NFS, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../bufpool.cxx at line: 322 : couldn't get a free page. The stack trace showed: 0xdffa8ff0: 0x13d890 waitForReboot+0x90 0xdffa9010: 0x13da8d fault_dump+0x67 0xdffa9030: 0x13d98d PANIC+0x29 0xdffa9040: 0x167bbb _ZN18Buffer_Cached_Pool17makeCachedBuffersEi+0 0xdffa9070: 0x13a67d _ZN19Memory_AddressSpace16makeCachedBufferEv+0 0xdffa9090: 0x167749 _ZN18Buffer_Cached_Pool15getAnyCachedBufEji+0x 0xdffa90c0: 0x7383ac _ZN17UnCachedIO_Object9readBlockEym16BlockIO_P 0xdffa9140: 0x631f07 _ZN14UFS_CgBlkEntry10finishTakeEv+0x137

Fix When CDMS attempted to access a file or directory from the original server and was returned a "stale file handle" error, 16 bytes of memory were allocated but never freed. With a large number of errors, the Data Mover eventually ran out of resources. This memory leak has been resolved.




Symptom Description

Applications using Celerra XML API received no QueryStatus if the application asked for Tree Quota Status, but no file systems were mounted. This issue led third-party applications to fail or timeout when performing this query.

Fix XMLAPI server now returns Query Status to TreeQuotaQueryParams requests, even if no file systems exist on the Celerra.



Version 5.6.38.2


Symptom Description

When loading the Data Mover's page, the data (table graph (cpu/mem)) for server_2 took over two minutes to load while the server_3 graph loaded quickly. This occurred when the Control Station's clock was set behind the user's system clock.

Fix Code now queries for the Control Station time and accounts for the time difference between the Control Station and the user's system before querying for data from Jserver.



Symptom Description

When trying to view the OSM log in Celerra Monitor (Celerra Monitor -> Expand Celerra folder -> Select OSM Log), the following error message was displayed in a pop-up window: The remote session has been disconnected on mo/d/y time. The program is attempting to reconnect to the server. In case of a Control Station server failure on a very large system, it may take up to 20 minutes. If you would like to continue, press 'Yes' of just wait, otherwise press 'No"' and exit the program.

Fix If /var/log/messages contain non-printable characters, Celerra Monitor will now strip them from the log content that is passed to Celerra Monitor. The original log files remain unchanged.



Symptom Description

Graphs within the Celerra Manager were intermittently not displayed. JServer reported indication processing errors when a VDM had a checkpoint that was mounted read-only. The Jserver log contained a message indicating the cache was not updated for this file system.

Fix Altered JServer indications processing code so that it detects when a checkpoint is mounted read-only on a VDM and non longer updates its VDM mounted file systems table.



Version 5.6.38.2


Symptom Description

The WebUI Task Status screen did not display task details for Replication V1 tasks.

Fix From the WebUI, when displaying properties for a Replication V1 task, the steps are now displayed.



Symptom Description

The apl_tm.log reported XML start and end tag mismatch errors when an attempt was made to delete 6000 or more alerts in one request. The following error message was displayed in the apl_tm.log: -:5:13:End tag does not match start tag

Fix This problem only occurred when a user attempted to delete 6000 or more alert messages simultaneously. Code has been modified to correct this problem.



Symptom Description

If there were multiple instances of the same alert and user tried to delete or accept them from the alert list on the Celerra Manager Home Status page, that particular alert was accepted or deleted, but the next duplicate alert was displayed, giving the appearance that accept/delete of the first instance was unsuccessful.

Fix This was fixed by applying a threshold mechanism to the alert to eliminate duplicates and limit the number of alerts that are posted to one every 6 hours until the problem is resolved. Events will still be logged in /nas/log/sys_log at the original rate.



Symptom Description

After creating a checkpoint through WebUI with the maximum SavVol value specified, the maximum storage capacity was not listed on the Checkpoint Storage tab of the File System properties page.

Fix The code now correctly sets the maximum SavVol value and the WebUI is updated properly.



Version 5.6.38.2



Symptom Description

When using the command server_cifssupport with the option -cred or -accessright on a Data Mover containing a standalone CIFS server or a NetBIOS (non compname) CIFS server, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 1d963b Err code: 0 Target addr: 0 **. The stack trace showed: 0x23281f4: 0x146c3c waitForReboot+0x90 0x2328214: 0x146e4f fault_dump+0x67 0x2328234: 0x13c56c handle_fatal_fault+0xa 0x2328260: 0xe2942c _ZN12xmlAuditUser10initDomainEv+0x1f4 0xc33c7910: 0xe2abdd

_ZN12xmlAuditUser24buildNtCredFromWindowsIdE11 0xc33c7ab0: 0xe2e59e

_ZN12xmlAuditUser7getUserEP14XmlElementNodebPK 0xc33c7b30: 0xe2ea48

_ZN12xmlAuditUser7getUserEP14XmlElementNodebPK 0xc33c7bd0: 0xe30142

_ZN12xmlAuditUser7getUserEP14XmlElementNodebPK

Fix The Data Mover will no longer panic under this condition.



Symptom Description

CIFS client received only one popup message for quota events per CIFS session. If a CIFS session was disconnected and reconnected, the user received another popup message, but only one.

Fix Code has been modified to restore ability to send popup messages to CIFS clients when a failure occurs. If the quota usage goes below the soft limit, a new popup will be send upon crossing the limit again during the same CIFS session.




Version 5.6.38.2


Symptom Description

Mac OS 10.5 clients running on Intel-based systems could not retrieve a list of CIFS shares. The Finder hung after connecting to the server until cancelled by the user. This occurred if the total list of shares was longer than 4096 bytes.

Fix The Data Mover now sends a correct MSRPC reply for shares enumeration exceeding the client's protocol limits, eliminating this issue.



Symptom Description

With MIXED_COMPAT access policy, how access is determined depends on where permissions were last set. If last set from UNIX, the mode bits are the true representation of access and the ACL is only for display. However, if the owner or group was changed from UNIX, access checking switched to the ACL. This changed the resulting access and no longer matched what was intended when permissions were last set.

Fix Now when using MIXED_COMPAT, if access checking for an object is done using the mode bits before the owner or group is changed from UNIX, this will not change after the operation.



Symptom Description

When attempting to connect through CFS, MACOS 10.5 clients joined to the Windows domain were challenged for a password, or could not connect if NTLM authentication was disallowed. Kerberos authentication failed, causing the user to fall back to NTLM authentication.

Fix Code now handles MACOS 10.5 Kerberos authentication properly by returning the expected Kerberos mechanism object identifier.




Version 5.6.38.2


Symptom Description

The server_cifssupport -cred command displayed the error The user <user> in the domain <domain> is not connected if the full domain name (i.e. "domain.com") was specified. The command worked as expected if the “short” domain name or the -build option was specified.

Fix The command now displays CIFS credential info properly when either full or short domain names are used.



Symptom Description

The Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 9aba2c Err code: 0 Target addr: 0 **. The stack trace showed: 0x1c8c2a4: 0x13e694 waitForReboot+0x90 0x1c8c2c4: 0x13e891 fault_dump+0x67 0x1c8c2e4: 0x138768 handle_fatal_fault+0xa 0x1c8c360: 0x9a0bf3 _ZN13smb_threadCtx5startEv+0x63b 0x942affe0: 0x142e3c Sthread_startThread_internal+0xe

Fix When an unsupported SMB command is received (SMB_COM_NT_RENAME for instance) it could result in the Data Mover using an uninitialized variable. The solution ensures that we don't use uninitialized data in this instance.



Symptom Description

If the cifsserver param in the cepp.conf or viruschecker.conf file is and IP address instead of a NetBIOS name, a Data Mover failover occurred.

Fix When an IP addr is specified in the param CIFSserver of cepp.conf or viruschercker.conf, code now uses the given IP addr and not the NetBios Name



Version 5.6.38.2


Symptom Description

Using the WebUI to perform quota management for a Data Mover which did not have a valid CIFS configuration caused the Data Mover to panic with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: abd170 Err code: 0 Target addr:1 **. The stack trace showed: 0x1cabea8: 0x13e6c4 waitForReboot+0x900x1cabec8: 0x13e8c1 fault_dump+0x670x1cabee8: 0x138798 handle_fatal_fault+0xa0x1cabf20: 0xa8273d

_ZN15sid_domainInfos6sameIdEP10smb_domain+0x190xca7cf8f0: 0xa7d9ed

_ZN11lookupQuery16getMappingFromDCEb+0x2670xca7cf9b0: 0xa7d51c _ZN11lookupQuery12getMSMappingEbb+0x4b60xca7cfb30: 0xa7d053 _ZN8uidQuery16lookup_cifsQueryEb+0x1030xca7cfba0: 0xa8101c _Z16xml_lookupFromIdP7macDatab+0x93c

Fix The Data Mover no longer panics in this situation. It verifies that a valid connection to a Domain Controller exists before performing the lookup SID call for quota management.



Symptom Description

Third-party CEPA (Celerra Event Publishing Agent) applications could not determine whether CEPA was enabled or disabled on a Data Mover.

Fix Added a virtual Windows Registry setting that can be read by applications - CEPP.Enabled. A setting of 0 indicates that CEPP is stopped, and 1 indicates that it is started.



Symptom Description

User privileges and system privileges were displayed in hexadecimal format in server_cifssupport -cred output. Users were unable to easily interpret the information.

Fix The value of each bit that compose the privilege mask is now displayed with a text description. The original hexadecimal value is still displayed as well.



Version 5.6.38.2


Symptom Description

Users found that copying a large number of small files with Windows XP, Vista, and Win2003 was slower than when copying from a Windows-based CIFS server. The clients opened each file, then quickly opened the file a second time, keeping the initial instance of the file open. When the already-opened file was opened a second time, the Celerra sent an oplock break notification to the client, but delayed it by up to 9ms. After opening thousands of files, these short delays had a noticeable impact.

Fix Celerra delayed sending oplock breaks until a file had been open for at least 9ms to help avoid known issues with Windows NT and Win9x. The Data Mover now only delays oplocks when talking to these types of clients - all others will be responded to immediately.




Symptom Description

The Data Mover was not checking the enabled/disabled status of GPOs, resulting in disabled GPOs still being applied. This affected either the "Computer configuration settings disabled" and "All settings disabled". The Data Mover uses only computer configuration settings, so user configurations settings were not affected. The problem can be worked around by changing the Link Enabled status of the GPO to No.

Fix Added a check of the flags which enable/disable user and/or computer settings per group policy.




Symptom Description

When using CAVA with non-ASCII CIFS server names, the server_viruschk command listed incorrect state for VC servers (CHECK_IN_PROGRESS, FILE_NOT_FOUND)

Fix Code now handles non-ASCII CIFS server names correctly.



Version 5.6.38.2


Symptom Description

If the bit 3 (symbolic link backup bit) of the parameter cifs acl.extacl was set, CIFS clients were unable to follow UNIX symbolic links.

Fix Code now only checks this bit when in backup mode and for all other cases CIFS clients can follow UNIX symbolic links.



Symptom Description

When a file was opened using Win32 API with the flag delete on close, the read-only bit was not checked. The file was not deleted on close and no error was reported.

Fix In this situation, the open now fails with the status CANNOT_DELETE



Symptom Description

When a server_dbms command was issued while the Data Mover was shutting down, or when the root file system was unmounting, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 0x00017d37ef Err code: 0 Target addr: 0x00be088b48 **. The stack trace showed: 0x119c500 _ZN7DskDump9checkdumpEPKc+0xa2 0x119a6b8 dump_return+0x4 0x167e42 waitForReboot+0x182 0x167fc2 fault_dump+0x8e 0x145635 handle_fault+0x1d 0x1837439_ZN12processTable7processEP14XmlElementNodeR 0x18385a1 _ZN11repairTable6actionEPKcP8db_tableP14XmlE0x381409 _ZN17macCCMDCommand_DB6invokeEPKcP7macDataRP8

Fix The Data Mover no longer panics in this situation, but the following error is reported: The internal database environment of this VDM cannot be initialized. Error: Stale handle.



Version 5.6.38.2



Symptom Description

After creating a new CIFS compname with an alias, the Aliases field on the CIFS Server Properties page showed the alias name with the phrase "last message repeated 1 times" appended to it.

Fix On server_cifs command, 'last message repeated 1 times' message is no longer displayed after the second alias name.



Symptom Description

After upgrading to NAS 5.6, Mac OS X 10.4 and 10.5 clients were unable to browse the list of shares via CIFS. Some Intel-based Mac users were unable to connect to shares at all, even when specifying a share name to connect to specifically.

Fix Corrected a number of issues that prevented OS X clients from listing shares.



Symptom Description

During configuration of the storage array IP address, the CSA configuration screen reported all command were successful but never continued. The "next " button" never became enabled to move on to the next section. Users needed to select the back button and go all the way back to the beginning where the MAC configuration was selected, then the application picked up where it left off and continued successfully.

Fix The hang in the Configuring Control Station no longer occurs.



Version 5.6.38.2


Symptom Description

While using Replication V1, when a user selected the remote system on the new VDM replication page, the page turned blank.

Fix The query being sent by APL to list remote VDMs was giving incomplete responses. The APL was not sending a possible ID (rootFilesystem) for all the VDMs name in the response. This caused a null to be inserted instead of the ID which resulted in a null pointer exception in the GUI code causing this new page to go blank. This has been fixed.



Symptom Description

The server_dns command did not report a usage error message when user provided either the -p or -d or -o options, but then failed to provide argument values.

Fix A usage error message is now displayed in this situation.



Symptom Description

SP public addresses were not changed to the public IP addresses specified during CSA configuration of an NS20FC even though the installation completed without any errors.

Fix The problem occurred because CSA continued until the end without stopping when IP configuration had failed because of a backend issue (such as one SP was down). The code has been modified to have a verification for successful completion of IP configuration step before moving forward, preventing the issue.




Version 5.6.38.2

CORE The following entries describe fixed problems related to the Celerra Data Movers:


Symptom Description

Host clients lost access to CIFS shares after a Data Mover reboot due to an incorrect CIFS server configuration. This was caused by an inconsistency in the way the Data Mover and the Control Station truncated certain CIFS configuration properties.

Fix Code now ensures that CIFS server properties: name, domain, aliases, etc., get truncated and correctly recorded on the Control Station.



Symptom Description

When using the Celerra Startup Assistant, users didn't always detect that activity was occurring after cable check had completed and hit the "Next" button repetitively.

Fix The "Next" button is now disabled when the NAS service check is running and is enabled again if any problem is reported.



Symptom Description

If a user exported an NFS file system with more than 8192 characters of export options, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../malloc.cxx at line: 327 : Memory corrupted. The stack trace showed: 0xc2013b60: 0x13d8bc waitForReboot+0x900xc2013b80: 0x13dab9 fault_dump+0x670xc2013ba0: 0x13d9b9 PANIC+0x290xc2013bb0: 0x188675 free+0x690xc2013be0: 0x188c94 _ZdlPv+0x100xc2013bf0: 0x1fbe94 _Z17splitOptionStringPcRS_S0_S0_+0x1ea0xc2013c10: 0x1fc366 _Z13exports_queryP7macData+0x3160xc2013c70: 0x1fd55e _Z11xml_exportsP7macData+0x230

Fix The code no longer allows options list to be longer than 8K, preventing the panic.



Version 5.6.38.2



Symptom Description

When FileMover was configured with a local CIFS connection to another file system on the same Data Mover and either one of the following conditions were true:1. NFS or CIFS clients were reading offline files that had a Read Policy of “passthrough”2. NDMP backup was running with EMC_DATA=”Y”, forcing backup to read the offline data instead of

the stub file attributes

Clients (including NDMP processes) received read errors or the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../cifsclient_msg.cxx at line: 197 : Not connected to a server. The stack trace showed: 0xde13d880: 0x13d890 waitForReboot+0x900xde13d8a0: 0x13da8d fault_dump+0x670xde13d8c0: 0x13d98d PANIC+0x290xde13d8d0: 0xad5584 _ZN6SmbMsg4sendEi+0x1c0xde13d8f0: 0xad5541 _ZN6SmbMsg7processEv+0x170xde13d910: 0xae78f2 _ZN13SmbRemoteNode5closeEv+0x8a0xde13d970: 0xbbbf0f

_ZN17DHSM_CIFS_RemoteP15remoteBlockReadEjR11Fi0xde13da30: 0xbbaabe

_ZN10DHSM_Vnode15remoteBlockReadEjR11File_Stat

Fix The Data Mover CIFS client was updated to ensure data is properly read in pass through mode.




Symptom Description

Vista clients crash (blue screen) when accessing FileMover offline files if the secondary storage was unavailable. Earlier versions of Windows were unaffected.

Fix When this occurred, the Data Mover returned a message to CIFS clients with an error, but also with a non-zero data length. The Data Mover now returns a data length of zero (as no data is returned to the client).



Version 5.6.38.2





Symptom Description

Users were unable to access some offline files but there were no messages logged in the server log. From the secondary storage, no request for the offline data was received from the Celerra for the files with the problem. Other offline files in the same directory had no problem being accessed.

Fix The offline files that could not be accessed had a flag set in the file system indicating they were in the process of being deleted. This flag prevents Celerra from attempting to access the offline data for the file. The flag is no longer used in the case of passthrough FileMover connections.



Symptom Description

iSCSI remote restore hung when a synchronization error occurred during a reverse copy. The error was not reported to the user.

Fix The synchronization error is now handled and returned to the user and the remote restore operation is rolled back.



Symptom Description

After an upgrade to 5.6, the first attempt to dialhome (either testing or a real event) was successful, but all subsequent attempts failed. If the modem was reset(off/on), then the first attempt worked again.

Fix This problem has been resolved and all dialhome events are processed correctly and dialhomes are generated.




Version 5.6.38.2


Symptom Description

The system didn’t check whether disk volumes were of supported RAID types prior to marking them for use by Celerra. Additionally if disk volumes were of supported RAID type but were somehow modified to an unsupported type using standard CLARiiON tools there could be unintended side affects including failed upgrades with : Error 5008: server_2 : clar_r5_performance : storage pool has members which do not have consistent disktype.

Fix Disk volumes built from unsupported RAID configurations or meta LUNs will no longer be marked for use by Celerra. When detected during diskmark, a health check warning will be generated but the disk will not be added to the Celerra database.In addition heath checks have been added and will fail with an error for any existing disk volume which meets the following criteria.• Is built from a Meta LUN• Is built on an unsupported RAID configuration AND• Is used in a system defined AVM pool• Is not in-useThe following error is displayed when the nas_storage -check -all command fails: Error 5017: storage health check failedAPM00070204288 d13, metaLUN, doesn't match any storage profile.Other disk volumes built from unsupported RAID configurations will continue to function and will not affect upgrades.




Symptom Description

The upgrade from NAS 5.5 to 5.6 succeeded on the primary Control Station but failed on the secondary Control Station while upgrading Linux. At the point of failure, the following error message appeared in a dialog box on the system console: Duplicate Labels: Multiple devices on your system are labelled /. Labels across devices must be unique for your system to function properly. Please fix this problem and restart the installation process.

Fix To address this issue, code was changed in the following ways: (1) Assign unique labels to disk partitions during upgrades as well as fresh installs. (2) Allow duplicate partition labels in cases where the duplicates would not affect system operation. (3) Scan RDF LUNs for preexisting labels, but ignore errors that occur when attempting to format read-only R2 LUNs during fresh installs.



Version 5.6.38.2


Symptom Description

The nas_checkup command did not check inode usage in the root file system of a Data Mover or Virtual Data Mover (VDM). The inode usage on the root file system was greater than 90%, yet the nas_checkup passed. It should have been flagged as a critical problem.

Fix Added additional PUHC /PAHC checks for Data Mover/Virtual Data Mover space/inode usage.



Symptom Description

After a fresh install or upgrade to 5.6, if a second Data Mover was added and the Control Station was rebooted, the Control Station lost access to the internal network.

Fix Modified the upgrade procedure to deal correctly with the upgrade.



Symptom Description

If the CLARiiON generated an event that contained special characters, such as parentheses, the event did not trigger a callhome. This problem occurred on Fibre Channel and integrated systems.

Fix This problem has been resolved.



Symptom Description

During installation or upgrade, the /nbsnas directory was created on a CFS/CNS system, which is not applicable to CFS/CNS systems.

Fix Code now removes /nbsnas directory during upgrade of CFS/CNS systems.



Version 5.6.38.2

MirrorView The following entries describe fixed issues related to MirrorView:



Symptom Description

During an upgrade to 5.6, when the upgrade process issue a command to stop 'crond', the script waited 10 seconds and then checked the status of the crond. If it had not stopped after 10 seconds, the following error was issued: Error : Failed to stop crond.Action: Follow these steps to resolve the problem: 1. Exit from the upgrade process. 2. Reboot the Control Station.

Fix Ten seconds was not long enough to wait for the 'crond' to stop. Code now waits up to a minute, periodically polling the crond to see if it has stopped. If it stops within the allotted minute we continue with the upgrade. If the crond has not stopped within the minute, we then issue the same error message.



Symptom Description

If an entry already existed in the nas_cel table, the nas_cel command did not continue to populate/update all remaining fields of the entry. Subsequently, the missing entry caused the nas_mview -init command to fail.

Fix The nas_cel -create/-update command now validates the mount_dev field even if the nas_cel entry already exists.




Version 5.6.38.2


Symptom Description

While running a Data Mover failover on a system using NDMP, the Control Station failed over (or, on single-control station issues, rebooted) due to out of memory issues, causing the failover process to fail. This was more likely to occur on systems with very large configurations or smaller amounts of Control Station memory (such as the CFS-14).

Fix The NDMP handler used during failover was enhanced to limit the amount of memory it will use at any given time, helping to prevent this issue.



Symptom Description

After upgrading to Celerra Network Server version5.5, NDMP backups were automatically aborting full / incremental backups on backing up 512kb with medium errors. The following error is seen in the server_log: 2007-08-23 14:57:14: CAM: 3: cdb: 0a 00 00 f0 00 00 00 00 00 00 00 00 | SCSI ERR ON #4800 camstat 0x84 bstat DeviceError | scsi stat.skey.ascq 0x02.03.3b00 Check condition | skey [ ] Medium error _____ ascq Sequential positioning error 2007-08-23 14:57:14: NDMP: 3: DartTapeInterface: write error 2007-08-23 14:57:14: NDMP: 3: Tape write error: No error reported . In prior releases, Celerra sent an error of weof failed to the NDMP host when this event occurred, but no longer does. NetWorker relies on this error, and when it didn't receive the error, it could not mark the volume to full and skip it. Instead, backups failed, and Networker attempted to reuse the bad tapes in future backups.

Fix Media errors are now reported with ndmp_mtio commands and Legato Networker marks tapes as "full" as expected.




Version 5.6.38.2


Symptom Description

While running a Data Mover failover on a system using NDMP, the Control Station failed over (or, on single-control station issues, rebooted) due to out of memory issues, causing the failover process to fail. This was more likely to occur on systems with very large configurations or smaller amounts of Control Station memory (such as the CFS-14).

Fix The NDMP handler used during failover was enhanced to limit the amount of memory it will use at any given time, helping to prevent this issue.



Symptom Description

Running multiple Volume-Based Backup (VBB) restores simultaneously resulted in an out-of-memory condition. This caused the Data Mover to panic with the following DART panic/fault message: >>PANIC in file: ../addrspac.cxx at line: 275 Out of memory. The stack trace showed: 0xfc18be70: 0x13d890 waitForReboot+0x90 0xfc18be90: 0x13da8d fault_dump+0x67 0xfc18beb0: 0x13d98d PANIC+0x29 0xfc18bec0: 0x139766

_ZN19Memory_AddressSpace10allocPagesEi12Memory 0xfc18bee0: 0x856114 _Z11GetBlockBufv+0x80 0xfc18bf10: 0xc93b9c

_ZN18vbbRestoreFileDataC1EP13vbbDataModulePP15 0xfc18bf40: 0xc92b87 _ZN14vbbFileRestore11RestoreDataEv+0x41 0xfc18bf70: 0xc9185a

_ZN14vbbFileRestore12startRestoreEv+0x218. VBB took memory from a shared buffer pool, but memory was not pre-allocated for VBB, only other applications.

Fix VBB restore buffers have been changed to prevent this out-of-memory conditions.




Version 5.6.38.2

Networking The following entries describe fixed issues related to Networking:


Symptom Description

The Data Mover panic was caused by an unstable network link during link up/link down event processing. When a link is unstable and bounces continuously, the Data Mover enters a subroutine that loops and waits until the link is stable. In this case, the link was never stabilized, the Data Mover entered an infinite loop, and eventually Watchdog thread panicked the Data Mover. DART panic/fault message: >>PANIC in file: ../sched.cxx at line: 823 : SYSTEM WATCHDOG. The stack trace showed: 0x3857f34: 0x13d890 waitForReboot+0x900x3857f54: 0x13da8d fault_dump+0x670x3857f74: 0x13d98d PANIC+0x290x3857f84: 0x13f71f system_watchdog+0x770x3857f94: 0x13770d _t_nmi+0x630x3857fe0: 0x14105c Sthread_startThread_internal+0xe

Fix To fix this issue, a loop limit was added in the subroutine that handles link up/link down event processing when links bounce.




Symptom Description

If a DNS server responded to a Data Mover, but responded with a server failure error code, the Data Mover did not mark the DNS server as down. If a single DNS server entered a state where it could not respond properly, the Data Mover did not attempt to contact other, potentially working, DNS servers.

Fix The Data Mover now switches to alternate servers upon receiving the server failure error code.




Version 5.6.38.2



Symptom Description

Users lost access to NFS and CIFS shares until the Data Mover was rebooted. The following messages were seen in the server_log:2008-03-14 03:46:50: CFS: 3: System runs out of vnode2008-03-14 01:37:37: LOCK: 4: 2: 99% nodes are consumed by

file locks2008-03-14 01:37:37: LOCK: 4: Possibly entropic clients: <list

of IP addresses that held NFS locks>The list indicated that a single client held an excessively large number of NFS clients. This problem also could have been resolved by rebooting that client, or otherwise clearing its NFS locks.

Fix NFS Clients were able to exhaust all 256000 vnode resources in a Data Mover by opening a large number of NFS locks. To help prevent a small number of clients from having this kind of impact, the system now refuses locks if more than 90% of vnodes are consumed by locks, reserving vnodes for other critical use.




Symptom Description

After modifying an ACL from both NFSv4 and CIFS, NFSv4 "owner@" and "group@" ACEs were lost.This problem occurred when:• An NFSv4 user placed owner@ or group@ ACE on a file• When the ACL was presented to CIFS users, they saw the ACE as the name of the current

owner/group instead of a "special" ACE. CIFS users were able to modify the ACL. The ACEs for owner or group was played back to the Celerra as the actual user/group name instead of special "owner@" ACEs.

When NFSv4 users viewed the ACL, it contained ACEs for the current owner or group of the file, not "owner@" or "group@". If the owner or group of the file changed, the ACEs were no longer applied to the new owner, but continued to be applied to the old owner.

Fix If an ACL contains an entry for the current owner or group of a file, it is now presented to NFSv4 clients as user@ or group@ ACEs.




Version 5.6.38.2


Symptom Description

Solaris NFSv4 clients received permission denied errors when attempting to view ACLs on files. This occurred even though the user had permission to view ACLs of the file.

Fix Users that have permission to view ACLs can now read the ACL with NFSV4, but cannot modify it.




Symptom Description

When using NFSv4, the Data Mover panicked with the following DART panic/fault message: Assertion failure: 'db_ref > 0' on line 951 in file '../include/stream.hxx' >>PANIC in file: ../assert.c at line: 26 : assert failed. The stack trace showed:0xc7e47c10: 0x13d664 waitForReboot+0x900xc7e47c30: 0x13d861 fault_dump+0x670xc7e47c50: 0x13d761 PANIC+0x290xc7e47c60: 0x188b81 _assert+0x510xc7e47c80: 0x160e68 _ZN5datab7freeRefEv+0x420xc7e47ca0: 0x555329

_ZN11NFSv4_Owner9saveReplyERP4msgb8nfsstat4i+00xc7e47cd0: 0x55a5f3

_ZN11NFSv4_State5closeEmP8stateid4P8nfs4_ctxRP0xc7e47d50: 0x558403

_ZN16NFSv4_StateTable5CloseEmP8stateid4P8nfs4_

Fix The problem occurred if an NFSv4 client issued a file close request, then issued the same request again before the first had completed. This happened if the Data Mover was delayed in closing a file for any reason, and hadn't completed before the client retransmitted the request. The Data Mover will no longer panic in this case.




Version 5.6.38.2


Symptom Description

After an upgrade to 5.6, clients were unable to connect to NFS export if a file system was exported to a netgroup containing nested netgroups.

Fix Nested netgroups are now resolved properly when using LDAP as a name resolution source.




Symptom Description

After using NFSv4 clients, a Data Mover became unresponsive to NFSv3 and NFSv4 clients until the Data Mover was rebooted or failed over. This was triggered by clients not reading the data over the same path the delegation callbacks were sent on.

Fix Code has been enhanced to prevent the Data Mover from hanging under this condition.




Symptom Description

If an NFS client mounted an export twice without sending an unmount in between, the client's access rights were not re-evaluated when the second mount was received. Clients typically never send a MOUNT request without an UNMOUNT, but this could happen if a client crashed and rebooted before UNMOUNT was done, if network problems prevented the MOUNT from being received, etc.

Fix Celerra will now re-evaluate host access rights (read/write, root access, etc) if it receives a new MOUNT request but believes the client already has the export mounted.




Version 5.6.38.2



Symptom Description

When running the fs_replicate -reverse command using an interface name such as "fsn0:0", the replication failed . This was due to the fact that a colon ":" was used as delimiter by the command.

Fix Code now blocks naming an interface with a ":" character.The command will now fail and an error will be logged in the server log.




Symptom Description

When the nas_task –info command was issued, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: f2858c Err code: 0 Target addr: c **. The stack trace showed: 0x1cb9c64: 0x13eec4 waitForReboot+0x900x1cb9c84: 0x13f0c1 fault_dump+0x670x1cb9ca4: 0x1387a0 handle_fatal_fault+0xa0x1cb9d10: 0xf23775

_ZN3Cmd7executeEP10DicXmlDataRP8CCMD_Msg+0x150xda1108e0: 0xf1e524

_ZN12CmdContextDb23executeTasksListRequestEP100xda110920: 0xf1c5a2

_ZN10CmdService16handleTaskObjectEP10DicXmlDat0xda110a00: 0xf1c14e

_ZN10CmdService7executeEP10DicXmlDatai+0x920xda110a30: 0xf1338a

_ZN18DicXmlAsyncService7executeEP17dicIncoming

Fix The issue was fixed and Data Mover no longer panics on the nas_task –info command.



Version 5.6.38.2


Symptom Description

When a Replicator v1/v2 upgrade was attempted after a local failover replication, the user got a "Control Station database is corrupted" error. This was due to an inconsistency in the in the AVM database caused by volume groups not being deleted when they should have been.

Fix Code now locks the volume groups prior to calling the delete function. This allows the volume groups to be deleted correctly.



Symptom Description

Using Replicator V2, when trying to do a nas_copy using the -from_base option, instead of doing a differential copy from the base provided, a full copy was done.

Fix User specified checkpoint with -from_base option is directly accepted as common base and a differential copy is done with the user specified source.



Symptom Description

While using the CLI, if the nas_replicate -create command was issued twice at the same time from the Control Station, one instance of the command succeeded while the other hung.

Fix Code will now fail one of the duplicate create commands to prevent this hang condition.



Symptom Description

User issued a Replicator V2 swithchover operation and then deleted the DART interconnect from the source side. The same local replication session was listed twice in the CLI and GUI. Both the source side and destination sides of the replication were visible.

Fix With this fix, the same replication session ID is no longer reported.



Version 5.6.38.2


Symptom Description

If replication commands were issued for the same session simultaneously on the source and the destination, the Control Station event log was full of messages indicating HTTPD service and DIC_D pool were blocked. The following is an example message: Jan 3 09:23:51 2008:DART:KERNEL:ERROR:3:Slot2:::1199370231: ThreadsServicesSupervisor: Service:HTTPD Pool:DIC_D BLOCKED for 243610 seconds: Server operations may be impacted .

Fix The command issued to the source side now logs an error and the command is rejected.



Symptom Description

When configuring an interconnect, it could be configured with a large number of source and destination network interfaces. In this scenario the interconnect validation command on the Control Station timed out and failed prematurely with an error similar to: $ nas_cel -interconnect -validate id=40003 validating...failed Error 5005: server_4 : Timed out. The issue was caused by a Control Station command that had a constant timeout for interconnect validation. When number of interfaces is large, it takes longer to validate the interconnect.

Fix As a solution for this issue, the timeout on the Control Station is now a variable value and is dependent on number of interfaces configured in the interconnect. This prevents the premature time out failure of the validation command.



Symptom Description

Deleted V2 replications were still visible in the replication list page displayed in the Celerra Manager. When user selected one of the replications that was just deleted and tried to display its properties, nothing happened. User waited nearly 20 minutes and nothing ever displayed on the page. This problem only occurred if the Replication delete operation failed unexpectedly.

Fix When there is an error (session not found or any other error) returned from the Control Station when queried for a replication properties page, Celerra Manager now displays the following error message to the user: The specified replication session ID or alias name was not found.



Version 5.6.38.2


Symptom Description

While using Replicator V2, the wizard displayed file systems that were in use by other replication sessions in the list of available existing file systems. If the existing file system was already in use, users had to continue through all the way to the end to wait for the error (file system is in use by other replication).

Fix Existing file systems that are used in any other replication are no longer displayed in the Destination FS list.



Symptom Description

Some conditions (like out of space on the root file system of the Data Mover ) resulted in Replicator V2 database write failure. These failures were not being handled properly when the nas_replicate -reverse command was executed. This caused replication to fail instead of recovering when the condition was corrected.

Fix The nas_replicate -reverse command now retries the operation until the condition causing database write failure is resolved



Symptom Description

While using Replicator V2, the replication session encountered an error that halted progress. This problem occurred because the source side of replication was reporting inactive and the destination side was reporting stopped. This caused the START button to be highlighted and selectable, but failed if selected.

Fix In this case the START button should not be selectable because the source side is inactive. This has been fixed.



Version 5.6.38.2


Symptom Description

When a V1 File Level Retention (FLR) file system replication was deleted from the Celerra Manager, the restart checkpoints that the system created while starting the replication were not deleted. The abort (Delete from Celerra Manager) could be seen in the cmd_log: 2008-03-04 16:29:31.019 db:0:5938:S: fs_replicate -abort id=40,id=78. There was nothing else in the /nas/log/cmd_log after the above command.

Fix When a replication for FLR file system is deleted from the Celerra Manager, the internal checkpoints that the system creates while starting the replication are now deleted.



Symptom Description

When a user attempted to delete or accept an alert via Celerra Manager, user received the following error: Accept alert(s). Alert accept failed. Failed to find alert. Alert may have been altered by a different user session.

Fix The DART code which populates the alert value included a new line (thus breaking up the Alert) which caused only a part of the alert to be passed as an argument. The fix ensures that the alert value is on a continuous line. When the execution to delete an alert is passed, the value sent matches correctly with the value in the database.



Symptom Description

After starting a Replication v2 Loopback nas_copy and rebooting the Data Mover, the copy operation appeared to never complete. It also displayed incorrect status information for "Full Copy", time complete, and other stats.

Fix This problem occurred if the copy was completing when the Data Mover rebooted. The replication recovery process did not properly identify the state of the copy operation, and prevented the copy from completing. The code has been updated to prevent this condition.



Version 5.6.38.2


Symptom Description

When a local abort was run on a create Replicator v2 session task, the task was not being properly cleaned up.

Fix A local abort of a create task will now properly clean up the task on the local side.



Symptom Description

When a replication create task was aborted on the destination of a local session, the source was not cleaned up. This could also happen if a local Replicator v2 session was stopped and deleted on the destination and then the destination file system was also removed.

Fix Local stop and delete operations will now succeed even if the other side isn't present.



Symptom Description

User was unable to start a replication session from the WebUI, but could start the replication session using the CLI. If a Replicator V2 session was stopped and the source VDM was moved from one Data Mover to another Data Mover, the following error is logged : Error 13422034974: Invalid remote Celerra id 0.

Fix This is fixed and the replication session now starts correctly.



Symptom Description

When users attempted to create or modify a Replication v2 bandwidth schedule and specified an end-time of 08:00 or 09:00, the command failed with: Error 13160415800: The specified bandwidth schedule argument is mal-formed.

Fix Users can now specify an end-time of 08:00 or 09:00.



Version 5.6.38.2



Symptom Description

If a user attempted to stop a Replication v2 session before creation had finished, the session create operation appeared to hang.

Fix The code was updated to remove the deadlock that resulted in this condition.



Symptom Description

The "Previous Rate" fields in nas_replicate -info output always showed values of zero.

Fix The previous transfer/read/write rates and average read/write rates are now populated as expected.



Symptom Description

If a SCSI inquiry command was issued to the backend timed out, the Data Mover panicked if the storage array answered the request at the same time that the timeout occurred. DART panic/fault message: >>PANIC in file: ../volume.cxx at line: 7608 : Physical device has been disconnected. The stack trace showed: 0xb806f890: 0x13d890 waitForReboot+0x90 0xb806f8b0: 0x13da8d fault_dump+0x67 0xb806f8d0: 0x13d98d PANIC+0x29 0xb806f8e0: 0x732dbb

_ZN11BasicVolume17checkSerialNumberEv+0x15d 0xb806f9f0: 0x72e7a1 _Z13volumeCommandR6Option+0xedd 0xb806fbf0: 0x16863b

_ZN11cfgcmd_desc6invokeEPKcPP11CCMDMessageii+0 0xb806fc60: 0x20ccc2 _Z10xml_cfgcmdP7macDataRP8CCMD_Msg+0x38e

Fix When an inquiry command times out, code now modifies the data field to prevent the inquiry data from being misinterpreted as valid. This will prevent this type of panic.




Version 5.6.38.2



Symptom Description

When doing large I/O requests (512 KB or greater) it was possible that double allocations of memory were needed. Only one of these entries was freed which caused a memory leak and eventually the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../addrspac.cxx at line: 275 : Out of memory. The stack trace showed: 0xee48f5d0: 0x13d600 waitForReboot+0x900xee48f5f0: 0x13d7fd fault_dump+0x670xee48f610: 0x13d6fd PANIC+0x290xee48f620: 0x1394d6

_ZN19Memory_AddressSpace10allocPagesEi12Memory0xee48f640: 0x16bdcb

_ZN20Buffer_Uncached_Pool10addBuffersEmim+0x970xee48f680: 0x16bce4

_ZN20Buffer_Uncached_Pool14getUncachedBufE15St0xee48f6a0: 0x16aa04 allocb+0x72

Fix The code now monitors for this condition and makes sure both allocations are freed once they are no longer being used.




Symptom Description

When a file system was corrupted so that two or more inodes pointed to the same unnamed stream, file systems could not be unmounted, or a Data Mover panicked with a message similar to the following:- Assertion failure: 'useCount == vnodePtr->useCount' on line 903 in file '../vfsnode.cxx'- PANIC: unexpected node state in release()

Fix The problem was related to file system corruption where inodes were corrupted and referenced the same unnamed stream. The DART code did not handle a many-to-1 mapping of inodes to unnamed streams, and subsequently reference counts got confused, and panics and unmount hangs were happening. The fix now handles the case where multiple inodes map to the same unnamed stream.




Version 5.6.38.2

:

:


Symptom Description

NDMP backup excluded files/directories whose name had the same initial characters as the checkpoint virtual directory name. For example, with default checkpoint virtual directory name (.ckpt), files named .ckpt.lnk were not backed up.

Fix Code now excludes only the checkpoint virtual directory from backup and allows other files.




Symptom Description

User got Permission Denied error when a mounting file system via NFS. The file system was in the server export list but did not appear in the showmount command output.

Fix This problem was due to a duplicate entry in the export database. Code has been modified to prevent these duplicate entries.




Symptom Description

CIFS threads became blocked, eventually leading to CIFS users having no access. This occurred when a directory was being renamed at the same time as its parent directory was being deleted.

Fix Locking was added to eliminate this race condition.




Version 5.6.37.6

:

Version 5.6.37.6

CDMS The following entries describe fixed problems pertaining to Celerra Data Migration Service:


Symptom Description

A Data Mover became deadlocked when an NFS client was trying to create a new file, if the Data Mover's vnode free list was empty and a replication pause request was executed on the file system opened by the NFS client.

Fix Code now requests an exclusive file system lock instead of just taking the lock. An error "File_Busy_File_Status" is returned if a lock is already held, otherwise the lock will be granted.




Symptom Description

During CDMS NFS migration, memory corruption or page fault caused the Data Mover to panic with the following DART panic/fault message: >>PANIC in file: ../malloc.cxx at line: 327 : Memory corrupted. The stack trace showed: 0xce4c5a10: 0x13d890 waitForReboot+0x90 0xce4c5a30: 0x13da8d fault_dump+0x67 0xce4c5a50: 0x13d98d PANIC+0x29 0xce4c5a60: 0x188789 free+0x69 0xce4c5a90: 0x188da8 _ZdlPv+0x10 0xce4c5aa0: 0x188dbe _ZdaPv+0xc 0xce4c5ab0: 0xb97f95 _ZN14RemoteDirEntryD1Ev+0x5b 0xce4c5ac0: 0xba9ef1

_ZN21Remote_Protocol_NFSV313remoteDirReadERPvR

Fix The cause of this panic was an uninitialized member of an attributes structure. If the secondary server fails a request for any reason (permission, stale handle, other error), the Data Mover could panic as we may attempt to free an uninitialized pointer. This problem no longer occurs.




Version 5.6.37.6




Symptom Description

After upgrading to version 5.6, jserver failed to start, preventing Celerra Monitor from loading. This occurred if the Celerra had an attached Symmetrix with an unused paired BCV mirror device.

Fix Checks for the unused BCV device returned a null value to jserver, which did not handle the null value. Updated code to add a Null check to handle the device properly.




Symptom Description

If an attempt was made to restore a file system from a given checkpoint and the maximum number of checkpoints has already been created, the restore failed as expected, but the following error message was confusing: "Restore checkpoint ckpt_0001. An unknown error has occurred. details..."

Fix The error message has been updated and now reads: "Maximum of 96 ckpt for ckptfs1 exceeded*" .



Symptom Description

Jserver was not starting and reported "hd = null" error messages in the log file. Due to a large amount of Symmetrix devices which weren't in the sequential order, the old logic to get a Symmetrix device was using a loop count which introduced a parsing problem.

Fix The code has been modified to use the Symmetrix device number coming from the SYMAPI database, instead of using the loop count, and eliminates this problem.




Version 5.6.37.6


Symptom Description

When a checkpoint schedule was created before the Daylight Savings Time transition time but ran after the DST transition, the Control Station CPU ran at 100% and rebooted repeatedly. This was caused by a process which got stuck in a loop while calculating the next run time for the schedules. The problem only occurred in time zones where the DST transition time caused the time 00:00:00 to be skipped during DST transition (Brazil/East for instance).

Fix The function was changed to explicitly ignore the Daylight Savings Time feature while calculating the next and previous days.




Symptom Description

On the Celerra Manager alert list page, ‘schedule failed’ alert was showing “task (0)” in the description. If user right-clicked on that particular alert, it showed a link for task properties which led to the wrong task properties page.

Fix Adding the following new error for scheduled_task_failed_event when task id is 0 (zero): "Unable to get task id with failing schedule." and the task ID is no longer displayed on UI alert list page.



Symptom Description

When the replication destination Control Station was down or not accessible, requests to delete the suspended replication failed. The delete process was trying to delete internally created restore checkpoints that were created by a suspend action on the destination side. The delete process failed as it could not form the name of these checkpoints that consisted of a destination ID, because the destination Control Station was not accessible.

Fix Added additional checks to ensure the destination ID is available in order to form the restore checkpoint name. If not available, the restore checkpoint will not be deleted, and the replication session deletion will complete successfully. In this case restore checkpoint will remain on the destination system until they're manually deleted by the user.



Version 5.6.37.6


Symptom Description

When checking task status from the Celerra Manager, user received the error Invalid action response from Celerra Manager agent for task query tasks all. This occurred after renaming a schedule in the GUI.

Fix The rename function was fixed to replace the old schedule's name with the new name inside the schedule task file.




Symptom Description

Jserver issues commands to synchronize its in-memory version of CLARiiON status with the SymAPI database. If this operation took longer than 5 minutes, these synchronization tasks started to queue, and eventually failed.

Fix Jserver now first runs a few simple commands to determine if state has changed and a full resync needs to occur. Resync only occurs if changes (such as trespassed LUNs) have occurred since the last sync.



Symptom Description

While using Celerra Manager, the command services failed to process requests if the apl_task_mgr was stopped while the command services was in the middle of building the Admin Role Cache.

Fix Modified the way the authorization caches get updated to go through a single routine to decide which files need to be updated and to send the appropriate update requests (one at a time to ensure that APL isn't working on two requests at once from task 3).



Version 5.6.37.6


Symptom Description

While using Celerra Manager, If macstat was unable to establish a socket with the Data Mover, usually due to the Data Mover being off-line, the following exception was seen in system log: java.lang.Exception: Could not start macstat.

Fix JServer has been modified to retry 3 times in 10 second intervals. On the first retry, a message will be logged. On the second retry, a message will be posted. On the last retry, a java exception will occur indicating a Data Mover is not responding. These messages can be seen in the system_log.



Symptom Description

Deleting a group of users by selecting them from the admin user list page, then clicking the delete button left home directories on the /home on the Control Station.

Fix After the deletion task has completed successfully, the user's home directories are now removed from /home on the Control Station.



Symptom Description

The Celerra XML API v2 did not return the proper status for serviceState="off".

Fix The correct service state is now returned to the XML API client. The CLI (server_http command) was not impacted by this issue.



Version 5.6.37.6

CFS The following entries describe fixed issues pertaining to the Celerra File System:


Symptom Description

When the home directory of a user was deleted via the CLI and that user was deleted via the Celerra Manager, the following error was returned: "User not deleted". The user was deleted out of /etc/passwd but not out of /nas/site/user_db.

Fix The user is now deleted from both the /etc/passwd and the /nas/site/user_db.



Symptom Description

The Storage Pool Properties page in Celerra Monitor took a long time to load, in this case 8 minutes.

Fix Code has been modified to make use of storage pool ID, if provided in request, to reduce the time required for execution of request.



Symptom Description

When changes were being made to a directory located on a file system that was being unmounted, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: 8963d0 Err code: 0 Target addr: 0 ** . The stack trace showed: 0x1c89af4: 0x13e694 waitForReboot+0x90 0x1c89b14: 0x13e891 fault_dump+0x67 0x1c89b34: 0x138768 handle_fatal_fault+0xa 0x1c89ba0: 0x8b6ae8 _Z12ftpd_unmounty+0xa8 0xffd53d90: 0x643eb6 _ZN15unmountCallBack7executeEy+0x20 0xffd53db0: 0x644b17 _ZN14VFS_FileSystem10unmountNowEi+0x41 0xffd53dd0: 0x647598 _ZN14VFS_FileSystem6freezeEv+0x1c6 0xffd53e00: 0x11a262a _ZN15VvsOpConditions24execRefreshPreCondition

Fix Code now protects change of currentdir and rootdir by the open mutex. The unmount will wait for the operation “change dir “ to finish (it does not take a long time, just a few microseconds), and the Data Mover will no longer panic due to this condition.



Version 5.6.37.6



Symptom Description

When processing a GPO update, the Data Mover panicked with the following DART panic/fault message: *** Invalid Opcode exception. Virt ADDRESS: 0 ***. The stack trace showed: 0x170f8f8: 0x13d890 waitForReboot+0x90 0x170f918: 0x13da8d fault_dump+0x670x170f938: 0x137b3c handle_fatal_fault+0xa. A pointer used to identify the start of a binary blob was not being updated correctly. If there were two end brackets in the blob, the code looped through the blob twice. The Data Mover panicked since the pointer was not updated, and was pointing at some random location.

Fix The code now updates the pointer and correctly distinguishes between end brackets in the data and the delimiting end bracket for the blob.




Symptom Description

For unknown reasons, some applications tried to connect to an invalid share name (containing Unicode characters from the High Surrogate range which is unsupported). This created a memory corruption which was later seen if/when the corrupted object was deleted. The Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../malloc.cxx at line: 327 : Memory corrupted. The stack trace showed: 0xe120d4a0: 0x13d890 waitForReboot+0x900xe120d4c0: 0x13da8d fault_dump+0x670xe120d4e0: 0x13d98d PANIC+0x290xe120d4f0: 0x188751 free+0x690xe120d520: 0x188d70 _ZdlPv+0x100xe120d530: 0x188d86 _ZdaPv+0xc0xe120d540: 0x656ca6 _ZN15UFS_DirHashInfoD2Ev+0x580xe120d560: 0x659c4c _ZN20UFS_DirHashInfo_dir3D0Ev+0x34This also resulted in high CPU utilization when client connected (due to a large memory scan process).

Fix Code now uses a new mechanism to verify that share name and path is fully I18N compliant before using them. Share name and path that can not be translated are now rejected.




Version 5.6.37.6


Symptom Description

If a client machine connected using UID (User ID) -2 and quotas were enabled for a file system, the Data Mover panicked with the following DART panic/fault message: *** Divide exception. Virt ADDRESS: de930e ***. The stack trace showed: 0x170df3c: 0x13d890 waitForReboot+0x90 0x170df5c: 0x13da8d fault_dump+0x67 0x170df7c: 0x137b3c handle_fatal_fault+0xa 0x170dfd0: 0xde9249 __udivdi3+0x29 0xedff5c30: 0x9a78fc

_ZN13smb_threadCtx17callTrans2QFsInfoEP4msgbPc 0xedff5e50: 0x9a0751

_ZN13smb_threadCtx10execTrans2EP4msgbPcS2_+0x1 0xedff5e80: 0x9a1677

_ZN13smb_threadCtx15replyTrans2PrimEP4msgb+0x6

Fix Code no longer tries to get user quota information or information from quota tree for UID -2. If an error is received from quota access, the error is ignored, and the file system actual size is preserved.




Symptom Description

User reported loss of read or write access to CIFS shares when using the Celerra Event Publishing Agent (CEPA) feature. When Celerra Event Enabler (CEE) Framework returned a VC_ERROR_FAIL for an AV scan request, the Data Mover did not honor the requestTimeout value and did not drop the scan request nor generate a log entry to notify the Data Mover admin. When trying to write to a CIFS share, the following popup error was displayed in the GUI: Error Copying File or Folder. Make sure the disk is not full or write-protected and that the file is not currently in use.

Fix After the requested timeout period, the scan request is now dropped as expected.



Version 5.6.37.6


Symptom Description

When creating a DFS root FS and unicode was enabled, the computer name that came in as part of the request caused a memory leak if the string was allocated for it. Over time, this led to a Data Mover panic with the following DART panic/fault message: >>PANIC in file: ../bufpool.cxx at line: 322 : couldn't get a free page. The stack trace showed: 0xd5a55230: 0x13d890 waitForReboot+0x90 0xd5a55250: 0x13da8d fault_dump+0x67 0xd5a55270: 0x13d98d PANIC+0x29 0xd5a55280: 0x167b83

_ZN18Buffer_Cached_Pool17makeCachedBuffersEi+0 0xd5a552b0: 0x13a67d

_ZN19Memory_AddressSpace16makeCachedBufferEv+0 0xd5a552d0: 0x167711

_ZN18Buffer_Cached_Pool15getAnyCachedBufEji+0x 0xd5a55300: 0x736f1c

_ZN17UnCachedIO_Object9readBlockEym16BlockIO_P 0xd5a55380: 0x6298d2

_ZN14UFS_FileSystem9readBlockEliRP13Buffer_Cac

Fix Added a missing delete of an intermediate string in DFS getUncPath to prevent this condition.




Symptom Description

The server_checkup command displayed the following when the DNS test was run:Component CIFS :DNS : Checking the DNS configuration and connectivity to DNS servers.FailError 5005: server_3 : Void

This test checks to verify that the Data Mover can communicate with each DNS server configured. If multiple DNS servers were unavailable, this test timed out before the Data Mover responded that DNS servers were unavailable.

Fix Timeout no longer occurs while executing the checkup.



Version 5.6.37.6


Symptom Description

When using Sharedup V1.1.4 or earlier, the following unexpected error message was displayed when migrating a share that didn't have any flags enabled: "Partially OK: Share Flag not set on Share ..." The share and the share's ACL were successfully duplicated and fully functional.

Fix The unexpected message has been removed.



Symptom Description

When the CAVA service was incorrectly configured to use the local system account, the status of the virus checker server showed ONLINE in server_viruschk output. This implied that the virus checker server was able to check files when it could not.

Fix When the CAVA service uses the system account, server_viruschk now reports a status of ERROR_AUTH for that virus checker server.




Symptom Description

After user moved some CIFS servers to newly created VDMs, the Control Station exhibited high CPU utilization associated with never ending nas_xml processes and rebooted every few days.

Fix A problematic CIFS server configuration on VDM caused the Data Mover to return an unexpected error token in response to CIFS query from Control Station. Un-expected data received from the Data Mover resulted in an infinite loop in the Data Mover response parsing code. Code now exits the parsing loop when an unknown line is detected in the Data Mover's response.




Version 5.6.37.6



Symptom Description

When FSCK was run on an unmounted file system that had checkpoints, at the end of FSCK, the volume stack was not being cleaned up. This later caused the reference count issue on the Data Mover and checkpoint create operations failed.

Fix After FSCK for an unmounted file system, the volume stack is correctly cleaned up on the Data Mover and this condition no longer occurs.



Symptom Description

Failure to create/delete proxy errors were displayed in the mgmtd log. This is normal for local replications where the task to create a proxy of has already completed. These errors are ignored by the Data Mover and should be warnings instead.

Fix This error has been downgraded to a warning and can be safely ignored.



Symptom Description

Celerra Control Station was running out of memory followed by either a reboot (in case of single CS) or failover to the secondary (in case of dual CS).

Fix Third party monitoring applications such as ECC or Smarts were querying the Celerra utilization. The server_cifs server_x -o audit command coming through JServer was hanging during parsing of the output, taking memory on the Control Station. Having multiple hung instances taking all available memory caused the Control Station to fail. The code now parses and processes the output as the output stream from the server_cifs server_x -o audit command is produced rather than waiting for the entire output to be returned before parsing it (which filled up an input buffer). Parsing the output stream while the stream is being returned prevents this condition.




Version 5.6.37.6


Symptom Description

On a heavily loaded system with a slow backend I/O rate, if the system had a checkpoint whose SavVol reached the high water mark, the Data Mover panicked with the following DART panic/fault message: >>PANIC: I/O not progressing LastVol touched D17355136_0 Kind 8 (ptr=0xeb99c804). The stack trace showed: 0x697de90: 0x13e694 waitForReboot+0x90 0x697deb0: 0x13e891 fault_dump+0x67 0x697ded0: 0x13e791 PANIC+0x29 0x697dee0: 0x79906c _ZN9RawIO_IRP13checkProgressEv+0x11a 0x697dfd0: 0x798f48 _ZN17IrpProgressThread5startEv+0x6 0x697dfe0: 0x142e3c Sthread_startThread_internal+0xe

Fix The problem of dead lock for checkpoint high water mark event has been fixed, and the Data Mover no longer panics under this condition.



Symptom Description

The dbchk utility displayed the following errors when run on systems with CLARiiON RAID 6 LUNs:"Error: can not find disk c0t1l2+ 03261200120012NI+ referenced by camdisk file entry at index 41 for server server_4. Warning: found disk c0t1l2+DGC VRAID 03261200120012NI+ that does not have a path from server server_4."

Fix RAID 6 LUNs contain a LUN description of "DGC VRAID", which was not parsed correctly by dbchk. Other LUN types report descriptions of "DGC RAID" or "DGC DISK". This type is now correctly recognized.




Version 5.6.37.6



Symptom Description

The CLARiiON Navisphere Agent running on the Celerra (responsible for forwarding CLARiiON events to Celerra sys_log), occasionally had issues after restarting where data processing resulted in program memory corruption and eventually program failure. When the Navisphere Agent restarted, the same behavior could repeat itself after some log messages were replayed to the sys_log. CLARiiON’s Q1 2008 Navisphere patch (6.26.2.0.2-1) contains a fix for the memory issue which fixes the replay of old logs.

Fix CLARiiON’s Q1 2008 Navisphere patch (6.26.2.0.2-1) contains a fix for the memory issue which fixes the replay of old logs. Upgrade navicli and naviagent to Q1 2008 patch (6.26.2.0.2-1) to fix issues with naviagent memory management that caused the program failure.




Symptom Description

A memory leak condition occurred when using FileMover with NFS secondary servers if the secondary server responded to FileMover with a "stale handle" error. The Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../addrspac.cxx at line: 275 : Out of memory. The stack trace showed: 0xc9e6f650: 0x13d1db waitForReboot+0x8b0xc9e6f670: 0x13d3e3 fault_dump+0x670xc9e6f690: 0x13d2e3 PANIC+0x2b0xc9e6f6a0: 0x13918c

_ZN19Memory_AddressSpace10allocPagesEi12Memory0xc9e6f6c0: 0x187876 _Z11more_memoryiP9free_list+0x4e0xc9e6f6e0: 0x187923 malloc+0x89Stale handle errors are visible in the server log with messages like "NFS V3: Error: getAttr failed, nfs status 70".

Fix When FileMover receives the stale handle response, it looks up the file handle again, and retries the operation. Memory was lost during the retry. This fix makes sure any memory allocated on the initial request is freed before issuing the retry operation.




Version 5.6.37.6




Symptom Description

If a user sets up an HTTP connection, or gets info from server_http -info DHSM, the last line gives the CGI information. For example, if user set connection with -cgi n, the listing will show options = cgi=n. In version 5.6.36.4, code did not display that information, in other words, the options = was blank.

Fix Valid option list is now displayed for DHSM, NFS, HTTP and HTTPS connections.



Symptom Description

If a user performed a CNS install and then brought up the dialogue to change the IP Address, and clicked "OK" without changing anything, the subnet was reset to 255.255.0.0, instead of staying at 255.255.255.0. The user could work around this issue by typing in the correct subnet in the box on the screen.

Fix The subnet is no longer changed to 255.255.0.0.



Symptom Description

After a power outage, user found that a Data Mover network interface no longer existed. This led to loss of access to users.

Fix This problem occurred if the user was running a setup_slot command or performing a Data Mover failover and the process was interrupted while building the interface information in the NASDB. The interface building process now maintains state at all times – if the build process is interrupted, the interface list will be reverted to the previously known good state.




Version 5.6.37.6


Symptom Description

During a fresh install of an NSX with a mixed UPS environment( 6U & 3U), the following error message was reported at the end of the install, although both UPS were installed and configured correctly. Creating IDE cache of NAS file system #### done Configure the UPS emcnasUPS_i0 ... Time out during operation: 3u Pending CRITICAL FAULT: Failed to configure UPS on primary internal subnet Configure the UPS emcnasUPS_i1 ... COMPLETE Done Starting services... Restarted crond Performing Inventory....Done. System Inventory is placed in /nas/log/inventory.

Fix This problem no longer occurs when installing a system with a 3U UPS and a 6U UPS.



Symptom Description

When NAS code upgrades failed and reported that there were running tasks in the system, the instructions were not accurate enough to investigate and cleanup.

Fix Instructions were modified to be accurate and more intuitive to the user.



Symptom Description

During the install/upgrade process, the extended user/group databases must be initialized with the proper values so authentication & authorization can take place. During a recovery install, the files in /etc directory were set up with initial values so any changes previously made were lost. This resulted in the /etc files becoming out-of-sync with the secondary user/group databases. This issue caused access problems, such as nasadmin user not having appropriate permissions and could not perform some actions.

Fix Code now checks to see if this is a recover install. If it is, the code copies the back-up user/group files to the /etc directory so the current users/groups are maintained. Otherwise the step continues with the secondary database checks.



Version 5.6.37.6



Symptom Description

Celerra Manager was not reporting statistics because JServer would not start due to the Control Station’s name not being recognized by a script which populated /etc/hosts file with the Control Station name.

Fix The script was changed to correctly search for the Control Station’s name and add it to the various files used by Jserver to startup.




Symptom Description

When a Data Mover was serving as the target for iSCSI or IP replication V2 and received an invalid message from the source, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: /disks/Archive_Area_nsg4/5_5_23_200/ Dart/server /src/kernel/include/stream.hxx at line: 1591 : freeb called with NULL message block. The stack trace showed: 0xeda7fec0: 0x13d1d3 waitForReboot+0x8b0xeda7fee0: 0x13d3db fault_dump+0x670xeda7ff00: 0x13d2db PANIC+0x2b0xeda7ff10: 0xbdfcff

_ZN16FileVersionDelta9reFormateERP4msgbS2_Py+00xeda7ff40: 0xbe423e _ZN16DpCopierReceiver8readDataEv+0x12c0xeda7ff80: 0xbe3f66

_ZN16DpCopierReceiver11handleEventE22copierRec0xeda7ff90: 0xbe3976

_ZN19copierReceiverEvent11handleEventEv+0x16

Fix To prevent this Data Mover panic, when a CRC (cyclic redundancy check) detects a bad message it is now rejected and the connection closed and reopened. The source then resends the message.




Version 5.6.37.6

MPFS The following entries describe fixed problems pertaining to Multi-Path File Systems:

Networking The following entries describe fixed issues related to Networking:


Symptom Description

While using MPFS, when the file system became full, the Data Mover panicked with the following DART panic/fault message: getOneFreeDiskBlock failed: file system fl. The stack trace showed: 0x184275d0: 0x13d810 waitForReboot+0x90 0x184275f0: 0x13da0d fault_dump+0x67 0x18427610: 0x13d90d PANIC+0x29 0x18427620: 0x618a7e

_ZN14UFS_FileSystem28markCorruptedFsForUnmount 0x184276a0: 0x67dc04

_ZN17UFS_MemoryFileMap19getOneFreeDiskBlockElP 0x184276d0: 0x67b7d7

_ZN17UFS_MemoryFileMap18allocFileSpaceListEyyP 0x184277a0: 0x623cba

_ZN9UFS_Vnode10allocSpaceEmmRP11extentEntryRy+

Fix The problem was due to a rounding error under certain boundary conditions. This caused a counter to be off by one. Subsequently, when this counter was used it caused this panic. This has been fixed.




Symptom Description

The TCP Keepalive timer setting was broken. The idle timer was not reset to zero. As a result the old idle timer value was compared to the new timer value. In the case of HTTPD, a 5 minutes idle timer was compared to 90 seconds of new timer value. This caused a false KEEPALIVE timer to fire causing a connection reset with the Control Station.

Fix Before the fix, the nas_fs failed with an exception when the command took more than 5 minutes and under load. With the fix the nas_fs command will run past the five minutes and will finish without any problems



Version 5.6.37.6



Symptom Description

While using Rep V1, the Data Mover panicked if the following conditions occurred:1. Replication session went inactive2. Attempt to refresh the replication with new policy values: to=0, hwm=0 on the source. This

command failed as replication is inactive.3. Replication modify operation was executed that sets source side policy to a different values other

than previous or default (e.g. to=1200, hwm=1200)4. Replication abort command was issuedThe root cause of the panic is that when replication was aborted with the conditions noted above, the replication object was deleted, but some components were not cleaned out from memory.

Fix This issue was fixed by adding a destructor function, which is called whenever replication abort command is issued, and it cleans up remaining replication related components from memory.




Symptom Description

Several Rep V2 messages were confusing or vague.

Fix These messages were reworded to be more comprehensive and intuitive.



Symptom Description

Control Station sys log did not contain messages for file system extension, SavVol extension, and file system copy complete events.

Fix These events are now displayed in the Control Station sys log.



Version 5.6.37.6


Symptom Description

If user issues server_umount of a file system being used as source of the nas_copy command, the nas_copy command failed unexpectedly with I/O error. "Error 13160415351: I/O error from version."

Fix Unmount will be rejected gracefully and nas_copy will now succeed.



Symptom Description

The “Current Transfer Remain” in nas_replication -i information was invalid. This occurred while viewing the status of a Repv2 replication, if the data set being transferred was more than 4 GB (most common when the initial file system sync runs on a new replication session). This information was correct when viewed from the Celerra Manager.

Fix Corrected the information displayed.



Symptom Description

Setting up a new Replicator V2 session required up to double the amount of space on the destination site as on the source site.Replicator creates a destination file system that is the same size as the primary file system. It also created a SavVol file system the size of the amount of data on the source file system. This meant that if the source file system is full, double the space was be required on the destination when setting up a new replication session.For example: If the replication source was a 2 TB file system that was half-full, the new replication session required a 2 TB file system on the destination system plus a 1 TB SavVol, for a total of 3 TB.

Fix This issue has been corrected. The destination SavVol now only needs to be as large as a typical checkpoint SavVol.



Version 5.6.37.6


Symptom Description

During a period of very heavy write I/O to an IP replication source file system, the session became inactive. During the process of making the session inactive, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../sched.cxx at line: 822 : SYSTEM WATCHDOG. The stack trace showed: 0xdb2d5ea4: 0x13d1db waitForReboot+0x8b 0xdb2d5ec4: 0x13d3e3 fault_dump+0x67 0xdb2d5ee4: 0x13d2e3 PANIC+0x2b 0xdb2d5ef4: 0x13ee08 system_watchdog+0x7c 0xdb2d5f04: 0x137279 _t_nmi+0x63 0xdb2d5f50: 0x752069 _ZN16LogFilterCopyThr5startEv+0x4e9 0xdb2d5fe0: 0x1406f4 Sthread_startThread_internal+0xe

Fix Improved the process that marks a replication session inactive to avoid the watchdog panic.




Symptom Description

While using IP Replication V2, the nas_task -abort command failed when the session was already stopped. Errors similar to the following were displayed in the server_log: Error 13422297134: Abort request timed out. Please check the task status to see if abort task succeeded. This problem affected both the CLI and the GUI.

Fix Stopping a session that is already stopped now returns the SessionStopped status. This is clearer than the previous status returned under these conditions. The Stop command is now able to properly handle abort in any state.



Symptom Description

The Next Transfer Size (Kb) field was not displayed in the GUI but was displayed in the CLI.

Fix The "Next Transfer Size" field is now displayed in the properties page of Replicator V2 session.



Version 5.6.37.6


Symptom Description

File systems on VDM were not listed on the Select Source Screen of the Celerra Replicator wizard If no replications were present, the r/w file systems mounted on the virtual Data Movers were not listed on the select source file systems of wizards while creating the new replication using the ongoing fs option.

Fix This has been fixed. The VDMs are now added to the VDM list and the file system is displayed correctly.



Symptom Description

When user issued the nas_copy command, the replication session hung and the message read process full abort when user never issued an abort. This message was very misleading as code was performing a normal cleanup. [nasadmin@eng17310 ~]$ nas_task -info 3304Task Id = 3304Celerra Network Server = Local SystemTask State = RunningCurrent Activity = Info 26045317617: Process full abortThis problem could also be seen from the GUI when performing a copy.

Fix The nas_copy command cleanup state now returns a more meaningful message: "Primary cleaning up"



Symptom Description

Celerra Manager IP Replication V2 iSCSI loopback replication page displayed an error message along with static data which did not enable the user to make appropriate changes to correct parameter errors. This error occurred when the overwrite destination checkbox was enabled. “Start Replication AR100144i. The ISCSI LUN specified as destination is not read-only ... The Data Mover interconnect configured for this replication is not available ... “

Fix Code was fixed to ensure the correct code path is followed to display the “Start” button which allows incorrect parameters to be changed.



Version 5.6.37.6


Symptom Description

A nas_copy session was started and a panic or reboot happened after the transfer was done but before the session completed. In this instance the recovery process after reboot was not completely cleaned up. Later, if a nas_copy was run with the same alias, the command failed with the message: "Error 13160415247: The replication name is already in use."

Fix During recovery, following a reboot or panic, the nas_copy session is now completely cleaned up.



Symptom Description

The replication internal scheduler became inactive and could not function properly.

Fix This problem occurred because a session was listed as OK but the scheduler was actually inactive. This has been fixed.



Symptom Description

When more than one replication list request contained the same task_id, the Data Mover panicked with the following DART panic/fault message: ">>PANIC in file: ../malloc.cxx at line: 349 : Memory corrupted". The stack trace showed: 0xca184910: 0x13e694 waitForReboot+0x90 0xca184930: 0x13e891 fault_dump+0x67 0xca184950: 0x13e791 PANIC+0x29 0xca184960: 0x1a1bb5 free+0x69 0xca184990: 0x1a2214 _ZdlPv+0x10 0xca1849a0: 0x1e0890 _ZN9logObjectD0Ev+0x88 0xca1849c0: 0xf29f5c _ZN18CmdReplicatev2List7executeEP10DicXmlData+ The chances of this happening are higher when the system is busy processing a lot of commands.

Fix This problem occurred due to the object in the code being cleaned up from the memory twice. When code attempted to clean up the object a second time, the Data Mover panicked. This was fixed by removing the duplicate cleanup request.



Version 5.6.37.6


Symptom Description

After performing a checkpoint restore, a Replication destination file system appeared to be mounted read-write and could be written to by users, but was continuing to receive replication updates from the source.

Fix If a read-only filesystem (such as a replication destination) crossed 75% full when performing a checkpoint restore, it would be left in read-write state. This problem no longer occurs.



Symptom Description

When a refresh operation failed, user saw a refresh task on the secondary side when a nas_task –l command was issued. This task context was actually left over from a previously completed refresh task.

Fix The abort of refresh command now deletes the proxy on the secondary side and nas_task -l displays the correct information.



Symptom Description

While IP Replication was running, execution of the create/delete/refresh commands against the checkpoint of the SFS failed with the following errors in the server_log: VCS: 3: VVS::deleteVV vname=17915.ckpt007 snapfsid=10922 : preconditions failedADMIN: 3: SnapSure command Delete ID 10922 SavVol 17926 FsVol 17915 failed: DpRequest_vs_Busy

Fix The problem was caused by a race condition between IP Replication playback and checkpoint create/refresh/delete commands. When checkpoints commands are issued, the playback needs to be suspended, however suspend should not be allowed until freeze and thaw operations are completed on the SFS. The fix for this issue is to add additional check that will prevent this race condition.



Version 5.6.37.6


Symptom Description

If a Data Mover was rebooted while a nas_copy was in progress, internal checkpoints were left over on both the source and the destination. This problem was seen when using the CLI or the GUI.

Fix Internal checkpoints of the copy command are now deleted before the reboot.



Symptom Description

While using Replicator V2, the bandwidth schedule in the GUI did not display the correct start hour and end hour.

Fix Start (or End) time selector was not cleared before entering the screen, so the start (end) time kept the uninitialized value. Start (or End) time selector is now cleared and necessary initialization and validation for the entries are performed before adding the schedule to the list of schedules.



Symptom Description

Linux CBMCLI is a set of commands used by iSCSI Linux hosts to create/manage iSCSI LUNS. When user queried the replication status of a stopped session from the Linux CBMCLI, a session status of "n/a" was returned.

Fix Linux CBMCLI was updated to return "Session Stopped" status for a stopped session.



Symptom Description

When destination interface was down and an attempt was made to stop the session for both sides using Linux CBMCLI, the command returned: NBS Err: Unknown Error: 536872150.

Fix Linux CBMCLI was updated to return a "Network down" error in this case.



Version 5.6.37.6


Symptom Description

When the nas_replicate -info -all command was issued from the CLI, 300 duplicate CLI queries were generated. The CLI was getting the replication list and then for every replication from the list running the same query to map the ID into the file system name. This issue caused slow performance.

Fix The nas_replicate -info -all command has been modified to handle FS replications more efficiently. The queries are now triggered only once.



Symptom Description

When using the WEB UI FS replication page, the filtering for the VDMs was not done correctly. This caused VDMs that shouldn't have been displayed to show. If user then selected an invalid VDM and hit the OK button it resulted in a never ending task.

Fix The filtering for the VDMs to be shown on the new fs replication page was modified so only valid VDMs are displayed.



Symptom Description

On a heavily loaded system, checkpoints did not extend quickly enough after hitting the high watermark to prevent a checkpoint from going inactive. This caused SavVol extension to fail, which prevented other checkpoints from going inactive as well.

Fix Code now allows the extension of checkpoint that are mounted but inactivated to happen, so the SavVol can be extended, and the rest of the checkpoints won't be inactivated.



Version 5.6.37.6


Symptom Description

Following a Replicator v2 internal checkpoint refresh on a destination file system, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: dbc96c Err code: 0 Target addr: 0 **. The stack trace showed: 0x1c8c0b4: 0x13e694 waitForReboot+0x90 0x1c8c0d4: 0x13e891 fault_dump+0x67 0x1c8c0f4: 0x138768 handle_fatal_fault+0xa 0x1c8c140: 0xdc9f39

_ZN15snapshotContext10BlockInUseEP8DeltaVolyP8S 0xffea5dc0: 0xdb1e49

_ZN19PoolManagedDeltaVol18writeBlockFilteredEP 0xffea5e40: 0xdc5052

_ZN10SnappedVol18writeBlockFilteredEP10DiskIO_ 0xffea5e60: 0xdc500d

_ZN10SnappedVol18writeBlockInternalEP10DiskIO_ 0xffea5e80: 0x7aae43

_ZN11HyperVolume18writeBlockInternalEP10DiskIO

Fix A race condition occurred between a checkpoint delete operation and a Replicator write. Code now queues a checkpoint delete request on destination side if the replication session is transferring data and executes the request after data transfer is done.



Symptom Description

On a system with a large number (hundreds) of Replicator v2 sessions and small SLA (service level agreement) value configured on a Data Mover, the resource impact on checkpoint refreshes caused high CPU utilization, even when changes were not occurring on the source file systems.

Fix The code no longer performs automatic checkpoint refreshes for Replicator v2 unless the source file system has changed. This improves efficiency by avoiding unnecessary work.



Version 5.6.37.6


Symptom Description

Under Stress conditions with large quantities (i.e. 1024) of replication V2 sessions, if the user did not change the default TIMEOUT of 20 seconds, when trying to fail over 1024 replication sessions, not all the session failed over. The user then had to reissue the failover request for the sessions missed from the first request.

Fix This problem happened because the default timeout value for Celerra Inter-connect (CIC) was 20 seconds. The default timeout value for CIC has been changed from 20 to 100 seconds to reduce the amount of retry requests being sent to the Data Mover when it runs into these issues. On the Control Station there is a file called /nas/site/cmd_svc.cfg. In that file, there is a line TIMEOUT=100. The allowable range is between 5 and 240.



Symptom Description

When using Replicator V2, the stop command under some error conditions (error in stamping, or task propagation stage) did not clean up the command context on the secondary side. User did not receive an ack indicating that stamping succeeded.

Fix Task list on the secondary side now show stop commands that failed (in stamping state). The secondary side is also cleaned up and users no longer see leftover tasks.



Symptom Description

After issuing a server_iscsi -snap command, neither success nor failure messages were reported. For example issuing server_iscsi -snap -create would normally report the ID of the snap that was created. With this issue, that ID was not reported. Similarly, any errors that occurred when using the server_iscsi -snap command were not reported.

Fix The server_iscsi -snap command now reports status messages properly.



Version 5.6.37.6


Symptom Description

On a Dual-CS NS Celerra system, after a manual execution of the deploy_replication command to setup the Rep v1/v2 readiness, if a Control Station failover occurred, the change done from the deploy script execution was not visible from the secondary Control Station that took over. So, if the user had setup the cabinet for V2 readiness, after a Control Station failover, it reflected as V1 ready, and vice-versa.

Fix The fix ensures that the secondary Control Station is first changed to v1/v2 ready and only then the primary Control Station can change the v1/v2 readiness. It is user's responsibility to execute the deploy_replication command on both Control Stations.



Symptom Description

A memory leak condition occurred when using the server_sysstat command on the Control Station during Replication v2 operations. This eventually led to a Data Mover panic with the following DART panic/fault message: >>PANIC in file: ../addrspac.cxx at line: 282 : Out of memory. The stack trace showed: 0xffef9c10: 0x13e694 waitForReboot+0x900xffef9c30: 0x13e891 fault_dump+0x670xffef9c50: 0x13e791 PANIC+0x290xffef9c60: 0x13a286

_ZN19Memory_AddressSpace10allocPagesEi12Memory0xffef9c80: 0x142c33 _ZN7SthreadC1EPcP10DQueueHeadIS_Eji+0x1cb0xffef9ca0: 0xdcef32

_ZN21ckptBlockAllocatorThr6launchEPKc+0x6a0xffef9cd0: 0xdac3af _ZN19PoolManagedDeltaVol14startAllocatorEv+0xa

Fix This memory leak condition has been fixed.



Symptom Description

When user created an iSCSI replication session from CBM (Celerra Block Manager) or RM (EMC Replication Manager), the “preferred target” parameter was ignored.

Fix Code now allows user to specify destination target name (IQN) and a preferred target parameter.



Version 5.6.37.6


Symptom Description

After a file system SavVol filled, Replicator v2 sessions and one of the internal Replication checkpoints became inactive. The invalidated checkpoint was not the Repv2 common base checkpoint, which should have allowed Replicator to recover. However, when Replicator attempted to refresh this checkpoint, the operation failed, leaving the replication session inactive.

Fix When refreshing an inactive Replicator v2 checkpoint, code now re-mounts the checkpoint before refreshing, allowing the refresh to succeed.



Symptom Description

When hundreds of Replication v2 commands were executing simultaneously, the Data Mover panicked with the following DART panic/fault message: >>PANIC in file: ../sched.cxx at line: 829 : SYSTEM WATCHDOG. The stack trace showed: 0x001448a0 in Sthread_Mutex_unconstructed::lockSolid() 0x00f0bfbc in CmdCommonTimerList::insert(CmdCommon*)0x00f0c48a in CmdCommon::insertList() (this=0x98199344) at ../CmdCommon.cxx:199

Fix The race condition that led to this problem has been corrected.



Symptom Description

After creating a Replicator v2 session to replicate a file system, stopping the replication, and mounting the source file system read-only, attempts to run nas_copy between the file systems failed. The nas_copy failed as expected, but future Replicator operations against these file systems failed. Rebooting the destination Data Mover corrected the problem.

Fix When the nas_copy operation ran and failed, a file system reference on the destination system was not cleared, causing future operations to fail as well. This reference is now cleared, and commands succeed as expected.



Version 5.6.37.6

Security The following entries describe fixed security-related issues:


Symptom Description

When trying to setup an IP replication session, the Data Mover panicked with the following DART panic/fault message: *** Page Fault Interrupt. Virt ADDRESS: a1b317 Err code: 0 Target addr: 9 ** . The stack trace showed: 0x2324894: 0x146b8c waitForReboot+0x90 0x23248b4: 0x146d9f fault_dump+0x67 0x23248d4: 0x13c56c handle_fatal_fault+0xa 0x2324910: 0xa1af38 _Z13FindAndCreateP7LVolumePi+0x90 0xac267be0: 0xa1f1cd _Z10VolumePoolR6Option+0x551 0xac267c90: 0x19c6c3

_ZN11cfgcmd_desc6invokeEPKcPP8CCMD_Msgii+0x1a7 0xac267d00: 0x29da36 _Z10xml_cfgcmdP7macDataRP8CCMD_Msg+0x392 0xac267d50: 0x29981c

_ZN17macCCMDCommand_DB6invokeEPKcP7macDataRP8C

Fix The code has been fixed to clear the references held by other replication objects and ensure the Data Mover no longer panics under this condition.



Symptom Description

When using the lookup option of server_ldap for a large group (1000s of members), it timed out.$ server_ldap server_2 -lookup -gid 10000server_2 :Error 4020: server_2 : Input/output error Timed out

Fix The LDAP lookup option was optimized so that groups with many members can be queried.




Version 5.6.37.6


Symptom Description

While trying to complete requests to the LDAP server which was down, the Data Mover panicked with the following DART panic/fault message: *** Watch Point exception. Virt ADDRESS: 4ee939 ***. The stack trace showed: 0x9275d0fc: 0x14579c waitForReboot+0x90 0x9275d11c: 0x1459af fault_dump+0x67 0x9275d13c: 0x13b4c4 handle_fatal_fault+0xa 0x9275d190: 0x5041d2

_ZN16LdapDomainClient6searchERP10LdapClientPKc 0x9275d240: 0x503f0e

_ZN16LdapDomainClient6searchERP10LdapClientPKc 0x9275d2c0: 0x4fda69

_ZN16LdapDomainClient13gethostbyaddrEPciiP7Hos 0x9275d610: 0x1ce7e9

_ZN12ns_LdapEntry13gethostbyaddrEPciiP7Hostent 0x9275d640: 0x1ce86c

_ZN12ns_LdapEntry13gethostbyaddrEPciiP7Hostent

Fix An operation was corrected that caused the Data Mover to mark an LDAP server as online and connected when the server was actually down. The Data Mover attempted to send messages to the server without a valid connection and panicked. This issue has been corrected.



Symptom Description

If a Celerra Manager public key certificate expired exactly on the second it was checked, it was returned as a valid certificate. Using an expired certificate resulted in loss or inability to establish SSL connections.

Fix The code was changed to return a 'certificate expired' status, if the expiration date matches the current time, down to the second.



Symptom Description

If an invalid IP address is entered via server_ldap, the LDAP service remained hung in the "disconnected" state for up to 5 minutes, even if a good IP address was specified in the meantime.

Fix If a valid LDAP server address is entered, the LDAP service now becomes available immediately.



Version 5.6.37.6



Symptom Description

Setting up LDAP via server_ldap while the LDAP service is stopped resulted in the LDAP service being in the "failed" state and remaining that way when the LDAP service was started.

Fix LDAP configuration can now be defined while the LDAP service is stopped. It is taken into account when the service is started.



Symptom Description

Issuing the server_ldap command twice with IP addresses of the LDAP server[s] left the LDAP service in a disconnected state.

Fix Now the Data Mover connects immediately to the IP address provided by server_ldap.



Symptom Description

When using Sun iPlanet (LDAP) for CIFS and NFSv4 usermapping, performance was poor when user attempted to create many small files from an NFSv4 client. Traces showed the Data Mover was repeatedly performing LDAP lookups each time the user attempted to create a new file.

Fix The Data Mover now caches information from LDAP in the same way that it caches details from NIS, and does not need to perform repeated lookups.




Version 5.6.37.6


Symptom Description

Devices improperly mapped to LUNs in the reserved range of 0-0xF on the boot Symmetrix were marked and added to the configuration even though the following message was displayed during diskmark/Rescan:Discovering storage (may take several minutes)Warning:17716815787: server_2 c0t0l11 skipping reserved LUN id,000187400462 stor_dev=0x0184 (388 decimal), maps to a reserved host LUN id 0xb.

Fix Celerra will no longer attempt to mark LUNS in the reserved LUN range (0-15 on the storage array containing the Celerra control LUNS) for use as data LUNs. These LUNs were skipped on the first chain (path) to the LUNs, but not on redundant paths to the LUNs. These LUNs are now skipped on all paths.



Symptom Description

During system initialization, Tachyon-based Fibre Channel HBAs could issue a reset while the transmitter is turned on. This resulted in bad data being injected onto the Fibre Channel link. This condition could persist for up to several minutes.

Fix The HBA Driver has been restructured to ensure the HBA is stable before it is inserted into the Fibre Loop. Additionally, the HBA is removed from the Loop prior to Data Mover shutdown to ensure disruptions to the Fibre Loop are minimized.



Symptom Description

During initial configuration, the setup_clariion command failed with “Error 5017: storage health check failed” due to inconsistent view of paths to the array - one Data Mover saw two paths, and another saw four paths. This problem occurred because during the diskmark process, the scan for the devices was performed sequentially for all Data Movers.

Fix The code now performs scans for the devices across all Data Mover in parallel, preventing this issue.



Version 5.6.37.6

Tools The following entries describe fixed problems pertaining to tools such as EMCOPY, EMCACL, LGDUP, SHAREDUP:


:


Symptom Description

During Celerra installation using CSA, the network settings were not populated properly from the client PC causing CSA to hang and preventing the user from creating CIFS shares or NFS exports. This issue occurred if the DNS suffix on the client PC was empty.

Fix Code has been fixed to make sure that CSA will continue without this information.



Symptom Description

While running FSCK, the following message was displayed in the server_log: "Could not find the complete path for inode 8712643 with parent {pino} Partial Pathname is /fs1/dir1/dir2". The parent inode information should be displayed instead of the string "{pino}".

Fix The server_log now displays the message correctly, including the parent inode information.



Symptom Description

When trying to unmount a user file system after performing DHSM archiving using Rainfinity, the server_umount command failed with "Error 16: server_x : Device or resource busy" error. This problem was observed only when the path for archived file contained "/.etc/" anywhere but at the beginning of the path. This occurred because Data Mover took a reference to the vnode and never released it.

Fix The code has been fixed to properly release all the references upon finishing working with the file, preventing the vnode leak and unmount problem.



Version 5.6.37.6


Symptom Description

A .ckpt directory entry was generated based on the time zone name, and the directory entry was not getting generated if the time zone contained forward slashes (/) like "Europe/Tirane" because forward slash(/) represents the directory separator in UNIX.

Fix The forward slashes(/) in the time zone string are now replaced by underscore ( _ ) while generating the directory name.



Symptom Description

When iSCSI client issued a read request size larger than 1MB, the Data Mover panicked without producing a valid panic dump. The server_log showed "UFS: 3: makeIOList : list too long, failed" messages.

Fix Code was changed to handle larger size iSCSI I/O's by adding loop to handle it in multiple segments.




Symptom Description

The Data Mover panicked with the following DART panic/fault message: Assertion failure: '!(dirtyLink.is_queued())' on line 445 in file '../ufsdirty.cxx' >>PANIC in file: ../assert.c at line: 26 : The stack trace showed: 0x7cd67ec0: 0x14638c waitForReboot+0x90 0x7cd67ee0: 0x14659f fault_dump+0x67 0x7cd67f00: 0x146489 PANIC+0x29 0x7cd67f10: 0x1d0135 _assert+0x51 0x7cd67f30: 0x833bf0 _ZN15UFS_DirBlkCache13getFirstDirtyERP15UFS_Di 0x7cd67f70: 0x889649 _ZN16ufsflush_Initial13startDirFlushEv+0x24b 0x7cd67fb0: 0x888d81 _ZN16ufsflush_Initial5startEv+0x2af

Fix The panic occurred when another thread tried to access a deleted entry. Code was modified to prevent dirty block entries from getting deleted while I/O is in progress.



Troubleshooting and getting help

Troubleshooting and getting helpEMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink™ website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.


Symptom Description

During the upgrade to NAS 5.6 a checksum is added to the gid_map file on each file system. If the file system is approaching full (less than 24k available) the new gid_map file cannot be written and the Data Mover will fail to mount the file system because of the invalid gid_map file.Recommended Action: Customer Service should be contacted to help resolve this issue if it occurs.

Fix The PUHC/PAHC file system checks have been enhanced to alert the user to the possibility that this will occur. At least 128K of free space must be available on each file system for upgrade or normal operation. This check will only apply to read-write user file systems. Read only file system or root_fs_xxx will not be reported.


http://powerlink.emc.com


Copyright © 2008 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

version 5.6.42.5

Documents