<div>
Cheers for reply.<br />
<br />
We're replacing some Proliant dl380 g5s with some g8s. They're attached to both an EVA4400 and a P2000. &nbsp;Those Ciscos sound like the biz for the HBAs!<br />
<br />
I don't think we can do the same with our HPs. <br />
<br />
Hmmmm .... maybe we just get someone in to redo the zoning.
</div>


<div>
Yes you will have to re-do the zoning. <br />
Yes i don't think HP servers are capable of it so you will have to do it the hard way.<br />
If you plan it well and take all the correct measures you will spend very less time in doing it and will not face any issues.
</div>


<div>
<div class="content wysiwyg-content">
Hi, <br />
<br />
We have a couple of 5.0.u3 ESXi hosts that we want to replace in a prod cluster. We were thinking of building the new hosts offline with the same name and then shutting down the old hosts and adding the new. Sounds easy enough but they're attached to a FC SAN so there's Zoning involved and that's the part we're not certain on. &nbsp;<br />
<br />
How best could we do this for folk with limited zoning knowledge. &nbsp;The rest we should be fine with.<br />
<br />
Thanks
</div>
</div>


Hi, 

We have a couple of 5.0.u3 ESXi hosts that we want to replace in a prod cluster. We were thinking of building the new hosts offline with the same name and then shutting down the old hosts and adding the new. Sounds easy enough but they're attached to a FC SAN so there's Zoning involved and that's the part we're not certain on.  

How best could we do this for folk with limited zoning knowledge.  The rest we should be fine with.

Thanks

Cheers for reply.

We&#39;re replacing some Proliant dl380 g5s with some g8s. They&#39;re attached to both an EVA4400 and a P2000.  Those Ciscos sound like the biz for the HBAs!

I don&#39;t think we can do the same with our HPs. 

Hmmmm .... maybe we just get someone in to redo the zoning.

Yes you will have to re-do the zoning. 
Yes i don&#39;t think HP servers are capable of it so you will have to do it the hard way.
If you plan it well and take all the correct measures you will spend very less time in doing it and will not face any issues.

Replacing ESXi hosts

Hi, 

We have a couple of 5.0.u3 ESXi hosts that we want to replace in a prod cluster. We were thinking of building the new hosts offline with the same name and then shutting down the old hosts and adding the new. Sounds easy enough but they&#39;re attached to a FC SAN so there&#39;s Zoning involved and that&#39;s the part we&#39;re not certain on.  

How best could we do this for folk with limited zoning knowledge.  The rest we should be fine with.

Thanks

Microsoft server applications are those applications developed specifically, but not necessarily exclusively, on the Windows Server platform. In addition to well-known products like SQL Server, Exchange, Internet Information Services (IIS), Microsoft Dynamics, Forefront, Lync and Sharepoint, they include applications like Skype, BizTalk, Hyper-V, Groove and Commerce Server. Server applications are managed with the Microsoft System Center.

Microsoft Server Apps

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.

VMware

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.