Nodegrid appliances with RJ45 and USB serial ports will use the incoming RS232 signals to determine the status shown on the Access pages:
Changes to the RS232 signals will also trigger Nodegrid Device Up and Nodegrid Device Down events shown on Tracking :: Event List :: Events and sent via Auditing :: Events :: Device Events.
Since different vendors utilize RS232 signals differently, it is important to ensure each target device connected to the Nodegrid appliance is configured accurately. Each port has two settings involved in determining its status. Both are set by editing the port from Managed Devices :: Devices:
The default options are DCD for RS-232 signal for device state detection, with Enable device state detection based in data flow unselected. To determine which options are best for a given target device, it is necessary to review what signals are present when access is working properly. Here is how to check if access is working:
Once access is confirmed as working, navigate to Tracking :: Devices :: Serial Statistics to review the current RS232 signals for the specific port. The active signals will determine which options should be set on that port in Managed Devices :: Devices:
If neither CTS nor CD is active:
If CTS is active and CD is not active:
If CD active with or without CTS activity:
Note when Hardware based Flow Control is used, this can impact activity for the RTS and CTS signals. When either side exceeds the maximum data rate, the far side will no longer see a CTS signal. This means when both CTS and CD signals are active, it is preferred to set RS-232 signal for device state detection to use the DCD signal.
To learn more about RS232 signals, please review: What do the various RS232 signals mean?