Advanced Network Configuration
The network interface(s) and IP configuration(s) are managed directly in the Operating Systems.
Our deployment use the configured interface configuration but will also allow different form of security hardening in term of firewall and network interfaces segregation.
The deployment allows to configure services binding to dedicated network interfaces.
The Internal Firewall can filter and protect network flows between different network security layers.
Important Notes:
Hostname should have a maximum of 15 characters if AD authentication is set.
If DNS are not well configured and if the system cannot resolve properly the DNS - IP resolution, the system will not work as expected.
Network Interface - Standard Configuration
The solution will be used by the default network interface and associated IP configuration. These settings will be used to bind each different service of Nodeum.
Network Interface - Service mapping
Each service can be bind to specific network interface.
Nodeum Ansible Installation playbook needs to be reapplied once the inventory files have been modified accordingly to the mapping you need.
In the hosts information file, you can find in the extracted Nodeum installation package.
Follow this file(s): /inventory/hosts_vars/srv1.
It contains the different configurations and settings that will be applied the o host.
There is a section to define the service binding.
By default, the iface_name parameter is using the main network interface, but this information can be overwritten.
Different parameters to bind a list of services to a specific interface name.
Description of each parameter:
smb_iface_name
SAMBA
nfs_iface_name
NFS
rails_iface_name
RAILS
solr_iface_name
SOLR
catalog_iface_name
CATALOG INDEXER
Last updated