ndmuser's Posts

I opened case with VMWare techsupport. Specialist provided me with KB6482648 and KB9453805 explaining how to resignature all VMFS volumes, however it is not what I planned to hear. We could not f... See more...
I opened case with VMWare techsupport. Specialist provided me with KB6482648 and KB9453805 explaining how to resignature all VMFS volumes, however it is not what I planned to hear. We could not figure out why invisible LUN was detected as snapshot by ESX. I am using the simplest MSA1000 configuration with one switch, no storage groups, one HBA in each of 4 servers ( Exchange, ArcServe Backup, two ESXs). I have to schedule downtime for all my VMs for resignaturing sometimes next week so if someone knows better solution please let me know! Thanks!
THe "..resignaturing.. & .. snapshot LUN.." message, makes me think that there is a LUN # mismatch. To test this, go to the Configuration Tab in the Infrastructure Client, go to Advanced Se... See more...
THe "..resignaturing.. & .. snapshot LUN.." message, makes me think that there is a LUN # mismatch. To test this, go to the Configuration Tab in the Infrastructure Client, go to Advanced Settings, click on LVM, and change LVM.DisallowSnapshotLun from 1 to 0. If after changing to 0, you can see the LUN, then there's a definite mismatch in LUN number from when the LUN was first created to now. If possible, I would unpresent the LUN from both Hosts (through the SAN management interface) and re-present the LUN making sure to use the same LUN for both of the hosts. Mayur You are right! I changed LVM.DisallowSnapshotLun from 1 to 0 and I was able to see the second LUN. Could I change the value back? Will I lose it again? Could I leave everything as it is? How will it affect functionality? If I do unpresent-re-present operation how can I be sure that I am using the same LUN on both hosts? I used SSP on MSA 1000 for configuration. Thank you!
On both servers in 'Configuration/Storage adapters' I see the LUN ID 4 for this 'invisible' in Configuration/Storage LUN.
I would say so. The SAN Identifier is different but everything else is the same. Below is the output from the 'good' server: \---- RAID Controller (SCSI-3) vmhba0:0:0 (0MB) has 1 paths and ... See more...
I would say so. The SAN Identifier is different but everything else is the same. Below is the output from the 'good' server: \---- RAID Controller (SCSI-3) vmhba0:0:0 (0MB) has 1 paths and policy of Most Recently Used FC 6:1.0 210000e08b180a45<->500805f3000db151 vmhba0:0:0 On active preferred Disk vmhba0:0:3 /dev/sda (140010MB) has 1 paths and policy of Most Recently Used FC 6:1.0 210000e08b180a45<->500805f3000db151 vmhba0:0:3 On active preferred Disk vmhba0:0:4 /dev/sdb (420041MB) has 1 paths and policy of Most Recently Used FC 6:1.0 210000e08b180a45<->500805f3000db151 vmhba0:0:4 On active preferred Disk vmhba1:0:0 /dev/cciss/c0d0 (69970MB) has 1 paths and policy of Fixed Local 11:1.0 vmhba1:0:0 On active preferred \---- Thanks!
Yes.
warning:LVM:4903:vmhba0:0:4:1 may be a snapshot: disabling access. See resignaturing section in SAN config guide. (0:16:20:46.234 cpu2:1037) Thank you!
Which logs should I check? (I am the beginner:) Thank you!
I have 1 esx 3.0.1 server connected to MSA 1000. This server uses 2 LUNs on the SAN. Recently I added another esx 3.0.1 server and would like it to use the same 2 LUNS. For some reason I was able... See more...
I have 1 esx 3.0.1 server connected to MSA 1000. This server uses 2 LUNs on the SAN. Recently I added another esx 3.0.1 server and would like it to use the same 2 LUNS. For some reason I was able to see onle one of the SAN LUNs in the Configuration/Storage window while I see both in Configuration/Storage Adapters pane. Below is the output from esxcfg-mpath -l (from the 'bad' server) \---- RAID Controller (SCSI-3) vmhba0:0:0 (0MB) has 1 paths and policy of Most Recently Used FC 6:1.0 210000e08b189f42<->500805f3000db151 vmhba0:0:0 On active preferred Disk vmhba0:0:3 /dev/sda (140010MB) has 1 paths and policy of Most Recently Used FC 6:1.0 210000e08b189f42<->500805f3000db151 vmhba0:0:3 On active preferred Disk vmhba0:0:4 /dev/sdb (420041MB) has 1 paths and policy of Most Recently Used FC 6:1.0 210000e08b189f42<->500805f3000db151 vmhba0:0:4 On active preferred Disk vmhba1:0:0 /dev/cciss/c0d0 (69970MB) has 1 paths and policy of Fixed Local 11:1.0 vmhba1:0:0 On active preferred \---- The problem is with the Disk vmhba0:0:4 (420041 MB). Could you please help me to make it visible? Thank you!
I have ESX 3.0.1 Standard edition server. It was installed with host-based licensing . Recently we bought VC2 license and two ESX 3.0.1 Enterprise licenses. I installed VC2 and licensing server o... See more...
I have ESX 3.0.1 Standard edition server. It was installed with host-based licensing . Recently we bought VC2 license and two ESX 3.0.1 Enterprise licenses. I installed VC2 and licensing server on the same physical box. My goal is to upgrade existing ESX 3.0.1 Standard license to Enterprise license, switch from Host-based licensing to License Server-based licensing , then install the second ESX 3.0.1 Enterprise sever. As a result I would like to have VC2 with 2 Enterprise and 1 Standard licenses in the license pool. Could you please help me with the correct order of steps to achieve this goal? The additional complication is that I downloaded licenses for Enterprise edition for host-based licensing, not for license server-based mode. ( I was not sure if we get money for VC). Thank you!
Thank you for your post, gmorrow! I had problems with tarball too. VI3.0.1 ISO image worked perfectly fine for us. I would suggest to use ISO instead of tarball if you are new to VMware and no... See more...
Thank you for your post, gmorrow! I had problems with tarball too. VI3.0.1 ISO image worked perfectly fine for us. I would suggest to use ISO instead of tarball if you are new to VMware and not very experienced in Linux.