Start a Conversation

Unsolved

This post is more than 5 years old

2662

October 20th, 2015 07:00

VMAX3 Zoning Best Practices and FA layouts

Hey everyone!

I'm looking at trying to figure out zoning best practices and new FA layouts on a VMAX3.  We have several 3-Engine VMAX3's and I'm looking at opinions / recommendations / and best practices.

Using my previous VMAX and DMX knowledge, I'm guessing things are going to be similar, but wondering if people had an opinion since the whole 'Rule of 17' goes away, etc. 

Also, I believe I read someplace that the 0 and 1 ports are not combined anymore i.e. you don't have to worry about competing CPU, etc on say for example in the VMAX2 world  FA8H Port 0 and FA8H Port 1, etc...

Do you think that Even Directors on Fabric A and Odds and Fabric B and then divide ports as needed by applications/ etc work in this scenario?    Also with the 3 - Engine thing I'm probably going to be breaking things up into groups of 6 or 12 ports as far as zoning is concerned. 

Can someone point to any whitepapers or topics on this subject?

Thanks!

Brian

465 Posts

October 20th, 2015 15:00

Here are some considerations for you that will assist on your zoning choice in VMAX3.

  • A VMAX3 engine contains 2 directors (1, 2 or A, B – depends where you look )
  • Each director in an engine has its own redundant power and cooling.
  • Each director contains a number of IO modules, with the IO module type installed based on customer requirement. Up to 4 IO modules can be used for front-end connectivity.
  • The IO modules for 8 and 16GB FC are 4 port (hence a max of 16 FA ports per director)
  • The port numbers within an IO module are numbered consecutively. 4-7, 8-11, 24-27 and 28-31
  • The director numbers and engine numbers both increase from 1. So Directors 1 and 2 are in engine 1. Directors 3 and 4 are in engine 2 etc.

So you can see that the VMAX3 architecture does support your notion of even and odd director numbers in their own fabric.

From a masking perspective, you can have multiple ports used on the same director to the same host, but probably a good idea to spread them across the IO modules.

No Events found!

Top