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."
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).
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.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...