Skip to content

Commit 0117080

Browse files
committed
BZ:1811047 - add network teaming example
1 parent 9e66c2c commit 0117080

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

modules/installation-user-infra-machines-static-network.adoc

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -208,6 +208,25 @@ ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:bond0.100:none
208208
bond=bond0:em1,em2:mode=active-backup
209209
vlan=bond0.100:bond0
210210
----
211+
212+
a|Optional: Network teaming can be used as an alternative to bonding by using the `team=` parameter. In this example:
213+
214+
* The syntax for configuring a team interface is: `team=name[:network_interfaces]`
215+
+
216+
_name_ is the team device name (`team0`) and _network_interfaces_ represents a comma-separated list of physical (ethernet) interfaces (`em1, em2`).
217+
218+
[NOTE]
219+
====
220+
Teaming is planned to be deprecated when {op-system} switches to an upcoming version of {op-system-base}. For more information, see this https://access.redhat.com/solutions/6509691[Red Hat Knowledgebase Article].
221+
====
222+
223+
a|
224+
To configure a network team:
225+
226+
----
227+
team=team0:em1,em2
228+
ip=team0:dhcp
229+
----
211230
endif::ibm-z-kvm[]
212231
|===
213232
ifndef::ibm-z,ibm-z-kvm,ibm-power[]
@@ -432,4 +451,4 @@ ifeval::["{context}" == "installing-ibm-power"]
432451
endif::[]
433452
ifeval::["{context}" == "installing-restricted-networks-ibm-power"]
434453
:!ibm-power:
435-
endif::[]
454+
endif::[]

0 commit comments

Comments
 (0)