No SSH access after upgrade to vSphere 4.1

Similar Questions

• "No connection to the server of VR: does not not." after upgrade to vSphere 5.5

  As part of the upgrade to vSphere 5.1 to 5.5 along http://kb.vmware.com/kb/2057795 I've updated vSphere replication to 5.5.0.0 build 1309877. All rehearsals continued well then. I only add the new vCenter replication and it stopped for the old.

  After the migration of all VM including device just RV improved another 5.5 ESXi host I upgraded from original host and migrated the back of some VM. I noticed that only this VM is replicated again then. All other zeroes had "no connection to the server VR: does not not." and "Violation of RPO" messages (including RVS). If I migrate the original replication host virtual computer is restored. If I migrate to another connection from host to the server of VR is lost again - no matter what a host running VR.

  Any idea, please?

  Yes, it's possible, but I just wanted to rule out any more simple explanations first. I was worried especially when you said the VR server could not ping itself, but perhaps I misinterpreted what you were saying.

  In all cases, you can verify if this is your problem by looking for a line like this in the esx.conf of the hosts that you upgraded:

  / NET/vmkernelnic/Child [0001] / tags/4 = 'true '.

  If so, remove the line in the esx.conf and restart the host. Then, once the host is back, check that the network adapter assigned to the vmkernel is an accessible IP address.

  In my view, that the part "child [0001]" may be different on certain configurations if you do not find the exact line I've specified above, check around the lines part of [another] child.

• Slow IO performance after upgrade to vSphere 5

  Hi all

  I have a problem in our lab environment and I type some other brains in the community .

  First of all a brief overview:

  2 x Fujitsu RX300 S5 (FC HBA LP1150)

  1 x Fujitsu RX300 S6 (FC HBA LP1250)

  2 x Brocade 200E

  1 x Fujitsu Eternus DX90 (CF)

  1 x Fujtsu Siemens FibreCAT SX80 (CF)

  All devices are running with 4 G FC.

  Last week we updated our servers with the latest firmware (included HBA) and the latest vSphere 5 (updated 01 and the last patch-bundle). Everythings seems to run fine, after I've got svmotioned a few servers to get an empty data store. A few small servers (each. approximately 30 GB) need hours to get to the target data store. With CLI, I created a vmdk eagerzeroedthick to test the performance on our DX90. It took almost 10 minutes to create a 10 GB vmdk (about 17 MB / s; flow even showed DX90 performance monitor). I did the same on the FibreCAT and this storage is running normally with 170 MB per second.

  Now lets get things I did to track down the cause:

  1. I connected directly the first server with the DX90 (to avoid the fc switch)-> problem still there
     
  2. I went down the HBA firmware to version previos-> problem still there
     
  3. I installed the 4.1 vSphere update 02. I put only the investigation period and did test of 10 GB-> problem disappeared. for 10 GB, it took 39 seconds which is nearly 300 MB per second
     
  4. I installed (new installation) of the first version of vSphere 5-> surprise, the problem here is once again
     
  5. I installed ESXi 4.1 (I tested again and it took again 39 seconds for a 10 GB vmdk) and upgraded to vSphere 5-> problem is still there
     
  6. I tried all the way air, Fujitsu drivers customized for Emulex HBA and LUN parameters
     

  Writing performance monitor shows response time between 700 year 1400 ms and 17 MB per second with vSphere 5 to the DX90. With version 4, it is between 0 and 60 ms and nearly 300 MB per second. Only the SX80 works very well to any version (not support ALUA). Each unit works with the latest firmware.

  It is without doubt vSphere 5, what causes the problem. I can't find clues in newspapers or VMware KB.

  Does anyone have an idea or the same problem? If I can't find a solution in the coming days, I propose to prosecute.

  Thanks in advance

  Hi Martin,

  There is a similar discussion in a German community in vmware.

  The solution was simple, your table does not seem to support VAAI.

  If you follow the following article to disable VAAI.

  Turning off the feature in ESX/ESXi VAAI

  HtH,

  Ralf

• after upgrade to vsphere 5 - email does not send

  Hi all

  with vsphere 4 and ghettovcb, I had no problem in using the experimental feature of sending the mails after backup completion.

  Now after the upgrade to vsphere 5 and upgraded ghettovcb in the mail last version (esxi 5 incl. support), sent to the internal mail server lacks.

  Nothing else was changed.

  Error:

  2011-09-07 03:04:02 - info: = ghettoVCB JOURNAL END =.

  2011-09-07 03:05:17 - info: ERROR: can't send the log to 192.168.1.11:25 output to emailuser

  2011-09-07 03:05:18 - info: exit log by e-mail will not be erased and is stored in /tmp/ghettoVCB-email-474241.content

  Anything I could provide or check to fix this or help in any resolution?

  Can you check to see if the firewall is on, what's new with ESXi 5 and make sure that port 25 is open.

