Conference azur::mcc

548.0. "Can't Access V4.0 PCSA " by DUCAT2::64544::LICAUSE (Al Licause (338-5661)) Wed Dec 12 1990 19:58

I understand that I'm pitting one field test against another, but I'll ask
anyway.

In V1.1 IFT I was able to register and communicate with my DECstation 325c
running V4.0 FT of PCSA.  I could query it and get responses just as with
any other NODE4 type entity.  (V4.0 has an NML object which will respond
w/o having to spawn it).

Now in V1.1 EFT, when I try to do any sort of access to the same PC, I get
"Node terminated link before link confirmation."

I see by using the unsupported TREE utility with DNS, that there is an
entry for the PC, FOUR42 under stations or more precisely the directory
.MCC_STATIONS_BACK...  tree does not show the entire directory name unless
this is it.  If I traverse the tree it shows a child with the correct
08...ethernet address.

When I try to do a SHOW STATION FOUR42 anything, it responds with
Unknown entity.

Has anything changed in EFT which would cause access to such a system
to stop working or have I done something wrong?

I can access the PC using NCP tell commands and the response is immediate!

The PC was registered or at least what is already in DNS, using the
MCC setup command procedures.

I also have no trouble accessing any other VAX's or VAXstations in the
same manner.  Just for kicks I tried ERASEing and DEREGISTERing one of
the existing VAXstations that I can access.  All worked well.  I then
reregistered the same station and it took, and was able to then to
queries to that station?

A Bug or Feature?

Al

    
    
    
    
    
    
    I experienced the same "node terminated link before confirmation"
    when communicating with PCs. I entered a QAR, 1333, MCC_DEV database.
    Here's the answer
    
    "This is a known problem, we have new code ready to go.
    
    We check Node4s to find out whether they are multi-link capable or not.
    
    The PCs return an unexpected error on our attempt to start up the
    second link.
    We have further enhanced this multi-link checking to correctly failover
    to single link mode on any error that looks like it could be from normal
    management resource error."

RE:.1

thanks very much for this information.....I should really try to access
the QAR system 1st.

But I'm wondering if this same problem could be the reason that I can
no longer talk to our PRINTSERVER 20 since upgrading to EFT?

Al

by the way, can someone tell me where the QAR system for MCC is and if it
is available to anyone internal.....?

If not generally available, how about those of us that will be supporting
a field test site?

Al

Al,
Send mail to TOOK::Roscoe

Fred