I have a remote site set up to handle the network scanning. I did this to take the load off of the primary server after some performance issues. It was working fine until a power outage took down the remote site. When the remote site came back up it wasn’t connected to the primary. I’ve fixed that and the remote now shows connected. Now the primary server seems to be doing all the scanning despite the remote site being connected. I’m not sure how to fix that.
2 Spice ups
jaimedelapaz
(Jaime D (Spiceworks))
2
Hi,
Do you have any scan settings entered in the Central site? Any IP ranges?
Yes, the scan ranges are set up. The problem is that the primary server is doing the scanning instead of the remote site.
jaimedelapaz
(Jaime D (Spiceworks))
4
The IP ranges should only be on the site that is scanning them. If they are on the central site, then the central site will scan them. Make sure that they are removed from the central site if you do not want them scanned by the central site.
I’m confused, then. When I look at the Device Scanning on the remote site I’m told “Need to adjust scan schedules for this site? You manage all of your schedules from the Central Server”
So, I set up all of the scan groups and times on the primary server as I was told.
jaimedelapaz
(Jaime D (Spiceworks))
6
Those scans are set up correctly. I was referring to the IP range scans at the top of that page. Do you have anything entered in the Your Network portion of the scan page on the Central Site?
I have several that were in there from before I created the remote site. They are all disabled now. The snip shows just the first couple
jaimedelapaz
(Jaime D (Spiceworks))
8
Thanks. Are the scans still running on the central site itself?
Yes. It shows as linked to the remote site, but the remote site shows essentially no network traffic and the primary shows consistent network traffic.
jaimedelapaz
(Jaime D (Spiceworks))
10
If you delete one of the devices that is on the remote site, does it get scanned back in?
I’m not sure how you mean that. All of the scanned items are stored on the primary site.
jaimedelapaz
(Jaime D (Spiceworks))
12
Go ahead and delete a device from the central site. It should get scanned in by the remote site and created again, if everything is working properly.
I think we’re speaking across purposes here. I’m sorry if i’m sounding frustrated, but it doesn’t seem that it should be this difficult.
The remote site is currently showing zero network traffic. The primary site is showing all of the network traffic. Further, devices added to the network recently are NOT being discovered.
At this point I’m considering scrapping the entire inventory scan settings and starting over from scratch to see if that will make them work. If I can’t get this working, then I need to report to management that our inventory system is non-functional and we need to consider a different solution.
jaimedelapaz
(Jaime D (Spiceworks))
14
I’m trying to narrow down where the problem could be. What steps did you take to get the remote site connected to the central site after the power outage?
I appreciate that you’re trying to help and I’m sorry for my frustration.
Once I realized that the outage had taken down the remote site, I brought it back up then remote in. Once I had SpiceWorks running again, I went tin to Settings > Inventory > Device Scanning. I noticed at the top of the page that the remote site was not showing as connected to the primary. I went through the steps it asked for to reconnect the site. Namely, providing the Site Name, Central Server name, and Central port. Site callback is left blank. Synchronize ticket events from this site is unchecked.
jaimedelapaz
(Jaime D (Spiceworks))
16
Was the site name exactly the same as it was before the outage? Same spelling, punctuation, etc.
Now that’s an interesting question. The site has the same name as it had before the outage. However, the remote machine was replaced a few days before the outage. New machine with a new name. Is it possible the remote site wasn’t working properly before the power outage and I just hadn’t noticed it?
jaimedelapaz
(Jaime D (Spiceworks))
18
That’s possible. Theoretically, if the site name stays the same, then everything should work. Do we have any idea whether it was working properly before the outage? What is the status show on the central site >> remote sites settings page?
If you disconnect the remote site, reboot, and connect it again, do you get any error messages?
On the central site, the remote site is enabled. The site name matches the new (current) remote site. It shows last contact 3 hours ago and 62 devices with no helpdesk. Which is correct.
jaimedelapaz
(Jaime D (Spiceworks))
20
If you go to one of the devices on the Central site, does it show it belongs to the Remote site? What is the Last Scan time and Last Update time?
