(1) Physical interface settings
Set up physical interfaces to be used for the Redundant Line Control Function.
The physical interface settings vary depending on redundant network methods and configurations. For details on the differences of each setting, see the following Table 3.8 Physical interface settings (RHEL8) and Table 3.9 Physical interface settings (RHEL9).
Point
For RHEL 7 or later, the naming conventions for NIC names are changed to generate device names based on the hardware locations of NICs (Predictable Network Interface Names).
In an environment where Predictable Network Interface Names are enabled, interface names are displayed as enXXXXX. In an environment where Predictable Network Interface Names are disabled, interface names are displayed as ethX.
Replace the interface name (ethX) described in this manual with the interface name suitable for your environment. Replace the ifcfg-ethX file name with the file name suitable for your environment as well.
Only the required parameters in the Redundant Line Control Function are described for the configuration file (ifcfg-ethX) of the network interface in this manual. Set other parameters according to your environment.
For RHEL8
Redundant network methods | Tagged VLAN disabled | Tagged VLAN enabled | |
|---|---|---|---|
Fast switching mode (IPv4) | |||
NIC switching mode (IPv4) | Primary interface | ||
Secondary interface | |||
Virtual NIC mode | |||
GS linkage mode | Not supported | ||
Note
For RHEL 7 or later, the naming conventions for NIC names are changed to generate device names based on the hardware locations of NICs (Predictable Network Interface Names).
If you need to prevent device names of physical NICs from changing to unexpected names in an environment where traditional interface names (ethX) for RHEL6 or earlier are used, describe the definition of "HWADDR=<MAC address>" in the settings for the physical interfaces (the /etc/sysconfig/network-scripts/ifcfg-ethX file). For details, see "Linux documentation."
The setting "HOTPLUG=no" is not required.
The tagged VLAN interface name is available only by "interface name.VLAN-ID" format, such as eth0.1.
In the cluster environment of physical IP takeover II, set ONBOOT=no to ifcfg-ethX.
In the settings for the tagged VLAN interface (/etc/sysconfig/network-scripts/ifcfg-ethX.Y file) "PHYSDEV=", describe the physical interface name that configure the tagged VLAN interface, such as ethX.
/etc/sysconfig/network-scripts/ifcfg-ethX
TYPE=Ethernet BOOTPROTO=none IPADDR=XXX.XXX.XXX.XXX PREFIX=XX DEVICE=ethX ONBOOT=yes |
/etc/sysconfig/network-scripts/ifcfg-ethX
TYPE=Ethernet BOOTPROTO=none IPADDR=XXX.XXX.XXX.XXX PREFIX=XX DEVICE=ethX ONBOOT=no |
/etc/sysconfig/network-scripts/ifcfg-ethX
TYPE=Ethernet DEVICE=ethX ONBOOT=yes |
/etc/sysconfig/network-scripts/ifcfg-ethX.Y
VLAN=yes TYPE=Vlan PHYSDEV=ethX VLAN_ID=Y BOOTPROTO=none IPADDR=XXX.XXX.XXX.XXX PREFIX=XX ONBOOT=yes |
/etc/sysconfig/network-scripts/ifcfg-ethX
TYPE=Ethernet DEVICE=ethX ONBOOT=yes |
/etc/sysconfig/network-scripts/ifcfg-ethX.Y
VLAN=yes TYPE=Vlan PHYSDEV=ethX VLAN_ID=Y BOOTPROTO=none IPADDR=XXX.XXX.XXX.XXX PREFIX=XX ONBOOT=no |
/etc/sysconfig/network-scripts/ifcfg-ethX
TYPE=Ethernet BOOTPROTO=none DEVICE=ethX ONBOOT=yes |
Information
If you want to use the NIC switching mode to share the same physical connection between two virtual interfaces (one that bundles physical interfaces and the other that bundles tagged VLAN interfaces), you need to set up ifcfg-ethX the same as Setup 1 using the same IP address (IPADDR=) and other values. For example, if sha0 bundles eth0 and eth1, and sha1 bundles eth0.2 and eth1.2, configure ifcfg-eth0 according to ifcfg-ethX in Setup 1, not according to that shown in Setup 3.
For RHEL9
Redundant network methods | Tagged VLAN disabled | Tagged VLAN enabled | |
|---|---|---|---|
NIC switching mode (IPv4) | Primary interface | ||
Secondary interface | |||
Virtual NIC mode | |||
Note
For RHEL 7 or later, the naming conventions for NIC names are changed to generate device names based on the hardware locations of NICs (Predictable Network Interface Names).
If you need to use traditional interface name (ethX) for RHEL6 or earlier, set the traditional interface name (ethX) in "connection.id" and “connection.interface-name” with the nmcli connection modify command. Also, to prevent device names of physical NICs from changing to unexpected names, set the MAC address to “802-3-ethernet.mac-address” using the nmcli connection modify command.
The tagged VLAN interface name is available only by "interface name.VLAN-ID" format, such as eth0.1.
In the cluster environment of physical IP takeover II, set connection.autoconnect to "no" with the nmcli connection modify command.
Set the following parameters with the “nmcli connection modify” command.
ipv4.method: "manual"
ipv4.addresses: "XXX.XXX.XXX.XXX/XX"
connection.autoconnect: "yes"
After configuration, confirm that the following parameters are set for ethX by using the nmcli connection show command.
connection.type: "802-3-ethernet"
connection.interface-name: "ethX"
Set the following parameters with the “nmcli connection modify” command.
ipv4.method: "manual"
ipv4.addresses: "XXX.XXX.XXX.XXX/XX"
connection.autoconnect: "no"
After configuration, confirm that the following parameters are set for ethX by using the nmcli connection show command.
connection.type: "802-3-ethernet"
connection.interface-name: "ethX"
Set the following parameters with the “nmcli connection modify” command.
ipv4.method: "disabled"
ipv4.addresses: ""
connection.autoconnect: "yes"
After configuration, confirm that the following parameters are set for ethX by using the nmcli connection show command.
connection.type: "802-3-ethernet"
connection.interface-name: "ethX"
Create a VLAN interface using the nmcli connection add command.
# /usr/bin/nmcli connection add type vlan con-name ethX.Y ifname ethX.Y vlan.parent ethX vlan.id Y
Set the following parameters for the created ethX.Y using the nmcli connection modify command.
ipv4.method: "manual"
ipv4.addresses: "XXX.XXX.XXX.XXX/XX"
connection.autoconnect: "yes"
Set the following parameters with the “nmcli connection modify” command.
ipv4.method: "disabled"
ipv4.addresses: ""
connection.autoconnect: "yes"
After configuration, confirm that the following parameters are set for ethX by using the nmcli connection show command.
connection.type: "802-3-ethernet"
connection.interface-name: "ethX"
Create a VLAN interface using the nmcli connection add command.
# /usr/bin/nmcli connection add type vlan con-name ethX.Y ifname ethX.Y vlan.parent ethX vlan.id Y
Set the following parameters for the created ethX.Y using the nmcli connection modify command.
ipv4.method: "manual"
ipv4.addresses: "XXX.XXX.XXX.XXX/XX"
connection.autoconnect: "no"
Set the following parameters with the "nmcli connection modify" command.
connection.interface-name: "ethX"
connection.autoconnect: "yes"
ipv4.method: "disabled"
ipv6.method: "disabled"
After configuration, confirm that the following parameters are set for the ethX with the "nmcli connection show" command.
connection.type: "802-3-ethernet"
connection.interface-name: "ethX"
Information
If you want to use the NIC switching mode to share the same physical connection between two virtual interfaces (one that bundles physical interfaces and the other that bundles tagged VLAN interfaces), you need to set up ifcfg-ethX the same as Setup 1 using the same IP address (ipv4.addresses:) and other values. For example, if sha0 bundles eth0 and eth1, and sha1 bundles eth0.2 and eth1.2, configure eth0 according to ethX in Setup 1, not according to that shown in Setup 3.
(2) Verification of the physical interface
Verify if the physical interface is inserted into the system using the ip command.
Also, if the physical interface is UP, check whether "LOWER_UP" is displayed. If "LOWER_UP" is not displayed, the links might be down on the interface. Check the cable switch and HUB speed settings. Use the ethtool command to check the link state.
# ip addr show
eth0 <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet 192.168.70.2/24 brd 192.168.70.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::xxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
eth1 <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet 192.168.71.2/24 brd 192.168.71.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::xxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever |
In the above example, it is possible to use eth0 and eth1. For details on the ip command, refer to the Linux manual.
Information
When using Tagged VLAN, ensure that the NIC supports tagged VLAN functionality (IEEE 802.1Q). In addition, in a Redundant Line Control function, the effective range of VLAN-ID which can be specified is from 1 to 4094.
(3) Checking the name service
When using name services such as DNS or NIS, define keywords such as hosts in /etc/nsswitch.conf file to first refer to the local file. This allows to solve the address even if the DNS, NIS or LDAP sever is unreachable. The following is an example of /etc/nsswitch.conf.
# # /etc/nsswitch.conf # # An example Name Service Switch config file. This file should be # sorted with the most-used services at the beginning. # # The entry '[NOTFOUND=return]' means that the search for an # entry should stop if the search in the previous entry turned # up nothing. Note that if the search failed due to some other reason # (like no NIS server responding) then the search continues with the # next entry. # # Legal entries are: # # nisplus or nis+ Use NIS+ (NIS version 3) # nis or yp Use NIS (NIS version 2), also called YP # dns Use DNS (Domain Name Service) # files Use the local files # db Use the local database (.db) files # compat Use NIS on compat mode # hesiod Use Hesiod for user lookups # [NOTFOUND=return] Stop searching if not found so far # # To use db, put the "db" in front of "files" for entries you want to be # looked up first in the databases # # Example: #passwd: db files nisplus nis #shadow: db files nisplus nis #group: db files nisplus nis passwd: files shadow: files group: files #hosts: db files nisplus nis dns hosts: files dns ..... |
Information
If the host name rather than the IP address is used in setting GLS, enable the hostname resolution function (set by hanetparam -h), which allows you to change the host name to the IP address using only the /etc/hosts file without depending on the /etc/nsswitch.conf file setting.
(4) Route configuration
Route configuration is described below.
Default gateway configuration
For RHEL8
Define the default gateway address (GATEWAY) in the "/etc/sysconfig/network-scripts/ifcfg-ethX" file.
/etc/sysconfig/network-scripts/ifcfg-ethX
DEVICE=ethX (omitted) GATEWAY=192.168.1.254 |
Information
The default gateway device (GATEWAYDEV) can not be configured for a physical interface bound with NIC switching mode.
When defining the default gateway (GATEWAY) in the "/etc/sysconfig/network-scripts/ifcfg-ethX" file in the NIC switching mode, add the same configuration of GATEWAY in the configuration files of all NICs bound by GLS. Note that if different configurations of GATEWAY are defined in the "/etc/sysconfig/network" file and the "/etc/sysconfig/network-scripts/ifcfg-ethX" file, the configuration in the "/etc/sysconfig/network-scripts/ifcfg-ethX" file has a priority.
# /opt/FJSVhanet/usr/sbin/hanetconfig print [IPv4,Patrol / Virtual NIC] Name Hostname Mode Physical ipaddr Interface List +-----------+---------------+----+-----------------+-------------- sha0 192.168.1.10 e eth1,eth2 # cat /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 (omitted) GATEWAY=192.168.1.254 # cat /etc/sysconfig/network-scripts/ifcfg-eth2 DEVICE=eth2 (omitted) GATEWAY=192.168.1.254 |
If you do not use the "/etc/sysconfig/network" file in the environment where Virtual NIC mode is used, configure the route in the "/etc/sysconfig/network-scripts/ifcfg-shaX" file. You do not need to configure it in the "/etc/sysconfig/network-scripts/ifcfg-ethX" file in the same way as NIC switching mode. For details, see "3.3.3 Virtual NIC mode".
For RHEL9
Execute the following command to set the default gateway.
# /usr/bin/nmcli connection modify filename /etc/NetworkManager/system-connections/ethX.nmconnection +ipv4.gateway "192.168.1.254" |
Static route configuration
For RHEL8
NIC switching mode
To configure a static route on a routing table, use the nmcli command.
Apply the same setting for both physical interfaces (ethX, ethY) bundled by NIC switching mode.
Example: Setting static route to ethX and ethY
#/usr/bin/nmcli connection modify filename /etc/sysconfig/network-scripts/ifcfg-ethX +ipv4.routes "192.168.100.0/24 192.168.40.10" #/usr/bin/nmcli connection modify filename /etc/sysconfig/network-scripts/ifcfg-ethY +ipv4.routes "192.168.100.0/24 192.168.40.10" |
For information about configure static routes, refer to "Linux documentation".
When using source routing, the above configuration is not required.
Make sure that use "2.8.2 User command execution function" and execute the nmcli command to add or delete the setting of source routing.
Example: /etc/opt/FJSVhanet/script/interface/shaX
#!/bin/sh # # All Rights Reserved, Copyright (c) FUJITSU LIMITED 2004 # #ident "%W% %G% %U% - FUJITSU" # (omitted) if [ $ADDRESS_FAMILY = "inet" ] then case "$1" in 'activate') # # Activate interface # case "$2" in 'before') # # script before activate interface # # echo "execute script before activate interface on" $INTERFACE > /dev/console #if [ ! $INTERFACE = "ethX" ] #then # ifconfig $INTERFACE #else # ifconfig $INTERFACE #fi ;; 'after') # # script after activate interface # IFNAME=`/usr/sbin/ip addr show | /usr/bin/grep " 192.168.40.1/" | \ /usr/bin/sed -e "s/.* //"` /usr/bin/nmcli connection modify \ filename /etc/sysconfig/network-scripts/ifcfg-$IFNAME \ +ipv4.routes "192.168.100.0/24 192.168.40.10 src=192.168.40.1" /usr/bin/nmcli device modify $IFNAME \ +ipv4.routes "192.168.100.0/24 192.168.40.10 src=192.168.40.1" (omitted) 'inactivate') # # inactivate interface # case "$2" in 'before') # # script before inactivate interface # IFNAME=`/usr/sbin/ip addr show | /usr/bin/grep " 192.168.40.1/" | \ /usr/bin/sed -e "s/.* //"` /usr/bin/nmcli connection modify \ filename /etc/sysconfig/network-scripts/ifcfg-$IFNAME \ -ipv4.routes "192.168.100.0/24 192.168.40.10 src=192.168.40.1" /usr/bin/nmcli device modify $IFNAME \ -ipv4.routes "192.168.100.0/24 192.168.40.10 src=192.168.40.1" (omitted) |
Virtual NIC mode and GS linkage mode
To configure a static route on a routing table, define the configuration on the /etc/sysconfig/network-scripts/route-Interface name file.
Make sure that configure it for the virtual interface (route-shaX).
Example: Setting BOOTPROTO=none to ifcfg-shaX
/etc/sysconfig/network-scripts/route-shaX
GATEWAY0=192.168.40.10 NETMASK0=255.255.255.0 ADDRESS0=192.168.100.0 |
When using source routing, only the virtual NIC mode supports source routing using the /etc/sysconfig/network-scripts/rule-shaX file.
For details, refer to "Linux documentation".
For RHEL9
NIC switching mode
To configure a static route on a routing table, use the nmcli command.
Apply the same setting for both physical interfaces (ethX, ethY) bundled by NIC switching mode.
Example: Setting static route to ethX.nmconnection
#/usr/bin/nmcli connection modify filename /etc/NetworkManager/system-connections/ethX.nmconnection +ipv4.routes "192.168.100.0/24 192.168.40.10" #/usr/bin/nmcli connection modify filename /etc/NetworkManager/system-connections/ethX.nmconnection +ipv4.routes "192.168.100.0/24 192.168.40.10" |
When using source routing, the above configuration is not required.
Make sure that use "2.8.2 User command execution function" and execute the nmcli command to add or delete the setting of source routing.
Example: /etc/opt/FJSVhanet/script/interface/shaX
#!/bin/sh # # All Rights Reserved, Copyright (c) FUJITSU LIMITED 2004 # #ident "%W% %G% %U% - FUJITSU" # (omitted) if [ $ADDRESS_FAMILY = "inet" ] then case "$1" in 'activate') # # Activate interface # case "$2" in 'before') # # script before activate interface # # echo "execute script before activate interface on" $INTERFACE > /dev/console #if [ ! $INTERFACE = "ethX" ] #then # ifconfig $INTERFACE #else # ifconfig $INTERFACE #fi ;; 'after') # # script after activate interface # IFNAME=`/usr/sbin/ip addr show | /usr/bin/grep " 192.168.40.1/" | \ /usr/bin/sed -e "s/.* //"` /usr/bin/nmcli connection modify \ filename /etc/NetworkManager/system-connections/$IFNAME.nmconnection \ +ipv4.routes "192.168.100.0/24 192.168.40.10 src=192.168.40.1" /usr/bin/nmcli device modify $IFNAME \ +ipv4.routes "192.168.100.0/24 192.168.40.10 src=192.168.40.1" (omitted) 'inactivate') # # inactivate interface # case "$2" in 'before') # # script before inactivate interface # IFNAME=`/usr/sbin/ip addr show | /usr/bin/grep " 192.168.40.1/" | \ /usr/bin/sed -e "s/.* //"` /usr/bin/nmcli connection modify \ filename /etc/NetworkManager/system-connections/$IFNAME.nmconnection \ -ipv4.routes "192.168.100.0/24 192.168.40.10 src=192.168.40.1" /usr/bin/nmcli device modify $IFNAME \ -ipv4.routes "192.168.100.0/24 192.168.40.10 src=192.168.40.1" (omitted) |
Virtual NIC mode
To configure a static route on a routing table, set the following parameter to the virtual interface with the "nmcli connection modify" command.
ipv4.routes: "192.168.100.0/24 192.168.40.10"
When using source routing, set the following parameter to the virtual interface with the "nmcli connection modify" command.
ipv4.routes: "192.168.100.0/24 192.168.40.10 src=192.168.40.1"
Note
This version does not support IPv6 addresses for the Fast switching mode.
When using an IPv4 address
To create backup of the physical interface settings (the "/etc/sysconfig/network-scripts/ifcfg-ethX" or "/etc/sysconfig/network/ifcfg-ethX" file), the file name must begin with names other than "ifcfg-".
(e.g. bak_ifcfg-ethX)
If the file name begins with "ifcfg-", OS might recognize the interface as an interface to be activated during system startup.
Define the IPv4 address (virtual IP address, physical IP address, logical virtual interface, takeover virtual IP address) and a host name configured in the redundant line control function in the /etc/hosts file. These host names must be specified in the /etc/hosts file even if no host names but IP addresses are directly specified in environment definitions.
Note
This version does not support IPv6 addresses for the NIC switching mode.
When using an IPv4 address
To create backup of the physical interface settings (the "/etc/sysconfig/network-scripts/ifcfg-ethX" or "/etc/sysconfig/network/ifcfg-ethX" file), the file name must begin with names other than "ifcfg-".
(e.g. bak_ifcfg-ethX)
If the file name begins with "ifcfg-", OS might recognize the interface as an interface to be activated during system startup.
Define the IPv4 address (virtual IP address, physical IP address, monitored IP addresses to be specified in monitoring destination information) and a host name configured in the redundant line control function in the /etc/hosts file.These host names must be specified in the /etc/hosts file even if no host names but IP addresses are directly specified in environment definitions.
For RHEL8
Edit the setting (/etc/sysconfig/network-scripts/ifcfg-ethX file) for the physical interfaces that the GLS bundles as follows:
The descriptions vary depending the OS. See "Table 3.10 Configuration of physical interface" for the differences in descriptions.
Item | Value (Example) | Description |
|---|---|---|
TYPE | Ethernet | Specify the device type. Set "Ethernet". |
BOOTPROTO | none | Specify the protocol when getting the IP address. Set "none" or "static". |
DEVICE | ethX | Specify the device name. Set "ethX". |
ONBOOT | yes | Select whether to start the physical interface on startup of the OS. Set "yes". |
MTU | 9000 | Specify the length of MTU. When specifying the length of MTU, set the same value for the configuration file (ifcfg-ethX) of the primary interface and the secondary interface, and for the virtual interface configuration file (ifcfg-shaX). |
An example is shown below.
Example of /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE=Ethernet BOOTPROTO=none DEVICE=ethX ONBOOT=yes |
To create backup of the physical interface settings (the "/etc/sysconfig/network-scripts/ifcfg-ethX" file), the file name must begin with names other than "ifcfg-".
(e.g. bak_ifcfg-ethX)
If the file name begins with "ifcfg-", OS might recognize the interface as an interface to be activated during system startup.
For RHEL9
Set the following parameters to the physical interfaces with the nmcli command.
connection.interface-name: "ethX"
connection.type: "802-3-ethernet"
connection.autoconnect: "yes"
802-3-ethernet.mtu: the same value for the configuration of the primary, secondary and virtual interface.
ipv4.method: "disabled" or "manual"
Point
An address such as IPADDR is not necessary. Do not set it.
If you need to prevent device names of physical NICs from changing to unexpected names in an environment where traditional interface names (ethX) for RHEL6 or earlier are used, describe the definition of "HWADDR=<MAC address>" in the settings for the physical interfaces (the /etc/sysconfig/network-scripts/ifcfg-ethX file).
When modifying MTU, make sure to set 1280 or more.
To create backup of the physical interface settings (the "/etc/sysconfig/network-scripts/ifcfg-ethX" or "/etc/sysconfig/network/ifcfg-ethX" file), the file name must begin with names other than "ifcfg-".
(e.g. bak_ifcfg-ethX)
If the file name begins with "ifcfg-", OS might recognize the interface as an interface to be activated during system startup.
Define the IPv4 address (virtual IP address, physical IP address, logical virtual interface, takeover virtual IP address) and a host name in /etc/hosts file. These host names must be specified in the /etc/hosts file even if no host names but IP addresses are directly specified in environment definitions.
Before defining a virtual interface, the physical interface you are going to apply must be in active state and be sure the IPv4 address is assigned. (When the system is RHEL, in the file /etc/sysconfig/network-scripts/ifcfg-ethX, define "ONBOOT=yes" and "IPADDR=X.X.X.X" then reboot the system.)
Be sure to define the virtual gateway in the /etc/sysconfig/network-scripts/route-shaX file to set the static route information.
You do not need to configure the routing daemon for the network setting when using this method.
