Top
PRIMECLUSTER Global Link Services Configuration and AdministrationGuide 4.3Redundant Line Control Function
Chapter 3 Environment configuration > 3.2 System Setup > 3.2.2 Network configuration
PreviousNext

3.2.2 Network configuration

3.2.2.1 Setup common to modes

(1) Verification of the physical interface

Verify if the physical interface is inserted into the system using prtconf (1M) command.

# prtconf -D | grep "name of the physical interface"

For example, to use qfe, execute the command as below:

# prtconf -D | grep qfe
                SUNW,qfe, instance #0 (driver name: qfe)
                SUNW,qfe, instance #1 (driver name: qfe)
                SUNW,qfe, instance #2 (driver name: qfe)
                SUNW,qfe, instance #3 (driver name: qfe)

In the above example, it is possible to use qfe0, qfe1, qfe2, and qfe3. For details regarding prtconf (1M) command, refer to the Solaris manual.

If the system has no NIC installed, install a NIC. After adding a new NIC on the system, run "boot -r" command at the ok prompt, and then verify the physical interface as above.

Information

When using Tagged VLAN, ensure that the NIC supports tagged VLAN functionality (IEEE802.1Q). Refer to the documents of individual ethernet driver for configuring tagged VLAN interface. In addition, in a Redundant Line Control function, the effective range of VLAN-ID which can be specified is from 1 to 4094.

(2) Checking the name service

When using name services such as DNS or NIS, define keywords such as hosts, netmasks, and ipnodes 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.files:
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# does not use any naming service.
#
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.

passwd:     files
group:      files
hosts:      files dns
ipnodes:    files
networks:   files
protocols:  files
rpc:        files
ethers:     files
netmasks:   files
bootparams: files

Note

Even when using only IPv4 address in Redundant Line Control function, please define a host name as both /etc/inet/hosts file and /etc/inet/ipnodes file.

(3) Checking the network configuration files of the OS

When setting IP addresses using the network configuration files of the OS (/etc/hostname.interface file or /etc/hostname6.interface file), it is recommended to set up as follows for hardware failure such as NIC or SB (System Board).

Fast switching mode

[Solaris 10]
Create either or both of the following files as the network configuration files for both physical interfaces for redundancy:

  • /etc/hostname.interface

  • /etc/hostname6.interface

[Solaris 11]
Set both physical interfaces for redundancy by using the ipadm(1M) command.

NIC switching mode

[Solaris 10]
Create either or both of the following files as the network configuration files for either of the physical interfaces for redundancy:

  • /etc/hostname.interface

  • /etc/hostname6.interface

[Solaris 11]
Set either of the physical interfaces for redundancy by using the ipadm(1M) command.

GS/SURE linkage mode

It is not necessary to create any network configuration files of physical interfaces for redundancy.

Note

Services related to the network including Redundant Line Control function will not start if all IP addresses set by hostname.interface or the ipadm command cannot be allocated due to a hardware failure on system startup.

To activate Redundant Line Control function even in the case of a hardware failure, set interfaces as shown in the following figure:

  • For Solaris 10

    Create the hostname.interface file.

  • For Solaris 11

    Set IP addresses by the ipadm command.

For NIC switching mode, it is recommended to create the network configuration files so that at least one physical interface is to be activated on system startup as shown in the following figure:

Figure 3.2 Setup example of the OS setting file in the NIC switching mode (For Solaris 10)

Figure 3.3 Setup example of the OS setting file in the NIC switching mode (For Solaris 11)

When system boards are multiplexed or NICs with multiple ports are used, activation of the network service (svc:/network/physical) may fail because IP addresses cannot be assigned by rebooting the system while a failure occurs in the system board or the NIC. In this case, services related to the network including the service Redundant Line Control function (svc:/network/physical) will not start.

Therefore, if the a system board is multiplexed, it is recommended to set one or more physical interfaces to be activated on each system board so that at least one physical interface is to be activated on system startup as shown in the following figure.

For Solaris 10, set interfaces by creating the network configuration files.

For Solaris 11, set interfaces by using the ipadm command.

If you cannot follow the procedures above due to reasons such as the small number of equipped NICs, check that the physical interface to be activated for the network configuration file has no failure before rebooting the system.

Figure 3.4 Setup example of the OS setting file in the environment with redundant system boards (For Solaris 10)

Figure 3.5 Setup example of the OS setting file in the environment with redundant system boards (For Solaris 11)

In the NIC switching mode (physical IP takeover II), it is necessary to avoid IP duplication between nodes in the cluster. For Solaris 10, create an empty network configuration file to avoid IP addresses being set. When network configuration files are required, create network configuration files so that at least one physical interface other than the physical interface for redundancy is to be activated on system startup.

3.2.2.2 System setup in Fast switching mode

3.2.2.3 System setup in NIC switching mode

When using IPv4 address:

When using IPv6 address:

3.2.2.4 System setup in GS/SURE linkage mode

PreviousNext
Copyright FUJITSU LIMITED 2012-2017