Failover
In Failover mode, the GB1 and GB2 interfaces are both activated and each has a unique MAC address but they share a
common bond0 virtual interface. Only a single MAC exists for the shared bond0 interface and only a single IP can be
assigned to bond0. When data needs to be sent from the appliance, only GB1 will send it using the bond0 MAC/IP. When
traffic is sent to the bond0 MAC/IP, only GB1 will receive it, since only GB1 is responding to ARP requests using the bond0
MAC. If GB1 is disconnected, then GB2 assumes control of the bond0 MAC/IP for all data exchange.
Failover-Routed
In Failover-Routed mode, the appliance automatically switches to a secondary network interface in the event of a failure on
the primary interface. When enabled, this feature allows the appliance to route network traffic to a secondary interface when
a selected condition is met. After the administrator designates either the eth0 or eth1 network interface as the primary
interface, one of the following conditions must be selected as the trigger that initiates the failover-routed feature:
•
Primary Interface Down
•
Unreachable Primary Default Gateway
•
Unreachable DSView
•
Unreachable IP Address
To configure a network device:
1.
From the sidebar, click
Network Settings
.
2.
Enter the hostname (the hostname will be used for e-mail notifications as the sender address).
3.
Use the drop-down list to select Normal, Failover or Failover-Routed for the mode.
4. Enter the primary and secondary DNS addresses in the appropriate fields.
5.
Enter the domain name.
6. Use the drop-down lists to select the IPv4 and IPv6 default gateways, if
Normal
or
Failover
is the selected
mode.
-or-
If Failover-Routed is the selected mode:
a. Click the drop-down list to select the IPV4 Primary Interface.
b. Select the appropriate radio button option from the Failover-Routed IPv4 Trigger Mode list.
7.
Click
Apply
.
5.3.2 Bridge Group Configuration
An administrator can choose network interfaces to bridge together into a logical bridge group. This feature simplifies the
creation, deletion and maintenance of bridged interfaces. You can bridge both physical and virtual interfaces, and bridging
supports user-created interfaces as well as the pre-defined ones.
A bridge group can be created for each virtual and physical interface defined on the appliance. When a bridge group is
created, it will be assigned a Layer 3 IPv4/IPv6 address. When interfaces are added to a bridge group, a prompt will be
displayed, indicating that all IP addresses assigned to the interfaces will be lost and communication with devices
accessible through the ports within the bridge group will occur via the bridge group's IP address.
Appliance interfaces placed into a bridge group will not support DHCP services to prevent conflict with other DHCP
services on the network. The appliance will also not support UMIQ modules connected to bridged interfaces.
The appliance is not intended to be a general purpose ethernet bridge. The port bridging feature is intended to make
devices, which are physically connected to private interface ports, accessible via the public network infrastructure. In order
to prevent a switching loop when multiple bridged interfaces are accidentally connected to the same network switch, the
Spanning Tree Protocol (STP) feature is enabled by default for all bridge groups.
If the appliance is connected to a network switch with an active Bridge Protocol Data Unit (BPDU) Guard, the STP feature
must be disabled for the bridge group.
NOTE: Disabling STP will cause the appliance to store and forward ethernet frames between the ports of the bridge
group without any switching loop prevention.
Vertiv
| Avocent® Universal Management Gateway Appliance Installer/User Guide |
25
