2. Software
Prev Chapter 14. FAQ Next

2. Software

2.1.1. The eXpressWare drivers (IRM etc) fails to load after it has been installed for the first time.
2.1.2. Although the Network Manager is running on the Cluster Management Node, and all Cluster Nodes run the Node Manager, configuration changes are not applied to the adapters. I.e., the NodeId is not changed according to what is specified in %WinDir%\system32\drivers\etc\dis\dishosts.conf on the Cluster Management Node.
2.1.3. The Network Manager on the Cluster Management Node refuses to start.
2.1.1. The eXpressWare drivers (IRM etc) fails to load after it has been installed for the first time.
2.1.2. Although the Network Manager is running on the Cluster Management Node, and all Cluster Nodes run the Node Manager, configuration changes are not applied to the adapters. I.e., the NodeId is not changed according to what is specified in %WinDir%\system32\drivers\etc\dis\dishosts.conf on the Cluster Management Node.
2.1.3. The Network Manager on the Cluster Management Node refuses to start.

2.1.1.

The eXpressWare drivers (IRM etc) fails to load after it has been installed for the first time.

Please follow the procedure below to determine the cause of the problem.

  1. Verify that the adapter card has been recognized by the machine. This can be done as follows:

    If this command does not show any output similar to the example above, the adapter card has not been recognized. Please try to power-cycle the system according to FAQ Q: 1.1.1. If this does not solve the issue, a hardware failure is possible. Please contact Dolphin support in such a case.

  2. Check the kernel message log for relevant messages.

    		    # dmesg | grep MXH
		    # dmesg | grep MVH

  3. If the driver still fails to load, please contact support and provide the driver's kernel log messages.

2.1.2.

Although the Network Manager is running on the Cluster Management Node, and all Cluster Nodes run the Node Manager, configuration changes are not applied to the adapters. I.e., the NodeId is not changed according to what is specified in %WinDir%\system32\drivers\etc\dis\dishosts.conf on the Cluster Management Node.

The adapters in a Cluster Node can only be re-configured when they are not in use. This means, no adapter resources must be allocated via the IRM driver. To achieve this, make sure that upper drivers or services that use IRM (like SISCI, dis_nodemgr, dis_fsd, dis_scps) are stopped.

> sc.exe stop dis_nodemgr
> sc.exe stop dis_fsd
> sc.exe stop dis_scps
...
> sc.exe start dis_scps
> sc.exe start dis_fsd
> sc.exe start dis_nodemgr

2.1.3.

The Network Manager on the Cluster Management Node refuses to start.

In most cases, the interconnect configuration %WinDir%\system32\drivers\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 %WinDir%\system32\drivers\etc\dis\dishosts.conf manually, or re-create it with the Dolphin Network 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 %WinDir%\system32\drivers\etc\dis\log\dis_networkmgr.log for error messages. If you can not fix the problem reported in this log file, please contact Dolphin support providing the content of the log file.

Prev Up Next
1. Dolphin PCI Express Hardware Home Appendix A. dis_admin Reference