RPD event storm mitigation
An access network can include a plurality of remote nodes connected to a principal controller. The principal controller can experience an event storm when one or more of the plurality of remote nodes report an access network event at the same or substantially the same time. One or more remote nodes can mitigate such an event storm at the principal core by delaying by an event reporting delay the reporting of the access network event to the principal core. The event reporting delay can be based on an event delay policy associated with a given remote node. The even reporting delay can be different for each remote node or a group of remote nodes so that the principal core does not receive reports from the plurality of remote nodes so as to cause an event storm which can negatively impact the access network, one or more network devices, or both.
1 . A method for a remote node, of a plurality of remote nodes, connected to a principal controller of an access network, the method comprising:
detecting an access network event associated with the access network;
generating a report based on the access network event;
initiating an event reporting delay based on an event delay policy associated with the remote node; and
sending the report to the principal controller of the access network after the event reporting delay.
2 . The method of claim 1 , wherein the remote node comprises a remote physical layer (PHY) device (RPD), a remote PHY media access control (MACPHY) device (RMD), or both, and wherein the principal controller is a principal core, and wherein the access network event is associated with an auxiliary core connected to the remote node or a precision time protocol (PTP) synchronization.
3 . The method of claim 1 , wherein the remote node is a remote media access control physical layer (MACPHY) device (RMD), a remote media access control core (RMC) device, or both, and wherein the access network event is associated with a registration or de-registration of a cable modem connected to the RMD, the RMC device, or both.
4 . The method of claim 1 , wherein the principal controller is a principal core, and wherein the access network event is associated with a loss of connection between the remote node and an auxiliary core of the access network.
5 . The method of claim 1 , further comprising storing the report in an event pending queue prior to sending the report to the principal controller.
6 . The method of claim 1 , further comprising associating a timestamp with the report and storing the report and the timestamp in a local log of the remote node, wherein the timestamp indicates a time of occurrence of the access network event.
7 . The method of claim 1 , wherein the delay policy comprises a delay factor based on any of a random number generator, a type of access network event, a threshold associated with a number of occurrences of the type of access network event, an event storage capacity of the remote node, any combination thereof.
8 . A remote node, of a plurality of remote nodes, connected to a principal controller of an access network, the remote node comprising a memory and a processor, the processor configured to:
detect an access network event associated with the access network;
generate a report based on the access network event;
initiate an event reporting delay based on an event delay policy associated with the remote node; and
send the report to the principal controller of the access network after the event reporting delay.
9 . The remote node of claim 8 , wherein the remote node comprises a remote physical layer (PHY) device (RPD), a remote PHY media access control (MACPHY) device (RMD), or both, and wherein the principal controller is a principal core, and wherein the access network event is associated with an auxiliary core connected to the remote node or a precision time protocol (PTP) synchronization.
10 . The remote node of claim 8 , wherein the remote node is a remote media access control physical layer (MACPHY) device (RMD), a remote media access control core (RMC) device, or both, and wherein the access network event is associated with a registration or de-registration of a cable modem connected to the RMD, the RMC device, or both.
11 . The remote node of claim 8 , wherein the principal controller is a principal core, and wherein the access network event is associated with a loss of connection between the remote node and an auxiliary core of the access network.
12 . The remote node of claim 8 , wherein the processor is further configured to store the report in an event pending queue prior to sending the report to the principal controller.
13 . The remote node of claim 8 , wherein initiating the delay comprises associating a timestamp with the report and storing the report and the timestamp in a local log, wherein the timestamp indicates a time of occurrence of the access network event.
14 . The remote node of claim 8 , wherein the delay policy comprises a delay factor based on any of a random number generator, a type of access network event, a threshold associated with a number of occurrences of the type of access network event, an event storage capacity of the remote node, any combination thereof.
15 . A remote device in a distributed access architecture configured to delay reporting to a principal controller of an event of a type associated with event storms, the amount of the delay based on a delay policy stored by the remote device.
16 . The remote device of claim 15 comprising a remote media access control physical layer (MACPHY) device (RMD), a remote media access control core (RMC) device, or both, and where the event is of a type associated with a registration or de-registration of a cable modem connected to the RMD, the RMC device, or both.
17 . The remote device of claim 15 , wherein the principal controller is a principal core, and wherein the event is associated with a loss of connection between the remote node and an auxiliary core of the access network or a precision time protocol (PTP) synchronization.
18 . The remote device of claim 15 configured to store the report in an event pending queue prior to sending the report to the principal controller.
19 . The remote device of claim 15 where the delay policy is configured to temporally disperse the reporting of events to the principal controller that occur substantially at the same time.
20 . The remote device of claim 19 , wherein the delay policy comprises a delay factor, wherein the delay factor is based on any of a random number generator, a type of access network event, a threshold associated with a number of occurrences of the type of access network event, an event storage capacity of the remote node, any combination thereof.