HyperIP by NetEx Blog

HyperIP Series – You Asked About Multiple Interfaces….

Posted by DaveHuhne

Everybody tells me this is going to be easy so I’m finally going to try HyperIP. Now let me see again where is the HyperIP website. Okay I’ve downloaded the OVF file, now what? Oh yeah, I need to watch the HyperIP Support Tutorial videos on their website. Very cool, these HyperIP guys sure try and make it easy for us rookies. I like that.

Now what’s next? Oh install the Virtual Appliance on my virtual platform (VMware ESX or Microsoft Hyper-V) and start configuring. Makes sense. Wait a moment it looks like I need management and data ports. I only have one NIC on my server. Hmmm… what do I do now?

We’ve heard this type of story a few times and want to take this opportunity to clarify some interface points. HyperIP has two interfaces; a data and management port. The data interface is used for all traffic using the HyperIP tunnel and may also be used to manage HyperIP. The management port is available when a separate management network is required. If the management interface is used, be sure to set up routing in the HyperIP so traffic takes the proper path.

Okay I have my management and data ports configured and am having trouble sending any traffic, what’s up? The most common issue we’ve seen here is from the interfaces being on the same network. The management and data ports cannot exist on the same subnet. If a second subnet is not available, use only the data port in your configuration.

Okay I have my management port pointing out the WAN and the data port on the LAN, why aren’t the HyperIPs able to communicate? The HyperIPs only talk to each other on the data interfaces. No traffic flows between the data and management ports.

Okay I have the two interfaces configured on the networks that will be sending traffic across HyperIP and only some servers can communicate. Why is that? HyperIP acts like a one-armed router where traffic using HyperIP comes in, and is sent out, on the same data interface. The data interface will be used for servers and storage that will utilize HyperIP. If the HyperIP cannot be placed in the same network as the servers and storage, routes or access lists can be used in routers to direct traffic at HyperIP.

Alright I have both interfaces configured to the same VLAN and one NIC card. That should work shouldn’t it? The data and management interfaces cannot be on the same network. In this situation, only use the data interface for traffic and management. You will need to set user access to allow a browser on the data port.

Well I think that has answered my management questions.
Thanks very much HyperIP.

 

This entry was posted in HyperIP, and tagged , , , , , , , , , , Bookmark the permalink.

Riverbed Asked the Question, HyperIP Responded…

Posted by Marketing

In a recent blog Riverbed challenged other WAN optimization vendors to answer the question “Do competitors’ products work as well as Riverbed?” Well, since they asked, the answer is yes. In fact, HyperIP WAN Optimization virtual appliance works better than Riverbed.

First off, Riverbed poses the question of WAN optimization support for all important applications. We find it somewhat humorous that Riverbed would ask such a question about competitors’ application support when HyperIP has long set the standard in the industry for the broadest support in accelerating critical replication and backup applications of any WAN optimizer and does this with a virtual appliance (software). HyperIP accelerates replication applications from CA, Dell, EMC, HP, IBM, Microsoft, NetApp, Oracle, Quantum, Veeam and many more. A full list of supported applications can be found at http://www.netex.com/hyperip/supported-applications. In addition, NetEx is a VMware Technology Alliance Partner and HyperIP is ideal for supercharging vMotion and Storage vMotion migration over the WAN. HyperIP also supports Hyper-V live migrations over the WAN.

Riverbed also asked if other vendor’s products are useful for all their requirements. This is probably the wrong question to ask, as many customers don’t have a critical need to accelerate the movement of Microsoft Office documents between a central data center and branch offices. Or speed up their VOIP apps. Most companies don’t want to pay for products that they will not use. A better question is to ask how a product performs for business critical replication and disaster recovery requirements to meet specific Recovery Time Objectives.

Assuming that its products are the only WAN optimizers that people actually like, Riverbed then wants to know if other customers are happy with the vendor’s products. Well, I can’t speak for other companies but I know NetEx customers are very happy with HyperIP. In fact, more and more of our customers are choosing HyperIP over Riverbed. Take a look at our TechValidate research page for HyperIP customer testimonials. You’ll seem that many customers tried Riverbed and selected HyperIP instead.

Finally, Riverbed makes the claim that less-expensive products aren’t up to the task and wonders why competitive products are cheaper in the first place? With HyperIP by NetEx the answer is simple. HyperIP is deployed as a software-only virtual appliance running on VMware. There is no need for customers to waste precious IT budget dollars on expensive, proprietary Riverbed hardware that can’t be upgraded or installed in minutes anywhere in the world. Riverbed needs to understand that the purchase price isn’t the only component of product cost equation. HyperIP allows users to migrate to higher network speeds with a simple software key upgrade, no forklift hardware upgrade, no waiting weeks or months to get the hardware appliance ordered, delivered, installed and configured. To answer Riverbed’s question, HyperIP is a cost-effective WAN Optimization solution that was designed to deliver the performance of a hardware WAN optimizer but with the customer cost savings of server virtualization and the deployment speed, simplicity and flexibility of a virtual server appliance.

This entry was posted in HyperIP, and tagged , , , , , , , , , , Bookmark the permalink.