Dolphin installation for 2-node direct setup

Question:

I am trying to set my Dolphin connection for a 2-node direct communication. What are the things I should be aware of?

Answer:

All the required files can be found on Opal-RT's ftp site:     ftp://opal-rt.com/utils/Dolphin/

First read the HowToDolphinDXH510_v1_6.doc procedure attached. We suggest to use the Manual Installation instead of the Automatic Installation. Cluster configuration and Dolphin PX Adapter configuration are mandatory.

Before starting the installation procedure, if you happen to have more than one Dolphin card in one simulator, please remove the card that is not used for communication. This kind of setup can happen when you have one Dolphin card for communication and one Dolphin card for I/Os access in the same simulator. The rule of thumb is to leave only the Dolphin card associated to communication in each target.

There are a few things to make sure:

1. The dishost.conf file used must be identical on both targets.

2. The first HOSTNAME IP address must match the first target IP address (ie it is not a particular IP for the card, it's the IP of the target)

3. The second HOSTNAME IP address must match the second target IP address (ie it is not a particular IP for the card, it's the IP of the target)

In the attached dishost.conf, the first target IP is 192.168.0.126. The second target IP is 192.168.0.127.

4. The "/opt/DIS/sbin/dxconfig -c 1 -a 0 -n 4" line in the rc.local file must NOT be preceeded by the pound sign "#". All lines starting by a pound sign in the rc.local file are comments, not command lines.

5. The "/opt/DIS/sbin/dxconfig -c 1 -a 0 -n 4" line must be exactly like this one here for the first target. For the second target "/opt/DIS/sbin/dxconfig -c 1 -a 0 -n 8".

6. If you have another Dophin Card installed on the target for communicating with the PCIe switch (dophin IO), you must physically REVOVE this card before you install the dophin driver.

7. Make sure you reboot both targets after all modifications done on rc.local files and dishost.conf files.

8. After starting the targets, do this command: dis_services status
This will let you know if the driver is running on that particular target or not.

9. If the driver is running, then do this command on both targets: dxdiag
If the TEST RESULT = PASSED on both targets, then you are ready to go to load rtdemo2. If the test result fails, then the adaptor settings are not ok. Note that "dis_services status"; may return good while "dxdiag" may return bad. If that's the case, Dolphin comm. will not work. The "dis_services status" is only for the driver, so is "dis_services restart". The "dxdiag" is about the cluster configuration, which is launched by rc.local. Therefore if the rc.local file is not set properly, even if "dis_services restart" or "dis_services status" works, Dolphin comm. will not succeed because of the cluster config. Both the cluster configuration ("dxdiag") and the driver ("dis_services status") must work.

9. The model should be ran in XHP mode.

10. You can take the files attached for your Dolphin settings. Just change the IP addresses in the dishost.conf. The files are functionals as is for a setup where target 1 IP is 192.168.0.126 and target 2 IP is 192.168.0.127.

Keyword: SCIInitialize failed - Error code: 0x40000909

HowToDolphinDXH510_v1_6.doc - Dolphin Installation Procedure
DolphinSetup.rar - Dolphin Files