An external syslog server shows no detailed TCP information; what is the likely cause?

An external syslog server shows no detailed TCP information; what is the likely cause?

• A. Log facility is NOT configured.
• B. TCP logging is NOT enabled.
• C. User-defined audit log is NOT configured.
• D. Log level is NOT enabled.

Answer: (B)

The key idea is that detailed TCP information only appears in syslog if TCP logging is turned on. If TCP logging isn’t enabled on the Citrix ADC, the syslog stream won’t include TCP-specific events or fields, so an external syslog server will show little to no TCP detail regardless of other logging settings. Enabling TCP logging ensures the device captures and forwards those connection-level details to syslog. Other aspects, like the log facility or log level, affect where logs go or which severities are emitted, but they don’t specifically control whether TCP connection details are captured. A lack of TCP detail is most directly explained by not having TCP logging enabled.

The key idea is that detailed TCP information only appears in syslog if TCP logging is turned on. If TCP logging isn’t enabled on the Citrix ADC, the syslog stream won’t include TCP-specific events or fields, so an external syslog server will show little to no TCP detail regardless of other logging settings. Enabling TCP logging ensures the device captures and forwards those connection-level details to syslog.

Other aspects, like the log facility or log level, affect where logs go or which severities are emitted, but they don’t specifically control whether TCP connection details are captured. A lack of TCP detail is most directly explained by not having TCP logging enabled.