You are a Staff Engineer, Networking, for
MegaMoron
Communications Inc., the world's premier communications design company.
You have been tasked with the design of a Internet Protocol
(IP) backbone for RedNeckNet, a start up regional Internet Service
Provider
(ISP).
RedNeckNet is installing Points of Presences (POP's)
in
Stillwater & Tulsa, Oklahoma; St. Louis, Missouri; Lubbock,
Texas;
Little Rock, Arkansas; and
Wichita, Kansas, and needs an IP backbone network designed to connect
these locations. The president of the company, a Mr. H.
Simsen, has
insisted that the backbone be a Leased Line network hauled by
the carrier he has the most stock in, U.S. Sprawl. Given this
constraint,
your goal is to design a least cost network that will meet average
one-way
end-to-end delay specifications during the peak traffic period.
Investigation has revealed the following:
* IP router chassis have been installed at each POP
location. Leased line trunks must be specified to link the POP's
together.
* The design specifications call for no redundancy,
hence a single trunk to each POP location is allowable.
* The average packet size that will traverse this
network during the peak period is 710 bytes.
* The average one-way end-to-end delivery delays
between any city pair must be less than or equal to 31 msec.
* The propagation delays between sites are as
follows:
Stillwater - Lubbock: 5.2
msec
Stillwater - St. Louis: 6.6
msec
Stillwater - Wichita: 1.7
msec
Stillwater - Tulsa: 1.0
msec
Stillwater - Little Rock:
4.6 msec
St. Louis - Lubbock: 11.9
msec
St. Louis - Wichita: 3.6
msec
St. Louis - Tulsa: 6.3
msec
St. Louis - Little Rock: 4.7
msec
Lubbock - Wichita: 6.1 msec
Lubbock - Tulsa: 6.1 msec
Lubbock - Little Rock: 8.9
msec
Tulsa - Little Rock: 3.6
msec
Tulsa - Wichita: 2.2 msec
Wichita - Little Rock: 5.6
msec
* The overall average delivery
delays on any Leased Line link can be written as:
where
| From \ To | Tulsa | Little Rock | Lubbock | Stillwater | St. Louis | Wichita |
| Tulsa | - | 1,020 |
1,370 |
1,230 |
540 |
1,380 |
| Little Rock | 1,650 |
- | 650 |
260 |
480 |
1,070 |
| Lubbock | 1,700 |
870 |
- | 1,100 |
240 |
1,030 |
| Stillwater | 1,170 |
480 |
1,140 |
- | 250 |
1,060 |
| St. Louis |
850 |
210 |
550 |
210 |
- | 100 |
| Wichita | 1,100 |
1,010 |
980 |
1,040 |
400 |
- |
Rules of Engagement:
You may work in two person teams if you so desire.
Treat your project as if it were proprietary
corporate
information, i.e. do not disseminate your design in any manner to the
competition.
Doing so, and getting caught, will get anyone "fired" (i.e. an F for
the
course).
Make your final report short and sweet. DO NOT
GIVE ME A RUNNING COMMENTARY OF YOUR DERIVATION. I will dock you
points
if you do so. Your final report should be about three to four pages and
include:
(1) a WAN backbone network diagram showing
trunk locations, average traffic routed over these
trunks, and trunk size.
(2) a table, with 15 entries, showing how
traffic between each city pair entry is routed, and the expected
average
one-way end-to-end delivery delays traffic will face moving over this
route, in each direction.
NOTE: If you use asymmetrical routing (different
paths in different directions) your table in (2) will need to be
doubled
in size, and your diagram in (1) should clearly indicate the average
amount
of traffic routed in each direction.
(3) a list of costs (links & router cards)
(4) Sample calculations for EndtoEndPropagationDelay (pick one
link and show your calculations for that link).
Working bids will be considered for extra credit
points. The low bid will be that working design with the lowest
monthly
cost. The low bid designer(s) will receive 20 extra credit points. The
2nd lowest bid designer(s) will receive 15 points, and the 3rd lowest
bid
designer(s) will receive 10 points. All remaining designs with cost
<
the average class cost will receive 5 points extra credit. The
instructor reserves the
right
to modify these rules in the event of a tie and to deduct points for
crappy
designs.
<<<<<end>>>>>