...
First of all take note of the IP addresses and the interfaces name used by the VM for the management and data networks (192.168.60.x and 192.168.61.x) ) and the relevant interfaces
...
If in the compute node there is a dedicated interface (like cld-np-19 eno3) for data lan (use
Use the correct ip and interface name in the commands below changing the name and ip with yours (change "eno3" and "192.168.61.129")
Code Block |
---|
[root@cld-np-19 ~]# nmcli con add type ethernet ifname eno3 mtu 9000 (change here the interface name, eno3, with your one)
[root@cld-np-19 ~]# nmcli con mod eno3 ipv4.method manual ipv4.addr "192.168.61.129/24"
[root@cld-np-19 ~]# nmcli con up eno3
[root@cld-np-19 ~]# nmcli con mod eno3 802-3-ethernet.mtu 9000
[root@cld-np-19 ~]# ip link set eno3 mtu 9000 |
...
If the interfaces used the addresses with the tagged network (VLAN 302 andl VLAN 301 in same interface) use these commands (remember to use .
Use the correct IP int ip and interface name the commands below (change "enp2s0f0.302" and "192.168.61.129")
Code Block |
---|
[root@cld-nl-24 ~]# nmcli con add type vlan ifname enp2s0f0.302 dev enp2s0f0 id 302
[root@cld-nl-24 ~]# nmcli con mod vlan-enp2s0f0.302 ipv4.method manual ipv4.addr "192.168.61.129/24"
[root@cld-np-24 ~]# nmcli con up vlan-enp2s0f0.302
[root@cld-np-24 ~]# nmcli con mod vlan-enp2s0f0.302 802-3-ethernet.mtu 9000
[root@cld-np-24 ~]# ip link set enp2s0f0 mtu 9000
[root@cld-np-24 ~]# ip link set enp2s0f0.302 mtu 9000 |
The address to be used must be the original one
...
In foreman move the host under the ComputeNode-Prod_Yoga hostgroup.el9 hostgroup
Run puppet manually:
Code Block | ||
---|---|---|
| ||
puppet agent -t |
...