Release Notes P/N REV A06 September 30, 2009

Transcription

1 EMC Navisphere Host Agent/CLI and Utilities Version for FLARE OE yyy, xxx.5.yyy, xxx.5.yyy, xxx.5.yyy, xxx.5.yyy and yyy Release Notes P/N REV A06 September 30, 2009 These release notes include supplemental information about the EMC Navisphere Host Agent, CLI, Secure CLI, Server Utility, and Storage System Initialization Utility for the AIX, VMware, HP-UX, Linux, Solaris, and Windows operating systems, version Topics include: Revision history... 2 Product description... 2 New features and changes... 5 Environment and system requirements... 6 Fixed problems Known problems and limitations Technical notes Documentation Software media, organization, and files Installation Troubleshooting and getting help

2 Revision history Revision history The following table presents the revision history of this document. Revision Date Description A06 September 30, 2009 Added changes made for version x.x A05 March 3, 2009 Added changes made for version x.x A04 December 3, 2008 Adds support to IBM Power Linux operating systems. A03 November 17, 2008 Updated the following: Known problems and limitations Fixed Problems ( and ) A02 August 8, 2008 Removed references to Windows 2000 as a supported platform for Navisphere host software. A01 June 27, 2008 Initial release of product Product description The EMC SP Agent (Array Agent), which resides on the storage processors (SPs) in CX series, CX3 series, CX4 series, AX series, and AX4-5 series storage systems, communicates with Navisphere client applications to manage CX series, CX3 series, CX4 series, AX series, and AX4-5 series storage systems. The EMC Navisphere Host Agent is server-based software that communicates with Navisphere client applications, such as the Navisphere Command Line Interface (CLI) and Manager. A host agent automatically registers hosts and HBAs and also provides drive mapping information for the UI and CLI. The host agent has no direct user interface. Therefore, it must be configured with the remote agent configuration feature of Navisphere Manager or CLI or by editing the host agent configuration file. Although Navisphere clients do not manage CX series, CX3 series, CX4 series, AX series, and AX4-5 series storage systems through the host agent, the host agent is still required for the registration of the host bus adapters with the SPs to which they are connected and for integrating host-side information such as device and volume names. Several Navisphere clients can communicate with one Navisphere Host Agent. A host agent, however, should have only one connection to a particular storage processor (SP). 2

3 Product description For some operating systems (Windows, Solaris, AIX, HP-UX and Linux), the Navisphere Host Agent can monitor storage-system events and take such actions as sending or alerting a pager if specified events occur. Navisphere Manager provides an interactive way to define these events and actions. If you do not have Navisphere Manager, you can still define events and actions by editing the event monitor configuration file supplied with the host agent. The CLI (also referred to as Classic CLI) is a client application that allows simple operations on an EMC CX series, CX3 series, CX4 series, or AX series storage system. The CLI issues commands to a host or SP agent, requests storage-system status, and displays the resulting output as a tool for problem determination. The Secure CLI is a client application that allows simple operations on an EMC CX series, CX3 series, CX4 series, AX series, and AX4-5 series storage system. The Secure CLI issues commands to a management server, requests storage-system status, and displays the resulting output as a tool for problem determination. It is implemented using the Navisphere 6.X security model, which includes role-based management, auditing of all user change requests, management data protected with SSL, and centralized user account management. Note: AX4-5 series storage systems support only Secure CLI. You can use the CLI or Secure CLI in scripted applications to automate lengthy or repetitive management operations. It is also useful for obtaining quick status checks or for performing small, fast management changes. The use of Secure CLI instead of Classic CLI is strongly recommended. NOTE: Classic CLI is being phased out so any new scripts should be written using Secure CLI. It is HIGHLY recommended that existing CLI-based scripts be migrated to Secure CLI wherever possible. The error returns for both CLI and Secure CLI are now listed in this release note. Navisphere CLI is the client portion of a client-server application. If Navisphere CLI and Navisphere Host Agent are installed and running on the same host, this host may act as both the client and the server. The server utility will scan for CLARiiON devices and will display the list of discovered devices to you. The utility is used for basic troubleshooting by verifying that both connections to the storage system are correct and the mounted volumes are visible. It also allows you to register the host with the attached storage system. Note that the host agent provides additional information that is not available from running 3

4 Product description the server utility. Drive mapping and OS information is not stored on CX storage systems as a result of the push and therefore is available only through the host agent. If you require that information, the agent must be running on that host instead. The storage system initialization utility is an application that you can use to simplify the initialization and setup of a storage system. It provides a simple, straightforward user interface to discover and initialize storage systems. By using an existing LAN, you can set both SPs with the same operation. 4

