Patent Description:
<CIT> relates to transfer data in a wireless network in an efficient manner.

<CIT> relates to protocol and structure for a self-organizing network.

To form a high-availability cluster, a plurality of network devices (which may be referred to as cluster nodes in the high-availability cluster) may be linked and/or connected via a plurality of interfaces. A control interface may provide a control link by which cluster nodes may exchange control traffic in order to synchronize routing engine sessions of the cluster nodes. A fabric interface may provide a fabric link by which cluster nodes may forward network traffic (e.g., traffic that is originated from and/or destined for client devices that are communicatively connected with the high-availability cluster).

In some cases, the control link and the fabric link may be implemented by physical network cables such as Ethernet cables, fiber cables, and/or the like. While physical network cables may provide high transfer rates and reliability, physical network cables increase the cost and complexity of deploying high-availability clusters, decrease the flexibility in deploying high-availability clusters (e.g., the physical network cables may limit the physical placement of cluster nodes in an office building), and/or the like.

Some implementations described herein provide network devices that are configured as high-availability cluster nodes with wireless control and fabric links. In some implementations, a network device (e.g., a high-availability cluster node) may include a wireless physical interface module (PIM), a wireless network interface controller (NIC), a wireless communication adapter, and/or another type of component that provides wireless communication capabilities. The network device may communicatively connect a wireless control interface with a wireless control interface of another network device in a high-availability cluster to establish a wireless control link, by which control traffic may be exchanged. Moreover, the network device may communicatively connect a wireless fabric interface with a wireless fabric interface of the other network device to establish a wireless fabric link, by which network traffic may be exchanged. In this way, the network devices in the high-availability cluster may be connected wirelessly, which decreases the cost and complexity of deploying the high-availability cluster. Moreover, the flexibility of deploying the high-availability cluster is increased in that the physical location of the network devices is not restricted due to running physical network cables. Accordingly, the network devices may be more optimally placed (e.g., in an office building, across a campus, and/or the like) such that the wireless coverage of the high-availability cluster, for client devices that communicatively connect with the high-availability cluster, may be increased.

<FIG> are diagrams of one or more example implementations <NUM> described herein. As shown in <FIG>, example implementation(s) <NUM> may include a plurality of network devices, such as cluster node <NUM>, cluster node <NUM>, and/or the like. In some implementations, example implementation(s) <NUM> may include a greater quantity of network devices and/or a greater quantity of high-availability clusters.

In some implementations, the plurality of network devices may be linked and/or connected together to form a high-availability cluster. In this case, the plurality of network devices may be linked and/or connected together to form a logical or virtual network device (which may be referred to as a chassis cluster) that is more resilient to faults than if the plurality of network devices were to operate in discrete configurations. The plurality of network devices in the high-availability cluster may share session information associated with routing engine sessions and/or user sessions such that faults in the high-availability cluster may be mitigated by near instantaneous failover and/or reversion of stateful network traffic. The high-availability cluster may be deployed in various settings, contexts, and/or locations, such as an office branch, a campus, a retail location, and/or the like.

As shown in <FIG>, cluster node <NUM> and cluster node <NUM> (as well as other cluster nodes in the high-availability cluster) may be linked and/or connected via a plurality of wireless links, such as a wireless control link, a wireless fabric link, and/or the like. Cluster node <NUM> and cluster node <NUM> may exchange control traffic (e.g., traffic that is originated and/or terminated in a control plane or routing engine) via the wireless control link and may forward network traffic (e.g., traffic that is to be forwarded by a data plane or forwarding engine of a cluster node) via the wireless fabric link.

