System and method for deploying automatic configuration on unconfigured computing device

Abstract

The embodiment of the invention relates to a system and method for deploying automatic configuration on an unconfigured computing device. A method for deploying an automatic configuration may involve detecting a connection between a computing device and an additional computing device that operates a first protocol and is communicatively coupled with a controller through a network fabric. In one example, the method may also involve determining, by a second protocol, that the computing device is not configured for operation in the network fabric. Additionally or alternatively, the method may further involve, in response to determining that the computing device is not configured for operation in the network fabric, enabling the controller to configure the computing device for operation in the network fabric through a deployment mechanism. Various other devices, systems, and methods are also disclosed.

Description

BACKGROUND

[0001] A network fabric is sometimes managed by a controller that automatically configures newly added network devices. For example, the network fabric can include and / or represent a cloud controller that facilitates and / or implements a secure zero-touch provisioning (ZTP) process for day-zero devices that have not been configured for operation in the network fabric. In this example, the day-zero devices can lack functionality for one or more communication protocols, such as a link aggregation control protocol (LACP). Unfortunately, if such day-zero devices are connected to an aggregated Ethernet (AE) interface and / or a link aggregation group (LAG) on a network device in the network fabric, the AE interface and / or the LAG can not appear in the secure ZTP process due to the day-zero devices’ lack of functionality for the necessary communication protocol (e.g., LACP). As a result, the day-zero devices can not actually qualify for automatic configuration through the secure ZTP process.

[0002] Accordingly, the present disclosure identifies and addresses a need for additional and improved systems and methods for deploying automatic configuration on unconfigured computing devices. SUMMARY

[0003] As will be described in greater detail below, the present disclosure generally relates to systems and methods for deploying automatic configuration on unconfigured computing devices. In one example, a method for accomplishing this task can involve detecting a connection between a computing device and an additional computing device that runs a first protocol and is communicatively coupled to a controller through a network fabric. In this example, the method can also involve determining, through a second protocol, that the computing device is unconfigured for operation in the network fabric. Additionally or alternatively, the method can further involve enabling the controller to configure the computing device for operation in the network fabric through a deployment mechanism in response to determining that the computing device is unconfigured for operation in the network fabric.

[0004] Similarly, a corresponding network device can include a communication interface and circuitry communicatively coupled to the communication interface. In one example, the circuitry can be configured to communicate with a controller in a network fabric through a first protocol and / or detect a connection between a computing device and the network device through the communication interface. In this example, the circuitry can also be configured to determine, through a second protocol, that the computing device is unconfigured for operation in the network fabric. Additionally or alternatively, the circuitry can also be configured to enable the controller to program the computing device for operation in the network fabric through a deployment mechanism in response to determining that the computing device is unconfigured for operation in the network fabric.

[0005] The corresponding system may include a controller and a network device communicatively coupled to the controller. In one example, the network device may be configured to: communicate with the controller via a first protocol; and / or detect the connection between the computing device and the network device. In this example, the network device may also be configured to: determine via a second protocol that the computing device is not configured for operation within the network infrastructure. Additionally or alternatively, the network device may also be configured to: in response to determining that the computing device is not configured for operation within the network infrastructure, enable the controller to program the computing device for operation within the network infrastructure via a deployment mechanism.

[0006] Features of any of the embodiments described above can be combined with each other based on the general principles described herein. These and other embodiments, features, and advantages will be more fully understood after reading the following detailed description taken in conjunction with the accompanying drawings and claims. Attached Figure Description

[0007] The accompanying drawings illustrate several exemplary embodiments and form part of this specification. These drawings, taken in conjunction with the following description, demonstrate and illustrate various principles of this disclosure.

[0008] Figure 1 An exemplary system for deploying autoconfiguration on an unconfigured computing device is shown according to one or more embodiments of the present disclosure.

[0009] Figure 2 An exemplary network architecture for deploying autoconfiguration on an unconfigured computing device is shown according to one or more embodiments of the present disclosure.

[0010] Figure 3 A flowchart is shown of an exemplary method for deploying auto-configuration on an unconfigured computing device, according to one or more embodiments of the present disclosure.

[0011] Figure 4 It is a block diagram of an exemplary computing system capable of implementing one or more embodiments described and / or illustrated herein and / or used in conjunction with one or more embodiments described and / or illustrated herein.

[0012] In the accompanying drawings, the same reference numerals and descriptions denote similar but not necessarily identical elements. While the exemplary embodiments described herein may be modified and substituted in various forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the exemplary embodiments described herein are not intended to be limited to the specific forms disclosed. Rather, this disclosure covers all modifications, equivalents, and alternatives falling within the scope of the appended claims. Detailed Implementation

[0013] This disclosure describes various systems and methods for deploying auto-configuration on unconfigured computing devices. As will be described in more detail below, embodiments of this disclosure enable controllers used to manage network infrastructures to configure zero-day devices for operation within the network infrastructure via secure zero-touch deployment (ZTP). For example, a campus infrastructure may include and / or represent a cloud controller that can configure the zero-day device even if it lacks link aggregation control protocol (LACP) functionality.

