[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

5054.0. "problem with CISCO MIB after upgrade " by GIDDAY::CHONG (Andrew Chong - Sydney CSC ) Thu May 13 1993 08:30

Hi,

	A customer has problem with SNMP entities for CISCO routers after
he upgrade from V1.2 to V1.3 of DECMCC. He has reinstalled the CISCO mib
and the instance repository has been updated as per the release notes. 

	The problem is the following :

MCC> show snmp rcvp01 cisco local lsystem all char 
SNMP rcvp01 cisco local lsystem
AT 13-MAY-1993 15:47:26 Characteristics

The requested operation cannot be completed
                      VMS Routine Error = %NONAME-W-NOMSG, Message number
                                          00000000,
                      MCC Routine Error = %MCC-E-ILVSYNTAXERROR,  data type of
                                          ASN.1 value conflicts with type
                                          supplied

	This command does not fail on every cisco router only some. With some
of them, deregister and reregister the entity fixed the problem , yet some 
entity gave the same error after reregistration. 

	Any help appreciated.

Andrew

T.R	Title	User	Personal Name	Date	Lines
5054.1		MOLAR::YAHEY::BOSE		`Thu May 13 1993 10:56`	9
	Some of your Cisco routers are sending back PDUs which cannot be ASN.1 decoded by the SNMP AM. Possibly a bug in the agent. Turn on the packet trace to get an idea of what the AM is getting from the agent. $ define MCC_TCPIP_AM_LOG 60 /rb
5054.2	the trace....	GIDDAY::CHONG	Andrew Chong - Sydney CSC	`Fri May 14 1993 01:08`	378
	> > Some of your Cisco routers are sending back PDUs which cannot be > ASN.1 decoded by the SNMP AM. Possibly a bug in the agent. Turn on > the packet trace to get an idea of what the AM is getting from the > agent. > > $ define MCC_TCPIP_AM_LOG 60 > I did as suggested and the trace just when on and on. In fact what it is doing is geting all the attributes for lsystem and then repeating the process over and over again. Is this what it is suppose to do ? In fact I only asked for romid attribute , but it gave everything for lsytstem anyway. what are the other bits that can be turned on (or supressed) for MCC_TCPIP_AM_LOG ? Anyway, I got the log . I cant see anything wrong with it , comparing it with data returned from a cisco router that works. I did the same command on 2 cicco routers , one that worked (RAKX01), and one that failed (RCVP01). MCC> show snmp rakx01 cisco local lsystem romid SNMP rakx01 cisco local lsystem AT 14-MAY-1993 10:14:19 Characteristics romId = " System Bootstrap, Version 4.4(4), SOFTWARE Copyright (c) 1986-1992 by cisco Systems " MCC> show snmp rcvp01 cisco local lsystem romid SNMP rcvp01 cisco local lsystem AT 14-MAY-1993 10:15:05 Characteristics The requested operation cannot be completed VMS Routine Error = %NONAME-W-NOMSG, Message number 00000000, MCC Routine Error = %MCC-E-ILVSYNTAXERROR, data type of ASN.1 value conflicts with type supplied The trace for RCVP01 is included below. Due to the length of the trace, I have only included the begining of it which returned romid information {1 3 6 1 4 1 9 2 1 1}. If you need the complete trace ,its available at RIPPER::CISCO_LSYSTEM_TRACE.DAT Andrew ---------------------------------------------------- man/enter DECmcc (V1.3.0) MCC> show snmp rcvp01 cisco local lsystem all char << Sent SNMP message: >> [ 16 ] ( [ 2 ] 00000000 [ 4 ] 70 75 62 6c 69 63 -- public [ 0 ] ( [ 2 ] 00000001 [ 2 ] 00000000 [ 2 ] 00000000 [ 16 ] ( [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 02 00 00 00 01 00 00 00 01 00 00 00 03 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 02 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 02 00 00 00 01 00 00 00 01 00 00 00 02 00 00 00 00 00 00 00 [ 5 ] ) ) ) ) << Received SNMP message: >> [ 16 ] ( [ 2 ] 00000000 [ 4 ] 70 75 62 6c 69 63 -- public [ 2 ] ( [ 2 ] 00000001 [ 2 ] 00000000 [ 2 ] 00000000 [ 16 ] ( [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 02 00 00 00 01 00 00 00 01 00 00 00 03 00 00 00 00 00 00 00 [ APPLICATION 3 ] 05 2a a9 e2 ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 02 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 [ 4 ] 47 53 20 53 6f 66 74 77 61 72 65 20 28 47 53 33 2d 42 46 29 2c 20 56 65 72 73 69 6f 6e 20 38 2e 33 28 35 2e 38 29 2c 20 42 45 54 41 20 54 45 53 54 20 53 4f 46 54 57 41 52 45 0a 43 6f 70 79 72 69 67 68 74 20 28 63 29 20 31 39 38 36 2d 31 39 39 32 20 62 79 20 63 69 73 63 6f 20 53 79 73 74 65 6d 73 2c 20 49 6e 63 2e 0a 43 6f 6d 70 69 6c 65 64 20 54 75 65 20 30 36 2d 4f 63 74 2d 39 32 20 32 30 3a 34 31 20 62 79 20 6d 6c 77 ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 02 00 00 00 01 00 00 00 01 00 00 00 02 00 00 00 00 00 00 00 [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 01 00 00 00 01 00 00 00 ) ) ) ) << Sent SNMP message: >> [ 16 ] ( [ 2 ] 00000000 [ 4 ] 70 75 62 6c 69 63 -- public [ 0 ] ( [ 2 ] 00000002 [ 2 ] 00000000 [ 2 ] 00000000 [ 16 ] ( [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 02 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 03 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 04 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 05 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 06 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 07 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 08 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 09 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0a 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0b 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0c 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0d 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0e 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0f 00 00 00 00 00 00 00 [ 5 ] ) ) ) ) << Received SNMP message: >> [ 16 ] ( [ 2 ] 00000000 [ 4 ] 70 75 62 6c 69 63 -- public [ 2 ] ( [ 2 ] 00000002 [ 2 ] 00000002 [ 2 ] 00000007 [ 16 ] ( [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 [ 4 ] 0d 0a 53 79 73 74 65 6d 20 42 6f 6f 74 73 74 72 61 70 2c 20 56 65 72 73 69 6f 6e 20 34 2e 34 28 34 29 2c 20 53 4f 46 54 57 41 52 45 0d 0a 43 6f 70 79 72 69 67 68 74 20 28 63 29 20 31 39 38 36 2d 31 39 39 32 20 62 79 20 63 69 73 63 6f 20 53 79 73 74 65 6d 73 0d 0a ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 02 00 00 00 00 00 00 00 [ 4 ] 70 6f 77 65 72 2d 6f 6e -- power-on ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 03 00 00 00 00 00 00 00 [ 4 ] 52 43 56 50 30 31 -- RCVP01 ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 04 00 00 00 00 00 00 00 [ 4 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 05 00 00 00 00 00 00 00 [ APPLICATION 0 ] 00 00 00 00 ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 06 00 00 00 00 00 00 00 [ APPLICATION 0 ] 00 00 00 00 ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 07 00 00 00 00 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 08 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 09 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0a 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0b 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0c 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0d 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0e 00 00 00 00 00 00 00 [ 5 ] ) [ 16 ] ( [ 6 ] 01 00 00 00 03 00 00 00 06 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 09 00 00 00 02 00 00 00 01 00 00 00 0f 00 00 00 00 00 00 00 [ 5 ] ) ) ) )
5054.3	QAR #251	GIDDAY::CHONG	Andrew Chong - Sydney CSC	`Tue May 18 1993 22:10`	6
	Problem has been QARed (#251) Will also try modified version of Mib query utility to see if valid values are returned . Andrew
5054.4	traces available...	GIDDAY::CHONG	Andrew Chong - Sydney CSC	`Fri May 21 1993 00:31`	24
	more information..(for QAR #251) I have tried the Mib query utility and it returns correct information for cisco local lsystem attributes for those cisco boxes that failed via SNMP_AM. I have also done lan traces of a failed and a successful execution of the command "show snmp cisco_box cisco local lsystem hostname" . The trace is abit tedious to decode .I must admit having a first go at decoding snmp trace data, I can't see where the problem is which cause a %MCC-E-ILVSYNTAXERROR. The trace files are available on RIPPER:: RCVP01.LIS - trace of failed command RAKX01.LIS - trace of successful command Can someone please take a look at this. We have a customer with lots of cisco routers, all running same version of software, it's difficult to say that there is a problem with the agent when we can't pin point where the problem is . Regards, Andrew
5054.5		MOLAR::YAHEY::BOSE		`Fri May 21 1993 13:31`	2
	I'll take a look. - rahul.
5054.6	same problem..	MLNCSC::LASAGNA	NO!, le scarpe no !!	`Mon May 24 1993 06:23`	13
	Hi, I got the same problem as .0, in plus we have some cisco's in iconic map without cisco child entity after double-clicking in the box but i can see it in FCL. I upgraded from 1.2.3 and was all ok, the cisco child entity was at the right place for all the boxes. Rahul, do you need a trace from me too ?? Ciao, Andrea Lasagna.
5054.7		MOLAR::YAHEY::BOSE		`Mon May 24 1993 12:54`	23
	>> I got the same problem as .0, in plus we have some cisco's in iconic >> map without cisco child entity after double-clicking in the box but i >> can see it in FCL. Due to the way the Cisco agent works, the SNMP AM cannot discover the cisco private mib extension on the agent. You will have to manually add the cisco child entity to your map. Here are the steps involved : 1) Double-click into the SNMP global entity. 2) Bring up the tool-box window. 3) Select the cisco child entity and add it to the map. You will probably get a number of messages saying that the entity is partially registered, but ignore those messages. You should be now able to do SHOWs and SETs to the Cisco mib variables via the iconic map. >> Rahul, do you need a trace from me too ?? Since you are having the same problem, another trace is not necessary. Rahul.
5054.8	this really helps	MLNCSC::LASAGNA	NO!, le scarpe no !!	`Tue May 25 1993 03:40`	4
	Thanks a lot and keep us informed. Ciao, Andrea.
5054.9	any findings please !	GIDDAY::CHONG	Andrew Chong - Sydney CSC	`Tue Jun 01 1993 20:56`	11
	Hi there , There has not been any response to QAR #251 or to the traces posted in this note. To me the trace looks good, it means the cISCO doing the right thing. I am not experienced in looking at SNMP traces and need a second opinion. It the trace is good then the problem is with SNMP AM . I will do the right thing and CLD it if thats what needs to be done. Andrew
5054.10		MOLAR::YAHEY::BOSE		`Wed Jun 02 1993 11:32`	10
	The problem may very well be with the SNMP AM. I am trying to locate a Cisco agent so that I may reproduce the problem. So if anyone can volunteer access to a cisco agent on the DEC network (netid 16.), I'd be grateful to that person. There is already a CLD outstanding regarding this problem. Rahul.
5054.11		MOLAR::YAHEY::BOSE		`Wed Jul 07 1993 12:09`	7
	This turned out to be a problem with one of the PDU buffers overflowing due to large string values in the romID variable. The fix will be available in the next release. If anyone desperately needs an interim executable, please send me mail. Rahul.