WOW !! MUCH LOVE ! SO WORLD PEACE !
Fond bitcoin pour l'amélioration du site:
1memzGeKS7CB3ECNkzSn2qHwxU6NZoJ8o
Dogecoin (tips/pourboires):
DCLoo9Dd4qECqpMLurdgGnaoqbftj16Nvp
Rechercher sur le site:
Home
|
Publier un mémoire
|
Une page au hasard
Memoire Online
>
Informatique et Télécommunications
>
Sécurité informatique
Design , implementation and management of secured lan
( Télécharger le fichier original )
par
Eliud Ir. Eliud Aganze
Jomokenyatta university of agriculture and technology - B.sc information technology 2014
Disponible en
une seule page
suivant
Copyright
1. Abstract
Dedication
Acknowledgement
List of figures
List of tables
List of Abbreviations
CHAPTER ONE: INTRODUCTION
1.1. Project Overview
1.2. 1.2 Organization structure of JKUAT Karen Campus
Figure 1.1: Organization structure of JKUAT Karen
1.3 Main objectives of project
1.4 General description of the project process
1.3. 1.4.1 The statement of problem
1.4.2 Proposed solution
1.5 Project Schedule
CHAPTER TWO: METHODOLOGY
2.0 Methodology
2.1 Research Methodology
2.2 Research Questions
1.4. 2.3 Purpose of the Research
2.4 Research Techniques/ methods used
2.5 Research Technique used
2.5 Project methodology
1.5. 2.5.1 System Development Life Cycle approach Methodology
Figure 2.2: System Development Life Cycle approach
Phase 1:Investigation
Phase 2: Analysis
Phase 3: Design
Phase 4: Simulation
1.6. 2.5.2 Top-Down Network Design Methodology
1.7. 2.5.3 Plan, Design, Implement, Operate, and Optimize (PPDIOO) methodology
Figure 2.3. PPDIOO Network Lifecycle Influences Design
Benefits of the Lifecycle Approach to Network Design
2.5 Project Requirement specification
1.8. 2.5.1 Software requirement
1.9. 2.5.2 Hardware requirement
2.5.3 Operation System
CHAPTER THREE: LITERATURE REVIEW
1.10. 3.1 Introduction
3.2 LAN (local area network)
1.11. 3.2.1. Peer-to-Peer Networks
1.12. 3.2.2 Server-Based Networks
1.13. 3.3 LAN Design
3.4 LAN Installation
3.5 LAN Security
CHAPTER FOUR: SYSTEM ANALYSIS
2. Introduction
4.1 System analysis activities
4.1.0 The importance of system analysis:
4.2 Requirement analysis
2.1. 4.3.0 Identification of LAN design requirement
2.2. 4.3.1 Equipment features
4.3.2 Design Redundancy
4.4 Existing Network
4.4.1 Current Network equipment
4.4.2 Physical configuration state
Figure 4.1: JKUAT Karen network building
Figure 4.2: physical network building
4.4.3 Network design topology
2.3. 4.4.3.1 Star topology
2.4. 4.4.3.2 Bus topology
2.5. 4.4.3.3 Ring topology
2.6. 4.4.3.4 Flat Network
Table of advantages and disadvantages
Table 4.1. Comparison between network topologies
Figure 4.3. Flat network
2.7. 4.4.3.5 Hierarchical network
Figure 4.4. Hierarchical design
Table comparison between hierarchical and flat network designFlat Network Hierarchical NetworkAdvantages
Table 4.2. Comparisons between hierarchical and flat network design
2.8. 4.4.4 Currentnetwork design problem
Figure 4.5. Current network design
2.9. 4.4.4.1 Logical configuration state
Figure 4.6. Current logical design
2.10. 4.4.5. Network addressing Schema and Naming
Figure 4.7: Addressing schema
4.4.5.1 Auditing the existing Network
2.11. 4.4.5.2 Existing network Management
4.4.6 System analysis of the current Network Management
4.4.6.1 How the current network is managed
4.4.6.2 Flowchart of the current network management
Figure 4.8: flowchart diagram of existing system
4.4.6.3 Weakness of the current system
4.4.6.4 Proposed Solution to the current system problem:
Figure 4.9. Flowchart of the proposed system
Figure 4.10. Activity diagram of the proposed system
4.4.6.5 Analysis of network traffic
Figure 4.11: network traffic and protocols
Figure4.12: Jkuat karen network traffic and protocols
4.4.6.6 Strength of the current network:
4.4.6.7 Weakness of the current network:
4.4.7 Proposed system
2.12. 4.4.7.0 Physical design
Figure4.13. Proposed physical design
4.4.7.1 Logical design
Figure 4.14. Proposed logical design
4.4.7.1 Proposed security strategies
2.13. 4.4.7.2Proposed Management strategies
2.14. 4.4.7.3 Proposed WAN
Figure 4.15. Proposed WAN
2.15. 4.4.7.4 Proposed Address schema
Table 4.1: Address Schema
4.4.7.5 General Merits of proposed system
CHAPTER FIVE: NETWORK DESIGN
2.16. 5.0. Definition
2.17. 5.1. Design principals
Figure 5.1: illustration of PDIOO
Figure 5.2: illustrate the tasks
2.18. 5.2 logical network topology
Figure 5.3: JKUAT LAN logical design
2.19. 5.2.1 Flat versus Hierarchical Topologies
2.20. 5.2.1.0 Flat network topology
Figure 5.4: Flat network design
2.20.1.1. 5.2.1.1 Hierarchical Design Model
Figure 5.5: Hierarchical design for JKUAT Karen Campus
i. Access Layer
Device Connectivity
Figure 5.6: device connectivity of JKUAT LAN Campus
1. Switches used in access layer
ii. Distribution Layer
Figure 5.7: distribution layer JKUAT LAN Campus
iii. Core Layer
Figure 5.8: JKUAT LAN core layer
5.3 Switching technologies
2.21. 5.3.0Spanning Tree Protocol (STP)
Figure5.9: Spanning tree illustration in Switching
5.3.1 VLAN (Virtual Local Area Network)
Figure 5.10: illustration of VLANs in JKUAT Karen's LAN
Figure 5.11: trunk port between switches
2.22. 5.3.2Designing Models for Addressing and Numbering
2.23. 5.3.2.0 Static and Dynamic Addressing for End Systems
2.24. 5.3.2.1 Hierarchical Routing
2.25. 5.3.2.2 IP address subnetting
2.26. 5.3.2.2.0 VLANS
Table 5.1: VLAN table
2.27. 5.3.2.2.1 VLANS IP address
Table 5.2: VLAN IP address
2.28. 5.3.2.2.3 Point to pint IP address
Table 5.3: point to point router IP address
2.29. 5.3.1.2.4 DNS and DHCP server IP address
Table 5.4: DNS and DHCP IP address
2.30. 5.3.3 Network security and management design
2.31. 5.4.0 System design of Jkuat network management online
2.32. 5.4.0.1 Introduction
5.4.0.2 UML Diagrams
2.33. 5.4.0.2.0 Use case diagrams
Figure 5.12: use case diagram of administrator
Figure 5.13: use case diagram of jkuat network mngt system online
Figure 5.14: use case diagram of administrator
5.4.0.2.1 Activity diagrams
Figure 5.15: activity diagram of jkuat network mngt system online
Figure 5.16: activity diagram of administrator
5.4.0.2.2 Sequence diagrams
Figure 5.17: sequence diagram for administrator
Figure 5.17: sequence diagram for user
5.4.0.2.3 Class Diagrams
Figure 5.18: class diagram of jkuat network mngt system online
5.4.0.3 Database design
5.4.0.3.0 Design process
2.34. 5.4.0.3.1 Normalization
2.35. 5.4.0.3.3 Process of normalization
Figure5.20: full dependency
5.4.0.2 Database Schema Tables
5.4.0.3 Entity relationship diagram (ERD)
Figure 5.21: ERD diagram
5.4.0.4 Interface design
5.4.1 Good interface design
Figure 5.22: interface design
Figure 5.23. Home page
Figure 5.24. Login Page
Figure 5.26. Problem
Figure 5.27. Solution and comment
Figure 5.28: FAQ
6.1 Coding
6.2 User Interface
Login Page
Figure 6.0: login form
Figure 6.1: home Page
Figure 6.2: solution form
Figure 6.3: problem Page Screenshot.
Figure 6.4: view problem
Figure 6.5: Employee page.
Figure 6.6: Network Schema
Figure 6.7: Student computer DHCP
Figure 6.8: Lecture computer DHCP
Figure 6.9: Show interface route from Director Switch
Figure 6.10: Access control list Director Router
Figure 6.11: Access control list and login
Figure 6.12: Telnet and ping IP address
Figure 6.13: Spanning tree configuration
Figure 6.14: Ping IP address
6.3 System testing
6.2.1 Methods / Types of Testing
6.2.1.1 Functional testing
6.2.1.2 White Box Testing
6.2.2 The Testing Process
6.2.2.1 Test Data
Table 6.1: Test Data
6.2.2.2 Tests Justification
6.4 System implementation
6.4.1 System change over
6.4.1.1 Parallel running
6.4.1.2 Direct changeover
6.4.1.3 Pilot running
6.4.1.4 Phased changeover
6.5 Changeover Technique Used
6.6 Chosen strategy
CHAPTER SEVEN: PROJECT APPRAISAL
7.1 Objectives met
7.2 Achievements
7.1.1 System Achievement
7.1.2 Personal Achievement
7.2 Limitations/ shortcomings encountered.
3. Conclusion
7.3 Recommendations
References
16. Appendix
1. Interview Questions
Table 3: Interview Questions
4. Source codes
4.1. Login. Php
4.2. Db.php
suivant
Rechercher sur le site:
"Soit réservé sans ostentation pour éviter de t'attirer l'incompréhension haineuse des ignorants"
Pythagore