Cluster node <NUM> and cluster node <NUM> may exchange control traffic via the wireless control link to form a unified control plane or routing engine for the high-availability cluster, to synchronize the configuration and kernel state of the control plane or routing engine to facilitate the high-availability of interfaces and services of the high-availability cluster, and/or the like. The control traffic may include, for example, routing engine session information, information identifying one or more routing tables (e.g., a routing information base (RIB), a forwarding information base (FIB), a label information base (LIB), a label forwarding instance base (LFIB), and/or the like) associated with the routing engine, routing protocol traffic (e.g., border gateway protocol (BGP) traffic, open shortest path first (OSPF) traffic, routing information protocol (RIP) traffic, intermediate system to intermediate system (IS-IS) protocol traffic, and/or the like), keep-alive or heartbeat packets (e.g., packets that may be used to determine whether a cluster node has become unresponsive and/or whether a failure or fault associated with a cluster node has occurred ), and/or the like.

The wireless fabric link may permit cluster node <NUM> and cluster node <NUM> (and other cluster nodes in the high-availability cluster) to form a unified data plane or forwarding engine for the high-availability cluster. In this case, cluster node <NUM> and cluster node <NUM> may forward network traffic via the wireless fabric link (e.g., cluster node <NUM> may forward network traffic to cluster node <NUM> via the wireless fabric link and/or cluster node <NUM> may forward network traffic to cluster node <NUM> via the wireless fabric link). The network traffic (which also may be referred to as transit traffic) may include application traffic, web traffic, voice (e.g., voice over Internet protocol (VoIP)) traffic, and/or other types of traffic that originated and/or terminated at a client device and/or other devices that communicatively connect with the high-availability cluster.

In some implementations, each of cluster node <NUM> and cluster node <NUM> may include a wireless PIM (or a wireless NIC, a wireless communication adapter, and/or another type of component that provides wireless communication capabilities). The wireless control link may communicatively connect a wireless control interface of cluster node <NUM> (e.g., provided by the wireless PIM of cluster node <NUM>) and a wireless control interface of cluster node <NUM> (e.g., provided by the wireless PIM of cluster node <NUM>). The wireless fabric link may communicatively connect a wireless fabric interface of cluster node <NUM> (e.g., provided by the wireless PIM of cluster node <NUM>) and a wireless fabric interface of cluster node <NUM> (e.g., provided by the wireless PIM of cluster node <NUM>).

The wireless control link and wireless fabric link may be implemented over wireless channels. For example, the wireless control link may be implemented over wireless channel <NUM>, and the wireless fabric link may be implemented over wireless channel <NUM>. A wireless channel may include a particular channel frequency and an upper frequency bound and a lower frequency bound determined based on a channel width (e.g., <NUM>, <NUM>, etc.). For example, wireless channel <NUM> may have a channel frequency of <NUM> and a channel width of <NUM>, and therefore may have an upper frequency bound of <NUM> and a lower frequency bound of <NUM>. In some implementations, a channel frequency may be associated with various licensed and/or unlicensed radio frequency (RF) ranges, such as the <NUM> RF range (e.g., between <NUM> and <NUM>), the <NUM> RF range (e.g., between <NUM> and <NUM>), the <NUM> RF range (e.g., between <NUM> and <NUM>), and/or the like. In some implementations, a channel frequency may be unassociated with an RF range and/or with any defined communication protocol channel.

In some implementations, wireless channel <NUM> and wireless channel <NUM> may be the same wireless channel or different wireless channels, may be non-overlapping wireless channels, may be half-duplex wireless channels or full-duplex wireless channels, and/or the like. In some implementations, wireless channel <NUM> may be different from and/or non-overlapping with the wireless channels that cluster node <NUM> uses for wireless communication links with client devices. In some implementations, wireless channel <NUM> may be different from and/or non-overlapping with the wireless channels that cluster node <NUM> uses for wireless communication links with client devices. In some implementations, wireless channel <NUM> and wireless channel <NUM> may be different from and/or non-overlapping with the wireless channels that cluster node <NUM> and cluster node <NUM> use for wireless communication links with client devices.

As shown in <FIG>, cluster node <NUM> and cluster node <NUM> (and other cluster nodes) may perform a process to form and/or establish the high-availability cluster, to add and/or remove cluster nodes from the high-availability cluster, and/or the like. As shown in <FIG>, and by reference number <NUM>, each cluster node may configure a cluster identifier and a node identifier. The cluster identifier may be associated with the high-availability cluster and may identify the high-availability cluster from other high-availability clusters. In this case, cluster node <NUM> and cluster node <NUM> may be configured with the same cluster identifier such that cluster node <NUM> and cluster node <NUM> are to be included in the same high-availability cluster. The cluster identifier may include a name, a numeric value, an alpha-numeric string, and/or the like.

The node identifier may be associated with and specific to a cluster node such that the node identifier may identify the cluster node from other cluster nodes in the same high-availability cluster. In this case, cluster node <NUM> and cluster node <NUM> may be configured with different node identifiers. The node identifier may include a name, a numeric value, an alpha-numeric string, and/or the like.

In some implementations, a cluster node (e.g., cluster node <NUM>, cluster node <NUM>, and/or the like) may configure a cluster identifier and node identifier for the cluster node based on receiving an instruction (e.g., a chassis cluster command and/or another type of instruction), which may be provided as input to the cluster node (e.g., by a user via a console port and/or another means for input to the cluster node). In some implementations, a cluster node may automatically configure a cluster identifier and node identifier for the cluster node based on an event, such as a reboot or restart of the cluster node and/or the like.

As shown in <FIG>, and by reference number <NUM>, cluster node <NUM> and cluster node <NUM> may configure a wireless channel for a wireless control link between cluster node <NUM> and cluster node <NUM>. In some implementations, cluster node <NUM> and cluster node <NUM> may automatically and jointly configure the wireless channel for the wireless control link between cluster node <NUM> and cluster node <NUM>. In some implementations, cluster node <NUM> and cluster node <NUM> may configure the wireless channel for a wireless control link based on receiving an instruction, which may be provided as input (e.g., by a user via a console port and/or another means for input).

To automatically and jointly configure the wireless channel for the wireless control link, cluster node <NUM> may broadcast a signal or communication that indicates the cluster identifier and node identifier configured for cluster node <NUM>. Cluster node <NUM> may broadcast a signal or communication that indicates the cluster identifier and node identifier configured for cluster node <NUM>. Cluster node <NUM> may search or scan for cluster nodes that have been configured with the same cluster identifier as cluster node <NUM>. Similarly, cluster node <NUM> may search or scan for cluster nodes that have been configured with the same cluster identifier as cluster node <NUM>. In this case, cluster node <NUM> and cluster node <NUM> may identify each other and, accordingly, may jointly configure the wireless channel for the wireless control link based on determining that cluster node <NUM> and cluster node <NUM> are configured with the same cluster identifier. Cluster node <NUM> and cluster node <NUM> may jointly configure the wireless channel such that the respective wireless control interfaces of cluster node <NUM> and cluster node <NUM> are operating on the same wireless channel. In some implementations, cluster node <NUM> and cluster node <NUM> may reboot or restart after the wireless channel for the wireless control link is configured.

As shown in <FIG>, and by reference number <NUM>, cluster node <NUM> and cluster node <NUM> may establish (e.g., after rebooting or restarting) the wireless control link over the wireless channel (e.g., wireless channel <NUM>) configured for the wireless control link. To establish the wireless control link, cluster node <NUM> and cluster node <NUM> may perform a handshake process and/or another type of wireless connection establishment process. The handshake process may include a four-way handshake process (e.g., a four-way handshake according to IEEE <NUM>. 11i) and/or another type of handshake process. Moreover, to increase the network security over the wireless control link, cluster node <NUM> and cluster node <NUM> may establish a tunnel over the wireless control link such that control traffic may be securely transmitted via the wireless control link. The tunnel may include an Internet protocol security (IPSec) tunnel and/or another type of tunnel in which packets of the control traffic are encrypted, authenticated, and/or encapsulated.

Cluster node <NUM> and cluster node <NUM> may synchronize the wireless control link to synchronize the respective routing engines of cluster node <NUM> and cluster node <NUM> such that the respective routing engines operate as a unified routing engine for the high-availability cluster. To synchronize the wireless control link (and the unified control plane or routing engine of the high-availability cluster), cluster node <NUM> and cluster node <NUM> may exchange control traffic via the wireless control link. In this case, cluster node <NUM> and cluster node <NUM> may exchange routing engine session information, routing tables, routing protocol traffic, keep-alive or heartbeat packets, and/or the like.

In some implementations, as part of the synchronization process, cluster node <NUM> and cluster node <NUM> may jointly establish a primary node and a secondary node (or secondary nodes) of the high-availability cluster. The primary node of the high-availability cluster may host and maintain the user sessions of the client devices communicatively connected with the high-availability cluster, may host and maintain the primary routing engine session for the high-availability cluster, and/or the like. The secondary node of the high-availability cluster may host and maintain backup information for the user sessions and routing engine session for the high-availability cluster such that, if the primary node fails or experiences a fault that causes a failover from the primary node to the secondary node, the secondary node may take over as the primary node of the high-availability cluster with little to no interruption of the stateful user sessions.

In some implementations, as part of the synchronization process, cluster node <NUM> and cluster node <NUM> may jointly configure an ingress point and an egress point for the high-availability cluster. The ingress point may be the cluster node where network traffic enters the high-availability cluster from one or more external networks (e.g., the Internet, a public telecommunications network, a provider network, and/or the like). In other words, network traffic that is destined for a client device communicatively connected with the high-availability cluster enters the high-availability cluster via the ingress point. The egress point may be the cluster node where network traffic exits the high-availability cluster to the one or more external networks. In other words, network traffic that is originated for a client device communicatively connected with the high-availability cluster exits the high-availability cluster via the ingress point.

In some implementations, cluster node <NUM> and cluster node <NUM> may configure the ingress point and the egress point such that the ingress point and the egress point are located on the same cluster node, which may be referred to as an active/passive configuration. In some implementations, cluster node <NUM> and cluster node <NUM> may configure the ingress point and the egress point such that the ingress point and the egress point are located on different cluster nodes (e.g., the ingress point may be located on cluster node <NUM> and the egress point may be located on cluster node <NUM>), which may be referred to as an active/active configuration. In some implementations, cluster node <NUM> and cluster node <NUM> may configure the ingress point and the egress point such that, if a cluster node (e.g., cluster node <NUM>) that is serving as the ingress point and/or the egress point for the high-availability cluster fails and/or experiences a fault that causes a failover, the other cluster node (e.g., cluster node <NUM>) may become the ingress point and/or the egress point.

As shown in <FIG>, and by reference number <NUM>, cluster node <NUM> and cluster node <NUM> may configure a wireless channel for a wireless fabric link between cluster node <NUM> and cluster node <NUM>. In some implementations, cluster node <NUM> and cluster node <NUM> may automatically and jointly configure the wireless channel for the wireless fabric link between cluster node <NUM> and cluster node <NUM>. In some implementations, cluster node <NUM> and cluster node <NUM> may automatically and jointly configure the wireless channel for the wireless fabric link based on establishing the wireless control link. In some implementations, cluster node <NUM> and cluster node <NUM> may configure the wireless channel for a wireless fabric link based on receiving an instruction, which may be provided as input (e.g., by a user via a console port and/or another means for input).

To automatically and jointly configure the wireless channel for the wireless fabric link, cluster node <NUM> and cluster node <NUM> may jointly configure the wireless channel such that the respective wireless fabric interfaces of cluster node <NUM> and cluster node <NUM> are operating on the same wireless channel. Moreover, cluster node <NUM> and cluster node <NUM> may jointly configure the wireless channel such that the wireless channel for the wireless fabric link and the wireless channel for the wireless control link are different wireless channels, are non-overlapping wireless channels, and/or the like.

As shown in <FIG>, and by reference number <NUM>, cluster node <NUM> and cluster node <NUM> may establish the wireless fabric link over the wireless channel (e.g., wireless channel <NUM>) configured for the wireless fabric link. To establish the wireless fabric link, cluster node <NUM> and cluster node <NUM> may perform a handshake process and/or another type of wireless connection establishment process. The handshake process may include a four-way handshake process (e.g., a four-way handshake according to IEEE <NUM>. 11i) and/or another type of handshake process. Moreover, to increase the network security over the wireless fabric link, cluster node <NUM> and cluster node <NUM> may establish a tunnel over the wireless fabric link such that network traffic may be securely transmitted via the wireless fabric link. The tunnel may include an IPSec tunnel and/or another type of tunnel in which packets of the fabric traffic are encrypted, authenticated, and/or encapsulated.

Once cluster node <NUM> and cluster node <NUM> have completed the configuration process of the high-availability cluster, cluster node <NUM> and cluster node <NUM> may continue to exchange control traffic via the wireless control link (e.g., cluster node <NUM> may transmit control traffic to cluster node <NUM> via the wireless control link and/or cluster node <NUM> may transmit control traffic to cluster node <NUM> via the wireless control link), may transmit and/or forward network traffic via the wireless fabric link (e.g., cluster node <NUM> may transmit and/or forward network traffic to cluster node <NUM> via the wireless fabric link and/or cluster node <NUM> may transmit and/or forward network traffic to cluster node <NUM> via the wireless fabric link), and/or the like. In some implementations, cluster node <NUM> and/or cluster node <NUM> may perform the actions described above in reference to reference numbers <NUM>-<NUM> (or a subset thereof) to establish control links and/or fabric links with other cluster nodes in the high-availability cluster.

In this way, a network device (e.g., a high-availability cluster node) may include a wireless PIM, a wireless NIC, a wireless communication adapter, and/or another type of component that provides wireless communication capabilities. The network device may communicatively connect a wireless control interface with a wireless control interface of another network device (or a plurality of other devices) in a high-availability cluster to establish a wireless control link, by which control traffic may be exchanged. Moreover, the network device may communicatively connect a wireless fabric interface with a wireless fabric interface of the other network device to establish a wireless fabric link, by which network traffic may be exchanged. In this way, the network devices in the high-availability cluster may be connected wirelessly, which decreases the cost and complexity of deploying the high-availability cluster. Moreover, the flexibility of deploying the high-availability cluster is increased in that the physical location of the network devices is not restricted due to running physical network cables. Accordingly, the network devices may be more optimally placed (e.g., in an office building, across a campus, and/or the like) such that the wireless coverage of the high-availability cluster, for client devices that communicatively connect with the high-availability cluster, may be increased.

As indicated above, <FIG> are provided merely as one or more examples.

<FIG> is a diagram of an example environment <NUM> in which systems and/or methods described herein may be implemented. As shown in <FIG>, environment <NUM> may include one or more network devices <NUM>-<NUM> through <NUM>-n (n ≥ <NUM>) (hereinafter referred to collectively as "network devices <NUM>," and individually as "network device <NUM>") and a network <NUM>. Devices of environment <NUM> may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections. In some implementations, network devices <NUM> may be linked and/or connected together to form a high-availability cluster. In some implementations, the high-availability cluster may include a plurality of nodes (e.g., two or more nodes) that are implemented by network devices <NUM>.

Network device <NUM> includes one or more devices capable of receiving, providing, storing, generating, and/or processing information. In some implementations, network device <NUM> may include a firewall, a router, a gateway, a switch, a bridge, a wireless access point, a base station (e.g., eNodeB, NodeB, gNodeB, and/or the like), and/or the like. In some implementations, network device <NUM> may be implemented as a physical device implemented within a housing, such as a chassis. In some implementations, network device <NUM> may be implemented as a virtual device implemented by one or more computer devices of a cloud computing environment or a data center.

In some implementations, network device <NUM> may include a wireless PIM, a wireless NIC, a wireless communication adapter, and/or another type of component that provides wireless communication capabilities. Network device <NUM> may communicatively connect a wireless control interface with a wireless control interface of another network device <NUM> in a high-availability cluster to establish a wireless control link, by which control traffic may be exchanged. Moreover, network device <NUM> may communicatively connect a wireless fabric interface with a wireless fabric interface of the other network device <NUM> to establish a wireless fabric link, by which network traffic may be exchanged.

