HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

3.9 CONFIGURATION AND CHANGE MANAGEMENT PROCESS REQUIREMENTS

Are configuration and change management procedures in place? Failure to have these in place and follow them could mean a disaster. Even for minor changes to the system. For example, if one maverick turns on level-2 discovery at a collection station that manages an entirely switched network infrastructure at a remote site, the upstream management servers' object database goes from maintaining 3000 objects to tens, if not hundreds, of thousands. It may seem like a "minor" change to one person but can mean downtime for many other operators because the upstream management station was not designed to handle the disk operations and the memory required to synchronize maps with that many objects. Stick to the developed C and CM processes to avoid unplanned downtime.

It is essential to test everything before deployment to production systems. If there is funding for test suites, purchase them. Use them to test deployment strategies, template distribution, alarm and automatic action testing, upgrades, patching and anything else that comes to mind. It will be well worth the money spent.