NAME: Ted Amachree

DATE: 04/11/2017
PROFESSOR: Tim Culhane
COURSE TITLE: Network Design and Infrastructure
CODE: IT 512.51

CHAPTER 3

Review QUESTIONS:

1. What is a discontiguous network?

A discontiguous network is one that is divided into segments such that another network
segment occupies the space that separates them.

A discontiguous network will have two or more subnetworks of a classful network

connected together by different classful networks. Say you have 10.8.0.0/16, 10.9.0.0/16,
10.10.0.0/16, and 10.11.0.0/16. If you own all of these networks, you could advertise
them summarized as 10.8.0.0/14.

Why does it pose challenges to a network designer?

It limits the network designers ability implement a new network design on an existing
network and as such make it impossible to achieve the design goal.

However, if you only owned the 10.8, 10.9, and 10.11 network spaces, you could not.
You would then only be able to summarize it down to two routes - 10.8.0.0/15, and
10.11.0.0/16.

The idea is that contiguous subnets can all be reach in the same direction. So if you have
4 routers, and routers A, B and C all point packets destined to 10.8 through 10.11 to
router D via a summary address, that works so long as the 10.8.0.0/14 network all resides
off of router D. However, as explained earlier, if 10.10.0.0/16 resides on router B, then
traffic destined to that network would not reach it's destination. That is a case where you
break up your summarization as the networks are no longer "contiguous".

For example, route summarization cannot be implemented on a discontiguous network.

2. Why is it important to characterize a network logical topology and not just its
physical topology?
What information does a logical topology illustrate that might be missed in with just
a physical topology?
Characterizing a network logical topology enables a network designer to be able to
upgrade a network.
The media access method, the way network access is controlled and collisions prevented,
is based on the logical topology rather than the physical topology. To effectively
troubleshoot communications problems, it is important to know not only the physical
topology of a network but also the logical topology, so that you know what path the data
packets take as they travel from one computer to another. To better understand current
and future network topology, routing, security, DNS, workload, performance, and
economic issues. However, the logical topology offers the network designer the high-
level conceptual construct of the network. It illustrates the architecture of the network,
whereas the physical topology doesnt.

3. The Cooperative Association for Internet Data Analysis(CAIDA) collects

information on network measurement and visualization resources. How could
CAIDAs work help a network designer characterize an existing network.

It enables the network designer to characterize the existing network by computing and
analyzing the baseline metrics of the existing network with network tools without having
to commit enormous resources to achieving this purpose.

4. The IETF Internet Protocol Metrics(IPPM) working group develops standard

metrics that can be applied to the quality, performance, and reliability of a network.
How could this groups work help a network designer characterize an existing
network.

Fault Tolerance

The expectation that the Internet is always available to the millions of users who rely on
it requires a network architecture that is designed and built to be fault tolerant. A fault
tolerant network is one that limits the impact of a hardware or software failure and can
recover quickly when such a failure occurs. These networks depend on redundant links,
or paths, between the source and destination of a message. If one link or path fails,
processes ensure that messages can be instantly routed over a different link transparent to
the users on either end. Both the physical infrastructures and the logical processes that
direct the messages through the network are designed to accommodate this redundancy.
This is a basic premise of the architecture of current networks.

Scalability
 A scalable network can expand quickly to support new users and applications without
impacting the performance of the service being delivered to existing users. Thousands of
new users and service providers connect to the Internet each week. The ability of the
network to support these new interconnections depends on a hierarchical layered design
for the underlying physical infrastructure and logical architecture. The operation at each
layer enables users or service providers to be inserted without causing disruption to the
entire network. Technology developments are constantly increasing the message carrying
capabilities and performance of the physical infrastructure components at every layer.
These developments, along with new methods to identify and locate individual users
within an internetwork, are enabling the Internet to keep pace with user demand.

Quality of Service (QoS)

The Internet is currently providing an acceptable level of fault tolerance and scalability
for its users. But new applications available to users over internetworks create higher
expectations for the quality of the delivered services. Voice and live video transmissions
require a level of consistent quality and uninterrupted delivery that was not necessary for
traditional computer applications. Quality of these services is measured against the
quality of experiencing the same audio or video presentation in person. Traditional voice
and video networks are designed to support a single type of transmission, and are
therefore able to produce an acceptable level of quality. New requirements to support this
quality of service over a converged network are changing the way network architectures
are designed and implemented.

REFERENCES

1. Wanjohi, B. M. (2013, July 03). Existing Networks. Retrieved May 20, 2017, from
https://docs.google.com/viewer?
a=v&pid=sites&srcid=ZGVmYXVsdGRvbWFpbnxibXdhbmpvaGl8Z3g6MjI1YzEzOW
IzNzgxNjk5Mg

2. Top-Down Network Design, Priscilla Oppenheimer. (3rd Edition) A system analysis

approach to enterprise