ArubaOS and Controllers

Reply
Occasional Contributor II
Posts: 10
Registered: ‎04-12-2010

Mesh AP(mesh point) not work.

Hi all,

I am trying mesh network, use controller 800(OS is 3.4.2.0), AP125(mesh portal) and AP70)(mesh point).

I setup mesh config follow:
- setup a mesh cluster profile
- setup a mesh radio profile
- assign the mesh cluster profile to an ap-group
- assign the mesh radio profile to an ap-group
- provision an AP with the mesh role mesh portal
- provision an ap with the mesh role mesh point

I provision the AP125 to mesh portal is good, and than I provision AP70 to mesh point had a problem.

The AP70 after reboot, the mesh not work.

And I find that AP70 has been re-boot agian.
(Aruba800) #show ap active 

Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
ap-125 ap-gp-70 10.10.10.95 0 AP:HT:6/9/20.5 0 MPP+AP:HT:116+/21/21 125 AM 6h:51m:6s N/A

(Aruba800) #show ap mesh topology 

Mesh Cluster Name: aruba-mesh
-----------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
ap-125 Portal (N) - 3 0 0 0 0 - 44s 6h:53m:13s 0

Total APs :1
(R): Recovery AP. (N): 11N Enabled. For Portals 'Uplink Age' equals uptime.


Anyone got any suggestions? Thanks a lot.
Guru Elite
Posts: 21,280
Registered: ‎03-29-2007

Mesh Config

Is the AP125 and the AP70 provisioned to the same group?
I'm also assuming that you have DHCP configured and giving out addresses. Do a "show log system " to see if there are any clues there.


Colin Joseph
Aruba Customer Engineering

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

Aruba Employee
Posts: 4
Registered: ‎04-02-2007

Re: Mesh AP(mesh point) not work.

Your problem is probably because the 11n portal has selected DFS channel 116 but the AP-70 mesh point does not support that channel and so never discovers the portal. Editing the regulatory profile for your mesh network to exclude those channels not supported by the point should solve it. You may need a new group with dedicated regulatory profile for mesh if you have 11n APs that should use those channels. The allowed channels for an AP-70 in US country code (would be the same as an AP-65):

(swad_2400) (config) #show ap allowed-channels ap-name ad-65-6

Allowed Channels for AP "ad-65-6" Country Code "US"
---------------------------------------------------
PHY Type Allowed Channels
-------- ----------------
802.11g (indoor) 1 2 3 4 5 6 7 8 9 10 11
802.11a (indoor) 36 40 44 48 149 153 157 161 165
802.11g (outdoor) 1 2 3 4 5 6 7 8 9 10 11
802.11a (outdoor) 149 153 157 161 165
Occasional Contributor II
Posts: 10
Registered: ‎04-12-2010

Re: Mesh AP(mesh point) not work.

Hi Colin, Aidan

Thanks your reply.
AP125 and AP70 in the same group.
I configured static ip for ap(AP125 and AP70), and controller 800 in the same sub-network.

