[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

4048.0. "ASN.1-encoding corrupt with CISCO MIB" by ZTOIS1::VISTA (Renato VISTA, SIS Strasbourg, France) Fri Nov 06 1992 09:37

	Hi,

	I want to manage via DECmcc/SNMP V1.2 Access Module CISCO Terminal
	Server with TS-Software Version 8.3(1), System Bootstrap version
	4.4(1).

	I use the private mib CISCO_MIBDEF.TXT included in the DECmcc/BMS V1.2
        kit (note that it runs on ULTRIX 4.2A platform).

	When I do the following command :

	MCC>show snmp <cisco-ts> cisco local lts ltsLineSessionTable * -
			all attributes

	I obtain...

			VMS Routine Error = Error = 0
			MCC Routine Error = %MCC-E-ASNCORRUPT, 
						ASN.1-encoding corrupted


	Those messages occur when the sessions for given ports are LAT 
        sessions.


	By investigating with a PC-based NAT NMS/SNMP platform, using the same
	CISCO private MIB (8.3), the LAT session for a given port 
	returned values are the following :

		tslineSessType		= 7		(ie LAT)
		tslineSesDir		= 3		(ie outgoing)

		tslineSessAddr		= no value returned !!!

		tslineSesName		= <current service name>
		tslineSesCur		= 0		(ie not current
							session)
		tslineSesIdle		= <Time in seconds of idle>


	NAT/NMS has no ASN.1 error message, but DECmcc has got ones...

	Does anybody have any opinion about this kind of problem ?

	Regards,
	Renato

	PS : the tslineSesAddr is described as MANDATORY. Because NAT/NMS gets
	     no value for a LAT session, I've edited the CISCO_MIBDEF.TXT ASN.1
	     file, changing attribute STATUS from MANDATORY to OPTIONAL, and
	     reloaded the DECmcc dictionary/parse_tables. The problem is still
	     existing...

	PPS :

	Here is the ASN.1 section of CISCO private mib (8.3) :




               -- Local Terminal Server Line Session Table

          -- This group contains terminal server specific
          -- information on a per line and per session basis.

               ltsLineSessionTable OBJECT-TYPE
                   SYNTAX  SEQUENCE OF LTsLineSessionEntry
                   ACCESS  not-accessible
                   STATUS  mandatory
                   DESCRIPTION
                            "A list of terminal server line and session
                            entries."
                   ::= { lts 3 }

               ltsLineSessionEntry OBJECT-TYPE
                   SYNTAX LTsLineSessionEntry
                   ACCESS  not-accessible
                   STATUS  mandatory
                   DESCRIPTION
                            "A collection of per session and per TTY
                            objects in the cisco Terminal Server
                            implementation."
                   INDEX { INTEGER, INTEGER }
               ::= { ltsLineSessionTable 1 }

              LTsLineSessionEntry ::=
                   SEQUENCE {
                       tslineSesType
                           INTEGER,
                       tslineSesDir
                           INTEGER,
                       tslineSesAddr
                           NetworkAddress,
                       tslineSesName
                           DisplayString,
                       tslineSesCur
                           INTEGER,
                       tslineSesIdle
                           INTEGER
                   }


          -- The following section describes the components of the
          -- table.

               tslineSesType OBJECT-TYPE
                   SYNTAX  INTEGER {
                        unknown(1),
                        pad(2),
                        stream(3),
                        rlogin(4),
                        telnet(5),
                        tcp(6),
                        lat(7),
                        mop(8),
                        slip(9),
                        xremote(10)
                   }
                   ACCESS  read-only
                   STATUS  mandatory
                   DESCRIPTION
                           "Type of session."
                   ::= { ltsLineSessionEntry 1 }

               tslineSesDir OBJECT-TYPE
                   SYNTAX  INTEGER {
                        unknown(1),
                        incoming(2),
                        outgoing(3)
                   }
                   ACCESS  read-only
                   STATUS  mandatory
                   DESCRIPTION
                           "Direction of session."
                   ::= { ltsLineSessionEntry 2 }

               tslineSesAddr OBJECT-TYPE
                   SYNTAX  NetworkAddress
                   ACCESS  read-only
                   STATUS  mandatory
                   DESCRIPTION
                           "Remote host address of session. [What about
                           PAD connections?]"
                   ::= { ltsLineSessionEntry 3 }

               tslineSesName OBJECT-TYPE
                   SYNTAX  DisplayString
                   ACCESS  read-only
                   STATUS  mandatory
                   DESCRIPTION
                           "Remote host name of session."
                   ::= { ltsLineSessionEntry 4 }

               tslineSesCur OBJECT-TYPE
                   SYNTAX  INTEGER
                   ACCESS  read-only
                   STATUS  mandatory
                   DESCRIPTION
                           "Boolean whether session is the currently
                           active one."
                   ::= { ltsLineSessionEntry 5 }

               tslineSesIdle OBJECT-TYPE
                   SYNTAX  INTEGER
                   ACCESS  read-only
                   STATUS  mandatory
                   DESCRIPTION
                           "Time in seconds session has been idle."
                   ::= { ltsLineSessionEntry 6 }

