interface_teaming
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
interface_teaming [2021/04/08 22:15] – [Edit Interface Files] walkeradmin | interface_teaming [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 159: | Line 159: | ||
====Testing==== | ====Testing==== | ||
\\ | \\ | ||
- | + | Firstly we need to know if all the interfaces came up correctly, to test this use the following: | |
- | + | \\ | |
- | + | ip link show |grep "state UP" | |
+ | \\ | ||
+ | \\ | ||
+ | In the case of the test server this shows the following output: | ||
+ | \\ | ||
+ | < | ||
+ | 2: eth0: < | ||
+ | 3: eth1: < | ||
+ | 4: mngt: < | ||
+ | </ | ||
+ | \\ | ||
+ | We can see that the team interface (logical) is present and that the two physical interfaces eth0 and eth1 are present. | ||
+ | \\ | ||
+ | \\ | ||
+ | To see the status of the interfaces we can use the follwoing command: | ||
+ | \\ | ||
+ | \\ | ||
+ | teamdctl mngt state (where mngt is the name of the team) | ||
+ | \\ | ||
+ | \\ | ||
+ | This shows the following output: | ||
+ | \\ | ||
+ | < | ||
+ | setup: | ||
+ | runner: activebackup | ||
+ | ports: | ||
+ | eth0 | ||
+ | link watches: | ||
+ | link summary: up | ||
+ | instance[link_watch_0]: | ||
+ | name: ethtool | ||
+ | link: up | ||
+ | down count: 0 | ||
+ | eth1 | ||
+ | link watches: | ||
+ | link summary: up | ||
+ | instance[link_watch_0]: | ||
+ | name: ethtool | ||
+ | link: up | ||
+ | down count: 0 | ||
+ | runner: | ||
+ | active port: eth0 | ||
+ | </ | ||
+ | \\ | ||
+ | It can be see that the two interfaces (eth0 and eth1) have a link: up. At the bottom the runner is listed as having eth0 as the active port. | ||
+ | \\ | ||
+ | \\ | ||
+ | To test the team simply ping an IP or Name, and unplug the interfaces one at a time, as long as one interface is connected your pings will continue. | ||
+ | \\ | ||
+ | \\ | ||
+ | Note: some switches take some time to detect that an interface has been plugged in, this might cause an outage in your pings, the switch may need to be reconfigured to mitigate this. | ||
+ | \\ | ||
+ | \\ | ||
+ | Lastly check the IP Addressing is as expected. Use the following command: | ||
+ | \\ | ||
+ | \\ | ||
+ | ip -br -c a | ||
+ | \\ | ||
+ | This will give a similar output to below: | ||
+ | \\ | ||
+ | < | ||
+ | lo | ||
+ | eth0 UP | ||
+ | eth1 UP | ||
+ | mngt | ||
+ | </ | ||
+ | \\ | ||
+ | Above we can see that the team mngt has the IP details, and that eth0 and eth1 are simply listed as being UP. | ||
+ | \\ | ||
+ | \\ | ||
interface_teaming.1617916539.txt.gz · Last modified: 2023/03/09 22:35 (external edit)