Navi Agent

1

EMC Navisphere

Host Agent/CLI and Utilities Version 6.28.21 for FLARE OE

02.23.050.5.yyy, 02.24.xxx.5.yyy, 02.26.xxx.5.yyy, 03.24.xxx.5.yyy, 03.26.xxx.5.yyy

and 04.28.000.5.yyy

Release Notes P/N 300-007-053

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

Topics include:

Revision history.......................................................................................... 2 Product description ................................................................................... 2 New features and changes........................................................................ 5 Environment and system requirements.................................................. 6 Fixed problems......................................................................................... 12 Known problems and limitations .......................................................... 30 Technical notes ......................................................................................... 45 Documentation......................................................................................... 91 Software media, organization, and files ............................................... 94 Installation ................................................................................................ 94 Troubleshooting and getting help ......................................................... 95

2

Revision history

EMC Navisphere Host Agent/CLI and Utilities and 04.28.000.5.yyy Release Notes

Revision history

The following table presents the revision history of this document.

Revision Date Description

A06 September 30, 2009 Added changes made for version 6.28.21.x.x

A05 March 3, 2009 Added changes made for version 6.28.20.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

(189937 and 203863)

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

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

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.

5

New features and changes


New features and changes

New features in version 6.28.21.x

None.


None.


Version 6.28.10.x of the product adds support for Linux distributions on IBM Power Series servers.


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

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 Navisphere Secure CLI will be the command line client of choice going forward. Whenever possible scripts using CLI commands should use Navisphere Secure CLI (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.


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

Minimum hardware requirements Minimum software requirements

Solaris 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

Sun Solaris 9, 10 (SPARC), Solaris 10 on x86 compatible servers (Opteron). Note: Only Navisphere Server Utility, Inittool and Navisphere Secure CLI 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.

7



Operating system

Minimum hardware requirements Minimum software requirements

Windows Intel-compatible PC with 64 MB of RAM and at least 30 MB of free disk space.

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: All utilities are supported on IA64 systems as well. For iSCSI support, iSCSI initiator driver should be version 2.4 or higher.

AIX IBM AIX workstation with at least 64 MB of RAM and 14 MB of free disk space.

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.11.11.0612.459 Base Patches for HP-UX 11i v1, December 2006”.

HP-UX HP server with at least 30 MB of free disk space and 64 MB of RAM.

Other TCP/IP protocol installed and configured.

Linux An Intel-compatible, processor-based system capable of accepting PCI HBAs, with at least 200 MB of free disk space and 64 MB RAM.

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.

VMware VMware ESX Server with sufficient memory and disk space.

OS ESX 3.0 ESX 3.0.1 ESX 3.0.2 ESX 3.5.0

IBM Power Linux

OS Red Hat Enterprise Server RHEL 5 and Novell/SUSE Enterprise Server SLES 10.

8



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:

FLARE Host Agent Server Utility

Classic CLI Initialization Utility Secure CLI

Off-Array Manager

04.28 (CX4) 6.28 6.26.5 6.24 6.22 6.20 6.19

6.28 6.28 6.26.5 6.24 6.22 6.20 6.19

6.28

02.23.050.5 (AX4-5)

6.28 6.26.5 Supported with Navisphere Manager ;not supported with Navisphere Express

6.28 6.26.5 Classic CLI is not supported on AX4-5

6.28 6.26.5

6.28 6.26.5

9



FLARE Host Agent Server Utility

Classic CLI Initialization Utility Secure CLI

Off-Array Manager

03.26 (CX3), 02.26 (CX)

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26

03.24 (CX3), 02.24 (CX)

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26 6.24

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26 6.24

03.22 (CX3) 6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26 6.24 6.22.20 6.22

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26 6.24 6.22.20

02.20 (AX100/150)

6.28 6.26 6.24 6.22.20 6.22 6.20 Supported with Navisphere Manager; not supported with Navisphere Express

6.28 6.26 6.24 6.22.20 6.22 6.20

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26 6.24 6.22.20 6.22 6.20

02.19 (CX)

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

6.28 6.26 6.24 6.22.20 6.22 6.20 6.19

10



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

11



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

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 http://Powerlink.EMC.com 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 6.28.21.0.27

The 6.28.21.0.39 version of Management Server is available in this package:

CX4 FLARE Bundle 04.28.000.5.707

Platforms Brief description Symptom details Solution (or workaround)

All Navisphere CLI Navisphere Secure CLI A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive. 30426530 / 232402 Frequency of occurrence: Rarely under a specific set of circumstances Severity: Medium

A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive due to a CMI Listener Thread issue within the management server process. KnowledgeBase ID: None

Exists in versions: 6.28.0.4.31 6.28.0.4.32 6.28.10.3.19 6.28.20.1.40 Fixed in version: 6.28.21.0.27

All Navisphere CLI Navisphere Secure 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. 229857 Frequency of occurrence: Rarely under a specific set of circumstances Severity: 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


http://powerlink.emc.com/

13

Fixed problems



All Navisphere CLI Navisphere Secure CLI A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive. 230751 Frequency of occurrence: Rarely under a rare set of circumstances Severity: 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


All Navisphere CLI Navisphere Secure CLI An engineering level event is displayed in the getlog command output. 230804 Frequency of occurrence: Always Severity: Low

An engineering level event is displayed in the getlog command output. The 71270006 event should not be displayed: A 05/12/09 01:00:35 Flaredrv 71270006 Bus 0 disk 6c status:

KnowledgeBase ID: None


All Navisphere CLI Navisphere Secure 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. 233402 Frequency of occurrence: Rarely under a specific set of circumstances Severity: Medium

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



All Navisphere CLI Navisphere Secure CLI SP logs (getlog command) are filled with the informational message: Internal Information only. PSM File "AlertProviderInfo.xml" Deleted. 29897990 / 229008 29916784 / 229502 Frequency of occurrence: Always Severity: Low

SP logs (getlog command) are filled with the informational message: Internal Information only. PSM File "AlertProviderInfo.xml" Deleted. This happens because the management server is deleting the AlerProviderInfo.xml psm file and creating a new one. KnowledgeBase ID: None


All Navisphere CLI Navisphere Secure CLI During an NDU from version 6.28 to version 6.29 a single storage processor bugcheck causes Navisphere Manager to become unresponsive. 235467 Frequency of occurrence: Always under a specific set of circumstances Severity: 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


All Navisphere CLI Navisphere Secure CLI A single storage processor bugcheck causes Navisphere CLI and Secure CLI to become unresponsive. 233051 Frequency of occurrence: Rarely under a specific set of circumstances Severity: Medium

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



All Navisphere Secure CLI Response time for the Secure CLI getlun command is slow with large configurations. 227020 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

Response time for the Secure CLI getlun command is slow with large configurations. KnowledgeBase ID: None


Linux Navisphere CLI Navisphere Secure CLI CLI and Secure CLI commands take a long time to run on SUSE 10 Linux systems. 27916664 / 226159 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

CLI and Secure CLI commands take a long time to run on SUSE 10 Linux systems. KnowledgeBase ID: None


All 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. 226984 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

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. Exists in versions: 6.28.0.4.31 6.28.0.4.32 6.28.10.3.19 6.28.20.1.40 Fixed in version: 6.28.21.0.27

16

Fixed problems



Linux Solaris HP-UX VMWare 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). 29696572 / 227488 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

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


All Navisphere Secure CLI Issuing a getlun command with the –xml switch does not always return properly formatted xml. 224196 Frequency of occurrence: Infrequently under a specific set of circumstances. Severity: Low

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

Enable stats logging on the storage system. Exists in versions: 6.28.0.4.31 6.28.0.4.32 6.28.10.3.19 6.28.20.1.40 Fixed in version: 6.28.21.0.27

Solaris AIX

Navisphere Secure CLI All Secure CLI commands will crash (core dump); then they experience a network timeout. 228334 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

All Secure CLI commands will crash (core dump); then they experience a network timeout. KnowledgeBase ID: None


17

Fixed problems



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. 228795 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

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


All Navisphere Secure CLI The metalun –list command does not show performance counters for Non Zero Request Count Arrivals or Sum Outstanding Results. 225309 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

The metalun –list command does not show performance counters for Non Zero Request Count Arrivals or Sum Outstanding Results. KnowledgeBase ID: None

The -nzrca and –sor switches were added to the metalun –list command to show these counters. Exists in versions: 6.28.0.4.31 6.28.0.4.32 6.28.10.3.19 6.28.20.1.40 Fixed in version: 6.28.21.0.27

All Navisphere Secure CLI The metalun –list command takes a long time to run. 231291 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

The metalun –list command takes a long time to run. Performance improvements were made to improve the response time. KnowledgeBase ID: None


All Navisphere Secure CLI The ndu -list -xml command gives non-xml output. 224195 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

The naviseccli ndu -list -xml command gives non-xml output. KnowledgeBase ID: None


18

Fixed problems



All Navisphere Secure CLI The backendbus –get –physical -xml command and the ioportconfig –list –xml command give non-xml output. 219108 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

The naviseccli backendbus –get –physical -xml command and the ioportconfig –list –xml are giving non-xml output. KnowledgeBase ID: None


All Navisphere CLI Navisphere Secure CLI For hot spare disk output only,the getdisk command does not work correctly (bus info may be incorrect). 30630484 / 233248 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

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


HP-UX Navisphere Host Agent Navisphere Host Agent terminates upon startup. 30346392 / 231434 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

Navisphere Host Agent terminates upon startup when it attempts to verify whether the PowerPath® library is being used. KnowledgeBase ID: None


19

Fixed problems



All Navisphere Secure CLI The storagegroup –list -xml command gives non-xml output. 224166 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

The naviseccli storagegroup –list –xml command gives non-xml output. KnowledgeBase ID: None


All Navisphere CLI Navisphere Secure CLI The rebuild priority with the bind command is not set correctly. 230772 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

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


Linux Navisphere Secure CLI On a system that is running IA64 Linux, Navisphere Secure CLI cannot execute any command. 231461 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

On a system that is running IA64 Linux, Navisphere Secure CLI 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 6.28.20.1.40


HP-UX Navisphere Host Agent Navisphere Host Agent takes a long time to start up when an HP-UX system is connected to a Symmetrix® storage system. 27037778 / 214517 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

When an HP-UX host is connected to a Symmetrix storage system, it takes long time for the Navisphere Host Agent to start up. This happens only if the storage system has volumes that are in a Not Ready state and PowerPath or PVLinks is not installed. KnowledgeBase ID: None

Exists in versions: 6.28.0.4.31 6.28.10.3.7 Fixed in version: 6.28.20.1.40

Linux Navisphere SecureCLI Navisphere Secure CLI does not work on SUSE Linux IA 64 systems. 219917 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

Navisphere Secure CLI does not work on SUSE Linux IA 64 systems. KnowledgeBase ID: None


All Navisphere Secure CLI 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. 213821 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

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



Solaris Navisphere Host Agent LUN mapping switches back and forth between the physical device name and the logical mount point. 26196956 / 213849 Frequency of occurrence: Frequently under a specific set of circumstances Severity: Low

LUN mapping switches back and forth between the physical device name and the logical mount point. KnowledgeBase ID: None


All Navisphere Secure CLI The vague message Corrupt or invalid package file is returned for the Navisphere Secure CLI ndu –install command if there is not enough space on the storage processor to transfer the file. 210799 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

The vague message Corrupt or invalid package file is returned for the Navisphere Secure CLI ndu –install command if there is not enough space on the storage processor to transfer the file. KnowledgeBase ID: None


All Navisphere Host Agent Centralized monitors (Host Agents) notify clients of “old” events. 27005800 / 217426 Frequency of occurrence: Rarely under a specific set of circumstances Severity: High

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: emc204932


22

Fixed problems



All Navisphere Secure CLI The backendbus –analyze and backendbus –resetspeed commands fail if –np is included on the command line. 213177 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

The backendbus –analyze and backendbus –resetspeed commands fail if –np is included on the command line. KnowledgeBase ID: None

Navisphere Secure CLI now properly processes the –np switch. Exists in versions: 6.28.0.4.31 6.28.10.3.7 Fixed in version: 6.28.20.1.40

All Navisphere Server Utility Starting a snapshot fails with Error: 0x3E050071 (attempted the operation on the non-active path. Please retry the operation). 212704 Frequency of occurrence: Rarely under a specific set of circumstances Severity: Low

