Hello , Recently we moved to a new nav server. We started to seed the database with a switch we had in the former version nav server. After seeding most of our switches to database we discover that there is an issue and most of switch under *Collected info* section , doesn't have the Type filled , result all switch doesn't have post/interface inventory although snmp check is successful any idea what is wrong? Please advise Thanks [image: 2020-08-09_12-27-04.png]
On Sun, 9 Aug 2020 12:29:31 +0300 Tal Bar-Or tbaror@gmail.com wrote:
Recently we moved to a new nav server. We started to seed the database with a switch we had in the former version nav server. After seeding most of our switches to database we discover that there is an issue and most of switch under Collected info section , doesn't have the Type filled , result all switch doesn't have post/interface inventory although snmp check is successful any idea what is wrong?
How did you seed the new database? One by one, or by bulk import?
Type definitions must be also be migrated from one NAV installation to the next for SeedDB to discover the types of newly added SNMP devices (i.e. these need to be imported *before* the devices are).
If the device types are missing from your database when a device is seeded, ipdevpoll will automatically create new device types with auto-filled information for each new SNMP sysObjectID it encounters.
Inventory information is not part of the seed process. This must be collected anew by ipdevpoll if you only migrate via seed data rather than a full database migration.
If none of this resolves itself after a few minutes, I would suspect your backend processes aren't running. Output of `nav status`?
-- sincerely, Morten Brekkevold Uninett
-
Morten Brekkevold -
Tal Bar-Or