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

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

Get iDRAC/ILO (aka Baseboard Management Controller) IP via PowerCLI

[Update: 1 report states issues w/ HP Gen9 systems.  Newer Dell, and older HP systems don't seem to have issues.  If you have a HP Gen9 system, feel free to contact me via google hangouts and/or twitter to start an interactive session and we can work through figuring out a workaround.]

Summary:
Needed a way to figure out what IP my HP iLO's / Dell iDrac's were configured with.  Ended up using an oldie, but a goodie script put together by Carter Shanklin.

PreReqs:

Powershell 2+PowerCLI 4+Must have Port 443 (https) access to your ESXi hosts.If firewalls are an issue you may have the option of running this from your vCenter if it's still running on Windows.  If it's the vApp, you'll need to open access to port 443.Download Carter's scriptShort and Sweet: $info = Get-VMHostWSManInstance -VMHost (Get-VMHost myESXiServer) -ignoreCertFailures -class OMC_IPMIIPProtocolEndpoint $info # You can remove the -ignoreCertFailures flags if your systems have trusted certs. # Th…
Read more

Misc: Fire TV Stick 2 Screen Cut Off, no display adjustment option

Summary:
Long story short, Fire TV Stick (2nd Generation) doesn't allow you to calibrate the screen, software wise, forcing you to use your TV settings (if available) to fit the screens content within it's borders.  Super annoying for some apps, but you can fix this dumb issue as I was able to.

If your TV allows you to adjust its settings, then you'd be fine as well, but the Vizio I have, has no such setting.

Solution:
Get the Amazon Fire TV instead.  It's only slightly more expensive, but doesn't suffer the problems the Fire Stick does.



Workaround:
First you have to enable ADB debugging (step 1 here) on your fire stick.Next you'll need the ADB provided w/ Android Studio, or you can install w/ brew on the Mac.I prefer brew cause it's easier, keep following steps described by Amazon page if you are using Windows.Open Terminalbrew cask install android-platform-toolsNext find the IP address of your FirestickSettings --> Device --> About --> NetworkSteps a…
Read more