Hi,

Very nice wrap up! Thanks for that. I just have a stupid question: Is vPath still supported only on VSG, ASA 1000V, and v-WAAS or have other network services been added to the list, please? It was recommended to adjust MTU sizes of the network path between VEM's to allow for the overhead on MTU slapped on by vPath. If i recall correctly, the MTU overhead varies according to encapsulation(62 bytes for VLAN's and 82 for Layer 3?)...

If I may ask, do you envisage challenges on administering of routing protocols for a long term within vPath enabled large scale data centers at all? If so, what would be the cons (the pros are mentioned above :-)), please, besides the administering of MTU size for the various protocol encapsulations?

IMHO, the Virtual Security Gateway (VSG) is an excellent NX-OS-based virtual network service node supporting policy-based traffic access control to virtualized server environments and I "think" (I maybe wrong though) that VSG is also referred to as a "compute firewall".

The good part is the VSG and VNMC can be installed as virtual machines using bootable ISO files or through OVF files with help of the VMware vCenter.

Very well done when one looks at all the complicated technical stuff pooled in by various partners (Cisco, VMware etc.)and served up aligned towards total customer satisfaction.

Cheers

santanu