Procurve 2824 restoring config from old switch to new switch
Hi there We have had some trouble with a Procurve 2824 (J4903A) switch so as a precautionary measure we have bought a replacement to have ready as a hot swap spare. I have copied off of the original switch the following files;
flash,
running-config
startup-config.
On the new switch I have copied the flash file from the old switch and rebooted the switch. I then tried to copy the startup-config but received the following errors;
Line 53. Incomplete Input: high
Line 54. Incomplete Input: high
corrupted download file.
Just to be sure I re-copied the startup-config from the old working switch and tried to re-copy but received the same message.
What can i do as i need to have the new switch ready to swap out if the original switch dies with the same config as the original switch.
Thanks
Switches / Hubs
Last Comment
boders67
8/22/2022 - Mon
MrJemson
What is line 53 and 54 of the old config?
There is probably a conflict in the synax from the old switch to the new...
Please post to config if you can.
boders67
ASKER
Thanks for looking at this problem. The config is as listed below
; J4903A Configuration Editor; Created on release #I.08.56
hostname "Main Core"
interface 1
name "Mitel_3300"
exit
interface 2
name "Network_DHCP"
exit
interface 7
name "Mitel_Tracker"
exit
interface 17
name "DMZ"
exit
interface 18
name "DMZ"
exit
interface 19
name "DMZ"
exit
sntp server 192.168.1.14
ip routing
timesync sntp
sntp unicast
sntp 600
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
forbid 1,17-19
untagged 2-6,8-11,13-16,20,22-24
ip address 192.168.1.249 255.255.255.0
no untagged 1,7,12,17-19,21
exit
vlan 10
name "Voice"
forbid 2,17-19
untagged 1,7,12,21
ip address 193.168.1.249 255.255.255.0
tagged 3-6,8-11,13-16,20,22-24
exit
vlan 20
name "D M Z"
untagged 17-19
no ip address
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder sensitivity high
fault-finder sensitivity high
ip route 0.0.0.0 0.0.0.0 192.168.1.1
Does that mean i change the line from
fault-finder sensitivity high to fault-finder sensitivity high All or
fault-finder sensitivity All
As this line is duplicated should i delete the extra line?
This error happened on the new switch because it has the newer software on it. If i were to upgrade our original old server to the latest software i am guessing that this too would give the same error. Would this stop the switch from working until that error line is fixed?
I am a little cautious of updating the software as all of our other switches end up here so if it goes down then it is going to be a major problem. Is it wise to update or to leave it as it is?
Thanks
MrJemson
It would be:
fault-finder sensitivity high all
You can delete the second line.
May as well leave the swtches on the current software.
Unless you want to standardize everything, in which case upgrade the software and change the config accordingly, as you are correct in saying you will have the same issue on the other switch if you upgrade the software.
The fault-finder line just relates to the HP fault finder application.
The switch will work fine without this line anyway.
boders67
ASKER
Mr Jemson, thank you so much for your swift and accurate advice. these forums are a life saver when you find yourself in an uncertain position and not wanting to muck things up. I updated my switches this weekend and after a short heart stopping moment while the switches rebooted they all came up and are functioning as they should. Thanks again for your help
There is probably a conflict in the synax from the old switch to the new...
Please post to config if you can.