Good network management planning saves time and resources. This tip, from SearchNetworking.com, guides network consultants and systems integrators through a streamlined network management process.
 |
||||
|
|
|||
|
||||
Requires Membership to View
To gain access to this and all member only content, please provide the following information:
By submitting your registration information to SearchNetworkingChannel.com you agree to receive email communications from the TechTarget network of sites, and/or third party content providers that have relationships with TechTarget, based on your topic interests and activity, including updates on new content, event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile, unsubscribing via email or by contacting us here
- Your use of SearchNetworkingChannel.com is governed by our Terms of Use
- We designed our Privacy Policy to provide you with important disclosures about how we collect and use your registration and other information. We encourage you to read the Privacy Policy, and to use it to help make informed decisions.
- If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States.
What information do you want from your network management system? Who should get it? When?
If you take the time to plan for your system, you'll have those questions answered before you spend hours of fruitless time on your system, and your experience won't devolve into too-much-data hell.
Glynn Meek, president and CEO of TriActive Inc., suggests using a six-step planning process to keep things on an even keel.
- Find out what you have. Many organizations lack current network documentation, and without knowing what's out there on the other end of your cabling, you can't even begin to know what you want to monitor. Auto discovery modules do this easily.
- Set network monitoring limits. Do you want to monitor everything on the network? Probably not, so limit your monitoring to those events that will have an impact on the business or on user productivity. Determine this at the business level.
- Find the drivers on the critical business path. If something is happening off the critical path, it's not nearly as important as something that will affect, say, the processing of an online order.
- Determine how often to monitor. You have to set the polling frequency to one that will not bog down your network with management traffic but that will still allow you to know what's happening.
- Determine which IT people to send alerts to. Alert only those who need to deal with the problem, not the whole IT staff. And at the same time, determine who should be in the escalation path. (If Bob can't solve the problem, we escalate to Jim.)
- Set up report reviews on a regular basis. By reviewing your reports, particularly with an eye to spotting trends, you can determine where problems are about to happen and nip them in the bud.
This tip originally appeared on SearchNetworking.com.
This was first published in November 2006