Network Design and Implementation: Principles and Methodologies, Study notes of Java Programming

Download Network Design and Implementation: Principles and Methodologies and more Study notes Java Programming in PDF only on Docsity!

Contents

Declaration

We are Information Technology students at Ambo University, and we verify that this internship report was originally prepared for us at Dasheen Bank Nekemte Branch. When preparing this report we used the detailed works covered which we performed in Dasheen Bank Nekemte Branch ICT-Center, observed during our training, and actually worked based on daily, weekly and monthly work, during the training program with our teammates.

Acknowledgment

We would like to start by thanking our grateful gratitude for the almighty of God for making us stronger which a difficult time that we faced, and keeping us safe and joyful during our internship training. Also, we would like to give our delightful gratitude to Mr. Abdi Sitota who has provided us with the necessary attendance, support, and information needed to complete this internship report. Finally we would like to thank every group member of our internship training for being punctual and helpful throughout the internship training.

Chapter One

1.1 Introduction

Users within Dasheen Bank have been experiencing unnecessary outages and connectivity issues which seem to be getting worse over time. Often network services go down, without backup options in place. This causes the company as a whole to suffer a loss in productivity, revenue, and man hours. After deliberation, the decision was taken to expand Dasheen Bank’s footprint by redesigning the network while adding scope to create some redundancy with new hardware and WAN links, optimizing the traffic flow, and reducing data traffic congestion between sites. Dasheen Bank has expanded into multiple sites across the country, and now its size and status from a user and network perspective will have to be redefined. The main emphasis of this study will follow the PIDOO methodology concerning the layer two and layer three devices, the physical connectivity between servers and users, connectivity between Dasheen Bank’s main data centre, external sites and partners, and possible disaster recovery (DR site) solutions. A solution is needed to increase the meantime between failures, decrease downtime, and create redundancy across Dasheen Bank’s network infrastructure. By implementing a network-wide general overhaul, or a complete redesign of the present network starting with the main data centre, the proposed solution has to be compatible with the network and security technologies, and adhere to the recommended working practices of today. To satisfy the demands of user design requirements, the phases of the PDIOO and Network Design and implementation life cycle methodologies are illustrated as follows. Each phase is critical when making any network design decisions. Planning (Analyzing Requirements) In the planning phase, specific network design requirements need to be identified. Key considerations include:

• Determining where to install the network.
• Identifying the required services and their users.

• To examine the WAN of Dasheen Bank, investigate and audit its current setup, and suggest changes to optimize data flow.
• To design a secure network infrastructure where internal users can access internal servers, external services, and the internet, while restricting public access from the internet to the external servers only.
• To design a redundancy solution (at the network level) for the main network services.
• To ensure overall connectivity within the network and test its performance.

1. 2. Deliverables

The key deliverables in this project are:

• To research WAN technologies offered by telecommunications service providers and select a service and WAN topology best suited to Dasheen Bank's requirements.
• To design a fully functioning network model using network simulation and virtual host software tools.
• To achieve the goals of network connectivity, redundancy, and security as per Dasheen Bank's network requirements.
• To submit a finalized report, a fully functioning simulation model, and a logbook containing all records of practical work, designs, communications, and any planning along with a timeline for the duration of this project.
• To produce configurations and show diagnostic information of routers, switches, and firewalls.

1. 3. Objective of the Internship

1 .3.1 General Objective The main objective of this internship is to prepare us for the real working environment that we are going to face after graduation. It’s mainly focuses on practical understanding of different hardware and software resources that we have learned in class room. Additionally, the aim is to put in practice the knowledge gained in class room to solve real problems.

