300-004-292 A06 Elccnt 0

EMC Navisphere
Host Agent/CLI and Utilities

Version 6.24.3 for FLARE OE 03.24.yyy and 02.24.yyy
Release Notes
P/N 300-004-292
REV A06
February 29, 2008
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,
Windows Server 2003, and Windows 2000 operating systems.
Topics include:
Product description ................................................................................... 2
New features and changes........................................................................ 4
Environment and system requirements.................................................. 6
Fixed problems ......................................................................................... 10
Known problems and limitations .......................................................... 20
Technical notes ......................................................................................... 35
Documentation ......................................................................................... 77
Software media, organization, and files ............................................... 78
Installation ................................................................................................ 78
Troubleshooting and getting help ......................................................... 79
1
Product description
Product description
The EMC SP Agent (Array Agent), which resides on the storage
processors (SPs) in CX series, CX3 series and AX series storage systems,
communicates with Navisphere client applications to manage CX series,
CX3 series and AX 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 and
AX 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).
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 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 or AX 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.
2 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Product description
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.
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 the connections to the storage
system are correct and the mounted volumes are visible. It also allows a
user to register the host with the attached storage system. Note that the
host agent provides additional information that is not available from
running 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 a user requires that information,
the agent must be running on that host instead.
The storage system initialization utility is an application that can be used
to simplify the initialization and setup of a storage system. It provides a
simple, straightforward user interface to discover and initialize storage
systems. Using an existing LAN, both SPs can be set through the same
operation.
EMC Navisphere Host Agent/CLI and Utilities Release Notes 3

New features and changes
New features at initial 6.24 version

This section describes any new features and changes for the 6.24 version
of the product.
Secure CLI support for AIX and HP-UX
Secure CLI is now supported on AIX and HP-UX.
NDU support in Secure CLI
Secure CLI now supports the NDU command.
Storage-system capture and duplication
This is a CLI-only feature that lets you capture a storage system’s
configuration and duplicate it onto another storage system.
Ability to clone a mirror
The ability to clone a mirror has been added.
Fast bind
Fast bind allows a LUN to be used as soon as it is bound. It remains
unowned for a short period of time, and then transitions to being
fully usable.
LDAP-based security
LDAP users may configure their storage system so that users can use
their LDAP login to log in to Navisphere.
Proactive hot sparing
Proactive hot sparing is a function that initiates a copy from a failing
disk onto a hot spare disk before the failing disk actually fails. Since
the copy is faster than a rebuild, this allows for reduced total
recovery time.
Global reserved LUN pool
The SP A and SP B reserved LUN pools have been combined into a
single pool that both SPs share.
Application of event monitor templates to peer SP
Event monitor now works when you are setting up storage-system-
based responses. When you apply a template to one of the storage
processors of the storage system, the template will automatically be
applied to the other storage processor. In the past, you would have

to apply the template to both storage processors for complete

monitoring of the storage system. This change does not affect
centralized monitoring, where responses are generated from an off-
array monitoring station. Also, this does not affect the removal of
templates. A template must be removed individually from each SP
as in prior versions.
Increased SnapView limits
The limits on the number of sessions, snapshots, and reserved LUN
pool LUNs has been increased
Changes to the 6.24 version from previous versions

The following command sets now require a Secure CLI security file in
order to operate under Navisphere CLI scripts: SnapView snapshot,
SAN Copy and MirrorView -sync.
You can still use Navisphere CLI to issue these commands, but they now
call Navisphere Secure CLI when run against a storage system running
either FLARE® version 03.24 or 02.24. The existing Navisphere CLI
output is unaffected by these changes.
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) and
Java CLI will not be supported. Using Secure CLI now will help avoid
the need to modify scripts at a later date.

Environment and system requirements

This section explains the minimum hardware and software
environments for proper operation of this version of the Navisphere
Host Agent, CLI, Secure CLI, Server Utility and Storage System
Initialization Utility.
Note: See the EMC Support Matrix for specific supported OS versions.
Not all operating systems support PowerPath® software.
Operating Minimum hardware requirements Minimum software requirements

system
Solaris Sun system capable of accepting PCI, OS Sun Solaris 8, 9, 10 (U1 or U2) SPARC
SBus, or cPCI HBAs with at least 30 MB of Note: Navisphere host software is not
free disk space and 64 MB of RAM. supported for Solaris on x86 compatible
servers.
Windows Intel-compatible PC with 64 MB of RAM OS Microsoft Windows Server 2003 (32-bit
and at least 30 MB of free disk space. and 64-bit) (SP1 or SP2)
Windows 2000 (SP2 , SP3 or SP4)
AIX IBM AIX workstation with at least 64 MB of OS IBM AIX Version 5.2 or 5.3 (32-bit or 64-
RAM and 14 MB of free disk space. bit).
HP-UX HP server with at least 30 MB of free disk OS HP-UX 11.00, HP-UX 11i v1.0 (11.11), and
space and 64 MB of RAM. 11i v2.0 (32 bit and 64 bit, PA-RISC and
IA64 systems) running the latest patches.
Other TCP/IP protocol installed and configured.

Operating Minimum hardware requirements Minimum software requirements

