| Is cross-group verification on? Does the Sun or the NT machine have
more than one network interface?
I often see this when there are multiple network interfaces in use, and
xgroup verification is on. What typically happens is that the
initiator ("A") sends its request through one interface on the
non-initiator ("B"), the one that the host name in A's xgroup table
resolves to - then the outbound link is established. Then B sends its
request for the inbound link to A - but B's routing table is configured
to send to A's IP address through the second interface whose IP address
does not match the hostname in A's table. Right host name, wrong IP.
You can see this on A by using netstat -a during the brief time when
the inbound link exists, but at least in v3.2A, you see no log entry on
A other than "ld, operation failed to complete" and the exit messages
for dmqld (at least it doesn't when B's second address is not
resolvable to a name).
Unix DmQ v3.x, with the exclusion of v3.2A, does not support operation
over multiple interfaces. If you do have multiple interfaces, and one
or more that do not match the IP address of "hostname" is being used
for DmQ traffic, then you need to use v3.2A on that machine - or turn
xgroup verify off on the other machine(s).
My guess is that the same applies to NT DmQ, since it's based on the
same code, but DmQ engineering will have to answer that one. Also,
there is no 3.2A for NT, I guess you will may have to wait for 4.0 on
NT for multiple-interface support (ask engineering on that one too).
(In the case of B using something like ServiceGuard or Sun IP
Switchover (or whatever it's called), with "floating IP" addresses, B's
host name will not match either, and you will get a log message on A
saying "host XYZ port 11111 not found in local address database" or
something similar, where XYZ is the "native" hostname, which was not in
A's xgroup table (i.e., XYZ is what you get when you use the "hostname"
command on B)).
|