[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

605.0. "MCC aborts when NCL continues - bug or feature?" by MEK::KENNEDY (Give me your watch & I'll tell you) Wed Jan 09 1991 17:34

Executing the command:
	Show Node router_name Routing Destination Node * All Ident

MCC reports "Insufficient resources at target entity" and returns to the prompt.

NCL (on DECnet/ULTRIX) reports the error:
	"FAILED IN DIRECTIVE: Show
	 DUE TO: No Resource Available",
but continues to list more Destination Nodes.

Is this the intended behavior of MCC?
T.RTitleUserPersonal
Name		DateLines
605.1Let's call it a "Restriction"TOOK::CAREYThu Jan 10 1991 11:4317
    
    Bug or Feature?  How 'bout restriction?
    
    I didn't realize that NCL rebounded from that error.
    
    MCC could probably be trained to respond similarly, I'm just not sure
    that we should spend the resources on that right now.
    
    We have high hopes that as the routers mature they will not be as prone
    to this sort of resource problem and the whole thing will become a 
    non-issue.  Perhaps that is wishful thinking.
    
    Anyway, thanks for pointing out the difference, do you have strong
    opinions in either direction?
    
    -Jim Carey
605.2MARVIN::COBBGraham R. Cobb (Wide Area Comms.), REO2-G/H9, 830-3917Thu Jan 10 1991 15:4417
>    We have high hopes that as the routers mature they will not be as prone
>    to this sort of resource problem and the whole thing will become a 
>    non-issue.  Perhaps that is wishful thinking.

You must be joking :-)

Actually that  particular  problem  seems  to  have  gone  away.  At least I
haven't  seen  it here (in OSIrouter 500 development) for a while.  However,
the  DEMSA-based  routers  will  always  be very tight on memory (even newer
routers aren't going to be happy to waste much memory which could be used to
support larger networks).

It would  be  nice  if MCC continued.  That error can sometimes be fatal and
sometimes  not (it depends where the resource problem occurs).  However, the
CMIP protocol indicates unambiguously whether there is more data.

Graham
605.3I'd rather see all the informationMEK::KENNEDYGive me your watch & I'll tell youThu Jan 10 1991 16:5224
Re: .1

I'd prefer DECmcc to display the rest of the info, assuming that its possible. 
In this case (see rest of note), the problem is completely reproducible, so
I don't see how retrying the command (hoping that the resource situation has
improved) would help.   

Re: .2
> Actually that  particular  problem  seems  to  have  gone  away.  At least I
> haven't  seen  it here (in OSIrouter 500 development) for a while.  

I'm anxiously awaiting the EFT update now. (tho not relevant to this 
discussion, I think the error might be misleading:

Show Node MEK_NS:.vrtnr1 Routing Destination Node AA-00-04-00-3C-30
%NCL-E-INVALIDCMLDATA, return data corrupt or incorrectly encoded
 at %X00000000000000000000000000000000

Command failed due to:
 no resources available

It always fails on this node, which (coincidentally?) is the router itself.
I'm pretty ignorant about what's going on here, but it doesn't really smell
like a resource problem to me.
605.4MARVIN::COBBGraham R. Cobb (Wide Area Comms.), REO2-G/H9, 830-3917Fri Jan 11 1991 11:237
There was indeed a non-resource related problem with the Routing Destination
Node  management  which  has  been  fixed.  It may well have been related to
this.

By the way, the %NCL-E-INVALIDCMLDATA error is fixed in EFTU as well.

Graham