Abstract: In general, techniques are disclosed for automatic discovery and load balancing of virtual service instances of a plurality of cloud data centers within a Software Defined Networking (SDN) or a Network Functions Virtualization (NFV) environment. In one example, a global load balancing device (GLB) of a first cloud data center receives, from an SDN controller, address information for a first set of virtual service instances provided by the first cloud data center and a hostname of a domain for which to perform load balancing across the plurality of cloud data centers. The GLB device requests, from a domain name server (DNS) for the domain, address information for other sets of virtual service instances provided by other cloud data centers. Further, the GLB device applies a load balancing algorithm to direct network traffic to one or more of the virtual service instances provided by the plurality of cloud data centers.

Abstract: A network device may receive, from a first neighbor network device, information indicating that the network device is to remove a bit indexed explicit replication (BIER) header from a multicast packet prior to transmitting the multicast packet to the first neighbor network device. The network device may receive the multicast packet from a second neighbor network device, where the multicast packet includes the BIER header and is to be transmitted to the first neighbor network device, and where the network device, the first neighbor network device, and the second neighbor network device are included in a same BIER domain. The network device may remove the BIER header from the multicast packet, and may transmit the multicast packet to the first neighbor network device after removing the BIER header from the multicast packet.

Abstract: A first device may receive network traffic including a first label. The first label may be an inclusive multicast label associated with a second device. The second device may be a designated forwarder for an Ethernet segment. The first device may determine a second label based on receiving the network traffic including the first label. The second label may be used to route the network traffic to a customer edge device, via a third device, rather than the second device. The third device may be a non-designated forwarder for the Ethernet segment. The first device may provide the network traffic, including the second label, to the third device to permit the third device to provide, via the Ethernet segment, the network traffic to the customer edge device based on the second label when a failure occurs in association with the second device.

Abstract: The disclosed apparatus may include (1) a power distribution module that (A) distributes power to a network device that forwards traffic within a network and (B) includes a series of interlock blocks keyed to (I) enable power supply modules whose electrical ratings satisfy a certain threshold to be installed to the network device and (II) prevent other power supply modules whose electrical ratings do not satisfy the certain threshold from being installed to the network device and (2) at least one power supply module that (A) has an electrical rating that satisfies the certain threshold, (B) includes a flange that is keyed to fit between the interlock blocks of the power distribution module, and when installed to the network device by way of the power distribution module, (C) provides power to the network device that forwards traffic within the network. Various other apparatuses, systems, and methods are also disclosed.

Abstract: A device may receive configuration information that identifies a set of server devices. The device may send, to the set of server devices, a request communication associated with determining a status of the set of server devices after receiving the configuration information. The device may process a response communication from the set of server devices after sending the request communication to the set of server devices. The request communication and the response communication may be associated with each other. The device may dynamically monitor the status of the set of server devices after processing the response communication. A first subset of the set of server devices may be monitored based on traffic from the first subset of the set of server devices. A second subset of the set of server devices may be monitored based on an additional response communication from the second subset of the set of server devices.

Abstract: A device may receive a first network topology message from a network device. The first network topology message may include first network topology information associated with the network device in a first set of fields of the first network topology message. The device may generate a second network topology message. The second network topology message may include second network topology information associated with the device in a first set of fields of the second network topology message. The first set of fields of the second network topology message may correspond to the first set of fields of the first network topology message. The second network topology message may include the first network topology information associated with the network device in a second set of fields of the second network topology message. The device may provide the second network topology message.

Abstract: A device may receive information that identifies a bandwidth value of a label-switched path (LSP) that includes a protected link or a protected node. The device may determine a bypass LSP bandwidth threshold based on the bandwidth value. The device may determine a set of path bandwidth values associated with a set of paths. The device may compare the set of path bandwidth values and the bypass LSP bandwidth threshold. The device may select a path, of the set of paths, based on comparing the set of path bandwidth values and the bypass LSP bandwidth threshold. The device may generate a bypass LSP using the path.

Abstract: A device may receive a firewall filter entry that includes one or more match conditions associated with filtering network traffic. The device may identify an access control list (ACL) template associated with the firewall filter entry. The ACL template may be associated with a template type. The device may identify one or more rules, for verifying the firewall filter entry, based on the template type associated with the ACL template. The device may verify the firewall filter entry using the one or more rules. The device may determine a hardware resource, for storing the firewall filter entry, based on the template type and based on verifying the firewall filter entry. The device may store the firewall filter entry using the hardware resource of the device.

Abstract: In general, techniques are described for configuring and managing virtual networks. For example, a distributed virtual network controller is described that configures and manages an overlay network within a physical network formed by plurality of switches. A plurality of servers are interconnected by the switch fabric, each of the servers comprising an operating environment executing one or more virtual machines in communication via the overlay networks. The servers comprises a set of virtual switches that extends the overlay network as a virtual network to the operating environment of the virtual machines.

Abstract: The disclosed computer-implemented method may include (1) creating, at a proxy node within an IP network, a proxy group that includes a plurality of network nodes within a subnet of the IP network that are represented by a pseudo MAC address, (2) receiving a neighbor solicitation from a network node included in the proxy group, (3) identifying, within the neighbor solicitation, a link-layer address of the network node that sent the neighbor solicitation, (4) modifying the neighbor solicitation by replacing the link-layer address of the network node with the pseudo MAC address of the proxy group, and then (5) forwarding the modified neighbor solicitation to another network node included in the proxy group to facilitate completion of an NDP process in which the other network node responds to the modified neighbor solicitation with a neighbor advertisement proxied by the proxy node. Various other methods, systems, and apparatuses are also disclosed.

Abstract: A device may include one or more processors to receive, from at least one user device, multiple network packets. The device may identify, from the network packets, a set of individual network packets, the set including at least two of the received network packets that are destined for a particular destination device. The device may generate, based on the set of individual network packets, a batch packet, the batch packet including: the set of individual network packets, data identifying the number of individual network packets included in the set, and offset data for each of the individual network packets included in the batch packet. Based on the batch packet, the device may perform an action.

Abstract: In some examples, a computing device comprises a virtual network endpoint; a network interface card (NIC) comprising a first hardware component and a second hardware component, wherein the first hardware component and the second hardware component provide separate packet input/output access to a physical network interface of the NIC, wherein the NIC is configured to receive a packet inbound from the physical network interface; and a virtual router to receive the packet from the NIC and output, using the first hardware component, in response to determining a destination endpoint of the packet is the virtual network endpoint, the packet back to the NIC, wherein the NIC is further configured to switch, in response to receiving the packet from the virtual router, the packet to the virtual network endpoint and to output, using the second hardware component, the packet to the virtual network endpoint.

Abstract: A device receives policy information associated with configuring a network, and receives network information associated with the network. The device determines, based on the network information, that the policy information is associated with implementation of egress peer engineering techniques for the network, and identifies, based on the network information, a first set of destinations of the network that satisfies a particular threshold bandwidth. The device assigns costs and bandwidths to the first set of destinations based on the policy information, and monitors bandwidth utilization by the first set of destinations. The device processes information associated with the first set of destinations, with a model, based on the bandwidth utilization and based on the egress peer engineering techniques, to generate a first set of ranked destinations, and causes traffic in the network to be managed based on the first set of ranked destinations and the policy information.

Abstract: A system is configured to determine a first power level of a first signal output from a first modulator, and determine a second power level of a second signal output from a second modulator. The first signal may include a first optical signal associated with a particular polarization orientation, and the second signal may include a second optical signal associated with the particular polarization orientation. The system is configured to determine a relationship between the first power level and the second power level, and to set, based on the relationship between the first power level and the second power level, a reverse bias voltage associated with the first modulator, where the reverse bias voltage may be used to control the first power level of the first signal.

Abstract: This disclosure describes techniques for analyzing information generated as a result of monitoring resources within computing environments. In one example, this disclosure describes a method that includes observing a plurality of alerts generated in response to monitoring resources associated with a plurality of connected elements within a network; determining a plurality of occurrence counts; determining a plurality of concurrent occurrence counts, wherein each of the plurality of concurrent occurrence counts represents a count of concurrent occurrences of two or more of the alerts in the set of historical alerts; and identifying one or more root cause alerts, wherein the one or more root cause alerts are determined based on the plurality of occurrence counts and the plurality of the concurrent occurrence counts, and wherein the one or more root cause alerts are a subset of the plurality of alerts.

Abstract: In some embodiments, an apparatus includes a switch fabric having at least a first switch stage and a second switch stage, an edge device operatively coupled to the switch fabric and a management module. The edge device is configured to send a first portion of a data stream to the switch fabric such that the first portion of the data stream is received at a queue of the second switch stage of the switch fabric via the first switch stage of the switch fabric. The management module is configured to send a flow control signal configured to trigger the edge device to suspend transmission of a second portion of the data stream when a congestion level of the queue of the second switch stage of the switch fabric satisfies a condition in response to the first portion of the data stream being received at the queue.

Abstract: A network device may determine, based on at least one network egress characteristic associated with a network device, a measure of priority associated with a network address. The network device may provide the measure of priority to a plurality of other routers, determine that a particular network egress characteristic of the at least one network egress characteristic has changed, and update the measure of priority based on the particular network egress characteristic. Based on the updated measure of priority, the network device may perform an action.

Abstract: A device may receive a set of border gateway protocol labels via a set of corresponding border gateway protocol messages. A border gateway protocol label, of the set of border gateway protocol labels, may be associated with a label descriptor attribute. The label descriptor attribute being associated with providing information regarding a forwarding semantic associated with the border gateway protocol label. The device may select the border gateway protocol label for routing network traffic toward a network device associated with the border gateway protocol label based on the label descriptor attribute. The device may route the network traffic toward the network device based on the border gateway protocol label and after selecting the border gateway protocol label.

Abstract: A device may receive a digital voucher, a customer certificate, and configuration information for automatically configuring the device. The digital voucher may include a first customer identifier that identifies a customer associated with the device and a device identifier that identifies the device. The customer certificate may include a second customer identifier that identifies the customer and a customer public key associated with the customer. The configuration information may include information that identifies a configuration for automatically configuring the device. The device may validate at least one of the digital voucher, the customer certificate, or the configuration information. The device may configure the device, using the configuration, based on validating at least one of the digital voucher, the customer certificate, or the configuration information.

Abstract: In one example, a network management system (NMS) and method models services in a network. The NMS identifies externally mapped attributes in a vendor neutral yang model of a network service, assigns an attribute type to one or more of the externally mapped attributes, wherein assigning includes determining, by a learning system, the attribute type of one or more of the externally mapped attributes based on an analysis of attribute types assigned to the externally mapped attributes of other network services, constructs a separate dependency graph for each of the externally mapped attributes and builds a separate hidden service model for each of the externally mapped attributes, wherein the externally mapped attribute for each hidden service model is a merge attribute for that hidden service model.