Network Management

 View Only
Back to discussions
Expand all | Collapse all

Seeking Input on Distribution Layer Switch Configuration in Our Network Design

This thread has been viewed 10 times

  • 1.  Seeking Input on Distribution Layer Switch Configuration in Our Network Design

    Posted Nov 14, 2023 01:16 PM
    Edited by desong1011 Nov 15, 2023 01:42 AM

    Hi all,

    I am seeking some insights regarding the configuration of the distribution layer switch in our network design, specifically whether we should enable IP routing or remove it. Below are the key facts for consideration:

    1. ISPs: We currently utilize two ISPs, with a combined total bandwidth of approximately 1.3Gbps.

    2. Redundancy: Our network's redundancy is limited. We have only one firewall and one core switch, with no VRRP or router failover capabilities.

    3. Workforce: On a daily basis, approximately 100-150 employees are present in the office.

    4. Software Utilization: Most of our software applications are cloud-based.

    5. Routing: Inter-VLAN routing is managed at the core switch, using only static routing without any dynamic protocols.

    6. Network Design: Our current setup follows the Cisco three-layer model. This includes one core switch, one distribution switch on each of the three floors, and 2930f switches used in a stacking configuration as access switches.

    7. Role of Distribution Switches: The distribution switches (model 3810M) are currently functioning as Layer 2 switches with no IP routing enabled.

    I would appreciate any recommendations or ideas on whether enabling IP routing on our distribution switches would be beneficial, or if it's preferable to remove the distribution layer. Your expertise and insights on this matter would be highly valuable.

    Thanks for taking time to read my post. 



  • 2.  RE: Seeking Input on Distribution Layer Switch Configuration in Our Network Design

    Posted Nov 24, 2023 11:45 AM

    This would be best to discuss with your Aruba/network partner. For the size of 150 users (let's say 300 devices), I'd assume a distribution layer could be considered overkill, and a 'collapsed core' would be good enough. Running L3 in your access layer (or distribution) would be beneficial mainly if you run into performance issues due to 'hairpinning' to your core. But if your applications are mostly in the cloud/on the internet, there may not be too much traffic between different access VLANs, and moving L3 to your access (or distribution) may just make things more complicated.

    For this size of network, a 3810M may even be enough as a core... except if there are big data flows.

    Do you have (performance) issues at the moment?



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: Seeking Input on Distribution Layer Switch Configuration in Our Network Design

    Posted Nov 25, 2023 01:00 AM

    what is the core switch model ?

    As Herman Roberts says, you should simplify the design and stick to a 2 layers architecture : core + access.



    ------------------------------
    Frederic MEUNIER
    ------------------------------



Related Content