|
I'm not very familiar with the demo and what it comes with (Rob,
Claudia, you guys know your way around that, right?) but I am familiar
with DECnet phase 4.
Unfortunately, the "Internal Error in DECnet Phase IV AM" is the error
you will get whenever something occurs way outside of the AMs
expectations. Hopefully, that isn't very often any more.
Couple of things could be going wrong here, and if you can get me some
more information, either I'll be able to shed more light on it or
someone else will.
The problem is either related to the DNS setup, or it's related to
something specific and strange about your node4, Reggae.
Try the following requests to Node4 Reggae:
SHOW NODE4 reggae ALL IDENTIFIERS
SHOW NODE4 reggae CIRCUIT * ALL IDENTIFIERS
SHOW NODE4 reggae CIRCUIT * ALL CHARACTERISTICS
SHOW NODE4 reggae LINE * ALL IDENTIFIERS
SHOW NODE4 reggae LINE * ALL CHARACTERISTICS
These requests are done on your behalf by the registration FM as part
of the register procedure. If any of these requests fail to work,
please try the corresponding NCP requests, such as:
MCC> SHOW NODE4 reggae LINE * ALL CHARACTERISTICS
information can be retrieved using the NCP command:
NCP> TELL reggae SHOW KNOWN LINE CHAR
or if it's the local node, just SHOW KNOWN LINE CHAR.
The error you've gotten may also indicate some error in the DNS setup
of the MCC Instance Repository (which happens to be kept in the
namespace). Assuming that these requests work, we'll pursue that
next.
Please respond via MAIL to TOOK::CAREY (that's me) in order to keep the
notes file uncluttered, and to get you best response.
-Jim Carey
|