-
Notifications
You must be signed in to change notification settings - Fork 4
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
No Peer issue in manifest output #106
Comments
This is correct result. In this example, Host So we are not missing any information here. If the diagram is wrong, it must have processed the information incorrectly.
|
I think the right thing to do, would be to ensure we have isAlias pointing back (so that switch port has isAlias and also host port has it too). For reference: sdn-sense/siterm#524 For host port URI - yes, please - it would be easier mapping back |
It doesn't really matter. One way isAlias is perfectly fine for SENSE model. It may be inconvenient in some cases but the opposite can said for some other cases. |
No peer issue was of unavailable port - that port was removed from siterm fe - but not cleaned. |
While reviewing code, dashboard generations, identified this. The following instance:
returns the following manifest:
And that produces a wrong mermaid diagram due to missing Peer between
T2_US_UCSD_OASIS:oasis
andT2_US_SDSC:sn3700_s0
, see# NO Peer? Issue
. Template used to query is the following:The text was updated successfully, but these errors were encountered: