| 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 am using DECmcc T1.2.4 under Ultrix 4.2A. I try to receive events
from my local node4 node (FISHER). I have installed the special evl image
and I ran the mcc_dna4_evl_setup.sh script. Under mcc iconic map I activate
the notification services with a notify request on node4 FISHER. I generate
some DECNET events under NCP (they are displayed at the console), this
does not activate a notification message
...
I reproduce there the NCP and MCC output showing that the logging
monitor is really going to the /usr/etc/mcc_dna4_evl_monitor process. So
what is wrong ? Is there a way to get a log of mcc_dna4_evl_monitor.
Thanks for your help.
ncp>sho k logg
Known Logging Volatile Summary as of Tue Mar 3 12:02:38 WET 1992
Logging = console
State = On
Name = /dev/console
Sink node = 47.859 (FISHER), events =
0.0-9
2.0-1
3.0-7
4.0-19
288.0-31
Logging = file
State = Off
Name = /usr/adm/eventlog
Logging = monitor
State = On
Name = /usr/etc/mcc_dna4_evl_monitor
Sink node = 47.859 (FISHER), events =
0.0-9
2.0-1
3.0-7
4.0-19
ncp>
MCC> show node4 fisher local sink monitor all attributes , via port = ln0
Node4 47.859 Local Sink Monitor
AT 1992-03-03-12:15:21.270+00:00Iinf All Attributes
Type = Monitor
State = On
Name = "/usr/etc/mcc_dna4_evl_monitor"
Initial Type = Monitor
Initial Name = "/usr/etc/mcc_dna4_evl_monitor"
Initial State = On
MCC> show node4 fisher outbound stream fisher remote sink monitor all attribute
, via port = ln0
Node4 47.859 Outbound Stream 47.859 Remote Sink Monitor
AT 1992-03-03-12:17:57.328+00:00Iinf All Attributes
Type = Monitor
EventsFilter = { (
Choice = C5,
Source_Entity = All Sources,
Event = { 0.0 event records lost,
0.1 automatic node counters,
0.2 automatic line counters,
0.3 automatic service,
0.4 line counters zeroed,
0.5 node counters zeroed,
0.6 Passive loopback,
0.7 Aborted service request,
0.8 Automatic counters,
0.9 Counters zeroed } ),
(
Choice = C5,
Source_Entity = All Sources,
Event = { 2.0 Local node state change,
2.1 Access control reject } ),
(
Choice = C5,
Source_Entity = All Sources,
Event = { 3.0 Invalid message,
3.1 Invalid flow control,
3.2 Data base reused,
3.3 Cryptographic failure
Remote Node,
3.4,
3.5,
3.6,
3.7 } ),
(
Choice = C5,
Source_Entity = All Sources,
Event = { 4.0 Aged packet loss,
4.1 Node unreachable packet los,
4.2 Node out-of-range packet
loss,
4.3 Oversized packet loss,
4.4 Packet format error,
4.5 Partial routing update loss,
4.6 Verification reject,
4.7 Circuit down circuit fault,
4.8 Circuit down,
4.9 Circuit down operator
initiated,
4.10 Circuit up,
4.11 Initialization failure
line fault,
4.12 Initialization failure,
4.13 Initialization failure
operator initiated,
4.14 Node reachability change,
4.15 Adjacency up,
4.16 Adjacency rejected,
4.17 Area reachability change,
4.18 Adjacency down,
4.19 Adjacency down operator
initiated } ) }
Initial Events Filter = { (
Choice = C5,
Source_Entity = All Sources,
Event = { 0.0 event records lost,
0.1 automatic node counters,
0.2 automatic line counters,
0.3 automatic service,
0.4 line counters zeroed,
0.5 node counters zeroed,
0.6 Passive loopback,
0.7 Aborted service request,
0.8 Automatic counters,
0.9 Counters zeroed } ),
(
Choice = C5,
Source_Entity = All Sources,
Event = { 2.0 Local node state change,
2.1 Access control reject } ),
(
Choice = C5,
Source_Entity = All Sources,
Event = { 3.0 Invalid message,
3.1 Invalid flow control,
3.2 Data base reused,
3.3 Cryptographic failure
Remote Node,
3.4,
3.5,
3.6,
3.7 } ),
(
Choice = C5,
Source_Entity = All Sources,
Event = { 4.0 Aged packet loss,
4.1 Node unreachable packet los,
4.2 Node out-of-range packet
loss,
4.3 Oversized packet loss,
4.4 Packet format error,
4.5 Partial routing update loss,
4.6 Verification reject,
4.7 Circuit down circuit fault,
4.8 Circuit down,
4.9 Circuit down operator
initiated,
4.10 Circuit up,
4.11 Initialization failure
line fault,
4.12 Initialization failure,
4.13 Initialization failure
operator initiated,
4.14 Node reachability change,
4.15 Adjacency up,
4.16 Adjacency rejected,
4.17 Area reachability change,
4.18 Adjacency down,
4.19 Adjacency down operator
initiated } ) }
MCC>
MCC> show node4 fisher local sink monitor all attributes ,via port = ln0
Node4 47.859 Local Sink Monitor
AT 1992-03-03-14:38:07.832+00:00Iinf All Attributes
Type = Monitor
State = On
Name = "/usr/etc/mcc_dna4_evl_monitor"
Initial Type = Monitor
Initial Name = "/usr/etc/mcc_dna4_evl_monitor"
Initial State = On
MCC>
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2470.1 | How did you make it work? | STRASB::EBLE | Tue Mar 17 1992 12:45 | 13 | |
Hi,
it's still not working. If it is working on your Ultrix site, could
you reply giving the result of a :
show node4 [yournode] local sink monitor all attributes
and a :
show node4 fisher outbound stream fisher remote sink monitor all attribute
Just to see if Imade a mistake setting the decnet event logger.
Thanks.
| |||||