Automated NID Discovery via SOAM VLAN Cycling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Manual configuration of network interface device (NID) addresses, particularly IPv4 and IPv6, is time-consuming and prone to errors, leading to significant overhead and costs due to the complexity and length of addresses.
Innovation Solution
An automated system using Service Operations, Administration, and Maintenance (SOAM) processes, including Ethernet vendor-specific OAM frames, to discover and configure NIDs by generating discovery messages and cycling through untagged and tagged VLAN IDs until a response is received, allowing for automated determination of NID identification and configuration data download.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual configuration of NID addresses is used, then field technicians can set addresses directly, but the process is time-consuming and error-prone
Solution Approach 1:
The NID automatically generates discovery messages and configures its own address without requiring manual field technician intervention. The device performs self-discovery by cycling through VLAN IDs and self-configures by processing the response to obtain its address, eliminating the time-consuming manual configuration process while maintaining operational simplicity through automated workflows.
Solution Approach 2:
The system performs preliminary actions by pre-configuring the NID with a maintenance entity endpoint (MEP) before deployment. This preliminary setup enables the NID to immediately begin automated discovery and configuration processes upon activation, reducing the time required for field technicians to configure addresses while ensuring proper operational setup from the start.
2Ease of operation
If manual configuration of NID addresses is used, then field technicians can set addresses directly, but errors may occur due to complexity and length of addresses
Solution Approach 1:
The NID automatically generates discovery messages and configures its own address without requiring manual field technician intervention. The device performs self-discovery by cycling through VLAN IDs and self-configures by processing the response to obtain its address, eliminating the time-consuming manual configuration process while maintaining operational simplicity through automated workflows.
Solution Approach 2:
The system uses feedback mechanisms where the NID sends discovery messages and processes responses to automatically determine its configuration. The automated feedback loop between the NID and the network management system ensures accurate address assignment by validating the configuration through response processing, eliminating human error while maintaining operational simplicity.
3Loss of time
If automated discovery and configuration is implemented, then configuration time is reduced, but system complexity increases
Solution Approach 1:
The system performs preliminary actions by pre-configuring the NID with a maintenance entity endpoint (MEP) before deployment. This preliminary setup enables the NID to immediately begin automated discovery and configuration processes upon activation, reducing the time required for field technicians to configure addresses while ensuring proper operational setup from the start.
Solution Approach 2:
The system introduces an intermediary network management system that mediates between the NID and the network infrastructure. This intermediary handles the complex automated discovery and configuration processes, including cycling through VLAN IDs and processing responses, thereby reducing configuration time while managing system complexity through a dedicated intermediary component rather than distributing complexity across all devices.
4Loss of time
If automated discovery and configuration is implemented, then operational costs are reduced, but overhead for automation infrastructure increases
Solution Approach 1:
The system performs preliminary actions by pre-configuring the NID with a maintenance entity endpoint (MEP) before deployment. This preliminary setup enables the NID to immediately begin automated discovery and configuration processes upon activation, reducing the time required for field technicians to configure addresses while ensuring proper operational setup from the start.
Solution Approach 2:
The system introduces an intermediary network management system that mediates between the NID and the network infrastructure. This intermediary handles the complex automated discovery and configuration processes, including cycling through VLAN IDs and processing responses, thereby reducing configuration time while managing system complexity through a dedicated intermediary component rather than distributing complexity across all devices.
Data Source
AI summary
A system for and method of automatic discovery and configuration of network interface devices is presented. A network interface device (NID) may be included a pre-configured maintenance entity end point (MEP), whereby upon use, the NID may begin sending at least one discovery message to a provider edge device, each discovery message including an organizationally unique identifier. The provider edge device may strip the discovery message(s) to determine the message content, which may then be forwarded to a NIS management system. The NID management system may then identify an identification number of the NID, determine where the NID is installed and send any configuration data to the NID via the provider edge device to configure the NID.