Conference azur::mcc

    
    Hi Peter,
    
    If you want to manage DECbridge 5xx or 6xx, and FDDI DECconcentrator,
    you can effectively use two ways :
    
    
    . via DECMCC ELM AM/FM modules, you can read and write (ie ACT) via 
    proprietary protocol onto those network entities (for the
    DECconcentrator 500, ELM 1.0 can manage firmware V3.0B ; ELM V1.2 can
    manage firmware V3.1). 
    Note also that the presentation (syntax, semantic and data translation) 
    is Digital/DECmcc specific. Furthermore, no asynchonous event can be sent 
    by those entities via that protocol, but you can set polling-rules easily on
    Port (ETHERNET, FDDI), following statistic data on each FDDI layers,
    using the FDDI/BRIDGE auto-topology application.
    
    . via DECMCC SNMP/AM, you can 
    
    	- read ONLY (!!) MIB-II and PRIVATE MIB data (via DEC ELANEXT V2.0
    private mib, and FDDI STD private MIBs) from DECbridges 5xx (firmware
    3.0B) and DECbridges 6xx, asynchronous rfc-std events (snmp trap) 
    COLDSTART/WARMSTART/LINKUP being able to be sent to DECmcc Director
    
    	- read AND write private MIB data (via FDDI STD) from/onto FDDI
    DECconcentrator equipments (firmware V3.0B), asyncronous rfc-std events
    (snmp traps) LINKUP/COLDSTART/AUTHENTICATION FAILURE being able to be
    sent to DECmcc Director
    
    Of course, both kinds of equipments can be monitored via a
    polling-rules using the SNMP private MIBs...
    
    
    For CHIPCOM HUB, it's right that there is an agreement around DECmcc
    MSU (!!). But, it seems that a "dummy" AM calling SNMP AM, is being
    developped and that AM seems to be integrated to a DECmcc platform
    V1.3(?) and to be able to launch applications (by clicking icon)...
    I have no added information about that AM... 
    
    
    Regards,
    Renato
    

    
    Hello Renato,
    
    Many thanks for the help, from what you are saying I need to propose
    the DECmcc ELM AM to manage the DECconcentrators and DECbridges, and
    use the SNMP AM to manage the hub.
    
    I have been trying to find the DECmcc ELM V1.2 SPD on the net, to
    include in the proposal. Anyone know of its location.I can only
    find the V1.0 SPD.
    
    Also, if I don't propose the INGRES Base tools can the customer do ANY
    management reports??
    
    regards peter.

RE: 3270.1
    
>   For CHIPCOM HUB, it's right that there is an agreement around DECmcc
>   MSU (!!).
    
    Users expect to see a front panel picture of the Hub being managed
    (with live LEDs, cards displayed in the right order, empty slots
    shown), along with the ability to select (via mouse) a particular
    card for more information.
    
    Hub vendors have written their own visual applications (e.g. Synoptics,
    DEC's HUBwatch) to do this, and worked with framework vendors to allow
    "launching" of these applications.
    
    I believe that MSU's agreement with Chipcom (and Synoptics, and DEC's
    HUBwatch) fall into this category.
    
    DECmcc can launch the Synoptics application with V1.2.
    HUBwatch is close. Don't know about Chipcom...

    
>   But, it seems that a "dummy" AM calling SNMP AM, is being
>   developped and that AM seems to be integrated to a DECmcc platform
>   V1.3(?) and to be able to launch applications (by clicking icon)...
>   I have no added information about that AM... 
    
    Can someone provide more information on this "dummy" AM ?
    
    						Chris

    
>    I have been trying to find the DECmcc ELM V1.2 SPD on the net, to
>    include in the proposal. Anyone know of its location.I can only
>   find the V1.0 SPD.
 

Speak to Mike Bouchard (DELNI::BOUCHARD) for the DECmcc ELM V1.2 SPD.
He is the ELM product manager.

Regards,

