Network Configuration
Recent versions of the AMD software have removed the network configuration features from rtminst.
You can use the command nmtui to start a text interface to configure the communications port.
Commands
ip address
Lists all the network interfaces on the server, so you can determine which one to configure, rtminst is also handy to do this with.
lo is the loopback interface, ignore it, it's no use for communications outside of the AMD server.
rtminst
Go to option 1 "Interface identification and network setup", and review the available interfaces.
Check the interfaces for which ones as 'UP' (using ip address), or have a link detect flag of 'Y' (using rtminst). Typically Linux names the interfaces in a sensible order based on the hardware IDs, the on board interfaces first, then the add on cards, and in the same port order, i.e. on board port 1 will be first, on board port 2 second, add on card 1 port 1 third, etc. So you can usually infer the correct port, if not, some cable swapping may be required, make sure only the communications port you want to use has an active cable plugged into it.
In the above screen shots we've determined ens32 is the interface to use.
Use this method to set up an address temporarily - until the next reboot, so you can SSH/SCP for remote admin copying updates/patches etc. The address will be lost when the AMD is rebooted.
If DHCP is available on your comms network, for a temporary address, the command is simply
ifup ens32
Once complete, run ip address again to see the address received.
ip address
In this case DHCP has given ens32 the address 192.168.93.128.
If there's no DHCP available, or you have a static addressed assigned for the AMD, you can configure it. For example to configure the IP address 192.168.93.128 with a mask of 255.255.255.0 (/24), and a default gateway of 192.168.93.1:
ip address add 192.168.93.128/24 dev ens32
route add default gw 192.168.93.1
Display the route table.
route -n
The above commands for temporary addresses will be forgotten whenever the server is restarted, to make the configuration permanent, the following configuration file needs to be created.
The interface configuration files are found in: /etc/sysconfig/network-scripts/ and are named in the following format: ifcfg-interfacename, e.g. ifcfg-ens32.
Use vi to edit/create the config file.
vi /etc/sysconfig/network-scripts/ifcfg-ens32
Example for a static address of 192.168.93.128/24 192.168.93.1 gateway, and the Google DNS servers (change them to the customers internal servers).
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.93.128
PREFIX=24
GATEWAY=192.168.93.1
DNS1=8.8.8.8
DNS2=8.8.4.4
DEFROUTE=yes
# Disable ipv6 #
IPV6INIT=no
NAME=ens32
DEVICE=ens32
ONBOOT=yes
Save and exit vi <ESC>:wq.
Reload the configuration file by stopping and starting the interface. Or you could reboot the server.
ifdown ens32 && ifup ens32
After adding/changing IP addresses you may need to restart the ssh daemon before you can SSH or SCP to the server.
systemctl restart sshd