[0014] As a concrete example, the zero-day device can be connected to the communication interface of a network device within a campus infrastructure. In one example, the network device's communication interface may include and / or represent an Aggregate Ethernet (AE) interface and / or a Link Aggregation Group (LAG). In this example, the network device may run and / or implement a Link Layer Discovery Protocol (LLDP), which detects the connection from the zero-day device to that communication interface. LLDP can notify and / or inform instances of LACP running and / or implemented on the network device.

[0015] Continuing this example, LLDP can obtain physical link information (e.g., the address of the communication interface) about the communication interface to which the zero-day device is connected. For example, LLDP can detect and / or determine that the zero-day device is connected to "<et-0 / 0 / 1, AE0> The interface will then notify LACP of this information. In response, LACP can extend and / or apply it to...<et-0 / 0 / 1, AE0> "interface." In other words, this network device enables LACP to "<et-0 / 0 / 1, AE0> "Start and / or activate on the interface."

[0016] Therefore, LACP can be used to...<et-0 / 0 / 1, AE0> "One or more settings of the interface are programmed and / or configured. These settings may include and / or represent..."<et-0 / 0 / 1, AE0> The interface includes LACP pairing information (e.g., pairing system priority, pairing system identifier, pairing management key, pairing port priority, pairing port identifier, etc.). Additionally or alternatively, LACP can initiate and / or activate a multiplexed state machine with LACP collection and / or distribution settings to indicate that the zero-day device is configured to process data transmitted through the interface.<et-0 / 0 / 1, AE0> "The traffic received by the interface and / or through this"<et-0 / 0 / 1,AE0> "The interface sends traffic. In one example, LACP can be started and / or activated locally."<et-0 / 0 / 1, AE0> "interface.

[0017] By performing the steps described above, the network device enables the cloud controller to configure the zero-day device via Secure ZTP, even if the zero-day device initially lacks LACP functionality. In one example, LLDP can detect and / or determine that the Secure ZTP process has completed the configuration of the zero-day device. Additionally or alternatively, LLDP can update one or more settings of the network device and / or local LACP information to reflect the completion of the configuration. After configuration, the zero-day device can be converted, transformed, and / or upgraded to a day-one device, which is configured via LACP for standard operation within the network infrastructure. Therefore, the day-one device can now send and / or receive traffic through the network infrastructure.

[0018] The following will refer to Figures 1 to 2 and Figure 4 This section provides a detailed description of exemplary devices, systems, and their corresponding implementations for deploying auto-configuration on unconfigured computing devices. It will be combined with... Figure 3 The document describes in detail exemplary methods for deploying auto-configuration on unconfigured computing devices.

[0019] Figure 1 An exemplary system 100 capable of being deployed automatically on unconfigured computing devices is shown. Figure 1As shown, exemplary system 100 may include and / or represent network device 106, controller 120, and / or computing device 130. In some examples, network device 106 may include and / or represent circuit system 104 and / or communication interface 102. In one example, circuit system 104 may be communicatively coupled to communication interface 102 within network device 106. In this example, circuit system 104 and / or communication interface 102 may operate, manipulate, and / or implement protocols 112 and / or 114. Additionally or alternatively, circuit system 104 and / or communication interface 102 may include, use, and / or implement one or more settings 134 (e.g., LACP settings and / or information).

[0020] In some examples, network device 106 may be communicatively coupled to controller 120 within and / or through a network structure. In one example, computing device 130 may be connected to and / or communicatively coupled to network device 106 via communication interface 102. In this example, circuitry 104 may detect the connection established between computing device 130 and network device 106.

[0021] In some examples, circuit system 104 can detect, locate, and / or determine that computing device 130 is not configured for operation within the network architecture. In one example, circuit system 104 can perform this detection, location, and / or determination via protocol 114. In this example, circuit system 104 can enable controller 120 to configure, program, and / or set up computing device 130 for operation within the network architecture via deployment mechanism 150. Circuit system 104 can perform the above-described operations in response to the detection, location, and / or determination that computing device 130 is not configured for operation within the network architecture.

[0022] In some examples, protocol 112 may include and / or represent an instance of LACP. In some examples, protocol 114 may include and / or represent an instance of LLDP. Additionally or alternatively, deployment mechanism 150 may be a ZTP process and / or a secure ZTP process.

[0023] In some examples, computing device 130 may include and / or represent a zero-day configuration and / or state when it becomes connected to network device 106 via communication interface 102. For example, this zero-day configuration may constitute and / or represent a state and / or condition in which computing device 130 cannot be integrated into the network fabric due to at least a partial lack of proper configuration. Additionally or alternatively, this zero-day configuration may constitute and / or represent a state and / or condition in which computing device 130 has not yet been assigned one or more addresses (such as Internet Protocol (IP) addresses) by controller 120 to facilitate and / or support communication and / or traffic exchange with one or more other devices in the network fabric.

