2. Software

2.1.1. Although the Network Manager is running on the frontend, and all nodes run the Node Manager, configuration changes are not applied to the adapters. I.e., the node ID is not changed according to what is specified in /etc/dis/dishosts.conf on the frontend.
2.1.2. The Network Manager on the frontend refuses to start.
2.1.1. Although the Network Manager is running on the frontend, and all nodes run the Node Manager, configuration changes are not applied to the adapters. I.e., the node ID is not changed according to what is specified in /etc/dis/dishosts.conf on the frontend.
2.1.2. The Network Manager on the frontend refuses to start.
2.1.1.

Although the Network Manager is running on the frontend, and all nodes run the Node Manager, configuration changes are not applied to the adapters. I.e., the node ID is not changed according to what is specified in /etc/dis/dishosts.conf on the frontend.

The adapters in a node can only be re-configured when they are not in use. This means, no adapter resources must be allocated via the dis_irm kernel module. To achieve this, make sure that upper layer services that use dis_irm (like dis_sisci and dis_supersockets) are stopped.

> sc stop dis_nodemgr
> sc stop dis_irm 
...
> sc start dis_irm 
...
> sc start dis_nodemgr
...
2.1.2.

The Network Manager on the frontend refuses to start.

In most cases, the interconnect configuration c:\WINDOWS\system32\drvers\etc\dis\dishosts.conf is corrupted. This can be verified with the command testdishosts. It will report problems in this configuration file, as in the example below:

# testdishosts

socket member node-1_0 does not represent a physical adapter in dishosts.conf

DISHOSTS: signed32 dishostsAdapternameExists() failed

In this case, the adapter name in the socket definition was misspelled. If testdishosts reports a problem, you can either try to fix c:\WINDOWS\system32\drvers\etc\dis\dishosts.confmanually, or re-create it with the Dolphin Netwowork Configurator GUI, dis_netconfig or the command line version of the Dolphin Network Configurator, dis_mkconf.

If this does not solve the problem, please check c:\WINDOWS\system32\drvers\etc\dis\log\scinetworkmanager.log for error messages. If you can not fix the problem reported in this logfile, please contact Dolphin support providing the content of the logfile.