Skip to main content

What is Difference between Contiguous and Discontiguous Networks With Example

I am trying to Explain both terms in some details with example, and trying to keep them as simple as I can so that you can easily understand the meaning of the terms and differences between them.Contiguous Network
The Synonyms of the word Contiguous is Continuous that means “connected together so as to form an unbroken sequence in time”.Now come to the Technical meaning of the Contiguous Network, is that Series of Classfull Subnets that lie under the same Major Classfull Network where the packets can pass between the Subnets crossing the subnet that also lies in the same Major Classfull Network.
Or Define in another Way

A classful network in which packets sent between every pair of subnets can pass only through subnets of that same classful network, without having to pass through subnets of any other classful network.
Still Not got my Point, Ok lets have and Example of Contiguous Network with IP Subnet Addresses. Suppose you have a Classfull network with Subnets as follows,
192.168.0.0/24
192.168.1.0/24
192.168.2.0/24
192.168.3.0/24
See as I defined above this series of Classfull subnets can be summerized into a one classfull network 192.168.0.0/22
If it were non-contiguous (dis-contiguous) networks then you might have:
192.168.1.0/24
192.168.4.0/24
192.168.17.0/24
192.168.240.0/24
In this case you would not be able to summarize the networks without including other networks in the process. Using a network statement like 192.168.0.0/16 will include all of those networks but crucially it also includes all networks from 192.168.0.0 to 192.168.255.0.
So from above example we can define Discontiguous Network as A classfull network in which packets sent between at least one pair of subnets must pass through subnets of a different classfull network
Labels:

Comments

Post a Comment

Popular posts from this blog

Basic MPLS BGP and L3VPN Lab Setup

In this lab, we’ve set up a basic MPLS, BGP, and L3VPN environment, which is a great foundation for understanding how service providers build scalable networks. The lab uses the EVE-NG simulator along with Router IOS C7200-ADVENTERPRISEK9-M, Version 15.2(4)M8 to emulate a realistic MPLS environment. Below is a summary of the key components and roles of each router in the lab. MPLS Core Routers : The MPLS core consists of the routers responsible for label switching and forwarding customer traffic through the network: PE1 (Provider Edge 1) : Connects customer networks to the MPLS core and handles both MPLS and BGP routing. It also hosts VRF (Virtual Routing and Forwarding) instances for customers. PE2 (Provider Edge 2) : Functions similarly to PE1, connecting another customer network to the MPLS core. P1 (Core Router 1) and P2 (Core Router 2) : These routers serve as MPLS core routers and handle label switching but do not store or process customer routes directly. They simply f
Post a Comment
Read more

OSPF Adjacency Stuck in EXSTART on Cisco IOS XR – Issue and Solution

In a recent lab setup using Cisco IOS XR on EVE-NG, I faced a common but frustrating issue with OSPF adjacencies getting stuck in the EXSTART state. After spending considerable time troubleshooting interface MTUs and configurations, I discovered that the root cause was related to the virtual network interface type being used. This post outlines the issue, troubleshooting steps, and the eventual solution that got everything working. Issue: While configuring OSPF between two routers running Cisco IOS XR in my lab, OSPF adjacencies were getting stuck in the EXSTART state. I verified that interface configurations, MTU settings, and OSPF parameters were correct, but the problem persisted. I tried adjusting the MTU size, using the mtu-ignore command, and even checked for ACLs, but nothing seemed to resolve the issue. Troubleshooting Steps: MTU Settings: I started by verifying that both sides of the OSPF adjacency had matching MTUs. I used the default MTU and even tried different values wit
Post a Comment
Read more

How to Properly Clone an EVE-NG Lab with Configurations

Cloning labs in EVE-NG is a great way to duplicate setups and expand or experiment on a new copy without affecting the original lab. However, if not done correctly, the cloned lab may only copy the topology without configurations. In this guide, I’ll show you how to properly clone a lab in EVE-NG with all configurations using the EVE-NG GUI . Follow these steps to ensure that both the topology and router configurations are retained when cloning your lab. Steps to Clone an EVE-NG Lab with Configurations Save Running Configuration on All Devices In your original lab, make sure all devices have their configurations saved to NVRAM. Go into the CLI of each router and run the command: copy running-config startup-config Export All Configurations (CFGs) On the left sidebar in the EVE-NG Web UI , click on the "More Actions" option. Then select "Export all CFGs" . This step exports the configurations of all devices in the lab. Shutdown All Devices After exporting the confi
Post a Comment
Read more