topic error while tarring/zipping config, config could not be saved in ExtremeSwitching (Other)

error while tarring/zipping config, config could not be saved

dr_watson — Fri, 17 Mar 2017 14:04:00 GMT

Good morning,
i have a question about an Extreme x670 G2 Switch error messages.
We use 2 extreme 670 G2 Switche for the redundant connection our server.
Both are configured as a stack.to upgrade the number of ports if necessary.
When we save the configuration, one switch will displayed me the following error message.

error while tarring/zipping config, config could not be saved on Standbys!

I can see that the configuration file save correctly with the new date and time.
We use version 15.6.4.2 .

On both switches are the sane configuration, one switch displayed me this error-message.
Why?

RE: error while tarring/zipping config, config could not be saved

Ram3 — Fri, 17 Mar 2017 15:34:00 GMT

Please follow the instructions on the below mentioned article:
https://gtacknowledge.extremenetworks.com/articles/Solution/Unable-to-save-configuration-error-while...

RE: error while tarring/zipping config, config could not be saved

dr_watson — Fri, 17 Mar 2017 16:47:00 GMT

Excause me, we have do this before i wrote my question.
Sorry i forgot it to write in my text

RE: error while tarring/zipping config, config could not be saved

dr_watson — Fri, 17 Mar 2017 18:48:00 GMT

Some Information what i have done on myy summit.

rrm /usr/local/tmp/*
NOTE: This will remove all files from /usr/local/tmp.
Continue? (y/N)
Continue? (y/N) Yes
Slot-1 MLAG_205.17 # ls /usr/local/tmp
drwxrwxrwx 2 root root 1024 Mar 14 08:33 dhcp

1K-blocks Used Available Use%
423648 423648 0 100%
Slot-1 MLAG_205.18 #
save configuration
The configuration file primary.cfg already exists.
Do you want to save configuration to primary.cfg and overwrite it? (y/N) Yes
Saving configuration on master .... done!
error while tarring/zipping config, config could not be saved on Standbys!

It is the same error then before.

RE: error while tarring/zipping config, config could not be saved

David_Choi — Mon, 20 Mar 2017 07:34:00 GMT

Hi dr.watson,

In your output, it looks like the usage of internal memory still 100% (not sure why it was not cleared 100%) even though you executed the "rm /usr/local/tmp/*" command.

Slot-1 MLAG_205.17 # ls /usr/local/tmp
drwxrwxrwx 2 root root 1024 Mar 14 08:33 dhcp

1K-blocks Used Available Use%
423648 423648 0 100%

Youn can see that 100% is still used (423648 / 423648) and 0 available (Use% is 100% as well).

I think there might be a possiblity of HW defect on the internal-memory in the swtich. I would recommend kindly open a ticket for this failure and check if this switch should be replaced or not.

RE: error while tarring/zipping config, config could not be saved

Drew_C — Mon, 20 Mar 2017 07:34:00 GMT

GTAC should be able to look at the file usage in depth with debug-mode and can remove any files that might be stuck in the wrong place.
For example, a failed software upgrade could potentially leave files in a temporary folder that users can't access through normal CLI processes.