HyperIP by NetEx Blog

HyperIP Series – You Asked About vMotions Over Global Networks….

Posted by Marketing

Storage vMotion is different from “vMotion” where your storage stays the same and you change hosts, or “live storage vMotion” where the host is the same and you change the datastore. The storage vMotion I’m talking about is changing both the host and datastore. Storage vMotion works great on a LAN, but performing it over a WAN is a whole different story.

If you have ever tried to Storage vMotion your virtual machines over a WAN, I’m guessing it didn’t work so well. Most who try to do this are not able to. Why, you ask? Because over a WAN the native TCP stack on your ESX(i) hosts will start to back down. You’ll be lucky to complete a small storage vMotion over moderate distance in several hours, if at all. We have several customers who have tried this natively and have run into problems.  Now they use HyperIP WAN Optimization virtual appliance to mitigate performance issues making long distance vMotion a reality.

One of our customers, a large ‘financial’ enterprise level corporation, has been using HyperIP for their storage vMotions for well over a year now. When they first realized they had a need to migrate VM’s over their WAN, they would start a storage vMotion at the end of the day, expecting it to be completed when they came into the office the next day.  What they found is that in almost all attempts, the vMotion failed. They installed HyperIP and instantly they were vMotioning thousands of VM’s over their WAN between data centers. Last time we spoke to them, they had storage vMotioned over 1200 VM’s using HyperIP. They now do this on a regular basis. Before HyperIP they were lucky to get a single vMotion to finish.

Being able to move a VM at high speed anywhere in the world at anytime can have a profound impact on the way you do business and the way that your IT infrastructure is built and managed. You can build and configure VM’s locally at your corporate IT data center and HyperIP storage vMotion them out to where they need to go. If you are consolidating data centers or branch offices, you’ll need to move those VM’s over your WAN, or even a small internet link. If your organization is building dozens, hundreds, or thousands of VM’s, you’ll want to use HyperIP to move them.

In conclusion, HyperIP is downloadable, easy to implement, has a very small VM footprint, is inexpensive, and most important of all is absolutely necessary to storage vMotion your VM’s over a WAN. Download HyperIP now to start your free 30 day evaluation to take advantage your new ability to storage vMotion your VM’s anywhere in the world. Click the big orange box above to start the download process.

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

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.