Skip to content

Commit c31aae1

Browse files
committed
HCIDOCS-139: Added static IP example..
1 parent 89dba97 commit c31aae1

File tree

1 file changed

+30
-9
lines changed

1 file changed

+30
-9
lines changed

modules/ipi-install-configuring-networking.adoc

Lines changed: 30 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ You can also configure networking from the web console.
1717

1818
.Procedure
1919

20-
. Export the bare-metal network NIC name:
20+
. Export the bare-metal network NIC name by running the following command:
2121
+
2222
[source,terminal]
2323
----
@@ -30,6 +30,8 @@ $ export PUB_CONN=<baremetal_nic_name>
3030
====
3131
The SSH connection might disconnect after executing these steps.
3232
====
33+
34+
.. For a network using DHCP, run the following command:
3335
+
3436
[source,terminal]
3537
----
@@ -39,20 +41,38 @@ $ sudo nohup bash -c "
3941
# RHEL 8.1 appends the word \"System\" in front of the connection, delete in case it exists
4042
nmcli con down \"System $PUB_CONN\"
4143
nmcli con delete \"System $PUB_CONN\"
42-
nmcli connection add ifname baremetal type bridge con-name baremetal bridge.stp no
44+
nmcli connection add ifname baremetal type bridge <con_name> baremetal bridge.stp no <1>
4345
nmcli con add type bridge-slave ifname \"$PUB_CONN\" master baremetal
4446
pkill dhclient;dhclient baremetal
4547
"
4648
----
49+
<1> Replace `<con_name>` with the connection name.
4750

48-
. Optional: If you are deploying with a provisioning network, export the provisioning network NIC name:
51+
.. For a network using static IP addressing and no DHCP network, run the following command:
52+
+
53+
[source,terminal]
54+
----
55+
$ sudo nohup bash -c "
56+
nmcli con down \"$PUB_CONN\"
57+
nmcli con delete \"$PUB_CONN\"
58+
# RHEL 8.1 appends the word \"System\" in front of the connection, delete in case it exists
59+
nmcli con down \"System $PUB_CONN\"
60+
nmcli con delete \"System $PUB_CONN\"
61+
nmcli connection add ifname baremetal type bridge con-name baremetal bridge.stp no ipv4.method manual ipv4.addr "x.x.x.x/yy" ipv4.gateway "a.a.a.a" ipv4.dns "b.b.b.b" <1>
62+
nmcli con add type bridge-slave ifname \"$PUB_CONN\" master baremetal
63+
nmcli con up baremetal
64+
"
65+
----
66+
<1> Replace `<con_name>` with the connection name. Replace `x.x.x.x/yy` with the IP address and CIDR for the network. Replace `a.a.a.a` with the network gateway. Replace `b.b.b.b` with the IP address of the DNS server.
67+
68+
. Optional: If you are deploying with a provisioning network, export the provisioning network NIC name by running the following command:
4969
+
5070
[source,terminal]
5171
----
5272
$ export PROV_CONN=<prov_nic_name>
5373
----
5474

55-
. Optional: If you are deploying with a provisioning network, configure the provisioning network:
75+
. Optional: If you are deploying with a provisioning network, configure the provisioning network by running the following command:
5676
+
5777
[source,terminal]
5878
----
@@ -69,34 +89,35 @@ $ sudo nohup bash -c "
6989
+
7090
[NOTE]
7191
====
72-
The ssh connection might disconnect after executing these steps.
92+
The SSH connection might disconnect after executing these steps.
7393
74-
The IPv6 address can be any address as long as it is not routable via the bare-metal network.
94+
The IPv6 address can be any address that is not routable through the bare-metal network.
7595
7696
Ensure that UEFI is enabled and UEFI PXE settings are set to the IPv6 protocol when using IPv6 addressing.
7797
====
7898

79-
. Optional: If you are deploying with a provisioning network, configure the IPv4 address on the provisioning network connection:
99+
. Optional: If you are deploying with a provisioning network, configure the IPv4 address on the provisioning network connection by running the following command:
80100
+
81101
[source,terminal]
82102
----
83103
$ nmcli connection modify provisioning ipv4.addresses 172.22.0.254/24 ipv4.method manual
84104
----
85105

86-
. `ssh` back into the `provisioner` node (if required):
106+
. SSH back into the `provisioner` node (if required) by running the following command:
87107
+
88108
[source,terminal]
89109
----
90110
# ssh kni@provisioner.<cluster-name>.<domain>
91111
----
92112

93-
. Verify the connection bridges have been properly created:
113+
. Verify that the connection bridges have been properly created by running the following command:
94114
+
95115
[source,terminal]
96116
----
97117
$ sudo nmcli con show
98118
----
99119
+
120+
.Example output
100121
[source,terminal]
101122
----
102123
NAME UUID TYPE DEVICE

0 commit comments

Comments
 (0)