How to locate the fiber channel SAN disks on the ESX Server
Hi all
Please help on this
How to find and configure the fiber channel SAN disks on the ESX Server
Concerning
Vijay
Assuming that you have configured LUNS on your storage space itself you will need to ensure that the ID in the world of fiber HBA on the host ESX (you can see them registered against fiber HBA under storage adapters, WWID) are configured on the switch of fiber access (read and write).
In the VI Client connected to your ESX host, select the storage adapters tab and highlight the Fibre HBA. Right-click and select Rescan. If you have correctly configured the SAN and the Fibre switch, then the LUNS now appear under the fiber HBA. Go to storage and select Add storage. Follow the wizard through to add LUNS and VMFS format. Do this for each ESX host that you want to see the LUNS.
If you found this helpful, please consider awarding points
Tags: VMware
Similar Questions
-
How to locate the owner of an iPhone that has been reported lost and deleted?
How to locate the owner of an iPhone that has been reported lost and deleted?
You return to the police or to the carrier the phone is bound to and let them deal with him. Privacy laws prevent Apple, or the carrier to disclose this information.
-
How to find the right server to use windowsmail to send and receive e-mails?
How to find the right server to use windowsmail to send and receive e-mails?
Who is your current e-mail server? (Which is after the @ in your address).Windows Mail: Setting up an account of end-to-end
http://Windows.Microsoft.com/en-us/Windows-Vista/Windows-mail-setting-up-an-account-from-start-to-finish -
How to check the ESX memory for errors?
Hi all
I faced with the strange behavior of ESX:
Some linux VMs (RHEL) were stopped. No error messages in the vCenter nor LabManager, I even thought that someone just connected and Runic stop.
Below you will find information of ESX server logs:
(1) the vmkernel newspaper:
#grep - color = always-i ' 1922 [^ 0-9] "... /VMkernel *"
.. (/ VMkernel.8:Dec 8 22:22:40 WKK1EC02 vmkernel: 290:11:51:47.230 cpu14:23084) UserDump: 1441: Dumping cartel 23079 (of the world 23084) to file the vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-vmx-zdump.000...
(2) the journal of the VM:
# grep ' 08 Dec' /vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-1.log '.
16:53:49.164 Dec 08: vmx | GuestRpcSendTimedOut: message to the Toolbox has expired.
16:54:14.972 Dec 08: vmx | GuestRpcSendTimedOut: message to the Toolbox has expired.
21:59:05.262 Dec 08: mks | Cannot write the temporary image THUMB
21:59:15.264 Dec 08: mks | Cannot write the temporary image THUMB
21:59:30.270 Dec 08: mks | Cannot write the temporary image THUMB
21:59:35.271 Dec 08: mks | Cannot write the temporary image THUMB
21:59:45.275 Dec 08: mks | Cannot write the temporary image THUMB
21:59:50.285 Dec 08: mks | Cannot write the temporary image THUMB
22:00:00.274 Dec 08: mks | Cannot write the temporary image THUMB
22:00:05.276 Dec 08: mks | Cannot write the temporary image THUMB
22:01:15.410 Dec 08: mks | Cannot write the temporary image THUMB
22:03:25.312 Dec 08: mks | Cannot write the temporary image THUMB
22:05:00.324 Dec 08: mks | Cannot write the temporary image THUMB
22:05:05.340 Dec 08: mks | Cannot write the temporary image THUMB
22:05:15.331 Dec 08: mks | Cannot write the temporary image THUMB
22:05:20.341 Dec 08: mks | Cannot write the temporary image THUMB
22:05:30.344 Dec 08: mks | Cannot write the temporary image THUMB
22:05:35.353 Dec 08: mks | Cannot write the temporary image THUMB
22:05:40.354 Dec 08: mks | Cannot write the temporary image THUMB
22:05:45.366 Dec 08: mks | Cannot write the temporary image THUMB
22:05:50.357 Dec 08: mks | Cannot write the temporary image THUMB
22:05:55.361 Dec 08: mks | Cannot write the temporary image THUMB
22:06:00.365 Dec 08: mks | Cannot write the temporary image THUMB
22:06:05.371 Dec 08: mks | Cannot write the temporary image THUMB
22:06:10.395 Dec 08: mks | Cannot write the temporary image THUMB
22:06:15.379 Dec 08: mks | Cannot write the temporary image THUMB
22:06:20.381 Dec 08: mks | Cannot write the temporary image THUMB
22:06:30.397 Dec 08: mks | Cannot write the temporary image THUMB
22:06:40.403 Dec 08: mks | Cannot write the temporary image THUMB
22:20:45.541 Dec 08: mks | Cannot write the temporary image THUMB
22:21:10.580 Dec 08: mks | Cannot write the temporary image THUMB
22:21:15.538 Dec 08: mks | Cannot write the temporary image THUMB
22:21:20.554 Dec 08: mks | Cannot write the temporary image THUMB
22:21:25.545 Dec 08: mks | Cannot write the temporary image THUMB
22:21:30.580 Dec 08: mks | Cannot write the temporary image THUMB
22:21:35.591 Dec 08: mks | Cannot write the temporary image THUMB
22:21:40.537 Dec 08: mks | Cannot write the temporary image THUMB
22:21:45.629 Dec 08: mks | Cannot write the temporary image THUMB
22:21:50.583 Dec 08: mks | Cannot write the temporary image THUMB
22:21:55.616 Dec 08: mks | Cannot write the temporary image THUMB
22:22:00.590 Dec 08: mks | Cannot write the temporary image THUMB
22:22:05.638 Dec 08: mks | Cannot write the temporary image THUMB
22:22:10.595 Dec 08: mks | Cannot write the temporary image THUMB
22:22:15.582 Dec 08: mks | Cannot write the temporary image THUMB
22:22:20.622 Dec 08: mks | Cannot write the temporary image THUMB
22:22:25.583 Dec 08: mks | Cannot write the temporary image THUMB
22:22:30.627 Dec 08: mks | Cannot write the temporary image THUMB
22:22:35.673 Dec 08: mks | Cannot write the temporary image THUMB
22:22:40.588 Dec 08: mks | Panic: file lock (was the bug 49968)
22:22:40.589 Dec 08: mks | Bora/lib/image/imageUtilPng.c:462 unrecoverable memory allocation failure
22:23:21.438 Dec 08: mks | Backtrace:
22:23:21.440 Dec 08: mks | Backtrace [0] 0x3ccf63d8 eip 0xa3f88cd
22:23:21.442 Dec 08: mks | Backtrace [1] 0x3ccf6818 eip 0x9ff705c
22:23:21.443 Dec 08: mks | Backtrace [2] eip 0xa2803bc 0x3ccf6b88
22:23:21.443 Dec 08: mks | Backtrace [3] eip 0xa2803f6 0x3ccf6bb8
22:23:21.444 Dec 08: mks | Backtrace [4] eip 0xa27fcc3 0x3ccf6bd8
22:23:21.444 Dec 08: mks | Backtrace [5] eip 0xa27fd28 0x3ccf6c28
22:23:21.445 Dec 08: mks | Backtrace [6] eip 0xa115582 0x3ccf7128
22:23:21.445 Dec 08: mks | Backtrace [7] eip 0xa115717 0x3ccf7138
22:23:21.445 Dec 08: mks | Backtrace [8] eip 0xa00d0a9 0x3ccf7168
22:23:21.446 Dec 08: mks | Backtrace [9] 0x3ccf9278 0xa00dbef eip
22:23:21.447 Dec 08: mks | Backtrace [10] eip 0x3ccf9298 0xa298217
22:23:21.447 Dec 08: mks | Backtrace [11] eip 0x3ccf92b8 0xa298255
22:23:21.448 Dec 08: mks | Backtrace [12] eip 0x3ccf92e8 0xa10bfe9
22:23:21.448 Dec 08: mks | Backtrace [13] eip 0xa0f2e81 0x3ccf93c8
22:23:21.504 Dec 08: mks | Backtrace [14] eip 0x160534fb 0x3ccf94b8
22:23:21.505 Dec 08: mks | Backtrace [15] eip 00000000 0x1613ae3e
22:23:21.507 Dec 08: mks | SymBacktrace [0] 0x3ccf63d8 eip in function 0xa3f88cd in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.508 Dec 08: mks | SymBacktrace [1] 0x3ccf6818 eip 0x9ff705c panic function in/usr/lib/vmware/bin/vmware-vmx of the object loaded on the 0x9f98000
22:23:21.508 Dec 08: mks | SymBacktrace [2] 0x3ccf6b88 eip in function 0xa2803bc in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.511 Dec 08: mks | SymBacktrace [3] 0x3ccf6bb8 eip in function 0xa2803f6 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.511 Dec 08: mks | SymBacktrace [4] 0x3ccf6bd8 eip in function 0xa27fcc3 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.512 Dec 08: mks | SymBacktrace [5] 0x3ccf6c28 eip in function 0xa27fd28 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.513 Dec 08: mks | SymBacktrace [6] 0x3ccf7128 eip in function 0xa115582 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.514 Dec 08: mks | SymBacktrace [7] 0x3ccf7138 eip in function 0xa115717 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.515 Dec 08: mks | SymBacktrace [8] 0x3ccf7168 eip in function 0xa00d0a9 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.515 Dec 08: mks | SymBacktrace [9] 0x3ccf9278 eip in function 0xa00dbef in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.516 Dec 08: mks | SymBacktrace [10] 0x3ccf9298 eip in function 0xa298217 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.517 Dec 08: mks | SymBacktrace [11] 0x3ccf92b8 eip in function 0xa298255 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.518 Dec 08: mks | SymBacktrace [12] 0x3ccf92e8 eip in function 0xa10bfe9 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.519 Dec 08: mks | SymBacktrace [13] 0x3ccf93c8 eip in function 0xa0f2e81 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
22:23:21.519 Dec 08: mks | SymBacktrace [14] 0x3ccf94b8 eip 0x160534fb in function (zero) in the object /usr/lib/vmware/lib/libpthread.so.0 to the 0x1604e000
22:23:21.520 Dec 08: mks | SymBacktrace [15] eip 00000000 0x1613ae3e based on cloning in object /usr/lib/vmware/lib/libc.so.6 loaded in 0 x 16069000
22:23:21.520 Dec 08: mks | Msg_Post: error
22:23:21.521 Dec 08: mks | [msg.log.error.unrecoverable] fatal error VMware ESX: (mks)
22:23:21.521 Dec 08: mks | Bora/lib/image/imageUtilPng.c:462 unrecoverable memory allocation failure
22:23:21.521 Dec 08: mks | [msg.panic.haveLog] a log file is available in "/ vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware.log". [msg.panic.haveCore] a base file is available in "/ vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-vmx-zdump.000". [msg.panic.requestSupport.withLogAndCore] please request support and include the contents of the log file and the base file. [msg.panic.requestSupport.vmSupport.vmx86]
22:23:21.523 Dec 08: mks | To collect the data to submit to the VMware support, run 'vm-support.
22:23:21.524 Dec 08: mks | [msg.panic.response] we will respond on the basis of your entitlement to support.
22:23:21.525 Dec 08: mks | ----------------------------------------
22:23:21.739 Dec 08: vmx | Watched VTHREAD thread 1 "mks" is dead
22:23:22.651 Dec 08: 1 vcpu. Watched VTHREAD thread 0 "vmx" is dead
22:23:22.740 Dec 08: vcpu-3 | Watched VTHREAD thread 0 "vmx" is dead
22:23:22.741 Dec 08: vcpu-2 | Watched VTHREAD thread 0 "vmx" is dead
22:23:22.743 Dec 08: vcpu-0 | Watched VTHREAD thread 0 "vmx" is deadI found the suggestion to check the ESX memory for problems.
I found the information that ESX 3.0 was ramcheck service which could check the memory, but there is no such service in future versions of ESX.
Could someone help me find how to check the memory without stopping the ESX Server (I could not migrate virtual machines per host)?
The only way you will get a true test of the memory of the HOST must stop it and run the test directly. Any tool running in the ESX console will only have indirect access RAM. The vmkernel controls access to physical RAM.
-
How to configure the SMTP server for the osb 10.3.1
Hi all
Anyone can share information on how to configure the SMTP server for the osb 10.3.1
and then how to send an email to OSB 10.3.1
Thanks in advance!See this url:
https://blogs.Oracle.com/christomkins/entry/sending_an_email_from_oracle_s -
VMDK file unreadable after migration of VM &; update of the ESX Server
Last night we have updated the ESX servers here and in the migration process machines from one node to the other (by placing a single node of the cluster in maintenance mode). During this migration, the VMs one has stopped running. When we finished the migration and had updated the ESX Server, we brought the system to the top and tried to start this virtual machine.
First, we looked in the directory of the virtual machine and saw that the VMDK file has a different name, with - dish at the end (before hard). We have renamed the file, removing the - flat extension, and this is where we saw these messages. ESX Server always gbehaved as if the file did not exist or was unreadable. Here is an extract from the log:
14:40:08.232 27 Feb: vmx | KHZEstimate 2931923
14:40:08.232 27 Feb: vmx | 2932 MHZEstimate
14:40:08.232 27 Feb: vmx | NumVCPUs 1
14:40:08.247 27 Feb: vmx | UUID: location-UUID is 56 4 d d4 6 to 87 30 4 c 0 b - 74 63 41 09 76 a7 1A f8
14:40:08.247 27 Feb: vmx | WORKER: Create a new group with numThreads = 2 (2)
14:40:08.337 27 Feb: vmx | Mainmem mapped as pageable
14:40:08.361 27 Feb: vmx | MStat: Creation vm.uptime Stat
14:40:08.361 27 Feb: vmx | MStat: Creation vm.suspendTime Stat
14:40:08.361 27 Feb: vmx | MStat: Creation vm.powerOnTimeStamp Stat
14:40:08.369 27 Feb: vmx | VMXVmdb_LoadRawConfig: Loading of raw configuration
14:40:08.376 27 Feb: vmx | Cannot find the file cognos4dios.zurich.ibm.com.vmdk
14:40:08.378 27 Feb: vmx | Cannot find the file cognos4dios.zurich.ibm.com.vmdk
14:40:08.378 27 Feb: vmx | DISC: Scsi0:0 OPEN 'cognos4dios.zurich.ibm.com.vmdk' R [(null) persistent]
14:40:08.380 27 Feb: vmx | Cannot find the file cognos4dios.zurich.ibm.com.vmdk
14:40:08.382 27 Feb: vmx | DISKLIB-LINK: 'cognos4dios.zurich.ibm.com.vmdk': cannot open (the system cannot find the specified file).
14:40:08.382 27 Feb: vmx | DISKLIB-STRING: 'cognos4dios.zurich.ibm.com.vmdk': cannot open (the system cannot find the specified file).
14:40:08.382 27 Feb: vmx | DISKLIB-LIB: cannot open "cognos4dios.zurich.ibm.com.vmdk" with flags 0xa (the system cannot find the specified file).
14:40:08.382 27 Feb: vmx | Msg_Post: error
14:40:08.382 27 Feb: vmx | http://Msg.disk.FileNotFound VMware ESX Server cannot find the virtual disk 'cognos4dios.zurich.ibm.com.vmdk '. Please check that the path is valid and try again.
14:40:08.382 27 Feb: vmx | http://Msg.disk.noBackEnd can't open the Flash 'cognos4dios.zurich.ibm.com.vmdk' or one of the disks disk that it depends on.
14:40:08.382 27 Feb: vmx | http://Msg.disk.configureDiskError reason: the system cannot find the specified file. -.
14:40:08.399 27 Feb: vmx | Power DiskEarly module has failed.
14:40:08.399 27 Feb: vmx | VMX_PowerOn: ModuleTable_PowerOn = 0
14:40:08.401 27 Feb: vmx | WORKER: asyncOps = 0 maxActiveOps = 0 maxPending = 0 maxCompleted = 0
14:40:08.752 27 Feb: vmx | vmdbPipe_Streams could not read: OVL_STATUS_EOF
14:40:08.752 27 Feb: vmx | Output of idle VMX
14:40:08.764 27 Feb: vmx | VMX VMDB Flushing connections
14:40:08.771 27 Feb: vmx | IPC_exit: disconnect all discussions
14:40:08.771 27 Feb: vmx | Exit VMX (0).
14:40:08.772 27 Feb: vmx | VMX has left the building: 0.
The VMDK file is indeed the most, but VMware seems unable to open it. For what it's worth, it was also noted a .hlog file in the directory of the virtual machine on the server:
cognos4dios. Zurich.IBM.com - 3 c 377802 .hlog:
C2 C0 71 17 14 6 b6 01-49 fb 00 1 a 64 35 20 e9
Anyone can shed some light on this? Done-flat suffix in the VMDK file have a special meaning? Any recommendations for the rescue of this virtual machine?
Thank you very much in advance.
Kind regards
Michael L.
-Flat.vmdk file is your data file where all of your actual data has been stored. Name back to the original value.
It seems that you have lost the descriptor file (vmname.vmdk). If you have not an extraction backup the following procedures to re-create this file
-
Adding a new NETWORK adapter to the ESX Server
I have an ESX 3.5 server that has two NIC onboard. I decided that I will join the ESX Server to the SAN, so I need these two NICS for iSCSI. I'm going to install a NETWORK card in the PCI - X slot. Unfortunately, without GUI, I'm confused as to how it will work. Can someone give me some advice on how to add a new NETWORK card? I checked esxcfg and I don't know if that's what I'm trying to use. Any help would greatly be appreciated.
In the VI client, you should be able to go on the tab network management under configuration see the NIC it to add them to the correct vSwitch.
Kyle
-
DEOs change to the political necessity of round robin to restart the ESX Server
Hi friends,
When set politics multi-path set to Round robin, is it necessary to restart the ESX Server?
Thank you.
No.... You should see that paths become active after you change the setting.
André
-
Hello
Is it possible to move configurations of lab manager between the ESX server host computers / data warehouses? I don't see an option in the library & gt; Clone library. Thank you!
Recently, I used SSMove to migrate our datastore LM set a new LUN. It's really simple to use. This KB gives complete instructions on SSMove http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1006694&sliceId=1&docTypeID=DT_KB_1_1&dialogID=8456583&stateId=0%200%209407965
See you soon
Paul
-
Re: How to find the location of a VMware Workstation v10.0.3 vmdk readers when stereotypes are present.
Hello
Since nearly five months, I have worked on a particular project and am reviewing me with the details of the project. The virtual machine has three virtual disks. I remember the BONES of the virtual machine as well as the first disc of the vmdk virtual machine data files are in the Windows host file containing the virtual machine. Nothing unusual so far. I remember that I put the third disk of the virtual machine on my axis f: physical, but I want to make sure that before you start again work on the project.
I see of http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003880 we should be able to examine the vmx file and see the locations of virtual disk. What I've noticed, is that since I was a snapshot, I see this:
scsi0:2.present = 'TRUE '.
scsi0:2.filename = "MyProject-Disk3 - 000001.vmdk".
So what I see in the vmx is the physical location of the disk snapshot delta and not the physical location of the vmdk.
I also did a search for vmware vmdk files - x.log and I find:
2014 03-21 T 11: 35:46.964 - 04:00 | Worker #2 | I120: DISKLIB-DSCPTR: open [0]: "sample - Disk3.vmdk" (0xe)
2014 03-21 T 11: 35:46.964 - 04:00 | Worker #2 | I120: DISKLIB-LINK: opened 'F:\MyProject-Disk3\MyProject-Disk3.vmdk' (0xe): monolithicSparse, 83886080 sectors / 40 GB.
2014 03-21 T 11: 35:46.964 - 04:00 | Worker #2 | I120: DISKLIB-LIB: open 'G:\VMware VMs\MyProject\MyProject-Disk3-000001.vmdk' (0xa, type monolithicSparse flags).
So by brute force, I discovered that the parent for the VM Disk3 vmdk is the physical disk F. And even here, the only reason why I know that I have the right VM disk, because I included "Disk3" in the VM disk naming convention that I used.
But what happens if I hadn't used a physical VM disk naming convention which did not include the name of the virtual disk of the virtual machine? How could 100% sure that the third disk of my VM was the vmdk parent that I had located on the physical disk F?
There must be an easier way to do this for days just like that.
I look forward to your reply.
Kind regards...
P.S. I noticed that if I close this virtual machine and click on the 3 hard drive (SCSI), it only shows the name of the file of the virtual delta "MyProject-Disk3 - 000001.vmdk" machine and not the parent vmdk.
P.S. I noticed that if I close this VM and try using the disk utilities, the map shows that the path to the file delta 'MyProject-Disk3 - 000001.vmdk' and the parent vmdk.
Virtual disk snapshot files have the file name of the virtual disk parent included in the file descriptor hard (text file), or in the hard data file according to the format of the virtual disk. In the case of a monolithic virtual disk format (i.e. a hard single file), you may need to use a hex editor to find the 'parentFileNameHint' somewhere between 0x200 and 0x400.
André
-
How do I rescan fiber channel without having to reboot host
Hello
I have a few questions regarding the removal of LUNS and vmotion. My first question is that I can't seem to be able to delete a LUN in vsphere client 5. I get the error message but I think it's because guests can still see the LUN. I unpresented this LUN in command mode and deleted. Now in vsphere client, the logic unit number shows idle and when I do a new scan task's not going anywhere. It seems that the host cannot see that LUN more and is having a heart attack. The worst is that vmotion does not work when this happens. So to fix this I had to reboot the esx host. Once the host is back online this LUN disappeared and vmotion works again.
Now my problem is that I have 32 esx host and I don't want to have to restart all the and the fact that vmontion does not work I can not migrate the virtual machine between hosts. Is there a way to force guests to rescan the channels fiber so that they will not see the deleted LUN more or is there another solution for this?
Thanks in advance
It sounds as if you did not remove the VMFS datastore before unpresenting/remove the logic unit number!
There are different as KB to remove a datasbase in vCenter Server data store, but those who are for v4.x and I'm not sure if they apply to the v5.0 as well (e.g. http://kb.vmware.com/kb/1026661) maybe a restart of management on hosts agents will cancel the deleted LUN, have you tried this already?
You can also take a look at best practices: how to properly remove a unit logic of an ESX host number
André
-
How to locate the index z (physical) encoder
Hello
I'm trying to locate the Z Index of a rotary encoder. I need the counter to zero at each time 0 reached the encoder shaft this same point.
My problem is that when I run the VI, the angular position starts at 0, no matter where the tree, and this point is used to reset the counter to 0 once occurs a revolution at 360 degrees. Therefore, whenever I run the VI, the current position of the tree is used as the Z-Index.
Is it possible to locate the actual physical Z-Index of the encoder that is to a specific location of the tree, so that whenever the tree reaches this point, the counter is reset to 0 and this point becomes the Z-Index whenever I run the VI (and not be the location of the tree at the moment that the VI is executed)?
Basically, I'm trying to accomplish the autoguiding technique to be resolute position of the shaft encoder and not to arbitrary locations that are in the location of the tree using the VI, that can be different each time I run the VI.
Thank you
R15
You can set a Z index position which will reset the counter to 0 whenever it passes through this station. The meter will always be preloaded with values (0, unless you change it) when you start the meter, and you go to the Z index position first of all to establish the reference position before anything else. The angular 'Measure of Position' example shows how to set the initial counter value and activate the Z index.
-
How to locate the folder the user on Windows XP desktop?
Original title: how to locate desktop on windows professional
Recently, my computer crash with blue screen. I downloaded the windows professional in a new folder on the same drive. Now I'm trying to locate the desktop folder in previous
Hi razasum,
We recommend that you open the drive where you installed Windows, for example c :) and try the following steps:
a. open the Documents and Settings folder.
b. open the user folder and locate the desktop folder.If you are looking for a specific file or folder, and then try to search for it.
See How to search for files and folders in Windows XPVisit our Microsoft answers feedback Forum and let us know what you think.
-
How anyone SAN disk of multiple ESX hosts?
Dear all,
We presented several SAN drives to a few servers ESX 4.0 memory of EVA.
As one of the SAN is not necessary now, we want anyone there.
It is also confirmed he does not need to keep all the data in this SAN disk, would you please indicate the steps to this end, but no need to shutdown ESX servers?
In fact, I tried to study the following document, but it is too difficult for me. Help, please.
Unpresenting a LUN that contains a store of ESX 4.x and ESXi4.i data
Kind regards
Tommy
what you need to do is really, make sure the logic unit number is empty, remove the LUN of your stocks of VI. From there, ask enterprise to after LUN storage team. When they have been the team of storage upnpresented, rescan your storage adapters, and logical unit number should not be more visible to your VI.
-
How to change the windows server 2003 standard Edition sp2 activation key
I'm going to conver physical server to a child in HyperV.
When I create the machine of the child after that I converted with disk2vhd.exe small tool the physical server to the .vhd file, I got the message to reactivate windows, because it's new material.
How can I do this?
The operating system is windows server 2003 sp2 standard edition
Thank you!
Support is located in the Windows Server Forums:
http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer/
Maybe you are looking for
-
Could not open file .xls of recipients
Sent by e-mail to several people with an .xlsb file attached. They are not able to open the file
-
Re: laptop equium A200-VO1 autonomy
I bought a new Equium VO1 and I want to know the average battery for this laptop battery life.I am only able to use it to 1.15 until it stops, and I don't know if this is the case with only my pc or that's what you get from toshiba? Thank youOWEZ...
-
Not found base system device driver
Recently, at startup, I get an error message 'Base system device driver' not found. Windows cannot find the driver appropriate to solve the problem. I use a laptop Presario F756NR with Windows Vista (32-bit) OS. I checked the 'properties' of device a
-
The DVD on my Pavilion A1375A Media Center PC drive is set to region 1 - I am in Australia (region 4). I can't set it to region 4. I asked HP to sell me a new DVD player, but they do not know what the new discs region code will be and asked that I co
-
Misfortune-FAH! 214C004D4EA2 Trojan
This Trojan horse was captured only by McAfee Stinger. It was impossible to remove it. The C:\\Windows\SysWOW64\vrfcore.dll file is infected. The system is stable. Please notify. Misfortune-FAH! 214C004D4EA2 Trojan