The LUNS are usually tress passed by the Host side Activity. From the Clariion the LUNS would go tress pass only when there is issue with the SP side.
The Tress passing back the LUNS is easy process. right Click on the LUN and then Tress pass. Once you do this you should be able to see the current SP owner on the properties TAB of the LUN.
In the Event Log on the SPA or SPB you should be able to see the mesasge "trespass" - this will have a disk listed - from the disk you can discover which riad group the disk is assigned to. This will tell you when the trespass occurred.
In restoring LUNs to the default SP owner, you should use the host based failover application - if using PowerPath you can issue the "powermt restore -all"
Governor2
31 Posts
0
September 24th, 2010 02:00
Hi,
The LUNS are usually tress passed by the Host side Activity. From the Clariion the LUNS would go tress pass only when there is issue with the SP side.
The Tress passing back the LUNS is easy process. right Click on the LUN and then Tress pass. Once you do this you should be able to see the current SP owner on the properties TAB of the LUN.
dynamox
9 Legend
•
20.4K Posts
0
September 24th, 2010 04:00
if you are running PowerPath, "powermt restore" relocates LUNs back to their default owners.
kelleg
4 Operator
•
4.5K Posts
0
September 24th, 2010 13:00
In the Event Log on the SPA or SPB you should be able to see the mesasge "trespass" - this will have a disk listed - from the disk you can discover which riad group the disk is assigned to. This will tell you when the trespass occurred.
In restoring LUNs to the default SP owner, you should use the host based failover application - if using PowerPath you can issue the "powermt restore -all"
glen
SKT2
2 Intern
•
1.3K Posts
0
September 26th, 2010 18:00
even if the LUNs got tresspassed, the logs will still report at the physical "disk" level; is that you meant?