Unit Shutdown for Tresspass > Please explain error?

Is there other events around this one ? Trespass is sometime really normal, like when you extend a metalun.

A LUN has trespassed from one storage processor to another. If you see a lot of these and very often ..time to investigate why LUN(s) are bouncing back and forth. If LUNs are trespassing very often ..like every second or so..you will see very poor performance on the host.

which is the OS and fail over s/w used?

When a host HBA failover software detects that the path to a LUN is not present, it will issue a command to the array to move (trespass) the LUN to the peer SP in order to establish connection with the LUN. The array will log this activity in the Event Log.

If there is a misconfiguration of the failover software you can get into a condition called "trespass storm" - this happens when the host starts trespassing the LUN back and forth between SP's. This occurs most with Veritas DMP (the messages in the Event log will not say "trespass" but will say "Background Verify Started" followed by "Background Verify Aborted" in quick succession). If you see these messages filling the Event Log, you need to shut down the host that's causing this. This is sometimes difficult to determine as the messages in the log refer to a disk in the Raid Group that contains the LUN that is trespassing.

The other OS/failover software combination that can cause a trespass storm is HP-UX/PVlinks. There you will see the messages in the Event Log as "trespass" messages.

You can find additional information by going to KnownledgeBase and doing a search on "trespass"

Also, be sure to see the new CLARiiON Home page on PowerLink:

Home > Support > By product > CLARiiON CX3 UltraScale Series

regards,

glen