5 New features and changes New features and changes New features in version x None. New features in version x None. New features in version x Version x of the product adds support for Linux distributions on IBM Power Series servers. New features in version x This section describes any new features and changes for version 6.28.x of the product. Ability to manage CX4 series storage systems IPv6 management capabilities Increased Event Monitor log size This section describes any new features and changes specifically for Navisphere Express-managed AX4-5 series storage systems running FLARE OE xx and later: The ability to create a RAID 6 RAID group using Secure CLI The ability to add or remove a global administrator account, and to change the password of a global administrator account, using Secure CLI The ability to set or remove a domain master a domain master using Secure CLI The ability to retrieve background verify reports using Secure CLI. This section describes any new features and changes specifically for AX4-5 series storage systems running FLARE OE xx and later without the expansion enabler: The ability to create a RAID group using SAS drives in the disk processor enclosure. The ability to bind a hot spare LUN using SAS drives in the disk processor. 5

6 Environment and system requirements Future enhancements and modifications This section describes any future enhancements or modifications that may affect the functionality of the applications in your environment. Please be aware that will be the command line client of choice going forward. Whenever possible scripts using CLI commands should use (Secure CLI) as the command line interface. New Navisphere CLI features will be added to Secure CLI only. In a future version, Classic CLI (Navisphere CLI) will not be supported. The Java CLI client is no longer being released; the last version of the Java CLI client is 6.24 and it is available from Powerlink. Using Secure CLI now will help avoid the need to modify scripts at a later date. Environment and system requirements This section explains the minimum hardware and software environments for proper operation of this version of the Navisphere Host Agent, CLI, Secure CLI, Server Utility and Storage System Initialization Utility. Note: See the EMC Support Matrix for specific supported OS versions. Not all operating systems support PowerPath software. Operating system Solaris Minimum hardware requirements Sun system capable of accepting PCI, SBus, or cpci HBAs with at least 30 MB of free disk space and 64 MB of RAM. OS Minimum software requirements Sun Solaris 9, 10 (SPARC), Solaris 10 on x86 compatible servers (Opteron). Note: Only Navisphere Server Utility, Inittool and are supported for Solaris 10 on x86 compatible servers. Navisphere Server Utility and Agent are not supported on hosts using Solaris native failovers. (STMS/MPxIO) AX4-5 series is not supported with Solaris 8. 6

7 Environment and system requirements Operating system Windows AIX HP-UX Linux VMware IBM Power Linux Minimum hardware requirements Intel-compatible PC with 64 MB of RAM and at least 30 MB of free disk space. IBM AIX workstation with at least 64 MB of RAM and 14 MB of free disk space. HP server with at least 30 MB of free disk space and 64 MB of RAM. An Intel-compatible, processor-based system capable of accepting PCI HBAs, with at least 200 MB of free disk space and 64 MB RAM. VMware ESX Server with sufficient memory and disk space. Minimum software requirements OS Microsoft Windows Server 2003 (32-bit and 64-bit) (SP2), Windows Vista Business SP1, and Windows Server 2008 including Hyper-V (without software running in the Guest O/S) Note: utilities are supported on IA64 systems as well. For iscsi support, iscsi initiator driver should be version 2.4 or higher. OS IBM AIX Version 5.3 or 6.1 (32-bit or 64- bit). Note: AIX runtime environment should be at level 8 or higher. AX4-5 series is not supported with AIX 5.2. OS 11i v2.0 and 11iv3.0 (32-bit and 64-bit, PA- RISC and IA64 systems) running the latest patches. For IPv6 support, the minimum patch level is: "GOLDBASE11i B Base Patches for HP-UX 11i v1, December Other TCP/IP protocol installed and configured. OS Red Hat 4.x (32- and 64-bit) Red Hat 5.x (32-bit and 64-bit) SuSE SLES 9 and SuSE SLES 10 AsianUX 2.0 Note: AX4-5 series is not supported with Red Hat 3.0 or SuSE 8. OS ESX 3.0 ESX ESX ESX OS Red Hat Enterprise Server RHEL 5 and Novell/SUSE Enterprise Server SLES 10. 7

8 Environment and system requirements Disk space requirements The following table contains the minimum disk space requirements for Host Agent/CLI and other utilities. Applications Minimum disk space requirement (in MB) Host Agent 100 Navisphere CLI 105 Server Utility 105 Navisphere management software requirements EMC recommends that you always use the current shipping version of Navisphere Agent and Navisphere Manager to manage domains and for off-array management stations. Navisphere Manager and Navisphere CLI are compatible with older versions of software but newer features will not be available depending on the combination of software versions in use. The following table describes the compatibility matrix for Navisphere software: Host Agent FLARE Server Utility (CX4) (AX4-5) Supported with Navisphere Manager ;not supported with Navisphere Express Classic CLI Initialization Utility Secure CLI Classic CLI is not supported on AX Off-Array Manager

9 Environment and system requirements FLARE Host Agent Server Utility Classic CLI Initialization Utility Secure CLI Off-Array Manager (CX3), (CX) (CX3), (CX) (CX3) (AX100/150) Supported with Navisphere Manager; not supported with Navisphere Express (CX)

10 Environment and system requirements NOTES: 1. The FLARE bundle indicates the level of software running on the subject storage system. 2. The version of the Central Monitoring Host Agent must be at least as new as the newest revision of the monitored storage systems. 3. Secure CLI can be used only with and higher versions of FLARE. 4. Use of older clients may result in anomalies in behavior. EMC recommends using a client that is at least of equal revision as the storage-system software. 10

11 Environment and system requirements Navisphere management IPv4/IPv6 support Network capabilities IPv4 address only Concurrent IPv4 & IPv6 addresses IPv6 address only Multi-system Navisphere domain Supported IPv4 only not supported Single-system Navisphere domain Supported supported supported Management port Supported supported supported Service port Supported IPv4 only supported iscsi Ports Supported IPv4 only not supported IP Sec not supported not supported not supported Host Agent Supported IPv4 only not supported Server Utility Supported IPv4 only not supported Initialization Utility Supported IPv4 only not supported Navisphere UI Supported supported supported Navisphere CLI Classic CLI supported IPv4 only not supported Java CLI supported IPv4 only not supported Secure CLI supported supported supported Distributed Event Monitoring supported IPv4 only not supported Central Event Monitoring supported IPv4 only not supported SNMP supported IPv4 only not supported Off Array Management Server supported supported supported Set Up page SP IP addresses supported supported self generated Filtering IP Management stations supported supported supported Hardware Domain Support CX series supported IPv4 only not supported AX series supported IPv4 only not supported CX3 series supported IPv4 only not supported CX4 series supported IPv4 only domain of one 11

12 Fixed problems Fixed problems This section lists significant issues that were fixed in this version or that were called out in a previous revision of the release notes. Visit the EMC Powerlink Issue Tracker website at for the most recent updates and information on previous Navisphere Host Agent, Navisphere CLI, Navisphere Storage System Initialization Utility, and Navisphere Server Utility versions. Problems fixed in update The version of Management Server is available in this package: CX4 FLARE Bundle Platforms Brief description Symptom details Solution (or workaround) Navisphere CLI A single storage processor bugcheck causes Navisphere CLI A single storage processor and Secure CLI to bugcheck causes Navisphere CLI become unresponsive due and Secure CLI to become to a CMI Listener Thread unresponsive. issue within the / management server process. Rarely under a specific set of circumstances KnowledgeBase ID: None Medium Navisphere CLI The storage processor is shown as unmanaged and new attempts to connect to the storage processor with Navisphere CLI and Secure CLI will fail Rarely under a specific set of circumstances Medium An internal memory object gets corrupted and causes the management server process to hang and eventually restart. During this period the storage processor is shown as unmanaged and new attempts to connect to the storage processor with Navisphere CLI and Secure CLI will fail. KnowledgeBase ID: None

13 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Navisphere CLI A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive Rarely under a rare set of circumstances Medium Navisphere CLI An engineering level event is displayed in the getlog command output Always Navisphere CLI The storage processor is shown as unmanaged and new attempts to connect to the storage processor with Navisphere CLI and Secure CLI will fail Rarely under a specific set of circumstances Medium A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive due to deleted memory reuse within the management server process. KnowledgeBase ID: None An engineering level event is displayed in the getlog command output. The event should not be displayed: A 05/12/09 01:00:35 Flaredrv Bus 0 disk 6c status: KnowledgeBase ID: None An internal object is not deleted and causes the management server process to hang and eventually restart. During this period the storage processor is shown as unmanaged and new attempts to connect to the storage processor with Navisphere CLI and Secure CLI will fail. KnowledgeBase ID: None

