We recently had to move our Spiceworks instance to a new server. After the move, we have not seen toner reporting actually work at all. All of our printers in question are HP's that reported fine before the move, and afterward we do not receive toner alerts, and in the inventory information page we do not even see a toner level report at all.

We have SNMP scans configured, and they do indeed work, as I have removed an item in question from the listing, let the scan complete, and it adds the device back in to the listing, but still no alert nor toner report.

Well, I did these steps, let the network scan run, no dice. It still doesn't see any toner levels for any printer. The model is an HP LJ4200, but this is affecting all printers on site. It just seems odd that we had no issues prior to the move of the data.

I have tried multiple times to create the SNMPWalk log, and each time it flat out will not write a log. All I am getting is a string of outputs stating that certain modules are not being found. Is this a problem or is this normal? It looks like what they have in the example screenshots, but I never actually get an output to file at all.

I have moved our entire spiceworks install/database to a freshly commissioned server. I am still unable to run SNMPWalk, it never generates a log, at all. The destination is writable, and everything else is in place, but it simply does not generate the test's log file.

Any ideas would be extremely helpful, as I am beginning to believe we are having an issue with Spiceworks itself, and not configuration.

I got it to output to file by modifying the batch script included in the zip file. The destination needed to be changed to a non-profile location for what ever reason. Regardless, now I have sent logs of two devices from our network. Let me know what else I can do.

I already got it, I just directed the script to create it on a non-userpath location. I think it has something with how our LDAP setup creates profiles inside Windows. If I had been smarter, I would have used my Mac ;)

Question: Is there some sort of extension that I need to make sure is installed and enabled for this function to work? It just seems odd that we dont even have a section for the ink/toner to be listed in at all.

OK guys, heres what I have done. I installed a new instance of SpiceWorks on a spare workstation and imported none of our data. I let it do a network scan, and it found the devices just fine, in addition to the toner levels and other information we were missing. We were going to just wipe out our database and import tickets only, but I started having major doubts (we would lose all of our settings pertaining to users, emails, etc and its just not acceptable to have to re-do all of this work.).

I could really use some help in figuring out how to completely wipe out our device inventory and start with a new fresh scan.

AK has asked me to chime in here so I'd like to go ahead and do so. What is the difference in the scan ranges that you have set up for the new install vs. your previous install? Is there a different SNMP string you are using, or are the scan ranges set up differently?

Basically, we want to troubleshoot the differences between the two installs to see if we can find what is causing the issue in the original. From there we can decide the best route. Thanks!

Cole, I haven't had a chance to update this since I last posted, but I want to let you guys know that community strings do not follow a database restore. When I looked at the scan parameters again, I noticed that SNMP was set to "None", as opposed to having our organization's string embedded. After resetting this option and rerunning our scans, all our alerts came back normally! Is this a known issue?

Thanks for the heads up. I'm glad to hear things are working for you now and I've passed the information regarding to the SNMP strings not migrating over onto the devs. Is there anything else we can help you with? :)

Regards,

Cole

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.