Overview

By default, gateway system logs may be stored in RAM (memory), which means the content is lost after a power cycle. Configuring the log save location to NVM (Non-Volatile Memory) ensures that system logs are retained persistently across gateway reboots or power outages, facilitating subsequent troubleshooting and system analysis. This guide explains saving system logs to non-volatile memory on a Robustel gateway when troubleshooting evidence must survive a restart or temporary power loss. It covers how to change the log save position to NVM and confirm persistent storage. The key takeaway is that NVM logging should be enabled intentionally because persistent storage is more useful for intermittent faults.

What You Will Need

Hardware/Software Prerequisites

• 1x Robustel Gateway Device
• 1x Computer with access to the gateway's Web Management Interface
• Administrator account privileges (e.g., admin)

Step-by-Step Configuration Guide

Step 1: Log In and Access the System Log Configuration Interface

1. Use a browser to log in to the gateway's Web management interface (the default address is usually 192.168.0.1).
2. In the left-hand dark blue navigation bar, click 【Services】 to expand the menu, then select 【SysLog】. The log configuration area will be displayed on the right.

Step 2: Enable the System Logging Function

In the "System Log Settings" area, locate the "Enable" switch at the top and toggle it to the ON position (as shown in the figure) to activate the logging function.

Step 3: Configure Log Level and Save Location

1. System Log Level: From the "SysLog Level" dropdown menu, select the desired level of log detail. The example in the figure shows "Debug" mode, which provides the most verbose logging.
2. Save Location: This is the critical setting. Click the "Save Position" dropdown menu and select "NVM" from the list of options.

Step 4: Submit the Configuration

Scroll to the bottom of the page and click the blue 【Submit】 button to save and apply the configuration. The system will subsequently start writing generated logs to the NVM storage.

Verification and Testing

1. Check Current Configuration: After submission, the "Save Location" field on the page should persistently display "NVM".
2. Generate Test Logs: Perform an action that generates logs (e.g., unplug and replug a network cable, or restart a service) to trigger log recording.
3. Verify Log Persistence: Reboot the gateway. After the reboot, log back into the system and check the system logs to see if they contain the test event logs recorded before the restart. If visible, this confirms that the logs were successfully saved to NVM and retained after the reboot.

Troubleshooting/ FAQ

Q1: After configuring logs to save to NVM, the gateway indicates insufficient storage space. What should I do?

A1: NVM storage space is limited. It is recommended to:

• Regularly log into the system to download or clear old log files.
• Adjust the "Syslog Level" appropriately, for example, changing from "Debug" to "Info" or "Warning", to reduce the output of unnecessary logs and extend the available storage duration.

Q2: What is the main difference between saving logs to NVM versus saving to RAM?

A2:

• Saving to RAM: Logs are written quickly, but all log content is lost if the gateway powers down or reboots.
• Saving to NVM: Logs are persisted after writing; they are not lost due to gateway power failure or reboot, making this very suitable for troubleshooting issues that cause system restarts.

Q3: Is it possible to send logs to a remote server and save them to NVM simultaneously?

A3: Yes, this is a recommended redundant backup strategy. As shown in the figure, while configuring the save location to NVM, you can also enable the "log to remote" switch above and fill in the IP address and port of the remote syslog server. This way, logs are saved locally in NVM andsent to the remote server in real-time, achieving dual backup for enhanced security.

Conclusion

Revision History