04-24-2013 06:29 AM
Hi people, i'm getting spammed with the following error messages on my Nexus 1000v VSM (It's running as a HA pair):
2013 Apr 24 14:14:08 Nexus-vsm %KERN-2-SYSTEM_MSG: mts_print_msg_opcode_in_
queue: opcode 55299 - 100 messages - kernel
2013 Apr 24 14:14:08 Nexus-vsm %KERN-2-SYSTEM_MSG: mts_acquire_q_space() fa
iling - no space in sap 306, uuid 405 - kernel
2013 Apr 24 14:14:08 Nexus-vsm %KERN-2-SYSTEM_MSG: mts_deliver_local_atomic
:mts_acquire_q_space failed for opcode 55299, src_sap = 2 - kernel
2013 Apr 24 14:14:12 Nexus-vsm last message repeated 59 times
2013 Apr 24 14:14:12 Nexus-vsm %KERN-2-SYSTEM_MSG: mts_do_msg_input() faili
ng since no space available in 306 (src_sap = 306, opc = 55301) - kernel
2013 Apr 24 14:14:12 Nexus-vsm %KERN-2-SYSTEM_MSG: mts_deliver_local_atomic
:mts_acquire_q_space failed for opcode 55299, src_sap = 2 - kernel
2013 Apr 24 14:14:13 Nexus-vsm %KERN-2-SYSTEM_MSG: mts_is_q_space_available
():1296: regular+fast mesg total = 27262, soft limit = 4096 - kernel
2013 Apr 24 14:14:13 Nexus-vsm %KERN-2-SYSTEM_MSG: mts_is_q_space_available
(): NO SPACE sap=306, sap_opt = 0x1, hdr_opt = 0x4, rq=27262(37273187), lq=0(0),
pq=0(0), nq=0(0), sq=0(0), fast: rq=0, lq=0, pq=0, nq=0, sq=0 - kernel
2013 Apr 24 14:14:13 Nexus-vsm %KERN-2-SYSTEM_MSG: mts_print_longest_queue_
state: opcode counts for first and last 50 messages in recv_q of sap 306: - kern
el
Haven't been able to find anything related to it on google. Can anyone help me out?
04-24-2013 06:40 AM
Always provide the software version. Then we will definitely help you.
Robert
04-24-2013 06:48 AM
Sounds good. :-)
VSM version: 4.2(1)SV1(5.1)
Host: ESXi 4.1.0 Build 348481
vCenter Server: 4.1.0 Build 345043
05-13-2013 04:32 PM
Hi Peter,
Do you have netflow on your running configuration? Seems to me that you are exporting a lot of flows from the line card on to the supervisor. Decoding this message:
Nexus-vsm %KERN-2-SYSTEM_MSG: mts_is_q_space_available
(): NO SPACE sap=306, sap_opt = 0x1, hdr_opt = 0x4, rq=27262(37273187), lq=0(0),
306 corresponds to the netflow's Service Access Point ( SAP).
rq = receive queue of netflow is saturated.
Try one of the following:
a) Increase the inactive timeout
b) Increaste the active timeout.
c) check the number of interfaces you have netflow on .( limit is 256 switch-wide)
Even with a, b and c, if you have traffic that is shortlived or voluminuous you might see this error.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: