Wired Intelligent Edge

 View Only
last person joined: 10 hours ago 

Bring performance and reliability to your network with the Aruba Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of the ArubaOS-Switch and ArubaOS-CX devices, and find ways to improve security across your network to bring together a mobile first solution.
Expand all | Collapse all

VSF require license and 5400 series module compatibility?

This thread has been viewed 15 times
  • 1.  VSF require license and 5400 series module compatibility?

    Posted Jun 23, 2022 12:08 PM
    Does VSF configuration require licenses on the 5406s switches?
    Any requirement for VSF?

    Also are all generations of switch modules in the 5400 series compatible with chassis?


  • 2.  RE: VSF require license and 5400 series module compatibility?

    Posted Jun 23, 2022 01:56 PM
    Hi, speaking about ArubaOS-Switch based switch series - such as Aruba 5400R zl2 and Aruba 2930F - the VSF (Virtual Switching Framework) implementation does not require any licensing, it's a feature contained in the recent/current AOS-Switch software main releases (say it was introduced with AOS-Switch 16.02 main software release on Aruba 5400R zl2 Switch series).

    Specifically speaking about Aruba 5400R zl2 series (not to be confused with HP 5400zl Switch series) there is enough documentation to understand requirements and properties (say as example this quite old technical whitepaper or this presentation).

    Basically to form a VSF prerequisites require that you have two Aruba 5406R zl2 or two Aruba 5412R zl2 (you can't mix say an Aruba 5406R zl2 with an Aruba 5412R zl2 together) operating in v3 only mode and so with only v3 zl2 Modules (differences between other generations and the latest v3 zl3 are explained here, and v3 zl2 Modules installation guide here). You also need 10G or 40G VSF Links (generally made with DAC) and then it's a matter of software configuration. Keep in mind that each VSF Member will work with just one Management Module (the other is taken offline if installed <- no redundancy at chassis level as when you deal with two MMs on a single standalone Chassis).

    Consider to read also the VSF dedicated Chapter on the official Aruba 3810M/5400R zl2 Management and Configuration Guide (for ArubaOS-Switch 16.10) available here (docs can be freely and easily browsed on asp.arubanetworks.com portal).

  • 3.  RE: VSF require license and 5400 series module compatibility?

    Posted Jun 23, 2022 08:01 PM
    Thank you for the quick response.

    If I understand the documents correctly, to configure VSF, all modules in the chassis has to be v3.  VSF can be configured over 10Gb fibre cables not necessary have to be DAC cables.

    We have an existing 5406R in production, if we add another 5406R and configure VSF, how does the port numbering get assigned?  The 2nd or the new 5406R will be renumbered (member 2/slot/port) without affecting the existing production configuration?

  • 4.  RE: VSF require license and 5400 series module compatibility?

    Posted Jun 24, 2022 03:20 AM
    Hi! technically speaking VSF supports only Aruba v3 zl2 Modules and requires that the chassis (Aruba 5400R zl2 Switch series) is operated using the "v3 only-mode" of operation (this excludes any older v2 zl Module from operation in the chassis): these requirements/restrictions, clearly, impose some choices on your side (losing any v2 zl Module, as example).

    With regard to port renumbering once VSF is activated first on the VSF Conductor: this renumbering is going to happen on VSF Conductor itself and on the VSF Standby too once it joins the VSF stack.

    Saved running configuration on the VSF Conductor should be preserved during the Standalone -> VSF (Conductor) shift.

    See this updated VSF Configuration guide (it supersedes the one I initially linked above).