• HA problem after upgrade to vSphere 4.1

  Hello world...

  I have a problem with HA after the upgrade from ESX 3.5 to vSphere 4.1.

  HA no longer works.

  I got a lot of error messages like:

  HA agent has an error: cmd addnode failed for the main node: internal error of AAM - agent could not be started. : HA unknown error

  Cannot complete the HA configuration error

  By contacting the agent HA error timeout

  Can someone help me with this?

  Make sure that DNS resolves host names and vCenter each hosts and vCenter. I don't have a large number of guests so I use the host on all hosts and vCenter files to make sure whether or not they solve if DNS is running. Make sure that the names match Upper / Lower case. Once you are sure that name resolution and you can see each host and vCenter each try it involved removing the cluster hosts and machines by adding back again once.

• Location of the service after upgrade to vSphere Console

  In December, I improve VMWare VCenter and servers ESX, vSphere 4.0 3.5 u1. I then discover that my Service on hosts 3 Console, have changed rather than the local store, to a shared SAN store. I can find it, is the only workaround:

  de : http://www.VMware.com/support/vSphere4/doc/vsp_esx40_vc40_rel_notes.html

  If you choose a store of data shared for the service console, the installation or upgrade of software tool does not issue a warning

  For ESX 4.0, the service console must be installed on a VMFS datastore that resides on the local host drive or on a drive of SAN which is masked and zoned on that particular only host. This version does not support the installation of the service on a data store console that is shared between the hosts. When you install ESX 4.0 or upgrading to ESX 4.0, you must select a store location of VMFS data for the service console (esxconsole.vmdk). If you select a data store that is shared between the hosts, the installation tool or software upgrade does not issue a warning.

  Workaround: Do not install the service on a VMFS datastore console shared between hosts.

  Is there someone who can tell me, how to move the service console?

  Best regards

  Peter

  I do not think that it is possible to move the ESXConsole.

  Read this post http://communities.vmware.com/thread/214439

  The easiest way is to reinstall GUESTS concerned with access to SAN.

  In this way, that you don't have the ability to install ESXConsole on SAN disks.

  I googled and found this post that explains how to handle the ESXConsole, maby this will help you.

  http://getvirtical.blogspot.com/2009/11/making-cloned-boot-LUNs-boot-with-ESX4.html

  If you have found this device or any other answer useful please consider useful or correct buttons using attribute points.

  Concerning

  A. Mikkelsen

• PROBLEM AFTER UPGRADE TO VSPHERE 3.5u4

  HAI

  I WAS UPDATED SUCCESSFULLY ESX3.5U4 TO VSPHERE 4

  HAS} IMPROVED VMTOOLS

  B} UPGRADED THE VIRTUAL HARDWARE

  AFTER THAT I DON'T SEE THE IP ADDRESS IN THE SUMMARY OF THE VIRTUAL MACHINE.

  CONNECT SAYS INCREASE VIDEORAM

  I CAN'T INCREASE THE RAM AND MEMORY ON THE FLY THAT IS TO SAY WHEN THE VM IS POWERED BY SCREENSHOT OF FIXING IAM PLS ADVICE

  BUT the PERFORMANCE OF the virtual machine IS GREAT

  VAMSI

  HI -.

  To problem VC not related IP:

  Can you please check/usr/bin/vmware-user process runs on a virtual machine.

  Also can you please post vmware.log (this will be under the VM on the host folder) and vm - upgrader.log (you can find it under/tmp/vmware-root)

  -Alain J

• Legally no bought Lightroom - no access after upgradeing to the cloud

  I just upgraded my Photoshop and now I can't get in my legally purchased Lightroom (an older version I had on my machine) with ALL MY PRESETS there.  I paid for this legally and I want that my access restored.  How do I do that?  I don't want at this level, I'm fine with where I am.  I'm actually furious, I'm suddenly denited access to it.

  Hi Mikeh25189320,

  Please use the following link for Install Photoshop Lightroom

  See also, find the serial number of your product Adobe quickly

  Let us know if that helps.

