This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

NetPath Service not getting created

Has anyone seen this before -

We are able to install a NetPath probe on a system but unable to create any service whether on the intranet or an Internet service.

A support ticket has been raised but it has been quite a while that we are able to get the NetPath Service created.

Some logs from NetPath

2018-10-29 13:14:55,309 [21] DEBUG SolarWinds.NetPath.Bgp.BusinessLayer.BgpBusinessLayerPlugin - (null)  { Stop entered

2018-10-29 13:14:55,309 [21] INFO  SolarWinds.Orion.Common.SWEventLogging - (null)  Bgp Service [HYDNCMAPP01] Stopped

2018-10-29 13:14:55,309 [21] DEBUG SolarWinds.NetPath.Bgp.BusinessLayer.BgpBusinessLayerPlugin - (null)  Stoping Bgp Business Layer Plugin

2018-10-29 13:14:55,340 [Scheduler] DEBUG SolarWinds.Common.Utility.Scheduler - (null)  Checking if Scheduler should shutdown

2018-10-29 13:14:55,340 [Scheduler] INFO  SolarWinds.Common.Utility.Scheduler - (null)  Got ShuttingDownEvent. Exiting.

2018-10-29 13:14:55,340 [21] INFO  SolarWinds.NetPath.Bgp.LocalManager.LocalBgpManager - (null)  Stopping Local BGP Manager

2018-10-29 13:14:55,356 [21] INFO  SolarWinds.NetPath.Bgp.LocalManager.LocalBgpManager - (null)  Stopping Local BGP Manager

2018-10-29 13:14:55,434 [21] DEBUG SolarWinds.NetPath.Bgp.BusinessLayer.BgpBusinessLayerPlugin - (null)  BGP Resolver Business Layer stopped.  Current App Domain: domain-SolarWinds.NetPath.Bgp.BusinessLayer.dll

2018-10-29 13:14:55,434 [21] DEBUG SolarWinds.NetPath.Bgp.BusinessLayer.BgpBusinessLayerPlugin - (null)  } Stop exited

2018-10-29 12:32:18,249 [23] INFO  SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Stopping plugin: "BGP Resolver Business Layer"

2018-10-29 12:32:18,343 [23] INFO  SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Plugin: "BGP Resolver Business Layer" stopped in 0.081 sec.

SW Support states that the BGP Business Layer of NetPath is crashing. Support suggested opening BGP port 43 & port 443 from the Orion server to Internet for site whois.arin.net & stat.ripe.net. But our observation is that - other Orion setups (where NetPath is working) is that the Orion server does not even have Internet access.

Multiple probes have been tried - even the Main Poller as probe.

Security settings on probes like AV & FW exclusion settings on probes as well as Main Poller have been checked and rechecked, but no sign of NetPath service creation success.

At the behest of Support, we have run Configuration wizard too but no light visible at the end of dark tunnel. Unable to find our path emoticons_sad.png err NetPath!!

abdhijasharma nikhil.n csameergangadhar.kbendale.vijay

Case # - 00191002 Netpath configuration

  • Here are some suggestions from my experience if i run into errors similar to yours:

    Check the .Net-Framework Version installed on all servers. It needs to be same on the main poller and the APEs. I saw the weirdest behavior if those versions did not match.

    You could use the Solarwinds Log Adjuster on your main poller and set the loglevel of the BGP Resolver Business Layer to "ALL" or "DEBUG".

    Maybe you will see something useful yourself or you can post the logs here (or PM them to me).

    Best Regards

    Rene

  • Thanks for your inputs, will check the .Net versions definitely. Our logs are set to Debug mode .. Support has been provided with the logs too.

    Is it really necessary to have the whois.arin.net and stat.ripe.net sites opened out to the Main poller for port 43 (BGP) & 443 ?

  • .Net versions on the Main Poller & APE's are the same 4.6.2

  • To be honest i do not think those are "necessary", but thats only my opinion, not based on any technical knowledge. I could imagine if those 2 services are not reachable by the netpath probe, you could see less informations about the hops/nodes located outside of your network. I would trust the solarwinds support regarding this.

    Since your .NET versions are all the same i am currently not much of a help. I did not encounter your issue so far and without any additional logs i could just make suggestions.

    Best Regards

    Rene

  • The problem has been resolved.

    Resolution: The server had a Security service running called URLScan 3.1 (provided by Microsoft).

    The URLScan logs showed

    #Software: Microsoft UrlScan 3.1

    #Version: 1.0

    #Date: 2018-11-15 02:50:30

    #Remark: AllowDotInPath is enabled.  Checksbased on extensions will be unreliable.

    #Fields: Date Time c-ip s-siteid cs-method cs-uri x-action x-reason x-context cs-data x-control

    #Software: Microsoft UrlScan 3.1

    #Version: 1.0

    #Date: 2018-11-15 05:07:45

    #Remark: AllowDotInPath is enabled.  Checksbased on extensions will be unreliable.

    #Fields: Date Time c-ip s-siteid cs-method cs-uri x-action x-reason x-context cs-data x-control

    2018-11-15 06:03:23 10.22.15.133 2 PUT /api2/cloudnetworkmonitor/servicemonitors/0 Rejected verb+not+allowed HTTP+method - -

    #Software: Microsoft UrlScan 3.1

    #Version: 1.0

    #Date: 2018-11-15 06:44:35

    #Remark: AllowDotInPath is enabled.  Checksbased on extensions will be unreliable.

    #Fields: Date Time c-ip s-siteid cs-method cs-uri x-action x-reason x-context cs-data x-control

    2018-11-15 07:00:53 10.22.15.133 2 PUT /api2/cloudnetworkmonitor/servicemonitors/0 Rejected verb+not+allowed HTTP+method - -

    2018-11-15 07:04:45 10.22.15.133 2 PUT /api2/cloudnetworkmonitor/servicemonitors/0 Rejected verb+not+allowed HTTP+method - -

    The URLScan.ini file was edited to allow the PUT requests

    [AllowVerbs]

    ;

    ; The verbs (aka HTTP methods) listed here are those commonly

    ; processed by a typical IIS server.

    ;

    ; Note that these entries are effective if "UseAllowVerbs=1"

    ; is set in the [Options] section above.

    ;

    GET

    HEAD

    POST

    PUT

    The issue has been resolved.

    abdhijasharmanikhil.ncsameercobriengangadhar.k