14 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Navisphere CLI SP logs (getlog command) are filled with the informational SP logs (getlog command) are message: Internal filled with the informational Information message: Internal only. PSM File Information only. "AlertProviderIn PSM File fo.xml" Deleted. "AlertProviderInfo.x This happens because the ml" Deleted. management server is / deleting the / Always AlerProviderInfo.xml psm file and creating a new one. KnowledgeBase ID: None Navisphere CLI During an NDU from version 6.28 to version 6.29 a single storage processor bugcheck causes Navisphere Manager to become unresponsive Always under a specific set of circumstances Medium Navisphere CLI A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive Rarely under a specific set of circumstances Medium A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive due to the management server process becoming stuck in an infinite loop. KnowledgeBase ID: None A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive due to TLD double delete within the management server process, specifically within QoS. KnowledgeBase ID: None

15 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Linux Response time for the Secure CLI getlun command is slow with large configurations Always under a specific set of circumstances Navisphere CLI CLI and Secure CLI commands take a long time to run on SUSE 10 Linux systems / Always under a specific set of circumstances Navisphere Host Agent When installing the host agent on a system that uses iscsi, the installer reboots the system when the user completes the installation Always under a specific set of circumstances Medium Response time for the Secure CLI getlun command is slow with large configurations. KnowledgeBase ID: None CLI and Secure CLI commands take a long time to run on SUSE 10 Linux systems. KnowledgeBase ID: None When installing the host agent on a system using iscsi, the installer reboots the system when the user completes the installation. The user expects a reboot now or later option and not an immediate reboot. KnowledgeBase ID: None Added the reboot now or later option at the end of the installation

16 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Linux Solaris HP-UX VMWare AIX Solaris AIX Navisphere Host Agent Centralized monitors cannot contact the storage processors to gather events if the storage system has the classic CLI option disabled (it is enabled by default) / Always under a specific set of circumstances Issuing a getlun command with the xml switch does not always return properly formatted xml Infrequently under a specific set of circumstances. Secure CLI commands will crash (core dump); then they experience a network timeout Always under a specific set of circumstances Medium Centralized monitors cannot contact the storage processors to gather events if the storage system has the classic CLI option disabled (it is enabled by default). KnowledgeBase ID: None Issuing a getlun command with the xml switch will return improperly formatted xml if you have specified subcommands that require stats logging to be enabled on the storage system when it is not enabled. The disk information will be compounded together rather than each disk having its own element. KnowledgeBase ID: None Secure CLI commands will crash (core dump); then they experience a network timeout. KnowledgeBase ID: None Enable stats logging on the storage system

17 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Windows Navisphere Server Utility The Navisphere Server Utility does not properly update the Windows Registry for TCP/IP settings when the iscsi option is selected during installation Always under a specific set of circumstances The metalun list command does not show performance counters for Non Zero Request Count Arrivals or Sum Outstanding Results Always under a specific set of circumstances The metalun list command takes a long time to run Always under a specific set of circumstances The ndu -list -xml command gives non-xml output Always under a specific set of circumstances The Navisphere Server Utility does not properly update the Windows Registry for TCP/IP settings when the iscsi option is selected during installation. KnowledgeBase ID: None The metalun list command does not show performance counters for Non Zero Request Count Arrivals or Sum Outstanding Results. KnowledgeBase ID: None The metalun list command takes a long time to run. Performance improvements were made to improve the response time. KnowledgeBase ID: None The naviseccli ndu -list -xml command gives nonxml output. KnowledgeBase ID: None The -nzrca and sor switches were added to the metalun list command to show these counters

18 Fixed problems Platforms Brief description Symptom details Solution (or workaround) The backendbus get physical The naviseccli backendbus get xml command and the physical -xml command ioportconfig list xml and the ioportconfig list command give non-xml output. xml are giving non-xml output. KnowledgeBase ID: None Always under a specific set of circumstances HP-UX Navisphere CLI For hot spare disk output only,the getdisk command does not work correctly (bus info may be incorrect) / Always under a specific set of circumstances Navisphere Host Agent Navisphere Host Agent terminates upon startup / Always under a specific set of circumstances Medium For hot spare disk output only,the getdisk command does not work correctly if the bus id is 4 or greater. If the bus id is less than 4 the disk information will be reported correctly (for example, 2_1_10). If the bus id is 4 or greater the disk information will be truncated (for example, 1_10). Only the hot spare output for buses >= 4 is affected; all other getdisk output is correct. KnowledgeBase ID: None Navisphere Host Agent terminates upon startup when it attempts to verify whether the PowerPath library is being used. KnowledgeBase ID: None

19 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Linux The storagegroup list -xml command gives non-xml output Always under a specific set of circumstances Navisphere CLI The rebuild priority with the bind command is not set correctly Always under a specific set of circumstances On a system that is running IA64 Linux, cannot execute any command Always under a specific set of circumstances The naviseccli storagegroup list xml command gives non-xml output. KnowledgeBase ID: None The rebuild priority with the bind command is not set correctly. This applies to a CLI bind command that is issued to a version 6.29 or later system. KnowledgeBase ID: None On a system that is running IA64 Linux, cannot execute any command due to a change in the uname family info (returned as string vs. number). KnowledgeBase ID: None

20 Fixed problems Problems fixed in update Platforms Brief description Symptom details Solution (or workaround) HP-UX Navisphere Host Agent When an HP-UX host is Navisphere Host Agent takes a connected to a Symmetrix long time to start up when an storage system, it takes HP-UX system is connected to a long time for the Symmetrix storage system. Navisphere Host Agent to / start up. This happens only if the storage system has volumes that are in a Always under a specific set of Not Ready state and circumstances PowerPath or PVLinks is Medium not installed. KnowledgeBase ID: None Linux Navisphere SecureCLI does not work on SUSE Linux IA 64 systems Always under a specific set of circumstances Medium When issuing a Secure CLI bind command, the rebuild priority cannot be set to LOW, MEDIUM, or ASAP. The command will return success but the actual value will be HIGH Always under a specific set of circumstances does not work on SUSE Linux IA 64 systems. KnowledgeBase ID: None When issuing a Secure CLI bind command, the rebuild priority cannot be set to LOW, MEDIUM, or ASAP. The command will return success but the actual value will be HIGH. KnowledgeBase ID: None

21 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Solaris Navisphere Host Agent LUN mapping switches back and forth between the physical device name and the logical mount point / Frequently under a specific set of circumstances The vague message Corrupt or invalid package file is returned for the ndu install command if there is not enough space on the storage processor to transfer the file Always under a specific set of circumstances Navisphere Host Agent Centralized monitors (Host Agents) notify clients of old events / Rarely under a specific set of circumstances High LUN mapping switches back and forth between the physical device name and the logical mount point. KnowledgeBase ID: None The vague message Corrupt or invalid package file is returned for the ndu install command if there is not enough space on the storage processor to transfer the file. KnowledgeBase ID: None Centralized monitors (Host Agents) notify clients of old events. The storage processor sends back the entire event log instead of just the events that have happened since the last time new events were requested. KnowledgeBase ID: emc

22 Fixed problems Platforms Brief description Symptom details Solution (or workaround) The backendbus analyze and backendbus resetspeed commands fail if np is included on the command line Always under a specific set of circumstances The backendbus analyze and backendbus resetspeed commands fail if np is included on the command line. KnowledgeBase ID: None now properly processes the np switch Navisphere Server Utility Starting a snapshot fails with Error: 0x3E (attempted the operation on the non-active path. Please retry the operation) Rarely under a specific set of circumstances The XML generated when using the xml switch with the getall command is not valid and cannot be read by standard XML viewers Always under a specific set of circumstances Starting a snapshot fails with Error: 0x3E (attempted the operation on the non-active path. Please retry the operation). This happens only when there are inactive paths to the source LUN. KnowledgeBase ID: None The XML generated when using the xml switch with the getall command is not valid and cannot be read by standard XML viewers. KnowledgeBase ID: None

23 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Linux The thinlun -list -opdetails command displays only the error code Always under a specific set of circumstances Navisphere Host Agent A performance issue exists with centralized monitors that cause the host agent to take a long time to start up Always under a specific set of circumstances High When a Secure CLI command encounters a timeout, the application aborts instead of exiting gracefully Always under a specific set of circumstances Medium Navisphere CLI A single storage processor bugcheck (0xe ) causes commands to fail / Rarely under a specific set of circumstances Medium The thinlun -list - opdetails command displays only the error code and does not display a textual description of the error. KnowledgeBase ID: None A performance issue exists with centralized monitors that cause the host agent to take a long time to initially startup. The startup time will get longer as the number of storage systems being monitored increases. KnowledgeBase ID: None When a Secure CLI command encounters a timeout, the application aborts instead of exiting gracefully. KnowledgeBase ID: None A single storage processor bugcheck (0xe ) causes commands to fail. KnowledgeBase ID: None Exists in version:

24 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Navisphere CLI The getcrus encdrivetype command The getcrus encdrivetype may display Unknown command may display for the enclosure drive Unknown for the enclosure type if one of the disks drive type. within the enclosure has an Unknown drive type KnowledgeBase ID: None Rarely under a specific set of circumstances Canceling a storage pool expansion results in a subroutine failure (0x c) Rarely under a rare set of circumstances Medium Storage pools are displayed as Offline when a disk within the storage pool is removed or the enclosure containing the disk is powered off Rarely under a specific set of circumstances Canceling a storage pool expansion results in a subroutine failure (0x c) if the newly added disks become faulted before the actual cancel operation is attempted. KnowledgeBase ID: None Storage pools are displayed as Offline when a disk within the storage pool is removed or the enclosure containing the disk is powered off. KnowledgeBase ID: None Exists in version: Exists in version:

