Unit #1 - Confirm Client and Equipment Requirements

MARY HELP COLLEGE
HARDWARE AND NETWORKING SERVICING

LEVEL IV
UC: BUILD A SMALL WIRELESS LAN

MODULE CODE: EIS HNS4 M03 1123
NOMINAL DURATION: 40 HRS.
UNIT ONE: CONFIRM CLIENT AND EQUIPMENT REQUIREMENTS

CLIENT AND ORGANIZATIONAL REQUIREMENTS
 To design a network that meets customers' needs, the

organizational goals, organizational constraints,
technical goals, and technical constraints must be
identified.
 After gathering all customer requirements, the
designer must identify and obtain any missing
information and reassess the scope of the design
project to develop a comprehensive understanding of
the customer's needs.
ASSESSING THE SCOPE OF A NETWORK DESIGN
PROJECT
 When assessing the scope of a network design,

consider the following:
 Whether the design is for a new network or is a
modification of an existing network.
 Whether the design is for an entire enterprise network,
a subset of the network, or a single segment or
module..
 Whether the design addresses a single function or the
network's entire functionality.
Scope of Design Comments
 The backbone at the central office needs to be redesigned. All

Entire network branch offices' LANs will be upgraded to Fast Ethernet
technology.
 Introduction of private IP addresses requires a new addressing

plan.
 Certain LANs must also be segmented.
Network layer  Routing must be redesigned to support the new addressing
plan and to provide greater reliability and redundancy.
 The central office backbone and some branch offices require

redundant equipment and redundant links are needed.
Data link layer
Table 1. 1 Network Design Scope Assessment

IDENTIFY REQUIRED INFORMATION
 Determining requirements includes

extracting initial requirements from the
customer and then refining these with
other data that has been collected from
the organization.
EXTRACTING INITIAL REQUIREMENTS
 Initial design requirements are typically extracted

from the Request for Proposal (RFP) or Request for
Information (RFI) documents that the customer
issues.
 An RFP is a formal request to vendors for proposals
that meet the requirements that the document
identifies.
 An RFI is typically a less formal document an
organization issues to solicit ideas and information
from vendors about a specific project.
 The first step in the design process should be
pre-documenting (sifting, processing,
reordering, translating, and so forth) the
design requirements and reviewing them
with the customer for verification and
approval, obtaining direct customer input, in
either oral or written form.
 Figure 1-1 illustrates an iterative approach to
developing the design requirements document.
EXTRACTING INITIAL REQUIREMENTS
1. Extract the initial customer requirements (from the

RFP or RFI).
2. Query the customer for a verbal description of the
initial requirements.
3. Produce a draft document that describes the design
requirements.
4. Verify the design requirements with the customer,
and obtain customer approval.
5. Revise the document as necessary to eliminate
errors and omissions.
N.B. 2 to 5 are repeated if the customer has additional comments about
the draft document.
GATHERING NETWORK REQUIREMENTS
 The process of gathering requirements can be

broken down into five steps.
 During these steps (which are sometimes called

milestones), the designer discusses the project with
the customer's staff to determine and gather the
necessary data, including appropriate
documentation.
Figure 2 Gathering Data for Design Requirements

Identify the planned network applications and
Step 1
network services.
Step 2 Determine the organizational goals.
Determine the possible organizational

Step 3
constraints.
Step 4 Determine the technical goals.
Determine the technical constraints that must

Step 5
be taken into account.
Note:
 The process is not unidirectional; the

designer might return to a step and make
additional inquiries about issues as they arise
during the design process.
PLANNED APPLICATIONS AND NETWORK
SERVICES
 The designer must determine which applications the

customer is planning to use and the importance of
each of these applications.
 Using a table helps organize and categorize the
applications and services planned; the table should
contain the following information:
 Planned application types: Include e-mail,
groupware (tools that aid group work), voice
networking, web browsing, video on demand (VoD),
databases, file sharing and transfer, computer-aided
manufacturing, and so forth.
SERVICES
 Applications: Specific applications that will be

