| 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 |
As I was setting up notify requests at my customer yesterday, we saw a strange phenomenon: As circuit down and circuit up events came in from a DECnet node, a notification was created for all the domains where this node is a member of PLUS ONE DOMAIN, FOR WHICH NOTIFICATIONS WERE ALWAYS CREATED, EVEN IF THE NODE4 ENTITY IS NOT A MEMBER. Anyone with a clue where to look for the cause of this ? EricV. p.s. this is for BMS V1.2.3 couple of 100 domains, in a 3 level hierarchy. notify request in top level domain for NODE4 * CIRCUIT *, (circuit down circuit fault, circuit up), expand=true primary domain contains 11 regional domains and the routers for those regions, which sink their events to the DECmcc node in the control center.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4752.1 | maybe a bug | TOOK::S_KO | Hoot mon! | Fri Apr 02 1993 15:05 | 4 |
are you explicitly specifying "expand = true"?
if so, please try the request without this argument (the default is to
expand anyways).
| |||||
| 4752.2 | Simple notify requests | BRSVMS::VDKERCKHOVE | Never say NEVER | Fri Apr 09 1993 04:59 | 14 |
Sorry for the delay, customer needed attention...
> are you explicitly specifying "expand = true"?
Nope, simple notify requests:
Notify Domain .PRIMAIR Entity List = (SABIN *), Events = (Any event)
Notify Domain .PRIMAIR Entity List = (NODE4 * CIRCUIT *), -
Events = (Circuit Down Circuit Fault, Circuit UP)
Notify Domain .PRIMAIR Entity List = (NODE4 * CIRCUIT * ADJACENT NODE *), -
Events = (Adjacency Down,Adjacency Up)
I'll QAR this if I need to ?
Eric.
| |||||
| 4752.3 | de-registered entity did it | BRSVMS::VDKERCKHOVE | Never say NEVER | Wed Apr 14 1993 16:38 | 15 |
Found it ! The domain trapping all notifications was the last successful return of a DIR DOMAIN .PRIMAIR MEMBER * domain .PRIMAIR had a de-registered domain. after deletion of this member and re-creation of the notify requests all works fine. at startup, MC warned me about a global entity being de-registered but withut telling which one. it took me quite a while to find the name of the de-registered global entity entity and i didn't correlate the 2 problems. it shouldn't be that difficult for mcc to include the name of the enity it found de-registered... EricV | |||||