25 Fixed problems Platforms Brief description Symptom details Solution (or workaround) If the verification of a storage pool fails because of a lack of space, you can no longer expand the storage pool. Eventually the storage pool may run out of space and I/O will start failing Always under a specific set of circumstances Medium Problems fixed in update x.x If the verification of a storage pool fails because of a lack of space, you can no longer expand the storage pool. Eventually the storage pool may run out of space and I/O will start failing. KnowledgeBase ID: None You can now expand a storage pool that has failed verification. Exists in version: Platforms Brief description Symptom details Solution (or workaround) Navisphere Host Agent For events that are new to Exists in version: When events are viewed through the CX4 series storage the UI or CLI while a CX4 series systems and that are storage system is centrally logged for devices in the monitored, sometimes the Device SPE enclosure, the device field is N/A. field will appear as N/A when viewed through the UI or CLI. NOTE: This issue applies Always under the circumstances only when using central mentioned above monitoring to gather and view events. This does not apply to distributed monitoring. Solaris Navisphere Host Agent Navisphere Host Agent does not collect information about disks with EFI labels accurately / , Always under the circumstances mentioned above Navisphere CLI lunmapinfo and lun mount point information in the Navisphere UI does not show accurate information. This happens if the host has disks with EFI labels. Exists in version:

26 Fixed problems Problems fixed in update Platforms Brief description Symptom details Solution (or workaround) HP-UX, AIX, Linux, Solaris Navisphere CLI Navisphere CLI snapshots, SAN Copy and Mirrorview sync commands need to be executed with full path Always Medium Linux Navisphere Server Utility - HAVT Issues summary gives the error The version of PowerPath installed does not support iscsi storage systems Always Critical Navisphere CLI snapshots, SAN Copy and Mirrorview sync commands do not produce any output on UNIX platforms. This occurs when you run Classic CLI commands outside of an installed directory and you have not added CLI to their path. Underlying Secure CLI is not called as the CLI does not know the path for launching. This does not occur on Windows because Windows installer asks if you wish to add to the path. When running PowerPath on Linux, you need to run a special script after installation if the server will be connected to an iscsi storage system. If the script is not run, the HAVT will output the message: This version of PowerPath doesn't support iscsi. The message is slightly misleading and should probably read A required script was not run when PowerPath was installed. This script is required to be run if connecting to iscsi arrays

27 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Windows and Solaris CX3-10c Navisphere Server Utility - HAVT Failover mode 4 support for HAVT appears as unsupported Rarely under a rare set of circumstances. Navisphere CLI The spportspeed command in version 6.26 Secure CLI fails on a version storage system Always under a rare set of circumstances Navisphere CLI The domain -add command for adding CIMOM to the domain does not work when targeted against an off-array CIMOM Always under the circumstances indicated. Navisphere Storage System Initialization Utility The initialization utility does not apply iscsi port settings properly for CX3-10c storage systems Rarely under rare set of circumstances. Navisphere Server Utility HAVT shows Windows/Solaris PowerPath 5.1 with failovermode 4 as unsupported. Failover mode 4 should be supported in ALUA configurations; therefore this issue is a "false positive". The spportspeed command in version 6.26 Secure CLI on a version storage system will return Too many parameters. This is a misleading message. When the Navisphere CLI domain add command is used, it will return the following error Internal error in Management Server. Running the utility against an uninitialized storage system does not always result in the iscsi port settings being applied (that is, IP, gateway, and net mask). The storagesystem name, security settings, and management port settings are correctly set in all cases

28 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Navisphere Server Utility The naviserverutilcli The Navisphere Server Utility contains incorrect usage contains incorrect usage strings. strings for the startsnapshot, stopsnapshot, allowaccess and Always removeaccess commands. Each of the commands contain a - when they should not For example: Expected: -startsnap -s <snapshot name> -o <device name> should be displayed as: Expected: startsnap -s <snapshot name> -o <device name> Windows 2000, Windows 2003, Windows XP and Windows Vista Linux Navisphere Host Agent When running NaviAgent.exe in silent mode, the agent configuration initialization fails to create the agent.configuration file Always Navisphere Host Agent Navisphere Agent terminates on Linux Always Medium A warning message will be entered in the Computer Management Application log stating EV_AttachedServe r::ev_attachedse rver: PollServerAttrib utes() returned error: No configuration information could be loaded The agent.configuration file will not be present in the host agent installation directory. Navisphere Agent starts properly on Linux but then kills itself if the number of open connections exceeds Exists in version:

29 Fixed problems Platforms Brief description Symptom details Solution (or workaround) Navisphere Server Utility - HAVT Navisphere Server Utility shows a success status even if the initiators are not fully registered Rarely After registering initiators using the Navisphere Server Utility the initiator may appear as logged in but not registered even though the server utility displays a success message. previous

30 Known problems and limitations Known problems and limitations This section identifies: current bugs likely to be of interest to all customers, functionality that is intentionally not included, but may be expected, issues, such as known performance limits under certain conditions. Visit the EMC Powerlink Issue Tracker website at for the most recent updates and information on previous Navisphere Host Agent, Navisphere CLI, Navisphere Storage System Initialization Utility, and Navisphere Server Utility versions. Platforms Brief description Symptom details Solution (or workaround) Navisphere Initialization Use the Navisphere There are two workarounds: Tool Initialization Tool to set-up Back up to the discovery an iscsi storage system. screen and use the The Navisphere Initialization 1. Select the storage discover again option to Tool will skip over the iscsi system -discovery recapture the iscsi port page if the back button is page (click Next) information for the clicked. 2. Enter the IP address storage system and then (click Next) continue through the 3. Enter the iscsi IP wizard. Always under a specific set of address (click Next) Continue through the circumstances Initialization Tool and 4. Go to the Change the leave the iscsi ports name and Initialize Medium uninitialized. Then use management security Manager or Express later page. (click Back) to configure the iscsi Instead of going to the ports. iscsi IP address page, if the system sends you to the IP address page clicking Next once again skips the iscsi page as well

31 Known problems and limitations Platforms Brief description Symptom details Solution (or workaround) Navisphere CLI The disk firmware update command uses bus 0 as a default Always The arrayconfig -rollback command may delete the user configuration Always under a specific set of circumstances The arrayconfig commands do not copy SAN Copy sessions Always Critical If you use 0_10 to specify the disk, bus 0 is automatically assumed as the specified bus in the CLI. After a successful duplication, if you destroy a RAID group and create another RAID group with the same ID (even if it is a different type), the rollback will destroy the newly created RAID group as well. If you set up SAN Copy sessions and perform an arrayconfig -capture/-duplicate sequence, the SAN Copy sessions are not present. This is the way the CLI behaves for several other commands as well. Use the b_e_d format to indicate a different bus Make sure the new RAID group has a different ID None. The SAN Copy configuration is not supported with the arrayconfig command

32 Known problems and limitations Platforms Brief description Symptom details Solution (or workaround) The sancopy -create command may fail Always under a specific set of circumstances Medium For the firmware command, Secure CLI automatically copies the firmware file to the storage system Always The mirrorview -add image command may fail Always under a specific set of circumstances Medium If you are creating a SAN Copy session with version 6.24 as the source and version 6.22 as the destination, the command will fail. The firmware command ignores the -c command that was used in classic CLI when the firmware file was not located on the storage system. Now it will copy the local firmware file to the storage system. If you are creating a MirrorView image, the command will fail if you supply a hostname for the -array host parameter. The version 6.22 destination storage system must be part of the SAN Copy domain. Or use Navisphere Manager to create the SAN Copy sessions None You must supply an IP address for the -array host parameter

33 Known problems and limitations Platforms Brief description Symptom details Solution (or workaround) AX4-5 AX4-5i AX4-SC AX4-5SCi AX4-5 AX4-5i AX4-SC AX4-5SCi If naviseccli is used to create a SAN Copy session using -destlunnumber, the operation will fail with a Caller not privileged error Always If the Mirror Write Intent Log is allocated, and then reallocated, the peer SP will not reflect the changes when the naviseccli mirror -sync -listlog command is issued. Always Medium This is a naviseccli limitation for SAN Copy commands and occurs because the request is being blocked. This will occur when creating a session between AX4-5 storage systems but will work when the target is an older revision. The mirror -allocatelog command sets the write intent log LUNs for SP A and SP B. If previous values exist, the mirror -listlog command on the peer SP will not reflect the new values. If no previous values existed, the peer SP will display the correct information. Use destwwn instead of -destlunnumber or use the UI Restarting the management server will clear up this problem. Steps for Navisphere Express users : 1. Navigate to the Services page with the menu item on the left side of the screen. 2. Click the Restart Navisphere Express button Steps for Navisphere Manager users: 1. Open a browser to 2. Log in 3. Click the Restart Management Server button

