navisphere host agent/cli and utilities version 6.28.21 release...

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 -o should be displayed as: Expected: startsnap -s -o

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

http://powerlink.emc.com/

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:///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:///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 t

navisphere host agent/cli and utilities version 6.28.21 release...

Documents