Abstract: Systems and methods are provided for performing a node-level redundant failover-type process with respect to the protocol-independent multicast (PIM) functionality in a multi-chassis environment. When a PIM-related failure occurs on a first network device, but otherwise it remains operational, a second network device is configured to assume responsibility for performing PIM data traffic forwarding. Upon detecting the PIM-related failure of the first network device, the second network device sends a PIM-DR failover event signal to the second network device's PIM module by loading multicast route states used by the first network device into the PIM data traffic forwarding hardware of the second network device. Upon the second network device assuming responsibility, the first network device disables its PIM data traffic forwarding functionality.

Abstract: Systems and methods are provided for performing a node-level redundant failover-type process with respect to the protocol-independent multicast (PIM) functionality in a multi-chassis environment. When a PIM-related failure occurs on a first network device, but otherwise it remains operational, a second network device is configured to assume responsibility for performing PIM data traffic forwarding. Upon detecting the PIM-related failure of the first network device, the second network device sends a PIM-DR failover event signal to the second network device's PIM module by loading multicast route states used by the first network device into the PIM data traffic forwarding hardware of the second network device. Upon the second network device assuming responsibility, the first network device disables its PIM data traffic forwarding functionality.

Abstract: Some examples relate to auto-configuration of a parameter related to a multicast protocol on a network device. In an example, a network device in a multicast network may identify the network topology of the multicast network. Upon identification, the network device may enable a multicast protocol on the network device based on the network topology of the multicast network. The network device may determine a network parameter related to the multicast network. In response to the determination, a multicast parameter related to the multicast protocol may be auto-configured on the network device.

Abstract: In some examples, a method includes identifying, by a network switching device, a network packet received via a particular port as a Message Queuing Telemetry Transport (MQTT) packet, wherein the MQTT packet is transmitted between a broker device and a subscriber device; performing, by the network switching device, a deep packet inspection (DPI) to identify a network address corresponding to the broker device; applying, by the network switching device, a network policy defined in a policy engine that is specific to at least one of the broker device and the subscriber device, wherein the at least one of the broker device and the subscriber device is not statically configured in the policy engine; and performing, by the network switching device, a specific action based on the applied network policy.

Abstract: Some examples relate to auto-configuration of a parameter related to a multicast protocol on a network device. In an example, a network device in a multicast network may identify the network topology of the multicast network. Upon identification, the network device may enable a multicast protocol on the network device based on the network topology of the multicast network. The network device may determine a network parameter related to the multicast network. In response to the determination, a multicast parameter related to the multicast protocol may be auto-configured on the network device.

Abstract: In some examples, a method includes identifying, by a network switching device, a network packet received via a particular port as a Message Queuing Telemetry Transport (MQTT) packet, wherein the MQTT packet is transmitted between a broker device and a subscriber device; performing, by the network switching device, a deep packet inspection (DPI) to identify a network address corresponding to the broker device; applying, by the network switching device, a network policy defined in a policy engine that is specific to at least one of the broker device and the subscriber device, wherein the at least one of the broker device and the subscriber device is not statically configured in the policy engine; and performing, by the network switching device, a specific action based on the applied network policy.