cancel
Showing results for 
Search instead for 
Did you mean: 
Alex_Bron
Mission Specialist
Mission Specialist
  • 358 Views

Bug in chapters on Automating Network Teaming

In the chapters 2.5/2.6 on Automated Network Teaming, they consistently forget to bring up the slave devices when they stop and start the team0 device. For example: in the lab exercise 8, the teamtune playbook disables the team0 device and brings up the team0 connection:

    - name: Disconnect team interface
      command: nmcli dev dis team0

    - name: Reactivate team interface
      command: nmcli con up team0

Next in 9 the state of team0 is inspected:

[root@servera ~]# teamdctl team0 state
setup:
runner: activebackup
runner:
active port:

Which is correct: only the master is brought up but none of the slaves. But in 10 they can ping the 192.168.0.254 address???

This happens both in the descriptive text of 2.5 and in the exercise of 2.6.

 

Labels (1)
0 Kudos
0 Replies
Join the discussion
You must log in to join this conversation.