[0024] In some examples, circuit system 104 can detect computing device 130 via LLDP when or after it has been communicatively coupled to network device 106. In one example, circuit system 104 can find and / or determine physical link information about communication interface 102 via LLDP. For example, circuit system 104 can find and / or determine address 116 of communication interface 102 via LLDP. In this example, circuit system 104 can initiate, apply, and / or activate LACP on communication interface 102 based at least in part on address 116.

[0025] In some examples, circuit system 104 may configure and / or program settings 134 of communication interface 102 using one or more default values ​​for LACP. In some implementations, settings 134 may include and / or represent LACP pairing information for communication interface 102 (e.g., pairing system priority, pairing system identifier, pairing management key, pairing port priority, pairing port identifier, etc.). In one example, circuit system 104 may initiate, apply, and / or activate LACP collection settings to instruct computing device 130 to be configured to process traffic received through communication interface 102. Additionally or alternatively, circuit system 104 may initiate, apply, and / or activate LACP distribution settings to instruct computing device 130 to be configured to send traffic through communication interface 102. Furthermore, circuit system 104 may initiate, apply, and / or activate an AE interface that enables controller 120 to configure and / or program computing device 130 for operation within a network architecture via a ZTP process.

[0026] In some examples, during the ZTP process, the circuit system 104 may receive messages from the computing device 130 or the controller 120 via LACP. In one example, the circuit system 104 may update the settings 134 of the communication interface 102 via LACP based at least in part on the message. In this example, the circuit system 104 may enable LACP to be maintained and / or kept operational so that the controller 120 can continue to configure the computing device 130 via the ZTP process, regardless of the message.

[0027] In some examples, circuit system 104 can detect the completion of configuration 132 for computing device 130 to operate within the network infrastructure via LLDP. For example, controller 120 can complete a secure ZTP process to configure and / or program computing device 130 for operation within the network infrastructure, and circuit system 104 can detect the completion of this secure ZTP process. In this example, circuit system 104 can then update settings 134 of communication interface 102 to reflect that configuration 132 for computing device 130 has been completed. For example, circuit system 104 can update instances of LACP on network device 106 and / or communication interface 102 to indicate that the secure ZTP process has ended and / or computing device 130 is now configured for operation within the network infrastructure.

[0028] In some examples, completing configuration 132 can effectively transition, transform, and / or upgrade computing device 130 from a day-zero state to a day-one state. In one example, this day-one state enables computing device 130 to forward traffic and / or control data to one or more additional devices through the network infrastructure.

[0029] In some examples, circuit system 104 may include and / or represent one or more electrical and / or electronic circuits capable of processing, applying, modifying, transforming, displaying, sending, receiving, and / or executing data for system 100. In one example, circuit system 104 may access and / or analyze data stored in a storage device to facilitate and / or support automatic configuration for deployment of unconfigured computing devices. Additionally or alternatively, circuit system 104 may initiate, execute, and / or run certain executable files, code snippets, and / or computer-readable instructions to facilitate and / or support automatic configuration for deployment of unconfigured computing devices.

[0030] Although Figure 1While shown as a single unit, circuit system 104 may include and / or represent a collection of multiple processing units and / or electrical or electronic components that work together and / or operate. In one example, circuit system 104 may include and / or represent one or more application-specific integrated circuits (ASICs). Additionally or alternatively, circuit system 104 may include and / or represent one or more central processing units (CPUs) and / or graphics processing units (GPUs). Examples of circuit system 104 include, but are not limited to, processing devices, microprocessors, microcontrollers, field-programmable gate arrays (FPGAs), systems on chips (SoCs), parallel accelerator processors, tensor cores, integrated circuits, chiplets, optical modules, receivers, transmitters, transceivers, storage devices, memory devices, logic circuit systems, portions of one or more of the above, variations or combinations of one or more of the above, and / or any other suitable circuit system.

[0031] In some examples, communication interface 102 may include and / or represent one or more ports, connectors, physical interfaces, Ethernet interfaces, and / or transceivers that establish and / or support communication between computing device 130 and network device 106. Additionally or alternatively, communication interface 102 may include and / or represent one or more virtual and / or logical interfaces that establish and / or support communication between computing device 130 and network device 106. For example, communication interface 102 may include and / or represent an AE interface and / or LAG.

[0032] In some examples, network device 106 and / or computing device 130 may both include and / or represent any type or form of physical computing device capable of reading computer-executable instructions and / or processing network traffic. Examples of network device 106 and / or computing device 130 include, but are not limited to, routers (such as provider edge routers, hub routers, spoke routers, autonomous system border routers, and / or area border routers), rack-mounted telecommunications equipment, switches, hubs, modems, bridges, repeaters, gateways (such as broadband network gateways), multiplexers, network adapters, network interfaces, client devices, laptop computers, tablet computers, desktop computers, servers, variations or combinations of one or more of the above, and / or any other suitable computing device.

[0033] In some examples, controller 120 may include and / or represent any type or form of physical and / or virtual device capable of managing the network infrastructure and / or performing ZTP procedures to configure computing devices introduced and / or added to the network infrastructure. In one example, controller 120 may include and / or represent a cloud controller. Additionally or alternatively, controller 120 may include and / or represent a Dynamic Host Configuration Protocol (DHCP) server.

[0034] Figure 2 An exemplary network architecture 200 is shown that facilitates and / or supports the deployment of auto-configuration on unconfigured computing devices. In some examples, Figure 2 The network structure 200 in the above may include and / or involve the combination of the above. Figure 1 The same and / or similar devices, components, configurations and / or features described. In one example, network structure 200 may include and / or represent a campus structure distributed across multiple structures, such as buildings 230(1)-(N)). In this example, network structure 200 may include and / or represent network devices 106(1)-(N), network devices 206(1)-(N), computing devices 130(1), 130(2), 130(3), 130(4), 130(5), 130(6), 130(7), 130(8), switches 220(1)-(N), routers 210(1)-(N), network 204 and / or controller 120.

[0035] In some examples, building 230(1) may house, hold, and / or surround network devices 106(1)-(N) and / or computing devices 130(1)-(4). In one example, building 230(N) may house, hold, and / or surround network devices 206(1)-(N) and / or computing devices 130(5)-(8). In this example, network devices 106(1)-(N) may all be communicatively coupled and / or connected to each of the computing devices 130(1)-(4), and / or network devices 206(1)-(N) may all be communicatively coupled and / or connected to each of the computing devices 130(5)-(8).

[0036] In some examples, switches 220(1)-(N) may all be communicatively coupled and / or connected to each of network devices 106(1)-(N) and 206(1)-(N). In one example, routers 210(1)-(N) may all be communicatively coupled and / or connected to each of switches 220(1)-(N). In this example, routers 210(1)-(N) may all be communicatively coupled to and / or connected to network 204. Additionally or alternatively, controller 120 may be communicatively coupled and / or connected to network 204. Accordingly, controller 120 may be communicatively coupled to computing devices 130(1)-(8) and / or able to communicate with computing devices 130(1)-(8) via routers 210(1)-(N), switches 220(1)-(N), network devices 106(1)-(N) and / or network devices 206(1)-(N).

[0037] As a specific example, network architecture 200 enables controller 120 to configure computing device 130(1) from a day-zero state for operation via secure ZTP. In this example, computing device 130(1) may lack LACP functionality in a day-zero state. In one example, computing device 130(1) can be connected to an AE interface and / or LAG via one or more network devices among network devices 106(1)-(N). In one example, network devices 106(1)-(N) can run and / or implement instances of LLDP that detect connections of computing device 130(1) to the AE interface and / or LAG. In this example, the LLDP can notify and / or inform instances of LACP running and / or implemented on one or more network devices among network devices 106(1)-(N).

[0038] Continuing this example, LLDP can obtain physical link information about the AE interface and / or LAG to which computing device 130(1) is connected. For example, LLDP can detect and / or determine that computing device 130(1) is connected to the AE interface and / or LAG, and then notify LACP of this information. In response, LACP can then be extended and / or applied to the AE interface and / or LAG. In other words, one or more network devices among network devices 106(1)-(N) can initiate and / or activate LACP on the AE interface and / or LAG.

[0039] For this purpose, LACP can program and / or configure one or more settings for the AE interface and / or LAG. Such settings may include and / or represent LACP pairing information for the AE interface and / or LAG (e.g., pairing system priority, pairing system identifier, pairing management key, pairing port priority, pairing port identifier, etc.). Additionally or alternatively, LACP can initiate and / or activate a multiplexed state machine with LACP collection and / or distribution settings to instruct computing device 130(1) to be configured to process traffic received through the AE interface and / or LAG and / or traffic sent through the AE interface and / or LAG. In one example, LACP can locally initiate and / or activate the AE interface and / or LAG.

[0040] By performing the above steps, one or more of the network devices 106(1)-(N) can enable controller 120 to configure computing device 130(1) via secure ZTP, even if computing device 130(1) initially lacks LACP functionality due to its day-zero state. In one example, LLDP can detect and / or determine that controller 120 has completed the secure ZTP process for configuring computing device 130(1). Additionally or alternatively, LLDP can update one or more settings and / or local LACP information in network devices 106(1)-(N) to reflect the completion of configuration. After configuration, computing device 130(1) can be converted, transformed, and / or upgraded to a day-one device capable of standard operation within the network structure via LACP. Accordingly, upon reaching day-one state, computing device 130(1) can send and / or receive traffic 250 through network structure 200.

[0041] Network 204 generally refers to any medium or architecture capable of facilitating communication or data transmission. In one example, network 204 may facilitate communication between controller 120 and routers 210(1)-(N). In particular, network 204 may facilitate and / or support this communication through one or more intermediate nodes (e.g., hops) between controller 120 and routers 210(1)-(N). These intermediate nodes may represent and / or include any type or form of suitable network device.

