Aug 01

Meet NPX 004 – Samir Roshan

“VMTurbo"

  • Name: Samir Roshan
  • NPX Number: 004
  • Employer: Nutanix Inc
  • Blog URL: thinkingloudoncloud.com
  • Twitter: @kooltechies
  • Virtualisation background: 10+ years of virtualisation experience
  • Storage Background: Storage has been a continuous part of my journey in the virtualisation world sometimes mainstream some times not. I will say close to ~5 years overall.
  • Hyper Converged Infrastructure background: Since my joining Nutanix in 2014
  • Future of HCI and other emerging technologies: HCI will be the mainstream platform for running application and infrastructure going forward. HCI will replace 3 tier storage completly over a period of time. In other emerging technologies we will see a constant pull and push of new concepts and prototypes. There will be concrete steps taken in the field of Micro-services. Cloud computing and dev-ops will continue its rally , Openstack will have a hard time surviving.
  • Value of NPX: Enormous !! NPX is the first certification to blend Multi hypervisors enabling architects to advise on architect solutions which includes Private Cloud, Microservices and Public cloud. The certification is an extremely challenging and rewarding one from the perspective of experience and skill sets required to go through it. Architects who wants to pursue skills in multiple areas should really go for it.
  • What made you go for NPX: Primarily because of the value and learning by pursuing NPX. It has enabled me to look at the challenges in IT at a very holistic level. I am in a position to advise my customer on different hypervisors, HCI, Webscale, Microservices and on Cloud.
  • Advise to people looking into the NPX track: Preparation is the key, this is probably the top level certification in the world right now. There are no shortcuts in order to achieve this, you need to follow the exam blueprint covering each areas in detail. Solid architectural understanding, technical expertise on the selected hypervisors, expert knowledge on the Nutanix platform is key to success.
  • Other: For all NPX aspirants feel free to reach out for any clarification or if you need any mentorship for the program.

Jul 30

Heads up! LUNs attached to VMware vSphere 6.0 hosts may remain in APD Timeout state

“VMTurbo"
28 July VMware released a knowledgeable article describing a problem with ESXi 6.0 and the All Path Down (APD).

The problem is that a LUN that have experienced an APD state never exist the APD state and the LUN is not accessible from the ESXi host even though the connection between the ESXi host and the datastore has been established.

Currently there is not fix or workaround that will guarantee to get the LUN back online but there are recommended actions when this happens:

  • Follow VMware KB 2014155 to kill outstanding I/O to a LUN and maybe also restart the ESXi host management agents.
  • Reboot the ESXi host.

Good news is that not all APD event will see this behaviour but i have not been able to find the exact once yet. Will update the blog post when/if i do.

For additional information, please read VMware KB 2126021

Jul 30

Top vBlog 2015 gift received

“VMTurbo"
As i wrote in this blog post my blog was voted as number 17 during the annual top vBlog voting contest held by Eric Siebert at vSphere-land and i’m really thankful to all my readers for this. Just wanted to let you know that i received the prize the other day and it was a nice coin as you can see by the below picture.

Top-VBlog-2015

Once again, thanks Eric for putting this together since i understand it takes quite a lot of time and also a thanks you to Infinio for sponsoring the voting contest.

Jul 28

Upgrade to vSphere ESXi 6 via command line

“VMTurbo"

