The problem is that LUNs could have trespassed and be on a different SP than the one that you built the script for - this is just an informational message letting you know that the SP you issued the command to no longer owns the LUN, but it will send the command to the owning SP. Not a real problem and by design.  glen
Before working on my servers, I create a snapview session. If everything has gone well, I stop the session. Note that I do not create a snapshot, unless I have a need to mount a lun on another host.  Upon clicking "Stop Session" I have been getting the following alerts:   There is no description of what device "Disk0001" is, unless it is Bus 0, Enc 0, Disk 01.  The explanation offered by Primus emc116651 states:  "Failed starting session for LUSP A: This command was sent to the SP that does not own the LUN (0x71008043)"  The following log entries show that I had no errors on two of the four luns in the session. These two were on one SP but the other two luns were on the other SP.  14.  Date:05/21/2010  Time:11:40:51 AM  Event Code:0x71000004  Description:SnapView session physics0_xivmigration has been stopped on LUN 666 with status of 0.  13.  Date:05/21/2010  Time:11:40:51 AM  Event Code:0x71000004  Description:SnapView session physics0_xivmigration has been stopped on LUN 668 with status of 0.  12.  Date:05/21/2010  Time:11:40:52 AM  Event Code:0x71008043  Description:Disk0003 is not active on this SP.  11.  Date:05/21/2010  Time:11:40:52 AM  Event Code:0x71000007  Description:SnapView has been unbound from device Disk0003.  10.  Date:05/21/2010  Time:11:40:52 AM  Event Code:0x71008043  Description:Failing Command: Set LUN.  9.  Date:05/21/2010  Time:11:40:53 AM  Event Code:0x71008043  Description:Disk0001 is not active on this SP.  8.  Date:05/21/2010  Time:11:40:53 AM  Event Code:0x71000007  Description:SnapView has been unbound from device Disk0001.  7.  Date:05/21/2010  Time:11:40:53 AM  Event Code:0x71008043  Description:Failing Command: Set LUN.  6.  Date:05/21/2010  Time:11:40:54 AM  Event Code:0x4600  Description:'Stop' called by ' Navi User   My theory is:  When I click "Stop Session" it sends the command to a specific SP. If a lun or luns, in the reserved lun pool, assigned to my session, belongs to the SP other than the one my command went to, the result will be "Event Number 71008043".  Am I correct?  Thanks, Rob
Event Number 71008043 when a Snap Session is Stopped