How can I check whether the AMD receives data from properly configured TCAM?

Use the AMD's rcon commands: show mapstats global and show mapstats byagent.

  1. Open rcon, establish a connection to the AMD and type:

    show mapstats global
  2. Analyze the results of the command:

    1. The frontendMappingCount and backendMappingCount counters will show the number of username mappings received by the AMD.

      The frontendMappingCount will show a number of login mappings (ICA analyzer mappings) and the backendMappingCount will show a number of session username mappings.

    2. The avgMappingDelay and maxMappingDelay show the delay with which TCAM sends the mappings.

    3. A value other than zero (0) presented in the emptyMappings counter, suggests that TCAM is sending mappings without the username.

  3. Use the show mapstats byagent command to obtain more specific view.

    The show mapstats byagent command will display the frontendMappingCount and backendMappingCount on a per TCAM basis. Each TCAM will be identified by the IP address of the Citrix server that it is installed on.

Additional commands are available for further diagnostics. For more information, see Table 1. Commands available for session mapping diagnostics.

For a lower level debugging you can use a standard tool called tcpdump.

  1. Log on to the AMD as root and, in the console command line, type:

    tcpdump host IP_ADDRESS and port PORT_NUMBER and udp -I IFC -n -nn

    where IP_ADDRESS means the IP address of the Citrix server with TCAM installed and running, PORT_NUMBER is the number of UDP port on which the AMD receives the data, IFC is the name of the communication network interface. For example,

    tcpdump host and port 514 and udp -I eth0 -n -nn

    will dump all the TCP traffic received on the NIC eth0 on port 514 from the IP address

    If you are not sure what Ethernet interface is used for communication purposes, type:

    grep -^net.comm- /usr/adlex/config/rtm.config

    to see the communication NIC system name.

  2. Analyze the captured traffic.

    The format of the received data should look like:


    where SRC_IP should be the IP address of the Citrix server on which TCAM is running while DST_IP and DST_PORT should be the IP address of the AMD and the UDP port number on which the AMD receives the Citrix performance data.

    Note that TCAM sends the performance data every 60 seconds while the session mapping data whenever a new mapping occurs. It means that new entry should appear on the console screen at least every minute.

Table 1. Commands available for session mapping diagnostics.

The following table presents statistics available for session mapping diagnostics:




Global statistics


Number of front-end mappings received by the AMD.


Number of back-end mappings received by the AMD.


Total number of sessions, which have not received a mapping.


Total number of mappings with an empty username the AMD has received.


Number of mappings which have arrived, but have not been used (for whatever reason).


Similar to unusedMappings, but narrowed to situations when the mapping arrives after the allowable wait timeout (delay too large)


Averaged difference between the time of mapping arrival and session beginning.

for mappings which arrive before a session starts the delay (less than zero) is not taken into account


Largest observed mapping arrival delay.


Averaged delay for discarded mappings (mappings which arrived after the acceptable wait time).


Largest observed discarded mapping arrival delay.

Per-agent (TCAM) statistics


Number of sessions associated with a particular agent, which have not received a mapping.


Number of mappings with an empty username the AMD has received from a particular agent.

How can I check whether the AMD has been configured to detect and monitor Citrix-based applications?

Properly installed and configured TCAM is not sufficient to monitor the Citrix-based applications. You also have to define a software service based on the ICA (Citrix) analyzer using the RUM Console. For more information, see Citrix XenApp or XenDesktop Monitoring.

How can I check whether AMD sees the session mapping data?

  1. Log on to AMD as root.

  2. Launch the AMD console program by typing in rcon at the command prompt.

  3. Type show clientmap at the rcon command prompt to display Citrix users,


    Display the user session mapping information by typing in show sessionclientmap at the rcon command prompt. The command displays session mappings only and does not refer to performance data.

    The command show clientmap should be used prior to show sessionclientmap command. The latter may mislead the user by yielding empty output, because session mappings are removed from the AMD memory just after they are processed by the AMD.


    The mappings are also removed from the AMD memory after exceeding a specified timeout, called the lease time. The lease time parameter is configured in the RUM Console, in the AMD Configuration window, at Advanced ► User-IP mapping ► General: Session Client Name Mapping Lease Time and its default value is 60 seconds.

    The empty list may also indicate that there is a problem with receiving session mappings data from TCAM. It may also mean that no new sessions have been established recently.

For more information, see Citrix XenApp or XenDesktop Monitoring and User-IP Mapping - General.

The report server does not seem to receive Citrix performance data from the AMD. How can I check the data is generated on the AMD?

Log on to AMD as root and type at the command prompt the following command:

ls -lt /var/spool/adlex/rtm/ctxdata* | head -n 20

This command lists 20 of the most recent files containing the Citrix performance data, generated by the AMD. Note the file creation date and time of each file and compare it with the system time by means of thedate command. If the listed files are not recently generated, the AMD may be improperly configured or TCAM is not configured to send the performance data to this AMD. For more information, see TCAM Administration via Command Line Interface.


  • No labels

1 Comment

  1. Hi,

    the reported grep:

    grep -^net.comm- /usr/adlex/config/rtm.config

    seems to be not valid:

    grep: invalid option -- '^'
    Usage: grep [OPTION]... PATTERN [FILE]...
    Try 'grep --help' for more information.

    What's wrong with the syntax?