• NFS problem after upgrade to vSphere, ESXi 5.0 5.1

  Hello community,
  I installed / updated on a Dell r.620 Server ESXi 5.0 5.1 vSphere
  I also have an ESXi installed 5.0 an another r.620 Dell both connected to a Snyology Racksation via NFS. (at different volumes)
  Now, I have the problem that I can't install an OS (Windows XP, Windows 8, Windows 7) located on an NFS share in a new created virtual machine.
  I am not connected without vCenter, just with the vSphere Client direct connected.
  The system boots, but I can not choose to install the operating system on the new created VMDK but then nothing happens.
  I also tried to format the drive before installation, formatting breaks down after 15 minutes with the message: "unable to format the drive...". 0 x 80070057 ".
  When the virtual machine is on the local storage of the VM to the server, everything works fine.
  I can also install and start virtual machines on the same NFS with an ESXi 5.0 share.
  Formerly installed VMs can also start. All hung on the windows logo screen and the German Embassy "Comuptereinstellungen werden übernommen"... for over an hour...
  The same virtual machines work fine on the ESXi 5.0, located on the same NFS share.
  But on the NFS share, I can write and read the data with the Client vSphere (on configuration-> storage) with no problems, so I guess that there is a problem with the NFS, permissions etc volume.
  So I guess there must be a problem with the NFS share on vSphere Host 5.1.

  Does anyone have an idea what is the problem?

  Thank you very much!

  No worries

