From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Wed May 31 2006 - 11:48:35 ART
I would think that if you explain your logic and ask him how "they want
to see it"....this may help.
Dave Schulz,
Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com%20>
________________________________
From: CCIEin2006 [mailto:ciscocciein2006@gmail.com]
Sent: Wednesday, May 31, 2006 10:43 AM
To: Schulz, Dave
Cc: Koen Zeilstra; Bajo; ccielab@groupstudy.com
Subject: Re: logging trap severity level for category "alarms"
The semantics certainly can be tricky here. Do you think the proctor
would answer this question or would that give the answer away?
On 5/31/06, Schulz, Dave <DSchulz@dpsciences.com> wrote:
Koen -
There is not a category called "alarm", however....understanding what an
alarm is may help. An alarm would mean that there is a problem, or,
condition that cause a problem. Therefore, a level 4 (warning) would
have the closest meaning here, since the next message up from that
(notifications), defines this as being normal. Just my 2 cents.
Dave Schulz,
Email: dschulz@dpsciences.com
-----Original Message-----
From: nobody@groupstudy.com [mailto: nobody@groupstudy.com
<mailto:nobody@groupstudy.com> ] On Behalf Of
Koen Zeilstra
Sent: Wednesday, May 31, 2006 8:51 AM
To: Bajo
Cc: ccielab@groupstudy.com
Subject: Re: logging trap severity level for category "alarms"
Ok. Assuming the mapping in the router is correct:
router(config)#logging trap ?
<0-7> Logging severity level
alerts Immediate action needed (severity=1)
critical Critical conditions (severity=2)
debugging Debugging messages (severity=7)
emergencies System is unusable (severity=0)
errors Error conditions (severity=3)
informational Informational messages (severity=6)
notifications Normal but significant conditions (severity=5)
warnings Warning conditions (severity=4)
<cr>
Which one is category "alarms"???
-----------------------
Beware of Programmers who carry screwdrivers.
-- Leonard Brandwein
On Wed, 31 May 2006, Bajo wrote:
| The higher number in severity (which the lower severity) covers all
the
| numbers below ( which is higher severity)". From the Doc CD
"specifying the
| level *critical* causes messages as the critical (3), alert (2), and
| emergency (1) levels to be saved to the logging history table. " ( I
know
| the mapping in the Doc is not correct. Should be 2 1 0 respectively)
|
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123tcr/1
23tfr/cfrgt_04.htm#wp1100509
|
| So Severity 7 (debugging) will get all.
|
|
| On 5/31/06, Koen Zeilstra <koen@koenzeilstra.com> wrote:
| >
| > Hi group,
| >
| > If the task asks you to logg warning, alarms and cricital messages
to a
| > certain host, which severity level do you need to use?
| >
| > {0 | emergencies}. System is unusable
| > {1 | alerts}.Immediate action needed
| > {2 | critical}.Critical conditions
| > {3 | errors}.Error conditions
| > {4 | warnings}.Warning conditions
| > {5 | notifications}.Normal but significant conditions
| > {6 | informational}.Informational messages
| > {7 | debugging}. Debugging messages
| >
| >
| > warning -> 4
| > critical -> 2
| > alarms -> ??????
| >
| > Are alarms errors or notifications?
| >
| > So that would be either level 4 of level 5??
| >
| >
| > regards,
| >
| > Koen
| >
| >
| >
| > -----------------------
| > Isn't it strange that the same people that laugh at gypsy fortune
| > tellers take economists seriously?
| >
| >
This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:23 ART