netscaler.adc.nstrace module – Configuration for nstrace operations resource.
Note
This module is part of the netscaler.adc collection (version 2.6.0).
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install netscaler.adc
.
To use it in a playbook, specify: netscaler.adc.nstrace
.
New in netscaler.adc 2.0.0
Synopsis
Configuration for nstrace operations resource.
Parameters
Parameter |
Comments |
---|---|
Base NITRO API path. Define only in case of an ADM service proxy call Default: |
|
Captures Dropped Packets if set to Choices:
|
|
Capture SSL Master keys. Master keys will not be captured on FIPS machine.
Choices:
|
|
Enable or disable runtime temp file cleanup Choices:
|
|
ID for the trace file name for uniqueness. Should be used only with -name option. |
|
Name of the trace file. |
|
File size, in MB, treshold for rollover. If free disk space is less than 2GB at the time of rollover, trace will stop |
|
Filter expression for nstrace. Maximum length of filter is 255 and it can be of following format:
common use cases: Trace capturing full sized traffic from/to ip 10.102.44.111, excluding loopback traffic start nstrace -size 0 -filter “CONNECTION.IP.NE(127.0.0.1) && CONNECTION.IP.EQ(10.102.44.111)” Trace capturing all traffic to (terminating at) port 80 or 443 start nstrace -size 0 -filter “CONNECTION.DSTPORT.EQ(443) || CONNECTION.DSTPORT.EQ(80)” Trace capturing all backend traffic specific to service service1 along with corresponding client side traffic start nstrace -size 0 -filter “CONNECTION.SVCNAME.EQ(“service1”)” -link ENABLED Trace capturing all traffic through Citrix ADC interface 1/1 start nstrace -filter “CONNECTION.INTF.EQ(“1/1”)” Trace capturing all traffic specific through vlan 2 start nstrace -filter “CONNECTION.VLANID.EQ(2)” Trace capturing all frontend (client side) traffic specific to lb vserver vserver1 along with corresponding server side traffic start nstrace -size 0 -filter “CONNECTION.LB_VSERVER.NAME.EQ(“vserver1”)” -link ENABLED |
|
Logs packets in appliance’s memory and dumps the trace file on stopping the nstrace operation Choices:
|
|
Includes filtered connection’s peer traffic. Choices:
|
|
The ID of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The IP of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The name of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The password of the managed NetScaler instance. Define only in case of an ADM service proxy call In Settings > Administration > System Configurations > Basic Settings, if you select Prompt Credentials for Instance Login, ensure to configure username and password of a managed instance. |
|
The username of the managed NetScaler instance. Define only in case of an ADM service proxy call In Settings > Administration > System Configurations > Basic Settings, if you select Prompt Credentials for Instance Login, ensure to configure username and password of a managed instance. |
|
Specify how traces across PE’s are merged Choices:
|
|
Capturing mode for trace. Mode can be any of the following values or combination of these values:
Choices:
|
|
The IP address of the NetScaler ADC appliance acting as a proxy server. Define only in case of an ADM service proxy call Choices:
|
|
Number of files to be generated in cycle. |
|
The authentication token provided by a login operation. |
|
The password with which to authenticate to the NetScaler ADC node. |
|
Which protocol to use when accessing the nitro API objects. Choices:
|
|
The username with which to authenticate to the NetScaler ADC node. |
|
Unique number that identifies the cluster node. |
|
Nodes on which tracing is started. |
|
The ip address of the NetScaler ADC appliance where the nitro API calls will be made. The port can be specified with the colon (:). E.g. 192.168.1.1:555. |
|
Use separate trace files for each interface. Works only with cap format. Choices:
|
|
If The module will not save the configuration on the NetScaler ADC node if it made no changes. Choices:
|
|
Size of the captured data. Set 0 for full packet trace. |
|
skip local SSH packets Choices:
|
|
skip RPC packets Choices:
|
|
The state of the resource being configured by the module on the NetScaler ADC node. Default: |
|
Time per file (sec). |
|
Number of 16KB trace buffers |
|
Format in which trace will be generated Choices:
|
|
If Choices:
|
Notes
Note
For more information on using Ansible to manage NetScaler ADC Network devices see https://www.ansible.com/integrations/networks/citrixadc.
Examples
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Indicates if any change is made by the module Returned: always Sample: |
|
Dictionary of before and after changes Returned: always Sample: |
|
List of differences between the actual configured object and the configuration specified in the module Returned: when changed Sample: |
|
Indicates if the module failed or not Returned: always Sample: |
|
list of logged messages by the module Returned: always Sample: |