Astra Wireless Documentation
  • Technical documentation
    • Astra Quanta⁣ Technical User Manual
      • Introduction⁣⁣⁣⁣⁣⁣⁣
        • Key Features⁣⁣⁣⁣⁣
        • Hardware Platform⁣⁣⁣⁣⁣
        • Power Supply⁣⁣⁣⁣⁣⁣
        • Lightning⁣ ⁣protection unit⁣⁣⁣⁣⁣
        • Packing list⁣⁣⁣⁣⁣⁣⁣
      • Planning considerations⁣⁣⁣⁣⁣⁣⁣
      • Link pre-configuration in the lab⁣⁣⁣⁣⁣
      • Installation
      • Operation & Administration⁣⁣⁣⁣⁣
        • Web GUI access⁣⁣⁣⁣
        • Dashboard⁣⁣⁣⁣
        • General settings⁣⁣⁣⁣⁣
        • Security settings⁣⁣⁣⁣
        • Radio settings⁣⁣⁣⁣
        • Network settings⁣⁣⁣⁣⁣
        • Switch Settings
        • SNMP settings⁣⁣⁣⁣
        • Spectrum Analyzer⁣⁣⁣⁣⁣
        • Antenna Alignment Tool⁣⁣⁣⁣⁣
        • Maintenance⁣⁣⁣
        • Instant DFS⁣⁣⁣⁣
        • Graphs⁣⁣⁣⁣
      • Troubleshooting⁣⁣⁣⁣⁣⁣⁣⁣⁣
    • Astra Evolution Technical User Manual
      • Introduction⁣⁣⁣⁣⁣⁣
        • Key Features⁣⁣⁣⁣⁣⁣⁣
        • Hardware Platform⁣⁣⁣⁣⁣⁣⁣⁣
        • Power supply⁣⁣⁣⁣⁣⁣⁣
        • Lightning protection unit⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣
        • Synchronization unit⁣⁣⁣⁣⁣⁣⁣
        • ⁣⁣⁣Packing List
      • Planning considerations⁣⁣⁣⁣⁣⁣⁣⁣⁣
      • Link Pre-configuration in the lab⁣⁣⁣⁣⁣⁣⁣⁣⁣
      • Installation⁣⁣⁣⁣⁣
      • Operation & Administration⁣⁣⁣⁣⁣⁣⁣
        • Web GUI access⁣⁣⁣⁣⁣⁣
        • Device Status⁣⁣
        • Basic Settings⁣⁣⁣⁣⁣
          • System Settings⁣⁣⁣⁣⁣⁣
          • Network Settings⁣⁣⁣⁣⁣⁣⁣
          • Link Settings⁣⁣⁣⁣⁣⁣
          • Static Links⁣⁣⁣⁣⁣
          • MAC Switch⁣ ⁣
          • IP Firewall
          • SNMP
          • QoS Options⁣⁣⁣⁣⁣⁣
          • Traffic Shaping⁣⁣⁣⁣⁣⁣⁣
          • Extra Commands⁣⁣⁣⁣⁣⁣
        • Maintenance
        • Spectrum Analyzer
        • DFS
        • Command Line
      • Troubleshooting⁣⁣⁣⁣⁣⁣
        • No access to the local unit⁣⁣⁣⁣⁣
        • The wireless link cannot be established⁣⁣⁣⁣⁣
        • The wireless link is established, but there is no access to the remote device⁣⁣⁣
        • The wireless link throughput is lower than expected⁣⁣⁣
        • Common errors in configuration⁣⁣⁣⁣
        • Emergence Repair Console⁣⁣
        • Unicast-flood detection⁣⁣⁣⁣
    • AstraFleX⁣ Technical User Manual
      • Getting started with AstraFleX User Manual
      • ⁣⁣IP-address format
      • General Purpose Command Set
      • Layer 2 commands set -PHY and MAC
        • ⁣prf ⁣command
        • ⁣⁣lag command (Link Aggregation )
        • ⁣⁣svi command
        • ⁣⁣ltest (radio link test)
        • macf command (addresses mapping)
        • ⁣⁣arp command (ARP protocol)
        • ⁣⁣switch command
        • ⁣⁣dfs (Dynamic Frequency Selection)
        • ⁣⁣lldp command
        • ⁣⁣mint command
        • ⁣⁣rfconfig command
      • ⁣⁣Layer 3 Command set – IP Networking
        • ⁣⁣Ifconfig command (interfaces configuration)
        • tun command (tunnels building)
        • qm command (QoS configuration)
        • ⁣⁣route command (static routes configuration)
        • ⁣⁣arip command
        • ⁣⁣OSPF command
        • ARDA (Aqua Router DAemon)
        • ⁣⁣netstat command (Network statistics)
        • ⁣⁣ipfw command (IP Firewall)
          • ⁣⁣PCAP-filters
        • ⁣⁣loadm command (load meter)
        • ⁣⁣rpcapd command (Remote Packet Capture)
        • ⁣⁣snmpd command (SNMP daemon)
        • ⁣⁣td command (Telnet daemon)
        • ⁣⁣nat command (Network Address Translation)
        • ⁣⁣trapd command (SNMP Traps support)
        • dhcpd command (DHCP Server)
        • ⁣⁣dhcpr command (DHCP relay)
        • dhcpc command (DHCP Client)
        • ⁣⁣vrrp command (VRRP server)
      • ⁣⁣Other commands
    • ⁣NEXT Monitoring System Technical User Manual
      • Description⁣ and operational principles
      • Installation
      • Configuration⁣⁣ ⁣and⁣ management⁣
        • Wireless⁣ ⁣⁣devices preparation
        • Accounts⁣ and user groups
        • Devices⁣ ⁣and links
        • Incident⁣ ⁣⁣management
        • System⁣⁣ ⁣configuration
      • Monitoring⁣ ⁣and management
        • R⁣ep⁣o⁣⁣rts
        • Devices
        • ⁣⁣Incidents
        • MAP
      • Technical support
  • White⁣ papers
    • MINT ⁣⁣⁣technology
    • Dynamic ⁣⁣Frequency ⁣⁣Selection
    • ⁣⁣RADIUS authentication for admin users
    • Security in Astra Wireless Devices
    • ⁣⁣Performance of the Astra Wireless devices
      • Astra Quanta
        • ⁣⁣Thr⁣⁣⁣oughpu⁣t⁣⁣⁣⁣⁣⁣
        • ⁣Packet ⁣⁣performanc⁣e⁣⁣⁣⁣⁣
      • Astra Evolution
        • H22 platform
          • Packet ⁣⁣⁣perfor⁣mance⁣⁣
          • Throug⁣hput⁣⁣⁣⁣⁣⁣
        • H16 platform
          • Packet⁣⁣ ⁣perfor⁣mance⁣⁣
          • ⁣⁣⁣⁣⁣⁣Throug⁣hput⁣⁣⁣⁣⁣⁣⁣
    • ⁣⁣⁣Link ⁣⁣⁣aggregation, balancing and redundancy
      • Astra Evolution
        • Redundancy ⁣⁣⁣with Failover option
        • Redundancy w/o aggregation and AstraMUX
        • Redundancy⁣⁣⁣ ⁣with aggregation and w/o AstraMUX
        • Redundancy ⁣⁣with AstraMUX
        • Full⁣ Duplex
      • Astra Quanta
        • Aggregation ⁣with redundancy ⁣based on⁣ LACP
        • Redundancy⁣⁣⁣ ⁣based ⁣on STP
        • ⁣Redundancy⁣⁣ based on⁣ OSPF
        • ⁣Redundancy with Evolution
    • Beamforming⁣ ⁣technology
    • ⁣⁣⁣Remote ⁣⁣⁣L2 management of Evolution via CLI
    • ⁣⁣⁣Remote ⁣⁣⁣L2 management of Evolution via Web GUI
    • Connectivity with mobile objects⁣⁣⁣⁣
      • Mining industry⁣⁣⁣
      • Railway transport⁣⁣⁣
      • Transport over the water⁣⁣⁣
      • Configuration example⁣⁣⁣
Powered by GitBook

Astra Wireless Technology © 2024. All rights reserved. For more information about available models, sales and technical support, please proceed to https://astrawireless.net/

On this page
  • Description
  • Configuration Example
  1. White⁣ papers
  2. ⁣⁣⁣Link ⁣⁣⁣aggregation, balancing and redundancy
  3. Astra Evolution

Redundancy ⁣⁣⁣with Failover option

PreviousAstra EvolutionNextRedundancy w/o aggregation and AstraMUX

Last updated 1 year ago

CAUTION

Configurations from the scenarios below are examples that demonstrate the potential capabilities of the Astra Wireless devices. The configurations may vary depending on the model and firmware version. We do not recommend copying this solutions to the hardware without checking.

Description

Evolution family units have a functional channels redundancy function. A hot reserve might be created by using the Failover option. The Failover option does not depend on the method of data transmission on the main link. The only condition is connectivity at level 2 between Astra Wireless devices through both links. The principle of operation is extremely simple. The Astra Wireless device, on which the Failover option is configured, checks the availability of a specific MAC address through the primary link. If this MAC address is available, then the operation of the backup link is blocked. The radio module stops broadcasting on the backup master. The reserved slave device only listens to the radio while there is no signal from the master. Thus, the backup link can operate on the same frequency as the main one, but it does not have any influence on it. As soon as the tracked MAC address disappears in the main link, the backup link will be unlocked and traffic will begin to be transmitted over it. The process is completely automatic. However, the transition to a backup link is associated with a short-term idle time. Traffic will return automatically to the primary link as soon as backup link is failure. For example, in the figure below, if the Master 1 - Slave 1 link is selected as the main one, the Master 2 device will turn off the radio interface, and the Slave 2 device will switch to the broadcast listening mode.

The tracked MAC address can be determined in two ways: automatically and manually. In the figure below, regardless of the selected method, the Master 1 will track the Slave 1 MAC address and the Master 2 - Slave 2 MAC address.

If Evolution devices are used as the main link, this gives additional advantages. In this case, both radio links can be configured with the Failover option. For both links, the quality of the established connection will be automatically evaluated. Connection with the worst indicators will automatically become a backup link. Channel selection parameters can be controlled manually.

NOTE

It is also possible to connect two Astra Wireless devices to one external antenna or use one radio frequency.

The Failover option is a part of the MINT proprietary protocol, so the task implementation will require joining all devices into a single MINT area. After joining devices into a single MINT area, there is a risk of a switching loop appearance. In this article, we will review two ways to prevent the switching loop appearance:

  • Using different switch groups (figure 2a): different switch groups are used for data transmission on the main and backup links, on the Master 1-Slave 1 link switch group #1 is used, on the Master 2 - Slave 2 link switch group #2 is used.

  • Using the switch border option (figure 2b): the switch border option must be enabled on all prf interfaces. At the same time, it is allowed to use the same switch groups for data transmission on the main and backup links.

Configuration of Failover in AstraFleX

mint IFNAME [-]failover {MAC|auto}
Parameter
Description

mint IFNAME failover MAC

Enable Failover option to check "MAC" availability

mint IFNAME failover auto

Enable Failover option to check "MAC" availability. "MAC" will be selected in automatic mode

mint IFNAME [-]failover

Disable Failover

Configuration Example

A management is VLAN 100 inside a switch group #100. A transport of user data is inside a switch group #1.

CAUTION

STP protocol may block correct working Failover option, so it should be disabled. Failover option causes short-time loops in one broadcast domain.

If the devices of the main and backup links are mounted on the same site and use the same frequency channel, we recommend to use different "Network SID". This will avoid establishing cross links: Master 1 - Slave 2 and Master 2 - Slave 1. In this example, the Network SIDs 10101010 and 10101011 are used.

The article provides one of the possible configurations of radio link settings and data transmission. The configuration used in your network may differ from the one shown.

Configure Master 1 and Slave 1 as the main link.

Master 1

rf rf6.0 band 40
rf rf6.0 mimo
rf rf6.0 freq 5000 bitr 300000 sid 10101010 burst
rf rf6.0 txpwr 25 pwrctl distance auto
dfs rf6.0 dfsoff
mint rf6.0 -roaming leader
mint rf6.0 -type master
mint rf6.0 -name "Master 1"
mint rf6.0 -key "123456789"
mint rf6.0 poll start
ifc svi100 up
ifc vlan100 vlan 100 vlandev eth0 up
sw group 100 add vlan100 rf6.0 sw group 100 order 1
svi 100 group 100
ifc svi100 192.168.1.1/24
sw group 100 stp off
sw group 100 start

Slave 1

rf rf6.0 band 40
rf rf6.0 mimo
rf rf6.0 burst
dfs rf6.0 dfsoff
mint rf6.0 prof 1 -band 40 -freq 5000 -bitr 300000 -sid 10101010 -nodeid 00020 -type slave -netid 0 -minbitr 30000 -autobitr -mimo -key "123456789"
mint rf6.0 -name "Slave 1"
ifc svi100 up
ifc vlan100 vlan 100 vlandev eth0 up
sw group 100 add vlan100 rf6.0 svi 100 group 100
ifc svi100 192.168.1.2/24
switch group 100 order 1
sw group 100 stp off
sw group 100 start

Configure Master 2 and Slave 2 as a backup link.

Master 2

rf rf6.0 band 40
rf rf6.0 mimo
rf rf6.0 freq 5000 bitr 300000 sid 10101011 burst
rf rf6.0 txpwr 25 pwrctl distance auto
dfs rf6.0 dfsoff
mint rf6.0 -roaming leader
mint rf6.0 -type master
mint rf6.0 -name "Master 2"
mint rf6.0 -key "123456789"
mint rf6.0 poll start
ifc svi100 up
ifc vlan100 vlan 100 vlandev eth0 up
sw group 100 add vlan100 rf6.0 svi 100 group 100
ifc svi100 192.168.1.3/24
switch group 100 order 1
sw group 100 stp off
sw group 100 start

Slave 2

rf rf6.0 band 40
rf rf6.0 mimo
rf rf6.0 burst
dfs rf6.0 dfsoff
mint rf6.0 prof 1 -band 40 -freq 5000 -bitr 300000 -sid 10101011 -nodeid 00040 -type slave -netid 0 -minbitr 30000 -autobitr -mimo -key "123456789"
mint rf6.0 -name "Slave 2"
ifc svi100 up
ifc vlan100 vlan 100 vlandev eth0 up
sw group 100 add vlan100 rf6.0 svi 100 group 100
ifc svi100 192.168.1.4/24
switch group 100 order 1
sw group 100 stp off
sw group 100 start

Create one MINT domain.

Master 1

ifc prf0 up
prf 0 parent eth0
mint prf0 -name "Master 1 prf"
mint prf0 -nodeid 00050
mint prf0 -type master
mint prf0 -mode fixed
mint prf0 -key "123456789"
mint prf0 -authmode public
mint prf0 start
mint join rf6.0 prf0

Slave 1

ifc prf0 up
prf 0 parent eth0
mint prf0 -name "Slave 1 prf"
mint prf0 -nodeid 00080
mint prf0 -type master
mint prf0 -mode fixed
mint prf0 -key "123456789"
mint prf0 -authmode public
mint prf0 start
mint join rf6.0 prf0

Master 2

ifc prf0 up
prf 0 parent eth0
mint prf0 -name "Master 2 prf"
mint prf0 -nodeid 00070
mint prf0 -type master
mint prf0 -mode fixed
mint prf0 -key "123456789"
mint prf0 -authmode public
mint prf0 start
mint join rf6.0 prf0

Slave 2

ifc prf0 up
prf 0 parent eth0
mint prf0 -name "Slave 2 prf"
mint prf0 -nodeid 00090
mint prf0 -type master
mint prf0 -mode fixed
mint prf0 -key "123456789"
mint prf0 -authmode public
mint prf0 start
mint join rf6.0 prf0

Configure switch groups for data transmission.

Use different switch groups (figure 2a):

Master 1

switch group 1 add eth0 rf6.0 switch group 1 start

Slave 1

switch group 1 add eth0 rf6.0 switch group 1 start

Master 2

switch group 2 add eth0 rf6.0 switch group 2 start

Slave 2

switch group 2 add eth0 rf6.0 switch group 2 start

Use switch border option (figure 2b):

Master 1

switch group 1 add eth0 rf6.0 switch group 1 start
 
mint prf0 swborder

Slave 1

switch group 1 add eth0 rf6.0 switch group 1 start
 
mint prf0 swborder

Master 2

switch group 1 add eth0 rf6.0 switch group 1 start
 
mint prf0 swborder

Slave 2

switch group 1 add eth0 rf6.0 switch group 1 start
 
mint prf0 swborder

Enable Failover option.

Manual MAC address settings:

Master 1

mint rf6.0 failover "MAC Slave 1"

Master 2

mint rf6.0 failover "MAC Slave 2"

Automatic MAC address settings:

Master 1

mint rf6.0 failover auto

Master 2

mint rf6.0 failover auto

Manual backup link selection.

CAUTION

When Failover option is enabled on two devices of the Evolution family, a situation may occur when both links are equal in their characteristics (link cost). In this case, you need to manually specify which of the links will be redundant, assigning an additional cost to a specific interface.

Master 2

mint rf6.0 -extracost 3000

Slave 2

mint rf6.0 -extracost 3000
Example with different switch groups
Example with switch border option usage