Loading...
Loading...
When a user registers a device and decides to change the device name and re-use the original name for another device, the second device registration will fail with the error reporting duplicate name used: "Duplicate Device name or uuid was detected"
When a user registers a device and decides to change the devices name and re-use the original name for another device, second device registration will fail with the error reporting duplicate name used. This is caused by an issue with changing not only sensor table, but also EM_peers table, and device configuration file (sftunnel.json) to use the new name as specified in sensor table.
For work around the user would need root access to FMC console (ssh). Work around would have the following steps (ndb database) 1. Find out the device UUID by name from sensor table > select uid from sensor where name="ftd2"; - get $uuid. 2. Update the name in EM_peers table too. > update EM_peers set name="ftd2" where uuid ="$uuid"; 3. vi /var/sf/peers/$uuid/sftunnel.json and set the value like: "name": "ftd2", 4. Restart sftunnel : pmtool restartbyid sftunnel. After that the registration with original name : ftd1 should work.
the issue is fixed in 7.2.4 and upgrading to 7.2.4 before starting renaming devices would be preferred.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.