CODEWITHSUNDEEP
redhawksdromniorb
ARob
ARob

Reputation: 11

Issues with connecting remote device to Redhawk SDR domain

I'm having an issue with getting a device to connect to a Redhawk SDR domain. I've tried following answer questions to similar questions like this one issues-with-running-a-second-node-on-another-processor but can't work it out. When I enter the command nameclt list on the device machine I get the following response:

Caught a TRANSIENT exception when trying to validate the type of the 
NamingContext. Is the naming service running?

I'm running the domain manager on a VM with CentOS 6.8 x64 with Redhawk 2.0.2. The device is also on a VM, cloned from the first one. The two VMs are on separate hosts connected by Ethernet LAN. I've configured the hosts and VMs to bridge to their respective Ethernet port and can ping all 4 machines. The device VM is 192.168.1.2. The device host is 192.168.1.5. The domain host is 192.168.1.6 and the domain VM is 192.168.1.3.

My omniORB.cfg on the device VM is as follows:

InitRef = NameService=corbaname::192.168.1.3
InitRef = EventService=corbaloc::192.168.1.3:11169/omniEvents
supportBootstrapAgent = 1
endPoint = giop:unix:

My omniORB.cfg on the domain VM is as follows:

InitRef = NameService=corbaname::127.0.0.1
InitRef = EventService=corbaloc::127.0.0.1:11169/omniEvents
supportBootstrapAgent = 1
endPoint = giop:unix:

Edit: For more information, the two hosts are connected directly together between their two Ethernet ports. There is no router or switch. The IPs for the hosts are statically assigned.

Upvotes: 0

Views: 168

Answers (0)

Related Questions