Abstract: A computer-implemented method for preventing split-brain scenarios in high-availability clusters may include (1) detecting, at a first node of a high-availability cluster, a partitioning event that isolates the first node from a second node of the high-availability cluster, (2) broadcasting, from a health-status server and after the partitioning event has occurred, a cluster-health message to the first node that includes at least a health status of the second node that is based on whether the health-status server received a node-health message from the second node, and (3) reacting, at the first node and based at least in part on whether the first node received the cluster-health message, to the partitioning event such that the partitioning event does not result in a split-brain scenario within the high-availability cluster. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The techniques of this disclosure may improve multicast forwarding in an Ethernet Virtual Private Network when delivering multicast traffic to receivers on a different IP subnet than the multicast source. A method may include configuring first and second layer-2 domains to forward network traffic; configuring a first layer-3 Integrated Routing and Bridging (IRB) interface for the first layer-2 domain and a second layer-3 IRB interface for the second layer 2 domain; receiving a multicast packet from a multicast source device, the multicast source device being included in the first layer-2 domain, the multicast packet having a multicast receiver device in the second layer-2 domain; and forwarding, using the first and second layer-3 IRB interfaces, the multicast packet to the multicast receiver device, without receiving the multicast packet from another provider edge router that has been elected as the designated router on the second IRB interface for the second layer-2 domain.

Abstract: An extend ping protocol is described that allow connectivity tests to be performed for individual network interfaces of a target device without requiring network reachability between the testing device and the remote interface whose status is being queried. Moreover, the extend ping protocol supports a plurality of different probe types that allow an administrator to control how identification information within an extended ping echo request is resolved to the unreachable interfaces.

Abstract: Example embodiments described herein provide systems and methods for transmitting data packets between a protocol sender and a protocol receiver in a cloud environment, having either the protocol sender or the protocol receiver residing within a virtualized host. A protocol acceleration module may observe the data packets transmitted along the data path between the protocol sender and the protocol receiver using protocol stack configuration information of the protocol sender. The protocol acceleration module may override the protocol stack configuration information with policy-based protocol stack configuration information such that data packets transmitted from the protocol acceleration module to the protocol receiver use the policy-based protocol stack configuration information. For various embodiments, the protocol stack configuration information of the protocol sender is not modified.

Abstract: A network device receives configuration information defining one or more abstract hops for which membership is defined as those network devices that satisfy a logical combination of one or more constituent attributes. The network device determines based on network topology information, for each of the defined abstract hops, a set of network devices that qualify for membership in the abstract hop. The network device receives a request to establish a label switched path (LSP) from an ingress network device to an egress network device, wherein the request specifies, as a constraint for the LSP, a plurality of hops in a defined order, including the one or more abstract hops. The network device selects a path from the ingress network device to the specified egress network device based on the ordered abstract hop constraint, and establishes the LSP along the selected path according to the defined order of the request.

Abstract: A system may comprise a first group of switches, each switch including a first group of inputs and outputs, and a first group of controllers, each controller being independent from one another and corresponding to a switch of the first group of switches, to selectively control the switch to connect the switch's inputs with outputs. The first group of switches and controllers may be installed in a chassis. The system may comprise a second group of switches, each switch including a second group of inputs and outputs, and a second group of controllers, each controller corresponding to a switch of the second group of switches, to selectively control the switch to connect the switch's inputs with outputs. The second group of controllers may control and connect, via a group of control links, to the first group of controllers.

Abstract: A device may establish a communication session, with a client device, for monitoring a latency of a service. The device may receive, from the client device, a request for a monitored service list. The monitored service list may identify one or more services for which service latency monitoring is supported. The device may provide, to the client device, the monitored service list. The device may receive, from the client device, a service latency monitoring session request that may identify the service to be monitored. The device may establish, with the client device, the service latency monitoring session based on the service latency monitoring session request. The device may cause the service to be performed. The device may generate information for determining the latency of the service. The device may transmit, to the client device and via the service latency monitoring session, the information for determining the latency of the service.

Abstract: An apparatus may comprise a board that can mechanically support one or more components of the apparatus. The one or more components may include a processor to process a signal received or provided via the apparatus. The apparatus may comprise one or more sets of contacts via which the processor is to receive or provide the signal. The one or more sets of contacts may be associated with permitting the apparatus to function as a connector. The apparatus may comprise one or more electrical connections that provide connectivity between the processor and the one or more sets of contacts.

Abstract: A device may receive task navigation information, identify a selection of a first task, of multiple tasks, based on the task navigation information, and provide a list of a group of tasks from the multiple tasks. The list of the group tasks may be based on information identifying tasks historically selected subsequent to the selection of the first task. The device may identify a selection of a second task, of the multiple tasks subsequent to identifying the selection of the first task; and store information identifying that the second task has been selected subsequent to the first task based on identifying the selection of the second task subsequent to the selection of the first task. The information identifying that the second task has been selected subsequent to the first task may include a number of times that the second task has been selected subsequent to the first task.

Abstract: A device may receive or generate a message for routing to a destination on a communication channel. The communication channel may have been established between a source and the destination. The device may perform a first determination of policy information related to at least one of the message, the destination, or the source of the message. The policy information may describe an action for a network device to perform. The device may associate a policy token with the message. The policy token may describe or identify the policy information. The device may provide the message with the associated policy token to the network device on the communication channel to cause the network device to perform a second determination of the policy information based on the policy token, to perform the action described by the policy information, and to provide the message on the communication channel.

