Interfaces

From Scalelogic Wiki
Revision as of 14:06, 4 June 2014 by migrate>Ad-B
Jump to navigation Jump to search

Here you can set the interfaces settings.

To edit the Network interface settings, choose EDIT from the drop-down menu OPTIONS.

You can define, wheter the interface will get the IP from a DHCP or will it be configured via STATIC configuration. 

You can use static or dynamic (DHCP) network interface configuration.

When using static configuration of network interface, enter :

  • IP address,
  • netmask,
  • broadcast,
  • gateway.

If you set a new IP address, you will lose your connection with the server during activation and you will have to log in again. In the URL entry line of your browser, please enter the new IP address. If you do not get access, please use the console to set a new IP address. In order to access servers in another subnet, you need to enter the address of the router as the gateway.

Note

If you use an NTP server to maintain proper time and date, please make sure you have appropriate gateway and DNS settings.


Create bond interface 

Bonding allows for load-balancing or fail-over for incoming and outgoing connections. Here you can create or edit bonding network interfaces. In order to create a bonding interface, press the button Create Bond Interface:

  • select the network interfaces you want to create a new bonding interface for,
  • select the preferred bonding mode from the Type drop-down menu,
  • select dynamic (DHCP) or static configuration for the network interface,
  • if you want to get a DNS address dynamically, select get DNS ,
  • when using static configuration for a network interface, enter the IP address, netmask, broadcast and gateway. Afterwards, click the Apply button and a new bonding interface will be created.

Note

In order to take advantage of bonding more than one ethernet NIC needs to be plugged into the box. Please note that MAC addresses need to have a 02 prefix, for example: 02:xx:yy:zz:vv:nn
Each network interface is characterized by the following fields:

Primary
A string (eth0, eth2, etc) specifying which slave is the primary device. The specified device will always be the active slave while it is available. Only when the primary is off-line will alternate devices be used. This is useful when one slave is preferred over another, e.g., when one slave has higher throughput than another. The primary option is only valid for the active-backup mode.

Interface
Network interface name.

Cable
Shows if a cable is connected to the NIC.

State
Characterizes the state of the network interface. NIC can be in a bonding or single state.

Bonding modes:

balance-rr
       Transmissions are received and sent out sequentially on each bonded slave interface. This mode provides fault tolerance and load balancing.

active-backup
only one slave in the bond is active. Another bonded slave interface is only used if the active bonded slave interface fails. This mode provides fault tolerance.

balance-xor
Transmission is based on the following equation: [(the source MAC address XOR'd with the destination MAC address) modulo (slave count)]. This selects the same slave for each destination MAC address. This mode provides fault tolerance and load balancing.

broadcast :
Transmits everything on all slave interfaces. This mode provides fault tolerance.

802.3ad
IEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification. Requires a switch that supports IEEE 802.3ad Dynamic link aggregation.

balance-tlb :
Channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave. This mode provides fault tolerance and load balancing

Warning : Using cards from different manufacturers or cards based on different chipsets in one bond team may cause low performance or unstable behavior.