| Hi,
in general I've noticed, that it isn't possible to receive events from
the global entity. You have to specify a subentity (eg. LINE, CIRC) to
receive the event from.
The setup should be in this way (DECMCC - MCC node, SERVER - Event node):
MCC> DISABLE NODE4 SERVER LOCAL SINK MONITOR
MCC> SET NODE4 SERVER LOCAL SINK MONITOR NAME MCC_DNA4_EVL
MCC> CREATE NODE4 SERVER OUTBOUND STREAM DECMCC REMOTE SINK -
MONITOR CLASS=0, EVENT TYPE={1,2,3,4,5,6,7,8,9}
MCC> ENABLE NODE4 SERVER LOCAL SINK MONITOR
MCC> GETEVENT NODE4 SERVER LINE SVA-0 ANY EVENT
You need to have proxy access to a priviledged account on node SERVER, or to
specify BY USER = username, BY PASSW = password.
The perform a zero operation on the LINE SVA-0 entity and the event should
be received.
MCC> ZERO NODE4 SERVER LINE SVA-0
Hope this helps.
ChriS
PS.: Does anyone know when/if/why not it will be possible to receive events
from any classes. If I specify an event class 481 by an application it
is not related to any sub-entity, so no events can be received on MCC-
side. Is there a trick to make this possible (logical relation between
a event class and a subentity) ?
|
| I've found the correct way to receive the events from the network:
on the node where you want receive the event
MCC> DISABLE NODE4 local_node LOCAL SINK MONITOR
MCC> SET NODE4 local_node LOCAL SINK MONITOR NAME MCC_DNA4_EVL
MCC> ENABLE NODE4 local_node LOCAL SINK MONITOR
then, if you want to receive the events from your local node
MCC> CREATE NODE4 local_node OUTBOUND STREAM local_node REMOTE SINK -
_MCC> MONITOR CLASS=0, EVENT TYPE={1,2,3,4,5,6,7,8,9}
MCC> GETEVENT NODE4 local_node REMOTE NODE local_node ANY EVENTS
to receive the event from a remote node
MCC> CREATE NODE4 remote_node OUTBOUND STREAM local_node REMOTE SINK -
_MCC> MONITOR CLASS=0, EVENT TYPE={1,2,3,4,5,6,7,8,9}, -
_MCC> BY USER=xyz, BY PASSWORD=zxy (privileged)
MCC> GETEVENT NODE4 remote_node REMOTE NODE remote_node ANY EVENTS
On another session, if I perform
MCC> ZERO NODE4 (local or remote node)
I receive the notification from local or remote node
Thank you for your availability
Alberto
|
|
Re: .0
Two things may have happened here, and at least one of them is a bug.
1) On a VAX/VMS system, it is not possible to receive events from a
remote_node if you are not receiving them from the local_node
as well. I notice on your second attempt you did not disable the
event sink, so you were locally receiving all of the class 0 events
as well as receiving them from the remote_node. It is difficult to
tell if this is really a difference or not, but it may be the reason
you were successful.
2) Of greater concern (to me), is the second possibility:
I notice that you included user information to use a non-default
account on the remote system in your second attempt. Presumably,
this was to make sure that you were logged into an account with
enough privilege to perform the operation.
If your default account doesn't have the privilege to perform the
event setup on the remote node, you should have received an error.
Is this what you believe happened? If so, then there is a bug
somewhere in that interaction (either DECmcc dropped the error
message, or the remote_node didn't properly report the error).
Either way, we'll want to address it.
Do you have a theory about what it is that finally really worked for
you? That will help me to know what is happening.
-Jim Carey
P.S. NODE4 event reception: I will bug this. I'm not sure what we
will do about it. In a nutshell, the counters zeroed event looks like
it occurred against a Remote Node and not the global entity Node4.
This has to do with the way EXEC counters work in DECnet Phase 4. Most
of the Node4 counters reflect the interaction of the node with itself.
Oh well, I meant this to be quick, but I was wrong. Node4 counters
consist of about twenty counters. Most of these counters are actually
counting the amount of traffic between the node4, and itself as a
remote node. Most of the counters (aside from error counters) actually
reflect the "network" traffic created by operations like "SET HOST 0"
and the like. When these are zeroed, the event that is triggered looks
just like the "counters zeroed" event for any other remote node,
because, in fact, that is what is happening.
You may have noticed at one time or another that you don't have very
many executor counters (usually right after restarting your system).
You don't even have a "Seconds Since Last Zeroed" counter. This is
because your system has not yet had a connection to itself: it hasn't
seen itself as a remote node, so isn't keeping track of this.
We proposed separating these to make them cleaner, but opted instead to
present the information already familiar to DECnet users.
Anyway, there's two things we could do, and we'll try to squeeze one
of them in as soon as possible:
1 - never return these counters zeroed events against the global
entity Node4 and change the documentation.
2 - copy the event upon receipt and deliver it as both a Node4 event
and a Node4 Remote Node event, which is probably most correct, but
obviously the most work.
Preferences? Could you live with just 1 above?
-Jim Carey
|