@pubjohndoe wrote:
Wonder what happens with 2930 series... Though it would be nice to see 2530 getting dropped and 2930 being the first model.
Well...to see the Aruba 2930F becoming the new "entry level" in a unified switching portfolio...Aruba should drop at least three things:
- Aruba 2530 Switch series
- Aruba 2540 Switch series
- Aruba 2930F Switch series price (to be near to - at worst - to the Aruba 2540 Switch series price figures)
Nearly impossible. For what then? ah...no portfolio overlapping?
I see some technology approaches overlapping instead: will VSF deployed on ArubaOS-CX be exactly as the VSF deployed on Aruba 2930F?
I don't believe it will.
Just consider that actually VSF on ArubaOS-Switch shows its own peculiarities: VSF deployed on Aruba 2930F has neither the very same set of features - absence of FSU recalls you nothing? - nor the very same set of restrictions/requirements - the 2 VSF Members limits recalls you nothing? - the VSF deployed on Aruba 5400R zl2 has...that's to say that VSF on ArubaOS-Switch - due to Hardware differences (only?) between platforms - shows its own flavours.
The fact is that we will deal with three flavours of VSF Virtual Switching Framework implementations where instead VSX is - AFAIK - VSX sic et simpliciter (no matter if deployed on Aruba 8320, 8325 or 8400...and probably nothing will change on Aruba CX 6400 too):
On ArubaOS-Switch NOS:
- VSF on Aruba 2930F Switch series ONLY (up to 8 VSF Members if > 16.06 software is used, up to 4 if < 16.06)
- VSF on Aruba 5400R zl2 Switch series ONLY (2 members only + various other requirements)
On ArubaOS-CX NOS:
- VSF on Aruba CX 6300 Switch series ONLY (up to 10 VSF Members)
There is IMHO overlapping.
Haven't seen Aruba CX 6300 documentation yet...so I'm currently not able to compare VSF on ArubaOS-Switch versus VSF on ArubaOS-CX as an educated guess...but I feel the flavouring listed above will be reflected by the fact that underlying NOSes and platforms' hardwares are really totally differents so VSF requirements, restrictions and probably features on Aruba CX 6300 will necessarily differentiate.
A note about Aruba CX 6300M naming:
Here I see a relationship with existing Aruba 2930M and Aruba 3810M Switch series ..for my line of reasoning here I suppose we all were used to associate the M suffix of 2930 and 3810 not only to their modularity features but also to their Backplane Stacking capabilities (so it was easy to know who is run what in a VSF versus Backplane comparison): now think about a customer who know them and will approach the new Aruba 6300 Switch series...he/she will be inducted to think that Aruba CX 6300 models with M suffix will be charecterized by using a similar stacking technology approach (backplane versus frontplane) where instead, running on the same ArubaOS-CX NOS, the M suffix on their names merely means simply Modular (Fan/PS) from the Hardware standpoint and it has nothing to do with stacking technology approach they really support...OK that's not overlapping...but it is just naming confusion that could have been avoided.