| 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,
Having now worked a fair amount with decnet event sinks I think I
now understand it well enough to ask the following question...
Given that I am sinked to a DECnet IV router (from an Ultrix WS running
1.2.7) and have targeted all "Node reachability status" messages to be
automatically sent to the correct node, my question is is there any way
to toggle the severity of the alarm based on the status of this event
ie. reachable/unreachable???
Note: the node reachability status is event 4.14 and seems to be the
only event my router reports when a endnode in the same area as the
router goes up or down. I would have thought I would also see
adjacency up/down messages but can't figure out how to get my router
to generate them.
Thanks and regards,
Peter Lamb
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2814.1 | see discussion in 2405.* | DADA::DITMARS | Pete | Mon Apr 27 1992 21:23 | 23 |
>my question is is there any way > to toggle the severity of the alarm based on the status of this event > ie. reachable/unreachable??? The short answer: there is not a clean way with the T1.2.7 kit. Please participate in 2405.* Event 4.14 is even worse than the events discussed in 2405, because the interesting information (up/down) is in the text of the event. Here's a real hack: 1) define a "null-domain" rule watching for event 4.14 which kicks off a batch job command procedure 2) the command procedure parses the event text and invokes the data collector to send an event "Node reachability change" targetted to the correct entity with the correct severity (e.g. Major if the text says the node isn't reachable, Clear if the text says the node is reachable again) You'll have to be judicious about where to employ this, as it sounds fairly expensive. | |||||
| 2814.2 | adjacent node events | TOOK::CALLANDER | MCC = My Constant Companion | Wed Jun 17 1992 17:19 | 2 |
have you tried looking for the node4 <router> circuit <> adjacent node <> circuit up and down events? they can be useful in this area. | |||||