Wireless Access

Just upgraded 2 7220's (master/local) to 6.3.1.17 from 6.3.1.2 and our syslog server is being literally battered with the following warnings:

 

 asap_firewall_forward: bond0, insufficient headroom, require 66, but 64, skb data length 46.

 

Prob about 700mb syslog messages for the 2 controllers.

 

Things "seem" to be "ok"... but when we typically see about 4mb of log files per day.. something aint right!

 

The upgrade was somewhat forced, after I was planning to schedule it in this week, and preloaded the images to the non boot partition, and the local rebooted this morning.. for some reason, and booted into the new partition, causing an upgrade to all connected APs.  So I had to upgrade the Master this evening.  

 

Any ideas what these warnings are about??

For now, it seems to be cosmetic.  It was introduced in 6.3.1.17.  We will post here when we see what version of code the fix will be put in.

Thanks.. Ill see what I can do to supress these messages so we can actually see stuff from the 500 other devices we monitor!

Id it possible to just turn off this specific trap, as Ive had to re-enable higher level of syslog due to some issues we are having, and this error produced about 16gb of log files in less than a week!

 

 

This is targeted to be fixed in 6.3.1.19.  Unfortunately, you cannot stop syslog for specific messages.

 

...you mean whatever they turned on in .17, theyre turning back off again?!

 

Thanks again for the clarification

The condition that is causing that specific message is being fixed so that it no longer generates that message.

got that too on AP125 connected to MC3400 under 6.3.1.18 , i suddenly saw this today in CLI log on the AP125 itself.

 

anyways.. thanks for fixing this soon in 6.3.1.19

 

regards

ben

6.3.1.19 release?

---

networkforce@systex.com.tw wrote:

6.3.1.19 release?

---

It is currently expected to be around 14th November, but this is subject to change without notice.

Hi, Any updates regarding the release schedule? We'd also like to get rid of these messages, and were planning to have maintenance window this week if just possible.

No update so far.

Aparently this was fixed in 6.3.1.19 however we just upgraded one of our controllers and we are still seeing these syslog messages

 

(wireless-remote-wmc) #show ver
Aruba Operating System Software.
ArubaOS (MODEL: Aruba3400), Version 6.3.1.19
Website: http://www.arubanetworks.com
Copyright (c) 2002-2015, Aruba Networks, Inc.
Compiled on 2015-11-16 at 21:30:12 PST (build 52571) by p4build

 

(wireless-remote-wmc) #show log system 10

Jan 14 09:25:13 KERNEL(bus_gps_test@192.168.0.5): printk: 7 messages suppressed.
Jan 14 09:25:13 KERNEL(bus_gps_test@192.168.0.5): asap_firewall_forward: bond0, insufficient headroom, require 66, but 64, skb data length 160.
Jan 14 09:25:17 KERNEL(bus_4@192.168.0.4): printk: 840 messages suppressed.
Jan 14 09:25:17 KERNEL(bus_4@192.168.0.4): asap_firewall_forward: bond0, insufficient headroom, require 66, but 64, skb data length 152.
Jan 14 09:25:18 KERNEL(bus_2@192.168.0.4): printk: 527 messages suppressed.
Jan 14 09:25:18 KERNEL(bus_2@192.168.0.4): asap_firewall_forward: bond0, insufficient headroom, require 66, but 64, skb data length 1232.
Jan 14 09:25:18 KERNEL(bus_gps_test@192.168.0.5): printk: 9 messages suppressed.
Jan 14 09:25:18 KERNEL(bus_gps_test@192.168.0.5): asap_firewall_forward: bond0, insufficient headroom, require 66, but 64, skb data length 46.
Jan 14 09:25:18 KERNEL(bus_1@192.168.0.4): printk: 1244 messages suppressed.
Jan 14 09:25:18 KERNEL(bus_1@192.168.0.4): asap_firewall_forward: bond0, insufficient headroom, require 66, but 64, skb data length 1232.

Please open a TAC case so that they can examine your setup

 

We've upgraded to 6.3.1.20 which has now fixed this issue for AP65 and AP70.

Possibly.

If it was introduced in R6.3.1.17, can we use R6.3.1.16 without this issue?

 

Semih