34 Known problems and limitations Platforms Brief description Symptom details Solution (or workaround) AX4-5 AX4-5i AX4-SC AX4-5SCi AX4-5 AX4-5i AX4-SC AX4-5SCi If an SPS is removed and reinserted, the power and cooling module on that SP may be reported as faulted. Sometimes A LUN may become unowned if a consistent SnapView session is repeatedly started and stopped Sometimes This problem occurs only on storage systems that have two SPs, but only one SPS. If the SPS is removed, the SPS status is reported correctly, but the power and cooling module may also be reported as faulted (without any explanation). Even after the SPS is replaced and fully recharged, Navisphere will continue to show the power and cooling module as faulted. This problem occurs when a Snapview session is started and stopped several times in rapid succession. A LUN may temporarily become unowned in this situation. Restarting the management server will clear up this problem. Steps for Navisphere Express users : 1. Navigate to the Services page with the menu item on the left side of the screen. 2. Click the Restart Navisphere Express button Steps for Navisphere Manager users: 1. Open a browser to 2. Log in 3. Click the Restart Management Server button Waiting for the next poll cycle, or issuing any Secure CLI command that causes a poll to occur should resolve the LUN ownership issue

35 Known problems and limitations Platforms Brief description Symptom details Solution (or workaround) Navisphere Server Utility - HAVT Resetting the default location during installation after choosing a different location may not correctly reset the application default location in subsequent screens Always Windows 2000, Windows 2003, Windows XP, Windows Vista Solaris Opteron Server Support CD The link Browse CD Contents opens another Internet Explorer window to the same page Rarely under a rare set of circumstances. Server Support CD The PDF documents cannot be read on Opteron hardware Always While installing the Navisphere Server Utility if the default installation folder is modified and restored, the restored location will be the application default and not the user default. This default location can be misleading and can result in an undesired installation location. If you click the Browse CD Contents link while using Microsoft Internet Explorer version 7 and the Windows autorun feature is turned on, the browser will open another Internet Explorer window to the same html page. The following error message will be displayed when attempting to open a PDF document on Opteron hardware. An attempt to execute the following command failed: acroread Make sure that the program exists and the file has the correct permissions and is executable. If you have changed the default installation location and subsequently attempted to restore the default location, verify that the installer reports your intended location. Input the location directly if necessary Use Windows Explorer to browse the CD contents. Turn off the Windows autorun feature and then click the Browse CD Contents link At this time Acrobat Reader is not available for Solaris OS running on Opteron hardware. Use another OS that has Acrobat Reader installed

36 Known problems and limitations Platforms Brief description Symptom details Solution (or workaround) The following error is None Navisphere networkadmin returned when network -set returns an error when the admin set command is command is successful issued to change the IP address of the SP: A network error occurred while Always trying to connect:: 'a.b.c.d' (IPAddress). Message : Error occurred because of time out The command will successfully change the IP address, but since changing the IP address in Windows takes effect immediately (even before a reboot) the client CLI gets disconnected from the SP and shows this message. Windows 2008 Server Core installation Navisphere CLI tries to install multipart bundles and fails with an error Always with an unsupported list file Medium Navisphere Server Utility - Installation In the installation step "Choose High Availability reports folder", the choose button will not allow a new folder to be selected. Always When you attempt to install a multipart, sequentially installed bundle with Secure CLI, you will see the message: Cannot install two revisions of the same package at once (0x e) When you press the choose button, a popup window appears with no options to select another folder. This is a Server Core limitation that does not support the Windows Explorer UI, which is required by the installation software to select or create a new folder. Use the NST to install the bundle Accept the default folder. Copy the report manually to a separate directory when needed. Installing and running the Navisphere Server Utility on a Server Core installation is not recommended

37 Known problems and limitations Platforms Brief description Symptom details Solution (or workaround) Windows 2008 Server Core installation Navisphere Server Utility - HAVT The Display issues report button does not work. A prompt window will be shown with the error message: Windows cannot find 'iexplorer'. Make sure you typed the name correctly, and then try again. Always File transfer commands will fail when connected to the storage system with an IPv6 connection Likely under a specific set of circumstances A Server Core installation does not support any graphical software, including Internet Explorer, which is needed to view the report. When using an IPv6 address to connect to an SP from Secure CLI, the managefiles -retrieve and -delete subcommands fail. Copy the report to another machine with an appropriate xml file viewer, and then view the report on this second machine. Running Navisphere Server Utility on a Server Core installation is not recommended Workarounds for this problem include: using the Navisphere Management UI managefiles interface with an IPv4 or IPv6 address and connecting to the SP from Secure CLI using an IPv4 address