used, such as Microsoft Internet Explorer,
Cisco Unified Meeting Place, and so forth.
 Level of importance: The importance of the
applications—whether critical, important, or
not important is noted.
 Comments: Additional notes taken during the
data-gathering process.
Level of Importance
Application Type Application (Critical, Important, Comments
Not Important)
E-mail  Microsoft Office Outlook  Important
Groupware  Cisco Unified Meeting  Important  Need to be able to

Place share presentations and
applications during remote
meetings
Web browsing  Microsoft Internet  Important
Explorer, Netscape
Navigator, Opera
Video on demand  Cisco Digital Media  Critical
System
Database  Oracle  Critical  All data storage is based on
Oracle
Customer support  Custom applications  Critical
applications
Table 1. 2 shows an example of data gathered about the planned applications for the sample company
SERVICES
 Infrastructure services include security, QoS, network

management, high availability, and IP multicast.
 Software distribution, backup, directory services, host
naming, and user authentication and authorization are
examples of other services and solutions that are deployed
to support a typical organization's many applications.
 Table 1-3 shows sample data that was gathered about the
infrastructure services planned for the sample company,
Corporation X.
Service Comments
Security Deploy security systematically: Firewall technology to protect the internal network; virus-
scanning application to check incoming traffic for viruses; intrusion detection and prevention
systems to protect from and inform about possible outside intrusions. Consider the use of
authentication, authorization, and accounting systems to ensure that only authenticated and
authorized users have access to specific services.
QoS Implementation of QoS to prioritize more important and more delay-sensitive traffic over
less important traffic (higher priority for voice and database traffic; lower priority for HTTP
traffic).
Network management Introduction and installation of centralized network management tools (such as HP Open
View with Cisco Works applications) for easier and more efficient network management.
High availability Use redundant paths and terminate connections on different network devices to eliminate
single points of failure.
IP multicast Introduction of IP multicast services needed for the introduction of videoconferencing and
e-learning solutions.
Voice Company wants to migrate to IP telephony.
Mobility Need mobility for employees and guest access for clients.
Table 1. 3 Shows an example of data gathered about the planned applications for the sample
company
ORGANIZATIONAL GOALS
 Every design project should begin by determining the

organizational goals that are to be achieved.
 The criteria for success must be determined, and the

consequences of a failure understood.
 Network designers are often eager to start by analyzing the

technical goals before considering the organizational goals and
constraints.
 However, detailed attention to organizational goals and

constraints is important for a project's success.
Note:
 In discussions about organizational goals, the

designer obtains knowledge about the customer's
expectations of the design's positive outcomes for
the organization.
 Both short- and long-term goals should be identified.

 This is an opportunity to determine what is important to the

customer.
 Some sample questions a designer might ask to help determine
organizational goals include the following:
 What are you trying to accomplish with this project?
 What business challenges are you currently facing?
 What are the consequences of not resolving these issues?
 What is the major objective of this project?
 What is driving the change?
 What other technology projects and business initiatives will affect your group in
the next two to five years?
 What skill sets does your technical staff currently have?
 What is your goal for return on investment?
 Organizational goals differ from organization to

organization.
 The following are some typical goals that commercial

organizations might have:
 Increase the operation's generated revenue and profitability. A
new design should reduce costs in certain segments and propel
growth in others. The network designer should discuss with the
customer any expectations about how the new network will
influence revenues and profits.
 Shorten development cycles and enhance productivity by

improving internal data availability and interdepartmental
communications.
 Improve customer support and offer additional customer
services that can expedite reaction to customer needs and
improve customer satisfaction.
 Open the organization's information infrastructure to all key
stakeholders (prospects, investors, customers, partners,
suppliers, and employees), and build relationships and
information accessibility to a new level.
ORGANIZATIONAL CONSTRAINTS
 When assessing organizational goals, it is important to

analyze any organizational constraints that might affect
the network design.
 Some sample questions the designer might ask to help
determine organizational constraints include the
following:
 What in your current processes works well?
 What in your current processes does not work well?
 Which processes are labor-intensive?
 What are the barriers for implementation in your
