Network Device ISSU Control for Incompatible Configuration Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In-service software upgrades (ISSU) on network devices can detrimentally impact configuration functionalities, causing misbehavior or stopping their execution, leading to resource wastage in attempting to fix issues, and existing scripts often fail to correctly deactivate or activate these functionalities.
Innovation Solution
A network device automatically identifies and deactivates configuration functionalities incompatible with ISSU using first and second configuration data structures, performs the ISSU, and then activates them post-upgrade, minimizing resource usage and script reliance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration functionalities are deactivated manually using scripts before ISSU, then incompatible functionalities can be deactivated, but scripts often fail to correctly identify and deactivate all incompatible functionalities, leading to resource wastage and operational issues
Solution Approach 1:
The system performs automatic identification and deactivation of incompatible configuration functionalities through self-service mechanisms. The network device autonomously compares configuration data structures before and after the software package application, identifies incompatible functionalities, and deactivates them without requiring external manual intervention or complex scripting.
Solution Approach 2:
The system changes the state parameter of configuration functionalities from active to inactive automatically. By monitoring and comparing configuration parameters before and after software package application, the system detects parameter changes that indicate incompatibility and automatically adjusts the functionality state to resolve the contradiction between software upgrade and configuration compatibility.
2Reliability
If all configuration functionalities are deactivated during ISSU to ensure compatibility, then no misbehavior occurs, but compatible functionalities are unnecessarily deactivated, causing operational performance issues
Solution Approach 1:
The system applies local quality by selectively deactivating only the specific configuration functionalities that are incompatible with the software upgrade, rather than deactivating all functionalities globally. The automatic identification process targets only the local incompatible elements, preserving the operational quality of compatible functionalities.
Solution Approach 2:
The system segments the configuration functionalities into compatible and incompatible groups through automatic comparison of configuration data structures. By dividing the configuration space and identifying specific incompatible segments, the system can apply deactivation only where necessary, maintaining productivity of the compatible segments.
3Productivity
If ISSU procedure is performed without deactivating incompatible configuration functionalities, then no service disruption occurs, but the incompatible functionalities misbehave or stop executing, causing resource wastage
Solution Approach 1:
The system performs preliminary action by automatically identifying and deactivating incompatible configuration functionalities before the ISSU procedure commences. This preliminary deactivation prevents the misbehavior and resource wastage that would occur during the upgrade, while maintaining continuous network operation through the in-service upgrade capability.
Solution Approach 2:
The system applies preliminary anti-action by preemptively deactivating incompatible configuration functionalities before they can cause harm during the ISSU procedure. This counter-action prevents the potential misbehavior and resource wastage, allowing the upgrade to proceed smoothly without negative consequences.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
A network device may be configured to identify a first configuration data structure included in the network device and may be configured to obtain a data package associated with an ISSU procedure that includes a second configuration data structure. The network device may be configured to identify, based on the first configuration data structure and the second configuration data structure, one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure. The network device may be configured to cause the one or more configuration functionalities of the network device to be deactivated and to thereafter cause the ISSU procedure to be performed. The network device may be configured to cause, after causing the ISSU procedure to be performed, the one or more configuration functionalities of the network device to be activated.