The Organizational NOS (Network Operating System)

Transcription

1 The Organizatinal NOS ( Operating System) Bryan.vandussen@reedbusiness.cm Nvember 2008 The Organizatinal NOS Executive Summary perating systems (perating systems designed and develped fr netwrking devices such as ruters and switches [NOSs]) have traditinally been designed t meet the needs f their hardware and innvative new netwrk-based applicatins. Hwever, the expected explsin in netwrk vide traffic driven by mbility, business Internet, cnsumer Internet, and cnsumer IPTV/CATV services have drastically changed the cmplexity f netwrk architectures and have changed hw NOSs are designed and used. Instead f a single NOS generically designed fr all devices, the new NOS is designed fr the psitin the devices ccupy in the netwrk (access, cre, data center, custmer premise) and peple and rganizatins that use and manage them. The result is a mre custmized netwrk perating system made fr peratinal grups and individuals the rganizatinal NOS. Unlike an verarching single NOS that attempts t meet all the requirements f all devices, in all areas f the netwrk, fr all services, and every grup that perates and manages them, rganizatinal NOSs are tailred t meet the unique requirements f the peple and prcesses that perate and manage a variety f service prvider, enterprise, and cnsumer netwrks. Organizatinal NOSs als prvide a cmmn language that enables rganizatins and their netwrks t seamlessly cmmunicate and interperate. The rganizatinal NOS s ability t satisfy the diverse peratinal requirements f a variety f grups and individuals while preserving and enhancing the interactin between them, enables netwrks t be used in new ways. Organizatinal NOS s help peratrs f all sizes, capability, and levels f expertise deliver new services at unprecedented speed with unmatched availability. This paper argues that a single NOS may nt be the mst efficient apprach. Instead, NOSs shuld be designed nt nly fr the place in the netwrk ccupied by the devices, but als t meet the needs f the peple and prcesses that use them. Organizatinal NOSs One Size Des Nt Fit All NOSs have been used in a wide variety f devices by a wide variety f rganizatins fr decades. Dating back t the first nn-mechanical telephne switch and including many f tday s ruters, switches, security appliances, vice, vide, applicatin ptimizers, strage appliances, and ther netwrk devices; NOSs have been used as the platfrm fr delivering nt nly basic netwrk transmissin, switching, and ruting, but als fr a wide range f enhanced vice, vide, and data services. These devices have als been used in a number f places in netwrks by a variety f rganizatins, grups, and individuals that range frm the largest netwrk service prvider and crprate enterprise t the individual perating a hme wired r wireless netwrk. The netwrking devices, althugh sized r cnfigured t meet a variety f psitins r functins in the netwrk service prvider cre and edge, the data center, branch ffice access, small and mediumsized business access, and hme netwrking may use an perating system that is nt tailred t its 2008 In-Stat All Rights Reserved

2 The Organizatinal NOS place in the netwrk nr t the peple and prcesses that emply it. Fr example: service prvider persnnel might discver that the NOS in their cre ruters include enterprise features such as SNA r AppleTalk supprt. Or, an enterprise r small business IT grup might find that an access ruter NOS includes supprt fr MPLS r integratin with a service prvider-riented back ffice system. Organizatins r individuals using netwrking devices that have t many r t few NOS capabilities can impact nt nly the efficiency f the rganizatin and peple using the devices, but als create: Blated NOS s that use large amunts f RAM, yet still deliver pr perfrmance: Anyne wh has attempted t upgrade a persnal cmputer that has limited CPU and RAM capacity with a new OS that has a larger image with mre functinality, knws that a big OS can slw things dwn r frce the user t invest in hardware upgrades. In the netwrk, the same scenari hlds true. T much OS functinality in a small device can result in pr perfrmance and additinal cst. Cmplex integratin with service prvider and enterprise security, management, prvisining, and billing systems: Service prviders invest millins f dllars in their management, prvisining, and billing systems. A NOS that includes features and functins that may be well suited fr enterprise netwrks r include access features in cre netwrk devices, can add cmplexity t the task f tying the device t back ffice systems. This can result in increased sftware develpment and maintenance csts, as well as lnger lead times t develp and launch new netwrk-based services. Lengthy timelines t perfrm sftware maintenance: Any NOS that increases sftware cmplexity by including nn-essential features and functins can als make it mre difficult fr netwrk peratrs t update sftware t accmmdate bug fixes and ther sftware changes. Operatrs can face extra regressin and interperability testing t ensure cmpatibility fr features that are nt used in specific netwrk areas r devices. In sme cases, bug fix might even require nt just a sftware relad, but als a visit by a technician t perfrm the hardware upgrade. Increased training and re-training csts: Even thugh an rganizatin may nt use a specific feature r functin in a NOS, users f that NOS must nevertheless understand the features and be familiar with cnfiguratin ptins fr them. Higher cst t perate and maintain netwrks: Larger sftware images, increased sftware cmplexity, and mre difficult integratin with netwrk management and back ffice systems increases peratins and maintenance csts. NOSs that are nt tailred t meet the needs f the rganizatins that use them increase the number f peple required t supprt them as well. A NOS, custmized t meet the needs f the place in the netwrk it ccupies and the rganizatin that perates it, is simpler, mre cst effective, and easier t integrate with management and back ffice systems. Let s examine the peple wh use NOSs and their needs and hw the rganizatinal NOS has been develped t meet thse needs In-Stat All Rights Reserved Page 2

