[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 330
  • Last Modified:

Another ProLiant ESXi 4>5 upgrade question

So, I've been able to upgrade my ProLiant DL360 G5 thanks to the HP VMWare boot CD suggested in this thread: http://www.experts-exchange.com/Software/VMWare/Q_27651729.html

But now I wanted to do the same on a ProLiant DL380 G6 and got this error message:

screenshot
How do I resolve this? Any suggestions?

Thanks!
0
Xeronimo
Asked:
Xeronimo
  • 5
  • 4
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
are you using the HP version of ESXi 5.0?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If this is OEM HP ESXi 5.0 just continue with installation.
0
 
XeronimoAuthor Commented:
@hanccocka:

Yes, I'm using the HP version of ESXi 5.0
It's the same CD I used to upgrade that other ProLiant yesterday. There I didn't get those error messages (although I got the same error message in the Update Manager!), is that normal?

And so what you're saying is that I should force the migration (that's how the option is called)? I can't do it right now though ... the window of opportunity has closed ... tomorrow or on the weekend then.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Correct, its likely other drivers have been installed in the previous installation.
0
 
XeronimoAuthor Commented:
Hm, are you sure then that forcing the migration won't make me lose network access (since one of the problematic drivers is apparently the NIC one)?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you got three options

1. do not upgrade
2. fresh virgin install
3. proceed with upgrade

any upgrade carrys a risk, and you will need to check upgraded server afterwards to check configuration before production.

resolving network issues, adding drivers, vswitches is straightforward.
0
 
XeronimoAuthor Commented:
a. Ok, I'll try the upgrade (and pray ;)). But what if I need to add drivers later (for example to get network connectivity) again, how would I do that?
b. In the case of a fresh install I also need to redefine all the storage connections etc, right?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
a. upload the vib and install
b. you need to recreate everything
0
 
XeronimoAuthor Commented:
I did a virgin fresh install and it worked.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now