How #VMware’s NSX Will Set the Pace for Its Future Growth (via Yahoo Finance)
How VMware’s NSX Will Set the Pace for Its…
VMware launched NSX in November 2013 after it acquired the technology from Nicira, a startup supplier, for $1.3 billion.
How #VMware’s NSX Will Set the Pace for Its Future Growth (via Yahoo Finance)
VMware launched NSX in November 2013 after it acquired the technology from Nicira, a startup supplier, for $1.3 billion.
Top Horizon 7 Insights and IT Best Practices From Our Pros
vmw-tech-consulting-servicesWe’ve talked a lot about the newest capabilities introduced in VMware Horizon 7, but how does it change the roles within your IT organization or impact your long-term end-user computing strategy?
LSI3108 based controllers now #VSAN 6.2 Certified – Blah, Cloud.
After a long an arduous certification and regression testing process following many problems with LSI 3108 based controllers that I have been using for VSAN they are finally VSAN 6.2 certified.
Virtual Volumes Compatiblity Guide Gets A Refresh
Over the last year the number of Virtual Volumes implementations has increased significantly. From a handful of key VVol partners in early 2015 we now have over 150 array models certified for VVols from 15+ partners with more on the way. Given this rapid growth in support for VVols we have heard from customers that the VMware Compatibility Guide for Virtual Volumes needs to be updated to make it faster and easier to use.
Troubleshooting with vRops part 4: Standard Deviation (via michaelryom.dk)
In the last blog post I showed you what Object level metrics are and how they could be used, to fast get an idea to of how a VM is behaving. In this one I’m going to focus on what metrics can be used to get a better understanding of how a VM is behaving.
Troubleshooting with vRops part 3: Object Level Metric (via michaelryom.dk)
In this part I am going to show you how to use object level metrics, to fast and easily assess if for example a VM is having problems. This is something that would give you a quick indication of this object is having problems that need to be address. This should be looked at before diving into the raw metrics, as this will help you and can guide you in the right direction.
Troubleshooting with vRops part 2: Summary and Symptoms (via michaelryom.dk)
In the first part of this series on vRops, I talked about vRops capabilities compared to the vRops edtion. In this part I will start to dig into how you should start looking at a problem the vRops way. I my self have fallen victim to, all too quickly jumping over to the “all metrics” tab, and start throwing graph up on screen to see if I can find the cause of the issue. The problem with that method is that it is highly inefficient and like looking for a needle in a haystack, it can take quite some time and the result may not have gotten you any closer to finding the problem… Why there are haystacks with needles in them ?
Troubleshooting with vRops part 1: vRops Capability (via michaelryom.dk)
vRops 6 have been out for a while now, and with that a lot of great things have come, depended on your vRops license that is.
Next Generation Networking: Defining The Software-Defined Network (via thedataplumber.net)
The purpose of this post is to define the concepts, the Software-Defined Network (SDN), and some current architectures. The detail here will underpin many of the posts to come.
#vRealize Operations Manager 6.2.1 is out. Go for it! (via vxpresss.blogspot.com)
A few hours back VMware announced the release of vRealize Operations Manager 6.2.1. This is a maintenance release and is highly recommended for use cases such as:
Forwarding Events from #vRealize Log Insight (via bkdatacentre.com)
I have so far written a few articles on vRLI, see the links at the bottom of this page for the links. This article goes in to forwarding events from vRealize Log Insight to a 3rd party Syslog Server and filtering them.
Adding Worker Nodes to #vRealize Log Insight (via bkdatacentre.com)
In my pevious post Deploying & Configuring Log Insight I touch on the possibility of adding multiple nodes to scale the total Log Injection Rate and Events per Second, in addition additional nodes will ensure your logging infrastructure is highly available, which is a critical point from a security perspective.
Installing and configuring the NSX for #vSphere Managment pack (via bkdatacentre.com)
Download the NSX for vSphere Management pack from the VMware Solution Exchange https://solutionexchange.vmware.com/store/products/management-pack-for-nsx-for-vsphere-2-0
Configuring NSX Adaptor for Log Insight (via bkdatacentre.com)
So if you have installed your NSX content pack in log insight and noticed that no information is presented in the new dashboard:
#VMware vRealize Operations Manager (vROps) 6.X Architecture (via Virtual Maestro)
VMware vRealize Operations Manager (vROps) 6 helps IT admins to monitor, troubleshoot, and manage the health and capacity of virtual environment. vRealize Operations is a suite that includes vCenter Infrastructure Navigator (VIN), vRealize Configuration Manager (vCM), vRealize Log Insight, and vRealize Hyperic.
vROps 6.x Persistence and its databases (via blogs.virtualmaestro.in)
The Persistence layer is the layer where the data is persisted to a disk. The layer primarily consists of a series of databases that replace the existing vCOps 5.x filesystem database (FSDB) and PostgreSQL combination.
NSX – Transport Zone (via vcrooky.com)
Next up is creating a Transport Zone! Transport Zones are a way to define which clusters/hosts are be able to see and participate in the virtual network that are being configured. Its like a container that houses NSX Logical Switches along with their details which is then assigned to a collection of ESXi hosts that should be able to communicate with each other across the physical network infrastructure.
NSX – Distributed Logical Router (Basics) via vcrooky.com
In this post I will step through the basic deployment steps of a Distributed Logical Router (DLR)… but first what is a DLR?
NSX – Logical Switch (via vcrooky.com)
Next up on the NSX build out is creating logical switches! A logical switch is a distributed port group on a distributed switch. So why logical? Because it gets a unique VNI (VXLAN Network Identifier) to overlays the L2 network.
#ESXi 6.0 Update 2 bug with VMXNET3 vNICs
The ESXi 6.0 Update 2 has introduced a bug with VMXNET3 vNICs that causes the ESXi to crash.