Native ALUA DSM - Windows Server 2008

Folks,
We are trying to work our array work with the Windows Native DSM. We are an
Active Standby array, and it seems to come up and work and failover fine.

We have an error condition where we want the DSM to issue a failover Set
Target Port Groups command. We are reporting the Unavailable state for the
volume as per SPC, and returning Check condition, not ready, LU not
accessible, Target port in Unavailable State as per SPC for IOs. But that
does not seem to make the DSM issue a failover command.

My question is:
What are the requirements from the DSM perspective from a storage array when
the storage array wants to trigger the DSM to issue a failover command for
the Windows Native ALUA DSM?

I am seeing the same behavior with our TPG storage processor.
Have you made any preogress in determining the cause?

On Jul 17, 10:03*pm, LaGeek <LaG...@discussions.microsoft.com> wrote:[color=blue]
> Folks,
> We are trying to work our array work with the Windows Native DSM. We are an
> Active Standby array, and it seems to come up and work and failover fine.
>
> We have an error condition where we want the DSM to issue a failover Set
> Target Port Groups command. We are reporting the Unavailable state for the
> volume as per SPC, and returning Check condition, not ready, LU not
> accessible, Target port in Unavailable State as per SPC for IOs. But that
> does not seem to make the DSM issue a failover command.
>
> My question is:
> What are the requirements from the DSM perspective from a storage array when
> the storage array wants to trigger the DSM to issue a failover command for
> the Windows Native ALUA DSM?[/color]

No we havent. I am not even sure how to get in touch with someone in the ALUA
DSM team. It surprised me that this did not work, because it seems pretty
basic...

"Ed I" wrote:
[color=blue]
> I am seeing the same behavior with our TPG storage processor.
> Have you made any preogress in determining the cause?
>
> On Jul 17, 10:03 pm, LaGeek <LaG...@discussions.microsoft.com> wrote:[color=green]
> > Folks,
> > We are trying to work our array work with the Windows Native DSM. We are an
> > Active Standby array, and it seems to come up and work and failover fine.
> >
> > We have an error condition where we want the DSM to issue a failover Set
> > Target Port Groups command. We are reporting the Unavailable state for the
> > volume as per SPC, and returning Check condition, not ready, LU not
> > accessible, Target port in Unavailable State as per SPC for IOs. But that
> > does not seem to make the DSM issue a failover command.
> >
> > My question is:
> > What are the requirements from the DSM perspective from a storage array when
> > the storage array wants to trigger the DSM to issue a failover command for
> > the Windows Native ALUA DSM?[/color]
>
>[/color]

Send email to [email]mpio@microsoft.com[/email]

LaGeek wrote:[color=blue]
> No we havent. I am not even sure how to get in touch with someone in the ALUA
> DSM team. It surprised me that this did not work, because it seems pretty
> basic...
>
> "Ed I" wrote:
>[color=green]
>> I am seeing the same behavior with our TPG storage processor.
>> Have you made any preogress in determining the cause?
>>
>> On Jul 17, 10:03 pm, LaGeek <LaG...@discussions.microsoft.com> wrote:[color=darkred]
>>> Folks,
>>> We are trying to work our array work with the Windows Native DSM. We are an
>>> Active Standby array, and it seems to come up and work and failover fine.
>>>
>>> We have an error condition where we want the DSM to issue a failover Set
>>> Target Port Groups command. We are reporting the Unavailable state for the
>>> volume as per SPC, and returning Check condition, not ready, LU not
>>> accessible, Target port in Unavailable State as per SPC for IOs. But that
>>> does not seem to make the DSM issue a failover command.
>>>
>>> My question is:
>>> What are the requirements from the DSM perspective from a storage array when
>>> the storage array wants to trigger the DSM to issue a failover command for
>>> the Windows Native ALUA DSM?[/color]
>>[/color][/color]