T.R | Title | User | Personal Name | Date | Lines |
---|
4082.1 | Entity Inaccessible | MARVIN::COBB | Graham R. Cobb (DECNIS development), REO2-G/G9, 830-3917 | Tue Nov 17 1992 10:53 | 6 |
| When you get Entity Inaccessible for a Phase V node it is always worth
trying with NCL and then with the command line interface to MCC. Those two
only rely on the DEMSA being up and the node name being set up correctly in
the NCP database for the host. Have you tried either or both of those?
Graham
|
4082.2 | we are seeing this intermittently | COOKIE::HOLSINGER | Carp� per diem | Tue Nov 17 1992 13:31 | 14 |
|
We are also seeing this phenomenon.
Have a VMS MOM registered to manage MEDIALIBRARY subclass of NODE.
We occasionally see this occur during a Show All Attributes directive,
sandwiched between two successful replies.
Environment is VMS V5.5-2, MCC V1.2 and DMS EFT2.
It does not seem to be an NCP configuration database problem.
Any ideas would be most welcome.
Also, please adjust the title of this note if possible.
-Paul
|
4082.3 | | VF::LANGASQUE | | Tue Nov 24 1992 10:21 | 23 |
| We have this kind of config,
AREA 1
DEMSA 1 DEMSA 2
| /
| /
| /
| /
| /
| /
DEMSA 3
AREA 2
By default demsa 2 is the designated router from area 1.
In MCC demsa 2 and 3 are accessible, demsa 1 is inaccessible.
If i disable demsa 2 routing circuit, demsa 1 become accessible.
When i re-enable demsa 2 demsa 1 is inaccessible again.
Eric
|