Managing Network Performance
A large, busy network may not work as fast as we like. This lesson looks at ways of monitoring the performance of the network to look for problems.
Bottlenecks
Traditionally bottles have a fat body and a thin neck.
The narrow neck makes the water come out slowly.
In a network, a problem area that slows down the whole network is called a bottleneck. For example if the server does not have enough RAM, this will slow the whole network. It will cause a bottleneck.
One of the goals of monitoring a network’s performance is to look for bottlenecks so that they can be fixed.
Potential bottlenecks include:
Not enough RAM in server
Windows NT Performance Monitor
Performance Monitor is a program that comes with NT. It allows us to watch the performance of various sub-systems of our network.
With Network Monitor you can make graphs or generate performance log files. You can monitor the computer running the program or other computers on the network.
SNMP –Simple Network Management Protocol
This is a system that is built into some hubs, routers, NICs and servers. It enables these devices to log their own performance then report back to a monitoring program.
SNMP is part of the TCP/IP suite of protocols and is an industry standard, allowing devices from different companies to work together.
SMS – System Management Server
This is software from Microsoft for use with NT networks. It does not come with NT; it must be bought separately.
SMS does several jobs:
Maintains an inventory (list) of all hardware and software on the network. This is kept in an SQL database.
Automates the installation of software throughout the network.
Manages shared applications
Allows detailed monitoring of network performance including monitoring of traffic on the cable.
| list of lessons | Course Plan | Instructor's Info | Links | UAE | Guestbook |View Guestbook | Books | Search|HCT|
