ArubaOS and Controllers

Reply
New Contributor
Posts: 2
Registered: ‎05-22-2009

WLAN Disappeared after upgrade

We upgraded to 3.4.0.2 this morning from 3.3.2.11.
We are missing our visitor or guest WLAN and the only alert I have is that VLAN 25 does not exist. Of course this SSID for our guest is built on this vlan. So my assumption is that it is the failure of the VLAN configuration that is causing the vistor SSID to not work.

The VLAN appears to be configured properly:
.
.
.
vlan 25 "Internet-Guest-Inside"
.
.
.
interface vlan 25
ip address 172.16.225.1 255.255.255.0
ip nat inside
operstate up
description "SCI vistors Inside Network"
.
.
.
ip dhcp excluded-address 172.16.225.1 172.16.225.10
.
.
.
ip dhcp pool scivisitor-pool
default-router 172.16.225.1
dns-server 192.168.1.36
domain-name stanleygroup.com
lease 1 0 0
network 172.16.225.0 255.255.255.0
authoritative
!
service dhcp
.
.
.
aaa profile "stanley-public-aaa"
initial-role "stanley-cp-logon"
radius-accounting "public-cp-auth"
.
.
.
wlan ssid-profile "stanley-public-ssid"
essid "SCIVISITOR"
max-clients 30
ht-ssid-profile "HIGHTHRUON"
.
.
.
wlan virtual-ap "stanley-public-vap"
aaa-profile "stanley-public-aaa"
ssid-profile "stanley-public-ssid"
vlan 25
dos-prevention
rap-operation persistent
broadcast-filter arp
.
.
.

The log information leads me to believe there is some kind of failure which causes the VLAN to not be created and cascades to the SSID.

Aug 18 10:55:44 fpapps: <315382> |fpapps| Reboot Cause: User reboot.
Aug 18 10:55:56 nanny: PAPI_Send: To: 7f000001:8407 Type:0x4 Timed out.
Aug 18 10:55:56 nanny: PAPI_Send: To: 7f000001:8407 Type:0x4 Timed out.
Aug 18 10:56:02 mobileip: PAPI_Send: To: 7f000001:8226 Type:0x4 Timed out.
Aug 18 10:56:02 mobileip: PAPI_Send: To: 7f000001:8226 Type:0x4 Timed out.
Aug 18 10:56:05 snmp: PAPI_Send: To: 7f000001:8212 Type:0x4 Timed out.
Aug 18 10:56:05 snmp: PAPI_Send: To: 7f000001:8212 Type:0x4 Timed out.
Aug 18 10:56:05 snmp: PAPI_Send: To: 7f000001:8212 Type:0x4 Timed out.
Aug 18 10:56:05 snmp: PAPI_Send: To: 7f000001:8212 Type:0x4 Timed out.
Aug 18 10:56:08 cli: PAPI_Send: To: 7f000001:8372 Type:0x4 Timed out.
Aug 18 10:56:08 fpapps: <313078> |fpapps| XSec Vlan Interface 4095 not found line 877
Aug 18 10:56:08 fpapps: <313078> |fpapps| XSec Vlan Interface 4095 not found line 877
Aug 18 10:56:08 nanny: PAPI_Send: To: 7f000001:8407 Type:0x4 Timed out.
Aug 18 10:56:08 nanny: PAPI_Send: To: 7f000001:8407 Type:0x4 Timed out.
Aug 18 10:56:10 httpd: PAPI_Send: To: 7f000001:8214 Type:0x4 Timed out.
Aug 18 10:56:10 httpd: PAPI_Send: To: 7f000001:8214 Type:0x4 Timed out.
Aug 18 10:56:13 authmgr: PAPI RxPacket: ACK to invalid packet type 0x00000043
Aug 18 10:56:13 authmgr: PAPI RxPacket: ACK to invalid packet type 0x00000043
Aug 18 10:56:13 cfgm: <399801> |cfgm| An internal system error has occurred at file sapi.c function sapi_rsp line 247.
Aug 18 10:56:13 cfgm: <399801> |cfgm| An internal system error has occurred at file sapi.c function sapi_rsp line 247.
Aug 18 10:56:13 pim: <399801> |pim| An internal system error has occurred at file sapi.c function sapi_rsp line 247.
Aug 18 10:56:13 pim: <399801> |pim| An internal system error has occurred at file sapi.c function sapi_rsp line 247.
Aug 18 10:56:17 cli: PAPI_Send: To: 7f000001:8372 Type:0x4 Timed out.
Aug 18 10:56:21 ads: PAPI_Send: To: 7f000001:8214 Type:0x4 Timed out.
Aug 18 10:56:21 ads: PAPI_Send: To: 7f000001:8214 Type:0x4 Timed out.
Aug 18 10:56:23 snmp: LargeReplyTimeout: TIMEOUT
Aug 18 10:56:23 snmp: LargeReplyTimeout: TIMEOUT
Aug 18 10:56:23 snmp: PAPI_SendWaitForLargeReply: No response from 7f000001:8226
Aug 18 10:56:23 snmp: PAPI_SendWaitForLargeReply: No response from 7f000001:8226
Aug 18 10:56:25 authmgr: <325022> |authmgr| Bogus VLAN ID:4095 received.
Aug 18 10:56:25 snmp: IP addr 0xa01becc port 0
Aug 18 10:56:25 snmp: trapSrcIp 0x0
Aug 18 10:56:27 l2tp: <142005> |l2tp| Unable to make named pipe server sock async
Aug 18 10:56:35 stm: <304001> |stm| Unexpected stm (Station managment) runtime error at data_path_handler, 571, data_path_handler: recv - Network is down
Aug 18 10:56:42 stm: <305004> |stm| AP HER-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:56:43 stm: <305004> |stm| AP LAU-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:56:43 stm: <305004> |stm| AP STA-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:56:44 stm: <305004> |stm| AP LAU-AP02: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:56:44 stm: <305004> |stm| AP STA-AP02: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:56:51 nanny: <303079> |AP LAU-AP01@172.21.21.2 nanny| Restarted process /sbin/syslogd, new pid 315
Aug 18 10:56:52 nanny: <303079> |AP LAU-AP02@172.21.21.4 nanny| Restarted process /sbin/syslogd, new pid 315
Aug 18 10:57:00 stm: <305004> |stm| AP STL-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:02 stm: <305004> |stm| AP DSM-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:11 nanny: <303079> |AP DSM-AP01@172.21.21.7 nanny| Restarted process /sbin/syslogd, new pid 275
Aug 18 10:57:27 stm: <305004> |stm| AP DNV-AP03: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:29 nanny: <303079> |AP DNV-AP03@172.21.21.8 nanny| Restarted process /sbin/syslogd, new pid 321
Aug 18 10:57:31 stm: <305004> |stm| AP MNP-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:37 stm: <305004> |stm| AP SLC-AP02: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:41 stm: <305004> |stm| AP DNV-AP05: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:44 localdb: <133006> |localdb| User 00:1b:77:c2:28:8a Failed Authentication
Aug 18 10:57:44 localdb: <133019> |localdb| User 00:1b:77:c2:28:8a was not found in the database
Aug 18 10:57:50 stm: <305004> |stm| AP SJN-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:51 authmgr: <132030> |authmgr| Dropping EAPOL packet sent by Station 00:1b:77:ad:51:de 00:1a:1e:90:86:01
Aug 18 10:57:51 stm: <305004> |stm| AP PHX-AP02: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:53 stm: <305004> |stm| AP WPB-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:55 stm: <305004> |stm| AP CHG-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:57 stm: <305004> |stm| AP BSE-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:57:57 stm: <305004> |stm| AP MNP-AP02: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:58:00 nanny: <303079> |AP PHX-AP02@172.21.21.13 nanny| Restarted process /sbin/syslogd, new pid 321
Aug 18 10:58:01 stm: <305004> |stm| AP BTR-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:58:01 stm: <305004> |stm| AP NPL-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:58:02 stm: <305004> |stm| AP DNV-AP04: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:58:03 stm: <305004> |stm| AP SLC-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:58:04 nanny: <303079> |AP CHG-AP01@172.21.21.15 nanny| Restarted process /sbin/syslogd, new pid 321
Aug 18 10:58:04 stm: <305004> |stm| AP DNV-AP02: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:58:07 stm: <305004> |stm| AP PHX-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:58:08 nanny: <303079> |AP BTR-AP01@172.21.21.18 nanny| Restarted process /sbin/syslogd, new pid 320
Aug 18 10:58:08 nanny: <303079> |AP BSE-AP01@172.21.21.16 nanny| Restarted process /sbin/syslogd, new pid 321
Aug 18 10:58:10 nanny: <303079> |AP SLC-AP01@172.21.21.21 nanny| Restarted process /sbin/syslogd, new pid 321
Aug 18 10:58:10 stm: <305004> |stm| AP DNV-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Aug 18 10:58:11 nanny: <303079> |AP NPL-AP01@172.21.21.19 nanny| Restarted process /sbin/syslogd, new pid 339
Aug 18 10:58:12 stm: <305004> |stm| AP ICY-AP01: wlan virtual-ap "stanley-public-vap" is invalid.
Moderator
Posts: 243
Registered: ‎09-12-2007

