EasyManua.ls Logo

Ruckus Wireless ZoneFlex R310 - Page 150

Ruckus Wireless ZoneFlex R310
152 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
failover in case of one of the ports is disconnected) at the expense of more overhead.
The slow (default) rate is adequate for the vast majority of Enterprise WLAN cases.
Slow (lacp-rate 0) (default) requests link partner to transmit LACPDUs every 30
seconds.
Fast (lacp-rate 1) requests link partner to transmit LACPDUs every one second.
Transmit hash (xmit-hash) defines how the AP chooses to distribute packets between
the two physical Ethernet links which comprise the bonded link. Network topology
and expected traffic flows should be considered when choosing which transmit hash
option to use so as to spread traffic as evenly as possible between the two physical
links.
Layer 2 (xmit-hash 0) (default) uses the source & destination MAC addresses in the
packet to determine which physical link the packet is sent over. This is a fully-compliant
802.3ad option.
Layer 3 & Layer 4 (xmit-hash 1) uses source & destination IP addresses as well as
source & destination ports. This policy uses upper layer protocol information, when
available, to generate the hash. This allows packets destined for a particular network
peer to be distributed across both physical links, although a single connection is
limited to one of the physical links.
For fragmented packets, layer 4 information is omitted.
This algorithm is not fully 802.3ad compliant.
Layer 2 & Layer 3 (xmit-hash 2) uses source & destination MAC addresses as well
as source & destination IP addresses. This algorithm places all traffic to a particular
network peer on the same physical link. For non-IP traffic, the formula is the same
as for the layer2 transmit hash policy. This policy is intended to provide a more
balanced distribution of traffic than layer2 alone, especially in environments where a
layer3 gateway device is required to reach most destinations. This algorithm is 802.3ad
compliant.
Add or Delete (add|delete) are used to explicitly define which physical Ethernet ports
(ethx) are part of the bond interface (bond0). At a bare minimum, to enable LACP on
the AP this option must be used to add both physical ports to the bond interface.
Examples
Enable with defaults:
:set bond bond0 add eth0
:set bond bond0 add eth1
150
ZoneFlex Indoor Access Point Release 104.0 User Guide
Appendix B: Configuring Link Aggregation (LACP) for AP Backhaul

Table of Contents

Other manuals for Ruckus Wireless ZoneFlex R310

Related product manuals