nerdexam
F5

201 · Question #242

During a maintenance window, an EUD test was executed and the output displayed on the screen. The BIG-IP Administrator did NOT save the screen output. The BIG-IP device is currently handling…

The correct answer is D. Collect file /shared/log/eud.log. To retrieve previous EUD results without impacting critical traffic, the administrator should collect the EUD log file from /shared/log/eud.log.

Section 5: Troubleshoot a BIG-IP System

Question

During a maintenance window, an EUD test was executed and the output displayed on the screen. The BIG-IP Administrator did NOT save the screen output. The BIG-IP device is currently handling business critical traffic. The BIG-IP Administrator needs to minimize impact. What should the BIG- IP Administrator do to provide the EUD results to F5 Support?

Options

  • ABoot the device into EUD then collect output from console
  • BExecute EUD from tmsh and collect output from console
  • CCollect file /var/log/messages
  • DCollect file /shared/log/eud.log

How the community answered

(46 responses)
  • A
    7% (3)
  • B
    13% (6)
  • C
    2% (1)
  • D
    78% (36)

Why each option

To retrieve previous EUD results without impacting critical traffic, the administrator should collect the EUD log file from /shared/log/eud.log.

ABoot the device into EUD then collect output from console

Booting the device into EUD requires a reboot and takes the device offline, causing significant impact to critical traffic.

BExecute EUD from tmsh and collect output from console

Executing EUD from tmsh would run new diagnostics, potentially consuming resources, and is not necessary if the previous results are already logged.

CCollect file /var/log/messages

The /var/log/messages file contains general system logs but does not store the specific, detailed output of EUD tests.

DCollect file /shared/log/eud.logCorrect

The End User Diagnostics (EUD) tool on BIG-IP systems logs its results to the /shared/log/eud.log file, allowing administrators to review past test outputs without re-executing the diagnostic. Accessing this log file is a non-disruptive way to retrieve the EUD results while the device handles business critical traffic.

Concept tested: BIG-IP EUD log file location

Source: https://my.f5.com/manage/s/article/K7172

Topics

#EUD logs#Troubleshooting#Log files#F5 Support

Community Discussion

No community discussion yet for this question.

Full 201 Practice