Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Help with an unknown Error-message

Hello all,

Can anybody help me with the following error-message that appears from time to time in my syslogfile? I have searched the whole internet for an explanation.

Sep 25 02:38:42 as5300-3 4028: Sep 25 02:38:41: %LINK-3-BOGUSENCAP: Interface Serial2:7, bad encapsulation in idb->enctype = 0x30

Thanks,

Martijn Koopsen

3 REPLIES
Bronze

Re: Help with an unknown Error-message

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122sup/122sems/semsvol1/emflcfe.htm#xtocid13

It would be interesting to see the config and the version being used, as well as how often you are seeing the message. Are there any other messages immediately before or after this one?

New Member

Re: Help with an unknown Error-message

Currently i am running 12-1-16 IP version.

I asked if i could send a config but the company policy prohibits it. But i can tell you that the config is very staightforward.... No fancy stuff.

I thought it had something to do with the autodetect encapsulation command you can set on the serial interfaces but what i did ......it sure did not work.

The message is there approxiamately every 10th caller......There is however no relationship between for example analog/isdn and the error........... But the calls were not connected if the error came along.

Another odd thing was that the person that dialed in.......did not get connection.....tried again.......and there was success.

The only thing i could find was that if the callload went up the problem pooped up.

There are no other messages before or after.......

Bronze

Re: Help with an unknown Error-message

I really don't see any mention of this message in the last 18 months, so this could be a new issue. I would suggest you open a case with the TAC, include the serial config (if possible), the version, and the logged messages, so that this can be further pursued. I can't say right now what the cause is, what a workaround may be, or what the effect (aside from a failed call) is.

92
Views
0
Helpful
3
Replies
CreatePlease to create content