ISR 4321 got annoying messages if i start terminal moinitor

[marcel.pludra]

Hi all,

i got annoying messages if i enable 'terminal monitor' on my ISR4321.

Following messages occur:

*Feb 22 10:02:01.058: IOSXE-INJECT: set pak datagramstart(from 0x7FB53EF0F8F8 to 0x7FB53EF0F8F8), datagramsize(from 576 to 576);
*Feb 22 10:02:01.058: IOSXE-INJECT: add L3 inject hdr
*Feb 22 10:02:01.058: IOSXE-INJECT: inject hdr len 32, feature hdr len 0, l2-enc len 0, link type ip, pak len 576, total len 608, inject type normal, seqnum 71590
*Feb 22 10:02:01.058: IOSXE-INJECT: inject_sb inject_flag=0x0, subtype=0, type_flags=0x0,
*Feb 22 10:02:01.058:  send out the l3 packet to cpp:
7FB53EF0F8D0:                   01010000 00000240          .......@
7FB53EF0F8E0: 02600000 20010000 00000000 0000000E  .`.. ...........
7FB53EF0F8F0: 01000001 00100200 45C00240 C9920000  ........E@.@I...
7FB53EF0F900: FF06A59E 0A8EFA01 C0A8848E 0016D9D3  ..%...z.@(....YS
7FB53EF0F910: D791425A 8050D608 50100E4C B39A0000  W.BZ.PV.P..L3...
7FB53EF0F920: 093BEA0D C87B4A63 6EECEC0F 8B773949  .;j.H{Jcnll..w9I
7FB53EF0F930: A5A9CA0B BD555F36 D2F68EF1 692B192E  %)J.=U_6Rv.qi+..
7FB53EF0F940: BD53137D 2EA3881C 578ACF52 87F181AD  =S.}.#..W.OR.q.-
7FB53EF0F950: 1E26D06D A7EA1BC2                    .&Pm'j.B
*Feb 22 10:02:01.062:  IP protocol TCP dst 55763, src 22 ...
*Feb 22 10:02:01.062: IOSXE-INJECT: pak inject type normal, ready for tx, seqnum 71590
*Feb 22 10:02:01.062: IOSXE-INJECT: inject_hdr pal_if_handle=0xE, flags=0x10, cause=2, sub_cause=0Output intf Di0 matches debug filer

My ISR is working as a CUBE. There is a Dialer configured and a SIP Trunk to Provider and CUCM.
I think this messages are from the Dialer 0 interface.

Can i ignore this messages?
And how can i deactivate this messages because i want to debug SIP messages and i cannot do this because of this annoying messages.

Is it maybe a proivder Problem?

Thanks for helping

[AckAck]

Glad I'm not the only one. Had an ISR 4331 doing the same thing. Maybe related to this bug.

when debug interface is applied, this is treated as debug condition however it causes actual messages to be printed, without having any actual debug enabled [just debug condition is present]

I was able to clear it by dumping the debug for the interface (even though the if doesn't show up in sho debug). So run:

no debug interface Di0

Or whatever interface is being shown in your output. Mine was Output intf Gi0/0/1 matches debug filer, so ran the above with Gi0/0/1 and it stopped the messages. 

When I ran this, it returned the following:

This condition is the last interface condition set.
Removing all conditions may cause a flood of debugging
messages to result, unless specific debugging flags
are first removed.

Proceed with removal? [yes/no]: y

This sounds a lot like the bug listed above. For grins, you may want to first check sho debug condition all, just to see if a condition is actually reported there. I cleared mine before checking this, but would have been interesting to see.