EMC storage serial number CK200114700647 disk error LUN tresspass very frequent why?

1. First run the command to find out the trespassed LUNs.

$ /nas/sbin/navicli -h getlun -default -owner   

2. If the trespassed LUNs are non-Celerra LUNs owned by the CLARiiON and not the Celerra, gather SP Collects and engage CLARiiON Support for review.

3. If they are Celerra LUNs, it could be caused by device/path configuration. Follow the next steps to verify it.

4. Run this command to show which chains see any disks. This command is independent of SP ownership of a LUN:

ns704cws1 nasadmin]$ server_devconfig ALL -p -s -d " grep -v devices "  grep -v tid
server_2 :
chain= 0, scsi-0
  stor_id= APM00044700202  Celerra_id= APM000447002020000 <-------Celerra_id is the serial number. This chain is connected to the CLARiiON. This is important when working with environments with multiple backends.

  chain= 16, scsi-16
   stor_id= APM00044700202  Celerra_id= APM000447002020000
chain= 32, scsi-32
   stor_id= APM00044700202  Celerra_id= APM000447002020000
chain= 48, scsi-48
   stor_id= APM00044700202  Celerra_id= APM000447002020000

--------- output truncated to only show one Data Mover server_2 -----------------------

5. Check the Data Mover Host Bus Adapters (HBA) to see the associations among chains, HBAs and SP ports.  Any differences between the chains from the server_devconfig -probe output and the chains that are displayed from the fcp bind show output should be noted:

[nasadmin@ns704cws1 server]$ .server_config ALL -v "fcp bind show"
server_2 : commands processed: 1
command(s) succeeded
output is complete

*** Persistent Binding Table ***
Chain 0000: WWN 5006016030601377 HBA 0   SP-a0 Bound      < ---- chain 0 is connected to SPA port 0 using HBA0 on the Data Mover server_2
Chain 0016: WWN 5006016830601377 HBA 0   SP-b0 Bound
Chain 0032: WWN 5006016130601377 HBA 1   SP-a1 Bound
Chain 0048: WWN 5006016930601377 HBA 1   SP-b1 Bound
Chain 0064: WWN 5006048000000000 HBA 2  N_PORT Bind Pending
Chain 0080: WWN 5006048000000000 HBA 3  N_PORT Bind Pending
Existing CRC: 481e0b22, Actual: 481e0b22, CRC Matchs
***   Dynamic  Binding Table ***
Chain 0000: WWN 5006016030601377 HBA 0 ID 0 Inx 00:00 Pid 0000 S_ID 622b13 Sys
Chain 0016: WWN 5006016830601377 HBA 0 ID 0 Inx 01:01 Pid 0016 S_ID 622713 Non
Chain 0032: WWN 5006016130601377 HBA 1 ID 1 Inx 02:00 Pid 0032 S_ID 632b13 Sys
Chain 0048: WWN 5006016930601377 HBA 1 ID 1 Inx 03:01 Pid 0048 S_ID 632713 Non
Chain 0064: WWN 0000000000000000 HBA 2 ID 2 Inx 04:81 Pid 0064 S_ID 000000 Non
Chain 0080: WWN 0000000000000000 HBA 3 ID 3 Inx 05:81 Pid 0080 S_ID 000000 Non
FCP Base Chain: 0  Dump Slot: 2  Dump Chain: 0 16 32 48
Adapter Chain Offset 0:0 1:32 2:64 3:80  dumpInit 1
1134051748: ADMIN: 4: Command succeeded:  fcp bind show

--------- output truncated to only show one Data Mover server_2 -------------------------

6. By now we have checked all the paths, and we also need to correct the /nas/server/slot_2/camdisk which all the device/path configuration is resident on Celerra.

7. Check the camdisk configuration for each Data Mover:

cat /nas/server/slot_2/camdisk
1:c0t0l0+5 02160000000000NI+,c32t0l0+5 02160000000000NI+:
2:c0t0l1+5 02160100010001NI+,c32t0l1+5 02160100010001NI+:
3:c0t0l2+5 02160200020002NI+,c32t0l2+5 02160200020002NI+:
4:c0t0l3+5 02160300030003NI+,c32t0l3+5 02160300030003NI+:
5:c0t0l4+5 02160400040004NI+,c32t0l4+5 02160400040004NI+:
6:c0t0l5+5 02160500050005NI+,c32t0l5+5 02160500050005NI+:
7:c0t1l0+5 02161000100010NI+,c32t1l0+5 02161000100010NI+:
8:c0t1l1+5 02161100110011NI+,c32t1l1+5 02161100110011NI+:

8. Run the command to rescan the device and update the camdisk.

server_devconfig -c -s -a

9. Once the camdisk is corrected, you need to trespassed the LUNs back to their owner.