An LTM device is monitoring pool members on port 80. The LTM device is using an HTTP monitor with a send string of GET / and a blank receive string.
What would cause the pool members to be marked down?
While investigating the cause of a device failover, an LTM Specialist discovers the following events in /var/log/ltm:
01010029:5: Clock advanced by 518 ticks 01010029:5: Clock advanced by 505 ticks 01010029:5: Clock advanced by 590 ticks 01010029:5: Clock advanced by 568 ticks 01010029:5: Clock advanced by 1681 ticks 01010029:5: Clock advanced by 6584 ticks 01140029:5: HA daemon_heartbeat tmm fails action is failover and restart. 010c0026:5: Failover condition, active attempting to go standby.
Which issue caused the failover?
An LTM Specialist is troubleshooting an issue with a new virtual server. When connecting through the virtual server, clients receive the message "The connection was reset" in the browser, although connections directly to the pool member show the application is functioning correctly.
ltm pool srv1_https_pool {
members {
192.168.2.1:https{
address 192.168.2.1
}
}
}
ltm virtual https_example_vs {
destination 192.168.1.155:https
ip-protocol tcp
mask 255.255.255.255
pool srv1_https_pool
profiles {
http { }
tcp { }
}
snat automap
vlans-disabled
}
How should the LTM Specialist resolve this issue?
An LTM device pool has suddenly been marked down by a monitor. The pool consists of members
10.0.1.1:443 and 10.0.1.2:443 and are verified to be listening. The affected virtual server is
10.0.0.1:80.
Which two tools should the LTM Specialist use to troubleshoot the associated HTTPS pool monitor via the command line interface? (Choose two.)
An LTM Specialist is working with an LTM device configured with 10 virtual servers on the same domain with a different key/cert pair per virtual. For examplE. www.example.com; ftp.example.com; ssh.example.com; ftps.example.com.
What should the LTM Specialist do to reduce the number of objects on the LTM device?
