Pages Menu
TwitterRssFacebook
Categories Menu

Posted by on Aug 9, 2015 in Compute, Infrastructure | 0 comments

Failed to vMotion – What does VSAN have to do with it?

vMotion migration [167772244:1439137055175670] failed to read stream keepalive: Connection closed by remote host, possibly due to timeout
Migration to host <10.0.0.66> failed with error msg.vmk.status.VMK_MIG_CONN_CLOSED (195887167).
Migration [167772244:1439137055175670] failed to connect to remote host <10.0.0.84> from host <10.0.0.66>: Timeout.
vMotion migration [167772244:1439137055175670] failed to create a connection with remote host <10.0.0.84>: The ESX hosts failed to connect over the VMotion network
Failed waiting for data. Error 195887371. The ESX hosts failed to connect over the VMotion network.

Those have seen error 195887371 know it as the great MTU mistake where the MTU sizes don’t match up and vMotion fails to work properly.  However, what was interesting about this error message is it references my VSAN’s VMkernel network.  I flip over to the vCenter web interface and eye spy with my little eye that the VSAN VMkernel also is enabled as vMotion interface.  Well that can’t be! I admittedly don’t know why or how this happened but case closed, problem solved.

Rookie mistake? Probably, but it happens to the best of us.

Read More

Posted by on Mar 13, 2015 in Automation, Compute, DevOps, Infrastructure, Management, Networking, Security | 0 comments

Version Updates – What’s New?

code release

In a word…Everything!

Big release day for VMware engineering yesterday.  Great work guys!

 

VMware vSphere 6.0n (ESXi, vCenter)

6
12-Mar-15
VMware vRealize Operations for Horizon 6.x
6.1.0
12-Mar-15
VMware vRealize Automation 6.x
6.2.1
12-Mar-15
VMware vRealize Orchestrator 6.x
6.0.1
12-Mar-15
vRealize Business Advanced\Enterprise 8.x
8.2.1
12-Mar-15
vRealize Business Standard 6.x
6.1.0
12-Mar-15
vRealize Business Standard 6.x for vSphere
6.1
12-Mar-15
vRealize Code Stream 1.x
1.1.0
12-Mar-15
vRealize Infrastructure Navigator 5.x
5.8.4
12-Mar-15
vRealize Operations Manager 5.x
5.8.5
12-Mar-15
VMware vCloud Networking and Security
5.5.4
12-Mar-15
VMware vCenter Site Recovery Manager 6.x
6
12-Mar-15
VMware Virtual SAN 6.x
6
12-Mar-15
VMware vSphere Data Protection 6.x
6
12-Mar-15
VMware vSphere Replication 6.x
6
12-Mar-15
VMware Integrated Open Stack
1
12-Mar-15
VMware View 6.x
6.1
12-Mar-15
VMware Horizon Client for Windows 3.x
3.3
12-Mar-15
VMware Workspace Portal 2.x
2.1.1
12-Mar-15
VMware App Volumes 2.x
2.6
12-Mar-15
VMware vSphere PowerCLI 6.x
6
12-Mar-15
vRealize Orchestrator Active Directory plugin
2.0.0
12-Mar-15
vRealize Orchestrator vRealize Automation plugin
6.2.1
12-Mar-15

 

 

Thanks to Amy C for the compiled list!

Disclaimer

Read More

Posted by on Mar 8, 2015 in Compute, Infrastructure | 1 comment

vSphere 6 Upgrade Install Error NSX

vSphere6_NSX_Error

 

<CONFLICTING_VIBS ERROR: Vibs on the host are conflicting with vibs in metadata.  Remove the conflicting vibs or use Image Builder to create a customer ISO providing newer versions of the conflicting vibs.  [‘VMware_bootbank_esx-dvfiler-switch-security_5.5.0-0-0.2107100’, ‘VMware_bootbank_esx-vsip_5.5.0-0-0.2107100’, ‘VMware_bootbank_esx-vxlan_5.5.0-0-0.2107100’]>

I spent the day upgrading all my hosts to vSphere 6.0 from vSphere 5.5.  It felt right, it felt like it was time.  However, I must admit – I was not successful at first.  Did you check out the way wordy above? Yikes!

What I could make out from the upgrade error is there was something about the vSphere 6 upgrade that wasn’t jiving with NSX 6.1.2.  It appeared if I could “un-prep” this host then I could be on my way.  Fortunately, it is way easy to remove the VIBs that NSX installs during a host prep.

Once your host is back online, SSH to it and issue the following commands in bold:
~ # esxcli software vib remove -n esx-vxlan

Removal Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed:
VIBs Removed: VMware_bootbank_esx-vxlan_5.5.0-0.0.2107100
VIBs Skipped:
~ #
~ # esxcli software vib remove -n esx-dvfilter-switch-security
Removal Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed:
VIBs Removed: VMware_bootbank_esx-dvfilter-switch-security_5.5.0-0.0.2107100
VIBs Skipped:
~ # esxcli software vib remove -n esx-vsip
Removal Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed:
VIBs Removed: VMware_bootbank_esx-vsip_5.5.0-0.0.2107100
VIBs Skipped:

That’s it! Go ahead and start that the upgrade again!

PS I’m sure VMware will have better method of upgrading to vSphere 6 where NSX is installed.  However, us early adopters sometimes don’t get to ride on easy street.

Read More

Posted by on Nov 22, 2014 in Infrastructure | 0 comments

Stuck at the Loading module mptsas screen

mpt2sas

 

So you’re booting vSphere up and you’re stuck at the “Loading module mptsas”

Although this isn’t common, what do you do to get around it?

Here are some possible causes

1.  Bad hard drive

2. I/O controller hardware issue

3. I/O controller firmware issue

I faced this issue recently and sure enough, as soon as I took one of the hard drives out, vSphere booted up just fine!  I ran a health check scan on the drive and the puppy was sick!

Read More