• PowerCLI Script to add disk fails after upgrade to vSphere 5.5 U1 and PowerCLI 5.5 R2

  Hi all

  I created the following script to add a disk to a virtual machine mode multi-writer for Oracle RAC. This script used to work on vSphere 5.5 GA and GA 5.5 PowerCLI, but now no longer works with vSphere 5.5 U1 and PowerCLI 5.5 R2. I don't know exactly, what has changed, but I think it has something to do with SCSI controller specification objects, more specifically the controller key.

  SE connect-VIServer VC

  $vmname = Read-Host "VM name to add disks to.

  $vmdk = Read-Host 'drive to add (full path) '.

  $busnumber = Read-host "SCSI Bus number".

  $unitnumber = Read-Host "drive number '.

  [int64] $capacity = Read-Host "disk capacity (GB).

  $vm = get - VM $vmname

  [int64] $capcitykb = ($capacity * 1 GB) / 1 KB

  Write-Host "create new album"$vmdk"of size"$capacity"GB"$vm"SCSI ID"$busnumber":" $unitnumber

  Write-Host 'capacitΘ in Ko' $capcitykb

  $ctrll = get-controller SCSI - VM $vm |? {$_.extensiondata.busNumber - eq $busnumber}

  Write-Host 'Controller key' $ctrll.extensiondata.controllerkey

  $spec = new-Object VMware.Vim.VirtualMachineConfigSpec

  $spec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] (1)

  $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDeviceConfigSpec

  $spec.deviceChange [0] .operation = 'Add '.

  $spec.deviceChange [0] .fileOperation = "crΘer".

  $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDisk .device

  $spec.deviceChange [0].device.key = - 100

  $spec.deviceChange [0].device.backing = new-Object VMware.Vim.VirtualDiskFlatVer2BackingInfo

  $spec.deviceChange [0].device.backing.fileName = $vmdk

  $spec.deviceChange [0].device.backing.thinProvisioned = $false

  $spec.deviceChange [0].device.backing.split = $false

  $spec.deviceChange [0].device.backing.writeThrough = $false

  $spec.deviceChange [0].device.backing.eagerlyScrub = $true

  $spec.deviceChange [0].device.backing.diskMode = "independent_persistent".

  $spec.deviceChange [0].device.connectable = new-Object VMware.Vim.VirtualDeviceConnectInfo

  $spec.deviceChange [0].device.connectable.startConnected = $true

  $spec.deviceChange [0].device.connectable.allowGuestControl = $false

  $spec.deviceChange [0].device.connectable.connected = $true

  $spec.deviceChange [0].device.controllerKey = $ctrll.extensiondata.controllerkey

  $spec.deviceChange [0].device.unitNumber = $unitNumber

  $spec.deviceChange [0].device.capacityInKB = $capacitykb

  $spec.extraConfig = new-Object VMware.Vim.OptionValue [] (1)

  $spec.extraConfig [0] = new-Object VMware.Vim.OptionValue

  $spec.extraConfig [0] .key = 'scsi' + $busnumber + ': ' + $unitnumber + '.sharing.

  $spec.extraConfig [0] .value = 'multi-writer'

  $vm. ExtensionData.ReconfigVM ($spec)

  For some reason any $ctrll.key no longer returns any value and is completely absent, if I do a $ctrll | Get-Member to view the properties of the object.

  Any advice on how to get this script working would be greatly appreciated.

  Kind regards

  Michael

  Hi Luke,.

  Took a bit of debugging, but I finally got the script to work. Looks like that the values for $ctrll.key that I expected to be in the object disappeared definitively. In order to find the correct value, I now have to check $ctrll.extensiondata.key. Also, I needed to cast variables very carefully to the device specification. For the controllerKey it must be cast to int, like the unitNumber. Also found that the calculation for capacitykb should be cast to int64 and the 1 GB and 1 KB should be lowercase for a reason, otherwise the value is returned as a zero. So some weird things in 5.5 U1 which may seem spoiled API. Here is the final script as i've got working. It is not enough, there is no validation, police checks or anything either, but it works.

  SE connect-VIServer VC

  $vmname = Read-Host "VM name to add disks to.

  $vmdk = Read-Host 'drive to add (full path) '.

  [int] $busnumber = Read-host "SCSI Bus number number"

  [int] $unitnumber = Read-Host "drive number '.

  $capacity = Read-Host "(GB) disc.

  $vm = get - VM $vmname

  [int64] $capcitykb = ($capacity * 1 GB) / 1 KB

  Write-Host "create new album"$vmdk"of size"$capacity"GB"$vm"SCSI ID"$busnumber":" $unitnumber

  Write-Host 'Disk in KB capacity' $capcitykb

  $ctrll = get-controller SCSI - VM $vm |? {$_.extensiondata.busNumber - eq $busnumber}

  Write-Host "controller key" $ctrll.extensiondata.key "

  $spec = new-Object VMware.Vim.VirtualMachineConfigSpec

  $spec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] (1)

  $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDeviceConfigSpec

  $spec.deviceChange [0] .operation = 'Add '.

  $spec.deviceChange [0] .fileOperation = "crΘer".

  $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDisk .device

  $spec.deviceChange [0].device.key = - 100

  $spec.deviceChange [0].device.backing = new-Object VMware.Vim.VirtualDiskFlatVer2BackingInfo

  $spec.deviceChange [0].device.backing.fileName = "" + $vmdk ".

  $spec.deviceChange [0].device.backing.thinProvisioned = $false

  $spec.deviceChange [0].device.backing.split = $false

  $spec.deviceChange [0].device.backing.writeThrough = $false

  $spec.deviceChange [0].device.backing.eagerlyScrub = $true

  $spec.deviceChange [0].device.backing.diskMode = "independent_persistent".

  $spec.deviceChange [0].device.connectable = new-Object VMware.Vim.VirtualDeviceConnectInfo

  $spec.deviceChange [0].device.connectable.startConnected = $true

  $spec.deviceChange [0].device.connectable.allowGuestControl = $false

  $spec.deviceChange [0].device.connectable.connected = $true

  $spec.deviceChange [0].device.controllerKey = [int] $ctrll.extensiondata.key

  $spec.deviceChange [0].device.unitNumber = [int] $unitNumber

  $spec.deviceChange [0].device.capacityInKB = $capacitykb

  $spec.extraConfig = new-Object VMware.Vim.OptionValue [] (1)

  $spec.extraConfig [0] = new-Object VMware.Vim.OptionValue

  $spec.extraConfig [0] .key = 'scsi' + $busnumber + ': ' + $unitnumber + '.sharing.

  $spec.extraConfig [0] .value = 'multi-writer'

  $vm. ExtensionData.ReconfigVM ($spec)

  Now I just need to check if the script that I have which attaches to this disc to the other nodes works Oracle RAC.

• Performance issues after upgrade to view 5 on Windows 7

  I'm having a lot of performance problems after upgraded to vSphere 5 and 5 view connecting using PCoIP.  Interaction with the virtual machine are slower with either double or single monitor.  I tried all solutions different workaround proposed on the site of Teradici.  If someone has bugs or suggestions about how do to clear up things please answer.

  Add the following line in the vm config file.

  mks.poll.headlessRates = 1000 100 2

  It should solve your PCoIP lag problems, let me know what your results are.

• Host CPU is Incompatible - car Upgrade to vSPhere 4

  We have 4 ESX host with identical hardware and CPU (they were purchased at the same time). Since the upgrade to vSphere 4 I can't using vMotion to migrate specific VMS between hosts.

  I get the error in the attached photo.

  Anyone has any ideas, I'm a bit confused because the CPU is all identical, I have even doubled checked with "VMWare CPU Info".

  HI Marc P

  You are probably affected by this specific bug ESX(I) 4:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1011294

  "VMotion stops working after upgrade to vSphere 4.0 with a host processor is not compatible error"

• Lost access to the volume after upgrade 4.1

  Setup

  1 x HP c7000 blade box

  3 x HP BL460cG6 with dual Xeons 5540 and 48Gb of RAM, cards ISCSI HBA, QLogic

  3 x HP P4300 Lefthands

  4 x 3020 Cisco switches for blade in the back the c7000, 2 x dedicated to iSCSI traffic

  vSphere 4.1 Server

  The problem

  We went through the entire process of upgrading our server for vSphere 4.0 to 4.1 to manage a stand-alone ESXi 4.1 system, so our attentions turn to our 3 blades running ESXi 4.0u1 we used the built in Update Manager, downloaded the 4.0 to 4.1 upgrade file and we have improved our first blade and it did not notice problems as there put servers have was little used those.  We then upgraded the second and moved our main mail on her server.

  It was when we did that we started getting errors when people were losing connection to the exchange server, after some research we've seen of the event and we have been to see the error:

  "Lost access to the volume because of connectivity issues."  Recovery attempt is underway and the results will be available shortly"

  Then 10 seconds later we get the message:

  "Successfully restored access to the volume due to connectivity problems."

  This error only occurs on the blades of 4.1, we have restored a blade on 4.0 and errors are not displayed and no errors were reported with the servers on this blade.  As far as we can say it is not a network problem since all blades for iSCSI traffic flows on the same switches to the Lefthands, and we were losing the connection to volumes on the two Lefthands.

  We have a call connected with HP about this, but from the Yes, we cannot determine what is causing this problem and how to solve.

  So any help is greatly appricated

  Thank you

  Dave

  This is due to a combination of ESX(I) 4.1, QLogic and version Lefhand SAN/IQ 8.5 with the 10092-00 patch version. I did a blogpost on his problem:

  http://yuridejager.wordpress.com/2011/02/07/lost-access-to-volume-error-with-hp-lefthand-san-storage-after-upgrading-to-vmware-vsphere-41/. I hope this helps.

• Unable to access iBooks Store for iPad after upgrade to iOS 9.3.3.

  We do not seem to access my iPad iBooks store 2 Air or my wife Mini 4 iPad after upgrading iOS 9.3.3 machines. When you click on any of the icons store across the lower part of the application, we get a blank white page. We can access all our books purchased on the iCloud, but cannot look for first timers. The iBooks app seems to work normally on my iPhone 6 after the iOS upgrade. Anyone else has a similar problem?

  Yes. Double-click the home button on the iPad and the iBooks app sliding upwards and out of the screen to close.

  Click on the home button to return to the home screen, then hold home and power/sleep buttons for 10-15 seconds or until the Apple logo appears.

  Reset draw iPads. Let them restart and try opening the iBooks App again.

  No data should be lost by the present.

• Problems with HTTPS access site after upgrading to FireFox 30.0

  I have problems to access our HTTPS Corporate sites after upgrade to FireFox 30.0 of the Mavericks MAC or receive an error message "user not authorized" or the page does not load. I was able to access Web sites mentioned above when you use 29,0 FF. I have read and tried all the items on support to clear the cache and cookies, remove and reinstall the software, trying to change the SSL level & remove the cert8.db and cookie files in the profile.

  Internal just to validate that it was not a problem with our Web site, I tried and was able to access these sites via Safari for MAC Mavericks. I'm looking for what anyone help possible.

  Thank you
  Jim

  Many issues of the site can be caused by corrupted cookies or cache.

  • Clear the Cache

  Press < Alt > or < F10 > to display the toolbar.
  Followed;

  Windows; Tools > Options
  Linux; Edit > Preferences
  Mac; name of the application > Preferences

  Then Advanced > network > content caching Web: clear now

  and

  • Delete Cookies

  Press < Alt > or < F10 > to display the toolbar.
  Followed;

  Windows; Tools > Options
  Linux; Edit > Preferences
  Mac; name of the application > Preferences

  Then confidentiality.
  Under historical, select Firefox will use the custom settings.
  There is a button on the right side, called View the Cookies.

  If there is still a problem,
  Start Firefox in Safe Mode {web link}
  While you are in safe mode;
  Press < Alt > or < F10 > to display the toolbar.
  Followed;

  Windows; Tools > Options
  Linux; Edit > Preferences
  Mac; name of the application > Preferences

  Then Advanced > General.
  Find and stop using hardware acceleration.

  Dig safe web sites and see if there is still a problem. Then restart.