cancel
Showing results for 
Search instead for 
Did you mean: 

How to manage the space and persistent data on NVRAM?

How to manage the space and persistent data on NVRAM?

Junespiano
New Contributor

My EXOS Linux 5.10.177 Switch returns this warnings:

04/24/2024 08:35:48.85 <Warn:log.NVRAMFull> Slot-2: NVRAM is full, old messages are overwritten.
04/24/2024 08:35:03.86 <Warn:log.NVRAMFull> Slot-1: NVRAM is full, old messages are overwritten.
03/28/2024 11:48:23.32 <Warn:log.NVRAMFull> Slot-1: NVRAM is full, old messages are overwritten.
03/28/2024 11:48:04.09 <Warn:log.NVRAMFull> Slot-2: NVRAM is full, old messages are overwritten.
03/02/2024 11:19:27.26 <Warn:log.NVRAMFull> Slot-1: NVRAM is full, old messages are overwritten.
03/02/2024 11:19:07.72 <Warn:log.NVRAMFull> Slot-2: NVRAM is full, old messages are overwritten.
02/04/2024 16:10:01.08 <Warn:log.NVRAMFull> Slot-1: NVRAM is full, old messages are overwritten.
02/04/2024 16:09:42.15 <Warn:log.NVRAMFull> Slot-2: NVRAM is full, old messages are overwritten.
02/03/2024 12:21:40.36 <Warn:log.NVRAMFull> Slot-2: NVRAM is full, old messages are overwritten.
02/03/2024 12:21:02.06 <Warn:log.NVRAMFull> Slot-1: NVRAM is full, old messages are overwritten.
02/03/2024 09:10:36.14 <Warn:log.NVRAMFull> Slot-2: NVRAM is full, old messages are overwritten.
02/03/2024 09:09:58.25 <Warn:log.NVRAMFull> Slot-1: NVRAM is full, old messages are overwritten.

How to manage this space?

How to deal with the growing of the logs saved there?

How much is the capacity of storage on NVRAM?

1 ACCEPTED SOLUTION

Gabriel_G
Extreme Employee

Hello!

This log simply indicates that the NVRAM log buffer (show log messages nvram) has become full and old log messages are being overwritten. This occurs normally and can generally be ignored as there is nothing to manage here.

To answer your questions specifically:

How to manage this space?

-> There is nothing to manage and no commands to manage this space. This log is technically severity warning so that it shows up in NVRAM log buffer (warning severity and above) but is mostly just an informational log.

How to deal with the growing of the logs saved there?

-> This is normal and OK. You can technically filter or limit the number of logs saved to nvram via 'configure log target nvram' commands, but it is not required as the log buffer will always get full at some point unless you disable this log target completely.

How much is the capacity of storage on NVRAM?

-> About 150 log messages


If you don't like these logs, you can hide them with the following command:
configure log filter DefaultFilter add exclude events log.NVRAMFull

Hope that helps!

View solution in original post

1 REPLY 1

Gabriel_G
Extreme Employee

Hello!

This log simply indicates that the NVRAM log buffer (show log messages nvram) has become full and old log messages are being overwritten. This occurs normally and can generally be ignored as there is nothing to manage here.

To answer your questions specifically:

How to manage this space?

-> There is nothing to manage and no commands to manage this space. This log is technically severity warning so that it shows up in NVRAM log buffer (warning severity and above) but is mostly just an informational log.

How to deal with the growing of the logs saved there?

-> This is normal and OK. You can technically filter or limit the number of logs saved to nvram via 'configure log target nvram' commands, but it is not required as the log buffer will always get full at some point unless you disable this log target completely.

How much is the capacity of storage on NVRAM?

-> About 150 log messages


If you don't like these logs, you can hide them with the following command:
configure log filter DefaultFilter add exclude events log.NVRAMFull

Hope that helps!

GTM-P2G8KFN