Thank you again. Unfortunately, it seems I am misunderstanding.
When you say that both of my ports do not support changing the HW
address, I assume that means my NICs do not allow their MAC addresses
to be changed. However, it seems I can change their addresses via the
ip command with no problem (see below).
I guess I need details on what NIC card requirements teamd has. I can
buy new cards, if I know what I'm looking for.
Thank you for your patience,
J.L. Hill
---------------------
# ip add ls eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.0.101/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
# ifdown eth0
Killed old client process
...
Listening on LPF/eth0/50:e5:49:ec:d6:3f
Sending on LPF/eth0/50:e5:49:ec:d6:3f
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
# ip link set eth0 address 02:01:02:03:04:08
# ip link ls eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
mode DEFAULT group default qlen 1000
link/ether 02:01:02:03:04:08 brd ff:ff:ff:ff:ff:ff
root@thor:/home/jh# ip addr ls eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
group default qlen 1000
link/ether 02:01:02:03:04:08 brd ff:ff:ff:ff:ff:ff
On Mon, Jan 5, 2015 at 12:14 PM, Flavio Leitner <fbl(a)sysclose.org> wrote:
On Monday, January 05, 2015 10:24:13 AM PanaColina wrote:
> Thank you for your response -- testing with activebackup pointed
> towards one problem:
>
> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Got link watch from port config.
> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Using sticky "0".
> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Failed to set port
> hardware address.
Either roundrobin or activebackup modes requires changing the HW
address for all ports. If that fails, the mode doesn't work.
It seems both your ports don't support that, unfortunately.
fbl