In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
At the final stage reconfigure all trunks as routed ports reusing earlier created interlinksHowever, I would not do this. I would leave it as a trunk everywhere and the reason would be a little bit different design:
Int fa0/1Will do exactly that - allow only VLAN 201 on trunk.
switchport trunk allow vlan 201
I configured the trunk to allow only vlan254 between sw2 and sw3You removed VLAN 100 from link, and fw is in located in vlan 100. There are several ways to resolve this, for example:
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.
I suggest you overlay your existing connectivity, ie introduce another vlan on each of your trunk ports. Use different vlan number on all switch interlinks (keep them point to point only). Configure layer 3 SVIs and enable eigrp routing across those new interlinks.
That way you can maintain your existing topology intact until you are ready to slowly cutover to layer 3 (at this stage you should have layer 3 links everywhere).
Once you get to the stage where layer 2 is no longer needed start removing obsolete vlans. At the final stage reconfigure all trunks as routed ports reusing earlier created interlinks