| PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System) |
|
Contents
Index
|
| Appendix B Examples of configuring system environments | > B.8 Example of configuring NIC switching mode (IPv4/IPv6) |
This section describes an example configuration procedure of the network shown in the diagram below.
The xx, yy and zz in the figure below are assigned automatically by the automatic address configuration.
For configuring the cluster system, refer to the Cluster system manual.
In this section, description of private LAN is omitted.
The dotted line indicates that the interface is inactive.
If the Standby patrol monitoring function is not used, omit 6) and 9) in the procedure for setting up on each host.
When using IPv6 address as a takeover virtual interface, it may take around 30 seconds to recover the communication after switching the node. In order to hold a communication instantly, start IPv6 routing daemon beforehand on both operating and standby nodes. For details on this issue, refer to "D.2 Trouble shooting".
An example of configuring /etc/inet/ndpd.conf to use Solaris server as an IPv6 router is described below:
For details on /etc/inet/ndpd.conf, refer to the Solaris manual.
ifdefault AdvSendAdvertisements true # Every interface sends a router advertisement. prefix fec0:1::0/64 hme0 # hme0 sends Prefix "fec0:1::0/64". |
1-1) Define IP addresses and hostnames in /etc/inet/hosts file.
192.168.70.1 hosta # HOST-A/B/C Takeover virtual IP 192.168.70.2 host11 # HOST-A Physical IP 192.168.70.3 host21 # HOST-B Physical IP 192.168.70.4 host31 # HOST-C Physical IP 192.168.70.100 swhub1 # Primary HUB IP 192.168.70.101 swhub2 # Secondary HUB IP |
1-2) Write the hostnames defined above in /etc/hostname."interface-name" files. If a file does not exist, create a new file.
- Contents of /etc/hostname.hme0
|
host11 |
1-3) Define the subnet mask in /etc/inet/netmasks file.
192.168.70.0 255.255.255.0 |
1-4) Create /etc/hostname6.hme0 file as an empty file.
1-5) Define IP addresses and hostnames in /etc/inet/ipnodes file.
fec0:1::1 v6hosta1 # HOST-A/B/C Takeover virtual IP |
Run the following command to reboot the system. Make sure hme0 are enabled as IPv4/IPv6 interfaces after rebooting the system.
/usr/sbin/shutdown -y -i6 -g0
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m d -i 192.168.70.1 -e 192.168.70.2 -t hme0,hme1
Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/hostname.hme0.
/opt/FJSVhanet/usr/sbin/hanetconfig create inet6 -n sha0 -m d -i fec0:1::1/64 -t hme0,hme1
/opt/FJSVhanet/usr/sbin/hanetpoll create -n sha0 -p 192.168.70.100,192.168.70.101 -b off
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -a 02:00:00:00:00:00 -t sha0
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0
/opt/FJSVhanet/usr/sbin/hanetpoll on
/opt/FJSVhanet/usr/sbin/strptl -n sha1
1-1) Define IP addresses and hostnames in /etc/inet/hosts file. Defined information is the same as for HOST-A.
1-2) Write the hostnames defined above in /etc/hostname."interface-name" files. If a file does not exist, create a new file.
- Contents of /etc/hostname.hme0
|
host21 |
1-3) Define the subnet mask in /etc/inet/netmasks file. Defined content is same as HOST-A.
1-4) Create /etc/hostname6.hme0 file as an empty file.
1-5) Define IP addresses and hostnames in /etc/inet/ipnodes file. Defined content is same as HOST-A.
Run the following command to reboot the system. Make sure hme0 are enabled as IPv4/IPv6 interfaces after rebooting the system.
/usr/sbin/shutdown -y -i6 -g0
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m d -i 192.168.70.1 -e 192.168.70.3 -t hme0,hme1
Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/hostname.hme0.
/opt/FJSVhanet/usr/sbin/hanetconfig create inet6 -n sha0 -m d -i fec0:1::1/64 -t hme0,hme1
/opt/FJSVhanet/usr/sbin/hanetpoll create -n sha0 -p 192.168.70.100,192.168.70.101 -b off
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -a 02:00:00:00:00:01 -t sha0
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0
/opt/FJSVhanet/usr/sbin/hanetpoll on
/opt/FJSVhanet/usr/sbin/strptl -n sha1
1-1) Define IP addresses and hostnames in /etc/inet/hosts file. Defined information is the same as for HOST-A.
1-2) Write the hostnames defined above in /etc/hostname."interface-name" files. If a file does not exist, create a new file.
- Contents of /etc/hostname.hme0
|
host31 |
1-3) Define the subnet mask in /etc/inet/netmasks file. Defined content is same as HOST-A.
1-4) Create /etc/hostname6.hme0 file as an empty file.
1-5) Define IP addresses and hostnames in /etc/inet/ipnodes file. Defined content is same as HOST-A.
Run the following command to reboot the system. Make sure hme0 are enabled as IPv4/IPv6 interfaces after rebooting the system.
/usr/sbin/shutdown -y -i6 -g0
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m d -i 192.168.70.1 -e 192.168.70.4 -t hme0,hme1
Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/hostname.hme0.
/opt/FJSVhanet/usr/sbin/hanetconfig create inet6 -n sha0 -m d -i fec0:1::1/64 -t hme0,hme1
/opt/FJSVhanet/usr/sbin/hanetpoll create -n sha0 -p 192.168.70.100,192.168.70.101 -b off
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -a 02:00:00:00:00:02 -t sha0
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0
/opt/FJSVhanet/usr/sbin/hanetpoll on
/opt/FJSVhanet/usr/sbin/strptl -n sha1
After completing step 9) of both HOST-B and HOST-C, connect to the administration server using Cluster Admin View, then setup the cluster environment.
To create Gls resources, select the SysNode compliant with HOST-A, HOST-B, and HOST-C. Once Gls is created, register the two Gls resources on the userApplication.
When registering on the userApplication, select the SysNode compliant with HOST-A, HOST-B, and HOST-C in the order of operation node followed by standby node. Then, register the takeover address "192.168.70.1 - fec0:1::1".
After completing the configuration, start the userApplication to activate the takeover virtual interface on the operation node.
|
Contents
Index
|