T.R | Title | User | Personal Name | Date | Lines |
---|
2464.1 | What's in a (node) name | UTRTSC::SCHOLLAERT | Holland - San Marino : double digits... | Wed Mar 24 1993 12:32 | 9 |
| Hello Suzanne,
I think ALL-IN-1 displays those records from NETWORK.DAT which contain
a Node field not equal to the local node name. On a cluster
the match should be cluster alias.
Regards,
Jan
|
2464.2 | | KERNEL::COOPER | Suzanne Cooper UK Customer Support (833)3502 | Wed Mar 24 1993 13:09 | 6 |
| The node name field in profile is blank, the Network records have the
cluster alias. i.e there must be something set incorrectly so that the
search doesn't identify that the network records belong to that
node/cluster, hence my question.
Suzanne
|
2464.3 | More on NETWORK records for the local node being omitted | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Wed Mar 24 1993 13:49 | 15 |
| The 'Node' field in the profile has nothing to do with this. I don't even know
what it's for (although I'm sure Dave T will enlighten us :-), but don't worry
about it for this problem.
The search should omit any NETWORK records whose NODE field is the same as
OA$PRIMARY_NODE. There is a subtle bug in this area (possibly fixed in a
PFR :-) if you have a remote message router. I assume you don't, so this won't
be your problem.
As you say the problem only occurs on one node in the cluster, it seems most
likely that OA$PRIMARY_NODE is being incorrectly defined on that node. Check
its value on all nodes in the cluster: assuming you have a local message router,
and are running ALL-IN-1 V3.0, its value should be the cluster alias.
Scott
|
2464.7 | Clarification | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Wed Mar 24 1993 18:24 | 8 |
| >> Scott's reply which started talking about the NODE field in the Profile
>> when all the previous replies were talking about the NODE field in NETWORK
Not quite. .2 mentioned the profile field, which is why in .3 I said to
ignore it. I know better than to mention obscure profile fields for no
reason :-)
Scott
|