4 Responses

  1. Ian Erikson
    Ian Erikson at |


    Nice article.

    To add, I believe you would also want to create an appliance port network control policy. The desired policy is to “warn” instead of shut down. The reason for this is that even if you lose all a fabric interconnect(s) uplinks, the servers will still be able to communicate with storage. While clients will not be able to reach servers, its always better to let the servers continue to make their storage reads and writes.

  2. Why You Should Pin vMotion Port Groups In Converged Environments | Wahl Network

    […] the use of either chassis switches (as with an HP c7000 BladeSystem) or domain switches (as with Cisco UCS Fabric Interconnects). In these situations, there exists the ability to keep the vMotion traffic from ever egressing the […]

  3. Enterprise NAS with vSphere 5.1, EMC VNX VG8 & Symmetrix VMAX 20K | vcdx133.com

    […] Attach NAS to Cisco UCS as Appliance Ports […]

  4. Resolving ENM Source Pinning Failed Errors with Appliance Ports - Wahl Network

    […] within a Cisco UCS environment is by creating an Appliance Port on the Fabric Interconnects. I wrote about this a long time ago for those looking to consume NFS storage with a directly attached NAS box, and I would imagine […]

Share your point of view!