07-15-2014 11:25 AM - edited 03-01-2019 11:44 AM
Hi all,
I just spun up a UCS central cluster (primary node), and I am noticing that the vm appliance IP is pingable, but the virtual IP is not (verified we put in the correct one).
This is the first boot up, and I know there's a post-install config that occurs, but not sure how long it's supposed to take (currently ~20 min mark). If I try to execute anything show related, I just get a "not yet the leader - try again in a few minutes."
Thoughts?
Thanks,
Ryan
07-24-2014 07:02 AM
I get this as well.
07-28-2015 07:05 PM
Are you using a dv switch? We just had issue with another product using VRRP to provide the failover services for two VMs. The fix was to change the port group security settings so that MAC address changes and forged transmits were allowed (this is allowed by default on a standard vswitch but blocked by default on a dvswitch).
07-29-2015 03:12 AM
Our instance has been working fine on a dvswitch for months and nothing changed so i doubt that would be it but i'll check it out.
07-28-2015 12:53 PM
was this ever answered? I am also running into this issue, trying to open a tac case, hopefully they can help.
08-04-2015 10:10 AM
Finally resolved my issue..
deployed 2 new VMs and restored a configuration backup.
TAC stated that this is a known issue where if one node isn't shut down properly the RDM requires a FSCK and there is no way to get root permissions without using a recovery disk (boot centos/redhat).. so the shared stored is offline and can't be used which leaves both nodes thinking they are the secondary.
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