09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

traceroute <strong>to</strong> www.yahoo.com (204.71.200.74), 30 hops max, 40 byte packets<br />

1 enss (192.207.123.1) 4.871 ms 1.988 ms 2.334 ms<br />

2 (137.39.3.89) 6.034 ms 13.311 ms 6.728 ms<br />

3 (146.188.177.134) 5.914 ms 5.232 ms 5.042 ms<br />

4 (146.188.177.149) 6.619 ms 12.762 ms 7.101 ms<br />

5 (206.132.150.129) 7.227 ms 6.767 ms 6.327 ms<br />

6 (206.132.253.97) 6.392 ms 117.242 ms 70.468 ms<br />

7 (206.132.151.22) 133.405 ms 75.601 ms 89.595 ms<br />

8 (206.132.254.41) 239.353 ms 239.590 ms 241.420 ms<br />

9 (208.178.103.58) 291.413 ms *<br />

10 www9.yahoo.com (204.71.200.74) 73.694 ms 68.444 ms 67.123 ms<br />

Traceroute is available for UNIX (it is native on some UNIX implementations; for<br />

o<strong>the</strong>rs, it is available as source on <strong>the</strong> Internet), Windows NT (native), Windows<br />

95/98, and Macin<strong>to</strong>sh (as a shareware add-on), and as part of Cisco IOS.<br />

Network Baselining and Problem Identification<br />

Network performance baselining is <strong>the</strong> measurement of key performance aspects of<br />

<strong>the</strong> <strong>network</strong>'s operation. Data collection is done in sampled increments over a fixed<br />

period of time so that an accurate picture of <strong>the</strong> <strong>network</strong>'s traffic flow patterns can<br />

be established. The idea is that regular baselining is continuously performed, with<br />

comparisons made <strong>to</strong> previous performance baselines.<br />

Ideally, baselining should begin when <strong>the</strong> <strong>network</strong> is placed in<strong>to</strong> production.<br />

However, baselining can be helpful no matter when you start. The following are just<br />

some of <strong>the</strong> reasons for performing <strong>network</strong> baselining:<br />

• Ensure that your design is suitable for your user requirements. Most data<br />

<strong>network</strong>s grow out of necessity, not planning. A business is started, it moves<br />

in<strong>to</strong> office space, it purchases some computers, it needs a LAN, and so on.<br />

This is not what is considered <strong>to</strong> be a designed <strong>network</strong>. Ra<strong>the</strong>r, it's just a<br />

collection of computers connected <strong>to</strong>ge<strong>the</strong>r. A sort of "orange juice can and<br />

string" <strong>network</strong>—you can hear sound (move data) on it, and you are happy.<br />

This is a very common approach in <strong>the</strong> start of new businesses, since<br />

<strong>network</strong>ed communication between computers is usually <strong>the</strong> only design<br />

goal. So if it works, that's usually all that matters.<br />

• Later on, <strong>the</strong> business grows and <strong>network</strong>-dependent applications start <strong>to</strong><br />

become important <strong>to</strong> business function that <strong>the</strong> <strong>network</strong>'s initial reactive<br />

design approach begins <strong>to</strong> show its limitations. Unfortunately, this is also<br />

usually <strong>the</strong> time that a business can least afford any major business<br />

disruption, such as a new <strong>network</strong> implementation or a painful <strong>network</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!