[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

2389.0. "KINETICS private MIB pb" by PRSSOS::BONNAFE (Guy BONNAFE - CSC France) Fri Feb 21 1992 07:15

	Using BMS V1.1 and SNMP AM V1.1, i'm currently trying to add the
	KINETICS private MIB to the dictionary. At the end of the process,
	my dictionary is updated and new parse tables are generated.

	I'm now able to register the SNMP entity and i can see the new
	Excelan subclass on the screen. By double clicking in the 
	Excelan box, all the new subclasses are there ( scc, alap, ethernet,
	aarp, atif, ddp, rtmp, kip, zip, nbp, echo and buffer ).

	But if i try to request something on one of the new subclasses,
	the Management Window displays the following message :
	" No response from entity ".

	( Note that if i try a request on a MIB-II subclass of the same entity,
	i get the answer ).

	I would expect something like "Attribute Not Gettable" if the private
	MIB wasn't implemented on the Kinetics itself, and something like
	" no privilege ... " if it was an access control problem.

	Any idea ?
	Guy.

T.R Title User Personal
Name Date Lines

2389.1 No way to check for "access control" problems TOOK::MINTZ Erik Mintz, DECmcc Development, dtn 226-5033 Fri Feb 21 1992 10:15 13

T.R	Title	User	Personal Name	Date	Lines
2389.1	No way to check for "access control" problems	TOOK::MINTZ	Erik Mintz, DECmcc Development, dtn 226-5033	`Fri Feb 21 1992 10:15`	13
	> I would expect something like "Attribute Not Gettable" if the private > MIB wasn't implemented on the Kinetics itself, and something like > " no privilege ... " if it was an access control problem. Part of the security scheme in the SNMP protocol is that access control problems (at the agent) cause the agent not to respond at all. That means a director (e.g. DECmcc) can't tell the difference between a failed agent and an agent refusing to answer for access control reasons. I would suggest checking to see whether "public" community access is permitted to the enterprise portion of the MIB for the Kinetics.

>	I would expect something like "Attribute Not Gettable" if the private
>	MIB wasn't implemented on the Kinetics itself, and something like
>	" no privilege ... " if it was an access control problem.

Part of the security scheme in the SNMP protocol is that access control
problems (at the agent) cause the agent not to respond at all.
That means a director (e.g. DECmcc) can't tell the difference
between a failed agent and an agent refusing to answer for access control
reasons.

I would suggest checking to see whether "public" community access
is permitted to the enterprise portion of the MIB for the Kinetics.