3.1.2.5 GS/SURE linkage mode

PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System)

Table 3.5 shows the information required to configure GS/SURE linkage mode.

Components					Value
Virtual interface information (1)		Virtual interface name			C-1
		Virtual IP address or host name			C-2
		Subnet mask			C-3
		Physical interface information (1)		Physical interface name	C-4
				IP address or host name	C-5
				Subnet mask	C-6
		Physical interface information (2)		Physical interface name	C-7
				IP address or host name	C-8
				Subnet mask	C-9
		(Repeat for the number of the physical interfaces)
(Repeat for the number of the virtual interfaces)
Remote node information (1)	Remote node name				C-10
	Virtual IP information (1)		Virtual IP address		C-11
			Remote host physical IP address information	IP address or host name (1)	C-12
				IP address or host name (2)	C-13
				(Repeat for the number of IP addresses)
			Monitoring on/off		C-14
			Send RIP from remote host on/off		C-15
			Network information of relaying host		C-16
	(Repeat for the number of virtual IP)
(Repeat for the number of remote nodes)

Description of each component is as follows:

<Virtual interface information>: Setup the followings for the number of virtual interfaces.

Virtual interface name (C-1): A virtual interface name is specified via "hanetconfig create" command with -n option, in "shaX" (where X is a natural number) format.

Virtual IP address or host name (C-2): 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.

Subnet mask (C-3): 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.

<Physical interface information>: Setup the followings for the number of physical interfaces for redundancy.

Physical interface name (C-4,7): Specify a name for the physical interface. Physical interface name is specified via "hanetconfig create" command with -t option.

Physical IP address or host name (C-5,8): 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.

Subnet mask (C-6,9): 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.

<Remote node information>: Configure the following for the number of host nodes.

Remote host name (C-10): 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.

<Virtual IP information>: Setup the followings for the number of virtual IP.

Virtual IP address or host name (C-11): 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.

Remote host physical IP address information (C-12,13): 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.

Monitoring on/off (C-14): 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.

Send RIP from remote host on/off (C-15): 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".

Network information of relaying host (C-16): 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.