• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 318
  • Last Modified:

copy switch config

I asked a question about cisco vs. hp switches here 2 days ago, and got some really helpfull answers.
Today I found out that all that needs to be done on the new HP switch is- it needs to be configured exactly like another already production running switch.
My final question on this issue is.....
Can I copy a startup config over from one HP switch to another, maybe through a TFTP server like it is done on Cisco gear?, or are there any other time saving techniques that can be applied.
That would make my life so much easier, and save bundles of time.
Have a great day
2 Solutions
Yes you can copy the config
by two ways :

Log into the web interface (if enabled) and go to the tab labeled "Diagnostics", then "Configuration Report". This tab contains a text copy of the running configuration.

from ftp
copy startup-config tftp <tftp-ip-addr> <filename>


copy running-config tftp <tftp-ip-addr> <filename>

to recover it to the other switch just do the inverse !

copy tftp startup-config <tftp-ip-addr> <filename>


copy tftp runnning-config <tftp-ip-addr> <filename>

dont forget to save the confige in this case .
Yes.  I have previously deployed 40 HP Switches by copying in configs.  This was a few versions ago and the syntax changed which Osmoze covered.  

Don't forget that when you copy in the new config the IP address and STP/RSTP priority numbers will change to be identical to your other HP switch too which could cause a problem. If you were connecting both to your network, make sure you change the IP address before you copy to the running-config.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now