December 2017 - Network Kings

SDN tutorial Software-Defined Networking

January 7, 2021December 27, 2017 by Atul

SDN Software Defined Networking

SDN is a Technology which works on manageable networking devices. Devices consist in two parts, one is Data plane and another one is Control plane. Earlier networking devices were tightly coupled (Data Plane & Control Plane) and you could not be asked your vendor to give you data and control plane separately. In tightly coupled devices you cannot make modifications. Because they both are coupled with each other.

To overcome above limitation, SDN technology comes into picture which gives your ability to purchase data Plane and control plane separately. It decouple Data plane & Control plane, now you can design your own application/code (that will write in a programming language like Python, Java etc) as per your requirement and we make that code compatible with control plane and data plane. Now only code decide, device will work like a switch ,like a router(define routing) or a firewall(Security device) .

Note:– Your controller will decide which language you will use for your application.

e.g. :– The physical devices of your computer is like data plane, Operating system is like CLI and if you are making word document then you will need MS- Office (ms-office written in a programming language) . Similarly to make a device working we need a code (written in a language)that code and functions will decide how your device will work .most important your code and platform like CLI should compatible with each other .

Masters in SDN requires networking skills, a good understanding of programming language and O/S knowledge. J

Components of SDN —

Data Plane?Data Plane in networking device works like forwarding plane, which actually forwards the data .e.g physical ports on switch works as data plane . Data plane also known as forwarding device, open flow switch and SDN switch. There is no intelligence in data plane it’s like dummy device.

Control Plane ? Control plane in networking device works like controller .which actually control the flow of data. it’s like IOS (internetwork operating system) of device which runs from CLI(command line interface) mode. control plane also known as SDN controller.

Below earlier networking devices where DATA PLANE and CONTROL PLANE are tightly coupled

Below SDN technology devices, which decouple DATA PLANE and CONTROL PLANE

Communication between data plane and control plane is known as “South Bound Interface” & communication between control plane and application/code known as “North Bound Interface”.

e-.g?In below diagram trying to explain the concept , where train track works like data/physical plane and driver of the train, moreover controller who actually controls the track, works like control plane or SDN controller .

If you are buying a switch or any networking/communication device (manageable) from market that will cost you around Rs.30, 000. That means around 25,000 they are charging for control plane and only 5000 is for physical/data plane. Because control plane actually consist logic/code/rule of statements where physical plane is only your hardware cost.

Hope bit clarity is done about SDN J

Now come into bit inside ?

Physical Data Plane can be purchase from market as describe above. like a dumb hardware device .

Virtual Data Plane ? We have one
emulator called MININET (software) , by using that we can make virtually data plane and put SDN controller over it . Nothing will happen by combining virtual data plane and open source control plane. To make it working we need to build an application in such a programming language.

That application/code will define which device will come. It may come IN SWITCH, IN HUB, IN FIREWALL, IN LOAD BALANCER or in any other device whose code we have defined/designed in our application. INTRESTING

Note — No need to purchase control plane now because we have many open source solutions.

SDN is not fixed functionality. By changing or adding code we can enhance the existing functionality .it helps to manage centralized.

SDN CONTROLLER ?

*Name*	*Language*
NOX	C++
POX(Mainly Use)	PYTHON
BEACON	JAVA
TREMA	RUBY,C
FLOODLIGHT	JAVA
FLOWVISION	C

MININET

It’s an EMULATOR tool, software program which use lightweight virtualization in behind. If your designed code works properly on mininet emulator. It will definitely work well on real physical data plane too. Application run’s smooth on emulator it means your code is good to go and it will work on real environment /hardware without any modification. Topologies of mininet are
Single, Linear, Tree, Minimal, Custom.

CCNA EIGRP Basic Configuration

December 28, 2020December 16, 2017 by Atul

R1(config)#router eigrp 1
R1(config-router)#no auto-summary
R1(config-router)#network 192.168.13.0

R3(config)#router eigrp 1
R3(config-router)#no auto-summary

R1#
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.13.3 (FastEthernet0/0)
is up: new adjacency
R3#
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.13.1 (FastEthernet0/0)
is up: new adjacency
Let?s configure all the network commands so all routers become EIGRP neighbors and advertise
their networks:

