"CPU Receive Multicast Queue is full"

Hello.
I am getting a Critical controller error on my WCS panel that says "CPU Receive Multicast Queue is full on Controller 'xxx.xxx.xxx.xxx'. "
I have blanked out the IP above- it's the controller's IP address.
What exactly does this error mean, and what can I do to fix this? I haven't had much luck in finding information on this particular error and it's starting to bother me.
It triggers a couple times a day, or sometimes several days apart.
My controller is running version 4.1.171.0 and my WCS is 4.1.83.0.
Thanks!

Hi Peter,
There is a bug filed for the same CSCsf27201. Sometimes even when you are not using multicast traffic ,ARP and CDP packet keep hitting controller CPU and reports this message. Although these packets are dropped when que gets filled but WLC reports this message which will is already resolved in upcoming release.
This message will not affect your network in anyway.
HTH
Ankur
*Pls rate all helpfull post

Similar Messages

Wism 7.0.230 Alarm: CPU Receive Multicast Queue is full on Controller

Hello
How can I get rid of this message ?
"Cpu Receive Multicast Queue is full on Controller"
This alarm appears every 5 minutes.
I have this message only with Wism2, not with Ctrl 5508.
Do you know if this affect controller performance ?
Regards
Michel Misonne

There have been many post similar to yours, except you have the WiSM2. From other post, it seems like it doesn't affect performance but more of an eye sore. I guess you can wait to see if one of the Cisco engineer respond to your post and maybe try will be able to clarify why you see than my assumption of an "eye sore":)
Here is from an older doc
Q. I see a lot of "CPU Receive Multicast Queue is full on Controller" messages on the 2006 Wireless LAN Controller (WLC), but not on the 4400 WLCs. Why? I have disabled multicast on the controllers. What is the difference in the Multicast Queue Limit between the 2006 and 4400 WLC platforms?
A. Because multicast is disabled on the controllers, the messages that cause this alarm might be Address Resolution Protocol (ARP) messages. There is no difference in queue depth (512 packets) between the 2000 WLCs and the 4400 WLCs. The difference is that the 4400 NPU filters ARP packets whereas everything is done in software on the 2006. This explains why the 2006 WLC sees the messages but not the 4400 WLC. A 44xx WLC processes multicast packets via hardware (through CPU). A 2000 WLC processes multicast packets via software. CPU processing is more efficient than software. Therefore, the 4400's queue is cleared faster, whereas the 2006 WLC struggles a bit when it sees a lot of these messages.
Sent from Cisco Technical Support iPhone App

WiSM error message : Message: CPU Receive Multicast Queue is full on Controller

Hi,
I heve several WiSM modules, the version is 7.0.220.0. Each of WiSM receive the following error message : CPU Receive Multicast Queue is full on Controller. I searched the bug toolkit, some old version of WLC hit this bug, but not affect our version.. Please help to mention me how to debug this error.
Best Regards,

Multicast Queue Depth
The multicast queue depth is 512 packets on all controller platforms. However, the following message might appear on 2106 controllers: “Rx Multicast Queue is full on Controller.” This message does not appear on 4400 series controllers because the 4400 NPU filters ARP packets while all forwarding (multicast or otherwise) and multicast replication are done in the software on the 2106.
This message appears when too many multicast messages are sent to the CPU. In controller software releases prior to 5.1, multicast, CDP, and ARP packets share the same queue. However, in software releases 5.1 and later, these packets are separated into different queues. There are currently no controller commands that can be entered to determine if the multicast receive queue is full. When the queue is full, some packets are randomly discarded.
Do you have a lot of clients using multicast ?
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin

WiSM - "CPU Receive Multicast Queue is full on controller"

After we upgrade to WiSM 4.1.185.0 for 5 days, we got critical
alert message about "CPU Receive Multicast Queue is full on
Controller" from one controller. We have never seen this error in previous
versions. I do not see high CPU usage on the controller now. What could be wrong?
Thanks!
Zhenning

