In my last post, I discussed the importance of a strong network foundation. Let’s get a little deeper into this now. The strategies depicted in the diagram below have been developed over nearly two decades of Cisco Services experience in the field. These outline what MUST be addressed in order to successfully and fully optimize your investment. Omission of any one will induce risk into the project. I will highlight this as we pass through the strategies.
The design will impact every other strategy and this is why I am starting here. If I only had a nickel for every network that I “fixed” by moving them off of the old administrative VLANs and to a multi-layer or better routed-access campus model, I would be sipping fruity drinks on a tropical island right now. These customers had invested in the correct hardware but had the wrong design and no matter how well we executed the following strategies, success would not be achieved. The VLANs created large fault domains where a problem with any single element impacted all elements. This design was great in its day, there was only data and no need for real-time services. But the time it takes spanning-tree to converge is simply too long for real-time services.
There is no magic single design that works for all customers and all instances. If you are not familiar with Cisco’s Design Zone it’s important that you visit and bookmark this site. This is where designs that have been proven in the field are documented and posted.
Once hardware is deployed, the next step is to ensure that you have a full inventory of the hardware in your network. Once you have this in hand, you can begin to leverage the information that is posted on Cisco.com. Considerations for hardware include:
- End of Life: Here’s a great example of why understanding the End-of-Life of your hardware and software matters: Imagine you have a new Unified Contact Center solution being deployed but it just hit a snag. The deployed router hardware does not support key features required by this solution. A deeper look reveals that an End-of-Life notice was posted and this hardware passed the End-of-Software-Support milestone some time ago. In order to succeed in deploying this new solution, you need to update your hardware. End result? Project delayed! Make a note, that Last-Date-of-Support (LDoS) is not the only milestone that should be tracked. LDoS represents when TAC will no longer support the hardware. Hardware and software lifecycle can really impact your project. Too new, and you risk encountering issues that have not yet been discovered. Too old, and you risk the problem outlined above. Cisco publishes all notices for End-of-Sale and End-of-Life Products. You should also review the End-of-Life Policy to be aware of the latest milestone and timelines.
- Field Notice: Major issues with products are communicated via field notices. Keeping an eye on these ensures that you are aware of potential impacts to operations and stability of your network – that are not security related (I will address Cisco Security Advisories, Responses, and Notices addressed in a later post). Cisco publishes all of our Product Field Notices.
These hardware considerations can all be a handful to do manually but there are tools to automate tracking end-of-life and field notices. Cisco Prime Infrastructure offers inventory end-of-life and field notice alerting capabilities. Cisco Network Optimization Service (NOS) offers comprehensive reporting and consulting that automates the process of identifying and tracking alerts that could impact your network. More importantly, your NOS engineer will lead in assessing the risk and lead the process to remediate. This service also provides the ability to plug into the stream of Cisco knowledge in real-time. This arms your architecture and engineering teams with the latest best practices from Cisco’s ongoing experience in deploying our solutions. As an example, read how Cisco IT worked alongside NOS engineers for design and testing during a major upgrade.
Look for my upcoming post where I will talk about the next step—software strategy.