US20150124823A1 - Tenant dhcp in an overlay network - Google Patents

Tenant dhcp in an overlay network Download PDF

Info

Publication number
US20150124823A1
US20150124823A1 US14/484,165 US201414484165A US2015124823A1 US 20150124823 A1 US20150124823 A1 US 20150124823A1 US 201414484165 A US201414484165 A US 201414484165A US 2015124823 A1 US2015124823 A1 US 2015124823A1
Authority
US
United States
Prior art keywords
dhcp
switch
network
virtual
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/484,165
Inventor
Ayaskant Pani
Sanjay Thyamagundalu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cisco Technology Inc
Original Assignee
Cisco Technology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201361900359P priority Critical
Application filed by Cisco Technology Inc filed Critical Cisco Technology Inc
Priority to US14/484,165 priority patent/US20150124823A1/en
Assigned to CISCO TECHNOLOGY, INC. reassignment CISCO TECHNOLOGY, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: THYAMAGUNDALU, SANJAY, PANI, AYASKANT
Publication of US20150124823A1 publication Critical patent/US20150124823A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. local area networks [LAN], wide area networks [WAN]
    • H04L12/46Interconnection of networks
    • H04L12/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/0803Configuration setting of network or network elements
    • H04L41/0813Changing of configuration
    • H04L41/082Changing of configuration due to updating or upgrading of network functionality, e.g. firmware
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/12Arrangements for maintenance or administration or management of packet switching networks network topology discovery or management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/22Arrangements for maintenance or administration or management of packet switching networks using GUI [Graphical User Interface]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0805Availability
    • H04L43/0811Connectivity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/50Testing arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/12Shortest path evaluation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/16Multipoint routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/18Loop free
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/20Hop count for routing purposes, e.g. TTL
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/28Route fault recovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/48Routing tree calculation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/64Routing or path finding of packets in data switching networks using an overlay routing layer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/20Support for services or operations
    • H04L49/201Multicast or broadcast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/25Routing or path finding through a switch fabric
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2007Address allocation internet protocol [IP] addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2061Address allocation involving aspects of pools of addresses, e.g. assignment of different pools of addresses to different dynamic host configuration protocol [DHCP] servers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/60Details
    • H04L61/6004Structures or formats of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/22Header parsing or analysis
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/10Mapping of addresses of different types; Address resolution
    • H04L61/103Mapping of addresses of different types; Address resolution across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]

Abstract

Systems, methods, and non-transitory computer-readable storage media for dynamic host configuration protocol (DHCP) relay functionality in overlay networks. A system on a overlay network fabric can first receive a DHCP request from a host device, the system including a tunnel endpoint (TEP) configured to connect the host device to the overlay network fabric via a tunnel. The system then enables a relay agent information option for relaying the DHCP request with sub-options inserted into the DHCP request, and inserts information into to the sub-options in the DHCP request to yield a modified DHCP request. Here, the information can include an address of the system and an interface of a circuit associated with the system, etc. Next, the system forwards the modified DHCP request to a destination DHCP server based on an address of the destination DHCP server associated with the DHCP request.

