Download full document:


Statistics for UDP Protocol resource.


(click to see Operations)

NameData TypePermissionsDescription
clearstats<String>Read-writeClear the statsistics / counters.
Possible values = basic, full
udptotrxpkts<Double>Read-onlyTotal number of UDP packets received.
udprxpktsrate<Double>Read-onlyRate (/s) counter for udptotrxpkts
udptotrxbytes<Double>Read-onlyTotal number of UDP data received in bytes.
udprxbytesrate<Double>Read-onlyRate (/s) counter for udptotrxbytes
udptottxpkts<Double>Read-onlyTotal number of UDP packets transmitted.
udptxpktsrate<Double>Read-onlyRate (/s) counter for udptottxpkts
udptottxbytes<Double>Read-onlyTotal number of UDP data transmitted in bytes.
udptxbytesrate<Double>Read-onlyRate (/s) counter for udptottxbytes
udpcurratethreshold<Double>Read-onlyLimit for UDP packets handled every 10 milliseconds. Default value, 0, applies no limit. This is a configurable value using the set rateControl command.
udptotunknownsvcpkts<Double>Read-onlyStray UDP packets dropped due to no configured listening service.
udpbadchecksum<Double>Read-onlyPackets received with a UDP checksum error.
udpcurratethresholdexceeds<Double>Read-onlyNumber of times the UDP rate threshold is exceeded. If this counter continuously increases, first make sure the UDP packets received are genuine. If they are, increase the current rate threshold. This is a configurable value using the set rateControl command.


(click to see Properties)


Some options that you can use for each operations:

  • Getting warnings in response:NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:


    If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

  • Authenticated access for individual NITRO operations:NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:



    Note:In such cases, make sure that the request header DOES not include the following:



Mandatory parameters are marked in redand placeholder content is marked in <green>.

get (all)





Use this query-parameter to get protocoludp resources based on additional properties.


Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue> Accept:application/json


HTTP Status Code on Success: 200 OK HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the errorResponse Headers:


Response Payload:

{ "protocoludp": [ {