nerdexam
Avaya

72201T · Question #29

How can you view the entire contents of the current Avaya Aura@ Communication Manager (CM) call processing log file?

The correct answer is C. by using the Linux cd to /var/log/esc and ls -l commands to find current <log filename>; cat <log. Option C is correct because the CM call processing log is stored in /var/log/esc, and since log files in that directory are rotated with timestamped names, you must first run ls -l to identify the current active log filename before using cat to display its full contents. Why…

Perform Routine System Administration Tasks

Question

How can you view the entire contents of the current Avaya Aura@ Communication Manager (CM) call processing log file?

Options

  • Aby using the CM SAT to enter the list callp log all commands
  • Bby using the Linux cd to /var/log/Avaya and cat ecs.log commands
  • Cby using the Linux cd to /var/log/esc and ls -l commands to find current <log filename>; cat <log
  • Dby using the CM SAT to enter the display callproc log all command
  • Eby using the Linux cd to /var/log/Avaya and cat callproc.log commands

How the community answered

(27 responses)
  • A
    15% (4)
  • B
    7% (2)
  • C
    74% (20)
  • E
    4% (1)

Explanation

Option C is correct because the CM call processing log is stored in /var/log/esc, and since log files in that directory are rotated with timestamped names, you must first run ls -l to identify the current active log filename before using cat to display its full contents.

Why the distractors are wrong:

  • A & D reference the CM SAT (System Access Terminal) with commands like list callp log all or display callproc log all - these SAT commands don't exist in Avaya CM for viewing raw log file contents; the SAT is used for administration, not Linux log file access.
  • B points to /var/log/Avaya with ecs.log - the path is wrong (it's /var/log/esc) and the filename ecs.log is incorrect.
  • E uses the correct /var/log/Avaya path attempt but callproc.log is not the actual filename used by CM, and again the directory is wrong.

Memory tip: Think of "esc" in the path /var/log/esc as standing for "Engine Server Core" - the heart of CM call processing. Remember you always need to look before you read (ls -l first, then cat) because the log filename changes with rotation.

Topics

#log file management#Linux commands#Communication Manager diagnostics#file navigation

Community Discussion

No community discussion yet for this question.

Full 72201T Practice