Technical data

Dual-Ethernet Operation

802.11d Support

The original 802.11 standard defined operation in only a few regulatory domains

(countries). 802.11d added the ability for 802.11 WLAN equipment to operate in addi-

tional countries by advertising the country code in the beacon. Devices pick up the

country code and adjust communication accordingly. You do not have to configure or

enable this feature; the Meru implementation currently works automatically for all

countries listed in setup. There is no show command that displays this feature. Vali-

date 802.11d in the 802.11 Beacons and Probe Response, Country code IE field.

Dual-Ethernet Operation

Dual-Ethernet support enables the controller’s second Ethernet port and provides the

ability for it to work either as a redundant interface or a second active interface.

If the second interface is configured as redundant, it will serve as a backup interface

to the first interface. This means that it will be idle as long as the first interface is

functional and will perform all functions of the first interface if the first interface

fails. In a redundant configuration, the first interface must have a static IP address.

If the second interface is configured as active, it can be configured as a separate

interface that can support an additional configuration, for example to support GRE

tunneling while the first interface is configured for VLANs.

It is implicit in the configuration of redundant mode that the second Ethernet inter-

face should be connected to a switch port in which it can perform the same functions

as the default Ethernet interface.

Note that when changing from redundant to dual active operation, a controller

reboot is required.

Configuring Dual Ethernet

The second Ethernet interface can be configured as either redundant or active. An

active interface can be used to support a VLAN or GRE (Generic Routing Encapsula-

tion) tunneling. A redundant interface is a backup interface in case the primary

interface fails.

Note:

The first Ethernet interface is treated as the default interface. The

responsibility of the default interface is to pass wireless tunnel traffic between the

APs and the controller. In addition to the general support of GRE and VLAN, the

default interface is also the designated management interface for the controller,

providing support for management access traffic via SSH and HTTPS.