Scribd
Upload
113 views3 pages

Enterprise Network Architecture

Uploaded by

Qusai Rihab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
113 views3 pages

Enterprise Network Architecture

Uploaded by

Qusai Rihab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

ENTERPRISE NETWORK

ARCHITECTURE
TABLE OF CONTENTS

1 Hierarchical Layers.........................................................................................................................................1
1.1 Access layer...........................................................................................................................................1
1.2 Distribution layer..................................................................................................................................1
1.3 Core layer..............................................................................................................................................1
2 LAN/Campus Architecture.............................................................................................................................2
2.1 Two Tier Design.....................................................................................................................................2
2.2 Three Tier Design..................................................................................................................................2
2.3 Layer 2 access layer (STP based)...........................................................................................................2
2.4 Layer 3 access layer (routed access).....................................................................................................2
2.5 Simplified Campus Design.....................................................................................................................2
3 Home Architecture........................................................................................................................................3
4 Datacenter Architecture................................................................................................................................3

1 HIERARCHICAL LAYERS

- Number of layers needed depends in the environment

1.1 ACCESS LAYER

- = network edge
- Connects end users/devices to the LAN
- Access layer switches are not interconnected to each other, traffic has to go through distribution layer
- VLAN assignment/Security/QoS tagging is important

1.2 DISTRIBUTION LAYER

- Aggregate point for the access layer


- Provides a path through which the access layer can forward traffic
- Boundary between layer 2 and layer 3
- On layer 2 side: STP boundary
- On layer 3 side: IP summarization
- VLANs (SVIs)/Routing (protocols)/ACL/QoS
- Need to be deployed in pairs for redundancy
- Distribution layer switches should be interconnected to each other using either L2 or L3 link
- Distribution layer can be used to interconnect geographically separated buildings with low number of
fiber-optic cables
- Sometimes called Aggregation layer in datacenter environment

1
1.3 CORE LAYER

- Aggregates distribution switches


- Dedicated core layer advised when networks grow beyond 3 distribution layers in a single location
- Provides very high forwarding rates, scalability, high availability
- Reduces large network complexity

2 LAN/CAMPUS ARCHITECTURE

- Terminology:
o Star: one central device connects to several others
o Full mesh: all nodes are connected to each other (#links=N(N-1)/2)
o Partial mesh: a mesh were not all nodes are connected to each other
o Hybrid: combining topologies
- Hierarchical design is most appropriate for north-south traffic flows (like end point communicating with
WAN edge)

2.1 TWO TIER DESIGN

- = Collapsed Core
- Access and distribution/core layer
- Hybrid design with star topology at access layer & partial mesh at distribution layer

2.2 THREE TIER DESIGN

- Access, distribution and core layer


- Recommended when more than 2 pairs of distribution switches are required
- Very scalable, but costly

2.3 LAYER 2 ACCESS LAYER (STP BASED)

- Traditional: L2 access layer, L3 distribution layer


- Distribution switches should be in pairs and run an FHRP. HSRP and VRRP are most common but these
have only one active router and this only use a single uplink. Manual configuration of distribution layer is
necessary for load balancing (one distribution switch for odd VLANs, one for even VLANs). GLBP is better
but this only works on loop-free topologies (because all uplinks from access layer must be in forwarding
state (so not blocked by STP)).

2.4 LAYER 3 ACCESS LAYER (ROUTED ACCESS)

- Access layer has layer 3 switches (and SVIs)


- Access to distribution uplinks are routed links, not trunks
- Advantages:
o No FHRP needed
o No STP needed
o Increased uplink utilization
o Easier troubleshooting
o Faster convergence
- Disadvantages:
o Does not support spanning VLANs across multiple access switches
o Not most cost-effective because L3 switches are more expensive than L2

2
2.5 SIMPLIFIED CAMPUS DESIGN

- Relies on switch clustering such as Virtual Switch Stacking (VSS) and StackWise (switch stacking)
- Multiple physical switches act as a single logical switch (2switches for VSS, up to 9 switches for switch
stacking)
- Chassis switching
- Advantages:
o Simplified design
o No FHRP needed
o Increased uplink utilization
o Easier troubleshooting
o Faster convergence
o Distributed VLANs without the need to block any links

3 HOME ARCHITECTURE

- SOHO (= Small Office Home Office)


- Most of the time one single networking device for all functions

4 DATACENTER ARCHITECTURE

- Aggregation layer has scalability issues in a 3-tier datacenter design


- LAN Architectures are optimized for north-south traffic flows (from core to access and vice versa)
- Leaf-spine design is a new design alternative for modern datacenters, where most traffic is east-west (like
between servers in datacenter)
- Spine = backbone only
- Leafs = switching where servers connect to, typically on TOR (= Top Of Rack)
- Full mesh between spine and leaf
- Can be 2 or 3 layers
- Internet and core switches come in at the leaf switches
- Very scalable

You might also like