If I'm not intending to boot from an iSCSI array, do I need to go the extra step and configure iSCSI vNIC's for use within vSphere or am I safe with just creating standard vNic's with the appropriate settings for Jumbo Frames, etc...?
I believe before UCS 2.0 that was sufficient, but from talking with TAC it sounds like the iSCSI vNIC is now mandatory with vSphere..
Is there any added benefit to creating iSCSI vNIC's (beyond booting from an iSCSI array.)
Just to add to Louis, the iSCSI vNIC creates a hardware initiator within the host (required for iSCSI boot). For post-boot iSCSI access you can use the built-in vSphere software iSCSI initiator which just binds to the parent vmknic & vNIC interface.
When configuring your jumbo frames, ensure you test ping with a jumbo packet to ensure efficient transport. Many times there's a switch or interface that's missed which renders a jumbo MTU inefficient.
Scott Lowe put together a create article on Jumbo frames w/ VMware. It's drafted against vSphere 4, but still applies to vSphere 5.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...