3 Replies Latest reply on Feb 7, 2014 6:03 AM by John_K

    Layer 2 Connection and Related Interfaces

    rlejano

      We are trying to integrate Layer 2 Connections from Solar Winds Orion into HP UCMDB.

      UCMDB follows ITIL rules and Layer 2 Connections must be related to 2 or more interfaces.

       

      The dbo.NodeL2Connections table in Solar Winds Orion stores the NodeID and MACAddress.

      NodeL2Connections_zpsb8607562.jpg

       

      Using the dbo.Interfaces table we determined that the MACAddress is related to Interfaces of the second Node of the Layer 2 Connection while the NodeID reflects the first Node of the Layer 2 Connection but these Nodes have many Interfaces in the dbo.Interfaces table and from this table we can not determine both Interfaces related to a Layer 2 Connection.

      We have also joined Port ID in dbo.NodeL2Connections to Port ID in other tables such as dbo.UDT_Port but no PortIDs match.

       

      Does Solar Winds Orion show the Interfaces connected by a Layer 2 Connection? If so, in which table(s)?

       

      Thank you

        • Re: Layer 2 Connection and Related Interfaces
          John_K

          Hello,

           

          yes, you are right - we are trying build L2 connection also from these tables - NodeL2Connections - Interfaces. In nodeL2Connections we store bridge data (CAM table) - so if these devices have been comunicating together, we might stored MAC address on one side.

           

          "Layer 2 Connection but these Nodes have many Interfaces in the dbo.Interfaces table and from this table we can not determine both Interfaces related to a Layer 2 Connection"

          Please clarify. You haven't found corresponding match?

           

          You can use this SQL query to find possible mathces.

           

          A -> B connection

           

          SELECT nodel2connections.nodeid, macaddress, interfaces.interfaceid
          FROM nodel2connection left outer join on nodel2connections.macaddress = interfaces.physicaladdress

          WHERE nodel2connections.nodeid  = A and interfaces.nodeid = B

           

          A <-B - just replace last line - WHERE nodel2connections.nodeid  = B and interfaces.nodeid = A

           

          "Does Solar Winds Orion show the Interfaces connected by a Layer 2 Connection? If so, in which table(s)?"

           

          Check TopologyData (NPM 10.6) / ToplogyConnections (10.7 RC) - if connection was generated, you will find sourcenodeid - mappednodeid and also if we know about interfaces, you will also find details about sourceinterfaceid, mappedinterfaceid.

           

          Hope it helps.

           

           

          Best regards,
          John

          1 of 1 people found this helpful
            • Re: Layer 2 Connection and Related Interfaces
              rlejano

              "Layer 2 Connection but these Nodes have many Interfaces in the dbo.Interfaces table and from this table we can not determine both Interfaces related to a Layer 2 Connection"
              Please clarify. You haven't found corresponding match?


              To clarify, we can find matches with the Interface table but the NodeL2Connections table only tells you one of the interfaces between a L2 connection.

                • Re: Layer 2 Connection and Related Interfaces
                  John_K

                  NPM 10.6 doesn't support multiple connections. For generating L2 connections is more complex logic behind.

                   

                  You can also try matching nodeCiscoCdpEntries (DeviceId)/nodeLlldpEntries(RemoteSystemName) with nodes sysname, if match, check

                  NodeCiscoCdpEntries.DevicePort with Interfaces.InterfaceName
                  NodeLldpEntries.RemotePortId with Interfaces.InterfaceName

                   

                  Multiple connections are planned to implement in future. I think this would be more suitebale for you to check just in one topology table than looking and matching in more tables.

                   


                  Best regards,
                  John