Network <NUM> includes one or more wireless networks. For example, network <NUM> may include a cellular network (e.g., a long-term evolution (LTE) network, a code division multiple access (CDMA) network, a <NUM> network, a <NUM> network, a <NUM> network, another type of cellular network, etc.), a wireless local area network (WLAN) (e.g., a Wi-Fi network, an unlicensed spectrum wireless network, and/or the like), a wireless peer-to-peer (P2P) network (e.g., Wi-Fi direct, Bluetooth, and/or the like), and/or the like, and/or a combination of these or other types of networks.

<FIG> and <FIG> are diagrams of example components of one or more devices of <FIG>. <FIG> is a diagram of example components of a device <NUM>. In some implementations, device <NUM> may correspond to device <NUM>. In some implementations, device <NUM> may include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include a bus <NUM>, a processor <NUM>, a memory <NUM>, a storage component <NUM>, an input component <NUM>, an output component <NUM>, and a communication interface <NUM>.

Bus <NUM> includes a component that permits communication among the components of device <NUM>. Processor <NUM> is implemented in hardware, firmware, or a combination of hardware and software. Processor <NUM> takes the form of a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, processor <NUM> includes one or more processors capable of being programmed to perform a function. Memory <NUM> includes a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by processor <NUM>.

Communication interface <NUM> includes a transceiver-like component (e.g., a transceiver and/or a separate receiver and transmitter) that enables device <NUM> to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface <NUM> may permit device <NUM> to receive information from another device and/or provide information to another device. For example, communication interface <NUM> may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.

Device <NUM> may perform one or more processes described herein. Device <NUM> may perform these processes based on processor <NUM> executing software instructions stored by a non-transitory computer-readable medium, such as memory <NUM> and/or storage component <NUM>. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

<FIG> is a diagram of example components of a device <NUM>. In some implementations, device <NUM> may correspond to device <NUM>. In some implementations, device <NUM> may include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include one or more input components <NUM>-<NUM> through <NUM>-B (B ≥ <NUM>) (hereinafter referred to collectively as input components <NUM>, and individually as input component <NUM>), a switching component <NUM>, one or more output components <NUM>-<NUM> through <NUM>-C (C ≥ <NUM>) (hereinafter referred to collectively as output components <NUM>, and individually as output component <NUM>), and a controller <NUM>.

Input component <NUM> may be points of attachment for physical links and may be points of entry for incoming traffic, such as packets. In some implementations, input component <NUM> may send and/or receive packets.

In some implementations, switching component <NUM> may enable input components <NUM>, output components <NUM>, and/or controller <NUM> to communicate.

In some implementations, output component <NUM> may send packets and/or receive packets.

Controller <NUM> may create routing tables based on the network topology information, create forwarding tables based on the routing tables, and forward the forwarding tables to input components <NUM> and/or output components <NUM>.

Controller <NUM> may perform one or more processes described herein. Controller <NUM> may perform these processes in response to executing software instructions stored by a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

<FIG> is a flow chart of an example process <NUM> for configuring wireless control and fabric links for high-availability cluster nodes. In some implementations, one or more process blocks of <FIG> may be performed by a first network device included in a high-availability cluster (e.g., network device <NUM>, device <NUM>, device <NUM>, and/or the like). In some implementations, one or more process blocks of <FIG> may be performed by another device or a group of devices separate from or including the first network device, such as one or more other network devices and/or the like. In some implementations, the high-availability cluster may include a plurality of nodes (e.g., two or more nodes).

As shown in <FIG>, process <NUM> may include configuring a first wireless channel for a wireless control link (block <NUM>). For example, the network device (e.g., using processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, communication interface <NUM>, input component <NUM>, switching component <NUM>, output component <NUM>, controller <NUM>, and/or the like) may configure a first wireless channel for a wireless control link, as described above.

