Wireless Access

Reply
cdj
Contributor I
Posts: 72
Registered: ‎07-17-2013

Could not determine version number of config file.

I've loaded a new config on the controller but everytime I use the command "boot config-file <newstartup-config>" it gives the following message:

 

Could not determine version number of config file.

Error determining current configuration file version.

 

I've tried this with other configs on the controller and they all give me the same output except the default.cfg file which the controller takes.



MVP
Posts: 4,301
Registered: ‎07-20-2011

Re: Could not determine version number of config file.

Please read this :

https://arubanetworkskb.secure.force.com/pkb/articles/HowTo/R-134

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
cdj
Contributor I
Posts: 72
Registered: ‎07-17-2013

Re: Could not determine version number of config file.

Is this still applicable with AOS 3.4.2.2 and 3.4.5.1

MVP
Posts: 4,301
Registered: ‎07-20-2011

Re: Could not determine version number of config file.

Yes

Product and Software: This article applies to ArubaOS 3.3.1.x or later.

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
cdj
Contributor I
Posts: 72
Registered: ‎07-17-2013

Re: Could not determine version number of config file.

I miss spoke, I currently have 3.4.2.2 and 3.4.5.1 on partition 0 and 1 respectfully. The problem is after I following the steps in the document, it still seems to pull from the default.cfg even after the " boot config-file <newstartup-config> command. Also when I do a show boot, it show the config file I want but it just does run that config.

 

Does this solution only apply if you have 3.3.1.x on one of the partitions?

Guru Elite
Posts: 21,257
Registered: ‎03-29-2007

Re: Could not determine version number of config file.


cdj wrote:

I miss spoke, I currently have 3.4.2.2 and 3.4.5.1 on partition 0 and 1 respectfully. The problem is after I following the steps in the document, it still seems to pull from the default.cfg even after the " boot config-file <newstartup-config> command. Also when I do a show boot, it show the config file I want but it just does run that config.

 

Does this solution only apply if you have 3.3.1.x on one of the partitions?


The boot config-file parameter is case sensitive.  If you point to a file that does not exist, it will boot from the default.cfg file.  If you also manipulate a configuration file offline, you could also get the error that you mention as well as that result.  To make sure, please open a case with support so that they get to the bottom of your issue.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: