Method for safeguarding reachability of a remote network node with programmable auto rollback
A system and a method for providing a set of operational checks to be implemented prior to configuration changes being made in a mobile network that includes a user computer connected to a management configuration system and connected to a data center having a storage and to a computer located at a remote cell site. The management configuration system provides for saving of an existing system configuration, and the automatic execution of a script that comprises a set of user-specified and programmed operational checks to ensure a new system configuration is valid prior to implementation of the new configuration on the system, where if the new configuration fails the operational checks, the system automatically rolls back to the previous configuration.
1 . A method for providing a set of operational checks to be implemented prior to configuration changes being made in a mobile network including a user computer connected to a management configuration system and connected to a data center having a storage, which in turn is connected to a Cell Site Router (CSR) for a computer located at a remote cell site, the method comprising the steps of:
the user computer setting operations checks that are transmitted to the management configuration system;
the user computer indicating to the management configuration system that fail-safe mode is initiated;
the management configuration system automatically saving a configuration of at least one program executing on the computer on the data center storage;
the user computer generating commands to modify the configuration of the at least one program;
the management configuration system automatically performing syntax and semantics checks of the generated commands;
if the generated commands pass the check for syntax and semantics, the generated commands are installed on the user computer as a new configuration;
the management configuration system automatically performing an operations check of the new configuration to determine if the at least one program is properly configured;
if the operations check determines the at least one program is properly configured, the management configuration system ends the fail-safe mode operation; and
if the operations check determines the at least one program is not properly configured, the management configuration system reverts the configuration to the saved configuration.
2 . The method of claim 1 , wherein the at least one program comprises a program for the CSR.
3 . The method of claim 2 , wherein the CSR comprises a virtual CSR (vCSR).
4 . The method of claim 3 , wherein the operations check comprises a script that causes the vCSR to ping the data center and if a subnet to the data center is denied, the ping fails, and the script reports a failed operations check.
5 . The method of claim 1 , further comprising the step of: the user computer transmitting a commit command to the management configuration system, which causes the generated commands to be installed as the new configuration.
6 . The method of claim 1 , wherein the generated commands comprise access control policy configurations.
7 . The method of claim 6 , wherein the access control policy configurations are selected from the group consisting of: Access Control Lists (ACL), Policy-Based Routing (PBR), IP address configuration, generic router configurations, and combinations thereof.
8 . The method of claim 1 , wherein the operations check comprises a script that verifies for the conditions selected from the group consisting of: reachability to the CSR from the data center, reachability to Remote Radio Units (RRU), process health, CPU utilization and memory health, time synchronization, control plane synchronization, control plane states, interface states, counters and statistics, management plane connectivity, traffic engineering validation, and combinations thereof.
9 . The method of claim 8 , wherein the operations check for process health includes the operation check script checking:
if a set of processes that are outlined in the script are up and running after a config change, or
if there is a core-dump/crash in the system prior to or after the config change.
10 . The method of claim 8 , wherein the operations check for time synchronization includes the operation check script verifying if the time synchronization fails or is out-of-sync after a config change.
11 . The method of claim 8 , wherein the operations check for control plane synchronization includes checking for control plane adjacencies, or specific forwarding table entries, or both.
12 . The method of claim 8 , wherein the operations check for control plane states includes checking for dynamic control plane protocol states.
13 . The method of claim 12 , wherein the dynamic control plane protocol states include: Open Shortest Path First (OSPF), Border Gateway Protocol (BGP), Intermediate System-to-Intermediate System (IS-IS).
14 . The method of claim 8 , wherein the operations check for interface states comprises physical/logical interface operational information.
15 . The method of claim 8 , wherein the operations check for counters and statistics includes counters related to interface, forwarding information, and Access Control Lists (ACL).
16 . The method of claim 8 , wherein the operations check for traffic engineering validation includes measuring latency, jitter, queue-length, and throughput for classes of traffic after config change.