Abstract: First and second network devices may be configured to multihome a host. The first network device may advertise a first MAC and IP advertisement route indicative of a first link between the first network device and the host. The second network device may advertise a backup MAC and IP advertisement route indicative of a second link between the second network device and the host. Based on the backup MAC and IP advertisement route, the first network device may store a backup path for reaching the host via the second network device. After failure of the first link, the first network device may forward traffic destined for the host based on the stored backup path.

Abstract: A method for managing a network by a network monitoring system, wherein the network comprises a plurality of network devices, the method comprising receiving, by the network monitoring system, in-band network telemetry (INT) data from a network device of the plurality of network devices, updating a latency model of the network using the INT data to obtain an updated latency model, identifying a congestion point in the network using the updated latency model and at least a portion of the INT data, validating the congestion point; and initiating a remediation action based on the validation.

Abstract: Embodiments of the present disclosure include systems and methods for providing a flexible network management system for configuring network devices. A studio definition specifying a set of configuration parameters for configuring network devices in a plurality of network devices is received. A workspace definition associated with the studio definition, the workspace definition specifying values for a subset of the set of configuration parameters is received. A set of build operations on the studio definition and the workspace definition are performed to generate a set of configuration commands for a subset of the plurality of network devices. The subset of the plurality of network devices are configured based on the set of configuration commands.

Abstract: Packet processing in a EVPN L2 MPLS deployment includes performing tag editing operations in the egress pipeline. More particularly, tag manipulation is based on the egress port. Packet processing further includes performing ESI label selection in the egress pipeline, and includes selecting the ESI label based on the ingress port where the ingress port can be a physical port or a subinterface configured on a physical port.

Abstract: A method, device, and computer readable medium for managing overheat behavior in a network device. The method includes determining that a first temperature exceeds a threshold by at least one temperature sensor disposed in a network device. The method includes logging a temperature sensor name of the at least one temperature sensor, the first temperature, and actions taken prior to determining that the first temperature exceeds the threshold. The method further includes disabling network device capabilities and enabling a subset of network device capabilities after powering cycling the network device.

Abstract: An EVPN network device may advertise an EVPN IMET (type-3) route in a corresponding message to one or more peer EVPN network devices. The EVPN IMET route advertisement message may include an E-tree extended community indicating a leaf or root designation of a locally attached site at the advertising EVPN network device. The inclusion of the E-tree extended community in the EVPN IMET route advertisement message may provide desired traffic handling for implementing an EVPN E-tree service such as handling of BUM traffic.

Abstract: In general, embodiments relate to a method for managing a network device. The method includes detecting a change of at least one physical port on the network device; and in response to detecting the change, disabling the at least one physical port, wherein disabling the at least one physical port prevents the at least one physical port from being allocated to any logical port on a network processor in the network device.

Abstract: Systems and methods that allow configuration of a path at a network device using a representative user visible interface for that path are disclosed. A feature of this path may thus be configured using this representative user visible interface through a configuration interface of the network device. When a feature for the path is configured by reference to its corresponding representative user visible interface, the interfaces of that path that correspond to that feature can be determined and the configuration for that feature can be applied to interfaces of the path, even where those interfaces reside in different subdomains.

Abstract: A method for generating an application-aware virtual topology (AAVT) routing table for a network device among network devices connected via a wide area network is provided. The method is executed by a network controller connected to the network and includes: receiving, from the network devices, path information of the network devices; generating, using the path information, an underlay graph specifying a path topology of the network device; generating, based on the path topology specified in the underlay graph, the AAVT routing table for the network device where the AAVT routing table includes a set of paths; and transmitting, in response to generating the AAVT routing table, the AAVT routing table to the network device to cause the network device to program the set of paths.

Abstract: A network device includes multiple interconnected network chips where the packet processing functionality is distributed between ingress and egress pipelines. TCP MSS clamping can be implemented in the egress pipeline. Processing in the egress pipeline can identify the presence of a TCP MSS value in the packet. The egress pipeline can compare the packet TCP MSS value with a user configured TCP MSS value. The egress pipeline can replace the packet TCP MSS value with the user configured TCP MSS value if the former is greater than the latter, and recompute a checksum. The packet with the replaced TCP MSS value and replaced checksum is then forwarded from the switch toward its eventual destination.

Abstract: Systems, methods and products for providing a centralized view of media production devices connected to a network. An example method includes identifying a set of media production devices connected to a network and compiling a list of the identified devices. Network position information is then collected for the identified devices using resources including IS-04 device registries, LLDP tables, FDB tables and ARP tables. For each of the identified devices, a corresponding connection to the network is identified and corresponding network statistics are collected for each of the identified connections of the devices to the network, where the network statistics are correlated to the identified devices. A list of the identified devices is then stored in a searchable format with the corresponding network statistics, and particular ones of the devices may be highlighted to denote conditions indicated by the corresponding network statistics.

Abstract: A method for authenticating an origin of a network device. The method includes reading one or more encrypted parameters from a memory of the network device, decoding the one or more encrypted parameters, and determining whether one or more of the decoded parameters match parameters obtained from a trusted platform module (TPM) installed in the network device and/or a read only memory (ROM) of the network device. In response to a mismatch between the decoded parameters and the parameters obtained from the TPM or the ROM, at least one of suspending operation of the device or transmitting a report of an authentication failure across a network on which the device is operating.

Abstract: A method for distributing information includes: receiving, at a replicator, a single data stream originating from a data source where the single data stream includes a first plurality of data units from the data source; replicating, by the replicator, the single data stream to obtain a first replicated data stream and a second replicated data stream; adding a delay between the first plurality of data units in the single data stream before replicating the single data stream; transmitting the first replicated data stream to a first data recipient using a first communication channel; and transmitting the second replicated data stream to a second data recipient using a second communication channel. The replication of the single data stream is performed by a lower layer device to obtain the first replicated data stream and the second replicated data stream substantially synchronously.

Abstract: A method and system for centralized network multicast state publication. Specifically, in overcoming the limitation(s) of existing monitoring and/or reporting approaches to ascertaining network multicast state, embodiments disclosed herein deliver a solution for centralized network multicast state publication. To that end, embodiments disclosed herein employ a centralized network controller configured to obtain aggregated network state, including network multicast state, through embedded logical agents interspersed across a network (e.g., on each network device). Thereafter, the network multicast state may be published through one or many notification channel(s) to any number of subscribing consumers interested in the network multicast state. Furthermore, the notification channel(s) may be implemented using an open-source, distributed, in-memory database that also features a message queuing (or messaging) system.

Abstract: A network device may receive one or more configuration scripts as part of provisioning information in a secure device provisioning operation. When executing a particular configuration script, the network device may maintain a timeout value indicative of an allocated time for completion of the execution of the configuration script. The network device may update the timeout value based on an indication in the configuration script.

Abstract: A switching system manager programmed to obtain a base lookup data structure comprising nodes that enumerate all prefixes of a first traffic management policy of a first type and all prefixes of a second traffic management policy of a second type, modify the base lookup data structure based on a first set of inheritance rules associated with the first traffic management policy to generate an updated lookup data structure comprising first traffic management policy label allocations, modify the updated lookup data structure based on a second set of inheritance rules associated with the second traffic management policy to generate a combined lookup data structure comprising the first traffic management policy label allocations and second traffic management policy label allocations, program packet classification hardware of the switching system to adapt the switching system to process packets based on the combined lookup data structure.

Abstract: Systems and methods for the dynamic mapping of network element data between data models in network devices are disclosed. In particular, a marked-up native data model can be processed to create a mapping schema file based on the markup included in the native data model. This mapping schema file may define mappings between elements of the native data model and corresponding elements of an external data model. The mapping schema file can then be used to dynamically map network element data from the native data model to the external data model, such as when responding to requests for network element data associated with the mapped elements.

Abstract: A method for analyzing a pair of domain name system (DNS) packets, the method comprising: extracting a portion of a request DNS packet to obtain extracted request DNS information, wherein the extracted request DNS information comprises a first timestamp generated by the edge network device, obtaining a response DNS packet, extracting at least a portion of the response DNS packet to obtain extracted response DNS information, wherein the extracted response DNS information comprises a second timestamp generated by the edge network device, after the obtaining, processing the extracted request DNS information and extracted response DNS information to obtain processed information, wherein the processed information comprises a roundtrip time derived from the first timestamp and the second timestamp, and transmitting the processed information to a monitoring system, wherein the pair of DNS packets are not transmitted to the monitoring system.

Abstract: Methods and apparatus for enabling detection of configuration changes in a network device. One method uses a configuration counter in a system database of the network device. In response to an atomic submission of CLI commands to a configuration agent and the storing of the corresponding configuration in a system database, the configuration counter is incremented. An OpenConfig module maintains an expected value of the configuration counter and, upon completion of its own command submissions, compares the expected value to the value in the configuration counter. If the two values do not match, it indicates that the configuration counter in the system database has been incremented as a result of a configuration change from a source other than the OpenConfig module. A configuration client can then be notified of the configuration change so that it can revert the configuration to a desired configuration.

Abstract: Techniques disclosed herein provide a method and systems for installing routes by a route reflect (RR) device when the tunnel RIB of the RR device does not include any tunnel labels definitions. The unicast routing information base (RIB) of route reflector (RR) device is configured to include a next hop associated with a first network device. When the RR device receives a route from the first network device that comprises a tunnel label for reaching the second network device, the RR device resolves the next hop of the received route using the unicast RIB of the RR device. In response to the resolving, the RR device forwards the route to a third network device (e.g., identified by an export route target of the RR device).