10-06-2014 01:09 PM
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.
10-07-2014 05:43 AM
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?
07-10-2015 05:56 AM
07-13-2015 07:12 AM
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.
Cheers,
Jayesh
07-14-2015 08:49 AM
I have tried chanaging the the local host through the GUI and it gives me a error that it cannot do that? Any ideas?
07-14-2015 10:04 AM
Is it possible you to open a TAC case?
Br,
Nadeem
07-14-2015 11:02 AM
What is the error you are getting now? Can you share that snapshot please.
10-07-2014 06:49 AM
Hello
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.
Br,
Nadeem
07-09-2015 11:58 AM
Nadeem,
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?
Thanks
Tim
07-09-2015 12:05 PM
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
VSOM: root/secur4u
SSH: root/secur4u
if its VSM 7.x , default username password
VSMC: localadmin/secur4u
VSOM:admin/admin
SSH: localadmin/secur4u
Br,
Nadeem
07-09-2015 01:06 PM
07-10-2015 05:47 AM
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
[localadmin@VSM76COLO-1 ~]$sudo su -
[root@VSM76COLO-1 ~]#whoami
root
[root@VSM76COLO-1 ~]# pwd
/root
[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
[root@VSM76COLO-1 bin]#filemysql
mysql: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
[root@VSM76COLO-1 bin]#
07-09-2015 01:26 PM
07-09-2015 01:52 PM
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
Regards
Nadeem
07-10-2015 05:47 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide