| 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 |
Hi, I have set-up MCC to monitor all the DECnet events coming from a few routers. These are X25ROUTERS, running DLM Circuit. Event 7.5 (Clear) and 7.10 (Call failure) don't get through to the MAP and NOTIFICATION windows, as if MCC_DNA4_EVL throws them away : with REPLY/ENABLE=NET I see them ariving at EVL. Is this normal ? Is there a list of events that are not forwarded to MCC by MCC_DNA4_EVL ? EricV.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4045.1 | Events 5.17-18 are missed too | EEMELI::VESALAINEN | DECnet Phase V = OSI for the Masses | Mon Nov 09 1992 04:22 | 3 |
I have also noticed that events 5.17 (DTE up) and 5.18 (DTE down)
are not getting through. This is a real pity if we want to monitor
x.25 connections.
| |||||
| 4045.2 | << PhaseIV Event >> | JASPIE::BALL | Thu Nov 12 1992 16:02 | 15 | |
Hi -
The events that are captured at this time are all Architected DECnet
PhaseIV events. Sorry about the X25 events but I believe (anyone in
management can correct me if I'm wrong) there was never any funding in
this area.
The architected events can be found in the Network Management
Functional Specification Version T4.3.0 section 7.
Thank you...
- darryl
| |||||
| 4045.3 | FS on the net ? | BRSVMS::VDKERCKHOVE | Never say NEVER | Fri Nov 13 1992 02:58 | 8 |
> The architected events can be found in the Network Management > Functional Specification Version T4.3.0 section 7. > Thank you... is that document available somewhere on the net ? Also thank you... | |||||
| 4045.4 | See PhaseIV AM Use manual | BAHTAT::LZOPCB::bond | Wed Nov 18 1992 10:48 | 14 | |
I think you will find that the events you can receive are documented as an appendix to the DECmcc PhaseIV AM use manual. From memory, there are a couple of tables, the first lists all the DECnet events and the second lists those that you can issue a GETEVENT for, along with the DECmcc node4 child entity that you issue GETEVENT against. It is only these listed events that are supported by the PhaseIV AM. Of course, you could always write a program that connects to the EVL event sink, picks up the X.25 specific events and uses the mcc_evc_send procedure to send the event to the data collector and target the correct node4 entity. Or use the script AM to poll the DTE state using ncp. But it is a shame it was never in PhaseIV AM - I suspect it is the single most asked for thing for node4. | |||||