Is MPLS mandatory for Traffic Engineering? Read more
Tier 1,Tier 2 and Tier 3 Service Providers
What is tier in the first place ? If you are dealing with Service Provider networks, you hear this term a lot. But how we define Tier 1,Tier 2 and Tier 3 Service Providers ?
What should be their infrastructure to be seen as Tier 1 for example ?
Which tier is bigger in scale ? Which one is better for the customers to purchase a service from ?
Why Service Providers claim that they are Tier 1 or Tier 2 ? Read more
Is fate sharing bad thing in network design? Someone asked this question recently on my youtube channel and I want to share a post for the website followers as well.
First of all, what is fate sharing ? Below is the Wikipedia definition of fate sharing.
” Fate-sharing is an engineering design philosophy where related parts of a system are yoked together, so that they either fail together or not at all ” Read more
Introduction to VPN (Virtual Private Network)
Let’s start with the definition. VPN is a logical network and created over shared physical infrastructure.
Shared infrastructure can be private such as MPLS VPN of a Service Provider or over the Public infrastructure such as Internet.
There are many concepts to understand VPN in detail but in this article I will cover the definition, common design considerations, and some not well known concepts about it.
We can group VPNs into two categories. WAN and the Datacenter VPN Technologies.
WAN VPN Technologies
2.mGRE (Multipoint GRE)
8. MPLS L3 VPN Read more
Network mergers and acquisitions are the processes which can be seen in any type of businesses. As a network designers, our job to identify the business requirements of both existing networks and the merged network and finding best possible technical solutions for the business.
There are many different areas which need to be analyzed carefully. Wrong business requirement gathering and design analyze, definitely lead to catastrophic failures.
Business and network analysis and technical information gathering are the key steps and there are many questions which need to be asked and answered should be well understood.
Network mergers and acquisitions is also called as Network integration.
Below are the key points for any type of network mergers and acquisitions projects.
- Business analysis and information gathering
OSPFv2 by default setup only one adjacency over a single link. But this can be an issue some time and as a network designer you should understand the consequences and know the available solutions.
Placing a link in wrong OSPF area can create an OSPF sub optimal routing especially in hub and spoke topology.
In IS-IS or OSPFv3, this wouldn’t be an issue because IS-IS and OSPFv3 allow link to be placed in more than area or level. (In IS-IS, area is assigned to the router, not to the link. Thus I use level keyword)
Let’s look at the below network to understand what is the issue and how OSPF multi-area adjacency can solve the sub optimal routing problem. Read more
IS-IS Design considerations on MPLS backbone
Using IS-IS with MPLS require some important design considerations. IS-IS as a scalable link state routing protocol has been used in the Service Provider networks for decades.
In fact, eight of the largest nine Service Providers use IS-IS routing protocol on their network as of today. Read more
BGP Peering is an agreement between different Service Providers. It is an EBGP neighborship between different Service Providers to send BGP traffic between them without paying upstream Service Provider.
To understand BGP peering, first we must understand how networks are connected to each other on the Internet. The Internet is a collection of many individual networks, which interconnect with each other under the common goal of ensuring global reachability between any two points.
BGP Peering and Transit Links
What is reliability in networking ? Why reliability is an important design tool ? I will provide the answers of these questions with the examples in this post.
Reliability is within the reasonable amount of time, which depends on the application type and architecture, delivering the legitimate packets from source to destination.
This time is known as delay or latency and it is one of the packet delivery parameters. Consistency of delay known as jitter and it is very important for some type of applications such as voice and video, jitter is our second delivery parameters.
Let’s start with this IP network shown below (Figure-1).
Figure-1 IBGP Next Hop handling in IP networks
You always wonder how fast is your network, right? How long does it take the information travel over the network?
I will share with you this special article, which you can use to find the speed of your network and define it with a numerical number.
I will use ring, partial mesh and full-mesh physical topologies to explain the concept.
Note : I assume bandwidth of all the links in the examples are the same for simplicity.
Pim sparse mode – Multicast is used to send the data to the multiple receivers at the same time. Multicast reduces the load on the servers (Senders/Source in multicast term), provides efficient capacity usage on the network links.
MPLS Design – MPLS Design Case Studies are the useful resources to learn the design details of MPLS.
You will be provided a brief information about the business and technical requirements. You can share your answer at the comment section below.
Note: This is only one of the case studies in the DesignWorld.
DesignWorld provides video and written content for the network designers.
EIGRP vs OSPF – Below comparison table is your primary resource for the OSPF and EIGRP routing protocols when you compare them from the design point of view.
Knowing and understanding these design practices will not only help you for the real life network design but also will help for the any design certification exams.
If you have any question regarding the parameters in the comparison chart, please share in the comment so I can provide more information.
The MANET stands for mobile ad hoc network; in practice, the term generally applies to ad hoc wireless networks of sufficient complexity that some internal routing mechanism is needed to enable full connectivity.
Companies don’t always have high availability. What’s more, there is always a concern of budget and complexity with the high availability even though a number of factors need to be considered during network design.
If the applications of the company do not require high availability, dual carrier or two links to the same carrier is not necessary.
Multihoming refers to a connection to the two different carriers/service providers even though two routers via two links to the same provider is not considered multihomed.
If you design multi level IS-IS network and if you have more than one exit (L1-L2 routers) from the Level 1 domain, you will likely create a suboptimal routing. Multi-level IS-IS design is for large-scale network. What’s more, most of the real life networks use only flat Level 2 IS-IS as their interior gateway protocol (IGP).
I implore all my readers to always remember this topic: IGP LDP synchronization. It is important to use IGP LDP synchronization to avoid blackholing, especially when MPLS networks fails to function effectively.
Understanding everything about routing design is no brainer, especially if you have the chart below on your wall.
The table below highlights the pros and cons of each routing protocol. Of course, you need to consider the design attributes shown in Figure A before embarking on routing design.
Should you like the comparison of the routing protocols illustrated in the table below or should you want to see similar comparison for other technologies, feel free to add your comment in the comment section.
Another boon for all my readers!
If you are interested in network design or considering CCDE, CCDP, or CCDA certification, you can subscribe for membership here so that you can peruse all the design resources (Videos , Tests , Case Studies , and E-Books).
Figure A: Comparison of Routing Protocols
Dual Core Network Design – Dual core design, also known as dual plane or disjoint plane topologies, refers to a highly redundant network chosen by companies whose main objective is to improve the resiliency of their network. Created using different data planes, dual core design is implemented by companies that receive the service from the different service providers. Put simply, big companies use dual core design in order to improve their network. Institutions that generally use this design are found in Europe; they include banks, hospitals, and other financial institutions. What’s more, some companies outside Europe use this design.
The links – passing through same fiber conduit, building, town, or city – are identified as Shared Risk Link Group (SRLG) since they share the same fate if there are any technical glitches. It is pertinent to carefully identify SRLG links between the providers. And if there are shared links, diverge links should be demanded.
Bad Network Design – Availability of a system is mainly measured with two parameters. Mean time between failure (MTBF) and Mean time to repair (MTTR)
MTBF is calculated as average time between failures of a system. MTTR is the average time required to repair a failed component (Link, node, device in networking terms)
Operator mistakes is widely seen as the source of the failure of the systems. Thus although it is not individually used to calculate availability value of a system, Mean time between mistakes (MTBM) is commonly used term among the network engineers.
Most failures are caused by human error;estimate range between 70 to 80 percent. How can so many people are so incompetent?
Actually they are not ! It’s a design problem.
HSRP, VRRP and GLBP are the three commonly used first hop redundancy protocols in local area networks and the data center.
In this post, I will briefly describe them and highlight the major differences. I will ask you a design question so we will discuss in the comment section below.
Last week I sent a below questions and asked the optimal place for an OSPF ABR (Area Border Router). There was a high level of participation. Thanks everyone who shared their thoughts. Hopefully they didn’t do it only for a free CCDE Workbook prize 🙂
Whatever you design , it should be usable first. Computer network design is not an exception.You are not designing a network to support one service only such as VPN or Internet.It should give enough functionality for today and future needs.
Your design should be usable today and the future !
It was so common to use TDM and Ethernet, IP or MPLS as a transport mechanism at the Access and Aggregation network and for the mobile backhaul. TDM is for the real time , delay , loss, jitter sensitive traffic, Ethernet is for the general data applications.
Building a TDM based network is good for real time applications but expensive at the same time. Thus if you will design a converge transport network, you need to understand your business requirements first.
Which services business want to offer ? What are the trends ?
Network Design should be simple! Simplicity is the first network design best practice that I want you to remember. If you have been in the field long enough, you have probably heard about the KISS principle.
If you are a regular follower of my blog, you have maybe heard about the SUCK principle as well.
KISS stands for Keep It Simple Stupid. But do you really know what the simple part is ? Can every part of the network be a simple ?
Unfortunately NOT ! It just cannot be ! But still you should on simplifying as much of your network as possible.
As I have indicated in the past here, intelligence should be at the edge of the networks and network core should be as simple as possible. If you read the above article, you will see some examples. ( There are different opinions about the place of simplicity in networks. Some researchers believe that if the core has some intelligence the overall network complexity is reduced ).
Networks have many protocols, technologies. Understanding each of them might be easy but interaction between them creates complexity.
In my CCDE training sessions, I like to give the Pepper and Salt example to explain this point.