3 Replies Latest reply on Mar 24, 2017 9:21 AM by zackm

    VRF Interface report

    mbis84

      Hi All,

      I'm looking to generate a report from Orion for all interfaces (physical/svi) in nodes that belong to a particular VRF. I have the VRF name/rd etc. Any suggestion on how to do that?

        • Re: VRF Interface report
          zackm

          I don't have any VRFs in my lab to test real data, but if you make a report with a custom datasource  of the SWQL type, this should get you in the right ballpark:

           

          SELECT 
              v.Name
              ,v.RouteDistinguisher
              ,v.Status
              ,v.Node.Caption
              ,v.Interfaces.Description
              ,v.Interfaces.DistributionProtocol
              ,v.Interfaces.VrfInterfaceType
              ,v.Interfaces.DisplayName
          FROM Orion.Routing.VRF v
          WHERE v.Name LIKE '%Name Goes Here%'
          

           

           

          Let me know if you need more help!

           

           

          -ZackM

          Loop1 Systems: SolarWinds Training and Professional Services

            • Re: VRF Interface report
              mbis84

              Thanks for your reply ZackM. It surely did produce a report with VRFs, but it is incomplete i.e. not all nodes were included. I found that the default poller forVirtual Routing and Forwarding is only enabled in one third of our devices. In the rest, the poller did not find a matching OID. I have to now find out an OID/poller that will enable VRF for other devices also. As always, any hint will be appreciated.

                • Re: VRF Interface report
                  zackm

                  For me, I would either search the NPM Content Exchange, or do some Googling to see if I could find an associated OID that would help. You can also start by using the SNMPWalk.exe utility in the SolarWinds install directory to see what OIDs are responding on your devices so you can narrow down your search.

                   

                  It sounds like you're going to have to create a Universal Device Poller to gather this metric from the unsupported devices.