[0042] Network 204 may use wireless and / or wired connections to facilitate and / or support communication or data transmission. In one example, network 204 may include and / or represent all or part of the Internet. Additional examples of network 204 include, but are not limited to: intranet, wide area network (WAN), local area network (LAN), personal area network (PAN), power line communications (PLC), cellular network (e.g., Global System for Mobile Communications (GSM) network), multiprotocol label switching (MPLS) network, portions of one or more of the above, variations or combinations of one or more of the above, and / or any other suitable network. Although shown as a component of network structure 200, network 204 may alternatively constitute and / or represent a combination of network devices located outside and / or separate from network structure 200.

[0043] In some examples, combined Figure 1 and Figure 2 The system may include and / or represent one or more additional devices, circuits, components and / or features (not necessarily in the context of...) Figure 1 and Figure 2 (As shown and / or labeled). For example... Figure 1 and Figure 2 The system shown may also include and / or represent additional network devices, computing devices, controllers, routers, switches, analog and / or digital circuit systems, onboard logic, transistors, transmitters, receivers, transceivers, antennas, resistors, capacitors, diodes, inductors, switches, registers, triggers, connectors, lines, buses, semiconductor (e.g., silicon) devices and / or structures, processing devices, storage devices, circuit boards, sensors, packages, substrates, housings, combinations or variations of one or more of the above, and / or any other suitable components for facilitating and / or supporting independent reliability testing. In some implementations, one or more of these additional devices, circuits, components, and / or features may be inserted and / or applied. Figure 1 and Figure 2 The references are made to any existing devices, circuits, components, and / or features shown herein to conform to the objectives and / or purposes described herein. Figure 1 and Figure 2 The described coupling and / or connection can be a direct connection without intermediate components, devices and / or nodes, or an indirect connection with one or more intermediate components, devices and / or nodes.

[0044] In some examples, the phrase “coupled to” and / or the term “coupled” as used herein can refer to a direct connection and / or an indirect connection. For example, direct coupling between two components can constitute and / or represent a coupling in which the two devices or components are directly interconnected through a single node that provides continuity from one of the two devices or components to the other. In other words, direct coupling can exclude and / or omit any additional devices or components between the two devices or components.

[0045] Additionally or alternatively, indirect coupling between two devices and / or components may constitute and / or represent a coupling in which the two devices or components are indirectly interconnected through multiple nodes that cannot provide direct electrical and / or communication continuity from one of the two devices or components to the other. In other words, indirect coupling may include and / or incorporate at least one additional device or component between the two devices or components.

[0046] Figure 3 This is a flowchart of an exemplary method 300 for deploying auto-configuration on an unconfigured computing device. In one example, Figure 3 The steps shown can be implemented and / or performed by network devices included in the network structure. Additionally or alternatively, Figure 3 The steps shown may be incorporated into and / or involve combinations thereof. Figure 1 and Figure 2 The provided description is consistent with certain sub-steps and / or variations.

[0047] like Figure 3 As shown, method 300 may include the following steps: detecting a connection between a computing device and an additional computing device, the additional computing device running a first protocol and communicatively coupled to a controller via a network structure (310). Step 310 may be performed in various ways, including in combination with the above. Figure 1 and Figure 2 Any of those described. For example, an instance of LLDP running on a network device can detect newly established connections between the network device and computing devices lacking LACP functionality. In this example, the network device may be communicatively coupled to a cloud controller via a network infrastructure and / or the Internet. Additionally or alternatively, the connection may be established through the network device's communication interface.

[0048] Method 300 may also include the following step: determining via a second protocol that the computing device is not configured for operation within the network architecture (320). Step 320 can be performed in various ways, including in combination with the above. Figure 1 and Figure 2Any of those described. For example, an instance of LACP running on the network device could determine that the computing device has not yet been configured for operation within the network infrastructure, and / or is currently in a zero-day state.

[0049] Method 300 may further include the following step: in response to determining that the computing device is not configured for operation in the network architecture, enabling the controller to configure the computing device for operation in the network architecture via a deployment mechanism (330). Step 330 may be performed in various ways, including in combination with the above. Figure 1 and Figure 2 Any of those described. For example, in response to determining that the computing device is currently in a day-zero state, the network device can initiate and / or activate LACP on a communication interface that facilitates and / or supports the connection between the network device and the computing device. Therefore, the cloud controller can then execute and / or complete a secure ZTP procedure on the computing device to configure it for operation within the network infrastructure.

[0050] Figure 4 This is a block diagram of an exemplary computing system 400, which is capable of implementing one or more embodiments described and / or shown herein and / or used in combination with one or more embodiments described and / or shown herein. In some embodiments, all or part of the computing system 400 may be combined, alone or in combination with other elements. Figure 3 One or more of the steps described herein, and / or as a combination performed alone or in combination with other elements. Figure 3 The means for one or more of the steps described herein. All or part of the computing system 400 may also perform any other steps, methods, or processes described and / or shown herein, and / or serve as means for performing and / or implementing any other steps, methods, or processes described and / or shown herein. In one example, the computing system 400 may include and / or store all or part of certain software modules.

