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

What is Cisco Supervisor Engine?

Supervisor Engine is a module that is installed in the Cisco Chassis-based Catalyst Switches or Routers. Supervisor engine contains nearly all the same components of a fixed Cisco Switches or Routers. These Supervisor engines come in a variety of different types with different functionalities and are installed in the Switches/Router Chassis as per requirements of the network types.

Benefits of Supervisor Engines
By installing Latest Supervisor Engines in your existing investments (Switches and Routers) you can scale system performance and integrate next-generation services into your Networks.
Within a single multilayer switch chassis, two supervisor modules with integrated route processors can be used to provide hardware redundancy. If an entire supervisor module fails, the other module can pick up the pieces and continue operating the switch.
The supervisor engine contains the following integrated daughter cards that perform forwarding and routing and provide the protocols supported …
Post a Comment
Read more

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL https://get.docker.com/ | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.
Post a Comment
Read more

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.
Post a Comment
Read more