Custom YANG Models in Network Agents for Unified Device Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network device management systems face complexity due to mismatch between vendor-specific and user-defined data models, limiting flexibility and efficiency in network management.
Innovation Solution
Allow users to define custom YANG modules alongside vendor-supplied models, enabling network agents to manage devices using both types of models seamlessly, with custom modules being loaded into the network agent and indistinguishable from vendor-supplied interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If vendor-specific data models are used for network device management, then device compatibility and management efficiency are improved, but flexibility and adaptability to user-defined requirements deteriorate
Solution Approach 1:
The system segments data models into vendor-specific models and custom user-defined models, allowing each to operate independently while being managed through a unified interface. This enables maintenance of vendor model efficiency while adding user customization capability without conflict
Solution Approach 2:
The network device is designed to handle multiple types of data models (vendor-specific and custom) through a single management interface. The system provides universal functionality to load, validate, and manage both standardized vendor models and user-defined custom models, eliminating the need for separate management systems
2Adaptability or versatility
If custom data models are allowed alongside vendor models, then flexibility and user-defined configuration capability are improved, but system complexity increases
Solution Approach 1:
The system introduces an intermediary mechanism (the unified data model interface and validation system) that mediates between custom user models and vendor models. This intermediary handles model loading, validation, and interaction, preventing direct complexity conflicts while enabling both model types to coexist seamlessly
Solution Approach 2:
The system dynamically changes operational parameters based on model type, applying appropriate validation rules and processing methods for vendor models versus custom models. This parameter adaptation allows the system to maintain simplicity for each model type while supporting both through a single flexible framework
3Adaptability or versatility
If multiple data model types are supported, then compatibility across vendor devices is improved, but validation and processing complexity increases
Solution Approach 1:
The validation and processing mechanism dynamically adapts to the specific data model type being handled. The system automatically adjusts validation rules, processing logic, and interaction protocols based on whether it is dealing with vendor-specific models or custom models, maintaining appropriate complexity only for each model type while supporting both
Data Source
AI summary
Embodiments as disclosed allow the definition and use of custom models in association with a network agent on a network device. In particular, custom models can be placed on a network device and utilized by the network device. The use of these custom models including, notifications and responses associated with those custom models, may appear indistinguishable to use of vendor supplied models.