Subscribe

Re: Stack Same Path warning... recabling advice.

Ontap does this automatically. Once you move the fiber ports you will see it change.

Re: Stack Same Path warning... recabling advice.

I found this link. I am not quite sure if the explanation of the FC multipathing for an HA pair is accurate or just confusing me even more.

http://blog.hernanjlarrea.com.ar/index.php/netapp-cabling-and-hardware-basics/

Re: Stack Same Path warning... recabling advice.

I know people at NetApp struggled with MPHA at first; the concept is difficult to understand at first, once you have worked with it for a while it will make sense. The link you have is about the best explanation you will find; the diagrams are very good at the end of the article. The old shelves had IN/OUT on the modules; they changed at some point to arrows.

If you send me you layout I might be able to help more. Let me know the type of modules you are using in each stack. We have a lot of equipment onsite, I can send pictures if that helps.

You can always get NetApp PS services to help you with this, I'm sure they will charge for this.

Re: Stack Same Path warning... recabling advice.

Thank you. I will send you something once I have gathered them. Pretty much here is how I understand it in terms of multipathing for an HA.

Controller 1, connects to:

Channel A, IN port of first shelf of stack

Channel B, OUT port of the last shelf of stack

Controller 2 connects to:

Channel B, IN port of first shelf of stack

Channel A, OUT port of last shelf of stack

Is that correct?

Re: Stack Same Path warning... recabling advice.

You got it.

I would use the same controller ports, Controller 1 connects to stack 1 A IN on controller port 1a and B out would be port 3a on controller 1. Controller 2 would connect to stack 1 A OUT on 1a and port 3a for B IN on the last shelf of the stack 1. To verify this storage show disk -p on both controllers, during downtime you should be able to pull  module A on shelf 1 stack 1 and both systems should stay up, you will see errors messages after a few minutes. Re-insert the module after a few minutes and check the MPHA again.

Re: Stack Same Path warning... recabling advice.

Thanks again.  six of our stacks are saying " primary and redundant are on the same path" Just by running show disk -p, I can see that they are either both on A or both on B module. On top of that both cables are connected to the same ASIC on the controller (example: 1a, 1b) So they are two issues it seems. What do you think is the best approach in terms in order in which of these issue I should first? should I separate module connectivity first or the ASIC connectivity?

Thanks,

md

Re: Stack Same Path warning... recabling advice.

Thanks again. also I guess another question is when one path is disconnected, the redundant takes over, but is there a setting that dictates how this happens, meaning some option that has to be enabled? or timeout that has to be configured? things of that nature that I should be aware of. I know before in another more stable environment, I added a shelve in a DS4243 stack and everything went smoothly without disruption. But that is SAS connection, I don't know if variables are different with a FC HBA shelves.

Re: Stack Same Path warning... recabling advice.

Since you have 4 cards in the controller you can use (assuming 3 stacks are on the A controller and 3 stacks are on controller B), you can connect them like this:

(I assume stacks 1-3 are assigned to controller A and stack 4-6 are assigned to controller B)

1a/3a stack1

1b/3b stack2

1c/3c stack3

4a/11a stack 4

4b/11b stack 5

4c/11c stack 6

You can't use 1d/1c on stack for two reasons, same ASIC and what would happen if card in slot 1 failed.

If you have any any stacks were the primary port on the shelf if the same such as:

PRIMARY  PORT  SECONDARY PORT SHELF BAY

-------- ----  --------- ---- ---------

2a.06.0   A    1a.06.0    A     6    0

You should be able switch the cables on the last shelf in stack to correct this problem. It would be better to do this doing downtime, it shouldn't cause any down time, after each change check it.

Once you get the disk stacks connected properly:

PRIMARY  PORT  SECONDARY PORT SHELF BAY

-------- ----  --------- ---- ---------

2a.06.0   B    1a.06.0    A     6    0

Once you get the disk stacks connected properly first, you should be able to move the connections on the controller. You might want to do at separate times. You should do this during a scheduled downtime and let your end users know that an outage is possible. I would consider using NetApp Professional Services to plan and do this, six stacks is a lot to take on, if you make a mistake or something else goes wrong while you are doing this you could lose data. You could take down the cluster, boot in maintenance mode, make the changes and check it in maintenance to be safe. This will allow you check it with "storage show disk -p" and "aggr status -r". Lots of planning, verify and verify again to be sure.

Re: Stack Same Path warning... recabling advice.

Thanks again, you've been really great help. I learned alot.

md

Re: Stack Same Path warning... recabling advice.

I hope I was able to help, good luck