NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
GS748T v5 ignores downloaded startup-config file
Hi community! Downloading a startup-config file to the GS748T v5 (Firmware v6.3.1.16) has no effect. I'm using HTTP text-file download via the Web interface. Browser is FF on Linux. The download to...
I'll answer my own question for the benefit of the googlers:
startup-config download works (tested via HTTP) if I set a static switch IP address instead of assigning one via DHCP. Don't ask me why this matters, but it's a workaround anyway.
netgear: Feel free to contact me for details if you wanna fix this. I use the ISC DCHP server v4.3.1 in a pretty straight setup. Test done with 6.3.1.16 and 6.3.1.19 (same behaviour).
BR,
tom
I did the following test with 3 different transfer methods (HTTP using FF, HTTP using IE8, TFTP):
1. Reset the switch to factory defaults and reboot
2. Upload the startup-config from the switch to the computer
3. Edit the "System Name" and "System Location" fields to "ABC" and "123" (to have some easily visible modification). Don't change any other settings.
4. Download the modified startup-config back to the switch
5. Reboot the switch (dunno if this is necessary for the new config to show up)
Expected behaviour:
Switch shows "ABC" as system name and "123" as system location (instead of the default blank fields) in the Web interface.
Observed behaviour:
Download (from computer to switch) confirms a successful file transfer with all 3 methods,
but the transferred file has no effect. Switch still shows blank fields as system name and system location in the Web interface.
Upload (from switch to computer) works only via HTTP and yields identical files with FF and IE8. TFTP upload of text-file config yields a transfer error. TFTP upload of the error log, however, works!
Regards,
Tom
I'll answer my own question for the benefit of the googlers:
startup-config download works (tested via HTTP) if I set a static switch IP address instead of assigning one via DHCP. Don't ask me why this matters, but it's a workaround anyway.
netgear: Feel free to contact me for details if you wanna fix this. I use the ISC DCHP server v4.3.1 in a pretty straight setup. Test done with 6.3.1.16 and 6.3.1.19 (same behaviour).
BR,
tom
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
