www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / Design / CCDP / Chapter 1: The Cisco Enterprise Architecture Model / Cisco Hierarchical Network Model

Cisco Hierarchical Network Model

The most important idea concerning the Cisco Hierarchical Network model is the construction of the network step by step, implementing one module at a time, starting with the foundation. The implementation of each module can be supervised by the network architect, but the details are covered by specialized teams (e.g., routing, security, voice, etc.). This modular approach is the key to making implementation simple. The main advantages of the Cisco Hierarchical Network model are as follows:

  • Easy to understand and implement
  • Flexibility
  • Cost savings
  • Modular
  • Easily modified
  • Easy network growth
  • Facilitates summarization
  • Fault isolation

This model was created so that the construction of the IIN would be easier to understand. Cisco has always tried to make efficient and cost-effective networks that have a modular structure so they can be easily divided into building blocks. The modular network design facilitates modifications in certain modules, after implementation, and makes it easy to track faults in the network.

A special feature promoted by the Cisco Hierarchical Network model is summarization. This allows for smaller routing tables and smaller convergence domains, which leads to many advantages, such as summarizing routes from an OSPF area as they enter the backbone or having a more stable network by not advertising specific network changes to other areas or domains. For example, a network failure or modification in an OSPF area means a specific prefix will not be advertised within that area, but this does not impact the rest of the network because that prefix is part of a larger, summarized network that does not change. This behavior enhances efficiency in the network’s functionality and allows for optimal network design.

Note:    Depending on the situation, summarization can also have some disadvantages, including making troubleshooting more difficult and allowing traffic black holes.

The Cisco Hierarchical Network model (see Figure 1.9 below) is defined by the following three layers:

  • The Core (backbone) Layer
  • The Distribution Layer
  • The Access Layer

1.9

Figure 1.9 – Cisco Hierarchical Network Model Layers

These three layers might sometimes collapse into each other to make networking easier, especially in small networks. For example, a network might have two real layers: an Access Layer and a collapsed Distribution and Core Layer. Although the Distribution and Core Layers may be considered united in this scenario, there is a clear difference between the functionalities of the Distribution Layer and the functionalities of the Core Layer within the compressed layer.

The Core Layer is the backbone of the network and its main purpose is to move data as fast as possible through Core Layer devices. The design purpose in the Core Layer is providing high bandwidth and obtaining a low overhead. The Core Layer contains Layer 3 switches or high-speed routers, which are used to obtain wire speed. For example, if the Core Layer devices have 10 Gbps interfaces, the devices should send data at 10 Gbps without delay on those interfaces.

It is not possible to connect to all of the necessary resources through the LAN because some resources are remotely located. A legacy network concept, the 80/20 rule, states that 80% of the network resources are local and 20% are remote. In modern networks this rule is inverted, meaning 20% of the network resources are local and 80% are accessible remotely. The Distribution Layer is the layer that provides access to these remote resources, as fast as possible, usually using Layer 2 switches. This layer facilitates speedy access to resources located in other networks (different locations) or on the Internet.

The Access Layer connects users to the network using Layer 2 and Layer 3 switches. This layer is often called the desktop or workstation layer because it connects user stations to the network infrastructure. The Access Layer also connects other type of devices, including servers, printers, and access points.

The Cisco Hierarchical Network model can be generically mapped to the OSI model, as follows:

1.10

Figure 1.10 – Cisco Hierarchical Network Model Mapped to the OSI Model

As shown in Figure 1.10 above, each layer has physical and data-link processes, but the higher OSI layers used in the Access, Distribution, and Core Layers might be different. The Core Layer mainly uses transport and network services and there is some overlap between the Core and Distribution Layers in this regard. The Distribution Layer also handles transport and network services but with more emphasis on the Network Layer (Layer 3). The Access Layer is involved with the upper layer protocols, namely Transport, Session, Presentation, and Application Layers. This makes sense, as speed decreases going from the Core Layer to the Access Layer because of the addition of more layers of protocols, applications, and services.

To summarize, users connect to the network through the Access Layer, access remote resources through the Distribution Layer, and move data through the network as fast as possible through the Core Layer.

The Core Layer

The Core Layer of the network involves the following aspects:

  • High speed
  • Reliability and availability
  • Redundancy
  • Fault tolerance
  • Manageable and scalable
  • No filters, packet handling, or other overhead
  • Limited, consistent diameter
  • Quality of Service (low latency)

High speed refers to ports operating close to true wire speed on the Core Layer devices, with minimal delay. Reliability is another important issue when defining how often equipment functions at normal parameters. Redundancy and fault tolerance are intertwined, and they influence the recovery time when a network device or service stops functioning. Sometimes the network is back up and running seamlessly (transparently) because of redundancy technologies, so when something crashes in the network, users are not impacted and can continue working.

Another feature of the Core Layer operations is it does not influence the traffic in any way, as its main goal is fast traffic switching. To avoid overhead and to move traffic through the Core Layer as quickly as possible, complex security features and filtering are not configured on Core Layer devices; instead, they are configured in the Access and Distribution Layers. One important aspect that should be monitored carefully is the growth of the Core Layer. The network backbone usually consists of a limited but consistent diameter, and a solid network design should support Distribution and Access Layer expansions without impacting the Core Layer.

A very powerful feature used in the Core Layer is called Quality of Service (QoS); however, the QoS parameters implemented in the Core Layer are different from the QoS parameters used at the network edge, as they are focused on ensuring low-latency packet switching. Quality of Service is a complex and sophisticated topic that will be covered in detail later in this book. However, to preview, the major QoS techniques are as follows:

  • Best effort: This implies sending traffic without the guarantee of assurance or reliability.
  • Integrated Services approach (IntServ): IntServ is based on the admission control concept on the network devices. For example, when someone uses a VoIP telephone, all of the devices in the path to the destination can communicate with each other and reserve the amount of bandwidth necessary for that call. To achieve this, IntServ uses protocols like the Resource Reservation Protocol (RSVP).
  • Differentiated Services (DiffServ): This is the most modern and popular QoS approach in that it classifies and marks traffic on a hop-by-hop basis. The DiffServ approach is comprised of the following disciplines:
    • Classification
    • Marking
    • Congestion management
    • Congestion avoidance
    • Traffic compression
    • Link Fragmentation and Interleaving (LFI)

When using DiffServ, each layer is assigned specific QoS mechanisms that integrate and work together with the QoS mechanisms at other layers.

Note:    The QoS features presented above are not specific to the Core Layer. Instead, they are generic concepts that are applied to all three layers and are presented in this section as a reference.

 

The Distribution Layer

Unlike the Core Layer, the Distribution Layer includes features that involve some kind of traffic processing, since this is where policies are implemented in a network, for example, which user can access what resources from outside of the network. This is also where many of the security features are implemented in response to the growing number of attacks from the Internet.

The Distribution Layer shares some common features with the Core Layer, like QoS techniques and redundancy features. Except for these commonalities, the Distribution Layer performs a unique and completely different set of functions, such as the following:

  • Access control to the Core Layer
  • Redundancy to Access Layer devices
  • Routing protocol boundaries
  • Redistribution
  • Filtering
  • Route summarization
  • Policy routing
  • Security
  • Separate multicast and broadcast domains
  • Routing between VLANs
  • Media translation and boundaries (e.g., FastEthernet to GigabitEthernet)
  • Aggregation

The value of this separation of functions is easier to understand, troubleshoot, and manage when there are different jobs occurring in these hierarchical network layers.

 

The Access Layer

In an Enterprise Campus design, the Access Layer is characterized by a shared LAN, a switched LAN, and VLANs to the workstations and servers. This layer provides high availability and flexible security features, like port security, Address Resolution Protocol (ARP) inspection, and VLAN Access Control Lists (VACLs). These security features will be covered in detail in the dedicated security chapter later in this book.

Other functions of the Access Layer involve port security, 802.1x, broadcast control, and defining QoS trust boundaries (i.e., what devices are trusted based on the QoS settings or the distance to the actual desktop stations before classification and marking takes place). In addition, to mitigate the threat of users trying to deploy Denial of Service (DoS) attacks on the network, rate limiting techniques can be implemented.

Other features implemented in the Access Layer include the Spanning Tree Protocol (STP – to ensure that the Layer 2 logical topology is loop-free) and Power over Ethernet (PoE) or voice VLAN settings (if the network functionality requires them). Examples of the latter would be automatically placing the voice traffic in a voice VLAN when plugging an IP phone into a Cisco switch, and powering IP phones using an Ethernet cable when using PoE-capable Cisco Catalyst switches. From a WAN standpoint, the Access Layer can provide access to PSTN, Frame Relay, or ATM networks and ISDN, DSL, or cable services.

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.