One of the presenters at Network Field Day 15 will be TELoIP around their VINO (Virtual Intelligent Network Overlay) SD-WAN solution. I am going to build a bit off of a couple of other NFD15 delegates’ thoughts (Phil Gervasi – https://networkphil.com/2017/03/27/teloip-at-networking-field-day-15/ and Brandon Carroll – http://globalconfig.net/presenting-vendor-preview-teloip/) as well as some of the ones I have been having myself.
I normally go into tech presentations by doing my homework. I want to get the basics out of the way so that I get more out of the presentation. SD-WAN is something that as a network engineer you hear a lot about, but in my case, have not had too much experience with. I have built a few Meraki cloud environments, but it was pretty much limited to that.
Looking through some of the documentation, here is what I want to communicate about my initial thoughts heading into the TELoIP presentation. I am picturing a hub and spoke type of company in my mind of a main campus and branch offices. The critical resources are held at the main campus and the branch offices are connecting in to utilize them (voice, data stores, etc). The VINO product offers a way to build the network logically, connecting these sites and services to each other through what seems to be a very useful, and unique dashboard. Some parts of this dashboard allow for observation of detailed analytics on topics such as voice as they share in this example screenshot:
One other images that they shared was more of a single site monitor with things such as bandwidth stats, uptime, and a few more QoE charts as well. That page looks like this:
Having an easy way to link sites together, display key networking stats, and monitor connections is something that a lot of vendors in the SD-WAN space are all touting. I want to learn specifically, what sets TELoIP apart from the rest. I want the answer to “Why should I go with your product?” Those are the types of questions I will be asking. From my research, I read a little bit about one unique feature and that is their utilization of multiple ISPs for redundancy and maximum bandwidth. They describe this the following way:
VINO aggregation provides the full combined top speed of all links, plus bidirectional IPQoS and pre-emptive fast failover. Load Balancing relies on path-steering to assign traffic to a single link, once the session is established it is vulnerable to link outages because the session IP address will change and terminate the session. Load Balancing can only provide the bandwidth of a single link compared to VINO which uses per-packet aggregation to provide the whole sum of bandwidth from all underlay links. In short, VINO offers faster speeds with greater reliability and performance than Load Balancing.
I want to look for more details like that. That is just one example of a way they are thinking different to offer a unique solution.
Lastly, I want to see the different scopes this product can apply to. Are they more suitable for larger configurations, or would a smaller environment be more the speed of what VINO would be best for.
Overall, this is what I am looking to learn from their presentation at NFD15:
- What are the unique features of VINO?
- What does the optimal configuration of the product look like?
- What are the limitations of VINO?
- Also, anything that you want to know! Comment below or find me on Twitter @TheRoutingTable.
Be sure to check back here at https://theroutingtable.com, http://www.techfieldday.com, or the TFD YouTube Channel for more information and a wrap up, after the presentation takes place. You can also visit TELoIP’s website as well @ http://www.teloip.com/
Disclaimer: Gestalt IT, organizers of Network Field Day was responsible for my travel expenses to attend Network Field Day. I do not receive any cash compensation as a delegate from either Gestalt It or any of the mentioned vendors. All opinions are my own.