Abstract: A network device may receive, from a source device, an option request that includes a source address of the source device and a destination address of a destination device, wherein the network device is associated with an Internet protocol version 6 (IPv6) network. The network device may identify a map code that is associated with an address translation for traffic associated with the destination device and may determine, based on identifying the map code, a source prefix code and a destination prefix code for the address translation. The network device may determine a source IPv6 prefix and a destination IPv6 prefix for the address translation based on the source prefix code and the destination prefix code and may provide, to the source device, an option response to the option request to permit the source device to use the source IPv6 prefix and the destination IPv6 prefix for the traffic.

Abstract: A first network device may receive a request associated with forming a high-availability cluster with a second network device, wherein the first network device is associated with a session of a user device. The first network device may determine, based on authorization information associated with the first network device, that the first network device is authorized to form the high-availability cluster. The first network device may configure communication links with the second network device to form the high-availability cluster. The first network device may synchronize, with the second network device, session information associated with the session via the communication links. The first network device may route session traffic of the session to the second network device and a data network to enable the user device to receive a high-availability service during the session.

Abstract: In general, various aspects of the techniques are described in this disclosure for distributed label assignment for labeled routes. In one example, a method includes obtaining, by a first thread of a plurality of execution threads for at least one routing protocol process executing on processing circuitry of a network device, an allocation of first labels drawn from a label space for a network service; adding, by the first thread, the first labels to a first local label pool for the first thread; generating, by the first thread, after obtaining the allocation of the first labels, a labeled route comprising a route for the network service and a label assigned by the first thread from the first local label pool; and outputting, by the network device, the labeled route.

Abstract: Problems associated with providing a large Clos network having at least one top of fabric (ToF) node, a plurality of internal nodes, and a plurality of leaf nodes may be solved by: (a) providing L2 tunnels between each of the leaf nodes of the Clos and one or more of the at least one ToF node to ensure a non-partitioned IGP L2 backbone, and (b) identifying the L2 tunnels as non-forwarding adjacencies in link state topology information stored in ToF node(s) and leaf node(s) such that the L2 tunnels are not used for forwarding traffic. Tunnel formation is prevented over L2.

Abstract: A device determines traffic and costs associated with a network that includes network devices interconnected by links, and determines traffic assignments for the network based on the traffic and the costs associated with the network. The device determines tunnel use for the network based on the traffic assignments, and determines peer link use for the network based on the tunnel use. The device determines costs associated with the traffic assignments, the tunnel use, and the peer link use for the network, and generates traffic plans based on the traffic assignments, the tunnel use, the peer link use, and the costs associated with the traffic assignments, the tunnel use, and the peer link use. The device causes one of the traffic plans to be implemented in the network by the network devices and the links.

Abstract: An ingress fabric endpoint coupled to a switch fabric within a network device reorders packet flows based on congestion status. In one example, the ingress fabric endpoint receives packet flows for switching across the switch fabric. The ingress fabric endpoint assigns each packet for each packet flow to a fast path or a slow path for packet switching. The ingress fabric endpoint processes, to generate a stream of cells for switching across the switch fabric, packets from the fast path and the slow path to maintain a first-in-first-out ordering of the packets within each packet flow. The ingress fabric endpoint switches a packet of a first packet flow after switching a packet of a second packet flow despite receiving the packet of the first packet flow before the packet of the second packet flow.

Abstract: A network device, associated with peer network devices, may receive policy information for a protocol; and compute a first update message based on information regarding a route associated with the policy information. The network device may determine that an upper utilization threshold for one or more of peer queues, associated with the peer network devices, is not satisfied; and write the first update message to the peer queues based on determining that the upper utilization threshold is not satisfied. The network device may compute a second update message based on the information regarding the route; determine that the upper utilization threshold for one or more of the peer queues is satisfied; and pause writing the second update message to the peer queues based on the upper utilization threshold being satisfied. The network device may permit the peer network devices to obtain data from corresponding ones of the peer queues.

