-
Notifications
You must be signed in to change notification settings - Fork 22
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
MPLSWatcher - Labels, LSPs, Mappings. #53
Comments
thanks @fischerdouglas for the feedback!
yes, I have, but I'm limited by Topolograph design to get maximum what I can get from the network via a single connection to it :) Since Topolograph builds its network view from LSDB, I can onboard to Topolograph everything what LSDB has. In the sense of LSP - it would require a connection to PE routers and getting details about ingress/transit/egress LSP (output also depends on vendor). It's not a problem from network automation perspective - it's possible to achieve vendor agnostic via Netbox and prepare
Regarding labels - I can onboard Source Routing labels, since they are shared in LSDB across area.
L2/L3 mapping it's a challenging task where Netbox may be also helpful. If we have routerA with established Adj to routerB we can build L2/L3 mapping if Netbox has routerA and routerB with all links filled into it, then we can make a call
|
Hum... Just wondering in my mind, and echoing here...
|
thanks for sharing ideas, sounds interesting! ) |
This tools are incredible! Excellent work!
I will adopt and recommend it.
Have you considered an equivalent view of MPLS things?
At least the basic Labels.
But it would be great if it could show LSPs.
Even greater if would permit to see the L2/L3 vs Labels vs PEs Mappings.
The text was updated successfully, but these errors were encountered: