MESH Implementation With AP5131 version 1.1.2.0-005R

MESH ImplementationWith AP5131 version 1.1.2.0-005R

Contents

Mesh Networking Overview Test Network Diagram Configuring a LAN for Mesh Networking Configuring a WLAN for Mesh Networking Configuring Radio for Mesh Networking Verify Mesh Networking

Mesh Networking Overview

AP-5131's new mesh networking functionality As a bridge to connect two Ethernet networks. As a repeater to extend your network's coverage area without additional cabling.

The AP-5131 mesh networking functionality is configurable in two modes. A wireless client bridge mode A wireless base bridge mode accepts connections from client bridges These two modes are not mutually exclusive.

AP-5131s can be configured as a repeater By configuring both a base and a client bridge function at the same time to transmit data with associated MUs in their coverage area (client bridge mode) as well as forward traffic to other AP-5131s in the mesh network (base bridge mode). The number of AP-5131s and their intended function within the mesh network dictate whether they should be configured as base bridges, client bridges or both (repeaters).

Mesh Networking Overview (contd) In Client Bridge Mode

AP5131 scans to locate other access points using the WLAP client's ESSID. Then it is required to go through the association and authentication process to establish wireless connections with the located devices. This association process is identical to the AP-5131's current MU association process. Once the association and authentication process is complete, the wireless client adds the connection as a port on its bridge module. This causes the client bridge to begin forwarding packets to the base bridge node. The base bridge realizes it is talking to a wireless client bridge. It then adds that connection as a port on its own bridge module. The two bridges at that point are communicating using the Spanning Tree Protocol (STP). After the client bridge establishes at least one wireless connection (if configured to support mobile users), it begins beaconing and accepting wireless connections. If configured as both a client bridge and a base bridge, it begin accepting client bridge connections. Therefore, the mesh network could connect simultaneously to different networks in a manner whereby a network loop is not created and then the connection is not blocked. Once the client bridge establishes at least one wireless connection, it begins establishing other wireless connections as it finds them available. Thus, the client bridge is able to establish simultaneous redundant links.

Mesh Networking Overview (contd) In Client Bridge mode

The client bridge creates up to three connections if it can find base bridges for connection. If the connections are redundant (on the same network), then one connection will be forwarding and the others blocked. However, if each of the connections links to a different wired network, then none are redundant and all are forwarding. Thus, the bridge automatically detects and disables redundant connections, but leaves non-redundant connections forwarding. This gives the user the freedom to configure their topology in a variety of ways without limitations. This is important when configuring multiple AP-5131s for base bridge support in areas like a shipping yard where a large radio coverage area is required

In Base Bridge Mode

AP5131 operates normally at boot time. The base bridge supports connections made by other client bridge AP-5131s. The dual-radio model AP-5131 affords users better optimization of the mesh networking feature by enabling the AP-5131 to transmit to other mesh network members using one independent radio and transmit with associated MUs using the second independent radio.

Test Network Diagram

Base Bridge192.168.1.1/24

MUsL

AN

LAN

HU

B

Printer

MUs

MUsB

B

CC

C

Base Bridge192.168.1.10/24

Client Bridge192.168.1.20/24

Test Laptop #1192.168.1.200/24

WLAN1ESSID:BLUE

B : Base BridgeC : Client BridgeCB : Repeater

Test Laptop #2192.168.1.100/24

Configuring a LAN for Mesh Networking

1Click “Mesh STP Configuration”

2

Modify priority lower than default,32768, to make a root bridgeIn this case I change the priority from 32768 to 32000

Just check the IP address of Root Bridge

Configuring a LAN for Mesh Networking


2

You can use default priority to set a client bridge

Just check the IP address of Client Bridge #1

Configuration a LAN for Mesh Networking


2


You can use default priority to set a client bridge

Configuring a WLAN for Mesh Networking

1

Click “Edit”

2

Click the checkbox to disable “Client Bridge Backhaul”


3

Click the checkbox to disallow MU to MU Communication”

Check the ESSID of Mesh Network

4


1

Click “Edit”

2

You can use default configuration of enable “Client Bridge Backhaul”


3



4


1

Click “Edit”

2

You can use default configuration of enable “Client Bridge Backhaul”


3



4

Configuring Radio for Mesh Networking

1

2


Click the checkbox to configure as a root bridge

Click the checkbox to enable radio 2In this case you can use 802.11a mode for mesh network


1

2


Click the checkbox to configure as a client bridge

Click the checkbox to enable radio 2In this case you can use 802.11a mode

for mesh network


1

2


Click the checkbox to configure as a client bridge

Click the checkbox to enable radio 2In this case you can use 802.11a mode

for mesh network

Verify Mesh Networking

1

2

You can see the number of Client Bridges with real time


Check the Mesh Status


Check the Base Bridge and get detailed information

1



Check the Base Bridge and get detailed information

1



After Mesh network is configured, PING test from client bridge to other mesh members


- When the Client Bridge ,192.168.1.20/24 which associated test laptop #1 is down, I got the just only one ping loss


- When the Client Bridge ,192.168.1.20/24 is down, test laptop #2 associated with another client bridge,192.168.1.10/24

Thank you for your time and attention

Documents

MESH Implementation With AP5131 version 1.1.2.0-005R