| 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 |
Hello,
Can anyone explain the observed behaviour of Notification services with
respect to the following :-
2 notify requests, both expecting events from the designated router
(DR2000)
i) Notify domain xxxx entity node4 yyyy circ syn-* event circuit down
ii) Notify domain xxxx entity node4 yyyy circ ethernet adjacent node *
event adjacency down
When the relevant event occurs for i) then I get a single entry in the
notification window.
When an adjacency down occurs on the ethernet I *always* get 2 entries in
the notification window both having the same information and timestamp.
Software is DECmcc 1.2 (SSB)
There is only one domain in existence, and opcom shows that a single
adjacency down event is delivered.
Richard.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3543.1 | please rerun with log | TOOK::S_KO | Hoot mon! | Wed Aug 12 1992 12:49 | 10 |
hi Richard,
no, that doesn't sound right.
if you would please, define the logical MCC_NOTIFICATION_FM_LOG to be 6
and rerun your test (just case ii) and send me the log (took::s_ko)
Thanks!
-s
| |||||
| 3543.2 | verifying that both notifications are coming from a single notify request | MCC1::DITMARS | Pete | Mon Aug 17 1992 16:12 | 29 |
Hi,
Display the details of the duplicate notifications.
There's a field on the details window that shows the
ID of the originating notify request. If the IDs are
different, then it's a matter of the notify requests
somehow overlapping unexpectedly.
If you select both notifications and extract them to
a file, that will also show the notify request ID (the
first number in the [nn,nn] is the notify request ID).
And you can have the satisfaction of posting it here. :^)
If the IDs are the same, then indeed there is some duplication
going on somewhere inside the notif FM or dna4 AM.
To isolate it further, use FCL and do the following:
MCC> GETEVENT node4 yyyy circ ethernet adjacent node * -
adjacency down, FOR DUR 1:0:0
If two events come back for every one reported by OPCOM,
then there's either a problem with DNA4 or the event
is really being reported twice via DECnet and OPCOM is
just smart enough to filter the duplicate out.
If only one event is coming back, and it's turning into
two notifications for a single notify request, then there's
a problem in the notification FM.
| |||||