nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Web Management Archive funtion

michaels2408

I am using an ICX7250-24P with firmware 9.0.10j_cd1. According to the web management pdf saving a running archive from the web management console --> management --> infra is possible using the 'Save Running Config as Archive' button. The PDF references the naming convention for the archive as CX7K_ARCHIVE followed by _## where ## is the archive number. I have set the archive size to 50 but when I try to save the running archive using the mentioned naming format I continually get the ERROR: error - the input file name does not follow the archive naming convention. I have tried several different types of file names - CX7K_ARCHIVE, CX7K_ARCHIVE_0, CX7K_ARCHIVE_1, CX7K_ARCHIVE_00, CX7K_ARCHIVE_01. What is the correct archive naming convention?

Find more posts tagged with

Accepted answers

All comments

inphobia

seems you're missing the leading "I", it's icx7k, not cx7k.

at least that's how it is on 7850's running 10.0.10/20

example: ICX7K_ARCHIVE_51

edit: after my next reply, the number you use always needs 2 digits, so "01" insteaf of "1" for example.

Chandini

Hi Michaels2408

Thank you for reaching us

Below are few links that will help you with checking ICX archive process. Please run through them and let me know if you have tried them

From Web:

From CLI:

The error you mentioned is related to naming convention. Make sure prefix matches. Below is a snip from the document.

I hope this helps.

Thanks

inphobia

perhaps the documentation could be a bit clearer, i also struggled with this at first. as you highlighted it says

"The archive-naming convention requires archive names be prefixed with the predefined string "ICX7K_ARCHIVE"

firstly, this is somewhat incorrect, it needs to be prefixed with "ICX7K_ARCHIVE_" (note the trailing underscore), the web manual omits that part.

while you can deduce from the example the the "archive naming convention" is 2 digits from the cli docs, i never found this mentioned in detail. also it needs to be exactly 2 digits, so you might need to prefix it with 0.

2 bonus items:

the cli guide mentions a "golden archive", and while i can most likely guess what that means it's not to be found in the guide:
https://docs.commscope.com/search?bundle=fastiron-09010-managementguide&q=golden

the web guide like to call it "archive-naming convention" with a dash between archive & naming, cli says "archive naming convention" without a dash.

Chandini

Hi Inphobia

Ack and Thanks for providing your feedback.

inphobia

when i started looking over cfg-archive docs in the 10.0.20 command reference i found quite some inconsistencies (or just plain errors).

instead of posting that whole lot here, what do you suggest? there is always the document feedback email address; but just for cfg-archive i already have 7 different pages with errors (minor ones, like parameters not listed as required, or visa versa , copy/paste errors, those kinda things)

also: any suggestion on how consistency can be reported. cfg-archive for example, the links you provided all speak of "archive naming convention" (with or without a dash), but in the command reference this isn't mentioned at all, they do mention "archive serial numbers" there (which references the 2 digits at the end of the string).

and finally: i have reported a few typos in the actual by opening a case, but this is way to much overhead for us and you, where do i report those?
minor stuff like this:
SSH@campus-core1#cfg-archive management show-current-config
Show the conf_archive configuration

-> i can guess what "conf_archive" refers to, but that's not used anywhere else, either use cfg-archive or configuration archive....

thx in advance

Chandini

Hi Inphobia

Thank you for your feedback.

I would suggest to drop a email to the Ruckus documentation team with regard to error correction or typos. If facing any issue please feel free to let us know. It would be taken care.

Thanks

inphobia

did exactly that and while it took a few days i got a response & they'll be looking my very long mail to see if this can clear up some confusion.

Chandini

Hi Inphobia

Ack and Thank you for your time in providing feedback.

Thanks