Warnings of redundancy of the path in VMware

Similar Questions

• PpsPermission cannot open the path

  I have a problem when my application tries to access to the phone.

  The app show this debug info:

  [UI] {W} [10:20:09.463 06/05/15] [22128 KB] PpsPermission cannot open the path: "/ pps/services/phone/private/calls/.all?delta".
  [UI] {W} [10:20:09.490 06/05/15] [22144 KB] PpsPermission cannot open the path: "/ pps/services/phone/protected/calls/.all?delta".
  [UI] {W} [10:20:09.601 06/05/15] [22144 KB] PpsPermission cannot open the path: "/ pps/services/phone/public/calls/.all?delta".
  [UI] {D} [10:20:09.623 06/05/15] [22128 KB] failed to open object pps phone
  [UI] {W} [10:20:09.643 06/05/15] [22144 KB] PpsControl cannot open the path: / pps/services/phone/private/control
  [UI] {W} [10:20:09.660 06/05/15] [22128 KB] PpsControl cannot open the path: / pps/services/phone/protected/control
  [UI] {W} [10:20:09.679 06/05/15] [22128 KB] PpsControl cannot open the path: / pps/services/phone/public/control
  [UI] {W} [10:20:09.698 06/05/15] [22128 KB] PpsControl cannot open the path: / pps/services/phone/private/control
  [UI] {W} [10:20:09.716 06/05/15] [22128 KB] PpsControl cannot open the path: / pps/services/phone/protected/control
  [UI] {W} [10:20:09.735 06/05/15] [22128 KB] PpsControl cannot open the path: / pps/services/phone/public/control
  [UI] {W} [10:20:09.948 06/05/15] [24080 KB] PpsPermission cannot open the path: "/ pps/services/phone/private/calls/.all?delta".
  [UI] {W} [10:20:10.069 06/05/15] [24080 KB] PpsPermission cannot open the path: "/ pps/services/phone/protected/calls/.all?delta".
  [UI] {W} [10:20:10.094 06/05/15] [24080 KB] PpsPermission cannot open the path: "/ pps/services/phone/public/calls/.all?delta".
  [UI] {D} [10:20:10.122 06/05/15] [24080 KB] failed to open object pps phone
  [UI] {W} [10:20:10.146 06/05/15] [24080 KB] PpsControl cannot open the path: / pps/services/phone/private/control
  [UI] {W} [10:20:10.170 06/05/15] [24080 KB] PpsControl cannot open the path: / pps/services/phone/protected/control
  [UI] {W} [10:20:10.198 06/05/15] [24080 KB] PpsControl cannot open the path: / pps/services/phone/public/control
  [UI] {W} [10:20:10.225 06/05/15] [24080 KB] PpsControl cannot open the path: / pps/services/phone/private/control
  [UI] {W} [10:20:10.339 06/05/15] [24080 KB] PpsControl cannot open the path: / pps/services/phone/protected/control
  [UI] {W} [10:20:10.371 06/05/15] [24080 KB] PpsControl cannot open the path: / pps/services/phone/public/control

  Someone had this problem?

  ignore the warnings, it's just the usual journal spam

• Can't mount NFS share - operation failed, diagnostics report: failed to get the path console for volume

  I'm trying to mount a NFS on ESXI 6 volume, but continue to operate in the error.  Googling everything nothing helped, so I'm here. Error:

  Call "HostDatastoreSystem.CreateNasDatastore" of object "ha-datastoresystem" on ESXi '192.168.xx.xx' failed.

  Operation failed, the diagnostic report: failed to get the path of the console for the volume, the name of the sample.

  The NFS share is located on a synology nas. I checked the permissions and configuration. Everything seems correct based on the various boards and KB articles.

  Ideas?

  Thank you.

  Find the esx.conf file in/etc/vmware.

  If you could also share a copy with me...

  Try to mount the NFS VMware KB: Volume fails with the error: could not resolve the host name

  Check the link as well below.

  http://www.Bussink.ch/?p=1640

• The term 'Select-Object-property' is not recognized as a cmdlet, function, script file or executable program. Check the spelling of the name, or if a path has been included, make sure the path is correct, and then try again.

  I have a fairly new version of PowerCLI (5,5 Rel 1) 5.5 being ESXi and vCenter.

  I also checked that automation. Core is installed:

  PowerCLI C:\Windows\system32 > Get-PSSnapin VMware.VimAutomation.Core

  Name: VMware.VimAutomation.Core

  PSVersion: 2.0

  Description: This Windows PowerShell snap-in contains the Windows PowerShell cmdlet

  TS of vSphere management.

  but after connecting to vCenter, I get error trying to run:

  PowerCLI C:\Windows\system32 > $Results = ForEach ($DRSRule to $DRSRules)

  > > {}

  > > «|» Select-Object-Property @{N = 'Cluster'; E = {(Id-vue-Get $DRSRule.Clust)}

  amplifier. {{ID). name}}.

  > > @{N = "Name"; {E = {$DRSRule.Name}}.

  > > @{N = "enabled"; {E = {$DRSRule.Enabled}}.

  > > @{N = 'Type of DRS'; {E = {$DRSRule.KeepTogether}}.

  > > @{N = "MV"; E = {$VMIds = $DRSRule.VMIds - split ","}

  > > $VMs = ForEach ($VMId to $VMIds)

  > > {}

  > > (Get-View-Id $VMId). Name

  {> >}

  {{> > $VMs - join ","}}

  {> >}

  > >

  The term 'Select-Object-property' is not recognized as a cmdlet, fu

  function, script file or executable program. Check the spelling of the name, or if

  a path was included, make sure the path is correct and try again.

  On line: 3 char: 32

  +     "" | Select-Object-Property < < < < @{N = 'Cluster'; E = {(Get-view-Id $DRSRule

  . {{Cluster.Id). name}}.

  + CategoryInfo: ObjectNotFound: (Select-Object-property string :)

  [], CommandNotFoundException

  + FullyQualifiedErrorId: CommandNotFoundException

  PowerCLI C:\Windows\system32 > Add-PSSnapin VMware.VimAutomation.Core

  Is ' Select-Object-Property not installed?  If not, where I get it, please?

  see you soon

  KC

  Note, I received this Dean here code: PowerCLI: extraction rules DRS; Deans blog

  There should be a space between the - Property parameter and Select-Object

• How do you get the path of the data store or the URL of a virtual disk in vRealize Orchestrator?

  I need to eager zero a virtual disk while building a virtual machine. I found the eagerZeroVirtualDisk_Task() under VcVirtualDiskManager function, which takes in 2 parameters:

  name - (String) the name of the disk, is a path to the data store or a URL pointing to the virtual disk that needs to be inflated.

  Data Center - (VcDatacenter) if the name is a path of data store, the data center for the path of the data store. Not necessary when called directly on ESX. If not specified on a call to VirtualCenter, the name must be a URL.

  How can I get the correct path of data store given the virtual disk? I intend to iterate through the features of the virtual machine to get the disks.

  Thank you!

  Actually figured out how to get the path of the data store, and how a drive zeros. In case it is useful to share the code here:

  var vimHost = vm.vimHost; VM instanceof VCVirtualMachine

  var vDiskMgr = vimHost.virtualDiskManager;

  for each disk

  var features = vm.config.hardware.device;

  for each {(dev var in devices)

  dev.backing contains a lot of useful things...

  If (dev instanceof VcVirtualDisk) {}

  a disc!

  var dsPath = dev.backing.fileName;

  System.log ("path of disk:" + dsPath);

  Data var Center =

  System.getModule('com.vmware.library.vc.datastore').getDatacenterForDatastore (dev.backing.datastore);

  var vcTask = vDiskMgr.eagerZeroVirtualDisk_Task (dsPath, datacenter);

  wait

  var waitResult =

  System.getModule('com.vmware.library.vc.basic').vim3WaitTaskEnd (vcTask, true, 5);

  }

  }

• Hot Add Remove lun fails in rescan periodical at the time of the withdrawal, although the path is marked as DEAD as planned

  So we run the hot add and remove cases from LUNs in the certification for ESX 5.5 with Workbench 3.0 kit

  The hot add succeeds to the two manual add and periodic scan... Deletion succeeds manual extraction, but a failure in periodicals rescan same removal so it lists the path out of SERVICE.

  Here are the logs

  [August 26, 2014 20:01:29: WLMANAGER] [0] FRAME: no charges Found.

  [August 26, 2014 20:02:25: HOTADDREMO] [0] INFO: hot test add using RESCAN

  [August 26, 2014 20:07:55: HOTADDREMO] [0] INFO: performance of rescan the first server

  [August 26, 2014 20:08:28: HOTADDREMO] [0] INFO: found new LUN eui. 48d8bf5f64e64100

  [August 26, 2014 20:08:28: HOTADDREMO] [0] INFO: add hot with the new analysis is the first server

  [August 26, 2014 20:08:28: HOTADDREMO] [0] INFO: Running rescan the second server

  [August 26, 2014 20:09: HOTADDREMO] [0] INFO: found new LUN eui. 48d8bf5f64e64100

  [August 26, 2014 20:09: HOTADDREMO] [0] INFO: add hot with rescan is the second server

  [August 26, 2014 20:09: HOTADDREMO] [0] INFO: hot test add using PERIODICALLY RESCAN

  [August 26, 2014 20:15:05: HOTADDREMO] [0] INFO: Test runs on the first server

  [August 26, 2014 20:15:06: HOTADDREMO] [0] INFO: found new LUN eui.48d8bf5f64e64200

  [August 26, 2014 20:15:06: HOTADDREMO] [0] INFO: add hot with the new analysis from time to time, is the first server

  [August 26, 2014 20:15:06: HOTADDREMO] [0] INFO: Test runs on the secondary server

  [August 26, 2014 20:15:08: HOTADDREMO] [0] INFO: found new LUN eui.48d8bf5f64e64200

  [August 26, 2014 20:15:08: HOTADDREMO] [0] INFO: add hot with periodically rescan is the second server

  [August 26, 2014 20:15:10: WLMANAGER] [0] FRAME: no charges Found.

  [August 26, 2014 20:16:07: HOTADDREMO] [0] INFO: hot control remove using RESCAN

  [August 26, 2014 20:17:27: HOTADDREMO] [0] INFO: hot execution removes the test on the first server

  [August 26, 2014 20:18: HOTADDREMO] [0] INFO: LUNS deleted eui.48d8bf5f64e64200

  [August 26, 2014 20:18: HOTADDREMO] [0] INFO: Test successfully on the first server

  [August 26, 2014 20:18: HOTADDREMO] [0] INFO: hot execution removes the test on the second server

  [August 26, 2014 20:18:33: HOTADDREMO] [0] INFO: LUNS deleted eui.48d8bf5f64e64200

  [August 26, 2014 20:18:33: HOTADDREMO] [0] INFO: Test passed on the second server

  [August 26, 2014 20:18:33: HOTADDREMO] [0] INFO: hot control remove by using PERIODICALLY RESCAN

  [August 26, 2014 20:23:20: HOTADDREMO] [0] INFO: Test runs on the first server

  [August 26, 2014 20:23:21: HOTADDREMO] [0] INFO: check the path to removed LUN on the first server

  [August 26, 2014 20:24:17: TRANSPORT] [0] FRAMEWORK: running cmd 'esxcfg-mpath - bd eui.48d8bf5f64e64100' mode of blocking on the host 'esxia.amiads.com '...

  [August 26, 2014 20:24:17: STAFBASE] [0] FRAMEWORK: command execution STAF: staf esxia.amiads.com PROCESS SAMECONSOLE RETURNSTDOUT RETURNSTDERR WORKDIR SHELL START / WAIT COMMAND esxcfg-mpath - bd eui.48d8bf5f64e64100

  [August 26, 2014 20:24:18: STAFPROCES] [0] FRAME: host esxia.amiads.com returned eui. 48d8bf5f64e64100 : * iSCSI disk (eui.48d8bf5f64e64100)

  vmhba34:C0:T65:l0 LUN:0 State: dead iscsi adapter: not available target: unavailable

  vmhba34:C3:T65:l0 LUN:0 State: dead iscsi adapter: not available target: unavailable

  
  

  [August 26, 2014 20:24:27: HOTADDREMO] [0] ERROR: LUN is found not deleted after periodic rescan on the first server

  
  

  So I checked the Vmware perl code that performs this case... it is available at /opt/vmware/VTAF/storage50-cert/VTAF/Test/Storage/StorageCert/FVT/HotAddRemoveLUNs.pm

  
  

  Sub RunHotRemoveTest

  {

  .....

  # Remove LUN only cause death I/O path.  It does not delete the LUN.

  # Evaluate for the dead I/O path.

  $deadPathFound = "NO";

  LogInfo (channel = > $channel, MSG = > "Check the path to remove LUN on $server");

  foreach my {$lun (@lunListBeforePeriodicallyRescan)

  #my $lunObj = $host2HbaObj-> CreateScsiLun (name = > $lun);

  $cmd = "esxcfg-mpath - bd $lun";

  My $cmdObj = new VTAF::Framework:Core:Common:Command)

  Home = > $host2Obj-> GetName();

  Cmd = > $cmd);

  my $rc = $cmdObj-> GetReturnCode();

  my $cmdResult = $cmdObj-> GetStdout();

  my $cmdError = $cmdObj-> GetStderr();

  If ($cmdError) {}

  $deadPathFound = "YES";

  LogInfo (channel = > $channel, MSG = > "mpath command returned: $cmdError");

  LogInfo (channel = > $channel, MSG = > "$lun is deleted after periodic rescan");

  }

  }

  If ($deadPathFound not 'YES') {}

  LogError (channel = > $channel, MSG = > "LUN is not deleted after periodic rescan on the $server");

  return FAILURE;

  } else {}

  LogInfo (channel = > $channel, MSG = > ' delete hot with periodically rescan PASSED on the $server ");

  }

  }

  So if you see the code above, Vmware itself expected the path to show the death, but they perceive three error codes for the output of esxcfg-mpath - bd < lunname >

  I think they expect an error to return to $cmdError... But looks at though it lists the path as DEAD, she returns to success... So the $deadPathFound is always set to no. He goes into the path of "not YES" and not the test case...

  I would like to open a folder from supported with VMware, but before that I would like to know if someone has faced this problem and had this problem of VMware using any patch in their Workbench... Or if any new workbench has this problem fixed...

  We are using Vmware Test Manager: 3.0.0 - 1610638

  5.5 storage certification: 3.0.0 - 1337995

  VMware Workbench say 3.0.1

  Than I went back to our older certification with ESX 5.1 where this matter has passed... and was able to check the logs. It has been performed with Workbench 2.0. In this they executed a more order "peripheral storage esxcli list d lunname" and lists the path as dead and also properly detects the dead path and scored the try with the... Unfortunately I don't seem to have their old code to compare with...

  [July 27, 2012 12:34:06: SCSILUN] [0] FRAMEWORK: check if the 'eui.93bb4a37348e4100' lun is available or not.

  [July 27, 2012 12:34:06: TRANSPORT] [0] FRAMEWORK: running cmd ' esxcli storage device base list d eui.93bb4a37348e4100 ' mode of blocking on the host 'esxia.amiads.com '...

  [July 27, 2012 12:34:06: STAFBASE] [0] FRAMEWORK: command execution STAF: staf esxia.amiads.com PROCESS SAMECONSOLE RETURNSTDOUT RETURNSTDERR WORKDIR SHELL START / WAIT COMMAND esxcli storage base device list d eui.93bb4a37348e4100

  [July 27, 2012 12:34:07: STAFPROCES] [0] FRAME: host esxia.amiads.com returned eui.93bb4a37348e4100

  Full name: * iSCSI disk (eui.93bb4a37348e4100)

  Definable display name: true

  Size: 2048

  Device type: Direct access

  Multichannel plugin: NMP

  Devfs Path: /vmfs/devices/disks/eui.93bb4a37348e4100

  Seller: * I

  Model: *.

  Review: 2 0 s

  SCSI level: 4

  Is nickname: false

  Status: dead

  RDM Capable is: true

  Is Local: false

  Is removable: false

  SSD is: false

  Is Offline: false

  Is perpetually booked: false

  Thin Provisioning status: Yes

  Attached filters:

  VAAI status: unknown

  Other UID: vml.01000000003933626234613337333438653431303053746f725472

  [July 27, 2012 12:34:07: MULTITECH] SETTING [0]: called VTAF::TestLib:Sphere:Storage:Lib:CLI:ScsiLun:IsLunAvailable (Password='password@123' Username = 'root' HostName = 'esxia.amiads.com' LunName = 'eui.93bb4a37348e4100') returns '1'

  [July 27, 2012 12:34:07: TRANSPORT] [0] FRAMEWORK: running cmd 'esxcfg-mpath - bd eui.93bb4a37348e4100' mode of blocking on the host 'esxia.amiads.com '...

  [July 27, 2012 12:34:07: STAFBASE] [0] FRAMEWORK: command execution STAF: staf esxia.amiads.com PROCESS SAMECONSOLE RETURNSTDOUT RETURNSTDERR WORKDIR SHELL START / WAIT COMMAND esxcfg-mpath - bd eui.93bb4a37348e4100

  [July 27, 2012 12:34:08: STAFPROCES] [0] FRAME: host esxia.amiads.com returned eui.93bb4a37348e4100: * iSCSI disk (eui.93bb4a37348e4100)

  vmhba34:C1:T65:l0 LUN:0 State: dead iscsi adapter: not available target: unavailable

  vmhba34:C0:T65:l0 LUN:0 State: dead iscsi adapter: not available target: unavailable

  [July 27, 2012 12:34:08: HOTADDREMO] [0] INFO: eui.93bb4a37348e4100 died because of the LUN to remove test

  So basically had the question warm Add Remove Lun. It is a problem in the ESX version we use and scripts of WorkBench. If we use the build ESX GA this would have worked. ESX changed the behavior of the command in version 5.5 of GA to a new approach and then back to the old approach again in 5.5 Update1.

  The version we use are two versions higher than the release of GA... Therefore, the behavior of this command is different between these two versions.

  ESXi 5.5 Patch 2	2014-07-01	1892794	N/A
  ESXi 5.5 Patch Express 4	2014 06-11	1881737	N/A
  ESXi 5.5 Update 1 has	2014-04-19	1746018	N/A
  ESXi 5.5 Express Patch3	2014-04-19	1746974	N/A
  ESXi 5.5 Update 1	2014 03-11	1623387	N/A
  ESXi 5.5 Patch1	2013 12-22	1474528	N/A
  ESXi 5.5 GA	2013-09-22	1331820	N/A

  
  

  This is the behavior in version 5.5 GA ESX

  ~ # vmware - v

  VMware ESXi 5.5.0 build-1331820

  Added the target

  ~ # esxcfg - mpath - bd eui.3db57bdc252c0200

  1. EUI.3db57bdc252c0200: FRIEND iSCSI disk (eui.3db57bdc252c0200)

  vmhba34:C0:t0:l0 LUN:0 Status: active iscsi adapter: iqn.1998-01.com.vmware:5213e0fa-31de-329a-5885-002590135b9e-17c7a47e target: IQN = iqn.1991 - 10.com.ami:itx002590135d84e923:l.v10 Alias = Session = 00023 000002 PortalTag = 5 d

  ~ # echo $?

  0

  Removed from the target

  ~ # esxcfg - mpath - bd eui.3db57bdc252c0200

  Device eui.3db57bdc252c0200 unknown

  ~ # echo $?

  1

  Now the version of ESX 5.5 Update 1, we use

  Added the target

  ~ # vmware - v

  VMware ESXi 5.5.0 build-1623387

  ~ # esxcfg - mpath - bd eui.5b5fbb54c4d80200

  1. EUI.5b5fbb54c4d80200: FRIEND iSCSI disk (eui.5b5fbb54c4d80200)

  vmhba38:C1:t0:l0 LUN:0 Status: active iscsi adapter: iqn.1998-01.com.vmware:5405e3db-f95e-9f9c-e99b-0025900cab82-01a17ffb target: IQN = iqn.1991 - 10.com.ami:itx00259014329a26b:l.sharontest Alias = Session = 00023 PortalTag = 9 000002 d

  ~ # echo $?

  0

  Removed from the target

  ~ # esxcfg - mpath - bd eui.5b5fbb54c4d80200

  1. EUI.5b5fbb54c4d80200: FRIEND iSCSI disk (eui.5b5fbb54c4d80200)

  vmhba38:C1:t0:l0 LUN:0 State: dead iscsi adapter: not available target: unavailable

  ~ # echo $?

  0

• Change the path to the Round Robin of the newest storage used

  Dear Experts,

  For one of our guests (on two hosts total), which is presented with two data warehouses:

  -Storage 1 (works with RoundRobin vmware)

  -Storage 2 (works with most recent used vmware)

  I need to know if I can change it so that things work and there are two VM in this data store 'storage 2'.

  All the foregoing gave two data warehouses are working with (Round Robin vmware) with host 2nd in our environment

  Please notify

  Just did on one of the used data stores. No problems.

  Just follow this Article

  VMware KB: Changing the path information for ESX ESXi hosts to access

• Impossible to change the path for the shared virtual machines

  Hello

  as long as user root, in the Preferences menu, shared, VMs when I change the location and

  (1) push apply 1 time, the path is created in the right place on the hard drive but when I want to share a virtual machine and move toward this path, the default path is the default: / var/lib/vmware... not the one created by the menu setting.

  Cannot change the location for the shared virtual machines.

  (2) push apply several times: odd error menu

  

  OS: Linux mandriva 64

  Any ideas?  Is this a way to manually change the path in a config file?

  Best respect

  Out of work station - stop pass.
  Then edit datastores.xml - don't know where the files on Linux - I expect it be in/etc/vmware/hostd or something like that

• The installation of VMWare View Server program

  Hello

  I have a solution of ESXi, vSphere 5 where I host all my virtual servers with a virtual vCenter Management Standard.  I'm working on that I need for a configuration of VMWare View and I was hoping someone here could help me.

  I have 12 physical blades to host my VMWare View solution (according to the calculations of number of jobs) and I have VMWare View Bundle licenses.

  Ive been reading through the notes and he says that this set comes with an edition of vCenter.

  A few questions:

  My existing vCenter instance should be used to manage the VMWare View host or do I need to install a separate instance of vCenter VMWare View and use the license in the bundle?

  I guess I should install ESXi instances in the beam that will allow me to supply only desktop computers?

  If I have servers connection and composer, should they be hosted in Clusters VMWare View or the cluster of servers existing vsphere 5?

  If this is the case, I also have a question about the network configuration.  When I install the ESXi for VMWare View, will I still have a requirement for a management console, the vmkernel, and the 'Front End' (for users IP address) vnic to the vswitch?

  Another question about the round rbin DNS.  I try to also install Connection 2 and 2 servers of composer whose load is balanced.  Anyone has any info on setting up of Robin DNS?

  Thank you very much

  We use a 6 with network storage based physical NETWORK adapter configuration.

  You will have a default port for management.  vMotion is split to its own IP address, and these two vmkernel ports are on the same vSwitch, with natachasery used by one and waiting for the other.

  iSCSI must be separated from its own vSwitch and pair of NICs as well supported by linked vmkernel ports for redundancy and load balancing.

  This leaves at least another vSwitch and pair of natachasery to the actual traffic of vm.

  -KjB

  Post edited by: kjb007: said vSwitch

• Tracking the path of death in ESXi 4.1

  What is the best approach to ESXi 4.1 for the path of death? I would like to an alert and e-mail when a new path of death is.

  Appreciate in advance your entries.

  There is alarm for this - degraded redundancy of storage path. Check it out.

• How to change the path to the use of the esx command line logic unit number

  Hi friends,

  We want to change the path to the lun, the scripts are there?

  Thank you.

  Check if http://www.vmware.com/support/developer/vcli/vcli41/doc/reference/vicfg-mpath.html nigra

  If you have found this information useful, please consider awarding points to 'Correct' or 'Useful'*.

• Can't find vmdk, even if the path is right?

  I wanted to rename a VMDK, so I renamed it manually. However, it is a VMDK split and I renamed it manually each piece. I am sure that each piece is aptly named. However, now merging won't let me add the VMDK to a virtual machine, so I decided to edit the vmx file a vm to force a path that him. When you start this virtual machine, I get an error saying "Unable to open path/to/vmdk/hdd.vmdk." The system cannot find the specified file. "Of course, the path is right and the file exists. Fusion just doesn't use the file.

  This is obviously because of something I did with the name change. How would I go about fixing this?

  Entegy wrote:

  I tried earlier to rename all the pieces back to their original name and merger was able to reuse the file. So I guess now the question is how you rename a VMDK?

  I thought that the vmware-vdiskmanager GUI wrapper covered this case, but apparently not.  With the power off virtual machine, you can use vmware-vdiskmanager on the command line in the Terminal to rename the drive:

  "/ Library/Application Support/VMware Fusion/vmware-vdiskmanager '-n sourceName.vmdk destinationName.vmdk

  Where sourceName.vmdk OS x is usually Users/your_username/Documents/Virtual Machines/.vmwarevm/vmname.vmdk

  The parent of a split disk VMDK covers rename all the parts, also make sure that you do not rename the basic disk if a snapshot is SEO.  For snapshots, you can delete snapshots, and then rename the convergent base image or rename the snapshot that let first movement to the top of the chain of snapshot for the basic disk.

• In the Service Console the path value preferred on vSphere?

  Hello

  We have a problem here.

  Environmental: political vSphere Host, 8 HBAs, path: fixed path of vmware, on 1,000 paths to storage

  To reduce the total number of paths we want to reconfigure our warehouses of data and reduce the number of used HBA for warehouses of test and reference using only 2 of the 8 host bus adapters. We use all the time, then put 6 of them on all our servers of vsphere for people with reduced mobility, only two remain active.

  That is why we have active and people with disabilities with the help of a script on paths of console service - it works very well.

  But after that we reduce active host bus adapters, vsphere seems to forget reset the preferred path (just checked in the GUI). We put vmhba1 and vmhba7 to be active, 0-8 (except no. 6 as is the lsi controller) should be disabled, but on most of these disabled HBA Lun remains the favorite.

  On esx 3.5 service console, we were used to:

  / usr/sbin/esxcfg-mpath - favorite - political fixed = - lun = $lun - path = $: ${lun # *------:}}

  but these options (favorite, political) seem to be outdated since vsphere, which apparently obtained these commands on the api storage?

  Can someone answer the following questions on this issue:

  1 did affect the feature if you prefer the path is one of the disabled?

  2 will be the vsphere host keeps this configuration after reboot (disabled HBA to a lun, active paths)?

  3. is there a new command to set the access path AND / OR politics (MRU, FIXED, RR) to a logical unit number?

  Thanks in advance,

  Kind regards

  Alex

  Hello

  for active/passive, please use MRU;

  as you know, when fixed in use and the LUNS mapped to multiple hosts, 1 host perhaps selects path fixed-to-controller 0 and 2nd host perhaps selects fixed path to controller 1, then the current path will change between two controllers, way stolen here;

  Binoche, VMware VCP, Cisco CCNA

• Where is the path to copy SYSPREP from Windows 2003 to Windows 2008 64-bit files?

  Im running Windows 2008 64 BIT for my vCenter server, but can't find the patch where should I copy the files?

  Can someone list the path?

  see this KB

  http://KB.VMware.com/kb/1005593

• What is the path for the storage of cookies

  On my computer, I installed WinPatrol and at the end of each browsing session, I used to make use of it's 'see the cookies' the function to remove. Recently, I had reason to update FireFox and since then the cookies in WinPatrol visualization function no longer works. According to WinPatrol, it's because the 'filepath' where are stored the cookies have been deleted. Unfortunately, I do not know which is the path or how to restore. If someone out there could tell me what it is and how to restore it I would be eternally grateful. And Yes, I know that I am a fool and shouldn't be allowed near a computer this is why I am asking for help.
  Thank you.

  You can leave the cookies expire when Firefox is closed to make the session cookies.

  • Firefox/tools > Options > privacy > "Use the custom settings for history" > Cookies: keep until: "closing of Firefox".

  Create an exception to "allow" cookie for the cookies you want to keep.

  • Firefox/tools > Options > privacy > "Use the custom settings for history" > Cookies: Exceptions