(Aruba800) #show log system 
Apr 14 11:13:31 :315382: |fpapps| Reboot Cause: Power Failure.
Apr 14 11:13:37 KERNEL: klogd started: BusyBox v0.60.4 (2009.12.18-19:21+0000)
Apr 14 11:13:37 KERNEL:
Apr 14 11:13:37 KERNEL: Aruba Networks Model A8xx
Apr 14 11:13:37 KERNEL: ArubaOS Version 3.4.2.0 (build 23093 / label #23093)
Apr 14 11:13:37 KERNEL: Built by p4build@stan on 2009-12-18 at 11:26:40 PST (gcc version 3.4.1)
Apr 14 11:13:37 KERNEL: Copyright (c) 2002-2009, Aruba Networks, Inc.
Apr 14 11:13:37 KERNEL: i2c-dev.o: Registered 'System I2C Interface' as minor 0
Apr 14 11:13:37 KERNEL: VFS: Disk change detected on device ide0(3,3)
Apr 14 11:13:37 :399816: |fpapps| Initializing the Line Card for Cabernet 1
Apr 14 11:13:37 :399816: |fpapps| Initializing the Cabernet STD Port Callbacks
Apr 14 11:14:46 :313078: |fpapps| XSec Vlan Interface 4095 not found line 877
Apr 14 11:14:46 :313078: |fpapps| XSec Vlan Interface 4095 not found line 877
Apr 14 11:14:46 :313256: |fpapps| Route resolve returned an Error
Apr 14 11:15:09 :325022: |authmgr| Bogus VLAN ID:4095 received.
Apr 14 11:15:36 :303022: |AP ap-m-70@10.10.10.97 nanny| Reboot Reason: No reboot message found.
Apr 14 11:22:37 :311002: |AP ap-m-70@10.10.10.97 sapd| Rebooting: SAPD: Rebooting after provisioning
Apr 14 11:22:37 :303086: |AP ap-m-70@10.10.10.97 nanny| Process Manager (nanny) shutting down - AP will reboot!
Apr 14 11:27:33 :303022: |AP 00:0b:86:c8:e0:b0@10.10.10.182 nanny| Reboot Reason: No reboot message found.
Apr 14 11:28:23 :311002: |AP 00:0b:86:c8:e0:b0@10.10.10.182 sapd| Rebooting: SAPD: Rebooting after provisioning
Apr 14 11:28:23 :303086: |AP 00:0b:86:c8:e0:b0@10.10.10.182 nanny| Process Manager (nanny) shutting down - AP will reboot!
Apr 14 11:29:08 :303022: |AP ap-m-70@10.10.10.97 nanny| Reboot Reason: AP rebooted Wed Apr 14 11:28:23 GMT 2010: SAPD: Rebooting after provisioning


And Now I have new testing.
I purge old AP70(ap-m-70), and have new another AP70.
One is ap-70(mesh portal), and ap-m-70(mesh point).

And I create new regulatory profile.

(Aruba800) #show ap regulatory-domain-profile tw-regulatory

Regulatory Domain profile "tw-regulatory"
-----------------------------------------
Parameter Value
--------- -----
Country Code TW
Valid 802.11g channel 1
Valid 802.11g channel 6
Valid 802.11g channel 11
Valid 802.11a channel 161
Valid 802.11g 40MHz channel pair 1+
Valid 802.11g 40MHz channel pair 5-
Valid 802.11g 40MHz channel pair 7+
Valid 802.11g 40MHz channel pair 11-
Valid 802.11a 40MHz channel pair 161-


The two AP70 in the same ap-group.


(Aruba800) #show ap active

Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
ap-70 ap-mesh 10.10.10.94 0 AP:1/9/21 0 MPP+AP:161/9/21 70 EM 4m:39s N/A
ap-m-70 ap-mesh 10.10.10.97 0 AP:1/15/21 0 AP:161/15/21 70 E 4m:23s N/A
ap-125 ap-gp-70 10.10.10.98 0 AP:HT:1/9/20.5 0 AP:HT:153-/19/19 125 E 4m:32s N/A


(Aruba800) #show ap-group ap-mesh

AP group "ap-mesh"
------------------
Parameter Value
--------- -----
Virtual AP ktc-vap-70
802.11a radio profile default
802.11g radio profile default
Wired AP profile wired-ap-untrust
Ethernet interface 0 link profile default
Ethernet interface 1 link profile default
AP system profile default
VoIP Call Admission Control profile default
802.11a Traffic Management profile N/A
802.11g Traffic Management profile N/A
Regulatory Domain profile tw-regulatory
RF Optimization profile default
RF Event Thresholds profile default
IDS profile ids-low-setting
Mesh Radio profile mesh-radio
Mesh Cluster profile mech-cluster priority 1


After I provision ap-m-70 to mesh point AP.
The ap-m-70 was be reboot, reboot, reboot.
Mesh point AP not work.

I can't see why it isn't working?!
Aruba Employee
Posts: 4
Registered: ‎04-02-2007

Re: Mesh AP(mesh point) not work.

Hi Clement,
You need to figure out if it's a mesh connectivity problem (mesh link not forming), or controller connectivity (link forms but point not reaching the controller). The various 'show ap mesh' CLI commands are useful for troubleshooting mesh issues:
- Does the mesh link ever form i.e. show ap mesh active (or topology) shows the point?
- If yes, what is the reason given for AP reboot ('show ap debug system-status)'?
- If no, does the mesh portal see the point (and what is cluster-id): show ap mesh neighbors
- If you have an SOE console on the point does it see the portal (and what is its cluster-id): run 'meshinfo'. Also check provisioned cluster, run 'apfcutil -r mesh0 MESH'.

/Aidan
Occasional Contributor II
Posts: 10
Registered: ‎04-12-2010

Re: Mesh AP(mesh point) not work.

Hi Aidan,

Thank you for your answer.
I change my lab.
Lab Environment:
Aruba controller 800(4.3.2.0),
mesh portal use AP70(ap-70),
mesh point use AP125(ap-m-125) and other AP70(ap-m-70).
I provision AP125 to mesh point AP, than AP125 boot ok, MESH is work.
show ap active and show ap mesh active

(Aruba800) #show ap active

Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
ap-m-125 mesh 10.10.10.95 0 AP:HT:1/15/20.5 0 MP+AP:161/15/19 125 EM 29m:19s N/A
ap-70 mesh 10.10.10.188 0 AP:6/15/20.5 0 MPP+AP:161/9/21 70 EM 2h:14m:23s N/A

Flags: R = Remote AP; P = PPPOE; E = Wired AP enabled; A = Enet1 in active/standby mode;
L = Client Balancing Enabled; D = Disconn. Extra Calls On; B = Battery Boost On;
X = Maintenance Mode; d = Drop Mcast/Bcast On; N = 802.11b protection disabled;
a = Reduce ARP packets in the air; S = RFprotect Sensor; d = Disconnected Sensor
M = Mesh; U = USB modem; K = 802.11K Enabled;

Channel followed by "*" indicates channel selected due to unsupported configured channel.

Num APs:2

(Aruba800) #show ap mesh active

Mesh Cluster Name: mesh-clusterX
--------------------------------
Name Group IP Address BSSID Band/Ch/EIRP/MaxEIRP MTU Enet 0/1 Mesh Role Parent #Children AP Type Uptime
---- ----- ---------- ----- -------------------- --- -------- --------- ------ --------- ------- ------
ap-70 mesh 10.10.10.188 00:0b:86:16:b9:d0 802.11a/161/9/21 1500 -/Tunnel Portal - 1 70 2h:6m:40s
ap-m-125 mesh 10.10.10.95 00:24:6c:c0:7e:70 802.11a/161/15/19 Tunnel/Tunnel Point ap-70 0 125 21m:36s

Total APs :2

(Aruba800) #


So...Mesh is work and good.
I change AP70(ap-m-70) assign to the mesh group and assign the mesh point role
But the AP70 not work. The AP70 still reboot than reboot, reboot, reboot.

I don't know why AP70(ap-m-70) not work?!

But at user site still use AP70!!

Clement
Search Airheads
Showing results for 
Search instead for 
Did you mean: