Abstract: A network device operable as a provide edge router is described. The network device comprises one or more processors operably coupled to a memory; a configuration interface configured for execution by the one or more processors to receive configuration data configuring the network device as a provider edge router of an intermediate layer 3 network to provide multi-homed layer 2 virtual bridge connectivity to a customer edge device using an active-standby mode of operation; and a routing process configured for execution by the one or more processors to send, to a remote provider edge router in response to determining the network device is able to send layer 2 packets to the customer edge device, a route advertisement that includes a static route specifying a layer 3 address of the customer edge device as a next-hop for a layer 3 subnet.

Abstract: A hypervisor of a device may receive information that identifies a virtual machine that is to use a universal asynchronous receiver/transmitter (UART) of the device. The hypervisor may map a set of first register addresses, associated with a physical UART port, and a set of variable addresses. The hypervisor may map a second set of register addresses, associated with a virtual UART port of the virtual machine, and the set of variable addresses. The hypervisor may permit the virtual machine to communicate, with a remote device, using the physical UART port based on mapping the set of second register addresses and the set of variable addresses.

Abstract: Techniques are described for automatic discovery of two or more virtual service instances configured to apply a given service to a packet in a software-defined networking (SDN)/network functions virtualization (NFV) environment. Virtual service instances may be deployed as virtual entities hosted on one or more physical devices to offer individual services or chains of services from a service provider. The use of virtual service instances enables automatic scaling of the services on-demand. The techniques of this disclosure enable automatic discovery by a gateway network device of virtual service instances for a given service as load balancing entities. According to the techniques, the gateway network device automatically updates a load balancing group for the given service to include the discovered virtual service instances on which to load balance traffic for the service. In this way, the disclosed techniques provide auto-scaling and auto-discovery of services in an SDN/NFV environment.

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: In general, the disclosure describes techniques for communicating multicast group leave requests between two or more load-balanced, multi-homed PE routers included in an Ethernet Virtual Private Network (EVPN). The techniques of the disclosure enable the two or more PE routers to synchronize IGMP state and routing information amongst one another to ensure that the one of the multi-homed PE routers elected as the designated forwarder (DF) ceases forwarding the multicast group traffic to the CE router, even if it is not the PE router that receives the IGMP leave request.

Abstract: In some examples, an electronic device includes a printed circuit board (PCB) device that includes a first trace electrically connected to a first pad of a first trace via on a first layer and a second trace electrically connected to a second pad of a second trace via on a second layer. In some examples, the PCB device also includes four ground pads on the first layer and an antipad surrounding the two trace vias, where a first ground pad is positioned between the first trace and the second trace, where the first ground pad and the second ground pad are approximately symmetrically positioned about a perpendicular bisector of a line from the first pad to the second pad, and wherein the third ground pad and the fourth ground pad are approximately symmetrically positioned about the perpendicular bisector of the line from the first pad to the second pad.

Abstract: The disclosed apparatus may include (1) providing a framework that enables a customer entity of a service provider to configure, via a customer portal, a network device of the service provider that directs network traffic of the customer entity, (2) creating, for the customer entity by way of the framework, a virtual network that includes at least a portion of the network device of the service provider, (3) detecting an attempt by the customer entity to configure at least a portion of the virtual network via the customer portal, and then in response to detecting the attempt by the customer entity, (4) performing a configuration operation that configures the portion of the virtual network as directed by the customer entity via the customer portal. Various other apparatuses, systems, and methods are also disclosed.

Abstract: Techniques are described for varying a bandwidth constraint at one or more hops along a path of a sub-label-switched path (sub-LSP) of a multi-path label-switched path (MP-LSP). The techniques include computing, by an ingress router, a plurality of paths for a plurality of sub-LSPs of a MP-LSP and outputting, by the ingress router, for each path of the plurality of paths, a respective resource reservation request message to establish a respective sub-LSP of the plurality of sub-LSPs, each respective resource reservation request message including an indication of an explicit route, a tunnel identifier indicating the MP-LSP, an identifier for the respective sub-LSP, an indication of a per-hop bandwidth constraint that corresponds to a respective incoming per-hop bandwidth constraint of the plurality of incoming per-hop bandwidth constraints, and one or more instructions to modify the indication of the per-hop bandwidth constraint.

Abstract: In one example, a network management system (NMS) is configured to enable a target network device to support a particular network service based on service configuration information for the particular network service. The service configuration information may include information about nodes in a vendor neutral model that need to be added or modified in order to support the particular network service. The NMS determines similarity scores between nodes in a vendor neutral model and nodes in a target device specific model. Based on the similarity scores, the NMS generates a mapping from the vendor neutral model to the target device specific model. Using the mapping, the NMS may configure a target device to support the particular service.

Abstract: An apparatus comprises a routing module configured to receive a data unit having a code indicator. The routing module is configured to identify a virtual destination address based on the code indicator. The routing module is also configured to replace a destination address of the data unit with the virtual destination address to define a modified data unit. The routing module is further configured to send the modified data unit.

