US 11,792,065 B2
Network controller, failure injection communication protocol, and failure injection module for production network environment
Nagendra Kumar Nainar, Morrisville, NC (US); Jaganbabu Rajamanickam, Kanata (CA); David John Zacks, Vancouver (CA); Carlos M. Pignataro, Cary, NC (US); Madhan Sankaranarayanan, Chinnamanur (IN); Cesar Obediente, Apex, NC (US); and Craig Thomas Hill, Sterling, VA (US)
Assigned to Cisco Technology, Inc., San Jose, CA (US)
Filed by Cisco Technology, Inc., San Jose, CA (US)
Filed on Feb. 17, 2022, as Appl. No. 17/674,686.
Prior Publication US 2023/0261928 A1, Aug. 17, 2023
Int. Cl. H04L 41/0604 (2022.01); H04L 41/0654 (2022.01); H04L 9/40 (2022.01); H04L 61/103 (2022.01); H04L 41/0631 (2022.01); H04L 67/133 (2022.01)
CPC H04L 41/0627 (2013.01) [H04L 41/0631 (2013.01); H04L 41/0654 (2013.01); H04L 61/103 (2013.01); H04L 63/101 (2013.01); H04L 67/133 (2022.05)] 10 Claims
OG exemplary drawing
 
1. A network device comprising:
one or more processing units; and
one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processing units, cause the one or more processing units to:
receive a control plane packet transmitted over a network connection;
parse a parsed failure type from the control plane packet;
create a child process by executing, in a dedicated runtime environment, a copy of a parent control plane process impacted by the parsed failure type, wherein the copy is created by performing a fork system call on the parent control plane process, and wherein the dedicated runtime environment is dedicated to the child process;
stop each timer of the parent process before performing the fork system call; and
start each timer of the child process at its respective last value after performing the fork system call.