An LTM Specialist is tasked with ensuring that the syslogs for the LTM device are sent to a remote syslog
server.
The following is an extract from the config file detailing the node and monitor that the LTM device is using
for the
remote syslog server:
monitor
Syslog_15002 {
defaults from udp
dest *:15002
}
node 91.223.45.231 {
monitor Syslog_15002
screen RemoteSYSLOG
}
There seem to be problems communicating with the remote syslog server. However, the pool monitor
shows that the remote server is up.
The network department has confirmed that there are no firewall rules or networking issues preventing the
LTM device from
communicating with the syslog server. The department responsible for the remote syslog server indicates
that there may
be problems with the syslog server. The LTM Specialist checks the BIG-IP LTM logs for errors relating to
the remote syslog
server. None are found. The LTM Specialist does a tcpdump:
tcpdump -nn port 15002, with the following results:
21:28:36.395543 IP 192.168.100.100.44772 > 91.223.45.231.15002: UDP, length 19
21:28:36.429073 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 169
21:28:36.430714 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 181
21:28:36.840524 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 169
21:28:36.846547 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 181
21:28:39.886343 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 144
NotE. 192.168.100.100 is the self IP of the LTM device.
Why are there no errors for the remote syslog server in the log files?

A.
The -log option for tcpdump needs to be used.

B.
The monitor type used is inappropriate.

C.
The “verbose” logging option needs to be enabled for the pool.

D.
When the remote syslog sever fails, it returns to service before the timeout for the monitor has expired.