Home > Articles > CCDE Study Guide: Enterprise Campus Architecture Design

CCDE Study Guide: Enterprise Campus Architecture Design

Chapter Description

In this chapter from CCDE Study Guide, Marwan Al-shawi discusses issues related to enterprise campus architecture design, including hierarchical design models, modularity, access-distribution design model, layer 3 routing design considerations, EIGRP versus link state as a campus IGP, and enterprise campus network virtualization.

From the Book

CCDE Study Guide

CCDE Study Guide

$79.99 (Save 20%)


The enterprise campus is one of the vital parts of the modular enterprise network. It is the medium that connects the end users and the different types of endpoints such as printers, video endpoints, and wireless access points to the enterprise network. Therefore, having the right structure and design layout that meets current and future requirements is critical, including the physical infrastructure layout, Layer 2, and Layer 3 designs. To achieve a scalable and flexible campus design, you should ideally base it on hierarchal and modular design principles that optimize the overall design architecture in terms of fault isolation, simplicity, and network convergence time. It should also offer a desirable level of flexibility to integrate other networks and new services and to grow in size.

However, the concept of network virtualization helps enterprises to utilize the same underlying physical infrastructure while maintaining access, and path and services access isolation, to meet certain business goals or functional security requirements. As a result, enterprises can lower capex and opex and reduce the time and effort required to provision a new service or a new logical network. However, the network designer must consider the different network virtualization design options, along with the strengths and weaknesses of each, to deploy the suitable network virtualization technique that meets current and future needs. These needs must take into account the different variables and constraints, such as staff knowledge and the hardware platform supported features and capabilities.

8. Further Reading | Next Section Previous Section