Abstract: A network device may receive a first data packet. The network device may determine that a level of available computing resources satisfies a threshold level. The network device may perform a secure socket layer (SSL) proxy function based on the level of available computing resources satisfying the threshold level. The network device may receive a second data packet. The network device may determine that the level of available computing resources fails to satisfy the threshold level. The network device may determine a security characteristic associated with the second data packet. The network device may determine a security rating associated with the second data packet based on the security characteristic. The network device may selectively perform the SSL proxy function based on the security rating.

Abstract: The techniques describe example network systems providing core-facing designated forwarder (DF) election to forward multicast traffic into an EVPN of a core network. For example, a first PE device of a plurality of PE devices participating in an EVPN comprises one or more processors operably coupled to a memory, wherein the one or more processors are configured to: determine that a first multicast traffic flow has started for the first PE device; in response, send a source-active (SA) route to indicate the first multicast traffic flow has started for the first PE device; receive, from a second PE device, a second SA route that indicates that a second multicast traffic flow has started for the second PE device; and perform an election of a core-facing DF from among the first PE device and second PE device, wherein the core-facing DF is configured to forward the multicast traffic into the EVPN.

Abstract: Disclosed is a network management system that provides an interface to enable diagnostics and troubleshoot of a remotely managed multi-site network. Some embodiments provide a natural language interface, while other embodiments provide a chatbot type interface that communicates with a technician via traditional text information on a display screen. The diagnostic and troubleshooting capabilities search a central data store that receives device property information from each site of the multi-site network. Based on devices or users that match portions of the entity, queries to the data store are initiated to obtain additional data on the devices. A response to the query is then provided based on the properties of the devices.

Abstract: Disclosed are embodiments for improving remote diagnostics of a computer system. Some embodiments obtain operational parameter values and log data from a plurality of network devices, and provide the operational parameter values and log data to a machine learning model. The model is trained to identify a root cause of a degradation of the computer system based on the operational parameter values and log data, and to provide recommendations of log data level settings for the network devices. If the model identifies a root cause of the degradation with sufficient confidence, a remedial action is identified and applied to the computer system. If the confidence level is insufficient, log data level settings of the network devices are modified based on the recommendations of the model. This process is performed iteratively, for example, such that the model receives log data based on its recommended log data levels, until a root cause is identified with sufficient confidence.

Abstract: This disclosure describes techniques that include collecting flow data associated with communications between network devices, and determining, based on the flow data, one or more virtual networks over which the communications are taking place. In one example, this disclosure describes a system configured to perform operations comprising: storing virtual network configuration information associated with a first virtual network and a second virtual network established within a network; collecting underlay flow data associated with communications between a first server and a second server, wherein each of the first server and the second server are implemented as bare metal servers; determining, based on the underlay flow data and the stored virtual network configuration information, that the first server and the second server have communicated over the first virtual network; and generating a user interface.

Abstract: A network device may assign, to a port of a plurality of ports on the network device, a precision timing protocol (PTP) port priority for PTP communications between the network device and another network device. The network device and the other network device may be communicatively connected via a plurality of links in a link aggregation group (LAG). Each port, of the plurality of ports, may be associated with a respective link, of the plurality of links, in the LAG. The network device may generate a link layer discovery protocol (LLDP) frame that includes information identifying the PTP port priority assigned to the port. The network device may transmit the LLDP frame to the other network device to identify, to the other network device, the PTP port priority.

Abstract: A disclosed method may include (1) generating a configuration file that represents a specific configuration of a network device included in a network, (2) storing the configuration file that represents the specific configuration of the network device among a set of configuration files available via an NMS, (3) assigning to the configuration file via the NMS, a configuration identifier that uniquely identifies the configuration file among the set of configuration files available via the NMS, (4) receiving, via the NMS, a rollback request to restore the network device to the specific configuration based at least in part on the configuration identifier, and then in response to receiving the rollback request, (5) restoring the network device to the specific configuration based at least in part on the configuration file. Various other systems, methods, and computer-readable media are also disclosed.

Abstract: A disclosed apparatus for accomplishing such a task may include (1) a circuit board incorporated into a module designed for insertion into slots of computing devices, (2) at least one conductive contact disposed on the circuit board, (3) a counter circuit disposed on the circuit board and communicatively coupled to the conductive contact, wherein the counter circuit comprises (A) a signal-change detector that detects signal changes as the module is inserted into one of the slots of the computing devices and (B) a counter device that maintains a dynamic count indicative of a number of times that the module has been inserted into one of the slots of the computing devices based at least in part on the signal changes, (4) a battery electrically coupled to the counter circuit, wherein the battery powers the counter device prior to the insertion. Various other apparatuses, systems, and methods are also disclosed.

Abstract: A controller device includes a memory configured to store a tree structure comprising a plurality of nodes, wherein the tree structure comprises a set of sub-structures, and wherein the tree structure defines a configuration of a network device of a set of network devices such that each node of the plurality of nodes corresponds to a respective resource of the network device. Additionally, the controller device includes processing circuitry configured to receive an instruction to update the configuration of the network device, wherein the instruction to update the configuration of the network device indicates a node of the set of nodes corresponding to the update; and verify, based on a sub-structure of the set of sub-structures corresponding to the node indicated by the instruction, the instruction to update the configuration of the network device.

Abstract: A network device may define a container LSP that includes multiple member LSPs. Each of the multiple member LSPs defines a path from the network device through a network of a plurality of network devices. The network device may receive traffic that includes multiple packet flows. The network device may identify a first set of packet flows that are intolerant to packet reordering. The network device may identify a second set of packet flows that are tolerant to packet reordering. The network device may distribute each of the first set of packet flows to a corresponding one of the multiple member LSPs. The network device may process the second set of packet flows to determine a distribution sequence for the second set of packet flows. The network device may distribute the second set of packet flows among the multiple member LSPs based on the distribution sequence.

Abstract: The disclosure describes techniques for detecting network measurement inaccuracies through the detection of sender delays or packet drops. For example, a sender device of a test packet may determine whether the sender device is experiencing any issues in sending the test packet to a receiver device and notify a controller of the issues such that the controller may generate an indication that one or more Key Performance Indicator (KPI) measurements based on the test packets from the sender device are inaccurate and/or untrustworthy, remove the inaccurate KPI measurements, and/or adjust the inaccurate KPI measurements.

Abstract: Techniques are described for providing end-to-end segment routing paths across metropolitan area networks. For example, a method comprises receiving, by an area border router (ABR) connected to one or more metropolitan area networks and a core network, a packet including a segment routing label stack including at least a label of the ABR, a context label associated with a routing instance of the ABR, and a subsequent label identifying a device in the segment routing path, determining, from a lookup of the context label in the metro routing table, a table next hop to the core routing table (or metro routing table); in response to determining the table next hop, determining, from a lookup of the subsequent label in the core routing table (or metro routing table), a next hop in the segment routing path; and sending, by the ABR, the packet toward the device in the segment routing path.

Abstract: An example network device includes a primary node and a secondary node. The primary node includes one or more processors implemented in circuitry and configured to receive a message from a collector device requesting to subscribe to statistics of a metrics streaming session; initiate a telemetry session for sending the statistics to the collector device; replicate data of the telemetry session to the secondary node; and send the data of the telemetry session to the collector device. In this manner, in the event of the switchover, the secondary node may act as the primary node and resume the telemetry session. That is, the secondary node, acting as a primary node following the switchover, may receive statistics data from one or more sensors related to the metrics streaming session, and send telemetry session data, representative of the statistics data, to the collector device as part of the telemetry session.