Description

    RELATED APPLICATIONS
  • This application claims priority to U.S. Provisional Patent Application No. 61/900,359, filed on Nov. 5, 2013, the content of which is incorporated herein by reference in its entirety.
  • TECHNICAL FIELD
  • The present technology pertains to dynamic host configuration protocol (DHCP), and more specifically pertains to relaying DHCP functionality in an overlay network.
  • BACKGROUND
  • Recent advancements in network technologies have allowed networks to support an increased demand for network data. In addition, networks have become larger and more complex, with massive amounts of devices joining the networks and communicating with each other. Yet as the size and complexity of a network grows, it becomes extremely difficult to manage the network settings of current devices and deploy new devices in the network. For example, with larger networks, implementing static addressing can be an extremely onerous task. On the other hand, dynamic and automated addressing schemes, such as DHCP, can be very difficult to implement, particularly in large and complex networks which often have various types of logical boundaries that prevent network settings from being distributed throughout the network. Unfortunately, this often leads to improper network settings on specific devices, which can create serious network connectivity issues. For example, improper network settings can prevent a device, such as a server, from being able to communicate on the network, and may result in addressing conflicts, which can even bring down a network.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
  • FIG. 1 illustrates an example network device according to some aspects of the subject technology;
  • FIGS. 2A and 2B illustrate example system embodiments according to some aspects of the subject technology;
  • FIG. 3 illustrates a schematic block diagram of an example architecture for a network fabric;
  • FIG. 4 illustrates an example overlay network;
  • FIG. 5 a diagram of an example DHCP service implementation; and
  • FIG. 6 illustrates an example method embodiment.
  • DESCRIPTION OF EXAMPLE EMBODIMENTS
  • Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure.
  • Overview
  • Data centers and networks are increasingly being built using virtual machines (VMs), virtual switches and routers, and physical networking devices with virtualization capabilities, such as virtual tunnel endpoints, in order to increase the size and capabilities of the network(s) by adding devices and virtual workloads using virtualization (e.g., overlay networks). Such virtualization devices often stack inside a hypervisor to forward packets inside of the host machine, or across host machines by leveraging an overlay network technology, such as virtual extensible LAN (VXLAN) technology. Such virtualization technologies also allow increasing numbers of devices, such as client devices and servers, to communicate on the network. This is at least partly a result of a greater number of network segments and addressing schemes available for use by devices to communicate on the network. For example, different routers and routing schemes can be used to allow clients to communicate across different network subnets, and even allow overlapping addresses to be used by a router without conflict.
  • This in turn can create an enormous challenge on system administrators in maintaining and deploying proper configuration settings for network devices, and automating service provisioning for devices on the network. For example, the complexity of a network with various addressing schemes and virtual network segments can prohibit DHCP service from being provided on the network, or otherwise limit DHCP service to only allow unique addresses or only serve devices connected to specific network segments or elements. Indeed, in some cases, it can be extremely difficult for a DHCP server to ascertain a proper address scope for selecting an address to be allocated to a device, or otherwise recognize, process, and relay DHCP messages appropriately.
  • The approaches set forth herein, on the other hand, can provide DHCP service to devices on any type of network, including overlay networks. In some cases, when a tenant DHCP request packet is sent, the ingress switch, such as the ingress leaf or top-of-rack (ToR) on a fabric, can insert its own IP address, such as its overlay VRF IP address, in the DHCP information option (DHCP Option 82), and subsequently act as a relay to forward DHCP messages to the tenant VRF. The DHCP server's response packet can be forwarded back to a switch that connects the DHCP server to the network fabric. The packet can then be forwarded to the pervasive switch virtual interface (SVI) IP address, and eventually received by one of the switches where the pervasive SVI is configured.
  • This receiving switch can look at the DHCP option 82 in the DHCP packet, which is retained (from the original DHCP request) in the DHCP response by the DHCP server, and identify the ingress switch connected to the host that originated the DHCP request. The receiving switch can then forward the DHCP packet to the ingress switch identified in the DHCP option 82, which can receive the DHCP packet and deliver it to the originating host. The originating host can thus receive the DHCP response to the DHCP request based on the address inserted by the ingress switch into the DHCP option 82.
  • In some cases, when allocating an address to the originating host, the DHCP server can determine the addressing scope based on the address of the ingress switch as indicated in the DHCP option 82. For example, if the gateway address of the ingress switch is in a class A IP network, the DHCP server can determine that the originating host should receive a class A IP address, and consequently identify an available class A IP address from its pool of available addresses in that scope. In some cases, the DHCP server can map the GI address to an address pool from which address assignment happens.
  • If the DHCP server supports multi-VRF, then the bridge domain (BD) virtual network identifier (VNID) can be identified as the subscriber identifier or the virtual private network identifier. On the other hand, if the DHCP server does not support multi-VRF, the BD VNID can be ascertained based on the relay agent's gateway address (GIADDR). In some cases, endpoint group (EPG) VNID can be encoded in the DHCP option 82 for EPG derivation to avoid BD-side flooding in stateless scenarios.
  • DESCRIPTION
  • The disclosed technology addresses the need in the art for accurate and efficient DHCP services in overlay solutions. Disclosed are systems, methods, and computer-readable storage media for DHCP services in overlay networks. A brief introductory description of relevant concepts, as well as example systems and networks, as illustrated in FIGS. 1 through 4, is first disclosed herein. A detailed description of DHCP services in overlay solutions, related concepts, and example variations, will then follow. These variations shall be described herein as the various embodiments are set forth. The disclosure now turns to an introductory description of relevant, networking concepts.
  • A computer network is a geographically distributed collection of nodes interconnected by communication links and segments for transporting data between endpoints, such as personal computers and workstations. Many types of networks are available, with the types ranging from local area networks (LANs) and wide area networks (WANs) to overlay and software-defined networks, such as virtual extensible local area networks (VXLANs).
  • LANs typically connect nodes over dedicated private communications links located in the same general physical location, such as a building or campus. WANs, on the other hand, typically connect geographically dispersed nodes over long-distance communications links, such as common carrier telephone lines, optical lightpaths, synchronous optical networks (SONET), or synchronous digital hierarchy (SDH) links. LANs and WANs can include layer 2 (L2) and/or layer 3 (L3) networks and devices.
  • The Internet is an example of a WAN that connects disparate networks throughout the world, providing global communication between nodes on various networks. The nodes typically communicate over the network by exchanging discrete frames or packets of data according to predefined protocols, such as the Transmission Control Protocol/Internet Protocol (TCP/IP). In this context, a protocol can refer to a set of rules defining how the nodes interact with each other. Computer networks may be further interconnected by an intermediate network node, such as a router, to extend the effective “size” of each network.
  • Overlay networks generally allow virtual networks to be created and layered over a physical network infrastructure. Overlay network protocols, such as Virtual Extensible LAN (VXLAN), Network Virtualization using Generic Routing Encapsulation (NVGRE), Network Virtualization Overlays (NVO3), and Stateless Transport Tunneling (STT), provide a traffic encapsulation scheme which allows network traffic to be carried across L2 and L3 networks over a logical tunnel. Such logical tunnels can be originated and terminated through virtual tunnel end points (VTEPs).
  • Moreover, overlay networks can include virtual segments, such as VXLAN segments in a VXLAN overlay network, which can include virtual L2 and/or L3 overlay networks over which VMs communicate. The virtual segments can be identified through a virtual network identifier (VNI), such as a VXLAN network identifier, which can specifically identify an associated virtual segment or domain.
  • Network virtualization allows hardware and software resources to be combined in a virtual network. For example, network virtualization can allow multiple numbers of VMs to be attached to the physical network via respective virtual LANs (VLANs). The VMs can be grouped according to their respective VLAN, and can communicate with other VMs as well as other devices on the internal or external network.
  • Network segments, such as physical or virtual segments; networks; devices; ports; physical or logical links; and/or traffic in general can be grouped into a bridge or flood domain. A bridge domain or flood domain can represent a broadcast domain, such as an L2 broadcast domain. A bridge domain or flood domain can include a single subnet, but can also include multiple subnets. Moreover, a bridge domain can be associated with a bridge domain interface on a network device, such as a switch. A bridge domain interface can be a logical interface which supports traffic between an L2 bridged network and an L3 routed network. In addition, a bridge domain interface can support internet protocol (IP) termination, VPN termination, address resolution handling, MAC addressing, etc. Both bridge domains and bridge domain interfaces can be identified by a same index or identifier.
  • Furthermore, endpoint groups (EPGs) can be used in a network for mapping applications to the network. In particular, EPGs can use a grouping of application endpoints in a network to apply connectivity and policy to the group of applications. EPGs can act as a container for buckets or collections of applications, or application components, and tiers for implementing forwarding and policy logic. EPGs also allow separation of network policy, security, and forwarding from addressing by instead using logical application boundaries.
  • Cloud computing can also be provided in one or more networks to provide computing services using shared resources. Cloud computing can generally include Internet-based computing in which computing resources are dynamically provisioned and allocated to client or user computers or other devices on-demand, from a collection of resources available via the network (e.g., “the cloud”). Cloud computing resources, for example, can include any type of resource, such as computing, storage, and network devices, virtual machines (VMs), etc. For instance, resources may include service devices (firewalls, deep packet inspectors, traffic monitors, load balancers, etc.), compute/processing devices (servers, CPU's, memory, brute force processing capability), storage devices (e.g., network attached storages, storage area network devices), etc. In addition, such resources may be used to support virtual networks, virtual machines (VM), databases, applications (Apps), etc.
  • Cloud computing resources may include a “private cloud,” a “public cloud,” and/or a “hybrid cloud.” A “hybrid cloud” can be a cloud infrastructure composed of two or more clouds that inter-operate or federate through technology. In essence, a hybrid cloud is an interaction between private and public clouds where a private cloud joins a public cloud and utilizes public cloud resources in a secure and scalable manner. Cloud computing resources can also be provisioned via virtual networks in an overlay network, such as a VXLAN.
  • The Dynamic Host Configuration Protocol (DHCP) is a protocol used in IP networks for dynamically distributing network settings to devices connecting to the network. In larger networks, static addressing can become extremely onerous. To this end, DHCP allows automated provisioning of network addressing to devices on the network. Thus, when a device connects to the network, it can send a DHCP request for network configuration settings to a DHCP server, which maintains a list of used and available network settings to allow the DHCP server to allocate addresses without creating addressing conflicts. The configurations settings can include, for example, an IP address, a subnet mask, a gateway address, a dynamic naming server (DNS) address, etc.
  • In networks with different network subnets, a relay agent can be implemented to relay DHCP/BOOTP messages between clients and servers on different subnets. In some cases, a router or switch can be enabled to function as a relay agent to relay DHCP messages to and from a DHCP server across subnets. In addition, DHCP option 82 (DHCP relay agent information option) can be enabled to allow a relay agent to further insert additional information into a DHCP message. For example, DHCP option 82 can allow circuit-specific information to be inserted into the DHCP request relayed to the DHCP server. The DHCP option 82 can include multiple sub-options for inserting additional information. In some cases, the sub-options can include a circuit ID sub-option and a remote ID sub-option. The circuit ID can indicate which circuit the DHCP request originated from, while the remote ID can indicate the remote information of the circuit, which typically refers to information about the relay agent.
  • In some embodiments, the remote ID can include the tunnel endpoint (TEP) IP and the BD-VNID. Moreover, the circuit ID can include the interface (IfIndex) and the EPG VNID of the ingress interface. In other embodiments, the DHCP option 82 can include additional sub-options, such as a server ID override, which can include the pervasive SVI IP of the BD; a link ID selection, which can include the subnet of the pervasive IP; the GIADDR, which can include the interface IP facing the DHCP server; and a VPNID, which can include the VRF name of the client VRF.
  • Having provided an introductory description of relevant concepts, the disclosure now turns to FIG. 1, which illustrates an example network device 110 suitable for implementing the present invention. Network device 110 includes a master central processing unit (CPU) 162, interfaces 168, and a bus 115 (e.g., a PCI bus). When acting under the control of appropriate software or firmware, the CPU 162 is responsible for executing packet management, error detection, and/or routing functions, such as miscabling detection functions, for example. The CPU 162 preferably accomplishes all these functions under the control of software including an operating system and any appropriate applications software. CPU 162 may include one or more processors 163 such as a processor from the Motorola family of microprocessors or the MIPS family of microprocessors. In an alternative embodiment, processor 163 is specially designed hardware for controlling the operations of router 110. In a specific embodiment, a memory 161 (such as non-volatile RAM and/or ROM) also forms part of CPU 162. However, there are many different ways in which memory could be coupled to the system.
  • The interfaces 168 are typically provided as interface cards (sometimes referred to as “line cards”). Generally, they control the sending and receiving of data packets over the network and sometimes support other peripherals used with the router 110. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided such as fast token ring interfaces, wireless interfaces, Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces and the like. Generally, these interfaces may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile RAM. The independent processors may control such communications intensive tasks as packet switching, media control and management. By providing separate processors for the communications intensive tasks, these interfaces allow the master microprocessor 162 to efficiently perform routing computations, network diagnostics, security functions, etc.
  • Although the system shown in FIG. 1 is one specific network device of the present invention, it is by no means the only network device architecture on which the present invention can be implemented. For example, an architecture having a single processor that handles communications as well as routing computations, etc. is often used. Further, other types of interfaces and media could also be used with the router.
  • Regardless of the network device's configuration, it may employ one or more memories or memory modules (including memory 161) configured to store program instructions for the general-purpose network operations and mechanisms for roaming, route optimization and routing functions described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example. The memory or memories may also be configured to store tables such as mobility binding, registration, and association tables, etc.
  • FIG. 2A, and FIG. 2B illustrate example system embodiments. The more appropriate embodiment will be apparent to those of ordinary skill in the art when practicing the present technology. Persons of ordinary skill in the art will also readily appreciate that other system embodiments are possible.
  • FIG. 2A illustrates a conventional system bus computing system architecture 200 wherein the components of the system are in electrical communication with each other using a bus 205. Exemplary system 200 includes a processing unit (CPU or processor) 210 and a system bus 205 that couples various system components including the system memory 215, such as read only memory (ROM) 220 and random access memory (RAM) 225, to the processor 210. The system 200 can include a cache of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor 210. The system 200 can copy data from the memory 215 and/or the storage device 230 to the cache 212 for quick access by the processor 210. In this way, the cache can provide a performance boost that avoids processor 210 delays while waiting for data. These and other modules can control or be configured to control the processor 210 to perform various actions. Other system memory 215 may be available for use as well. The memory 215 can include multiple different types of memory with different performance characteristics. The processor 210 can include any general purpose processor and a hardware module or software module, such as module 1 232, module 2 234, and module 3 236 stored in storage device 230, configured to control the processor 210 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 210 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.
  • To enable user interaction with the computing device 200, an input device 245 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 235 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing device 200. The communications interface 240 can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
  • Storage device 230 is a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 225, read only memory (ROM) 220, and hybrids thereof.
  • The storage device 230 can include software modules 232, 234, 236 for controlling the processor 210. Other hardware or software modules are contemplated. The storage device 230 can be connected to the system bus 205. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 210, bus 205, display 235, and so forth, to carry out the function.
  • FIG. 2B illustrates an example computer system 250 having a chipset architecture that can be used in executing the described method and generating and displaying a graphical user interface (GUI). Computer system 250 is an example of computer hardware, software, and firmware that can be used to implement the disclosed technology. System 250 can include a processor 255, representative of any number of physically and/or logically distinct resources capable of executing software, firmware, and hardware configured to perform identified computations. Processor 255 can communicate with a chipset 260 that can control input to and output from processor 255. In this example, chipset 260 outputs information to output 265, such as a display, and can read and write information to storage device 270, which can include magnetic media, and solid state media, for example. Chipset 260 can also read data from and write data to RAM 275. A bridge 280 for interfacing with a variety of user interface components 285 can be provided for interfacing with chipset 260. Such user interface components 285 can include a keyboard, a microphone, touch detection and processing circuitry, a pointing device, such as a mouse, and so on. In general, inputs to system 250 can come from any of a variety of sources, machine generated and/or human generated.
  • Chipset 260 can also interface with one or more communication interfaces 290 that can have different physical interfaces. Such communication interfaces can include interfaces for wired and wireless local area networks, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 255 analyzing data stored in storage 270 or 275. Further, the machine can receive inputs from a user via user interface components 285 and execute appropriate functions, such as browsing functions by interpreting these inputs using processor 255.
  • It can be appreciated that example systems 200 and 250 can have more than one processor 210 or be part of a group or cluster of computing devices networked together to provide greater processing capability.
  • FIG. 3 illustrates a schematic block diagram of an example architecture 300 for a network fabric 312. The network fabric 312 can include spine switches 302 A, 302 B, . . . , 302 N (collectively “302”) connected to leaf switches 304 A, 304 B, 304 c, . . . , 304 N (collectively “304”) in the network fabric 312.
  • Spine switches 302 can be L3 switches in the fabric 312. However, in some cases, the spine switches 302 can also, or otherwise, perform L2 functionalities. Further, the spine switches 302 can support various capabilities, such as 40 or 10 Gbps Ethernet speeds. To this end, the spine switches 302 can include one or more 40 Gigabit Ethernet ports. Each port can also be split to support other speeds. For example, a 40 Gigabit Ethernet port can be split into four 10 Gigabit Ethernet ports.
  • In some embodiments, one or more of the spine switches 302 can be configured to host a proxy function that performs a lookup of the endpoint address identifier to locator mapping in a mapping database on behalf of leaf switches 304 that do not have such mapping. The proxy function can do this by parsing through the packet to the encapsulated, tenant packet to get to the destination locator address of the tenant. The spine switches 302 can then perform a lookup of their local mapping database to determine the correct locator address of the packet and forward the packet to the locator address without changing certain fields in the header of the packet.
  • When a packet is received at a spine switch 302 i, the spine switch 302 i can first check if the destination locator address is a proxy address. If so, the spine switch 302 i can perform the proxy function as previously mentioned. If not, the spine switch 302 i can lookup the locator in its forwarding table and forward the packet accordingly.
  • Spine switches 302 connect to leaf switches 304 in the fabric 312. Leaf switches 304 can include access ports (or non-fabric ports) and fabric ports. Fabric ports can provide uplinks to the spine switches 302, while access ports can provide connectivity for devices, hosts, endpoints, VMs, or external networks to the fabric 312.
  • Leaf switches 304 can reside at the edge of the fabric 312, and can thus represent the physical network edge. In some cases, the leaf switches 304 can be top-of-rack (“ToR”) switches configured according to a ToR architecture. In other cases, the leaf switches 304 can be aggregation switches in any particular topology, such as end-of-row (EoR) or middle-of-row (MoR) topologies. The leaf switches 304 can also represent aggregation switches, for example.
  • The leaf switches 304 can be responsible for routing and/or bridging the tenant packets and applying network policies. In some cases, a leaf switch can perform one or more additional functions, such as implementing a mapping cache, sending packets to the proxy function when there is a miss in the cache, encapsulate packets, enforce ingress or egress policies, etc.
  • Moreover, the leaf switches 304 can contain virtual switching functionalities, such as a virtual tunnel endpoint (VTEP) function as explained below in the discussion of VTEP 408 in FIG. 4. To this end, leaf switches 304 can connect the fabric 312 to an overlay network, such as overlay network 400 illustrated in FIG. 4.
  • Network connectivity in the fabric 312 can flow through the leaf switches 304. Here, the leaf switches 304 can provide servers, resources, endpoints, external networks, or VMs access to the fabric 312, and can connect the leaf switches 304 to each other. In some cases, the leaf switches 304 can connect EPGs to the fabric 312 and/or any external networks. Each EPG can connect to the fabric 312 via one of the leaf switches 304, for example.
  • Endpoints 310A-E (collectively “310”) can connect to the fabric 312 via leaf switches 304. For example, endpoints 310A and 310B can connect directly to leaf switch 304A, which can connect endpoints 310A and 310B to the fabric 312 and/or any other one of the leaf switches 304. Similarly, endpoint 310E can connect directly to leaf switch 304C, which can connect endpoint 310E to the fabric 312 and/or any other of the leaf switches 304. On the other hand, endpoints 310C and 310D can connect to leaf switch 304B via L2 network 306. Similarly, the wide area network (WAN) can connect to the leaf switches 304C or 304D via L3 network 308.
  • Endpoints 310 can include any communication device, such as a computer, a server, a switch, a router, etc. In some cases, the endpoints 310 can include a server, hypervisor, or switch configured with a VTEP functionality which connects an overlay network, such as overlay network 400 below, with the fabric 312. For example, in some cases, the endpoints 310 can represent one or more of the VTEPs 408A-D illustrated in FIG. 4. Here, the VTEPs 408A-D can connect to the fabric 312 via the leaf switches 304. The overlay network can host physical devices, such as servers, applications, EPGs, virtual segments, virtual workloads, etc. In addition, the endpoints 310 can host virtual workload(s), clusters, and applications or services, which can connect with the fabric 312 or any other device or network, including an external network. For example, one or more endpoints 310 can host, or connect to, a cluster of load balancers or an EPG of various applications.
  • Although the fabric 312 is illustrated and described herein as an example leaf-spine architecture, one of ordinary skill in the art will readily recognize that the subject technology can be implemented based on any network fabric, including any data center or cloud network fabric. Indeed, other architectures, designs, infrastructures, and variations are contemplated herein.
  • FIG. 4 illustrates an exemplary overlay network 400. Overlay network 400 uses an overlay protocol, such as VXLAN, VGRE, VO3, or STT, to encapsulate traffic in L2 and/or L3 packets which can cross overlay L3 boundaries in the network. As illustrated in FIG. 4, overlay network 400 can include hosts 406A-D interconnected via network 402.
  • Network 402 can include a packet network, such as an IP network, for example. Moreover, network 402 can connect the overlay network 400 with the fabric 312 in FIG. 3. For example, VTEPs 408A-D can connect with the leaf switches 304 in the fabric 312 via network 402.
  • Hosts 406A-D include virtual tunnel end points (VTEP) 408A-D, which can be virtual nodes or switches configured to encapsulate and de-encapsulate data traffic according to a specific overlay protocol of the network 400, for the various virtual network identifiers (VNIDs) 410A-D. Moreover, hosts 406A-D can include servers containing a VTEP functionality, hypervisors, and physical switches, such as L3 switches, configured with a VTEP functionality. For example, hosts 406A and 406B can be physical switches configured to run VTEPs 408A-B. Here, hosts 406A and 406B can be connected to servers 404A-D, which, in some cases, can include virtual workloads through VMs loaded on the servers, for example.
  • In some embodiments, network 400 can be a VXLAN network, and VTEPs 408A-D can be VXLAN tunnel end points. However, as one of ordinary skill in the art will readily recognize, network 400 can represent any type of overlay or software-defined network, such as NVGRE, STT, or even overlay technologies yet to be invented.
  • The VNIDs can represent the segregated virtual networks in overlay network 400. Each of the overlay tunnels (VTEPs 408A-D) can include one or more VNIDs. For example, VTEP 408A can connect to virtual or physical devices or workloads residing in VNIDs 1 and 2; VTEP 408B can connect to virtual or physical devices or workloads residing in VNIDs 1 and 3, VTEP 408C can connect to virtual or physical devices or workloads residing in VNIDs 1, 2, 3, and another instance of VNID 2; and VTEP 408D can connect to virtual or physical devices or workloads residing in VNIDs 3 and 4, as well as separate instances of VNIDs 2 and 3. As one of ordinary skill in the art will readily recognize, any particular VTEP can, in other embodiments, have numerous VNIDs, including more than the 4 VNIDs illustrated in FIG. 4. Moreover, any particular VTEP can connect to physical or virtual devices or workloads residing in one or more VNIDs.
  • The traffic in overlay network 400 can be segregated logically according to specific VNIDs. This way, traffic intended for VNID 1 can be accessed by devices residing in VNID 1, while other devices residing in other VNIDs (e.g., VNIDs 2, 3, and 4) can be prevented from accessing such traffic. In other words, devices or endpoints in specific VNIDs can communicate with other devices or endpoints in the same specific VNIDs, while traffic from separate VNIDs can be isolated to prevent devices or endpoints in other specific VNIDs from accessing traffic in different VNIDs.
  • Each of the servers 404A-D and VMs 404E-L can be associated with a respective VNID or virtual segment, and communicate with other servers or VMs residing in the same VNID or virtual segment. For example, server 404A can communicate with server 404C and VM 404E because they all reside in the same VNID, viz., VNID 1. Similarly, server 404B can communicate with VMs 404F, 404H, and 404L because they all reside in VNID 2.
  • Each of the servers 404A-D and VMs 404E-L can represent a single server or VM, but can also represent multiple servers or VMs, such as a cluster of servers or VMs. Moreover, VMs 404E-L can host virtual workloads, which can include application workloads, resources, and services, for example. On the other hand, servers 404A-D can host local workloads on a local storage and/or a remote storage, such as a remote database. However, in some cases, servers 404A-D can similarly host virtual workloads through VMs residing on the servers 404A-D.
  • VTEPs 408A-D can encapsulate packets directed at the various VNIDs 1-4 in the overlay network 400 according to the specific overlay protocol implemented, such as VXLAN, so traffic can be properly transmitted to the correct VNID and recipient(s) (i.e., server or VM). Moreover, when a switch, router, or other network device receives a packet to be transmitted to a recipient in the overlay network 400, it can analyze a routing table, such as a lookup table, to determine where such packet needs to be transmitted so the traffic reaches the appropriate recipient. For example, if VTEP 408A receives a packet from endpoint 404B that is intended for endpoint 404H, VTEP 408A can analyze a routing table that maps the intended endpoint, endpoint 404H, to a specific switch that is configured to handle communications intended for endpoint 404H. VTEP 408A might not initially know, when it receives the packet from endpoint 404B, that such packet should be transmitted to VTEP 408D in order to reach endpoint 404H. Accordingly, by analyzing the routing table, VTEP 408A can lookup endpoint 404H, which is the intended recipient, and determine that the packet should be transmitted to VTEP 408D, as specified in the routing table based on endpoint-to-switch mappings or bindings, so the packet can be transmitted to, and received by, endpoint 404H as expected.
  • As one of ordinary skill in the art will readily recognize, the examples and technologies provided above are simply for clarity and explanation purposes, and can include many additional concepts and variations.
  • FIG. 5 illustrates a diagram 500 of an example DHCP service implementation. The DHCP service implementation can be on a fabric 312, which can include one or more VRF instances. In some embodiments, the fabric 312 can include a VRF-tenant 502 and a VRF-provider 504. The VRF-tenant 502 can refer to a VRF instance in tenant space within the fabric 312. On the other hand, the VRF-provider 504 can refer to a VRF instance in provider space within the fabric 312. As one of ordinary skill in the art will readily recognize, other VRF instances can also exist in other embodiments. In other words, the fabric 312 can include a single VRF or a multi-VRF, and the DHCP service implementation can function in either scenario.
  • The fabric 312 can include switches 506-514 which can connect the fabric 312 to non-fabric devices, such as clients, servers, L2 networks, L3 networks, etc. In some cases, the switches 506-514 can be TOR or leaf switches on the fabric. For example, the switches 506-514 can include leaf switches 304, as illustrated in FIG. 3. In addition, the switches 506-514 can include virtual tunneling capabilities in order to support an overlay solution. Thus, one or more of the switches 506-514 can serve as tunnel endpoints (TEPs) which can connect to a virtual tunnel endpoint (VTEP on the overlay network by encapsulating traffic through a virtual tunnel configured to enable communication between the overlay network and the underlying physical network.
  • Switch 506 can connect to the client 516 as well as host 518, allowing the client 516 and host 518 to communicate with the fabric 312. Switch 508 can similarly connect to host 518 and, like switch 506, can include TEP functionalities for establishing a virtual tunnel between the TEP in switch 508 and the VTEP 520 on the host 518.
  • As previously mentioned, the host 518 can include a VTEP 520, which can be configured to provide a virtual tunnel for communicating with TEPs on the fabric 312, such as the TEPs on switches 506 and 508. This way, host 518 can host clients, VMs, and/or virtual workloads, which can reside on an overlay space and connect to the underlying, physical network through a virtual tunnel established between the VTEP 520 and the TEPs on the switches 506 and 508 on the fabric 312. In FIG. 5, switch (ToR) 508 is shown hosting a client 522 which provides a DHCP service to hosts. The client 522 here can be a physical DHCP service, a VM running a DHCP service, or a DHCP service appliance, for example.
  • The connection between the client 516 and host 518 can be configured on the switches 506 and 508 as being in the same bridge domain 526 (BD 1). Thus, any communication flooded from one of the switches 506 and 508 to BD 1 will reach both the client 516 and host 518, as both reside on the same BD.
  • If BD 1 includes multiple subnets, it can create a DHCP challenge, where DHCP requests and responses may not cross the multiple subnets unless properly configured as described herein. Similarly, with multiple VRFs, a BD can have secondary or overlapping IP addresses, which can also create a DHCP challenge where DHCP requests and responses may not be properly relayed unless properly configured as described herein.
  • To avoid DHCP service problems resulting from multiple subnets, secondary or overlapping IP addresses, multiple routing instances in one or more VRFs, and any other DHCP relay problem, a smart relay solution can be implemented. Here, the DHCP relay agent information option (DHCP information option or DHCP option 82) can be enabled on one or more relay switches. For example, option 82 can be enabled on switch 506 to allow switch 506 to function as a relay agent. Thus, using option 82, switch 506 can insert additional information in a DHCP request to allow not only that request to be properly routed back to the originating client once a response is received from the DHCP server, but also ensure that the address information allocated to the originating client comports with the proper addressing scope.
  • For example, when receiving a DHCP request, switch 506 can insert its own IP address (i.e., its provider VRF IP address) into an option 82 sub-option in the DHCP request and forward the modified DHCP request back to the DHCP server 522. The DHCP server 522 can then extract the IP address of switch 506 from the DHCP request, and identify an available address for the originating host based on the scope of the address of switch 506 as indicated in the DHCP request. For example, if switch 506 has a class A IP address and is connected to the originating host, the DHCP server can check for available IP addresses in the class A range (i.e., 10.0.0.1 through 10.0.0.254—note that some addresses in the scope may be reserved such as 10.0.0.1 may be reserved for a gateway, and other addresses in the class A range may have other purposes, such as 10.0.0.255 may be a loopback address and 10.0.0.0 may be a broadcast address).
  • The DHCP server can then select network settings, including an IP address, in the proper scope, and forward the settings back to the originating host as a DHCP response. The DHCP response sent by the DHCP server can maintain the information inserted in the option 82 to allow any receiving device determine where the DHCP response should ultimately be sent (the receiving gateway). In other words, the IP address of switch 506 inserted into the option 82 by switch 506 at the time of receiving the DHCP request can allow the DHCP response to be forwarded from the DHCP server back to the switch 506. Once the switch 506 receives the DHCP response, it can forward the DHCP response back to the originating client, such as client 516. The originating client can then extract the information from the DHCP response and automatically and dynamically configure its network settings to allow it to connect to the network without creating a conflict, and without requiring manual, static addressing performed by the network admin.
  • To illustrate the process, assume that client 516 originates a DHCP request intended for DHCP server 518. Here, the client 516 can transmit a discover message on the subnet, VNID, or network segment of the switch 506, as a user datagram protocol (UDP). Switch 506, which connects to the client 516 can receive the message and relay the message forward. The switch 506 can be enabled to function as a relay agent with relay agent information option enabled, to allow switch 506 to insert additional information in the message so the message can be relayed across subnets, VRFs, BD, boundaries, segments, etc.
  • Upon receipt of the message, the switch 506 can insert its own IP address (GIADDR) into an option 82 sub-option and forward the message to the VTEP 520 on the host 518 on BD 1. The message is then received by the client on the host 520, which serves as DHCP server 522 and process the message to retrieve or allocate network configuration settings to the client 516.
  • The DHCP server 522 can then send a lease offer for to client 516. Here, the packet is routed back to the GIAddress. In some cases, the GIAddress can belong to multiple switches based on the pervasive SVI presence. Then, the receiving switch can look at the option 82 to redirect the packet to the originating switch (i.e., switch 506). Thus, the lease offer can be forwarded or redirected to the switch 506 connected to the client 516 based on the information in the option 82. In this example, the lease offer can be forwarded to switch 506 based on the IP address of switch 506 which was inserted into option 82 by switch 506 at the time switch 506 received the DHCP message from the client 516. Thus, irrespective of where the DHCP server 522 or any other device along the way sends the lease offer, the lease offer can always be directed back to the correct switch, switch 506, based on the information inserted into the option 82. The switch 506 will thus be able to receive the lease offer and relay it to the client 516 so the client can obtain the DHCP lease.
  • The information inserted into the option 82 can vary in different embodiments. Indeed, the option 82 sub-options used and the information inserted into the sub-options can vary depending on the specific environment, configuration settings, and/or circumstances. For example, the DHCP option 82 can include multiple sub-options for inserting additional information, as previously noted. In some cases, the sub-options can include a circuit ID sub-option and a remote ID sub-option. The circuit ID sub-option can indicate which circuit the DHCP request originated from, while the remote ID can indicate the remote information of the circuit, which typically refers to information about the relay agent.
  • In some embodiments, the remote ID sub-option can include the TEP IP and/or VNID of the BD in the overlay network (BD-VNID). Moreover, the circuit ID sub-option can include the interface (IfIndex) and the EPG VNID of the ingress interface. This can indicate what interface and VNID in the overlay network to use to forward messages to the specific EPG. In other embodiments, the DHCP option 82 can include additional sub-options, such as a server ID override, which can include the pervasive SVI IP of the BD, to indicate where to forward a message to the BD when the virtual interface is spread out over multiple physical devices, for example; a link ID selection, which can include the subnet of the pervasive IP; the GIADDR, which can include the interface IP facing the DHCP server; and a VPNID, which can include the VRF name of the client VRF, such as “VRF Tenant” from 502 in FIG. 5.
  • Accordingly, the DHCP service can function even in environments with multiple BDs and/or VRFs. For example, if a DHCP request is sent from client 516 to switch 506 and later forwarded to a DHCP server on a second VRF, such as DHCP server 524 on provider VRF 504, the DHCP response or lease offer can still be relayed back to the switch 506 connected to the client 516 and further to the client 516 based on the information inserted into the DHCP option 82. In other words, the information provided in the DHCP option 82 can relay DHCP messages across multiple VRFs, VLANs, VNIDs, subnets, BDs, or any other boundary; and the type of information included in the DHCP option 82 can depend on the type of environment or boundaries that need to be crossed. As previously mentioned, the information inserted in the DHCP option 82 can include an address of the ingress switch associated with the originating host, information identifying the VRF of the ingress switch, information identifying the VNID and/or EPG of a host and/or switch for relaying the DHCP messages back to the host, the circuit information, the gateway information, interface information, Pervasive SVI IP information, VPNID information, remote ID information, tunneling information (e.g., TEP information, including physical TEP or virtual TEP), BD information, etc.
  • Having disclosed some basic system components and concepts, the disclosure now turns to the exemplary method embodiment shown in FIG. 6. For the sake of clarity, the method is described in terms of a switch 506, as shown in FIG. 5, configured to practice the method. The steps outlined herein are exemplary and can be implemented in any combination thereof, including combinations that exclude, add, or modify certain steps.
  • At step 600, the switch 506 first receives a DHCP request from a host device, the switch 506 being a TEP configured to connect the host device to the overlay fabric network 312 via a tunnel. The switch 506 can be a leaf switch, such as leaf switch 304, a TOR switch, an edge device on the fabric 312, an ingress switch on the fabric 312 connecting the host device to the fabric 312, etc. Moreover, the host device can be a client device, such as a user terminal or mobile device; a server; a resource, such as a printer or gaming system; a virtual machine; etc. Further, the DHCP request can be a DHCP lease request or DHCP discover message, for example.
  • At step 602, the switch 506 enables the relay agent information option for relaying the DHCP request with sub-option fields on the DHCP request to insert information into at least one of the sub-option fields in the DHCP request. When enabled, the relay agent information option allows DHCP option 82 to be used in the DHCP messages. As previously explained, DHCP option 82 can allow sub-options in the DHCP messages for information to be inserted into the sub-options of the DHCP messages, to further expand or augment the information in the DHCP messages.
  • The information inserted into the DHCP option 82 can include address information associated with the ingress switch (i.e., switch 506) communicating with the host device (for example the IP address of the ingress switch), information identifying the VRF of the ingress switch, information identifying the VNID and/or EPG for relaying the DHCP messages back to the host device, the circuit information (e.g., circuit ID), the gateway information (e.g., GIADDR), interface information (e.g., IfIndex), Pervasive SVI IP information, VPNID information, remote ID information, tunneling information (e.g., TEP information, including physical TEP or virtual TEP), VLAN information, BD information, etc.
  • In addition, the switch 506 can serve as a relay agent for DHCP messages. Here, the switch 506 can use the information in the DHCP option 82 to relay DHCP messages across boundaries, such as subnets, VNIDs, VLANs, EPGs, BDs, circuits, VRFs, segments, etc.
  • At step 604, the switch 506 inserts information into to one or more sub-option fields in the DHCP request to yield a modified DHCP request, the information including an address of the switch 506 and/or an interface of a circuit associated with the switch 506. For example, the switch 506 can insert its TEP IP and/or BD-VNID into a sub-option in the DHCP request. In some cases, the switch 506 can also insert a circuit ID, which can include the interface index and EPG VNID of the ingress interface. In yet other cases, the switch 506 can include other information in various sub-options, including a pervasive SVI IP of the BD, a subnet of the pervasive SVI IP, a gateway address associated with the DHCP server, a VRF name, a MAC address of the switch 506, etc.
  • At step 606, the switch 506 then forwards the modified DHCP request to a destination DHCP server based on an address of the destination DHCP server associated with the DHCP request. In other words, the switch 506 relays the DHCP request to the DHCP server. The address, such as IP or media access control (MAC) address, of the DHCP server can be indicated in the DHCP request, such as the header of the DHCP request, for example. Thus, the switch 506 can forward the DHCP request to the address of the DHCP server as indicated on the DHCP request. However, in some embodiments, the DHCP server address can be configured on the switch 506 or listed on a table on the switch 506 such that the switch 506 can determine where to send any DHCP requests that it receives, even if such requests do not specify an address for the DHCP server. For example, in some cases, the DHCP request may not include an address of a DHCP server, but the switch 506 can nevertheless relay the DHCP request to the DHCP server either by performing a lookup or flooding the request to multiple addresses or an address group. Indeed, in some cases, the DHCP request may indicate 0.0.0.0 as the destination address, which would prompt the request to be flooded by the switch 506 to the network and/or the segment or subnet of the DHCP server.
  • The DHCP server then receives the DHCP request and generates a lease offer or DHCP response. The DHCP response can include an IP address, a subnet mask, a DNS IP, a gateway IP, etc. Moreover, the DHCP response can also preserve the information inserted into the DHCP request through the DHCP option 82, to allow the DHCP response to be relayed back to the proper switch and ultimately the proper host device. The DHCP server then sends the DHCP response which is relayed back to the switch 506 based on the information inserted into the sub-options in the DHCP request. The switch 506 then receives the DHCP response and relays it to the host device.
  • The host device subsequently receives the DHCP response and applies the network settings in the DHCP response according to the lease offer. Accordingly, the host device can automatically and dynamically receive the network configuration settings it needs to communicate on the network, without creating addressing conflicts with other devices, which could cause severe problems. Moreover, the host device can receive the network settings in the DHCP response even when connecting to an overlay network with many different boundaries which would otherwise prevent DHCP information from being relayed across such boundaries.
  • For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
  • In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
  • Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
  • Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
  • The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
  • Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims. Moreover, claim language reciting “at least one of” a set indicates that one member of the set or multiple members of the set satisfy the claim.

Claims (20)

1. A method comprising:
receiving, via a receiving switch on an overlay fabric network, a dynamic host configuration protocol (DHCP) request from a host device, the receiving switch comprising a tunnel endpoint (TEP) configured to connect the host device to the overlay fabric network via a tunnel;
enabling a relay agent information option for relaying the DHCP request with sub-option fields on the DHCP request, the sub-option fields for inserting information into the DHCP request;
inserting information into to at least one of the sub-option fields in the DHCP request to yield a modified DHCP request, the information comprising at least one of an address of the receiving switch and an interface of a circuit associated with the receiving switch; and
forwarding the modified DHCP request to a destination DHCP server based on an address of the destination DHCP server associated with the DHCP request.
2. The method of claim 1, wherein the information is inserted into a sub-option field in the DHCP request based on the relay agent information option, wherein the sub-option field comprises a remote identifier, the address of the receiving switch comprising at least one of a TEP IP address, a receiving switch media access control (MAC) address, and an overlay virtual routing and forwarding (VRF) IP address, and the relay agent information option being option 82.
3. The method of claim 1, wherein the receiving switch comprises at least one of a top-of-rack switch, a leaf switch, a virtual switch, an edge device in the overlay network fabric, a virtual tunnel endpoint (VTEP), an ingress switch in the overlay network fabric, and a port in a pervasive switch virtual interface.
4. The method of claim 1, wherein the information further comprises at least one of a circuit identifier, a server identifier override, a link identifier selection, a gateway interface address, and a virtual network identifier.
5. The method of claim 4, wherein the circuit identifier comprises at least one of an interface index value associated with an ingress interface and an endpoint group (EPG) virtual network identifier (VNID) associated with the ingress interface.
6. The method of claim 4, wherein the server identifier override comprises a pervasive switch virtual interface (SVI) IP address of a bridge domain associated with the receiving switch.
7. The method of claim 6, wherein the link identifier selection comprises a subnet of the pervasive SVI IP address.
8. The method of claim 4, wherein the gateway interface address (GIADDR) comprises one of an IP address associated with an interface facing the destination DHCP server or a pervasive IP address associated with a bridge domain in a virtual routing and forwarding (VRF) instance.
9. The method of claim 4, wherein the virtual network identifier (VNID) comprises a virtual routing and forwarding (VRF) name.
10. The method of claim 1, wherein virtual machines reside in the overlay network fabric and communicate with the overlay network fabric via a tunnel provided by the receiving switch.
11. The method of claim 1, wherein the overlay network fabric comprises at least one of a virtual extensible local area network (VXLAN), Network Virtualization using Generic Routing Encapsulation (NVGRE) network, a Stateless transport tunneling (STT) network, a spine-leaf network, and a CLOS network, the method further comprising:
receiving a response to the DHCP request from the DHCP server, the response comprising a DHCP lease offer; and
relaying the response to the host device.
12. A system comprising:
a processor; and
a computer-readable storage medium having stored therein instructions which, when executed by the processor, cause the processor to perform operations comprising:
receiving, via a receiving switch on an overlay network, a dynamic host configuration protocol (DHCP) request from a device, the receiving switch comprising a tunnel endpoint (TEP) configured to connect the device to the overlay network via a tunnel;
enabling a relay agent information option for DHCP requests on the receiving switch, the relay agent information option providing sub-option fields for inserting information into the DHCP request for relaying additional information into the DHCP request;
inserting information into to the sub-options in the DHCP request to yield a modified DHCP request, the information comprising at least one of an address of the receiving switch and interface information associated with a circuit where the receiving switch resides; and
relaying the modified DHCP request to a destination DHCP server based on an address of the destination DHCP server associated with the DHCP request.
13. The system of claim 12, the computer-readable storage medium storing additional instructions which, when executed by the processor, result in an operation further comprising:
receiving a response to the DHCP request from the destination DHCP server, the response comprising a DHCP lease offer; and
relaying the response to the device based on routing information contained in at least one of the response and the DHCP request.
14. The system of claim 12, wherein the sub-option fields comprise a first field for indicating a remote identifier, and a second field for indicating the address of the receiving switch comprising an overlay virtual routing and forwarding (VRF) IP address, the relay agent information option being option 82.
15. The system of claim 12, wherein the receiving switch comprises at least one of a top-of-rack switch, a leaf switch, a virtual switch, an edge device in the overlay network fabric, a virtual tunnel endpoint (VTEP), and a port in a pervasive switch virtual interface.
16. The system of claim 12, wherein the information further comprises at least one of a circuit identifier, a server identifier override, a link identifier selection, a gateway interface address, and a virtual private network identifier.
17. A non-transitory computer-readable storage medium having stored therein instructions which, when executed by a processor, cause the processor to perform operations comprising:
receiving, via a receiving switch on an overlay network, a dynamic host configuration protocol (DHCP) request from a host, the receiving switch comprising a tunnel endpoint (TEP) configured to connect the host to the overlay network via a tunnel;
enabling a relay agent information option for DHCP requests on the receiving switch, the relay agent information option providing sub-option fields for inserting information into the DHCP request for inserting additional information into the DHCP request prior to forwarding the DHCP request;
inserting information into to at least one of the sub-options in the DHCP request to yield a modified DHCP request, the information comprising at least one of an address of the receiving switch and an interface of a circuit associated with the receiving switch; and
forwarding the modified DHCP request to a destination DHCP server based on an address of the destination DHCP server associated with the DHCP request.
18. The non-transitory computer-readable storage medium of claim 17, storing additional instructions which, when executed by the processor, result in operations further comprising:
receiving a response to the DHCP request from the destination DHCP server; and
forwarding the response to the device based on routing information contained in at least one of the response and the DHCP request.
19. The non-transitory computer-readable storage medium of claim 17, wherein the information is inserted into a sub-option field in the DHCP request based on the relay agent information option, wherein the sub-option field comprises a remote identifier, the address of the receiving switch comprising an overlay virtual routing and forwarding (VRF) IP address, and the relay agent information option being option 82, and wherein the receiving switch comprises at least one of a top-of-rack switch, a leaf switch, a virtual switch, an edge device in the overlay network fabric, a virtual tunnel endpoint (VTEP), and a port in a pervasive switch virtual interface.
20. The non-transitory computer-readable storage medium of claim 17:
wherein the information further comprises at least one of a circuit identifier, a server identifier override, a link identifier selection, a gateway interface address, and a virtual private network identifier;
wherein the circuit identifier comprises at least one of an interface index value associated with an ingress interface and an endpoint group (EPG) virtual network identifier (VNID) associated with the ingress interface;
wherein the server identifier override comprises a pervasive switch virtual interface (SVI) IP address of a broadcast domain associated with the receiving switch;
wherein the link identifier selection comprises a subnet of the pervasive SVI IP address;
wherein the gateway interface address (GIADDR) comprises one of an interface IP of an interface facing the destination DHCP server or a pervasive IP address associated with a bridge domain in a virtual routing and forwarding (VRF) instance; and
wherein the virtual network identifier (VNID) comprises a virtual routing and forwarding (VRF) name.
US14/484,165 2013-11-05 2014-09-11 Tenant dhcp in an overlay network Abandoned US20150124823A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US201361900359P true 2013-11-05 2013-11-05
US14/484,165 US20150124823A1 (en) 2013-11-05 2014-09-11 Tenant dhcp in an overlay network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/484,165 US20150124823A1 (en) 2013-11-05 2014-09-11 Tenant dhcp in an overlay network

Publications (1)

Publication Number Publication Date
US20150124823A1 true US20150124823A1 (en) 2015-05-07

Family

ID=53006944

Family Applications (10)

Application Number Title Priority Date Filing Date
US14/290,151 Active 2034-12-19 US9374294B1 (en) 2013-11-05 2014-05-29 On-demand learning in overlay networks
US14/329,729 Active 2035-01-30 US9698994B2 (en) 2013-11-05 2014-07-11 Loop detection and repair in a multicast tree
US14/333,151 Active 2035-01-16 US9667431B2 (en) 2013-11-05 2014-07-16 Method and system for constructing a loop free multicast tree in a data-center fabric
US14/336,964 Active 2034-12-25 US9654300B2 (en) 2013-11-05 2014-07-21 N-way virtual port channels using dynamic addressing and modified routing
US14/445,769 Active US9634846B2 (en) 2013-11-05 2014-07-29 Running link state routing protocol in CLOS networks
US14/448,733 Active 2034-08-15 US9444634B2 (en) 2013-11-05 2014-07-31 Miscabling detection protocol
US14/449,033 Active US9985794B2 (en) 2013-11-05 2014-07-31 Traceroute in a dense VXLAN network
US14/477,812 Pending US20150124644A1 (en) 2013-11-05 2014-09-04 Stage upgrade of image versions on devices in a cluster
US14/484,165 Abandoned US20150124823A1 (en) 2013-11-05 2014-09-11 Tenant dhcp in an overlay network
US15/585,837 Active US10164782B2 (en) 2013-11-05 2017-05-03 Method and system for constructing a loop free multicast tree in a data-center fabric

Family Applications Before (8)

Application Number Title Priority Date Filing Date
US14/290,151 Active 2034-12-19 US9374294B1 (en) 2013-11-05 2014-05-29 On-demand learning in overlay networks
US14/329,729 Active 2035-01-30 US9698994B2 (en) 2013-11-05 2014-07-11 Loop detection and repair in a multicast tree
US14/333,151 Active 2035-01-16 US9667431B2 (en) 2013-11-05 2014-07-16 Method and system for constructing a loop free multicast tree in a data-center fabric
US14/336,964 Active 2034-12-25 US9654300B2 (en) 2013-11-05 2014-07-21 N-way virtual port channels using dynamic addressing and modified routing
US14/445,769 Active US9634846B2 (en) 2013-11-05 2014-07-29 Running link state routing protocol in CLOS networks
US14/448,733 Active 2034-08-15 US9444634B2 (en) 2013-11-05 2014-07-31 Miscabling detection protocol
US14/449,033 Active US9985794B2 (en) 2013-11-05 2014-07-31 Traceroute in a dense VXLAN network
US14/477,812 Pending US20150124644A1 (en) 2013-11-05 2014-09-04 Stage upgrade of image versions on devices in a cluster

Family Applications After (1)

Application Number Title Priority Date Filing Date
US15/585,837 Active US10164782B2 (en) 2013-11-05 2017-05-03 Method and system for constructing a loop free multicast tree in a data-center fabric

Country Status (1)

Country Link
US (10) US9374294B1 (en)

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150058470A1 (en) * 2013-08-20 2015-02-26 Arista Networks, Inc. System and method for sharing vxlan table information with a network controller
US20150124643A1 (en) * 2013-11-05 2015-05-07 Cisco Technology, Inc. Miscabling detection protocol
US20160065461A1 (en) * 2013-12-10 2016-03-03 Fujitsu Limited Risk mitigation in data center networks using virtual machine sharing
CN105763671A (en) * 2016-04-27 2016-07-13 杭州华三通信技术有限公司 IP address distribution method and apparatus
US20160344687A1 (en) * 2015-05-22 2016-11-24 International Business Machines Corporation Multi-tenant aware dynamic host configuration protocol (dhcp) mechanism for cloud networking
US20170026234A1 (en) * 2015-07-24 2017-01-26 Aruba Networks, Inc. Auto provisioning of bulk access points
US9996653B1 (en) 2013-11-06 2018-06-12 Cisco Technology, Inc. Techniques for optimizing dual track routing
US10020989B2 (en) 2013-11-05 2018-07-10 Cisco Technology, Inc. Provisioning services in legacy mode in a data center network
US10069726B1 (en) * 2018-03-16 2018-09-04 Tempered Networks, Inc. Overlay network identity-based relay
US10079761B2 (en) 2013-11-05 2018-09-18 Cisco Technology, Inc. Hierarchical routing with table management across hardware modules
US10116493B2 (en) 2014-11-21 2018-10-30 Cisco Technology, Inc. Recovering from virtual port channel peer failure
US10116539B1 (en) 2018-05-23 2018-10-30 Tempered Networks, Inc. Multi-link network gateway with monitoring and dynamic failover
US10142163B2 (en) 2016-03-07 2018-11-27 Cisco Technology, Inc BFD over VxLAN on vPC uplinks
US10148586B2 (en) 2013-11-05 2018-12-04 Cisco Technology, Inc. Work conserving scheduler based on ranking
US10158545B1 (en) 2018-05-31 2018-12-18 Tempered Networks, Inc. Monitoring overlay networks
US10171344B1 (en) * 2017-02-02 2019-01-01 Cisco Technology, Inc. Isolation of endpoints within an endpoint group
US10178133B2 (en) 2014-07-30 2019-01-08 Tempered Networks, Inc. Performing actions via devices that establish a secure, private network
US10182496B2 (en) 2013-11-05 2019-01-15 Cisco Technology, Inc. Spanning tree protocol optimization
US10187302B2 (en) 2013-11-05 2019-01-22 Cisco Technology, Inc. Source address translation in overlay networks
US10193750B2 (en) 2016-09-07 2019-01-29 Cisco Technology, Inc. Managing virtual port channel switch peers from software-defined network controller

Families Citing this family (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9014007B2 (en) * 2013-05-31 2015-04-21 Dell Products L.P. VXLAN based multicasting systems having improved load distribution
US9455901B2 (en) 2013-10-04 2016-09-27 Nicira, Inc. Managing software and hardware forwarding elements to define virtual networks
US9264400B1 (en) * 2013-12-02 2016-02-16 Trend Micro Incorporated Software defined networking pipe for network traffic inspection
US9369388B2 (en) * 2014-01-24 2016-06-14 Cisco Technology, Inc. Forwarding index based adaptive fabric load balancing
US20170155580A1 (en) * 2014-02-04 2017-06-01 Architecture Technology, Inc. Low-Overhead Routing
US10164795B1 (en) * 2014-02-28 2018-12-25 Juniper Networks, Inc. Forming a multi-device layer 2 switched fabric using internet protocol (IP)-router / switched networks
KR20150113597A (en) * 2014-03-31 2015-10-08 한국전자통신연구원 Method and apparatus for processing arp packet
US10216853B2 (en) * 2014-06-27 2019-02-26 Arista Networks, Inc. Method and system for implementing a VXLAN control plane
US20160087887A1 (en) * 2014-09-22 2016-03-24 Hei Tao Fung Routing fabric
CN104283980B (en) * 2014-10-09 2018-02-09 新华三技术有限公司 One kind ARP pickup apparatus and method
US20160234154A1 (en) * 2015-02-06 2016-08-11 Google Inc. Systems and methods for direct dispatching of mobile messages
US9942058B2 (en) 2015-04-17 2018-04-10 Nicira, Inc. Managing tunnel endpoints for facilitating creation of logical networks
US9661022B2 (en) * 2015-04-24 2017-05-23 Dell Products L.P. System and method for authorizing devices joining a network fabric
WO2016177322A1 (en) * 2015-05-04 2016-11-10 Hangzhou H3C Technologies Co., Ltd. Multicast data packet forwarding
WO2016184368A1 (en) * 2015-05-16 2016-11-24 华为技术有限公司 Method, device and system for authorizing service of user
US9804880B2 (en) * 2015-06-16 2017-10-31 Vmware, Inc. Reservation for a multi-machine application
US9992153B2 (en) * 2015-07-15 2018-06-05 Nicira, Inc. Managing link aggregation traffic in edge nodes
US10243914B2 (en) 2015-07-15 2019-03-26 Nicira, Inc. Managing link aggregation traffic in edge nodes
US9967182B2 (en) 2015-07-31 2018-05-08 Nicira, Inc. Enabling hardware switches to perform logical routing functionalities
US20180219773A1 (en) * 2015-08-04 2018-08-02 Nokia Technologies Oy Interconnection of overlay networks
US10313186B2 (en) 2015-08-31 2019-06-04 Nicira, Inc. Scalable controller for hardware VTEPS
CN106549820A (en) * 2015-09-23 2017-03-29 阿里巴巴集团控股有限公司 Method and device for identifying network loop and traffic cleaning equipment and system
US9998324B2 (en) 2015-09-30 2018-06-12 Nicira, Inc. Logical L3 processing for L2 hardware switches
US10230576B2 (en) * 2015-09-30 2019-03-12 Nicira, Inc. Managing administrative statuses of hardware VTEPs
US9948577B2 (en) 2015-09-30 2018-04-17 Nicira, Inc. IP aliases in logical networks with hardware switches
US10263828B2 (en) 2015-09-30 2019-04-16 Nicira, Inc. Preventing concurrent distribution of network data to a hardware switch by multiple controllers
US10250553B2 (en) 2015-11-03 2019-04-02 Nicira, Inc. ARP offloading for managed hardware forwarding elements
US9985867B2 (en) * 2015-12-11 2018-05-29 Cisco Technology, Inc. Optimizing EVPN for data centers with redundant top-of-rack deployments
US9998375B2 (en) 2015-12-15 2018-06-12 Nicira, Inc. Transactional controls for supplying control plane data to managed hardware forwarding elements
US9917799B2 (en) 2015-12-15 2018-03-13 Nicira, Inc. Transactional controls for supplying control plane data to managed hardware forwarding elements
US9992112B2 (en) 2015-12-15 2018-06-05 Nicira, Inc. Transactional controls for supplying control plane data to managed hardware forwarding elements
US10129125B2 (en) * 2015-12-18 2018-11-13 Mcafee, Llc Identifying a source device in a software-defined network
US10298460B2 (en) * 2015-12-21 2019-05-21 Dell Products, Lp System and method for aggregating communication and control of wireless end-points in a data center
CN106982163A (en) * 2016-01-18 2017-07-25 华为技术有限公司 Method for obtaining routing on demand and gateway
CN107294743A (en) * 2016-03-30 2017-10-24 华为技术有限公司 Network path detection method, controller and network device
US20170317919A1 (en) * 2016-04-29 2017-11-02 Cisco Technology, Inc. Interoperability between data plane learning endpoints and control plane learning endpoints in overlay networks
CN107332772A (en) * 2016-04-29 2017-11-07 华为技术有限公司 Forwarding table item building method and device
US20170324651A1 (en) * 2016-05-09 2017-11-09 Cisco Technology, Inc. Traceroute to return aggregated statistics in service chains
US20170346684A1 (en) * 2016-05-24 2017-11-30 Apstra, Inc. Configuring system resources for different reference architectures
US10050804B2 (en) * 2016-06-01 2018-08-14 Pluribus Networks, Inc. Loop-free fabric utilizing distributed address and port tables
US10182035B2 (en) 2016-06-29 2019-01-15 Nicira, Inc. Implementing logical network security on a hardware switch
US10050874B2 (en) * 2016-11-01 2018-08-14 Nicira, Inc. Media access control address learning for packets
CN108574635A (en) * 2017-03-09 2018-09-25 华为技术有限公司 Route priority configuration method, equipment and controller
US20180278514A1 (en) * 2017-03-27 2018-09-27 Juniper Networks, Inc. Traceroute for multi-path routing
US10218572B2 (en) 2017-06-19 2019-02-26 Cisco Technology, Inc. Multiprotocol border gateway protocol routing validation
US10091348B1 (en) 2017-07-25 2018-10-02 Cisco Technology, Inc. Predictive model for voice/video over IP calls

Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040103310A1 (en) * 2002-11-27 2004-05-27 Sobel William E. Enforcement of compliance with network security policies
US20040160956A1 (en) * 2001-03-27 2004-08-19 Hardy William Geoffrey Network tunnelling
US20040249960A1 (en) * 2001-03-27 2004-12-09 Hardy William Geoffrey Access networks
US20050013280A1 (en) * 2003-07-14 2005-01-20 Buddhikot Milind M. Method and system for mobility across heterogeneous address spaces
US20050175020A1 (en) * 2004-02-05 2005-08-11 Samsung Electronics Co., Ltd. Tunneling service method and system
US20060028285A1 (en) * 2004-07-26 2006-02-09 Samsung Electronics Co., Ltd. Method and apparatus for automatic tunnel configuration
US20060209688A1 (en) * 2005-03-02 2006-09-21 Hitachi Communication Technologies, Ltd. Packet forwarding apparatus
US20060250982A1 (en) * 2005-05-05 2006-11-09 Harrow Products Llc Methods and systems for discovering and configuring network devices
US20060280179A1 (en) * 2001-04-25 2006-12-14 Meier Robert C Dhcp over mobile ip
US7152117B1 (en) * 2001-10-04 2006-12-19 Cisco Technology, Inc. Techniques for dynamic host configuration using overlapping network
US20070280264A1 (en) * 2006-05-30 2007-12-06 Motorola, Inc. Method and system for intertechnology handoff of a hybrid access terminal
US20080092213A1 (en) * 2005-04-29 2008-04-17 Huawei Technologies Co., Ltd. Method, system and server for realizing secure assignment of dhcp address
US20080147830A1 (en) * 2006-12-14 2008-06-19 Ridgill Stephen P Selective sub-net filtering in a pre-boot execution environment (pxe)
US20090193103A1 (en) * 2008-01-29 2009-07-30 Small Keith M Method of and System for Support of User Devices Roaming Between Routing Realms by a Single Network Server
US20100191813A1 (en) * 2009-01-28 2010-07-29 Juniper Networks, Inc. Automatically releasing resources reserved for subscriber devices within a broadband access network
US20100191839A1 (en) * 2009-01-28 2010-07-29 Juniper Networks, Inc. Synchronizing resource bindings within computer network
US20100223655A1 (en) * 2007-11-20 2010-09-02 Huawei Technologies Co., Ltd. Method, System, and Apparatus for DHCP Authentication
US20100312875A1 (en) * 2009-06-05 2010-12-09 Square D. Company Automated discovery of monitoring devices on a network
US20130097335A1 (en) * 2011-10-14 2013-04-18 Kanzhe Jiang System and methods for managing network protocol address assignment with a controller
US20130182712A1 (en) * 2012-01-13 2013-07-18 Dan Aguayo System and method for managing site-to-site vpns of a cloud managed network
US20130250951A1 (en) * 2012-03-22 2013-09-26 Brocade Communications Systems, Inc. Overlay tunnel in a fabric switch
US20130311991A1 (en) * 2011-01-13 2013-11-21 Huawei Technologies Co., Ltd. Virtual machine migration method, switch, and virtual machine system
US20130311663A1 (en) * 2012-05-15 2013-11-21 International Business Machines Corporation Overlay tunnel information exchange protocol
US20130322446A1 (en) * 2012-06-05 2013-12-05 International Business Machines Corporation Virtual ethernet port aggregation (vepa)-enabled multi-tenant overlay network
US20130322453A1 (en) * 2012-06-04 2013-12-05 David Ian Allan Routing vlan tagged packets to far end addresses of virtual forwarding instances using separate administrations
US20130332577A1 (en) * 2012-06-06 2013-12-12 Juniper Networks, Inc. Multitenant server for virtual networks within datacenter
US20140016501A1 (en) * 2012-07-16 2014-01-16 International Business Machines Corporation Flow based overlay network
US20140068750A1 (en) * 2012-08-30 2014-03-06 Tropos Networks, Inc. Establishing an ipsec (internet protocol security) vpn (virtual private network) tunnel
US20140146817A1 (en) * 2012-11-29 2014-05-29 Futurewei Technologies, Inc. System and Method for VXLAN Intern-Domain Communications
US20140269712A1 (en) * 2013-03-14 2014-09-18 International Business Machines Corporation Tagging virtual overlay packets in a virtual networking system
US20140321277A1 (en) * 2013-04-30 2014-10-30 Comcast Cable Communications, Llc Network Validation
US20150092593A1 (en) * 2013-09-30 2015-04-02 Juniper Networks, Inc. Methods and apparatus for implementing connectivity between edge devices via a switch fabric

Family Cites Families (266)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS573233B2 (en) 1978-08-25 1982-01-20
CA1237820A (en) 1985-03-20 1988-06-07 Hitachi, Ltd. Multilayer printed circuit board
US4700016A (en) 1986-05-16 1987-10-13 International Business Machines Corporation Printed circuit board with vias at fixed and selectable locations
US5115431A (en) 1990-09-28 1992-05-19 Stratacom, Inc. Method and apparatus for packet communications signaling
US5859835A (en) 1996-04-15 1999-01-12 The Regents Of The University Of California Traffic scheduling system and method for packet-switched networks
GB9626752D0 (en) 1996-12-23 1997-02-12 Northern Telecom Ltd Management of data structures
US5926458A (en) 1997-01-31 1999-07-20 Bay Networks Method and apparatus for servicing multiple queues
US6456624B1 (en) * 1997-10-29 2002-09-24 Enterasys Networks, Inc. Network address resolve blocker
US6389031B1 (en) 1997-11-05 2002-05-14 Polytechnic University Methods and apparatus for fairly scheduling queued packets using a ram-based search engine
US6714553B1 (en) 1998-04-15 2004-03-30 Top Layer Networks, Inc. System and process for flexible queuing of data packets in network switching
US7480242B2 (en) 1998-11-24 2009-01-20 Pluris, Inc. Pass/drop apparatus and method for network switching node
US6996099B1 (en) 1999-03-17 2006-02-07 Broadcom Corporation Network switch having a programmable counter
US6650640B1 (en) 1999-03-01 2003-11-18 Sun Microsystems, Inc. Method and apparatus for managing a network flow in a high performance network interface
US6662223B1 (en) 1999-07-01 2003-12-09 Cisco Technology, Inc. Protocol to coordinate network end points to measure network latency
US6680942B2 (en) * 1999-07-02 2004-01-20 Cisco Technology, Inc. Directory services caching for network peer to peer service locator
US6952421B1 (en) 1999-10-07 2005-10-04 Cisco Technology, Inc. Switched Ethernet path detection
US6757897B1 (en) 2000-02-29 2004-06-29 Cisco Technology, Inc. Apparatus and methods for scheduling and performing tasks
US6880086B2 (en) 2000-05-20 2005-04-12 Ciena Corporation Signatures for facilitating hot upgrades of modular software components
US7082102B1 (en) 2000-10-19 2006-07-25 Bellsouth Intellectual Property Corp. Systems and methods for policy-enabled communications networks
US6954463B1 (en) 2000-12-11 2005-10-11 Cisco Technology, Inc. Distributed packet processing architecture for network access servers
US6944863B1 (en) 2000-12-21 2005-09-13 Unisys Corporation Queue bank repository and method for sharing limited queue banks in memory
US7027418B2 (en) 2001-01-25 2006-04-11 Bandspeed, Inc. Approach for selecting communications channels based on performance
US6677831B1 (en) 2001-01-31 2004-01-13 3Pardata, Inc. Differential impedance control on printed circuit
US8429296B2 (en) 2001-03-06 2013-04-23 Pluris, Inc. Method and apparatus for distributing routing instructions over multiple interfaces of a data router
US20020188754A1 (en) 2001-04-27 2002-12-12 Foster Michael S. Method and system for domain addressing in a communications network
US7272137B2 (en) 2001-05-14 2007-09-18 Nortel Networks Limited Data stream filtering apparatus and method
US7027414B2 (en) 2001-08-09 2006-04-11 Hughes Network Systems, Llc Method, apparatus, and system for identifying and efficiently treating classes of traffic
US20030058860A1 (en) 2001-09-25 2003-03-27 Kunze Aaron R. Destination address filtering
US7613167B2 (en) 2001-09-27 2009-11-03 Broadcom Corporation Method and system for upstream priority lookup at physical interface
US6834139B1 (en) 2001-10-02 2004-12-21 Cisco Technology, Inc. Link discovery and verification procedure using loopback
US7277383B2 (en) 2001-10-05 2007-10-02 Samsung Electronics Co., Ltd. Redundancy mechanization protocol for a massively parallel router
US7284047B2 (en) 2001-11-08 2007-10-16 Microsoft Corporation System and method for controlling network demand via congestion pricing
US7177946B1 (en) 2001-12-06 2007-02-13 Cisco Technology, Inc. Optimal sync for rapid spanning tree protocol
US8089888B2 (en) 2001-12-10 2012-01-03 Qualcomm Incorporated Method and apparatus for testing traffic and auxiliary channels in a wireless data communication system
US20030115319A1 (en) 2001-12-17 2003-06-19 Dawson Jeffrey L. Network paths
US6668313B2 (en) 2001-12-21 2003-12-23 Agere Systems, Inc. Memory system for increased bandwidth
US7307986B2 (en) 2002-02-04 2007-12-11 Intel Corporation State record processing
US6941649B2 (en) 2002-02-05 2005-09-13 Force10 Networks, Inc. Method of fabricating a high-layer-count backplane
US20030174650A1 (en) 2002-03-15 2003-09-18 Broadcom Corporation Weighted fair queuing (WFQ) shaper
US8078763B1 (en) 2002-04-04 2011-12-13 Juniper Networks, Inc. Dequeuing and congestion control systems and methods for single stream multicast
EP1367750A1 (en) 2002-05-30 2003-12-03 Agilent Technologies, Inc. Testing network communications
US20030231646A1 (en) 2002-06-14 2003-12-18 Chandra Prashant R. Method and system for efficient random packet enqueue, drop or mark processing in network traffic
US7209976B2 (en) 2002-07-16 2007-04-24 Jeremy Benjamin Protocol communication and transit packet forwarding routed between multiple virtual routers within a single physical router
US6907039B2 (en) 2002-07-20 2005-06-14 Redback Networks Inc. Method and apparatus for routing and forwarding between virtual routers within a single network element
US7280477B2 (en) 2002-09-27 2007-10-09 International Business Machines Corporation Token-based active queue management
US7206284B2 (en) 2002-11-27 2007-04-17 International Business Machines Corporation Method and apparatus for automatic congestion avoidance for differentiated service flows
US20040111507A1 (en) 2002-12-05 2004-06-10 Michael Villado Method and system for monitoring network communications in real-time
US20070061451A1 (en) 2002-12-05 2007-03-15 Michael Villado Method and system for monitoring network communications in real-time
US20050201375A1 (en) 2003-01-14 2005-09-15 Yoshihide Komatsu Uninterrupted transfer method in IP network in the event of line failure
FR2852762B1 (en) 2003-03-19 2005-06-17 Method for assessment of the bandwidth of a digital link
US6876952B1 (en) 2003-04-30 2005-04-05 Cisco Technology, Inc. Methods and apparatus for maintaining queues
US7372857B1 (en) 2003-05-28 2008-05-13 Cisco Technology, Inc. Methods and apparatus for scheduling tasks
US7372865B2 (en) 2003-07-09 2008-05-13 Fujitsu Limited Processing data packets using time stamped marker packets
US20050010685A1 (en) * 2003-07-11 2005-01-13 Agency For Science, Technology And Research Method and a system for enabling data to be stored in a computer network; a method and a system for storing data in a computer network
US7516211B1 (en) 2003-08-05 2009-04-07 Cisco Technology, Inc. Methods and apparatus to configure a communication port
US7474666B2 (en) 2003-09-03 2009-01-06 Cisco Technology, Inc. Switch port analyzers
US7580409B1 (en) 2003-09-08 2009-08-25 Extreme Networks, Inc. System for and method of communicating control information between entities interconnected by backplane connections
GB2421158B (en) 2003-10-03 2007-07-11 Avici Systems Inc Rapid alternate paths for network destinations
US7539131B2 (en) 2003-11-26 2009-05-26 Redback Networks Inc. Nexthop fast rerouter for IP and MPLS
US7366099B2 (en) 2003-12-01 2008-04-29 Cisco Technology, Inc. Method and apparatus for synchronizing a data communications network
US7657706B2 (en) 2003-12-18 2010-02-02 Cisco Technology, Inc. High speed memory and input/output processor subsystem for efficiently allocating and using high-speed memory and slower-speed memory
CA2554876A1 (en) 2004-02-06 2005-08-18 Apparent Networks, Inc. Method and apparatus for characterizing an end-to-end path of a packet-based network
US7583667B2 (en) 2004-03-19 2009-09-01 Avaya Inc. Automatic determination of connectivity problem locations or other network-characterizing information in a network utilizing an encapsulation protocol
JP2005277804A (en) 2004-03-25 2005-10-06 Hitachi Ltd Information relaying apparatus
US8081566B1 (en) 2004-04-19 2011-12-20 Rockstar BIDCO, LLP Method and apparatus for indicating congestion in a source routed network
FR2870064A1 (en) 2004-05-07 2005-11-11 France Telecom performance measurement in a packet transmission network
US7555579B2 (en) 2004-05-21 2009-06-30 Nortel Networks Limited Implementing FIFOs in shared memory using linked lists and interleaved linked lists
JP4390649B2 (en) * 2004-07-14 2009-12-24 富士通株式会社 Network loop detection devices
US7411915B1 (en) 2004-07-21 2008-08-12 Cisco Technology, Inc. Automatically configuring switch ports with appropriate features
WO2006025579A1 (en) 2004-09-03 2006-03-09 Anritsu Corporation Missing packet measurement device and error measurement device using the same
US7467226B2 (en) 2004-10-05 2008-12-16 Cisco Technology, Inc. Method and apparatus for flooding link state packets to achieve faster convergence
US20060075093A1 (en) 2004-10-05 2006-04-06 Enterasys Networks, Inc. Using flow metric events to control network operation
GB2419255A (en) 2004-10-14 2006-04-19 Agilent Technologies Inc Modifying an aggregate test in a network probe
GB2419490A (en) 2004-10-19 2006-04-26 Agilent Technologies Inc Analysing datagrams in a packet forwarding apparatus making use of a separately retrievable multicast field.
WO2006043624A1 (en) 2004-10-21 2006-04-27 Nec Corporation Communication quality measurement device and measurement method thereof
US7742437B2 (en) 2004-11-15 2010-06-22 Cisco Technology, Inc. CSNP cache for efficient periodic CSNP in a router
US9426092B2 (en) 2006-02-03 2016-08-23 Level 3 Communications Llc System and method for switching traffic through a network
JP4454516B2 (en) 2005-02-16 2010-04-21 富士通株式会社 Failure detection device
CN100576812C (en) * 2005-02-28 2009-12-30 日本电气株式会社 Packet ring network system, method for connection between packet rings, and inter-ring connection node
US7570649B2 (en) 2005-02-28 2009-08-04 Alcatel Lucent Forwarding state sharing between multiple traffic paths in a communication network
JP2006245849A (en) 2005-03-02 2006-09-14 Fujitsu Ltd Communication apparatus
US7436772B2 (en) 2005-03-23 2008-10-14 Microsoft Corporation Available bandwidth estimation
US7894407B2 (en) 2005-03-25 2011-02-22 Alcatel-Lucent Usa Inc. Method and apparatus for seamless roaming for wireless networks
US7672244B2 (en) 2005-03-30 2010-03-02 Cisco Technology, Inc. Converting a network device from data rate traffic management to packet rate
US7693144B2 (en) 2005-03-31 2010-04-06 Alcatel-Lucent Usa Inc. Method of providing VPLS service in a bridged (e.g. 802.1D) network of a service provider
US7486720B2 (en) 2005-05-11 2009-02-03 Mitsubishi Electric Research Laboratories, Inc. Training frames for MIMO stations
US7894372B2 (en) * 2005-05-31 2011-02-22 Iac Search & Media, Inc. Topology-centric resource management for large scale service clusters
US8189483B2 (en) 2005-06-01 2012-05-29 Litepoint Corporation Method for measuring sensitivity of data packet signal receiver
US20060274647A1 (en) * 2005-06-02 2006-12-07 Broadcom Corporation Dynamic port failover
US7773611B2 (en) 2005-06-15 2010-08-10 Cisco Technology, Inc. Method and apparatus for packet loss detection
GB0513321D0 (en) 2005-06-29 2005-08-03 Ibm A method and system for determining a plurality of scheduling endpoints in a grid network
US7599303B2 (en) 2005-07-26 2009-10-06 Cisco Technology, Inc. System and methods for sending trace messages
US8223666B2 (en) 2005-08-23 2012-07-17 Cisco Technology, Inc. Method of constructing a forwarding database for a data communications network
US20070053303A1 (en) 2005-09-08 2007-03-08 Acterna Llc Transmission Quality Monitoring For Multimedia Streams
US7835293B2 (en) 2005-09-13 2010-11-16 Cisco Technology, Inc. Quality of service testing of communications networks
US20070058557A1 (en) 2005-09-15 2007-03-15 Interdigital Technology Corporation Method and apparatus for scheduling data transmissions based on a traffic data pattern model
US7864669B2 (en) 2005-10-20 2011-01-04 Cisco Technology, Inc. Method of constructing a backup path in an autonomous system
US20070097872A1 (en) 2005-10-27 2007-05-03 Inventec Corporation Network connection apparatus testing method
CN100563203C (en) 2005-11-11 2009-11-25 华为技术有限公司 A method to transmit signal of network element of leaf node at multicast tree in communication network
US7872992B2 (en) 2005-12-09 2011-01-18 Panasonic Corporation Network system and relay device
US8233384B2 (en) * 2005-12-21 2012-07-31 Rockstar Bidco, LP Geographic redundancy in communication networks
JP4759389B2 (en) 2006-01-10 2011-08-31 アラクサラネットワークス株式会社 Packet communication device
US7756066B2 (en) 2006-01-10 2010-07-13 Cisco Technology, Inc. Seamless spanning tree restart of a single supervisor
US8441919B2 (en) 2006-01-18 2013-05-14 Cisco Technology, Inc. Dynamic protection against failure of a head-end node of one or more TE-LSPs
US7911938B2 (en) 2006-01-20 2011-03-22 Cisco Technology, Inc. System and method for preventing loops in the presence of control plane failures
US7835378B2 (en) 2006-02-02 2010-11-16 Cisco Technology, Inc. Root node redundancy for multipoint-to-multipoint transport trees
US20070183337A1 (en) 2006-02-03 2007-08-09 International Business Machines Corporation FC-AL cabling management system
US8204005B2 (en) 2006-03-09 2012-06-19 Intel Corporation Wireless communication device and method for dynamic bidirectional aggregation of MAC frames with delayed channel access in a wireless network
US8934486B2 (en) 2006-03-16 2015-01-13 Cisco Technology, Inc. System and method for implementing multicast over a label-switched core network
US7539133B2 (en) 2006-03-23 2009-05-26 Alcatel-Lucent Usa Inc. Method and apparatus for preventing congestion in load-balancing networks
US7747734B2 (en) 2006-03-29 2010-06-29 International Business Machines Corporation Apparatus, system, and method for error assessment over a communication link
DE602006019946D1 (en) 2006-05-02 2011-03-17 Acterna France System and method for monitoring a data network segment
US7715309B2 (en) 2006-05-24 2010-05-11 At&T Intellectual Property I, L.P. Method and apparatus for reliable communications in a packet network
US7426604B1 (en) 2006-06-14 2008-09-16 Sun Microsystems, Inc. Virtual output buffer architecture
US7630368B2 (en) 2006-06-30 2009-12-08 Sun Microsystems, Inc. Virtual network interface card loopback fastpath
US7899049B2 (en) 2006-08-01 2011-03-01 Cisco Technology, Inc. Methods and apparatus for minimizing duplicate traffic during point to multipoint tree switching in a network
KR100833510B1 (en) 2006-08-03 2008-05-29 한국전자통신연구원 Method and Apparatus for measurement of LSP performance parameters using MPLS OAM packet
JP5092307B2 (en) 2006-08-04 2012-12-05 富士通株式会社 Network device and a data control program
US7822594B2 (en) 2006-08-07 2010-10-26 Voltaire Ltd. Service-oriented infrastructure management
WO2008073013A1 (en) 2006-12-13 2008-06-19 Telefonaktiebolaget Lm Ericsson (Publ) A method of scheduling data transmission in a radio network
EP1936880A1 (en) 2006-12-18 2008-06-25 British Telecommunications Public Limited Company Method and system for congestion marking
US9253274B2 (en) 2007-01-19 2016-02-02 Cisco Technology, Inc. Service insertion architecture
IL189514A (en) 2007-02-14 2011-12-29 Marvell Israel Misl Ltd Logical bridging system and method
CN101247321B (en) 2007-02-14 2012-07-04 华为技术有限公司 Method, device and system for routing diagnosis in network based on diameter protocol
JP4992482B2 (en) 2007-03-09 2012-08-08 富士通株式会社 Network test equipment
US8045558B2 (en) 2007-04-23 2011-10-25 Cisco Technology, Inc. Extensions to IPv6 neighbor discovery protocol for automated prefix delegation
US8005013B2 (en) 2007-06-12 2011-08-23 Hewlett-Packard Development Company, L.P. Managing connectivity in a virtual network
JP5061748B2 (en) * 2007-06-21 2012-10-31 日本電気株式会社 Packet ring network system, a packet transfer method
JP2009049708A (en) 2007-08-20 2009-03-05 Fujitsu Ltd Apparatus for gathering network fault information, system, method and program
US9350639B2 (en) 2007-09-06 2016-05-24 Cisco Technology, Inc. Forwarding data in a data communications network
US7729296B1 (en) 2007-09-07 2010-06-01 Force 10 Networks, Inc. Distributed BPDU processing for spanning tree protocols
US7991877B2 (en) 2007-10-05 2011-08-02 International Business Machines Corporation Rogue router hunter
JP2009111747A (en) 2007-10-30 2009-05-21 Sony Corp Relay device and method, and program
US8000251B2 (en) 2007-11-14 2011-08-16 Cisco Technology, Inc. Instrumenting packet flows
US8514712B1 (en) 2007-12-06 2013-08-20 Force10 Networks, Inc. Non-stop VoIP support
US7752666B2 (en) * 2007-12-21 2010-07-06 At&T Labs, Inc. Detection of routing loops based on time-to-live expiries
US7830223B2 (en) 2008-01-30 2010-11-09 Cisco Technology, Inc. Ground straddling in PTH pinfield for improved impedance
US7948910B2 (en) 2008-03-06 2011-05-24 Cisco Technology, Inc. Monitoring quality of a packet flow in packet-based communication networks
JP5432928B2 (en) 2008-03-12 2014-03-05 テレフオンアクチーボラゲット エル エム エリクソン(パブル) Method and apparatus for link state handshake for a loop prevention
US8073945B2 (en) 2008-04-25 2011-12-06 At&T Intellectual Property I, L.P. Method and apparatus for providing a measurement of performance for a network
US7787399B2 (en) 2008-07-25 2010-08-31 Alcatel-Lucent Usa Inc. Automatically configuring mesh groups in data networks
US7778204B2 (en) 2008-07-25 2010-08-17 Alcatel-Lucent Usa Inc. Automatic maintenance of a distributed source tree (DST) network
US7937492B1 (en) 2008-09-30 2011-05-03 Juniper Networks, Inc. LSP ping and traceroute for bypass tunnels
US7936754B2 (en) 2008-12-12 2011-05-03 At&T Intellectual Property I, L.P. Methods and apparatus to dynamically store network routes for a communication network
US8234369B2 (en) 2008-12-23 2012-07-31 Verizon Patent And Licensing Inc. Web page response monitoring
WO2010082939A1 (en) 2009-01-19 2010-07-22 Hewlett-Packard Development Company, L.P. Load balancing
US7826469B1 (en) 2009-03-09 2010-11-02 Juniper Networks, Inc. Memory utilization in a priority queuing system of a network device
US8243743B2 (en) 2009-04-09 2012-08-14 Ciena Corporation In-band signaling for point-multipoint packet protection switching
US8990431B2 (en) 2009-05-05 2015-03-24 Citrix Systems, Inc. Systems and methods for identifying a processor from a plurality of processors to provide symmetrical request and response processing
CN101883044A (en) 2009-05-08 2010-11-10 华为技术有限公司 Method, device and system for establishing bidirectional point-to-multipoint label switch paths
CN101562543B (en) 2009-05-25 2013-07-31 阿里巴巴集团控股有限公司 Cache data processing method and processing system and device thereof
CN102045229B (en) 2009-10-19 2014-12-10 中兴通讯股份有限公司 Topology management method and system of Ethernet multi-loop network
US8891368B2 (en) 2009-11-06 2014-11-18 Brocade Communications Systems, Inc. Presentation of a selected port
US20110110587A1 (en) 2009-11-12 2011-05-12 Banner Ron Generating Harmonic Images
US8687629B1 (en) 2009-11-18 2014-04-01 Juniper Networks, Inc. Fabric virtualization for packet and circuit switching
DK2507951T5 (en) 2009-12-04 2013-12-02 Napatech As Apparatus and method for receiving and storing data packets controlled by a central controller
US9497092B2 (en) 2009-12-08 2016-11-15 Hand Held Products, Inc. Remote device management interface
US8325459B2 (en) 2009-12-08 2012-12-04 International Business Machines Corporation Channel performance of electrical lines
US8442063B1 (en) 2009-12-21 2013-05-14 Xuyang Zhou System and method for scheduling unicast and multicast traffic
US9054996B2 (en) 2009-12-24 2015-06-09 Juniper Networks, Inc. Dynamic prioritized fair share scheduling scheme in over-subscribed port scenario
US8773978B2 (en) 2010-02-15 2014-07-08 Futurewei Technologies, Inc. System and method for protecting ingress and egress of a point-to-multipoint label switched path
JP2013520137A (en) 2010-02-16 2013-05-30 ホアウェイ・テクノロジーズ・カンパニー・リミテッド Rate fluctuations Multicast transmissions for clock distribution in a packet network
JP5427644B2 (en) 2010-02-25 2014-02-26 株式会社日立製作所 Printed board
US8364864B2 (en) 2010-03-17 2013-01-29 Juniper Networks, Inc. Multi-bank queuing architecture for higher bandwidth on-chip memory buffer
US8713525B2 (en) 2010-03-25 2014-04-29 International Business Machines Corporation Software management system for network data processing systems
US8249069B2 (en) 2010-03-30 2012-08-21 Cisco Technology, Inc. Forwarding multi-destination packets in a network with virtual port channels
DE112011101132T5 (en) 2010-03-31 2013-01-03 Flextronics Ap, Llc Improved rear drilling of multilayer circuit boards
US8218557B2 (en) 2010-04-09 2012-07-10 Telefonaktiebolaget L M Ericsson (Publ) Scalable distributed user plane partitioned two-stage forwarding information base lookup for subscriber internet protocol host routes
US8811398B2 (en) 2010-04-30 2014-08-19 Hewlett-Packard Development Company, L.P. Method for routing data packets using VLANs
US9036481B1 (en) 2010-05-05 2015-05-19 Marvell International Ltd. Method and apparatus for adaptive packet load balancing
US8625616B2 (en) 2010-05-11 2014-01-07 Brocade Communications Systems, Inc. Converged network extension
US8750297B2 (en) 2010-05-20 2014-06-10 Comcast Cable Communications, Llc Ascertaining per-hop network characteristics
US8634308B2 (en) 2010-06-02 2014-01-21 Brocade Communications Systems, Inc. Path detection in trill networks
US8553545B2 (en) 2010-06-22 2013-10-08 Verizon Patent And Licensing Inc. Congestion buffer control in wireless networks
CN102598616B (en) 2010-06-24 2015-12-02 华为技术有限公司 Multicast implemented method, apparatus and system for
US8407689B2 (en) 2010-06-25 2013-03-26 Microsoft Corporation Updating nodes considering service model constraints
CN102333413A (en) 2010-07-12 2012-01-25 鸿富锦精密工业(深圳)有限公司 Printed circuit board
US20120030150A1 (en) 2010-07-29 2012-02-02 Telcordia Technologies, Inc. Hybrid Learning Component for Link State Routing Protocols
US8392908B2 (en) 2010-07-30 2013-03-05 Sap Ag Standardized procedures for implementing software changes
US8339973B1 (en) 2010-09-07 2012-12-25 Juniper Networks, Inc. Multicast traceroute over MPLS/BGP IP multicast VPN
US8886766B2 (en) 2010-10-25 2014-11-11 Salesforce.Com, Inc. Systems and methods for tracking responses on an online social network
US8737418B2 (en) 2010-12-22 2014-05-27 Brocade Communications Systems, Inc. Queue speed-up by using multiple linked lists
US9396090B2 (en) 2010-12-28 2016-07-19 Sap Se System overview diagram generator
US8868766B1 (en) 2011-03-29 2014-10-21 Amazon Technologies, Inc. Optimizing communication among collections of computing resources
JP5235032B2 (en) 2011-04-04 2013-07-10 シャープ株式会社 Display device, an information processing system and program
EP2690820B1 (en) 2011-04-26 2016-06-08 Huawei Technologies Co., Ltd. Method, apparatus and system for mapping service instance
US8693489B2 (en) 2011-04-28 2014-04-08 Alcatel Lucent Hierarchical profiled scheduling and shaping
US9225628B2 (en) 2011-05-24 2015-12-29 Mellanox Technologies Ltd. Topology-based consolidation of link state information
US8693341B2 (en) 2011-06-10 2014-04-08 Force10 Networks, Inc. Method and apparatus for optimizing data traffic path through a stacked switch LAG configuration
TWI434634B (en) 2011-08-09 2014-04-11 中原大學
US9134992B2 (en) 2011-08-31 2015-09-15 Vmware, Inc. Interactive and visual planning tool for managing installs and upgrades
US20130064246A1 (en) 2011-09-12 2013-03-14 Cisco Technology, Inc. Packet Forwarding Using an Approximate Ingress Table and an Exact Egress Table
US8610000B2 (en) 2011-10-07 2013-12-17 Tyco Electronics Corporation Circuit board for an electrical connector
US20130124708A1 (en) 2011-11-10 2013-05-16 Electronics And Telecommunications Research Institute Method and system for adaptive composite service path management
US8935375B2 (en) 2011-12-12 2015-01-13 Microsoft Corporation Increasing availability of stateful applications
US8761053B2 (en) 2012-02-09 2014-06-24 Futurewei Technologies, Inc. Link state fast flood with computed multi-protocol-label-switching (MPLS) broadcast tree
EP2815360A4 (en) 2012-02-17 2015-12-02 Vencore Labs Inc Multi-function electric meter adapter and method for use
US9426068B2 (en) 2012-02-24 2016-08-23 Futurewei Technologies, Inc. Balancing of forwarding and address resolution in overlay networks
US9143429B2 (en) 2012-02-28 2015-09-22 Google Inc. Identifying an egress point to a network location
US9178778B2 (en) 2012-03-23 2015-11-03 Avaya Inc. System and method for end-to-end RTCP
US9438965B2 (en) 2012-04-13 2016-09-06 The Nielsen Company (Us), Llc Methods, apparatus, and articles of manufacture to identify media delivery
US9106508B2 (en) 2012-04-30 2015-08-11 International Business Machines Corporation Providing services to virtual overlay network traffic
US8837300B2 (en) 2012-06-05 2014-09-16 Cisco Technology, Inc. Managing trace requests over tunneled links
US9064216B2 (en) 2012-06-06 2015-06-23 Juniper Networks, Inc. Identifying likely faulty components in a distributed system
US10129182B2 (en) 2012-06-29 2018-11-13 Juniper Networks, Inc. Methods and apparatus for providing services in distributed switch
CN103580902B (en) 2012-08-07 2015-01-14 腾讯科技(深圳)有限公司 Computer information system and dynamic disaster recovery method thereof
US9258195B1 (en) 2012-08-08 2016-02-09 Shoretel, Inc. Logical topology visualization
US8989192B2 (en) 2012-08-15 2015-03-24 Futurewei Technologies, Inc. Method and system for creating software defined ordered service patterns in a communications network
US9602430B2 (en) 2012-08-21 2017-03-21 Brocade Communications Systems, Inc. Global VLANs for fabric switches
US9124527B2 (en) 2012-08-29 2015-09-01 International Business Machines Corporation Sliced routing table management
WO2014032174A1 (en) 2012-08-31 2014-03-06 Bce Inc. Ip mpls pop virtualization and fault tolerant virtual router
US8837476B2 (en) 2012-09-07 2014-09-16 International Business Machines Corporation Overlay network capable of supporting storage area network (SAN) traffic
US8989048B2 (en) 2012-09-25 2015-03-24 Hangzhou H3C Technologies Co., Ltd. Node system ID change in link state protocol network
US20140086253A1 (en) 2012-09-26 2014-03-27 Futurewei Technologies, Inc. Overlay Virtual Gateway for Overlay Networks
US9178715B2 (en) 2012-10-01 2015-11-03 International Business Machines Corporation Providing services to virtual overlay network traffic
US10044548B2 (en) 2012-10-15 2018-08-07 Jetflow Technologies Flowlet-based processing
US9380111B2 (en) 2012-10-17 2016-06-28 Verizon Patent And Licensing Inc. Feature peer network with scalable state information
US9160797B2 (en) 2012-10-17 2015-10-13 Verizon Patent And Licensing Inc. Network devices with feature peer network logic
US9787570B2 (en) 2012-10-17 2017-10-10 Verizon Patent And Licensing Inc. Dynamic feature peer network for application flows
US9245626B2 (en) 2012-10-26 2016-01-26 Cisco Technology, Inc. System and method for packet classification and internet protocol lookup in a network environment
WO2014071996A1 (en) 2012-11-12 2014-05-15 Abb Technology Ag System and method for visualizing a combined physical and virtual communication network of a power plant
US20140146661A1 (en) 2012-11-28 2014-05-29 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for facilitating process restart in an is-is system
US9137154B2 (en) 2012-11-29 2015-09-15 Lenovo Enterprise Solutions (Singapore Pte. LTD Management of routing tables shared by logical switch partitions in a distributed network switch
US8934278B2 (en) 2012-12-28 2015-01-13 Qualcomm Incorporated Hybrid ternary content addressable memory
US8958226B2 (en) 2012-12-28 2015-02-17 Qualcomm Incorporated Static NAND cell for ternary content addressable memory (TCAM)
US20140201375A1 (en) 2013-01-11 2014-07-17 Anuta Networks, Inc. Method, apparatus and system pertaining to cloud computing
US8854972B1 (en) 2013-01-25 2014-10-07 Palo Alto Networks, Inc. Security device implementing flow lookup scheme for improved performance
US9178799B2 (en) 2013-02-01 2015-11-03 TELEFONAKTIEBOLAGET L M ERRICSSON (publ) Method and system of shortest path bridging (SPB) enhanced resilience with loop mitigation
WO2014132136A2 (en) 2013-02-27 2014-09-04 Marvell World Trade Ltd. Efficient longest prefix matching techniques for network devices
CN104022960B (en) 2013-02-28 2017-05-31 新华三技术有限公司 Based on the method and apparatus of OpenFlow protocol PVLAN
US9197551B2 (en) 2013-03-15 2015-11-24 International Business Machines Corporation Heterogeneous overlay network translation for domain unification
WO2014169251A1 (en) 2013-04-12 2014-10-16 Huawei Technologies Co., Ltd. Service chain policy for distributed gateways in virtual overlay networks
EP2802103B1 (en) 2013-05-06 2018-04-18 Viavi Solutions Inc. Method and system for measuring packet loss
US9258243B2 (en) 2013-05-10 2016-02-09 Cisco Technology, Inc. Symmetric service chain binding
US9160666B2 (en) 2013-05-20 2015-10-13 Telefonaktiebolaget L M Ericsson (Publ) Encoding a payload hash in the DA-MAC to facilitate elastic chaining of packet processing elements
JP5769208B2 (en) 2013-05-21 2015-08-26 国立研究開発法人情報通信研究機構 Visualization system network configuration and operation
US9471356B2 (en) 2013-06-12 2016-10-18 Dell Products L.P. Systems and methods for providing VLAN-independent gateways in a network virtualization overlay implementation
US9749231B2 (en) 2013-07-02 2017-08-29 Arista Networks, Inc. Method and system for overlay routing with VXLAN on bare metal servers
US9374323B2 (en) 2013-07-08 2016-06-21 Futurewei Technologies, Inc. Communication between endpoints in different VXLAN networks
US20150016277A1 (en) 2013-07-10 2015-01-15 Dell Products L.P. Interconnect error notification system
US9426060B2 (en) 2013-08-07 2016-08-23 International Business Machines Corporation Software defined network (SDN) switch clusters having layer-3 distributed router functionality
US9824756B2 (en) 2013-08-13 2017-11-21 Globalfoundries Inc. Mapping a lookup table to prefabricated TCAMS
US9755960B2 (en) 2013-09-30 2017-09-05 Juniper Networks, Inc. Session-aware service chaining within computer networks
US20150113143A1 (en) 2013-10-18 2015-04-23 Hewlett-Packard Development Company, L.P Network resource automation management
US9674086B2 (en) 2013-11-05 2017-06-06 Cisco Technology, Inc. Work conserving schedular based on ranking
US9502111B2 (en) 2013-11-05 2016-11-22 Cisco Technology, Inc. Weighted equal cost multipath routing
US9825857B2 (en) 2013-11-05 2017-11-21 Cisco Technology, Inc. Method for increasing Layer-3 longest prefix match scale
US9246852B2 (en) 2013-11-05 2016-01-26 National Instruments Corporation Lossless time based data acquisition and control in a distributed system
US9832122B2 (en) 2013-11-05 2017-11-28 Cisco Technology, Inc. System and method for identification of large-data flows
US9635937B2 (en) 2013-11-05 2017-05-02 Cisco Technology, Inc. Rack mounting kit for telecommunications equipment and rack cross brace
US9655232B2 (en) 2013-11-05 2017-05-16 Cisco Technology, Inc. Spanning tree protocol (STP) optimization techniques
US20150127797A1 (en) 2013-11-05 2015-05-07 Cisco Technology, Inc. System and method for multi-path load balancing in network fabrics
US9769078B2 (en) 2013-11-05 2017-09-19 Cisco Technology, Inc. Dynamic flowlet prioritization
US9544185B1 (en) 2013-11-05 2017-01-10 Cisco Technology, Inc. Hardware based fast convergence for network failures
US9374294B1 (en) 2013-11-05 2016-06-21 Cisco Technology, Inc. On-demand learning in overlay networks
US9876711B2 (en) 2013-11-05 2018-01-23 Cisco Technology, Inc. Source address translation in overlay networks
US9888405B2 (en) 2013-11-05 2018-02-06 Cisco Technology, Inc. Networking apparatuses and packet statistic determination methods employing atomic counters
US20150124817A1 (en) 2013-11-05 2015-05-07 Cisco Technology, Inc. Ip-based forwarding of bridged and routed ip packets and unicast arp
US20150124824A1 (en) 2013-11-05 2015-05-07 Cisco Technology, Inc. Incast drop cause telemetry
US9876715B2 (en) 2013-11-05 2018-01-23 Cisco Technology, Inc. Network fabric overlay
US9590914B2 (en) 2013-11-05 2017-03-07 Cisco Technology, Inc. Randomized per-packet port channel load balancing
US9397946B1 (en) 2013-11-05 2016-07-19 Cisco Technology, Inc. Forwarding to clusters of service nodes
US9509092B2 (en) 2013-11-06 2016-11-29 Cisco Technology, Inc. System and apparatus for network device heat management
US9166887B2 (en) * 2013-12-26 2015-10-20 Telefonaktiebolaget L M Ericsson (Publ) Multicast convergence
US9389847B2 (en) 2014-06-28 2016-07-12 Vmware, Inc. Selection of relevant software bundles
US9223767B1 (en) 2014-06-28 2015-12-29 Vmware, Inc. Unified graphical user interface for displaying a plan of operations in a datacenter

Patent Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040160956A1 (en) * 2001-03-27 2004-08-19 Hardy William Geoffrey Network tunnelling
US20040249960A1 (en) * 2001-03-27 2004-12-09 Hardy William Geoffrey Access networks
US20060280179A1 (en) * 2001-04-25 2006-12-14 Meier Robert C Dhcp over mobile ip
US7152117B1 (en) * 2001-10-04 2006-12-19 Cisco Technology, Inc. Techniques for dynamic host configuration using overlapping network
US20040103310A1 (en) * 2002-11-27 2004-05-27 Sobel William E. Enforcement of compliance with network security policies
US20050013280A1 (en) * 2003-07-14 2005-01-20 Buddhikot Milind M. Method and system for mobility across heterogeneous address spaces
US20050175020A1 (en) * 2004-02-05 2005-08-11 Samsung Electronics Co., Ltd. Tunneling service method and system
US20060028285A1 (en) * 2004-07-26 2006-02-09 Samsung Electronics Co., Ltd. Method and apparatus for automatic tunnel configuration
US20060209688A1 (en) * 2005-03-02 2006-09-21 Hitachi Communication Technologies, Ltd. Packet forwarding apparatus
US20080092213A1 (en) * 2005-04-29 2008-04-17 Huawei Technologies Co., Ltd. Method, system and server for realizing secure assignment of dhcp address
US20060250982A1 (en) * 2005-05-05 2006-11-09 Harrow Products Llc Methods and systems for discovering and configuring network devices
US20070280264A1 (en) * 2006-05-30 2007-12-06 Motorola, Inc. Method and system for intertechnology handoff of a hybrid access terminal
US20080147830A1 (en) * 2006-12-14 2008-06-19 Ridgill Stephen P Selective sub-net filtering in a pre-boot execution environment (pxe)
US20100223655A1 (en) * 2007-11-20 2010-09-02 Huawei Technologies Co., Ltd. Method, System, and Apparatus for DHCP Authentication
US20090193103A1 (en) * 2008-01-29 2009-07-30 Small Keith M Method of and System for Support of User Devices Roaming Between Routing Realms by a Single Network Server
US20100191839A1 (en) * 2009-01-28 2010-07-29 Juniper Networks, Inc. Synchronizing resource bindings within computer network
US20100191813A1 (en) * 2009-01-28 2010-07-29 Juniper Networks, Inc. Automatically releasing resources reserved for subscriber devices within a broadband access network
US20100312875A1 (en) * 2009-06-05 2010-12-09 Square D. Company Automated discovery of monitoring devices on a network
US20130311991A1 (en) * 2011-01-13 2013-11-21 Huawei Technologies Co., Ltd. Virtual machine migration method, switch, and virtual machine system
US20130097335A1 (en) * 2011-10-14 2013-04-18 Kanzhe Jiang System and methods for managing network protocol address assignment with a controller
US20130182712A1 (en) * 2012-01-13 2013-07-18 Dan Aguayo System and method for managing site-to-site vpns of a cloud managed network
US20130250951A1 (en) * 2012-03-22 2013-09-26 Brocade Communications Systems, Inc. Overlay tunnel in a fabric switch
US20130311663A1 (en) * 2012-05-15 2013-11-21 International Business Machines Corporation Overlay tunnel information exchange protocol
US20130322453A1 (en) * 2012-06-04 2013-12-05 David Ian Allan Routing vlan tagged packets to far end addresses of virtual forwarding instances using separate administrations
US20130322446A1 (en) * 2012-06-05 2013-12-05 International Business Machines Corporation Virtual ethernet port aggregation (vepa)-enabled multi-tenant overlay network
US20130332577A1 (en) * 2012-06-06 2013-12-12 Juniper Networks, Inc. Multitenant server for virtual networks within datacenter
US20140016501A1 (en) * 2012-07-16 2014-01-16 International Business Machines Corporation Flow based overlay network
US20140068750A1 (en) * 2012-08-30 2014-03-06 Tropos Networks, Inc. Establishing an ipsec (internet protocol security) vpn (virtual private network) tunnel
US20140146817A1 (en) * 2012-11-29 2014-05-29 Futurewei Technologies, Inc. System and Method for VXLAN Intern-Domain Communications
US20140269712A1 (en) * 2013-03-14 2014-09-18 International Business Machines Corporation Tagging virtual overlay packets in a virtual networking system
US20140321277A1 (en) * 2013-04-30 2014-10-30 Comcast Cable Communications, Llc Network Validation
US20150092593A1 (en) * 2013-09-30 2015-04-02 Juniper Networks, Inc. Methods and apparatus for implementing connectivity between edge devices via a switch fabric

Cited By (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150058470A1 (en) * 2013-08-20 2015-02-26 Arista Networks, Inc. System and method for sharing vxlan table information with a network controller
US9621508B2 (en) * 2013-08-20 2017-04-11 Arista Networks, Inc. System and method for sharing VXLAN table information with a network controller
US10079761B2 (en) 2013-11-05 2018-09-18 Cisco Technology, Inc. Hierarchical routing with table management across hardware modules
US10182496B2 (en) 2013-11-05 2019-01-15 Cisco Technology, Inc. Spanning tree protocol optimization
US9444634B2 (en) * 2013-11-05 2016-09-13 Cisco Technology, Inc. Miscabling detection protocol
US10164782B2 (en) 2013-11-05 2018-12-25 Cisco Technology, Inc. Method and system for constructing a loop free multicast tree in a data-center fabric
US10148586B2 (en) 2013-11-05 2018-12-04 Cisco Technology, Inc. Work conserving scheduler based on ranking
US10187302B2 (en) 2013-11-05 2019-01-22 Cisco Technology, Inc. Source address translation in overlay networks
US10020989B2 (en) 2013-11-05 2018-07-10 Cisco Technology, Inc. Provisioning services in legacy mode in a data center network
US20150124643A1 (en) * 2013-11-05 2015-05-07 Cisco Technology, Inc. Miscabling detection protocol
US9634846B2 (en) 2013-11-05 2017-04-25 Cisco Technology, Inc. Running link state routing protocol in CLOS networks
US9654300B2 (en) 2013-11-05 2017-05-16 Cisco Technology, Inc. N-way virtual port channels using dynamic addressing and modified routing
US9667431B2 (en) 2013-11-05 2017-05-30 Cisco Technology, Inc. Method and system for constructing a loop free multicast tree in a data-center fabric
US9698994B2 (en) 2013-11-05 2017-07-04 Cisco Technology, Inc. Loop detection and repair in a multicast tree
US9985794B2 (en) 2013-11-05 2018-05-29 Cisco Technology, Inc. Traceroute in a dense VXLAN network
US10225179B2 (en) 2013-11-05 2019-03-05 Cisco Technology, Inc. Virtual port channel bounce in overlay network
US9996653B1 (en) 2013-11-06 2018-06-12 Cisco Technology, Inc. Techniques for optimizing dual track routing
US20160065461A1 (en) * 2013-12-10 2016-03-03 Fujitsu Limited Risk mitigation in data center networks using virtual machine sharing
US9503367B2 (en) * 2013-12-10 2016-11-22 Fujitsu Limited Risk mitigation in data center networks using virtual machine sharing
US10178133B2 (en) 2014-07-30 2019-01-08 Tempered Networks, Inc. Performing actions via devices that establish a secure, private network
US10116493B2 (en) 2014-11-21 2018-10-30 Cisco Technology, Inc. Recovering from virtual port channel peer failure
US9887961B2 (en) * 2015-05-22 2018-02-06 International Business Machines Corporation Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
WO2016188375A1 (en) * 2015-05-22 2016-12-01 International Business Machines Corporation Multi-tenant aware dynamic host configuration protocol (dhcp) mechanism for cloud networking
US20160344687A1 (en) * 2015-05-22 2016-11-24 International Business Machines Corporation Multi-tenant aware dynamic host configuration protocol (dhcp) mechanism for cloud networking
GB2555740A (en) * 2015-05-22 2018-05-09 Ibm Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US9973467B2 (en) * 2015-07-24 2018-05-15 Aruba Networks, Inc. Auto provisioning of bulk access points
US20170026234A1 (en) * 2015-07-24 2017-01-26 Aruba Networks, Inc. Auto provisioning of bulk access points
US10142163B2 (en) 2016-03-07 2018-11-27 Cisco Technology, Inc BFD over VxLAN on vPC uplinks
CN105763671A (en) * 2016-04-27 2016-07-13 杭州华三通信技术有限公司 IP address distribution method and apparatus
US10193750B2 (en) 2016-09-07 2019-01-29 Cisco Technology, Inc. Managing virtual port channel switch peers from software-defined network controller
US10171344B1 (en) * 2017-02-02 2019-01-01 Cisco Technology, Inc. Isolation of endpoints within an endpoint group
US10069726B1 (en) * 2018-03-16 2018-09-04 Tempered Networks, Inc. Overlay network identity-based relay
US10200281B1 (en) 2018-03-16 2019-02-05 Tempered Networks, Inc. Overlay network identity-based relay
US10116539B1 (en) 2018-05-23 2018-10-30 Tempered Networks, Inc. Multi-link network gateway with monitoring and dynamic failover
US10158545B1 (en) 2018-05-31 2018-12-18 Tempered Networks, Inc. Monitoring overlay networks

Also Published As

Publication number Publication date
US20150124642A1 (en) 2015-05-07
US20150124654A1 (en) 2015-05-07
US9654300B2 (en) 2017-05-16
US10164782B2 (en) 2018-12-25
US9698994B2 (en) 2017-07-04
US20170237651A1 (en) 2017-08-17
US20150124643A1 (en) 2015-05-07
US9985794B2 (en) 2018-05-29
US20150124587A1 (en) 2015-05-07
US20150124586A1 (en) 2015-05-07
US20150124644A1 (en) 2015-05-07
US9667431B2 (en) 2017-05-30
US9374294B1 (en) 2016-06-21
US9634846B2 (en) 2017-04-25
US9444634B2 (en) 2016-09-13
US20150124629A1 (en) 2015-05-07

Similar Documents

Publication Publication Date Title
US8392608B1 (en) Using virtual networking devices to manage network configuration
EP2648370B1 (en) Location-Aware Virtual Service Provisioning in a Hybrid Cloud Environment
US8619779B2 (en) Scalable architecture for enterprise extension in a cloud topology
US9698995B2 (en) Systems and methods for providing multicast routing in an overlay network
US8755377B2 (en) Facilitating operation of one or more virtual networks
US10225179B2 (en) Virtual port channel bounce in overlay network
EP2719124B1 (en) A scalable multi-tenant network architecture for virtualized datacenters
US8830834B2 (en) Overlay-based packet steering
US9276811B1 (en) Providing virtual networking functionality for managed computer networks
US9374316B2 (en) Interoperability for distributed overlay virtual environment
US8953441B2 (en) Re-routing network traffic after link failure
US9203784B2 (en) Distributed virtual switch architecture for a hybrid cloud
US9042384B2 (en) Distributed routing domains in multi-tenant datacenter virtual networks
US8750288B2 (en) Physical path determination for virtual network packet flows
US20140105216A1 (en) Network devices with feature peer network logic
US9794084B2 (en) Method and apparatus for implementing a flexible virtual local area network
US9407540B2 (en) Distributed service chaining in a network environment
US8824485B2 (en) Efficient software-based private VLAN solution for distributed virtual switches
US9912612B2 (en) Extended ethernet fabric switches
US20150063353A1 (en) Implementation of virtual extensible local area network (vxlan) in top-of-rack switches in a network environment
US9037691B1 (en) Managing use of intermediate destination computing nodes for provided computer networks
US9225636B2 (en) Method and apparatus for exchanging IP packets among network layer 2 peers
JP5763081B2 (en) Method and apparatus for transparent cloud computing using virtual network infrastructure
CN104350467B (en) Cloud security of the elastic layer implementation using sdn
KR101912073B1 (en) Virtualization gateway between virtualized and non-virtualized networks

Legal Events

Date Code Title Description
AS Assignment

Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PANI, AYASKANT;THYAMAGUNDALU, SANJAY;SIGNING DATES FROM 20140903 TO 20140911;REEL/FRAME:033725/0531

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION