Regarding you're first point, you're correct. Since we use CPU pooling on VMAX3 directors, it is no longer necessary to ensure that each individual CPU core can talk to an EFD. Any BE CPU core can now talk to any EFD drive attached to that director. Thus the only best practice now is to try to balance the EFD raidsets across directors.
Regarding your second point, this also involves the new CPU pooling technology. Unlike older VMAXes, any port on a director can be addressed by any FE CPU core in the pool. Therefor each port can utilize all the FE CPUs on its respective director board, all the way up to reaching full line-rate on that port. With that being said, my personal suggestion is to target at least 4 to 8 FC ports for use with each director board.
KW160
121 Posts
1
February 19th, 2016 10:00
Regarding you're first point, you're correct. Since we use CPU pooling on VMAX3 directors, it is no longer necessary to ensure that each individual CPU core can talk to an EFD. Any BE CPU core can now talk to any EFD drive attached to that director. Thus the only best practice now is to try to balance the EFD raidsets across directors.
Regarding your second point, this also involves the new CPU pooling technology. Unlike older VMAXes, any port on a director can be addressed by any FE CPU core in the pool. Therefor each port can utilize all the FE CPUs on its respective director board, all the way up to reaching full line-rate on that port. With that being said, my personal suggestion is to target at least 4 to 8 FC ports for use with each director board.