[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

3747.0. "SNMP and CMIP mgmt for the one product" by OZROCK::MUGGERIDGE (X.25 is 1-2-3) Wed Sep 16 1992 01:43

Hi,

I'm working with a 3rd party supplier to integrate their Flexible Communications
Platform, (FCP), into our ALPHA systems to provide sync comms support.

The FCP connects to the host via SCSI and provides such things
as processor failover and indications of cooling fan failures, hot swap etc.
From a communications standpoint it is capable of supporting Channelised T1/E1,
RS449, RS232, V.35.

The FCP will be managed via SNMP, but the protocols and device driver will be
managed via NCL.  With this in mind, we plan on selling MCC as an integral
part of the completed product.


Now my questions:  (BTW:  I know very little about SNMP)

1.  Will events generated for SNMP and EMA be logged in the same fashion from
a network managers point of view?

2.  After looking at the SNMP_AM book, it appears as though there is limited
number of events which are registered by MCC.  How do we add the vendor
specific events?  Is this documented?

3.  Is MCC capable of hiding the fact that the FCP is managed via SNMP and
the protocols managed via CMIP?  Will a N/W mgr need to be experienced with
both mgmt diretors?


Thanks for any assitance,
Matt.

T.R	Title	User	Personal Name	Date	Lines
3747.1	Well, yes, but ...	FRSOLD::ORCHIS::SYSTEM	Information, that's all I need...	`Mon Sep 21 1992 14:20`	30
	Hi Matt, from my limited understanding :-), here are the answers: 1. You mean SNMP and CMIP, don't you? If you do :-), well, yes. As long as you use DECmcc. 2. You add them by defining EnterpriseSpecific traps (events) in your MIB (Management Information Base). This should be documented in various RFCs and maybe the DECmcc Developers Guide (I'm not sure of this one). Ask one of the SNMP gurus out there 3. Well, errrhhmmm, no. As far as I know. You could maybe put both icons (CMIP and SNMP) into a domain and hide them this way, but this is surely not what you want. But let me ask you a question: Why the heck do you use both CMIP AND SNMP? This is somewhat like building a plane with two pairs of wings, ailerons and (side rudders). You can use it, but it's damned hard to fly. And clumsy, too. If I were you (or the customer), I would concentrate on one protocol and try to get it to work at first hand. Porting to the other protocol will be much easier then. Anyway, I hope this helps. See Ya Josch
3747.2	Just how difficult will it be to integrate SNMP and CMIP	OZROCK::MUGGERIDGE	X.25 is 1-2-3	`Thu Sep 24 1992 00:52`	27
	Josch, Thanks for your comments. Yes I do mean SNMP and CMIP. The reason for using both protocols is a business decision based on the way things are done now. The WAN Device Drivers is managed via CMIP and has been since the birth of time. We have no intentions or market reasons for implimenting an SNMP MOM. The FCP MOM could be implemented with CMIP but the vendor has already devoted much time in designing an SNMP MOM. For time to market reasons it was not viable to implement a CMIP MOM. Furhtermore, they don't wish to become dependent on DECnet because they will be selling their box stand-alone as a router. (I think the only dependency would be NETMAN). RFC: I have never seen this kind of mixed management of the one product, but from your reply I get the feeling it will be a dog to work with. I am very interested in hearing other views on this. We have been lead to believe by DEC Sales people that it will be virtually seamless thanks to MCC. How optimistic is this? Thanks, Matt.