R1(config)#router eigrp 1
R1(config-router)#network 192.168.12.0

R3(config)#router eigrp 1
R3(config-router)#network 192.168.34.0

R2(config)#router eigrp 1
R2(config-router)#no auto-summary
R2(config-router)#network 192.168.12.0
R2(config-router)#network 192.168.24.0

R4(config)#router eigrp 1
R4(config-router)#no auto-summary
R4(config-router)#network 192.168.24.0
R4(config-router)#network 192.168.34.0
R4(config-router)#network 4.0.0.0

Check show ip eigrp neighbors on all the devices,

R1#show ip route eigrp
4.0.0.0/24 is subnetted, 1 subnets
D 4.4.4.0 [90/158720] via 192.168.13.3, 00:21:48, FastEthernet0/0
D 192.168.24.0/24 [90/33280] via 192.168.13.3, 00:21:53 FastEthernet0/0
D 192.168.34.0/24 [90/30720] via 192.168.13.3, 00:21:50, FastEthernet0/0

Types of IP Versions

February 22, 2022December 16, 2017 by Atul

How many Types of IP Versions are there?

Internet Protocol Versions —

What happened to IPV1, IPV2, IPV2.5, IPV3, IPV3.1??

Internet Protocol Introduction —

– An IP address is an identifier for a computer or device on a TCP/IP network.

– Protocol (Rules) is a method by which?data/Info?is sent from one computer to another on the?Internet/Network.

Note:- If the PC(Node) is connected to a network as well as the internet ,then the PC will have an Internal (private) IP Address which makes its location on the local network, and on external (Public)IP Address which is the IP address of your internet connection .

History of IP Version —

Earlier the design for TCP was struggling to solve two problems at the same time: how do we establish end to end connectivity/package data, and how do we send that data from one location to another?

TCP version 1 was designed in 1973, TCP version 2 was documented in March
1977. In August 1977, Jon Postel (American? computer scientist) realized they were going the wrong direction with the protocols. Specifically they were trying to use TCP to do two things: serve as a host level end to end protocol, and to serve as a routing protocol. These two things should be provided in a different layeres. Then they decided that a new distinct internetwork protocol (IP) is needed .from here TCP and IP works on different platforms.

TCP(TCP Protocol number 6) be used strictly as a host level end to end protocol on layer 4 of the OSI (Open system Interconnection) Model and layer 3 of the TCP/IP (Transmission Control Protocol)Model .

IP (Internet Protocol) be used as a Routing Protocol at layer 3 of OSI Model and Layer 2 of TCP/IP Model.

There were two major predecessor steps before IP (Internet Protocol) firmed up:

Split between TCP and IP

Variable length addresses were removed, leaving fixed 4-byte(32 bits and 4 Octets) addresses

First TCP and IP split happened , then VLSM removed and size got fixed of 4 Bytes .

IP Versions ?

Version numbers: There are 1,2, 2.5, 3, 3.1 and 4

2.5 was a "implementation split", in which the single header remained same, but the code was split into two TCP and IP . Version 3 was the first version that had the headers fully split (and included "protocol numbers" to identify which transport protocol was being used) but it included variable-length addresses TCP 3 was a paper specification driven by the experience gained from running TCP 2.5.

Version 3.1 had the variable-length addresses removed, and Version 4 was proper cleanup of 3.1 and decided it will announce on Internet to use publically. 18-19 September 1978 meeting notes list the schedule for TCP “Version 4 Ready for testing”.

Stability was added in the (IPV4) fourth revision of Internet protocol that is how we got to IPv4.

Version 1, Version 2 and Version 3 they were the experimental /test versions
of implementation and improved as the internet started to grow. They did not announce for public use because they were in initial growing stage.

IPv5 is Stream Protocol, It was a failed attempt to expand and solve some of IPv4’s problems that’s why it also did not announce publically.

IP Headers?

Before Internet Protocol (IP) Version 3 Headers were not split. In Version 3 they Split into different section/fields.

An?IP header?is a prefix to an IP packet that contains information about the IP version, length of the packet, source and destination IP addresses, etc. It consists of the following fields.