Network Device Automatic Provisioning via Iterative Virtual Circuit Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network device provisioning methods fail to automate configuration across heterogeneous network technologies like Frame Relay and ATM, where DLCI numbers vary significantly, making it challenging to establish consistent connectivity without manual intervention.
Innovation Solution
A method and apparatus that iteratively apply virtual circuit identifiers to configure network devices, using techniques like Inverse Address Resolution Protocol (IARP) to determine IP addresses and netmasks, ensuring connectivity with a configuration server, and dynamically constructing commands to adapt to varying DLCI conventions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a generic bootstrap configuration with preset DLCI is used for automatic provisioning, then deployment speed is improved, but adaptability to heterogeneous network technologies deteriorates
Solution Approach 1:
The patent implements dynamic configuration by allowing the bootstrap configuration to adapt its DLCI values based on the specific network technology detected during deployment. The system dynamically queries the network to discover active virtual circuits and automatically configures the appropriate DLCI for Frame Relay or VCI for ATM, transforming a static preset configuration into a dynamic, environment-aware provisioning process.
Solution Approach 2:
The invention changes the parameter values (DLCI/VCI) based on the detected network technology. Instead of using a fixed preset DLCI, the system queries the network interface to retrieve the actual DLCI for Frame Relay or VCI for ATM, thereby adapting the configuration parameters to match the heterogeneous network environment while maintaining automated provisioning.
2Adaptability or versatility
If manual configuration methods are used for heterogeneous network technologies, then adaptability is improved, but deployment time and complexity increase
Solution Approach 1:
The patent enables the network device to self-configure by automatically querying the network interface for active virtual circuits and selecting the appropriate DLCI or VCI without human intervention. The system performs self-discovery of the network environment, automatically adapts the configuration parameters, and completes the provisioning process autonomously, eliminating the need for manual technician intervention while maintaining full adaptability to different network technologies.
Solution Approach 2:
The invention implements a feedback mechanism where the system queries the network interface to discover active virtual circuits, receives feedback about the actual DLCI/VCI values in use, and automatically adjusts the configuration based on this feedback. This closed-loop approach ensures the configuration matches the real network state while maintaining automated deployment speed.
3Ease of operation
If preset DLCI values are used in bootstrap configuration, then configuration simplicity is improved, but connectivity reliability across multiple regions deteriorates
Solution Approach 1:
The patent performs preliminary querying of the network interface to discover active virtual circuits and determine the correct DLCI or VCI values before finalizing the configuration. By preparing and validating the configuration parameters in advance based on actual network conditions, the system ensures connectivity reliability across multiple regions while maintaining the simplicity of automated configuration deployment.
Data Source
AI summary
A method is disclosed for automatically provisioning network devices for use with virtual circuit networks, such as frame relay and ATM networks. The device receives a list of identifiers corresponding to virtual circuits from a configuration interface for the virtual circuit network. The device iteratively applies each identifier from the list to individual instances of interface configuration commands and attempts to provide connectivity with a remote device. Once a configuration command is applied, the device will obtain an IP address for a device terminating the virtual circuit corresponding to the identifier selected from the list; and determines an IP address for itself. The device tests the virtual circuit for connectivity with the remote device. If the device is able to determine that the virtual circuit corresponding to the selected identifier provides connectivity to the remote device, then that virtual circuit is used to connect to the remote device.