Network Core Dump via Preserved Firmware APIs

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional network core dump processes are unreliable due to reliance on network device drivers, which can be locked up or wedged, and require reinitialization, and they also depend on persistent memory states that are not always available in modern computing devices.

Innovation Solution

Preserving network device firmware in memory post-boot and invoking standard application programming interfaces (APIs) to perform network core dumps without relying on network device drivers, using a network bootstrap program like PXELINUX that provides device-agnostic access through UNDI APIs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network device drivers are used to perform network core dump, then the core dump can be transferred over the network, but the reliability deteriorates when the network device is locked up or wedged

Engineering Contradiction:

Improvenetwork core dump reliabilityVSAvoidnetwork device driver reinitialization difficulty

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces firmware as an intermediary layer between the operating system and the network device. The firmware contains a network bootstrap program with standard APIs that can operate independently of the network device driver. When the driver fails or the device is locked up, the firmware provides an alternative pathway to access the network device and perform core dump operations, thus resolving the reliability issue without requiring driver reinitialization.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network access functionality into two independent parts: the network device driver loaded by the operating system, and the firmware-resident network bootstrap program with standard APIs. This segmentation allows the core dump functionality to be separated from the driver dependency, enabling reliable network access even when the driver fails, while maintaining ease of operation through the standardized firmware interface.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If network device driver is loaded into memory, then network functionality is provided, but the driver cannot be easily reinitialized when it fails

Engineering Contradiction:

Improvenetwork device functionalityVSAvoiddriver reinitialization ease

Core Design Contradiction:

Adaptability or versatilityVSEase of repair

Solution Approach 1:

The firmware acts as a permanent intermediary that remains in memory regardless of driver state. It provides a standardized API interface that can invoke network device functions without relying on the driver's state, allowing the system to recover from driver failures without complex reinitialization procedures.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent effectively creates a backup copy of the network device interface functionality in the firmware. This firmware-resident copy of the network bootstrap program with standard APIs serves as an alternative implementation that can be invoked when the original driver-based interface fails, providing ease of repair without losing network functionality.

Inventive Principle:

Principle #26Copying

3Productivity

If conventional network core dump process is used, then network core dump can be performed, but it is not reliable when network device driver causes crash

Engineering Contradiction:

Improvecore dump transfer capabilityVSAvoidcore dump reliability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The firmware serves as a mediator that provides a driver-independent pathway for core dump operations. The standard APIs in the firmware can directly invoke network device functions without going through the potentially faulty driver layer, ensuring that core dump transfers can proceed reliably even when the driver is the source of the crash.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of having the operating system driver control network access, the patent inverts the approach by having the firmware-resident standard APIs control network access directly. This inversion bypasses the driver layer that may cause crashes, providing a more reliable pathway for core dump operations while maintaining full network functionality.

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS8677187B2Performing network core dump without drivers

Publication Date: 2014.03.18 VMWARE INC

AI summary

Core dump is performed over a network without relying on network device drivers. Instead of network device drivers, firmware of network devices that is typically used during boot is preserved in memory post-boot, and one or more application program interfaces of the firmware are invoked to perform the network core dump. For ease of implementation, a network bootstrap program that has standard application program interfaces for calling into the firmware of network devices may be invoked when performing core dump over the network.