Tim,
Yeah, that could happen if you delete the zone.
You can safely empty the nad_* tables and nothing else will be impacted.
Javier
Tim Carr wrote:
Hello…
I’m running into a problem whereby network autodiscovery isn’t working,
after I went through this process:
- I have a system and running watching several subnets
- I added another zone with a specific subnet (10.100.14.0/24)
- JFF discovered it correctly
- I realized that I didn’t have the SNMP string in there
correctly, so I deleted the 10.00.14.0/24 zone
- I re-added the zone, with the correct SNMP string
- Network autodiscovery runs, but it will not come up with that
zone in the “Discovered Networks” area
I’ve checked the logs, and the discovery process is running, and it
finds all IP’s out there, but it comes up with this line for each IP:
10:31:43 N 9 : Scanning Host 10.100.14.148 Already Added
So things are running correctly, but it won’t re-populate the database
with that subnet. I looked in the NAD_IPS table in the database, and
all the IP’s are in there for the 10.100.14.0 network.
I don’t want to blow the whole JFF installation away as I’m already
watching other subnets and have a good amount of configuration time
invested in this particular instance.
Any thoughts?
Thanks,
Tim Carr
Buchanan Associates
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Javier Szyszlican, Project Leader, JFFNMS
[EMAIL PROTECTED]
I hope JFFNMS or I were helpful to you, if you
can, please donate at http://jffnms.org/donate
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
jffnms-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jffnms-users
