Conference azur::mcc

860.0. "POPENIM/ENIM_GRAPH functionality in MCC?" by CRONIC::LEMONS (And we thank you for your support.) Tue Apr 02 1991 13:22

As our LAN has ~ 1000 stations, the RBMS V1.1/ETHERnim/POPENIM/ENIM_GRAPH
combination was extremely valuable.  ENIM_GRAPH and ETHERnim have continued to
be enhanced, and RBMS has been superseded by DECelms.  Lacking, though, is
POPENIM's ability to update ETHERnim with the bridged topology.

What had/will DECmcc provide in terms of this functionality?

Thanks!
tl

          <<< WLYWLD::SYS$SYSDEVICE:[NOTES$LIBRARY]ETHERNIM.NOTE;1 >>>
                        -< VAX ETHERnim/LAN Management >-
================================================================================
Note 386.7                    POPENIM V1.0 problem.                       7 of 8
WLYWLD::BRIENEN "Chris Brienen - DECmcc (non-DECnet) AMs"  23 lines   1-AUG-1990 17:20
                              -< Some answers... >-
--------------------------------------------------------------------------------
    Some answers:
    
    DECelms, as it currently exists (standalone point product that is a
    superset of RBMS), will not incorporate the functionality of POPENIM.
    
    Anyone is free to hack up POPENIM to work with DECelms, though I know
    of no one currently doing this.
    
    Some additional information:
    
    Note that providing RBMS/ETHERNIM/POPENIM functionality in DECmcc (the
    EMA compliant DECmcc, not the Netstation offering) *is* being looked at
    (and worked on) now for inclusion in an upcoming version.
    
    For DECmcc this support means at least:
    
        1. Bridge support (already in MCC V1.0)
    	2. Alarms support (already in MCC V1.0)
    	3. Iconic Map support
        4. (Auto) Topology support
        5. FDDI (DECbridge and DECconcentrator) support
    	6. Events (at least sinking SYSIDs)