2 nearly identically topologies, different results. Not sure if either Antimony or Containerlab issue. #2789
-
I have an issue that is driving me crazy and I can't seem to figure out what's happening. I'm using Containerlab v0.69.3 with Antimony as a GUI overlay. I created both topologies inside of the Antimony GUI. Both topologies are using exactly the same kinds of nodes with exactly the same image. (ceos:4.32.0F) Both have 11 nodes, so I don't think it's an issue with server resources. Both topologies have no start-up config. I was thinking it might be a name-space issue because I had previously configured a topology with similar named nodes as a different user, but I've tried wiping every trace of that. Here is everything I've tried:
Nothing seems to work for this topology if the node names are slightly similar to previous node names. Here is some relevant conf and log output, first from the NON-working topology and then from the WORKING topology: ################ NOT WORKING ###############
Containerlab deploy log:
Example device logs:
############## WORKING ###################
Containerlab logs:
Example device logs:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
UPDATE: Apparently the issue was the "-" characters in my hostnames! I'm guessing the issue is the special significance - has in yaml? Eitherway, when I removed that everything worked. |
Beta Was this translation helpful? Give feedback.
UPDATE: Apparently the issue was the "-" characters in my hostnames! I'm guessing the issue is the special significance - has in yaml? Eitherway, when I removed that everything worked.