Forum Discussion

ed_dsn's avatar
ed_dsn
Icon for Neophyte rankNeophyte
8 months ago

Dynamic Topology Mapping - ISIS only

Is there a way to create a dynamic map depicting only the IGP ?  By default, it appears LM wants to create a map with both the BGP adjacencies and the IGP adjacencies shown.  Basically I want to keep...
  • Anonymous's avatar
    Anonymous
    8 months ago

    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)

     

ed_dsn's avatar
ed_dsn
Icon for Neophyte rankNeophyte

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.

Anonymous's avatar
Anonymous
8 months ago

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)