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.

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.

Abstract: A method for processing multicast data packets has steps for (a) requesting a second router upstream router by a multiple-processor data router to join a multicast group, the request including identification of a single physical ingress port from a plurality of available ports for receiving the multicast data packets; (b) preparing a multicast forwarding information base (MFIB) limited to only forwarding information incorporating the identified physical ingress port, and distributing the MFIB to a client software module hosting the identified physical ingress port; (c) receiving the multicast data packets at the identified ingress port; and (d) using only the MFIB to route the received multicast data packets.

Abstract: A software application in a multi-processor data router in which a forwarding information base for the router is maintained is provided with a server module and one or more client modules, each client module associated with one or more communication interfaces of the data router. The application is characterized in that the server module sends to each client module only that portion of the forwarding information base specific to the communication interfaces associated with the client module.

Abstract: A software application in a multi-processor data router in which a forwarding information base for the router is maintained is provided with a server module and one or more client modules, each client module associated with one or more communication interfaces of the data router. The application is characterized in that the server module sends to each client module only that portion of the forwarding information base specific to the communication interfaces associated with the client module.