NIC Fabric Manager Mapping via LLDP for Data Center Configuration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In data centers, the manual provisioning and mapping of server NIC/Mezz card interfaces to fabric managers lead to difficulties in propagating server profiles and interface configurations, resulting in potential fabric downtime, network outages, and security issues due to the interchangeability of fabric management services between interconnected switches.

Innovation Solution

Implementing a system where network interface cards (NICs) use unicast Link Layer Discovery Protocol (LLDP) packets to map and propagate server profiles and interface configurations to fabric managers, creating a mapping table that is updated in real-time, and sending this information to a Baseboard Management Controller (BMC) for external management consoles to ensure accurate configuration propagation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If manual provisioning and mapping of server NIC/Mezz card interfaces to fabric managers is used, then device complexity is reduced, but information propagation accuracy deteriorates and reliability worsens

Engineering Contradiction:

Improveprovisioning process complexityVSAvoidconfiguration propagation reliability

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The NIC automatically performs fabric manager discovery and profile propagation without manual intervention. The system self-configures by discovering the correct fabric manager through LLDP communication and automatically propagating server profiles and interface configurations, eliminating the need for manual provisioning while ensuring accurate information delivery.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements bidirectional communication between NIC and fabric manager using LLDP packets. The NIC sends discovery requests and receives fabric manager responses, creating a feedback loop that enables automatic identification of the correct fabric manager and ensures accurate configuration propagation based on real-time network topology information.

Inventive Principle:

Principle #23Feedback

2Reliability

If static mapping for NIC interfaces is implemented, then reliability improves, but adaptability deteriorates due to fabric interchangeability

Engineering Contradiction:

Improvemapping stabilityVSAvoidfabric manager interchangeability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The mapping between NIC interfaces and fabric managers is made dynamic rather than static. The NIC continuously discovers fabric managers through LLDP and automatically updates its mapping based on current network conditions. This dynamic approach maintains reliability by ensuring the NIC always connects to the correct active fabric manager while adapting to fabric interchangeability and swaps.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

LLDP packets serve as an intermediary mechanism between NIC and fabric manager. These packets carry fabric manager identification information and enable the NIC to dynamically discover and adapt to the correct fabric manager without requiring static pre-configuration, thus resolving the conflict between mapping stability and fabric interchangeability.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If management consoles send requests to fabric managers without accurate mapping, then ease of operation improves, but harmful factors increase due to fabric downtime and security issues

Engineering Contradiction:

Improveconfiguration management easeVSAvoidfabric downtime and security risks

Core Design Contradiction:

Ease of operationVSObject-generated harmful factors

Solution Approach 1:

The NIC performs preliminary fabric manager discovery and mapping establishment before management consoles attempt to send configuration requests. By pre-establishing accurate mappings through LLDP discovery, the system ensures that subsequent configuration operations are directed to the correct fabric manager, preventing fabric downtime and security issues while maintaining ease of operation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements preliminary verification of fabric manager identity and mapping accuracy before allowing configuration requests to proceed. This anti-action prevents incorrect requests from reaching wrong fabric managers, thereby preemptively eliminating the harmful effects of fabric downtime, network outages, and security vulnerabilities associated with misdirected configuration operations.

Inventive Principle:

Principle #9Preliminary anti-action

Data Source

PatentUS20240364627A1Approaches to seamlessly propagate server profiles and associated interface configurations to external managed network fabrics in a datacenter

Publication Date: 2024.10.31 DELL PROD LP

AI summary

Described herein are embodiments of systems and methods for network fabric setup within and outside of a modular fabric chassis for its sleds such that server profiles and associated interface configurations may be propagated seamlessly to external managed network fabrics in a data center. Once a switch port of a network switch is connected to a NIC interface of a NIC, the NIC receives from the connected switch port of the network switch a packet comprising a fabric manager attribute. The NIC populates a table comprising mappings between NIC interfaces and corresponding fabric manager information and sends the mapping table to a baseboard management controller (BMC). The BMC maintains a fabric manager attribute per interface in a BMC attribute registry for each NIC. Fabric manager information may be seamlessly refreshed from NIC to BMC or other consoles in case of link down or fabric manager swap situations.