Hosts initiate LUN trespasses, not the array. You can look in the Event Log and there should be trespass messages - this should provide you with a disk number - 2-3-6 for example. From the number this will tell you the raid group that the LUN is in.  If you open a case with EMC and supply spcollects we can determine which LUNs are trespassing.  glen
hello how many tresspass triggers the alarm, and where to detect the root cause of excessive trespasses, i have vCenter 4.1with many esx 4.1, with 2 fc fiberchannel each one, fabric with dual fc switches, zoning configured, alua mode 4, flare 04.29.000.5.006, NMP with path selection policy set to : FIXED in all luns  the clarrion events is  71164000 Severity Warning Host B-IMAGE Storage Array CKMXXXXXXX SP N/A Device N/A Description Excessive trespasses detected. Lun:  any idea.
what and who triggers trespass - cx4 with esx 4.1 reports Excessive trespasses 
71164000