Starting a snapshot fails with Error: 0x3E050071 (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


All Navisphere Secure CLI The XML generated when using the –xml switch with the getall command is not valid and cannot be read by standard XML viewers. 209970 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

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



All Navisphere Secure CLI The thinlun -list -opdetails command displays only the error code. 212441 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

The thinlun -list -opdetails command displays only the error code and does not display a textual description of the error. KnowledgeBase ID: None

Exists in version: 6.28.10.3.7 Fixed in version: 6.28.20.1.40

All Navisphere Host Agent A performance issue exists with centralized monitors that cause the host agent to take a long time to start up. 215349 Frequency of occurrence: Always under a specific set of circumstances Severity: High

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


Linux Navisphere Secure CLI When a Secure CLI command encounters a timeout, the application aborts instead of exiting gracefully. 207904 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

When a Secure CLI command encounters a timeout, the application aborts instead of exiting gracefully. KnowledgeBase ID: None


All Navisphere CLI Navisphere Secure CLI A single storage processor bugcheck (0xe1198006) causes commands to fail. 26080002 / 211133 Frequency of occurrence: Rarely under a specific set of circumstances Severity: Medium

A single storage processor bugcheck (0xe1198006) causes commands to fail. KnowledgeBase ID: None


24

Fixed problems



All Navisphere CLI Navisphere Secure CLI The getcrus –encdrivetype command may display Unknown for the enclosure drive type. 213062 Frequency of occurrence: Rarely under a specific set of circumstances Severity: Low

The getcrus –encdrivetype command may display Unknown for the enclosure drive type if one of the disks within the enclosure has an Unknown drive type. KnowledgeBase ID: None


All Navisphere Secure CLI Canceling a storage pool expansion results in a subroutine failure (0x4000803c). 212008 Frequency of occurrence: Rarely under a rare set of circumstances Severity: Medium

Canceling a storage pool expansion results in a subroutine failure (0x4000803c) if the newly added disks become faulted before the actual cancel operation is attempted. KnowledgeBase ID: None


All Navisphere Secure CLI Storage pools are displayed as Offline when a disk within the storage pool is removed or the enclosure containing the disk is powered off. 212825 Frequency of occurrence: Rarely under a specific set of circumstances Severity: Low

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


25

Fixed problems



All Navisphere Secure CLI 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. 220708 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

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: 6.28.10.3.7 Fixed in version: 6.28.20.1.40

Problems fixed in update 6.28.10.x.x


All Navisphere Host Agent When events are viewed through the UI or CLI while a CX4 series storage system is centrally monitored, sometimes the Device field is N/A. 203860 Frequency of occurrence: Always under the circumstances mentioned above Severity: Low

For events that are new to the CX4 series storage systems and that are logged for devices in the SPE enclosure, the device field will appear as N/A when viewed through the UI or CLI. NOTE: This issue applies only when using central 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. 21958358 / 189937, Frequency of occurrence: Always under the circumstances mentioned above Severity: Low

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.


26

Fixed problems


Problems fixed in update 6.28.0


HP-UX, AIX, Linux, Solaris

Navisphere CLI Navisphere CLI snapshots, SAN Copy and Mirrorview –sync commands need to be executed with full path. 174832 Frequency of occurrence: Always Severity: Medium

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.

Exists in versions: 6.26.7.0.81 6.26.5 6.26.0.2.24 6.24.0.6.13 Fixed in version: 6.28.0

Linux Navisphere Server Utility -

HAVT

Issues summary gives the error The version of PowerPath installed does not support iSCSI storage systems. 159139 Frequency of occurrence: Always Severity: Critical

When running PowerPath 4.3.3 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..

Exists in versions: 6.24.0.6.12 6.26.0.2.24 6.26.5 6.26.7.0.81 Fixed in version: 6.28.0

27

Fixed problems



Windows and Solaris

Navisphere Server Utility - HAVT Failover mode 4 support for HAVT appears as unsupported. 175719 Frequency of occurrence: Rarely under a rare set of circumstances. Severity: Low

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

Exists in versions: 6.26.0.2.24 6.26.5 6.26.7.0.81 Fixed in version: 6.28.0

All Navisphere CLI The spportspeed command in version 6.26 Secure CLI fails on a version 03.22 storage system. 176803 Frequency of occurrence: Always under a rare set of circumstances Severity: Low

The spportspeed command in version 6.26 Secure CLI on a version 03.22 storage system will return Too many parameters. This is a misleading message.

Exists in versions:

6.26.0.2.24

6.26.5 6.26.7.0.81 Fixed in version: 6.28.0

All Navisphere CLI The Navisphere Secure CLI domain -add command for adding CIMOM to the domain does not work when targeted against an off-array CIMOM. 177056 Frequency of occurrence: Always under the circumstances indicated. Severity: Low

When the Navisphere CLI domain –add command is used, it will return the following error – Internal error in Management Server.


CX3- 10c

Navisphere Storage System Initialization Utility The initialization utility does not apply iSCSI port settings properly for CX3-10c storage systems. 176941 Frequency of occurrence: Rarely under rare set of circumstances. Severity: Low

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 storage-system name, security settings, and management port settings are correctly set in all cases.


28

Fixed problems



All Navisphere Server Utility The Navisphere Server Utility contains incorrect usage strings. 192956 Frequency of occurrence: Always Severity: Low

The naviserverutilcli contains incorrect usage strings for the startsnapshot, stopsnapshot, allowaccess and 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>

Exists in versions: 6.24.0.6.12

6.26.0.2.24

6.26.0.5 6.26.5 6.26.7.0.81 Fixed in version: 6.28.0

Windows 2000, Windows 2003, Windows XP and Windows Vista

Navisphere Host Agent When running NaviAgent.exe in silent mode, the agent configuration initialization fails to create the agent.configuration file. 192992 Frequency of occurrence: Always Severity: Low

A warning message will be entered in the Computer Management Application log stating EV_AttachedServer::EV_AttachedServer: PollServerAttributes() returned error: No configuration information could be loaded The agent.configuration file will not be present in the host agent installation directory.

Exists in versions: 6.26.5 6.26.7.0.81 Fixed in version: 6.28.0

Linux Navisphere Host Agent Navisphere Agent terminates on Linux. 185083 Frequency of occurrence: Always Severity: Medium

Navisphere Agent starts properly on Linux but then kills itself if the number of open connections exceeds 1024.

Exists in version: 6.26.0 Fixed in version: 6.28.0

29

Fixed problems



All Navisphere Server Utility - HAVT Navisphere Server Utility shows a success status even if the initiators are not fully registered. 191642 Frequency of occurrence: Rarely Severity: Low

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.

Exists in versions: All previous Fixed in version: 6.28.0

30

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 http://Powerlink.EMC.com for the most recent updates and information on previous Navisphere Host Agent, Navisphere CLI, Navisphere Storage System Initialization Utility, and Navisphere Server Utility versions.


All

Navisphere Initialization

Tool

The Navisphere Initialization Tool will skip over the iSCSI page if the back button is clicked. 203961 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

Use the Navisphere Initialization Tool to set-up an iSCSI storage system. 1. Select the storage

system -discovery page (click Next)

2. Enter the IP address (click Next)

3. Enter the iSCSI IP address (click Next)

4. Go to the Change the name and Initialize management security page. (click Back)

Instead of going to the iSCSI IP address page, if the system sends you to the IP address page. clicking Next once again skips the iSCSI page as well.

There are two workarounds: • Back up to the discovery

screen and use the discover again option to recapture the iSCSI port information for the storage system and then continue through the wizard.

• Continue through the Initialization Tool and leave the iSCSI ports uninitialized. Then use Manager or Express later to configure the iSCSI ports.

Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27


31




All

Navisphere CLI

The disk firmware update command uses bus 0 as a default. 156450 Frequency of occurrence: Always Severity: Low

If you use 0_10 to specify the disk, bus 0 is automatically assumed as the specified bus in the CLI.

This is the way the CLI behaves for several other commands as well. Use the b_e_d format to indicate a different bus. Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All

Navisphere Secure CLI The arrayconfig -rollback command may delete the user configuration. 147897 Frequency of occurrence: Always under a specific set of circumstances Severity: Low

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.

Make sure the new RAID group has a different ID. Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All

Navisphere Secure CLI The arrayconfig commands do not copy SAN Copy sessions. 155510 Frequency of occurrence: Always Severity: Critical

If you set up SAN Copy sessions and perform an arrayconfig -capture/-duplicate sequence, the SAN Copy sessions are not present.

None. The SAN Copy configuration is not supported with the arrayconfig command. Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

32




All

Navisphere Secure CLI The sancopy -create command may fail. 156861 Frequency of occurrence: Always under a specific set of circumstances Severity: 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 version 6.22 destination storage system must be part of the SAN Copy domain. Or use Navisphere Manager to create the SAN Copy sessions. Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All

Navisphere Secure CLI For the firmware command, Secure CLI automatically copies the firmware file to the storage system. 157009 Frequency of occurrence: Always Severity: Low

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.

None. Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All

Navisphere Secure CLI The mirrorview -add image command may fail. 158010 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

If you are creating a MirrorView image, the command will fail if you supply a hostname for the -array host parameter.

You must supply an IP address for the -array host parameter. Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

33




AX4-5 AX4-5i AX4-SC AX4-5SCi

Navisphere Secure CLI If naviseccli is used to create a SAN Copy session using -destlunnumber, the operation will fail with a Caller not privileged error. 184049 Frequency of occurrence: Always Severity: Low

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.

Use –destwwn instead of -destlunnumber or use the UI. Exists in versions: 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27


Navisphere Secure CLI If the Mirror Write Intent Log is allocated, and then re-allocated, the peer SP will not reflect the changes when the naviseccli mirror -sync -listlog command is issued. Frequency of occurrence: Always Severity: Medium

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.

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

http://<sphost>/setup 2. Log in 3. Click the Restart

Management Server button.

Exists in versions: 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

34





Navisphere Secure CLI If an SPS is removed and re-inserted, the power and cooling module on that SP may be reported as faulted. Frequency of occurrence: Sometimes Severity: Low

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.

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

http://<sphost>/setup 2. Log in 3. Click the Restart

Management Server button.

Exists in versions: 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27


Navisphere Secure CLI A LUN may become unowned if a consistent SnapView session is repeatedly started and stopped. 203604 Frequency of occurrence: Sometimes Severity: Low

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.

Waiting for the next poll cycle, or issuing any Secure CLI command that causes a poll to occur should resolve the LUN ownership issue. Exists in versions: 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

35




All 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. 191253 Frequency of occurrence: Always Severity: Low

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 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. Exists in versions: 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

Windows 2000, Windows 2003, Windows XP, Windows Vista

Server Support CD The link “Browse CD Contents” opens another Internet Explorer window to the same page. 190257 Frequency of occurrence: Rarely under a rare set of circumstances. Severity: Low

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.

Use Windows Explorer to browse the CD contents. Turn off the Windows autorun feature and then click the “Browse CD Contents” link. Exists in versions: 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

Solaris Opteron

Server Support CD The PDF documents cannot be read on Opteron hardware. 193126 Frequency of occurrence: Always Severity: Low

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.

At this time Acrobat Reader is not available for Solaris OS running on Opteron hardware. Use another OS that has Acrobat Reader installed. Exists in versions: 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

36




All Navisphere Secure CLI Navisphere networkadmin -set returns an error when the command is successful 175239 Frequency of occurrence: Always Severity: Low

The following error is returned when network admin –set command is issued to change the IP address of the SP: A network error occurred while 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.

None Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All Navisphere Secure CLI Navisphere CLI tries to install multipart bundles and fails with an error. 193222 Frequency of occurrence: Always with an unsupported list file Severity: Medium

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 (0x7151801e)

Use the NST to install the bundle Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

Windows 2008 Server Core installation

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. Frequency of occurrence: Always Severity: Low

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.

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. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

37




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.

Frequency of occurrence: Always Severity: Low

A Server Core installation does not support any graphical software, including Internet Explorer, which is needed to view the report.

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. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All Navisphere Secure CLI File transfer commands will fail when connected to the storage system with an IPv6 connection. 198452 Frequency of occurrence: Likely under a specific set of circumstances Severity: Low

When using an IPv6 address to connect to an SP from Secure CLI, the managefiles -retrieve and -delete subcommands fail.

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.

Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

38




Vista Windows Server 2008

Navisphere Storage System Initialization Utility Version 6.28 of the Storage System Initialization Wizard does not work on a multihome server 200914 Frequency of occurrence: Likely under a specific set of circumstances Severity: Medium

Failure to discover storage systems on an attached subnet.

Change the relative metric for the desired interface to be lower than any competing routes for destination 255.255.255.255. The easiest way to do this is to lower the metric for the desired interface, which can be done using the netsh command, For example: netsh interface ipv4 set interface "local area connection 2" metric=2 (The default metric for Ethernet interfaces in Windows Server 2008/Vista appears to be 10.) Once initialization is done the metric can be restored to its normal value (default is automatic), For example: netsh interface ipv4 set interface "local area connection 2" metric=automatic Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

Windows Navisphere Storage System Initialization Utility Storage System Initialization Wizard Help is not displayed if Firefox is the default browser 203063 Frequency of occurrence: Always under a specific set of circumstances Severity: Medium

Clicking the Help option from the Help Menu item, will not launch help.

Change the default browser to IE. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

39




All Navisphere Secure CLI Management server stops responding when adding 100 LUNs to the global reserved LUN pool (GRLP). 200850 Frequency of occurrence: Likely under a specific set of circumstances Severity: Medium

When 100 LUNs are added to the global reserved pool at the same time using the naviseccli reserved -lunpool -addlun command, the request times out and restarts management server. This results in errors like the following seen on the command line: Message : End of data stream Message : Error occurred because unknown network error

You should add no more than 10 LUNs to the GRLP per instance of the command. You can always issue the command multiple times if more LUNs need to be added to GRLP. Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All Navisphere Secure CLI The backendbus -resetspeed command will fail with a Failed: Enclosure SPE SP's cables are incorrect error. 201988 Frequency of occurrence: Sometimes under a specific set of circumstances Severity: Medium

In some cases, when an enclosure is added that is running at a different speed than the back-end bus it is cabled to, you may see a Failed: Enclosure SPE SP's cables are incorrect. error when trying to reset the speed on the bus the enclosure is cabled to.

Go to the setup page for the targeted SP, and click the Refresh Management Server with the latest Subsystem Configuration data. button at the bottom of the page. Once this is done the “miscabling” fault will clear and the backendbus -resetspeed command will work. Since both SPs reboot on a resetspeed operation, there should be no need to refresh the data on both SPs from the setup page, since the reboot will cause a complete refresh. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

40




All Navisphere Secure CLI Navisphere Agent took 30 minutes before starting to respond to any command after rebooting both SPs at the same time on a large config array. 202137 Frequency of occurrence: Sometimes under a specific set of circumstances Severity: Medium

The storage system will not be manageable through Navisphere for a period of time (up to 30 minutes) when this problem happens. There are two necessary conditions for this problem to happen: • A very large

configuration with lots of disks, LUNs and storage groups.

• CIMOM (Management server) initial peer poll failure.

The management server initial poll of the peer SP may fail if the management server on the peer SP has not started fully. After timing out on each other’s peer poll for a period of time (because of the large amount peer data to merge), the management server on both the SPs will eventually recover from this situation and come up normally.

None Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All Navisphere Secure CLI Navisphere reports an SPE resume fault but does not provide adequate information to identify the specific resume. 202234 Frequency of occurrence: Always Severity: Medium

The CLI getcrus command gives inconsistent resume fault displays for different types of devices: for some types of devices (like the I/O module, power) the resume fault is displayed, and for the others (like the management module, the CPU module) the resume fault is not displayed. But for all these cases, the resume fault status is displayed at the enclosure level.

The resume faulted status shown at the enclosure level will not help identify which of the devices the fault is actually associated with, but you can execute the getresume –all command to get individual resume faults. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

41




All Navisphere Secure CLI Navisphere CLI Navisphere Secure CLI/CLI getcrus and Navisphere SecureCLI faults commands report the SPE power supply as faulted after injecting an SMBus fault to one of the communication paths to the power supply. 203093 Frequency of occurrence: Whenever certain conditions are met Severity: Medium

Navisphere Secure CLI/CLI getcrus and Navisphere Secure CLI faults commands report the SPE power supply as faulted after SMBus fault occurs to one of the communication paths to the power supply.

Though showing the power supply as faulted could be misleading, the actual SMBus fault is also reported by both UI and CLI getcrus command. So, fixing the SMBus fault will automatically clear the power supply fault (assuming that the power supply does not have any other fault on its own). Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All Navisphere Secure CLI Two SnapView sessions with same name in uppercase and lowercase are created successfully but only one of them is listed in Navisphere UI/CLI. 203364 Frequency of occurrence: Only under the circumstances described above. Severity: Low

When two (or more) SnapView sessions are created with the same name, but with different cases, for example, “SnapSession1” and “SNAPSESSION1” -- both the sessions get created successfully, but the Navi sphere UI and CLI display only one of these sessions (there is no way to determine which will be displayed). An attempt to recreate the session that is not displayed fails (as expected) because the session actually exists.

Do not create sessions using the same name but with different cases. Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

42




All Navisphere Secure CLI Navisphere CLI Performance counter corruption results in invalid counters. 190134 Frequency of occurrence: Very infrequent Severity: Low

If the performance cunters on the SP are corrupted, this may result in invalid counters being displayed in Navisphere commands getcontrol and getall as seen below: Controller busy ticks: 4294967295 Controller idle ticks: 4294967295 ...

Use the setup page, targeting the SP that is experiencing the issue, and select Restart Management Server Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All Navisphere Secure CLI Sometimes duplicating a configuration with metaLUNs results in a Navisphere Secure CLI error. 203682 Frequency of occurrence: Intermittent Severity: Medium

After running a script that creates a configuration with metaLUNs, then captures it, destroys the configuration and duplicates it, you may see an unknown error when executing the naviseccli getdisk command.

Use the setup page, targeting the SP that is experiencing the issue, and select Refresh Management Server State. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

Windows 2008 and Vista

Navisphere Agent A custom response application window cannot be launched on Windows 2008 and Vista. 208811 Frequency of occurrence: Always under the circumstances mentioned above Severity: Low

On Windows 2008 and Vista, a custom response application window cannot be launched. If you set notepad.exe as the custom response, the notepad window will not pop up on the server. It should not be a problem in customer sites because the user usually does not use a popup application window as the customer response.

This issue is OS specific. A custom response application window can be launched on other Windows platforms, by checking Allow service to interact with desktop in the properties of Navisphere Agent service. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

43




Hyper-V Navisphere Agent Cannot use modem capability of Event Monitor on Hyper-V systems. 208920 Frequency of occurrence: Always under the circumstances mentioned above Severity: Low

Event Monitor cannot use modem capability to configure EMC Connect Home on Hyper-V systems. This is a restriction of Microsoft Hyper-V.

Configure EMC Connect Home on a Windows platform rather than onHyper-V systems. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All Navisphere Agent You are unable to apply the central monitor template on host agent with a manually edited Event Monitor configuration. 208815 Frequency of occurrence: Rarely under a rare set of circumstances. Severity: Low

Sometimes you are unable to apply central monitor template after you edit the Event Monitor configuration manually. This issue does not happen in customer sites normally, since the user is not supposed to edit the Event Monitor configuration manually.

Manually cleaning the Event Monitor configuration from NaviMon.cfg and restarting Navisphere Agent will return the host agent to normal. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All Navisphere Secure CLI The config capture command (arrayconfig –capture) does not capture battery information for all the batteries on the storage system. 206839 Frequency of occurrence: Always Severity: Medium

Config capture captures information for only one battery per enclosure, instead of capturing information about both the batteries present in an enclosure.

Use the Secure CLI or Navisphere Manager UI for viewing information about all batteries on the storage system. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

44




All

Navisphere Secure CLI Secure CLI command backendbus -analyze may incorrectly display the disk state as requested bypass, after replacing 4 GB disks with 2 GB disks on a 4 GB BE. 217534 Frequency of occurrence: Occasionally Severity: Medium

Secure CLI command backendbus -analyze may incorrectly display the disk state as requested bypass, after replacing 4 GB disks with 2 GB disks on a 4 GB BE.

The accurate disk state information can be retrieved by using the getall –disk command or by restarting the management server from the storage system’s setup page. Exists in versions: 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All

Navisphere Secure CLI Secure CLI command arrayconfig –duplicate does not duplicate SAN Copy sessions. However, it mistakenly duplicates reserved snapshots of ISC sessions. 218682Frequency of occurrence: Always Severity: Medium

Secure CLI command arrayconfig –duplicate does not duplicate SAN Copy sessions. However, it mistakenly duplicates reserved snapshots of ISC sessions.

No workaround Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

All

Navisphere Secure CLI The networkadmin -set management port speed command fails when setting auto negotiation to OFF. 222405 Frequency of occurrence: Always Severity: Low

The networkadmin -set management port speed command fails when setting auto negotiation to OFF. If the management ports are not set to virtual ports, the command will fail with this error: Modify operation for Management Port failed.

No workaround Exists in versions: 6.24.0.6.7 6.26.0.6.7 6.26.5.0.95 6.26.7.0.81 6.28.0.4.25 6.28.10.3.11 6.28.20.1.40 6.28.21.0.27

http://opseroom01.corp.emc.com/eRoom/SPOmidrangesysdiv/NavisphereStorageMgmtDev/0_13aa30

45

Technical notes


Technical notes

It is important to read these technical notes; they do not appear anywhere else in CLARiiON documentation.

Technical notes for all platforms

The information described in the following sections applies to all platforms that support the Navisphere Host Agent, CLI, Server Utility, and Storage System Initialization Utility software.

Host agent

On UNIX platforms the HostIDFile.txt file is not removed when you uninstall the Host Agent. This ID file is not removed because the host ID needs to be consistent for the life of the host. Otherwise, the host may have multiple host IDs associated within the storage system.

A server cannot be connected to an AX storage system while it is connected to a CX or CX3 storage system.

You can configure the Navisphere Host Agent to automatically detect the storage systems, with the exception of JBOD devices. To automatically detect JBOD devices, you must enter JBOD device names in the agent.config file.

It is important to note that EMC does not support the simultaneous use of device auto-detection and specific device entries in the agent.config file.

To shorten a lengthy discovery process at agent startup, avoid restarting the Host Agent while I/O is occurring on the storage system.

When using storage groups, you may be unable to log a host in to the storage system when:

• A multi-homed server has two IP addresses and possibly two hostnames.

• A host in a cluster has multiple IP addresses. In this case, there is an IP address for the cluster and an IP address for each host in the cluster.

• Server network settings, for example DNS settings, are not configured properly.

• A host is not known to DNS or any other name service. As a result, the host can be contacted only by using its IP address. To solve this problem, you need to create a text file called

46

Technical notes


agentID.txt. This text file tells the host agent the IP address to use when it communicates with the client. The first line of this text file is the fully qualified hostname. The second line is the IP address. If either of these lines is empty, the default value for that parameter is used. If you want to include comments, create an empty third line and start your comments on the fourth line. Following is an example of an agentID.txt file.

Hostname

128.221.41.34 optional comments are allowed here

To find the IP address of the host, perform a network name lookup on the client and look for the hostname. Then ping the host from the client machine to get the host’s IP address.

After creating agentID.txt, you need to figure out where to store its location:

1. If the environment variable EV_AGENTID_DIRECTORY is defined and is not zero length, this directory is used.

If this is a Windows system: See if the location of the agent configuration file is in the registry at: HKEY_LOCAL_MACHINE\SOFTWARE\EMC \Agent\1.0\ConfigPath

If the location is stored there, it is used. If it is not there, this directory is used: \

2. If this is a UNIX system, this directory is used: /

3. If this is a NetWare system, this directory is used: sys: \

NOTE: This is a change from Navisphere Host Agent 6.2 and earlier. The use of agentID.txt on UNIX platforms required that your current working directory be “/” when manually starting the agent. Failure to do this resulted in the wrong hostname/IP address being used.

Host agent file for CX series, CX3 series, CX4 series, AX series, and AX4-5 series storage systems

Do not create device entries for CX, CX3, CX4, AX, and AX4-5 series storage systems in the Host Agent configuration file.

47

Technical notes


With the exception of certain Options Supported directives, the parameters defined in the Host Agent configuration file do not affect CX, CX3, CX4, AX, or AX4-5 series storage systems.

Event Monitor log size increase

The Event Monitor log size default is greater in version 6.28 than in past versions (100 MB instead of 25 MB). This increase in log size will also take effect on CX4 series storage systems. As a result, in order to monitor a CX4 series storage system, EMC recommends upgrading the host agent that is performing the monitoring to version 6.28.

If version 6.28 software needs to be downgraded to a previous version for any reason, the following steps should be performed to avoid any issues with log file size: 1. Save the log. 2. Clear the log. 3. Set the maximum log size to 25 MB. 4. Perform the downgrade.

CLI

Error codes from the CLI are provided in the Table of Classic and Secure CLI error codes.

What you need to do to upgrade to Secure CLI Script changes required – Existing CLI scripts are compatible with

the new Secure CLI with the following exception: The commands must be invoked with naviseccli instead of navicli and java -jar navicli.jar.

Setting up valid credentials – For Secure CLI, valid credentials are required for each command. To avoid the need to specify the username and password in each command, you can create credentials using Secure CLI. Use the -AddUserSecurity command to store credentials locally on the server in an encrypted file. Note that the credentials are slightly different than those used with Java CLI, so you cannot use a security file created by Java CLI.

48

Technical notes


Differences in how output is displayed and processed Several improvements have been made in the Secure CLI regarding how output is displayed and processed.

Secure CLI displays information about both SPs -- Classic CLI displays information only about the targeted SP. For example:

• getsp — Classic CLI returns N/A for the serial number of the non-targeted SP; Secure CLI returns the actual serial number.

• getall — Classic CLI returns N/A for the serial number of the non-targeted SP; Secure CLI returns the actual serial number.

• chglun — Classic CLI returns the string SP A: Unit not bound on an unbound LUN; Secure CLI returns the string SP A: Unit not bound, SP B: Unit not bound on an unbound LUN.

Consolidation of warnings -- Certain Classic CLI commands prompt the user with multiple warnings and ask for multiple confimations. Secure CLI displays a single instance of all the pertinent warnings and prompts the user for a single confirmation. This is true of the following commands:

• alpa • firmware • networkadmin • port • storagegroup

For Classic and Java CLI support, the management software on the storage system you are managing must be at version 6.19 or later -- If you are using Secure CLI to manage a version of Navisphere that is earlier than 6.19, Classic CLI is not supported, and you can use only commands that Java CLI supports.

Compatibility mode -- MirrorView/Synchronous, SnapView, and SAN Copy commands are now executed by Secure CLI. A compatibility mode was created for older scripts that use the CLI MirrorView, SnapView and SAN Copy command sets. In compatibility mode, CLI MirrorView, SnapView and SAN Copy commands are routed through Secure CLI. This mode is automatically set if you are using:

• MirrorView with management server 6.7 or later • SnapView or SAN Copy with management version 6.24 or later

49

Technical notes


To use this feature, you have to configure security on your system and the storage systems. You need to create accounts on your storage systems using the UI or Navisphere Secure CLI. To create a local security file use this command:

Naviseccli –user <username of array accounts> –password<password of array accounts> -scope 0 (for global) | –scope 1 (for local) -addusersecurity.

NOTE: EMC recommends that you use Navisphere Secure CLI for all commands.

navicli -d command for CX series, CX3 series, and AX series storage systems – When addressing a CX, CX3, or AX SP Agent with the navicli command, you do not need to specify a device entry (-d <device name>).

Most CLI commands require a device entry (-d <device name>) on the command line to direct the management request to the appropriate storage-system device. Because the CX, CX3, and AX SP Agent manages only the storage-system device (SP) on which it is installed, the CLI does not require the -d entry on the command line for these storage systems.

It is better not to use the CLI to configure and manage remote mirrors – Since the CLI communicates with the CX, CX3, and AX series SP Agent through one SP at a time, using the CLI to configure and manage a remote mirror is inefficient. EMC recommends that you use Navisphere Manager for these tasks because it can monitor both SPs on the primary and secondary storage systems and can also provide a more complete picture of the remote mirror configuration and status.

Comments removed from the Host Agent configuration file – When you use Navisphere Manager or CLI to rename a storage system or change the Host Agent configuration file, the comments in the file are removed. When the requested changes to the configuration file take effect, comments that previously resided in the file are permanently lost.

50

Technical notes


XML output changed with Java-based CLI – The output for XML has changed since Navisphere version 6.2. The new output represents true data type. For example:

• A LUN number is returned as a signed integer. • A Boolean is returned as a Boolean • A -1 means undefined, instead of not available, or not

applicable.

Previously the same information was returned as strings. This only affects output for commands that use the XML switch.

Unsupported security encryption key error – When upgrading from the Navisphere version 6.2 Java-based CLI, you will encounter this error if you are using a local security file. Navisphere version 6.4 and later requires JRE 1.4.2, which does not support the older JRE’s encryption methodologies. To resolve this issue, remove security credentials by issuing -RemoveUserSecurity.

Caller Not Privileged error – If a Caller Not Privileged error is returned from a Java or Secure CLI command, it could mean that the command was issued with invalid security credentials (username, password, scope), or that the command was issued without the required level of authorization (correct role) to perform the operation.

Automated CLI commands may fail – Navisphere uses several internal databases to represent the state of the storage system, and updates their status through regular polls to the system software. For this reason, some automated CLI commands may fail if they are executed prior to Navisphere's internal system polls.

For example, immediately sending a request to allocate a newly bound LUN as a clone private LUN (CPL) may fail, since the clone database has not yet recognized that the LUN is fully bound. In such situations, short delays should be added to the script before sending the request.

Classic CLI and NDU – Starting with version 6.28, Classic CLI will no longer support the NDU command. If you attempt to use Classic CLI to perform any NDU functions, an error will be returned. Please use the Secure CLI or NST to perform NDU operations.

Classic CLI and “Invalid Enclosure” – When using version 6.28 Classic CLI to target a storage system running FLARE OE version 02.24.xxx.5.017, 03.24.xxx.5.017, 02.26.xxx.5.011, or 03.26.xxx.5.011, or earlier, the getcrus and getresume commands will show Invalid Enclosure, instead of Enclosure SPE for the SPE enclosure.

51

Technical notes


Note: If you use version 6.28 Classic CLI to target a CX4 series storage system, you will also see the same Invalid Enclosure string when running getcrus or getresume.

Server utility HAVT Tool

The HAVT tool is supported on these fibre-attach platforms:

• HP-UX (11.11, 11.23 IA 64, 11.23 PA RISC) • Solaris 8, 9, 10 • Microsoft Windows 2000, 2003, 2008 • AIX 5.2, 5.3 • Linux RedHat Enterprise Versions 3 , 4 and 5 • SuSE Enterprise Server Versions 8 , 9 and 10 • AsianUX Version 2. • IBM Power Linux Red Hat Enterprise Server RHEL5 and

Novell/SUSE Enterprise Server RHEL5.

It is also supported with any of these configurations:

• CLARiiON Series CX, AX, AX4-5, and CX3 series • Navisphere versions: Version 6.7 or later

The HAVT tool is supported on these iSCSI-attach platforms:

• Microsoft Windows 2003, 2008 • RedHat Enterprise (RHEL) 3 , 4, and 5 • SuSE Enterprise (SLES) 8, 9 and 10 • AsianUX (2.0) • VMware ESX 3.x • AIX 5.2 and 5.3 • HP-UX 11.11, 11. 23,and 11.31 • Solaris 10

It is also supported with any CX or AX storage system that supports iSCSI:

• QLogic 4010, 4060/4062 and 4050/4052 HBAs are supported on iSCSI Linux and Windows systems.

• QLogic 4050/4052 HBAs are supported for iSCSI VMware ESX 3.x systems.

Retrieving HAVT report files -- Files uploaded to the storage system may be retrieved using the Navisphere CLI and Secure CLI managefiles command.

52

Technical notes


HAVT report files can grow to over 1 MB -- One of the server utility screens states that the size is usually less than 100 KB. This is not accurate. Depending on the size of the configuration, the report file can grow to over 1 MB.

To gather QLogic iSCSI HBA information for HAVT reports -- QLogic iSCSI CLI must be installed.

If HAVT reports are not in the tabbed format, you must change a setting in your browser.

In some cases, the report may be displayed as a simple HTML page instead of in table format. To fix this, check your browser for an Active Content Blocked information bar or dialog box. Click the information bar or dialog box and select Enable Blocked Content.

If you do not see an Active Content Blocked information bar or dialog box, you need to make sure that JavaScript is enabled. (On most browsers, JavaScript is turned on by default.)

To enable JavaScript in IE:

1. Go to the Tools menu and select Internet Options. 2. In the Internet Options dialog box, select the Security tab (at the

top of the window). 3. Under the Security tab, select the Internet Web content zone. 4. Under Security Level for this zone:

If there is a slider bar, move the slider bar to Medium. Otherwise, if the security level is Custom:

a. Select the Custom Level … button at the bottom of the page to open the Security Settings window.

b. In the Security Settings window, scroll down until you get to the section called Scripting (near the bottom).

c. Under Scripting, select the option marked Enable in the Active scripting category.

d. Click the OK button.

To enable JavaScript in Firefox:

1. Go to the Tools menu and select Options. 2. In the dialog box that comes up, go the Content category of

options. 3. Click Enable JavaScript.

53

Technical notes


Table of Classic and Secure CLI error codes

Navisphere Classic CLI error codes

Error value

Description

0 No error.

1 Invalid command line parameters.

2 Too few parameters

3 Too many parameters.

4 Invalid bind type.

5 Invalid LUN number.

6 Invalid rebuild time.

7 Disk names for groups of RAID type 1/0 must have an even number of arguments.

8 Invalid number of disks in bind command.

9 Invalid disk name specified.

10 An enclosure containing one or more of the disks is not present.

11 Disk already bound or binding.

12 Disk is empty or missing.

13 Invalid stripe size.

14 Disk name not unique; all names in disk-name must be unique.

15 Invalid cache flags.

16 Invalid default owner.

17 Incorrect number of chglun parameters.

18 Unable to determine name of target host machine.

19 Enable/disable flag invalid.

20 Invalid usable cache size.

21 Invalid page size.

22 Invalid watermark value.

23 High watermark less than low watermark.

24 No device name listed on command line.

25 Invalid idle threshold.

26 Invalid idle delay.

27 Invalid write aside size.

28 Disks must be on separate buses for bind.

54

Technical notes


Error value

Description

29 The Agent was unable to configure any devices.

30 LUN does not exist.

31 LUN already exists.

32 Cannot get current working directory for firmware command.

33 Illegal position for hot spare.

34 Invalid read cache value.

35 Invalid read cache size.

36 Invalid write cache value.

37 Invalid write cache size.

38 Invalid RAID 3 cache size.

39 Cannot access device.

40 Switch not supported.

42 Unknown error

50 Agent - Memory allocation error.

51 Agent - Invalid device name.

52 Agent - Host connection not found.

53 Agent - SP not found.

54 Agent - Invalid SP suffix.

55 Agent - Invalid LUN number.

56 Agent - Invalid page size.

57 Agent - Invalid command line switch.

58 Agent - Error bind command.

59 Agent - Error chglun command.

60 Agent - Error unbind command.

61 Agent - Error firmware command.

62 Agent - Error trespass command.

63 Agent - Error rebootSP command.

64 Agent - Generic error.

65 Agent - Unknown error.

66 Error returned from Agent.

67 RAID 3 does not support write caching

68 RAID Group - Invalid RAID Group ID.

55

Technical notes


Error value

Description

69 RAID Group - Valid values for trespass option are a and b.

70 RAID Group - Valid values for priority option are ASAP, High, Medium, and Low.

71 RAID Group - Valid values for lex option are yes and no.

72 RAID Group - RAID Group not found.

73 RAID Group - RAID Group not supported on this system.

74 RAID Group - Valid values for rm option are yes and no.

75 RAID Group - Valid values for sq option are mb, gb, sc, and bc.

76 RAID Group - Valid values for pl option are bf, ff.

77 RAID Group - Valid values for sp option are a and b.

78 RAID Group - Specific Disk download not supported.

79 RAID Group - This RAID Group has LUNs in it. Unbind them and run removerg again.

80 Zerodisk command failed.

81 Zeroing not supported.

Storage group commands error codes

82 This version of the FLARE software does not support Access Logix (SAN or shared storage) systems.

83 The group name entered does not match any Storage Groups for this storage system.

84 The HBA UID specified is not known by the storage system.

85 The LUN number specified is not a bound LUN number.

86 Fairness not supported.

87 The retyped password does not match (case sensitivity not checked).

88 Server could not be found, or is not running an Agent.

89 Invalid switch combination.

90 The UID (unique id) you entered does not match any Storage Groups for this storage system.

91 This version of FLARE software does not support the warm reboot feature.

56

Technical notes


Error value

Description

92 Setpath cannot be used to map to the special default Storage Group.

93 Invalid number of disks in RAID Group.

94 This version of FLARE software does not support the Dual Simultaneous Access.

95 This name identifies more than one Storage Group. Please identify the Storage Group that you wish to perform this operation on by providing its unique identifier (uid).

96 Inaccessible command.

97 New storage-system serial number must be a 12-character or less alphanumeric value.

98 Cannot perform inquiry.

99 Cannot read block data.

100 Cannot write to file.

101 Cannot open pipe.

102 The host specified is not known by the storage system.

103 Network name size is too big.

104 Network admin not configured.

105 Not a privileged user.

106 Read only access.

107 Invalid contact information.

108 Invalid host description.

109 Invalid auto configuration.

110 Invalid privileged user list.

111 Invalid interval.

112 Invalid baud rate.

113 Invalid log size.

114 Invalid managed device.

115 Storage-system option not available.

116 Invalid megapoll value.

117 This version of Agent does not support Remote Agent Configuration.

118 Invalid use of explicit device names value.

119 The valid value of baud rate is 9600 or 19200.

120 This option is not supported.

57

Technical notes


Error value

Description

121 Error while parsing file.

122 All of the specified users are already in the privileged user list.

SnapView, MirrorView, and other CX series or FC4700 series-only command error codes

123 Snapshot does not exist.

124 This version of FLARE software does not support SnapView.

125 Invalid SP name.

126 Reserved LUN pool does not exist.

127 Package number invalid.

128 This version of FLARE software does not support non-disruptive software installation (NDU).

129 Cannot open this file.

130 File does not exist.

131 RAID type must be r1 (RAID 1), r3 (RAID 3), r5 (RAID 5), or r1_0 (RAID1/0).

132 Multiple subcommands specified. Check syntax.

133 Disk for PSM must be on DPE bus 0.

134 Configuration does not exist.

135 Configuration already exists.

136 Size specified is too small.

137 Configuration does not exist. Run the navicli initializearray command to configure the system.

138 First option must be a subcommand.

139 Cannot create RAID Group for PSM (Persistent Storage Manager).

140 Name or UID (unique ID) is required.

141 Invalid name specified.

142 Image UID is required.

143 Name and LUN are required.

144 Storage-system UID (unique ID) and LUN UID are required.

145 Mirror not found.

146 Image not found.

147 Synchronized rate cannot be changed since input image is primary.

58

Technical notes


Error value

Description

148 Name and UID both specified.

149 Invalid reserved LUN pool.

150 Invalid session.

151 Session does not exist.

152 Session is stopping.

153 Invalid snapshot.

154 Snapshot does not exist.

155 The -o option requires “-all” or “-filename.”

156 Path to store files is required.

157 Cannot specify both “-all” and “-filename.”

158 Enter file index or “quit.”

159 Invalid input.

160 Index is out of range.

161 File not found.

162 Space not available to retrieve file.

163 Specified feature not supported.

164 Feature must be specified.

165 Cannot specify both '-lun' and '-lunuid'

166 Invalid Storage Processor name.

167 PSM (Persistent Storage Manager) is not broken.

168 PSM (Persistent Storage Manager) is broken. Cannot list or create PSM.

169 LUN cannot be unbound.

170 Operation not supported on this type of storage system.

171 Incompatible arguments. Invalid storage-system serial number.

172 Directory not specified.

173 Invalid number of blocks.

174 Number of blocks not specified.

175 Reading of data not supported on this storage system.

176 Invalid snapshot World Wide Name (WWN).

177 Invalid storage-system serial number.

178 Navicli '-f' option required to store data in file.

179 Invalid IP address format.

59

Technical notes


Error value

Description

180 Storage Group cannot be shared.

181 Invalid HLU number.

182 Invalid ALU number.

183 Invalid port ID.

184 Remote server cannot be managed.

185 Email response test failed.

186 Emailpage response test failed.

187 Modempage response test failed.

188 SNMP response test failed.

189 Phone home response test failed.

190 Mandatory switch for email/emailpage.

191 Mandatory switch for modempage.

192 Mandatory switch for SNMP.

193 Only one message or file can be specified.

194 Valid dial string contains only digits, parentheses, hyphen.

195 File does not exist or cannot open.

196 Specified user already exists.

197 The offset switch is not supported for this storage system.

198 Valid COM port number is 1, 2, 3, or 4.

199 Valid dial command is atd, atDp or atD.

200 Valid message delay contains only ",,," (one or more commas).

202 Target LUN number is missing.

203 Session name is missing.

204 SnapView multiple session feature is not supported.

205 Cannot specify both snapshot name and snapshot ID.

206 Cannot specify both -mode and -simulation.

207 This command is not supported on remote host.

208 Switch -pathname must be specified.

209 Get local server attributes failed.

210 This version of FLARE software does not support Hi5 RAID type.

211 Only one of the switches -snapshotid, -snapshotname, or -lun can be specified.

60

Technical notes


Error value

Description

212 Specified session and snapshot must be based on the same target LUN.

213 Specified session and snapshot must be based on the same target LUN.

214 Cannot add LUN to reserved LUN pool; the maximum number of reserved LUNs that can be added is n.

215 The HLU (host LUN) number you specified cannot be found.

216 This command must be issued from the SP to which the LUN will trespass.

217 Invalid bus or enclosure number.

218 Invalid WWN seed.

219 Invalid EMC part number.

220 This RAID Group has maximum number of LUNs already.

221 Not enough reserved LUNs in the specified SP's reserved LUN pool.

222 This LUN cannot be added to the Storage Group since it is participating in a remote mirror.

223 Allocate log must specify LUN with valid owner.

224 This request has been issued through the SP that is not the current owner of the targeted LUN.

226 Invalid NDB password.

227 Insert test event failed.

228 The -addroffset switch is supported only for a non-destructive bind.

229 The -addroffset switch must be supplied for a non-destructive bind.

230 Cannot unbind LUN, PSM LUN that is not double faulted.

231 Cannot unbind LUN because it is in use as an active hot spare.

232 Cannot unbind LUN because a feature of the storage system is using it.

233 Cannot unbind LUN because it is contained within Storage Group.

234 Incorrect LUN in storage group

235 Cannot display LUN WWNs and update LUN map information at the same time.

61

Technical notes


Error value

Description

236 The DMF is not supported

237 Incorrect parameters while creating DMF

238 Incorrect Name and UID specified for the DMF

239 It is required to enter Name or UID for the DMF

240 The specified DMF is removed, the destination does not exist.

241 Incorrect destination LUN WWN and number specified

242 DMF name is not unique

243 Unknown Descriptor for DMF

244 Incorrect List and Set specified for DMF

245 Throttle switch for DMF is missing

246 Throttle switch for DMF is invalid

247 Invalid Max value for DMF

248 Invalid poll value for DMF

249 Incorrect source LUN, WWN and Number specified.

250 The destination for DMF is less than the source

251 The peer SP is alive

252 The DMF specified is neither Source nor destination

253 The specified descriptor name for DMF is duplicate

254 Duplicate. LUN ID for DMF

255 The destination DMF exists.

256 DMF copy length is zero.

257 Source specified for DMF is a private LUN

258 Destination specified for DMF is a private LUN

259 DMF Modify destination is smaller than source

260 DMF source specified is not on peer

261 DMF destination specified is not on peer

262 SNAP Rollback is not supported

263 Flush rate is missing for SNAP

264 Flush rate for SNAP is invalid

265 SNAP session is not rolling back

266 SNAP session is not persistent

267 SNAP session is rolling back

268 Snap session source is rolling back

62

Technical notes


Error value

Description

269 Snap session has max

270 SNAP has invalid session name

271 Simulation is not supported

272 SNAP chunk size is not changeable

273 Session is rolling back, can not stop

274 Session is rolling back can not activate

275 Session is rolling back can not deactivate

276 Mirrors with same name

277 Error: -phonehome response test is not supported on the targeted Agent. Please use -ipconnecthome or -mdmconnecthome instead.

278 Response using modem from Agent on SP is not supported.

279 Error: -ipconnecthome response test failed

280 Error: -ipconnecthome is not supported.

281 Error: -mdmconnecthome response test failed.

282 Error: -mdmconnecthome is not supported.

283 Error: -connectto and -routerip are mandatory.

284 Error: -modemnum, -connectto, and -method are mandatory.

285 Error: -smtpmailserver, -destaddress, and -serialnumber are mandatory

286 Error: -emailhome response test failed.

287 Error: invalid modem method. Valid method should be one of \"Direct Dial\", \"UUNET WAN\", \"UUNET SYM\", \"UUNET EQN\", \"UUNET JTO\", \"UUNET EQT\", \"UUNET GEN\",\"UUNET GRC\" and case sensitive.

288 Cannot add a hot spare to Storage Group.

289 Chglun parameter not supported on a non-Flare LUN.

290 Unable to bind the metaLUN, use CLE command metalun –destroy instead.

291 This version of FLARE software does not support getsniffer or setsniffer on metaLUNs.

292 You must issue this command from the SP that owns the LUN on which verify will be run.

293 Cannot specify both -feature and -featurename.

63

Technical notes


Error value

Description

326 Invalid switch specified for a reserved snap session.

327 Invalid switch specified for a reserved snap LUN.

328 Cannot activate reserved snapshot LUN.

329 Cannot deactivate reserved snapshot LUN.

330 Cannot stop a reserved session.

331 Cannot remove a reserved snapshot LUN.

332 Cannot modify a reserved snapshot LUN.

333 Cannot start rollback on a reserved session.

334 Cannot change rollback session as it is reserved.

335 The format of decimal number specified is inappropriate.

336 Precision of the decimal number specified exceeds the maximum precision of n (where n varies depending upon the situation).

338 Cannot add a snapshot to Storage Group because the snapshot specified is reserved.

344 Use the -nolocal switch if Agent version is not at least version 6.5 when setting SPS time.

345 Do not use the -nolocal switch if Agent version is version 6.5 or greater when setting SPS time. This storage system does not support any NVRAM card.

346 This storage system does not support any NVRAM card.

347 This storage system does not support any operation on shutting down the Array

348 This storage system does not support any operation on LUN cache dirty condition.

349 Error parsing .lst file.

350 Cannot open .lst file.

351 Syntax error in .lst file.

352 Snap consistent start not supported

353 The LUN list contains duplicate LUN number.

354 DMF Invalid Autorestart value

355 Snap migration lun for snap session

356 Snap migration lun for snapshot

357 Can not port switches together

358 Snap no hotspare in addluntocache

64

Technical notes


Error value

Description

359 Snapshot name too long

360 Managedby not supported

361 Cachecard not supported

362 Invalid SQ flags on AX

363 DMF destination does not exist

364 Invalid disk HA

365 Invalid disks NONHA

366 Can not access host

367 DMF lite src not local

368 DMF invalid port wwn

369 DMF modify src multi switches

370 Port removed HBA logged in.

371 Luncache no cache dirty

372 SG not connected to host

373 Can not unbind why double db fault

374 Luncache not default owner

375 Snap only persistent sessions

376 DMF DESTPORTWWN DESTWWN and DESTLUN specified

377 Need add audit

378 No luns in RG

379 RG does not exist

380 SIW rules failed

381 No luns owned by target in RG

382 No luns owned by target

383 Remove RG duplicate Raid group number

384 No sniff hot spare

385 SIW jre not found

386 SIW rules security

387 Raid reboot peer SP command

388 Unknown SIW error

389 Illegal error

390 SIW rules login failed

391 Resume not supported

65

Technical notes


Error value

Description

392 RAID reset and hold command

393 Invalid parity elements hold value

394 Invalid disk FW

395 Snapcopy globalcache not committed

396 Snapcopy globalcache not supported

397 Non redundant RAID group

398 Disk not found

399 Reserved snap can not add lun private

400 Reserved snap maximum allowed is exceeded

401 Invalid RG type flags

402 Raid type supported

403 Raid type not supported

404 Raid type and disk unmatched

405 Numbers disk even

406 Invalid Rg type flags 2

407 DMF name and descriptorID specified

408 Snap remove active snapshot

409 Snap active snapshot

410 The destination LUN does not exist

411 The connection type specified is same as current.

412 Invalid storage group name

413 Invalid connection

414 Remote subsystem can not be retrieved

415 Duplicate switches

416 Maximum of 240 characters allowed.

417 Values not numeric

418 Inserting event failed

419 Invalid speed request

420 Invalid speed duplex

421 Must be an IPv6 address in colon hexadecimal format

422 No SP ports

423 Duplicate disks

424 SecureCLI executable not found

66

Technical notes


Error codes returned by Secure CLI – The following table contains all error codes that are returned by Secure CLI:

Navisphere Secure CLI error codes

Error value (hexadecimanl)

Description

General feature command errors

0x0000 CLI success

0x0001 Invalid arguments

0x4D00 Management Server is not available.

0x4D01 Error encountered during command execution

0x4D02 Invalid command entered.

0x4D03 Command is running. Client should poll for status.

0x4D04 CLI multiple override needed

0x4D05 Invalid speed supplied by user

0x4D06 Speed not supported on this port

0x4D10 CIM API Instance is NULL

0x4D41 CLI provider error override

0x4DD0 Invalid command.

Security error codes

0x4000 Security already initialized.

0x4001 User not logged in.

0x4040 User denied access.

0x4041 Invalid password.

0x4042 No roles defined.

0x4043 User already exists.

0x4044 Invalid role value.

0x4045 Invalid list type.

0x4046 File update failed.

0x4047 Only global admin.

0x4048 Invalid scope value.

0x4049 Username invalid.

0x404a Username does not exist.

0x404b Update local data failed.

0x404c Credentials do not match.

0x404d User deletion failed.

0x404e Initialization failed.

67

Technical notes



Description

0x404f Error writing to PSM.

0x4050 Authentication object not initialized.

0x4051 Administration object not initialized.

0x4052 Change user failed.

0x4053 Peer not responding.

0x4054 Change service password failed.

0x5370 Security invalid command.

0x5371 Security feature not available.

0x5372 Execute error.

Domain error codes

0x4300 Event directory created.

0x4301 Event domain destroyed.

0x4302 Event directory destroyed.

0x4303 Event nodes added.

0x4304 Event nodes removed.

0x4305 Event version mismatch.

0x4306 Event local system info changed.

0x4307 Event New domain created.

0x4308 Event local master.

0x4309 Event Local node demoted.

0x430a Event New master defined.

0x430b Event node part of diff domain.

0x430c Event client data destroyed.

0x4340 Event no database in PSM.

0x4341 Event no backup database.

0x4342 Event inconsistent DIR DB.

0x4343 Event internal provider error.

0x4344 Event directory creation failed.

0x53A0 Directory invalid command

0x53A1 Directory feature not available

0x53A2 Directory execute errors

Legacy support error codes

0x4400 Gateway system not found.

0x4401 System not found in directory.

0x4402 Invalid agent configuration.

68

Technical notes



Description

0x4403 Unable to save configuration.

0x4404 Cookie not found.

0x4405 Unsupported on NAVI LITE.

0x4480 Warning no update needed.

0x44fc Error net exception.

0x44fd Error with provider modify exception.

0x44fe Error with provider read exception.

0x44ff Unknown exception.

Analyzer error codes

0x4800 Null object key.

0x4801 Null attribute.

0x4802 Null digest.

0x4803 Null persistent content.

0x4804 Error with reading of persistent file.

0x4805 Error with updating persistent file.

0x4806 Archive not created.

0x4807 Error with deleting archive.

0x4808 Error with getting properties.

0x4809 Error with setting properties.

0x480a Error with getting samples.

0x480ab Error with getting latest samples.

0x480c Error with ZIP.

0x480d File not found.

0x480e Archive creator busy.

0x480f Function not supported.

0x4810 Saving properties.

0x4811 Staring of log.

0x4812 Stopping of the log.

0x4813 Setting auto stop properties running.

0x4814 Data logging not running.

0x4815 Start logging running.

0x4816 Stop logging not running.

0x4817 Peer unavailable.

0x4818 Archive unavailable.

69

Technical notes



Description

0x4819 Error with returning the existing archive.

0x481a Error with logging skip sample.

0x481b Error with deleting old archive.

0x481c Error with data logging disallow running.

0x48fe Persistent exception.


0x4DC0 Invalid Analyzer command

0x4DC1 Analyzer Provider not found

0x4DC2 CLI Analyzer execute error

SnapView clone error codes

0x4b40 Trans object creation failed.

0x4b41 Trans object loss exception.

0x4b42 Transaction exception.

0x4b43 Unable to get specified instance.

0x4b44 No Lun numbers available.

0x4b45 Generic exception.

0x4b46 Cloneview name already used.

0x4b47 Protected restore not enabled.

0x4b48 Can not disable fast restore on cloneviews.

0x4b49 Source or cloneLUs exceeded max limit.

0x4b4a Can not change LU to private.

0x4b4b Can not add clone driver to LU ext attributes.

0x4b4c Can not remove clone driver from LU ext attributes.

0x4b4d LU not available.

0x4b4f CPL metalun not supported.

0x4b40 SP not primary or controlling.

0x4b41 Source LU is rolling back.

0x4D40 Invalid snap clone command

0x4D41 over ride needed

0x4D42 Unexpected clone error occurred

0x4D43 Clone feature object is not available

0x4D44 Clone enabling software is not installed

0x4D45 Specified CloneGroup is not available.

0x4D46 Specified Clone is not available.

0x4D47 No available LUs for cloning on the system.

70

Technical notes



Description

0x4D48 Specified LU is not available for cloning.

0x4D49 The Clone Private LUNs have not been allocated.

0x4D50 The protected restore is not supported

0x4D51 The optional fast recovery is not supported.

0x4D52 Can not add clone, the Max number of clones are already present on CloneGroup

0x4D53 Can not add clone, since a clone in the clone group is syncing or reverse syncing

0x4D54 Unable to sync or reverse sync clone before it be fractured.

0x4D55 Unable to reverse sync clone because it is Out-Of-Sync

0x4D56 Unable to reverse sync clone because a clone in its CloneGroup is either Synchronizing or Reverse Synchronizing.

0x4D57 Unable to sync clone because a clone in its Clone Group is either Reverse Synchronizing or Reverse Out-Of-Sync.

0x4D58 Unable to deallocate CPL while there is still clone group

0x4D59 Can not perform create, addclone or allocateCPL on a LU while it is migrating

0x4D60 MetaLUN(s) cannot be used as clone private LUN(s)

0x4D61 The luns being specified do not match the source luns. They have to be same capacity as the source luns.

0x4D62 Can not perform setfeature on a LU while it is private

0x4e40 NAVIALU MR name already exists.

0x4e41 NAVIALU MR LU is dirty.

0x4e42 NAVIALU generic exception.

0x4e43 NAVIALU transaction exception.

0x4e44 NAVIALU MR Lu is private.

0x4e45 NAVIALU MR consumed by aggregate.

0x4e46 NAVIALU MR other drivers found

0x4e47 NAVIALU MR LU in expanding state.

0x4e48 NAVIALU MR LU is shutdown state.

0x4e49 NAVIALU MR ALU is max.

0x4e4a NAVIALU MR ALU is comp max.

0x4e4b NAVIALU MR comp in ALU max.

NQM error codes

0x4D90 NPO feature object is not available

71

Technical notes



Description

0x4D91 NPO driver is not installed

0x4D92 Unknown exception on CIMAPI calls

0x4D93 Specified CIM class object does not exist or can not be found

0x4D94 NULL return from CIM calls. NPO Object does not exist or method is not supported

0x4D95 Max class number NPO supports is reached

0x4D96 Invalid NPO subcommand

0x4D97 Invalid NPO command line switches

0x4D98 Invalid NPO command line switches value.

0x4D99 LUNs have to be specified by WWNs or LUN numbers

0x4D9A Too few parameters

0x4D9B Too many parameters

0x4D9C Wait for creating archive.

0x4D9D Need to stop NQM first before perform the operation

0x5100 NPO idle state.

0x5101 Remove goal in fallback policy.

0x5102 Delete fallback policy.

0x5103 Class contained.

0x5104 Policy contained.

0x5105 Background class can not be removed.

0x5106 Code maxclasses reached.

0x5107 Code maxpolicies reached.

0x5108 Code maxschedules reached.

0x5109 Event not exists.

0x5114 Target already contained.

0x5115 Target not contained.

0x5116 Removegoal in schedule policy.

0x511e NPO running state.

0x511f NPO measuring state.

0x5120 NPO one policy allowed.

0x5121 Set classes to driver.

0x5122 Class has no goal.

0x5123 Class already contained.

0x5124 Class not contained.

72

Technical notes



Description

0x5125 Modify fallback policy.

0x5133 Policy not contained.

0x5135 Event already contained.

0x513e No active policy.

0x513f Error ZIP.

0x5140 File not found.

0x5141 Archive creator busy.

0x5142 Delete archive.

0x5143 Archive not created.

0x5149 Null digest.

0x514a Null persistent content.

0x514b Read persistent file.

0x514c Update persistent file.

0x5154 Class does not exist.

0x5155 Policy is active.

0x5156 Code maxclassinapolicy reached.

0x515f Class running.

0x5160 Code maxluninaclass reached.

0x5161 Code maxsgiinaclass reached.

0x5162 Invalid WWN.

0x5163 Class measuring.

0x5164 Public lun does not exist.

0x5165 SG does not exist.

0x516a Class invalid goal type.

0x5170 Policy does not exist.

0x5171 Schedule running.

0x5172 Schedule conflict.

0x517b SP degraded.

0x517c Class IO overlap.

0x517d Redundant string.

0x5185 Policy incomplete.

0x5186 Policy broken.

0x518f Null string.

0x5190 String limit.

73

Technical notes



Description

0x51e0 Fail converge.

0x51e1 Goal attained.

0x51e2 Converge then fall.

0x51e3 Disable fallback.

0x51e4 Suspend event.

0x51e5 Fallback LUN unbound.

0x51fe Invalid input.


MirrorView error codes

0x4DA0 Invalid Sync Mirror command

0x4DA1 Invalid Async Mirror command

0x4DA2 Sync Mirror feature object is not available

0x4DA3 Async feature object is not available

0x4DA4 Sync enabling software is not installed

0x4DA5 Async enabling software is not installed

0x4DA6 Unexpected Sync Mirror error occur

0x4DA7 Unexpected Async error occur

0x4DA8 No available LUs for mirroring on the system.

0x4DA9 Specified LU is not available for cloning.

0x4DAA Specified mirror source is not available.

0x4DAB Mirrorview requires same lun size on mirrored images

0x4DAC LUN is in a storage group.

0x4DAD Multiple error occurs.

0x4DAE intentlog allocate error

0x4DAF intentlog deallocate error

0x4DB0 disablepath error

0x4DB1 layered driver can't be added to LU stack

0x4DB2 Adding a layered driver to LU stack failed

0x4DB3 Removing a layered driver to LU stack failed

0x4DB4 Mirror can't be activated

0x4DB5 The mirror can't be deactivated (not active)

0x4DB6 Error on fracture image

0x4DB7 Error on sync image

0x4DB8 Error on promote image

0x4DB9 Requested image wasn't found/didn't exist

74

Technical notes



Description

0x4DBA Error on remove image

0x4DBB Error on specified LU is used by other feature and can not be chosen as mirror LU

0x4DBC Can not perform create, add secondary image or allocate WIL on a LU while it is migrating

0x4DBD Can not perform setfeature on a LU while it is private

0x4DBE Image not valid

MirrorView/A error codes

0x4f40 Generic Exception.

0x4f41 Mirror length name exceeds max.

0x4f42 Mirror name already used.

0x4f43 Mirror invalid number of LUs.

0x4f44 Mirror group name length exceeds maximum.

0x4f45 Mirror group name already used.

0x4f46 Can not add driver.

0x4f47 Can not remove driver.

0x4f48 SP not primary or controlling.

0x4f49 Mirror group name invalid characters.

0x4f4a LU participating in mirror.

0x4f4b Mirror Poll failed

MirrorView/S error codes

0x5040 Generic exception.

0x5041 Mirror poll failed.

0x5042 Mirror name length exceeds max.

0x5043 Mirror name already used.

0x5044 Mirror invalid number of LUs.

0x5045 Mirror group name length exceeds maximum.

0x5046 Mirror group name already used.

0x5047 Mirror luns not ready.

0x5048 Mirror secondary already exists.

0x5049 Mirror secondary same as primary.

0x504a Mirror primary is rolling back.

0x504b Mirror group name invalid.

0x504c Mirror group description invalid.

0x504d WIL metalun not supported.

75

Technical notes



Description

MirrorView consistency group error codes

0x5340 The maximum number of groups is already defined.

0x5341 Unable to locate the specified group

0x5342 The following group cannot be destroyed because it still has mirror members:

0x5343 Unable to locate the specified mirror

0x5344 This mirror cannot be added to the group because it does not have exactly 1 secondary image.

0x5345 Either the -remoteuid or -remoteaddress switch must be used because this mirror has more than 1 secondary image.

0x5346 The remoteuid cannot be the same the array on which the group resides.

0x5347 The mirror has no images on the specified remote array.

0x5348 The mirror is already a member of a group, so it cannot be added to this one.

0x5349 The remote image specified does not reside on the same array as the rest of the group's members.

0x535A Specified mirror is not a member of the group.

0x535B The specified missing mirror is not a member of the group.

0x535C Group name is already used.

iSCSI (connection) error codes

0x5200 Redirector error not local.

0x5201 Feature is not enabled.

0x5202 Duplicate user account full.

0x5203 Portid is invalid.

0x5204 Port contains a portal.

0x5205 Portal IP is not unique.

0x5206 Portal gateway unreachable.

0x5207 Invalid groupname non unique.

0x5208 Local user exists.

0x5209 Invalid account non unique.

0x520a Ping start error.

0x520b Invalid command Id.

0x520c Destroy portal group non empty.

0x520d No ports found.

0x520e Invalid SP ID.

76

Technical notes



Description

0x520f Feature not located.

0x5210 Get parameter by name failure.

0x5211 Invalid hexpassword length.

0x5212 Invalid hex password char.

0x5213 Route feature is not enabled.

0x5214 Route add failure.

0x5215 Duplicate route entry.

0x5216 Required network value dest.

0x5217 Required network value mask.

0x5218 Required network value GW.

0x5219 Required network value INTF.

0x521a Required meric value.

0x521b Route non persistent.

0x521c Gateway unreachable.

0x521d Invalid mask.

0x521e Invalid source address.

0x521f Invalid gateway address.

0x5220 Invalid dest address.

0x5221 Invalid dest mask values.

0x5222 Invalid dest mask combo.

0x5223 Invalid interface address.

0x5224 No interface found.

0x5225 No interface for GW found.

0x5226 No gateway found.

0x5227 No sourcemask found.

0x5228 ISNS feature is not enabled.

0x5229 WSA internal error.

0x522a Connect timeout.

0x522b Connect refused.

0x522c Connect unreachable.

0x522d Connect failed.

0x522e Internal COM error.

0x522f Add server Dup failure.

0x5230 Get server list PSM failure.

77

Technical notes



Description

0x5231 Add Server PSM failure.

0x5232 Delete Server failure.

0x5233 Delete Server PSM failure.

0x5234 Set primary server failure.

0x5235 Set primary server PSM failure.

0x5236 Get on tag physical port failed.

0x5237 Required network value IPAddress.

0x5238 ISNS no context entry found.

0x5239 Unknown ping error.

0x523a Ping timeout.

0x523b TR needs fragmentation.

0x523c Invalid MTU arguments.

0x523d Invalid traceroute arguments.

0x523e Invalid MTU NIC.

0x523f Invalid Zone_auth usage

0x5240 iSCSI_password violation

0x5241 iSCSI account violation

0x5242 Duplicate user account

0x5243 Initiator is not enabled

0x5244 Invalid ZGA auth usage

0x5245 Zonepath not valid for zone

0x5246 No port keys found

0x5247 No FE ports found

0x5248 IP Address incompatible protocol

0x5249 Required network value IPAddress (IPv6 or IPv4)

0x524a IP address not supported for operation

0x524b Invalid destination IP

0x52fe Netsh internal error

0x52ff Helper request internal error.

0x5320 Invalid connection command

0x5321 Connection feature object is not available

0x5322 Connection enabling software is not installed

0x5323 Unexpected connection error occurred

ISNS error codes

0x53D0 Invalid Isns command.

78

Technical notes



Description

0x53D1 Isns feature object is not available.

0x53D2 Isns enabling software is not installed.

0x53D3 Isns unexpected errors occurred.

LUN migration error codes

0x5300 Lun migration invalid command

0x5301 Lun migration feature not available

0x5302 Lun migration feature not supported

0x5303 Lun migration execute error

0x5304 Lun migration spec migration not available

0x5305 Lun migration spec source not available

0x5306 Lun migration base can not be hot spare

0x5307 Lun migration spec dest not available

Arrayconfig error codes

0x5420 CLI utility capture feature not available.

0x5421 CLI-capture execute error.

0x5422 Duplicate feature not available.

0x5423 Duplicate execute error.

0x5424 Invalid command.

0x6100 Generic exception.

0x6101 Duplication in progress.

0x6102 Duplication in progress in Peer.

0x6103 Duplication not in progress.

0x6104 Error accessing status.

0x6105 Capture in progress in Peer.

0x6106 Capture peer form exception.

0x6508 Fix unavailable.

0x6509 Rule exception.

0x650a Access level violation.

0x650b Dependencies not met.

0x650c Rule run exception.

0x650d Enumerate instances not supported.

0x650e Task still running.

0x650f Task limits reached.

0x6510 Inconsistent packages.

79

Technical notes



Description

0x6511 Single task limit.

0x6512 Redirect

Event Monitor (emconfig) error codes

0x5700 EMCONFIG code get usage.

0x5701 EMCONFIG code invalid argument.

0x5702 EMCONFIG code too few parameters.

0x5703 EMCONFIG code too many parameters.

0x5704 EMCONFIG code bad first option.

0x5705 EMCONFIG code unknown option.

0x5706 EMCONFIG code can load file.

0x5707 EMCONFIG code inaccessible cmd.

0x5708 EMCONFIG code not supported.

0x5709 EMCONFIG code command not valid.

0x570A EMCONFIG code EMSA not found.

0x570B EMCONFIG code EMSA save config failed.

0x570C EMCONFIG code invalid template name.

0x570D EMCONFIG code classic subcmd parse success.

0x570E EMCONFIG code classic subcmd parse Failure.

SnapView error codes

0x6200 Generic Exception.

0x6201 Poll failed.

0x6202 Session name too long.

0x6203 LU is rolling back.

0x6204 Invalid LU for session.

0x6205 Snapshot name too long.

0x6206 Snapshot name exists.

0x6207 Maximum SLUs for TLU.

0x6208 No LUN found.

0x6209 Lu is private.

0x620A Can not add driver.

0x620B Illegal owner.

0x620C Rollback not in progress.

0x620D Rollback in progress.

0x620E Rollback not supported.

0x620F Can not rollback clone mirror prevented.

80

Technical notes



Description

0x6210 No TLU for SLU.

0x6211 Session not found.

0x6212 Session transitioning.

0x6213 Region not found.

0x6214 Sessions exceeded for SLU.

0x6215 Sessions active.

0x6216 San copy remove error.

0x6217 LU in user VA.

0x6218 SLU active.

0x6219 No cache LUs to add.

0x621A No cache LUs to remove.

0x621B Maximum cache luns exceeded.

0x621C Invalid LU to remove from cache.

0x621D LU already in cache.

0x621E Invalid LU to add to cache.

0x621F Can not rollback active san copy.

0x6220 San copy active.

LDAP error codes

0x6300 Maximum number of server exists.

0x6301 Server IP exists.

0x6302 Error occurred saving server config.

0x6303 Destroy server with role mapping.

0x6304 CSO error.

0x6305 Invalid role mapping name.

0x6306 Can not update role mapping.

0x6307 Invalid role mapping type.

0x6308 Invalid role mapping request.

0x6309 Internal provider error.

0x630A Maximum number of group mapping exists.

0x630B Maximum number of User mapping exists.

0x630C Exceeded maximum number of group mapping.

0x630D Exceeded maximum number of user mapping.

0x630E Role mapping does not exist.

0x630F Role mapping already exists.

81

Technical notes



Description

0x6310 Invalid protocol type.

0x6311 Invalid server type.

0x6312 Invalid IP address.

0x6313 Invalid role.

0x6314 Zipping configuration files.

0x6315 Propagating configuration files.

0x6316 Unzipping configuration files.

0x6317 Retrieving configuration files.

0x6318 Empty configuration files.

0x6319 Copying configuration files.

0x6312 Invalid IP address.

0x631A Deleting configuration files.

0x631B Configuration file does not exist.

0x631C Failed to save file to local.

0x631D LDAP feature not initialized.

0x631E Can not contact authentication server.

0x631F LDAP set options failed.

0x6320 LBER set options failed.

0x6321 LDAP initialized failed.

0x6322 LDAP invalid protocol.

0x6323 LDAP missing server certificate.

0x6324 LDAP missing APP bind DN PW.

0x6325 LDAP simple bind failed.

0x6326 LDAP search failed.

0x6327 LDAP non unique user id.

0x6328 LDAP no user searchpath.

0x6329 LDAP bind password decryption failed.

0x632A LDAP user does not exist.

0x632B Invalid server config.

0x632C LDAP timeout.

0x632D LDAP invalid credentials.

0x632E LDAP server down.

0x632F LDAP authentication error

MetaLUN error codes

0x4D80 Invalid MetaLUN command.

82

Technical notes



Description

0x4D81 MetaLUN feature object is not available

0x4D82 MetaLUN feature is not enabled

0x4D83 Unexpected error occurred during MetaLUN command execution

0x4D84 Specified MetaLUN is not available

0x4D85 Specified base LU is not available.

0x4D86 Specified LU is not available.

0x4D87 Destroy multiple ALUs failed.

0x4D88 Destroy multiple ALUs was only partially successful.

Portal Errors

0x5440 Portal invalid command

0x5441 Portal feature not available

0x5442 Portal execute errors

BAD Block reporting (BRT) Error Plugin Errors

0x5600 BRT code not accessible.

0x5601 Invalid not enough parameters

0x5602 BRT code invalid command.

0x5603 BRT code invalid date format

0x5604 BRT code invalid end date.

0x5605 BRT code no bad blocks.

0x5606 BRT code output file could not be created

0x5607 BRT code invalid input file

0x5608 BRT code Invalid file could not be opened.

0x5609 BRT code clean failed in LUNs.

0x560a BRT code error getting events.

0x560b BRT code incorrect input file.

0x560c BRT code unknown exception.

0x560d BRT code success with errors.

0x560e BRT code clean session timeout.

Technical notes for specific platforms

The information described in the following section applies to specific platforms that support the Navisphere Agent, CLI, Server Utility, and Storage System Initialization Utility software. The platforms are listed alphabetically.

83

Technical notes


AIX - Host agent

Install the agent -- In AIX systems, you must use the inutoc command to create a .toc file before you install the Navisphere Agent. Type the following three commands at the command line prompt to create the .toc file:

cd /usr/sys/inst.images rm .toc /usr/sbin/inutoc

Make sure the agent stops -- When you use the rc.agent stop command to stop the Navisphere Agent, it may not stop. To ensure the agent has stopped, type:

ps –e | grep agent

(this returns the PID of the process)

kill –9 <PID>

The AIX Array Initialization Tool is no longer distributed.

The Install script for NAVIAGENT and NAVICLI was modified – It now uses executables from the /usr/sbin directory instead of the /etc directory. This eliminated the need for the bos.compat.links package that linked executables from /etc to /usr/sbin.

You may have a problem installing Navisphere host software from the CD -- You may have trouble installing the Navisphere packages directly from the CD. The problem is that smit looks for installable packages in usr/sys/inst.images. The top-level AIX directory on the CD causes smit to fail. To install the software you should: 1. Mount the CD. 2. Copy the contents of <cd_mount_point>/AIX/usr/sys/inst.images

to /usr/sys/inst.images. 3. Run smit, and direct it to /usr/sys/inst.images.

AIX – Utilities

AIX runtime environment: AIX runtime environment (rte) should be at version 8 or later. By default AIX 5.2 and AIX 5.3 come with default runtime environment 6. You must install xlc.rte.aix50.feb2007.ptf from following location:

http://www-1.ibm.com/support/docview.wss?rs=2239&context=SSJT9L&dc=D400&uid=swg24015076&loc=en_US&cs=UTF-8&lang=en





84

Technical notes


HP-UX – Storage system initialization utility

You can also run the initialization utility from the CX (or AX)-Series Server Support CD as described below for your operating system.

1. Insert the CX (or AX)-Series Server Support CD in the server’s drive.

2. At the command prompt (#) in an hpterm window, enter the following command to create a CD-ROM directory:

mkdir /cdrom

Identify the CD drive device file by executing the following command and looking for the CD in the drive listing:

ioscan -funC disk

This command lists all recognized drives and their associated device files. The CD device file will be similar to /dev/dsk/c1t2d0.

3. Mount the CD drive:

mount –F cdfs –o rr /dev/dsk/device_filename /cdrom

where device_filename is the device filename from step 3. For example:

mount –F cdfs –o rr /dev/dsk/c1t2d0 /cdrom

4. Navigate to the HP-UX directory:

cd /cdrom/hpux

5. Run the Navisphere Initialization Utility:

./naviinittool

HP-UX/AIX – Server Support CD

CX (or AX)-Series Server Support CDs are created using the Rock Ridge extension format. Hence on AIX and HP-UX systems you need to use proper options for Rock Ridge format when mounting the CD.

Linux – Host agent/CLI

IA-64 Red Hat Enterprise Linux 4.0 installation -- If you get errors while trying to install Navisphere packages on an IA-64, install the IA-32 Execution Layer and required 32-bit compatibility packages for runtime support for 32-bit application. Please refer to the following procedure from Red Hat:

http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-notes/as-itanium/



85

Technical notes


Red-Hat Enterprise Linux-4 for the 64-bit Intel-Itanium2 architecture includes runtime support for 32-bit applications through Intel's IA-32 Execution Layer. The IA-32 Execution Layer is provided on the Extras disk for the Intel-Itanium2 architecture. In addition, a set of 32-bit libraries and applications are provided on a separate 32-bit Compatibility-Layer disk. Together, the IA-32 Execution Layer and 32-bit compatibility packages provide a runtime environment for 32-bit applications on the 64-bit native distribution. To install the IA-32 Execution Layer and required 32-bit compatibility packages, follow these steps: 1. Install Red-Hat Enterprise Linux 4 for the Intel-Itanium2

Architecture. 2. During the first system boot, the Additional CDs screen

prompts you to insert the Red Hat Enterprise Linux Extras CD. Insert the CD (which is where the ia32el package is located) and click Install if you wish to run 32-bit applications.

3. When prompted, choose Misc from the available choices, which will install the ia32el and ksh packages.

4. You can click Details to verify the selection of packages to be installed. At this point the ia32el package will start itself as a service.

5. After the installation of the packages, you will be prompted again with the same Additional CDs screen as during installation. At this point you can choose to install compatibility libraries by inserting the 32-bit Compatibility Layer disk and selecting Install.

6. Select all of the packages, or the particular packages required in order to provide runtime support for your 32-bit applications.

7. To verify the installation of the 32-bit compatibility layer and libraries after installation, verify that the /emul directory has been created and contains files.

8. To verify that the 32-bit compatibility mode is in effect, type the following in a shell prompt:

service ia32el status

86

Technical notes


IA-64 Red Hat Enterprise Linux 5.0 installation. -- If you receive errors while trying to install Navisphere packages on an IA-64, install the IA-32 Execution Layer and required 32-bit compatibility packages to runtime support for 32-bit application on ia64. Please refer to the following procedure from Red Hat:

https://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/release-notes/RELEASE-NOTES-ia64-en.html

The IA-32 Execution Layer is provided on the Supplementary disk for the Intel Itanium2 architecture. In addition, a set of 32-bit libraries and applications are provided on a separate 32-bit Compatibility Layer disk. Together, the IA-32 Execution Layer and 32-bit compatibility packages provide a runtime environment for 32-bit applications on the 64-bit native distribution. To install the IA-32 Execution Layer and required 32-bit compatibility packages, follow these steps:

1. Insert the Red Hat Enterprise Linux 5 Supplementary CD, which contains the ia32el package.

2. After the system has mounted the CD, change to the directory containing the Supplementary packages. For example:

cd /media/cdrom/Supplementary/

3. Install the ia32el package:

rpm -Uvh ia32el-<version>.ia64.rpm

Where <version> is the corresponding version of the ia32el package to be installed.

4. Eject the Supplementary CD:

eject /media/cdrom

5. To verify the installation of the 32-bit compatibility layer and libraries after installation, check that the /emul directory has been created and that it contains files.

6. To verify that the 32-bit compatibility mode is in effect, type the following in a shell prompt

service ia32el status

7. At this point you can install compatibility libraries by inserting the 32-bit Compatibility Layer disk. You may choose to install all of the packages available on the disk or choose the particular packages required to provide runtime support for your 32-bit applications.



87

Technical notes


Registration failures (not enough devices). -- The default number of sg devices installed on both Red Hat and SuSE systems (16 entries) may not be enough, and as a result some of the paths may not be registered. To fix this problem, you must create an adequate number of these sg entries. The system administrator can use the following script (or its equivalent) to create these entries:

#!/bin/bash -

x=0

while (($x < 256))

do

y=$((x++))

fname="/dev/sg"$y

echo mknod $fname c 21 $y

mknod $fname c 21 $y

done

Location of Naviagent start/stop script location has changed -- For all versions of Linux, the script is in /etc/init.d/naviagent.

Linux 64-Bit Systems(Red Hat and SUSE). -- To run Navisphere Agent and CLI on 64-bit Linux systems, you must have 32-bit compatibility libraries installed on the system.

Linux – Storage system initialization utility

You can also run the initialization utility from the CX-Series Server Support CD or AX-Series Server Support CD as described below for your operating system.

1. Insert the CX (or AX)-Series Server Support CD into the server’s drive.

2. From a console window, mount the CD-ROM drive by entering the following command:

mount /mnt/cdrom

3. Change to the CD-ROM directory by entering the following command:

cd /mnt/cdrom

4. Navigate to the Linux directory.

cd linux

5. Run the Navisphere Initialization Utility.

./naviinittoolcli

88

Technical notes


Solaris - Storage system initialization utility

You can also run the initialization utility from the CX-Series Server Support CD or from the AX-Series Server Support CD as described below for your operating system.

1. Insert the CX (or AX)-Series Server Support CD into the server’s drive.

2. Navigate to the Solaris directory:

cd /cdrom/cdrom0/solaris

3. Run the Navisphere Initialization Utility.

./naviinittool

Solaris - Utilities

To exit when running a utility from the CD with Solaris File Manager - Exit (e) does not work when running the utilities from the CD with the Solaris File Manager. To exit, use CTRL-C.

Windows - Host agent

Installing a new agent uninstalls previously installed agent – When the agent is installed, any previously installed agent will be uninstalled as part of the new agent installation process.

Auto-detect – The Host Agent configuration file should not contain any ATF, PowerPath or standard device entries for CX, CX3, or AX storage systems. The auto-detect feature of the remote agent configurator does not detect CX, CX3, and AX storage systems.

Windows – CLI

Unable to add iSCSI host or host appears multiple times in iSCSI configurations --If you cannot add an iSCSI host to a storage group or the iSCSI host appears multiple times in the CLI portlist command, it may be due to incorrect handling of case in the Microsoft Initiator.

If you manually registered an iSCSI initiator and then restarted the Host Agent, you may experience these problems when you use capital letters in hostnames. If you have capital letters in the hostname, perform the following steps to correct the problem:

1. Start the iSCSI initiator applet in the Control Panel on your host. 2. Select the Initiator Settings tab. 3. Select the Change button at the bottom of the dialog box. This

will change the iSCSI name to lowercase.

89

Technical notes


4. Using CLI, remove the manually created initiator record. 5. Reboot the host or restart the Host Agent to push the initiator to

the storage system.

If this does not solve the problem, contact Microsoft for corrective action.

IPv6 only hosts. -- If any client side tool (NST, CLI) experiences long delays on an IPv6-only Windows 2003 system, you must verify the DNS setup. Failed DNS lookups can cause long delays in executing commands. The delays will not be observed if there is an IPv6 DNS server configured or the DNS Client Service is stopped. Use the “netsh” utility to set the IPv6 DNS Server address or use the control panel to stop the DNS Client Service.

Clusters

EMC recommends that you place all shared disks (LUNs), including the quorum disk, into the same storage group.

Host agent iSCSI support

The host agent will not detect iSCSI storage systems connected to it during the system startup. The agent will do a rescan 10 minutes after the host reboot, and during that time will detect all iSCSI storage systems connected to it and register them.

VMware

ESX 3.0.x and later do not support mixed iSCSI and Fibre Channel connections to a single, physical VMware server.

ESX 3.0.x and later require version 03.22, or later, of the FLARE Operating Environment.

ESX 3.5.x and ESX 4.0.x, which have the Service Consoles, will work the same way that ESX 3.0.x works.

ESX 3i and ESX 4i have no Service Consoles to install or run the Host Agent or server utility. Registration of the CLARiiON storage system will happen automatically when the ESX 3i or ESX 4i server reboots or when you rescan the ESX 3i or ESX 4i server host bus adapters. Manual registration is not necessary.

90

Technical notes


VMware – CLI

• The CLI is supported in the Service Console on ESX 3.0.x, ESX 3.5.x, and ESX 4.0.x.

• The CLI is supported in the following Virtual Machines: Windows (Windows 2000, Windows Server 2003) and Linux (Red Hat 3 and 4, SLES 8).

VMware – Host agent

• The Host Agent is supported in the Service Console on ESX 3.0.x, ESX 3.5.x, and ESX 4.0.x.

• The Host Agent is also supported in the following Virtual Machines for iSCSI software: Windows (Windows 2000, Windows Server 2003) and Linux (Red Hat 3 and 4, SLES 8).

VMware – Server utility

The server utility is supported in the Service Console on ESX 3.0.x, ESX 3.5.x, and ESX 4.0.x.

The Server Utility is also supported in the following Virtual Machines for iSCSI software: Windows (Windows 2000, Windows Server 2003) and Linux (Red Hat 3 and 4, SLES 8).

VMware – Storage system initialization utility

You can run the storage system initialization utility in both the ESX Service Console and the Virtual Machines.

91

Documentation


Documentation

The following documents apply to this product release:

Part number Publication

300-002-044 EMC CLARiiON Server Support Products for AIX Installation Guide

300-002-043 EMC CLARiiON Server Support Products for HP-UX Installation Guide

300-002-041 EMC CLARiiON Server Support Products for Linux Installation Guide

300-005-048 EMC CLARiiON iSCSI Server Setup Guide for AIX

300-005-050 EMC CLARiiON iSCSI Server Setup Guide for HP-UX

300-003-806 EMC CLARiiON iSCSI Server Setup Guide for Linux

300-003-807 EMC CLARiiON iSCSI Server Setup Guide for VMware ESX Server 3.i and 3.x Hosts

300-003-805 CLARiiON iSCSI Server Setup Guide for Windows

300-004-281 EMC CLARiiON Server Support Products for VMware ESX Server and Virtual Machines Installation Guide

300-002-039 EMC CLARiiON Server Support Products for Solaris Servers Installation Guide

300-002-038 EMC CLARiiON Server Support Products for Windows Servers Installation Guide

069001166 Installation Roadmap for CLARiiON Storage Systems (Powerlink)

Documentation updates

This section contains changes to the CLARiiON server support products installation guides listed in the table above and the Navisphere Server Utility help, which is available with the Windows version of the Server Utility.

92

Documentation


Navisphere Server Utility help

The Troubleshooting the Host Agent using the Navisphere Server Utility topic states that the host agent and server utility cannot be installed on the same server; this is no longer true. If you want to install the server utility on the same server as the host agent, you can install version 6.22.20 or later of the server utility.

Navisphere Secure CLI

The Navisphere Secure CLI can run on servers or remote management stations that are attached to CLARiiON storage systems.

Please note the following corrections to the EMC Navisphere Command Line Interface (CLI) Reference manual (300-003-628-A08):

The createrg command omitted the RAID 6 and hot spare support for CX and AX4-5 series. The –raidtype switch is mandatory for Navisphere Express managed AX4-5 series storage systems, but optional for Navisphere Manager managed AX4-5 series and CX with FLARE 03.26.XXX and later. It is not a supported switch for CX with FLARE versions earlier than 03.26.XXX, or for AX series systems. For AX4-5 series storage systems, RAID 6 is supported only on FLARE 02.23.050.5.7xx and later. For an AX4-5 series storage system managed by Navisphere Express, a hot spare RAID group can be created only through the bind on disk command.

Write caching is highly recommended for RAID types RAID 5 and RAID 6, and read caching is recommended for these RAID types.

The -parityelements and –type switches in the getlun command are relevant to RAID 6 LUNs.

A RAID 6 LUN can be in a metaLUN.

The networkadmin command omitted support for setting the SNMP ommunity string, which is a suboption of the -mib switch. You can specify -community <communitystring> to set the SNMP community string to which the SP's SNMP agent responds. Community strings can be no more than 255 characters in length.

For example, to set the SNMP community to "NoTpUbLiC" (without the quotes):

networkadmin -mib -community NoTpUbLiC

And to enable SNMP request processing at the same time:

networkadmin -mib -enable -community NoTpUbLiC

93

Documentation


Please note the following corrections to the EMC Navisphere Command Line Interface (CLI) Reference manual (300-003-628-A10):

Replace the description and the note of the -elszm option for the metalun -expand command with the following text:

Sets the stripe element size for a metaLUN component. You determine this by multiplying the stripe size of the first LUN in each component (stripe size of the first LUN = stripe element size of the LUN multiplied by the number of disks in the LUN) by the element size multiplier. Valid multiplier values are 1 through 255. The default element size multiplier is 4 and the multiplier should be set according to the Best Practices.

For more information on metaLUN stripe multiplier, refer to the EMC CLARiiON Best Practices for Fibre Channel Storage: FLARE Release 26 Firmware Update, available on the Powerlink website.

Windows Server Support Installation Guide

The Windows Server Support Installation Guide indicates that CX4 storage systems do not support Windows 2000 servers as an attached host. CX4 series storage systems do support Windows 2000 servers as an attached host but host software support for Windows 2000 servers is limited to version 03.26 or earlier. Scripts that run from Windows 2000 servers will not support the complete set of CX4 features. Refer to the ESM for more detailed information.

94

Software media, organization, and files


Software media, organization, and files

The following table lists the software and documentation media for this product version.

Part number CD-ROM

053-002-131 CX4-Series Core Server Support CD-ROM

053-002-135 EMC Documentation and Resources for CX4 Series and Storage Systems CD-ROM

053-001-987 AX4-Series Server Support CD-ROM

Installation

For installation instructions, refer to the documents listed in the “Documentation” section.

95

Troubleshooting and getting help



This section provides specific instructions for contacting EMC Customer Service and obtaining additional information about EMC products.

Where to get help

EMC 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 Powerlink and choose Support. On the Support page, you will see several options, including one for making a service request. Note that to open a service request, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.


96



Copyright © 2008-2009 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. However, 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 regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

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.

Open source copyright and license information for this product is in “Navisphere Management Suite Open Source Copyright and License Information” located in the Technical Documentation and Advisories section on EMC Powerlink.

Navi Agent

Documents

Transcript of Navi Agent