Network Device Log Collection via Trigger Packets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for collecting logs related to errors in network devices are inefficient, often requiring manual reproduction and analysis, which is time-consuming and labor-intensive, especially when errors occur unexpectedly or involve silent failures, leading to missed log collection due to storage limitations.

Innovation Solution

An information processing method that automatically collects logs by detecting errors, identifying relevant packets, and storing them in a network device, using a trigger packet system to manage data storage and transmission efficiently, even during high CPU load conditions, thereby reducing communication impact.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dedicated equipment is installed in a network to collect logs, then log collection capability is improved, but it becomes difficult to collect logs at the timing of error occurrence and requires manual reproduction work

Engineering Contradiction:
Improvelog collection capabilityVSAvoidtime for manual reproduction work
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by detecting errors in advance and automatically collecting relevant log data at the timing of error occurrence. The error detection unit monitors network devices and triggers automatic log collection when errors are detected, eliminating the need for manual reproduction work and ensuring logs are captured at the critical moment of error occurrence.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by allowing network devices to automatically detect errors and collect their own log data without requiring external dedicated equipment or manual intervention. The device autonomously identifies errors, determines relevant log criteria, collects matching log data, and transmits it to management devices, making the log collection process self-sufficient.

Inventive Principle:
Principle #25Self-service

2Loss of information

If logs are collected continuously to ensure availability, then log data completeness is improved, but storage resources are consumed and may miss errors due to storage limitations

Engineering Contradiction:
Improvelog data completenessVSAvoidstorage resource consumption
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The system applies local quality by collecting log data selectively based on specific error-related criteria rather than uniformly collecting all logs. The log data collection unit determines criteria such as time ranges, device identifiers, and error types relevant to detected errors, collecting only the necessary portions of log data that have local relevance to the specific error context.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system uses partial action by collecting only the specific log data portions needed for error analysis rather than complete continuous logs. When errors are detected, the system collects log data within specific time windows and for specific devices related to the error, avoiding the resource consumption of continuous full-scale log collection while ensuring relevant information is captured.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If automatic error detection and log collection is implemented, then error analysis efficiency is improved, but CPU load increases which may impact network communication

Engineering Contradiction:
Improveerror analysis efficiencyVSAvoidCPU load
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system implements periodic action by triggering log collection operations periodically based on error detection events rather than continuously. The error detection unit monitors for errors and initiates log collection only when errors occur, creating a periodic, event-driven collection pattern that improves error analysis efficiency while avoiding the sustained CPU load of continuous collection.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system applies dynamics by adjusting log collection operations based on real-time error conditions and device states. The log data collection unit dynamically determines collection criteria, time ranges, and data volumes based on the specific error context, allowing the system to adapt collection intensity to actual needs and reduce unnecessary CPU consumption during normal operation.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10511502B2Information processing method, device and recording medium for collecting logs at occurrence of an error
Publication Date: 2019.12.17 FSAS TECH INC
  • US10511502B2 patent drawing
  • US10511502B2 patent drawing
  • US10511502B2 patent drawing

AI summary

An information processing method executed by a processor included in an information processing device includes acquiring, when an error occurred at the information processing device is detected, first identification information that include identification information of a transmission source of a first packet transmitted or received when the error has occurred and identification information of a transmission destination of the first packet; receiving a second packet; determining whether second identification information included in the second packet matches with the first identification information, the second identification information including identification information of a transmission source of the second packet and identification information of a transmission destination of the second packet; storing data corresponding to the second packet when it is determined that the second identification information matches with the first identification information; and transmitting the data to a management device that analyzes the error when an instruction is received from the management device.