Error: Issues information is not available at this time. (vCenter Appliance)

The above was a wonderfully descriptive error I would receive in the web client.  This started appearing after I removed individual nodes from a cluster and readded them back to inventory.  (was trying to clear some bunk HA errors)

Long story short, I had to open the C# client to find out what 'warning/error' it was complaining about.  Quite simply, I had forgotten to re-add the hosts back into the vDS and migrate the vMotion/vSAN vmk connections.

Man-o-man, I see why so many people complain about the web client.

The upside to the story was I found out a couple of things about vSAN.

  1. Having a 3-node cluster minimum, I was able to remove and re-add each host back into the cluster with no issues to VM's running on each host.
  2. Even w/ the vDS problem, vSAN kept chugging along w/ VM's running just fine.
  3. In other words, even without vCenter managing things, the ESXi hosts kept everything running just fine.
  4. This was on my mac mini vSAN cluster.

Comments

Bennett said…
I don't remember exactly what the error was, but I had a very similar nondescript issue while building my cluster the first time. Net was - I blew it away and rebuilt it.

I didn't get as far as clustering the 3 machines, so I am wondering if it had something to do with what you found.

I agree - web client is sometimes pretty bad. I use it more than I should since I'm trying to leverage more cli and scripting.

Interesting.
December 30, 2014 at 12:08 PM
Anonymous said…
I had the same problem. I had to re-add the host to a vDS. In the host virtual switches list, there was a vds showing no uplinks... very strange because I use such vds to management traffic. So it appears to be a gui problem. If the vds had no uplinks, how I was acessing the host? Host wasnt in the vds related objects, but the host had such vds. So I re-added the host to the vds.
September 16, 2016 at 3:07 PM
pkiran78 said…
I am getting same issue and my management traffic is going through vSwitch.
I have VDS configured but I am using it for VSAN and vMotion traffic.
Can you please help in such scenario.
April 21, 2018 at 5:34 AM
pkiran78 said…
I am getting same issue but my management traffic is via vSwitch.
I am using VDS for VSAN and vMotion traffic.
I am using vCenter 6.5
Can you please help in such scenario.
April 21, 2018 at 5:36 AM
Post a Comment

Popular posts from this blog

RacADM, Powershell, and Kerberos KeyTabs

Summary: I was looking to automate configuration of iDRAC's (Dell Remote Admin Console) synonymous w/ iLOM and many other acronyms.  I also wanted to enable domain authentication in a somewhat secure manner.  By using a kerberos keytag, I'm able to in the very least obfuscate the username and password into a file for upload into the iDRAC.  What follows is a journey into a ridiculous realm. PreReqs: RACADM ktpass Powershell 3.0 (2.0 probably works too, but I was using 3.0 @ the time) Your root CA's cert This is so it AD Authentication can be setup Solution: It's not a complete solution, but hopefully it'll help you get started in your own endeavors.  Below assumes the iDRAC has been configured and is available on the network in default config. To generate a kerbero's keytab , you simply need the name and password of a service account (this is simply a Active Directory user account) in your domain. ktpass /pass ReallySecurePas5word /ptype K
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnect. Using
Read more

PowerCLI: The SSL connection could not be established, see inner exception.

Image
Summary: Unable to connect to ESXi/vCenter server with Connect-VIserver cmdlet, get the following error: "The SSL connection could not be established, see inner exception." Be sure to "Set-PowerCLIConfiguration -InvalidCertificateAction:Ignore" if you plan to connect to an ESXi/vCenter that does not have trusted certificate.  Interestingly, something must've changed recently because the PowerCLI module actually would output a more descriptive message about setting your PowerCLIConfiguration. This appears to be the case w/ Powershell Core 6.1.  I'm actually unsure when this behavior started happening and whether is module or powershell related.  Regardless, figured I'd post this since I was initially confused myself when running some things on another system.
Read more