- AVC: Application Visibility and Control. Cisco Deep Packet Inspection feature embedded in routers. it enables application recognition based on signature and fields extraction.
- ART: Application Response Time. Cisco passive probe embedded in routers. It enables TCP application performance metrics such as latency per network part.
- BR: Border Router. Cisco PfR component
- CSR: Cloud Services Router
- FNF: Flexible NetFlow. Latest Netflow version.
- IP: Internet Protocol – Layer 3 Datagram Protocol.
- IPFIX: Internet Protocol Flow Information Export. Industry standard for Netflow
- LAN: Local Area Network
- MACE: Measurement, Aggregation, and Correlation Engine
- MC: Master Controller Cisco PfR component
- MMA: Cisco Metric Mediation Agent. Cisco passive probe embedded in routers. It enables TCP & UDP application performance metrics.
- NAT: Network Address Translation
- DPI: Deep Packet Inspection. Generic name for application recognition engine over telecommunication network.
- NBAR2: Network Based Application Recognition. Cisco Deep Packet Inspection Engine
- PfR: Performance Routing
- SNMP: Simple Network Management Protocol
- TCP: Transmission Control Protocol—L4 Reliable Transport Mechanism.
- UDP: User Datagram Protocol—L4 Transport Mechanism. Connectionless transport layer protocol
- VRF: Virtual Routing and Forwarding
- WAAS: Wide Area Application Services
- WAN: Wide Area Network
Cisco is a feature bundle embedded in routers, targeted at improving end-user experience when they use applications over Wide Area Network (WAN). Cisco IWAN provides the ability to report your application performance metrics, enables per-application policy for granular control of application bandwidth use (Application Visibilty and Control, AVC), monitors network performance and selects the best path for each Class of Service (Performance Routing, PfR), and optimize application traffic for faster response time and less bandwidth (Wide Area Application Services, WaaS).
Netflow version 9 and IPFIX are the protocols of choices for Cisco IWAN to export information from the routers.
eye.lo is a probe-less application-aware platform. Network information are exported by IWAN features towards eye.lo through an open export format Netflow Version 9 and IP Flow Information Export (IPFIX).
Eye.lo leverages Cisco AVC application recognition and performance metrics to:
- Provide visibility into different types of traffic,
- Quickly isolate and troubleshoot application performance issues,
- Check CoS policy consistency across the Network
eye.lo leverages Cisco PfR data to:
- Display synthetic view of hybrid infrastructure based on path change & out-of-policy event.
- Provide full visibility on traffic per path when PfR intelligently load balances traffic over all WAN paths to protect critical applications from fluctuating WAN performance.
- Understand performance issue based metrics (Jitter, latency, loss)
eye.lo is a multi-tenant software platform dedicated to Service Provider. Its distributed architecture, based on redundant nodes, insures smooth scalability, optimal level of use of resources, fault tolerance and low latency response for the concurrent requests and big data.
LivingObjects recommends a centralized collection to ease implementation of new customers. However, eye.lo can also be deployed in isolated environment.
eye.lo installation and operation don’t need any additional 3rd party license or tool to deliver full visibility on critical application. eye.lo is a probe-less solution which leverages advanced metrics provided by Cisco Intelligent WAN features embedded in Customers Premises Equipment (CPE). No additional box is needed to provide full visibility on critical application over the network.
Cisco IWAN + eye.lo, without any additional box, enables:
- Full visibility on application traffic and optimization
- Multi-tenant massive deployment
- Sober storage strategy & best responsiveness
Highly customizable environment
eye.lo is deployed in Service Providers’ DCs on a single server or a distributed infrastructure. Above 3000 routers, LivingObjects recommends a distributed architecture which enables smooth scalability across time. I/O are optimized for random data access. Data storage needs to be implemented on physical machine with SSD. The other components can be virtualized, but need dedicated VM infrastructure not to compete with other software for I/O.
LivingObjects recommends Linux Debian distribution with Kernel version greater than 3.16. For other distribution contact LivingObjects at email@example.com. To access eye.lo, end-customers can use any recent web browsers.
eye.lo is a multi-tenant platform that delivers Communication Service Providers (CSP), Managed Service Providers (MSP) and Network Integrators with a powerful application-aware management tool, helping them to assure the delivery of WAN connectivity services to their business customers.
For all the traffic and applications going through the WAN links and accesses, for thousands of enterprise customers, eye.lo™ is divided into several modules that allow to :
- Display executive view of network and critical application KPIs.
- Drill down near real time dashboards and assess end-user experience with fine-grain end-to-end application performance metrics across LAN, WAN and Application servers.
- Troubleshoot hybrid network path (PfR) issues
- Alert when critical application performance is out-of-policy
- Report daily, executive view of your Network SLA
- Closely customize customers’ network (Dashboard, alerting, site clustering, custom applications,…)
- Easily admin multi-tenant profiles and rights
Monitor flow and polling collection
Launching IWAN services is:
- Deciding service scope available for enterprise customers.
- Adapting user rights and eye.lo features accordingly,
- Reviewing the network customer topologies to define routers templates and check IWAN impact on existing CPE portfolio
- Sizing the collection link and eye.lo hosting hardware
- Adapting the provisioning system to automatically deliver the seed files to eye.lo platform every night
- Training the sales and manage services team
Based on experience, LivingObjects can deliver a full set of professional services to help deploy IWAN services in less than three months.
In the past, typical network traffic could easily be identified using well known port number. HTTP, HTTPS, POP3, or IMAP were among common traffic seen in enterprise. Today, there is increasing number of applications which is delivered over HTTP – both business and recreational applications. And many applications use dynamic ports such as Exchange, and voice and video which are delivered over RTP. This makes them impossible to be identified by looking at port number.
NBAR2 is Cisco’s Deep Packet Inspection (DPI), based on application signature, and Field Extraction (FE) technologies, to retrieve fields such as HTTP URL, SIP domain, mail server, and so on. Application information such as Sharepoint, Netflix, or Google Docs is provided by Nbar2 signature dictionary, called protocol pack. The protocol pack is updated several times a year to include new applications. Version 16.0 includes more than 1500 signatures.
PfR is part of Cisco IWAN. PfR monitors network performance and routes applications based on application performance policies and load balances traffic based upon link utilization levels to efficiently utilize all available WAN bandwidth. PfR is comprised of two major Cisco IOS components, a Master Controller (MC) and a Border Router (BR).
The Master Controller is a policy decision point at which policies are applied to various traffic classes that traverse the Border Router systems.
- The hub master controller is the master controller at the hub-site, which is either a data center or a head quarter. This is the device where all policies are configured. It also acts as master controller for that site and makes optimization decision.
- Branch Master Controller: The Branch Master Controller is the master controller at the branch-site. There is no policy configuration on this device. It receives policy from the Hub MC. This device acts as master controller for that site for making optimization decision.
Border Routers (BRs) are in the data forwarding path. Border Routers collect data from their Performance Monitor cache and smart probe results, provide a degree of aggregation of this information, and influence the packet forwarding path as directed by the Master Controller to manage user traffic.
With up to 50 CPEs, the service runs on a VM with 4CPUs/8GB RAM/100GB disk. A Debian Linux distribution is recommended + installation of Docker 1.9 and Ansible.