LMS 2.6, DFM 2.0.10
Any ideas as to why the DFM discovery process would stick at 90% for all devices not in the unknown or questioned categories?
Services are all running normally and I've reinitialized the databases but still no luck.
I can post the Release Notes from the bug, but direct database access is something that should only be done with TAC's assistance:
Group administration UI shows a different set of root group names for the various application hierarchies. For example, when you launch Common Services -> Groups -> Group admin, you will see CS@ for the CS group hierarchy, and RME@ for the RME group hierarchy. Because of this mismatch, DFM discovery of devices is stuck at 90%.
This happens when the hostname of the CiscoWorks server is changed from lowercase to uppercase or the vice versa, followed by a daemon manager restart.
Note: This issue will not appear if the hostname is changed to a different string.
1. Stop Daemon manager.
2. Delete the OGS tables from the all the databases. CS, DFM, Campus OGS tables are present in CmfDb and RMEOGStables will be present in RmeDb. Note: The user defined groups will be lost by deleting the tables.
The following are the commands:
drop table csogsgrouppropertiestable;
drop table csogsgroupcachetable;
drop table csogstagtable;
drop table csusergroupassociationtable;
delete from dbversion where component='cs';
drop table dfmogsgrouppropertiestable;
drop table dfmogsgroupcachetable;
drop table dfmogstagtable;
drop table dfmusergroupassociationtable; delete from dbversion where component='dfm';
drop table campusogsgrouppropertiestable; drop table campusogsgroupcachetable; drop table campusogstagtable; drop table campususergroupassociationtable; delete from dbversion where component='campus';
drop table rmeogsgrouppropertiestable;
drop table rmeogsgroupcachetable;
drop table rmeogstagtable;
drop table rmeusergroupassociationtable; delete from dbversion where component='RME';
3. After this, open NMSROOT/etc/ogs/applications.reg in notepad and empty the contents (remove all the lines) and save the file.
4. Start Daemon manager.