Cisco recently concluded a two part webinar series, Be Open To The NFV Ideas That Matter Most, with the release of SDxCentrals NFV Mega Reports. In the webinar series, we learned about the role NFV has in creating an open network architecture that addresses those business needs and highlight opportunities for new services that operators can deliver, how Cisco VNFs fit into the larger SP architecture, and much more. If you haven’t already done so, watch the webinar series on-demand:
Special thanks to those who joined us and submitted questions to the Cisco webinar series. The presenters ran out of time and did not get to all your questions but the Be Open To the NFV Ideas That Matter Most Q&A is now available below:
Why does the market opportunity for Managed and Hosted services increase by 15%?
Cisco: As mentioned in the webinar, AMI-Partners has ongoing research into the spending businesses of all sizes do and plan for Information and Communications Technology. Using their forecasting methodologies coupled with the custom survey research results, AMI-Partners calculated the 15% impact and expansion that NFV/SDN can drive.
What types of services are a part of Remotely Managed IT Services (RMITS)?
Cisco: Remotely Managed IT Services include managed networking (WAN, VPN, etc.), managed security (IPS, FW, web, etc.), managed mobile devices, remotely managed servers and storage.
Open source is very important, but then how do vendors position themselves to this open source impact?
Cisco: I can’t speak for other vendors but how we see it is: up until networking got open source fever, many engineers across vendors and operators spent too much time effectively do the same thing over and over without adding intellectual property value. This work is best done by community where everyone can contribute and draw from. This actually frees up engineering talent to work on stuff which adds IP value. Of course, to work, companies must contribute as much as use. We think we and the industry as on the whole will be much better off by making open source projects work. Sometimes it looks ugly, but long term very beneficial.
How does the open network architecture differ from Cisco ACI?
Cisco: Open network architecture is a vision we have for SP networks; it’s not a branded term but rather a general term to provide a high level way of describing key layers and thus highlight the major abstraction points (services to infrastructure for example) in a SP network from apps to infrastructure. ACI is a Cisco branded solution set that uses SDN principles and adds application policy control and management to how apps and network interact.
ACI is part of the Open Network Architecture. ACI is focused on the Data Center and from there via modules into the Enterprise WAN. Look at ACI as a module within a larger set of software modules. The Open Network Architecture allows to combine ACI with other tools like analytics or SD WAN solutions.
What does CMTS stand for?
Cisco: Cable Modem Termination System (CMTS), which is part of the MSO (cable) architecture.
What percentage of SDN/NFV will cannibalize existing services or will the projected growth be purely additive/organic to existing business?
Cisco: There does not seem to be across the board agreement among analysts that we work with on this topic. Rough consensus seems to be that we won’t see significant cannibalization for a few more years. At some point the economics will drive operators to SDN/NFV plus orchestration and open source projects and org changes, because the old business models are not sustainable.
Cisco: Thank you for your question. These services are different as they go beyond IaaS. It is more than just compute and storage service. In the webinar, we look at services like IWAN, VPN, email and Web security, and expand into collaboration services.
Can you identify exactly which Cisco/Redhat products fit where in the MANO/ETSI architecture such as the VIM, VNFM, Orchestrator, etc.
Cisco: Please take a look at our “at a glance”, which should describe the details you are looking for.
Is it possible to build NFV services on top of existing IaaS platforms? Risk and opportunities?
Cisco: Yes it is definitely possible. Risk is high in some cases opportunities, fast in some cases. Deployments at scale need special a NFVi.
Do you see MANO (management and orchestration) being far behind the maturity curve relative to NFV and NFVi? Or are they at the same stage?
Cisco: Thank you for your question. They develop in close relation to each other. Also, MANO covers more than virtual functions, as we mentioned today and during the last webinar. Therefore its scope and capabilities should not be seen as limited by NFV.