The other day i had to upgrade my lab ESXi mgmt server from version 5.5 to 6.0 host via the command prompt and it’s actually pretty straight forward. I took the following steps to perform the upgrade:

  1. Download the latest ESXi version from the VMware website
  2. Log on to the ESXi server using SSH
  3. Verify running ESXi version using e.g.
    1. run the following command:
      vmware -v
      In my case i was running ESXi 5.5.0 build-2143827
      Screen Shot 2015-06-25 at 11.36.32
    2. Starting the Direct Console User Interface (DCUI) from the SSH session by typing:
      dcui
      Screen Shot 2015-06-25 at 12.04.40
      Press ctrl c to leave the DCUI mode and get back to the original SSH session
  4. Upload the ESXi .zip depot to the ESXi host by running the following command:
    scp VMware-ESXi-6.0.0-2494585-depot.zip root@10.10.100.xyz:/vmfs/volumes/54aeddbd-e5943701-1cf2-f8db88fbd420/
    Screen Shot 2015-06-25 at 11.59.16
    The 54aeddbd-e5943701-1cf2-f8db88fbd420 directory is scratch directory where e.g. the core, downloads, var directories exists. When upgrading multiple ESXi hosts you should use a shared datastore but i didn’t have one available for my single ESXi mgmt host. Thanks Mostafa for pointing this out.
    Screen Shot 2015-06-25 at 11.59.32
  5. Shut down the running virtual machines on the host byt first identify their VM IDs and then shutting them down:
    1. Identify VM IDs by running:
      vim-cmd vmsvc/getallvms
      This will give you output like:
      Vmid/Name/File/Guest OS/Version/Annotation
      In my case e.g:
      12/ad01/[MGMT-DS02] ad01/ad01.vmx/windows8Server64Guest/vmx-10
    2. Shut down the VMs by running:
      vim-cmd vmsvc/power.shutdown 12
  6. Put the ESXi host in maintenance mode by running the following command:
    vim-cmd /hostsvc/maintenance_mode_enter
    Screen Shot 2015-06-25 at 11.56.34
  7. Verify the existing ESXi host software profile by running the following command:
    esxcli software profile get
    In my case i was using the Standard profileScreen Shot 2015-06-25 at 11.53.24
  8.  Verify the profiles available in the VMware VMware-ESXi-6.0.0-2494585-depot.zip file by running the following command:
    esxcli software sources profile list –depot=/vmfs/volumes/54aeddbd-e5943701-1cf2-f8db88fbd420/VMware-ESXi-6.0.0-2494585-depot.zip
    Important: Make sure to use two minus – – signs before depot
    Both the Standard and no-tools profiles were includedScreen Shot 2015-06-25 at 12.02.48
  9. Perform the upgrade by running the following command:
    esxcli software profile update –depot=/vmfs/volumes/54aeddbd-e5943701-1cf2-f8db88fbd420/VMware-ESXi-6.0.0-2494585-depot.zip –profile=ESXi-6.0.0-2494585-standard
    Important: Make sure you use
    * the update and not install command
    * use two minus – – signs before profile
    This was the output from the successful upgrade: Screen Shot 2015-06-25 at 12.04.18
  10. Reboot the ESXi host, via DCUI
  11. Log on via SSH when the host has been rebooted
  12. Verify that the new version is running using “vmware -v”,  “dcui” or “esxcli software profile get”
    Screen Shot 2015-06-25 at 12.47.52
  13. Exit maintenance mode by running the following command:
    vim-cmd /hostsvc/maintenance_mode_exi
    Screen Shot 2015-06-25 at 12.50.15
  14. Power on your VMs by running the following command:
    vim-cmd vmsvc/power.on VMid
    In my case i started with the VM ID = 2

Simple as that to upgrade the ESXi host from version 5.5 to 6.0 via CLI.

Jul 23

Nutanix Operating System 4.1.4 released

“VMTurbo"

It has only been approximately 1,5 months since the latest Nutanix Operating System (NOS) release and yesterday, 2015-07-22, Nutanix released yet another version of its operating system. Read more about the previous release 4.1.3 here. The new version, 4.1.4, comes with e.g. the following new features:

  • Restore virtual machine (VM) locality after Acropolis host failure.
    • This means VMs are being migrated back to the Acropolis host where they were running before the Acropolis host were brought into maintenance mode. This feature is also included for the Nutanix Clusters configured with Best Effort High Availability (HA).
  • Metro Availability
    • Take local snapshots of metro availability protection domain (PD) and replicate asynchronous remote site.
      • Can be scheduled via PRISM (Nutanix UI)
    • Snapshot is taken on both sites in the Metro Availability cluster but driven by the primary site
    • Data transfer is kept to a minimum since only PD metadata replication is performed to complete the snapshot.
  • Improved performance to Disk Firmware upgrades.

NOS 4.1.4 can be downloaded from your existing Nutanix cluster via PRISM or via the Nutanix Portal

Screen Shot 2015-07-23 at 23.56.34

The complete release notes for NOS 4.1.4 can be found here.

The following software were also been updated yesterday:

  • Prism Central 4.1.4 – Release notes can be found here.
  • NCC 2.0.1 – Release notes can be found here.

Jul 21

Nutanix Operating System PreUpgrade checks

“VMTurbo"

I have been asked a few times what is actually included in the Nutanix Operating System (NOS) PreUpgrade check available before you conduct a NOS upgrade so i figure i write a short blog post about it.

The NOS PreUpgrade check is available via the Upgrade Software link under the gear icon at the right hand side of PRISM. You can run the check manually or it will be automatically taken care of before the Upgrade process starts.

Screen Shot 2015-06-11 at 05.28.04

The PreUpgrade will run a set of tests to verify that your cluster is in a good state before continue with the manual or automatic upgrade. The following list includes the most important tests included in the PreUpgrade check:

  • All CVMs are reachable
  • Cluster state
  • Cluster services
  • Enough free space exists
  • Metadata son release is valid and not corrupt.
  • Upgrade is compatible with current version of NOS
  • Upgrade software is not corrupt
  • It checks for:

There is also and PostUpgrade check running when the NOS upgrade is complete but that is not a process you can start manually via PRISM.

Jul 19

Heads up! Quiescing operations cause a Windows virtual machine to panic

“VMTurbo"
I usually don’t create blog post with bug related information but i think VMware KB 2115997, Quiescing operations cause a Windows virtual machine to panic with a Stop 24 error on ntfs.sys, updated July 9 2015 is something that i need to share. I have been contacted a few times over the past weeks in regards of this issue.
When you take a snapshot of a virtual machine you might see the following:

  • Snapshot operation fails
  • The virtual machine (VM) panic with the following information:
    • A problem has been detected and Windows has been shut down to prevent damage to your computer

The problem affects the ESXi 5.x (5.0.x , 5.1.x and 5.5.x) and ESXi 6.0.x when the VM runs one of the following VMware tools versions:

  • 8.6.15
  • 9.0.15
  • 9.4.11
  • 9.10.0
  • 9.4.12

There is locally a patch available for ESXi 6.0.x, ESXi600-201507403-BG, which you can read about here.

Unfortunately there is no patch available for 5.x but there are a few workarounds

  • Install a VMware tools version that is not affected
  • Disable snapshot quiescing for your VMs
  • Don’t select “Quiesce guest file system” when manually taking VM snapshot(s)

Jul 17

Meet NPX 003 – Jonathan Kohler

“VMTurbo"

  • Name: Jonathan Kohler
  • NPX Number: 003
  • Employer: Nutanix
  • Blog URL: vdoogle.wordpress.com
  • Twitter: @JonKohler
  • Virtualisation background: Health Care – Mission/Life Critical app BCA virtualization, and DC/Infra consulting.
  • Storage Background: Multi-PB EMC environments, NetApp, EqualLogic
  • Hyper Converged Infrastructure background: Nutanix XCP
  • Future of HCI and other emerging technologies: Good question, I don’t have a crystal ball, but I do predict that nothing will ever slow down. The pace of innovation in HCI and beyond is break neck speed.
  • Value of NPX: NPX presents technologists from all walks of life the ability to sharpen their Enterprise Architecture skills in at least two different product (hypervisor) families. This is HUGE, as forcing a two product stack “X Level” really rounds out the foundational knowledge, and sharpens two points instead of one.
  • What made you go for NPX: I love tough challenges.
  • Advise to people looking into the NPX track: Start early, and study often. Get hands on experience. Ask others to challenge you. Treat EVERY project you do like an “X Level” project, regardless of its actual scope.