Yes we have ethernet multicast disabled on the controller. I cannot see that bug it is saying available to employee only.
I only see this message once. I opened a TAC case and I was told it could be caused by traffic and this message should not effect anything.
Zhenning

5508 - Multicast Error Messages - Receive Multicast Queue is full on Controller

I'm starting to see an error creep up that I havn't seen since 2003/2004 on my brand new 5508 controllers. I'm recieving the following from my WCS:
Receive Multicast Queue is full on Controller and then on the controller itself RX Multicast Queue Full. I understand this used to be due to a large influx of ARP requests or CDP packets on older controllers but, this was supposed to be fixed in an update many years ago.
I'm just wondering if anyone else has seen this on their 5508's. These were advertised as having the horsepower to handle our user loads which arn't really that high at 300 users at any given time max. Has anyone seen this?

Traditionally, this was a cosmetic error, a the WLC uses the same queue for Multicast, Unicast and Broadcast traffic.
One thing to check is that you aren't trunking all of your VLAN to the WLC, just the ones that support wireless clients.
Steve

WISM-2 RX Multicast Queue Full

We are running a WISM-2 controller with software release 7.2.111.3 (which unfortunately i cannot upgrade right now). There are 290 Access Points connected to the controller with up to
670 current clients.
Almost every weekday for the last two weeks (during peek times mostly) we go the message "RX Multicast Queue Full" several times. When this happens we get a lot of syslog messages from the controller as well:
Local0.Warning -Traceback: 1018e840 10627490 1060b448 10931318 119cc460 11a3256c
Local0.Warning *dtlArpTask: Apr 22 11:45:35.528: %BCAST-4-Q_ADD_FAILED: bcast_net.c:3594 Broadcast/Multicast queue add failed.
Local0.Warning -Traceback: 1091bc28 1018e7ec 10627490 1060b448 10931318 119cc460 11a3256c
Local0.Warning *dtlArpTask: Apr 22 11:45:35.528: %OSAPI-4-MSGQ_SEND_FAILED: osapi_msgq.c:518 Failed to send a message to the message queue object: BCAST-Q . enqueue failed.
At the most we got about 100.000 syslog messages just from this on a single day.
Broadcast and multicast are both disabled on the controller and everything i have found in the forums and in the system message guides seem to indicate that there is no
negative impact on performance from this.
I would really like to find out which traffic exactly causes these messages but i have not found a good way (or any way at all really) to troubleshoot this yet.
Can anybody give me some pointers or should i contact Cisco TAC and open a case for this?
Thanks in advance for any help!

There shouldn't be any negative impact from this...but there is alwasy a chance.
take a look at the switch side config for the WiSM. Make sure you are pruning non-wireless VLANs from the portchannel
"wism slot 3 module 2 allowed vlan 100,101,102,110 etc.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

%ACE-2-901001 kernel: Warning:-MTS queue is full messages on ACE 4710

I am getting the following messages repeated continually in my Admin context
Apr 18 2012 14:42:27 CHIACE01: %ACE-2-901001 kernel: Warning:- MTS queue is full for opcode 4062 sap 63994 pid 18847 clear idle debug plugin sessions or telnet/ssh connections to recover
How do i clear them?
How can I check whether i have idle debug sessions?
or telnet/ssh sessions ( as far as i am aware no open telnet sessions, as they alway time out after 5 minutes)!

Hi,
Could be related to CSCtn85846
Symptom:
A warning message is displayed as follows: "Warning:- MTS queue is full for opcode %d sap %d pid %d clear idle debug plugin sessions or telnet/ssh connections to recover"
Conditions:
MTS messages to command shell are not processed as it executes user commands. Because a user command may take a while to terminate, the command shell can receive many MTS messages which won't be processed and run out of buffer space for the MTS queue. When this happens, a warning message is displayed.
Workaround:
This warning can be ignored. User can close all debug plugin sessions and terminate command execution in all telnet/ssh connections to stop display of warnings.
Dan

AS5350- DNS Task Queue is FULL

AS5350: Following errors and tracebacks observed.
%SIP-3-INTERNAL: DNS Task Queue is FULL -Traceback= 0x60460880 0x61423724 0x613C2C9C 0x613EA948 0x613FC8E8 0x6144F9C4 0x6144FC60
%SIP-3-INTERNAL: DNS Task Queue is FULL -Traceback= 0x60460880 0x61423724 0x613C2C9C 0x613EA948 0x613FC8E8 0x6144F9C4 0x6144FC60
%SIP-3-QUEUE_ERROR: Unable to enqueue event SIPSPI_EV_DNS_RESOLVE (38) to a process watched queue. Current size: 128, max size: 128 -Traceback= 0x60460880 0x614235EC 0x6144F888 0x613C2BF4 0x613EA948 0x613FC8E8 0x6144F9C4 0x6144FC60
Is there a way to manipulate this queue size and avoid such errors.
What is the mechanism that generates these errors.
Thanx in advance.

An internal or external event was dropped because it could not be added to the queue, probably because the queue is full. The result can be minor (retransmission of a SIP message) or major (dropped call), depending on the event that was lost. This error might indicate that the call rate is exceeding the capacity of the gateway. If this is the case, the CPU utilization is excessively high (above 75%). Copy the error message exactly as it appears on the console or in the system log. Issue the show process memory command to gather data that may help identify the nature of the error.

Unable to receive multicast on a multi network interface host

