Skip to main content

Posts

Showing posts with the label Virtualization

VMware on AWS - How to restore NSX DFW firewall rules to previous state

Customers who uses NSX day-in, day-out would like to have a point-in time restore functionality of DFW firewall rules. Many customer have a large footprints in VMC and make changes to DFW quite often. This feature was missing for long time and we could see its included in recent versions . Let's see how DFW configuration roll back works  NSX DFW configuration has versioning, and it is stored in the NSX Manager.  Every time when someone update DFW configuration, NSX creates one more version but keep storing the previous ones. You can rollback for previous config but reapplying it once again.  You can find the options under Networking & Security tab , > Security > Distributed Firewall . In the right side we see an Actions drop down. Choose View to get to the below screen.  Let’s go through the use case:  1. Original state- default config with no custom rules:  a. There are no saved configurations during last 30 days: In my existing test setup, with the current setting

Update Manager 6.5 issue ""interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader""

This post is related to the issue what we faced today when we replaced the SSL certificates in our setup.  When I launched the web-client and access the update manager tab,  I get the message  "interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader" I started off by restarting the VMWare vSphere Update Manager Service for the affected vCSA: 1. Log into vCenter using the administrator@vsphere.local account. 2. Home - System Configuration - Services - Restart This did not resolve my issue...  And we tried restarting all the services by  SSH/Console into the affected server and run the following commands: service-control --stop --all service-control --start --all Still no luck.  Make sure the certs are applied and it gets reflected in the config file. ( verify if the thumbprint matches)  root@homelab71 [ /usr/lib/vmware-updatemgr/bin ]# pwd /usr/lib/vmware-updatemgr/bin root@ho

What’s New in vSphere 6.5: Host & Resource Management and Operations

vSphere 6.5 brings a number of enhancements to ESXi host lifecycle management as well as some new capabilities to our venerable resource management features, DRS and HA.  There are also greatly enhanced developer and automation interfaces, which are a major focus in this release.  Last but not least, there are some notable improvements to vRealize Operations, since this product is bundled with certain editions of vSphere.  Let’s dig into each of these areas. Enhanced vSphere Host Lifecycle Management Capabilities With vSphere 6.5, administrators will find significantly easier and more powerful capabilities for patching, upgrading, and managing the configuration of VMware ESXi hosts. VMware Update Manager (VUM) continues to be the preferred approach for keeping ESXi hosts up to date, and with vSphere 6.5 it has been fully integrated with the VCSA.  This eliminates the additional VM, operating system license, and database dependencies of the previous architecture, and now benefit

Introducing vSphere 6.5

VMware announces vSphere 6.5, the latest version of its industry-leading virtualization platform.  This new release of vSphere features a dramatically simplified experience, comprehensive built-in security, and a universal app platform for running any app. vSphere 6.5 accelerates the customer transition to digital transformation and cloud computing by addressing key challenges: 1.     Environments growing increasingly complex, 2.     Growing IT security threats, and 3.     The need to support both existing and new apps and services. Let’s take a look at some of the key capabilities. Dramatically Simplified Experience vSphere 6.5 elevates the customer experience to an entirely new level. It provides exceptional management simplicity, operational efficiency, and faster time to market vSphere 6.5 makes the  vCenter Server Appliance  the fundamental building block of a vSphere environment. The core vSphere architecture is built around this easy to deploy and manage appr

What is the difference between PCPU Used and PCPU Utilized?

I’m often asked the question when looking at vSphere statistics – “What is the difference between PCPU Used and PCPU Utilized and why don’t they match?” Let’s take a look as it can be somewhat complex. First lets start with some definitions: Time Stamp Counter (or TSC) – is a 64 bit register available on all modern processors that counts clock cycles at a consistent rate and is not affected by changes in clock frequency. Unhalted Cycles – another count of ‘all’ clock cycles, but this one is dependent on the clock frequency and therefore the rate can change if the clock frequency changes (due to things like power management or Hyper-Threading). Wall Clock Time – refers to elapsed real world time. Okay now lets define our two counters using the above definitions: PCPU utilized (which is TSC based) = (non-idle state TSC cycles)/wall clock time PCPU used (which is unhalted cycle based) = (unhalted cycles)/wall clock time So assuming a non Hyper-Threaded system, and no pow

Configuring SNMP traps for the vCenter Server

Steps to configure the vCenter Server to generate SNMP traps: A.In the Home page of vSphere Client B.Select vCenter Server Settings  C.Select SNMP configuration D.Enable one of the SNMP receivers E. Provide the details for :  Receiver URL : Provide the host name of the Management Server (target SNMP server / monitoring tool) which will be connected to the VMware vCenter Server. (VMware vCenter Server sends the SNMP traps to this Management Server) Configure port 162 as the SNMP port. Community String: Provide community string (default string is "public")  SNMP versions v1/v2/v3 are supported That is all that is needed for the configuration.  Now you need to configure alarm for generating SNMP traps in the vCenter server. When ever there is a change in the environment ( host state change, VM state change ,etc) the trigger will be generated and send an alert to the monitoring server.  Configure the Alarms After you have setup the external SNMP server, v

Explore vsphere 6.0

VVols Perhaps the most wanted feature in vSphere 6 is Virtual Volumes, or VVOLs. VVOLs extends the VMware software-defined storage (SDS) story to its storage partners, and completely changes the way its hypervisor consumes storage; it radically changes how storage is presented, consumed and managed by the hypervisor. No longer is virtual machine (VM) storage bound by the attributes of the LUN, as each VM disk (VMDK) can have its own policy-driven SLA. VMware has a passel of storage vendors on board to equip its storage, with the ability to offer VVOLs storage to the VMware hypervisor. I'm sure this feature will get much press and customer attention in the coming days. vMotion vSphere vMotion just got 10 times better, and a lot more interesting. For one thing, it supports live VM migration  across vCenter servers, and over long distances. It used to support round trip times (RTTs) of 10 ms, but now supports RTTs of 100 ms. A ping from Portland, Ore., to Boston, Mass., is 90 ms;