ArubaOS and Controllers

Reply
Occasional Contributor I
Posts: 8
Registered: ‎05-02-2011

AOS-W 5.0.3.2 clients are not filtered properly using essid

Hi,
I have an Alcatel 6000 controller with AOS-W 5.0.3.2 on it. When I try to use WLAN section on the monitoring page in Web UI, and try to list clients. It does not return any or it returns an incorrect list. Is Anybody having such problem? By the way, I installed and tried 6.0.1.2 and 6.0.1.0 respectively before 5.0.3.2, and controller had reloads with datapath and watchdog timeouts reasons. We have 400+ AP61 with an M3 card, using captive portal both with wired and wireless profiles. If it is not the case with the software I guess I am going to reload sometime.
Guru Elite
Posts: 21,279
Registered: ‎03-29-2007

Re: AOS-W 5.0.3.2 clients are not filtered properly using essid

For the display issue, I would clear my browser cache.

For the datapath reboots, please contact support ASAP.


Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor I
Posts: 8
Registered: ‎05-02-2011

Re: AOS-W 5.0.3.2 clients are not filtered properly using essid

oh my bad I forgot the include, it is the same with console command.

(AWAC) #show user-table essid 3_Kuzey_Yurt

Users
-----
IP MAC Name Role Age(d:h:m) Auth VPN link AP name Roaming Essid/Bssid/Phy Profile Forward mode
---------- ------------ ------ ---- ---------- ---- -------- ------- ------- --------------- ------- ------------
192.168.0.1 00:24:2c:0a:09:e4 authenticated 00:09:56 00:24:6c:c1:79:de Wireless Boun-Wlan-N/00:24:6c:97:9d:e0/g YolGecenHan tunnel
192.168.1.33 00:22:fa:72:09:00 authenticated 00:02:53 N/A Wireless Boun-Wlan-N/00:24:6c:97:88:60/g YolGecenHan tunnel
193.140.192.20 00:1f:3b:9f:20:1b cap-guest-logon 01:06:23 N/A Wireless 4_Kuzey_Yurt/00:24:6c:f4:06:f0/g cap-aaa-profile tunnel
192.168.1.1 00:1c:a8:19:27:2c 001ca819272c cap-guest-logon 02:03:46 tunnel 1 Wired cap-aaa-profile tunnel
192.168.1.2 00:25:d3:01:56:b1 authenticated 00:05:57 N/A Wireless Boun-Wlan-S/00:24:6c:96:f3:d0/g YolGecenHan tunnel
193.140.192.50 00:1f:3b:9f:20:1b cap-guest-logon 01:06:23 N/A Wireless 4_Kuzey_Yurt/00:24:6c:f4:06:f0/g cap-aaa-profile tunnel
192.168.1.103 1c:65:9d:3e:71:78 1c659d3e7178 cap-guest-logon 02:01:31 tunnel 1 Wired cap-aaa-profile tunnel
192.168.2.2 00:23:4d:e3:fe:b2 authenticated 01:01:43 N/A Wireless Boun-Wlan-N/00:24:6c:97:9d:e0/g YolGecenHan tunnel
192.168.2.3 00:1a:73:3b:18:39 authenticated 00:04:19 N/A Wireless boun_guest/00:24:6c:97:8f:50/g YolGecenHan tunnel
192.168.164.134 c4:46:19:7a:e6:15 authenticated 00:00:01 00:24:6c:c1:6f:7a Wireless Kilyos_Guney_yurt/00:24:6c:96:f7:a0/g YolGecenHan tunnel
192.168.164.147 00:0d:f0:39:30:85 authenticated 00:00:30 00:24:6c:c1:6f:7a Wireless Kilyos_Guney_yurt/00:24:6c:96:f7:a0/g YolGecenHan tunnel
192.168.100.202 00:22:fa:2e:83:b2 seyhan.aktas authenticated 00:07:35 Web 00:24:6c:c1:70:3c Wireless 1_Kiz_Yurdu/00:24:6c:97:03:c0/g cap-aaa-profile tunnel
192.168.164.40 f0:7b:cb:47:01:be authenticated 00:05:01 00:24:6c:c1:78:e1 Wireless Kilyos_Guney_yurt/00:24:6c:97:8e:10/g YolGecenHan tunnel
192.168.100.40 70:1a:04:da:3d:b9 yesim.olcer authenticated 00:00:43 Web 00:24:6c:c1:6f:e9 Wireless 1_Kiz_Yurdu/00:24:6c:96:fe:90/g cap-aaa-profile tunnel
192.168.100.41 00:22:5f:04:3f:d4 ece.mendi authenticated 00:06:15 Web 00:24:6c:c1:6f:e9 Wireless 1_Kiz_Yurdu/00:24:6c:96:fe:90/g cap-aaa-profile tunnel
192.168.100.43 00:15:af:ce:50:68 duygu.koyden authenticated 00:02:54 Web 00:24:6c:c1:7a:20 Wireless 1_Kiz_Yurdu/00:24:6c:97:a2:00/g cap-aaa-profile tunnel
192.168.164.44 e0:91:53:1c:46:06 authenticated 00:04:55 00:24:6c:c1:79:44 Wireless Kilyos_Guney_yurt/00:24:6c:97:94:40/g YolGecenHan tunnel
192.168.164.45 70:1a:04:7c:4b:21 authenticated 00:04:55 00:24:6c:c1:7a:40 Wireless Kilyos_Guney_yurt/00:24:6c:97:a4:00/g YolGecenHan tunnel
192.168.100.46 00:24:2b:9a:6a:f4 dilek.calik authenticated 00:01:17 Web 00:24:6c:c1:7a:26 Wireless 1_Kiz_Yurdu/00:24:6c:97:a2:60/g cap-aaa-profile tunnel
Guru Elite
Posts: 21,279
Registered: ‎03-29-2007

Re: AOS-W 5.0.3.2 clients are not filtered properly using essid

Is that your only controller in your network? What did you upgrade from, initially?


Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor I
Posts: 8
Registered: ‎05-02-2011

Re: AOS-W 5.0.3.2 clients are not filtered properly using essid

yes it is the only one. we upgraded because we purchased pefng licenses, which were not compatible with 3.x.
Guru Elite
Posts: 21,279
Registered: ‎03-29-2007

Re: AOS-W 5.0.3.2 clients are not filtered properly using essid

Do you have the backup flash from before you upgraded that you can go back to? If not, do a "backup flash" right now.

After that do a wms reinit-db and then reboot, because the database structure is different and that might be causing your issue.


Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor I
Posts: 8
Registered: ‎05-02-2011

Re: AOS-W 5.0.3.2 clients are not filtered properly using essid

sorry for the late response, I wms re-init ed and rebooted. It did not solved the issue.
Guru Elite
Posts: 21,279
Registered: ‎03-29-2007

Re: AOS-W 5.0.3.2 clients are not filtered properly using essid

You need to open a support case, because something else is going on...


Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor I
Posts: 8
Registered: ‎05-02-2011

Re: AOS-W 5.0.3.2 clients are not filtered properly using essid

thanks, I will do as soon as possible.
Search Airheads
Showing results for 
Search instead for 
Did you mean: