Cisco Switch Swap

We currently have 3 sites. Each site has a Cisco 3560  switch that serves as default gateway for each site. These are 10/100 switches and have 15 years of config changes layered in. A lot of the config pertains to a phone system we no longer have. I'd like to swap out the switches for new GB switches and start fresh. All sites have their own /24 subnets. I'm looking for programming and recommendations on how to go about swapping these outbasic-network.jpgbasic-network.jpg. Initial plan was to swap Cisco for Cisco but open to other suggestions. Please see the four notes below.

1. Currently there is a P2P between Site 1 and Site 2. This needs to stay.

2. Currently there is a VPN between Site 1 and Site 3. This can go away once we have a P2P between Site 3 and Site 1.

3. Site 2 needs to have a new subnet added, and be able to communicate to all existing subnets at the other sites. This new subnet will be 10.X.X.X/22 because I'm out of addresses on current 192.168.2.X/24 private subnets.
      I'd like the new subnet to use DHCP on the new switch.

4. Each site has it's own ISP so routes will need to include that access.


I'd appreciate any initial thoughts or ideas.
HELFITAsked:
Who is Participating?
 
Garry GlendownConnect With a Mentor Consulting and Network/Security SpecialistCommented:
Replacing the Cisco switches with newer models (e.g. 3850 w/ L3) is of course the simplest thing to do, as - apart from renaming the interface - there's relatively little you'd need to do in order to get everything to work like before. Anyway, I'd definitely recommend doing a fresh config in order to get rid of stuff known to be unused.

Your points 1 and 2 are so far not a problem, #3 shouldn't be, either. Just set up the VLAN, configure the IPs for L3 communication, and add the route to the 10.* subnet on the other two L3 switches towards the one at Site 2. DHCP also shouldn't be a problem. Just add multiple pools, the internal software takes care of supplying the IPs matching each VLAN it receives requests on.
#4 should remain unchanged, also, just keep the default route towards the ISP router. The 192.168.* and 10.* routes are more specific, so they will remain to be preferred over the default route.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.