An LTM Specialist uploaded new releases .iso and .md5 files titled "BIGIP-FILENAME" via the GUI.
Which commands are run via the command line from the root directory to verify the integrity of the new .iso file?
An LTM Specialist uploaded new releases .iso and .md5 files titled "BIGIP-FILENAME" via the GUI.
Which commands are run via the command line from the root directory to verify the integrity of the new .iso file?
To verify the integrity of an .iso file, you need to use the md5sum command alongside the .md5 file. The correct directory path to navigate to is /shared/images, which is specified in option B. From there, you run the command with the appropriate .md5 file (missing in option B, ideally it should be .md5 at the end). However, based on efficiently verifying the iso file, B provides the precise directory path needed.
cd /shared/images; md5sum --check BIGIP-FILENAME.iso.md5 # https://support.f5.com/csp/article/K8337#proc1
B is missing .md5 at the end A and C are wrong directory /var/shared/images... instead of shared/images D is the last choice, because the question is asking which command run on the root directory to verify .iso file. So we need to cd to shared/images first, then run md5sum command. https://support.f5.com/csp/article/K8337
Should be B
cd /shared/images md5sum --check BIGIP-FILENAME.iso.md5
I try at my lab, and the command is "cd /shared/images/" and type the command "md5sum --check BIGIP-11.5.10-0.0.13.iso.md5" so there is no answer to that choice
Correct Answer:B
Answer is B - done this a million times on all our company f5 devices
Sorry, just seen that B is missing .md5 at the end. Chances are is that the answer is D, because its probably the same answer as B, but it adds ".md5" at the end of the command.
D - Best Answer