NetPath probes gone after server migration and upgrade

We upgraded to 2024.2.1 and migrated our primary polling engine to a new server. After verifying the functionality of the migration, we've found that all the netpath probes we had created seem to be gone. They are in the database, but I can't find a link in any of the tables to the engines table. Is there a way to get these back without recreating all of them?

Find more posts tagged with

netpath errors

netpath probes

NetPath

Accepted answers

All comments

taylor.crowley

A few Questions spring to mind:

During the migration, did you change the Hostname of the server?
When you look in the Engines table, are there any old or stale entries?
And lastly, in the NetPath_Probes table, are the probes assigned to an EngineID that no longer exists?
- i.e., does Probe A have a number in the EngineID column that belongs to an engine that is stale, duplicated, or doesn't exist in the Engines table?

mharvey

I was looking at that. Yes the hostname of the server changed, however there is only one entry in the engines table and it's the server we migrated to. The Netpath.Probes table only has the new engine in it. What I found most interesting/disturbing is that while the NetPath_EnpointServices has all the previous endpoints, the NetPath_EndpointServiceAssignments has nothing in it. As I recreated one of the paths we were monitoring it duplicated in the NetPath_EnpointServices table and added an entry to the NetPath_EndpointServiceAssignments. I'm hoping there's an easier way to redirect rather than having to recreate them all.

adam.beedell

I'd expect you'd be able to just assign a new copy in that case, not the case?

mharvey

I can create it again, just a bit frustrating having to recreate them all when they are in the database already but there's no way to point what's already there that I can find.