bovc's Posts

Thanks - I guess there's no other way than that /Rasmus
VC VMware update VMware converter I should mention that the ESX servers has not been upgraded to U3, but that shouldn't make a difference? /Rasmus
Hi, Is it not possible to update from VC2.5u2 to VC2.5u3? Is a complete re-installation nessesary? If I try to run the install is simply says: Product already installed. Please... See more...
Hi, Is it not possible to update from VC2.5u2 to VC2.5u3? Is a complete re-installation nessesary? If I try to run the install is simply says: Product already installed. Please use Add/Remove programs in Control Panel to customize (or something close to that). Any ideas? Thanks in advance, Rasmus
This did it for me: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1006583&sliceId=2&docTypeID=DT_KB_1_1&dialogID=32992936&stateId=1 0 32996972
Hi, We're using AdventNet OpManager with the new ESX monitor module (ESX MIBs are included). Thanks, Rasmus
Isn't Pegasus some sort of mail program? This is SNMP not working - not SMTP Anyway, thanks for the time you took to post an answer. /Rasmus
Hi, I've tried to enable snmp on our esx servers according to this article: ...but it doesn't work. Our management app still cannot access the servers with the public community.... See more...
Hi, I've tried to enable snmp on our esx servers according to this article: ...but it doesn't work. Our management app still cannot access the servers with the public community. Now, is there anything not explained in the above article that I need to do before it will work? A reboot of the esx etc.? Thanks in advance, Rasmus
What was the problem on your dns server?
Hi, We have the exact same problem on two IBM servers. We have the exact same setup on an IBM blade center, where there's no probs, which leads me to think, that this might be a hardware ... See more...
Hi, We have the exact same problem on two IBM servers. We have the exact same setup on an IBM blade center, where there's no probs, which leads me to think, that this might be a hardware issue. I've tried connectiong from two different computers with VI client, and like I said - it works on the blade esx servers with the same VI Client - but no luck. Also tried restarting the ESX server, and restart the different vmware management services - again no luck. Dd you find any solution to your problem? Thanks, Rasmus
Hi, We have the exact same problem! The vm's are running fine, but we can't open the console. I've tried several restarts of the esx server, but it doesn't seem to work. The ESX servers a... See more...
Hi, We have the exact same problem! The vm's are running fine, but we can't open the console. I've tried several restarts of the esx server, but it doesn't seem to work. The ESX servers are IBM X Series 3850. We have the exact same installation on some IBM blades, where there's no problem at all. Only these two 3850 seems to have the problem. Maybe it's a hardware issue? Did you resolve this? Thanks, Rasmus
Hi, I really need an answer on this. Isn't there anyone out there who can help me? The basic question is just whether or not SAN LUN ID's need to be unique on a global view, or if it is eno... See more...
Hi, I really need an answer on this. Isn't there anyone out there who can help me? The basic question is just whether or not SAN LUN ID's need to be unique on a global view, or if it is enough that the ID's is unique on the individual SAN boxes. Thanks in advance. Rgds, Rasmus
Anyone?
To further explain: SAN01: LUN1 + LUN2 SAN02: LUN1 + LUN2 SAN03: LUN1 + LUN2 Total: 6 LUNs. We have 6 ESX servers, and they ALL see each LUN. So what I was trying to ask, was whether t... See more...
To further explain: SAN01: LUN1 + LUN2 SAN02: LUN1 + LUN2 SAN03: LUN1 + LUN2 Total: 6 LUNs. We have 6 ESX servers, and they ALL see each LUN. So what I was trying to ask, was whether this could conflict? Cause basically each server will see 3 different LUNs all named LUN1 - can they tell the difference? The LUNs are placed on different SAN boxes with seperate IP's, controller, etc. So basically there shouldn't be a problem - correct? Rasmus
I get your point. But the problem is not whether all esx servers sees each LUN with the same ID, but rather if each servers can see 6 LUN which are not named 1-6, but 1 and 2 (pr. SAN box)? ... See more...
I get your point. But the problem is not whether all esx servers sees each LUN with the same ID, but rather if each servers can see 6 LUN which are not named 1-6, but 1 and 2 (pr. SAN box)? It's a little difficult exlaining it I hope you understand. Rasmus
Hi, Does it matter what LUN ID I give our different LUNs? We have 6 ESX-servers and 3 SANs - each with 2 LUNs. Now, on each SAN-box the two LUNs are named 1 and 2. Shouldn't this be able to... See more...
Hi, Does it matter what LUN ID I give our different LUNs? We have 6 ESX-servers and 3 SANs - each with 2 LUNs. Now, on each SAN-box the two LUNs are named 1 and 2. Shouldn't this be able to work since the LUNs are on different SAN boxes? Or is it a bad thing? The reason I ask, is because we've seen some odd things over time. Usually finding solutions, but they just keep coming. We have the DisallowLUNSnapshot set to 0. Rgds, Rasmus
The resource settings on the vm is just set to normal. Nothing has been touched there. The vm is not an old migrated one. It has been installed in a ver. 3.0.1 environment along with other vm'... See more...
The resource settings on the vm is just set to normal. Nothing has been touched there. The vm is not an old migrated one. It has been installed in a ver. 3.0.1 environment along with other vm's that works just fine in resource pools. I tried manually setting custom share values, but it didn't make a difference. I then changed it back to Normal (cpu and memory) and tried again, with no luck I've successfully added it to the medium resource pool though, and tried to migrate it from there to the high priority group, but again - no luck! Anyone got a clue? Rasmus
I agree - it sounds that way, but they DO inherrit from the pools. Nothing has been set up on the individual machines. Rasmus
Hi, We've got a setup of 6 ESX servers (2x 2,5GHz, 8GB ram each) in a DRS/HA cluster. In this cluster I've created 3 resource pools: low, medium and high. Low group = CPU Shares:Low, RAM Sh... See more...
Hi, We've got a setup of 6 ESX servers (2x 2,5GHz, 8GB ram each) in a DRS/HA cluster. In this cluster I've created 3 resource pools: low, medium and high. Low group = CPU Shares:Low, RAM Shares:Low, Both:No Limit and expandable. Medium group = CPU Shares:Medium, RAM Shares:Medium, Both:No Limit and expandable. High group = CPU Shares:6000, RAM Shares:High, Both:No Limit and expandable. Now... There are approximately 11 vm's in each group. And then there's 1 which I've not put into any group yet - simply because I get the error below. The vm belongs in the high priority group, but when I try to add it, I get an error saying: "The memory resource shares for VM-NAME are much higher than the virtual machine's in the resource pool. With its current share settings, this virtual machine will be entitled to 62% of the CPU resources in the pool. Are you sure you want to do this?" Then I can select yes or no. But the error confuses me... Is this a CPU or memory thing? - cause it mentions both! Anyone seen this error before, or knows what to do? Maybe recommendations to a re-design of the resoruce pools? Thanks in advance, Rasmus
MCWILL: What you suggest solves my issue (had the exact same!)!!! Thanks a lot. But... What does this setting do exactly? I'm curious since I'm going to implement it on all our productio es... See more...
MCWILL: What you suggest solves my issue (had the exact same!)!!! Thanks a lot. But... What does this setting do exactly? I'm curious since I'm going to implement it on all our productio esx servers Thanks in advance, Rasmus