[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
|
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
3150.0. "Alarm rule disabled after exception is encountered." by SUBWAY::REILLY (Mike Reilly - New York Bank District) Tue Jun 09 1992 12:54
Why does a wildcard rule disable itself when an exception occurs?
eg:
::::::::::::::
mcc_notification.log_2
::::::::::::::
Alarm: indeterminate Domain JPM_DEV:.DOMAIN.CISCO_WAN Member * Rule wan
_cisco_cpu_peak encountered an exception 1992-06-09-11:29:30.203 Domain J
PM_DEV:.domain.cisco_wan [1,7]
Info1: %MCC-E-RECEIVEERROR, error trying to receive a packet<EOS>The rul
e has been disabled
Info2: (SNMP * cisco local lsystem avgBusy1 > 70, at every=00:02:00)
Text: WAN Cisco has high CPU utilization
Alarm: indeterminate Domain JPM_DEV:.DOMAIN.CISCO_WAN Member * Rule wan
_cisco_cpu_peak was disabled 1992-06-09-11:29:37.527 Domain JPM_DEV:.domain.c
isco_wan [1,8]
Info1: %MCC-E-RECEIVEERROR, error trying to receive a packet, The rule h
as been disabled
Info2: (SNMP * cisco local lsystem avgBusy1 > 70, at every=00:02:00)
Text: WAN Cisco has high CPU utilization
After we encounted the error message the rule is disabled, could the
alarms FM be modified to just log the exception and keep running.
- Mike
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3150.1 | | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Tue Jun 09 1992 13:18 | 4 |
| RECEIVE_ERROR is an RPC error message indicating that the target AM has
probably aborted so disabling the alarm rule is probably all that can
be done. Looks like an SNMP AM bug.
|