Cat4500e Sup7e Flow control - strange log

[pic_whizz]

Hi,

We have just deployed a large number (33) Cat4500e SUP7e running 3.3.2 IOS XE. Only on one switch we see this message in the logs:-

%C4K_NOVAFFM-3-SPIMANEXCESSIVEFLOWCONTROLWAIT: STANDBY:SpiMan: excessive wait > 10000 ms blocking for flow control on RkNovaFfmL2_AggPortUpdate count == 85125 (suppressed 3 times)

I cannot find any info on this error. Please could someone explain what this means and what the fix is..

Many Thanks,

Matt

[Wilson Bonilla]

Hi Matt.

Those messages come in the logs when excessive amount of mcast packets are punted to the CPU. I would say if you don't see high cpu utilization you don't really need to worry about, maybe it was a SEU.

Wilson B.

[andyirving]

The FFM is the Forwarding Feature Manager in IOS XE, this is essentially the control plane, so it does look like its an internal error rather than a data plane issue.

As it only happens on one of the 33 switches I think it is a transient issue, a reboot is in order I think.

Let us know if it resolves the issue for future reference.

Andy I

[Lionel Bourdillon]

Hi Matt,

Do you resolve your problem ?

I get the same type of logs on a 4500X VSS (IOS XE 03.04.00.SG) :

Apr 18 11:30:31: %C4K_NOVAFFM-3-SPIMANEXCESSIVEFLOWCONTROLWAIT: SpiMan: excessive wait > 10000 ms blocking for flow control on RkNovaFfmL3_UnionUpdateBulk count == 14399 (suppressed 6 times)

Apr 18 11:31:05: %C4K_NOVAFFM-3-SPIMANEXCESSIVEFLOWCONTROLWAIT: SpiMan: excessive wait > 10000 ms blocking for flow control on RkNovaFfmServicePolicy_onServicePolicyUpdate count == 5183 (suppressed 6 times)

Thanks,

Lionel

[InayathUlla Sharieff]

Hi  Lionel,

As Wilson stated above I will stand with him on the same answer:

C4K_NOVAFFM-3-SPIMANEXCESSIVEFLOWCONTROLWAIT<http://www.cisco.com/cgi-bin/Support/Error
decoder/index.cgi?action=search&counter=0&paging=5&links=reference&index=all&query=C4K_NOV
AFFM-3-SPIMANEXCESSIVEFLOWCONTROLWAIT >  SpiMan: excessive wait > 10000 ms blocking
for flow control on RkNovaFfmMfib_UnionBulkUpdate count == 688 (suppressed 3 times)

Action plan:


The reason for those messages was that there were many packets in CPU queue waiting to be
processed.

Workaround:

Just reload the switch and let me know the status of the switch.

HTH

Regards

Inayath

*Plz rate all usefull posts.

[Lionel Bourdillon]

Hi Inayath,

A reload of the entire VSS and I no longer receives the logs.

Before reloading i tried a VSS switchover : it had no effect on the logs.

thanks for your help,

Lionel

[InayathUlla Sharieff]

Hi Lionel,

Thanks for the update. Happy to hear the news.

HTH

REgards

Inayath

*Plz rate all usefull posts.