JDMils_Interact's Posts

JDMils_Interact · ‎12-27-2018

I used the Add Host method from the client to add the host, and when added, vmk0 is on the standard switch.

JDMils_Interact · ‎12-26-2018

I rebuilt the host using the 6.0.0 6921384 ISO so it is now the same version as the upgraded hosts (which were upgraded from 5.5 to 6.0.0 6921384). All hosts had their main management IP as vmk0 ...

I rebuilt the host using the 6.0.0 6921384 ISO so it is now the same version as the upgraded hosts (which were upgraded from 5.5 to 6.0.0 6921384). All hosts had their main management IP as vmk0 which was on the distributed switch, and a secondary management IP vmk5 on the standard switch. I'm not sure how this was setup. When I setup HOST05, it automatically created a primary management IP vmk0 on the standard switch and I would like to move this to the distributed switch to match the other hosts, but I cannot figger out a way to do this. I tried removing the host from vCenter and re-adding it but that does not change the setup.

JDMils_Interact · ‎12-23-2018

So, it's been done already on the other hosts, I just have no info on how to do it- I guess I'll have to log a support call for this?

JDMils_Interact · ‎12-20-2018

Thanks Hassan, I tried those steps and still get the same error: A change in the network configuration disconnected the host 'MyvCenterServer.mydomain.local' from vCenter Server. The change ha...

Thanks Hassan, I tried those steps and still get the same error: A change in the network configuration disconnected the host 'MyvCenterServer.mydomain.local' from vCenter Server. The change has been rolled back. When I added the host to the cluster, I added it with the IP address assigned to vmk0, so that is now the main IP for this host as vCenter sees it so I assume this is why the error occurs. I tried to add the host using the secondary IP (vmk5) but there is no DNS for that IP and I verified this with the other hosts in the same cluster.

JDMils_Interact · ‎12-19-2018

The physical switches do have the VLAN as this host was working OK before it was upgrade from 5.5 to 6.0. The VLAN is VLAN036 on the standard switch and is called MY_VLAN36 on the DV switch- bot...

The physical switches do have the VLAN as this host was working OK before it was upgrade from 5.5 to 6.0. The VLAN is VLAN036 on the standard switch and is called MY_VLAN36 on the DV switch- both have the same VLAN designation. The other three hosts all have vmk0 on the dv switch.

JDMils_Interact · ‎12-19-2018

I just migrated 4 hosts from 5.5 to 6.0U3 and three worked fine, the last one HOST05, upgraded but I lost the network connections. I thus re-installed the V6.0U3 OS from an ISO and am in the midd...

I just migrated 4 hosts from 5.5 to 6.0U3 and three worked fine, the last one HOST05, upgraded but I lost the network connections. I thus re-installed the V6.0U3 OS from an ISO and am in the middle of setting it back up for the cluster and found the following, strange setup: All existing hosts have the vmk0, the Management kernel on VLAN036, on the DV switch. They have a secondary management IP allocated as vmk2 on VLAN037 on the standard switch. My new host HOST05 has the vmk0 (VLAN036) on the local switch and the vmk5 (secondary Management IP) on VLAN037 on the same standard switch. My question is, how do I move vmk0 from the standard switch to the DV switch? I tried to migrate vmk0 from the standard switch to the DV switch using: - Select DV switch. - Manage Virtual Adapters. - Add. - Migrate existing virtual adapters. - Select "Management Network" (which is vmk0), change destination port group to port group with VLAN036 on DV switch. - Finish Error: Call "HostNetworkSystem.UpdateNetworkConfig" for object "networkSystem-973651" on vCenter Server "MyvCenterServer.mydomain.local" failed. Network configuration change disconnected the host 'HOST05.mydomain.local' from vCenter server and has been rolled back. A change in the network configuration disconnected the host 'HOST05.mydomain.local' from vCenter Server. The change has been rolled back. I tried the same from the web client with the same result. So it looks like it won't migrate the vm kernel due to the loss of comms between the vCenter server and host. So how do I do this? I tried launching the thick client and attaching directly to the host and using the above method, but when it comes to choosing the destination port group to attach the vmk0 kernel to, I get nothing in the drop-down.

JDMils_Interact · ‎11-21-2018

I have the following site setup: vCenter Server: Ver: 5.5.0, build 2646482 Hosts: VMware ESXi, 5.5.0, 3029944 SRM: Ver: 2991419, Build 5.8.1 I was asked to look into an issue where...

