Select appropriate contents for each mode.
When using Fast switching mode, determine the information required for configuration of the mode listed in the Table 3.2 Configuration information of Fast switching mode.
Components | ||
|---|---|---|
Virtual interface information (1) | Virtual interface name | |
Virtual IP address or host name | ||
Subnet mask | ||
Physical interface information (1) | Physical interface name | |
IP address or host name | ||
Subnet mask | ||
Physical interface information (2) | Physical interface name | |
IP address or host name | ||
Subnet mask | ||
(Repeat for the number of physical interfaces) | ||
(Repeat for the number of virtual interfaces) | ||
Description of each component is as follows:
Setup the followings for the number of virtual interfaces.
Specify a name for a virtual interface, which will be assigned to the physical interface used for redundancy. Specify shaX (X represents a number) of this component using "hanetconfig create" command with -n option.
Specify an IP address or host name to be assigned for the virtual interface. The network portion (IPv4) and a prefix (IPv6) of this IP address must be different from the IP address assigned for the physical interface. When using IPv4, use "hanetconfig create" command with -i option to specify the IP address to be allocated for the virtual interface. When using IPv6, configure these in /etc/inet/ndpd.conf file.
When using IPv4 address, specify the sub network mask value applied to the virtual IP address. If subnet is not used, this configuration can be omitted. This component is written in /etc/inet/netmasks file. However, this configuration is not necessary if using IPv6 address.
Setup the followings for the number of physical interfaces used for redundancy.
Specify a name for the physical interface. This component can be set using "hanetconfig create" command with -t option (e.g. hme1, qfe2 etc).
If using IPv4 address, specify an IP address or host name to be assigned for the physical interface. The network portion of this IP address must be different from IP address of other physical and virtual interface. Set up this component as follows:
[Solaris 10]
Create "/etc/hostname.physical interface name" file and then assign the IP address (or host name) in the file.
[Solaris 11]
Use the ipadm(1M) command.
Make sure this value is different from the other IP.
If using IPv4 address, specify a sub network mask value applied to the physical IP address. If subnet is not used for allocation, this configuration can be omitted. This configuration is written in /etc/inet/netmasks file. Note that, this configuration is not necessary if using IPv6 address.
Table 3.3 Configuration information of NIC switching mode shows the information required to configure NIC switching mode:
Components | ||
|---|---|---|
Virtual interface information (1) | Virtual interface name | |
Virtual IP address (or host name) | ||
Subnet mask | ||
Physical interface information (1) | Physical interface name | |
IP address or host name | ||
Physical interface information (2) | Physical interface name | |
Standby interface information | Virtual interface name | |
Automatic switching back mode | ||
Local MAC address configured in Standby interface | ||
Monitored remote system information | Primary Monitored remote system IP address or host name | |
Secondary Monitored remote system IP address or host name | ||
HUB-to-HUB monitoring | ||
(Repeat for the number of physical interfaces) | ||
Description of each component is as follows:
Setup the followings for the number of virtual interfaces.
Name a virtual interface to be configured on a physical interface used for GLS. Specify the name using "hanetconfig create" command with -n option, in "shaX" (where X is a natural number) format.
Specify an IP address or host name allocated to the virtual interface. The network portion (for IPv4) or prefix (for IPv6) of this IP address must be the same IP address assigned to the physical interface. This value is specified using "hanetconfig create" command with -i option.
When using IPv4 address, specify the value of a sub network mask used for the virtual IP address. This configuration can be omitted if not allocating a subnet. Set a subnet mask in /etc/inet/netmasks file. When using IPv6 address, it is not required to configure this value.
Setup the followings for the number of physical interfaces for redundancy.
Specify a name of the physical interface. This can be specified using "hanetconfig create" command with -t option. (e.g. hme1,qfe2)
Specify an IP address or host name assigned to the physical interface. This IP address must be different from the IP address of the other physical and virtual interfaces. Set up this component as follows:
[Solaris 10]
Create "/etc/hostname. <physical interface name>" file and then assign an IP address (or host name) in the file.
[Solaris 11]
Use the ipadm(1M) command.
When using Standby patrol function, setup the followings. Skip this process if Standby patrol function is not used.
Specify a name to a virtual interface for standby patrol function. Specify it using "hanetconfig create" command with -n option, in "shaX" (where X is a natural number) format.
Setting up the Standby patrol function enables the automatic switch back function when a transfer path recovers from a failure. Specify "q" to "hanetconfig create" command with -m option for using immediate switch-back after a transfer path recovery, or "p" for using standby interface capability.
If the standby patrol function is used, specify a local MAC address to be allocated to the standby interface. A local MAC address is specified in the form of: "02:XX:XX:XX:XX:XX" (where X represents a hexadecimal digit between 0 and F). The leading value "02" indicates the local MAC address, and the rest of the values can be arbitrary. However, please make sure that each MAC address should be unique within a single network. If the same MAC address is used within a network, the standby patrol may not run properly. A local MAC address is specified using "hanetconfig create" command with -a option.
Setup the following for the number of virtual interfaces. This configuration cannot be omitted.
Specify an IP address or host name of a HUB to be monitored while primary physical interface is being used. This IP address is assigned using "hanetpoll create" command with -p option.
Specify an IP address or host name of a HUB to be monitored while the secondary physical interface is being used. This IP address is specified using "hanetpoll create" command with -p option. This step can be omitted. In such case, the same value as primary remote end IP address or host name is applied.
Indicate whether the HUB-to-HUB monitoring function should monitor a transfer path between cascaded HUBs or not, when two HUBs are used:
on: monitor between HUBs,
off: do not monitor between HUBs.
The default value is "off". Specify the value using "hanetpoll create"command with -b option.
Table 3.4 Configuration information of GS/SURE linkage mode shows the information required to configure GS/SURE linkage mode.
Components | ||||
|---|---|---|---|---|
Virtual interface information (1) | Virtual interface name | |||
Virtual IP address or host name | ||||
Subnet mask | ||||
Physical interface information (1) | Physical interface name | |||
IP address or host name | ||||
Subnet mask | ||||
Physical interface information (2) | Physical interface name | |||
IP address or host name | ||||
Subnet mask | ||||
(Repeat for the number of the physical interfaces) | ||||
Virtual gateway information | Virtual gateway IP address | |||
(Repeat for the number of the virtual interfaces) | ||||
Remote node information (1) | Remote node name | |||
Virtual IP information (1) | Virtual IP address | |||
Remote host physical IP address information | IP address or host name (1) | |||
IP address or host name (2) | ||||
(Repeat for the number of IP addresses) | ||||
Monitoring on/off | ||||
Send RIP from remote host on/off | ||||
Network information of relaying host | ||||
(Repeat for the number of virtual IP) | ||||
(Repeat for the number of remote nodes) | ||||
Description of each component is as follows:
Setup the followings for the number of virtual interfaces.
A virtual interface name is specified via "hanetconfig create" command with -n option, in "shaX" (where X is a natural number) format.
Specify an IPv4 address or host name to be assigned to the virtual interface. The network portion of this IP address must be different from the IP address assigned to the physical interface. Virtual IP address or host name is specified via "hanetconfig create" command with -i option.
Specify a sub network mask value applied to the virtual IP address. This procedure can be omitted if not applying a subnet. Subnet mask is specified in /etc/inet/netmasks file. When applying subnet mask, apply the same mask value to the whole virtual and physical IP.
Setup the followings for the number of physical interfaces for redundancy.
Specify a name for the physical interface. Physical interface name is specified via "hanetconfig create" command with -t option.
Specify an IP address or host name to be assigned to the physical interface. The network portion of this IP address must be different from the IP address allocated to the other physical and virtual interfaces. The physical IP address (or host name) is specified via -i option while executing "hanetconfig create" command with -n option. Do not create "/etc/hostname.<physical interface name>" file.
Specify a sub network value applied to the physical IP address. This procedure can be omitted if not applying a subnet. Subnet mask is specified in /etc/inet/netmasks file. If using subnet mask, apply the same mask value to a whole virtual and physical IP.
Setup the following for the number of virtual interfaces.
Specify the IP address of the remote virtual gateway. The network (subnet) portion of the IP address should be the same as the IP address assigned to the virtual interface. This item is specified via "hanetgw create" command with -g option.
Configure the following for the number of host nodes.
Specify an arbitrary name (within 16 one-bit characters) to identify the node of remote host. Remote host name is specified via "hanetobserv create" command with -n option.
Setup the followings for the number of virtual IP.
Specify a virtual IP address or host name of the remote host. The virtual IP address or host name is specified via "hanetobserv create" command with -i option. Also, the host name and IP address must be defined in /etc/inet/hosts file.
Specify a physical IP address or host name in the virtual IP of the remote host. List these physical IP addresses separated by ',' (commas). Remote host physical IP address information is specified via "hanetobserv create" command with -t option. The IP address and the host name specified here must be defined in /etc/inet/hosts file as well.
Set whether or not to use monitoring function.
on: Turn on the monitoring function from the local host
off: Does not turn on the monitoring.
If monitoring is enabled from the remote host, monitoring the remote host can be omitted. Check the configuration of the remote host and decide whether or not to turn on the monitoring function.
If the remote host (GS) is setup as a hot standby server, then define this in either active node or standby node. This configuration can be specified via "hanetobserv create" command with -m option.
For this component, specify whether or not to send RIP packets from a remote host.
on: Awaits notification from the remote host and sends notification of the node whether the node has switched or not. After receiving RIP packets from the remote host, it sends out the notification.
off: Does not wait for notification from the remote host. It sends out a notification to every path.
Initially, this is set to "on". If the global server (GS) is setup as a hot standby server, then define this in either operation node or standby node while setting up Monitored remote system information. This configuration is specified using "hanetobserv create" command with -r option.
Caution) If the remote system is setup as a hot standby server, because RIP determines whether operational node or standby is functioning, the parameter should be set as "on".
Specify an IP address or host name of communicating remote network. This IP address and host name must be defined in /etc/inet/hosts file. This configuration is specified using "hanetobserv create" command with -c option.
Table 3.5 Configuration of redundancy mode shows description of parameters for each mode. These values apply to all modes and virtual interfaces on one server. You cannot change these values for each virtual interface or redundancy mode. This configuration is not necessary when using the default value.
Contents | Fast switching mode | NIC switching | GS/SURE | Default |
|---|---|---|---|---|
Transfer path monitoring interval | A | N | N | 5 sec |
The number of constant monitoring prior to outputting message | A | N | N | 0 time |
The number of constant monitoring prior to switching cluster | A | N | N | 5 sec |
Switching cluster immediately after starting | A | N | N | none |
Outputting message (monitoring the physical interface) | A | N | N | none |
Standby patrol monitoring period | N | A | N | 15 sec |
The number of constant standby monitoring prior to outputting message | N | A | N | 3 times |
Deactivating the standby interface | N | A | N | unplumb |
Monitoring period | N | A | A | 5 sec |
The number of monitoring | N | A | A | 5 times |
Recovery monitoring period | N | N | A | 5 sec |
Cluster switching | N | A | A | Yes |
Link up waiting period | N | A | A | 60 sec |
Link status monitoring function | N | A | N | Disabled |
[Meaning of the symbols] A: Available, N: Not available
The followings are description of each of the content.
Specify the transfer path monitoring interval in seconds. The range of the intervals that can be specified is from 0 to 300 sec. If "0" is specified, it will not monitor the transfer path. Initially, it is set to 5 seconds. The transfer path monitoring interval is set using "hanetparam" command with -w option. This feature is available for Fast switching mode.
Specify the number of times for monitoring before outputting the message (No: 800 or 801) if the message needs to be output as a transfer path failure is detected. The effective range of the numbers which can be specified is from 0 to 100. If "0" is specified, it will not output a message. Initially it is set to 0 (does not output any message). using "hanetparam" command of -m option. Note that this feature is only available for Fast switching mode.
Specify whether or not to switch over the cluster if a failure occurs on a whole transfer path of the virtual interface. The effective range of the numbers is from 0 to 100. it will not switch the cluster. When configuring to switch the cluster, set how many times it repeatedly monitors. The range is from 1 to 100. Initially, it is set to 5, meaning that a cluster failover is triggered after continuously detecting the same failure 5 times. This feature is specified using "hanetparam" command with -i option. This feature is available only for Fast switching.
Specify whether or not to switch the cluster immediately after the cluster starts up. Configure this if a failure occurs in entire transfer path of the virtual interface before the system starts up. The values which can be specified are either "on" or "off". If "on" is selected, cluster is switched immediately after the userApplication starts up. On the other hand, if "off" is selected, the cluster is not switched even after the userApplication starts up. As an initial value, it is set to "off". This setting is specified using "hanetparam" command with -c option. This is available for Fast switching.
Configure whether or not to output a message when the status of the physical interface changes (detecting a failure in transfer path or transfer path recover) in the virtual interface. The values which can be specified are either "on" or "off". If "on" is selected, a message (message number: 990, 991, 992) is output. If "off" is selected, a message is not output. Initially, it is set to "off". This setting is specified via "hanetparam" command with -s option. This is available for Fast switching.
Specify the monitoring interval (in seconds) of operational NIC for standby patrol function. The values which can be specified are from 0 to 100. If "0" is specified, it will not run monitoring. Note if the user command function (using user command when standby patrol fails or detects recovery) is enabled, do not set the parameter to "0". If the parameter is set to "0", the user command function will not work. Initially, the parameter is set to 15 (seconds). This setting is specified via "hanetparam" command with -p option. This configuration is available for NIC switching mode with standby patrol function is enabled.
When a failure is detected in a transfer path using the standby patrol function, a message will be output to inform the failure. In this section, specify how many times to monitor until the message (message number: 875) is output. The values which can be specified are from 0 to 100. If "0" is selected, it stops outputting a message and disables monitoring using the standby patrol function. Note if the user command function (using user command when standby patrol fails or detects recovery) is enabled, do not set the parameter to "0". If the parameter is set to "0", the user command function will not work. Initially, the parameter is set to 3 (times). This configuration is specified via "hanetparam" command with -o option. This is available in NIC switching mode, which uses the standby patrol function. Using this option, the number of monitoring times doubles immediately after the standby patrol starts.
Specify how the standby interface is deactivated. The values which can be specified are either "plumb" or "unplumb". If "plumb" parameter is specified, the standby interface is deactivated and sets "0.0.0.0" for the IP address. With this parameter, it is possible to use "INTERSTAGE Traffic Director" as a high-level application. On the other hand, selecting "unplumb" deactivates the standby interface and then it sets to unused status. Initially, the parameter is set to "unplumb".
Specify "plumb" for the following situations:
When configuring high-reliable networks of non-global zones in the shared-ip configuration with the NIC switching mode
When configuring high-reliable LinkAggregation which the LACP mode is active with the NIC switching mode
This configuration is specified by "hanetparam" command with -d option. This is available exclusively for NIC switching mode.
Specify the monitoring period in seconds. The values which can be specified are from 1 to 300. The default value is 5 (seconds). This configuration is specified by "hanetpoll on" command with -s option. This feature is available for NIC switching and GS/SURE linkage mode.
Specify the number of monitoring times. The values which can be specified are from 1 to 300. The default value is 5 (times). This configuration is specified using "hanetpoll on" command with -c option. This feature is available for NIC switching and GS/SURE mode.
Specify the monitoring period when a failure is detected by monitoring the remote host by GS/SURE linkage mode. The values which can be specified are from 0 to 300. The default value is 5 (seconds). This configuration is assigned via "hanetpoll on" command with -b option. This feature is available for GS/SURE linkage mode.
Specify whether or not to switch the node when a failure occurs to every transfer paths.
yes: Switch nodes when a failure occurs to a whole transfer paths.
no: Does not switch nodes when a failure occurs to a whole transfer path.
The default parameter is "yes". This configuration is specified by "hanetpoll on" command with -f. This feature is available for NIC switching and GS/SURE linkage mode operating as a cluster.
In NIC switching mode, specify the time period (in seconds) until the HUB links up after monitoring starts. The values which can be specified are from 1 to 300. If this option is not specified, then the default value is used. Initial value is set to 60 (seconds). If the value is less than the product of monitoring period and monitoring times ("monitoring period" multiplied by "monitoring times"), then the value is ignored and ends up using the value of the product of monitoring period and monitoring times. This configuration is specified by "hanetpoll on" command with -p option. This feature is available for NIC switching and GS/SURE linkage mode.
Specify whether to monitor the link state of the NICs in the virtual interface bundles. The link state is monitored at intervals set by using the -s option of the hanetpoll on command, and GLS immediately performs NIC switching when NIC link down is detected. Also, to switch NICs by detecting an error by the transfer path monitoring, check the link status of the NIC which is the destination of switching beforehand. If NIC is in link down state and the state continues for over 5 seconds (when the standby patrol is set: over 2.5 seconds), switching will be restricted. Specify this monitoring with the -l option of the hanetpoll on command. This function is enabled in NIC switching mode.
The following describes the upper limit of configuration in each mode.
Upper limit of redundant line control methods
The following table lists the upper limit of configuration items set in the redundant line control methods.
Configuration item | Upper limit |
|---|---|
Total number of virtual interfaces and logical virtual interfaces | 64 |
See
For information on how to set the upper limit, refer to "7.1 hanetconfig Command".
Upper limit of GS/SURE linkage mode
The following table lists the upper limit of configuration items set for communication host monitoring for GS/SURE linkage mode.
Configuration item | Upper limit |
|---|---|
Maximum number of virtual IP addresses (Note 1) | 64 |
Maximum number of physical IP addresses | 128 |
Maximum number of nodes in which a single virtual IP address can be transferred | 4 |
Maximum number of relay destination IP addresses for TCP relay function | 256 |
Note 1)
In the environment where GLS is used in a cluster configuration, you need to configure the following virtual IP addresses as monitoring targets:
Virtual IP address of communication target
Virtual IP address of GLS on the cluster standby node
See
For information on how to set the upper limit, refer to "7.5 hanetobserv Command".
