Mark,
that type of ordering makes it hard to sort KNOWN critical situations from situations where the criticality is unknown. I would suggest that if a situation has known impact to the equipment then the equipment is able to ascertain if the situation is within INFORMATION to FATAL range. UNKNOWN would only be used if there is no clear impact to the equipment so this has to be tested outside the scope of the equipment. The test then would be put UNKNOWN in it's own bucket (severity==0) for further analysis and then respond based on value of severity. Whether this is an increasing or decreasing order is entirely arbitrary IMO.
I have no idea what 'cleared' means but it smells like trying to encode state into the severity of the problem and that probably isn't a good thing.
Thomas W. Studwell
Senior Technical Staff Member, Autonomic Computing Architecture
IBM Software Group
C151/Bldg 500
4205 S Miami Blvd, Durham, NC 27703
(919) 254-7574 Fax: (919) 254-7628 Mobile: (919) 619-1038
studwell@us.ibm.com
"What marks the mind of the strategist is an intellectual elasticity or flexibility that enables him to come up with realistic responses to changing conditions... In strategic thinking, one first seeks a clear understanding of the particular character of each element of a situation and then makes the fullest possible use of human brainpower to restructure the elements in the most advantageous way." (Keniche Ohmae, The Mind of the Strategist)
Mark Ellison <ellison@ieee.org>
11/22/2004 12:44 PM |
|
This is from the ITU-ALARM-TC-MIB published in RFC 3877. Note the references to ITU M.3100 and &.733...
ItuPerceivedSeverity ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ITU perceived severity values"
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
SYNTAX INTEGER
{
cleared (1),
indeterminate (2),
critical (3),
major (4),
minor (5),
warning (6)
}
Thomas Studwell wrote:
- From our experience I would recommend UNKNOWN starting at 0 (zero) with the other levels incrementing by values of 10 so range is 0 to 70.
Thomas W. Studwell
Senior Technical Staff Member, Autonomic Computing Architecture
IBM Software Group
C151/Bldg 500
4205 S Miami Blvd, Durham, NC 27703
(919) 254-7574 Fax: (919) 254-7628 Mobile: (919) 619-1038
studwell@us.ibm.com
"What marks the mind of the strategist is an intellectual elasticity or flexibility that enables him to come up with realistic responses to changing conditions... In strategic thinking, one first seeks a clear understanding of the particular character of each element of a situation and then makes the fullest possible use of human brainpower to restructure the elements in the most advantageous way." (Keniche Ohmae, The Mind of the Strategist)
Homayoun Pourheidari <homayoun@bea.com>
11/19/2004 08:07 PM
|
|
I don't think the colors are standardized. I suggest 0-7, in descending
order.
H.
--
Vambenepe, William N wrote:
>Severity is defined as a "short" in the pseudo schema but the
>description of the value contains strings (and colors, how cute), not
>numbers:
>
>o FATAL - Condition is unrecoverable and the service is no longer
>available.
>o CRITICAL (Red) - Condition that affects service has occurred.
>Immediate corrective action is required.
>o MAJOR (Orange) - Problem with a relatively high severity level
>has occurred. It is likely that normal use of the object will be
>impeded.
>o MINOR (Yellow) - Problem with a relatively low severity level
>has occurred. It is unlikely that normal use of the object will be
>impeded.
>o WARNING (Cyan) - Problem that affects service will or could
>occur. Diagnostic and corrective action is recommended.
>o INFORMATION (Green) - Message output is normal (that is, what
>was expected). For example, a process begins, a process finishes, or
>status information is displayed.
>o UNKNOWN (Blue) - Severity level cannot be determined.
>
>Am I supposed to change the type to a restriction of xs:string? OR to
>provide a mapping from numbers to these values? If so, what's the range?
>0-100 (if yes how do I map?), 0-70, 0-6, 1-7...
>
>What is the value of these colors? Do I get to color ResourceId in
>purple?
>
>William
>
>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.
>
>
>
>
[attachment "homayoun.vcf" deleted by Thomas Studwell/Raleigh/IBM] To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.
