A quick way to determine whether LUNs are trespassed using Navisphere or CLI

Advertisements

Description :-

The solution shows how to quickly identify whether LUNs have trespassed on a
CLARiiON array. For NS Gateway arrays that use Access Logix and
Storage Groups, an additional command needs to be run to verify whether
a particular LUN belongs to the Celerra.

Solution :-

To implement the changes that you made to the cifsmsg.txt file, restart (stop and start) the CIFS service on the Data Mover () by using this command syntax:

$ server_setup server_ -P cifs -o stop
$ server_setup server_ -P cifs -o start

Storage System : Check control lun ownership
Error HC_BE_1450559: Control LUNs: 0 has trespassed
Action : Run the following commands to trespass it back

Action : Run the following commands to trespass it back
* /nas/bin/nas_storage -failback id=1
* Then, to verify its success, run:
* /nas/bin/nas_storage -c -a
* If this fails, refer to EMC Knowledgebase emc123343 and escalate
this issue through your support organization. Provide this output in
the escalation.
* If it succeeds, run:
* /nas/bin/server_devconfig ALL -c -s -a

Storage System : Check control lun ownership
Error HC_BE_147459: Control LUNs: 0 has trespassed
Action : Run the following commands to trespass it back
* /nas/bin/nas_storage -failback id=1
* Then, to verify its success, run:
* /nas/bin/nas_storage -c -a
* If this fails, refer to EMC Knowledgebase emc123343 and escalate
this issue through your support organization. Provide this output in
the escalation.
* If it succeeds, run:
* /nas/bin/server_devconfig ALL -c -s -a

Command to resolve the issue :-

[nasadmin@NAS01 ~]$ /nas/bin/nas_storage -failback id=1
id = 1
serial_number = SL7F91109
name = SL7F9110900
acl = 0
done

[nasadmin@NAS01 ~]$ /nas/bin/nas_storage -c -a
Discovering storage (may take several minutes)
done

Issue is resolved.

Additional

Using Navicli to see trespassed LUNs.
For NS Integrated models where the CLARiiON array is dedicated
solely for Celerra hosts, the following command shows all trespassed,
Celerra related LUNs:

[nasadmin@NAS01 ~]$ /nas/sbin/navicli -h <IP address>

getlun -trespass -status  (Output shows ALU–Array LUN Numbers)
LOGICAL UNIT NUMBER 84
Default Owner:              SP B
Current owner:              SP A
Device Map:                 Valid
LOGICAL UNIT NUMBER 5
Default Owner:              SP A
Current owner:              SP B
Device Map:                 Valid
One additional command is needed for NS Gateway models where
multiple host types can be connected to the CLARiiON array and where
storage groups are used to control Host-access to LUNs.  Examine the storage group -list
command output to see which Storage Group applies to the Celerra
and which LUNs are owned by the Celerra.  In the following example, ALU
LUNs 5 and 92 are Celerra LUNs in a trespassed state as seen in the
above trespass status output.

Using Navisphere to see trespassed LUNs
Open the Navisphere GUI Interface>Tools>Trespassed LUNs Status
Note:  Wait for 15 seconds or more to allow time for the list to build.

Also see EMC VNXe Storage installation

DELLEMC VNX call home configuration

Leave a Reply