Network Interface Naming Utility for Consistent Logical Names
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network interface card (NIC) naming techniques rely on hardware addresses or bus addresses, leading to inconsistent logical interface names when NICs are replaced or reconfigured, requiring manual intervention to maintain naming consistency in data-center environments.
Innovation Solution
A network interface naming utility that assigns logical interface names based on network configuration attributes, such as network names or identifiers, using protocols like LLDP or DHCP, ensuring consistent naming regardless of hardware or bus address changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional naming techniques use MAC address or bus address to name network interface cards, then the naming method is simple and straightforward, but the logical interface names become inconsistent when NICs are replaced or reconfigured
Solution Approach 1:
The patent changes the naming parameter from hardware-based identifiers (MAC address, PCI address) to service-based identifiers (service name, network configuration attribute). This allows the logical interface name to remain consistent even when the physical NIC changes, because the naming is now based on the service or network configuration rather than the hardware identity.
Solution Approach 2:
The patent introduces a naming utility as an intermediary layer between the physical NIC and the logical interface name. This utility receives network configuration attributes from NICs and maps them to consistent logical names based on service identification, thereby decoupling the naming from hardware changes and ensuring consistency.
2Reliability
If manual involvement is used to reconfigure network configuration when changes are made to NICs, then naming consistency can be maintained, but the time and effort required for configuration increases
Solution Approach 1:
The patent implements a self-service mechanism where the naming utility automatically receives network configuration attributes from NICs, identifies the associated service, and assigns logical interface names without human intervention. This automation eliminates the manual reconfiguration time while maintaining naming consistency through service-based identification.
Solution Approach 2:
The system performs preliminary action by pre-establishing the mapping between services and network configuration attributes. When a NIC is added or replaced, the naming utility already has the service identification rules in place, allowing it to automatically assign the correct logical interface name without requiring manual configuration steps.
3Extent of automation
If logical interface names are assigned based on hardware addresses, then the assignment process is automatic, but the names become indeterminate when hardware changes occur
Solution Approach 1:
The patent changes the automation basis from hardware address matching to service attribute matching. The naming utility automatically receives network configuration attributes from NICs and determines logical interface names based on service identification rather than hardware identity, maintaining both automation and determinability even when hardware changes.
Solution Approach 2:
The naming utility acts as an intermediary that receives network configuration attributes from NICs and translates them into logical interface names based on service identification. This intermediary layer ensures that the automation process remains robust and deterministic by relying on stable service attributes rather than volatile hardware addresses.
Data Source
AI summary
A method and system for network interface naming is described.