Access Points

Reply
New Contributor
Posts: 2
Registered: ‎09-09-2010

AP-125 Mesh Portal Rebooting

I have recently configured an AP-125 to be used as a mesh portal. Before making this AP a mesh portal it was used as a standard access point with no issues. Once I configured it as a mesh portal the access point frequently reboots. This was never a problem before it was configured as a mesh portal.

As a test I reconfigured the access point as a standard access point for 24 hours. The AP functioned properly with no reboots for the 24 hours. I then reconfigured the AP as a mesh portal and the constant reboots started again. Seems to be an issue related to the access point functioning as a Mesh Portal. I have also swapped out the AP for a different brand new never used AP and get the same results when configured as a Mesh Portal.

When I look at the system status of the AP this is what I see.
Reboot Information
------------------
Reboot caused by kernel page fault at virtual address 0000000000000000, epc == a800000003e20000, ra == a800000003e20000


I am currently running an Aruba 6000 with and M3 controller. The Aruba OS version is 3.4.2.2

Here is the configuration details of the Access Point. Note the reboot and bootstrap counts.
AP "ATC-AP-102" Basic Information
---------------------------------
Item Value
---- -----
AP IP Address x.x.x.x
LMS IP Address x.x.x.x
Group Stark
Location Name N/A
Status Up; Mesh
Up time 17m:36s
Installation indoor

AP "ATC-AP-102" Hardware Information
------------------------------------
Item Value
---- -----
AP Type 125
Serial # AJ0191864
Wired MAC Address 00:24:6c:c4:dd:b0
Radio 0 BSSID 00:24:6c:cd:db:10
Radio 1 BSSID 00:24:6c:cd:db:00
Enet 1 MAC Address 00:24:6c:c4:dd:b1

AP "ATC-AP-102" Operating Information
-------------------------------------
Item Value
---- -----
AP State Running
Entry created 2010-09-15 12:39:46
Last activity 2010-09-15 13:10:33
Reboots 236
Bootstraps 242
Bootstrap Threshold 16
Slot/Port 0/0

AP "ATC-AP-102" Radio 0 Operating Information
---------------------------------------------
Item Value Source
---- ----- ------
High throughput Enabled Configuration
Mode MPP Provisioned
Band 802.11a Provisioned
Channel 161 ARM
EIRP 19 Configuration

AP "ATC-AP-102" Radio 1 Operating Information
---------------------------------------------
Item Value Source
---- ----- ------
High throughput Enabled Configuration
Mode AP Configuration
Band 802.11g
Channel 6 ARM
Secondary Channel None ARM
EIRP 18 ARM
802.11b Protection Enabled Configuration

AP "ATC-AP-102" Provisioning Parameters
---------------------------------------
Item Value
---- -----
AP Name ATC-AP-102
AP Group Stark
Location name N/A
SNMP sysLocation Hallway Outside T121
Master N/A
Gateway N/A
Netmask N/A
IP Addr N/A
DNS IP N/A
Domain Name N/A
Server Name aruba-master
Server IP N/A
Antenna gain for 802.11a N/A
Antenna gain for 802.11g N/A
Antenna for 802.11a both
Antenna for 802.11g both
PPPOE User Name N/A
PPPOE Password N/A
PPPOE Service Name N/A
USB User Name N/A
USB Password N/A
USB Device Type any
USB Device Identifier N/A
USB Dial String N/A
USB Initialization String N/A
USB TTY device path N/A
Mesh Role mesh-portal
Installation indoor
Latitude N/A
Longitude N/A
Altitude N/A
Antenna bearing for 802.11a N/A
Antenna bearing for 802.11g N/A
Antenna tilt angle for 802.11a N/A
Antenna tilt angle for 802.11g N/A
Mesh SAE sae-default


When I look at the system status of the AP this is what I see.
Reboot Information
------------------
Reboot caused by kernel page fault at virtual address 0000000000000000, epc == a800000003e20000, ra == a800000003e20000


I am currently running an Aruba 6000 with and M3 controller. The Aruba OS versions is 3.4.2.2
Guru Elite
Posts: 20,966
Registered: ‎03-29-2007

Kernel Page Fault

Kernel Page Fault is not a regular occurrence. Please contact support.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

New Contributor
Posts: 2
Registered: ‎09-09-2010

Re: AP-125 Mesh Portal Rebooting

Thanks, I opened a support call with Aruba and they where able to correct the problem. This was a known issue with the version of ArubaOS I was using. I upgraded to the latest ArubaOS version and the problem was resolved.
Search Airheads
Showing results for 
Search instead for 
Did you mean: