[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 |
2602.0. "alarming execptions problem" by COL01::LUNT () Fri Mar 20 1992 10:31
Hello,
Due to lack of response from the QAR system, I am entering
this here in the notes file. I really need to get the alarming
working properly
Julie Ann
(20-mar-1992)
Recently I created alarm rules for 15 bridges. Each bridge has three
rules, one for reachability(device operating) and one for
each port(that the port is in forwarding state). The alarms poll every
5 minutes. I recieve one of the following two exceptions on 20-50% of
the alarms every time they execute.
The first message implies that perhaps my system or network too busy is for
the poll. But the second baffles me. Why would I get such a message? Do the
two have anything to do with one another? Do these messages have anything to
do with a V1.1 problem that I would get frequent exception messages of the
form: Error trying to transmit a packet, device inactive?
Julie Ann
Rule name: MCC 0 ALARMS RULE BYLN10_line_2_not_forwarding
Domain: Domain DECNOS_NS:.EU.BY.BYL.B151
Occurred at: 4-MAR-1992 16:37:46.23
Category: BRIDGE reachability
Description: BYLN10 Line 2 not in forwarding state
Severity: Indeterminate
Expression: (BRIDGE .EU.BY.BYL.BYLN10 line 2 port module state <>forwarding, at every=00:05:00)
Exception: Communication with the target has been interrupted
--------------------------------------------------------------------------
Rule name: MCC 0 ALARMS RULE BYLN06_line_2_not_forwarding
Domain: Domain DECNOS_NS:.EU.BY.BYL.O13
Occurred at: 4-MAR-1992 16:37:28.16
Category: BRIDGE reachability
Description: BYLN06 Line 2 not in forwarding state
Severity: Indeterminate
Expression: (BRIDGE .EU.BY.BYL.BYLN06 line 2 port module state <>forwarding, at every=00:05:00)
Exception: The requested operation cannot be completed
%MCC-E-INVDEVNAM, invalid Ethernet device specified.
T.R | Title | User | Personal Name | Date | Lines |
---|
2602.1 | This is a bridge (ethernet) problem | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Fri Mar 20 1992 13:23 | 14 |
| Julie Ann,
Both of the exceptions you have shown:
> Exception: Communication with the target has been interrupted
>
> Exception: The requested operation cannot be completed
> %MCC-E-INVDEVNAM, invalid Ethernet device specified.
are errors returned from the Bridge Access Module to Alarms.
Could someone on the Bridge / Ethernet project help on this one ?
/keith
|
2602.2 | Some known MCC_EA problems w/T1.2.4 | CHRISB::BRIENEN | DECmcc LAN and SNMP Stuff... | Fri Mar 20 1992 16:52 | 11 |
| I had to go looking to find this one: QAR#300, MCC_EXT_V1_2, 3/5/92
(for some reason I don't get copied on QARs for the ALARMS component)..
There were some MCC_EA (Ethernet Access common routine) problems recently
discovered/fixed in MCC that involved mis-handling of device tables.
The symptom was spurious %MCC-E-INVDEVNAM errors when issuing Bridge (and
Station) requests.
These fixes will appear in the DECmcc EFT Update code...
Chris
|