Network Management Switch Configuration Update via Multiplexer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network device management switch configurations are immutable after manufacturing, lacking the flexibility to modify or replace them during or after deployment, due to limitations in hardware design and communication protocols that only support single-master, single- or multiple-slave configurations.
Innovation Solution
Implementing multiple-master, single-slave interactions that allow access to non-volatile memory by a network device system controller, enabling in-the-field modification of management switch configurations through existing hardware, such as repurposed multiplexers, to regulate concurrent reading and writing and facilitate updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If single-master, single- or multiple-slave configurations are used for hardware design and communication protocols, then device complexity is reduced and ease of manufacture is improved, but adaptability to modify management switch configurations during deployment is lost
Solution Approach 1:
The multiplexer is designed to serve multiple functions: during normal operation it enables single-master or multiple-slave configurations for the management switch, but during deployment it can be reconfigured to enable multiple-master mode, allowing the system controller to access the management switch configuration. This multi-functionality resolves the contradiction by making a single hardware component adaptable to different operational modes without adding complex separate mechanisms.
Solution Approach 2:
The system employs dynamic reconfiguration of the multiplexer's control signals to switch between different master-slave configurations. The multiplexer's selection lines can be dynamically controlled to change which master or slave mode is active, allowing the hardware to adapt its behavior based on operational requirements without physical reconfiguration or increased device complexity.
2Ease of operation
If non-volatile memory is made accessible to system controller for configuration updates, then ease of operation during deployment is improved, but reliability of configuration storage is worsened due to concurrent access risks
Solution Approach 1:
The multiplexer acts as an intermediary between the system controller and the non-volatile memory. During normal operation, it directs access to the management switch. During deployment, it redirects access to the system controller. This intermediary mechanism enables the system controller to safely access configuration memory without direct concurrent access conflicts, as the multiplexer mediates the access rights based on operational mode.
Solution Approach 2:
The system performs preliminary action by switching the multiplexer to the appropriate configuration mode before initiating any configuration updates. This ensures that the system controller has exclusive access to the non-volatile memory before writing begins, preventing concurrent access issues. The mode switching occurs in advance, preparing the hardware architecture for safe configuration updates.
3Adaptability or versatility
If management switch configuration is made immutable after manufacturing, then manufacturing precision and reliability are improved, but adaptability for network changes during deployment is worsened
Solution Approach 1:
The system segments the operational lifecycle into distinct phases: manufacturing phase where configuration is programmed with high precision, and deployment phase where configuration can be modified. The multiplexer-based switching mechanism allows the same hardware to support both phases, enabling configuration updates during deployment without compromising the manufacturing precision achieved during the initial programming phase.
Solution Approach 2:
The system changes the accessibility parameter of the non-volatile memory based on operational phase. During manufacturing, the memory is accessible only to the management switch for precise configuration programming. During deployment, the multiplexer reconfigures to allow system controller access, enabling parameter changes and updates. This parameter change in memory accessibility resolves the contradiction between manufacturing precision and deployment adaptability.
Data Source
AI summary
A network device, method, and non-transitory computer readable medium storing computer readable program code, for the post-deployment updating of network device management switch configurations. Particularly, in overcoming limitations imposed by the current state of technology, embodiments disclosed herein enable and implement multiple-master, single-slave interactions amongst network device hardware and using communication protocols otherwise designed to support single-master, single- or multiple-slave(s) configurations. Further, through said multiple-master, single-slave interactions, embodiments disclosed herein facilitate the in-the-field modification of management switch configurations across scenarios following and/or during deployment of network devices in networks.