C.4.3.2 Reserve takeover virtual interface for fast switching mode

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

Contents Index

Appendix C Changes from previous versions

> C.4 Changes from Redundant control function 4.1A30 to version 4.1A40

> C.4.3 Other incompatibles

C.4.3.2 Reserve takeover virtual interface for fast switching mode

[Contents]

If the virtual interface in fast switching is registered as a cluster takeover resource with the "hanethvrsc" command, it will use the logical ID No.65 or later like "shaX:65" and "shaX:66".

If the virtual interface in fast switching is specified for multiple zones, the logical ID will be the same as that for the takeover virtual interface. However, the logical virtual interfaces like "shaX:65" and "shaX:66" will be generated in advance when the redundant line control function is started then the cluster takeover virtual interface will automatically be reserved. So, the same logical ID will not be used for multiple zones, and the cluster takeover virtual interface can be used.

[Changes]

Before modification

When the virtual interface and takeover IP are set with the "hanethvrsc" command, the takeover virtual interfaces like shaX:65 and shaX:66 will not be reserved.

See the following output example of the "ifconfig" command after the virtual interface and takeover IP settings.

# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.100.10 netmask ffffff00 broadcast 192.168.100.255
        ether XX:XX:XX:XX:XX:XX
hme1: flags=1000863<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 192.168.101.10 netmask ffffff00 broadcast 192.168.101.255
        ether XX:XX:XX:XX:XX:XX
hme2: flags=1000863<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
        inet 192.168.102.10 netmask ffffff00 broadcast 192.168.102.255
        ether XX:XX:XX:XX:XX:XX
cip0: flags=10080c1<UP,RUNNING,NOARP,PRIVATE,IPv4> mtu 1500 index 6
        inet 192.168.1.1 netmask ffffff00
sha0: flags=1000863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,IPv4> mtu 1500 index 8
        inet 192.168.200.10 netmask ffffff00 broadcast 192.168.200.255
        ether XX:XX:XX:XX:XX:XX

After modification

When the virtual interface and takeover IP are set with the "hanethvrsc" command, the takeover virtual interfaces like shaX:65 and shaX:66 will automatically be reserved.

See the following output example of the "ifconfig" command after the virtual interface and takeover IP settings.

# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.100.10 netmask ffffff00 broadcast 192.168.100.255
        ether XX:XX:XX:XX:XX:XX
hme1: flags=1000863<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 192.168.101.10 netmask ffffff00 broadcast 192.168.101.255
        ether XX:XX:XX:XX:XX:XX
hme2: flags=1000863<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
        inet 192.168.102.10 netmask ffffff00 broadcast 192.168.102.255
        ether XX:XX:XX:XX:XX:XX
cip0: flags=10080c1<UP,RUNNING,NOARP,PRIVATE,IPv4> mtu 1500 index 6
        inet 192.168.1.1 netmask ffffff00
sha0: flags=1000863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,IPv4> mtu 1500 index 8
        inet 192.168.200.10 netmask ffffff00 broadcast 192.168.200.255
        ether XX:XX:XX:XX:XX:XX
sha0:65: flags=1000862<BROADCAST,NOTRAILERS,RUNNING,MULTICAST,IPv4> mtu 1500 index 8
        inet 0.0.0.0 netmask 0

The "ifconfig" command outputs the takeover virtual interface (sha0:65). The environment settings and operation of a cluster system are the same as before.

[Notes]

When a cluster takeover virtual interface is registered, it will be reserved regardless of availability of zones.
The generated takeover virtual interface is "down", and "0.0.0.0" is allocated to the IP address. The takeover IP address is allocated during RMS startup then the interface will be "up".

Contents Index