Network Design and

. Administration II

RCS323
 What is Network Administration
• Network administration involves a wide array of operational tasks that help a
network to run smoothly and efficiently. Without network administration, it would
be difficult for all but the smallest networks to maintain network operations.
• The main tasks associated with network administration include:
– Design, installation and evaluation of the network
– Execution and administration of regular backups
– Creation of precise technical documentation, such as network diagrams, network cabling
documents, etc.
– Provision for precise authentication to access network resources
– Provision for troubleshooting assistance
– Administration of network security, including intrusion detection
RCS315 2
 What is network design
• Network Design is the structuring phase of network infrastructure,
where the designer must go through before it is implemented.
• It involves evaluating and understanding how all the elements of
the network link together (from routers, switches, and servers to
desktops, laptops, and printers) and how they can be made to run
as efficiently as possible.

RCS315 3
.

NETWORK DESIGN

RCS315 4
Coverage:
1. Background of Network Design
2. Network Design Concept
3. Network design Definition
4. Network design Principal
5. Network Design Methodology
1. Identify the network requirements.
2. Characterize the existing network.
3. Design the network topology/layout .
4. Prototype the design (logical design is simulated
RCS315 5
Network Design Background
• Today's IT environment continues to grow in both design and
complexity at a rapid pace.
• Your business' success hinges on a well-designed, reliable
network.
• Designing, architecting, implementing and managing technology is
what we do.
• A great network design can help an organization grow, enhance its
performance, and provide increased security.

RCS315 6
Network Design Concept
• Network design is a category of systems design that deals with data
transport mechanisms.
• As with other systems' design disciplines, network design follows an
analysis stage, where requirements are generated, logical design and
precedes implementation, where the system (or relevant system
component) is constructed.
• The objective of network design is to satisfy data communication
requirements while minimizing expense.
– Requirement scope can vary widely from one network design project to another
based on geographic particularities and the nature of the data requiring transport.

RCS315 7
 Network design Definition
• Is the structuring phase of network infrastructure, where the designer must go through before it is
implemented. It involves evaluating and understanding how all the elements of the network link
together (from routers, switches, and servers to desktops, laptops, and printers) and how they can
be made to run as efficiently as possible.
• A well-designed network can bring increased operational efficiency.
• Network design is a task that is usually performed by network designers, IT administrators, and other
related employees. 
• There are a number of details your network infrastructure design should show, these include:
1. A clear map of the network
2. The structure and layout of the cabling required
3. The quantity, type and location of all devices on the network 
4. Your IP addressing structure
5. Details of your network security architecture and processes
Network design Principals
•Regardless of network size or requirements, a critical factor for the successful implementation of any network design is
to follow good structured engineering principles. These principles include
–Scalability:
Scalable network designs can grow to include new user groups and remote sites and can support new applications
without impacting the level of service delivered to existing users.
–Availability:
A network designed for availability is one that delivers consistent, reliable performance, 24 hours a day, 7 days a week. In
addition, the failure of a single link or piece of equipment should not significantly impact network performance.
–Security:
Security is a feature that must be designed into the network, not added on after the network is complete. Planning the
location of security devices, filters, and firewall features is critical to safeguarding network resources.
–Manageability:
No matter how good the initial network design is, the available network staff must be able to manage and support the
network. A network that is too complex or difficult to maintain cannot function effectively and efficiently.
•To meet these fundamental design goals, a network must be built on a hierarchical network architecture that allows
for both flexibility and growth.

RCS315 9
 What is hierarchical network architecture
• A hierarchical network is defined as a treelike converging system
with multiple inflow points (sources) and one outlet (sink).
• (design)It involves dividing the network into discrete layers. This
helps the network designer and architect to optimize and select the
right network hardware, software, and features to perform specific
roles for that network layer.
• Hierarchical models apply to both LAN and WAN design

RCS315 10
.

METHODLOGY/
analysis

Step 1.Identify the network requirements.

Step 2 Characterize the existing network.
Step 3. Design the network topology/layout .
Step 4. Prototype the design (logical design is simulated

RCS315 11
 METHODLOGY
Step 1.
Identify the network requirements.
• The network designer works closely with the customer to document the
goals of the project.
–Identifying Customer Needs/Goals
• Goals are usually separated into two categories:
– Business goals: Focus on how the network can make the business more successful
– Technical goal/requirements: Focus on how the technology is implemented within
the network

RCS315 12
Step 2.
Characterize the existing network.
– Information about the current network and services is gathered and
analyzed.
– It is necessary to compare the functionality of the existing network with
the defined goals of the new project.
– The designer determines whether any existing equipment, infrastructure,
and protocols can be reused, and what new equipment and protocols are
needed to complete the design.

RCS315 13
Step 3.
Design the network topology and solutions
1. Designing a Network Topology
2. Designing Models for Addressing and Naming
3. Selecting Switching and Routing Protocols
4. Developing Network Security Strategies
5. Developing Network Management Strategies
• A common strategy for network design is to take a top-down approach.
In this approach, the network applications and service requirements are
identified, and then the network is designed to support them.

RCS315 14
Step 4
• When the design is complete, a prototype (a model) or proof-of-concept
test is performed. This approach ensures that the new design functions
as expected before it is implemented.
• Here logical design is simulated to see if it gives out the expected
results.(use either packet tracer or other means)
– Thus
– Testing of what you expect to get.
• Testing the Network Design
• Optimizing the Network Design
• Documenting the Network Design

RCS315 15
Step 1-4 How it could be arrived?
.

1. Analyzing Goals and Constraints

RCS315 17
 Analyzing Goals and Constraints
• Recall:
• What is Goals?
• What is Constraints
• Goal and Constraints are in two types:
1. Business goals: Focus on how the network can make the business more
successful
2. Technical goal/requirements: Focus on how the technology is
implemented within the network

RCS315 18
1.1-Analyzing Business Goals and Constraints
• The first thing to do is to understand the business goals for
the project, such as
– Why are we here What do you want to do (Plan)
– What advantage to the business will this project bring
• It is also important to understand the business constraints
• For example
– What we want is an unlimited budget and time to work
– But we will not get this
19
 Collect Information Before the Meeting
(Primary Analysis)
• The next step is to ensure that before meeting with the client,
whether internal or external some basic business related
information has been collected
• Such as
– Competition
– Market Conditions
– Future of the Industry
– Products Produced/Services Supplied
– Financial Condition
20
 Financial Condition
• You might decide to pass on a contract if the client
– Has a poor payment history
– Has high debt ratios, pending legal action, tax liens, or has recently laid
off staff
• Where do you find this type of information
• One source for inexpensive credit reports is Business Credit
– You can obtain information on a company’s credit rating, annual sales
volume, and public records, such as bankruptcy filings and tax liens

21
 Meet With the Customer
(detailed Analysis)
• Once the basic information has been collected, meet with the
customer to hear what they have to say
• At that meeting, collect information on the project
• Specifically try to get
– A concise statement of the goals of the project
• Problem to be solved
• New capability to be added
• What has the competition just done to them
– What must happen for the project to be a success
22
 Meet With the Customer
– What will happen if the project is a failure
• Is this a critical business function
• Is this just something they want to try
• Do they really think it will work
– Get a copy of the organization chart
• This will show the general layout of the organization
• It will suggest users to be accounted for
• It will suggest geographical locations to account for

23
 Meet With the Customer
– Find out about biases the customer has
– For example
• Will they only use certain companies products
• Do they avoid certain things
• This applies to the technical and management staff

24
 Start Gathering Information at the Site
• Once all of the basic information has been collected, it is time to
start gathering information at the site concerning the actual
project
• This information begins with information on the applications
– List all the applications that cross the network
• Now and after the project is completed
• Include both productivity applications and system management applications

25
Example: Applications List
Application Application New Importance Notes
Name Type Existing

MAS90 Enterprise accounting Existing Critical A new version that switches from client/ server to browser/server
will be out in one month

Quicken Accounting Existing Low CEO uses for home budget

OpenView System Existing High Monitors routers

AlertPage System New High Will read server log files

26
 Business Constraints
• Constraints on the project might include those related to business
practices, such as
– The security of the facility
– When can work be done
– What funds are available
– When are funds available

27
 Business Constraints
• Other constraints might relate to their staff
– What of their staff can you use
– When can you use their staff
– What is the level of competence of their staff, as they may be more of a
problem than a help
• The timeframe is always a constraint
– Due dates
– Milestones

28
 Business Constraints
• Political factors are always a problem
• Some will be obvious
• Others will not
– You probably will not ask about this
– It will just come out, hopefully
– Be aware of undercurrents at all times
– Look for
• Hidden agendas
• Turf wars (a situation in which two or more people or organizations are in competition over an area of
business or other activity)
• Group dynamics
• History of the project

29
 Putting It Into Practice
• Summarize what you find out
• Site an example and do as an assignment (Assg 1.1.1 )below

30
 Putting It Into Practice
• What are the business goals
– What Business is the company doing
– Market conditions
– Future of the industry
– Service provided
– Specific goal of the project
• What are the business constraints
– Budget
– Biases
• What applications will use the network
Assg 1.1.1
31