3 The Right NOS fr the Right Organizatin The Organizatinal NOS There are several discrete rganizatins and individuals that use netwrk perating systems. In sme cases, their needs and the tasks they perfrm verlap, hwever, in general each rganizatin has specific peratinal requirements that make a custmized NOS essential. In general, NOS rganizatins fall int eight categries that in general map t specific places devices ccupy in the netwrk (access, cre, data center, custmer premise): Service Prviders Large Enterprise Transmissin Grup: Respnsible fr Layer 1, 2, and sme Layer 3 services and the prcesses and interfaces t back ffice systems that supprt them. Access Grup: Respnsible fr Layer 3 services, netwrk quality f service, and sme netwrk-based applicatins services (fr example security) as well as the prcesses and interfaces t back ffice systems that supprt them. Grups: Respnsible fr data center, vice, vide, netwrk-based applicatins services and back ffice systems. There are ften multiple applicatin grups within large service prviders. Managed Services: Respnsible fr custmer premise equipment and "clud" cmputing as well as the back ffice systems that supprt them. Access and Branch Office Grup: Respnsible fr Layer 2 and 3 services, as well as basic netwrk-based capabilities such as Security. This grup is als respnsible fr the netwrk management systems that supprt the services they prvide. Grups: Respnsible fr data center, vice, vide, netwrk-based applicatins services and back ffice systems. There are ften multiple applicatin grups within large enterprises. Small and Medium Sized Businesses and Hme Owners Small and Medium Sized Businesses: Often have limited capital budgets and persnnel dedicated t netwrking frcing netwrk devices and managers t d it all at a lw cst. Hme Owners: Often implement Layer 2 and 3 and security services In-Stat All Rights Reserved Page 3

4 The Organizatinal NOS Figure 1 illustrates the rganizatins that use NOSs and the applicatins and services that they supprt. Figure 1: Wh Operates the? (Surce: In-Stat) Service Prvider Enterprise Access Grup: based Grup(s): Data Center, Vice, Vide, based, Access and Branch Office: Layer 2 Transmissin Grup : Layer 3, Layer 2, Transmissin Ser and Managed Services Grup(s): Data Center, Vice, Vide, based, Back Office Operatins: Data Center, Vice, Vide,,, Security, Layer 3, Layer 2 SMB and Hme s In Table 1, the NOS needs f the rganizatins utlined abve are examined. Fr service prviders and large enterprises, flexibility, integratin with netwrk management and back ffice systems, and an expert interface are key attributes. Fr SMB s and hme users, simplicity, ease f use, and a GUI are critical. Attribute Table 1: What D Operatrs Need frm the NOS? (Surce: In-Stat) Service Prvider Trans-missin Access and Managed Services Enterprise Access SMB, Hme User Interface Expert, CLI Expert, CLI Expert, CLI Expert, CLI Expert, CLI Webbased GUI Layer_1,_2 Carrier Ethernet, Carrier Ethernet, Limited Ethernet, Optical, Limited Cable, DSL, 2008 In-Stat All Rights Reserved Page 4

