VMware Cloud Community
sukid
Contributor
Contributor

After upgrade from esx 4.1 to esxi 5.0 I am no long able to ping the host


Help!

We have HP BL685c blade servers with esx 4.1 on them. Yesterday, I was trying to upgrade the esx4.1 to esxi5.0 with HP custom image esxi5.0 U1 ISO image. Everything seems working. except for two things.

1. Every reboot, it took around 30 minutes, it start to slow down after vmw_satp_eva loaded successfully.After this point, it took around 25 minutes.

2. Management network test fail.

We have HP BL685c and the fabric and HP fiber channel storage. I am thinking if there is something I need to configure after the esxi5.0 image was installed.

The host sees all four nics connected. I select the first one as the management nic and assign static IP to it.

Reply
0 Kudos
7 Replies
vmroyale
Immortal
Immortal

Note: Discussion successfully moved from VMware ESXi 5 to vSphere Upgrade & Install

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
Reply
0 Kudos
a_p_
Leadership
Leadership

Which EVA model do you use? Is it an EVA x400?

Do you have RAW devices configured? Booting with RAW devices - especially if used with MSCS - may slow down booting considerably.

André

Reply
0 Kudos
sukid
Contributor
Contributor

It is EVA8000. But, my problem is I cannot connect to the host. I move all VMs. There is no VMs on this host.

Reply
0 Kudos
a_p_
Leadership
Leadership

The EVA8000 is not supported by ESXi versions later than 4.1. ESXi 5.x has new storage features built in (like VAAI) which are not supported by this model (at least I'm not aware of it).

André

sukid
Contributor
Contributor

Thank you for your prompt reply.

We are having a new HP storage coming this week. That is why we are trying to upgrade to esxi5. But, right now, the bigger problem that I have is the networking issue. Do you think if I install esxi 4.1 the network problem will also resolved?


Reply
0 Kudos
a_p_
Leadership
Leadership

Without going into details it's hard to say what's causing the issue. Maybe the network issue is just a result of other issues. Anyway, I'd stay with ESXi 4.1 as long as the host is still connected to the EVA. I'm currently doing a migration with a customer from an EVA 4000 to a new 3PAR 7200 and we are going to keep the hosts at version 4 for the migration (we planned to use HP's SAN Copy utility as well as Storage vMotion) and upgrade them once the LUNs/VMs are all on the new storage.

André

Reply
0 Kudos
sukid
Contributor
Contributor


I will talk to our networking team tomorrow. If they don't know why, I will down grade to esxi 4.1.

Thank you again.

Reply
0 Kudos