FieldServer FS-8704-13 Manuale Utente
FS-8704-13 GE-SRTP
Driver Manual
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 (408) 262-2299 fax: (408) 262-9042
Visit our website: www.fieldserver.com E-mail: support@fieldserver.com
Page 15
6. Driver Notes
6.1 Driver Stats
The statistics recorded by the GE-SNPX Serial Driver are slightly different from the way that
Fieldserver driver normally record statistics. This difference arises from the fact that this driver is
not a simple poll response driver. Bare in mind that a single poll can generate a large number of
response fragments.
Fragment Ack/nack messages are NOT counted as message but the bytes sent/rcvd are counted.
Connection messages are counted as messages and the bytes sent/rcvd are counted.
This driver can expose these and additional statistics by writing data to a data array.
A special map descriptor is required. The driver recognizes the map descriptor by its name which
must be "SRTP-stats" .
The following example shows how this special map descriptor can be configured.
Nodes
Node_name, Protocol
null_node, SRTP
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length
SRTP_STATS , UINT32 , 600
Map_blocks
Map_block_Name, Data_Array_Name, Node_name, Length
srtp-stats , SRTP _STATS , null_node , 600
When the driver sees this map descriptor it uses the data array SRTP _STATS (in this example)
to store driver specific statistics. Only one of these map descriptors may be specified (per tier) per
FieldServer.
The driver stores the following stats for each port.. The offset into the data array can be found by
multiplying the port number by 50
Fieldserver driver normally record statistics. This difference arises from the fact that this driver is
not a simple poll response driver. Bare in mind that a single poll can generate a large number of
response fragments.
Fragment Ack/nack messages are NOT counted as message but the bytes sent/rcvd are counted.
Connection messages are counted as messages and the bytes sent/rcvd are counted.
This driver can expose these and additional statistics by writing data to a data array.
A special map descriptor is required. The driver recognizes the map descriptor by its name which
must be "SRTP-stats" .
The following example shows how this special map descriptor can be configured.
Nodes
Node_name, Protocol
null_node, SRTP
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length
SRTP_STATS , UINT32 , 600
Map_blocks
Map_block_Name, Data_Array_Name, Node_name, Length
srtp-stats , SRTP _STATS , null_node , 600
When the driver sees this map descriptor it uses the data array SRTP _STATS (in this example)
to store driver specific statistics. Only one of these map descriptors may be specified (per tier) per
FieldServer.
The driver stores the following stats for each port.. The offset into the data array can be found by
multiplying the port number by 50
Stat #
Stat Code
1 GE_STAT_BAD_SEND
2 GE_STAT_POLL_MSGS_SENT
3 GE_STAT_POLL_BYTES_SENT
4 GE_STAT_SESS_CONNECT
5 GE_STAT_DEV_CONNECT
6 GE_STAT_BAD_PDU
7 GE_STAT_BAD_PROTOCOL
8 GE_STAT_TIMEOUT
9 GE_STAT_MBOX_NAK_MAJOR
2 GE_STAT_POLL_MSGS_SENT
3 GE_STAT_POLL_BYTES_SENT
4 GE_STAT_SESS_CONNECT
5 GE_STAT_DEV_CONNECT
6 GE_STAT_BAD_PDU
7 GE_STAT_BAD_PROTOCOL
8 GE_STAT_TIMEOUT
9 GE_STAT_MBOX_NAK_MAJOR