ica_server_session_hop_detail
Configuration for Af report for ICA Server session hop detail resource.
(click to see Operations)
Properties
(click to see Operations)
Name | Data Type | Permissions | Description |
---|---|---|---|
serverside_packet_retransmits | <Double> | Read-write | Server side packet retransmits.. |
__count | <Double> | Read-write | count.. |
server_side_ns_delay | <Double> | Read-write | Server to Clinet NS delay.. |
state | <String> | Read-write | ICA Session state.. |
launch_duration | <Double> | Read-write | ica session launch duration.. |
server_jitter | <Double> | Read-write | ICA User server jitter.. |
serverside_rto | <Double> | Read-write | serverside rto.. |
id | <String> | Read-write | Id is ICA Session ID. Minimum length = 1 Maximum length = 64 |
serverside_0_win | <Double> | Read-write | server side 0 window count.. |
server_latency | <Double> | Read-write | ica session server latency.. |
serverside_cb | <Double> | Read-write | serverside cb. |
host_delay | <Double> | Read-write | Server induced delay.. |
rpt_sample_time | <Double> | Read-write | Report Sample time.. |
session_setup_time | <Double> | Read-write | ICA Session setup time.. |
server_srtt | <Double> | Read-write | server Smothen RTT.. |
session_end_time | <Double> | Read-write | ICA Session end time.. |
session_rtt | <Double> | Read-write | ICA Session rtt.. |
l7_serverside_latency | <Double> | Read-write | L7 serverside latency. |
Operations
(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:
http://<netscaler-ip-address>/nitro/v1/config/login?warning=yes
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:
X-NITRO-USER:<username>
X-NITRO-PASS:<password>
Note: In such cases, make sure that the request header DOES not include the following:
Cookie:NITRO_AUTH_TOKEN=<tokenvalue>
Note:
Mandatory parameters are marked in red and placeholder content is marked in <green>.
get (all)
URL: https://<MGMT-IP>/nitro/v1/config/ica_server_session_hop_detail
HTTP Method: null
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "ica_server_session_hop_detail":[{ "serverside_packet_retransmits":<Double_value>, "ica_user_name":<String_value>, "__count":<Double_value>, "server_side_ns_delay":<Double_value>, "state":<String_value>, "launch_duration":<Double_value>, "server_jitter":<Double_value>, "serverside_rto":<Double_value>, "id":<String_value>, "serverside_0_win":<Double_value>, "server_latency":<Double_value>, "serverside_cb":<Double_value>, "server_ip_address":<String_value>, "host_delay":<Double_value>, "rpt_sample_time":<Double_value>, "session_setup_time":<Double_value>, "server_srtt":<Double_value>, "session_end_time":<Double_value>, "session_rtt":<Double_value>, "l7_serverside_latency":<Double_value>}]}