Mailing List Archive: %NP_MD-3-TX_INBAND_MSG

%NP_MD-3-TX_INBAND_MSG_FAILURE message

Mar 16, 2004, 5:54 AM

Post #1 of 3 (628 views)

I have a 5350 (12.3(1a) + np.8.5.spe) and i'm getting quite a lot of messages like the one
below:

%NP_MD-3-TX_INBAND_MSG_FAILURE: Failed to send inband message for port 2/88 (enqueue fail
for framing mode=1)
%NP_MD-3-TX_INBAND_MSG_FAILURE: Failed to send inband message for port 2/63 (enqueue fail
for framing mode=1)

I have found 3 bugs (CSCdx36518, CSCdx06719, CSCdx75525) related, but 2 of them are
refering to cpu load and the last one to memory problems, while this 5350 goes up until
15% cpu load and has no memory problems.
Also, all bugs do not appear to apply to 12.3(1a) IOS.

Could there be something else i'm missing?

--
***************************************
Chatzithomaoglou Anastasios
Network Design & Development Department
FORTHnet S.A.
<achatz@forthnet.gr>
***************************************

Re: %NP_MD-3-TX_INBAND_MSG_FAILURE message [ In reply to ]

Aaron at Cisco

Mar 16, 2004, 9:50 AM

Post #2 of 3 (622 views)

Permalink

What input/output queue sizes do you have set on your async interfaces?

If you set this on your group-async:
--input queue 30
--output queue 65
does the problem go away?

Aaron

---

> I have a 5350 (12.3(1a) + np.8.5.spe) and i'm getting quite a lot of messages like the one
> below:

> %NP_MD-3-TX_INBAND_MSG_FAILURE: Failed to send inband message for port 2/88 (enqueue fail
> for framing mode=1)
> %NP_MD-3-TX_INBAND_MSG_FAILURE: Failed to send inband message for port 2/63 (enqueue fail
> for framing mode=1)

> I have found 3 bugs (CSCdx36518, CSCdx06719, CSCdx75525) related, but 2 of them are
> refering to cpu load and the last one to memory problems, while this 5350 goes up until
> 15% cpu load and has no memory problems.
> Also, all bugs do not appear to apply to 12.3(1a) IOS.

> Could there be something else i'm missing?

> --
> ***************************************
> Chatzithomaoglou Anastasios
> Network Design & Development Department
> FORTHnet S.A.
> <achatz@forthnet.gr>
> ***************************************

> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas

Re: %NP_MD-3-TX_INBAND_MSG_FAILURE message [ In reply to ]

achatz at forthnet

Mar 16, 2004, 9:58 AM

Post #3 of 3 (620 views)

Permalink

Aaron Leonard wrote:

> What input/output queue sizes do you have set on your async interfaces?
>

default input (=10 ?)
20 output

> If you set this on your group-async:
> --input queue 30
> --output queue 65
> does the problem go away?
>

I'll give it a try and see what happens...

> Aaron
>
> ---
>
>
>>I have a 5350 (12.3(1a) + np.8.5.spe) and i'm getting quite a lot of messages like the one
>>below:
>
>
>>%NP_MD-3-TX_INBAND_MSG_FAILURE: Failed to send inband message for port 2/88 (enqueue fail
>>for framing mode=1)
>>%NP_MD-3-TX_INBAND_MSG_FAILURE: Failed to send inband message for port 2/63 (enqueue fail
>>for framing mode=1)
>
>
>>I have found 3 bugs (CSCdx36518, CSCdx06719, CSCdx75525) related, but 2 of them are
>>refering to cpu load and the last one to memory problems, while this 5350 goes up until
>>15% cpu load and has no memory problems.
>>Also, all bugs do not appear to apply to 12.3(1a) IOS.
>
>
>>Could there be something else i'm missing?
>
>
>>--
>>***************************************
>> Chatzithomaoglou Anastasios
>>Network Design & Development Department
>> FORTHnet S.A.
>> <achatz@forthnet.gr>
>>***************************************
>
>
>>_______________________________________________
>>cisco-nas mailing list
>>cisco-nas@puck.nether.net
>>https://puck.nether.net/mailman/listinfo/cisco-nas
>
>

--
***************************************
Chatzithomaoglou Anastasios
Network Design & Development Department
FORTHnet S.A.
<achatz@forthnet.gr>
***************************************