vSphere Deprecation Announcements

3 #vSphere Deprecation Announcements: #vCenter for Win, Flash #WebClient and #vmkLinux APIs

vSphere Deprecation Announcements

VMware recently announced plans to deprecate several of its vSphere products: vCenter Server for Windows, Flash-Based vSphere Web Client, and vmkLinux APIs. The content and links below provide an overview of the deprecation, migration plan, and helpful resources. vCenter Server for Windows VMware plans to deprecate vCenter Server for Windows with the next numbered release (not […] The post vSphere Deprecation Announcements appeared first on VMware Tech Alliances (TAP) Blog .


VMware Social Media Advocacy

Advertisements

Know Before You Go @ VMworld Europe 2017

Know Before You Go @ #VMworld Europe 2017

Know Before You Go @ VMworld Europe 2017

This is a repost from the VMworld blog. We look forward to welcoming you to VMworld 2017 Europe, taking place the 11th-14th of September in Barcelona, Spain! Get ready to share four days of innovation with the industry’s top thought leaders, subject-matter experts, and IT professionals. To make the most of your onsite The post Know Before You Go @ VMworld Europe 2017 appeared first on VMware Cloud Provider Blog .


VMware Social Media Advocacy

Troubleshooting Cisco UCS Chassis: F0411 Thermal condition on chassis is upper-non-recoverable

Today I experienced an issue with a Cisco UCS chassis. The error in question was “F0411 Thermal condition on chassis is upper-non-recoverable”.

F0411 Thermal condition would make the chassis go red within equipment under the Cisco Unified Computing System Manager, then from there it would go yellow, with the fans stating they were “inoperable” even though they weren’t.  This process continually went back and fourth between yellow and red thousands of times. While the alert was concerning to see, it’s important to note the UCS Chassis itself was functioning normally with no issues.  Concerning to the eye at the very least, and worth investigating. Upon inspection of the device, everything was working normally; however, the fans were running full blast. To resolve the issue I opened a ticket with Cisco TAC. First thing first, I had to upload logs from the chassis. In order to get chassis logs, see the below image from Cisco’s website.
chassis

  1. Login to Cisco UCS Manager
  2. Go to admin tab in the upper left hand corner, then select ALL
  3. Select Create and Download Tech Support File
  4. Select the path to place the downloaded files
  5. Under options, select chassis
  6. Ensure the appropriate chassis ID is selected
  7. Click OK and wait for the file to generate

Posted by Stephen Owens (@thevirtualboi) at http://bit.ly/2xOkhPh


VMware Social Media Advocacy

vExperts, Thank You for a Great VMworld U.S.

vExperts, Thank You for a Great VMworld U.S.

vExperts, Thank You for a Great VMworld U.S.

Thank you to the vExpert community for coming out to join us for our annual vExpert Party at VMworld U.S. Each year we host the vExperts at a private event to provide a night of fun and entertainment. For this party we had food trucks, dessert truck, drinks, quarters, food & fire entertainment as well […] The post vExperts, Thank You for a Great VMworld U.S. appeared first on VMTN Blog .


VMware Social Media Advocacy

VMware Cloud on AWS Technical Overview

The post VMware Cloud on AWS Technical Overview appeared first on frankdenneman.nl .

Yesterday we launched the VMware Cloud on AWS service. VMware Cloud on AWS allows you to run your applications across private, public, and hybrid cloud environments based on VMware vSphere, with optimized access to AWS services. The Cloud SDDC consists of vSphere, NSX and vSAN technology to provide you a familiar environment which can be managed an operated with your current tool and skill set. By leveraging bare-metal AWS infrastructure the Cloud SDDC can scale in an unprecedented way.

VMware Cloud on AWS is a service and that means that we will not using product versions when we refer to the service. Instead we will be calling the first release the initial availability of the service. Any release after is referred to as future release. VMware Cloud on AWS is operated by VMware. In short that means that VMware is responsible for providing infrastructure resources, the customer is responsible for consuming the resources. This article explores the resource capacity of the Cloud SDDC at initial availability.

Compute in VMware Cloud on AWS
At initial availability, the VMware Cloud on AWS base cluster configuration contains four hosts. Each host is configured with 512GB of memory and contains dual CPUs. These CPUs are custom-built Intel Xeon Processor E5-2686 v4 CPU. Each CPU contains 18 cores running at 2.3GHz, resulting in a physical cluster core count of 144. Hyper-threading is enabled, allowing the VMs to consume 288 logical processors in the default Cloud SDDC configuration. Please note, that VMware Cloud on AWS uses a single, fixed host configuration; the option to add components to the host configuration is not offered at this time. However, the scale-out model enables expansion to up to 16 hosts, resulting in 576 CPU cores and 8TB of memory.

vSphere DRS and vSphere HA are enabled and are configured to provide the best availability and resource utilization. vSphere DRS is full automated and the migration threshold is set to the default vSphere DRS level to avoid excessive vSphere vMotion operations. High availability of cluster resources is provided by vSphere HA and Auto remediation hardware.

vSphere High Availability is used to guarantee enough resources for restarting VMs during an ESXi host failure. The ESXi hosts are monitored and in the event of a failure, the VMs on a failed host are restarted on alternative ESXi hosts in the cluster. To maximize productivity while minimizing overhead, the vSphere HA settings of the cluster is configured to tolerate the equivalent of one ESXi host failure (25% percentage-based admission control policy). The host isolation response is set to power off and restart the VMs.

vmc2aws

Host failures remediation is the responsibility of VMware. If a host fails permanently, VMware replaces this ESXi host without user intervention. Automatic remediation of failed hardware eliminates the impact of long-term resource reduction of a permanent host failure. The Cloud SDDC is configured with two DRS resource pools. One resource pool contains the management VMs to operate the Cloud SDDC, while the other top-level resource pool is created to manage customer workloads. Customers have the option to create child resource pools.

The full post is available at frankdenneman.nl site.


VMware Social Media Advocacy

vSphere 6.5 Update 1 is out, here’s why you want to upgrade

vSphere 6.5 Update 1 is out, here’s why you want to upgrade

VMware have just released the first major update to vSphere 6.5, normally, I don’t blog on these but this update is so big and it fixes some really annoying bugs I saw using the GA version of vSphere 6.5… thankfully, we worked hard with their support to overcome some of the issues I highlighted in yellow, this was of course done for  the greater good.

The release notes for ESXI 6.5 U1 can be seen here https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-esxi-651-release-notes.html and it can be downloaded from here https://my.vmware.com/web/vmware/details?downloadGroup=ESXI65U1&productId=614&rPId=17343

The release notes for vCenter 6.5 U1 can be seen here https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-vcenter-server-651-release-notes.html and it can be downloaded from here https://my.vmware.com/web/vmware/details?downloadGroup=VC65U1&productId=614&rPId=17343


VMware Social Media Advocacy

The race on data circuit – DataCore Software

In the current and wide storage market, where access to data is faster and faster to satisfy applications demanding more and more data, vendors are mainly divided in Hardware and Software.
Among the second ones, a Company dealing since 1998 with data abstraction from the underlying storage harwdare is DataCore Software.

1280px-DataCore_Logo
The Company will explain its solutions on September during Tech Field Day 15, where I’m lucky enough to join the delegates that attend the event. This presentation will be also live at the same link.

Today, its offer is based on 2 products:

  • SANsymphony-V
  • Hyper-converged Virtual SAN

While the second is actually an Hyper-converged solution, the first one is probably the one that performs the best results in an enterprise environment.

SANsymphony-V can manage all the current standards (DA, SAN, and Cloud), is storage-agnostic, is also hypervisor-agnosticIn the SPC-1 test (Storage Performance Council – an independent organization performing benchmarks on storage devices – you can find the specific and complete report here), classified 1° on response with 100% load: 32 ms.

 

keyelements

Let’s have a look at 3 usual scenarios

  • traditional: storage separated from computing – usually in large enterprises where storage is already in place
  • converged: scale-up storage & consolidation model
  • hyperconverged : high level of consolidation

As we can see on the image, there are 3 main components in the storage presentation

  • storage residing in a datacore disk pool
  • virtual disk created from the disk pool
  • host servers virtualizing disks for every application

A centralized GUI manages the whole organization regardless of the number of nodes.
I had a look and I found it quite clear and intuitive.

One of the strenght points of this solution is that 2 is the minimum number of nodes needed.

SANSymphony resides in the middle of the virtual infrastructure, directly on the I/O path (Parallel I/O technology) between applications and the undelying storage, regardless of the vendor.

I have to say that many of the features offered are already present in the market from other competitors, but none of them is applied in a universally format compatibility, allowing aggregation of many vendors of storage, everyone adopting that features in the very same way of the other ones.

Definition of different storages can be set by the system or manually according to performances, assigning one of the 15 “Tiers” – data will move towards the higher tier using availability and performance parameters, automating the transition from hot to cold down to archiving data in a quite granular way.

tier

An additional performance optimization is made by using nodes’ RAM for the high frequently accessed data, much faster than any SSD or Flash disk.

Almost 2 decades of life of the Company and the objective and verified performances of its solutions make Datacore Software one of the best support for accelerating data access. And maybe today the real challenge is nomore data availability (considered as granted), but quick data access. The faster solution will win…