25
accessible from the outside but are accessible within the subnet, you might want to check and
make sure that the default gateway was set up correctly.
From firmware version 9.0.0, WebMux IPv6 supports all modes of operation. It can operate in Two-
Armed NAT mode, Transparent mode, as well as One-Armed Single Network mode and OOP (Out-
of-Path) mode. It allows SNAT Layer 4 operations, as well as SSL termination. It also allows
incoming IPv6 traffic being load balanced to internal IPv4 based servers. However, for traffic
initiated behind the WebMux (not load balanced), it does not translate IPv4 to IPv6.
High Availability and Configuration
Two WebMux units can be paired together for high availability. In this configuration one unit must
be explicitly configured as a “primary” unit and “NOT running solo.” The other unit must be
configured as “NOT primary.” This can be done through the LCD setup or though the
Administrative Web Management Interface at /cgi-bin/rec or by going to the “reconfigure” screen
from the “network” menu in the main console of the Administrative Web Management Interface. It
can also be done by running the “rec” utility from the CLI.
Each unit will need to complete the LCD setup or “reconfigure.” Be sure that each unit is assigned
its own unique IP address to avoid addressing conflicts on your network. In some modes such as
NAT mode and Out-of-Path mode, there is a setting for the Server LAN gateway IP address. The
Server LAN gateway IP is the IP address that the servers use as their default gateway. This is
optional in Out-of-Path mode. Please review the Out-of-Path mode configuration section to decide
whether or not you need this. The Server LAN gateway IP setting will only show up for the primary
unit setup. This setting is passed to the secondary unit during synchronization. This IP address is
up only on the active unit.
If the primary unit goes down, the secondary unit will activate the Server LAN gateway IP on itself to
ensure that the real servers will always have a valid default gateway to use.
After these settings have been made, you will need to connect the two units together using a
crossover network cable plugged into the “backup” ports of the WebMux units.
To properly sync the two units, begin with both units turned off and be sure the Ethernet cable is
connected to the “backup” ports of both units. Turn the primary unit power on and wait for it to go
into the active state. You will see the LCD screen showing the updating status. You can now
power on the secondary unit. When fully booted, the secondary will show the host/domain name
and “[backup standby]” underneath. You will also see the message “(backed up by <IP address of
the secondary unit>)” at the top of the main console screen of the web management of the primary
unit, underneath the unit’s IP address(es). If you access the secondary unit, you will see the
message “Inactive member of a WebMux pair” and “(backed up by <IP address of primary unit>).”
This indicates that the units have properly synchronized. Setting and configurations made on the
primary unit will automatically synchronize with the secondary unit. It is essential that this
configuration is saved as changes will not propagate to the secondary unit until this is done.
There are a few things to keep in mind when you have two units paired in a high availability
configuration. In NAT, Transparent, and Single Network modes, you will not be able to access the
secondary WebMux through the “Internet” interface. You generally should not ever need to access
the secondary unit when it is on standby, but if you so desire you could access it from the “Server”
interface. In NAT and Transparent modes the server interfaces are on a different physical network
segment. Be sure your client machine is on the proper side of the network if you desire to access
the secondary unit. In Single Network and Out-of-Path modes you generally only need to connect