Abstract: A device may receive information identifying a set of tasks to be executed by a microservices application that includes a plurality of microservices. The device may determine an execution time of the set of tasks based on a set of parameters and a model. The set of parameters may include a first parameter that identifies a first number of instances of a first microservice of the plurality of microservices, and a second parameter that identifies a second number of instances of a second microservice of the plurality of microservices. The device may compare the execution time and a threshold. The threshold may be associated with a service level agreement. The device may selectively adjust the first number of instances or the second number of instances based on comparing the execution time and the threshold.

Abstract: A first device may determine an Internet Protocol version R (IPvR) interface address associated with a second device, where R is greater than or equal to four. The first device and the second device may be associated with an external border gateway protocol peering session. The first device may generate an Internet Protocol version S (IPvS) interface address based on the IPvR interface address associated with the second device, where S is greater than or equal to six and different than R. The first device may store the IPvS interface address in a routing table. The first device may receive, from the second device, a service route that includes the IPvS interface address, and may provide the service route to a third device. The first device may provide a labeled route to the third device. The labeled route may include a label associated with the IPvS interface address.

Abstract: The disclosed computer-implemented method may include (1) identifying a plurality of routes that lead to a plurality of eBGP peers that represent portions of network paths, (2) assigning a plurality of labels to the routes that lead to the eBGP peers, (3) advertising the labels to an iBGP peer to enable the iBGP peer to make routing decisions identified by the labels, (4) receiving, from the iBGP peer, traffic that is destined for an endpoint device and includes a label that (A) was selected by the iBGP peer and (B) corresponds to a specific route that leads to a specific eBGP peer, and then (5) forwarding the traffic to the endpoint device along the specific route that leads to the specific eBGP peer based at least in part on the label selected by the iBGP peer. Various other methods, systems, and apparatuses are also disclosed.

Abstract: The disclosed apparatus may include (1) a cage that houses at least one field-replaceable electronic module that, when operational, emits heat within a computing device, wherein the cage comprises (A) a front entry side that facilitates installation of the field-replaceable electronic module and (B) a back side that is located opposite the front entry side, (2) a heatsink that removably interfaces with the field-replaceable electronic module when the field-replaceable electronic module is installed in the cage and (3) a spring mechanism that (A) is coupled to the back side of the cage and (B) applies force to the heatsink such that the heatsink (I) is pressed against the field-replaceable electronic module and (II) establishes thermal contact with the field-replaceable electronic module to facilitate heat transfer from the field-replaceable electronic module to the heatsink. Various other apparatuses, systems and methods are also disclosed.

Abstract: The disclosed apparatus may include (1) a switch-fabric circuit board that includes at least one switch-fabric circuit that facilitates communicative connectivity between packet forwarding engines within a rackmount network device and (2) a plurality of optic circuit boards that are each communicatively connected to the switch-fabric circuit board. In this example, the optic circuit boards may include a plurality of packet forwarding engines that are communicatively connected to one another via the switch-fabric circuit and a plurality of communication ports that are each communicatively connected to at least one of the packet forwarding engines. In addition, the switch-fabric circuit board may reside between at least two of the optic circuit boards within the rackmount network device. Various other apparatuses, systems, and methods are also disclosed.

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: An apparatus includes a memory and a processor operatively coupled to the memory. The processor is configured to partition a set of ports of an optical multiplexer into a set of port groups including a first port group having a first set of ports and a second port group having a second set of ports mutually exclusive from the first set of ports. The processor is configured to associate the first port group with a first router and associate the second port group with a second router. When the optical multiplexer is operatively coupled to the first router and the second router, the first router is operatively coupled to the optical multiplexer via the first set of ports and not the second set of ports, and the second router is operatively coupled to the optical multiplexer via the second set of ports and not the first set of ports.

Abstract: A first device may receive information that assigns a function related to network traffic associated with a content delivery network. The first device may implement the function based on the information that assigns the function. The first device may receive the network traffic from the content delivery network and may provide the network traffic to a subscriber device. The first device may provide, to a second device, information associated with the network traffic based on implementing the function. The second device may manage a subscriber session associated with the subscriber device based on the information associated with the network traffic.

Abstract: Techniques are described for performing subscriber aware two-way active measurement protocol (TWAMP) data session provisioning between two endpoints in a computer network. For example, the disclosed techniques include extending TWAMP control messaging to include a communication mode for negotiating subscriber-aware TWAMP data monitoring. If the communication mode is supported by both endpoints, a subscriber identifier is specified when a TWAMP data session is provisioned (negotiated) over the control session. The disclosed techniques further include extending TWAMP data messaging to include the subscriber identifier in each test packet for the data session. In this way, each of the endpoints may identify a subscriber corresponding to one or more received TWAMP test packets based on the subscriber identifier included in the received TWAMP test packets.

Abstract: In one example, a network device is configured as a leaf node of an interconnected topology that defines a plurality of network paths from the network device to each of a plurality of other leaf nodes of the interconnected topology. The network device includes one or more processing units configured to forward a first packet of a packet flow along a first network path of the plurality of network paths, after receiving a second packet of the packet flow, determine an inactivity interval for the packet flow that represents an amount of time between receipt of the first packet and receipt of the second packet, compare the inactivity interval to a threshold, and when the inactivity interval is greater than the threshold, forward the second packet along a second network path of the plurality of network paths, wherein the second network path is different than the first network path.