Bob  

    
    re .3
    
    I agree Network managers/operators want to see the display showing the
    flashing led's etc, and interface cards etc. In fact we have just lost
    a DECmcc sale, i think mainly because of this.  We were also
    discounting the s/w by 90% (University) i.e giving it away and they
    still were not interested.
    
    re .4 many thanks for contact name.
    
    regards peter. 

    Chris,
    
    Referring to that Chipcom "Dummy AM", let's say something more.
    
    Because the EMM V2.1 of Chipcom was (and still is) a disaster, I
    started to write what somebody called a "dummy AM".  I know Renato
    refers to what I wrote as a point solution to solve the presentation
    provided by the SNMP AM from the Chipcom MIB.
    
    As this combination was not usable for one of our important customers,
    EIS Belgium decided to write an Access Module which implements a
    management model for the Chipcom Online hub, but in contrast with most
    other access modules, does not issues the real protocol calls.  Instead
    this AM use the generic SNMP access module for the basic SNMP access.
    Therefore functionally it IS a real Access Module, but which
    extensively calls the SNMP-AM through it's client interface.
    
    It does the translation of the MIB into a Digital flavoured management
    model of the entity. It translates all ununderstandable variables into
    meaningful variables, and supports verbs as RESET, SAVE etc.. which
    translates into the Simple SNMP SET verbs.
    The AM module can be demonstrated, but I am finishing the event handling
    at this time.
    
    Today, the AM requires an EMM V2.1 (which is an old one)
    (SNMP ... CHIPCOM ... CHIPMIB01 ...CHIGEN).
    Very recently Chipcom announced the EMM V3.0, which is accessed by a new
    flavoured MIB.  (SNMP ... CHIPCOM ... CHIPMIB02 ...CHIGEN)
    
    Today I have not done anything for EMM V3.0, but the technique used
    (tables) will adapt quite easily to this new version.
    
    I modelled the CTL, EMM, ENET, AUI and Bridge modules.  No Token-Ring
    or Terminal Server are handled.
    
    If anybody would like to use this AM or demo this, please let me know.
    Send me a mail and I'll keep you informed about the progress.
    
    	Regards,
    	Dominique
    

    
    
    Hi everybody,
    
    Expecting the great CHIPCOM oriented Access Module that everyone is
    waiting for (especially our customers...), I invite you to upgrade EMM
    V2.1 CHIPCOM module to EMM V1.3 CHIPCOM Module (BASIC version)
    available since several weeks. With this new firmware, you can acceed
    to a new SNMP agent with a new private MIB
    (CHIPCOM_HUB3_BRG_10BT_MIBDEF.TXT ASN.1 file)... And there's no
    comparison about the new way of representation only with SNMP/TCPIP AM
    using that new MIB. (no logical 1..272 interfaces, no CHIPCOM MODULE
    CLASS notion 1/2/3/4/5 & 6, no static occurrences of instances like
    1..17 or 1..272, etc)....You can obtain easily and very user-friendly
    your CHIPCOM configuration (ie Agents, MODULES in SLOTS, Ports in
    absolute indexation, SNMP subtrees for each king of modules like
    51xxM-yy for ETHERNET modules, 52zzM-tt for TOKEN RING modules,
    50xxM-uuu for CONTROL modules, etc...).
    
    I've already implemented that upgrade on site and, according to my
    customers who have seen the previous MIB (!!!), that new MIB is more
    reasonable to use via DECmcc TCPIP/AM firstly.. Of course, they are
    waiting for a CHIPCOM specific representation, but nowadays they're not
    so agressive against SNMP and more generally against DECmcc/EMA !!!
    
    Renato
    
    PS : note that that new MIB contains also a subset ASN.1 tree to manage
    Online Ethernet Bridge Module (OEBM) firmware V2.0 and V2.1, and also a
    specific CHIPCOM 10BT HUB.
    
    PPS : with the MIB Translator Utility (MTU) V1.2 of DECmcc/BMS V1.2,
    you can manage both EMM V2.1 Agent (CHIPCOM_HUB21_MIBDEF.TXT ASN.1
    file) and EMM V3.0 (CHIPCOM_HUB3_BRG_10BT_MIBDEF.TXT ASN.1 file) from
    the same DECmcc platform (ie the MIB tree is split in two subtrees
    CHIPCOM CHIPMIB01 and CHIPCOM CHIPMIB02).
    
    
                     

    
    Hi,
    
    And sorry for an hitting mistake !!!
    
    Of course, the advice migration of EMM is from V2.1 to V3.0 BASIC !!!
    
    Sorry again...
    Renato