VSOM Identity Collision

[coolsapper71]

I have 5 UCS Chassis that host all my cameras and my VSOM server.  During our initial deployment using VSOM 7.2 we had a IP issue.  I corrected our IP scheme and made the changes to the other machines.  But a error persists in our system.  It does not cause any issues, just a nuisance.  It says I have a Identity Collision.  But I have checked all the UCS chassis and on the backend in the Linux settings.  Can someone help me figure out the error and how to clear it.  I have attached pictures for reference.

[Scott Olsen]

You need to terminate the SQL statement with a semi-colon ";".

Cheers :-)

[coolsapper71]

Please see attached :

[root@localhost bin]# sudo /usr/BWhttpd/vsom_be/db/mysql/bin/mysql --defaults-fi                le=/usr/BWhttpd/vsom_be/db/db.cnf vsom
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 55
Server version: 5.6.18-enterprise-commercial-advanced-log MySQL Enterprise Serve                r - Advanced Edition (Commercial)

Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> select * select issue;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that                 corresponds to your MySQL server version for the right syntax to use near 'selec                t issue' at line 1
mysql>

[Scott Olsen]

Again, your syntax is incorrect and you haven't used the SQL command that Nadeem provided.  Please double check.

Also, I would *highly* recommend you open a case with TAC for this obvious software bug.

[coolsapper71]

I got the output, I am trying to locate the object

[coolsapper71]

Nadeem,

I have attached the output and I do not see the object that is causing the error.

[Kevin Monteiro]

Looks like a common issue. There may be stale entries in the VSOM DB regarding the ip-add change  after you upgraded to  vsm 7.5.0. 

The below steps mentioned by Nadeem should help you out, after you are done with it do a "Reset status" on VSOM page.

Make sure you carry out the steps on the VSOM cli, run the command "service Cisco status" to check vsom db running it shld be the first line when you run the command.

-Kevin