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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Actually, <strong>the</strong> purpose of <strong>network</strong> analysis is twofold. First, in order <strong>to</strong> implement any<br />

effective moni<strong>to</strong>ring and management system, you need <strong>to</strong> have an understanding<br />

of how your <strong>network</strong> functions. Your understanding should encompass <strong>the</strong><br />

following:<br />

• WAN link and LAN segment bandwidth utilization<br />

• WAN and LAN pro<strong>to</strong>col usage<br />

• Average and peak utilization <strong>network</strong> response times<br />

• Network traffic flow patterns between segments, gateways, and servers<br />

• Network application services<br />

• Layer 2 and Layer 3 packet statistics<br />

Through <strong>the</strong> use of <strong>network</strong> analysis techniques, you can establish a set of <strong>network</strong><br />

performance baselines. Network baseline data is used for a variety of <strong>network</strong><br />

management-related tasks. For example, when setting up <strong>network</strong> moni<strong>to</strong>ring,<br />

baseline data is used for setting management and moni<strong>to</strong>ring probe alarms.<br />

Although default values ("norms") for most moni<strong>to</strong>ring variables exist, <strong>the</strong>se might<br />

not always apply <strong>to</strong> your <strong>network</strong> environment. By using <strong>network</strong> baseline data <strong>to</strong><br />

set moni<strong>to</strong>ring alarm thresholds, your <strong>network</strong> management system will be more<br />

effective and provide more useful information.<br />

The second purpose of <strong>network</strong> analysis is <strong>to</strong> resolve <strong>network</strong> fault conditions and <strong>to</strong><br />

improve overall <strong>network</strong> performance through performance tuning. Performance<br />

tuning is making configuration and design adjustments <strong>to</strong> <strong>the</strong> <strong>network</strong> <strong>to</strong> improve<br />

its performance based on <strong>the</strong> results of management and analysis data. Again, here<br />

is where <strong>network</strong> baseline data is helpful. If <strong>the</strong> <strong>network</strong> users complain of poor<br />

<strong>network</strong> performance, without any performance baseline data it is difficult <strong>to</strong><br />

pinpoint a cause. Therefore, instead of identifying <strong>the</strong> actual problem, additional<br />

resources are implemented which might or might not actually fix <strong>the</strong> problem. There<br />

are some contexts where additional <strong>network</strong> resources are needed, but<br />

implementing <strong>the</strong>m without identifying <strong>the</strong> actual problem you are trying <strong>to</strong> correct<br />

can sometimes make <strong>the</strong> problem worse. Throwing money at performance<br />

problems is an expensive approach <strong>to</strong> resolving <strong>the</strong>m. Your approach <strong>to</strong> <strong>network</strong><br />

analysis depends largely on whe<strong>the</strong>r you are determining <strong>the</strong> <strong>network</strong>'s<br />

performance baseline or resolving a <strong>network</strong> performance or fault condition.<br />

Tools<br />

Although <strong>network</strong> management systems and vendor-specific GUI-based<br />

configuration <strong>to</strong>ols are <strong>the</strong> most commonly associated <strong>network</strong>ing <strong>to</strong>ols for <strong>network</strong><br />

data collection and diagnostics, <strong>the</strong>y are not <strong>the</strong> only <strong>to</strong>ols needed <strong>to</strong> effectively<br />

manage your <strong>network</strong>. Packet analyzers or packet sniffers, time domain reflec<strong>to</strong>rs,<br />

bit error rate testers, and software <strong>to</strong>ols like ping and traceroute are each valuable<br />

<strong>to</strong>ols that you will at some point need in order <strong>to</strong> resolve a problem on your <strong>network</strong>.

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

Saved successfully!

Ooh no, something went wrong!