Jul 14

vCenter Server won’t start

“VMTurbo"
This is actually the second blog post with the same name. I had the same problem, vCenter Server didn’t start, about a year ago and you can read that blog post here.

This blog post applies to vCenter Server 5.5.0 build 2442329 and the problem was that the vCenter Server service didn’t start after an unexpected reboot of the Windows 2012 R2 virtual machine (VM) running the the vCenter Server service.

While investigating the most recent vCenter Server log file, vpxd-xyz.log, located in the directory C:\ProgramData\VMware\VMware VirtualCenter\Logs i found the following:

“2015-07-xxT11:29:31.894+02:00 [04760 error ‘Default’] CoreDump: unable to create the dump file: class Vmacore::SystemException(The file or directory is corrupted and unreadable. )”
See the entire log file here

Based on the log file entries i tested the following:

  • Create a file on the C: root directory and it failed.
  • Create a file on my desktop and it failed.
  • Create a file in a lot of different directories on the C: and all the tests failed.
  • Create a file on D: and this was successful

So it was obvious that we had problem with the C: drive but at least some, e.g. vCenter Server, log files could be created:)

I also found a lot of entries in the Windows Server Event Log e.g.:

  • Application log
    Event ID 1000
    Level Error
    Faulting application name: vpxd.exe, version: 5.5.0.43769, time stamp: 0x54b90698
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
    Exception code: 0xe06d7363
    Fault offset: 0x0000000000008b9c
    Faulting process id: 0x1e9c
    Faulting application start time: 0x01d0bc80dd30a512
    Faulting application path: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 1aec81ff-2874-11e5-80d7-005056a041b3
    Faulting package full name:
    Faulting package-relative application ID:
  • Application Log
    Event ID 1001
    Level Information
    Source Windows Error Reporting
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: vpxd.exe
    P2: 5.5.0.43769
    P3: 54b90698
    P4: KERNELBASE.dll
    P5: 6.3.9600.17415
    P6: 54505737
    P7: e06d7363
    P8: 0000000000008b9c

The first action taken to solve the problem was running check disk using the following command:

  • chkdsk C: /F
    This command requires a reboot based on the following command output:
    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

However, during the reboot the check disk ran for a very very short time and didn’t solve my problem so i ran check disk again using the scan option:

  •  chkdsk C: /scan

When finished i could copy files to my C: drive again and the vCenter Server started again so everything is back to normal. Now we just have to figure out why the VM rebooted but that’s another story.

vCenter Server log file

Section for VMware VirtualCenter, pid=1424, version=5.5.0, build=2442329, option=Release

—— In-memory logs start ——–
mem> 2015-07-xxT11:29:31.827+02:00 [04760 info ‘Hooks’] Hooks Initialized