Abstract: In some embodiments, an apparatus includes a processor configured to receive a set of digital samples associated with a set of optical signals received at a coherent optical receiver. The set of digital samples is associated with a set of optical channels. Each optical channel from the set of optical channels is spaced from at least one adjacent optical channel from the plurality of optical channels. The processor is configured to calculate, for each optical channel from the set of optical channels, a spacing between that optical channel and at least one adjacent optical channel from the set of optical channels based on digital signal processing of the set of digital samples. The processor is configured to send a signal indicating, for each optical channel from the set of optical channels, the spacing between that optical channel and the at least one adjacent optical channel.

Abstract: The disclosed computer-implemented method may include (1) providing a framework that includes (A) a user-space component and (B) a kernel-space component, (2) identifying, via the user-space component, a series of kernel functions to be tested in kernel space, (3) identifying, via the user-space component, one or more arguments for the series of kernel functions to be tested in kernel space, and then (4) performing, via the user-space component, unit testing of a kernel from user space by (A) generating at least one message that identifies the series of kernel functions and the arguments and (B) sending the message to the kernel-space component to direct the kernel-space component to (I) populate a queue in kernel space with the series of kernel functions and the arguments and (II) sequentially execute the series of kernel functions in the queue with the arguments. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: A device may receive a route identifier that includes a range identifier or a configuration identifier. The range identifier may identify a range of broadcast domain identifiers associated with a first device. The configuration identifier may identify an Ethernet segment identifier (ESI) configuration of the first device. The device may identify the range identifier or the configuration identifier included in the route identifier. The device may select a designated forwarder from among multiple devices based on the range of broadcast domain identifiers or based on identifying the configuration identifier. The designated forwarder may be the same designated forwarder selected by at least one other device.

Abstract: In one example, an edge routing device of a service provider network includes one or more network interfaces configured to send and receive packets and a processing unit configured to retrieve, from a packet received via the one or more network interfaces, priority data from an Internet protocol (IP) header of the packet, form a first tag including a first set of data in a first priority field of the first tag, wherein the first set of data represents a first portion of the priority data, form a second tag including a second set of data in a second priority field of the second tag, wherein the second set of data represents a second portion of the priority data, encapsulate the packet with the first tag and the second tag, and forward, via the one or more network interfaces, the encapsulated packet.

Abstract: In some examples, a method includes receiving, by a first ingress network device for a network, a source tree join route message from an egress network device for the network, specifying a multicast source and a multicast group, and in response to receiving the source tree join route message, determining, by the ingress network device, whether the multicast source is multi-homed to the network via the first ingress network device and a second ingress network device for the network. The method includes, in response to determining that the multicast source is not multi-homed, forwarding traffic for the multicast source on an inclusive provider tunnel without initiating setup of a selective provider tunnel to the egress network device, and in response to determining that the multicast source is multi-homed, initiating setup of a selective provider tunnel to the egress network device and terminating forwarding multicast traffic on the inclusive provider tunnel.

Abstract: A device may receive an object. The device may determine object information for the object. The device may cause an internet search, based on the object information, to be performed to determine Internet search results. The object information may be provided as one or more Internet search queries for the Internet search. The device may receive the Internet search results based on causing the Internet search to be performed. The Internet search results may be related to the object information. The device may analyze the Internet search results to determine Internet-based object information. The device may store or provide the Internet-based object information to permit a determination as to whether the object is malicious.

Abstract: A network device may include multiple interfaces, each including a local database to store, in a first group of local records, information associated with a first group of data units sent from or received by a first one of the group of interfaces; a global database to store, in a group of global records, information associated with the first group of data units and information associated with a second group of data units sent from or received by a second one of said group of interfaces. The device may include a processor, to manage the local database and the global database; broadcast at least one of the local records to the second one of the group of interfaces; and analyze each of the local records to identify potential anomalies in the first group of data units.

Abstract: In some embodiments, a network segment within a switch fabric system includes a layer-2 flood route database and a layer-3 switch interface operatively coupled to the flood route database. The flood route database is configured to store layer-2 flood route information associated with the network segment and contains information such as a set of port identifiers and a set of status indicators. Each port identifier identifies a particular port within the network segment and each status indicator is uniquely associated with a particular port identifier. The layer-3 switch interface associated with the network segment is automatically activated when the flood route database contains at least one valid port identifier and the status indicator associated with at least one port identifier is active. This can allow data traffic to flow between separate network segments within the switch fabric system.

Abstract: This disclosure describes techniques for utilizing VXLANs within a network, such as a data center, for transporting L2 customer communications. Moreover, the disclosure describes techniques for auto-discovering, for each VXLAN, a corresponding replication node for replicating and distributing unknown destination, broadcast, and multicast frames to VXLAN Tunnel Endpoints (“VTEPs”) within the data center. Further, the techniques facilitate, by the replication node, discovery and auto-registration of the VTEPs for the respective customer network. As such, the techniques may facilitate configuration of VXLANs without necessarily relying on multicast protocols to provide such functionality. In this way, the techniques described herein may be used to supplement or even replace reliance on multicast protocols, such as the Protocol Independent Multicast (PIM) protocol, when configuring VXLANs within a network.

Abstract: In some embodiments, an apparatus comprises a schedule module within a switch fabric system. At a first time, the schedule module is configured to access a list of status indicators associated with a group of egress port indicators. The list of status indicators includes a set of status indicators each of which has a value greater than a threshold. The schedule module is configured to randomly select a status indicator from the set of status indicators and configured to reduce the value of the selected status indicator. The schedule module is then configured to send the egress port indicator associated with the selected status indicator such that a data cell is sent from an egress port associated with that egress port indicator. At a second time, when the value of every status indicator from the list of status indicators is not greater than the threshold, the schedule module is configured to increase the value of every status indicator above the threshold.