organization?
 What are your major concerns with the implementation of

a new solution?
 What projects already have budget approval?
 Are other planned technology projects and business
initiatives compatible with your current infrastructure and
technology solutions?
 Do you have a budget for technical development for your
staff?
 Are there any policies in place that might affect the project?
TYPICAL CONSTRAINTS
 Budget:
 Reduced budgets or limited resources often force network designers to
implement an affordable solution rather than the best technical solution.
 This usually entails some compromises in availability, manageability,
performance, and scalability.
 Personnel:
 The availability of trained personnel within the organization might be a
design consideration.
 Organizations might not have enough trained personnel, or they might
not have enough personnel.
TYPICAL CONSTRAINTS
 Policies:
 Organizations have different policies about protocols,

standards, vendors, and applications; to design the network
successfully, the designer must understand these policies.
 Schedule:
 The organization's executive management must discuss and

approve the project schedule to avoid possible
disagreements about deadlines.
Organizational
Gathered Data (Current Situation) Comments
Constraint
$650,000 Budget can be extended by a

Budget
maximum of $78,000
Two engineers with college degrees and Plans to hire additional engineers
Cisco Certified Network Associate (CCNA) for network maintenance; need
certifications for network maintenance; one has Cisco technical development plan for
Personnel Certified Network Professional (CCNP) certification staff
Three engineers for various operating systems and
applications maintenance
Prefers a single vendor and standardized protocols Current equipment is Cisco; prefers to
Policy stay with Cisco
Plans to introduce various new applications in the New applications that will be
next nine months introduced shortly are
Schedule videoconferencing, groupware,
and IP telephony.
Table 1.5 data gathered about the organizational goals of a sample company
TECHNICAL GOALS
 The technical goals of the project must also be

determined before the design starts.

determine technical goals include the following:
 What infrastructure issues exist or will exist related to your
applications rollouts?
 What skill sets does your technical staff need to acquire?
 Does your current network have any performance issues?
 Which portions of your network are considered mission-critical?
TECHNICAL GOALS
 The following list describes some common technical
goals:
 Improve network performance.
 Decrease expected downtime and related expenses.
 Modernize outdated technologies.
 Improve scalability of the network.
 Simplify network management.

TECHNICAL CONSTRAINTS
 Network designers might face various technical constraints

during the design process.

determine technical constraints include the following:
 How do you determine your technology priorities?
 Do you have a technology refresh process?
 What urgent technical problems require immediate resolution or mitigation?
 Do you have a plan for technical development for your staff in specific areas?
 Do any applications require special network features (protocols and so forth)?

 Good network design addresses constraints by identifying
possible trade-offs, such as the following:

 Existing equipment: The network design process is usually progressive; legacy
equipment must coexist with new equipment.
 Bandwidth availability: Insufficient bandwidth in parts of the network where the
bandwidth cannot be increased because of technical constraints must be resolved
by other means.
 Application compatibility: If the new network is not being introduced at the same
time as new applications, the design must provide compatibility with old
applications.
 Lack of qualified personnel: Lack of qualified personnel
suggests that the designer must consider the need for
additional training; otherwise, certain features might have
to be dropped.
 For example, if the network proposal includes the use
of IP telephony but the network administrators are not
proficient in IP telephony, it might be necessary to
propose an alternative solution.

 Table 1-7 presents sample technical constraints gathered for Corporation

X.
 Under existing equipment, the designer notes that the coaxial cabling in
the LAN's physical cabling plant still exists and comments that twisted pair
and fiber optics should replace it.
 The bandwidth availability indicates that the WAN service provider does
not have any other available links; the organization should consider
changing to another service provider.
 Application compatibility suggests that the designer should take care

when choosing equipment.
Gathered Data (Current
Technical Constraints Comments
Situation)
 Coaxial cable  The cabling must be replaced with

twisted pair to the desktop, and
Existing equipment fiber optics for uplinks and in the
core.
 64-kbps WAN link  Upgrade bandwidth; change to

