...
| Note |
|---|
The gateway configuration can break up the communication between the server and your workstation. Take care to check both before applying. |
| Anchor | ||||
|---|---|---|---|---|
|
Both the below procedures are possible via console access, using the SSH internal server. Gain a privilege access to the console using the "root" user.
2.1.3.1 Assign an IP address to each NIC
To manually assign an IP address to a specified NIC you should use the iface-configure.sh script located in /data/bin/. It accept the card name, the IP address to assign and its netmask as in the following example:
| Code Block |
|---|
/data/bin/iface-configure.sh eth0 78.47.213.169 255.255.255.0 |
After you press the Enter key, the script configures and restarts the network configuration.
| Warning |
|---|
Beware that you pass to the script the correct values, else you could cut yourself out of the server. To configure the NIC properly you must pass the three options specified above. |
| Info |
|---|
If called with no options, then the above script returns the actual NICs configuration. |
After the script exits please restart the tomcat service as well using the command:
| Code Block |
|---|
/data/bin/control-http.sh stop start |
2.1.3.2 Assign a default gateway and DNS(es)
To manually assign an IP address to a specified NIC you should use the net-configure.sh script located in /data/bin/. It accept the gateway IP address, two DNS addresses and hostname, as in the following example:
| Code Block |
|---|
/data/bin/net-configure.sh 46.4.25.83 8.8.8.8 8.8.4.4 privateserver.local |
After you press the Enter key, the script configures and restarts the network configuration.
You can pass to the script just the gateway and the first DNS IP addresses. If secondary DNS is missing, pass the empty string ("") as parameters
| Warning |
|---|
Beware you passed the correct values to the script or else you could cut yourself out of the server. To configure the NIC properly you must pass almost the gateway and the first DNS server IP. |
If called with no options, then the script return the actual network configuration.
2.1.3.3 Restart Cluster Manager
After the script exits please restart the cluster manager (even if you are in "single server" deployment) using the following command:
| Code Block |
|---|
pcs cluster stop --force pcs cluster start |
2.1.4 Configure static routes
...