Topic: 200-301 topic 1 question 969

An engineering team asks an implementer to configure syslog for warning conditions and error conditions. Which command does the implementer configure to achieve the desired result?

A.
logging trap 5
B.
logging trap 2
C.
logging trap 3
D.
logging trap 4

Re: 200-301 topic 1 question 969

0Every 1Awesome 2Cisco 3Engineer 4Will 5Need 6Icecream 7Daily

Re: 200-301 topic 1 question 969

A. logging trap 5: This sets the logging severity level to "notifications." Syslog messages at this level include system notifications that are not errors but are important for system administrators to be aware of, such as interface status changes.

B. logging trap 2: This sets the logging severity level to "critical." Syslog messages at this level include critical system events that require immediate attention, such as system crashes or severe errors.

C. logging trap 3: This sets the logging severity level to "errors." Syslog messages at this level include error messages that indicate problems within the system, such as configuration errors or service failures.

D. logging trap 4: This sets the logging severity level to "warnings." Syslog messages at this level include warning messages that indicate potential issues or conditions that may lead to problems if not addressed, such as high CPU usage or interface errors.

Re: 200-301 topic 1 question 969

D is correct

Re: 200-301 topic 1 question 969

Option 'd' is correct.
Wow, I screwed that one up completely :-)
In this question, the logging trap 4 command sets the logging severity level to warning (level 4). This means that log messages with severity levels 0 to 4 will be sent to the syslog server. You can adjust the severity level according to your requirements.

Here's a brief overview of syslog severity levels:

Emergency (0):     System is unusable.
Alert (1):         Action must be taken immediately.
Critical (2):         Critical conditions.
Error (3):         Error conditions.
Warning (4):         Warning conditions.
Notice (5):         Normal but significant conditions.
Informational (6):     Informational messages.
Debugging (7):     Debugging messages.

Therefore, option ‘d’ is correct.

Re: 200-301 topic 1 question 969

Doh - I should have said option 'c' , not 'd'.  Mea Culpa.

Re: 200-301 topic 1 question 969

The answer is option 'd'.
The confusion students have with this question is that the command identifies the logging level *and below* that are sent to the syslog server.  By issuing the command: logging trap 3, it identifies error (3), warning (4), notification (5), informational (6), and debugging (7).  No other command will include both error (3) and warning(4).

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960x/software/15_2_6_e/configuration_guide/b_1526e_consolidated_2960x_cg/b_1526e_consolidated_2960x_cg_chapter_01000010.pdf

Re: 200-301 topic 1 question 969

D. Doing the command with a 4 should return logs for 0-4.
Doing it with a 3 should return logs for 0-3

Re: 200-301 topic 1 question 969

Correct

Re: 200-301 topic 1 question 969

Answer D

Re: 200-301 topic 1 question 969

D is correct

Re: 200-301 topic 1 question 969

C. logging trap 3

Explanation:
The logging trap command is used to set the severity level for syslog messages that will be sent to the syslog server. The severity levels range from 0 to 7, with 0 being the most severe and 7 being the least severe.

In this scenario, the engineering team wants to configure syslog to capture warning conditions and error conditions. The severity level for warning messages is 4 (warning) and for error messages is 3 (error).

Therefore, by using the command logging trap 3, the implementer will configure syslog to capture and send error messages to the syslog server.

Re: 200-301 topic 1 question 969

From your explanation, we know the answer is D, not C. If we configure logging trap 3, we can't capture a warning message.

Re: 200-301 topic 1 question 969

D is correct !

Table 3 Message Logging Level Keywords
Level Keyword
Level
Description
Syslog Definition
emergencies
0
System unstable
LOG_EMERG
alerts
1
Immediate action needed
LOG_ALERT
critical
2
Critical conditions
LOG_CRIT
errors
3
Error conditions
LOG_ERR
warnings
4
Warning conditions
LOG_WARNING
notifications
5
Normal but significant condition
LOG_NOTICE
informational
6
Informational messages only
LOG_INFO
debugging
7
Debugging messages
LOG_DEBUG

Re: 200-301 topic 1 question 969

0- Every - emergency
1-Awesome - alert
2-cisco - critical
3-engineer - error
4-will - warning
5-need - notification
6-ice - informational
7-dailly - debug