another service provider because
Bandwidth availability the current one does not have any
other links to offer.
 IP version 6 (IPv6)-based  New network equipment must

Application
applications support IPv6.
compatibility
Table 1.7.Technical Constraints for

ASSIGNING APPROPRIATE AUTHORITY
 The importance of wireless network security cannot be

understated.
 With the proliferation of mobile devices and the

popularity of public Wi-Fi hotspots, the potential for data
breaches and other cyber security threats has increased
exponentially.
 12 best practices essential for ensuring that your data and

devices are safe from malicious actors.
CONT’D
1. Enabling Two-Factor Authentication (2FA)
 Two-factor authentication adds an extra layer of

security to the login process.
 It requires users to enter both a username and
password, as well as a code that is generated by an
authenticator app.
 This makes it more difficult for someone to gain
unauthorized access to the network.
CONT’D
2. Using a Strong Password
 Using a strong password is one of the most important

best practices for wireless network security.
 A strong password is at least eight characters long
and includes a mix of upper- and lower-case letters,
numbers, and symbols.
 Passwords should be changed regularly to ensure that
they remain secure.
CONT’D
3. Encrypting Data
 Encrypting data is another important best

practice for wireless network security.
 Data encryption scrambles data so that it can
only be decrypted and read by authorized users.
 This helps to protect sensitive information from
being accessed by unauthorized individuals.
CONT’D
4. Disabling SSID Broadcast

 Disabling SSID broadcast is another best practice for
wireless network security.
 When SSID broadcast is enabled, it allows anyone within
range of the wireless network to see the network's name.
 You can disable SSID broadcast by accessing the wireless
router's configuration page and disabling the SSID
broadcast feature.
CONT’D
5. Using MAC Filtering
 Using MAC filtering is another best practice for wireless network security.
 MAC addresses are unique identifiers assigned to devices that connect to
a network.
6. Enabling WPA3 Security

 Enabling WPA3 security is another best practice for wireless network
security.
 WPA3 is the most recent and most secure wireless security protocol.
 It provides stronger protection than WPA2 and should be used whenever
possible.
CONT’D
7. Using A VPN
 Using a VPN is another best practice for wireless network
security.
 A VPN encrypts all traffic between a device and the VPN
server, making it more difficult for someone to eavesdrop
on the connection.
 This is especially important when using public Wi-Fi
networks, as they are often less secure than private ones.
CONT’D
8. Disabling Remote Administration

 Disabling remote administration is another best practice
for wireless network security.
 When remote administration is enabled, it allows anyone
with the proper credentials to access the router's
configuration page and make changes to the network.
 This can be a security risk, as it allows unauthorized
individuals to potentially gain access to the network.
CONT’D
9. Changing the default password
 Changing the default password is another best

practice for wireless network security.
 Many routers come with a default password that is
easy to guess.
 This can be a security risk, as it allows unauthorized
individuals to potentially gain access to the
network..
CONT’D
10. Using a Firewall
 Using a firewall is another best practice for wireless
network security.
 A firewall helps to protect the network by blocking
incoming traffic that is not authorized.
 This can be especially important in preventing attacks
from malware and other malicious software.

CONT’D
11. Disabling UPnP

 Universal Plug and Play (UPnP) is a protocol that allows devices to
automatically discover and connect to each other.
 This can be a security risk, as it allows unauthorized devices to
potentially gain access to the network.
 To disable UPnP, access the wireless router's configuration page and
disable the feature.
 You can also disable UPnP on individual devices by accessing the
settings menu.
CONT’D
12.Disabling Unnecessary Services

 You often find that routers come with a number of unnecessary
services enabled.
 These can be a security risk, as they can provide potential
attackers with information about the network.
 To disable unnecessary services, access the wireless router's
configuration page and disable any services that are not needed.
 This will help to reduce the attack surface of the network.
 Common unnecessary services include things like telnet, SSH,
and HTTP.
WIRELESS DEVICE TECHNICAL REQUIREMENTS
DEFINE WIRELESS NETWORK REQUIREMENTS
 Requirements define what the wireless network must

do, which provides the foundation for the design.
 Requirements for a wireless network include needs, such
as signal coverage in all elevators and support for voice
telephony.
 Leave the technical details, such as specific technologies
(such as 2.4GHz vs. 5GHz 802.11n), components, and
configuration settings to the designers after all
requirements are well-defined and agreed upon.
WIRELESS DEVICE TECHNICAL
REQUIREMENTS
 Before implementing a wireless network, consider

the following types of requirements:
 Applications
 Environment
 Coverage areas
 End users
 Client devices
 Existing infrastructure
 Security
 Funding
 Schedules
APPLICATIONS
 Ultimately, the wireless network must support user applications,

so be sure to fully define them in the requirements.
 This could be general office applications, such as web browsing,

email, and file transfer, or it could be wireless patient monitoring
in a hospital or voice telephony in a warehouse.
 Be as specific as possible.
 The application requirements enable designers to specify

applicable throughput, technologies and products when
designing the system.
ENVIRONMENT
 Provide a description of the environment where the wireless

network will operate.
 For buildings, include the floor plan, type construction, and possible
locations for mounting access points.
 For outdoor areas, include satellite images, aerial photographs, or
drawings.
 Walk through the areas to verify accuracy of these items.
 Take lots of photos.
 In addition to a visible inspection, consider performing a RF site
survey.
 All of this will capture the environment in a way that will help
designers choose the right technical elements.
COVERAGE AREAS
 This describes where users will need access to the wireless

network.
 They might only need connectivity in their offices and

conferences rooms, but they may also need connectivity
inside cafeteria.
 By properly specifying coverage area, you’ll avoid the

unnecessary expense of installing access points where they’re
not needed.
END USERS
 Be sure to identify whether users are mobile or

stationary, which provides a basis for including
enhanced roaming in the design.
 Mobile users will move about the facility and possible

roam across IP domains, creating a need to manage IP
addresses dynamically.
 Some users, however, may be stationary, such as

wireless desktops.
CLIENT DEVICES
 You should specify the client devices (and existing client radios)
to ensure the solution accommodates them in the most
effective manner.
 For example, you could specify that users will have laptops
running Microsoft Vista operating system with integrated
802.11b/g radios.
 This provides a basis for deciding on the type of client radios to

specify for other client devices during the design and whether
there is a need to support legacy devices (i.e., 802.11b/g).
EXISTING INFRASTRUCTURE
 Be certain to describe all existing applicable

infrastructure.
 Identify locations and availability of communications

closets, switch types and available ports, PoE
interfaces, fiber runs, conduit, authentication
servers, VPN ports, and operational support
systems.
SECURITY
 Describe the sensitivity of the information that will

traverse the wireless network.
 If possible, cite existing corporate wireless security

policies.
 You will likely need to require encryption and

authentication of all client devices.
FUNDING
 The requirements stage of a wireless network
project is a good time to ask how much money is
available.
 If funding limits are known, then you will know how
much there is to work with when designing the
system.
SCHEDULES
 Of course, a company will generally want the wireless

network installed “yesterday,” but we all know that is
impossible.
 You will need to nail down a realistic completion date,

though, and plan accordingly.
 For example, you may be defining requirements in July,

and a retail store will likely demand that a wireless price
marking application be installed by the end of September.
IDENTIFY COMPONENTS TO BE INSTALLED TO MEET THE
TECHNICAL REQUIREMENTS
 Technical requirements are important because they describe

how software should function and what its behavior should be.
 This helps developers and users to understand the best way to

use the software.
 A document of clearly defined specifications helps to create a

project or software that has a proper process for
implementation.
 Developers and other technicians refer to this as technical

IDENTIFY COMPONENTS TO BE INSTALLED TO MEET THE
TECHNICAL REQUIREMENTS CONT’D
 Technical requirements vary depending on the product or industry.
 However, there is no all-encompassing list of technical requirements that apply to every

project or development.
 Here is a sample list of technical requirement examples:
 Accessibility
 Authentication and authorization
 Availability
 Information security
 Maintainability
 Performance
 Privacy
 Reliability
