5 replies
by ckilday
Joel,
For WAN links, check out error statistics as well. If you've got errors, you're getting re-transmissions which slows response time. Check for carrier drops or interface resets on your routers. They indicate a flakey circuit. That can cause re-synchronization, dropped sessions and lost time and productivity for your users. If you're buying bandwidth from a carrier, check out their report on the circuit. Most carriers commit to a specified percentage of uptime and usually keep track of something called "errored seconds". If there are a lot of these "errored seconds", you might be due a rebate on part of the circuit cost. It's also good ammunition to push for a fix from them. You need the circuits to be healthy so you can get accurate readings on your bandwidth utilization, etc... Hope this helps.
- ck
by joel_sweatte
by mel "blazing_saddles" dundee
You haven't been very specific as to where you want to look at these issues.
Do you have access to a router?
If so what type is it?
If so what protocols are you running?
What are your WAN links? This determines mibs or commands you would use.
Are you using a sniffer?
Have you looked at packet shapers between your WAN and Main site LAN. New Application management packages are now available for Layer 7 management.
Factors to look at in routers include buffers,memory, cpu utilization aside what the previous answer has given on interface stats
Accounting is a useful tool.
Collisions are also important to watch on LANS
Traffic shaping (for Frame Relay) from a central site to Tail sites will improve performance out of site on busy links in a central to tail site direction where multiple sites are employed and bandwidths of links vary.
Queuing strategies can be investigated
Compression can be considered
by joel_sweatte
by joel_sweatte
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending