topic MSM750 -wierd behaviour in M and MSM Series

MSM750 -wierd behaviour

Trevor Commulynx — Fri, 06 Nov 2009 21:23:53 GMT

Hi All,

I have a MSM750 (5.2.4.0-01-6771) with 50x MSM422's. I have deployed the AP's based on survey, checked and triple checked channel seclection, interferance and adjusted the cell size based on analisys. I have some grey areas where I am going to add more AP's due to environmental changes post survey and deployment.

I have 4x SSID's running on both radios- Radio 1 is runningA/N and Radio 2 B/G- both internal Antennas. SSID's- 2x run 802.1x and 2x run WPA2. I have rolled out 250 new notebooks with Intel N based cards (toshiba & HP) all drivers are updated etc.

I have one major problem. when users are working, they are connected at 802.11N and are working fine but then the client machines start locking up. when you turn off the wifi card they come good again. when you turn on the card, the user can keep working for an 1hr a day or just 5 minutes and then the lock up happens. Also, some notebooks are connecting at G speeds whens directly under the AP's even though I have adjusted power and wireless rates to force connectifyt to the closest AP.

All the AP's and controllers are in 1G switch ports, I have a very stable and large backbone throughout the campus on procurve 5406zl's.

Anyone seen this before? I also get this error in my MSM750 logs. This happens on servers that are teamed talking to the MSM750- DNS, Radius etc.

"Syslog severity trap for msg #30056 severity 5: user - iprulesmgr: Station Table Entry (id='6',ip-address='192.168.22.3',mac-address='00:04:23:E1:67:F4',virtual-ap-index='1') exists with the IP address claimed by the new station (mac-address='00:15:17:10:FE:E4'), for security reason we're terminating both stations"

Also, the AP's handle the offload onto the wired network once the Wireless client is authenticated.

Trev.

Re: MSM750 -wierd behaviour

Shadow13 — Sat, 07 Nov 2009 05:28:55 GMT

Hi,

I don't know much about MSM products, but what i understand from the log you posted that there is an IP address error, make sure you exclude the APs IP addresses from the DHCP pool you configured and double check if a device has configured a static IP address or something.

Regards.

Re: MSM750 -wierd behaviour

Sietze Reitsma — Sat, 07 Nov 2009 11:01:24 GMT

hello,

ask support or download the latest software version 5.3.3 (sw supportpack needed). In earlier releases radio's can disconnect or response slow in environments with interference. Maybe it does not solve your problems, but from a support perspective you can exclude radio driver problems.

I don't know what causes the duplicate IP adresses, but it seams to be another issue.

Re: MSM750 -wierd behaviour

Trevor Commulynx — Sat, 07 Nov 2009 23:10:24 GMT

Thanks Guys for the reposnes. I dont Have DHCP running on the MSM controller. the .22.3 address is the main DNS and DHCP server for AD + Radius. it runs a teamed nic.

I will update the firmware, just need to purchase the right support contract.

Trev.

Re: MSM750 -wierd behaviour

tpereirahpts — Mon, 15 Mar 2010 11:42:05 GMT

Hi Trev,

I'm experiencing the same problem as you had. Can you tell me if you find any resolution? Or you just ignore the messages?

Re: MSM750 -wierd behaviour

Trevor Commulynx — Mon, 15 Mar 2010 18:46:40 GMT

you can ignore the messages. I still havent solved the lock ups, although upgrading to windows 7 has stabalised it.

Re: MSM750 -wierd behaviour

Matt Marcos — Mon, 02 Aug 2010 04:25:39 GMT

We have pure N going with dynamic power controll. Found this last setting to cause problems with the same symptopms as you describe. Once we turned of dynamic power it became very stable.

Cheers,

Matt

Re: MSM750 -wierd behaviour

inayath_1 — Wed, 03 Nov 2010 06:39:10 GMT

HI Mat,
I am also facing the same issue with the latest firmware on msm (5.4.1) kindly let me know what to disable?
Thanks in advance.

Re: MSM750 -wierd behaviour

Matt Marcos — Wed, 03 Nov 2010 06:46:54 GMT