I have the following site setup: vCenter Server: Ver: 5.5.0, build 2646482 Hosts: VMware ESXi, 5.5.0, 3029944 SRM: Ver: 2991419, Build 5.8.1 I was asked to look into an issue where a Protection Group (PG) was showing an unconfigured virtual server so I investigated and could not enumerate the virtual servers of the PG. I clicked on: Site Recovery\Protection Groups - highlight the PG with the 6 configured servers and one unconfigured server - click on the Virtual Machines button and I get "This list is empty" ????? I even created a new PG and added 3 servers and when I try to view the servers in the PG I get the same thing. If I right-click any PG then the only option available to me is "+ Add Permission" and the others are greyed out. I'm signed in as the SSO administrator with FULL permissions.

JDMils_Interact · ‎11-13-2018

So, I fixed the issue. Not only does the installer need access to both the host management network but so too does the newly created vCenter server, so I created a new VMKernel port group on the ...

So, I fixed the issue. Not only does the installer need access to both the host management network but so too does the newly created vCenter server, so I created a new VMKernel port group on the standard switch, and configured the VMKernel port group for management traffic and gave it an IP on the same subnet as the vCenter server. In essence, this creates a new entry point to the host and bridges the vCenter server network to the host's management network! I completed the upgrade with this change! Thanks all for your help.

JDMils_Interact · ‎11-13-2018

Oh, and I tried the upgrade about 4 times so far and the exact same thing happens each time. :smileyconfused: I logged into the console of the new appliance and this is what I see: So I...

Oh, and I tried the upgrade about 4 times so far and the exact same thing happens each time. :smileyconfused: I logged into the console of the new appliance and this is what I see: So I logged into the new vCenter server console and opened the "/var/log/vmware/upgrade/upgrade-requirements.log and found the following: So, it seems that the new appliance cannot contact the host? I tried to ping the host by IP and it did not resolve so I may be able to fix.....

JDMils_Interact · ‎11-13-2018

I DID set DRS to manual, but I have not tried another host! I also noticed that when I signed into the vCenter admin console (port 5480) that there was an update so maybe one of these will fix th...

I DID set DRS to manual, but I have not tried another host! I also noticed that when I signed into the vCenter admin console (port 5480) that there was an update so maybe one of these will fix the issue? I'll give it a go, thanks!

JDMils_Interact · ‎11-13-2018

I am running the vcsa-setup.html off the DVD "VMware-VCSA-all-6.0.0-8874690.iso" and after entering all the required details, the process kicks off and creates the new vCenter server, powers it o...

I am running the vcsa-setup.html off the DVD "VMware-VCSA-all-6.0.0-8874690.iso" and after entering all the required details, the process kicks off and creates the new vCenter server, powers it on but then stops at "Configuring the machine" which is at the point where it starts to install the various applications required for vCenter. I then check the Tasks on the newly created appliance and I can see the error: Discover virtual appliance NewvCenterApplianceName VMware vSphere Update Manager had an unknown error. Check the events and log files for details. com.vmware.vcIntegrity MyParentvCenterServerName.local The following events keep popping up in the Events view of the newly created vCenter server: Guest operation Initiate File Transfer From Guest performed. info 11/13/2018 10:46:56 PM NewvCenterApplianceName root This is where the upgrade sits and from what I can see it will sit here for ever: I can putty to the new appliance but there does not seem to be much there to check. I had VMware support have a look and they said there are no logs they can check until the upgrade process errors-out. They suggested I create a new vCenter server at the new patch level which is ridiculous since all the hosts are on a distributed switch and I would have to power off the old vCenter server, power on the new one then add all the hosts to it. And during this time I would assume the virtuals on the hosts would lose network connectivity? Putty session to the newly created vCenter appliance: The original vCenter is Version: 5.5.0.30500 Build 4180648. Can anyone suggest which logs I should check to see what the problem is? Message was edited by: Julian Milano

JDMils_Interact · ‎11-08-2018

Thanks Joerg, I setup a new NIC on the SRM servers connected to the vCenter servers I'm upgrading, assigned the VMware-VLAN of the hosts and it worked!

JDMils_Interact · ‎11-07-2018

I work in an environment where we have many vCenter servers, isolated by customer, so each customer has a dedicated IP range for its virtual servers. These virtual servers are accessible by a jum...