5 The Organizatinal NOS Functins Optical, ATM, Frame Relay, TCP Optical, Frame Relay, Cable, DSL, TCP Frame Relay, Wireless, TCP FTTH, Wireless, TCP Layer_3 Functins IP Ruting, MPLS QS, Multicast IP Ruting, QS, IPSec NAC QS, VIP, Vide, DDS Intrusin Detectin IP Ruting, QS, IPSec NAC QS, VIP, Vide, DDS Intrusin Detectin IP Ruting, QS, IPSec Limited NAC Applicatin Functins Links t Back Office Links t Back Office DDS Intrusin Managed Services, Web Hsting, Strage, Mail, Vice, Vide, Back Office System DDS Intrusin Managed Services, Web Hsting, Strage, Mail, Vice, Vide, Manageme nt DDS Preventi n Interface TMN, XML XML APIs, XML XML APIs, XML Webbased GUI Prvisining and Billing CORBA, CORBA, CORBA, XML, APIs Nt Applicable High Availability In Service Sftware Upgrades, Prcess In Service Sftware Upgrades, Prcess Re- In Service Sftware In Service Sftware Upgrade Nt Applicable Nt Applicable 2008 In-Stat All Rights Reserved Page 5

6 The Organizatinal NOS Restartability startability Upgrades, Prcess Restartabili ty s Prgrammabilit y XML XML XML XML Nt Applicable Nt Applicable The peple that perate netwrks have different needs ften based n the devices and area f the netwrk they manage. Therefre, NOSs must be tailred t meet the requirements f each grup and netwrk area. But even by tailring the NOS t the needs f the netwrk place and peratr, it is imprtant t nt lse sight f a final critical requirement fr rganizatinal NOSs interperability. Keeping the Lines f Cmmunicatin Open Althugh service prviders, enterprises, SMBs and hme businesses may use separate NOSs designed specifically fr thse envirnments, rganizatinal NOSs must als prvide a cmmn, interperable language between thse grups and their netwrks. The cmmn language used by each rganizatinal NOS includes several areas where translatins are nt necessary and netwrks and grups can cmmunicate quickly and easily. Cmmunicatins prtcls: IP and IP ruting prtcls such as OSPF, RIP, MPLS and thers prtcls: SNMP Prgramming interfaces: APIs, CORBA, XML Cmmand Line and web-based management interfaces Cmbined, each rganizatinal NOS s cmmn cmmunicatins and management prtcls, prgramming, cmmand-line interface (CLI) and Web-based management interfaces prvide diverse grups with simple, yet pwerful ways t seamlessly perate netwrks acrss rganizatinal and netwrk bundaries. This enables rganizatinal NOSs t meet the unique needs f each peratinal grup and area in the netwrk withut sacrificing the ability t add new functins, services, and capabilities that crss netwrk and rganizatinal bundaries. Organizatinal NOSs make it pssible fr service prviders with cmplex, high capacity netwrks t prvide data, vice, vide, and applicatin services t the business wner perating a simple, hmebased netwrk. Organizatinal NOS s keep the lines f cmmunicatin pen while making it pssible fr rganizatins t simply and cst-effectively implement, manage, and maintain their netwrks and develp and cnsume innvative, netwrk-based service fferings In-Stat All Rights Reserved Page 6

7 The Organizatinal NOS Figure 2: Lines f Cmmunicatin (Surce: In-Stat) Service Prvider Enterprise Access and Branch Office: Layer 2 Access Grup: based Grup(s): Data Center, Vice, Vide, based, Ser and Managed Services Grup(s): Data Center, Vice, Vide, based, Back Office Transmissin Grup : Layer 3, Layer 2, Transmissin Operatins: Data Center, Vice, Vide,,, Security, Layer 3, Layer 2 SMB and Hme s Cnclusin: The Organizatinal NOS A single NOS might appear t be the mst efficient slutin fr every netwrk device, every place in the netwrk, and every netwrk wner. Hwever, upn clser examinatin, a NOS that is custmized t meet the unique needs f the devices, their psitin in the netwrk and the peple and prcesses that use them is mre efficient and cst-effective. The rganizatinal NOS is custmized t nt nly help make managing netwrk devices simpler and mre efficient, it als helps make peratrs, managers, business users, and cnsumers mre prductive and keeps netwrk csts dwn by ensuring that sftware images are nt weighed dwn by extraneus features and functins. Organizatinal NOSs help keep maintenance csts lw, netwrk availability high, and additin f new services and capabilities fast and easy. And, rganizatinal NOSs d this while ensuring that lines f cmmunicatin between rganizatins remain pen and netwrks interperable by speaking a cmmn language f industry standard netwrk prtcls, management, and prgramming interfaces In-Stat All Rights Reserved Page 7