Run naviseccli -h <sp_ipaddress> getagent.

This should return with information on device names

and configurations of the storage system.

Run naviseccli -h <sp_ipaddress> getcache. This should return with information about SP's
caching. Ensure Read and Write Cache is Enabled.

Run naviseccli -h <sp_ipaddress> getcrus. This should return with information about CRU's
(Customer Replaceable Units) & FRU's (Field Replaceable Units).

Run naviseccli -h <sp_ipaddress> faults -list. This should return with a summary of faults on the
array

Run naviseccli -h <sp_ipaddress> getall sp. It displays information about this storage processor
(SP) only.

Run naviseccli -h <sp_ipaddress> getall hba OR naviseccli -h <sp_ipaddress> port -list to

displays information about each switch, HBA and port.

Run naviseccli -h <sp_ipaddress> connection -getport -all. This should return with information
about iSCSI Configuration

Run naviseccli -h <sp_ipaddress> getlun rc wc to ensure that LUN Read and Write Cache are
enabled.

Run naviseccli -h <sp_ipaddress> getdisk -state to ensure that Disk Status is Enabled.

Run naviseccli -h <SP_IP_address> spcollect to start the SPCollect script.

Additional security information may also need to be specified (see 39860). Wait at least 10
minutes for the SPCollects to run, before attempting to retrieve them.

Run naviseccli -h <SP_IP_address> managefiles -list to list the files created by SPCollect.

Run naviseccli -h <SP_IP_address> managefiles -retrieve to allow you to pick the SPCollect that
you want to retrieve. Look at the date/time in the name of the SPCollect for the most recently
created to retrieve.

Impact Why does 'navicli getlun -at' command respond 'AutoTrespass=DISABLED'?

Why isn't auto-trespass in LUN Properties?

Issue navicli -h <host_name> getlun <LUN_number> -at responds "AutoTrespass=

 DISABLED" when the hosts accessing the LUN have the initiator settings set
to "HPAutoTresspass" enabled.

Environment Product: CLARiiON CX Series

EMC SW: Navisphere Agent/CLI
OS: HP-UX

Change HP-UX hosts with PVlinks are attached and the initiator type is set to
"HPAutoTrespass"' for the hosts. The site also has VMware hosts with the
initiator type set to "CLARiiON Open."

Resolution The HP-UX hosts use PVLinks as failover software. Therefore, PVLinks
controls all the paths and actions related to auto-trespass (-at). It is PVLinks
(not the CLARiiON array or its software) that decides whether auto-trespass
should be disabled or enabled. If needed, PVLinks will automatically set it to
"Enabled."
LUN Properties does not display auto-trespass because you cannot set it from
Navisphere.

Issue CLARiiON CX600 storage processor enclosure (SPE) fault light is on but there
are no faults.
Fault light on the SPE is always on even when there is no fault.
Navisphere Manager shows enclosure SPE is faulted.
Selecting Navisphere Manager Operations -> Tools-> Faults shows that the SPE
enclosure is faulted but if you drill down everything is functioning normally.
Resume PROM read failed messages with an extended status of 0x000x05
Navisphere Manager 6.x displays "UNINITIALIZED" for the serial number.

Environment Product: CLARiiON CX Series

Product: CLARiiON CX3 Series
Product: CLARiiON CX4 Series
EMC SW: Navisphere Manager 6.x

Cause If you see a fault light on the enclosure without any obvious faults, it might
 indicate that the resume PROMs have experienced checksum errors. Check the
Navisphere CLI event logs or FCLI ulogs for any resume PROM read failed
messages with an extended status of 0x000x05 where 5 indicates a checksum error
and x indicates the type of resume PROM. Checksum errors indicate that the
resume PROMs were not programmed correctly.
Additional information:
The date of manufacture of the CX-Series array indicates the likelihood of the
array experiencing this problem. An array shipped before May 24, 2002 will
definitely see the problem. Arrays that were shipped after May 24, 2002 might also
exhibit this behavior because they might have been shipped with old SP boards
that were not programmed correctly.
In the later revisions of array (CX3 Series, CX4 Series), checksum error may
happen under one of two conditions:
a. The array may experience checksum error on SP resume or on SP power supply
resume if it there was a replacement of those FRUs and so array tried to update
those resumes. If that update failed (SMBus was busy or there was a panic or just
reboot during resume write), then this can cause resume checksum error.

b. This solution was applied incorrectly. An error occurred during a write or one or
more resume PROMS as FLARE attempted to perform an update to all PROMS.
Because of this, it is extremely important to be careful applying this solution.
In a storage system running Release 26 or 28 applying this solution will cause a
panic on SP. Therefore, the customer must be informed about this. After the panic,
resume to which we were writing will be readable. We might need the second
reboot (no panic at this case) in order to have fault light on enclosure to go off.
EMC Engineering strongly advises against running the gp -clear all command
because this command run a storage system running Release 26 or 28 will cause
checksum errors on multiple resumes because of the panic during the resume
update.

Resolution Contact the EMC Customer Support Center or your support provider for technical
assistance. Please quote the solution ID (emc54012). The service procedure
requires logging on to the SP, which can only be performed by your support
provider.