—— In-memory logs end ——–
2015-07-xxT11:29:31.859+02:00 [04760 info ‘Default’] Logging uses fast path: true
2015-07-xxT11:29:31.859+02:00 [04760 info ‘Libs’] VThreadBase detected multiple threads.
2015-07-xxT11:29:31.859+02:00 [04760 info ‘Default’] Handling bora/lib logs with VmaCore facilities
2015-07-xxT11:29:31.859+02:00 [04760 info ‘Default’] Initialized channel manager
2015-07-xxT11:29:31.885+02:00 [04760 info ‘Default’] Current working directory: C:\Windows\system32
2015-07-xxT11:29:31.885+02:00 [04760 info ‘Default’] ThreadPool windowsStackImmediateCommit = true
2015-07-xxT11:29:31.885+02:00 [04760 info ‘ThreadPool’] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 200, 2, 90, 2147483647
2015-07-xxT11:29:31.885+02:00 [04760 info ‘ThreadPool’] Thread enlisted
2015-07-xxT11:29:31.885+02:00 [00828 info ‘ThreadPool’] Thread enlisted
2015-07-xxT11:29:31.885+02:00 [04760 info ‘Default’] Log path: C:\ProgramData\VMware\VMware VirtualCenter\Logs
2015-07-xxT11:29:31.885+02:00 [02408 info ‘ThreadPool’] Thread enlisted
2015-07-xxT11:29:31.885+02:00 [04760 info ‘Default’] Initializing SSL
2015-07-xxT11:29:31.885+02:00 [01836 info ‘ThreadPool’] Thread enlisted
2015-07-xxT11:29:31.886+02:00 [01352 info ‘ThreadPool’] Thread enlisted
2015-07-xxT11:29:31.887+02:00 [04760 info ‘Default’] Vmacore::InitSSL: handshakeTimeoutUs = 120000000
2015-07-xxT11:29:31.888+02:00 [04592 info ‘ThreadPool’] Thread enlisted
2015-07-xxT11:29:31.891+02:00 [04760 warning ‘Libs’] FileIOCreateRetry: Unrecognized error code: 1392
2015-07-xxT11:29:31.891+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] [VpxUnhandledException] Win32 Exception (3765269347) detected at 00007ff8f01c8b9c
–>
2015-07-xxT11:29:31.891+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] rip: 140707157019548 rsp: 86765840 rbp: 0
–>
2015-07-xxT11:29:31.891+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] rax: 140707201861943 rbx: 86766208 rcx: 60162048
–> rdx: 0 rdi: 6447380920 rsi: 19301800
–> r8: 1761332359 r9: 34772056277007 r10: 23362607753396275
–> r11: 2207616008235 r12: 1 r13: 0
–> r14: 0 r15: 0
–>
2015-07-xxT11:29:31.893+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] [VpxUnhandledException] Backtrace
–> backtrace[00] rip 000000018018b7fa
–> backtrace[01] rip 0000000180104c78
–> backtrace[02] rip 0000000180105f6e
–> backtrace[03] rip 00007ff7936adada
–> backtrace[04] rip 00007ff8f02a1c72
–> backtrace[05] rip 00007ff8f2d01328
–> backtrace[06] rip 00007ff8f2ce2456
–> backtrace[07] rip 00007ff8f2cf3acd
–> backtrace[08] rip 00007ff8f2cb8407
–> backtrace[09] rip 00007ff8f2cb762d
–> backtrace[10] rip 00007ff8f01c8b9c
–> backtrace[11] rip 0000000068fb54ca
–> backtrace[12] rip 00000001800fac8f
–> backtrace[13] rip 0000000180112e0c
–> backtrace[14] rip 0000000180113830
–> backtrace[15] rip 00007ff7935d9c92
–> backtrace[16] rip 00007ff7933befa2
–> backtrace[17] rip 00007ff7935f7c9b
–> backtrace[18] rip 00007ff8f1ba7f2a
–> backtrace[19] rip 00007ff8f05013d2
–> backtrace[20] rip 00007ff8f2cce954
–>
2015-07-xxT11:29:31.893+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] [VpxUnhandledException] Generating minidump …
2015-07-xxT11:29:31.894+02:00 [04760 warning ‘Libs’] FileIOCreateRetry: Unrecognized error code: 1392
2015-07-xxT11:29:31.894+02:00 [04760 error ‘Default’] CoreDump: unable to create the dump file: class Vmacore::SystemException(The file or directory is corrupted and unreadable. )
2015-07-xxT11:29:31.894+02:00 [04760 error ‘Default’] (Log recursion level 2) VpxUnhandledException

