| 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 |
A customer reported a problem with alarm rules not being fired after upgraded DecMcc from V1.2 to V1.3. This alarm rules monitors SNMP link up and down event transmitted from Translan bridges. The rules get fired when two traps of the same type is detected within 2 seconds. This is done in order to overcome a problem with SNMP implementation on Translan bridges whereby two linkdown traps and one linkup trap are sent for each linkdown event; and two linkup traps and one linkdown trap are sent for each linkup event. After the upgrade, the linkdown alarm rules was never fired. He monitored the incoming traps and is satisfied that the correct traps were being received by the MCC station. By deleting the old rules and redefining them, the new rules works fine. The only difference that he has noticed with the new alarm rule is that the format of the time duration was changed. In the old rule, the time duration is : 00:00:02 In the new rule, the time duration is : 00:00:02.00 ^^^ He is going to upgrade another MCC system shortly and will report back whether this is a generic problem. Has anyone experienced this problem before? Is this a likely explaination for this change in behaviour? Any ideas welcomed. Regards, Denny.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5331.1 | Similar problem with NODE4 alarms | SNOC01::MISNETWORK | MCC=My Constant Confusion | Wed Jul 14 1993 03:21 | 14 |
Denny,
we had a similar problem with DECnet alarms after upgrading to 1.3. We
use an alarm rule with the following expression -
OCCURS(NODE4 * CIRCUIT * ANY EVENTS)
This rule was enabled in a domain called DECMCC. Turns out that after
upgrading, this rule would not fire because the NODE4 that reported
the circuit events were not a member of the domain DECMCC. This worked
fine in V1.2, but in 1.3 you have to register the devices in the same
domain that the rule is registered in.
Cheers,
Louis
| |||||
| 5331.2 | ANTIK::WESTERBERG | Stefan Westerberg DS Stockholm | Wed Jul 14 1993 10:21 | 10 | |
Upgrading form V1.2 -> V1.3 seems to break the SNMP trap alarms. We have seen this on all our system when we upgraded them. The solution is to redefine all snmp occur rules. /Stefan P.S. Let SYS$SYSTEM:MCC_ALARMS_EXTRACT_RULES.EXE do the job. | |||||