Subscribe

Is there any way to tell what 'entry' it refers to in "entry doesn't exist" error?

Hi,

 

cDOT 8.3GA on FAS8040

 

I sometimes get "entry doesn't exist" error when using cDOT CLI. I think it will be very helpful to know what entry it refers to. Since it knows something is missing, why not output as part of error message what that something is?

 

Is there a way to have the error message output more specific info?

 

Thanks,

Re: Is there any way to tell what 'entry' it refers to in "entry doesn't exist" error?

Can you post a sample command that produces the output?  I've seen similar things from time to time if the command syntax is slightly off - for instance a missing comma in a list, a missing dash on an option - and the CLI tries to interpret an "option" as a value and it gets confused - and vague.