Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How To - Network Topology - draw.io issue #246

Open
NoahParkerAHEAD opened this issue Dec 17, 2024 · 4 comments
Open

How To - Network Topology - draw.io issue #246

NoahParkerAHEAD opened this issue Dec 17, 2024 · 4 comments

Comments

@NoahParkerAHEAD
Copy link

NoahParkerAHEAD commented Dec 17, 2024

When I upload the xml to draw.io I get this error message.

Error
BPWXqFOopaEeQmAnsZIH-4: Duplicate ID

I found the duplicate ID in the xml, but I don't understand how to resolve it.
It is found found twice in the xml:

I want to say one is found in the route table

@Claudio-Merola
Copy link
Collaborator

Hi,

That should not be happening. I don't advice to solve these types of problems directly in the XML file. The logic of the xml file is a little complicated and editing it directly might be a nightmare.

Have you tried to run the script again to generate a new xml file? do you get the same error?

@NoahParkerAHEAD
Copy link
Author

I agree we shouldn't be editing the xml file. I believe that the resource IDs are getting double referenced due to route table subnet association. As well as subnets being reference in the Vnet as well for networking visualization. Have you used this solution in an account that has a route table in it? I am curious if it worked.

@Claudio-Merola
Copy link
Collaborator

Yes, the solution was used in environments with UDRs and UDRs associates with different subnets

@containerpope
Copy link

@Claudio-Merola I have the same issue currently. When I changed some IDs it works again. In my case, the affected network components are linked with private endpoints. I added some numbers to make it work, because I had only 6 conflicts in total, but maybe that screenshot can help to resolve the issue.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants