- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Re: MSM 422 Mesh
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
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
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
08-24-2015 12:31 PM
08-24-2015 12:31 PM
MSM 422 Mesh
I am using two MSM 422 to set up a mesh network. These units have been in a standard wifi configuration until I recently needed to extend the network where no cabling was available. Once 422 is master, one is slave. Both talk to a 710 controller.
Slave unit will not talk to the master, but the Master sees the mesh ID (default of 1). The error on the controller is that the slave unit is unknown to the controller and therefore not allowed to join the mesh. If I plug the slave into the LAN momentarily, it will authenticate to the controller and the mesh is activated (and immediately creates a routing loop).
I have alternately set the IP on the slave to DHCP or Static, and always on the same subnet. I also set the discovery address to the IP of the controller. Is this a catch 22 where the mesh is not activated so the AP cannot authenticate, which is what is keeping the mesh from activating?
How do I resolve this?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2015 06:39 AM
09-03-2015 06:39 AM
Re: MSM 422 Mesh
I think this is out of date now (since v 5.x), but it may have some extra info:
http://h30499.www3.hp.com/t5/MSM-Series/Meshing-Help/m-p/5767595#M1309
The trick is to get the slave AP into the system so it is managed by teh controller, and then change the config with the local mesh settings. Leave the defaults for Local Mesh Profiles, and change the radio type to mesh only.
Change the master - modify local mesh profile 1 (do it without encryption whilst testing) and radio type to mesh only.