GXP2130 "File upload timeout" when i upload a tiny device configuration file


#1

Hi!

I have a tiny configuration file i’d like to upload to a GXP2130 (Prog 1.0.9.121) to sort-of have a standard config to work from.

However, when i upload it in Maintenance -> Upgrade and Provisioning -> Upload Device Configuration i end up with the error message “File upload timeout. Please try again.”. Very helpful. A bigger file with all sort of Pxx= config parameters loads in seconds and works fine. When i cut off all the unnecessary settings i get this error message.

The config file is this:

# Generated on 01/28/19 by GXP2130 [00:0B:82:6E:C6:98]
# boot 1.0.7.2 core 1.0.9.93 base 1.0.9.105 prog 1.0.9.121
P271=1
P270=Extension XX
P47=192.168.1.121
P48=192.168.1.121
P35=XX
P36=XX
P34=superdupersecretpassword
P3=Extension XX
P33=XX
P2380=0
P63=0
P31=1
P57=0
P58=8
P59=18
P60=9
P61=2
P62=2
P46=2
P98=123
P2301=0
P2302=1
P2303=0
P191=0
P401=0
P501=0
P1487=1
P1301=2
P1302=2
P30=192.168.1.1
P64=CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
P122=1
P334=80
P335=30
P2916=4
P2921=#555555
P2918=0
P6759=0
P8338=0
P1402=0
P1405=1
P1379=c
P1552=http://192.168.1.36:3128/
P1553=http://192.168.1.36:3128/
P2910=0
P8364=gxp2130_XX
P194=3
P8458=1
P285=21
P8459=23
P286=6
P6767=1
P192=gs-firmware.domain.local/
# End of exported configuration

Are there any Parameters that are mandatory? Or can someone point me to some documentation how to correctly build up a config.txt file?

Tanks in advance!
Max


#2

Hm.

Obviously vi and vim change the file in a way that it is no longer re-importable if you edit it.

Steps to reproduce:

  • download the device configuration file
  • open the downloaded config.txt with vi or vim on macOS or FreeBSD or Linux
  • change the name (P3=) to something else of the same length
  • write and quit (:wq) the file
  • the resulting file, although it SHOULD be the same size, now is 1 byte longer (WTF?!)
  • try to import the changed config.txt file
  • enjoy the “File upload timeout” error

So the downloaded file may have some special ending that vi or vim is “correcting” and thus renders the result unusable.

Any suggestions on this? I am pretty sure exactly that worked some years ago already (around version 1.0.3 or 1.0.4).

Thanks in advance
Max


#3

OK!

Now it’s getting weird. I just pasted the above config to a NEW file (yes, in vim on macOS), saved it and i could upload it without an issue.

Thx for watching this episode of “Stranger Things”!
Max