Airgapped NMS Upgrade Records for Scheduled Release Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Airgapped network management systems (NMS) face challenges in automatically checking for and installing software upgrades due to their offline nature, leading to potential software package mismatches and security vulnerabilities, as timer-based upgrade cycles fail to align with scheduled releases and force unnecessary upgrades to the most recent minor versions.
Innovation Solution
A forced upgrade technique using package upgrade records generated by an update server, which requires regular provision to the NMS deployment, enabling it to check for and install upgrades even when offline, and permits or denies user interface access based on record availability, allowing for selective minor version installation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If timer-based upgrade cycles are used for airgapped NMS, then the system can maintain basic upgrade timing, but the upgrades do not align with scheduled releases and force unnecessary minor version upgrades
Solution Approach 1:
The system performs preliminary action by pre-calculating and storing upgrade information in the package upgrade record before the airgapped NMS needs to upgrade. The record includes advance notice of scheduled releases and required upgrade actions, allowing the offline system to plan upgrades in advance without needing real-time communication or risking unnecessary upgrades.
Solution Approach 2:
The package upgrade record provides feedback mechanisms to the airgapped NMS by including upgrade status information, scheduled release dates, and completion confirmation. This feedback loop allows the offline system to track upgrade progress and verify that upgrades align with scheduled releases, preventing unnecessary minor version upgrades.
2Object-affected harmful factors
If airgapped NMS operates completely offline, then security is improved by reducing unauthorized access risk, but automatic upgrade checking and installation becomes impossible
Solution Approach 1:
The system performs preliminary action by pre-downloading and caching upgrade information, package upgrade records, and software packages before the airgapped NMS goes offline. This allows the offline system to automatically check for and install upgrades without needing real-time network connectivity, thus maintaining both security and automation capabilities.
Solution Approach 2:
The package upgrade record acts as an intermediary that bridges the airgapped NMS and the external update server. It contains all necessary upgrade information, status data, and instructions that the offline system needs to perform automatic upgrades, eliminating the need for continuous network communication while maintaining upgrade automation.
3Stability of the object's composition
If the NMS is forced to upgrade to the most recent minor version, then software consistency is improved, but system fragmentation increases due to unnecessary upgrades
Solution Approach 1:
The system applies local quality by customizing upgrade behavior for different NMS deployments based on their specific needs and environments. The package upgrade record allows each airgapped NMS to determine the appropriate upgrade target (minor version or major version) based on local requirements, preventing forced unnecessary upgrades and reducing software fragmentation while maintaining consistency where needed.
Solution Approach 2:
The upgrade system becomes dynamic by allowing the target version to be determined flexibly based on the current state of the NMS deployment and the package upgrade record. Instead of forcing upgrades to the latest minor version, the system can adaptively select the most appropriate version, balancing software consistency with avoiding unnecessary changes that cause fragmentation.
Data Source
AI summary
A forced upgrade technique for airgapped network management system (NMS) deployments utilizes a package upgrade record. The package upgrade record includes metadata about a target major version of a software package for the NMS deployment, and is generated by an update server that is airgapped from the NMS deployment. A control server of the NMS deployment determines whether the package upgrade record has been provided to the control server. Access to a user interface of the control server is denied in response to the package upgrade record not having been provided to the control server within an upgrade check window, while access to the user interface of the control server is permitted in response to the package upgrade record having been provided to the control server. Additionally, the NMS deployment may be forced to upgrade the software package to the target major.