An LTM Specialist troubleshooting an issue looks at the following /var/log/ltm entries:
Oct 2 04:52:42 slot1/tmm7 crit tmm7[21734]: 01010201:2: Inet port exhaustion on 10.143.109.5 to 10.143.147.150:53 (proto 17)
Oct 2 05:37:16 slot1/tmm7 crit tmm7[21734]: 01010201:2: Inet port exhaustion on 10.143.109.5 to 10.143.147.150:53 (proto 17)
Oct 2 05:57:32 slot1/tmm2 crit tmm2[21729]: 01010201:2: Inet port exhaustion on 10.143.109.5 to 10.143.147.150:53 (proto 17)
Oct 2 06:30:03 slot1/tmm7 crit tmm7[21734]: 01010201:2: Inet port exhaustion on 10.143.109.5 to 10.143.147.150:53 (proto 17)
Oct 2 06:37:44 slot1/tmm2 crit tmm2[21729]: 01010201:2: Inet port exhaustion on 10.143.109.5 to 10.143.147.150:53 (proto 17)
Oct 2 06:47:05 slot1/tmm5 crit tmm5[21732]: 01010201:2: Inet port exhaustion on 10.143.109.5 to 10.143.147.150:53 (proto 17)
Which configuration item should the LTM Specialist review to fix the issue?
An LTM Specialist is troubleshooting an issue with a new virtual server. When connecting through the virtual server, clients receive the message "Unable to connect" in the browser, although connections directly to the pool member show the application is functioning correctly. The LTM configuration is:
ltm virtual /Common/vs_https {
destination /Common/10.10.1.110:443
ip-protocol udp
mask 255.255.255.255
pool /Common/pool_https
profiles {
/Common/udp { }
}
translate-address enabled
translate-port enabled
vlans-disabled
}
ltm pool /Common/pool_https {
members {
/Common/172.16.20.1:443 {
address 172.16.20.1
}
}
}
How should the LTM Specialist resolve this issue?
-- Exhibit --
-- Exhibit --
Refer to the exhibit.
An LTM Specialist sets up AVR alerts and notifications for a specific virtual server if the server latency exceeds 50ms. The LTM Specialist simulates a fault so that the server latency is consistently exceeding the 50ms threshold; however, no alerts are being received.
Which configuration should the LTM Specialist modify to achieve the expected results?
-- Exhibit --
-- Exhibit --
Refer to the exhibit.
An LTM Specialist is troubleshooting an HTTP monitor that is marking a pool member as down. Connecting to the pool member directly through a browser shows the application is up and functioning correctly.
How should the send string be modified to correct this issue?
-- Exhibit --
-- Exhibit --
Refer to the exhibit.
An LTM Specialist is troubleshooting an HTTP monitor that is marking a pool member as down. Connecting to the pool member directly through a browser shows the application is up and functioning correctly.
ltm monitor http http_mon {
defaults-from http
destination *:*
interval 5
recv "200 OK"
send "GET /\\r\\n"
time-until-up 0
timeout 16
}
What is the issue?
Sheridan
13 days agoRory
2 months agoRima
3 months agoStephane
4 months agoValentin
5 months agoFrederick
5 months agoReena
6 months agoCeola
7 months agoLanie
7 months agoGearldine
7 months agoIsidra
8 months agoEvelynn
8 months agoCecilia
8 months agoEstrella
8 months agoBrittni
8 months agoIra
9 months agoDion
9 months agoAlbert
9 months agoJerry
9 months agoJulian
9 months agoCristina
10 months agoMila
10 months agoLaquanda
11 months agoTelma
11 months agoCheryll
1 years agoDorthy
1 years ago