- For years, enterprises invested in ‘good enough’ networks merely to make sure the plumbing connected everything together functionally.
- With cloud adoption rapidly increasing, fewer applications residing on-premises, and business continuity depending on 24×7 network access, enterprises need to re-think the network design and approach.
Enterprise networks were designed for years (and, to a large degree, still are) for three application areas: campus (or access), core, and data center. With cloud and ‘anywhere’ access of mission-critical applications, users must have quality access to resources no matter the connection point. Whether wired Ethernet, WLAN, wireless 3G/4G, or other means, downtime is unacceptable. Yet, as RFQs go out, access resilience is missing or getting surprisingly low priority. I contend that enterprises must raise the stakes and invest in redundant power, resilient management (whether in-box or in-stack), resilient protocols, and ultimately solid management interfaces (assurance, monitoring, orchestration, etc.). Now, it is true that redundant links have become more prominent with the availability of commercial cable and DSL at aggressive prices (relative to fractional T and frame a decade ago), yet within the campus, surprisingly few switches or WLAN have RPS or resilient, distributed uplinks. Continue reading “With Network Dependence Critical, Is Downtime Acceptable?”
You must be logged in to post a comment.