November 13, 201312 yr Hey guys, I was experimenting with vsphere server today. I've got 2 ESXi hosts, both same hardware. One gets added succesfully to vsphere, the other errors out upon trying to add. Turns out i'm experiencing this issue : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008707 These are taken from esxi comand line on both machines: Not working: /etc/vmware/vpxa # esxcfg-info | grep -i 'product name' |----Product Name.............................................X9SCL/X9SCMÿÿ |----World Command Line.................................grep -i product name Working: ~ # esxcfg-info | grep -i 'product name' |----Product Name.............................................X9SCL/X9SCM |----World Command Line.................................grep -i product name As you can see there are some weird characters in the first one. This one is running BIOS 2.0b, the other one 2.0a. Is anyone else having trouble with this and bios version 2.0b? Also in the Vsphere client on the host summary you can see some weird characters behind the motherboard brand an type. I did not think anything bad from it, but now it seems to be resulting in issues
November 13, 201312 yr Looks like I don't have that problem. I'm running vCenter 5.5. Wonder if you have a "defective" board. ~ # esxcfg-info | grep -i 'product name' |----Product Name.............................................X9SCL/X9SCM |----World Command Line.................................grep -i product name ~ #
November 14, 201312 yr Author That's strange. I did flash the BIOS myself because it came wit 1.x and I'm running a v2 CPU. The other working board came with 2.0a stock. I should maybe try a reflash Did you flash the BIOS to 2.0 or did it come with it? I contacted supermicro support but they are not quite fast to reply I guess. *EDIT: Tried a reflash of 2.0b... same result.
November 14, 201312 yr I will need to find my original box to verify, but I'm pretty sure it came with 2.0a, and I upgraded to 2.0b. I did not have a Sandy Bridge chip at the time to perform the upgrade with, so I was quite happy that it didn't arrive with 1.x.
December 23, 201312 yr I just upgraded my bios from version 1 to 2.0b, and I also got weird characters in the name - changing every time ESXi boots. I lose connection from vSphere Client after a few minutes every time I try to restart. And the address where it is disappears from the network, and can't even be ping'ed. So - I really can't do much. Sometimes I get a VM started, and it will keep running, but I can not at all administer the VM :-< I'm really in deep water here, so I hope someone can help/advise?
December 24, 201312 yr Bios 2.0c is out ... not sure if it addresses this issue or not... Thanks for the tip - sadly it didn't work. Anyone else?
December 24, 201312 yr I'd be contacting super micro support, they are very good and should quickly come to a resolution for you, especially as it's likely been seen before.
December 24, 201312 yr Thanks. After one more reboot, I have managed to stay in touch with the server for more than 2-3 minutes - I left the computer and Client connected overnight, and it's still there. Right now I don't want toi touch ANYTHING until after Christmas eve - so I don't know if I'm just lucky, or the issue indeed has disappeared. I'll post back with my findings.
December 24, 201312 yr Author 2.0c does not help. I did contact supermicro same time as starting this thread. I am yet to receive an answer.... So they are not always as helpful it seems. Sent from my HTC One using Tapatalk
December 24, 201312 yr 2.0c does not help. I did contact supermicro same time as starting this thread. I am yet to receive an answer.... So they are not always as helpful it seems. Sent from my HTC One using Tapatalk Well, it is the holidays. Give it a few days, Ogi
December 24, 201312 yr Author 2.0c does not help. I did contact supermicro same time as starting this thread. I am yet to receive an answer.... So they are not always as helpful it seems. Sent from my HTC One using Tapatalk Well, it is the holidays. Give it a few days, Ogi Where i'm from holidays don't start mid November
January 8, 201412 yr Late to the party - sorry if this isn't relevant any more. Could the bios problems be because you didn't update to 2.0a first before going to 2.0b? This wouldn't be the first time that a bios needs to be updated in stages. Although that is usually noted by the manufacturer I can see it not being noticed by them so no notice is given.
January 8, 201412 yr Author Yes i did update to 2.0b immediately. Did not see any notice it would be advised to update in stages.
January 8, 201412 yr It should be pointed out that that motherboard has a 2.0c bios available now. Not sure if it addresses any of the issues described here.
January 8, 201412 yr Author It should be pointed out that that motherboard has a 2.0c bios available now. Not sure if it addresses any of the issues described here. It does not solve the issue no. Sadly
January 28, 201412 yr Author BIOS v2.1 is out. No change in the problem... Sent from my HTC One using Tapatalk
January 28, 201412 yr Same weird characters here. Board is operating normally though, so I've just ignored it.
June 3, 201412 yr I wanted to post my continued experience, just in case others are curious about these strange characters. I just flashed to bios R 2.1, and now the funky characters are gone (for the most part), but I still have weird stuff showing up. Like here I'm still not noticing anything strange going on, but it is one of those little things that bugs me every time I see it.
June 3, 201412 yr Author Thx for updating. I've been running 2.1a while now with no better result. I also updated esxi to 5.5 update1. Still no change. Quite a frustrating little bugger Sent from my HTC One using Tapatalk
July 3, 201412 yr I haven't had this particular issue.. could I ask whether you followed the procedure outlined in my post here? http://lime-technology.com/forum/index.php?topic=26774.msg234518#msg234518 The reason I ask is that about 9 months ago, I helped someone via PM that ran the wrong batch file, and ended up with a similar issue. May be not directly related, but worth a look?
Archived
This topic is now archived and is closed to further replies.