| 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 |
Entered as QAR 159 in the MCC_013 QAR database. QAR # Status Sev Category Component Date in Date out ----- ------ --- -------- -------------- ------------ ------------- 00159 OP H MCC$ALARMS 12-FEB-1993 OCCURS RULE NOT FIRING ON SNMP LINK DOWN/UP TRAPS Reproducible at will: Y CPU Memory System device MCC T1.3.1 VAX/VMS V5.5 VAXstation 3100/M76, 32Mb After upgrade from V1.2 to T1.3.1 some SNMP traps no longer cause rule to fire. (This previously worked in V1.2). TOP LEVEL DOMAIN v v SECOND LEVEL DOMAINS v v THIRD LEVEL DOMAINS The SNMP entity issuing the traps is in a 'third level' domain. The traps show in the notification window as well as in incremented counters with a SHOW MCC 0 TCPIP_AM SINK ALL COUNT command. The following alarm rule, in the TOP LEVEL DOMAIN, never fires: Create Domain LOCAL_NS:.ovohio Rule SNMP_LINKDOWN - Expression = (OCCURS (SNMP * linkDown)), - Severity = Critical, - Category = "SNMP_LNKDN", - Also, showing the counters for this rule via the iconic map interface shows no incrementing of the counters. Some of the SNMP entities in some of the 'third level' domains behave correctly and fire this rule, others do not. With this problem, detection of network outages and subsequent unattended paging is not working properly. Thanks- Lee
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4538.1 | The SNMP entity has tobe a member of rule domain | TOOK::KWAK | Fri Feb 12 1993 18:03 | 20 | |
RE: .0
In DECmcc V1.2, the wildcarded OCCURS rules fire regardless of the
domain membership of the entity.
Suppose you have a rule expression:
OCCURS( snmp * any event) for domain .foo
When the Trap happens on entity called .ipbar, the Alarms rule did not
check if the entity .ipbar is a member of domain .foo, and fires
alarms. And all the domains to which ".ipbar" belongs received the
rule firing notification.
This was a BUG.
IN DECmcc V1.3 (T1.3.0), the Alarms FM makes sure that the entity
belongs to the domain (i.e. the ".ipbar" has to be a member of the
domain .foo in order for the above rule to fire).
William
| |||||
| 4538.2 | CSOADM::ROTH | MC5: Kick out the jams! | Sat Feb 13 1993 14:28 | 3 | |
Thanks, this should get me going... Lee | |||||