Free F5 Networks 301b Exam Questions

-- Exhibit –-- Exhibit --Refer to the exhibits.After upgrading LTM from v10 to v11, users are unable to connect to an application. The virtual server is usinga client SSL profile for re-terminating SSL for payload inspection, but a server SSL profile is being used to reencrypt the request.A client side ssldump did NOT show any differences between the traffic going directly to the server and thetraffic being processed by the LTM device. However, packet capture was done on the server, and differenceswere noted.Which modification will allow the LTM device to process the traffic correctly?

An LTM Specialist must perform a packet capture on a virtual server with an applied standard FastL4 profile.The virtual server 10.0.0.1:443 resides on vlan301.Which steps should the LTM Specialist take to capture the data payload successfully while ensuring no othervirtual servers are affected?

A new VLAN vlan301 has been configured on a highly available LTM device in partition ApplicationA. A newdirectly connected backend server has been placed on vlan301. However, there are connectivity issues pingingthe default gateway. The VLAN self IPs configured on the LTM devices are 192.168.0.251 and 192.168.0.252with floating IP 192.168.0.253. The LTM Specialist needs to perform a packet capture to assist withtroubleshooting the connectivity.Which command should the LTM Specialist execute on the LTM device command line interface to capture theattempted pings to the LTM device default gateway on VLAN vlan301?

An LTM Specialist has set up a custom SNMP alert.Which command line tool should the LTM Specialist use to test the alert?

An LTM Specialist is tasked with ensuring that the syslogs for the LTM device are sent to a remote syslogserver.The following is an extract from the config file detailing the node and monitor that the LTM device is using fortheremote syslog server:monitorSyslog_15002 {defaults from udpdest *:15002 }node 91.223.45.231 {monitor Syslog_15002screen RemoteSYSLOG }There seem to be problems communicating with the remote syslog server. However, the pool monitor showsthat the remote server is up.The network department has confirmed that there are no firewall rules or networking issues preventing theLTM device fromcommunicating with the syslog server. The department responsible for the remote syslog server indicates thatthere maybe problems with the syslog server. The LTM Specialist checks the BIG-IP LTM logs for errors relating to theremote syslogserver. 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 1921:28:36.429073 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 16921:28:36.430714 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 18121:28:36.840524 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 16921:28:36.846547 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 18121:28:39.886343 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 144NotE. 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?