Abstract: An amount of data change associated with a version of a content file with respect to one or more previous versions of the content file is determined. The amount of change associated with the version of the content file is determined using a tree data structure associated with the content file that is stored on a storage cluster. One or more statistics associated with backup snapshot are provided to a server. The server is configured to determine that the amount of data change associated with the version of the content file is anomalous based in part on the one or more statistics associated with the backup snapshot. A notification that data associated with the backup snapshot is potentially infected by malicious software is received from the server. The version of the content file is indicated as being potentially infected by malicious software.

Abstract: The present invention discloses a continuous process for the synthesis of dimethyl carbonate from methanol and carbon dioxide over a ceria-based mixed metal oxide-silica catalyst formulation in the presence of a dehydrating or water trapping compound (2-Cyanopyridine).

Abstract: A network element and method for programming a network element that includes detecting an update to a first route in a routing information base (RIB) is disclosed. The method includes locating a first route network prefix associated with the first route within a network prefix trie (NPT); determining that, prior to the update, a first parent network prefix and the first route network prefix were reachable using a pair of different next hops connected to the network element; and determining that, after the update, the first parent network prefix and the first route network prefix are reachable using a first common next hop connected to the network element. The method also includes removing an existing forwarding information base (FIB) entry in the FIB associated with the first route network prefix.

Abstract: Protocol-Independent Multicast (PIM) uses PIM hello messages to maintain neighborship information. PIM may be implemented in an Ethernet VPN (EVPN) providing Optimized Inter-Subnet Multicast (OISM). Techniques are disclosed for improving PIM neighborship efficiency and speed in an EVPN. An Inclusive Multicast Ethernet Tag (IMET) may be used to set PIM neighborship instead of using PIM hello messages and TCP may be used to determine if the neighbor is disconnected instead of tracking PIM timers.

Abstract: Techniques for operating a network device are provided. In some embodiments, a method may comprise: forwarding multicast data packets from a source in a first customer network to a receiver in a second customer network; detecting that another PE device is forwarding the multicast data packets, wherein: Protocol Independent Multicast (PIM) is enabled on supplemental bridge domain (SBD) logical interfaces of the PE device and the another PE device, the PE device and the another PE device are PIM neighbors, and the PE device and the another PE device communicate with each other and with the receiver using the PIM protocol through an Ethernet virtual private network (EVPN). The method may further comprise: determining the another PE device is an assert winner from among the PE device and the another PE device based on at least one PIM assert message, the another PE device forwarding the multicast data packets.

Abstract: Protocol-Independent Multicast (PIM) uses PIM hello messages to maintain neighborship information. PIM may be implemented in an Ethernet VPN (EVPN) providing Optimized Inter-Subnet Multicast (OISM). Techniques are disclosed for improving PIM neighborship efficiency and speed in an EVPN. An Inclusive Multicast Ethernet Tag (IMET) may be used to set PIM neighborship instead of using PIM hello messages and TCP may be used to determine if the neighbor is disconnected instead of tracking PIM timers.

Abstract: A network element and method for programming a network element that includes detecting an update to a first route in a routing information base (RIB) is disclosed. The method includes locating a first route network prefix associated with the first route within a network prefix trie (NPT); determining that, prior to the update, a first parent network prefix and the first route network prefix were reachable using a pair of different next hops connected to the network element; and determining that, after the update, the first parent network prefix and the first route network prefix are reachable using a first common next hop connected to the network element. The method also includes removing an existing forwarding information base (FIB) entry in the FIB associated with the first route network prefix.

Abstract: A network element and method for programming a network element that includes detecting an update to a first route in a routing information base (RIB) is disclosed. The method includes locating a first route network prefix associated with the first route within a network prefix trie (NPT); determining that, prior to the update, a first parent network prefix and the first route network prefix were reachable using a pair of different next hops connected to the network element; and determining that, after the update, the first parent network prefix and the first route network prefix are reachable using a first common next hop connected to the network element. The method also includes removing an existing forwarding information base (FIB) entry in the FIB associated with the first route network prefix.

Abstract: Techniques for operating a network device are provided. In some embodiments, a method may comprise: forwarding multicast data packets from a source in a first customer network to a receiver in a second customer network; detecting that another PE device is forwarding the multicast data packets, wherein: Protocol Independent Multicast (PIM) is enabled on supplemental bridge domain (SBD) logical interfaces of the PE device and the another PE device, the PE device and the another PE device are PIM neighbors, and the PE device and the another PE device communicate with each other and with the receiver using the PIM protocol through an Ethernet virtual private network (EVPN). The method may further comprise: determining the another PE device is an assert winner from among the PE device and the another PE device based on at least one PIM assert message, the another PE device forwarding the multicast data packets.

Abstract: Multicast traffic in a virtual extensible local area network (VXLAN). In some embodiments, a method is provided. The method includes registering a network device as a virtual extensible local area network (VXLAN) tunnel endpoint (VTEP) of a VXLAN. The VXLAN includes an overlay network and the overlay network is implemented on an underlay network. The method also includes receiving multicast traffic from the multicast source. The method further includes transmitting the multicast traffic to one or more multicast receivers using the underlay network.

