MSA Storage

MSA active/active Failed Redundancy Path (error 409) In ACU

 
adelgado
Frequent Advisor

MSA active/active Failed Redundancy Path (error 409) In ACU

Hi,

 

I've just upgraded our MSA1000 to active/active, and everything went smoothly.

 

This MSA100 is connected to a two HP StorageWorks 2/8q  fiber switches, one controller to one switch, and the other controller to the other switch. Servers are connected to fiber switches, one fiber cable to one fiber switch, the other fiber cable is connected to the other fiber switch.

 

The issue is that in ACU, we got Failed Redundancy Path (error 409) In ACU.

 

I can't guess what is the solution, as both controlles displays no error.

 

ACU version is latest one, 9.40.12.0.

 

Also, have installed MPIO.

 

Does anybody how to solve it?

 

Regards,

Senior Systems Administrator
34 REPLIES 34
Torsten.
Acclaimed Contributor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

Do you use the correct MPIO for active/active?

 

http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3Didx%253D1%257CswItem%253Dco_68650_1%257CswEnvOID%253D%257CitemLocale%253D%257CswLang%253D%257Cmode%253D4%257Caction%253DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

 


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
adelgado
Frequent Advisor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

Yes,

 

I'm using it.

 

I've tried to connect directly a server to the MSA1000, and happens the same.

 

Then, I tried connecting only to one controller (this is, disconnecting one of the controller's fiber cable), opened CLI window, and typed "controller all show", and showed me both internal controller and MSA1000.

 

Then I did the same for the other controller, this is, disconnecting one and connecting the other one. Then, ACU CLI only show the internal controller, but not the MSA1000.

 

Could it be that as was this second controller on the MSA set as standby, needs to be configured with cable attached to it?

 

Thanks

Senior Systems Administrator
Torsten.
Acclaimed Contributor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

Maybe you need to check selective storage presentation and/or zoning again?


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
adelgado
Frequent Advisor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

Hi Torsten,

 

Sorry for the inconvenience, but how do I do so?

 

Thanks a lot.

Senior Systems Administrator
Torsten.
Acclaimed Contributor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

On the server connected to the MSA, run ACU and check for SSP (right column in the example picture below).

 

Also connect to the switch (if there is any) and check the zoning settings.

 

Each server HBA must be allowed to access the LUN in question.

 

 

 


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
adelgado
Frequent Advisor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

I see,

 

But now, I don't have any volumes created at all.

 

BTW, how is that if I connect both MSA controllers directly to a server do the same? I mean, get the same error?

 

I understand that if is something concerning switches (that I already have, two StorageWorks 2/8q), connecting the controllers to the server, should not have this error, shouldn't?

 

Thanks

Senior Systems Administrator
Torsten.
Acclaimed Contributor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

As said, make sure that each server HBA can access the LUN in question.

 

If a switch is connected, configure the zoning accordingly.

 

If you enable SSP in the MSA, configure the LUNs to the WWN of the server.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Greybeard
Esteemed Contributor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

Try connecting both HBAs to the same switch, then the other one, and temporarily turn off zoning too. If this works then you likely have a config or switch firmware issue. Also check the HBAs have the same firmware / revision (assuming they are the same model) in case the new MSA controller code does not like one of them.

_________________________________________________
How to assign points on this new forum? Click the Kudos Star!
adelgado
Frequent Advisor

Re: MSA active/active Failed Redundancy Path (error 409) In ACU

Hi,

 

I've alredy connected both controllers to the same switch, as well as server, and nothing. Also, connected them to the other switch, and the same.

 

There are no zones configured at switch level.

 

I have to say that I have no LUN's created by now.

 

What makes me feel something is wrong at MSA level, is that on ACU I can disable the standby controller, seems as althoug it has been upgrade and active/active, is not configured to be active/active. Am I wrong?

 

I remember you LCD panels doesn't show errors.

 

Regards,

Senior Systems Administrator