- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Re: MSM750 -wierd behaviour
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2009 01:23 PM
тАО11-06-2009 01:23 PM
MSM750 -wierd behaviour
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2009 09:28 PM
тАО11-06-2009 09:28 PM
Re: MSM750 -wierd behaviour
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2009 03:01 AM
тАО11-07-2009 03:01 AM
Re: MSM750 -wierd behaviour
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2009 03:10 PM
тАО11-07-2009 03:10 PM
Re: MSM750 -wierd behaviour
I will update the firmware, just need to purchase the right support contract.
Trev.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2010 04:42 AM
тАО03-15-2010 04:42 AM
Re: MSM750 -wierd behaviour
I'm experiencing the same problem as you had. Can you tell me if you find any resolution? Or you just ignore the messages?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2010 11:46 AM
тАО03-15-2010 11:46 AM
Re: MSM750 -wierd behaviour
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2010 09:25 PM
тАО08-01-2010 09:25 PM
Re: MSM750 -wierd behaviour
Cheers,
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2010 11:39 PM
тАО11-02-2010 11:39 PM
Re: MSM750 -wierd behaviour
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2010 11:46 PM
тАО11-02-2010 11:46 PM
Re: MSM750 -wierd behaviour
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2010 12:04 AM
тАО11-03-2010 12:04 AM
Re: MSM750 -wierd behaviour
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.