I work in an environment where we have many vCenter servers, isolated by customer, so each customer has a dedicated IP range for its virtual servers. These virtual servers are accessible by a jumpbox called CustomerJumpBox01. I cannot ping the ESXi hosts for which the vCenter servers are hosted on from here, but I can ping the vCenter servers. The actual vCentre servers, one for each customer, is on another VLAN, which is accessible by another jumpbox called SharedJumpBox01. I can also access the hosts on which the customers' vCenter servers run on, from this jumpbox. I cannot ping the vCenter servers from this jumpbox. So, if I need to access one of my customers' many virtual servers, I would go thru CustomerJumpBox01. If I need to access the vCenter server object for a particular customer, I would go thru SharedJumBox01. Tonight I tried to upgrade one of our customer's vCenter servers from 5.0.0 to 6.0.0 so I attached the ISO "VMware-VCSA-all-6.0.0-8874690.iso" to jumpbox SharedJumpBox01 and ran the file "vcsa-setup.html" but I got the error "Unable to connect to vCenter Server". I tried the same thing from SharedJumpBox01 and got the error "Unable to connect to target ESXi host or vCenter server". So it looks like the problem I'm experiencing is that I need to run the upgrade on a server which has access to BOTH the ESXi host on which the vCenter server is located, the vCenter Server itself. Can someone confirm this for me please? What are the required ports for the upgrade? 443?

JDMils_Interact · ‎10-26-2018

I'm not sure what's happened, but I may have had power issues and I think my vCenter VCSA server has corrupted drive(s). This website shows exactly what happened to me and after implementing the ...

I'm not sure what's happened, but I may have had power issues and I think my vCenter VCSA server has corrupted drive(s). This website shows exactly what happened to me and after implementing the suggestions, the vCenter server now boots to the logon prompt. When I log in using the root credentials, I get this: [ERROR] Failed to connect to service. Use service-control command to manage applmgmt service. ... ... ... I have tried the suggestions on this website https://tsmith.co/2016/vcsa-wont-boot-fsck-failed/ and it still does not boot. Here is a screenshot of my VCSA: What can I do to fix this?

JDMils_Interact · ‎10-22-2018

this obviously wouldn't apply to a real cluster due to whole unpartitioned devices having to be available for vSAN use and the fact that real physical devices can't be expanded. I'm interested...

this obviously wouldn't apply to a real cluster due to whole unpartitioned devices having to be available for vSAN use and the fact that real physical devices can't be expanded. I'm interested in this quote! What's the difference between a "real" cluster and a nested cluster? I would have thought they be the same thing as, how would the hosts in a nested environment know they are virtual just like the virtual Windows & Linux machines which we normally run on VMware? With my previous-work environment, we only used fibre connected LUNs from an EMC SAN and the LUNs can easily be expanded and then in VMware we were able to expand the datastore using the underlying free space, but in my new job, they have vSAN in some clusters and I am trying to get up-to-speed with the setup via my home lab.

JDMils_Interact · ‎10-22-2018

Hi, You guys are right, I'm running a test environment at home on my Brix GB-Bri5H-8250. I've setup 3 nested hosts and it's not the fastest infrastructure base, but with 32GB RAM & 1TB HDD, it...

Hi, You guys are right, I'm running a test environment at home on my Brix GB-Bri5H-8250. I've setup 3 nested hosts and it's not the fastest infrastructure base, but with 32GB RAM & 1TB HDD, it's an economical test bed. All hosts are out of maintenance mode and working OK. Thanks for the help, I will evacuate the disks from the vSAN cluster one-at-a-time and re-add them back in. I thus assume that the individual disks from each host are treated like RAIDed storage and when one is removed, the others take the load. I've noticed that when I put one of the hosts in maintenance mode that it takes FOREVER, and I can see a lot of disk activity on the vSAN datastore and this is what must be happening there. Thanks again.

JDMils_Interact · ‎10-22-2018

I have three hosts and they are setup as below. My vSAN datastore is showing 10GB free so I increased the size of the LUNs presented to the hosts and am hoping that the vSAN datastore increases a...

I have three hosts and they are setup as below. My vSAN datastore is showing 10GB free so I increased the size of the LUNs presented to the hosts and am hoping that the vSAN datastore increases as well, but it hasn't so far and I cannot figger out why not? Host01 (VMware ESXi, 6.5.0, 9298722) -- mpx.vmhba1:C0:T0:L0,disk,10.00 GB,HDD (Boot disk) -- mpx.vmhba1:C0:T3:L0,disk,40.00 GB,Attached,HDD (was 20GB and I increased it to 40GB) -- mpx.vmhba1:C0:T2:L0,disk,20.00 GB,Attached,HDD -- mpx.vmhba1:C0:T1:L0,disk,5.00 GB,Attached,Flash (cache disk) Host02 (VMware ESXi, 6.5.0, 9298722) -- mpx.vmhba1:C0:T0:L0,disk,10.00 GB,HDD (Boot disk) -- mpx.vmhba1:C0:T3:L0,disk,40.00 GB,Attached,HDD (was 20GB and I increased it to 40GB) -- mpx.vmhba1:C0:T2:L0,disk,20.00 GB,Attached,HDD -- mpx.vmhba1:C0:T1:L0,disk,5.00 GB,Attached,Flash (cache disk) Host03 (VMware ESXi, 6.5.0, 9298722) -- mpx.vmhba1:C0:T0:L0,disk,10.00 GB,HDD (Boot disk) -- mpx.vmhba1:C0:T3:L0,disk,40.00 GB,Attached,HDD (was 20GB and I increased it to 40GB) -- mpx.vmhba1:C0:T2:L0,disk,20.00 GB,Attached,HDD -- mpx.vmhba1:C0:T1:L0,disk,5.00 GB,Attached,Flash (cache disk) vSAN Disk Management shows the disks and the correct sizing: Disk Model/Serial Number,Disk Tier,Total Capacity,vSAN Health Status,Disk Distribution/Host "VMware Virtual disk , 5.00 GB disks",Cache,15.00 GB,Healthy,1 disk on 3 hosts Local VMware Disk (mpx.vmhba0:C0:T1:L0),Cache,5.00 GB,Healthy,Host03 Local VMware Disk (mpx.vmhba0:C0:T1:L0),Cache,5.00 GB,Healthy,Host02 Local VMware Disk (mpx.vmhba1:C0:T1:L0),Cache,5.00 GB,Healthy,Host01 "VMware Virtual disk , 40.00 GB disks",Capacity,120.00 GB,Healthy,1 disk on 3 hosts Local VMware Disk (mpx.vmhba0:C0:T3:L0),Capacity,40.00 GB,Healthy,Host03 Local VMware Disk (mpx.vmhba0:C0:T3:L0),Capacity,40.00 GB,Healthy,Host02 Local VMware Disk (mpx.vmhba1:C0:T3:L0),Capacity,40.00 GB,Healthy,Host01 "VMware Virtual disk , 20.00 GB disks",Capacity,60.00 GB,Healthy,1 disk on 3 hosts Local VMware Disk (mpx.vmhba0:C0:T2:L0),Capacity,20.00 GB,Healthy,Host03 Local VMware Disk (mpx.vmhba0:C0:T2:L0),Capacity,20.00 GB,Healthy,Host02 Local VMware Disk (mpx.vmhba1:C0:T2:L0),Capacity,20.00 GB,Healthy,Host01 However the vSAN disk capacity has not changed: Capacity: 82.45GB Used: 66.41GB Free: 16.04GB If I understand correctly, my vSAN datstore should have the sum of all local disks on all hosts which should now equate to 15GB + 120GB + 60GB = 195GB? How do I get the rest of the disk space to show in the vSAN?

All

JDMils_Interact's Posts

Re: Migrate vmk0 from stamdard switch to distributed switch

Re: Migrate vmk0 from stamdard switch to distributed switch

Re: Migrate vmk0 from stamdard switch to distributed switch

Re: Migrate vmk0 from stamdard switch to distributed switch

Re: Migrate vmk0 from stamdard switch to distributed switch

Migrate vmk0 from stamdard switch to distributed switch

SRM- strange behaviour with SRM site- cannot see virtual machines in Protection Group

Re: Cannot upgrade V5.5.0 vCentre appliance to V6.0.0

Re: Cannot upgrade V5.5.0 vCentre appliance to V6.0.0

Re: Cannot upgrade V5.5.0 vCentre appliance to V6.0.0

Cannot upgrade V5.5.0 vCentre appliance to V6.0.0

Re: Upgrading vSphere 5.5.0 appliance to V6.0.0 u3 - does the upgrade need access to both ESXi host and vCenter server?

Upgrading vSphere 5.5.0 appliance to V6.0.0 u3 - does the upgrade need access to both ESXi host and vCenter server?

vCenter server is dead- Emergency Mode

Re: Expand vSAN datastore

Re: Expand vSAN datastore

Expand vSAN datastore