—— In-memory logs start ——–
mem> 2015-07-xxT11:29:31.827+02:00 [04760 info ‘Hooks’] Hooks Initialized
mem> 2015-07-xxT11:29:31.859+02:00 [04760 info ‘Default’] Section for VMware VirtualCenter, pid=1424, version=5.5.0, build=2442329, option=Release
mem> –>
mem> 2015-07-xxT11:29:31.859+02:00 [04760 info ‘Default’] Logging uses fast path: true
mem> 2015-07-xxT11:29:31.859+02:00 [04760 info ‘Libs’] VThreadBase detected multiple threads.
mem> 2015-07-xxT11:29:31.859+02:00 [04760 info ‘Default’] Handling bora/lib logs with VmaCore facilities
mem> 2015-07-xxT11:29:31.859+02:00 [04760 info ‘Default’] Initialized channel manager
mem> 2015-07-xxT11:29:31.885+02:00 [04760 info ‘Default’] Current working directory: C:\Windows\system32
mem> 2015-07-xxT11:29:31.885+02:00 [04760 info ‘Default’] ThreadPool windowsStackImmediateCommit = true
mem> 2015-07-xxT11:29:31.885+02:00 [04760 info ‘ThreadPool’] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 200, 2, 90, 2147483647
mem> 2015-07-xxT11:29:31.885+02:00 [04760 info ‘ThreadPool’] Thread enlisted
mem> 2015-07-xxT11:29:31.885+02:00 [00828 info ‘ThreadPool’] Thread enlisted
mem> 2015-07-xxT11:29:31.885+02:00 [04760 info ‘Default’] Log path: C:\ProgramData\VMware\VMware VirtualCenter\Logs
mem> 2015-07-xxT11:29:31.885+02:00 [02408 info ‘ThreadPool’] Thread enlisted
mem> 2015-07-xxT11:29:31.885+02:00 [04760 info ‘Default’] Initializing SSL
mem> 2015-07-xxT11:29:31.885+02:00 [01836 info ‘ThreadPool’] Thread enlisted
mem> 2015-07-xxT11:29:31.886+02:00 [01352 info ‘ThreadPool’] Thread enlisted
mem> 2015-07-xxT11:29:31.887+02:00 [04760 info ‘Default’] Vmacore::InitSSL: handshakeTimeoutUs = 120000000
mem> 2015-07-xxT11:29:31.888+02:00 [04592 info ‘ThreadPool’] Thread enlisted
mem> 2015-07-xxT11:29:31.890+02:00 [04760 verbose ‘vpxdvpxdSupportManager’] Uptime Log: C:\ProgramData\VMware\VMware VirtualCenter\Logs/1436693371889642.vpxduptime
mem> 2015-07-xxT11:29:31.891+02:00 [04760 verbose ‘vpxdvpxdSupportManager’] Moved 0 uptime log(s) to cache dir
mem> 2015-07-xxT11:29:31.891+02:00 [04760 warning ‘Libs’] FileIOCreateRetry: Unrecognized error code: 1392
mem> 2015-07-xxT11:29:31.891+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] [VpxUnhandledException] Win32 Exception (3765269347) detected at 00007ff8f01c8b9c
mem> –>
mem> 2015-07-xxT11:29:31.891+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] rip: 140707157019548 rsp: 86765840 rbp: 0
mem> –>
mem> 2015-07-xxT11:29:31.891+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] rax: 140707201861943 rbx: 86766208 rcx: 60162048
mem> –> rdx: 0 rdi: 6447380920 rsi: 19301800
mem> –> r8: 1761332359 r9: 34772056277007 r10: 23362607753396275
mem> –> r11: 2207616008235 r12: 1 r13: 0
mem> –> r14: 0 r15: 0
mem> –>
mem> 2015-07-xxT11:29:31.893+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] [VpxUnhandledException] Backtrace
mem> –> backtrace[00] rip 000000018018b7fa
mem> –> backtrace[01] rip 0000000180104c78
mem> –> backtrace[02] rip 0000000180105f6e
mem> –> backtrace[03] rip 00007ff7936adada
mem> –> backtrace[04] rip 00007ff8f02a1c72
mem> –> backtrace[05] rip 00007ff8f2d01328
mem> –> backtrace[06] rip 00007ff8f2ce2456
mem> –> backtrace[07] rip 00007ff8f2cf3acd
mem> –> backtrace[08] rip 00007ff8f2cb8407
mem> –> backtrace[09] rip 00007ff8f2cb762d
mem> –> backtrace[10] rip 00007ff8f01c8b9c
mem> –> backtrace[11] rip 0000000068fb54ca
mem> –> backtrace[12] rip 00000001800fac8f
mem> –> backtrace[13] rip 0000000180112e0c
mem> –> backtrace[14] rip 0000000180113830
mem> –> backtrace[15] rip 00007ff7935d9c92
mem> –> backtrace[16] rip 00007ff7933befa2
mem> –> backtrace[17] rip 00007ff7935f7c9b
mem> –> backtrace[18] rip 00007ff8f1ba7f2a
mem> –> backtrace[19] rip 00007ff8f05013d2
mem> –> backtrace[20] rip 00007ff8f2cce954
mem> –>
mem> 2015-07-xxT11:29:31.893+02:00 [04760 warning ‘win32vpxdOsLayer_win32′] [VpxUnhandledException] Generating minidump …
mem> 2015-07-xxT11:29:31.894+02:00 [04760 warning ‘Libs’] FileIOCreateRetry: Unrecognized error code: 1392
mem> 2015-07-xxT11:29:31.894+02:00 [04760 error ‘Default’] CoreDump: unable to create the dump file: class Vmacore::SystemException(The file or directory is corrupted and unreadable. )
mem> 2015-07-xxT11:29:31.894+02:00 [04760 error ‘Default’] (Log recursion level 2) VpxUnhandledException

