Jagath Yes, macvtap and vmotion is supported. There is no host component like VEM to load in case of VM-FEX for KVM. Also in case of KVM libvirt is also used for the mgmt piece currently. Thanks --Manish ... View more

Dani As I communicated to you in the unicast thread, this feature of full blown blade/SP failover has not made it in the list of upcoming features. A matter of feature prioritization is what it eventually boils down to. I will not go so far as to say it will be never, but its not in the immediate timeframe. Thanks --Manish ... View more

Hi, The subject of the thread is VN-Link in hardware (VM-FEX) so thats what I am going to assume the questions are on as VSM/VEM terminology is used with Nexus1000v too and that forwarding behavior is different. >traffic between two VM's on the same ESX server (on same VLAN) wouldnt be switched through the uplink switch right ? It will >be directly switched by VEM/ESX locally through its kernel ? No - ALL traffic goes upstream to the FI's which is where the switching port (veth) is instantiated. VM-A and VM-B on the same ESX host utilizing VM-FEX, traffic goes upstream to get switched. VM-A and VM-B on 2 diff ESX hosts, then ofcourse they have to. See inserted png file where both the scenarios I mentioned above are given. > Can you confirm me if my understanding is right on the following scenarios: > 1) Traffic between 2 hosts in same ESX server , same VLAN - switched locally by ESX (doesnt go upstream) No - in VM-FEX mode there is no local switching. >2) Traffic between 2 hosts in diff ESX servers, same VLAN - switched to uplink (VM-DATA) and layer 2 forwarding to other ESX Yes > 3) Traffic between 2 hosts in same ESX, different VLAN - forwarded to uplink since layer 3 isnt defined in VSM.. In my case it >goes to Dist1 switch and comes back Yes - inter VLAN requires L3 which the FI's are not (yet). Thanks --Manish ... View more

Chandra I don't believe I understand the issue then. If ethernet connectivity is the issue you ran into on HA test you shouldn't have had to reload ESX hosts to get connectivity back for the disk errors. As it is SAN based, connectivity to 3750 is only for IP/Ethernet. We do recommend port channeling upstream where possible. So if you have stacked switches upstream, port channel (LACP) from the FI's to them. It is not a requirement as in EHM there is always active/active usage of links but port channeling means the least number of moving parts when things change (links flap etc) plus minimizing number of hops for east-west blade traffic if its vPC upstream. Am unsure why criss cross to diff modules within the stack didn't work for you. Maybe you can contact me offline and I can look at your config etc. Thanks --Manish ... View more

Chandra Will have to break this down to narrow down on the issue. Fabric Failover *only* applies to Ethernet traffic. For FC, SAN multipathing applies and has nothing to do with Fabric failover capability of the M81KR. Where is your VMFS at as you mentioned disk errors? If its on the SAN, need to troubleshoot it from the SAN multipathing perspective i.e Manage Paths under VCenter and seeing the paths and target/lun etc on both paths. If its on NFS/iSCSI (i.e Ethernet), then we are looking at the soft switch and vNICs. For ESX soft switch environment (Nexus1000v/ DVS/ vSwitch), the recommendation is to *not* have Fabric Failover enabled on the vNICs i.e having one on each side (in pairs) with non-FF to provide load sharing and redundancy. What does your config look likes from a vNIC perspective if its the ethernet path? Thanks --Manish ... View more

Hubert Unfortunately we do not have a public document on the default CoPP functionality. The CoPP is in place for traffic form 10 GB ports to the SUP only. In EHM of operation, we do not process BPDU's etc and have very set rules for traffic handling to name a few. For the external 1 gig mgmt port, you will need to protect it via a firewall or acls. We do have a list of ports which are opened to come up with the firewall or acl config. Hope it helps and apologize for the non availability of an external doc on this. --Manish ... View more

Radek Have you tried installing the VEM using command line rather than VUM? Thanks --Manish ... View more