Cisco CCNP CIT Exam Training: Creating A Network Baseline
- Date: 2006-12-05 - Word Count: 515
Share This!
The first thing we've got to do in order to document our network is to create a network baseline. After all, if we don't know our goals, we can't accomplish them. A baseline is really a "network snapshot", a picture of our network devices and their performance - which also helps us spot issues before they happen.
Every network has its "breaking point", the point at which it can no longer transfer data effectively. By creating a baseline, you can see what the current network load is now - and by maintaining that baseline, you can spot network issues well before they become critical. For example, say you baseline all your network routers, and part of that is noting the CPU capability and usage. By maintaining the network baseline, you can note smaller, gradual increases in CPU usage and do something about it before the situation becomes critical.
Establishing a baseline also gives less-experienced network personnel a starting point for troubleshooting, and it gives new network support personnel a starting point as well.
To begin that task, we've got to define where this baseline will begin and end - in other words, we must define the scope of the baseline. Some questions to ask:
What is the scope of this baseline?
What goals do we have for our network?
What network devices will be part of this baseline?
What is the objective here? Why are we creating this baseline?
Baseline construction methods differ from one vendor to another, but I recommend the first thing you do when creating a baseline is taking inventory. Why? First, it's hard to create a full network picture if you don't know everything that's in your network; second, many networks are poorly inventoried.
When you're creating network documentation, consistency is vital. This goes for abbreviations, symbols, and icons. There are sets of Cisco icons for use in Microsoft Visio - find and use these icons when documenting and diagramming your network. Keep your usage of these icons consistent as well.
Decide upon your scope and your goals, and stick with that decision. Don't start documenting one part of the network and then jump to another part.
Also, don't hide the documentation! If I have to substitute for you at a client site, I should be able to find the documentation without asking anyone.
Most importantly, maintain the documentation. Nothing is worse than seeing a date at the top of a network baseline doc that's from last year. (Or the last century.) Don't fall into the trap of "I'll catch the documentation up next week", because I can practically guarantee that no matter how great your work ethic is, something's going to happen that will distract you from getting the documentation done. Do it now.
In short, when creating network documentation, follow these rules:
Define the scope of the documentation and stick to it.
Define your objective and the values to be documented.
Consistency is key. Keep abbreviations and terminology consistent from document to document.
Make sure the appropriate personnel have access to the documentation.
Keep the documentation current.
Your client will thank you, and those that follow you will thank you as well!
Every network has its "breaking point", the point at which it can no longer transfer data effectively. By creating a baseline, you can see what the current network load is now - and by maintaining that baseline, you can spot network issues well before they become critical. For example, say you baseline all your network routers, and part of that is noting the CPU capability and usage. By maintaining the network baseline, you can note smaller, gradual increases in CPU usage and do something about it before the situation becomes critical.
Establishing a baseline also gives less-experienced network personnel a starting point for troubleshooting, and it gives new network support personnel a starting point as well.
To begin that task, we've got to define where this baseline will begin and end - in other words, we must define the scope of the baseline. Some questions to ask:
What is the scope of this baseline?
What goals do we have for our network?
What network devices will be part of this baseline?
What is the objective here? Why are we creating this baseline?
Baseline construction methods differ from one vendor to another, but I recommend the first thing you do when creating a baseline is taking inventory. Why? First, it's hard to create a full network picture if you don't know everything that's in your network; second, many networks are poorly inventoried.
When you're creating network documentation, consistency is vital. This goes for abbreviations, symbols, and icons. There are sets of Cisco icons for use in Microsoft Visio - find and use these icons when documenting and diagramming your network. Keep your usage of these icons consistent as well.
Decide upon your scope and your goals, and stick with that decision. Don't start documenting one part of the network and then jump to another part.
Also, don't hide the documentation! If I have to substitute for you at a client site, I should be able to find the documentation without asking anyone.
Most importantly, maintain the documentation. Nothing is worse than seeing a date at the top of a network baseline doc that's from last year. (Or the last century.) Don't fall into the trap of "I'll catch the documentation up next week", because I can practically guarantee that no matter how great your work ethic is, something's going to happen that will distract you from getting the documentation done. Do it now.
In short, when creating network documentation, follow these rules:
Define the scope of the documentation and stick to it.
Define your objective and the values to be documented.
Consistency is key. Keep abbreviations and terminology consistent from document to document.
Make sure the appropriate personnel have access to the documentation.
Keep the documentation current.
Your client will thank you, and those that follow you will thank you as well!
Related Tags: network, exam, cisco, ccnp, cit, baseline
Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage, home of over 100 free certification exam tutorials, including Cisco CCNA certification test prep articles. His exclusive Cisco CCNA study guide and Cisco CCNA training is also available!Visit his blog and sign up for Cisco Certification Central, a daily newsletter packed with CCNA, Network+, Security+, A+, and CCNP certification exam practice questions! A free 7-part course, "How To Pass The CCNA", is also available, and you can attend an in-person or online CCNA boot camp with The Bryant Advantage! Your Article Search Directory : Find in Articles
Recent articles in this category:
- What Is An Sd Card? What Are Main Types Of Sd Cards
Manufactured as a competition offering to Sony's Memory Stick, the SD Card was developed by the SD C - Industrial Computers
In this day and age you can't afford to run an industry efficiently without a computer as it plays a - Computer Fix Services - Tips To Choose Good Quality Personal Computer Maintenance Online
Online computer repair services have become a fast and reliable problem solution for day to day tech - Reverse Engineering Romer For Aerospace
One of the most amazing things about reverse engineering is its significant contribution in any fiel - How To Buy The Best Projector Bulb
It is very important for you to know the right time to change the projector bulb before it will burn - Laptops Vs Desktops- Their Significance
Computers obviously are commonly used for more or less everything from entertainment to office work. - Cooling Your Laptop
It is common knowledge that laptops are commonly used by everyone but one must also know how to take - Dymo Labelwriter Fast Performance & Reliability
I don't think I'm the only one who has gotten tired of trips to the post office, standing in endless - Buying Dell Laptops A Long Time Investment
Today if you go to an office or a school, Dell laptops can be seen very commonly. Though we do not b - Hard Drives - Digital Space
The first hard drives (Hard Disk Drives, HDD) were developed by IBM in 1956. Since then the need for
Most viewed articles in this category:
- Video Killed the Beautiful View
"The sound brought our group to a stop; we turned around to see the ice mass collapse with a roar. A - Crossfire: The Dual GPU System Gamers Want
CrossFire is the new dual graphics card system from ATI. It offers remarkable image quality improvem - Canon PIXMA IP1600 Photo Printer Review & Its True Cost of Ownership
With Canon PIXMA iP1600 Inkjet Printer you can make high quality photo printings at home. No need to - Basic Information about Nero Burn DVD
Nero is a popular burning ROM designed to burn DVD's. The way this product got its name is very inte - The Development of the Vital IBM PC in Spite of the Corporate Culture of IBM
The public history of the PC began in August 1981, when IBM first announced "The IBM Personal Comput - PC Repairs
PC Repairs are often needed when we need our computer the most. One way to take away many problems o - Affordable Computer Printer Ink
The computer - once considered a luxury item - has easily become a staple in today's modern homes; a - Build your Own PC
Build your own PC! Simple and Fun. Just follow these instructions and you're on your way to a rel - Extending the Life of an Inkjet Printer with Proper Cleaning and Maintenance
Inkjet printers are becoming another "throw away" electronic device due to reducing costs and high i - Check Printers
A check printer is a printer that hooks up to a computer that has the capability of printing checks.