1. 3. 2 Specific Objectives The internship that we have taken a great experience that allowed us to better understand the professional workplace and expectations that come with it. The following are some specific objectives of our internship program. ✓ To have experience on how to communicate professionally with employees. ✓ To handle the real work environment. ✓ To become competent and confidential in the field. ✓ To develop the capability of problem-solving ability. ✓ To improve communication skill with workers. ✓ To become responsible in real work environment. ✓ To have a clear knowledge about what we have learned in the class. ✓ To implement theoretical aspects that we learned in class. ✓ To become somehow experienced about the basic tasks in the future. ✓ To have skill and concept about different network hardware and software resources. ✓ Provide us to broaden our chance for handling a job and jump starting our careers. ✓ To enable us to get hands-on real-life experience. ✓ To apply the principles and techniques theoretically learnt into real-life problem-solving situation. ✓ To strengthen our professional skills and interpersonal communications.

2.1.1 User Requirements In the model of system components in our generic system, the user component is at the highest layer. The term user primarily represents the end users of the system but can be expanded to include everyone involved in the system, such as network and system administrators and management of Dasheen Bank. User requirements comprise the set of requirements gathered or derived from user input, representing what is needed by users to successfully accomplish their tasks on the system. In general, the system should adapt to users and their environments, provide quick and reliable information access and transfer, and offer quality service to the user. This indicates the following general requirements:

• Timeliness : The user must be able to access, transfer, or modify information within a tolerable time frame.
• Interactivity : Similar to timeliness, this focuses on response time from the system (as well as the network) that aligns with user expectations.
• Reliability : Availability from the user’s perspective, requiring consistently available service.
• Security : Ensuring the confidentiality, integrity, and authenticity of user information and physical resources, as well as access to user and system resources.
• Affordability : Ensuring that purchases fit within a budget.
• Functionality : Encompasses any functional requirement the user has for the system.
• Supportability : Describes how well the network can be maintained at designed performance levels across various scenarios as described during the requirements analysis process.
• Future Growth : Anticipating if and when users plan to deploy and use new applications and devices on the network.

2.1.2. Application Requirements The application component interfaces with the user and device components and is a key part of the requirements analysis. Application requirements are requirements that are determined from application information, experience, or testing, and represent what is needed by applications to successfully operate on the system. Types of Application Requirements Application Types Application Groups Application Location Application Types What types of Applications/services are we using or providing?

• Mission critical:- applications have predictable, guaranteed, and/or high performance RMA requirements.
• Rate-critical:- applications have predictable, guaranteed, and/or high-performance capacity requirements.
• Real-time and interactive:- applications have predictable, guaranteed, and/or high performance delay requirements How sensitive are apps to RMA (reliability, maintainability, availability)? What capacity is needed? What delay time is acceptable? Application Groups

Device Types What kinds of devices are on the network? ➢ Generic Computing Devices: Includes normal PCs, Macs, laptops, handheld computers, and workstations. ➢ Customer Devices: Phones, smartphones, tablets, set-top boxes, computers, etc. ➢ Core Network Servers: Includes all types of servers, such as file servers, print servers, application/computation servers, and backup servers. ➢ Specialized Devices: Includes extreme servers (supercomputers, massively parallel servers), data collection systems (POS terminals), industry-specific devices, networked devices (cameras, tools), traffic lights, ATMs, etc. Performance results are influenced by various factors, including: Storage Performance: Involves the performance of flash drives, disk drives, or tapes. Processor (CPU) Performance: Refers to the efficiency and speed of the central processing unit. Memory (RAM) Performance: Includes access times and overall memory efficiency. Bus Performance: Involves bus capacity and arbitration efficiency. OS Performance: Relates to the effectiveness of the operating system's protocol stack and APIs. Device Driver Performance: The efficiency of device drivers in managing hardware. The locations of devices are also crucial: Generic devices can often be grouped based on their quantity. Servers and specialized equipment are typically listed individually.

2. 2 Network Requirements

Constraints from Existing Networks: Considerations for existing network limitations. Expected Scaling of Existing Networks: Anticipating future growth and scalability needs.

Interoperability Between Networks: Ensuring seamless integration and communication between different networks. Existing Network and Support Services: Utilizing current network resources and support systems. Existing Architectural and Design Guidelines: Adhering to established design principles and standards. Network requirements include integrating with existing networks and addressing network management concerns. Key considerations for network integration and future evolution include: Scaling Dependencies: How the size of the existing network will impact the new network. Location Dependencies: Potential changes in the placement of key components due to interactions between old and new networks. Performance Constraints : Existing network limitations that could affect the new network's performance. Network management and security issues must be addressed throughout development: Network Monitoring: How the network will be monitored for events and performance issues. Management Data Flow Hierarchy: The structure for managing data flow within the network. Network Configuration : Plans for configuring the network. Troubleshooting Support: Systems and processes for identifying and resolving network issues. Security analysis should assess the severity (impact) and probability of potential attacks.

Chapter Three

Requirements Analysis Process

Figure. 2 requirements analysis process

3.1 Gathering and Listing Requirements

Service requirements are gathered and developed with initial conditions on the architecture and design, with input from users, administration, and management, and then refined by applying our experience and knowledge about the analysis process. Some guidelines for quantifying requirements and developing thresholds and limits are given in this chapter, but first we must communicate with the users to gather their requirements. We begin with a discussion of the initial conditions on the network 3.1.1Determining Initial Conditions. Initial conditions are the basis for the start of the analysis process. They help to determine what you are designing toward, as well as the reasons for the architecture and design. Initial conditions consist of the type of network project, the scope of the architecture and design, initial architecture/design goals, and any outside forces acting on the network.

For example, you probably know the type of network project, as well as the scope of the project. Some examples of these are as follows: Type of Network Project Scope of Network Project

• New network • Network size
• Modification of an existing network • Number of sites
• Analysis of network problems • Distance between sites
• Outsourcing
• Consolidation
• Upgrade 3.1.2 Setting Customer Expectations At this point in the analysis process it is important to begin to set customer expectations. This consists of: ➢ a rapid, initial evaluation of the problem, and ➢ estimating resources and schedule. 3.1.3 Working with Users While it can be challenging to communicate with users (including administration and management), there are some successful techniques that you can use:
• developing a survey to email, FAX, or mail to users
• following up on the survey with one-on-one telephone calls or conference calls
• Following up calls with face-to-face meetings with selected individuals or groups
• Whiteboard sessions to elicit ideas from users

Service metrics:

• Reliability – mean time between failures (MTBFs) and mean time between mission critical failures (MTBCFs)
• Maintainability – mean time to repair (MTTR)
• Availability - relates failures to repair time
• Uptime and downtime (percentage of total time)
• Error and loss rates at various levels, such as packet error rate, bit error rate (BER).
• Capacity - Data rates & Data size
• Delay 3.2.1 Measurement Tools In addition to the management protocols and MIBs, we can use commonly available tools to help measure service metrics. One such tool is the utility ping (available in TCP/IP releases), which roughly measures round-trip delays between selected sources and destinations in the network 3.2.2 Where to Apply Service Metrics Where service metrics are applied is determined in part by what you plan to achieve from them (e.g., separating responsibilities). They are useful when trying to isolate and track problems in the network, especially when there are multiple groups responsible for the network.

Chapter Four

Characterizing The Existing Internetwork

An important step in top-down network design is to examine a Dasheen Bank customer’s existing network to better judge how to meet expectations for network scalability, performance, and availability. Examining the existing network includes learning us about the topology and physical structure and assessing the network’s performance. Characterize the existing internetwork in terms of: Its infrastructure:

• Logical structure (modularity, hierarchy, topology)
• Physical structure
• Addressing and naming
• Wiring and media
• Architectural and environmental constraints
• Health

4.1 Characterizing the Network Infrastructure

Characterizing the infrastructure of a network means developing a set of network maps and learning the location of major internetworking devices and network segments. Get a Network Map Learning the location of major hosts, interconnection devices, and network segments is a good way to start developing an understanding of traffic flow.