Looking for Suggestions – Router Naming and Task Improvements

[daniloideconceicao]

Hello Cisco Community,

I recently came across a Dual ISP MPLS Lab on LinkedIn and found it to be a great technical challenge. I’m currently rebuilding this topology in EVE-NG with the goal of deepening my understanding of MPLS VPNs, Inter-AS Option B, Internet Breakout, and MPLS Traffic Engineering, and eventually adding this lab to my GitHub portfolio.

Unfortunately, I wasn’t able to clearly read the router naming from the original topology image. I believe using a consistent and well-structured router naming convention is crucial to ensuring a clean lab environment and a better configuration experience.

I would really appreciate your help in:

Proposing a logical naming convention for routers based on good practices;

Reviewing my task list for the lab and suggesting any improvements or additions.

This lab is part of my ongoing development as a Cisco Certified Professional, and I’d love to make it as solid and realistic as possible. Any feedback or insights would mean a lot!

Thank you in advance,
Danilo Conceição

 

[Ramblin Tech]

I tend to name my nodes in CML either by their role in the network (CE, PE, P, BNG, TOR, AAA, etc) or by their node type (CSR1Kv, ASR9Kv, IOL, etc), appended with a serial number [1..254] that is unique with that lab setup. I then try to incorporate that serial number into the node's various IPv4 addresses [as last octet] and IPv6 addresses [as host interface ID] to the greatest extent that is practical. This leads to IPv4 using only /24 prefixes which is not necessarily real-world, but my trade-off is in ease of troubleshooting. When I ping, traceroute, or see address entries in a table, I know instantly which node that it is in my network.

There are other various tricks you can play with the IP addressing to ease lab troubleshooting, if you do not mind having an address scheme that does not lend itself well to summarization, but these also tend not to be real-world practices.

[daniloideconceicao]

Thank you very much for the feedback, and apologies for not being clear earlier.

I’m not looking for suggestions on naming conventions or IP addressing schemes in general — although I really appreciate those insights.

What I’m actually trying to do is recreate a specific MPLS Dual ISP lab topology that I saw on LinkedIn. I found it very challenging and educational, and I believe replicating it will help me deepen my understanding of MPLS and strengthen my portfolio (especially for GitHub and LinkedIn exposure).

Unfortunately, in the topology image I’ve saved, the router names are not clearly visible, which makes it difficult for me to map everything correctly in my EVE-NG lab.

To move forward, I will attach both the image of the topology and a detailed task list I’ve written based on what I could observe. My request is:
Could someone please help me identify and name the routers in the topology image based on these tasks and the general MPLS architecture being used?

My goal is to keep the structure as close as possible to the original lab, so that I can configure and test everything properly step by step.

Thank you once again for your support and for this amazing community!