NetWitness Nodex host with NIC Bonding not being added to Hosts page due to a 'Failed to find hostname for host' error.

[#1]

Article Number

000003247

Applies To

NetWitness Product Set: NetWitness Logs & Network
NetWitness Product/Service Type: Archiver, Log Decoder, Decoder, Concentrator
NetWitness Version/Condition: 12.3.1 and Above
Platform: CentOS/AlmaLinux

Issue

When a new NodeX server is installed with NIC bonding configuration and trying to add it on the Hosts page after discovery, the host will not be added and the following error will appear.

/var/log/netwitness/orchestration-server/orchestration-server.log:

2024-12-02 12:26:36,826 [                   sync-exec-4] ERROR       TaskManagement|Execution of '674d59e38e88ca0f8ce6fca5' failed
java.lang.IllegalStateException: Failed to find hostname for host d6eebb37-cfc2-4ece-b195-c3565255a282
	at com.google.common.base.Preconditions.checkState(Preconditions.java:590)
	at com.rsa.asoc.orchestration.salt.handler.ProvisionHostTaskHandler.lookupAndSetHostName(ProvisionHostTaskHandler.java:142)
	at com.rsa.asoc.orchestration.salt.handler.ProvisionHostTaskHandler.lambda$execute$1(ProvisionHostTaskHandler.java:114)
	at org.springframework.retry.support.RetryTemplate.doExecute(RetryTemplate.java:329)
	at org.springframework.retry.support.RetryTemplate.execute(RetryTemplate.java:209)
	at com.rsa.asoc.orchestration.salt.handler.ProvisionHostTaskHandler.execute(ProvisionHostTaskHandler.java:113)
	at com.rsa.asoc.orchestration.task.SyncTaskExecutionService.execute(SyncTaskExecutionService.java:87)
	at com.rsa.asoc.orchestration.task.SyncTaskExecutionService.lambda$submit$0(SyncTaskExecutionService.java:71)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at com.rsa.asoc.orchestration.task.SyncTaskExecutionService.lambda$submit$1(SyncTaskExecutionService.java:71)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
2024-12-02 12:26:36,829 [unchMessageListenerContainer-2] INFO       SystemOperation|ProvisionHostTask Failed, removing the key d6eebb37-cfc2-4ece-b195-c3565255a282

Cause

This issue occurs with Nodex servers that have NIC bonding and is caused by missing GATEWAY details in the interface configuration

Resolution

Please add GATEWAY parameter while adding details for NIC bonding configuration in the Nodex server.

Add the following attributes in the interface configuration file /etc/sysconfig/network-scripts/ifcfg-eth0:

DEVICE=eth0
TYPE=Bond
BONDING_MASTER=yes
IPADDR=<ip address of the host>
NETMASK=<subnet NETMASK>
GATEWAY=192.x.x.x
BONDING_OPTS="mode=1 miimon=100"
BOOTPROTO=none
NAME=eth0
ONBOOT=yes

Please use https://community.netwitness.com/t5/netwitness-platform-hardware/series-6-hardware-setup-guide/ta-p/572346 for detailed steps on NIC bonding configuration.