As further shown in <FIG>, process <NUM> may include establishing, using the first wireless channel, the wireless control link with a second network device in the high-availability cluster (block <NUM>). For example, the network device (e.g., using processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, communication interface <NUM>, input component <NUM>, switching component <NUM>, output component <NUM>, controller <NUM>, and/or the like) may establish, using the first wireless channel, the wireless control link with a second network device in the high-availability cluster, as described above.

As further shown in <FIG>, process <NUM> may include configuring a second wireless channel for a wireless fabric link (block <NUM>). For example, the network device (e.g., using processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, communication interface <NUM>, input component <NUM>, switching component <NUM>, output component <NUM>, controller <NUM>, and/or the like) may configure a second wireless channel for a wireless fabric link, as described above.

As further shown in <FIG>, process <NUM> may include establishing, using the second wireless channel, the wireless fabric link with the second network device (block <NUM>). For example, the network device (e.g., using processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, communication interface <NUM>, input component <NUM>, switching component <NUM>, output component <NUM>, controller <NUM>, and/or the like) may establish, using the second wireless channel, the wireless fabric link with the second network device, as described above.

In a first implementation, configuring the second wireless channel comprises configuring the second wireless channel based on establishing the wireless control link. In a second implementation, alone or in combination with the first implementation, process <NUM> further comprises synchronizing, based on establishing the wireless control link, a routing engine of the first network device and a routing engine of the second network device via the wireless control link. In a third implementation, alone or in combination with one or more of the first and second implementations, synchronizing the routing engine of the first network device and the routing engine of the second network device comprises at least one of transmitting one or more heartbeat packets to the second network device via the wireless control link, transmitting information identifying a routing table to the second network device via the wireless control link, or, transmitting routing protocol traffic to the second network device via the wireless control link.

In a fourth implementation, alone or in combination with one or more of the first through third implementations, process <NUM> further comprises causing the first network device to reboot based on configuring the first wireless channel, and establishing the wireless control link with the second network device comprises establishing the wireless control link with the second network device after causing the first network device to reboot. In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, process <NUM> further comprising configuring the first network device with a cluster identifier associated with the high-availability cluster and a node identifier associated with the first network device. In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, process <NUM> further comprises jointly establishing, with the second network device and via the wireless control link, a primary node for the high-availability cluster and a secondary node for the high-availability cluster.

<FIG> is a flow chart of an example process <NUM> for configuring wireless control and fabric links for high-availability cluster nodes. In some implementations, one or more process blocks of <FIG> may be performed by a first network device (e.g., network device <NUM>, device <NUM>, device <NUM>, and/or the like). In some implementations, one or more process blocks of <FIG> may be performed by another device or a group of devices separate from or including the first network device, such as one or more other network devices and/or the like.

As shown in <FIG>, process <NUM> may include configuring a first wireless channel for a wireless control link, wherein the first network device is included in a high-availability cluster (block <NUM>). For example, the network device (e.g., using processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, communication interface <NUM>, input component <NUM>, switching component <NUM>, output component <NUM>, controller <NUM>, and/or the like) may configure a first wireless channel for a wireless control link, as described above. In some implementations, the first network device is included in a high-availability cluster.

As further shown in <FIG>, process <NUM> may include synchronizing, via the wireless control link, a routing engine of the first network device and a routing engine of the second network device (block <NUM>). For example, the network device (e.g., using processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, communication interface <NUM>, input component <NUM>, switching component <NUM>, output component <NUM>, controller <NUM>, and/or the like) may synchronize, via the wireless control link, a routing engine of the first network device and a routing engine of the second network device, as described above.

As further shown in <FIG>, process <NUM> may include configuring a second wireless channel for a wireless fabric link, wherein the first wireless channel and the second wireless channel are different wireless channels (block <NUM>). For example, the network device (e.g., using processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, communication interface <NUM>, input component <NUM>, switching component <NUM>, output component <NUM>, controller <NUM>, and/or the like) may configure a second wireless channel for a wireless fabric link, as described above. In some implementations, the first wireless channel and the second wireless channel are different wireless channels.

In a first implementation, process <NUM> further comprises transmitting control traffic to the second network device via the wireless control link and transmitting network traffic to the second network device via the wireless fabric link. In a second implementation, alone or in combination with the first implementation, the control traffic comprises at least one of heartbeat packets, information identifying a routing table, or routing protocol traffic. In a third implementation, alone or in combination with one or more of the first and second implementations, the first wireless channel and the second wireless channel are non-overlapping wireless channels. In a fourth implementation, alone or in combination with one or more of the first through third implementations, the first wireless channel, the second wireless channel, and one or more third wireless channels that are used for wireless communication links between the first network device and one or more client devices are different wireless channels.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, establishing the wireless control link comprises establishing a first IPSec tunnel associated with the wireless control link, and establishing the wireless fabric link comprises establishing a second IPSec tunnel associated with the wireless fabric link. In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, the wireless control link is associated with a control interface of a wireless PIM included in the first network device and the wireless fabric link is associated with a fabric interface of the wireless PIM.

In a seventh implementation, alone or in combination with one or more of the first through sixth implementations, the first network device is configured as an ingress point and an egress point for the high-availability cluster, the second network device is configured to become the ingress point for the high-availability cluster if a failure associated with an ingress interface of the first network device occurs, and the second network device is configured to become the egress point for the high-availability cluster if a failure associated with an egress interface of the first network device occurs.

As used herein, the term traffic or content may include a set of packets. A packet may refer to a communication structure for communicating information, such as a protocol data unit (PDU), a network packet, a datagram, a segment, a message, a block, a cell, a frame, a subframe, a slot, a symbol, a portion of any of the above, and/or another type of formatted or unformatted unit of data capable of being transmitted via a network.

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more. " Further, as used herein, the article "the" is intended to include one or more items referenced in connection with the article "the" and may be used interchangeably with "the one or more. " Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.), and may be used interchangeably with "one or more. " Where only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, the terms "has," "have," "having," or the like are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise. Also, as used herein, the term "or" is intended to be inclusive when used in a series and may be used interchangeably with "and/or," unless explicitly stated otherwise (e.g., if used in combination with "either" or "only one of").

According to some example, techniques disclosed herein may be implemented using a non-transitory computer-readable medium which stores instructions. In other examples, the instructions are obtained and/or read from a transitory computer readable medium, such as a carrier wave, a signal or any other suitable transitory medium. For example, the techniques described herein may be implemented using a computer readable medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and/or executed by a computer.

Claim 1:
A method, comprising:
configuring (<NUM>, <NUM>, <NUM>), by a first network device (<NUM>, <NUM>, <NUM>) in a high-availability cluster, a first wireless channel for a wireless control link, wherein the first network device is configured as an ingress point and an egress point for the high-availability cluster;
establishing (<NUM>, <NUM>, <NUM>), by the first network device and using the first wireless channel, the wireless control link with a second network device (<NUM>, <NUM>, <NUM>) in the high-availability cluster;
exchanging, by the first network device and via the wireless control link, control traffic to form at least one of:
a unified control plane for the high-availability cluster based on synchronizing a configuration and kernel state of control planes of three or more network devices in the high-availability cluster,
wherein the three or more network devices in the high-availability cluster include the first network device and the second network device, or
a unified routing engine for the high-availability cluster based on synchronizing a configuration and kernel state of routing engines of the three or more network devices in the high-availability cluster; configuring (<NUM>, <NUM>, <NUM>), by the first network device, a second wireless channel for a wireless fabric link; and
establishing (<NUM>, <NUM>, <NUM>), by the first network device and using the second wireless channel, the wireless fabric link with the second network device;
wherein the second network device is configured to become the ingress point for the high-availability cluster in response to a failure associated with an ingress interface of the first network device occurs; and
wherein the second network device is configured to become the egress point for the high-availability cluster in response to a failure associated with an egress interface of the first network device occurs.