Automated Virtual Network Card Configuration for Distributed Control Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The setup and maintenance of virtualized distributed control systems are complex and time-consuming, particularly due to the need for configuring storage area networks and clusters, which are prone to human error and require significant IT overhead, leading to increased costs and system fragility.
Innovation Solution
Automating configuration choices by enforcing a common naming convention across all servers in a cluster, using a configuration data structure to ensure consistent naming and IP information, and providing a dialog for users to assign fixed labels to network cards, thereby reducing errors and simplifying the setup process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual configuration of storage area networks and clusters is performed, then system setup flexibility is maintained, but time consumption and error probability increase significantly
Solution Approach 1:
The system performs self-configuration by automatically detecting physical network cards, assigning virtual device names according to naming conventions, and configuring storage area networks without requiring manual IT intervention. The virtualization layer autonomously manages the configuration process, reducing both time consumption and human error.
Solution Approach 2:
The patent implements pre-defined naming conventions and configuration templates before the actual system setup. Virtual device names are predetermined based on standardized conventions, and configuration parameters are prepared in advance, allowing the system to be rapidly deployed without ad-hoc manual configuration during installation.
2Adaptability or versatility
If multiple software and hardware releases are maintained for legacy support, then system compatibility is improved, but maintenance complexity increases
Solution Approach 1:
The virtualization layer acts as an intermediary between legacy control systems and modern hardware infrastructure. By virtualizing the network and storage layers, the system can support multiple software and hardware releases without requiring physical legacy components, simplifying maintenance while maintaining compatibility.
Solution Approach 2:
The patent creates virtual copies of network interfaces and storage devices that emulate legacy system behavior. These virtual representations allow legacy control software to operate on modern hardware without direct hardware dependencies, reducing maintenance complexity while preserving system compatibility.
3Reliability
If common naming conventions are enforced across all servers, then configuration consistency is improved, but flexibility in individual server naming is reduced
Solution Approach 1:
The patent applies different naming strategies at different levels: standardized naming conventions are enforced for virtual device names to ensure consistency and automation, while physical network card names retain their original manufacturer-assigned identifiers. This allows configuration consistency where it matters for automation while preserving flexibility in the physical layer.
Data Source
AI summary
Systems and methods for automated commissioning of virtualized distributed control systems are disclosed. An example method includes accessing a data structure including a list of configuration names for network cards associated with first and second host servers of a virtual process control environment. The first and second host servers implement virtual machines corresponding to workstations for a process control system. The example method also includes when configuring the first host server, assigning a first name to a first one of the network cards associated with the first host server. The example method further includes when configuring the second host server, assigning the first name to a second one of the network cards associated with the second host server based on a user selection of the first name from the list of configuration names. The second host server is configured after the first host server.


