[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

5320.0. "SNMP access module woes" by OPG::SIMON () Fri Jul 09 1993 08:59

Hi,
   I am posting this on behalf of a guy on site who is having some problems.


He is running V1.3 under ULTRIX V4.3

When he does:


MCC> show snmp fred all attributes

He gets the data back, but between the vaues of registered name ans sysuptime
there is an error message:

 Internet Communications device error.

there are several notes in the conference about this, but ALL refer to VMS and 
he is using ULTRIX.

ALSO IF HE DOES 


MCC> show snmp * all attributes the first couple of nodes return data (with the
error message) and then it hangs. After this the only way to get anything out
of the tcpip am is to kiil the process.

Any ideas or pointers.

Cheers Simon....

P.S. this is real flakey!!!!!!!!

T.R	Title	User	Personal Name	Date	Lines
5320.1		MOLAR::YAHEY::BOSE		`Fri Jul 09 1993 10:23`	16
	Can you do the following commands separately and tell me which ones work correctly and which ones don't : MCC> show snmp fred all char MCC> show snmp fred all count MCC> show snmp fred all status MCC> show snmp fred all refer MCC> show snmp fred all ident The second problem is probably due to slow DNS access. (When you use a global entity wildcard, the entity instances are retrieved from DNS via the registration fm). My guess is that the problem has nothing to do with the SNMP AM. Rahul.
5320.2	More info.........	OPG::SIMON		`Fri Jul 09 1993 10:35`	27
	Rahul, here is the info you wanted: MCC> show snmp fred all char -- WORKS MCC> show snmp fred all count -- WORKS MCC> show snmp fred all status -- FAILS MCC> show snmp fred all refer -- WORKS MCC> show snmp fred all ident -- WORKS > The second problem is probably due to slow DNS access. (When you > use a global entity wildcard, the entity instances are retrieved from > DNS via the registration fm). My guess is that the problem has nothing > to do with the SNMP AM. We are NOT using DNS it's Local MIR. Cheers Simon......
5320.3	ICMP problem?	TOOK::MCPHERSON	Dead or Canadian?	`Fri Jul 09 1993 10:54`	8
	> > MCC> show snmp fred all status -- FAILS > Can you ping fred? I think that's essentially what the SNMP AM is doing to determine IP Reachability (in the status partition). /doug
5320.4		OPG::SIMON		`Fri Jul 09 1993 11:12`	5
	Doug, ping is OK Chhers SImon.....
5320.5		MOLAR::YAHEY::BOSE		`Fri Jul 09 1993 15:55`	11
	Can you check the mode on the mcc_tcpip_am executable? # ls -l /usr/mcc/mmexe/mcc_tcpip_am The mode should be something like -rwsr-xr-x. The s permission should be set on the file which will allow the executable to run under root id. Rahul.
5320.6	That was it!!	SAC::HERBERT	Paul Herbert UK Govt A/cs	`Mon Jul 12 1993 06:22`	14
	Hello, I'm the "guy" in .0. The fix suggested in .5 worked. We did the chmod, killed the process and did the "show snmp fred all status". ipReachability was returned with no error message. Thanks. My only thoughts now are why did the mcc_tcpip_am not have the s permission. Should all the files in mmexe have the same permissions? Paul.
5320.7	Don't SUID other MMs	TOOK::MINTZ	Erik Mintz	`Mon Jul 12 1993 07:43`	6
	> permission. Should all the files in mmexe have the same permissions? No. Only specific MMs should be SUID to root. Changing others would be dangerous.
5320.8		MOLAR::YAHEY::BOSE		`Mon Jul 12 1993 16:20`	6
	During installation the mcc_tcpip_am executable should automatically have the s permission set. Only thing I can think of is someone must changed it after installation. Rahul.