[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1767.0. "DECNET/TCP_IP PC AND MAC MANAGEMENT" by PRSUD1::CARRAYROU () Wed Nov 06 1991 05:26

    Customers need to manage a lot of PC and MAC 
    
    
    I try to manage this kind of object
    
    DOS + PATHWORK 4.0
    
    >CD \decnet
    >SCH
    >DLLDEPCA
    >DNNETHATH
    >NML
    
    I USE THE NCP TELL COMMAND , A SUBSET WORKS 
    I CAN CHECK EXEC , LINE , CIRCUIT WITH STATE , CHAR , COUNTER QUALIFIERS
    
    I CAN REGISTER THE NODE AND USE THE MOST "SHOW COMMAND" 
    ( SHOW , RECORD , EXPORT ) WITH NODE4 , LINE , CIRCUIT ENTITIES . 
    THE "SET COMMAND" SEEMS VERY LIMITED ( REFERENCE )
    
    COULD WE IMPROVE THE NML IMPLEMENTION ON PC OR 
    COULD WE CREATE A PC ENTITY (SUBSET OF NODE4 ENTITY) USING DECNET IV AM
    
    
    MAC II CX PATHWORK MAC V1.0   
    THE PROBLEM WITH MAC IS DIFFERENT
    
    I USE THE NCP TELL COMMAND , A SUBSET WORKS 
    I CAN'T REGISTER A NODE4 ENTITY ( MAC )
    
    DECWINDOW MODE / MCC UNHANDLED SERVICE REPLY 
     /  NODE DOES NOT SUPPORT REQUESTED DIRECTIVE
    
    LINE MODE / MCC UNHANDLED SERVICE REPLY 
    / NML OBJECT NOT FOUND ON NODE
    
    COULD WE IMPROVE THE NML IMPLEMENTION ON MAC 
    
    
    I MANAGE PC USING PC NFS  WITH SNMPD START
    I CAN MANAGE A SUBSET OF THE MIB I , II  WITH DECMCC TCPIP AM 1.1
    
    
    INFORMATIONS OR DIRECTIONS ARE WELCOME .
    
    THANKS 
    
    DIDIER
                                   
    
                                           
    
T.RTitleUserPersonal
Name
DateLines
1767.1Pathworks has their own notes filesTOOK::MATTHEWSThu Nov 07 1991 17:3417
    I doubt that the Pathworks people monitor this notes file. I am
    surprised that you are getting as much to work as you have. DECmcc
    was developed against the Netman Spec with no specific testing for
    many of the different implementations of Nice beyond VMS, Ultrix,
    and Routers. It is the responsibility of the various NML implementers
    to check out their implementations. 
    
    For the SET verb. DECmcc implements the reference attributes as
    orphaned attributes. The NML never sees this operation. I suspect
    that the NML access priviledges are wrong so that you are never
    actually setting anything in the NML. Another possibility is that
    they have not implemented set.
    
    If you expect answers I suggest you post your note in one of their
    notes files on RANGER.
    
    wally