« Introducing Target Driven Zoning (TDZ) | Main | FC and FCoE versus iSCSI – “Network-centric” versus “End-Node-centric” provisioning »



Feed You can follow this conversation by subscribing to the comment feed for this post.

Waldemar Pera

By default, channel-group mode is On without LACP. If you enable globally LACP and set channel-group to Active, everything is ok. (http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/EtherChannel.html).

Another workaround, it's off LACP on Linux side.

Erik Smith

Hi Waldemar, that link is a great reference and I probably should have included a couple of switch configuration references in my originl post.

However, the point of the blog post was to explain why the Partner MAC Address was zero and (to me at least) the link between LACP and this field was not immediately apparent. Based on the feedback I've already received, it seems like I may be in the minority here!

Thanks for taking the time to comment!


Kevin Joubert

Is the "Partner MAC Address" sort of a virtual hardware address for the connection pair? I have a strange situation where two systems are showing the same Partner MAC Address on their respective bond0 interfaces. I am thinking that these somehow the 4 ports (2 connections in each bond0 on each server) are portchanneled together.. and they shouldn't be I don't think.


Hi Kevin, I believe the Partner MAC Address is the MAC Address of the switch or switch pair that you are connecting to. If I noticed the same Partner MAC Address on two different servers that were connected to the same switch / switch pair, I wouldn't be concerned...

The comments to this entry are closed.


  • This is not an official EMC blog.
    The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC nor does it constitute any official communication of EMC.