THE NEED FOR INCREASED VISIBILITY IN VIRTUALIZED INFRASTRUCTURES
The traditional approach to network monitoring, using taps, splitters and physical probes, does not provide sufficient visibility in virtualized infrastructures for operator requirements. Physical probes cannot access the logical interfaces between internal VM-to-VM communication to monitor functions hosted on the same server, or in some cases between VMs located on different servers connected via virtual overlay networks. Moreover, new virtualization techniques, such as containers that rely heavily on distributing traffic between many lightweight, even transient, virtualized resources only exacerbate the visibility problem. Qosmos DPI-based NFV probe has been developed specifically to provide monitoring solutions with granular visibility into network activity across virtualized infrastructures.
QOSMOS PROBE SOLUTION
The Qosmos NFV Probe has been developed to provide non-intrusive visibility into network infrastructures. It identifies the application behind each IP session and delivers detailed metadata from protocols and applications. Relevant classification information and metadata is available either in real time, via an API, or from a standard database with an open data model.
At the heart of the probe is Qosmos ixEngine®, the market leading Deep Packet Inspection (DPI) engine that provides detailed real-time IP traffic classification and metadata extraction.
The Qosmos NFV Probe can be deployed to monitor both the external traffic on the virtualization platform’s physical interfaces, as well as VM-to-VM communications. Monitoring can be performed continuously or on-demand, depending on needs and data storage capabilities.
The Qosmos probe can be integrated in two ways:
- Software instance on a hypervisor monitoring the entire NFVI layer (resources and network)
- VNF running on a virtual machine to monitor specific VNFs
Implementation example based on NFV reference architecture
The Qosmos Probe can be deployed to monitor both the external traffic on the virtualization platform’s physical interfaces, as well as VM-to-VM communications. Monitoring can be performed continuously or on-demand, depending on needs and data storage capabilities.
EXAMPLES OF TRAFFIC DATA FOR CREATING KPIS
- VM and container names
- DNS resolution
- Volume per minute, IP address, VM, domain name, etc.
- Subscriber information (e.g. IMSI, IMEI, MSISDN, etc.)
- High-degree of information granularity for advanced troubleshooting of faults and performance issues
- Fully customizable extraction of traffic information and KPIs
- Optimized and dynamic configuration: monitoring can be turned on and off to investigate issues only when needed
- A single monitoring approach for hybrid environments where network services run across both physical and virtual functions
- Data model optimized for correlating network counters (response time, QoE, etc.) with infrastructure elements (VMs, containers, domains)
- Follows NFV standards for future proofing
- Runs on commodity hardware