Abstract: A network device may execute a software keep-alive process (SKAP) that enables the network device to continue to send keep-alive packets without interruption even during events such as a network operating system failover/switchover or an in-place system upgrade. The network device maintains a database of keep-alive network sessions storing information that is used to schedule and send keep-alive messages or packets for the keep-alive network sessions. The database may be shared between network operating subsystems and programs executed by the network device. The database may be updated by a network operating subsystem and the information may then be used by the SKAP to schedule and send out keep-alive messages or packets for the keep-alive network sessions. For example, a virtual machine may store information for a keep-alive network session in the database, which is used by SKAP to schedule transmission of keep-alive packets for that keep-alive network session.

Abstract: A network device may execute a process (e.g., a software keep-alive process (SKAP)) that schedules the transmission of keep-alive messages or packets. The network device maintains a database of keep-alive network sessions storing information that is used for scheduling the transmission of the keep-alive messages or packets for the keep-alive network sessions. The database may be read and a next transmission time and session frequency for one or more keep-alive sessions may be determined. The one or more keep-alive sessions may then be placed in appropriate banks within a timer queue based on the determined next transmission time and session frequency. Each bank is associated with a time period from the current time. The keep-alive sessions having sooner next transmission times are placed in higher priority banks. The scheduler may allow for real-time scheduling of the one or more keep-alive sessions.

Abstract: A network device may execute a process (e.g., a software keep-alive process (SKAP)) that schedules the transmission of keep-alive messages or packets. The network device maintains a database of keep-alive network sessions storing information that is used for scheduling the transmission of the keep-alive messages or packets for the keep-alive network sessions. The database may be read and a next transmission time and session frequency for one or more keep-alive sessions may be determined. The one or more keep-alive sessions may then be placed in appropriate banks within a timer queue based on the determined next transmission time and session frequency. Each bank is associated with a time period from the current time. The keep-alive sessions having sooner next transmission times are placed in higher priority banks. The scheduler may allow for real-time scheduling of the one or more keep-alive sessions.

Abstract: A network device may execute a software keep-alive process (SKAP) that enables the network device to continue to send keep-alive packets without interruption even during events such as a network operating system failover/switchover or an in-place system upgrade. The network device maintains a database of keep-alive network sessions storing information that is used to schedule and send keep-alive messages or packets for the keep-alive network sessions. The database may be shared between network operating subsystems and programs executed by the network device. The database may be updated by a network operating subsystem and the information may then be used by the SKAP to schedule and send out keep-alive messages or packets for the keep-alive network sessions. For example, a virtual machine may store information for a keep-alive network session in the database, which is used by SKAP to schedule transmission of keep-alive packets for that keep-alive network session.