| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2645.1 | Another case of no notification in cluster | 34071::ANDRES_B | | Tue May 13 1997 17:21 | 24 |
| Hello,
I have a customer would like to know why he does not receive
the notification on the NT box. The configuration is similar
to .0.
They have ALL-IN-1 installed on both nodes of the cluster.
One node is a VAX the other an Alpha. The Alpha is running
TCP/IP. If the TeamLinks user connects to the Alpha system
from TeamLinks and sends a message to them self then they don't
receive notification. If they connect from a VT session to
the same account and send a mail message to them self then
the TeamLinks user does get notification. The notification
just does not work if sending the message from the TeamLinks
client.
Why does TCP/IP have to be running on both nodes for notification
to work, if the node you are connecting to has TCP/IP. How does
it work with the other node (the VAX in this case)?
Thanks,
Beth Andres
|
| 2645.2 | always use sender | UTRTSC::SCHOLLAERT | Think before you shrink | Wed May 14 1997 08:45 | 17 |
| Hi,
Let me guess.
When sending mail from TeamLinks, the ALL-IN-1 sender takes care
of the the new mail notification. So running the sender on the
node where TCP/IP is running should fix the problems.
When sending mail from ALL-IN-1 VT, the new mail notification is
generated directly. So this works when TCP/IP is running on the
node the ALL-IN-1 VT user is logged in. Workaround might be
modifying form EMHEAD to prefine PRIORITY to SECOND_CLASS resulting
in ALL-IN-1 using the sender to deliver the message.
Cheers,
Jan
|
| 2645.3 | UCX all round | IOSG::SEATON | Ian Seaton, IOSG Office Server Development | Tue May 27 1997 11:32 | 13 |
| For reliable notifications, UCX needs to be available on all nodes in
the cluster. This limitation is set by the Broadcast Server which by
design only processes locally generated messages. If a message is
processed on nodes where UCX is not installed, Teamlinks Clients
recipients of the message that use TCP/IP will not be notified because
the Broadcast Handler cannot use TCP/IP to send the notification.
There is no work-around other than to only process messages on nodes
where all network transports used are available.
Ian
There is further discussion of this problem in note 2691.
|
| 2645.4 | I hope just one more question | OASS::ANDRES_B | | Tue May 27 1997 18:33 | 17 |
| I have one more question for this site before we all have a clear
understanding of what is going on. I hope this is the last hole
in this scenario, anyway.
It is understood that the sender or fetcher pass the notification
to the broadcast server and this all makes sense. Now if a VT user
on an node that is running UCX sends a message to a user on this
node that is connecting via TeamLinks the TeamLinks user will get the
notification. Now since these users are on the same node and the
message was initiated from the VT user, and my understanding is that
the sender should not be involved, what is sending the notification
to the broadcast server.
Thanks,
Beth
|
| 2645.5 | I hope I have the correct answer | 34071::ANDRES_B | | Fri May 30 1997 14:18 | 10 |
| Well after waiting for a couple of days and not getting a response
I started asking around about this issue. I was told the send code
in IOS sends the broadcasts. I am assuming the broadcasts are sent
via VMS broadcasts and to the Broadcast server.
If this is not correct please let me know. This is what I will relay
to the customer.
Beth Andres
|