Our past couple of blogs delved into how the US Federal Government continues to deploy traditional copper-based LANs while investigating how to add Software Defined Networking (SDN) functionality inside buildings and across campus. Previous blogs covered why we think Tellabs OLAN is architecturally the first best choice for SDN and why legacy copper-based LANs are poorly suited to accommodate SDN.
At this point I can now explain how Tellabs Optical LAN already matches SDN intent and already supports SDN like functionality today. Today, Tellabs OLAN defines network resources in software-based global policies and dynamically allocates them based on real-time network needs. That certainly sounds SDN-like and here are 7 more similarities between OLAN and SDN:
- With OLAN, the architecture and equipment has centralized intelligence and management
- The OLAN ONTs are thin client, no local management, store no network info nor user info, matching SDN “white-box” type device
- Simple and automated operations with policy-based templates and profiles that dynamically control global traffic management parameters
- LAN agility is achieved with scalability through software based actions, M2M automation and plug-and-play of sub-tended connected and powered devices
- OLAN improves security with fewer points of vulnerability (fewer devices and fewer full-functioning port access) and less human touch
- Greater stability is enjoyed with high network availability from fewer moving parts at lower costs
- Savings are gained with lower operational costs and capital costs with OLAN
If you’d like to learn more about this topic, feel free to download our Software Defined LAN Overview. Stay tuned for our last segment of this series, where I explain how Passive Optical LAN ultimately provides a path forward to true open-source and standards-based SDN.