[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

2984.0. "PhaseV events logged from router when using iconic map" by RDGENG::PRATT () Tue May 12 1992 17:49

Running VMS T1.2.7 (but also occurs with Ultrix T1.2.7 with DNU T5.1-5)

When using the iconic map to look at a phaseV router, double clicking on the 
node entity causes the following events to be logged by the router (both DECnis 
and WANrouter).

Event: Remote Protocol Error,
       from: Node DEC:.reo.reotn1 NSP Local NSAP %X490001AA000400020420 Remote N
SAP %X49002AAA00040064A820
       at  : 1992-05-12-19:43:31.970+01:00Iinf

       Reject Cause                      = Invalid Message Format
       Erroneous Transport PDU           = '48D5B8EF002A00'H





Event: Remote Protocol Error,
       from: Node DEC:.reo.reotn1 NSP Local NSAP %X490001AA000400020420 Remote N
SAP %X49002AAA00040064A820
       at  : 1992-05-12-19:43:32.520+01:00Iinf

       Reject Cause                      = Invalid Message Format
       Erroneous Transport PDU           = '48D7B8F1002A00'H

It logs about 20 of these each time. It doesn't appear to fail, because the map
eventually displays the child entities. Clicking on child entities also cause
similiar events to be logged.

Ian Pratt

T.R	Title	User	Personal Name	Date	Lines
2984.1	maybe it's 5.1 CMIP negotiation	TOOK::PURRETTA		`Tue May 12 1992 21:47`	18
	Ian, I think I know what's happening. In V1.2 we added support for CMIP 5.1 negotiation. This was needed by the DMS folks and common agent. What we now do is send a connect request to the entity with our version field in the NCB set to 5.1.0 to say we also support 5.1 CMIP. The node is supposed to negotiate down and send us 5.0.0 if that's all it supports or send us back 5.1.0 if it also supports CMIP 5.1. Ultrix and VMS do this currently. In the AM we also have a backoff algorithm such that if the node flat out rejects the request, we try again but send 5.0.0. My guess is that the routers look at the 5.1.0 and consider it an error and generate an event. I'll try to find out who I can talk to in router development about this. John
2984.2	No, but its our bug	MARVIN::COBB	Graham R. Cobb (Wide Area Comms.), REO2-G/H9, 830-3917	`Wed May 13 1992 11:51`	10
	The problem in .0 isn't the CMIP negotiation problem (although you are right that we don't correctly handle negotiation). It is a bug in our NSP implementation. It is present in WANrouter V1.0 and V1.0A, X25Gateway V1.0 and V1.0A, DECNIS V1.0 and V1.1. Ian has now QAR'd it against the DECNIS so we will try to fix it for V2.0. I will also QAR the CMIP negotiation bug. Graham (DECNIS software project leader)