Op 19 maart vindt het NLVMUG event 2015 plaats in Den Bosch. De NLVMUG volunteers willen je hier graag voor uitnodigen. Er wordt een gevarieerd programma voorbereid met keynote sessies en verschillende tracks met top sprekers.
We kunnen al een tipje van de sluier oplichten over een zeer interessante spreker die over zal komen uit de UK: VMware’s Chief Technology Officer EMEA Joe Baguley. Binnen de Cloud Community wordt Joe gezien als één van de meest invloedrijke personen in Europa (quote Computer Weekly UKtech50).
De volledige agenda zal binnenkort online beschikbaar zijn op http://www.nlvmug.com. Schrijf je nu in voor het NLVMUG event 2015, het inschrijfformulier is hier beschikbaar. Deelname aan de NLVMUG kost 49,00 euro excl BTW.
Donderdag, 19 maart 2015
1931 Congrescentrum Brabanthallen
Oude Engelenseweg 1
5222 AA ’s-Hertogenbosch
To resolve this issue, stop the alarm from triggering repeatedly and clear the IPMI System Event.log file and reset the sensors.
To clear the IPMI System Event.log file and reset the sensors:
- Open vCenter Server using vSphere Client.
- In the vCenter Inventory, select the ESXi/ESX host.
- Click the Hardware Status tab.
- Click System Event log under View.
- Click Reset Event Log. The red alert is removed from the System Event log.
- Click Reset Sensors to reset the host sensors.
Introduced in ESXi 5.1 Update 2 (Build Number: 1483097) and ESXi 5.5 Patch 1 (Build Number: 1474528), there is a new localcli command line to clear the IPMI SEL logs:
localcli hardware ipmi sel clear
To run localcli command on the ESXi 5.1 or 5.5 host:
- Connect to the ESXi host via SSH. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).
- Run this command:
localcli hardware ipmi sel clear
More information: VMware
When deploying the VMware vCenter Server Appliance (VCSA) it will default look for a DHCP address. When there is no DHCP server available the following error is displayed:
NO NETWORKING DETECTED, PLEASE LOGIN AND RUN THE COMMAND /opt/vmware/share/vami/vami_config_net TO CONFIGURE THE NETWORK
1. Press F2 to login
2. Enter default username: root
3. Enter default password: vmware
4. Run command: /opt/vmware/share/vami/vami_config_net
5. Press 6 to setup eth0
6. After allocate a static IP Address to the VCSA the post configuration can be done by using the following URL:
Hyper-Convergence Meets Data Protection and High Availability
In 2014, there were 28 million IT professionals worldwide. IDC expects this number to grow to 36 million by 2020. The trouble here is that the amount of data for which these professionals are held responsible is growing at a much higher rate. Today, each IT professional on average is responsible for 230GB; by 2020, that number will explode to 1,231GB. This massive spike is made even more challenging by the increasing richness of data sources and formats, driven by everything from new applications to the Internet of Things.
This is the reason that productivity — doing more with less — has never been more important for the engineers creating and building next generation data centers. This is one reason that hyper-converged storage has been increasingly popular. Hyper-converged infrastructure systems offer a software-defined scale-out architecture that integrates compute, networking, and storage via virtualization. At the end of the day, what these systems offer to the overburdened IT professional is a more productive way of creating and managing IT infrastructure.
The future of backup lies in hyper-convergence as well. The basic architecture of a backup appliance — a server, networking, storage, operating system, and backup software — will need to take advantage of more and faster processors and cores, memory, backplane and I/O performance. Flash-enabled architectures will increasingly become mandatory — not just to enable faster backup and recovery, but also because of the increased functionality that the backup appliance must support in terms of more capability and high availability. Techniques such as on-appliance virtualized instant recovery of virtual and physical environments, as well as off-appliance support of virtual environments, will present very different I/O loads that can only be reconciled with tiered flash and rotational storage.
Today I tried installing VMware vSphere Client 4.1 on my Windows 8.1 update 1 workstation and I received this error message:
This product can only be installed on Windows XP SP2 and above.
1. Download the vSphere ClientCLient installer
2. Properties > Compatibility > Run this program in compatibility mode for: Windows XP SP2
A general system error occurred: alias value should not be empty
This issue occurs when the Active Directory Identity Sources are not available.
This issue may also occur while SSO is starting up, or for a period of time after start-up. This occurs when the number of domains in the Active Directory forest is large.
This is a known issue affecting:
- VMware vCenter Server 5.5.0b (Build 1476327)
- VMware vCenter Server 5.5.0 Update 1 (Build 1623101)
- VMware vCenter Server Appliance 5.5.0b (Build 1476327)
- VMware vCenter Server Appliance 5.5.0 Update 1 (Build 1623101)
This issue is resolved in vCenter Server 5.5 Update 2, available at VMware Downloads. For more information, see the Resolved Issues section in the vCenter Server 5.5 Update 2 Release Notes.
More information: VMware
Virtual Hardware (VMX) Template configuration
||Number of virtual sockets: 1
Number of cores per socket: 2
||Number of video displays: 1
Total video memory: 5 MB (1280×1024)
|SCSI Controller 0
Hard disk 1
|LSI Logic SAS, bus sharing: none
40 GB, Thick Provision Eager Zeroed (<—best performance)
|CD/DVD Drive 1
|Floppy Drive 1
|Network Adapter 1
||VMXNET3, network: VM Network with DHCP (for joining domain)
||OS: Microsoft Windows Server 2012 R2 (64-bit)
||Advanced: Check and upgrade Tools during power cycling
|Virtual Machine Version
||8 (not 9 because you only can edit version 9 via vSphere web-client)
|Advanced > General
Virtual Machine BIOS configuration
|Boot-time Diagnostics Screen
Categories: Hyper-V, Microsoft, VMware Advanced Configuration, BIOS, Favorite, How-To, Hyper-V, Microsoft, Performance, Template, VMware, vSphere, Windows 2012R2
Last week I added a new vSphere host in my homelab, after I configured and started my backup job in the Backup & Replication 7.0 patch 4 environment I received this error messages:
Processing ‘DC01′ Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-12,nfchost:host-10,conn:vce01.vmpros.local]. Storage display name: [ESX01_VMFS02].
Failed to create NFC download stream. NFC path: [nfc://conn:vce01.vmpros.local,nfchost:host-10,stg:datastore-12@DC01/DC01.vmx].
When you look at the Backup Job log file you can see the details, logfile location: C:\ProgramData\Veeam\Backup\VMpros_-_Backup_01
In my case Veeam Backup could resolve my VMware vCenter 5.5 server but when he try to contact the vSphere host with some local datastores the backup failed. I tried to ping the hosts and couldn’t resolve the hostname of my vSphere host.
Make sure you have:
- Added the vSphere host in DNS, create a A record in your DNS server
Optionally: Add the vSphere hostsname(s) and IP-address(es) in the hostfile at your Veeam Backup server
More information: Veeam