WO2015199724A1 - Découverte de liaisons dans les réseaux sdn au moyen d'un contrôleur, et dispositifs de réseau commandés par ce contrôleur - Google Patents

Découverte de liaisons dans les réseaux sdn au moyen d'un contrôleur, et dispositifs de réseau commandés par ce contrôleur Download PDF

Info

Publication number
WO2015199724A1
WO2015199724A1 PCT/US2014/044599 US2014044599W WO2015199724A1 WO 2015199724 A1 WO2015199724 A1 WO 2015199724A1 US 2014044599 W US2014044599 W US 2014044599W WO 2015199724 A1 WO2015199724 A1 WO 2015199724A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
controller
link
network device
discovery
Prior art date
Application number
PCT/US2014/044599
Other languages
English (en)
Inventor
Ryan K. TIDWELL
Shaun Wackerly
Manfred R. Arndt
Original Assignee
Hewlett-Packard Development Company, L.P.
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
Application filed by Hewlett-Packard Development Company, L.P. filed Critical Hewlett-Packard Development Company, L.P.
Priority to PCT/US2014/044599 priority Critical patent/WO2015199724A1/fr
Publication of WO2015199724A1 publication Critical patent/WO2015199724A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV

Definitions

  • Software-defined networking is an approach to computer networking in which control decisions for routing traffic through the network can be decoupled from the network's physical infrastructure.
  • Network devices in software-defined networks can communicate with a network controller to assist in determining the logical topology of the network.
  • FIG. 1 is a diagram of a software-defined network including a network controller to allow link discovery in the network, according to an example.
  • FIG. 2 is a computing system including discovery instructions to allow link discovery in the network of FIG. 1, according to an example.
  • FIG. 3 is a computing system including a discovery module to allow link discovery in the network of FIG. 1, according to an example.
  • FIG. 4 is a flowchart of an improved method for link discovery in a software-defined network, according to an example.
  • FIG. 5 is a flowchart of an improved method for link discovery in a software-defined network, according to another example.
  • FIG. 6 is a flowchart of an improved method for link discovery in a software-defined network, according to another example.
  • FIG. 7 is a flowchart of an improved method for link discovery in a software-defined network, according to another example.
  • a network controller in a software-defined network can initiate a link discovery process to identify how network devices communicate to pass data throughout the network.
  • This link discovery process can, for example, be used to create an overall logical topology of the network, which may be useful for troubleshooting connectivity issues and for the design and maintenance of the network.
  • link discovery techniques currently exist, these techniques can be improved to more efficiently poll network devices for link information.
  • link discovery can be performed on networks including a combination of controlled and uncontrolled network devices (herein referred to as a
  • heterogeneous network Mapping a heterogeneous network can be challenging because in some situations, a network administrator may receive only limited connectivity information regarding the uncontrolled network devices. In such situations, the network controller may attempt to determine the topology of a network using indirect methods that are inefficient and can overload certain network devices.
  • One technique to improve the efficiency of the link discovery process in a software- defined network includes instructing controlled network devices to send a multicast link discovery advertisement with information that causes any client devices that receives the advertisement to disregard the advertisement.
  • This can allow client devices with small processors such as certain Wireless Fidelity (Wi-Fi) access points or Internet Protocol (IP) phones to avoid being confused or overwhelmed by such discovery requests.
  • Wi-Fi Wireless Fidelity
  • IP Internet Protocol
  • FIG. 1 illustrates an example of a network 100 including a network controller 102 connected to multiple network devices 104, 106, 108, 110, 112, 114, 116, 118, 120, 122, 124, and 126 via various wired or wireless data links.
  • Network 100 can be implemented as a software-defined network (SDN) in which network controller 102 interfaces with the various network devices via a suitable Application Program Interface ("API"), or another suitable protocol (e.g., Open Flow and/or simple network management protocol (SNMP)).
  • API Application Program Interface
  • Controller 102 may interface with the network devices via an interface channel that connects each controlled device to controller 102 to allow controller 102 to configure and manage the device, receive events from the device, and send packets using the device.
  • API Application Program Interface
  • SNMP simple network management protocol
  • Controller 102 can, for example, be Implemented In part using a software program on a computing system connected to network 100.
  • a software program on a computing system connected to network 100.
  • An example of such a computing system is described for example with respect to FIG. 2.
  • controller 102 can be implemented on a standalone network device in network 100.
  • controller 102 can be implemented on another network device in network 100, such as a network host or switch.
  • the network host or switch such as a network host or switch.
  • controller 102 functionality of controller 102 may be split among multiple controllers or other devices.
  • the various network devices are in the form of data communication equipment (network switches for devices 106, 108, 110, 112, 114, 120, 122) and client devices (personal computers for devices 118 and 126 and printers for devices 116 and 124). It is appreciated however, that the improved systems, methods, and mediums described herein can be used or adapted for networks including more or fewer devices, different types of devices, and different network arrangements. For example, in some implementations, other data communication equipment (such as suitable modems, hubs, and bridges) and other client devices (such as suitable Wi-Fi access points or IP phones) can be included.
  • data communication equipment such as suitable modems, hubs, and bridges
  • client devices such as suitable Wi-Fi access points or IP phones
  • network 100 includes a combination of "controlled” network devices (e.g., controlled network devices 106, 108, 114, 120, and 122) and
  • uncontrolled network devices e.g., uncontrolled network devices 110 and 112
  • controlled is intended to include devices within the control domain of network controller 102
  • uncontrolled is intended to refer to devices that are not within the control domain of network controller 102.
  • network 100 is described and illustrated as including only one
  • the improved systems, methods, and mediums described herein can be implemented in networks with multiple controllers.
  • network devices are in communication with multiple controllers such that control of the network can be smoothly handed over to a second controller if a first controller fails.
  • multiple controllers can work together to concurrently control a network.
  • a first controller can, for example, control certain network devices while a second controller can control other network devices.
  • reference in this application to a single controller that controls the operation of a network is intended to include such multiple controller configurations and other suitable multiple controller configurations.
  • network controller 102 includes improved discovery
  • FIG. 2 illustrates an example of a computing system 130 connected to network
  • computing system 130 can be used to perform link discovery of network 100 and, as depicted in FIG. 2, can include a processor 132, memory 134, input/output (I/O) devices 136, and a communication interface 138.
  • Computing system 130 can be in the form of a suitable server, desktop computer, laptop, tablet, or the like.
  • software that provides the functionality of controller 102 can be stored on memory 134 of computing system 130 to be executed by processor 132 of computing system 130.
  • computing system 130 can be a standalone personal computer that is connected to controller 102 so as to receive information from network controller 102 for network discovery.
  • computing system 130 can receive information from network controller 102 through indirect means.
  • computing system 130 may receive information from network controller 102 by Inserting a removable data storage device into computing system 130.
  • the removable data storage device can, for example, be in the form of a USB thumb drive or a storage disc containing information from network controller 102.
  • Processor 132 of computing system 130 can, for example, be In the form of a central processing unit (CPU), a semiconductor-based microprocessor, a digital signal processor (DSP) such as a digital image processing unit, other hardware devices or processing elements suitable to retrieve and execute instructions stored in memory 134, or suitable combinations thereof.
  • processor 132 can, for example, include single or multiple cores on a chip, multiple cores across multiple chips, multiple cores across multiple devices, or suitable combinations thereof.
  • Processor 132 can be functional to fetch, decode, and execute instructions as described herein.
  • processor 132 may include at least one integrated circuit (IC), other control logic, other electronic circuits, or suitable combination thereof that include a number of electronic components for performing the functionality of instructions stored on memory 134.
  • IC integrated circuit
  • Processor 132 may be implemented across multiple processing units and instructions may be implemented by different processing units In different areas of computing system 130.
  • Memory 134 of computing system 130 can, for example, be in the form of a non- transitory machine-readable storage medium, such as a suitable electronic, magnetic, optical, or other physical storage apparatus to contain or store
  • Memory 134 can, for example, be housed within the same housing as processor 132 for computing system 130, such as within a computing tower case for computing system 130. In some implementations, memory 134 and processor 132 are housed in different housings.
  • the term "machine-readable storage medium” may include Random Access Memory (RAM), flash memory, a storage drive (e.g., a hard disk), any type of storage disc (e.g., a Compact Disc Read Only Memory (CD-ROM), any other type of compact disc, a DVD, etc.), and the like, or a combination thereof.
  • memory 134 can include a main memory, such as a Random Access Memory (RAM), where software may reside during runtime, and a secondary memory.
  • the secondary memory can, for example, include a nonvolatile memory where a copy of software is stored.
  • memory 134 stores topological link data 140, discovery Instructions 128, mapping instructions 142, and display instructions 144. As described above, memory 134 can for example store other instructions relating to the functionality of a software-defined network controller 102.
  • Topological link data 140 can, for example, indicate: (1) which controlled network devices In the network are linked together, (2) whether the links between controlled network devices are single-hop or multi-hop, and (3) whether the links between controlled network devices are bi-directional or uni-directional.
  • Topological link data 140 can, for example, include information regarding which port of a controlled network device is used for communicating with an uncontrolled network device.
  • Topological link data 140 can, for example, include discovery protocol data that provides link information relating to uncontrolled network devices that are directly connected to controlled network devices. It is appreciated that topological link data 140 can include other information to assist in mapping network 100.
  • topological link data 140 can include media access control (MAC) address information for an uncontrolled network device linked to a controlled network device.
  • MAC media access control
  • the topological link data can include data in the form of another addressing scheme, such as Internet Protocol (IP) address or Address Resolution Protocol (ARP), for associating an address and a port used for that address.
  • IP Internet Protocol
  • ARP Address Resolution Protocol
  • Discovery instructions 128 can be executable by processor 132 such that computing system 130 is operative to perform link discovery of connected devices in a software- defined network. Various implementations of such discovery instructions 128 will be discussed below with respect to the flow charts of FIGs. 4-7.
  • mapping instructions 142 can be executable by processor 132 such that computing system 130 is operative to logically map the links discovered during the discovery process or otherwise known to controller 102.
  • mapping instructions 142 can be used to turn information regarding the various links between network devices, which can, for example be stored In the form of one or more tables as topological link data 140, into a logical topology map for displaying to a network administrator or other user.
  • mapping instructions 142 create a map to be displayed in the form of a graphical user interface (GUI) displayed on a screen of a computing device, such as a computer monitor.
  • GUI graphical user interface
  • mapping instructions 142 create a map to be printed onto a sheet of paper or other physical media.
  • mapping instructions 142 can provide varying degrees of information regarding elements of a network, such as icons depicting the makes and models of controlled network devices, symbols representing the type of link between devices (e.g., wired, wireless, etc.), descriptions for various elements, and the like.
  • Display instructions 144 can be executable by processor 132 such that computing system 130 is operative to display topological information of network 100, such as a topology map created by mapping instructions 142. Display instructions 144 can be used to display network information in other forms, such as for example a table that includes information regarding connected devices. In some implementations, display instructions 144 can be executable by processor 132 such that computing system 130 (i.e., a first system) is operative to provide mapping instructions 142 or related information to a "second" system so as display topology information created by computing system 130 on the second system.
  • the logical topology map can be returned to a caller in a storage format without being converted into a GUI.
  • the logical topology map can be in the form of a logical representation that provides structure mappings in which certain structures correspond to switches or other network devices. Such an implementation can, for example, be used where a machine displaying a GUI for the map is a separate machine from the controller that maps the network.
  • Computing system 130 can also include one or more I/O devices 136 to allow
  • I/O devices 136 can be connected to elements of computing system 130 via wired or wireless links.
  • Computing system 130 can also Include a communication Interface 138 to allow
  • Communication interface 138 can be implemented for use as a wired or wireless communication interface.
  • communication interface 138 contains one or more physical data ports to connect to network 100.
  • communication interface 138 can be in the form of a network interface controller having an Ethernet port.
  • network device 106 is implemented as a network switch containing multiple ports 146, 148, 150, and 152 and a switch chassis 154.
  • the ports and switch chassis 154 work together to allow device 106 to forward network traffic to another network device connected to device 106.
  • the ports can be used for receiving and sending data in network 100. It is appreciated that the ports can include wired connections to other network devices in network 100 and can, in some implementations, be in the form of virtual ports.
  • Switch chassis 154 of network device 106 can include a processor 158 and a memory 160 that operate together to allow device 106 to extract a set of fields from a received data packet execute flow routing instructions.
  • Processor 158 and memory 160 of device 106 can include one or more aspects of processor 132 and memory 134 described above with respect to computing system 130.
  • FIG. 3 illustrates computing system 130 in the form of functional modules.
  • computing system 130 includes a data storage module 162, a discovery module 164, a mapping module 166, a display module 168, and a communication module 170.
  • module refers to a combination of hardware (e.g., a processor such as an integrated circuit or other circuitry) and software (e.g., machine- or processor-executable instructions, commands, or code such as firmware, programming, or object code).
  • a combination of hardware and software can include hardware only (i.e., a hardware element with no software elements), software hosted at hardware (e.g., software that is stored at a memory and executed or interpreted at a processor), or at hardware and software hosted at hardware.
  • the singular forms "a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise.
  • the term “module” is intended to mean one or more modules or a combination of modules.
  • Data storage module 162 is a functional module of computing system 130 that
  • data storage module 162 includes hardware in the form of a hard drive, related firmware, and other software for allowing the hard drive to operatively
  • Data storage module 162 can include information that is stored within data storage module 162, such as topological link data 140 described above with respect to FIG. 2.
  • Discovery module 164 is a functional module of computing system 130 that includes a combination of hardware and software that allows computing system 130 to perform link discovery of controlled devices in a network.
  • discovery module 164 includes hardware in the form of a microprocessor on a single integrated circuit, related firmware, and other software for allowing the
  • Discovery module 164 can include Instructions used by computing system 130 to perform link discovery, such as discovery instructions 128 described above with respect to FIG. 1.
  • Mapping module 166 is a functional module of computing system 130 that includes a combination of hardware and software that allows computing system 130 to logically map the links discovered during the discovery process or otherwise known to controller 102.
  • mapping module 166 includes hardware in the form of a microprocessor on a single integrated circuit, related firmware, and other software for allowing the microprocessor to operatively communicate with other hardware of computing system 130.
  • Mapping module 166 can include instructions used by computing system 130 to map links, such as mapping instructions 142 described above with respect to FIG. 2.
  • Display module 168 is a functional module of computing system 130 that Includes a combination of hardware and software that allows computing system 130 to display topological information of network 100, such as a topology map created by mapping instructions 142 in FIG.
  • display module 168 includes hardware in the form of a computer monitor, related firmware, and other software for allowing the computer monitor to operatively communicate with other hardware of computing system 130. It is appreciated that in some embodiments, display module 168 can include hardware In the form of a display port and/or video card. Display module 168 can include instructions used by computing system 130 to display topological information of network of a network. Such instructions can include, for example, display instructions 144 described above with respect to FIG. 2. In some implementations, display module 168 can additionally or alternatively include hardware in the form of a computer printer or printer port, related firmware, and other software for allowing a printer to operatively communicate with other hardware of computing system 130.
  • Communication module 170 is a functional module of computing system 130 that includes a combination of hardware and software to allow computing system 130 to communicate with network 100.
  • communication module 170 includes hardware in the form of a network interface controller, related firmware, and other software for allowing the network interface controller to operatively communicate with other hardware of computing system 130 or devices on network 100.
  • FIGs. 4-7 illustrate examples of methods 172, 174, 176, and 178 that can, for
  • FIGs. 4-7 show a specific order of performance of functionalities of their methods, this order may be rearranged into another suitable order, may be executed concurrently or with partial concurrence, or a combination thereof. Likewise, suitable additional and/or comparable steps may be added to the methods to achieve the same or comparable functionality.
  • FIG. 4 is directed to a first method 172 to efficiently perform link discovery
  • Method 172 includes a step 180 of instructing a network device (e.g., network device 120) in a control domain of network controller 102 to send a multicast link discovery advertisement to a set of network devices that includes a client device (e.g., devices 116, 118, 124, 126).
  • This advertisement includes information that causes the client devices to disregard the advertisement.
  • this information can include forwarding criteria that excludes client devices as a class.
  • the link discovery can include an IP multicast address that excludes client devices, such as a multicast addresses assigned to switches, routers, or other network infrastructure devices.
  • a multicast packet sent to address 224.0.0.2 would be ignored by network devices that are not routers.
  • the multicast address can, for example, operate at both Layer 2 and Layer 3 levels.
  • a multicast packet can include a special multicast MAC address per the Ethernet specification as the destination MAC address to allow client devices in network 100 to ignore the advertisement.
  • Other suitable multicast addresses can be used in order to allow client devices in network 100 to ignore the advertisement.
  • Instructions 180 to send multicast link discovery advertisements can be provided by sending packets from controller 102 through datapaths of network 100.
  • Controller 102 can send a packet out through a datapath using a suitable packet-out command for a given software-defined networking protocol.
  • Packets can, for example, be in the form of an Ethernet frame including a header and payload.
  • Such packets can, for example, include type-length-value (TLV) elements that identify the network device, the network controller that controls the network device, a port used to connect to the network device, and a time-to-live value.
  • the Ethernet frame can, for example, include a datapath identification field that uniquely identifies a datapath. A lower 48 bits of the datapath identification field can be reserved for the device's MAC address, while a top 16 bits of the field can be In the form of a Virtual LAN (VLAN) identifier to distinguish multiple virtual switch instances on a single physical switch.
  • VLAN Virtual LAN
  • Method 172 further Includes a step 182 of receiving, from network devices in the control domain of controller 102, topological link data 140 for the network devices based on the advertisement.
  • Step 182 can, for example, be in response to controller 102 querying network devices in the control domain of network 100 to send controller 102 topological link data 140.
  • Topological link data 140 can be provided to controller 102 via a packet-in message event sent from a controlled network device.
  • Method 172 further includes a step 184 of determining a topology of network 100 based on the received topological link data 140. Step 184 can be Implemented via mapping instructions 142 described above with respect to FIG. 2.
  • method 172 can include an additional step of instructing network devices in the control domain of controller 102 to send neighbor link discovery advertisements.
  • method 172 can include an additional step of receiving, from network devices in the control domain of the controller, topological link data 140 based on both the multicast link discovery advertisements and the neighbor link discovery advertisements.
  • a neighbor link discovery advertisement can be a Link Layer Discovery Protocol (LLDP) packet, which each controlled network device can be instructed to flood through all of its ports.
  • LLDP Link Layer Discovery Protocol
  • method 172 allows the client devices to disregard the multicast link discovery advertisement from the network devices, method 172 can allow certain client devices with small processors, such as certain Wireless Fidelity (Wi-Fi) access points or Internet Protocol (IP) phones, to avoid being confused or overwhelmed by such requests.
  • Wi-Fi Wireless Fidelity
  • IP Internet Protocol
  • FIG. 5 is directed to a second method 174 to efficiently perform link discovery in network 100.
  • Method 174 includes a step 186 of instructing a first controlled network device (e.g., device 106) in a multi-hop link with a second controlled device (e.g., device 108) that contains an uncontrolled network devices (e.g., devices 110 and 112) to verify the connectivity of the multi-hop link.
  • a first controlled network device e.g., device 106
  • a second controlled device e.g., device 108
  • an uncontrolled network devices e.g., devices 110 and 112
  • controller 102 can assume that an uncontrolled network device exists if there are no other controlled network devices between the controlled network devices along the multi-hop link.
  • the instructions to verify the connectivity of the multi-hop link can be provided by sending a packet from controller 102 through a datapath of the network, with the packet containing instructions to verify the link.
  • the multi-hop link can, for example, be verified by instructing controlled network devices at both ends of the link to emit a broadcast (or multicast) discovery packet and to emit a link-local discovery packet.
  • Method 174 can further include a step 188 of instructing the first network device and the second network device to remove the multi-hop link when the connectivity of the multi-hop link is not verified within a predetermined amount of time.
  • removing the multi-hop link can include removing flow entries associated with the multi-hop link.
  • controller 102 can send the first and second network devices instructions to remove flow entries from flow tables by sending a delete flow table modification message.
  • controller 102 will remove the link from its own stored topological link data 140.
  • method 174 can include a step of instructing the second controlled network device to verify the connectivity of the multi-hop link and instructing the first network device and the second network device to remove the multi-hop link when the connectivity of the multi-hop link Is not verified by both the first and second controlled devices within the predetermined amount of time.
  • This technique can be advantageous compared to periodically polling all links as multi-hop links are often a small minority of links in a network. Moreover, in some situations controller 102 may be unaware of a break in a link between multiple unconnected devices (e.g., between device 110 and 112) in a multi-hop link.
  • code for discovery instructions 128 in accordance with method 174 is provided below:
  • FIG. 6 is directed to a third method 176 to efficiently perform link discovery in
  • Method 176 includes a step 190 of determining which ports of a network device (e.g., device 108) in a software-defined network are logically blocked by another network protocol.
  • controller 102 can receive port status information from a network device through the use of a "port -status" message that informs controller 102 of a change on a port of the network device, such as the port being logically blocked.
  • Method 176 further includes a step 192 of instructing the network device to only perform link discovery on ports that are not logically blocked.
  • the instructions to perform link discovery can, for example, include instructions for the network device to send neighbor link discovery advertisements through Its ports.
  • the instructions to perform link discovery can, for example, include instructions for the network device to send neighbor link discovery advertisements, which can, for example be flooded through each port of the network device.
  • the instructions to perform link discovery can, for example, include instructions for the network device to send multicast link discovery advertisements, which can, for example, be used for more complete link discovery of networks containing uncontrolled network devices.
  • This technique can, for example, make link discovery compatible with traditional networking protocols, such as spanning-tree.
  • the ports can be logically blocked by a spanning-tree protocol, but not physically down.
  • the link between device 108 and device 118 can be logically blocked by a spanning-tree protocol as device 108 is otherwise able to communicate with device 118 via device 120.
  • the technique can further prevent link discovery from introducing loopable packets (e.g., broadcast/multicast) into the controlled network.
  • Method 176 can further include a step of determining, before instructing the
  • controller 102 can be instructed to not proceed with determining whether any of its controlled network devices include logically blocked ports.
  • code for discovery instructions 128 in accordance with method 176 is provided below:
  • FIG. 7 is directed to a fourth method 178 to efficiently perform link discovery in
  • Method 178 includes a step 194 of receiving with controller 102 information indicating that a network device (e.g., device 108) has been connected to controller 102.
  • controller 102 can receive port status information from a network device through the use of a "port-status" message that informs controller 102 of a change on a port of the network device, such as a new device being connected to controller 102.
  • the status of a newly connected device can be provided to controller 102 in different ways, such as through a "Hello", “Features Reply", or "Packet in” message from the newly connected device or through other methods.
  • Method 178 further includes a step 196 of instructing network device 108 to
  • the predetermined window of time can be an actual amount of time (e.g., measured in seconds) that is expected to allow other network devices (e.g., devices 120 and 122) to be connected In series with network device 108.
  • the predetermined window of time can, for example, be configurable by the administrator based on network topology, network conditions, or other factors.
  • method 178 can also instruct other controlled network devices (e.g., network devices 106, 114, 120, and 122) to perform link discovery after the predetermined window of time.
  • the predetermined window of time can, for example, be determined by the
  • controller 102 based on an expected number of devices to be connected to the controller 102. For example, if three devices are expected to be connected in series, controller 102 can provide for an increased predetermined window of time than if only one two devices were expected to be connected in series. In some
  • controller 102 can instruct the network device to perform link discovery after the expected number of devices are connected rather than first waiting for the predetermined window of time to elapse.
  • controller 102 waits the predetermined window of time before instructing network device 108 to perform link discovery, whereas in other implementations, network device 108 is Instructed to wait the predetermined window of time before performing link discovery. In some implementations, the controller waits a predetermined window of time before providing instructions to network device 108 and the instructions to network device 108 also instruct network device 108 to wait a predetermined window of time before performing link discovery. In some implementations, the controller is programmed or otherwise configured to wait a predetermined window of time from the time the first discovered device is discovered before initiating link discovery. However, in some implementations, the controller can be programmed or otherwise configured to wait a predetermined window of time from the time a last device is discovered before initiating link discovery. For example, the predetermined window of time can be reset when a new device Is discovered.
  • data storage module 162 of computing system 130 can include aspects of discovery module 164 and vice versa.
  • the term “provide” Includes push mechanisms (e.g., sending data independent of a request for that data), pull mechanisms (e.g., delivering data in response to a request for that data), and store mechanisms (e.g., storing data at an intermediary at which the data can be accessed).
  • the term “based on” means “based at least in part on.” Thus, a feature that is described based on some cause, can be based only on the cause, or based on that cause and on one or more other causes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne des systèmes, des procédés et des supports d'informations pour la découverte de liaisons dans les réseaux SDN contenant un contrôleur de réseau et une pluralité de dispositifs de réseau commandés qui sont commandés par ce contrôleur. Ledit contrôleur est couplé par le biais du réseau aux dispositifs de réseau commandés, de sorte qu'il peut commander les dispositifs de réseau commandés pour découvrir des liaisons dans le réseau SDN.
PCT/US2014/044599 2014-06-27 2014-06-27 Découverte de liaisons dans les réseaux sdn au moyen d'un contrôleur, et dispositifs de réseau commandés par ce contrôleur WO2015199724A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2014/044599 WO2015199724A1 (fr) 2014-06-27 2014-06-27 Découverte de liaisons dans les réseaux sdn au moyen d'un contrôleur, et dispositifs de réseau commandés par ce contrôleur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2014/044599 WO2015199724A1 (fr) 2014-06-27 2014-06-27 Découverte de liaisons dans les réseaux sdn au moyen d'un contrôleur, et dispositifs de réseau commandés par ce contrôleur

Publications (1)

Publication Number Publication Date
WO2015199724A1 true WO2015199724A1 (fr) 2015-12-30

Family

ID=54938634

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/044599 WO2015199724A1 (fr) 2014-06-27 2014-06-27 Découverte de liaisons dans les réseaux sdn au moyen d'un contrôleur, et dispositifs de réseau commandés par ce contrôleur

Country Status (1)

Country Link
WO (1) WO2015199724A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010019395A1 (fr) * 2008-08-15 2010-02-18 Raytheon Company Multidiffusion dans un réseau à l'aide d'informations de voisins
US20120166798A1 (en) * 2010-12-22 2012-06-28 Konica Minolta Systems Laboratory, Inc. Method and system for using neighbor discovery unspecified solicitation to obtain link local address
US20120182860A1 (en) * 2009-10-06 2012-07-19 Hang Liu Method and apparatus for hop-by-hop reliable multicast in wireless networks
US20120327933A1 (en) * 2011-06-21 2012-12-27 Cisco Technology, Inc. Adjacency Discovery Through Multicast and Single-Hop Messaging
WO2014041550A1 (fr) * 2012-09-11 2014-03-20 Hewlett-Packard Development Company, L.P. Découverte d'appartenances aux groupes multidiffusion ip dans des réseaux sdn

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010019395A1 (fr) * 2008-08-15 2010-02-18 Raytheon Company Multidiffusion dans un réseau à l'aide d'informations de voisins
US20120182860A1 (en) * 2009-10-06 2012-07-19 Hang Liu Method and apparatus for hop-by-hop reliable multicast in wireless networks
US20120166798A1 (en) * 2010-12-22 2012-06-28 Konica Minolta Systems Laboratory, Inc. Method and system for using neighbor discovery unspecified solicitation to obtain link local address
US20120327933A1 (en) * 2011-06-21 2012-12-27 Cisco Technology, Inc. Adjacency Discovery Through Multicast and Single-Hop Messaging
WO2014041550A1 (fr) * 2012-09-11 2014-03-20 Hewlett-Packard Development Company, L.P. Découverte d'appartenances aux groupes multidiffusion ip dans des réseaux sdn

Similar Documents

Publication Publication Date Title
US10999145B2 (en) Dynamic service device integration
EP3787241A1 (fr) Procédé et dispositif de génération de routage
JP5811253B2 (ja) ネットワークシステム、及びネットワーク管理方法
US10341185B2 (en) Dynamic service insertion
EP2665229B1 (fr) Système de réseau et procédé d'acheminement
CN107409066B (zh) 用于自动检测和配置服务器上行链路网络接口的系统和方法
CN106452857B (zh) 生成配置信息的方法和网络控制单元
US8645567B2 (en) Method and system for packet filtering for local host-management controller pass-through communication via network controller
CN107078974B (zh) 网络交换机、由网络交换机执行的方法以及存储器资源
US8219713B2 (en) Method and system for a network controller based pass-through communication mechanism between local host and management controller
US20150009828A1 (en) Network System, Switch and Method of Network Configuration
US10277464B2 (en) Client auto-configuration in a multi-switch link aggregation
US9008080B1 (en) Systems and methods for controlling switches to monitor network traffic
US9537766B2 (en) Packet switching without look-up table for ethernet switches
JP2012244621A (ja) ネットワークスイッチ及びサーバのｖｌａｎｉｄによる接続の発見方法及び装置
CN104272684A (zh) Fabric交换机中的动态服务插入
US9602393B2 (en) Unregistered multicast packet forwarding to multicast router ports
US20150334019A1 (en) Routing control method and non-transitory computer-readable recording medium storing routing control program
WO2015199724A1 (fr) Découverte de liaisons dans les réseaux sdn au moyen d'un contrôleur, et dispositifs de réseau commandés par ce contrôleur
US20140105064A1 (en) Method and apparatus for path indication
WO2011144042A2 (fr) Procédé et dispositif périphérique adaptés pour délivrer des informations de routage
US10218534B2 (en) Determination of a network cloud containing an uncontrolled network device based on link data of controlled network devices

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14895804

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14895804

Country of ref document: EP

Kind code of ref document: A1