12 Replies Latest reply on Jul 17, 2017 2:45 PM by eherrera2528

    Discover Interfaces on node (powershell and curl)

    jdrouet

      I am running into an issue with trying to add interfaces on a node that I was successfully able to add by either powershell or curl.

       

      For powershell I am running the command:

      $discovered = Invoke-SwisVerb $swis Orion.NPM.Interfaces -verb DiscoverInterfacesOnNode 1647

       

      Which returns the error:

      Invoke-SwisVerb : The operation has timed out.

      At C:\Data\Powershell\solarwinds_insert.ps1:68 char:15

      + ... iscovered = Invoke-SwisVerb $swis Orion.NPM.Interfaces DiscoverInterf ...

      +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

          + CategoryInfo          : InvalidOperation: (:) [Invoke-SwisVerb], FaultException`1

          + FullyQualifiedErrorId : SwisError,SwisPowerShell.InvokeSwisVerb

       

      With CURL I am running the command:

      curl -k -u yyyyyyy:xxxxxxx -k --tlsv1.0 -H "Content-Type: application/json" -X POST "https://<server>:17778/SolarWinds/InformationService/v3/Json/Invoke/Orion.NPM.Interfaces/DiscoverInterfacesOnNode" -d "["1647"]"

       

      Which returns the error:

      {"Message":"The operation has timed out.","ExceptionType":"System.TimeoutException","FullException":"System.TimeoutException: The operation has timed out.\u000d\u000a   at SolarWinds.InformationService.Verb.VerbExecutor.Invoke(Object hostInstance, Object[] parameters)\u000d\u000a   at SolarWinds.InformationService.Verb.VerbExecutorContext.Invoke()\u000d\u000a   at SolarWinds.InformationService.Core.InformationService.Invoke[T](String entity, String verb, Action`1 setupParameters, Func`2 extractReturnValue)"}

       

      I have been able to push and pull lots of information, and manually discovering and adding the interfaces through the web GUI works fine.  The timeout occurs around 5 minutes for the curl and powershell commands which hopefully means there is a timeout adjustment which can be made.  Although discovering the interfaces on the web gui does not take nearly this long...

       

      Will be very appreciative of any assistance.  Even the logs that I looked at did not show much, although I am not entirely sure I was looking at the correct logs.

       

      Message was edited by: Jeff Drouet Fixed the wrong error output for the CURL version.

        • Re: Discover Interfaces on node (powershell and curl)
          tomas.vrabel

          Try to increase timeout for DiscoverInterfacesOnNode operation:

          Default timeout is 300 seconds.

          Default value can be overriden in config file {ORION_INSTALL_PATH}\SolarWinds\Orion\Information Service\3.0\Plugins\SolarWinds.Data.Providers.NPM.v3.dll.config, change value for key "DiscoverTimeout". Restart of SWISv3 is needed to reload this setting.

           

           

          Config file example:

          <?xml version="1.0" encoding="utf-8" ?>

          <configuration>

            <appSettings>

              <!-- Timeout in seconds -->

              <add key="DiscoverTimeout" value="300"/>

            </appSettings>

          </configuration>

          1 of 1 people found this helpful
            • Re: Discover Interfaces on node (powershell and curl)
              eherrera2528

              Hi Guys,

               

              about the thread:

              tomas.vrabel wrote:

               

              Try to increase timeout for DiscoverInterfacesOnNode operation:

              Default timeout is 300 seconds.

              Default value can be overriden in config file {ORION_INSTALL_PATH}\SolarWinds\Orion\Information Service\3.0\Plugins\SolarWinds.Data.Providers.NPM.v3.dll.config, change value for key "DiscoverTimeout". Restart of SWISv3 is needed to reload this setting.

               

               

              Config file example:

              <?xml version="1.0" encoding="utf-8" ?>

              <configuration>

                <appSettings>

                  <!-- Timeout in seconds -->

                  <add key="DiscoverTimeout" value="300"/>

                </appSettings>

              </configuration>

              I have been reviewing this solution and made the change in the Orion application but the same error still occurs. The only thing I could adjust was the timeout for the SWQL now the error that jdrouet exposes does not appear, but the service does respond with timeout. Why the application does not return a timeout and the SWIS does, the time it takes is about 7 minutes to perform the discovery interface action.

               

              timeoutError.png

               

              anyone can help me to resolve it? Thanks.

               

              tomas.vrabel tdanner

               

              Regards

                • Re: Discover Interfaces on node (powershell and curl)
                  tdanner

                  How long after clicking the "invoke" button does it take before you get that error response in SWQL Studio?

                    • Re: Discover Interfaces on node (powershell and curl)
                      eherrera2528

                      Thanks tdanner, I have changed the time from 500 to 700 because up to error response it was taking 5 minutes, so when i did it i receive the next result:

                      timeoutError.png

                       

                      The response time is the that appear on timer.

                       

                       

                      Thanks for your support.

                        • Re: Discover Interfaces on node (powershell and curl)
                          tomas.vrabel

                          This is strange, seems like communication problem between Orion services.

                          The name suggest that error is transient - do you receive same error all the time?

                           

                          Following questions should narrow the problem down:

                          1) do you receive same error all the time you invoke the verb for this node?

                          2) do you receive same error when you invoke verb for different node?

                          3) does the interface discovery works in Orion UI?

                          4) does this error occurs after restart of all Orion services (e.g. using Orion Service Manager)?

                          5) could you please check InformationService V3 log files for related exception, is there more information inside log files (full stack trace, some other related exception)? (SWIS V3 logs can be found under c:\ProgramData\SolarWinds\InformationService\v3.0\)

                            • Re: Discover Interfaces on node (powershell and curl)
                              eherrera2528

                              Hi tomas.vrabel, no i has been checking this exercise again but now im receiving the same error:

                               

                              timeoutError.png

                              answering your questions:

                               

                               

                              1. Does not always show the same error as explained above.

                              2. I do not receive the same error with another node, but I get it with nodes that have more than 1,000 interfaces.

                              3. Yes it works in Orion UI, It takes about 7 minutes but it works.

                              4. Yes, this error occurs after restarting the services with Orion Service Manager

                              5. No i can't find any log in the path that you indicated.

                                  

                              Thanks for your support.

                                • Re: Discover Interfaces on node (powershell and curl)
                                  tdanner

                                  The logs are in c:\ProgramData\SolarWinds\InformationService\v3.0\ (not under Program Files (x86)).

                                    • Re: Discover Interfaces on node (powershell and curl)
                                      eherrera2528

                                      Thanks tdanner:

                                       

                                      This is my Server Log:

                                       

                                      2017-07-05 08:52:25,992 [117] ERROR SolarWinds.InformationService.Core.InformationService - (null) (null) Exception for Operation: <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

                                        <s:Header>

                                          <a:Action s:mustUnderstand="1">http://schemas.solarwinds.com/2007/08/informationservice/InformationService/Invoke</a:Action>

                                          <a:MessageID>urn:uuid:a45847f5-4a6e-4edd-8a9b-4bf190ab6596</a:MessageID>

                                          <a:ReplyTo>

                                            <a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>

                                          </a:ReplyTo>

                                          <i18n xmlns="http://schemas.solarwinds.com/2007/08/informationservice" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

                                            <Culture>en-US</Culture>

                                          </i18n>

                                          <SwisProtocolVersion xmlns="http://schemas.solarwinds.com/2007/08/informationservice">2</SwisProtocolVersion>

                                          <IsBase64EncodingAccepted xmlns="http://schemas.solarwinds.com/2007/08/informationservice">true</IsBase64EncodingAccepted>

                                          <a:To s:mustUnderstand="1">net.tcp://10.120.1.5:17777/SolarWinds/InformationService/v3/Orion/ssl</a:To>

                                          <o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

                                            <u:Timestamp u:Id="_0">

                                              <u:Created>2017-07-05T13:47:19.940Z</u:Created>

                                              <u:Expires>2017-07-05T13:52:19.940Z</u:Expires>

                                            </u:Timestamp>

                                            <c:SecurityContextToken u:Id="uuid-141d7d2b-276c-4135-8625-500f91a9d617-34423" xmlns:c="http://schemas.xmlsoap.org/ws/2005/02/sc">

                                              <c:Identifier>urn:uuid:1d40e7c9-2b9f-4953-ab41-3a42400925b4</c:Identifier>

                                            </c:SecurityContextToken>

                                            <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">

                                              <SignedInfo>

                                                <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">

                                                </CanonicalizationMethod>

                                                <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1">

                                                </SignatureMethod>

                                                <Reference URI="#_0">

                                                  <Transforms>

                                                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">

                                                    </Transform>

                                                  </Transforms>

                                                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1">

                                                  </DigestMethod>

                                                  <DigestValue>wBLGtVhr7E+iv4sae3HrEcMputM=</DigestValue>

                                                </Reference>

                                              </SignedInfo>

                                              <SignatureValue>cV7cU2k/KePWwwzpLqPh3Gq6CIU=</SignatureValue>

                                              <KeyInfo>

                                                <o:SecurityTokenReference>

                                                  <o:Reference URI="#uuid-141d7d2b-276c-4135-8625-500f91a9d617-34423">

                                                  </o:Reference>

                                                </o:SecurityTokenReference>

                                              </KeyInfo>

                                            </Signature>

                                          </o:Security>

                                        </s:Header>

                                        <s:Body>

                                          <Invoke xmlns="http://schemas.solarwinds.com/2007/08/informationservice">

                                            <entity>Orion.NPM.Interfaces</entity>

                                            <verb>DiscoverInterfacesOnNode</verb>

                                            <parameters xmlns:b="http://schemas.datacontract.org/2004/07/System.Xml" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

                                              <b:XmlElement>

                                                <arg xmlns="">6</arg>

                                              </b:XmlElement>

                                            </parameters>

                                          </Invoke>

                                        </s:Body>

                                      </s:Envelope>

                                      2017-07-05 08:52:26,008 [117] ERROR SolarWinds.InformationService.Core.InformationService - (null) (null) Exception caught in method SolarWinds.InformationService.Core.InformationService.Invoke

                                      System.TimeoutException: The operation has timed out.

                                         at SolarWinds.InformationService.Verb.VerbExecutor.Invoke(Object hostInstance, Object[] parameters)

                                         at SolarWinds.InformationService.Verb.VerbExecutorContext.Invoke()

                                         at SolarWinds.InformationService.Core.InformationService.Invoke[T](String entity, String verb, Action`1 setupParameters, Func`2 extractReturnValue)

                                      2017-07-05 08:55:53,713 [82] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 08:55:53,713 [82] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:01:54,090 [85] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:01:54,090 [85] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:03:53,967 [80] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:03:53,967 [80] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:05:54,065 [79] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:05:54,065 [79] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:07:53,988 [37] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:07:53,988 [37] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:15:54,660 [84] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:15:54,660 [84] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:17:54,381 [19] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:17:54,381 [19] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:19:54,679 [81] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:19:54,679 [81] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:21:54,977 [64] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:21:54,977 [64] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:25:55,306 [7] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:25:55,306 [7] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 09:28:36,324 [60] INFO  SolarWinds.Data.Providers.Orion.Containers.LimitationSnapshotService.DAL.LimitationSnapshotDAL - (null) (null) Static String Cache lost 772 items.

                                      2017-07-05 09:28:36,324 [60] WARN  SolarWinds.Data.Providers.Orion.Containers.LimitationSnapshotService.DAL.LimitationSnapshotDAL - (null) (null) Entity Uri Cache lost 2 keys.

                                      2017-07-05 09:28:36,340 [60] INFO  SolarWinds.Data.Providers.Orion.Containers.LimitationSnapshotService.DAL.LimitationSnapshotDAL - (null) (null) Entity Uri Cache lost 659 items.

                                      2017-07-05 09:29:30,387 [58] WARN  SolarWinds.Orion.Core.Common.WCFChannelFactory`1 - SolarWinds.BusinessLayerHost| domain-SolarWinds.Orion.Core.BusinessLayer.DLL| SolarWinds.Orion.Core.Common.DALs.LicensingDAL.GetLicenses()|  (null) System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

                                       

                                       

                                      Server stack trace:

                                         at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)

                                         at System.ServiceModel.Channels.ServiceChannel.System.IDisposable.Dispose()

                                       

                                       

                                      Exception rethrown at [0]:

                                         at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

                                         at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

                                         at System.IDisposable.Dispose()

                                         at SolarWinds.Orion.Core.Common.WCFChannelFactory`1.DisposeChannel(T channel)

                                      2017-07-05 09:29:30,434 [58] INFO  SolarWinds.Orion.Core.Common.WCFChannelFactory`1 - SolarWinds.BusinessLayerHost| domain-SolarWinds.Orion.Core.BusinessLayer.DLL| SolarWinds.Orion.Core.Common.DALs.LicensingDAL.GetLicenses()|  (null) Channel LicenseServerContract to net.tcp://viptest:17777/orion/licensing/licenseserver Opened

                                      2017-07-05 09:29:55,028 [64] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 09:29:55,028 [64] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:09:56,357 [7] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:09:56,357 [7] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:11:56,483 [86] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:11:56,483 [86] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:13:56,656 [22] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:13:56,656 [22] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:17:56,705 [50] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:17:56,705 [50] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:27:57,035 [50] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:27:57,035 [50] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:29:57,271 [21] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:29:57,271 [21] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:31:57,053 [86] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:31:57,053 [86] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:41:57,602 [53] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:41:57,602 [53] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:43:57,900 [60] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:43:57,900 [60] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:55:57,803 [85] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:55:57,803 [85] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:57:58,337 [49] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:57:58,337 [49] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 10:59:58,340 [62] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 10:59:58,340 [62] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 11:03:58,030 [85] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 11:03:58,030 [85] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 11:35:59,893 [21] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 11:35:59,893 [21] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 11:37:59,911 [20] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 11:37:59,911 [20] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                      2017-07-05 11:41:59,756 [14] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Clearing cache for all users

                                      2017-07-05 11:41:59,756 [14] INFO  SolarWinds.InformationService.Core.QueryPlanCache - (null) (null) Cleared cache for all users

                                       

                                      Thanks guys, I really appreciate your help because I need to resolve this situation as soon as possible, I'm seeing that it has no effect changing the seconds in the XML.

                                       

                                      If you have any solution please let me know

                                        • Re: Discover Interfaces on node (powershell and curl)
                                          tdanner

                                          There's another timeout that we might be hitting. In C:\Program Files (x86)\SolarWinds\Orion\NPM\SolarWinds.NPM.BusinessLayer.dll.config, find this section:

                                           

                                                  <binding name="NPM.NetTcpBinding" sendTimeout="00:05:00" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647" portSharingEnabled="true">

                                                    <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" />

                                                    <security mode="TransportWithMessageCredential">

                                                      <message clientCredentialType="UserName" />

                                                    </security>

                                                  </binding>

                                           

                                          And change the "sendTimeout" value to something larger. Save and restart the "Orion Module Engine" service.

                                            • Re: Discover Interfaces on node (powershell and curl)
                                              eherrera2528

                                              Hi tdanner excuse me by my delay. This is the result of the changes that you says before:

                                               

                                               

                                              I have the following questions:

                                               

                                               

                                              1. Does the Orion platform allow you to partition the data stored in your database, in order to improve the response times of the queries?

                                              2. Does the Orion web application allow paging of data queried by blocks, for example, query all the interfaces of a batch device?

                                              3. Is it possible to get the query result on a device thousands of interfaces in less than a minute? If possible, through which function?

                                              4. Through the Orion SDK, is it possible through web services to get thousands of interfaces records queried on a device, in less than a minute? If possible, in what way?

                                              5. Which strategies are recommended for querying devices with a large number of configured elements. For example, interfaces, services, etc.

                                              5. Does the Orion platform have tracking functionality for possible security attacks through traffic monitoring?

                                              6. Does the Orion platform allow the monitoring of traffic of a device, passing through a virtual (logical) network firewall?

                                                • Re: Discover Interfaces on node (powershell and curl)
                                                  tdanner

                                                  There are a number of timeouts in the system. Apparently increasing that one wasn't enough to get this operation to succeed. Let me answer your numbered questions first:

                                                   

                                                  1. We do have a guide on configuring SQL Server and its hardware for best performance in Orion (SQL Server Configuration Best Practices - SolarWinds Worldwide, LLC. Help and Support ). However, the problem you are having here is not caused by database performance. The problem here is that this API call performs SNMP enumeration of all interfaces on the device before returning. If the device has a very large number of interfaces and is less than snappy at responding to Orion's SNMP queries, then this will take quite a while.

                                                  2. When you are querying data from Orion, you can certainly request it in pages. SWQL syntax includes the "WITH ROWS x TO y" clause to facilitate this. Unfortunately that only applies to SWQL queries and not the DiscoverInterfacesOnNode call.

                                                  3, 4. No, Orion is not able to enumerate that many interfaces on a device that fast.

                                                  5. For some use cases, the Discovery API (Discovery · solarwinds/OrionSDK Wiki · GitHub ) can be used to run these kinds of enumerations as background tasks that are not affected by timeouts on individual API calls.

                                                  5. Orion is not an Intrusion Detection System, but you can do some traffic monitoring using the NetFlow Traffic Analyzer product (for traffic passing through a switch) or the Quality of Experience feature in NPM (for traffic on a host).

                                                  6. If you just mean the quantity of traffic (bytes/packets per second), then normal NPM interface monitoring should work for those virtual interfaces. If you mean more detailed traffic analysis, look at our NetFlow Traffic Analyzer product.

                                                    • Re: Discover Interfaces on node (powershell and curl)
                                                      eherrera2528

                                                      Hi tdanner,

                                                       

                                                      Thanks for your help, these answers give me the basis to validate how I can build automatic solutions in the medium term. On the other hand, I have changed all possible timeouts, at least those that are in 5 minutes by default on the different files into Orion installation path in server, but is still happening that when i click 'invoke' in SWQL it takes five minutes to return a timeout error. Also I changed the timeouts in the SwqlStudio.exe.config file into install path of SWQL in my PC.

                                                       

                                                      So what do you think that i can do in order to resolve this issue?.

                                                       

                                                      PD: Please, remember that this process should be the same List Resource that is done in the Orion UI which takes about 6 to 7 minutes.

                                                       

                                                       

                                                      Thanks guys.