This is a standard setup issue. The ONLY ports that should be in that list (in other words, based on the output, in the Default Broadcast-Domain) are connected ports on the same physical network.
Different customers have different setups. With that, at a minimum, the broadcast-domain should include e0M from each node. *IF* you have e0c/e0d/e0e/e0f connected and are on the same physical network (whatever networ e0M is on, like 192.168.1.1 - 192.168.1.4) then it will work. If it is not, then it is entirely possible when the port fails (or the plug is pulled) it will go to another port and advertise there (Reverse ARP) that the IP address has moved.
I have seen this event transpire before and the cluster became unavailbel through the cluster_mgmt port.
Please correct your Broadcast-domain(s) and try again.
Typical Broadcast domains seperate things out. For example:
Default (MTU 1500):
node1:e0M
node2:e0M
node3:e0M
node4:e0M
NFS (MTU 900):
node1:a0a-101
node2:a0a-101
node3:a0a-101
node4:a0a-101
CIFS (MTU 1500):
node1:a0a-201
node2:a0a-201
node3:a0a-201
node4:a0a-201
Provide more detais if this does not work.
Suggestions include:
"broadcast-domain show ; ifgrp show"
Also
"net int show -failover"
(but please try to copy/paste if you can instead of a "picture". I know, some places cannot, but if you can, it is easier!