FAQ About Our VCX Controller and vCPE Solutions

Posted by Scott Sumner on Thursday, June 25, 2015 with No comments
We recently hosted an SDxCentral DemoFriday to introduce our new VCX Controller, and show how it addresses vCPE applications for enterprise and hybrid-cloud connectivity.

Here is the link if you'd like to see the replay.

Following this webinar, we received several great questions about our solution. Here are the questions and brief answers.

Please contact me or post a reply here if you'd like to learn more in-depth.

1.      Do you need NFV expertise (like knowledge of ETSI MANO) to use this solution?
No experience is necessary. Despite the use of NFV principles to reduce the vCPE hardware to the absolute minimum, the VCX Controller virtual appliance uses the same user interface, and supports the same CLI command set as its physical appliance (NID) predecessors. The VCX can also be delivered on a physical appliance. However, the VCX can also be run as a virtual machine on KVM or XXX, and can be orchestrated by a variety of open source and third party orchestrators.

2.      Does the solution support distributed NFV (D-NFV)?
Yes, multiple VCX Controllers can be installed throughout a network to support localization requirements where NFVI hosting certain performance assurance functions requires local processing or very low latency response – e.g. packet capture to feed to a locally installed DPI appliance. Generally, though, the VCX is centrally installed in a data center. As time stamping for all performance assurance functions is performed at the monitoring point by the Nano smart SFP or the ant Module, telemetry delay is does not affect delay measurement precision.

3.      How would existing management systems interface with the virtualized solution, compared to the physical NIDs?
External platforms can communicate in the same way with the VCX controller as they would with a standalone NID – SNMP, CLI, open-API or by using a web GUI. Each module is seen as a remote port, so that element management systems require only one connection to a VCX to manage all modules under its control. This approach is highly cost effective from an NMS / EMS licensing perspective. The familiar communication options makes migration from physical to a hybrid or fully virtualized instrumentation / vCPE environment straightforward, as operational procedures can be maintained without modification, in most cases.

4.      What are the cost benefits vs. alternatives?
vCPE and monitoring solutions using the VCX and Accedian Performance Modules in place of standalone NIDs or routers can be up to 90% less expensive, depending on configuration and scale. Accedian has an ROI tool to help service providers calculate their savings. Please visit Accedian.com/contact to discuss with a member of their engineering services team.

5.      Can this solution use existing network elements as test endpoints, instead of requiring the smart SFP?
Yes, as the VCX Controller and modules support standards-based performance assurance protocols like RFC-2544 and Y.1564 for service activation testing (SAT), and TWAMP and SOAM (RFC-5357 and Y.1731) for performance monitoring, they can interact with existing infrastructure supporting these standards, using these network elements as test reflectors instead of requiring modules or NIDs to be installed.

6.      How many service providers have actually deployed this? Is it available now?
To date, seven of the largest service providers globally have installed the solution in scale. Over 100 service providers in more than 25 countries have deployed in trials or regional installations.

7.      Do these physical and virtual solutions work together?
They work seamlessly together, using the same EMS and management methods to ensure operators can migrate to a virtualized CPE method while maintaining their existing installations, as well as choosing a hybrid environment where benefits of this approach are important (e.g. using NIDs for multi-tenant connections, and smart SFP modules for direct fiber connections to an enterprise).

8.      How far can the controller be located from the smart SFPs?
As there is a patented ‘lossless’ telemetry tunnel setup between the VCX Controller, and the Modules under their control, distance is not an issue. A reliable connection with “reasonably” low packet loss is required – any standard management VLAN connection would suffice. Time stamping is locally performed by the module, and communication overhead is minimal, so centralizing one VCX per market or region is feasible, depending on the number of sessions running (e.g. TWAMP monitoring sessions, SAT sessions, etc.).

9.      Is this for LAN or WAN?
This solution can, and is used for both. The standards employed and the resilience designed in follow telecom service provider guidelines, and are certified and hardened for large scale telco networks. The control signaling is also optimized for large geographic areas, making this solution well suited to large-scale WAN deployments, which can be more demanding from an instrumentation and vCPE point of view than a local deployment within a data center. The precision of the monitoring, however, can be used to monitor very short links and substantially identify minute sources of delay and congestion. In short, the solution offers the precision and small footprint required for data center applications (LAN), with the telecom-grade design required for WAN applications.

10.  Is the Nano smart SFP module getting the same/similar capabilities as the VeloCITY series?
Yes, the ultra-fast (100 ┬Ás) microburst detection, time stamping, packet brokering capabilities will be made available in the second generation modules which are now available.

11.   Does the VCX have an API (let's say REST or something like it) to integrate with non-vendor orchestrators?
A number of API options are available, in addition to a REST-ful interface, including NetCONF/Yang for SOAM configuration (and expanding to service definition). Please contact Accedian for complete details at Accedian.com/contact

12.  Can you share any more details about the lossless tunnels between the VCX and modules?
The tunnels are TCP-based, but employ proprietary, patented methods to compress bandwidth requirements, while also ensuring the lowest-latency transmission of data between modules and the VCX Controller. The suitability of a network connection is verified when the tunnel is established, to ensure that any connectivity issues are identified before a session is permitted to initiate.

13.  Is the customer traffic encrypted?
The solution does not alter or inspect the payload of the customer traffic in any way. This leaves the service provider many options to perform encryption using their preferred technique (MACSEC, IPSec, etc.) with virtualized or localized encryption methods. Please see our white paper, “vCPE - Performance Assured” for more details.

Categories: ,