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

Migrating Cisco 3750 to 9300

Which method is best to migrate the configuration of a Cisco 3750 core stack switches to a new Cisco 9300 core stack. Replacing 4 switches with a the new. Any advice is very much appreciated.
1
crjaq
Asked:
crjaq
2 Solutions
 
kevinhsiehCommented:
Can you have downtime? The easiest thing to do is copy the configuration from the old devices, and then paste into the new switches after you have VSS configured. Adjust anything that wasn't accepted without error on the new switch. Remove old switches from the rack and put new switches in the same place. Reattach cables to new switches. Test.

If you don't know how to do what I just described, you should get professional assistance.
0
 
JustInCaseCommented:
Generally, kevinhsieh approach is OK, I would suggest some changes to it to reduce downtime. Since not all configuration can be copied, just some portion can be copied. If QoS is configured on 3750 it must be configured with different set of commands since Catalysts 3750 and 9300 are using different IOS (IOS vs IOS XE 16 (Everest)). According to documentation stacking is supported on Cat 9300, VSS is not.

Generally approach would be:
- make sure that both switches have the same IOS version (upgrade/downgrade to the same version)
- read Open Caveats for device to estimate is some known bug that may affect production
- create stack
- copy paste what you can
- rewrite/adapt portion of code that can't be copy pasted
- test
- factory default device and configure device again
- double check configuration before prior going to production is everything in place
- prepare pretest and posttest for implementation
- perform pretests on old device before implementation
- if everything as well prepared, you will miss all the fun, it will be boring (just the way I like it)
- perform posttest on new device and compare against pretest if everything is OK

I would actually test new switch stack outside of production network first,  to check commands which will be accepted, prepare/rewrite the rest of the configuration and test new configuration. When you think it is ready you can go into production.  Which approach to adopt for implementation switch in production depends on many factors, maximum downtime, possibility of adding redundancy (current design and free rack space) etc...

The Police song Darkness

Life was easy when it was boring
The same is with well prepared implementation.
1
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.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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