Conference azur::mcc

1442.0. "Implement SNMP at application level ?" by IJSAPL::DUIN (Stef Duin - ACT Utrecht - DTN 838-3124) Wed Sep 04 1991 09:23

   Currently we are writing a functional specification for a DECmcc Access
   Module to a Radio Communications Control System (RCCS). RCCS was written
   by the customer.

   The proposed management protocol is based on the existing protocol within
   RCCS between the RCCS management software and the RCCS user interface. 
   As such, a dedicated AM needs to be developed (custom protocol).

   The customer requested me to investigate the usage of the DECmcc
   TCP/IP-SNMP Access Module V1.1, being a MIB-II implementation, capable of
   expansion with Private MIB extensions; the idea being to define Private
   MIB extensions for RCCS, and write an SNMP protocol driver (agent) for
   RCCS instead of an RCCS-AM for DECmcc.

   The environment is VMS V5.4-2 with DECmcc BMS V1.1 and DECmcc TCP/IP-SNMP
   AM V1.0 (to be replaced by V1.1 when available this fall) and VAX-UCX.

   I am aware of the following, but please correct me if wrong:

   	VMS is implementing the Common Agent as VMS Extended Agent, but 
   	the product cannot be expected to be available before well into 
   	calendar 1992.  I heard that it's SNMP protocol driver will be a
   	MIB-II implementation, capable of expansion with private MIB
   	extensions.

   	VMS-UCX is to become VMS-TCP/IP with an SNMP agent

   	Public domain SNMP software is available

   	(Ultrix) Common Agent code, an thus the SNMP protocol driver can
   	be obtained for usage in a Digital project.

   I also understand that only 1 (one) SNMP agent can exist on any TCP/IP
   node (by the way, does this cause conflict between VMS Extended Agent
   SNMP protocol driver and VMS TCP/IP-SNMP comms product, not to speak of
   the DECmcc TCP/IP-SNMP Access Module ?).

   The management of RCCS by DECmcc is defined in two phases; 1st phase is
   the recognition of RCCS events only, where phase-2 will implement
   complete management.  Phase-1 will need to be completed by 1-Nov-1991. 
   For now, Phase-2 is thought to be implemented using the VMS extended
   agent and SNMP as management protocol (with RCCS-Private Extensions).

   My questions are the following:

   1.	How difficult would it be to implement the SNMP RCCS-MIB private
   	extensions, i.e. how much time would it cost ?
   2.	Would the customer need to implement the MIB-I (or -II) as well ?
   3.	What are the potential conflicts with next version of VMS-UCX,
   	being VMS-TCP/IP including an SNMP agent ?
   4.	Can "application program level" SNMP co-exist with Common Agent
   	SNMP protocol driver and/or VMS-TCP/IP-SNMP agent.  If not, which
   	"trick box" has to be opened to keep it working.  We have to keep in
   	mind that althoug phase-1 is RCCS events only, a provision is made
   	in the func spec to request RCCS to send "status events" at the
   	start-up of the access module, so the SNMP traffic is in both 
   	directions.
   5.	In short, is this (implementing SNMP within RCCS) a viable approach,
   	keeping in mind that other applications, running on the same node,
	are also planned to be managed with DECmcc, using the VMS Extended
   	Agent (Common Agent)

   I would really appreciate any suggestions and must admit that my
   instinctive reacion to the customer is to stick with the initial
   approach, thus using the current RCCS management protocol, and avoid
   unmaintainable code and system/network management problems in the (near)
   future.

   Many thanks,

   	Stef Duin, ACT Utrecht.

  A bit late, but note .0 is entered in the following Notes Conferences:

	SNMP			MKNME::SNMP		Note 50
	Common Agent		DECWET::COMMON_AGENT	Note 72
	DECmcc			NOTED::MCC		Note 1442
	Digital Network Team	ENUF::DNT		Note 2946
	Network Management	ENUF::NETMGT		Note 279
	Network Mgt Europe	BONNET::NETMGT_EUROPE	Note 109

  Let this please not withold you from replying, I guess that similar
  questions will be arising where ever EMA is being implemented for
  Enterprise rather than just Network management....

  Stef.