Hello
I have a driver Smart-serial by defaul with 2 aditional conexion the firt make a push of values in the port 5000 and the second it's for http requests on port 8080.
For some reason one element works well with all conections but wen i duplicate or create and other element the session do not run.
I'm using the tag (connection="N°") to specify the conextion to use in the HTTP group.
The debug log show in the good element the start, prosessing and finish of group and the back element only start and finish without error and without content but is the same protocol.
Tanks
The code:
<Type relativeTimers="true" advanced="HTTP:HTTP Connection1;HTTP:HTTP Connection2" communicationOptions="makeCommandByProtocol">smart-serial</Type>
<Group id="114" connection="2">
<Name>getGeofences</Name>
<Description>GET /api/geofences/deviceid</Description>
<Type>poll</Type>
<Content>
<Session>14</Session>
</Content>
</Group>
<Ports>
<PortSettings name="HTTP Connection1">
<Type>
<DefaultValue>ip</DefaultValue>
</Type>
<BusAddress>
<DefaultValue>ByPassProxy</DefaultValue>
<Disabled>false</Disabled>
</BusAddress>
<IPport>
<DefaultValue>5000</DefaultValue>
<Disabled>false</Disabled>
</IPport>
<PortTypeSerial>
<Disabled>true</Disabled>
</PortTypeSerial>
<PortTypeUDP>
<Disabled>true</Disabled>
</PortTypeUDP>
</PortSettings>
<PortSettings name="HTTP Connection2">
<Type>
<DefaultValue>ip</DefaultValue>
</Type>
<IPport>
<DefaultValue>8080</DefaultValue>
</IPport>
<PortTypeSerial>
<Disabled>true</Disabled>
</PortTypeSerial>
<PortTypeUDP>
<Disabled>true</Disabled>
</PortTypeUDP>
<BusAddress>
<DefaultValue>bypassproxy</DefaultValue>
<Disabled>false</Disabled>
</BusAddress>
</PortSettings>
</Ports>
Hi Juan,
I opened a new message to add some more information from the tests that we performed.
The test included following:
- Connector with a smart-serial connection
- Element with IP address set to IP address of the DMA and IP port set to 10000.
This should result in the element opening port 10000 on the DMA, and listening for any incoming request on that specific port.
How to more easily debug:
- Into System Center > Logging > DataMiner > Port, you should see the listening port being created.
- Executing a command 'netstat -a' on the server itself should also show that the server has a listening port on that number.
- Performing a 'telnet [IP address] [port]' on any machine that can contact the DMA through that port should be able to open that port.
If actions above would not show the same results for you, it could indeed be an issue into the software. I would recommend to contact your TAM to further investigate and create the necessary task.
Hope above provides some more clarity.
Leander