T.R	Title	User	Personal Name	Date	Lines
4048.1	Try the mib query utility.	YAHEY::BOSE		`Sat Nov 07 1992 12:20`	10
	Run the mib query utility (/usr/mcc/mcc_system/mcc_tcpip_mq) to ask for the particular mib object from the cisco agent. You will have to provide the correct object id for the ltsLineSessionTable, which is 1.3.6.1.4.1.9.2.9.2.1 Let me know if you can get the information back from the agent correctly. /rb
4048.2	mcc_tcpip_mq returns status 52878858	ZTOIS1::VISTA	Renato VISTA, SIS Strasbourg, France	`Mon Nov 09 1992 05:29`	37
	Hi, I've used the /usr/mcc/mmexe/mcc_tcpip_mq utility to get values of variables : tslineSesType (ASN1 data type tslineSysType_enm) tslineSesDir ( lslineSesDir_enm) lslineSesAddr ( IPaddress) ... #/usr/mcc/mmexe/mcc_tcpip_qm <CISCO_TS> 1 0 OID> ...values per variables for (port,session)... Port 1, Session 1 (ie 1,1) is currently a LAT session. So I've got for the three following variables : tslineSesType : 7 (ie LAT session) tslineSesDir : 3 (ie outgoing) tslineSesAddr : ??? /usr/mcc/mmexe/mcc_tcpip_mq exited with error message : parse_init returned status = 52878858 # Any idea about the meaning of this status ? Regards, Renato Is there any problem with tslineSesAddr (datatype IPaddress) which has no sense for a LAT session ??
4048.3		YAHEY::BOSE		`Mon Nov 09 1992 18:40`	9
	Code 52878858 corresponds to the MCC condition MCC_S_ASNCORRUPT, which is why the SNMP AM is reporting a corrupt ASN1 encoding. Seems like the agent is sending back an invalid ASN1 encoding. Define the environment variable MCC_TCPIP_AM_LOG to a value of 60. This will cause the SNMP AM to dump the in and out packets. If you can mail me the log of what you get, I'll take a look. Rahul.
4048.4	SNMP AM Traces about CISCO TS	ZTOIS1::VISTA	Renato VISTA, SIS Strasbourg, France	`Tue Nov 10 1992 09:14`	184
	Rahul, Hereunder the traces you've asked. Regards, Renato --------------------------------------------------------------------------- DECmcc (V1.2.0) MCC> show snmp cisco52 cisco local lts ltslineSessionTable ( 3,1 ) all attrib << Called with state = 0 >> << Verb Code = 1 >> << EAS dump: Class Wildcard >> << ----- -------- 18 1 5009 1 2 1 5 1 2 1 << Attribute code = 1 >> << 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 ] 0c 1d 39 79 ) [ 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 ] 54 53 20 53 6f 66 74 77 61 72 65 20 28 53 54 53 58 2d 4c 52 29 2c 20 56 65 72 73 69 6f 6e 20 38 2e 33 28 31 29 2c 20 0a 43 6f 70 79 72 69 67 68 74 20 28 63 29 20 31 39 38 36 2d 31 39 39 31 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 32 32 2d 4f 63 74 2d 39 31 20 30 32 3a 30 38 20 62 79 20 62 6c 6f 63 6b ) [ 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 02 00 00 00 ) ) ) ) << Received SNMP message: >> [ 16 ] ( [ 2 ] 00000000 [ 4 ] 70 75 62 6c 69 63 -- public [ 2 ] ( [ 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 09 00 00 00 03 00 00 00 01 00 00 00 01 00 00 00 03 00 00 00 01 00 00 00 [ 2 ] 00000007 ) ) ) ) << General status: 1 >> << MCC status: 52854793 >> << VMS status: 0 >> << Exception index 0 >> << Current CVR: 52854857 >> SNMP cisco52 cisco local lts ltsLineSessionTable (3,1) AT 1992-11-10-11:07:58.309 All Attributes ltsLineSessionTable_Index = ( 3, 1 ) << Called with state = 0 >> << Verb Code = 1 >> << EAS dump: Class Wildcard >> << ----- -------- 18 1 5009 1 2 1 5 1 2 1 << Attribute code = 4 >> << 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 ] 0c 1d 39 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 ] 54 53 20 53 6f 66 74 77 61 72 65 20 28 53 54 53 58 2d 4c 52 29 2c 20 56 65 72 73 69 6f 6e 20 38 2e 33 28 31 29 2c 20 0a 43 6f 70 79 72 69 67 68 74 20 28 63 29 20 31 39 38 36 2d 31 39 39 31 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 32 32 2d 4f 63 74 2d 39 31 20 30 32 3a 30 38 20 62 79 20 62 6c 6f 63 6b ) [ 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 02 00 00 00 ) ) ) ) << Received SNMP message: >> [ 16 ] ( [ 2 ] 00000000 [ 4 ] 70 75 62 6c 69 63 -- public [ 2 ] ( [ 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 09 00 00 00 03 00 00 00 01 00 00 00 01 00 00 00 03 00 00 00 01 00 00 00 [ 2 ] 00000007 ) [ 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 09 00 00 00 03 00 00 00 01 00 00 00 02 00 00 00 03 00 00 00 01 00 00 00 [ 2 ] 00000003 ) [ 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 09 00 00 00 03 00 00 00 01 00 00 00 03 00 00 00 03 00 00 00 01 00 00 00 [ APPLICATION 0 ] 00 00 00 00 << General status: 0 >> << MCC status: 52878858 >> << VMS status: 0 >> << Exception index 0 >> << Current CVR: 0 >> << Clearing Handle... >> The requested operation cannot be completed VMS Routine Error = Error 0, MCC Routine Error = %MCC-E-ASNCORRUPT, ASN.1 encoding corrupted MCC> exit
4048.5		YAHEY::BOSE		`Tue Nov 10 1992 10:28`	8
	Your log shows that the ASN.1 encoding sent back by the Chipcom agent is corrupt. The ASN.1 dump routine fails when it tries to dump the PDU. You might want to point out to Chipcom that their agent is screwing up when a request is made for the object 1.3.6.1.1.9.2.9.3.1.3.3.1 /rb
4048.6	OK, and thank you! But...	ZTOIS1::VISTA	Renato VISTA, SIS Strasbourg, France	`Tue Nov 10 1992 10:47`	14
	Rahul, Thank you for your investigations. I suppose you speak about CISCO (instead of Chipcom...). I will communicate our results to my customer. But, just a question : how do you explain that other NMS platform (such as NAT/NMS PC-based platform) seems to accept the corrupted value returned by remote NAT/SNMP Agent ? Do you think there is an error handler catching the bad message and hiding it by not signalling the corrupted data ? Regards, Renato
4048.7		YAHEY::BOSE		`Tue Nov 10 1992 11:22`	9
	Renato, Chipcom or Cisco, they are all the same to the SNMP AM :-) Anyway, one of the mcc kernel routines which handle ASN.1 encoding is returning error status. Since you are absolutely sure that other management stations can handle this Cisco agent, we will investigate this problem further. Rahul.
4048.8	Pbs(?) at two levels... (+Getting SNMP traces)	ZTOIS1::VISTA	Renato VISTA, SIS Strasbourg, France	`Tue Nov 10 1992 12:19`	19
	Rahul, In conclusion, the problem contents two points : 1) the CISCO remote agent returns a corrupted/bad data to DECmcc 2) DECmcc Kernel Error Handler seems to be very strict versus NAT/NMS Error Handler I will be onsite next week. If it is possible, I will try to track with a Network Analyzer SNMP frames sent by CISCO remote Agent. I will post the detail tracking in a dozen of days. Regards, Renato PS : You maybe have any opinion about the current reply. Thanks in advance.
4048.9	DataType pb on CISCO TS agent (for LAT sessions)	ZTOIS1::VISTA	Renato VISTA, SIS Strasbourg, France	`Mon Nov 23 1992 11:43`	732
	Rahul, Hereunder traces of protocol data exchanges between CISCO Terminal Server and DECmcc/ULTRIX platform. (Please note that these traces have been caught via IRIS PC-based software available onsite). Effectively, when a LAT session is running for a given port (ie port 3.1), the values returned by CISCO agent are : tsLineSesType = 7 (ie LAT) tsLineSesDir = 3 (ie outgoing) tslineSesAddr = - NOT RETURNED by NAT/NMS - Error with mcc_tcpip_mq - "ASN.1 encoding corrupted" with DECmcc In fact, instead of returning a NetworkAddress Datatype (ie Ipaddress for MTU translator -see CISCO_MIBDEF. files-), the CURRENT LAT SERVICE NAME is returned !!! (see the end of the following traces, in my case LAT Service BILUXB). So, I will escalate this problem to CISCO. Thank for your help. Regards, Renato =========================================================================== Subject: Traces entre TAURUS et CISCO52 IRIS capture data Page 1 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 Summary for frame 0 0 02CF1F904633<- TAURUS 120 DIX 0800 UDP ???: Sr c=1133 Dest=161 Len=86 Chksum=288 IP UDP Dest=156.133.8.26 Src=156.133.8.45 Len=106 DLL DIX PType=08-00 Detail for frame 0 DLL: DLL: - - - - - Datalink Header - - - - - DLL: DLL: Frame 0 arrived at 13203 milliseconds, length = 120 bytes DLL: DLL: Destination Address = 02-CF-1F-90-46-33 (02CF1F904633) DLL: Source Address = AA-00-04-00-53-04 (TAURUS) DLL: DIX format, Protocol Type = 08-00 IP: IP: - - - - - Internet protocol (IP) - - - - - IP: IP: Internet header version = 4 IP: Internet header length = 20 bytes IP: Type of service = 00 IP: .....0.. = Normal Reliability IP: ....0... = Normal Throughput IP: ...0.... = Normal Delay IP: 000..... = Routine IP: IP: Total Packet Length = 106 IP: Identification = 970 IP: Fragment Information = 0000 IP: Fragment Offset = 0 IP: ..0............. = May Fragment IP: .0.............. = More Fragments IP: IP: Time to live (sec) = 30 IP: Protocol Type = 17 (UDP) IP: Header Checksum = 20328 IP: Source Address = 156.133.8.45 IP: Destination Address = 156.133.8.26 UDP: UDP: - - - - - User Datagram Protocol (UDP) - - - - - UDP: UDP: Source port = 1133 (Unknown) UDP: Destination port = 161 (Unknown) UDP: Length = 86 UDP: Checksum = 288 UDP: UDP: Port ??? data Hex for frame 0 0000: 02 CF 1F 90 46 33 AA 00 04 00 53 04 08 00 45 00 ....F3....S...E. 0010: 00 6A 03 CA 00 00 1E 11 4F 68 9C 85 08 2D 9C 85 .j......Oh...-.. 0020: 08 1A 04 6D 00 A1 00 56 01 20 30 82 00 4A 02 01 ...m...V. 0..J.. 0030: 00 04 06 70 75 62 6C 69 63 A0 82 00 3B 02 01 01 ...public...;... 0040: 02 01 00 02 01 00 30 30 30 82 00 0C 06 08 2B 06 ......000.....+. 0050: 01 02 01 01 03 00 05 00 30 82 00 0C 06 08 2B 06 ........0.....+. 0060: 01 02 01 01 01 00 05 00 30 82 00 0C 06 08 2B 06 ........0.....+. 0070: 01 02 01 01 02 00 05 00 ........ IRIS capture data Page 2 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 IRIS capture data Page 3 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 Summary for frame 1 1 +22m TAURUS<-02CF1F904633 250 DIX 0800 UDP ???: S rc=161 Dest=1133 Len=216 Chksum=4790 IP UDP Dest=156.133.8.45 Src=156.133.8.26 Len=236 DLL DIX PType=08-00 Detail for frame 1 DLL: DLL: - - - - - Datalink Header - - - - - DLL: DLL: Frame 1 arrived at 13225 milliseconds, length = 250 bytes DLL: DLL: Destination Address = AA-00-04-00-53-04 (TAURUS) DLL: Source Address = 02-CF-1F-90-46-33 (02CF1F904633) DLL: DIX format, Protocol Type = 08-00 IP: IP: - - - - - Internet protocol (IP) - - - - - IP: IP: Internet header version = 4 IP: Internet header length = 20 bytes IP: Type of service = 00 IP: .....0.. = Normal Reliability IP: ....0... = Normal Throughput IP: ...0.... = Normal Delay IP: 000..... = Routine IP: IP: Total Packet Length = 236 IP: Identification = 1235 IP: Fragment Information = 0000 IP: Fragment Offset = 0 IP: ..0............. = May Fragment IP: .0.............. = More Fragments IP: IP: Time to live (sec) = 255 IP: Protocol Type = 17 (UDP) IP: Header Checksum = 27868 IP: Source Address = 156.133.8.26 IP: Destination Address = 156.133.8.45 UDP: UDP: - - - - - User Datagram Protocol (UDP) - - - - - UDP: UDP: Source port = 161 (Unknown) UDP: Destination port = 1133 (Unknown) UDP: Length = 216 UDP: Checksum = 4790 UDP: UDP: Port ??? data Hex for frame 1 0000: AA 00 04 00 53 04 02 CF 1F 90 46 33 08 00 45 00 ....S.....F3..E. 0010: 00 EC 04 D3 00 00 FF 11 6C DC 9C 85 08 1A 9C 85 ........l....... 0020: 08 2D 00 A1 04 6D 00 D8 12 B6 30 81 CD 02 01 00 .-...m....0..... 0030: 04 06 70 75 62 6C 69 63 A2 81 BF 02 01 01 02 01 ..public........ 0040: 00 02 01 00 30 81 B3 30 10 06 08 2B 06 01 02 01 ....0..0... +.... 0050: 01 03 00 43 04 11 85 FE 01 30 81 88 06 08 2B 06 ...C.....0....+. 0060: 01 02 01 01 01 00 04 7C 54 53 20 53 6F 66 74 77 .......\|TS Softw 0070: 61 72 65 20 28 53 54 53 58 2D 4C 52 29 2C 20 56 are (STSX-LR), V IRIS capture data Page 4 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 0080: 65 72 73 69 6F 6E 20 38 2E 33 28 31 29 2C 20 0A ersion 8.3(1), . 0090: 43 6F 70 79 72 69 67 68 74 20 28 63 29 20 31 39 Copyright (c) 19 00A0: 38 36 2D 31 39 39 31 20 62 79 20 63 69 73 63 6F 86-1991 by cisco 00B0: 20 53 79 73 74 65 6D 73 2C 20 49 6E 63 2E 0A 43 Systems, Inc..C 00C0: 6F 6D 70 69 6C 65 64 20 54 75 65 20 32 32 2D 4F ompiled Tue 22-O 00D0: 63 74 2D 39 31 20 30 32 3A 30 38 20 62 79 20 62 ct-91 02:08 by b 00E0: 6C 6F 63 6B 30 14 06 08 2B 06 01 02 01 01 02 00 lo ck0...+....... 00F0: 06 08 2B 06 01 04 01 09 01 02 ..+....... IRIS capture data Page 5 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 Summary for frame 2 2 +6m 02CF1F904633<- TAURUS 93 DIX 0800 UDP ???: Src=1133 Dest=161 Len=59 Chksum=61349 IP UDP Dest=156.133.8.26 Src=156.133.8.45 Len=79 DLL DIX PType=08-00 Detail for frame 2 DLL: DLL: - - - - - Datalink Header - - - - - DLL: DLL: Frame 2 arrived at 13231 milliseconds, length = 93 bytes DLL: DLL: Destination Address = 02-CF-1F-90-46-33 (02CF1F904633) DLL: Source Address = AA-00-04-00-53-04 (TAURUS) DLL: DIX format, Protocol Type = 08-00 IP: IP: - - - - - Internet protocol (IP) - - - - - IP: IP: Internet header version = 4 IP: Internet header length = 20 bytes IP: Type of service = 00 IP: .....0.. = Normal Reliability IP: ....0... = Normal Throughput IP: ...0.... = Normal Delay IP: 000..... = Routine IP: IP: Total Packet Length = 79 IP: Identification = 972 IP: Fragment Information = 0000 IP: Fragment Offset = 0 IP: ..0............. = May Fragment IP: .0.............. = More Fragments IP: IP: Time to live (sec) = 30 IP: Protocol Type = 17 (UDP) IP: Header Checksum = 20353 IP: Source Address = 156.133.8.45 IP: Destination Address = 156.133.8.26 UDP: UDP: - - - - - User Datagram Protocol (UDP) - - - - - UDP: UDP: Source port = 1133 (Unknown) UDP: Destination port = 161 (Unknown) UDP: Length = 59 UDP: Checksum = 61349 UDP: UDP: Port ??? data Hex for frame 2 0000: 02 CF 1F 90 46 33 AA 00 04 00 53 04 08 00 45 00 ....F3....S...E. 0010: 00 4F 03 CC 00 00 1E 11 4F 81 9C 85 08 2D 9C 85 .O......O....-.. 0020: 08 1A 04 6D 00 A1 00 3B EF A5 30 82 00 2F 02 01 ...m...;..0../.. 0030: 00 04 06 70 75 62 6C 69 63 A0 82 00 20 02 01 02 ...public... ... 0040: 02 01 00 02 01 00 30 15 30 82 00 11 06 0D 2B 06 ......0.0.....+. 0050: 01 04 01 09 02 09 03 01 01 01 03 05 00 ............. IRIS capture data Page 6 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 Summary for frame 3 3 +15m TAURUS<-02CF1F904633 88 DIX 0800 UDP ???: Src=161 Dest=1133 Len=54 Chksum=29361 IP UDP Dest=156.133.8.45 Src=156.133.8.26 Len=74 DLL DIX PType=08-00 Detail for frame 3 DLL: DLL: - - - - - Datalink Header - - - - - DLL: DLL: Frame 3 arrived at 13246 milliseconds, length = 88 bytes DLL: DLL: Destination Address = AA-00-04-00-53-04 (TAURUS) DLL: Source Address = 02-CF-1F-90-46-33 (02CF1F904633) DLL: DIX format, Protocol Type = 08-00 IP: IP: - - - - - Internet protocol (IP) - - - - - IP: IP: Internet header version = 4 IP: Internet header length = 20 bytes IP: Type of service = 00 IP: .....0.. = Normal Reliability IP: ....0... = Normal Throughput IP: ...0.... = Normal Delay IP: 000..... = Routine IP: IP: Total Packet Length = 74 IP: Identification = 1236 IP: Fragment Information = 0000 IP: Fragment Offset = 0 IP: ..0............. = May Fragment IP: .0.............. = More Fragments IP: IP: Time to live (sec) = 255 IP: Protocol Type = 17 (UDP) IP: Header Checksum = 28029 IP: Source Address = 156.133.8.26 IP: Destination Address = 156.133.8.45 UDP: UDP: - - - - - User Datagram Protocol (UDP) - - - - - UDP: UDP: Source port = 161 (Unknown) UDP: Destination port = 1133 (Unknown) UDP: Length = 54 UDP: Checksum = 29361 UDP: UDP: Port ??? data Hex for frame 3 0000: AA 00 04 00 53 04 02 CF 1F 90 46 33 08 00 45 00 ....S.....F3.. E. 0010: 00 4A 04 D4 00 00 FF 11 6D 7D 9C 85 08 1A 9C 85 .J......m}...... 0020: 08 2D 00 A1 04 6D 00 36 72 B1 30 2C 02 01 00 04 .-...m.6r.0,.... 0030: 06 70 75 62 6C 69 63 A2 1F 02 01 02 02 01 00 02 .public......... 0040: 01 00 30 14 30 12 06 0D 2B 06 01 04 01 09 02 09 ..0.0...+....... 0050: 03 01 01 01 03 02 01 07 ........ IRIS capture data Page 7 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 Summary for frame 4 4 +504m 02CF1F904633<- TAURUS 120 DIX 0800 UDP ???: Src=1135 Dest=161 Len=86 Chksum=286 IP UDP Dest=156.133.8.26 Src=156.133.8.45 Len=106 DLL DIX PType=08-00 Detail for frame 4 DLL: DLL: - - - - - Datalink Header - - - - - DLL: DLL: Frame 4 arrived at 13750 milliseconds, length = 120 bytes DLL: DLL: Destination Address = 02-CF-1F-90-46-33 (02CF1F904633) DLL: Source Address = AA-00-04-00-53-04 (TAURUS) DLL: DIX format, Protocol Type = 08-00 IP: IP: - - - - - Internet protocol (IP) - - - - - IP: IP: Internet header version = 4 IP: Internet header length = 20 bytes IP: Type of service = 00 IP: .....0.. = Normal Reliability IP: ....0... = Normal Throughput IP: ...0.... = Normal Delay IP: 000..... = Routine IP: IP: Total Packet Length = 106 IP: Identification = 974 IP: Fragment Information = 0000 IP: Fragment Offset = 0 IP: ..0............. = May Fragment IP: .0.............. = More Fragments IP: IP: Time to live (sec) = 30 IP: Protocol Type = 17 (UDP) IP: Header Checksum = 20324 IP: Source Address = 156.133.8.45 IP: Destination Address = 156.133.8.26 UDP: UDP: - - - - - User Datagram Protocol (UDP) - - - - - UDP: UDP: Source port = 1135 (Unknown) UDP: Destination port = 161 (Unknown) UDP: Length = 86 UDP: Checksum = 286 UDP: UDP: Port ??? data Hex for frame 4 0000: 02 CF 1F 90 46 33 AA 00 04 00 53 04 08 00 45 00 ....F3....S...E. 0010: 00 6A 03 CE 00 00 1E 11 4F 64 9C 85 08 2D 9C 85 .j......Od...-.. 0020: 08 1A 04 6F 00 A1 00 56 01 1E 30 82 00 4A 02 01 ...o...V..0..J.. 0030: 00 04 06 70 75 62 6C 69 63 A0 82 00 3B 02 01 01 ...public...;... 0040: 02 01 00 02 01 00 30 30 30 82 00 0C 06 08 2B 06 ......000.....+. 0050: 01 02 01 01 03 00 05 00 30 82 00 0C 06 08 2B 06 ........0.....+. 0060: 01 02 01 01 01 00 05 00 30 82 00 0C 06 08 2B 06 ........0.....+. 0070: 01 02 01 01 02 00 05 00 ........ IRIS capture data Page 8 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 IRIS capture data Page 9 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 Summary for frame 5 5 +20m TAURUS<-02CF1F904633 250 DIX 0800 UDP ???: Src=161 Dest=1135 Len=216 Chksum=56243 IP UDP Dest=156.133.8.45 Src=156.133.8.26 Len=236 DLL DIX PType=08-00 Detail for frame 5 DLL: DLL: - - - - - Datalink Header - - - - - DLL: DLL: Frame 5 arrived at 13770 milliseconds, length = 250 bytes DLL: DLL: Destination Address = AA-00-04-00-53-04 (TAURUS) DLL: Source Address = 02-CF-1F-90-46-33 (02CF1F904633) DLL: DIX format, Protocol Type = 08-00 IP: IP: - - - - - Internet protocol (IP) - - - - - IP: IP: Internet header version = 4 IP: Internet header length = 20 bytes IP: Type of service = 00 IP: .....0.. = Normal Reliability IP: ....0... = Normal Throughput IP: ...0.... = Normal Delay IP: 000..... = Routine IP: IP: Total Packet Length = 236 IP: Identification = 1237 IP: Fragment Information = 0000 IP: Fragment Offset = 0 IP: ..0............. = May Fragment IP: .0.............. = More Fragments IP: IP: Time to live (sec) = 255 IP: Protocol Type = 17 (UDP) IP: Header Checksum = 27866 IP: Source Address = 156.133.8.26 IP: Destination Address = 156.133.8.45 UDP: UDP: - - - - - User Datagram Protocol (UDP) - - - - - UDP: UDP: Source port = 161 (Unknown) UDP: Destination port = 1135 (Unknown) UDP: Length = 216 UDP: Checksum = 56243 UDP: UDP: Port ??? data Hex for frame 5 0000: AA 00 04 00 53 04 02 CF 1F 90 46 33 08 00 45 00 ....S.....F3..E. 0010: 00 EC 04 D5 00 00 FF 11 6C DA 9C 85 08 1A 9C 85 ........l....... 0020: 08 2D 00 A1 04 6F 00 D8 DB B3 30 81 CD 02 01 00 .-...o....0..... 0030: 04 06 70 75 62 6C 69 63 A2 81 BF 02 01 01 02 01 ..public........ 0040: 00 02 01 00 30 81 B3 30 10 06 08 2B 06 01 02 01 ....0..0...+. ... 0050: 01 03 00 43 04 11 85 FE 38 30 81 88 06 08 2B 06 ...C....80....+. 0060: 01 02 01 01 01 00 04 7C 54 53 20 53 6F 66 74 77 .......\|TS Softw 0070: 61 72 65 20 28 53 54 53 58 2D 4C 52 29 2C 20 56 are (STSX-LR), V IRIS capture data Page 10 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 0080: 65 72 73 69 6F 6E 20 38 2E 33 28 31 29 2C 20 0A ersion 8.3(1), . 0090: 43 6F 70 79 72 69 67 68 74 20 28 63 29 20 31 39 Copyright (c) 19 00A0: 38 36 2D 31 39 39 31 20 62 79 20 63 69 73 63 6F 86-1991 by cisco 00B0: 20 53 79 73 74 65 6D 73 2C 20 49 6E 63 2E 0A 43 Systems, Inc..C 00C0: 6F 6D 70 69 6C 65 64 20 54 75 65 20 32 32 2D 4F ompiled Tue 22-O 00D0: 63 74 2D 39 31 20 30 32 3A 30 38 20 62 79 20 62 ct-91 02:08 by b 00E0: 6C 6F 63 6B 30 14 06 08 2B 06 01 02 01 01 02 00 lock 0...+....... 00F0: 06 08 2B 06 01 04 01 09 01 02 ..+....... IRIS capture data Page 11 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 Summary for frame 6 6 +5m 02CF1F904633<- TAURUS 198 DIX 0800 UDP ???: Src=1135 Dest=161 Len=164 Chksum=23337 IP UDP Dest=156.133.8.26 Src=156.133.8.45 Len=184 DLL DIX PType=08-00 Detail for frame 6 DLL: DLL: - - - - - Datalink Header - - - - - DLL: DLL: Frame 6 arrived at 13775 milliseconds, length = 198 bytes DLL: DLL: Destination Address = 02-CF-1F-90-46-33 (02CF1F904633) DLL: Source Address = AA-00-04-00-53-04 (TAURUS) DLL: DIX format, Protocol Type = 08-00 IP: IP: - - - - - Internet protocol (IP) - - - - - IP: IP: Internet header version = 4 IP: Internet header length = 20 bytes IP: Type of service = 00 IP: .....0.. = Normal Reliability IP: ....0... = Normal Throughput IP: ...0.... = Normal Delay IP: 000..... = Routine IP: IP: Total Packet Length = 184 IP: Identification = 975 IP: Fragment Information = 0000 IP: Fragment Offset = 0 IP: ..0............. = May Fragment IP: .0.............. = More Fragments IP: IP: Time to live (sec) = 30 IP: Protocol Type = 17 (UDP) IP: Header Checksum = 20245 IP: Source Address = 156.133.8.45 IP: Destination Address = 156.133.8.26 UDP: UDP: - - - - - User Datagram Protocol (UDP) - - - - - UDP: UDP: Source port = 1135 (Unknown) UDP: Destination port = 161 (Unknown) UDP: Length = 164 UDP: Checksum = 23337 UDP: UDP: Port ??? data Hex for frame 6 0000: 02 CF 1F 90 46 33 AA 00 04 00 53 04 08 00 45 00 ....F3....S...E. 0010: 00 B8 03 CF 00 00 1E 11 4F 15 9C 85 08 2D 9C 85 ........O....-.. 0020: 08 1A 04 6F 00 A1 00 A4 5B 29 30 82 00 98 02 01 ...o....[)0..... 0030: 00 04 06 70 75 62 6C 69 63 A0 82 00 89 02 01 02 ...public....... 0040: 02 01 00 02 01 00 30 7E 30 82 00 11 06 0D 2B 06 ......0 0.....+. 0050: 01 04 01 09 02 09 03 01 01 01 03 05 00 30 82 00 .............0.. 0060: 11 06 0D 2B 06 01 04 01 09 02 09 03 01 02 01 03 ...+............ 0070: 05 00 30 82 00 11 06 0D 2B 06 01 04 01 09 02 09 ..0.....+....... IRIS capture data Page 12 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 0080: 03 01 03 01 03 05 00 30 82 00 11 06 0D 2B 06 01 .......0.....+.. 0090: 04 01 09 02 09 03 01 04 01 03 05 00 30 82 00 11 ............0... 00A0: 06 0D 2B 06 01 04 01 09 02 09 03 01 05 01 03 05 ..+............. 00B0: 00 30 82 00 11 06 0D 2B 06 01 04 01 09 02 09 03 .0.....+ ........ 00C0: 01 06 01 03 05 00 ...... IRIS capture data Page 13 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 Summary for frame 7 7 +33m TAURUS<-02CF1F904633 199 DIX 0800 UDP ???: Src=161 Dest=1135 Len=165 Chksum=48773 IP UDP Dest=156.133.8.45 Src=156.133.8.26 Len=185 DLL DIX PType=08-00 Detail for frame 7 DLL: DLL: - - - - - Datalink Header - - - - - DLL: DLL: Frame 7 arrived at 13808 milliseconds, length = 199 bytes DLL: DLL: Destination Address = AA-00-04-00-53-04 (TAURUS) DLL: Source Address = 02-CF-1F-90-46-33 (02CF1F904633) DLL: DIX format, Protocol Type = 08-00 IP: IP: - - - - - Internet protocol (IP) - - - - - IP: IP: Internet header version = 4 IP: Internet header length = 20 bytes IP: Type of service = 00 IP: .....0.. = Normal Reliability IP: ....0... = Normal Throughput IP: ...0.... = Normal Delay IP: 000..... = Routine IP: IP: Total Packet Length = 185 IP: Identification = 1238 IP: Fragment Information = 0000 IP: Fragment Offset = 0 IP: ..0............. = May Fragment IP: .0.............. = More Fragments IP: IP: Time to live (sec) = 255 IP: Protocol Type = 17 (UDP) IP: Header Checksum = 27916 IP: Source Address = 156.133.8.26 IP: Destination Address = 156.133.8.45 UDP: UDP: - - - - - User Datagram Protocol (UDP) - - - - - UDP: UDP: Source port = 161 (Unknown) UDP: Destination port = 1135 (Unknown) UDP: Length = 165 UDP: Checksum = 48773 UDP: UDP: Port ??? data Hex for frame 7 0000: AA 00 04 00 53 04 02 CF 1F 90 46 33 08 00 45 00 ....S.....F3..E. 0010: 00 B9 04 D6 00 00 FF 11 6D 0C 9C 85 08 1A 9C 85 ........m....... 0020: 08 2D 00 A1 04 6F 00 A5 BE 85 30 81 96 02 01 00 .-...o....0..... 0030: 04 06 70 75 62 6C 69 63 A2 81 88 02 01 02 02 01 ..public........ 0040: 00 02 01 00 30 7D 30 12 06 0D 2B 06 01 04 01 09 ....0}0...+..... 0050: 02 09 03 01 01 01 03 02 01 07 30 12 06 0D 2B 06 ..........0...+. 0060: 01 04 01 09 02 09 03 01 02 01 03 02 01 03 30 11 ..............0. 0070: 06 0D 2B 06 01 04 01 09 02 09 03 01 03 01 03 40 ..+............@ IRIS capture data Page 14 Trames entre TAURUS et CISCO52 11/20/92 17:22:04 0080: 04 00 00 00 00 30 17 06 0D 2B 06 01 04 01 09 02 .....0...+...... 0090: 09 03 01 04 01 03 04 06 42 49 4C 55 58 42 30 12 ........BILUXB0. 00A0: 06 0D 2B 06 01 04 01 09 02 09 03 01 05 01 03 02 ..+............. 00B0: 01 00 30 13 06 0D 2B 06 01 04 01 09 02 09 03 01 ..0...+... ...... 00C0: 06 01 03 02 02 0C 2B ......+
4048.10	So it is them, not us.	YAHEY::BOSE		`Tue Nov 24 1992 20:54`	18
	Renato, Pretty good analysis on your part. As you pointed out, the Cisco agent needs to be fixed. The difference between us and NAT/NMS is that we ask for all the attributes in a partition in one Get-request PDU, and if anything is abnormal in the response PDU we reject the whole PDU. NAT/NMS, on the other hand, seems to be asking for each mib variable separately and can therefore ignore the bad values. Its either that, or it has the ability to open up the PDU and select the good values, while rejecting the bad ones. It is something that we might want to look into for future versions of the SNMP AM. Rahul.