Login to the controller. go to CONTROLLED AP's on the left menu. Now on the right side of the page goto CONFIGURATION then RADIO LIST. Click on the model AP you are configuring (my case was MSM422). For each radio (if you have dual radio APs) go down to ADVANCED WIRELESS SETTINGS. Untick AUTOMATIc POWEr CONTROL.

I use these settings for pure 5GHZ N

Guard interval : Long
Distance between aps: Small
Max avail output power = TICKED

Everything else default in this area of the config.

Hope this helps.

cheers,

Matt.

Re: MSM750 -wierd behaviour

inayath_1 — Wed, 03 Nov 2010 07:04:15 GMT

Hi Mat,
Thanks for the update.
My setup is like this:
unfiltered log frim version 5.4.1
Sep 28 19:25:06 crit iprulesmgr assert: iprulesmgr.c
GetVirtualAPIndexFromAssociationTableUsingMAC 10497 (memcmp(emptyMAC, aMACAddress, ETH_ALEN) != 0).
Sep 28 19:25:06 debug iprulesmgr There is no association information
for this station (mac-address='00:00:00:00:00:00') therefore the configuration of the VSC #1 will be applied.
Sep 28 19:25:06 warning iprulesmgr Station Table Entry
(id='0',ip-address='192.168.2.33',mac-address='00:19:E7:05:97:43',virtual-ap-index='1')
exists with the IP address claimed by the new station (mac-address='00:00:00:00:00:00'), for security reason we're terminating both station access.
Sep 28 19:25:06 debug iprulesmgr Removed Station Table Entry
(id='0',ip-address='192.168.2.33',mac-address='00:19:E7:05:97:43',virtual-ap-index='1')
as another station have been detected to be using this IP Address.
Sep 28 19:25:06 debug iprulesmgr Added Station Table Entry
(id='0',ip-address='192.168.2.33',mac-address='00:00:00:00:00:00',virtual-ap-index='1').
Sep 28 19:25:06 debug iprulesmgr Disabling Client Station Polling
mechanism as user (nas-port='1',ip-address='192.168.2.33') has no known MAC address (probably hidden through a router).
Sep 28 19:25:06 debug iprulesmgr Received IPC LOGIN REQ for user
(nas-port='1',framed-ip-address='192.168.2.33',calling-station-id='').
Sep 28 19:25:07 debug radiusd A:Login OK: [dauergast] (from client
localhost port 1)
Sep 28 19:25:07 info iprulesmgr Idle Timeout for user (nas-port='1')
set (value='3600').
Sep 28 19:25:07 info iprulesmgr Starting session for user
(virtual-ap-index='1',type='HTML',nas-port='1',name='dauergast',calling-station-id='',framed-ip-address='192.168.2.33',incoming-vlan-id='0').
Sep 28 19:25:14 warning iprulesmgr Station Table Entry
(id='0',ip-address='192.168.2.33',mac-address='00:00:00:00:00:00',virtual-ap-index='1')
exists with the IP address claimed by the new station (mac-address='00:19:E7:05:97:43'), for security reason we're terminating both station access.
Sep 28 19:25:14 debug iprulesmgr Removed Station Table Entry
(id='0',ip-address='192.168.2.33',mac-address='00:00:00:00:00:00',virtual-ap-index='1')

Any help from you would be appriciated.

thanks in advance.

Re: MSM750 -wierd behaviour

inayath_1 — Wed, 03 Nov 2010 07:05:36 GMT

MSM(192.168.1.1) -----------------192.168.1.2--------Router---192.168.2.1 -----Clients (192.168.2.2 - 30)

Now the issue I am facing is the users on the range 192.168.1.x are working fine without any problem.

But the users with the client of another block 192.168.2.x is not working and this is what i see in the logs pasted above.

Re: MSM750 -wierd behaviour

Matt Marcos — Wed, 03 Nov 2010 07:10:40 GMT

I'm no expert mate but from what I see in your logs:

You are using the controller as the DHCP server?

Maybe you need to enable the router to be a DHCP relay?

Looks to me like the MAC address for the client in the 192.168.2.x network is not getting back through the router.

cheers,

Matt.