catch on. Within six months, we had SO greatly improved the network that it was no longer the source of any problems. With a stable network came stable services. Long-term thinking is the only way to accomplish stability in an unstable environ- ment. Enforcing these three simple rules caused the network to go from being a point of ridicule for upper management to being a source of pride. Here's a closer look at the three rules: Chapter 37: GAD's Maxims Simplify This one is pretty straightforward. To comply with this rule, a proposed change must simplify the network or its operation in some way. Examples might include removing equipment, or replacing a complex IP scheme with one that's easier to understand or maintain. Perhaps the change will cause all of the routers to have the same revision of code. Anything that makes the operation or troubleshoot- ing of the network less complex saves time and money. Simple is good. If you can easily explain how a change will enhance the simplicity of the network, chances are the change is a valid one. Standardize Standardization can also make networks more cost-effective and easier to main- tain. If you have 200 routers, and they're all the same model, you will know what to expect from each router when you connect to it. While that may not be realistic, having a standard device for every function, and standard ways to deploy services, is. You can make all of your edge routers, the core switches in every building, and SO on, the same type. If you deploy NTP, it should be deployed the same way everywhere. Standardization allows for spares to be more readily available, and it allows for devices to be swapped in from less critical places in an emergency. Stabilize How to enhance stability is not always obvious. Perhaps the revision of IOS code that has been standardized on all the VoIP gateways has been reported to have an issue that might affect your environment. That code should no longer be con- sidered stable, and should be updated. Likewise, if there is a piece of hardware t