Friday, October 20, 2017

vSAN error when no vSAN is installed

We began receiving the "Retrieve a ticket to register the Virtual SAN VASA Provider" but don't have vSAN installed.  What's going on?  I found this article and could simply disable the vSAN Health Service.

To stop and disable the vSAN Health Service on vCenter Server for Windows

  1. Open the Services MSC
  2. Locate and "VMware Virtual SAN Health Service" service and click Stop.

  3. Double-click the VMware Virtual SAN Health Service to open its dialogue box.
  4. On the General tab, change the Startup type to Disabled and click OK

To stop and disable the vSAN Health Service on the vCenter Server Appliance

  1. Log in to the vCenter Server Appliance via SSH and activate a Bash shell. For more information on logging in to the vCenter Server appliance, see the Using the Appliance Shell to Configure the vCenter Server Appliance section in the vCenter Server Appliance Configuration guide.

  2. Stop the vSAN Health Service:
    # service vmware-vsan-health stop
    Stopping Virtual SAN Health Service:

  3. Disable the vSAN Health Service:
    # chkconfig vmware-vsan-health off

Proper Dismount of DataStore and LUN in VMWare

Some references for a proper dismount of a LUN in VMWare. 

More details to come when I have to do this again, I'll take some screen shots then.

Cisco WLC with Pico Station as a Bridge to wired client

I have a network attached sensor module that I needed to install in a location where I can't easily get a network cable run to.  So a quick easy attempt was to try a wireless link.  The setup is the sensor module attached to a Ubiquiti Pico Statoin, connected to a 2600 series wireless AP managed by a Cisco 2504.

I configured the Pico and it connected without problem to the wireless network.  I set the management interface of the Pico to pull from DHCP and it received an address without issue.  However the device connected behind it would not pull an address.  I then plugged the sensor module directly into the network to test, and it would pull an address just fine.  So I knew it had to be a configuration setting in the WLC.

In short, Configure Multicast and enable it on the controller.  Then under the Advanced tab of the SSID profile, don't require all client to have a DHCP address and enable Passive clients. 

Here are a couple of write ups to help with some more details.

Cisco Wireless APs fail to associate to the controller.

We had an issue with a 1200 series lightweight AP not associating with a 2100 series wireless controller.  During investigation and I found a certificate error associated to the LWAP join request.  Because I had the flexibility to do so, I thought "let's reboot the controller and see what happens".  After reboot none of the APs were associating and all were having the same error.  Not a good result.

I discovered this article

In addition, without an upgrade and certificate check disable, a quick fix to get the APs associated is to change the date.  Simply disable NTP on the WLC and set the date back a few years.  The APs associated right up and everything started working.