[0051] The term "computing system 400" broadly refers to any type or form of electrical load, including single-processor or multi-processor computing devices or systems capable of executing computer-readable instructions. Examples of computing systems 400 include, but are not limited to, workstations, laptops, client terminals, servers, distributed computing systems, mobile devices, network switches, network routers (e.g., backbone routers, edge routers, core routers, mobile service routers, broadband routers, etc.), network devices (e.g., network security devices, network control devices, network timing devices, Secure Sockets Layer Virtual Private Network (SSL VPN) devices, etc.), network controllers, gateways (e.g., serving gateways, mobile packet gateways, multi-access gateways, security gateways, etc.), and / or any other type or form of computing system or device.

[0052] The computing system 400 may be programmed, configured, and / or otherwise designed to conform to one or more network protocols. According to some embodiments, the computing system 400 may be designed to work with protocols of one or more layers of the Open Systems Interconnection (OSI) reference model, such as physical layer protocols, data link layer protocols, network layer protocols, transport layer protocols, session layer protocols, presentation layer protocols, and / or application layer protocols. For example, computing system 400 may include network devices configured according to Universal Serial Bus (USB) protocol, Institute of Electrical and Electronics Engineers (IEEE) 1394 protocol, Ethernet protocol, T1 protocol, Synchronous Optical Networking (SONET) protocol, Synchronous Digital Hierarchy (SDH) protocol, Integrated Services Digital Network (ISDN) protocol, Asynchronous Transfer Mode (ATM) protocol, Point-to-Point Protocol (PPP), Point-to-Point Protocol over Ethernet (PPPoE), Point-to-Point Protocol over ATM (PPPoA), Bluetooth protocol, IEEE 802.XX protocol, Frame Relay protocol, Token Ring protocol, Spanning Tree Protocol, and / or any other protocol suitable for configuration.

[0053] The computing system 400 may include various networking and / or computing components. For example, the computing system 400 may include at least one processor 414 and system memory 416. The processor 414 generally represents any type or form of processing unit capable of processing data or interpreting and executing instructions. For example, the processor 414 may represent an application-specific integrated circuit (ASIC), a system-on-a-chip (e.g., a network processor), a hardware accelerator, a general-purpose processor, and / or any other suitable processing element.

[0054] Processor 414 may process data according to one or more of the network protocols described above. For example, processor 414 may execute or implement portions of the protocol stack, process packets, perform memory operations (e.g., queuing packets for later processing), execute end-user applications, and / or perform any other processing tasks.

[0055] System memory 416 generally refers to any type or form of volatile or non-volatile storage device or medium capable of storing data and / or other computer-readable instructions. Examples of system memory 416 include, but are not limited to, random access memory (RAM), read-only memory (ROM), flash memory, or any other suitable memory device. While not mandatory, in some embodiments, computing system 400 may include volatile memory cells (such as, for example, system memory 416) and non-volatile storage devices (such as, for example, main storage device 432 detailed below). System memory 416 may be implemented in a network device as shared memory and / or distributed memory. Furthermore, system memory 416 may store packets and / or other information used in network operations.

[0056] In some embodiments, the exemplary computing system 400 may also include one or more components or elements other than the processor 414 and system memory 416. For example, such as Figure 4 As shown, computing system 400 may include a memory controller 418, an input / output (I / O) controller 420, and a communication interface 422, all of which can be interconnected via communication infrastructure 412. Communication infrastructure 412 generally refers to any type or form of infrastructure capable of facilitating communication between one or more components of a computing device. Examples of communication infrastructure 412 include, but are not limited to, communication buses (such as Serial ATA (SATA), Industry Standard Architecture (ISA), Peripheral Component Interconnect (PCI), PCI Express (PCIe), and / or any other suitable bus), and networks.

[0057] Memory controller 418 generally refers to any type or form of device capable of processing memory or data, or controlling communication between one or more components of computing system 400. For example, in some embodiments, memory controller 418 may control communication between processor 414, system memory 416, and I / O controller 420 via communication infrastructure 412. In some embodiments, memory controller 418 may include a Direct Memory Access (DMA) unit that can transfer data (e.g., packets) to or from a link adapter.

[0058] I / O controller 420 typically represents any type or form of device or module capable of coordinating and / or controlling the input and output functions of a computing device. For example, in some embodiments, I / O controller 420 may control or facilitate data transfer between one or more components of computing system 400, such as processor 414, system memory 416, communication interface 422, and storage interface 430.

[0059] Communication interface 422 broadly refers to any type or form of communication device or adapter capable of facilitating communication between the exemplary computing system 400 and one or more additional devices. For example, in some embodiments, communication interface 422 may facilitate communication between computing system 400 and a private or public network that includes additional computing systems. Examples of communication interface 422 include, but are not limited to, link adapters, wired network interfaces (such as network interface cards), wireless network interfaces (such as wireless network interface cards), and any other suitable interfaces. In at least one embodiment, communication interface 422 may provide a direct connection to a remote server via a direct link to a network (such as the Internet). Communication interface 422 may also provide such connectivity indirectly via, for example, a local area network (such as Ethernet), a personal area network, a wide area network, a private network (such as a virtual private network), a telephone or wired network, a cellular telephone connection, a satellite data connection, or any other suitable connection.

[0060] In some embodiments, communication interface 422 may also represent a host adapter configured to facilitate communication between computing system 400 and one or more additional network or storage devices via an external bus or communication channel. Examples of host adapters include, but are not limited to, Small Computer System Interface (SCSI) host adapters, Universal Serial Bus (USB) host adapters, IEEE 1394 host adapters, Advanced Technology Attachment (ATA), Parallel ATA (PATA), Serial ATA (SATA), and External SATA (eSATA) host adapters, Fibre Channel interface adapters, Ethernet adapters, etc. Communication interface 422 may also enable computing system 400 to participate in distributed or remote computing. For example, communication interface 422 may receive instructions from or send instructions to remote devices for execution.

[0061] like Figure 4 As shown, the exemplary computing system 400 may also include a primary storage device 432 and / or a backup storage device 434, which are coupled to the communication infrastructure 412 via a storage interface 430. Storage devices 432 and 434 generally represent any type or form of storage device or medium capable of storing data and / or other computer-readable instructions. For example, storage devices 432 and 434 may represent disk drives (e.g., so-called hard disk drives), solid-state drives, floppy disk drives, tape drives, optical disk drives, flash drives, etc. Storage interface 430 generally represents any type or form of interface or device for transferring data between storage devices 432 and 434 and other components of the computing system 400.

[0062] In some embodiments, storage devices 432 and 434 may be configured to read from and / or write to a removable storage unit configured to store computer software, data, or other computer-readable information. Examples of suitable removable storage units include, but are not limited to, floppy disks, magnetic tapes, optical discs, flash memory devices, etc. Storage devices 432 and 434 may also include other similar structures or devices for allowing computer software, data, or other computer-readable instructions to be loaded into computing system 400. For example, storage devices 432 and 434 may be configured to read from and write to software, data, or other computer-readable information. Storage devices 432 and 434 may be part of computing system 400 or may be stand-alone devices accessed through other interface systems.

[0063] Many other devices or subsystems can be connected to the computing system 400. Conversely... Figure 4 Not all components and devices shown herein are required to be present in order to practice the embodiments described and / or illustrated herein. The devices and subsystems described above may also be used in different ways. Figure 4 The interconnections are shown. The computing system 400 may also employ any number of software, firmware, and / or hardware configurations. For example, one or more embodiments of the exemplary embodiments disclosed herein may be encoded as a computer program (also referred to as computer software, software application, computer-readable instructions, or computer control logic) on a computer-readable medium. The term "computer-readable medium" generally refers to any form of device, carrier, or medium capable of storing or carrying computer-readable instructions. Examples of computer-readable media include, but are not limited to, transmissive media (such as carrier waves) and non-transient media (such as magnetic storage media (e.g., hard disk drives and floppy disks), optical storage media (e.g., compact disks (CDs) and digital video disks (DVDs)), electronic storage media (e.g., solid-state drives and flash memory media), and other distribution systems.

[0064] While the foregoing disclosure uses specific block diagrams, flowcharts, and examples to illustrate various embodiments, each block diagram component, flowchart step, operation, and / or component described and / or illustrated herein can be implemented individually and / or collectively using various hardware, software, or firmware (or any combination thereof). Furthermore, the disclosure of any component contained within other components should be considered exemplary in nature, as many other architectures can be implemented to achieve the same functionality.

[0065] In some examples, Figure 1 System 100 in this document may represent all or part of a cloud computing or network-based environment. Cloud computing and network-based environments can provide various services and applications via the Internet. These cloud computing and network-based services (e.g., Software as a Service, Platform as a Service, Infrastructure as a Service, etc.) can be accessed via a web browser or other remote interfaces. The various functions described herein may also provide network switching capabilities, gateway access capabilities, network security capabilities, network content caching and delivery services, network control services, and / or other networking capabilities.

[0066] Furthermore, one or more modules described herein can transform data, physical devices, and / or representations of physical devices from one form to another. Additionally or alternatively, one or more modules described herein can transform the processor, volatile memory, non-volatile memory, and / or any other part of the physical computing device from one form to another by executing on the computing device, storing data on the computing device, and / or otherwise interacting with the computing device.

[0067] The process parameters and order of steps described and / or illustrated herein are given by way of example only and may be changed as needed. For example, while the steps described and / or illustrated herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order shown or discussed. The various exemplary methods described and / or illustrated herein may also omit one or more steps described or illustrated herein, or include additional steps beyond those disclosed.

[0068] The foregoing description is intended to enable those skilled in the art to best utilize various aspects of the exemplary embodiments disclosed herein. This exemplary description is not intended to be exhaustive, nor is it limited to any precise form disclosed. Many modifications and variations may be made without departing from the spirit and scope of this disclosure. The embodiments disclosed herein should be considered illustrative rather than restrictive in all respects. Reference should be made to the appended claims and their equivalents in determining the scope of this disclosure.

[0069] Unless otherwise stated, the terms “connected to” and “coupled to” (and their derivatives) as used in the specification and claims shall be understood to allow for direct and indirect connections (i.e., through other elements or components). Furthermore, the term “a” (“a” or “an”) as used in the specification and claims shall be understood to mean “at least one”. Finally, for ease of use, the terms “comprising” and “having” (and their derivatives) as used in the specification and claims may be used interchangeably with “including” and have the same meaning.

Claims

1. A method comprising: The connection between the detection computing device and the additional computing device is as follows: Run the first protocol; as well as Communication is coupled with the controller through a network structure; The second protocol determines that the computing device is not configured for operation within the network architecture. as well as In response to determining that the computing device is not configured for operation in the network architecture, the controller enables the controller to configure the computing device for operation in the network architecture via a deployment mechanism.

2. The method according to claim 1, wherein: The first protocol includes the Link Aggregation Control Protocol (LACP); The second protocol includes the Link Layer Discovery Protocol (LLDP); and The deployment mechanism includes a zero-touch deployment ZTP process.

3. The method of claim 2, wherein detecting the connection between the computing device and the additional computing device comprises: After being communicatively coupled to the additional computing device, the computing device is detected via the LLDP.

4. The method according to claim 2, further comprising: The address of the communication interface of the additional computing device to which the computing device is communicatively coupled is found through the LLDP. as well as The LACP is activated on the communication interface, at least in part, based on the address.

5. The method of claim 4, wherein activating the LACP on the communication interface comprises: The LACP is used to configure one or more settings of the communication interface using one or more default values.

6. The method of claim 5, wherein configuring the settings of the communication interface includes at least one of the following: Activate LACP collection settings to indicate that the computing device is configured to process traffic received through the communication interface; or Activate LACP distribution settings to indicate that the computing device is configured to send traffic through the communication interface.

7. The method of claim 5, wherein configuring the settings of the communication interface includes: Activate the aggregated Ethernet interface, which enables the controller to configure the computing device for operation within the network architecture via the ZTP process.

8. The method according to claim 5, further comprising: Messages are received from the computing device or the controller via the LACP; The settings of the communication interface are updated, at least in part, based on the message, via the LACP. as well as The LACP is kept operational so that the controller can continue to configure the computing device through the ZTP process, regardless of the messages.

9. The method of claim 4, wherein the communication interface comprises at least one of the following: Aggregated Ethernet interface; or Link aggregation group (LAG).

10. The method of claim 1, further comprising: The completion of the configuration for the computing device to operate in the network structure is detected through the second protocol; as well as The first protocol is used to update one or more settings of the additional computing device to reflect the completion of the configuration.

11. The method according to claim 1, further comprising: After the configuration of the computing device is completed, the computing device is enabled to forward traffic through the connection.

12. A network device, comprising: Communication interface; as well as A circuit system coupled to the communication interface, wherein the circuit system is configured as follows: Communicating with the controller in the network structure via the first protocol; The connection between the detection computing device and the network device via the communication interface is verified. The second protocol determines that the computing device is not configured for operation within the network architecture. as well as In response to determining that the computing device is not configured for operation in the network architecture, the controller enables the controller to configure the computing device for operation in the network architecture via a deployment mechanism.

13. The network device according to claim 12, wherein: The first protocol includes the Link Aggregation Control Protocol (LACP); The second protocol includes the Link Layer Discovery Protocol (LLDP); and The deployment mechanism includes a zero-touch deployment ZTP process.

14. The network device of claim 13, wherein the circuitry is further configured to detect the computing device via the LLDP after being communicatively coupled to the network device.

15. The network device of claim 13, wherein the circuit system is further configured to: Using the LLDP, the address of the communication interface of the network device to which the computing device is communicatively coupled is found; and The LACP is activated on the communication interface, at least in part, based on the address.

16. The network device of claim 15, wherein the circuitry is further configured to: program one or more settings of the communication interface using one or more default values ​​via the LACP.

17. The network device of claim 16, wherein the circuit system is further configured to: Activate LACP collection settings to indicate that the computing device is configured to process traffic received through the communication interface; or Activate LACP distribution settings to indicate that the computing device is configured to send traffic through the communication interface.

18. The network device of claim 16, wherein the circuitry is further configured to: activate a converged Ethernet interface, the converged Ethernet interface enabling the controller to configure the computing device for operation within the network architecture via the ZTP process.

19. The network device of claim 16, wherein the circuit system is further configured to: Messages are received from the computing device or the controller via the LACP; The settings of the communication interface are updated, at least in part, based on the message, via the LACP; and The LACP is kept operational so that the controller can continue to configure the computing device through the ZTP process, regardless of the messages.

20. A system comprising: Controller; as well as A network device that is communicationally coupled to the controller, wherein the network device is configured to: Communicating with the controller via a first protocol; Detect the connection between the computing device and the network device; The second protocol determines that the computing device is not configured for operation within the network architecture. as well as In response to determining that the computing device is not configured for operation in the network architecture, the controller enables the controller to configure the computing device for operation in the network architecture via a deployment mechanism.

Images