CPC H04L 41/0806 (2013.01) [H04L 41/046 (2013.01); H04L 41/0816 (2013.01); H04L 43/00 (2013.01); H04L 47/825 (2013.01); H04L 51/046 (2013.01); H04L 63/029 (2013.01); H04L 67/02 (2013.01); H04L 67/10 (2013.01); H04L 67/1014 (2013.01); H04L 67/125 (2013.01); H04L 67/56 (2022.05); H04W 4/50 (2018.02); G06F 9/06 (2013.01); G06F 9/5088 (2013.01); H04L 51/58 (2022.05); H04L 63/168 (2013.01); H04L 63/20 (2013.01)] | 24 Claims |
1. A method comprising:
connecting a cloud extension agent to a remote network management platform;
wherein the cloud extension agent runs locally in a network as an active cloud extension agent;
wherein connecting the cloud extension agent to the network management platform comprises initiating an outbound connection from the cloud extension agent to the network management platform through a firewall of the network;
monitoring a status of the active cloud extension agent by the network management platform;
determining that the active cloud extension agent is no longer appropriate; and
initiating a handover to a first passive cloud extension agent of a plurality of cloud extension agents, wherein the determining is based on the status of the active cloud extension agent, and wherein the active cloud extension agent uploads status information to the remote network management platform via the outbound connection and the first passive cloud extension agent does not upload the status information to the remote network management platform, while both the active cloud extension agent and the first passive cloud extension agent connect to the remote network management platform at regular intervals, the status information comprising at least status of pending actions of the active cloud extension agent and changes in settings to the active cloud extension agent, and wherein determining that the active cloud extension agent is no longer appropriate and indicating the handover are based on the status information.
|