Conference azur::mcc

3847.0. "DECmcc/TeMIP internal operation" by ISIDRO::MAMORENO (Ancient Ferrita) Thu Oct 01 1992 14:06

    I am working at TIMG Spain supporting pre-sales activities for TELEFONICA.
We are dealing with R&D group of Spanish PTT trying to show DECmcc+TeMIP exce-
lences for Net.Mgnt. in TMN. R&D group is evaluating OpenView, UI/Atlas and
DECmcc/TeMIP as a platform for apllications development. We started so bad due
DEC image at this group, but now we have high credibility after demonstration
that DME is not Openview and HP was sending some false messages.

    I made several presentations at different levels, but mainly technical. 
Demos were very ligth and simple. Yesterday they had an internal presentation
comparing OpenView and DECmcc/TeMIP. The result is that people wants to know 
more about DECmcc/TeMIP internal operation and my acknoledge is limited.

    I should answer asap the following:

      1) Show a detailed operation of DECmcc/TeMIP (as Management System) with a
         Network Element that supports Q3 interfase and other NE that has
         a propietary protocol.
         
         * Detailed operation means how it works, so, what happen when an alarm
         is faired at NE, who takes the alarm in TeMIP (Event Mgr --> Notif FM
         --> AH ????), who filters and converts to ISO alarm, where and when is
         logged, how is updated IMPM,AHPM, etc.... 

         * Why are Events/Alarms (at leats in DECnet and TCP/IP) captured
         thru external EventMgr process?? It could be done in the AM. Is it
         the same approach with OSI-AM/Q3?? It seams to be that AM is only for
         dialogs, so how can we explain this implementation?? Can we say that
         EventMgrs are like AMs but with some special .... thing ??
        

      2) What happen when two Operators working in their Domains or OCs receives
         the same alarm. An ACK from one of them does inform the other??? Is
         there a difference if guys are accessing the same or different Domains?
         Can both generate a TT for the same problem, or can see if a TT 
         is allready for that??  How, who takes care of it ?


      3) MCC API is handling info passing among MMs, so Descriptors contains
         Object informations. Does mcc-call pass any kind of information or 
         only Object's?? When Notif FM informs IMPM about an alarm (or event)
         this alarm is not an Object, so is it a message that is passed 
         via mcc-call?

       
      4) XMP API is been implemented in the OSI-AM, so object/data conversions 
         should be done inside the AM. Is it true?  Is XMP API (DECcmi product?)
         calling CMIP directly or thru DECros API??          


      5) Do we know how will OMG API be integrated into DECmcc?? Same level 
         than MCC API?? Any idea?


    All these questions are in relationship. The most important thing is to
    explain how DECmcc/TeMIP  works and what is happening step by step on
    typical operations.
    
    Can you help me? Is there some paper explainig it?

    DECmcc intro and TeMIP intro manuals are not enough to answer TELEFONICA.
They want a deep explanation with details like: how a MM captures an alarm (or
event), which MM coverts an alarm to ISO format, where it stores data, how it 
informs other MMs and anything else relevant in the operation.
    I am reading TeMIP Ref. and DECmcc SRM manuals but I am not an expert.
    
    Thanks in advance and regards.
Miguel Angel