Can anyone please help?
I am not able to receive multicast on a multi network interface host.
This is the code:
public class LegacyMulticast {
public static void main(String[] args) throws IOException {
InetSocketAddress group = new InetSocketAddress("224.10.20.30", 12345);
NetworkInterface iface = NetworkInterface.getByName("eth3");
MulticastSocket socket = new MulticastSocket();
socket.setSoTimeout(5000);
socket.joinGroup(group , iface);
byte[] b = new byte[4096];
DatagramPacket datagram = new DatagramPacket(b, b.length);
try {
socket.receive(datagram);
System.out.println("Success");
catch (SocketTimeoutException ste) {
System.out.println("Failure");
socket.leaveGroup(group, iface);
The funny thing is that when I start this code, Wireshark detects IGMP join on the correct network interface caused by joinGroup call, followed by constant UDP traffic on correct port which I aim to receive and finally I see correct IGMP leave caused by leaveGroup call and the UDP traffic stops.
I just don't receive anything on socket.receive call.
I am trying to figure this one out for days now. Pls help someone :)
P.S. I suspected security, but System.getSecurityManager() call returns null.
P.P.S. I also tried implementing this with NIO, but with same result.

public class LegacyMulticast {
public static void main(String[] args) throws IOException {
InetSocketAddress group = new InetSocketAddress("224.10.20.30", 12345);
NetworkInterface iface = NetworkInterface.getByName("eth3");
MulticastSocket socket = new MulticastSocket(12345);
socket.setSoTimeout(5000);
socket.joinGroup(group , iface);
byte[] b = new byte[4096];
DatagramPacket datagram = new DatagramPacket(b, b.length);
try {
socket.receive(datagram);
System.out.println("Success");
catch (SocketTimeoutException ste) {
System.out.println("Failure");
socket.leaveGroup(group, iface);
This is still not working.
The multicast is coming from the network (not localhost), OS is Windows 7.
When I start a multicast stream localy via VLC application on this same group and port, I receive the traffic in this Java application OK.
Once again, Wireshark detects IGMP join and leave and multicast traffic flow on eth3 network interface initiated by the Java application, but it just doesn't see the UDP datagrams.

Help in resolving the error - Incident Queue is full

I've been given a 4.2.4 system to look into since the previous admin left some time ago.
I have found we are seeing the following
Error pn datax IncidentXmlNotificationServlet PN-1100: Java message: Error sending XML Notification. Incident Queue is full.
and we no longer get the previously configured XML emailed actions when a rule gets hit.
I have been looking trying to determine what and how needs to be cleared.
Any insight would be appreciated.

Thanks,
Actually that is what I did (reboot) and functionality has returned.
Thanks for suggesting something so obvious that I didn't think about that. I guess I wanted to make the issue and resolution more complex that it needed to be.

TCP Provider: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

Hi All,
We have snapshot replication . Job is failing in between due to below error.
Error messages:
The process could not connect to Subscriber 'XX:SD'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20084)
Get help: http://help/MSSQL_REPL20084
TCP Provider: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. (Source: MSSQLServer, Error number: 10055)
Get help: http://help/10055
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
see SQL Server Books Online. (Source: MSSQLServer, Error number: 10055)
Get help: http://help/10055
Login timeout expired (Source: MSSQLServer, Error number: HYT00)
Get help: http://help/HYT00
Please suggest

Hi Khushi，
According to your description, your snapshot replication job fails and you come across the error related to TCP Provider. Based on my research, the issue could occur as the following two situations.
1. OS runs out of memory for TCP buffers. When people use the two switch: the /PAE switch in the c:\boot.ini file and the /3gb switch in the boot.ini file. If the applications require many OS resources, such as by opening many TCP connections, this can cause
the OS to run out of memory for resources like TCP buffers.
2.OS runs out of available TCP “ephemeral” ports. When the client machine is opening many TCP connections and is running Windows Server 2003, Windows XP, or any earlier version of Windows, it may run out of TCP “ephemeral” ports.
To work around the issue, please follow the two solutions as below.
1.Remove the /3gb switch from c:\boot.ini. The root problem in this case is memory pressure on the OS, so removing the /3gb switch will give more memory to the OS and will alleviate this problem.
2.Make more ephemeral ports available following the steps in the article:
http://support.microsoft.com/kb/196271
For more information about the process, please refer to the article:
http://blogs.msdn.com/b/sql_protocols/archive/2009/03/09/understanding-the-error-an-operation-on-a-socket-could-not-be-performed-because-the-system-lacked-sufficient-buffer-space-or-because-a-queue-was-full.aspx
Regards,
Michelle Li

Can receive multicast with 2 different IP Subnet

I Have Sun Server installed with Solaris 10, and because the application requirement I had 2 interface with different subnet for example 10.160.x.x and 10.19.x.x right now only interface 10.160.x.x can receive multicast packets while multicast packet from 10.19.x.x subnet can not be receive by the 10.19.x.x interface.
Is there any configuration need so the 10.19.x.x can receive the multicast packets.
Sorry if my english is not good.
Regards,
Abi

MrHoffman wrote:
Where? There are various spots to [learn about Mac OS X Server|http://www.apple.com/server/macosx/resources/documentation.html]. For this case, in [the web administration manual|http://images.apple.com/server/macosx/docs/WebTech_Adminv10.6.pdf], certainly. Or the "Managing Multiple Sites on One Server" in the Web section of the Server Admin help file. Via Google, of course. Or [something here|http://labs.hoffmanlabs.com/node/1329]? The underpinnings of this environment are Apache, and you can learn about the pieces underneath Server Admin (and what Apple calls "sites") at the [Apache web site|http://www.apache.org], and in various Apache books.
I found the Apple's web administration manual you referenced contains numerous inaccuracies that it makes it difficult to use. For example, on page 35 is says:
+To create a website:+
+1. Open Server Admin and connect to the server.+
+2. Click the triangle at the left of the server.+
+3. The list of services appears.+
+4. From the expanded Servers list, select Web.+
+5. Click Sites, then click the Add (plus) button to add a site.+
The problem is there is you cannot ad a site from Server Admin, and it actually should be Server Preferences. Server 10.6 has a tab called Custom Sites, and there is no reference to it in the web administration manual. When I add a custom site, which I think is a second website in addition to the one that the server hosts, it asks about IP address and port (80 as a default). the IP address has an option "Any" and "10.0.1.5". I tried both and none of them works.
I will try to research more, but if you have any suggestion on how to setup a second website (domain name) correctly, please respond.

Odd messages in Console log: Event queue is full!

Hi Everyone,
I have been trying to use Dolly Drive for cloud Time Machine backups, and I'm pretty certain that Dolly Drive is not the culprit, but there is some underlying problem.
I am seeing tons of these messages:
/System/Library/CoreServices/coreservicesd[29] FMOD WATCH EVENTS DROPPED!
mds[41] (Error) FMW: WE ARE DROPPING FMW EVENTS!
And these:
kernel add_fsevent: event queue is full! dropping events (num dropped events: 148; num events outstanding: 2391).
kernel add_fsevent: kfse_list head 0x832b72c0 ; numpendingrename 1704
kernel add_fsevent: zalloc sez: 0
kernel add_fsevent: event_zone info: 4096 0x0
kernel add_fsevent: watcher 0xe57d004: num dropped 0 rd 36 wr 36 q_size 1024 flags 0x0
kernel add_fsevent: watcher 0x6d432004: num dropped 0 rd 818 wr 818 q_size 8192 flags 0xc
kernel add_fsevent: watcher 0x6d442004: num dropped 0 rd 2165 wr 2168 q_size 8192 flags 0x5
kernel add_fsevent: watcher 0x6d2ae004: num dropped 4775 rd 3739 wr 3738 q_size 4096 flags 0x1
What is going on? What is the event queue and why is it full. I'm on a fairly recent fresh install of OS X 10.6 with the latest 10.6.7 update applied. All disk permissions repaired, Disk verified, Spotlight index rebuilt.
Help please.

Yeah, I found that one. Didn't seem helpful, at least in my case.
Seems that there is some problems either with using Dropbox and having Spotlight index that directory. Whenever Dolly Drive/Time Machine starts up and calls mds for indexing, something goes screwy.
This is at least my me and a Dolly Drive tech guy figured.

ThreadpoolExecutor not creating threads unless queue is full

Hi I want to use the threadpool provided in java. i.e Threadpoolexecutor.
The requirement is:
1. I need to have a corepool size(1)
2. I need to have Maxpoolsize(40)
3. I need to have a Queue without predefined capacity. I can use a LinkedBlockingQueue for this.
But the problem is, if i construct a threadpool,
ThreadPoolExecutor threadPool = new ThreadPoolExecutor(1,40,600, TimeUnit.SECONDS,new LinkedBlockingQueue<Runnable>());
No new threads are created until the queue is full. I.e the no more than corePoolSize threads will ever be created. (And the value of the maximumPoolSize therefore doesn't have any effect.). But what i need to have is everytime a task is submitted, it should create a thread until it reaches MaxpoolSize() and then it should start Queing requests.
I know that this is a documented behaviour in javadoc. But i need to know if there is a proven workaround to do so.
Is there a way to do So.....

Please don't [double post|http://forums.sun.com/thread.jspa?threadID=5379100].

Receiver RFC Queue

Hi ,
I have configured a asyncronous scenario as JDBC> PI->RFC(JDBC sender and RFC receiver) , I have multiple JDBC sender channels but a single RFC receiver channel.
I want the RFC receiver channel to be set to EOIO, and queue name assigned to the RFC calls made by this RFC receiver channel.But I cannot find a place in the RFC receiver communication channel where I can set the Quality of service to EOIO.
Can some help me out as how to set the RFC receiver to be EOIO , I mean to queue all the RFC calls made.
Thanks for your response.
Venu

hi Michael,
I have similar requirement, scenarios is async SOAP->PI 7.0 SP15->SAP 4.6C (async RFC), as per SAP documentation RFC can be EOIO and I need to ensure messages are sent to SAP system in order also If message fails in R/3 during RFC processing, I need to stop sending next message to R/3.
Any suggestions?
regards,
sachin

"CPU Receive Multicast Queue is full"

Similar Messages

Maybe you are looking for