| 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 |
Anybody have any ideas why SMS V2.1 on VMS V5.4-2 should have alarm
rules going into disabled state with the error condition of :-
CANNOT COMMUNICATE WITH TARGET %-F-MBTOOSML,MAILBOX IS TOO SMALL FOR
REQUEST ..
Gary Lowe NUK CSC..
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2935.1 | What Entity is the Rule monitoring? | MOLAR::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Tue May 05 1992 14:57 | 13 |
> Anybody have any ideas why SMS V2.1 on VMS V5.4-2 should have alarm > rules going into disabled state with the error condition of :- > > CANNOT COMMUNICATE WITH TARGET %-F-MBTOOSML,MAILBOX IS TOO SMALL FOR > REQUEST .. Alarms was returned this error message when it called the Entity you specified in your Alarm Rule. What was the Rule Expression which caused this error? /keith | |||||
| 2935.2 | The rule that causes problem is... | PLUNDR::LOWEG | Don't believe a word | Tue May 19 1992 13:38 | 31 |
Thanks for the reply and sorry its taken so long getting back to your
question. Here is the alarm rule that is causing a problem..
creat mcc 0 alarms rule BRIDGE_CAE$TECH_LINE_1_COLLISIONS -
expression = (change_of(bridge .Br.Bridges.CAE$TECH LINE 1
COLLISION LIMIT EXCEEDED, *, *), at every
00:10:00), -
procedure = mcc_common:mcc_alarms_mail_alarm.com, -
exception handler = mcc_common:mcc_alarms_mail_exception.com, -
category = "Transmit Problem", -
description = "If a line cannot send a packet after 16 attempts -
this counter will increase. This is only true -
for lines on a LAN Bridge 200, and usually -
indicates that the line is very heavily used.", -
queue = "MCC_Alarms$Batch", -
parameter = "BBSPJGCR", -
perceived severity= Major, -
in domain BRSPVA_NS:.Br.Domain.BAe_Brough
And the same as above rule except LINE_2_COLLISIONS..
The customer has found that these rules have worked ok but after approx
2+ occurences he gets the CANNOT COMMUNICATE WITH TARGET %-F-MBTOOSML,
MAILBOX IS TOO SMALL FOR REQUEST error message when this alarm is
fired.
I am desperately trying to build a troubleshooting system from scratch
to see if I can reproduce this problem as its becoming a hot cookie..
Any help is very very welcome Gary Lowe CSC NUK..
| |||||