3750 - copy config from another 3750 switch in production 1

[blade10]

All-

I need to configure 10 3750 switches but use an existing config running on a 3750 in production.

would it be better to copy the running config on the production switch onto a tftp server first then copy up individually to wach switch afterwards.. or can I just copy on a one to one from prod switch to soon-to-be-production swithch...

Of course I'd have to make sure they are labelled properly as these switches will reside in the same location but different parts of the building(s)... are there any other settings in the config i'd need to set to differentiate them so there are no conflicts due to me copying the same config?

any support on this would be great!

thanks

blade

 

[lerdalt]

I think the big thing you need to watch out for is the ip address you put on for management. The way you have described will work. I have copied a config from an existing switch to a TFTP server, then edit that file for each switch I'm going to be deploying, making the necessary changes, then TFTP it back to the startup config on the new switch.

 

[blade10]

thank you lerdalt,

if there are any other "gotchas" you may think of please let me know if you have a moment to respond to this.

be well!

blade

 

[lerdalt]

Not knowing your config, there could be with AAA stuff, but as long as you copy the config to startup, you should be ok. I'd recommend doing one in a test just to be safe.

Otherwise, I can't really think of anything.

 

[blade10]

Lerdalt-

just curious, I have 7 of these switches that I need configured 3 maybe 4 out of the 7 will be management switches..

my question is, could I configure the end-user switches first (roughly 4 switches out of the 7) before I bother configuring the manegement switches..

someone pointed out that one of the 3750s I was working on today was a layer 2 48 port 3750 POE model and that I "might" have trouble with the config copy when its in production unless I configure the managed switch in the stack first..

does this really matter? I plan to tftp all the switches with one specific config then ship them to a different location where I will need to rack and stack and place proper IPs etc etc and then I thought I'd worry about stack port 1 -manager switch to stack port 2 (on 2nd switch) end user switch.. etc etc

I am wrong in assuming this? thanks for any info and appreciate your detail!

blade

 

[lerdalt]

Am I understanding you correctly that you will be stacking the 3750's? If that is the case, then this is going to change a little bit.

The POE model shouldn't be any different configuration wise then the non-POE model, unless you have lines in it for enabling/disabling power on individual ports.

Anyways, in a stacked environment, I find it best to configure the stack first, then put the configuration on it.

 

[blade10]

lerdalt-

hope all is well! looks like I got the configs on master and member switches just fine, yes they are stacked...

just a route question if I may ask to you? I will deploy one 3750 E series at one location which needs to communicate with a older Dell switch at another location )over fiber and the locations are very close to eachother).. I have read that you can do 802.1q trunking for this.. can you help me with the commands for this setup at all? I believe that in the setup you need to specify what exact port is needed to plug in the cat 5 cable at the Dell switch and then back at the 3750.. if there is any info you can provide on this situation please write back to me and thanks! I'll try and figure it out on my side and hope to hear back from u.

blade

 

[lerdalt]

The best I can give you is a sample configuration for the 3750.

On the interface you will be trunking to the Dell switch:
interface gig 1/0/1
description Trunk to Dell Switch
switchport trunk encapsulation dot1q
switchport mode trunk

 

[blade10]

thank you so much lerdalt, this will do great but is there anywhere here I need to specify an actual port number? for cisco to know what port on the Dell switch this will act as the dot1q trunk?

thanks again!

blade

 

[burtsbees]

Whatever the cisco connects to, as long as it's another trunk port with matching vlan tagging protocol, the cisco will know what port is connected to it. No additional configuration needed.

Burt