SELECTING APPROPRIATE POSITION FOR ACCESS
POINT
 Wireless Access Point (WAP) placement is an

important aspect of setting up and maintaining a
wireless network.
 Proper placement of WAPs ensures good coverage,

capacity, and performance.
 Here are some best practices for WAP placement:

SELECTING APPROPRIATE POSITION FOR
ACCESS POINT
CONDUCT A SITE SURVEY
 Before installing any WAPs, conduct

a Wireless site survey to identify areas with
poor coverage, high demand, and potential
sources of interference.
 This will help you to determine the optimal

location for each WAP.
ACCESS POINT
USE CEILING-MOUNTED WAPS
 Ceiling-mounted WAPs provide better

coverage than wall-mounted WAPs, as they
can reach a wider area and provide more
uniform coverage.
ACCESS POINT
PLACE WAPS IN THE CENTER OF THE COVERAGE AREA
 In general, WAPs should be placed in the

center of the area they are supposed to
cover, as this will ensure good coverage for
the entire area.
ACCESS POINT
AVOID PHYSICAL OBSTRUCTIONS:
 Physical obstructions such as walls, ceilings,

and furniture can interfere with wireless
signals, so it’s important to avoid placing
WAPs near these types of obstructions.
ACCESS POINT
USE MULTIPLE WAPS
 In large areas, it’s important to use multiple
WAPs to ensure good coverage and capacity.
 This will also help to reduce the risk of
congestion and ensure that users have a
good experience.
ACCESS POINT
USE POWER OVER ETHERNET (POE):
 PoE allows WAPs to receive power over
the same cable that carries the network
data, making it easy to install them in a
variety of locations.
ACCESS POINT
USE WIRELESS PLANNING TOOLS
 Wireless planning tools can help to predict
coverage, capacity, and performance of
wireless networks, by simulating the
environment and giving you an idea of how
the wireless network will perform.

ACCESS POINT PLACEMENT GUIDELINES FOR
SUCCESSFUL INSTALLATION
 In order to build a wireless network infrastructure, a

company needs to consider the placement of multiple
access points around their campus.
 Access points connect to a wired network and allow

devices to connect to that network via the access point
wirelessly.
 They are the cornerstone of wireless networking; as

such, knowing how to properly install them is essential.
 Physical access point placement plays a huge part in

this installation process.
 Access points must be placed in strategic locations

in order to provide maximum coverage.
 Depending on the size, shape, and needs of every

area of your infrastructure, your team will need to
install access points at different locations.
Place access points where Wi-Fi will be used the

most
 The first rule of proper access point placement
is to determine the locations where Wi-Fi
networks will be used the most.
 The closer a device is to an access point, the

better its connection will be.
SUCCESSFUL INSTALLATION CONT’D
Precise access point placement is key
 Access point placement is not just about picking the right

general area to install a device.
 You also need to consider the precise physical placement for

the access point in each room/location you need to service.
 Access points need to be built in optimal locations to provide

the best signal strength to the areas it will cover.
Avoid coverage overlap whenever possible

 When designing your wireless infrastructure, you need to
select the best access point locations that will provide
maximum coverage for your business.
 The simple answer to this problem is installing access points

anywhere you can, but this is almost always a bad idea.
 Not only does this introduce unnecessary costs, but it also

generates a lot of coverage overlap.
Electronic devices
 Devices that emit electromagnetic signals, such as
microwaves, are notorious for completely blocking
wireless signals.
 Whenever possible, access points should be placed

as far away from these devices as possible.
Building materials
 The building materials of the structures your business operates
in can cause varying degrees of wireless signal interference or
blockage.
 Concrete, brick, and other dense materials are infamous for

blocking Wi-Fi signals.
 Your team should place access points in areas that provide the
best area of coverage when considering the building materials
around it.
CABLING AND POWER REQUIREMENTS
 Wireless cabling, also known as wireless connectivity or wireless

networking, refers to the transmission of data or information
between devices without the need for physical cables or wires.
 Instead, wireless communication technologies such as Wi-Fi,

Bluetooth, or cellular networks are used to establish connections.
 When it comes to power requirements, wireless devices typically
require a power source to operate.
 The specific power requirements can vary depending on the device

and its intended use. Here are a few common examples:
CABLING AND POWER REQUIREMENTS CONT’D
Wireless Routers:
 Wireless routers, which provide Wi-Fi connectivity,

are usually powered by connecting them to a
standard electrical outlet.
 They require a continuous power source to function

and transmit wireless signals.
Wireless Access Points
 Similar to routers, wireless access points are devices that

provide wireless connectivity in a specific area or
location.
 They may be powered through an electrical outlet or, in

some cases, through Power over Ethernet (PoE)
technology, which allows both data and power to be
transmitted over the same Ethernet cable.
Wireless Cameras
 Wireless security cameras or other types of wireless

cameras may be powered by batteries or by connecting
them to an electrical outlet.
 Battery-powered wireless cameras are often designed

for flexibility and portability, while those connected to
an outlet can provide continuous power.
Wireless Devices
 Various wireless devices, such as smartphones,

tablets, and laptops, have built-in batteries
that power their wireless capabilities.
 These devices need to be periodically recharged

to maintain their wireless functionality.
End of Unit #1

Unit #1 - Confirm Client and Equipment Requirements

Uploaded by

Copyright:

Available Formats

Unit #1 - Confirm Client and Equipment Requirements

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit #1 - Confirm Client and Equipment Requirements

Uploaded by

Copyright:

Available Formats

MARY HELP COLLEGE

HARDWARE AND NETWORKING SERVICING

UC: BUILD A SMALL WIRELESS LAN

UNIT ONE: CONFIRM CLIENT AND EQUIPMENT REQUIREMENTS

 To design a network that meets customers' needs, the

 When assessing the scope of a network design,

 The backbone at the central office needs to be redesigned. All

 Introduction of private IP addresses requires a new addressing

 The central office backbone and some branch offices require

Table 1. 1 Network Design Scope Assessment

 Determining requirements includes

 Initial design requirements are typically extracted

1. Extract the initial customer requirements (from the

 The process of gathering requirements can be

 During these steps (which are sometimes called

Figure 2 Gathering Data for Design Requirements

Step 2 Determine the organizational goals.

Determine the possible organizational

Step 4 Determine the technical goals.

Determine the technical constraints that must

 The process is not unidirectional; the

 The designer must determine which applications the

 Applications: Specific applications that will be

E-mail  Microsoft Office Outlook  Important

Groupware  Cisco Unified Meeting  Important  Need to be able to

 Infrastructure services include security, QoS, network

 Every design project should begin by determining the

 The criteria for success must be determined, and the

 Network designers are often eager to start by analyzing the

 However, detailed attention to organizational goals and

 In discussions about organizational goals, the

 Both short- and long-term goals should be identified.

 This is an opportunity to determine what is important to the

 Organizational goals differ from organization to

 The following are some typical goals that commercial

 Shorten development cycles and enhance productivity by

 When assessing organizational goals, it is important to

 What are your major concerns with the implementation of

 Organizations have different policies about protocols,

 The organization's executive management must discuss and

$650,000 Budget can be extended by a

 The technical goals of the project must also be

 Some sample questions the designer might ask to help

 The following list describes some common technical

 Decrease expected downtime and related expenses.

 Modernize outdated technologies.

 Improve scalability of the network.

 Simplify network management.

 Network designers might face various technical constraints

 Some sample questions the designer might ask to help

 Do you have a technology refresh process?

 What urgent technical problems require immediate resolution or mitigation?

 Do any applications require special network features (protocols and so forth)?

 Good network design addresses constraints by identifying

possible trade-offs, such as the following:

equipment must coexist with new equipment.

 Bandwidth availability: Insufficient bandwidth in parts of the network where the

bandwidth cannot be increased because of technical constraints must be resolved

 Lack of qualified personnel: Lack of qualified personnel

suggests that the designer must consider the need for