(1) Physical interface settings
Set up physical interfaces. The physical interface settings vary depending on redundant network methods and operating system.
See the following Table 3.7 Physical interface settings.
Redundant network methods | Operating system | ||||
|---|---|---|---|---|---|
RHEL4/RHEL5 | SLES9/SLES10 | ||||
Tagged VLAN disabled | Tagged VLAN enabled | Tagged VLAN disabled | Tagged VLAN enabled | ||
Fast switching mode (IPv4) | |||||
Fast switching mode (IPv6) | |||||
Fast switching mode (Dual) | |||||
NIC switching mode (IPv4) | Primary interface | ||||
Secondary interface | |||||
NIC switching mode (IPv6) | Primary interface | ||||
Secondary interface | |||||
NIC switching mode (Dual) | Primary interface | ||||
Secondary interface | |||||
GS linkage mode | Not supported | Not supported | Not supported | ||
Note
When a operating system is RHEL4 or RHEL5, to specify "HWADDR=XX:XX:XX:XX:XX:XX" for the GLS physical interface settings (the "/etc/sysconfig/network-scripts/ifcfg-ethX" file), add "HOTPLUG=no" to the settings. When the system is RHEL5, SLES9, SLES10, edit /etc/udev/rules.d/60-net.rules file, /etc/hotplug/net.agent file or /etc/udev/rules.d/31-network.rules file to invalidate the network hotplug function of the interface (sha*,eth*.*).
Information
If "HOTPLUG=no" is set when the operating system is RHEL4 or RHEL5, it will not disable the PCI Hot Plug. Active maintenance of NIC (PCI cards) can be performed for the physical interface where "HOTPLUG=no" is set.
/etc/sysconfig/network-scripts/ifcfg-ethX
DEVICE=ethX BOOTPROTO=static HWADDR=XX:XX:XX:XX:XX:XX HOTPLUG=no BROADCAST=XXX.XXX.XXX.XXX IPADDR=XXX.XXX.XXX.XXX NETMASK=XXX.XXX.XXX.XXX NETWORK=XXX.XXX.XXX.XXX ONBOOT=yes TYPE=Ethernet |
/etc/sysconfig/network-scripts/ifcfg-ethX
DEVICE=ethX BOOTPROTO=static HWADDR=XX:XX:XX:XX:XX:XX HOTPLUG=no ONBOOT=yes TYPE=Ethernet |
/etc/sysconfig/network-scripts/ifcfg-ethX
DEVICE=ethX BOOTPROTO=static HWADDR=XX:XX:XX:XX:XX:XX HOTPLUG=no ONBOOT=yes TYPE=Ethernet |
/etc/sysconfig/network-scripts/ifcfg-ethX.Y
DEVICE=ethX.Y BOOTPROTO=static BROADCAST=XXX.XXX.XXX.XXX IPADDR=XXX.XXX.XXX.XXX NETMASK=XXX.XXX.XXX.XXX NETWORK=XXX.XXX.XXX.XXX ONBOOT=yes |
Information
If you want to use the NIC switching mode to share the same physical connection between two virtual interfaces, one bundles physical interfaces and the other 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.
/etc/sysconfig/network-scripts/ifcfg-ethX
DEVICE=ethX BOOTPROTO=static HWADDR=XX:XX:XX:XX:XX:XX HOTPLUG=no ONBOOT=yes TYPE=Ethernet |
/etc/sysconfig/network-scripts/ifcfg-ethX.Y
DEVICE=ethX.Y BOOTPROTO=static ONBOOT=yes |
/etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX
BOOTPROTO='static' BROADCAST='XXX.XXX.XXX.XXX' IPADDR='XXX.XXX.XXX.XXX' NETMASK='XXX.XXX.XXX.XXX' NETWORK='XXX.XXX.XXX.XXX' STARTMODE='onboot' PERSISTENT_NAME='ethX' UNIQUE='XXXXXXXXXXXXXXXX' _nm_name='bus-pci-XXXX:XX:XX.X' |
Note
Edit the setup file (/etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX) that is corresponding to the MAC address "XX:XX:XX:XX:XX:XX" of physical interfaces for GLS. Do not create the configuration file of /etc/sysconfig/network/ifcfg-ethX.
In certain machine environment, it happens that the interface names of your network devices switch from one boot to another. If you want to give your interfaces persistent names, add "PERSISTENT_NAME=ethX" in /etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX. Set ethX to the number of more than the implementable network interfaces (more than 300 is recommended). See also ifup(8)'s online manual(man ifup).
The "UNIQUE=" and "_nm_name=" values are automatically set in the setup file. Users are not supposed to change the values.
/etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX
BOOTPROTO='static' STARTMODE='onboot' PERSISTENT_NAME='ethX' UNIQUE='XXXXXXXXXXXXXXXX' _nm_name='bus-pci-XXXX:XX:XX.X' |
Note
Edit the setup file (/etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX) that is corresponding to the MAC address "XX:XX:XX:XX:XX:XX" of physical interfaces for GLS. Do not create the configuration file of /etc/sysconfig/network/ifcfg-ethX.
In certain machine environment, it happens that the interface names of your network devices switch from one boot to another. If you want to give your interfaces persistent names, add "PERSISTENT_NAME=ethX" in /etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX. Set ethX to the number of more than the implementable network interfaces (more than 300 is recommended). See also ifup(8)'s online manual(man ifup).
The "UNIQUE=" and "_nm_name=" values are automatically set in the setup file. Users are not supposed to change the values.
/etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX
BOOTPROTO='static' STARTMODE='onboot' PERSISTENT_NAME='ethX' UNIQUE='XXXXXXXXXXXXXXXX' _nm_name='bus-pci-XXXX:XX:XX.X' |
Note
Edit the setup file (/etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX) that is corresponding to the MAC address "XX:XX:XX:XX:XX:XX" of physical interfaces for GLS. Do not create the configuration file of /etc/sysconfig/network/ifcfg-ethX and /etc/sysconfig/network/ifcfg-ethX.Y.
In certain machine environment, it happens that the interface names of your network devices switch from one boot to another. If you want to give your interfaces persistent names, add "PERSISTENT_NAME=ethX" in /etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX. Set ethX to the number of more than the implementable network interfaces (more than 300 is recommended). See also ifup(8)'s online manual(man ifup).
The "UNIQUE=" and "_nm_name=" values are automatically set in the setup file. Users are not supposed to change the values.
/etc/opt/FJSVhanet/script/conf/vlan_if.conf
DEVICE<n>=ethX VLANID<n>=Y IPADDR<n>=XXX.XXX.XXX.XXX NETMASK<n>=XXX.XXX.XXX.XXX TYPE<n>=vlan |
Note
The above setup file does not exist after GLS installation. If you use tagged VLANs on SLES9, create the setup file.
In the setup file, a string from sharp "#" to line feed indicates a comment.
Add alphanumerical characters and/or periods "." after equal "=" for each parameter setup value. If you specify values other than alphanumerical characters and/or periods ".", the setting will be disabled. For example, such characters are set in the second line, the second line and after will be disabled.
"<n>" of DEVICE<n>=" and "VLANID<n>=" must begin with "0" in the setup file. If you set multiple tagged VLAN interfaces, specify a sequential range of numbers beginning with "0" (0, 1, 2, 3, 4, ...).
Example
# Tagged VLAN interface eth1.2 DEVICE0=eth1 VLANID0=2 IPADDR0=192.168.20.10 NETMASK0=255.255.255.0 TYPE0=vlan # Tagged VLAN interface eth2.5 DEVICE1=eth2 VLANID1=5 IPADDR1=192.168.50.10 NETMASK1=255.255.255.0 TYPE1=vlan ..... |
/etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX
BOOTPROTO='static' STARTMODE='onboot' PERSISTENT_NAME='ethX' UNIQUE='XXXXXXXXXXXXXXXX' _nm_name='bus-pci-XXXX:XX:XX.X' |
Note
Edit the setup file (/etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX) that is corresponding to the MAC address "XX:XX:XX:XX:XX:XX" of physical interfaces for GLS. Do not create the configuration file of /etc/sysconfig/network/ifcfg-ethX and /etc/sysconfig/network/ifcfg-ethX.Y.
In certain machine environment, it happens that the interface names of your network devices switch from one boot to another. If you want to give your interfaces persistent names, add "PERSISTENT_NAME=ethX" in /etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX:XX. Set ethX to the number of more than the implementable network interfaces (more than 300 is recommended). See also ifup(8)'s online manual(man ifup).
The "UNIQUE=" and "_nm_name=" values are automatically set in the setup file. Users are not supposed to change the values.
/etc/opt/FJSVhanet/script/conf/vlan_if.conf
DEVICE<n>=ethX VLANID<n>=Y IPADDR<n>= NETMASK<n>= TYPE<n>=vlan |
Information
For the secondary interface, no value must be set for "IPADDR<n>=" and "NETMASK<n>=".
Example: IPADDR0=(LF)
Note
The above setup file does not exist after GLS installation. If you use tagged VLANs on SLES9, create the setup file.
In the setup file, a string from sharp "#" to line feed indicates a comment.
Add alphanumerical characters and/or periods "." after equal "=" for each parameter setup value. If you specify values other than alphanumerical characters and/or periods ".", the setting will be disabled. For example, such characters are set in the second line, the second line and after will be disabled.
"<n>" of DEVICE<n>=" and "VLANID<n>=" must begin with "0" in the setup file. If you set multiple tagged VLAN interfaces, specify a sequential range of numbers beginning with "0" (0, 1, 2, 3, 4, ...).
Example
# Tagged VLAN interface eth1.2 DEVICE0=eth1 VLANID0=2 IPADDR0=192.168.20.10 NETMASK0=255.255.255.0 TYPE0=vlan # Tagged VLAN interface eth2.5 DEVICE1=eth2 VLANID1=5 IPADDR1=192.168.50.10 NETMASK1=255.255.255.0 TYPE1=vlan # Tagged VLAN interface eth3.2 DEVICE2=eth3 VLANID2=2 IPADDR2= NETMASK2= TYPE2=vlan # Tagged VLAN interface eth4.5 DEVICE3=eth4 VLANID3=5 IPADDR3= NETMASK3= TYPE3=vlan ..... |
(2) Verification of the physical interface
Verify if the physical interface is inserted into the system using ifconfig command.
Also, if the physical interface is UP, check whether it is marked as "RUNNING". If "RUNNING" 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.
# ifconfig -a
eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:192.168.70.2 Bcast:192.168.70.255 Mask:255.255.255.0
inet6 addr: fe80::xxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2140 errors:0 dropped:0 overruns:0 frame:0
TX packets:2140 errors:0 dropped:0 overruns:0 carrier:0
collisions:22 txqueuelen:1000
RX bytes:278285 (271.7 KiB) TX bytes:273656 (267.2 KiB)
Base address:0xec80 Memory:d2fc0000-d2fe0000
eth1 Link encap:Ethernet HWaddr 0xx:xx:xx:xx:xx:xx
inet addr:192.168.71.2 Bcast:192.168.71.255 Mask:255.255.255.0
inet6 addr: fe80::xxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2138 errors:0 dropped:0 overruns:0 frame:0
TX packets:2118 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:278492 (271.9 KiB) TX bytes:273666 (267.2 KiB)
Base address:0xecc0 Memory:d2fe0000-d3000000 |
In the above example, it is possible to use eth0 and eth1. For details regarding ifconfig 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) IPv6 RA daemon configuration
GLS supports radvd(router advertisement daemon for IPv6) for RA (router advertisement) daemon. To use IPv6(dual) on Fast switching mode, you must start RA daemon on the host running GLS in order to transmit RA from virtual interfaces. Other than this purpose, RA daemon is not necessary. The following describes configuration procedure.
radvd configuration
Define the configuration in /etc/radvd.conf
When transmitting network information (network fec0:1::, prefix length 64) from sha0 with RA(router advertisement), define the configuration description as shown below.
In addition, the difference in the version of radvd needs to define the following kernel parameters.
For details on radvd configuration, refer to radvd manual.
RHEL (/etc/sysctl.conf):
net.ipv6.conf.all.forwarding=1 |
SLES (/etc/sysconfig/sysctl):
IPV6_FORWARD=yes |
/etc/radvd.conf
interface sha0
{
AdvSendAdvert on; # Sending router advertisements
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
prefix fec0:1::0/64 # Sending Prefix fec0:1::0/64 from sha0
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
}; |
Configure radvd to startup during system startup (when run level is 2, 3, or 5).
RHEL: # chkconfig --level 235 radvd on SLES: # chkconfig --set radvd 235 |
Verify radvd is configured to startup on run level 2, 3, 5.
RHEL: # chkconfig --list radvd radvd 0:off 1:off 2:on 3:on 4:off 5:on 6:off SLES: # chkconfig --list radvd radvd 0:off 1:off 2:on 3:on 4:off 5:on 6:off |
(5) Route configuration
Route configuration of IPv4 is described below.
Configure IPv6 by using the user command function, not the network configuration file for the operating system. In the configuration file of the user command function, define the operating system command assigning the route of IPv6 to be executed after activation of the IP address. For details, refer to the Linux manual (ip(6), route(8) and so on).
Default gateway configuration
For RHEL:
Define the default gateway address (GATEWAY) in the "/etc/sysconfig/network" file.
/etc/sysconfig/network
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] 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 |
For SLES:
Define the default gateway address (default) in the "/etc/sysconfig/network/routes" file.
default 192.168.1.254 - - |
Static route configuration
To configure static route on a routing table, define the configuration on /etc/sysconfig/network-scripts/route-ethX. In addition, settings are required for physical interface bound with NIC switching mode.
RHEL (/etc/sysconfig/network-scripts/route-ethX):
GATEWAY0=192.168.40.10 NETMASK0=255.255.255.0 ADDRESS0=192.168.100.0 |
SLES (/etc/sysconfig/network/routes):
192.168.100.0 192.168.40.10 255.255.255.0 ethX |
(6) IPv6 module configuration
Supporting IPv6(dual) on GLS Fast switching mode or NIC switching mode, it is required to load IPv6 module on Linux. See the following for configuring IPv6 module.
Loading ipv6 module (RHEL only)
Configure /etc/sysconfig/network to use IPv6. Ignore the tunneling configuration, since GLS does not support tunneling feature.
NETWORKING_IPV6=yes IPV6TO4INIT=no |
Reboot the system.
# /sbin/shutdown -r now |
Verify IPv6 module is loaded.
# lsmod | grep ipv6 ipv6 662756 10 |
(7) Tagged VLAN configuration
To use tagged VLAN interfaces in Fast switching mode or NIC switching mode, set up the tagged VLANs as follows:
When the system is RHEL (RHEL4 only):
Configure /etc/sysconfig/network to use tagged VLAN.
VLAN=yes |
Reboot the system.
# /sbin/shutdown -r now |
Verify tagged VLAN module is loaded.
# lsmod | grep 8021q 8021q 18760 1 |
When the system is SLES (SLES9 and SLES10 only):
Copy the script file.
# cd /etc/opt/FJSVhanet/script/system # cp -p rc_event.slesvlan.sam rc_event |
Reboot the system.
# /sbin/shutdown -r now |
Note
The "-p" option of the "cp" command is required to take over permission of the script file. To copy the script file, be sure to use the "-p" option. You do not need to edit the "/etc/opt/FJSVhanet/script/system/rc_event" script file copied.
Also, to cancel the tagged VLAN interfaces, delete the script file using the following steps:
Delete the script file.
# cd /etc/opt/FJSVhanet/script/system # rm rc_event |
Reboot the system.
# /sbin/shutdown -r now |
Information
If you are using SLES9 and SLES10 for the operating system, it is necessary to create the "/etc/opt/FJSVhanet/script/conf/vlan_if.conf" setup file to use tagged VLAN interfaces. If you have deleted the script file, it is not necessary to delete the "/etc/opt/FJSVhanet/script/conf/vlan_if.conf" setup file. Deleting the above script file will disable the setup file.
Note
The "/etc/opt/FJSVhanet/script/conf/vlan_if.conf" setup file and the "/etc/opt/FJSVhanet/script/system/rc_event" script file are not backed up or restored. They are different than the GLS configuration file that can be backed up and restored with the "hanetbackup" and "hanetrestore" commands. You need to back up or restore the setup and script files if necessary.
(8) Network hotplug configuration(RHEL5, SLES9, SLES10 only)
To invalidate the network hotplug function of the interface (sha*,eth*.*), edit /etc/udev/rules.d/60-net.rules file, /etc/hotplug/net.agent file or /etc/udev/rules.d/31-network.rules file.
When the system is RHEL5:
To invalidate the network hotplug function of the interface (sha*), edit /etc/udev/rules.d/60-net.rules file.
SUBSYSTEM=="net", ENV{INTERFACE}=="sha*", GOTO="skipgls" ACTION=="add", SUBSYSTEM=="net", IMPORT{program}="/lib/udev/rename_device" SUBSYSTEM=="net", RUN+="/etc/sysconfig/network-scripts/net.hotplug" LABEL="skipgls" |
Note
When PTF of RHEL is applied, the "/etc/udev/rules.d/60-net.rules" file may return to the content before it is edited. Edit the file after application.
When the system is SLES9:
To invalidate the network hotplug function of the interface (sha*,eth*.*), edit /etc/hotplug/net.agent file.
. . . . . . . .
case $ACTION in
add|register)
case $INTERFACE in
# interfaces that are registered after being "up" (?)
#ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*)
ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|sha*|eth*.*)
debug_mesg assuming $INTERFACE is already up
exit 0
;;
. . . . . . . .
remove|unregister)
case $INTERFACE in
# interfaces that are registered after being "up" (?)
#ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*)
ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|sha*|eth*.*)
debug_mesg assuming $INTERFACE is already up
exit 0
;;
. . . . . . . . |
Note
Communication become impossible when this setting is not configured. Make sure to configure it when you use GLS.
Configure the above-mentioned setting again if the OS's patch or hotplug's patch rewrites /etc/hotplug/net.agent file.
Restore /etc/hotplug/net.agent file, if you uninstall GLS to stop the operation.
When the system is SLES10:
To invalidate the network hotplug function of the interface (sha*,eth*.*), edit /etc/udev/rules.d/31-network.rules file.
. . . . . . . .
# Network interfaces will be set up automatically by ifup if they are configured
# and service network is active.
# We also call ifdown although the interface vanished already, because there
# might be things to clean up. (E.g. killing ifplugd)
# There are interfaces which are created with ifup. We have to ignore these
# interfaces here.
SUBSYSTEM=="net", ENV{INTERFACE}=="ppp*|vlan*|modem*|sha*|eth*.*", GOTO="skip_ifup"
SUBSYSTEM=="net", ACTION=="add", RUN+="/sbin/ifup $env{INTERFACE} -o hotplug"
SUBSYSTEM=="net", ACTION=="remove", RUN+="/sbin/ifdown %k -o hotplug"
LABEL="skip_ifup"
. . . . . . . . |
Common settings between IPv4 and IPv6
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.
When using an IPv4 address
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.)
When using an IPv6 address
Define the IPv6 address (logical virtual interface, takeover virtual IP address) and a host name in /etc/hosts file.
Before defining a virtual interface, the physical interface you are going to apply must be in active state and be sure the IPv6 link-local address is assigned. (When the system is RHEL, in the file /etc/sysconfig/network-scripts/ifcfg-ethX, define "ONBOOT=yes" and in the /etc/sysconfig/network file, define "NETWORKING_IPV6=yes" then reboot the system.)
You must start the radvd daemon on 2 or more servers running as Fast switching mode in order to set the stateless address auto-configuration. Note that when starting up radvd on multiple servers, synchronize the prefix data of the virtual interfaces defined in /etc/radvd.conf between the servers. An example of setting a /etc/radvd.conf file when using a Linux server as an IPv6 router is shown below. In addition, depending on the version of radvd, kernel parameter(net.ipv6.conf.all.forwarding=1) must be defined in /etc/sysctl.conf file. For details on this topic, see the manual of radvd.conf(5) and radvd(8).
/etc/radvd.conf
interface sha0
{
AdvSendAdvert on; # Sending router advertisements
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
prefix fec0:1::0/64 # Sending Prefix fec0:1::0/64 from sha0
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
}; |
When setting stateless address auto-configuration against the physical interface(ethX) using Fast switching mode, start up radvd on either of the servers or provide IPv6 router on the same network. Additionally, stateless address auto-configuration on the physical interface (ethX) does not apply on the server that has kernel configuration (net.ipv6.conf.all.forwarding=1) for starting up radvd. In such case, after starting radvd, use sysctl command to reconfigure the kernel parameter. For details, refer to sysctl(8) manual.
# sysctl -w net.ipv6.conf.all.forwarding=0 |
Common settings between IPv4 and IPv6
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.
When using an IPv4 address
Define the IPv4 address (virtual IP address, physical IP address, monitored IP addresses to be specified in monitoring destination information) 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 booting an OS, the primary interface (physical interface) you are going to apply must in active state and make sure IPv4 address is assigned. (When the system is RHEL, in the file /etc/sysconfig/network-scripts/ifcfg-ethX, define "ONBOOT=yes" and in the /etc/sysconfig/network file, define "NETWORKING_IPV6=yes".)
Also, make sure the secondary interface (physical interface) is in inactive state.
For Redundant Line Control Function, the path information must be initialized and the routing daemon must be restarted. If path information is statically specified, the static paths must be described in a configuration file for routing daemon.
When using an IPv6 address
Define the IPv6 address (takeover virtual IP address, monitored IP addresses to be specified in monitoring destination information) and a host name in /etc/hosts file.
For communication using IPv6, use the virtual IP address defined for GLS. When using the IPv6 address assigned by stateless address auto-configuration, it will be changed according to the change of the link-local address assigned for the active NIC around the time of NIC switching.
Before booting an OS, the primary interface (physical interface) you are going to apply must in active state and be sure IPv6 address is assigned. (When the system is RHEL, in the file /etc/sysconfig/network-scripts/ifcfg-ethX, define "ONBOOT=yes" and in the file /etc/sysconfig/network, set "NETWORKING_IPV6=yes")
Also, make sure the secondary interface (physical interface) is in inactive state.
Do not set the server running NIC switching mode as IPv6 router.
In order to set stateless address auto-configuration against the physical interface(ethX) that uses NIC switching mode, make sure to set IPv6 router on the network connecting the server. Moreover, for IPv6 address prefix and prefix length configured in Redundant Line Control function, specify the same value configured on the IPv6 router. The following is an example of setting a /etc/radvd.conf file when using a Linux server as an IPv6 router. In addition, depending on the version of radvd, kernel parameter(net.ipv6.conf.all.forwarding=1) must be defined on /etc/sysctl.conf file. For details on this, see the manual of radvd.conf(5) and radvd(8).
/etc/radvd.conf
interface eth0
{
AdvSendAdvert on; # Sending router advertisements
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
prefix fec0:1::0/64 # Sending Prefix fec0:1::0/64 from eth0
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
}; |
If you use "HWADDR=XX:XX:XX:XX:XX:XX" in the setting (the /etc/sysconfig/network-scripts/ifcfg-ethX file) for the physical interface of the GLS bundles, add the "HOTPLUG=no" setting.
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.
