Project Report PDF
Project Report PDF
Project report submitted in partial fulfillment of the requirement for the award of the
degree of
Bachelor of Technology
Patience and preservation is the part and parcel to make fulfill any desired motto
successfully. Not only this two indispensable characters but also kind co-operation and zestful
help are always required by dint of which one can be able to reach his\her ultimate goal after
passing through a series of several incidents.
I am profoundly grateful to Mr. Ved Prakash, Head of Department, Computer Science
and Engineering for his expert guidance and continuous encouragement throughout to see that
this project rights its target.
I would like to express deepest appreciation towards Dr. Sanjay Dahiya, Assistant
Professor, Computer Science and Engineering Department whose invaluable supervision
supported me in this project.
At last I must express my sincere heartfelt gratitude to all the staff members of Computer
Engineering Department who helped me directly or indirectly during this course of work.
Gourav Kant
i
ABSTRACT
ii
Ch. Devi Lal State Institute of Engineering and Technology
Panniwala Mota (Sirsa)-125077 (Haryana)
Ph. No. 01668-277597 Fax No. 01668-277598
Website: www.cdlmgec.org
DECLARATION
I hereby declare that the Major Project Report entitled “Network Architecture Of The
College” submitted by me to the Computer Science and Engineering Department, Ch. Devi Lal
State Institute of Engineering and Technology, Panniwala Mota, Sirsa in partial fulfilment of the
requirement for the award of the degree of Bachelor of Technology in Computer Science and
Engineering is a bonafide project work carried out by me under the supervision of Mr. Ved
Prakash, Head of Department, Computer Science and Engineering Department.
I further declare that the work reported in this project has not been submitted and will
not be submitted, either in part or in full, for the award of any other degree or diploma in this
institute or any other institute or university.
Gourav Kant
1311151913
iii
Ch. Devi Lal State Institute of Engineering and Technology
Panniwala Mota (Sirsa)-125077 (Haryana)
Ph. No. 01668-277597 Fax No. 01668-277598
Website: www.cdlmgec.org
CERTIFICATE
This is to certify that the Project Report entitled “Network Architecture Of The
College” that is being submitted by Mr. Gourav Kant (Roll No. 1311151913) for the award of
Bachelor of Technology degree in Computer Science and Engineering to the Guru Jambheshwar
University of Science & Technology, Hisar, is a Project Work carried out by him under the
supervision and guidance of Mr. Ved Parkash, Head of Department, Computer Science and
Engineering, Ch. Devi Lal State Institute of Engineering and Technology, Panniwala Mota
(Sirsa). This is to further certify that he is a bonafide student of this State Institute of Engineering
and Technology.
iv
CONTENTS
Page No:
Acknowledgement i
Abstract ii
Declaration iii
Certificate iv
Contents
5. Chapter 5 - Project Work 22 -25
5.1. Network Connectivity 22
5.2. Connectivity of Network Floor-wise 23
5.2.1. Ground Floor
5.2.2. First Floor
5.2.3. Second Floor
6. Chapter 6 - Snapshot 26 - 35
6.1. Configuration 26
6.1.1. Configuration Of Router
6.1.2. Configuration Of DHCP Server
6.1.3. Configuration Of Access Point
6.1.4. Configuration Of Switch
6.2. Assigning IP Address 36
6.3. Designed Architecture 38
6.4. Project Details 43
References 45
Contents
CHAPTER 1 – INTRODUCTION0 TO PROJECT
1.1. INTRODUCTION
The information processing services are growing at an exponential rate. Network based
resources such as E-mail, client server, scheduling and discussion databases have reached
mission critical status on a global enterprise level. These network services must be robust and
fault tolerant to meet business demands. It is imperative that the underlying network
infrastructure carrying voice, data and video technologies support this growing demand now and
in the future.
The goal of this project is to provide an architecture strategy that will enable us o have an open
interoperable network. The architecture will provide a guideline that will allow for reusability of
technologies, economies of scale and support efficiencies.
Most of the commercial simulators are GUI driven, while some network simulators
are CLI driven. The network model / configuration describes the state of the network (nodes,
routers, switches, links) and the events (data transmissions, packet error etc.). An important
output of simulations are the trace files. Trace files log every packet, every event that occurred in
the simulation and are used for analysis. Network simulators can also provide other tools to
facilitate visual analysis of trends and potential trouble spots.
Most network simulators use discrete event simulation, in which a list of pending "events" is
stored, and those events are processed in order, with some events triggering future events—such
as the event of the arrival of a packet at one node triggering the event of the arrival of that packet
at a downstream node.
Simulation of networks is a very complex task. For example, if congestion is high, then
estimation of the average occupancy is challenging because of high variance. To estimate the
likelihood of a buffer overflow in a network, the time required for an accurate answer can be
extremely large. Specialized techniques such as "control variates" and "importance sampling"
have been developed to speed simulation
1
1.2. NETWORK EMULATION
A network emulator allows users to introduce real devices and applications into a test
network (simulated) that alters packet flow in such a way as to mimic the behavior of a live
network. Live traffic can pass through the simulator and be affected by objects within the
simulation.
The typical methodology is that real packets from a live application reach the emulation server
(where the virtual network is simulated. The real packet gets modulated into a simulation packet.
The Simulation packet gets demodulated into real packet after experiencing effects of loss,
errors, delay, jitter etc., thereby transferring these network effects into the real packet. Thus it is
as-if the real packet flowed through the real networks but in reality it flowed through the
simulated network.
Emulation is widely used in the design stage for validating communication networks prior to
deployment.
There are a wide variety of network simulators, ranging from the very simple to the very
complex. Minimally, a network simulator must enable a user to
1. Model the network topology specifying the nodes on the network and the links between
those nodes
2. Model the application flow (traffic) between the nodes
3. Providing network performance metrics as output
4. Visualization of the packet flow
5. Technology / protocol evaluation and device designs
6. Logging of packet / events for drill down analyses / debugging
2
1.3. COMPUTER NETWORK
Properties
Computer networking may be considered a branch of electrical
engineering, telecommunications, computer science, information technology or computer
engineering, since it relies upon the theoretical and practical application of the related
disciplines.
A computer network facilitates interpersonal communications allowing users to
communicate efficiently and easily via various means: email, instant messaging, chat rooms,
telephone, video telephone calls, and video conferencing. Providing access to information on
shared storage devices is an important feature of many networks. A network allows sharing of
files, data, and other types of information giving authorized users the ability to access
information stored on other computers on the network.
A network allows sharing of network and computing resources. Users may access and use
resources provided by devices on the network, such as printing a document on a shared network
printer. Distributed computing uses computing resources across a network to accomplish tasks. A
computer network may be used by computer crackers to deploy computer viruses or computer
worms on devices connected to the network, or to prevent these devices from accessing the
network via a denial of service attack.
3
CHAPTER 2 - TOOLS
This section would tell you about the tools you need to develop this software.
4
5
2.1.1. Overview
Packet Tracer is a cross-platform network simulator designed by Cisco Systems to run on
Mac OS, Linux and Microsoft Windows. A similar Android app is also available. Packet Tracer
allows users to create simulated network topologies by dragging and dropping routers, switches
and various other types of network devices. A physical connection between devices is
represented by a "cable" item. Packet Tracer supports an array of simulated Application Layer
protocols, as well as basic routing with RIP, OSPF, EIGRP, BDP, to the extents required by the
current CCNA curriculum. As of version 5.3, Packet Tracer also supports the Border Gateway
Protocol.
Version 6.0 added support for IOS version 15 and Hot Standby Routing Protocol. Version 6.1.1
added support for various DHCP, EIGRP and OSPF commands, improved support for Zone-
Based Firewall policies. As of version 6.2, Packet Tracer supports an embedded web server with
JavaScript and CSS support. The command line can be used for creating a router-to-pc
connection.
6
2.2. DEVICES AND CABLES THAT WILL BE USED
In this section we will study about all the Devices and Cables we need to develop this
network Architecture.
7
3. Bridges
A network bridge connects and filters traffic between two network segments at the data
link layer (layer 2) of the OSI model to form a single network. This breaks the network's
collision domain but maintains a unified broadcast domain. Network segmentation breaks down
a large, congested network into an aggregation of smaller, more efficient networks.
Bridges come in three basic types:
4. Switches
A network switch is a device that forwards and filters OSI layer 2 datagrams (frames)
between ports based on the destination MAC address in each frame. A switch is distinct from a
hub in that it only forwards the frames to the physical ports involved in the communication rather
than all ports connected. It can be thought of as a multi-port bridge.[10] It learns to associate
physical ports to MAC addresses by examining the source addresses of received frames. If an
unknown destination is targeted, the switch broadcasts to all ports but the source. Switches
normally have numerous ports, facilitating a star topology for devices, and cascading additional
switches.
Multi-layer switches are capable of routing based on layer 3 addressing or additional logical
levels. The term switch is often used loosely to include devices such as routers and bridges, as
well as devices that may distribute traffic based on load or based on application content (e.g., a
Web URL identifier).
5. Routers
A typical home or small office router showing the ADSL telephone line and Ethernet
network cable connections
8
6. Modems
Modems (MOdulator-DEModulator) are used to connect network nodes via wire not
originally designed for digital network traffic, or for wireless. To do this one or more carrier
signals are modulated by the digital signal to produce an analog signal that can be tailored to
give the required properties for transmission. Modems are commonly used for telephone lines,
using a Digital Subscriber Line technology.
7. Firewalls
A firewall is a network device for controlling network security and access rules. Firewalls
are typically configured to reject access requests from unrecognized sources while allowing
actions from recognized ones. The vital role firewalls play in network security grows in parallel
with the constant increase in cyber attacks.
Networking cables are networking hardware used to connect one network device to other
network devices or to connect two or more computers to share printers, scanners etc. Different
types of network cables, such as coaxial cable, optical fiber cable, and twisted pair cables, are
used depending on the network's physical layer, topology, and size.
There are several technologies used for network connections. Patch cables are used for short
distances in offices and wiring closets. Electrical connections using twisted pair or coaxial
cable are used within a building.
1. Twisted Pair
Twisted pair cabling is a form of wiring in which pairs of wires (the forward and return
conductors of a single circuit) are twisted together for the purposes of canceling
out electromagnetic interference (EMI) from other wire pairs and from external sources. This
type of cable is used for home and corporate Ethernet networks. Twisted pair cabling is used in
short patch cables and in the longer runs in structured cabling.
2. Fiber Optic
An optical fiber cable consists of a center glass core surrounded by several layers of
protective material. The outer insulating jacket is made of Teflon or PVC to prevent interference.
Optical fiber deployment is more expensive than copper but offers higher bandwidth and can
cover longer distances. There are two major types of optical fiber cables: short-range multi-mode
fiber and long-range single-mode fiber.
9
3. Coaxial Cable
Coaxial cables confine the electromagnetic wave inside the cable, between the center conductor
and the shield. The transmission of energy in the line occurs totally through the dielectric inside
the cable between the conductors. Coaxial lines can therefore be bent and twisted (subject to
limits) without negative effects, and they can be strapped to conductive supports without
inducing unwanted currents in them.
Although in most homes coaxial cables have been installed for transmission of TV signals, new
technologies (such as the ITU-T G.hn standard) open the possibility of using home coaxial cable
for high-speed home networking applications (Ethernet over coax).
In the 20th century they carried long distance telephone connections.
4. Patch Cable
A patch cable is an electrical or optical cable used to connect one electronic or optical
device to another or to building infrastructure for signal routing. Devices of different types (e.g. a
switch connected to a computer, or a switch connected to a router) are connected with patch
cords. Patch cords are usually produced in many different colors so as to be easily
distinguishable, and most are relatively short, no longer than a few meters. In contrast to on-
premises wiring, patch cables are more flexible but may also be less durable.
10
CHAPTER 3 - LITERATURE REVIEW
This chapter will mainly discuss on the study that are done by previous research of other
authors in the similar area of the present study. Throughout this chapter, there will be
comprehensive discussion on theoretical and practical views of previous studies done in Network
Simulation and network simulator. This study combines factors that other studies have done that
will tell us about network simulation. It includes the price attractiveness, time saving, perceived
risk, tangibility and high interactivity.
Packet Tracer allows students to design complex and large networks, which is often not
feasible with physical hardware, due to costs. Packet Tracer is commonly used by CCNA
Academy students, since it is available to them for free. However, due to functional limitations,
it is intended by Cisco to be used only as a learning aid, not a replacement for
Cisco routers and switches. The application itself only has a small number of features found
within the actual hardware running a current Cisco IOS version. Thus, Packet Tracer is
unsuitable for modeling production networks. It has a limited command set, meaning it is not
possible to practice all of the IOS commands that might be required.
Packet Tracer can be useful for understanding abstract networking concepts, such as
the Enhanced Interior Gateway Routing Protocol by animating these elements in a visual
form. Packet Tracer is also useful in education by providing additional components, including an
authoring system, network protocol simulation and an assessment system.
Time Saving
Time is also perceived as one of a factor that relates with the networking context. It is
believed that every employs have own perception of time, whether or not to work while failure.
It is more difficult to find the error in whole network of an organization, because there are many
devices and the cables so that is too default to go to each device one by one and check all the
configuration of each devices, sometimes devices are working properly but connections are not
working properly so you don’t get the error is in the device or in the connection or it may not be
the devices or may not in the connections , it may be in the connecting media’s.
So using network architecture for simulation and finding errors easily because it provide a
centralized view of a whole network. Through which the applying the correction method effect
may be observed. And it also useful for the making changes, because making change in the
network directly we can firstly apply in the network architecture, and see the it is suitable or
acceptable to the network.
Sometimes you apply some changes to the network it will not compatible to the network
resultantly it effect the performance of the network, of may be the developer are applying change
to the network and one of the device connected to the same network stop working then the whole
network is affected.
11
3.1. HISTORY
The chronology of significant computer-network developments includes:
∑ In the late 1950s, early networks of computers included the military radar system Semi-
Automatic Ground Environment (SAGE).
∑ In 1959, Anatolii Ivanovich Kitov proposed to the Central Committee of the Communist
Party of the Soviet Union a detailed plan for the re-organisation of the control of the Soviet
armed forces and of the Soviet economy on the basis of a network of computing centres.
∑ In 1960, the commercial airline reservation system semi-automatic business research
environment (SABRE) went online with two connected mainframes.
∑ In 1962, J.C.R. Licklider developed a working group he called the "Intergalactic Computer
Network", a precursor to the ARPANET, at the Advanced Research Projects
Agency(ARPA).
∑ In 1964, researchers at Dartmouth College developed the Dartmouth Time Sharing
System for distributed users of large computer systems. The same year, at Massachusetts
Institute of Technology, a research group supported by General Electric and Bell Labs used a
computer to route and manage telephone connections.
∑ Throughout the 1960s, Leonard Kleinrock, Paul Baran, and Donald Davies independently
developed network systems that used packets to transfer information between computers
over a network.
∑ In 1965, Thomas Marill and Lawrence G. Roberts created the first wide area
network (WAN). This was an immediate precursor to the ARPANET, of which Roberts
became program manager.
∑ Also in 1965, Western Electric introduced the first widely used telephone switch that
implemented true computer control.
∑ In 1969, the University of California at Los Angeles, the Stanford Research Institute,
the University of California at Santa Barbara, and the University of Utah became connected
as the beginning of the ARPANET network using 50 kbit/s circuits.[3]
∑ In 1972, commercial services using X.25 were deployed, and later used as an underlying
infrastructure for expanding TCP/IP networks.
∑ In 1973, Robert Metcalfe wrote a formal memo at Xerox PARC describing Ethernet, a
networking system that was based on the Aloha network, developed in the 1960s by Norman
Abramson and colleagues at the University of Hawaii. In July 1976, Robert
Metcalfe and David Boggs published their paper "Ethernet: Distributed Packet Switching for
Local Computer Networks" and collaborated on several patents received in 1977 and 1978.
In 1979, Robert Metcalfe pursued making Ethernet an open standard.
∑ In 1995, the transmission speed capacity for Ethernet increased from 10 Mbit/s to 100
Mbit/s. By 1998, Ethernet supported transmission speeds of a Gigabit. Subsequently, higher
speeds of up to 100 Gbit/s were added (as of 2016). The ability of Ethernet to scale easily
(such as quickly adapting to support new fiber optic cable speeds) is a contributing factor to
its continued use.
12
3.2. NETWORK PACKET
A network packet is a formatted unit of data carried by a packet-switched network.
Computer communications links that do not support packets, such as traditional point-to-point
telecommunications links, simply transmit data as a bit stream. When data is formatted into
packets, packet switching is possible and the bandwidth of the communication medium can be
better shared among users than with circuit switching.
A packet consists of control information and user data, which is also known as the payload.
Control information provides data for delivering the payload, for example: source and
destination network addresses, error detection codes, and sequencing information. Typically,
control information is found in packet headers and trailers.
3.3. TOPOLOGY
The cabling layout used to link devices is the physical topology of the network. This
refers to the layout of cabling, the locations of nodes, and the interconnections between the nodes
and the cabling.[1] The physical topology of a network is determined by the capabilities of the
network access devices and media, the level of control or fault tolerance desired, and the cost
associated with cabling or telecommunications circuits.
In contrast, logical topology is the way that the signals act on the network media, or the way that
the data passes through the network from one device to the next without regard to the physical
interconnection of the devices. A network's logical topology is not necessarily the same as its
physical topology. For example, the original twisted pair Ethernet using repeater hubs was a
logical bus topology carried on a physical star topology. Token ring is a logical ring topology,
but is wired as a physical star from the media access unit. Logical topologies are often closely
associated with media access control methods and protocols. Some networks are able to
dynamically change their logical topology through configuration changes to their routers and
switches.
13
3.3.2. Types Of Topologies
1. Bus Topology – It is defined by the use of a single main cable which has terminators on
both ends. All the other nodes like workstations, peripherals, etc. are connected to this
main cable. This type of topology is widely implemented in LANs as it is easy to install
and does not cost much. It also does not require much cabling as in the case of some
other topologies like star and mesh. The main disadvantage of this topology is that the
entire network is dependent on the main cable. In case some problem occurs in the main
cable, the whole system gets affected.
2. Star Topology – It is named as star topology as it looks similar to a star whereas all the
elements of the network are primarily connected to a central device. This central device is
known as hub and can be either of a hub, router or a switch. This central hub also works
as a repeater for data flow. A point-to-point connection is laid between the devices and
the central hub. Thus, all nodes are connected to each other only by the assistance of this
central hub. Installation and wiring is easy of star topology. The functioning of the entire
system depends on the central hub.
14
3. Ring Topology – It is in a shape similar to a ring, in which every node is connected to
only two neighbors. The messages move in only one and the same direction in this
arrangement. In case any cable or device breaks away from the loop, then it can be a fatal
problem for the entire network. Token ring technology is used to implement this type of
topology. It can be used for handling high volume of data. All devices are given the same
importance in this topology. In case the capacity is increased beyond its comfortable limit
then the network starts to compromise on speed.
15
5. Mesh Topology – In this type of arrangement every node participating in the network is
connected to every other node. However, this tends to be very expensive and difficult to
implement. Multiple paths are can be used for transmitting a message. Due to the
presence of dedicated links, it does not provide any traffic problem. The management of
this arrangement is tricky due to heavy wiring. The system is configured in such a way
that data takes the shortest path for reaching to its destination. Fault identification is also
easy in this type of topology.
16
3.4. NETWORK ARCHITECTURE
The Open Systems Interconnection model (OSI model) is a conceptual model that
characterizes and standardizes the communication functions of a telecommunication or
computing system without regard to their underlying internal structure and technology. Its goal is
the interoperability of diverse communication systems with standard protocols. The model
partitions a communication system into abstraction layers. The original version of the model
defined seven layers.
A layer serves the layer above it and is served by the layer below it. For example, a layer that
provides error-free communications across a network provides the path needed by applications
above it, while it calls the next lower layer to send and receive packets that comprise the contents
of that path. Two instances at the same layer are visualized as connected by
a horizontal connection in that layer.
OSI had two major components, an abstract model of networking, called the Basic Reference
Model or seven-layer model, and a set of specific protocols.
The concept of a seven-layer model was provided by the work of Charles Bachman at
Honeywell Information Services. Various aspects of OSI design evolved from experiences with
the ARPANET, NPLNET, EIN, CYCLADES network and the work in IFIP WG6.1. The new
design was documented in ISO 7498 and its various addenda. In this model, a networking system
was divided into layers. Within each layer, one or more entities implement its functionality. Each
entity interacted directly only with the layer immediately beneath it, and provided facilities for
use by the layer above it.
17
3.4.2. OSI Model Seven Layers
1. Physical (Layer 1)
OSI Model, Layer 1 conveys the bit stream - electrical impulse, light or radio signal through
the network at the electrical and mechanical level. It provides the hardware means of sending and
receiving data on a carrier, including defining cables, cards and physical aspects. Fast
Ethernet, RS232, and ATM are protocols with physical layer components.
2. Layer 1 Physical examples include Ethernet, FDDI, B8ZS, V.35, V.24, RJ45.
3. Network (Layer 3)
Layer 3 provides switching and routing technologies, creating logical paths, known
as virtual circuits, for transmitting data from node to node. Routing and forwarding are functions
of this layer, as well as addressing, internetworking, error handling, congestion control and
packet sequencing.
4. Layer 3 Network examples include AppleTalk DDP, IP, IPX.
4. Transport (Layer 4)
Layer 4, provides transparent transfer of data between end systems, or hosts, and is
responsible for end-to-end error recovery and flow control. It ensures complete data transfer.
5. Layer 4 Transport examples include SPX, TCP, UDP.
5. Session (Layer 5)
This layer establishes, manages and terminates connections between applications. The
session layer sets up, coordinates, and terminates conversations, exchanges, and dialogues
between the applications at each end. It deals with session and connection coordination.
6. Layer 5 Session examples include NFS, NetBios names, RPC, SQL.
6. Presentation (Layer 6)
This layer provides independence from differences in data representation
(e.g., encryption) by translating from application to network format, and vice versa. The
presentation layer works to transform data into the form that the application layer can accept.
This layer formats and encrypts data to be sent across a network, providing freedom from
compatibility problems. It is sometimes called the syntax layer.
7. Layer 6 Presentation examples include encryption, ASCII, EBCDIC, TIFF, GIF, PICT,
JPEG, MPEG, MIDI.
18
7. Application (Layer 7)
OSI Model, Layer 7, supports application and end-user processes. Communication
partners are identified, quality of service is identified, user authentication and privacy are
considered, and any constraints on data syntax are identified. Everything at this layer is
application-specific. This layer provides application services for file transfers, e-mail, and
other network software services. Telnet and FTP are applications that exist entirely in the
application level. Tiered application architectures are part of this layer.
v Layer 7 Application examples include Web browsers, NFS, SNMP, Telnet, HTTP, FTP.
19
CHAPTER 4 – OBJECTIVES AND REQUIREMENT SPECIFICATIONS
4.1. OBJECTIVES
Objectives are the primary goals which are supposed to be achieved by the software project.
Objectives of developing this system are:-
v To display the whole network of the organization, which helps to manage and making
changes in it.
v To setup a real time communication system which offers one to one and one to many
mode.
Before you begin with any kind of development activity it is necessary to look at what
problems exists or simply reasons for such development. If these problems are clear than
only we can duce an effective design which would be able to solve our problems successful.
Main problems for what we are developing this website are:-
v Unique access to information system
v Authority to access information in accordance to user
v Manage privacy by a single user
v Authorize user to modify the network
v Only one user can access the network at a time
20
4.3. REQUIREMENT SPECIFICATIONS
These are the minimum configuration required in your system to run this website.
21
CHAPTER 5 – PROJECT WORK
22
5.2. CONNECTIVITY OF NETWORK FLOOR-WISE
1. DIRECTOR OFFICE
2. ACADMIC OFFICE
3. ACCOUNTS OFFICE
4. EXAM BRANCH/OFFICE
5. LIBRARY
6. LAB 101, LAB 102
7. Room No. - 104, 120, 121, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 140.
1. SWITCHS ----- 03
2. ACCESS POINTS ----- 03
23
5.2.2. First Flour
1. SWITCHS ----- 01
24
5.2.3. Second Flour
1. SERVER ----- 01
2. ROUTER ----- 01
3. MODEM ----- 01
4. SWITCHS ----- 03
25
CHAPTER 6 – SNAPSHOT
6.1. CONFIGURATION
int f 0/0
ip address 192.168.10.9 255.255.255.0
no shutdown
int f 0/1
ip address 172.100.10.0 255.255.0.0
no shutdown
6. These commands will assign 192.168.10.9 IP to interface 0/0 with 255.255.255.0 subnet
mask and 172.100.10.1 IP to interface 0/1 with 255.255.0.0 subnet mask.
26
27
28
29
v Steps to configure Router using GUI
1. Double click on Router 309-01, a pop-up window will appear with four tabs namely
Physical, Config, CLI (Command Line Interface).
2. Click on Config, a window will appear with configuration.
3. Now select FastEthernet 0/0 and enter IP Address = 192.168.10.9 and Subnet Mask =
255.255.255.0 and then select FastEthernet 0/1 and enter IP Address = 172.100.10.2 and
Subnet Mask = 255.255.0.0
4. After entering the IP Address and Subnet Mask close the window.
30
6.1.2. CONFIGURATION OF DHCP SERVER
31
32
6.1.3. CONFIGURATION OF ACCESS POINT
1. Double click on Access Point-01, a pop-up window will appear with two tabs namely
Physical and Config.
2. Click on Config, a window will appear with Access Point configuration.
3. Select INTERFACE and then click on Port 0.
4. When you click on Port 0, Port 0 setting will appear which contains Port Status,
Bandwidth and Duplex.
5. Turn Port Status ON, select Bandwidth and Duplex also.
6. Now click on Port 2.
7. When you click on Port 0, Port 0 setting will appear which contains Port Status, SSID,
Channel, Authentication and Encryption Type.
8. Turn Port Status ON, enter SSID, select Channel and Authentication and enter Key or
Pass Phrase according to Authentication.
9. After entering such details select Encryption Type.
PORT 0
Port Status ON
Bandwidth 100Mbps
Duplex Full Duplex
PORT 1
SSID CDLSIDT
Channel 10
Authentication WAP-2 PSK
Pass Phrase cdlsiet.01 (For Access point-01)
Encryption Type AES
33
34
6.1.4. CONFIGURATION OF SWITCH
35
6.2. ASSIGNING IP ADDRESS
36
ÿ Assigning IP to the computers ( Nodes ) of LAB 206
37
6.3. DESIGNED ARCHITECTURE
38
6.3.2. Ground Floor
Block A
39
Block B
40
6.3.3. First Floor
41
6.3.4. Second Floor
42
6.4. PROJECT DESCRIPTION
43
CHAPTER 7 - CONCLUSION AND FUTURE SCOPE
In this chapter we may study about the whole conclusion of development activity of the
system. It will indicate the outcome of whole project report. Whereas future scope would provide
the idea of future implementations.
7.1. CONCLUSION
In this section we may talk about what we concluded from this project report.
Conclusion points of this report are:-
v Updating and modifying the n/w architecture so that helps to find the errors easily
and location of getting error will become easy.
v The benefits of network architecture is that by having direct access to developer.
v CLI is only the interface from where the router can be established and coded.
v Improve the network efficiency without changing the hardware.
Every developer has a vision to look forward about the future of its current Network or a
Network Architecture. He had not implements some feature in application due to some
acceptability issues. But in future he can as those issues could be vanished or neglected.
Future scope related to Skedaddle are:-
v Add some new devices if any one of net working properly due to the heavy load.
44
REFERENCES
Web Sites
https://learn-networking.com
https://learningnetwork.cisco.com
http://static-pt-assets.s3.amazonaws.com/tutorials70.htm
http://www.cisco.com/c/en/us/training.html
45