Practices for scaling ARP and ND for large data centers
draft-dunbar-armd-arp-nd-scaling-practices-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in ops area)
Last updated 2012-12-07 (latest revision 2012-08-31)
Stream IETF
Intended RFC status Informational
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 AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ron Bonica
Send notices to ldunbar@huawei.com, warren@kumari.net, draft-dunbar-armd-arp-nd-scaling-practices@tools.ietf.org
ARMD                                                L. Dunbar
Internet Draft                                         Huawei
Intended status: Informational                     W. Kumari
Expires: February 2013                                Google
                                              Igor Gashinsky
                                                       Yahoo
                                              August 31, 2012

      Practices for scaling ARP and ND for large data centers

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

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 February 31, 2013.

Copyright Notice

   Copyright (c) 2012 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
   (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.

                     Expires February 31, 2013               [Page 1]
Internet-Draft   Pratices to scale ARP/ND in large DC

Abstract

   This draft documents some simple practices that scale ARP/ND
   in data center environments.

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. Common DC network Designs.................................... 4
   4. Layer 3 to Access Switches................................... 4
   5. Layer 2 practices to scale ARP/ND............................ 5
      5.1. Practices to alleviate APR/ND burden on L2/L3
      boundary routers ............................................ 5
         5.1.1. Station communicating with an external peer........ 5
         5.1.2. L2/L3 boundary router processing of inbound
         traffic .................................................. 6
         5.1.3. Inter subnets communications ...................... 7
      5.2. Static ARP/ND entries on switches ...................... 7
      5.3. ARP/ND Proxy approaches................................. 8
   6. Practices to scale ARP/ND in Overlay models ................. 8
   7. Summary and Recommendations ................................. 9
   8. Security Considerations...................................... 9
   9. IANA Considerations ......................................... 9
   10. Acknowledgements .......................................... 10
   11. References ................................................ 10
      11.1. Normative References.................................. 10
      11.2. Informative References................................ 10
   Authors' Addresses ............................................ 11

Dunbar-Kumari-Gashinsky    Expires February 31, 2013  [Page 2]
Internet-Draft   Pratices to scale ARP/ND in large DC

1. Introduction

   As described in [ARMD-Problems], the increasing trend of
   rapid workload shifting and server virtualization in modern
   data centers requires servers to be loaded (or re-loaded)
   with different VMs or applications at different times.
   Different VMs residing on one physical server may have
   different IP addresses, or may even be in different IP
   subnets.

   In order to allow a physical server to be loaded with VMs in
   different subnets, or VMs to be moved to different server
   racks without IP address re-configuration, the corresponding
   networks need to enable multiple broadcast domains (many
   VLANs) on the interfaces of L2/L3 boundary routers and ToR
   switches. Unfortunately, when the combined number of VMs (or
   hosts) in all those subnets is large, this can lead to
Show full document text