Jeremy Littlejohn


Upcoming Events

Where the Cloud Touches Down: Simplifying Data Center Infrastructure Management

Thursday, July 25, 2013
10:00 AM PT/1:00 PM ET

In most data centers, DCIM rests on a shaky foundation of manual record keeping and scattered documentation. OpManager replaces data center documentation with a single repository for data, QRCodes for asset tracking, accurate 3D mapping of asset locations, and a configuration management database (CMDB). In this webcast, sponsored by ManageEngine, you will see how a real-world datacenter mapping stored in racktables gets imported into OpManager, which then provides a 3D visualization of where assets actually are. You'll also see how the QR Code generator helps you make the link between real assets and the monitoring world, and how the layered CMDB provides a single point of view for all your configuration data.

Register Now!

A Network Computing Webinar:
SDN First Steps

Thursday, August 8, 2013
11:00 AM PT / 2:00 PM ET

This webinar will help attendees understand the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging. It will also help users decide whether SDN makes sense in their environment, and outline the first steps IT can take for testing SDN technologies.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

See more from this blogger

LISP's Future Is Not In The Data Center

LISP (Locator/Identifier Separation Protocol) is an IETF draft protocol that separates location information from host information on the Internet. The essential problem that LISP is designed to solve is the cost and viability of increasingly large Internet routing tables. As a side benefit, LISP is also touted as addressing the lack of flexibility and mobility in Internet routing architectures that limit the ability of an enterprise, or even an individual user, from moving providers or locations easily.

LISP is an interesting protocol in that it needs heavy participation from enterprises, small businesses, and service providers to be truly effective. However, I feel that it is only going to ultimately benefit service providers. I don't believe it has an immediate future in the enterprise, even though it is being pushed there.

LISP functions by separating the IP address of your location on the Internet (called your RLOC), from the IP address of your host (your EID). This separation allows you to move freely without regard to huge routing table changes and enables Internet routing tables to consolidate and provide only connectivity level address routing while maintaining the ability to reach the host, all without the cost associated with maintaining routes to each individual host subnet.

That sounds complicated. It isn't. Essentially, LISP is a separate layer of address resolution. Your LISP capable router registers your host address space (your EIDs - non-RFC 1918, of course) with a LISP map server. The registrations also list the provider assigned IP address of all of your Internet gateways (your RLOCs). If you have two ISPs, then you have two entries and two RLOCs. When someone wants to reach you, if they are LISP-enabled, they look up your mapping in the LISP database and send their data in a LISP encapsulated packet from their edge gateway (their ITR - Ingress Tunnel Router) to your edge gateway (your ETR - Egress Tunnel Router). This LISP encapsulated tunnel is similar to a GRE tunnel, although there are technical differences in packet formation; it is not GRE. Once the packet arrives at your RLOC (your ETR) , the LISP encapsulation is removed and the original packet, which has your host IP as the destination and the original host IP as the source. It is put on the wire and delivered to your application. I have grossly oversimplified the process for the purpose of this short post, but the basics are there.

The more people that use LISP, the smaller the BGP tables get because they only need to provide Internet on-ramp information (RLOC routing), not host level detail (EID routing). This should theoretically result in less expensive service provider equipment and less administrative overhead for Internet routing. Although, the new LISP infrastructure will be an additional capital cost and ongoing administrative cost for whomever provides it.


Page:  1 | 2  | Next Page »


Related Reading


More Insights


Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
 
Vendor Comparisons
Network Computing’s Vendor Comparisons provide extensive details on products and services, including downloadable feature matrices. Our categories include:

Next Gen Network Reports

Research and Reports

Network Computing: April 2013



TechWeb Careers