Forum Discussion
Yeah - unfortunately there is just one option - ROUTING. That appears to encompass BGP, ISIS, OSPF...
And - also interestingly enough - when I deselect the checkmark from ROUTING, nothing seems to happen.
For the "nothing happening" bit, I'd reach out to support.
For the fact that they're all defined as "ROUTING" type, I ask, "what has LM done for topology in the last 5 years except update the icons?"
So, the topology sources are distinct, so there's no reason that the edges shouldn't be distinct. Looking at the BGP TS, it looks like it should be registering three edges, one Routing, one Endpoint, and one BGP Peer. If the TS isn't doing that, LM might be willing to help you figure out why. The code relies on snippets, so it's not easily decipherable what they're doing with it:
def bgpPeerEri = "bgp--" + peerASN + "--" + bgpPeer.peerId
lmtopo.registerEdge("Routing", routerEri, bgpPeerEri, edges)
def bgpEndpointEri = "endpoint:bgp--${bgpAsn}--${bgpId}--${bgpPeer.peerId}"
lmtopo.registerEdge("Endpoint", routerEri, bgpEndpointEri, edges)
def bgpPeerEndpointEri = "endpoint:bgp--${peerASN}--${bgpPeer.peerId}--${bgpId}"
lmtopo.registerEdge("BGP Peer", bgpEndpointEri, bgpPeerEndpointEri, edges)
Related Content
- 23 days ago
- 3 years ago