WO2016137512A1 - Cloud network management - Google Patents

Cloud network management Download PDF

Info

Publication number
WO2016137512A1
WO2016137512A1 PCT/US2015/018137 US2015018137W WO2016137512A1 WO 2016137512 A1 WO2016137512 A1 WO 2016137512A1 US 2015018137 W US2015018137 W US 2015018137W WO 2016137512 A1 WO2016137512 A1 WO 2016137512A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
virtual machine
remote
radio
computing device
Prior art date
Application number
PCT/US2015/018137
Other languages
French (fr)
Inventor
Allan DELGADO CAMPOS
Marcelo Eduardo MAGALLON GHERARDELLI
Original Assignee
Hewlett Packard Enterprise Development Lp
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 Enterprise Development Lp filed Critical Hewlett Packard Enterprise Development Lp
Priority to PCT/US2015/018137 priority Critical patent/WO2016137512A1/en
Publication of WO2016137512A1 publication Critical patent/WO2016137512A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/28Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45595Network integration; Enabling network access in virtual machine instances
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors

Definitions

  • Cloud network management often involves administrators that configure devices (e.g., switches, access points, etc.) located on unreachable networks (i.e., administrator is off-premise). Such administrators should verify that configuration changes have the desired effect on network clients' connectivity. For example, an administrator may request that a user that is on-premise perform connectivity tests and report back with the results. In another example, a virtual private network (VPN) can be established by the administrator so that the connectivity tests can be performed over a secure channel to the unreachable network.
  • VPN virtual private network
  • FIG. 1 is a block diagram of an example networking device for cloud network management
  • FIG. 2 is a block diagram of an example system for cloud network management
  • FIG. 3 is a flowchart of an example method for execution by a networking device for cloud network management.
  • FIG. 4 is a flowchart of an example method for execution by a remote computing device for cloud network management.
  • cloud network management can involve an on- premise user to coordinate with an administrator or a VPN.
  • Cloud-managed network devices e.g., switches, access points, etc.
  • Cloud-managed network devices can establish full-duplex communication channels (i.e., Web Socket) to a cloud management device.
  • a communication channel is used as a tunnel for network traffic (i.e., packet captures (PCAPs)) that originate off-premise.
  • PCAPs packet captures
  • a virtual machine is created, where network traffic of this off-premise virtual machine can be redirected to the on-premise network using the communication channel.
  • a remote connection is established with a remote computing device, where the remote computing device is configured to execute a remote virtual machine.
  • a radio is switched to a client station mode.
  • a virtual machine network packet is received from the remote computing device, and the radio is used to inject the virtual machine network packet into a local network as local traffic for the remote virtual machine.
  • FIG. 1 is a block diagram of an example networking device 100 for cloud network management.
  • the example networking device 100 may be a switch, an access point, a wireless router, a repeater, a bridge, or any other electronic device suitable for cloud network management.
  • networking device 100 includes controller 1 10, interfaces 1 15, and machine-readable storage medium 120.
  • Controller 1 10 may be one or more central processing units (CPUs), microprocessors, and/or other hardware devices suitable for retrieval and execution of instructions stored in machine-readable storage medium 120. Controller 1 10 may fetch, decode, and execute instructions 122, 124, 126, 128 to enable cloud network management, as described below. As an alternative or in addition to retrieving and executing instructions, controller 1 10 may include one or more electronic circuits comprising a number of electronic components for performing the functionality of one or more of instructions 122, 124, 126, 128.
  • CPUs central processing units
  • controller 1 10 may include one or more electronic circuits comprising a number of electronic components for performing the functionality of one or more of instructions 122, 124, 126, 128.
  • Radio(s) 1 12 may include wireless interface(s) for communicating with other computing devices via radio frequencies. Radio(s) 1 12 can be configured to facilitate wireless networks that allow for wireless communication between computing devices. Radio(s) 1 12 may support an alternative operating mode such as client station mode. When a radio 1 12 is switched to client station mode, the networking device 100 can use the radio 1 12 to behave like a client and join wireless networks provided by other networking devices. In other examples where networking device 100 is a switch, radio(s) 1 12 are not included in the networking device 100.
  • Interfaces 1 15 may include a number of electronic components for communicating with end devices.
  • interfaces 1 15 may be wireless interfaces such as wireless local area network (WLAN) interfaces and/or physical interfaces such as Ethernet interfaces, Universal Serial Bus (USB) interfaces, external Serial Advanced Technology Attachment (eSATA) interfaces, or any other physical connection interface suitable for communication with end devices.
  • WLAN wireless local area network
  • USB Universal Serial Bus
  • eSATA external Serial Advanced Technology Attachment
  • interfaces 1 15 may be used to send and receive data to and from other computing devices.
  • Machine-readable storage medium 120 may be any electronic, magnetic, optical, or other physical storage device that stores executable instructions.
  • machine-readable storage medium 120 may be, for example, Random Access Memory (RAM), Content Addressable Memory (CAM), Ternary Content Addressable Memory (TCAM), an Electrically-Erasable Programmable Read-Only Memory (EEPROM), flash memory, a storage drive, an optical disc, and the like.
  • RAM Random Access Memory
  • CAM Content Addressable Memory
  • TCAM Ternary Content Addressable Memory
  • EEPROM Electrically-Erasable Programmable Read-Only Memory
  • flash memory a storage drive, an optical disc, and the like.
  • storage drive an optical disc, and the like.
  • machine-readable storage medium 120 may be encoded with executable instructions for enabling cloud network management.
  • Remote connection establishing instructions 122 establish a connection with a remote computing device such as a cloud management server.
  • the connection may be a full-duplex communication channel over the Internet, where the remote computing device is on a different local area network than networking device 100.
  • the communication channel may also involve other networking devices such as switches and/or routers.
  • Radio mode switching instructions 124 modify a mode of the radio 1 12 based on requests from the remote computing device. Specifically, if a virtualization request is received from the remote computing device, the mode of the radio 1 12 can be switched to client station mode, which allows the networking device 100 to connect to other wireless networks. In some cases, computing device 100 includes multiple radios 1 12 so that one radio can be switched to client station mode while the other radios continue to operate in a normal operating mode that continues to provide wireless network(s). Alternatively, if the networking device 100 is a switch, radio mode switching instructions 124 are not included in machine-readable storage medium 120.
  • VM packet receiving instructions 126 receive virtual machine packets from a virtual machine of the remote computing device.
  • the remote computing device initiates the virtual machine and uses the connection established above to send packets from the virtual machine.
  • Networking device 100 identifies the virtual machine packets as originating from the remote computing device and, accordingly, processes them as described below.
  • VM packet injecting instructions 128 use the radio 1 12 in client station mode to inject the virtual machine packets into a network of networking device 100.
  • the virtual machine packets from the off-premise virtual machine can be treated as if they originated from a computing device that is on- premise.
  • the remote computing device can request that the wireless networks accessible to the radio 1 12 be discovered, where one of the wireless networks can then be selected for joining by the virtual machine.
  • the virtual machine can then be configured to remotely join the network of networking device 100 using network association parameters (e.g., internet protocol address, subnet mask, gateways, etc.) obtained by the radio 1 12. Because the virtual machine packets are tunneled through the established connection, the virtual machine is able to join the wireless network even though remote computing device is off-premise.
  • networking device 100 is a switch with no radio, the virtual machine packets can be injected into the network using a port of the switch.
  • FIG. 2 is a block diagram of an example system 200 including a remote computing device 216 interacting with computing devices of an off-premise network 201 .
  • Network 201 includes switch 202, access points 204A, 204N, and client computing devices 212A, 212N.
  • the components of access points 204A, 204N may be similar to the corresponding components of networking device 100 described above with respect to FIG. 1 .
  • access point A 204A includes radios 206A, 206N and controller 208. Controller 208 can be associated with firmware that includes instructions similar to as discussed above with respect to FIG. 1 .
  • Each of the radios 206A, 206N is configured to provide wireless networks of network 201 .
  • the radios 206A, 206N can broadcast service set identifications (SSID's) that identify wireless networks that can be joined by client computing devices 212A, 212N.
  • SSID's service set identifications
  • the wireless networks can be secured with encryption for preventing access by unauthorized devices.
  • Each of the radios 206A, 206N can also be configured to operate in a client station mode.
  • a radio 206A, 206N can be used to join wireless networks as if the corresponding access point 204A, 204N was a client device.
  • radio A 206A can be switched to client station mode while radio N 206N continues to operate in an access point mode (i.e., providing access to wireless networks).
  • Access point N 204N does not show components in order to simply FIG. 2; however, access point N 204N can include similar components as described above with respect to access point A 204A.
  • Client computing devices 212A, 212N use access points 204A, 204N to access wireless networks of network 201 .
  • client computing device A 212A can use access point A 204A to discover and join a wireless network.
  • packets from client computing device A 212 can then be accepted by access point A 204A and routed through switch 202 to provide client computing device 212A with access to the Internet or other client computing devices 212N on network 201 .
  • Remote computing device 216 is an off-premise device for managing components of network 201 such as switch 202 and access points 204A, 204N. Remote computing device 216 may be configured to access and reconfigure components such as switch 202 and access points 204A, 204N over the Internet. Because remote computing device 216 is off-premise, it cannot normally verify the reconfiguration of the components.
  • Remote computing device 216 includes virtual machine(s) 218 that are configured to verify the reconfiguration of the components.
  • Remote computing device 216 can instantiate a virtual machine 218 and then use a connection with an access point 204A, 204N to tunnel virtual machine packets between the remote computing device 216 and network 201 .
  • the initial connection between remote computing device 216 and the access point 204A, 204N allow the virtual machine 218 to behave as if it was on-premise.
  • virtual machine 218 can access and join wireless networks provided by access points 204A, 204N to verify a reconfiguration of the components of network 201 .
  • remote computing device 216 may instantiate multiple virtual machines 218, where packets from each machine are tunneled through a different radio (e.g., radio A 206A, radio N 206N) of an access point (e.g., access point A 204A, access point N 204N).
  • radio A 206A, radio N 206N e.g., radio A 206A, radio N 206N
  • remote computing device 216 can use the virtual machines 218 to confirm that the reconfigured components of network 201 still allow for communication between different client devices.
  • FIG. 3 is a flowchart of an example method 300 for execution by a networking device 100 for cloud network management. Although execution of method 300 is described below with reference to networking device 100 of FIG. 1 , other suitable devices for execution of method 300 may be used such as access point 204A, 204N of FIG. 2. Method 300 may be implemented in the form of executable instructions stored on a machine-readable storage medium, such as computer readable medium 120 of FIG. 1 , and/or in the form of electronic circuitry.
  • Method 300 may start in block 305 and continue to block 310, where networking device 100 establishes a connection with a remote computing device such as a cloud management server.
  • the communication channel may also involve other networking devices such as switches and/or routers.
  • Remote computing device may use the communication channel to reconfigure networking device 100 or other components on the same network.
  • networking device 100 modifies a mode of one of its radios in response to a virtualization request from remote computing device.
  • the virtualization request may notify networking device 100 that remote computing device will be initiating a virtual machine to verify the reconfiguration of the network.
  • networking device 100 receives virtual machine packets from a virtual machine of the remote computing device.
  • the virtual machine packets are sent from the virtual machine of remote computing device.
  • networking device 100 uses its radio in client station mode to inject the virtual machine packets into the network, which allows for the virtual machine to behave as if it is on-premise. Because the virtual machine packets are tunneled through the established connection, the virtual machine is able to join a wireless network as described below and verify the reconfiguration. Packets from the network can also be received by radio and then tunneled in the opposite direction to the virtual machine. Method 300 may then continue block 330, where method 300 may stop.
  • FIG. 4 is a flowchart of an example method 400 for execution by a remote computing device 216 for cloud network management. Although execution of method 400 is described below with reference to remote computing device 216 of FIG. 2, other suitable devices for execution of method 400 may be used. Method 400 may be implemented in the form of executable instructions stored on a machine-readable storage medium and/or in the form of electronic circuitry.
  • Method 400 may start in block 405 and continue to block 410, where remote computing device 216 establishes a remote connection to an access point in a different network than remote computing device 216.
  • the communication channel may also involve other networking devices such as switches and/or routers.
  • Remote computing device 216 may use the communication channel to reconfigure the access point or other components in the access point's network.
  • remote computing device 216 creates a virtual machine that is configured to join the remote network.
  • remote computing device 216 sends a virtualization request to the access point, where the remote connection us used as a tunnel for subsequent requests from the remote computing device 216.
  • remote computing device 216 sends a request to access point for the available wireless networks of the remote network.
  • a radio of the access point in client station mode is used by access points to discover the available wireless networks, which are sent back to the remote computing device 216.
  • remote computing device 216 selects and joins one of the wireless networks through the tunnel. Specifically, remote computing device 216 uses the radio to obtain network association parameters and then uses the network association parameters to join the selected wireless network. Method 400 may then continue to block 435, where method 400 may stop.
  • the foregoing disclosure describes a number of examples for enabling cloud network management.
  • the examples disclosed herein facilitate cloud network management by using a radio of an access point that is in client station mode as a tunnel for a remote virtual machine executed by a remote management device.

Abstract

Examples relate to enabling cloud network management. In some examples, a remote connection is established with a remote computing device, where the remote computing device is configured to execute a remote virtual machine. In response to a network virtualization request, a radio is switched to a client station mode. Next, a virtual machine network packet is received from the remote computing device, and the radio is used to inject the virtual machine network packet into a local network as local traffic for the remote virtual machine.

Description

CLOUD NETWORK MANAG EM ENT
BACKGROUND
[0001 ] Cloud network management often involves administrators that configure devices (e.g., switches, access points, etc.) located on unreachable networks (i.e., administrator is off-premise). Such administrators should verify that configuration changes have the desired effect on network clients' connectivity. For example, an administrator may request that a user that is on-premise perform connectivity tests and report back with the results. In another example, a virtual private network (VPN) can be established by the administrator so that the connectivity tests can be performed over a secure channel to the unreachable network.
BRIEF DESCRIPTION OF THE DRAWINGS
[0002] The following detailed description references the drawings, wherein:
[0003] FIG. 1 is a block diagram of an example networking device for cloud network management;
[0004] FIG. 2 is a block diagram of an example system for cloud network management;
[0005] FIG. 3 is a flowchart of an example method for execution by a networking device for cloud network management; and
[0006] FIG. 4 is a flowchart of an example method for execution by a remote computing device for cloud network management.
DETAILED DESCRIPTION
[0007] As described above, cloud network management can involve an on- premise user to coordinate with an administrator or a VPN. Cloud-managed network devices (e.g., switches, access points, etc.) can establish full-duplex communication channels (i.e., Web Socket) to a cloud management device. In examples described herein, a communication channel is used as a tunnel for network traffic (i.e., packet captures (PCAPs)) that originate off-premise. In these examples, a virtual machine is created, where network traffic of this off-premise virtual machine can be redirected to the on-premise network using the communication channel.
[0008] In some examples, a remote connection is established with a remote computing device, where the remote computing device is configured to execute a remote virtual machine. In response to a network virtualization request, a radio is switched to a client station mode. Next, a virtual machine network packet is received from the remote computing device, and the radio is used to inject the virtual machine network packet into a local network as local traffic for the remote virtual machine.
[0009] Referring now to the drawings, FIG. 1 is a block diagram of an example networking device 100 for cloud network management. The example networking device 100 may be a switch, an access point, a wireless router, a repeater, a bridge, or any other electronic device suitable for cloud network management. In the embodiment of FIG. 1 , networking device 100 includes controller 1 10, interfaces 1 15, and machine-readable storage medium 120.
[0010] Controller 1 10 may be one or more central processing units (CPUs), microprocessors, and/or other hardware devices suitable for retrieval and execution of instructions stored in machine-readable storage medium 120. Controller 1 10 may fetch, decode, and execute instructions 122, 124, 126, 128 to enable cloud network management, as described below. As an alternative or in addition to retrieving and executing instructions, controller 1 10 may include one or more electronic circuits comprising a number of electronic components for performing the functionality of one or more of instructions 122, 124, 126, 128.
[001 1 ] Radio(s) 1 12 may include wireless interface(s) for communicating with other computing devices via radio frequencies. Radio(s) 1 12 can be configured to facilitate wireless networks that allow for wireless communication between computing devices. Radio(s) 1 12 may support an alternative operating mode such as client station mode. When a radio 1 12 is switched to client station mode, the networking device 100 can use the radio 1 12 to behave like a client and join wireless networks provided by other networking devices. In other examples where networking device 100 is a switch, radio(s) 1 12 are not included in the networking device 100.
[0012] Interfaces 1 15 may include a number of electronic components for communicating with end devices. For example, interfaces 1 15 may be wireless interfaces such as wireless local area network (WLAN) interfaces and/or physical interfaces such as Ethernet interfaces, Universal Serial Bus (USB) interfaces, external Serial Advanced Technology Attachment (eSATA) interfaces, or any other physical connection interface suitable for communication with end devices. In operation, as detailed below, interfaces 1 15 may be used to send and receive data to and from other computing devices.
[0013] Machine-readable storage medium 120 may be any electronic, magnetic, optical, or other physical storage device that stores executable instructions. Thus, machine-readable storage medium 120 may be, for example, Random Access Memory (RAM), Content Addressable Memory (CAM), Ternary Content Addressable Memory (TCAM), an Electrically-Erasable Programmable Read-Only Memory (EEPROM), flash memory, a storage drive, an optical disc, and the like. As described in detail below, machine-readable storage medium 120 may be encoded with executable instructions for enabling cloud network management.
[0014] Remote connection establishing instructions 122 establish a connection with a remote computing device such as a cloud management server. The connection may be a full-duplex communication channel over the Internet, where the remote computing device is on a different local area network than networking device 100. In some cases, the communication channel may also involve other networking devices such as switches and/or routers.
[0015] Radio mode switching instructions 124 modify a mode of the radio 1 12 based on requests from the remote computing device. Specifically, if a virtualization request is received from the remote computing device, the mode of the radio 1 12 can be switched to client station mode, which allows the networking device 100 to connect to other wireless networks. In some cases, computing device 100 includes multiple radios 1 12 so that one radio can be switched to client station mode while the other radios continue to operate in a normal operating mode that continues to provide wireless network(s). Alternatively, if the networking device 100 is a switch, radio mode switching instructions 124 are not included in machine-readable storage medium 120.
[0016] VM packet receiving instructions 126 receive virtual machine packets from a virtual machine of the remote computing device. In this example, the remote computing device initiates the virtual machine and uses the connection established above to send packets from the virtual machine. Networking device 100 identifies the virtual machine packets as originating from the remote computing device and, accordingly, processes them as described below.
[0017] VM packet injecting instructions 128 use the radio 1 12 in client station mode to inject the virtual machine packets into a network of networking device 100. In this manner, the virtual machine packets from the off-premise virtual machine can be treated as if they originated from a computing device that is on- premise. The remote computing device can request that the wireless networks accessible to the radio 1 12 be discovered, where one of the wireless networks can then be selected for joining by the virtual machine. The virtual machine can then be configured to remotely join the network of networking device 100 using network association parameters (e.g., internet protocol address, subnet mask, gateways, etc.) obtained by the radio 1 12. Because the virtual machine packets are tunneled through the established connection, the virtual machine is able to join the wireless network even though remote computing device is off-premise. Alternatively, if networking device 100 is a switch with no radio, the virtual machine packets can be injected into the network using a port of the switch.
[0018] FIG. 2 is a block diagram of an example system 200 including a remote computing device 216 interacting with computing devices of an off-premise network 201 . Network 201 includes switch 202, access points 204A, 204N, and client computing devices 212A, 212N. The components of access points 204A, 204N may be similar to the corresponding components of networking device 100 described above with respect to FIG. 1 . [0019] As illustrated, access point A 204A includes radios 206A, 206N and controller 208. Controller 208 can be associated with firmware that includes instructions similar to as discussed above with respect to FIG. 1 . Each of the radios 206A, 206N is configured to provide wireless networks of network 201 . For example, the radios 206A, 206N can broadcast service set identifications (SSID's) that identify wireless networks that can be joined by client computing devices 212A, 212N. In this example, the wireless networks can be secured with encryption for preventing access by unauthorized devices.
[0020] Each of the radios 206A, 206N can also be configured to operate in a client station mode. When in client station mode, a radio 206A, 206N can be used to join wireless networks as if the corresponding access point 204A, 204N was a client device. For example, radio A 206A can be switched to client station mode while radio N 206N continues to operate in an access point mode (i.e., providing access to wireless networks). Access point N 204N does not show components in order to simply FIG. 2; however, access point N 204N can include similar components as described above with respect to access point A 204A.
[0021 ] Client computing devices 212A, 212N use access points 204A, 204N to access wireless networks of network 201 . For example, client computing device A 212A can use access point A 204A to discover and join a wireless network. In this example, packets from client computing device A 212 can then be accepted by access point A 204A and routed through switch 202 to provide client computing device 212A with access to the Internet or other client computing devices 212N on network 201 .
[0022] Remote computing device 216 is an off-premise device for managing components of network 201 such as switch 202 and access points 204A, 204N. Remote computing device 216 may be configured to access and reconfigure components such as switch 202 and access points 204A, 204N over the Internet. Because remote computing device 216 is off-premise, it cannot normally verify the reconfiguration of the components.
[0023] Remote computing device 216 includes virtual machine(s) 218 that are configured to verify the reconfiguration of the components. Remote computing device 216 can instantiate a virtual machine 218 and then use a connection with an access point 204A, 204N to tunnel virtual machine packets between the remote computing device 216 and network 201 . In this example, the initial connection between remote computing device 216 and the access point 204A, 204N allow the virtual machine 218 to behave as if it was on-premise. Accordingly virtual machine 218 can access and join wireless networks provided by access points 204A, 204N to verify a reconfiguration of the components of network 201 .
[0024] In some cases, remote computing device 216 may instantiate multiple virtual machines 218, where packets from each machine are tunneled through a different radio (e.g., radio A 206A, radio N 206N) of an access point (e.g., access point A 204A, access point N 204N). In this case, remote computing device 216 can use the virtual machines 218 to confirm that the reconfigured components of network 201 still allow for communication between different client devices.
[0025] FIG. 3 is a flowchart of an example method 300 for execution by a networking device 100 for cloud network management. Although execution of method 300 is described below with reference to networking device 100 of FIG. 1 , other suitable devices for execution of method 300 may be used such as access point 204A, 204N of FIG. 2. Method 300 may be implemented in the form of executable instructions stored on a machine-readable storage medium, such as computer readable medium 120 of FIG. 1 , and/or in the form of electronic circuitry.
[0026] Method 300 may start in block 305 and continue to block 310, where networking device 100 establishes a connection with a remote computing device such as a cloud management server. The communication channel may also involve other networking devices such as switches and/or routers. Remote computing device may use the communication channel to reconfigure networking device 100 or other components on the same network. In block 315, networking device 100 modifies a mode of one of its radios in response to a virtualization request from remote computing device. The virtualization request may notify networking device 100 that remote computing device will be initiating a virtual machine to verify the reconfiguration of the network. [0027] In block 320, networking device 100 receives virtual machine packets from a virtual machine of the remote computing device. The virtual machine packets are sent from the virtual machine of remote computing device. In block 325, networking device 100 uses its radio in client station mode to inject the virtual machine packets into the network, which allows for the virtual machine to behave as if it is on-premise. Because the virtual machine packets are tunneled through the established connection, the virtual machine is able to join a wireless network as described below and verify the reconfiguration. Packets from the network can also be received by radio and then tunneled in the opposite direction to the virtual machine. Method 300 may then continue block 330, where method 300 may stop.
[0028] FIG. 4 is a flowchart of an example method 400 for execution by a remote computing device 216 for cloud network management. Although execution of method 400 is described below with reference to remote computing device 216 of FIG. 2, other suitable devices for execution of method 400 may be used. Method 400 may be implemented in the form of executable instructions stored on a machine-readable storage medium and/or in the form of electronic circuitry.
[0029] Method 400 may start in block 405 and continue to block 410, where remote computing device 216 establishes a remote connection to an access point in a different network than remote computing device 216. The communication channel may also involve other networking devices such as switches and/or routers. Remote computing device 216 may use the communication channel to reconfigure the access point or other components in the access point's network. In block 415, remote computing device 216 creates a virtual machine that is configured to join the remote network.
[0030] In block 420, remote computing device 216 sends a virtualization request to the access point, where the remote connection us used as a tunnel for subsequent requests from the remote computing device 216. In block 425, remote computing device 216 sends a request to access point for the available wireless networks of the remote network. A radio of the access point in client station mode is used by access points to discover the available wireless networks, which are sent back to the remote computing device 216. In block 430, remote computing device 216 selects and joins one of the wireless networks through the tunnel. Specifically, remote computing device 216 uses the radio to obtain network association parameters and then uses the network association parameters to join the selected wireless network. Method 400 may then continue to block 435, where method 400 may stop.
[0031 ] The foregoing disclosure describes a number of examples for enabling cloud network management. In this manner, the examples disclosed herein facilitate cloud network management by using a radio of an access point that is in client station mode as a tunnel for a remote virtual machine executed by a remote management device.

Claims

CLAIMS We claim:
1 . A networking device for enabling cloud network management, comprising:
a radio that supports a client station mode;
an interface to receive communications from a remote computing device; and
a controller operatively connected to the radio, the controller to:
establish a remote connection with the remote computing device, wherein the remote computing device is configured to execute a remote virtual machine;
in response to a network virtualization request, switch the radio to the client station mode;
receive a virtual machine network packet from the remote computing device; and
use the radio to inject the virtual machine network packet into a local network as local traffic for the remote virtual machine.
2. The networking device of claim 1 , further comprising a second radio that operates in an access point mode while the radio is in the client station mode.
3. The networking device of claim 1 , wherein the controller is further to: use the radio to discover a plurality of wireless networks in the local network; and
send a list of the plurality of wireless networks to the remote computing device.
4. The networking device of claim 3, wherein the controller is further to: receive a join request from the remote computing device that specifies a selected wireless network of the plurality of wireless networks, wherein the join request is injected into the local network by the radio; and send network association parameters to the remote virtual machine, wherein the remote virtual machine uses the network association parameters to join the selected wireless network.
5. The networking device of claim 1 , wherein a second virtual machine of the remote computing device joins the local network using a second radio.
6. The networking device of claim 1 , wherein the remote computing device modifies a network configuration of the local network, and wherein the remote virtual machine uses the radio to verify the network configuration.
7. A method for enabling cloud network management, comprising:
establishing a remote connection with a networking device in a remote network;
creating a virtual machine that is configured to join the remote network; sending a network virtualization request to the networking device; and sending a virtual machine network packet to the access point, wherein the remote networking device injects the virtual machine network packet into the remote network as local traffic for the virtual machine.
8. The method of claim 7, wherein the networking device is an access point, and wherein the access point switches a radio to a client station mode in response to the network virtualization request.
9. The method of claim 8, further comprising:
sending a request for available wireless networks to the access point, wherein the access point uses the radio to discover a plurality of wireless networks in the local network; and
receiving a list of the plurality of wireless networks from the access point.
10. The method of claim 9, further comprising: sending a join request to the access point that specifies a selected wireless network of the plurality of wireless networks, wherein the access point uses the radio to inject join request into the remote network; and
receiving network association parameters from the access point; and using the network association parameters and the radio to join the selected wireless network.
1 1 . The method of claim 8, further comprising:
creating a second virtual machine that joins the remote network using a second radio; and
verifying that the virtual machine can communicate with the second virtual machine.
12. The method of claim 8, further comprising:
modifying a network configuration of the remote network; and
using the virtual machine and the radio to verify the network configuration.
13. A non-transitory machine-readable storage medium encoded with instructions executable by a processor for cloud network management, the machine-readable storage medium comprising instructions to:
establish a remote connection with a remote computing device, wherein the remote computing device is configured to execute a remote virtual machine, and wherein the remote computing device modifies a network configuration of a local network;
in response to a network virtualization request, switch a radio to a client station mode;
receive a virtual machine network packet from the remote computing device; and
use the radio to inject the virtual machine network packet into the local network as local traffic for the remote virtual machine, wherein the remote virtual machine uses the radio to verify the network configuration.
14. The non-transitory machine-readable storage medium of claim 13, wherein the instructions are further to tunnel network packets from the local network to the remote virtual machine.
15. The non-transitory machine-readable storage medium of claim 13, wherein the instructions are further to:
use the radio to discover a plurality of wireless networks in the local network; and
send a list of the plurality of wireless networks to the remote computing device.
PCT/US2015/018137 2015-02-27 2015-02-27 Cloud network management WO2016137512A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2015/018137 WO2016137512A1 (en) 2015-02-27 2015-02-27 Cloud network management

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2015/018137 WO2016137512A1 (en) 2015-02-27 2015-02-27 Cloud network management

Publications (1)

Publication Number Publication Date
WO2016137512A1 true WO2016137512A1 (en) 2016-09-01

Family

ID=56788946

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/018137 WO2016137512A1 (en) 2015-02-27 2015-02-27 Cloud network management

Country Status (1)

Country Link
WO (1) WO2016137512A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100042988A1 (en) * 2008-08-14 2010-02-18 Microsoft Corporation Installation Management using Virtual Machines
US20100299387A1 (en) * 2009-05-20 2010-11-25 Kaseya International Limited Remote management of virtual machines hosted in a private network
US20110239210A1 (en) * 2010-03-23 2011-09-29 Fujitsu Limited System and methods for remote maintenance in an electronic network with multiple clients
US20140204797A1 (en) * 2013-01-23 2014-07-24 Accton Technology Corporation Wireless access point device, network system and network auto-establishing method of the same
US20140269257A1 (en) * 2013-03-14 2014-09-18 Honeywell International Inc. Shadow access point for hierarchical tree network using 802.11 infrastructure nodes in fire detection systems and other systems

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100042988A1 (en) * 2008-08-14 2010-02-18 Microsoft Corporation Installation Management using Virtual Machines
US20100299387A1 (en) * 2009-05-20 2010-11-25 Kaseya International Limited Remote management of virtual machines hosted in a private network
US20110239210A1 (en) * 2010-03-23 2011-09-29 Fujitsu Limited System and methods for remote maintenance in an electronic network with multiple clients
US20140204797A1 (en) * 2013-01-23 2014-07-24 Accton Technology Corporation Wireless access point device, network system and network auto-establishing method of the same
US20140269257A1 (en) * 2013-03-14 2014-09-18 Honeywell International Inc. Shadow access point for hierarchical tree network using 802.11 infrastructure nodes in fire detection systems and other systems

Similar Documents

Publication Publication Date Title
US20210105669A1 (en) Service delivery to a roaming user equipment using a software-defined networking (sdn) controller
US11201814B2 (en) Configuration of networks using switch device access of remote server
EP3125476B1 (en) Service function chaining processing method and device
US10142342B2 (en) Authentication of client devices in networks
US9813291B2 (en) Shortest path bridging (SPB) configuration of networks using client device access of remote
US20150006737A1 (en) Method, apparatus, and system for providing network traversing service
US20170013452A1 (en) Network re-convergence point
US10164824B2 (en) Indicating a master network controller in a virtual router redundancy protocol
EP3494670B1 (en) Method and apparatus for updating multiple multiprotocol label switching (mpls) bidirectional forwarding detection (bfd) sessions
US9756148B2 (en) Dynamic host configuration protocol release on behalf of a user
US20230283589A1 (en) Synchronizing dynamic host configuration protocol snoop information
US11343332B2 (en) Method for seamless migration of session authentication to a different stateful diameter authenticating peer
US9118588B2 (en) Virtual console-port management
US11006339B2 (en) Handling at least one communication exchange between a telecommunications network and at least one user equipment
US20140269285A1 (en) Apparatus, system and method for load balancing traffic to an access point across multiple physical ports
WO2016137512A1 (en) Cloud network management
US11876881B2 (en) Mechanism to enable third party services and applications discovery in distributed edge computing environment
CN115623613A (en) Communication management method, system, device and medium based on wireless communication networking
WO2020221458A1 (en) Virtual network topology

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: 15883603

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: 15883603

Country of ref document: EP

Kind code of ref document: A1