I upgraded from LMS 3.1 to 3.2 yesterday. The upgrade went well, but DFM and Campus Manager didn't work afterwards.
After a few searches on the forum, and the help of a great Cisco TAC engineer, we were able to solve the PIDM database inconsistencies that were preventing DFM links from showing up. And Campus Manager needed a kick in the butt to start again it seems.
My PIDM table had many duplicate device ids, some registered to DFM 2.0 (on the previous server) and some registered to DFM 3.1 (current server). So it seems the previous upgrade (from 2.6 to 3.0 and then 3.1) had some bad entries.
My question for the pros is this : is there a tool that can be run against the LMS databases to check for inconsistencies like these ? Duplicate entries, wrong server names, application version, and other nasty stuff ?
My next chore is to move LMS from Windows 2003 to Windows 2008, but before I do that, I'd like to make sure the DB is clean
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...