From 0ff286adcfceb6bb3fa17924c42a664d59ddc516 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ji=C5=99=C3=AD=20Klime=C5=A1?= Date: Wed, 22 Jan 2014 17:47:37 +0100 Subject: [PATCH] man: add a Team example to nmcli-examples manual page --- man/nmcli-examples.xml | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/man/nmcli-examples.xml b/man/nmcli-examples.xml index 6b1268012..b5f958d62 100644 --- a/man/nmcli-examples.xml +++ b/man/nmcli-examples.xml @@ -190,6 +190,34 @@ $ nmcli con add type bond-slave ifname eth2 master mybond0 eth2. + Adding a team master and two slave connection profiles + +$ nmcli con add type team con-name Team1 ifname Team1 config team1-master-json.conf +$ nmcli con add type team-slave con-name Team1-slave1 ifname em1 master Team1 +$ nmcli con add type team-slave con-name Team1-slave2 ifname em2 master Team1 + + + + This example demonstrates adding a team master connection profile and two slaves. It is + very similar to the bonding example. The first command adds a master team profile, naming + the team interface and the profile Team1. The team configuration + for the master is read from team1-master-json.conf file. Later, you can + change the configuration with modify command + (nmcli con modify Team1 team.config team1-master-another-json.conf). + The last two commands add slaves profiles, both enslaved to Team1. + The first slave will be bound to em1 interface, the second to + em2. The slaves don't specify config and thus + teamd will use its default configuration. You will activate the whole setup + by activating both slaves: + +$ nmcli con add up Team1-slave1 +$ nmcli con add up Team1-slave2 + + By default, the created profiles are marked for auto-activation. But if another + connection has been activated on the device, the new profile won't activate + automatically and you need to activate it manually. + + Adding an ethernet connection profile with manual IP configuration