No the hosts were Rack servers, It didnt mention anything in the read me, but the NIC firmware said that that the nics wouldnt be changed, so tried one and no issues then the other and no issues.
Just curios as to if this is common behaviour or a peculiarity of the hardware vendor. It was good in a ways as I seriously had to find out how to use poershell for configuring VM's very quickly, but it also means a slap for the hardware guy, and a re-education on the change management process of production servers. On 21 May 2013 14:13, Eric Morrison <[email protected]> wrote: > Are the hosts blades?**** > > ** ** > > I’ve worked with Cisco UCS blades in the past where the firmware would > cause issues like this, but it’s usually listed in the readme file or > release notes for the firmware.**** > > ** ** > > Thanks,**** > > ** ** > > Eric Morrison**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Graeme Carstairs > *Sent:* Tuesday, May 21, 2013 5:49 AM > *To:* [email protected] > *Subject:* [NTSysADM] Hyper V Server 2012 Vritual Switch Canot > change/remove**** > > ** ** > > One of our hardware team decided that our Hyper-V host should have their > firmware upgraded.**** > > ** ** > > They are running Hyper-V Server 2012.**** > > ** ** > > It would appeart the in doing so the network card names or id's htat are > passed through ave changed, and as such when they started up the networking > wasnt working.**** > > ** ** > > After much fun in Powershell, and not being able to configure the existing > virtual switch I have managed to create new Virtual Switches on all the > hosts and set the netowrking back the way it was and all is well, guest > VM's all working fine.**** > > ** ** > > And the original virtual switch I had to then configure to private, and > then i got the error about file not found but eventually it let me remove > it.**** > > ** ** > > Is this common that when the BIOS is updated the Built in NIC ID's > Change???**** > > ** ** > > Also will this happen when we upgrade the NIC firmware cos guess what a > strange issue we have been having with netowrk perfrormance has been > identified as being resolved in a firmware update????**** > > ** ** > > Thanks**** > > ** ** > > Graeme**** > > > **** > > ** ** > > -- > Good news everyone, you have just received an e-mail from me! **** > -- Good news everyone, you have just received an e-mail from me!
