Conference azur::mcc

    
    Hi,
    
    I am not quite sure what your question is, so let me try to clarify
    a few things and then possibly we will understand the question better.
    
    DECmcc is a product family name. The current family consists of the EMS
    (Enterprise Management System) and SMS (Site Management System)
    products. These products have taken the older point products like
    DECnet Monitor and RBMS and reworked them so that they can coexist on a
    single system, and so that the interfaces are DECwindows based. To the
    best of my knowledge, I believe that other fixes and enhancements have
    also been made. The difference between the two products has to do
    with types of devices can be managed by each.
    
    The "futures" products, that were announced at DECworld, are the Director
    and BMS (Basic Management System). These two are currently available
    in their field test versions. They are the first EMA (Enterprise
    Management Architecture) compliant directors. They provide a plug-in
    environment that can be customized with the management modules that
    suit your needs, with all modules using the same interfaces and
    (forms and command line or decwindows) a cenralized data store.
    
    Each of these products have their advantages and disadvantages.
    If you state what your needs are we can probably help you in figuring
    out just what products suit your needs and why we would suggest
    it over the older point products.

    
    (This was a VERY brief synopsis of the products, a lot more detail
    is available if you are interested. A good starting place would
    be the MCC Introdution manual.)
    

    Thank you!
    I think I will become a bit more familiar with DNS then go onto
    DECmcc and in the mean time stick to running the diffirent products
    by themselves.
    
    REgards,
    
    By the way I have installed DECmcc but very early on and lost interest
    because I did not know DECwindows all that well but now that I have
    a bit more experience I will look forward to using DECmcc more.

    And what exactly is going to "happen" to ETHERnim, DECnet Monitor and
    friends when DECmcc BMS ships? Fade away, or will they plug into the
    director?
    
    hw

    NMCC/VAX ETHERnim, NMCC/DECnet Monitor, and other network management
    point products will still exist for some time as individual products
    AND within the two DECmcc Management Station (SMS and EMS) products.
    
    Over time, each point product's functionality will be superseded; at
    that time, the point product (eg, ETHERnim) will be retired (in some
    form).
    
    Lisa 

    
    Is the goal to build the point products' functionalities into a module
    or are they going to be spread throughout various AMs and FMs (eg
    Ethernet topology management in one FM, Ethernet activity in another?)
    
    Also is it possible to say what path DECelms will be taking to become
    EMA-compliant.
    
    rgds,
    hw

    RE: 239.5 (I presume we shouldn't even try to sell anymore ETHERnim)
    
    RE: point-products vs modules
    
    Point products implement functionality that get replaced by AMs, FMs,
    and (conceivably) PMs. Using ETHERnim as an example: MAP gets replaced
    by PM, Database/Configuration/"alarms" info gets replaced by multiple
    FMs, Ethernet/DECnet functions get replaced by multiple AMs.
    
    Please continue selling the point products (hopefully as part of the
    DECmcc "management station"), since they provide valuable functionality
    for users. MCC will be developing tools to make migration to the "real"
    MCC much easier.
    
    RE: DECelms path to EMA-compliance
    
    The MCC V1.0 (i.e. Bridge AM + FMs + FCL PM) replace the RBMS point
    product. DECelms is a superset of RBMS.
    
    The path for DECelms: migration of its existing functions into MCC AMs
    (possibly Bridge AM and a new one), FMs (for ring mapping, etc), and
    PMs.

    Re: .6 :
    
>    The MCC V1.0 (i.e. Bridge AM + FMs + FCL PM) replace the RBMS point
>    product. DECelms is a superset of RBMS.

    The way I understand it, The "super" part of DECelms is that it
    will also manage FDDI bridges/concentrators.
   
    So, a customer who has both Lanbridges and FDDI concentrators could
    theorically manage both from DECelms, OR choose to manage his
    Lanbridges from DECmcc (through Iconic Map) and manage his FDDI
    concentrator with DECelms.
    
    My question is : I have noticed in the past that you cannot use
    the Bridge AM if RBMS is running (RBMS uses a detached process to
    queue requests to the Ethernet driver). Has this restriction been
    lifted with the DECelms product ?
    
    Cordialement,
    
    Philippe.

    RE: 239.7
    
>   The way I understand it, The "super" part of DECelms is that it
>   will also manage FDDI bridges/concentrators.
    
    Yes, but it also "maps" the FDDI bridges/concentrators...
    
>   My question is : I have noticed in the past that you cannot use
>   the Bridge AM if RBMS is running (RBMS uses a detached process to
>   queue requests to the Ethernet driver). Has this restriction been
>   lifted with the DECelms product ?
    
    Yes, one of the improvements in DECelms over RBMS (and there are
    *many*: DECelms is a great product) is in the way the Bridge
    Protocol Type is used. Bridge AM and DECelms will now coexist/
    interoperate...