Practices for scaling arp-nd for Large Data Centers
draft-dunbar-armd-arp-nd-scaling-practices-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-07-03
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
IETF conflict review conflict-review-dunbar-armd-arp-nd-scaling-practices
Stream WG state (None)
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ARMD                                                          L. Dunbar
Internet Draft                                                   Huawei
Category: Informational                                       W. Kumari
                                                                 Google
                                                          I. Gashingsky
                                                                  Yahoo

Expires: Nov 2012                                          July 3, 2012

            Practices for scaling arp-nd for Large Data Centers

               draft-dunbar-armd-arp-nd-scaling-practices-00

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with
   the provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other documents
   at any time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on November 30, 2012.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Dunbar-Kumari-Gashinsky Expires November 2012                 [Page 1]
Internet-Draft          ARMD ARP/ND Practices                 June 2012

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with
   respect to this document.

Abstract

   This draft is intended to document some simple well established
   practices which can scale ARP/ND in data center environment.

Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC-2119 [RFC2119].

Table of Contents

   1. Introduction ................................................ 3
   2. Terminology ................................................. 3
   3. Potential Solutions to Scale Address Resolution in DC......... 4
      3.1. Layer 3 to Access Switches .............................. 4
      3.2. Practices to scale ARP/ND in layer 2 .................... 5
         3.2.1. When a station needs to communicate with an external
         peer: .................................................... 5
         3.2.2. L2/L3 boundary router processing of inbound traffic: 6
         3.2.3. Inter subnets communications ....................... 7
      3.3. Static ARP/ND entries on switches ....................... 7
      3.4. DNS based solution ...................................... 7
      3.5. ARP/ND Proxy approaches ................................. 8
      3.6. Overlay models ......................................... 9
   4. Summary and Recommendations ................................. 10
   5. Manageability Considerations ................................ 10
   6. Security Considerations ..................................... 10
   7. IANA Considerations ........................................ 10
   8. Acknowledgements ........................................... 10
   9. References ................................................. 11
   Authors' Addresses ............................................ 11

Dunbar-Kumari-Gashinsky                              Expires December 2012                 [Page 2]
Internet-Draft          ARMD ARP/ND Practices                 June 2012

1. Introduction

   As described in [ARMD-Problems], the increasing trend of rapid
   workload shifting and server virtualization in modern data centers
   is requiring servers to be loaded (or re-loaded) with different VMs
   or applications at different times. Those different VMs loaded to
   one physical server may have different IP addresses, or even be in
   different IP subnets.
   In order to allow a physical server to be re-loaded with VMs in
   different subnets, or VMs to be moved to different server racks
   without IP address re-configuration, the corresponding networks have
   to have multiple broadcast domains (many VLANs) on the interfaces of
   L2/L3 boundary routers and ToR switches. Unfortunately, this kind of
   network can lead to address resolution scaling issues, especially on
Show full document text