—— In-memory logs end ——–
2015-07-xxT11:29:31.894+02:00 [04760 error ‘Default’] Section for VMware VirtualCenter, pid=1424, version=5.5.0, build=2442329, option=Release
–>

Jul 10

Meet NPX 002 – Lane Leverett

“VMTurbo"

  • Name: Lane Leverett
  • NPX Number: 002
  • Employer:  Nutanix
  • Blog URL: N/A
  • Twitter: @wolfbrthr
  • Virtualisation background: I’ve been doing virtualization solutions since 2006 and ESX 2.5.  Primarily focused around server virtualization and VDI solutions and designs with various VARs.
  • Storage Background: Storage has been focused primarily to support virtualization requirements with solutions like EMC, NetApp, HP, IBM, and Dell.  Both Fiber Channel and Ethernet based storage solutions.
  • Hyper Converged Infrastructure background:  I first started with Hyper Convergence with Nutanix back in 2011/2012 at a VAR to augment and support existing virtualized solutions.  I could really see the value, especially for VDI based solutions where traditional storage was rigid, inflexible, and costly to a solution that needed none of those things.
  • Future of HCI and other emerging technologies:  Hyper Converged Infrastructure is really just the stepping stone to creating a truly software defined business model that will include, multi hypervisors, on premise, and off premise workloads (i.e. private and public cloud), and containerized solutions to allow for maximum flexibility and scale of workload.  I think the area that will truly make this possible and cause the most disruption is with software defined networking based solutions.  This will be the underpinning glue which will allow for true mobility, scale, and security no matter where the workload is running.
  • Value of NPX:  The NPX certification help to prepare enterprise architects to start facing the next set of challenges coming to the datacenter and help ensure they are raising the bar for themselves to not be just a master in a single domain, but to demonstrate true cross domain skills in multi hypervisors, emerging technologies and trends, and hybrid cloud scenarios.
  • What made you go for NPX:  I always want to make sure that I continue to sharpen my skills and stay relevant to where the industry is heading.  I see a lot of change coming to the IT industry over the next several years and I want to be the one helping to set that direction and guide and mentor others who will follow.
  • Advice to people looking into the NPX track:  Make sure to come prepared and to closely follow the blueprint guide.  Remember that simplicity is key to your design and bigger does not always mean better or higher quality.  To quote Ernst F. Schumacher, “Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius — and a lot of courage to move in the opposite direction.”

Back to the NPX section

 

Older posts «