| I am not completely certain I understand the question, but I will do my best ot answer what
I believe you are asking.
Events -- in reality events aren't "sent" from one node to another as much
broadcast on the net for receipt by any listener. So in the case
of DNA4 events, both MCC's can receive the decnet events if they
are both configured to be looking for them on the net and if
you have notify commands setup to give the info to the user.
Dir to Dir -- this was a bit less clear because I think you might be asking
for two different things here. Director to Director comunications
is coming, but not in this release. Director to Director will allow
a manager at MCC1 route a command through MCC2, so if they are
located on different lan segments, they can have access to
devices on the different segments (not all devices can be
managed across the wide area net).
But, I don't think that is really what you are looking for. It
sounds like what you really want is, every time a user on
either MCC does a SET directive you want to know about it on the
other MCC. To do this the easiest thing (if you are willing
to write some code) would be to enroll an FM that works like
the old control FM. It would pick up all requests destined
for AMs and pass them along. In your case you would want to
generate an event if you saw that the command is a SET command
and then pass it along (or possibly don't generate the event
unless you see success response). You could even use the
collection AM for the event generation. Just an idea.
|