Migrating from Cisco 3925 to Catalyst 8200

[Kmizer2013]

Hi everyone, im new to the community and hope im posting this in the right spot. I have some Cisco experience, but am admittedly limited in my knowledge. I recently got hired into a small company as a tech assistant, and quickly got thrusted into the admin roll because of issues with the last admin (Long story short).

We currently have a Cisco 3925 Integrated Services router, which Cisco ended support for near the end of 2022. The admin prior ordered a Catalyst 8200 roughly 6 months ago, and it just arrived. Im wondering if there is a simple/quick way to migrate to the new router. Ill be doing this after hours to limit any network downtime, but I want to be sure I can complete this in a timely manner. My first thought was to TFTP the old router config out, and upload it to the new router, but im guessing its not going to be quite that simple?

To better explain the setup, we only utilize two WAN ports (One SFP, one Ethernet) and one LAN port (Ethernet to a core switch, 4507R+E). We have around 20 VLAN's setup for each department, which is my biggest concern. Any input or thoughts would be greatly appreciated as I (hopefully) learn and grow into this roll.

Thank you!

-Kyle

[M02@rt37]

Hello @Kmizer2013,

Beacuse there isn't a lot of interfaces, you could prepare you configuration and copy/paste directly the config from CLI.

Check SFP compatibility for your C8200:

https://tmgmatrix.cisco.com/?npf=1241

[Leo Laohoo]

I am not concerned about the configuration.  I am terrified about the "under the hood" features that are enabled/disabled.

Things like licenses enabled or purchased (UC, Security, Bandwidth, etc), did the router came in autonomous or SD-WAN image, is the firmware updated to an MD release (as opposed to an ED release), is the 10 Gbps optics license enabled, etc.?

[Joseph W. Doherty]

The "simple/quick way to migrate to migrate to the new router", but possibly not least expensive, would be to contract out the migration.

I'm a bit surprised to read your biggest concern is dealing with 20 VLANs as often a WAN router is often "blind" to VLANs.

If you do proceed alone, expect to "stub your toe", often, but it should be a great learning experience.

[Leo Laohoo]

---

@Joseph W. Doherty wrote:
it should be a great learning experience.

---

And expand one's "vocabulary".

[DanielP211]

I would recommend that you check the current configuration. I doubt you have VLANs set up at the edge. There is likely a routing protocol and a connecting subnet between the CORE and WAN EDGE router.

The best approach is to start slowly by copying the configuration to a notepad and marking everything you don't understand. Once everything is clear, try migrating the configuration to the new device. Be cautious of port re-numbering, features, ACLs, and especially licenses.

[johnlloyd_13]

hi,

check if it has smartnet warranty. you can leverage TAC for guidance and verify your config.

you can also paste your config. just hide sensitive info/public ip.

the community forum will try to help with your config.