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.
Sooo... The IP Addressing scheme changed for all of your servers? How were the IP addresses of the servers actually changed?
What version were you at when you changed them?
It seems like you have not configured the host-name properly for this server, its showing there as "localhost. localhost". Its validation failed there only which cause this error. Please correct the proper host-name then try.
I hope that clears this error then.
Try deleting the event id from VSOM database and reset the status it will fix the issue.
Procedure to do so:
login as root on VSOM server
#sudo /usr/BWhttpd/vsom_be/db/mysql/bin/mysql --defaults-file=/usr/BWhttpd/vsom_be/db/db.cnf vsom
This command will get you to the SQL prompt
SQL> Select * from issue;
Once you run this command you will get a output of all event that are there on VSOM . copy and past e in any notepad . Grep the object id of of that error/alarm/event you are getting Collision identity.
SQL>DELETE from issue WHERE OBJECTID = '<objectid>';
or if you find any difficulties finding the object id post me the "Select * from issue; command output to me.
I never got alerted you replied to my post.
Do you happen to have the default root password that ships with them? No one seems to remember the password?
Where are you trying to login and what is the VSM version
if it VSM 6.x default user name and password
VSMC : root/secur4u
if its VSM 7.x , default username password
I think I see you're issue... you don't have the full path to the mysql binary. Double check Nadeem's post above ;-)
This is from one of my own servers:
[localadmin@VSM76COLO-1 ~]$ whoami
[localadmin@VSM76COLO-1 ~]$sudo su -
[root@VSM76COLO-1 ~]# pwd
[root@VSM76COLO-1 ~]# cd /usr/BWhttpd/vsom_be/db/mysql/bin/
[root@VSM76COLO-1 bin]# filemy
my_print_defaults mysql_convert_table_format mysql_find_rows mysql_upgrade
mysql mysqld mysql_fix_extensions mysql_waitpid
mysqladmin mysqld_multi mysqlhotcopy mysql_zap
mysqlbinlog mysqld_safe mysql_install_db
mysqlbug mysqldump mysql_secure_installation
mysqlcheck mysqldumpslow mysql_tzinfo_to_sql
mysql: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
Ok I think I am another step forward. Now I am getting prompted for the root password and it is not our localadmin password. I am assuming it got changed during the install last year. I have tried secur4u and the localadmin password we have set for the box.
SSH to server first
$ sudo su -
# sudo /usr/BWhttpd/vsom_be/db/mysql/bin/mysql --defaults-file=/usr/BWhttpd/vsom_be/db/db.cnf vsom
You need to terminate the SQL statement with a semi-colon ";".
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
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
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.
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.