Abstract: Embodiments described herein relate to techniques for designated forwarder (DF) elections, which may include: obtaining DF candidates that are part of a supplementary broadcast domain (SBD), wherein the DF candidate is one of the plurality of DF candidates for the SBD; performing a SBD DF election process to determine an SBD DF winner from among the DF candidates; making a first determination that the DF candidate is not the SBD DF winner; making second determination that a first broadcast domain (BD) provisioned on the DF candidate is not provisioned on the SBD DF winner; excluding the first BD from a set of BDs that are also provisioned on the SBD DF winner; performing additional DF election processes for each BD of the set of BDs; and processing multicast traffic based at least in part on the SBD DF election process and the additional DF election processes.

Abstract: Embodiments described herein relate to techniques for designated forwarder (DF) elections, which may include: obtaining DF candidates that are part of a supplementary broadcast domain (SBD), wherein the DF candidate is one of the plurality of DF candidates for the SBD; performing a SBD DF election process to determine an SBD DF winner from among the DF candidates; making a first determination that the DF candidate is not the SBD DF winner; making second determination that a first broadcast domain (BD) provisioned on the DF candidate is not provisioned on the SBD DF winner; excluding the first BD from a set of BDs that are also provisioned on the SBD DF winner; performing additional DF election processes for each BD of the set of BDs; and processing multicast traffic based at least in part on the SBD DF election process and the additional DF election processes.

Abstract: In one embodiment, a method is provided. The method includes determining that a network device should use an underlay multicast group associated with an overlay multicast group for multicast traffic. The underlay multicast group carries multicast traffic for the overlay multicast group. The overlay multicast group is associated with a virtual private network. The method also includes determining an underlay multicast group address for the underlay multicast group. The overlay multicast group is associated with an overlay multicast group address. A first portion of the underlay multicast group address is a function of the overlay multicast group address. The method further includes forwarding one or more multicast packets to one or more multicast receivers via the underlay multicast group using the underlay multicast group address.

Abstract: In general, the invention relates to a method for programming a network element. The method includes detecting an addition of a first route in a routing information base (RIB) on the network element, adding, in response to detecting the addition, a first route network prefix associated with the first route to a network prefix trie (NPT), identifying, based on the adding, a first parent network prefix for the first route network prefix using the NPT, making a first determination that the first route network prefix and the first parent network prefix are reachable via a first common next hop connected to the network element, and waiving, based on the first determination, a creation of a forwarding information base (FIB) entry associated with the first route network prefix in a FIB on the network element.

Abstract: In one embodiment, a method is provided. The method includes determining that a network device should use an underlay multicast group associated with an overlay multicast group for multicast traffic. The underlay multicast group carries multicast traffic for the overlay multicast group. The overlay multicast group is associated with a virtual private network. The method also includes determining an underlay multicast group address for the underlay multicast group. The overlay multicast group is associated with an overlay multicast group address. A first portion of the underlay multicast group address is a function of the overlay multicast group address. The method further includes forwarding one or more multicast packets to one or more multicast receivers via the underlay multicast group using the underlay multicast group address.

Abstract: Multicast traffic in a virtual extensible local area network (VXLAN). In some embodiments, a method is provided. The method includes registering a network device as a virtual extensible local area network (VXLAN) tunnel endpoint (VTEP) of a VXLAN. The VXLAN includes an overlay network and the overlay network is implemented on an underlay network. The method also includes receiving multicast traffic from the multicast source. The method further includes transmitting the multicast traffic to one or more multicast receivers using the underlay network.

Abstract: In general, the invention relates to a method for programming a network element. The method includes detecting an addition of a first route in a routing information base (RIB) on the network element, adding, in response to detecting the addition, a first route network prefix associated with the first route to a network prefix trie (NPT), identifying, based on the adding, a first parent network prefix for the first route network prefix using the NPT, making a first determination that the first route network prefix and the first parent network prefix are reachable via a first common next hop connected to the network element, and waiving, based on the first determination, a creation of a forwarding information base (FIB) entry associated with the first route network prefix in a FIB on the network element.

Abstract: Multicast traffic in a virtual extensible local area network (VXLAN). In some embodiments, a method is provided. The method includes registering a network device as a virtual extensible local area network (VXLAN) tunnel endpoint (VTEP) of a VXLAN. The VXLAN includes an overlay network and the overlay network is implemented on an underlay network. The method also includes receiving multicast traffic from the multicast source. The method further includes transmitting the multicast traffic to one or more multicast receivers using the underlay network.

Abstract: Multicast traffic in a virtual extensible local area network (VXLAN). In some embodiments, a method is provided. The method includes registering a network device as a virtual extensible local area network (VXLAN) tunnel endpoint (VTEP) of a VXLAN. The VXLAN includes an overlay network and the overlay network is implemented on an underlay network. The method also includes receiving multicast traffic from the multicast source. The method further includes transmitting the multicast traffic to one or more multicast receivers using the underlay network.

Abstract: Method and system for reducing multicast traffic loss including configuring, on a primary DR including a first configured DR priority, a DR parameter including a value and an attribute; sending to a secondary DR, after a PIM interface comes up, a PIM hello message including a default DR priority lower than a second configured priority of the secondary DR; sending to the secondary DR, after the primary DR reaches a system-up state, a PIM hello message including the default DR priority; performing DR functionality, by the primary DR, after reaching the system-up state; and sending to the secondary DR, after waiting a time period corresponding to the value of the DR parameter, a PIM hello message including the first configured DR priority, where the primary DR waits to send the last PIM hello message to the secondary DR after the time period based on the attribute of the DR parameter.