I came across a post in this forum that suggested there is an upgrade path from 1.13 to 1.14. Is this a valid option and reccomended? I noticed in my upgrade directory the option to upgrade from 1.13 to 1.14 is not present, while scripts for other upgrades such as 1.12 to 1.13 are present.
Should I consider upgrading from 1.13 to 1.14, and if so, how do I obtain the script and instructions to do so?
Thank you,
Matthew
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So.... What I found is the requirement to update the following, as they are the only updates avaiable for 1.14:
NetDB.pm in /opt/netdb/
upgrade-v1.13-to-v1.14.sql in /opt/netdb/sql (this is a MySQL script run in the mySQL shell)
*
Both files are located here in the Help forum. My milaeage with the updates varied, not so sure if they were worth the effort as some fields in "netdb -st" are now missing:
netdbadmin@netdb:/opt/netdb/sql$ netdb -st
NetDB Statistics
---------------------------------
MAC Entries: 12759
ARP Entries: 11001
Switch Entries: 27718
WiFi Entries: 0
Status Entries: 59601
Registrations: 0
DB Transactions: 12
Total Rows in DB: 111091
Last edit: Matthew Earley 2018-04-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Where were you able to locate version 1.14 of NetDB.pm?
I've downloaded the newest version of NetworkDB via SVN and it still had version 1.13. I'm trying to upgrade my server from Ubuntu 14 to 16 but since the upgrade I'm running into the errors below which I'm guessing are resolved in version 1.14.
Importing 9123 intstatus entries in to switchstatus table
Importing 8403 MAC entries in to switchports table
DBD::mysql::st execute failed: Data too long for column 'vendor' at row 1 at /usr/local/lib/site_perl/NetDB.pm line 2495.
DBD::mysql::st execute failed: Cannot add or update a child row: a foreign key constraint fails (`netdb`.`switchports`, CONSTRAINT `switchports_ibfk_1` FOREIGN KEY (`mac`) REFERENCES `mac` (`mac`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/local/lib/site_perl/NetDB.pm line 2524.
Importing 247 neighbor discovery entries in to neighbor table
Importing 6869 ARP Entries in to ipmac table
DBD::mysql::st execute failed: Data too long for column 'vendor' at row 1 at /usr/local/lib/site_perl/NetDB.pm line 2692.
DBD::mysql::st execute failed: Cannot add or update a child row: a foreign key constraint fails (`netdb`.`ipmac`, CONSTRAINT `ipmac_ibfk_2` FOREIGN KEY (`mac`) REFERENCES `mac` (`mac`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/local/lib/site_perl/NetDB.pm line 2783.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was able to locate the files, but ended up using the orginal 1.13. 1.14 and the work-around did not do well for me. I went back to a clean install with 1.13 and updated the ieee oui.txt file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Jonathan,
I came across a post in this forum that suggested there is an upgrade path from 1.13 to 1.14. Is this a valid option and reccomended? I noticed in my upgrade directory the option to upgrade from 1.13 to 1.14 is not present, while scripts for other upgrades such as 1.12 to 1.13 are present.
Should I consider upgrading from 1.13 to 1.14, and if so, how do I obtain the script and instructions to do so?
Thank you,
Matthew
So.... What I found is the requirement to update the following, as they are the only updates avaiable for 1.14:
*
Both files are located here in the Help forum. My milaeage with the updates varied, not so sure if they were worth the effort as some fields in "netdb -st" are now missing:
Last edit: Matthew Earley 2018-04-09
Where were you able to locate version 1.14 of NetDB.pm?
I've downloaded the newest version of NetworkDB via SVN and it still had version 1.13. I'm trying to upgrade my server from Ubuntu 14 to 16 but since the upgrade I'm running into the errors below which I'm guessing are resolved in version 1.14.
I was able to locate the files, but ended up using the orginal 1.13. 1.14 and the work-around did not do well for me. I went back to a clean install with 1.13 and updated the ieee oui.txt file.