Re: WLAN Disappeared after upgrade

First, greetings from a former Iowa resident. :)

I don't think it's the VLAN. The log messages you are seeing refer to VLAN 4095 - I think it's an error message related to some internal use of that VLAN, probably for xSec.

However the APs appear to be replying that the VAP configuration is invalid. Did you post the entire WLAN set of profiles, or just snippets? For example, I notice there's no opmode setting for the SSID profile - not sure if it's really missing, or if you just didn't paste it.

In my experience, the biggest reason APs reject a config is because of VLAN (seems ruled out here, especially if "show vlan" and "show ip interface brief" seem normal) or regulatory settings - someone tries to hardcode a channel setting on an AP when the regulatory domain profile prohibits it.. I believe you can look at "show ap debug" or "show ap config" to get the AP to spit out what it doesn't like, but unfortunately I'm the marketing guy now and couldn't tell you the exact command anymore.

Might want to just open a TAC case.. it might be easier. :)
---
Jon Green, ACMX, CISSP
Security Guy
New Contributor
Posts: 2
Registered: ‎05-22-2009

Support Resolved the issue

Thanks jgreen for the response. Yes those were just snippets of the config.

Here is how it got resolved. . After a lot of poking around on the system, we ultimately assigned the virtual-ap to VLAN 1. This made it happy and it loaded and all the APs worked. Of course now they were all in the wrong VLAN. Then without changing the VLAN configuration we assigned the virtual-ap to VLAN 25, booted the controller, and walla! they were all using VLAN 25 now, no problem. It is like the association between the virtual-ap and the VLAN database, or some such, had become corrupt and all it required was a reassociation. So all is good now.
Search Airheads
Showing results for 
Search instead for 
Did you mean: