Wireless Access

Anyone ever see this kind of message before?

When do you see this message, at bootup?

I'm getting the same errors on a local controllers.  It's a 6000 series running 5.0.4.5.  Output of part of the post below.  Also, might be unrelated, but we are having issues with the SFP slots not always coming back up on reboot.  

Apr 20 10:24:01 KERNEL: 2:Enabling all XGS ports now....
Apr 20 10:24:01 KERNEL: 5:Slot 2 has an SC/NEB type 0x4
Apr 20 10:24:01 KERNEL: 5:Slot 3 has an SC/NEB type 0x4
Apr 20 10:24:01 KERNEL: 7:<4>process `soed' is using obsolete setsockopt SO_BSDCOMPAT
Apr 20 10:24:03 :399801: <ERRS> |fpapps| An internal system error has occurred at file dapi.c function dapiCtl line 335.
Apr 20 10:24:05 :399801: <ERRS> |fpapps| An internal system error has occurred at file dapi.c function dapiCtl line 335.
Apr 20 10:24:05 :399801: <ERRS> |fpapps| An internal system error has occurred at file dapi.c function dapiCtl line 335.
Apr 20 10:24:08 KERNEL: 4:Slot 2 has an SC/NEB type 0x4
Apr 20 10:24:08 KERNEL: 4:Slot 3 has an SC/NEB type 0x4
Apr 20 10:24:09 :313404: <ERRS> |fpapps| Error Setting the port speed for interface 11
Apr 20 10:24:10 :313404: <ERRS> |fpapps| Error Setting the port speed for interface 12
Apr 20 10:24:21 :313078: <ERRS> |fpapps| XSec Vlan Interface 981 not found line 877
Apr 20 10:24:21 :313078: <ERRS> |fpapps| XSec Vlan Interface 981 not found line 877
Apr 20 10:24:22 :313256: <WARN> |fpapps| Route resolve returned an Error
Apr 20 10:24:38 :399816: <ERRS> |ike| Vlan 981 is not configured yet
Apr 20 10:25:03 KERNEL: 4:Slot 2 has an SC/NEB type 0x4
Apr 20 10:25:03 KERNEL: 4:Slot 3 has an SC/NEB type 0x4
Apr 20 10:25:20 :399816: <ERRS> |ike| Vlan 981 is not configured yet
Apr 20 10:25:20 :306510: <WARN> |publisher| Dropping message from 8214 for service 'aaa-idle-user-timeout (service not found)'
Apr 20 10:25:22 KERNEL: 1:<4>process `snmpd' is using obsolete setsockopt SO_BSDCOMPAT
Apr 20 10:25:30 KERNEL: 2:<4>process `trapd' is using obsolete setsockopt SO_BSDCOMPAT
Apr 20 10:26:03 :306514: <ERRS> |publisher| Pubsub send message code 0 source port 8378 to destination port 8345 failed, errno Connection timed out

(Aruba6000_1) #show  switchinfo
Hostname is Aruba6000_1


Ettinger Datacenter
System Time:Mon Apr 30 09:21:19 EDT 2012

Aruba Operating System Software.
ArubaOS (MODEL: Aruba6000-US), Version 5.0.4.5
Website: http://www.arubanetworks.com
Copyright (c) 2002-2012, Aruba Networks, Inc.
Compiled on 2012-02-18 at 17:56:01 PST (build 32431) by p4build

ROM: System Bootstrap, Version CPBoot 1.2.0.0 (build 20527)
Built: 2009-01-20 18:56:10
Built by: p4build@re_client_20527


Switch uptime is 54 days 14 hours 49 minutes 16 seconds
Reboot Cause: User reboot.
Supervisor Card
Processor XLR 732 (revision B2) with 2017M bytes of memory.
32K bytes of non-volatile configuration memory.
512M bytes of Supervisor Card System flash (model=CF 512MB).

Config File: default.cfg

Boot Partition: PARTITION 1


mgmt is administratively down line protocol is down
Hardware is Ethernet, address is 00:0B:86:61:02:A2



VLAN1 is up line protocol is up
Hardware is CPU Interface, Interface address is 00:0B:86:0B:9E:A0 (bia 00:0B:86:0B:9E:A0)
Description: 802.1Q VLAN
Internet address is 172.16.0.254  255.255.255.0
Routing interface is enable, Forwarding mode is enable
Directed broadcast is disabled, BCMC Optimization disabled ProxyARP disabled
Encapsulation 802, loopback not set
MTU 1500 bytes
Last clearing of "show interface" counters 54 day 14 hr 49 min 16 sec
link status last changed 54 day 14 hr 45 min 53 sec


switchrole:master
Configuration Changed since last save
No crash information available.
Reboot Cause: User reboot.

-----

(Aruba6000_1) #show log system all | include KERNEL
Mar 26 12:33:06  KERNEL: 2:Slot 2 has an SC/NEB type 0x4
Mar 26 12:33:06  KERNEL: 2:Slot 3 has an SC/NEB type 0x4
Mar 26 12:33:07  KERNEL: 2:Slot 2 has an SC/NEB type 0x4
Mar 26 12:33:07  KERNEL: 2:Slot 3 has an SC/NEB type 0x4
Mar 26 16:13:44  KERNEL: 2:Slot 2 has an SC/NEB type 0x4
Mar 26 16:13:44  KERNEL: 2:Slot 3 has an SC/NEB type 0x4
Mar 26 16:13:45  KERNEL: 2:Slot 2 has an SC/NEB type 0x4
Mar 26 16:13:45  KERNEL: 2:Slot 3 has an SC/NEB type 0x4
Apr 12 14:21:01  KERNEL: 2:Slot 2 has an SC/NEB type 0x4
Apr 12 14:21:01  KERNEL: 2:Slot 3 has an SC/NEB type 0x4
Apr 12 14:21:02  KERNEL: 4:Slot 2 has an SC/NEB type 0x4
Apr 12 14:21:02  KERNEL: 4:Slot 3 has an SC/NEB type 0x4
Apr 13 11:16:36  KERNEL: 3:Slot 2 has an SC/NEB type 0x4
Apr 13 11:16:36  KERNEL: 3:Slot 3 has an SC/NEB type 0x4
Apr 13 11:16:37  KERNEL: 3:Slot 2 has an SC/NEB type 0x4
Apr 13 11:16:37  KERNEL: 3:Slot 3 has an SC/NEB type 0x4
Apr 17 14:28:08  KERNEL: 2:Slot 2 has an SC/NEB type 0x4
Apr 17 14:28:08  KERNEL: 2:Slot 3 has an SC/NEB type 0x4
Apr 17 14:28:08  KERNEL: 2:Slot 2 has an SC/NEB type 0x4
Apr 17 14:28:08  KERNEL: 2:Slot 3 has an SC/NEB type 0x4

Can you power down the chassis and reseat the M3?

Not at this time - it's currently in production. I can do it in the summer college break. That was from our master controller. I just checked the logs on the local controller and found the following KERNEL messages.  Would you be able to shed some light as to what is causing these?

(Aruba6000_2) #show log all | include KERNEL
Apr 29 03:00:05  KERNEL(2251 Liberty - 00:24:6c:ca:a8:31@192.168.41.60): vap aruba103 vlan is 0. discovering tunnel vlan
Apr 29 06:05:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: cfg_2: 0x3ff
Apr 29 06:05:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: cfg_3: 0x18001ff
Apr 29 06:05:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: cfg_4: 0xffff
Apr 29 06:05:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: cfg_5: 0x27ffef
Apr 29 06:05:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: done cfg2 0x7114 ifctl 0x10000 miictrl 0x12
Apr 29 06:05:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: pll reg 0x18050010: 0x1099  AG7100: cfg_1: 0x1ff0000
Apr 29 06:05:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: unit 0 phy is up...RGMii 100Mbps half duplex
Apr 29 06:05:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): VSC8601: unit 0  phy_addr 1
Apr 29 11:33:06  KERNEL(23rd and Liberty Mesh Point - d8:c7:c8:c3:4e:8e@(none)): eth1: 100Mbs Full duplex, port  0, queue  0
Apr 29 11:44:15  KERNEL(2251 Liberty - 00:24:6c:ca:a8:31@192.168.41.60): vap aruba103 vlan is 0. discovering tunnel vlan
Apr 29 19:38:12  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: cfg_2: 0x3ff
Apr 29 19:38:12  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: cfg_3: 0x18001ff
Apr 29 19:38:12  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: cfg_4: 0xffff
Apr 29 19:38:12  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: cfg_5: 0x7ffef
Apr 29 19:38:12  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: done cfg2 0x7115 ifctl 0x10000 miictrl 0x12
Apr 29 19:38:12  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: pll reg 0x18050010: 0x1099  AG7100: cfg_1: 0x1ff0000
Apr 29 19:38:12  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: unit 0 phy is up...RGMii 100Mbps full duplex
Apr 29 20:06:45  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: cfg_2: 0x3ff
Apr 29 20:06:45  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: cfg_3: 0x18001ff
Apr 29 20:06:45  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: cfg_4: 0xffff
Apr 29 20:06:45  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: cfg_5: 0x7ffef
Apr 29 20:06:45  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: done cfg2 0x7115 ifctl 0x10000 miictrl 0x12
Apr 29 20:06:45  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: pll reg 0x18050010: 0x1099  AG7100: cfg_1: 0x1ff0000
Apr 29 20:06:45  KERNEL(2152 Chew St - 00:24:6c:ca:a6:b3@192.168.40.40): AG7100: unit 0 phy is up...RGMii 100Mbps full duplex
Apr 30 06:03:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: cfg_2: 0x3ff
Apr 30 06:03:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: cfg_3: 0x18001ff
Apr 30 06:03:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: cfg_4: 0xffff
Apr 30 06:03:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: cfg_5: 0x27ffef
Apr 30 06:03:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: done cfg2 0x7114 ifctl 0x10000 miictrl 0x12
Apr 30 06:03:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: pll reg 0x18050010: 0x1099  AG7100: cfg_1: 0x1ff0000
Apr 30 06:03:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): AG7100: unit 0 phy is up...RGMii 100Mbps half duplex
Apr 30 06:03:22  KERNEL(Chapel Outdoor AP - 00:24:6c:cd:8a:0e@192.168.147.171): VSC8601: unit 0  phy_addr 1

The "Chapel Outdoor AP" looks like it powered on around 6:00 AM both 4/29 and 4/30.  Is that normal?  Does it only get powered on during the day?

The other messages are due to the APs rebooting.

What version of code are you running?

Do "show ap debug system-status ap-name "2152 Chew St"" and see why the ap is rebooting and if there is crash info available.  

It also looks like APs are boostrapping (23rd and liberty mesh point and 2251 liberty).  Do the "show ap debug system-status ap-name xxx" for those as well to see why they bootstrapped (if they did).

I would open a TAC case on any AP that has crashed or consistently bootstraps.  There may be fixes available in ArubaOS or network changes that can help.

The Chapel Outdoor AP is on all the time so I'm not sure what caused it to lose power.

Chapel uptime is 17 weeks, 23 hours, 1 minute
System returned to ROM by power-on
System restarted at 15:18:41 UTC Mon Jan 2 2012
System image file is "flash:c2950-i6q4l2-mz.121-22.EA14.bin"

We are running 5.0.4.5.

(Aruba6000_1) #show ap debug system-status ap-name "2251 Liberty - 00:24:6c:ca:a8:31"

Reboot Information
------------------
AP rebooted Fri Dec 31 16:04:08 PST 1999: SAPD: Unable to contact switch. Called by sapd_hello_cb:4
---------------------------------------------------------------------------------------------------

Rebootstrap Information
-----------------------
Date       Time     Reason (Latest 10)
--------------------------------------
2012-04-20 23:17:08 Switching to LMS 192.168.240.33 (sapd_check_hbt)
2012-04-20 23:28:02 Switching to primary LMS 192.168.240.31
2012-04-23 07:58:19 Switching to LMS 192.168.240.33 (sapd_check_hbt)
2012-04-23 08:09:41 Switching to primary LMS 192.168.240.31
2012-04-25 23:01:17 Switching to LMS 192.168.240.33 (sapd_check_hbt)
2012-04-25 23:12:36 Switching to primary LMS 192.168.240.31
2012-04-29 02:48:24 Switching to LMS 192.168.240.33 (sapd_check_hbt)
2012-04-29 02:59:43 Switching to primary LMS 192.168.240.31
2012-04-29 11:32:42 Switching to LMS 192.168.240.33 (sapd_check_hbt)
2012-04-29 11:43:52 Switching to primary LMS 192.168.240.31


Rebootstrap LMS
---------------
(none found)
------------

Crash Information
-----------------
(none found)
------------

I have a TAC case on the mesh point and at this point they are thinking it's a bug of some sort.

Thanks for your help.