Wired Intelligent Edge

last person joined: yesterday 

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

Best practice for adding new S3500 switches to mobility access switch stack

This thread has been viewed 2 times

  • 1.  Best practice for adding new S3500 switches to mobility access switch stack

    Posted Mar 01, 2015 05:41 PM

    I have a number of questions regardiing the S3500 switch in stack configuration.

    1. What is the maximum number of switches in a single switch stack comprising S3500 switches?

    2. And can you add a new S3500 switch with a different software version to that of the existing switch stack?

    3. Lastly, will the switch stack retain all the original configuration when new switches are added to the stack?



  • 2.  RE: Best practice for adding new S3500 switches to mobility access switch stack

    EMPLOYEE
    Posted Mar 01, 2015 05:46 PM

    1)   8 switches in a stack (0-7). If you need more than 8, you can create a "sub-stack" which a separate stack that is L2 connected to the main stack (you can use DAC cables at 10G, they will be switchports instead of stacking ports). Just don't add too many or you risk exceeding the MAC tablesl

    2)   You can add the switches, but they will remain dormant until you upgrade the code.

    3)   Yes, the primary (which is one of your existing switches) has control of the config. When you add new switches, you simply start configuring the new interfaces. The format will be <new-sw-#>/0/<port>

     

    You can verify stacking with:

     

    show stacking members

     



  • 3.  RE: Best practice for adding new S3500 switches to mobility access switch stack

    Posted Mar 01, 2015 05:50 PM

    Thanks for the prompt response, Tim!