[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

1232.0. "EMS/INMS, overhead in MCC?" by NEOV00::MRIVERA (Mario Rivera, EIS Monterrey Mexico) Wed Jul 10 1991 16:42

Hi:

I'm proposing DECmcc BMS to customer. However I have some questions 
(quoted here from customer's questionnaire). Can anybody give me some 
light on this. 

The first two ones are associated and I believe EMA-products are INMS. 
Right? Even being INMS can someone explain interface methods. 

> The vendor should specify the minimum and maximum number of Element
> Managers Systems (EMS) supported and mention the name of those EMS. An
> element manager is a system designed specifically for the management of
> a certain kind of device (for example, a router, modem, multiplexer,
> CSU/CDU, etc.) An element manager, unlike Integrated Network Management
> Systems (INMS), can manage only devices of a specific vendor. Integrated
> Network Management Systems work with a broad spectrum of gear from a
> number of vendors. 

> The vendor should specify the EMS Interface Methods used. The EMS
> interface refers to the physical connection of the element manager to
> the device, for example, alert parsing, generic alerts, protocol
> conversion; and the capabilities of current element manager system
> interfaces such as capturing/forwarding alerts, monitoring and
> controlling via interface/terminal emulation. 

I've already posted a question on overhead but I got no answer. Any 
rough estimates or directions to an acceptable enswer? Also can comeone
further explain to me the Mainstream ans Sidestream approaches. What are
their implications and practical issues. 

> The vendor should specify the overhead introduced by the product to the
> network (traffic) and to the system where it runs. Mention if the
> product operates under a Mainstream os Sidestream approach. Mainstream
> management is a host based approach. With the sidestream concept, some
> or all components used in accomplishing the network management tasks
> reside in a special purpose management processor. 

Thanks,
Mario

T.R Title User Personal
Name Date Lines

1232.1 CMIP or SNMP ENUF::GASSMAN Wed Jul 10 1991 18:54 10

T.R	Title	User	Personal Name	Date	Lines
1232.1	CMIP or SNMP	ENUF::GASSMAN		`Wed Jul 10 1991 18:54`	10
	This sounds like a bid wired for AT&T. EMA products are integrated in the sense that they provide a similar command syntax for all supported protocols, hold data in a common database, and allow functions (sometimes) to be used across all supported protocols. You are talking here about a 'manager of manager' type system. They way EMA products will approach this is thru Network Management Forum protocols (OSI CMIP basically) or thru SNMP proxy techniques. bill

    This sounds like a bid wired for AT&T.  EMA products are integrated in
    the sense that they provide a similar command syntax for all supported
    protocols, hold data in a common database, and allow functions
    (sometimes) to be used across all supported protocols.
    
    You are talking here about a 'manager of manager' type system.  They
    way EMA products will approach this is thru Network Management Forum
    protocols (OSI CMIP basically) or thru SNMP proxy techniques.  
    
    bill