HP Networking
Discover how the new HP Networking combines the technologies and alliances of 3Com, ProCurve and TippingPoint into the next networking leader.

Simplify your disaster recovery plan—with HP Ethernet Virtual Interconnect

By Dave Tucker, Technical Marketing Engineer, HP Networking

 

dt.jpgI’ve been reflecting on some of the great discussions I’ve had recently with customers and partners about HP Ethernet Virtual Interconnect (EVI ). One of the most talked about use cases was the application of EVI in disaster recovery and so I though I would share an example with you.

 

First, 3 reasons network administrators love HP Ethernet Virtual Interconnect

 

Before we get there, let’s talk about the real value proposition of EVI for network administrators: 

 

  1. It doesn't cost anything! EVI is a free software upgrade for HPN customers.
  2. Simple deployment. Much of the complexity is hidden in the protocol itself and therefore requires only 5 steps to configure at each site.
  3. Transport independent. You don't need to make changes to your existing WAN, or worse, have to go out to tender for a new WAN service

Long-distance live virtual machine (VM) migration is a hot topic right now and enterprises are increasing the focus on business continuity. Get ahead of your application teams and deploy EVI. Now the network is no longer the limiting factor in your company's application deployment, virtualization strategy or business continuity plan. Now, back to that example…

 

Back to the topic at hand: Ethernet Virtual Interconnect for disaster recovery

 

HP's EVI can be used to simplify a VMware Site Recovery Manager (SRM) deployment. For those of you who know your VMware, you will know that SRM  is all about disaster recovery. SRM doesn’t have any specific requirement for an L2 Data Center Interconnect as it creates a shadow copy of the VMs at the disaster recovery site that only becomes active when the disaster recovery plan is activated. But here's the trick. . . the recovery VM has the exact same IP address as the protected VM.

 

Now, SRM provides a means of re-mapping these IP addresses through a series of scripts. In an ideal world this would be sufficient but unfortunately in the real world our environment is littered with the odd application where the developer decided to reference an IP address rather than a DNS name or that VM that doesn't run VMtools. Both of these make IP address re-mapping a herculean effort!

 

Using EVI, we can extend up to 4K VLANs from the protected data center to the recovery data center, which then removes the requirement for address re-mapping, preserving your sanity and giving you peace of mind that your networking will support your business continuity plan.

 

This is only one potential use case for EVI.

 

What problem can EVI solve in your network?

 

Read my colleague’s blogs talking  more about the data center today:

>> Follow HP Networking on Twitterand Google+| Join HPN LinkedIn Community| Like us HPN Facebook

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the community guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.