system
Linux An Intel-compatible, processor-based OS Red Hat 4.0 (32- and 64-bit) U1 or U3
system capable of accepting PCI HBAs, Red Hat 3.0 (32-bit and 64-bit (single path
with at least 200 MB of free disk space and only)) (U5, U6, or U7)
64 MB RAM. SuSE SLES 9 (SP1, SP2, or SP3) or 10
(32-bit only)
SuSE SLES 8 (SP2, SP3 , SP4(32-bit and
64-bit (single path only))
MLSE 3.0 or 4.0
Red Flag 4.1 or 5.0 (32-bit)
AsianUX 1.0, 2.0 SP1
Other None
VMware VMware ESX Server with sufficient OS ESX 2.5 with Native Failover only.
memory and disk space. ESX 2.5.1 with Native Failover only.
ESX 2.5.2 with Native Failover only.
Note: Above not supported with CX3
series storage systems.
ESX 2.5.3
ESX 2.5.4
ESX 3.0
ESX 3.0.1
ESX 3.0.2
ESX 3.5.0
ESX 3i
Other None
Note: In addition to the software revisions listed above, the operating

system on the server that will run the Java-based CLI client must support
Java JRE revision 1.4.2 or higher. The operating systems currently
qualified to support this version of Java-based CLI are:
Windows Server 2003
Windows XP
Windows 2000 with SP3 or SP4
Sun Solaris 7, 8, 9 and 10
Linux Red Hat Enterprise Linux 3.0 and 4.0
Linux IA64 AS 3.0, AS 4.0
SuSE Linux SLES 8.0 and 9.0
IBM AIX 5.2 and 5.3

Hewlett-Packard HP-UX 11.0 and 11i

VMware ESX Server 2.5.1, 2.5.2, 2.5.3, 3.0, 3.0.1, 3.0.2 and 3.5.0
Navisphere management software requirements

In order to take advantage of features introduced with this version, the
CX3 series FLARE software must be at version 03.22.5xx. For CX series
and AX series systems, FLARE software must be at version 02.16.yyy
(minimum).
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:
Off-Array Manager,
Classic and Server Utility, and
FLARE Host Agent Java CLI Secure CLI Initialization Tool
03.24(CX3), 6.24 6.24 6.24 6.24
02.24(CX) 6.22.20 6.22.20
6.22 6.22
6.20 6.20
6.19 6.19
6.17
6.16
03.22(CX3) 6.24 6.24 6.24 6.24
6.22.20 6.22.20 6.22.20 6.22.20
6.22 6.22 6.22
6.20 6.20
6.19 6.19
6.17
6.16
02.20 (AX) 6.24 6.24 6.24 6.24
6.22.20 6.22.20 6.22.20 6.22.20
6.22 6.22 6.22 6.22
6.20 6.20 6.20 6.20
6.19

Off-Array Manager,
Classic and Server Utility, and
FLARE Host Agent Java CLI Secure CLI Initialization Tool
02.19 (CX) 6.24 6.24 6.24 6.24
6.22.20 6.22.20 6.22.20 6.22.20
6.22 6.22 6.22 6.22
6.20 6.20 6.20 6.20
6.19 6.19 6.19 6.19
6.17 6.17
6.16 6.16
02.17 (CX) 6.24 6.24 Not 6.24
6.22.20 6.22.20 supported 6.22.20
6.22 6.22 6.22
6.20 6.20 6.20
6.19 6.19 6.19
6.17 6.17 6.17
6.16 6.16
02.16 (CX) 6.24 6.24 Not 6.24
6.22.20 6.22.20 supported 6.22.20
6.22 6.22 6.22
6.20 6.20 6.20
6.19 6.19 6.19
6.17 6.17 6.17
6.16 6.16 6.16
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 later 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.

Fixed problems
Fixed problems
This section lists significant issues that were fixed in this version or that
were called out in a previous version 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.24.3 (FLARE versions 02.24.*.5.017 and

03.24.*.5.017)
Solution (or
Platforms Brief description Symptom details
workaround)
All Navisphere Host Agent A host agent acting as a Fixed in code
A host agent acting as a centralized centralized monitor may Exists in version:
monitor may be unresponsive. be unresponsive. This 6.24.0.6.13
14742513/140687 appears more often when
the agent is monitoring a Fixed in version:
Frequency of occurrence: large number of storage 6.24.3.2.0
Sometimes under a rare set of systems.
circumstances. KnowledgeBase ID: None
Severity:
High
All Navisphere Secure CLI The SPCollect command, Fixed in code
The SPCollect command, when issued when issued to one Exists in version:
to one storage processor, may be run on storage processor, may be 6.24.0.6.13
the other storage processor. run on the other storage
Fixed in version:
181206 processor.
6.24.3.2.0
Frequency of occurrence: KnowledgeBase ID: None
Infrequently under a rare set of
circumstances.
Severity:
Low
All Navisphere Secure CLI The port –list -all Fixed in code
The port –list -all command does not command does not display Exists in version:
display all of the information. all of the information. The 6.24.0.6.13
173633 storage processor and
Fixed in version:
HBA information is
Frequency of occurrence: missing. 6.24.3.2.0
Always under a specific set of KnowledgeBase ID: None
circumstances.
Severity:
Low

Fixed problems
Solution (or
workaround)
All Navisphere CLI The management server Fixed in code
Navisphere Secure CLI process starts up and then Exists in version:
terminates within a matter 6.24.0.6.13
The management server process starts
of minutes. During startup,
up and then terminates within a matter of Fixed in version:
the management server
minutes. 6.24.3.2.0
process tries to manage
19964760/177246 all the attached host
Frequency of occurrence: agents. If issues exist with
Infrequently under a rare set of the connections to those
circumstances. agents, the process will
Severity: repeatedly try to contact
Medium the agents. Eventually, the
process hits a resource
threshold and restarts
itself. CLI commands will
fail during the restart of the
process.
KnowledgeBase ID: None
All Navisphere CLI The management server Fixed in code
Navisphere Secure CLI process will experience Exists in version:
performance issues when 6.24.0.6.13
The management server process will
the amount of memory the
experience performance issues when the Fixed in version:
process allocates gets too
amount of memory the process allocates 6.24.3.2.0
high. The process will
gets too high.
allocate memory as
181192 different objects are
Frequency of occurrence: retrieved so larger
Rarely under a specific set of configurations are at risk
circumstances. of hitting this issue. During
Severity: these performance
Medium slowdowns with the
management server
process, Navisphere CLI
and Secure CLI
commands will also
experience performance
issues until the
management server
process is restarted.

Fixed problems
Solution (or
workaround)
All Navisphere Secure CLI If a network exception Fixed in code
The managefiles command states that a occurs when a file is Exists in version:
file is not retrievable or it cannot be transferring with the 6.24.0.6.13
deleted. managefiles command,
Fixed in version:
177212 the file remains locked and
can no longer be retrieved 6.24.3.2.0
Frequency of occurrence: or deleted until the
Rarely under a specific set of management server
circumstances. process is restarted.
Severity: KnowledgeBase ID: None
Low
Linux Navisphere CLI Issuing CLI commands Fixed in code
Issuing CLI commands from a Linux from a Linux system will Exists in version:
system will leak system resources. leak system resources. 6.24.0.6.13
Eventually any CLI command will hang Eventually any CLI
command will hang until Fixed in version:
until the server is rebooted.
the server is rebooted. 6.24.3.2.0
178448
Frequency of occurrence: KnowledgeBase ID: None
Rarely under a specific set of
circumstances.
Severity:
Medium
All Navisphere CLI A repeated loop goes Fixed in code
Navisphere Secure CLI through all LUNs and Exists in version:
disks on the system. While 6.24.0.6.13
The management server process does
iterating through the lists,
not scale well with systems that have a Fixed in version:
the CPU on the storage
high number of LUNs and disks. 6.24.3.2.0
processor is completely
181189 busy and Navisphere CLI
Frequency of occurrence: and Secure CLI
Rarely under a specific set of commands may
circumstances. experience performance
Severity: issues or the storage
Medium processor may panic.
All Navisphere Secure CLI If the –t option is used but Fixed in code
If the –t option is used but a value less a value less than 120 Exists in version:
than 120 (seconds) is given, the value is (seconds) is given, the 6.24.0.6.13
ignored and the default timeout is used. value is ignored and the
Fixed in version:
180690 default timeout (120
seconds) is used. Timeout 6.24.3.2.0
Frequency of occurrence: values down to 3 seconds
Always under a specific set of should be allowed.
circumstances. KnowledgeBase ID: None
Severity:
Low

Fixed problems
Problems fixed in update 6.24.2 (FLARE versions 02.24.*.5.014 and

03.24.*.5.014)
Solution (or
workaround)
All Secure CLI The arrayconfig Fixed in code
Using the –output option with the command does not create Exists in version:
-capture command does not create a an output file even if one 6.24.0.6.13
file. does not already exist
Fixed in version:
(162054) 6.24.2.5.0
Frequency of occurrence:
Always
Severity:
Low
CX3-10c CLI, Secure CLI Selecting ports 2 or 3 with Fixed in code
The alpa command does not work the alpa command on Exists in version:
against the CX3-10c storage system. CX3-10c storage systems 6.24.0.6.13
(165459) returns an error.
Fixed in version:
Frequency of occurrence: KnowledgeBase ID
6.24.2.5.0
Always
Severity:
Medium
All Secure CLI The getlun command Fixed in code
After issuing a getlun command, the CLI entered without any Exists in version:
exits with Unknown error. switches or with the 6.24.0.6.13
(165601) -mirrorname switch may
Fixed in version:
result in the command
Frequency of occurrence: prematurely ending with 6.24.2.5.0
Infrequently under a specific set of an Unknown error.
circumstances KnowledgeBase ID
Severity:
Medium

Fixed problems
Solution (or
workaround)
All Secure CLI With systems running If the storage-system is
The getlun command entered with the Navisphere software running Navisphere
-snapshots switch displays None in the earlier than version 6.24, version 6.24 or later,
the snapshot information Not Available
Snapshots list field.
was available. With is displayed. If it is
(171478) running Navisphere
systems running
Frequency of occurrence: Navisphere version 6.24, it software earlier than
Always under a specific set of is no longer available to version 6.24, the
circumstances the command and the appropriate snapshot
Severity: default value is None. information is
Low KnowledgeBase ID displayed.
Exists in version:
6.24.0.6.13
Fixed in version:
6.24.2.5.0
All CLI In some situations the Fixed in code
CLI exits prematurely or dumps core. connection the CLI used Exists in versions:
(157040) was closed because of an 6.22.0.4.67
exception that the CLI did
Frequency of occurrence: not expect. In those 6.24.0.6.13
Rarely under a specific set of situations the CLI would Fixed in version:
circumstances exit or dump core. 6.24.2.5.0
Severity: KnowledgeBase ID
Medium
Solaris Secure CLI The installation of the Fixed in code
The installation of the Solaris Agent/CLI Solaris Agent/CLI package Exists in version:
package permanently changes permanently changes 6.22.0.4.67
permissions on a root directory from 755 permissions on a root
directory from 755 to 775. 6.24.0.6.13
to 775.
(168149) KnowledgeBase ID
Fixed in version:
6.24.2.5.0
Always
Severity:
Medium
CX300 CLI Issuing a getall command The actual port speed
CX500 Port speed information is displayed as to a CX300, CX500, or is displayed.
CX700 Invalid port speed. CX700 running Exists in version:
(171302) Navisphere version 6.24 6.24.1.5.0
software causes port
Frequency of occurrence: Fixed in version:
speed information to be
Always under a specific set of displayed as Invalid 6.24.2.5.0
circumstances port speed.
Severity: KnowledgeBase ID
Low

Fixed problems
Solution (or
workaround)
All CLI The networkadmin -get The networkadmin -get
The networkadmin -get command does command does not work if command returns the
not work if it is issued with the hostname issued with the hostname proper information for
of the storage processor instead of the IP of the storage processor requests made with
address. instead of the IP address. either SP hostname or
(171332) KnowledgeBase ID SP IP address.
Frequency of occurrence: Exists in version:
Always under a specific set of 6.24.0.6.13
circumstances Fixed in version:
Severity: 6.24.2.5.0
Low
All CLI, Secure CLI In configurations with a Fixed in code.
Commands may time out or take a long large number of LUNs and Exists in versions:
time before completing. metaLUNs and a large 6.22.0.4.67
(18116846/168125) number of LUNs mapped
to hosts, commands may 6.24.0.6.13
Frequency of occurrence: take a long time to Fixed in version:
Infrequently under a specific set of complete. 6.24.2.5.0
circumstances KnowledgeBase ID
Severity:
Medium
All CLI The CLI will hang while Fixed in code.
CLI ndu command hangs while running running the preinstallation Exists in version:
the preinstallation rules. rules and prevents the 6.24.0.6.13
NDU.
(169904) Fixed in version:
KnowledgeBase ID
(172397) 6.24.2.5.0
Infrequently under a specific set of
circumstances
Severity:
Medium

Fixed problems
Problems fixed in update 6.24.1

Platforms Symptom details Problem description Solution description
Windows Navisphere Server Utility The setting for iSCSI The HAVT portion of
Incorrect network settings can network traffic may cause the Navisphere Server
cause performance issues on network congestion and a Utility will now report
Windows systems using iSCSI. large drop in iSCSI and warn you that
(162278) performance. systems with the
Microsoft iSCSI
Frequency of occurrence: Initiator installed and
Always more than one network
Severity: interface should use
Low the Navisphere Server
Utility to optimize their
iSCSI connections.
Exists in versions:
6.19.0.4.14 6.22.0.4.67
6.22.20.0.9 6.24.0.613
Fixed in version:
6.24.1.4.0
Windows Navisphere Server Utility The setting for iSCSI The iSCSI
Incorrect network settings can network traffic may cause configuration wizard
cause performance issues on network congestion and a now supports a page
Windows systems using iSCSI. large drop in iSCSI that shows you
(164259) performance. possible network
connections that could
Frequency of occurrence: exhibit this iSCSI
Always network congestion. It
Severity: allows you to select
Low the networks to modify
and will make the
changes for you.
Exists in versions:
6.19.0.4.14 6.22.0.4.67
6.22.20.0.94
6.24.0.6.13
Fixed in version:
6.24.1.4.0

Fixed problems

All Navisphere Secure CLI The management server The memory
Memory corruption caused the process opens a PSM file allocation, where the
management server process to and then tries to allocate a process was hanging
hang while it had a PSM file buffer to copy the data. before, now happens
open. This was causing the The memory allocation while the PSM file is
storage processor to panic. hangs because of previous closed.
(160065) memory corruption. This Exists in versions:
then causes the PSM timer 6.19.0.4.14 6.22.0.4.67
Frequency of occurrence: to trigger its two-minute
Rarely under a rare set of 6.22.20.0.94
panic timer. 6.24.0.6.13
circumstances
Severity:
Fixed in version:
Medium
6.24.1.5.0
Linux AIX Navisphere Host Agent The host agent is The code was modified
Solaris HP- Using a host agent as a essentially "managing" so that it does not
UX VMware centralized monitor that is both storage processors. access the second
managing both storage The agent ends up with storage system copy
processors of a storage system two storage-system after it has been
is causing the host agent to objects and deletes one to deleted.
crash. save on memory usage. It Exists in versions:
(162332) then tries to use the 6.16.0.4.63 6.19.0.4.14
deleted memory and 6.22.0.4.67
Frequency of occurrence: crashes.
Always 6.22.20.0.94
6.24.0.6.13
Severity:
Fixed in version:
Medium
6.24.1.5.0
All Navisphere CLI The getall command will The debug information
Issuing a getall command to a display debug information was removed and now
CX300, CX500, or CX700 when trying to display a displays Invalid
running version 6.24 software port's speed if the port Port Speed.
will cause debug information to speed is not set correctly Exists in versions:
be included in the port or is invalid. 6.22.0.4.67
information section. 6.22.20.0.94
(164260) 6.24.0.6.13
Frequency of occurrence: Fixed in version:
Always under a specific set of 6.24.1.5.0
circumstances.
Severity:
Low

Fixed problems

All Navisphere CLI When using the The -np switch is now
The lunmapinfo command lunmapinfo command and passed down when the
does not persist the -np ("no specifying the IP of a storage processor is
poll") option when querying the storage processor, the managed. If the switch
storage processors. storage processor will be is specified, the
managed and polled to storage processor will
(161814)
gather the appropriate not be polled.
Frequency of occurrence: information. You can Exists in versions:
Always include a -np switch to ask 6.16.0.4.63 6.19.0.4.14
Severity: that a poll is not done. This 6.20.0.3.11 6.22.0.4.67
Low switch is not being passed 6.22.20.0.94
down when managing the 6.24.0.6.13
storage processor so a poll
is always done. This can
Fixed in version:
have an impact on
performance. 6.24.1.5.0
All Navisphere CLI When the setpath CLI will now query the
The setpath command cannot command is used against port in question to
be used to manually register a a CX3-10c storage determine what type of
host to a CX3-10c storage system, it assumes that port it is and will issue
system. there are four iSCSI ports the correct command
but there are only two. to register.
(164590)
This causes the system to Exists in versions:
Frequency of occurrence: give an error about iSCSI 6.24.0.6.13
Always under a specfic set of ports not being configured
circumstances. Fixed in version:
when you are specifying a
Severity: fibre port on the command 6.24.1.5.0
Medium line.

Fixed problems
Problems fixed in update 6.24.0

Platforms Symptom details Problem description Solution Description
All Navisphere CLI For some SAN Copy The commands are
For some SAN Copy options, the -m flag will not now functional.
commands, the -m flag will not return data. Specifically, Exists in versions:
return data. the SAN Copy -time and - 6.16.0.4.63 6.19.0.4.14
(128279) complete options do not 6.20.0.3.11 6.22.0.4.67
return any data.
Frequency of occurrence: 6.22.20.0.94
Always
Severity: Fixed in version:
Medium 6.24.0.6.13
All Navisphere Secure CLI Snap session UI properties The UI, classic CLI,
Snap session creation time show a different session and secure CLI all
varies. create time than navicli list report consistent
146737 sessions -createtime, times.
which shows a different Exists in versions:
Frequency of occurrence: create time than naviseccli
Always 6.19.0.4.14
list sessions -createtime
6.20.0.3.11 6.22.0.4.67
Severity:
6.22.20.0.94
Medium
Fixed in version:
6.24.0.6.13

Known problems and limitations

This section includes important information that does not appear
anywhere else. This section consists of two major subsections:
The first one describes problems and limitations that are common to
host agents for all platforms.
The second section describes problems and limitations for platform-
specific host agents.
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 and limitations common to all platforms

The information described in the following sections applies to all
platforms that support the Navisphere Host Agent, CLI, Secure CLI,
Server Utility, and Storage System Initialization Utility software.
Platforms Symptom details Problem description Prevention/resolution
or workaround
All Navisphere CLI If the customer uses 0_10 This has been the way
The disk firmware update to specify the disk, bus 0 is the CLI behaves for
command uses bus 0 as a automatically assumed as several other
default. the specified bus in the commands as well.
CLI. Use the b_e_d format
(156450)
to indicate a different
Frequency of occurrence: bus.
Always Exists in version:
Severity: 6.24.0.6.13
Low
All Navisphere CLI The arrayconfig Use Secure CLI
Java CLI usage shows the command is shown in the instead of Java CLI.
arrayconfig option. usage for Java CLI. Java Exists in version:
CLI does not support this 6.24.0.6.13
(153363)
command.
Always
Severity:
Medium


or workaround
All Navisphere CLI If you are using version Use Secure CLI
The navicli mirrorview -list 6.24 classic CLI and instead of Java CLI.
output removed leading issuing the mirrorview - Exists in version:
spaces for some fields. list command to a storage 6.24.0.6.13
system running a version
(157304)
of Navisphere earlier than
Frequency of occurrence: version 6.24, the format
Always will be different (some
Severity: white spaces are missing).
Low
All Navisphere SecureCLI After a successful Make sure the new
The arrayconfig -rollback duplication, if you destroy RAID group has a
command may delete the a RAID group and create different ID.
user configuration. another RAID group with Exists in version:
the same ID (even if it is a
(147897) 6.24.0.6.13
different type), the rollback
Frequency of occurrence: will destroy the newly
Always under a specific set of created RAID group as
circumstances well,
Severity:
Low
All Navisphere Secure CLI If you set up SAN Copy None. The SAN Copy
The arrayconfig commands sessions and perform an configuration is not
do not copy SAN Copy arrayconfig supported with the
sessions. -capture/-duplicate arrayconfig
(155510) sequence, the SAN Copy command.
sessions are not present. Exists in version:
Always 6.24.0.6.13
Severity:
Critical
All Navisphere Secure CLI If you are creating a SAN The version 6.22
The sancopy -create Copy session with version destination storage
command may fail. 6.24 as the source and system must be part of
version 6.22 as the the SAN Copy domain.
(156861)
destination, the command Or use Navisphere
Frequency of occurrence: will fail. Manager to create the
Always under a specific set of SAN Copy sessions.
circumstances Exists in version:
Severity: 6.24.0.6.13
Medium


or workaround
All Navisphere Secure CLI The firmware command None.
For the firmware command, ignores the -c command, Exists in versions:
secure CLI automatically that was used in classic 6.19.0.4.14 6.20.0.3.11
copies the firmware file to the CLI when the firmware file 6.22.0.4.67
storage system. was not located on the 6.22.20.0.94
(157009) storage system. Now it will 6.24.0.6.13
copy the local firmware file
Frequency of occurrence: to the storage system.
Always
Severity:
Low
All Navisphere Secure CLI If you are creating a You must supply an IP
The mirrorview -addimage MirrorView image, the address for the
command may fail. command will fail if you -arrayhost parameter.
supply a hostname for the Exists in version:
(158010)
-arrayhost parameter.
Frequency of occurrence: 6.24.0.6.13
Always under a specific set of
circumstances
Severity:
Medium
All Navisphere Secure CLI Unable to create SAN The management of
Unable to create a SAN Copy Copy sessions with secure the destination LUN
session through secure CLI CLI when using a version information occurs in a
using a version 6.19 storage 6.19 storage system with a different area (the
system and any storage storage system running version 6.19 storage
system running any other version 6.24. To system) with Secure
version. reproduce, first make a CLI versus classic CLI
(158198) SAN Copy connection with and Navisphere
a source storage system Manager. As a result,
Frequency of occurrence: running version 6.19 and the source storage
Always another storage system system cannot
Severity: running any other version successfully manage
Critical as destination. Next issue the future storage
the sancopy -create system's LUN
command. The command information. A
will fail with Command workaround is to use
not supported. Navisphere Manager
or classic CLI to
configure things in this
situation.
Exists in versions:
6.19.0.4.14 6.20.0.3.11
6.22.0.4.67
6.22.20.0.94
6.24.0.6.13


or workaround
All Navisphere Secure CLI The backendbus - None
The backendbus -analyze analyze command might Exists in version:
command might not work not recognize all cases 6.24.0.6.13
correctly. where a speed change is
(159019) required.
Always under a specific set of
circumstances
Severity:
Medium
All Navisphere CLI The getloop command None
The getloop command does does not return any Exists in version:
not return any connections. connections. The other 6.24.0.6.13
information is present; only
(159020)
the connections are
Frequency of occurrence: missing.
Always
Severity:
Low
All Navisphere Secure CLI The reserved -lunpool - None
The reserved -lunpool - freeluns command will Exists in version:
freeluns command output is display a blank field if 6.24.0.6.13
not consistent with classic there are no unallocated
CLI. LUNs. This is not
(158423) consistent with classic CLI,
where under those
Frequency of occurrence: conditions the same
Always under a specific set of command would display
circumstances None.
Severity:
Medium


or workaround
All Navisphere Storage System A race condition exists Since the management
Initialization Utility between the iSCSI port ports are set up
Running the utility against an settings being applied and correctly in all cases,
uninitialized storage system the storage processor the workaround is to
does not always result in the rebooting to pick up the use the Navisphere
iSCSI port settings being new management port Manager UI (Storage
applied (that is, IP, gateway, settings. System > iSCSI >
and netmask). The storage- Port Management) to
system name, security configure the iSCSI
settings, and management port settings;
port settings are correctly set alternatively, the
in all cases. Navisphere Secure
(158820) CLI connection
command can be
Frequency of occurrence: used.
Likely under a specific set of Exists in versions:
circumstances
6.22.0.4.67
Severity: 6.22.20.0.94 6.24.0.6.7
Low
All Navisphere Secure CLI Due to changes in the way Use Navisphere
Output inconsistencies exist the getall Secure CLI Classic CLI to obtain
when using getall to target a command is handled in consistent output from
version 6.24 storage system version 6.24, some fields the getall command as
compared to a storage no longer exist in the compared to previous
system running an earlier output and other formatting versions.
version. has changed. EMC does Exists in version:
(159527) not guarantee consistency
6.24.0.6.13
between Navisphere
Frequency of occurrence: versions with this specific
Always command.
Severity:
Low
All Navisphere Init Tool The installation tool Do not launch at the
If you install the Navisphere finishes in an incorrect end of the wizard.
Installation Wizard and at the directory. It can start the Instead, run the wizard
end of the installation select wizard executable, but that from the Start
launch now, the resulting executable cannot find the Programs menu. This
wizard execution does not help files. starts it in the correct
have online help. directory where online
help is available. Or,
(159552)
running the wizard
Frequency of occurrence: directly from the CD
Always will provide online
Severity: help.
Low Exists in version:
6.24.0.6.7


or workaround
Unix Navisphere Server Utility - The issue here is that, Use a manual
HAVT although Control Center procedure to
EMC Control Center® agent agents may be installed on determine if EMC
information does not appear UNIX platforms, this will Control Center
in the HAVT checklist on not be detected or agent(s) are installed.
UNIX platforms. displayed by the NSU- Exists in version:
HAV. This impacts the
(155232) 6.24.0.6.12
Storage Management
Frequency of occurrence: Software section checklist
Always in the HAVT report
Severity:
Low
Linux Navisphere Server Utility - The host platforms Use a manual
HAVT affected here are: SuSE procedure to
HAVT checklist - Host System Linux, Red Hat Linux and determine this
information does not match AsianUX. The information information.
information presented in the displayed in the Exists in version:
E-Lab™ Navigator wizard for Manufacturer and Model
6.24.0.6.12
Red Hat, SUSE and AsianUX fields of the Host System
information section of the
(155234)
HAVT checklist is incorrect
Frequency of occurrence: since it does not match
Always what is presented in the
Severity: E-Lab Navigator Wizard
Low for these systems.
AIX Navisphere Server Utility - The HBA section of the Use a manual
HAVT HAVT checklist on AIX is procedure to
HAVT checklist: The incorrect in that the determine this
information in the HBA information for model and information.
section for AIX is not firmware versopm are Exists in version:
available. unavailable. It does not
6.24.0.6.12
appear that this
(155235)
information is readily
Frequency of occurrence: available with the ODM or
Always any other tool at this point
Severity: in time.
Low


or workaround
HP-UX Navisphere Server Utility - In the HAVT checklist, the Use a manual
HAVT Manufacturer field of the procedure to
HAVT checklist: Host System Host System section of the determine this
Manufacturer is not available checklist is listed as not information.
on HP-UX. available. There does not Exists in version:
appear to be a tool/API
(155236) 6.24.0.6.12
available to gather this
Frequency of occurrence: information at this time.
Always
Severity:
Low
HP-UX Navisphere Server Utility - In the HAVT checklist, the Use a manual
HAVT HBA section is missing procedure to
HAVT Checklist: HBA manufacturer and firmware determine this
information is missing or versions. The Model field information.
"incorrect" for HP-UX. contains information about Exists in version:
the HBA, but does not
(155237) 6.24.0.6.12
match up with what is
Frequency of occurrence: presented in the E-Lab
Always Navigator Wizard.
Severity:
Low


or workaround
AIX Navisphere Server Utility - In the Attached Storage Use a manual
HAVT Systems section of the procedure to
Attached storage system HAVT checklist, the model determine this
information does not display and storage operating information.
properly. environment are displayed Exists in version:
as Not available,
(156800) 6.24.0.6.12
The model # and base
Frequency of occurrence: revision of software on
Always attached storage systems
Severity: is not returned on an
Low inquiry command under
certain conditions. Those
are:
• Initiator type is not set

to fibre open (3)
• The initiator is running
in DMP mode (failover
mode 2).
This means that in the
following cases, the model
number and base revision
will be unavailable:
• HP-UX will always

report unavailable for
those fields unless the
initiators are
unregistered (initiator
type is never fibre
open)
• When AIX and Linux
are running with DMP
for failover
• When Solaris is
running a version of
DMP < 4.1 and using
for failover
• When failover mode is
incorrectly set to 2


or workaround
AIX Navisphere Secure CLI, The Navisphere Secure Use Java CLI
Navisphere CLI CLI client on AIX (navicli.jar) that
incorrectly converts 64-bit correctly reports these
The mirror -syncl-async -list unsigned integers to a values, or use
command run from an AIX string format for printing. Navisphere Secure
host reports the Image Size CLI with the -xml
field as zero, rather than the switch to output the
actual size of the mirror. correct values in XML
(158839) format (unformatted).
Frequency of occurrence: Exists in version:
Always 6.24.0.6.13
Severity:
Low
AIX Navisphere Secure The Navisphere Secure Use Java CLI
CLI CLI client on AIX (navicli.jar) that
incorrectly converts 64-bit correctly reports these
The snapview unsigned integers to a values, or use
-listclonegroup command string format for printing. Navisphere Secure
run from an AIX host reports CLI with the -xml
the SourceLUNSize field as switch to output the
zero, rather than the actual correct values in XML
size of the LUN. format (unformatted).
(158839) Exists in version:
6.24.0.6.13
Always
Severity:
Low
Linux Navisphere Server Utility - The manufacturer field for Use a manual
HAVT HBAs (both Emulex and procedure to
fibre QLogic) is blank determine this
HAVT Checklist: when running on Linux. information.
Manufacturer of HBA is
Exists in version:
missing (Emulex and QLogic
fibre) on a Linux system. 6.24.0.6.12
(158004)
Always
Severity:
Low


or workaround
All Navisphere Server Utility - When the initiator type on Use Navisphere
HAVT a storage system is Secure CLI to check
changed from a type that initiator settings
No error appears if the is valid for a host to manually.
initiator type is changed to another type that is not Exists in version:
something other than fibre valid (for example, from
open. fibre open to an SGI type 6.24.0.6.12
(158023) on a storage system
Frequency of occurrence: attached to a Linux
Always system), the server loses
contact with the storage
Severity:
system altogether. As a
Low result, HAVT no longer is
aware of the existence of
the storage system and
does not even see the
storage system during the
device scan (this would
also be the case with
Navisphere Agent). Since
no information is available
in the scan the initiator
settings cannot be
scanned.


or workaround
All Navisphere Server Utility - HAVT cannot distinguish Manually verify the
HAVT between a dual ported configuration.
HBA and two HBAs. When Exists in version:
No warning is issued about the tool detects two HBAs,
only having a dual ported it will automatically output 6.24.0.6.12
HBA zoned to the storage the message:
system.
(158211) Warning: Two
Frequency of occurrence: Fibre Channel
Always HBAs were
detected in the
Severity: server. This may
Medium not be accurate
if only one
dual-ported HBA
is installed in
the server.
(0x5c42)”
If more than two HBAs are

found, the tool will no
longer display this
message in the report.
When a second
single/dual-ported HBA is
installed into the server,
this message is no longer
displayed. When at least
three HBAs are detected,
then the tool assumes that
there are at least two
HBAs in the server.
Suse 8 Navisphere Server Utility - The server report Use a manual
HAVT generated does not list the procedure to
OS manufacturer name determine this
OS manufacturer and model and model number information.
number are not listed. (distribution and version). Exists in version:
(159138)
6.24.0.6.12
Always
Severity:
Medium


or workaround
Linux Navisphere Server Utility - When running PowerPath Run the iscsi_script.sh
HAVT 4.3.3 on Linux a special noted in the
script needs to be run after PowerPath release
Issues summary gives the installation if the server will notes.
error The version of be connected to an iSCSI Exists in version:
PowerPath storage system. If the
installed does not 6.24.0.6.12
script is not run, the HAVT
support iSCSI
storage systems. will output the message:
This version of
(159139) PowerPath
Frequency of occurrence: doesn't support
Always iSCSI. The message is
Severity: slightly misleading and
should probably read A
Critical required script
was not run when
PowerPath was
installed. This
script is
required to be
run if
connecting to
iSCSI arrays.
All Navisphere Server Utility - HAVT reports show When running with an
HAVT storage systems that are LDAP system, there
physically connected, but must always be a
The HAVT Server Report may not have storage global administrator
should be enhanced to group attachments – or account for the
identify that the check is may not have visibility to domain. This would
physical and that other any LUNs on the given mean that for HAVT
actions may need to be taken storage system. The event uploads the global
before failover software can code listed in the HAVT administrator account
be used to verify HA. reports are not could always be used
Status codes referenced by documented . for upload. Another
HAV should be accompanied option for version
with a document that explains 6.24/LDAP systems
the code or removed from the would be for an
report. alternate global/local
(158468) administrator or
Frequency of occurrence: manager account to be
created for HAVT
Always
uploading.
Severity:
Exists in version:
Low
6.24.0.6.12


or workaround
All Navisphere Server Utility - The HAVT upload feature Use a manual
HAVT of the Navisphere Server procedure to
Utility should be supporting determine this
LDAP scope is not supported the LDAP scope. Currently information. .
by the HAVT feature of HAVT upload only Exists in version:
Navisphere Server Utility. supports local and global
(159378) scope. 6.24.0.6.12
Always
Severity:
Medium
AIX HP-UX Navisphere Host The host agent will Either use the
Linux Agent encounter a memory Windows-based host
Solaris access violation after agent as your central
When a UNIX-based contacting the secondary monitor, which is not
Navisphere Host Agent is storage processor of the affected by this
configured as a central first storage system it memory access
monitor for both storage attempts to monitor, violation, or do not
processors of one or more resulting in process upgrade the host agent
storage systems, the host termination. on your central monitor
agent may terminate shortly workstation to the
after startup (within two versions affected by
minutes). this issue.
(162703) Exists in version:
6.24.0.6.13
Likely under a specific set of
circumstances
Severity:
Critical
All Navisphere Secure CLI After performing a Restart the Navisphere
Navisphere CLI software revert to version Management Server
6.22, the Navisphere and open Navisphere
After performing a software
Management Server is Manager in a new
revert from version 6. 24 to
reporting back-end cabling browser window to
version 6. 22, Navisphere
and bus status that is resolve the issue.
Manager may report back-
inconsistent with the actual Exists in version:
end cabling errors and invalid
state of the storage
back-end bus speed settings. 6.24.0.6.13
system.
(163296)
Likely during a specific event
Severity:
Low


or workaround
All Navisphere CLI Using the Classic Use Navisphere
Classic Navisphere CLI Navisphere CLI (rather Secure CLI to list
output of MirrorView than Navisphere Secure MirrorView information.
information of a pre-version- CLI) to list MirrorView Exists in version:
6.24 storage system can information of a pre-
6.24.0.6.13
result in missing whitespace. version-6.24 stoage
system will result in output
(159017)
that is missing whitespace,
Frequency of occurrence: which could have an effect
Always under a rare set of on customer script
circumstances behavior.
Severity:
Low
All Navisphere CLI The Navisphere CLI None.
backendbus -analyze Exists in version:
The Navisphere CLI command might not 6.24.0.6.13
recognize all cases where
backendbus -analyze
a speed change is
command might not
required.
recognize all cases where a
speed change is required.
(159018)
Rarely under a rare set of
circumstances.
Severity:
Low
Navisphere CLI Occasionally, the navicli Retry the command.
The navicli port -list and port -list and port -list Exists in version:
-initiatorcount return false -initiatorcount commands 6.24.0.6.13
data intermittently return incorrect
information. Objects are
(148199)
not being locked correctly.
Infrequently under a rare set
of circumstances
Severity:
Medium

Problems and limitations for specific platforms

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

None.
HP-UX operating system

None.
Linux operating system

None.
Solaris operating system

None.
VMware operating system

None.
Windows operating systems

None.

Technical notes
Technical notes
This section includes important information that does not appear
anywhere else. This section consists of two major subsections:
The first one describes technical notes that are common to
Navisphere Host Agents, the CLI for all platforms, Server Utility,
and Storage System Initialization Utility.
The second section describes technical notes for platform-specific
Navisphere Host Agents, CLI, Server Utility, and Storage System
Initialization Utility.
Technical notes for all platforms

The information described in the following sections applies to all
platforms that support the Navisphere Agent, CLI, Server Utility, and
Storage System Initialization Utility software.
Host agent
UNIX platforms - HostIDFile.txt file is not removed – On UNIX
platforms, when you uninstall the host agent, the file containing the
host ID (HostIDFile.txt) is not removed because the host ID needs to
be consistent for the life of the host machine (or as long as possible).
Otherwise, the host may have multiple host IDs associated within
the storage system.
Invalid host configurations – A server cannot be connected to a CX
series or CX3 series storage system and an AX series storage system
at the same time.
Device auto-detection – With the exception of JBOD devices, you
can configure the Navisphere Host Agent to automatically detect the
storage systems. To monitor JBOD devices, you need to enter JBOD
device names in the agent.config file.
EMC does not support the simultaneous use of device auto-detection

and specific device entries in the agent.config file.
Lengthy discovery process – To shorten the device discovery

process at agent startup, avoid restarting the host agent while I/O is
occurring on the storage system.

Technical notes
Storage groups and network settings – When using storage groups,

it may not be possible to properly log a host in to the storage system.
These symptoms can be observed under any of the following
circumstances:
• A multi-homed server has two IP addresses and possibly two
hostnames.
• In a cluster, a host may have multiple IP addresses. Typically
one is for the cluster and others are for each individual host in
the cluster.
• Incorrect or incomplete server network settings can also lead to
problems. One possible scenario is incorrect DNS settings.
• 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.
Manually create a file named agentID.txt with the format in the
following example:
hostname
128.221.41.34
Note: The location of this file depends upon the host type and the
existence (or lack thereof) of an environment variable as follows: If
environment variable EV_AGENTID_DIRECTORY is defined and
not of zero length, its value is used. Otherwise, for Windows only, if
the location of the agent configuration file can be found in the
registry (HKEY_LOCAL_MACHINE\SOFTWARE\EMC
\Agent\1.0\ConfigPath), its value will be used. Otherwise,
directory \ is used for Windows, / for UNIX systems, and sys:\ for
NetWare.
The purpose of this file is to tell the host agent what hostname/IP
address to use, so that it matches the one the client uses. The fully
qualified hostname must be on the first line of the file, and the host's
dot-notation IP address must be on the second line. Comments are
allowed in the file on lines following these two lines only. Lines are
visible only if they are properly terminated; adding a blank line after
the first two lines would ensure this. Lines may be empty, in which
case the corresponding value defaults to what it would have been in
the absence of this file.
Enter the IP address that you obtain when you perform a network
name lookup from the client machine. Look for the hostname that
the client will manage. One way to get a host's IP address to enter
into this file is to ping the hostname from the client machine.
Warning: This is a change from Navisphere Host Agent 6.2 and
earlier. The use of agentID.txt on UNIX platforms required that your

Technical notes
current working directory be “/” when manually starting the agent.

Failure to do this resulted in the wrong hostname and/or IP address
being used. Therefore, any assumptions that may have been made
regarding the use of the current working directory are no longer
valid.
Host agent file for CX series, CX3 series and AX series storage systems
Do not enter any device entries for CX series, CX3 series and AX
series storage systems into the host agent configuration file.
None of the other parameters defined in the host agent configuration
file affects CX series, CX3 series and AX series storage systems,
except certain Options Supported directives.
CLI
Secure CLI. The following information describes differences
between Secure CLI, Classic CLI and Java 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. In order to maintain
compatibility and avoid the need to specify the username and
password for each command, user credentials need to be created
using the -AddUserSecurity command in Secure CLI. This will
store the credentials locally on the server in an encrypted file.
Note that the credentials are slightly different than those used
with Java CLI so there is no forward compatibility with a
security file created by Java CLI and the security file required by
Secure CLI.
• Parsing output – Classic CLI displays information only about
the targeted SP; Secure CLI displays information about both SPs.
For example:
• getsp, getall commands – Classic CLI returns N/A for the
serial number of the non-targeted SP; Secure CLI returns the
actual serial number.
• chglun command – Executing chglun on an unbound LUN
returns the string SP A: Unit not bound in Classic CLI,
but will return the string SP A: Unit not bound, SP
B: Unit not bound in Secure CLI.

Technical notes
Certain CLI commands prompt the user with multiple warnings

to confirm. Secure CLI will display a single instance of all the
pertinent warnings and prompt the user with a single
confirmation. This is true of the following commands:
• alpa
• firmware
• networkadmin
• port
• storagegroup
• Managing a system running a version of Navisphere prior to
version 6.19 with Secure CLI does not include Classic CLI
support – Using Secure CLI on a management server running a
version of Navisphere prior to version 6.19 allows you to use
only the commands that Java CLI supports. In order to have both
Classic and Java CLI support, the management server on the
storage system you are attempting to manage must be at version
6.19.
Compatibility mode – MirrorView/Synchronous, SnapView
(snapshot and snapsession-related) and SAN Copy commands are
now performed with NaviSecCLI because the server is now located
in a provider and not within the storage-system agent. To help with
existing scripts that used the CLI MirrorView, SnapView and SAN
Copy command sets, a compatibility mode has been created. This
will seamlessly route existing CLI MirrorView, SnapView and SAN
Copy commands through NaviSecCLI. There is no command line
interaction required by the user for this compatibility mode to be
engaged. It is automatically engaged when talking to a version 6.7
and greater management server for MirrorView or when addressing
a 6.24 or greater management server for SnapView or SAN Copy.
Since Navisphere CLI will be launching NaviSecCLI, you will also
have to configure security on your system and the storage systems
with the new software. You will need to create accounts on your
storage systems using the UI or NaviSecCLI, To establish the local
security file you must run the following command:
Naviseccli –user <username of array accounts> –password<password
of array accounts> -scope 0 (for global) | –scope 1 (for local) -
addusersecurity.
This creates an encrypted file on your host system with your
username, the password, and scope to be sent to the storage systems
during the execution of naviseccli. The commands that will invoke
naviseccli are mirrorview, snapview (except clone-related
commands), sancopy, getall, and setfeature –feature rm (where rm

Technical notes
stands for remote mirror). The getall command has been modified to
display SnapView, SAN Copy and MirrorView information when
launched from naviseccli. The observable behavior of mirrorview
and setfeature should not change despite the hidden differences, but
getlun, which does not even launch naviseccli, will be altered. For
getlun the change occurs only when addressing a storage system
that supports the aforementioned software, and is at the line starting,
MirrorView Name if any:. Instead of a value of either a name or
Not Mirrored, it will display Unavailable.
NOTE: EMC recommends that you use NaviSecCLI for all commands.
navicli -d command for CX series, CX3 series, and AX series

storage systems – When addressing a CX series, CX3 series, and AX
series SP agent with the navicli command, you do not need to
specify a device entry (-d <device name>) in the navicli command
line. Most CLI commands require a device entry (-d <device name>)
on the command line in order to direct the management request to
the appropriate storage-system device. Because the CX series, CX3
series, and AX series 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.
Using the CLI to configure and manage remote mirrors – Since the
CLI communicates with the CX series, CX3 series, 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.
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, lun number would return as
a signed integer; a boolean as a Boolean). A -1 will signify
undefined, not available, or not applicable. Previously the same
information was returned as strings. This affects output data types
only when using the XML switch.

Technical notes
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 be either
that the command was issued with invalid security credentials
(username, password, scope) or the command was issued without
the required level of authorization (correct role) to perform the
operation. [113871]
Scripting CLI – Navisphere uses several internal databases to
represent the state of the storage system, and updates their status
through regular polls to the system software. It is possible that some
automated CLI commands will 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. [116509]
Error codes returned by Classic CLI – The following table contains
all error codes that are returned by Classic CLI:
Navisphere CLI error codes
Error Description
value
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.

Technical notes
Error Description
value
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.
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.
41 Command is not supported.
42 Unknown error
50 Agent - Memory allocation error.
51 Agent - Invalid device name.

Technical notes
Error Description
value
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.
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 runremoverg again.
80 Zerodisk command failed.

Technical notes
Error Description
value
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.
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
identifer(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.

Technical notes
Error Description
value
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.
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.
nondisruptive 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.

Technical notes
Error Description
value
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.
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.

Technical notes
Error Description
value
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.
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.

Technical notes
Error Description
value
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.
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.

Technical notes
Error Description
value
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 a
Storage Group.
235 Cannot display LUN WWNs and update LUN map
information at the same
time.
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: -connecto 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.

Technical notes
Error Description
value
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 a Storage Group.
289 Chglun parameter not supported on a non-Flare LUN.
290 Unable to bind the metaLUN, use CLE command
metalun –destroy instead.
getsniffer or setsniffer on metaLUNs.
292 You must issue this command from the SP that owns
the LUN on which the verfiy will be run.
293 Cannot specify both -feature and -featurename.
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

Technical notes
Error Description
value
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
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 removedHBA 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

Technical notes
Error Description
value
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
392 RAID reset and hold command
393 Invalid parity elements hold value
394 Invalid disk FW
395 Snapcopy globalcache not commited
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

Technical notes
Error codes returned by Secure CLI – The following table contains

all error codes that are returned by Secure CLI:
NaviSECCLI Error Codes
Error value Description
(hexadecimal)
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.

Technical notes

(hexadecimal)
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 Directroy 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.

Technical notes

(hexadecimal)
0x4402 Invalid agent configuration.
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.

Technical notes

(hexadecimal)
0x4818 Archive unavailable.
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 anabled.
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 occured
0x4D43 Clone feature object is not available
0x4D44 Clone enabling software is not installed
0x4D45 Specified CloneGroup is not available.

Technical notes

(hexadecimal)
0x4D46 Specified Clone is not available.
0x4D47 No available LUs for cloning on the system.
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 recovry 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.

Technical notes

(hexadecimal)
NQM error codes
0x4D90 NPO feature object is not available
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 Invaild NPO subcommand
0x4D97 Invaild NPO command line switches
0x4D98 Invaild NPO command line switch value.
0x4D99 LUNs have to be specified by WWNs or LUN numbers
0x4D9A Too few parameters
0x4D9B Too many parameters
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.

Technical notes

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

Technical notes

(hexadecimal)
0x51e0 Fail converge.
0x51e1 Goal attained.
0x51e2 Converge then fall.
0x51e3 Disable fallback.
0x51e4 Suspend event.
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

Technical notes

(hexadecimal)
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
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.
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 supprted.
MirrorView consistency group error codes
0x5340 The maximum number of groups is already defined.

Technical notes

(hexadecimal)
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.
0x520f Feature not located.

Technical notes

(hexadecimal)
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.
0x5231 Add Server PSM failure.

Technical notes

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

Technical notes

(hexadecimal)
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.
0x6511 Single task limit.
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.

Technical notes

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

Technical notes

(hexadecimal)
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.
0x6310 Invalid protocol type.
0x6311 Invalid server type.
0x6312 Invalid IP address.
0x6313 Invalid role.
0x6314 Zipping configuration files.
0x6315 Propogating 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.

Technical notes

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

Technical notes
Server utility
HAVT supported platforms. The HAVT tool is available on the
following host platforms:
• HP-UX (11.0, 11.11, 11.23 IA 64, 11.23 PA RISC)
• Solaris 8, 9
• Microsoft Windows 2000, 2003
• AIX 5.1, 5.2, 5.3
• Linux RedHat Enterprise Versions 3 and 4
• SuSE Enterprise Server Versions 8 and 9
• AsianUX Version 2.
And the following storage system configurations:
• Supported storage system SW versions:Version 6.7 - current
• Navisphere versions: Version 6.7 - current
• CLARiiON models - CX series/AX series
ISCSI support
• Platform support:
Microsoft Windows 2000, 2003
Redhat Enterprise (RHEL) 3 and 4
SuSE Enterprise (SLES) 8 and 9
AsianUX (2.0)
• Storage-system support:
Any CX or AX that supports iSCSI
• iSCSI HBA support:
QLogic 4010 HBA for both Linux and Windows with iSCSI.
HAVT report files. Files uploaded to the storage system may be
retrieved using the Navisphere CLI and Secure CLI managefiles
command.
HAVT report file size. 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.
HAVT QLogic iSCSI HBA information. In order for QLogic iSCSI
HBA information to be gathered in the report, the QLogic iSCSI CLI
must be installed.
HAVT tabbed format reports. If the reports do not appear in tabbed
format, check your browser for either an information bar or dialog
box for Active Content Blocked. Click it and then Enable Blocked
Content.

Technical notes
If you do not see such a box, make sure Javascript is enabled. On

most modern browsers Javascript is turned on by default and no
settings will need to be changed to view the reports. If Javascript is
not enabled, you will see the whole file as a simple HTML page. To
view the tabbed format reports, you will have to then enable
Javascript.
To enable Javascript in IE:
1. Go to the Tools menu and select Internet Options.
2. In the Internet Options window, 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 for this 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 the Enable Javascript option to turn Javascript on.
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.

Technical notes
AIX - Host agent

Installing the agent. On AIX 5.1 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
Stopping the agent. 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>
Initialization tool no longer distributed. The AIX Array
Initialization Tool is no longer distributed.
Instal script. The instal script for NAVIAGENT and NAVICLI was
modified to use executables from the /usr/sbin directory instead of
from /etc. This eliminated the need for the bos.compat.links package
that linked executables from /etc to /usr/sbin.
Installation from CD. When you attempt to install the Navisphere
host software, 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.

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 /dev/dsk/device_filename /cdrom
where device_filename is the device filename from step 3. For
example, mount /dev/dsk/c1t2d0 /cdrom
4. Navigate to the HP-UX directory:
cd /cdrom/hpux
5. Run the Navisphere Initialization Utility:
./naviinittool
Linux – Host agent

IA-64/Itanium Red Hat Linux 3.0 installation. Before attempting to
install Navisphere Agent on IA-64 machines make sure that you
have installed Compatibility Arch Support packages. Failure to do so
will result in Navisphere Agent installation aborting with errors
about missing dependency libraries.
IA-64 Red Hat Enterprise Linux 4.0 installation. If you get errors
while trying to install Navisphere packages, 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:
http://www.redhat.com/docs/manuals/enterprise/RHEL-
4-Manual/release-notes/as-itanium/

Technical notes
Red Hat Enterprise Linux 4 for the 64-bit Intel Itanium2 architecture
includes runtime support for 32-bit applications through the use of
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. The IA-32 Execution Layer and 32-bit compatibility packages
together 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. 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.
4. 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.
5. Select all of the packages, or the particular packages required in
order to provide runtime support for your 32-bit applications.
6. 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. To verify that the 32-bit
compatibility mode is in effect, type the following in a shell
prompt:
service ia32el status
Naviagent start/stop script location. The location of the Navisphere
Agent stop/start script changed. For all versions of Linux, the script
can be found at /etc/init.d/naviagent.

Technical notes
Registration failures (not enough devices). The number of sg

devices installed on both Red Hat and SuSE systems by default (16
entries) is not enough in many cases and as a result some of the
paths may not be registered. The solution would be to create an
adequate number of these sg entries. The following script (or its
equivalent) may be used by the system administrator 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
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

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/cxseries/solaris
3. Run the Navisphere Initialization Utility.
./naviinittool
Solaris - Utilities
Running utilities from 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 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 series, CX3
series and AX series storage systems. The auto-detect feature of the
remote agent configurator does not detect CX series, CX3 series and
AX series storage systems.
Backup of Navisphere Event Monitor Navimon.cfg file – For
customers who use Navisphere Event Monitor and are upgrading to
6.24 from a pre-6.5 version of Navisphere, you must back up the
<install drive:>\Program Files\EMC\Navisphere
Agent\Navimon.cfg file before uninstalling that version of
Navisphere Agent. If you do not back up this file, you may lose any
existing Navisphere Event Monitor configuration.
Once the 6.24 Navisphere Agent has been installed, you can stop it,
copy the Navimon.cfg back to its original location, and then restart
the Navisphere Agent.

Technical notes
Windows – CLI
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.
[116814]
If you manually registered an iSCSI initiator and then restarted the host
agent, you may experience these connection problems due to use of
capital letters in hostnames. If you have capital letters in the hostname,
perform the following steps (in the order specified) 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.
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.
Clusters
EMC recommends that you place all shared disks (LUNs), including the
quorum disk, into the same storage group.
VMware
• ESX 2.5.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 greater, of the FLARE
Operating Environment.
• ESX 3.5.0, which has the Service Console, will work the same way as
ESX 3.0.x.
• ESX 3i has no Service Console to install or run the host agent or
server utility. Registration of the CLARiiON storage system will
happen automatically when the ESX 3i server reboots or when you
rescan the EXC 3i server host bus adapters. Manual registration is
not necessary. However, the ESX 3i server that appears in
Navisphere Manager will not have an OS name, OS revision
information, or device mapping information.

Technical notes
VMware – CLI
The CLI is supported in the Service Console on ESX 2.5.x, ESX 3.0.x and
ESX 3.5.0.
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 not supported for ESX 2.1. Only manual registration is
supported. ESX 2.5 and later (except for ESX 3i) contains host agent
support on the ESX Service Console. Do NOT run the host agent from a
Virtual Machine.
VMware – Server utility

ESX 2.5 and later (except for ESX 3i) contains server utility support on
the ESX Service Console. Do NOT run the server utility from a Virtual
Machine.
VMware – Storage system initialization utility

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

Documentation
Documentation
The following documents apply to this product version:
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-004-281 EMC CLARiiON Server Support Products for VMware ESX Server
Installation Guide
300-002-039 EMC CLARiiON Server Support Products for Solaris Installation Guide
300-002-038 EMC CLARiiON Server Support Products for Windows Installation
Guide
069001166 EMC Installation Roadmap for CX3 series, CX series, AX series, and
FC series 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.
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 CLI
The Navisphere CLI can run on servers or remote management stations that
are attached to CLARiiON storage systems.

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-001-826 EMC CX3-Series Core Server Support CD-ROM
EMC Documentation and Resources for CX3 UltraScale Series and CX-Series
053-001-830
Storage Systems CD-ROM
053-001-587 NetWare and IRIX Server Support CD-ROM
Installation
For installation instructions, refer to the documents listed in the
“Documentation” section.

Troubleshooting and getting help
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 EMC WebSupport on Powerlink. To open a
case on EMC WebSupport, you must be a WebSupport customer.
Information about your site configuration and the circumstances under
which the problem occurred is required.

Copyright and license information
Copyright and license information

Copyright © 2006-2008 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.
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.

300-004-292 A06 Elccnt 0

Uploaded by

Copyright:

Available Formats

You might also like

300-004-292 A06 Elccnt 0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

300-004-292 A06 Elccnt 0

Uploaded by

Copyright:

Available Formats

EMC Navisphere

Host Agent/CLI and Utilities

These release notes include supplemental information about the EMC®

2 EMC Navisphere Host Agent/CLI and Utilities Release Notes

EMC Navisphere Host Agent/CLI and Utilities Release Notes 3

New features and changes

New features at initial 6.24 version

4 EMC Navisphere Host Agent/CLI and Utilities Release Notes

to apply the template to both storage processors for complete

Changes to the 6.24 version from previous versions

Future enhancements and modifications

EMC Navisphere Host Agent/CLI and Utilities Release Notes 5

Environment and system requirements

Not all operating systems support PowerPath® software.

Operating Minimum hardware requirements Minimum software requirements

6 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Operating Minimum hardware requirements Minimum software requirements

Note: In addition to the software revisions listed above, the operating

EMC Navisphere Host Agent/CLI and Utilities Release Notes 7

 Hewlett-Packard HP-UX 11.0 and 11i

Navisphere management software requirements

8 EMC Navisphere Host Agent/CLI and Utilities Release Notes

EMC Navisphere Host Agent/CLI and Utilities Release Notes 9

Problems fixed in update 6.24.3 (FLARE versions 02.24.*.5.017 and

10 EMC Navisphere Host Agent/CLI and Utilities Release Notes

EMC Navisphere Host Agent/CLI and Utilities Release Notes 11

12 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Problems fixed in update 6.24.2 (FLARE versions 02.24.*.5.014 and

EMC Navisphere Host Agent/CLI and Utilities Release Notes 13

14 EMC Navisphere Host Agent/CLI and Utilities Release Notes

EMC Navisphere Host Agent/CLI and Utilities Release Notes 15

Problems fixed in update 6.24.1

16 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Platforms Symptom details Problem description Solution description

EMC Navisphere Host Agent/CLI and Utilities Release Notes 17

Platforms Symptom details Problem description Solution description

18 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Problems fixed in update 6.24.0

EMC Navisphere Host Agent/CLI and Utilities Release Notes 19

Known problems and limitations

Problems and limitations common to all platforms

20 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Platforms Symptom details Problem description Prevention/resolution

EMC Navisphere Host Agent/CLI and Utilities Release Notes 21

Platforms Symptom details Problem description Prevention/resolution

22 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Platforms Symptom details Problem description Prevention/resolution

EMC Navisphere Host Agent/CLI and Utilities Release Notes 23

Platforms Symptom details Problem description Prevention/resolution

24 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Platforms Symptom details Problem description Prevention/resolution

EMC Navisphere Host Agent/CLI and Utilities Release Notes 25

Platforms Symptom details Problem description Prevention/resolution

26 EMC Navisphere Host Agent/CLI and Utilities Release Notes

Platforms Symptom details Problem description Prevention/resolution

• Initiator type is not set

• HP-UX will always

EMC Navisphere Host Agent/CLI and Utilities Release Notes 27

Hewlett-Packard HP-UX 11.0 and 11i

Lengthy discovery process – To shorten the device discovery

Storage groups and network settings – When using storage groups,

navicli -d command for CX series, CX3 series, and AX series

Unsupported security encryption key error – When upgrading from

Error codes returned by Secure CLI – The following table contains