7.5 hanetobserv Command

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

Contents Index

Chapter 7 Command reference

7.5 hanetobserv Command

[Name]

hanetobserv - Setting, modifying, deleting, and displaying the information for the communication target monitoring function

[Synopsis]

/opt/FJSVhanet/usr/sbin/hanetobserv command [args]

[Feature description]

The hanetobserv command sets, modifies, deletes, and displays the monitoring destination information required for the operation in GS/SURE linkage mode.

Command	Process outline	Authority
create	Sets a monitoring destination	Super user
print	Displays monitoring destination information	General user
modify	Modifies monitoring destination information	Super user
delete	Deletes monitoring destination information	Super user

(1) create command

The operation in GS/SURE linkage mode requires the monitoring of the communication target. This enables the system to continue communication using other communication paths when a failure occurs. Use the create command to generate a communication target. The following is the command format for generating a monitoring destination:

GS communication (If adding ipaddress):
/opt/FJSVhanet/usr/sbin/hanetobserv create -n node -i ipaddress -t nicaddress1[,nicaddress2,...] -m {on | off} [-r {on | off}]

GS communication (If adding more nicaddress to an already defined ipaddress):
/opt/FJSVhanet/usr/sbin/hanetobserv create -n node -i ipaddress -t nicaddress3[,nicaddress4,...]

SURE communication (using SURE communication function):
/opt/FJSVhanet/usr/sbin/hanetobserv create -n node -i ipaddress -t nicaddress1:pm-id[,nicaddress2:pm-id,...] -m {on | off} [-r {on | off}]

SURE communication (using TCP relay function):
/opt/FJSVhanet/usr/sbin/hanetobserv create -i ipaddress -c clientaddress1[:subnetmask][,clientaddress2[:subnetmask],...]

-n node:

Specify a name by which to identify the node of a communication target, using up to 16 one-byte characters.

-i ipaddress:

Specify a host name or IP address of a virtual interface held by the communication target. This host name must correspond to an IP address in a network database such as the /etc/inet/hosts and /etc/inet/ipnodes files. You can directly specify an IP address instead of a host name. In this case, you must specify the IP address in dotted decimal notation.

-t nicaddress1[:pm-id][,nicaddress2[:pm-id],...]:

Specify the host names or IP addresses of physical interfaces bundled by a virtual interface, by listing them delimited with a comma (,).

nicaddressX:

Specify the host name or IP address of a physical interface bundled by a virtual interface.

pm-id:

Specify the identifier of the PM (processor module) group to which the physical interface of the communication target belongs when it is the SURE system. Specify a number from 1 to 8. This option is not required if the communication target is GS.

-m on | off:

Set whether or not to monitor the virtual interface of the monitoring destination that has been set.

Since the local host need not monitor the communication target if the remote host monitors it, specify a mode depending on the setting of the remote host.

In hot standby configuration (GS), specify this parameter only on one of the active and standby nodes when their monitoring destination information is defined.

on:

The local host monitors the communication target.

off:

The local host does not monitor the communication target.

-r on | off:

Sets if or not a RIP packet is sent from the other device. It is possible to omit this option. When omitted, RIP sending on (ON) is set. When GS has a hot standby configuration, define this parameter only in one node at setting the monitor-to information of an operation node or a standby node.
Notes)
Be sure to set RIP to "on" in order to decide which of an operation node or a standby node is working by RIP when the other system has a hot standby configuration.

on:

When sending a notification of node switching to the other system, it sends a notification of node switching waiting for receiving RIP from the other system.

off:

When sending a notification of node switching to the other system, it sends a notification of node switching to all routes without waiting for receiving RIP from the other system.

-c clientaddress1[:subnetmask][,clientaddress2[:subnetmask],...]:

Specify the communication parties and destination networks with which communication should be performed using the virtual interface of the relay destination, by listing them delimited with a comma (,).

clientaddressX:

Specify the host name or IP address of a remote host or network with which communication should be actually performed. This host name must correspond to an IP address in a network database such as the /etc/inet/hosts and /etc/inet/ipnodes files. You can directly specify an IP address instead of a host name. In this case, you must specify the IP address in dotted decimal notation. If a remote network is specified, a "subnetmask" must be specified.

subnetmask:

This option must be specified when a remote network is specified in "clientaddressX". Specify the subnet mask value of the network in dotted decimal notation.

(2) print command

Use the print command to display the current monitoring destination information. The following is the format of the print command. If no option is specified, information on both the monitoring destination and the relay destination is output.

/opt/FJSVhanet/usr/sbin/hanetobserv print [-o] [-c]

-o:

Specify this option to output information on only the monitoring destination.

-c:

Specify this option to output information on only the relay destination.

The following shows an example of displaying monitoring destination information:

Item		Explanation
Destination Host		Outputs the host name of the communication target.
Virtual Address		Outputs the virtual interface name.
POLL		Outputs the monitoring mode.
RIP		With or without an RIP packet sent from the other end device.
POLL	ON	The local host monitors the communication target.
	OFF	The local host does not monitor the communication target.
RIP	ON	With an RIP packet sent from the other host.
	OFF	Without an RIP packet sent from the other host.
NIC Address(:PMgroupID)		Outputs the IP address or host name of a physical interface bundled by a virtual interface. An ID value is shown in parentheses.

Item		Explanation
Virtual Address		Outputs the virtual interface name.
Client		Outputs the network type of the communication destination.
Client	host	Indicates that the host address of the communication destination is output in "Address".
	net	Indicates that the network address of the communication destination is output in "Address".
Address		Outputs address information of the communication destination.

(3) modify command

Use the modify command to modify the monitoring destination information generated using the create command. The following is the format of the modify command:

/opt/FJSVhanet/usr/sbin/hanetobserv modify -n node,new-node |
    -n node -i ipaddress,new-ipaddress |
    -n node -i ipaddress -t nicaddress,new-nicaddress1[:pm-id][,new-nicaddress2[:pm-id],...] |
    -n node -i ipaddress {-m {on | off} | -r {on | off}} |
    -i ipaddress -c clientaddress[:subnetmask],new-clientaddress[:subnetmask]

-n node,new-node:

Specify the node name of the monitoring destination information to be modified.

node:

Specify a node name that is set in the monitoring destination information (to be modified).

new-node:

Specify a node name to be used after modification.

If this parameter is specified, none of parameters "-i", "-t", and "-m" needs to be specified.

-i ipaddress,new-ipaddress:

Specify a host name or IP address of a virtual interface of the monitoring destination information to be modified. This parameter cannot be specified at the same time as when the node name or operation mode is modified.

ipaddress:

Specify a host name or IP address that is set in the monitoring destination information (to be modified).

new-ipaddress:

Specify a host name or IP address to be used after modification.

If this parameter is specified, none of new-node in parameter "-n" and parameters "-t" and "-m" needs to be specified.

-t nicaddress,new-nicaddress1[:pm-id][,new-nicaddress2[:pm-id],...]:

Specify the IP address or host name of physical interfaces bundled by a virtual interface of the monitoring information to be modified. This parameter cannot be specified at the same time as when the node name, host name or IP address of the virtual interface, or operation mode is modified.

nicaddress:

Specify the first IP addresses or host names in the IP address or host name list that bundles physical interface that are set in the monitoring destination information (to be modified). Check the first real interface names using the print command of hanetobserv.

If the monitoring target data displayed from executing "hanetobserv print" command contains "ipaddressC,ipaddressD" under "NIC Address(:PMgroupID)" section, in such a case, use the headmost entry or "ipaddressC".

new-nicaddress1[:pm-id][,new-nicaddress2[:pm-id],...]:

Specify all the IP address or host name of a physical interface to be bundled after modification, by listing them delimited with a comma (,).

If this parameter is specified, none of new-node in parameter "-n", new-ipaddress in parameter "-i", and parameter "-m" needs to be specified.

new-nicaddressX:

Specify the host name or IP address of interfaces to be bundled by a virtual interface.

pm-id:

-m on | off:

Specify the operation mode of the monitoring destination information to be modified.
This parameter cannot be simultaneously specified, when changing other parameters.

-r on | off:

Specify the existence of the RIP transmission from a remote system.
This parameter cannot be simultaneously specified, when changing other parameters.

-c clientaddress[:subnetmask],new-clientaddress[:subnetmask]:

Modify the host name or IP address of the party with which communication should be actually performed. If a subnet mask value is specified in the information to be modified, the subnet mask value must be specified for modification.

clientaddress[:subnetmask]:

Specify the client information to be modified. If a subnet mask value is specified in the information that has been defined, the subnet mask value must be specified.

new-clientaddress[:subnetmask]:

Specify the client information to be used after modification. To specify a network, the subnet mask value must be specified.

(4) delete command

The following is the format of the delete command used to delete the monitoring destination information created using the create command:

/opt/FJSVhanet/usr/sbin/hanetobserv delete -n all |
        -n node1[,node2,...] |
        -n node -i ipaddress1[,ipaddress2,...] |
        -n node -i ipaddress -t nicaddress1[:pm-id][,nicaddress2[:pm-id],...] |
        -c all |
        -i ipaddress -c all |
        [-i ipaddress] -c clientaddress1[:subnetmask][,clientaddress2[:subnetmask],...]

-n all:

If all is specified, all monitoring destination information is deleted.

-n node1[, node2, ...]:

Specify a remote node name or IP address that is set in the monitoring destination information and should be deleted. You can specify more than one remote node name or IP address by listing them delimited with a comma.

-n node -i ipaddress1[,ipaddress2,...]:

Delete the virtual interface information under the node information that is set in the monitoring destination information. Specify a node name or virtual IP address attached to the virtual interface under the remote node name to be deleted. You can specify more than one node name or IP address by listing them delimited with a comma. If only one virtual interface is defined under node, the node definition information is also deleted.

-n node -i ipaddress -t nicaddress1[:pm-id][,nicaddress2[:pm-id],...]:

This command deletes the list of IP addresses or host names of physical interface assigned under virtual interface. Specify the host name or IP address of the physical interface you wish to delete. It is possible to specify more than one name or IP addresses by separating them with comma.
In the case where a single list of hostname or IP address of the physical interface is defined, the virtual interface will be deleted as well. Furthermore, if only one virtual interface is defined under the node, the configuration data including the mutual interface will be deleted as well. The host name or IP address or the physical interface can be verified using hanetobserv print command.

-c all

Delete the definition that is set to use the TCP relay function.

-i ipaddress -c all

Delete all the information under the virtual interface information specified in the "-i" option.

[-i ipaddress] -c clientaddress1[:subnetmask][,clientaddress2[:subnetmask],...]

Delete all the real NIC information to be relayed. Specify the "-i" option to delete only the real NIC information under a specific virtual interface. You can specify more than one NIC by listing them delimited with a comma.

[Notes]

Configuration information must be defined before a monitoring destination is created.
This command can be set if a virtual interface in GS/SURE linkage mode (operation mode "c") is defined.
To add, delete, or change a monitoring destination, the virtual interface in GS/SURE linkage mode (operation mode "c") must be inactivated.
No monitoring destination registered in a cluster can be deleted or changed. First release the cluster definition and then delete or change the monitoring destination.
An IP address or host name to be specified when the communication target monitoring function is set or changed must be defined in /etc/inet/hosts and /etc/inet/ipnodes.
The node name information must not be specified as "all".
Up to 32 physical interfaces can be specified to be bundled by the virtual interface of the communication target to be specified in the monitoring destination information.
When specified a numeric string for a host name, it is dealt with as decimal and converted into an IP address corresponding to its value to work. (For instance, when specified "123456", it is regarded an IP address "0.1.226.64" is specified.)
When specified a host name to where to set a host name or an IP address with this command, it is not possible to change the corresponding host name on the host database of such as /etc/inet/hosts and /etc/inet/ipnodes files. To change the information of the host name, it is necessary to temporarily delete a definition of a Redundant Line Control function to use the corresponding host name and to set the definition again.
Do not use characters other than alphanumeric characters, period, and hyphen for the host name. If characters other than the above are used, re-write the host names in /etc/inet/hosts and /etc/inet/ipnodes so that it does not contain any other characters. Also, the first and last character for the host name must be alphanumeric character.

[Examples]

(1) create command

The following shows a setting example in which monitoring is performed while the communication target's node hahostA has virtual IP address "vip1", which bundles two physical IP address ipaddressC and ipaddressD. The host name is assumed to be associated with the IP address in the /etc/inet/hosts file.

# /opt/FJSVhanet/usr/sbin/hanetobserv create -n hahostA -i vip1 -t ipaddressC,ipaddressD -m on

The following shows a setting example in which monitoring is not required because the already defined communication target hahostA has virtual IP address "vip2", which bundles physical IP address ipaddressF and ipaddressG. The host name is assumed to be associated with the IP address in the /etc/inet/hosts file.

# /opt/FJSVhanet/usr/sbin/hanetobserv create -n hahostA -i vip2 -t ipaddressF,ipaddressG -m off

The already defined communication target hahostA has virtual IP address "vip2", which bundles two physical IP addresses ipaddressF and ipaddressG. The following shows a setting example in which new physical IP addresses ipaddressH and ipaddressJ are bundled and added to virtual IP address "vip2". The system takes over the monitoring mode used when physical IP addresses ipaddressF and ipaddressG are set. The host name is assumed to be associated with the IP address in the /etc/inet/hosts file.

# /opt/FJSVhanet/usr/sbin/hanetobserv create -n hahostA -i vip2 -t ipaddressH,ipaddressJ

Define the SURE interface to be used to communicate with the node of the communication target when the TCP relay function in GS/SURE linkage mode is used. The SURE virtual IP address "vip2" to be used is assumed to be already defined. The following shows a setting example in which a network (10.0.0.0) is added to the communication target. The host name is assumed to be associated with the IP address in the /etc/inet/hosts file.

# /opt/FJSVhanet/usr/sbin/hanetobserv create -i vip2 -c 10.0.0.0:255.0.0.0

(2) print command

The following shows an example of displaying the configuration information list of a virtual interface.

# /opt/FJSVhanet/usr/sbin/hanetobserv print

(3) modify command

The following shows an example of changing the node name (hahostB) in the communication target monitoring destination information to hahostH.

# /opt/FJSVhanet/usr/sbin/hanetobserv modify -n hahostB,hahostH

The following shows an example of changing the virtual IP address "vip1" of the node (hahostB) in the communication target monitoring destination information to "vip2".

# /opt/FJSVhanet/usr/sbin/hanetobserv modify -n hahostB -i vip1,vip2

The following shows an example of changing the physical IP addresses (ipaddress1 and ipaddress2) bundled by virtual IP address "vip1" of the node (hahostB) in the communication target monitoring destination information to ipaddress3, ipaddress4, and ipaddress5.

# /opt/FJSVhanet/usr/sbin/hanetobserv modify -n hahostB -i vip1 -t ipaddress1,ipaddress3,ipaddress4,ipaddress5

The following shows an example of changing the physical IP addresses (ipaddress6 and ipaddress7) bundled by virtual IP address "vip2" of the node (hahostB) in the communication target monitoring destination information to ipaddress7 and ipaddress8.

# /opt/FJSVhanet/usr/sbin/hanetobserv modify -n hahostB -i vip2 -t ipaddress6,ipaddress7,ipaddress8

The following shows an example of changing the "on" setting of the monitoring mode of the node (hahostB) in the communication target monitoring destination information to "off".

# /opt/FJSVhanet/usr/sbin/hanetobserv modify -n hahostB -m off

The following shows an example of changing the communication target (ipaddress6) in the relay destination information (ipaddress6 and ipaddress7) of the virtual IP address "vip2" in the communication target monitoring destination information to a network specification (10.0.0.0, 255.0.0.0).

# /opt/FJSVhanet/usr/sbin/hanetobserv modify -i vip2 -c 10.0.0.0:255.0.0.0,ipaddress7

(4) delete command

The following shows an example of deleting all the monitoring destination information.

# /opt/FJSVhanet/usr/sbin/hanetobserv delete -n all

The following shows an example of deleting all the information held by the monitored host (hahostA).

# /opt/FJSVhanet/usr/sbin/hanetobserv delete -n hahostA

The following shows an example of deleting the information under the virtual IP address "vip1" held by the monitored host (hahostA).

# /opt/FJSVhanet/usr/sbin/hanetobserv delete -n hahostA -i vip1

The following shows an example of deleting the information under the virtual IP address "vip1" held by the monitored host (hahostA).

# /opt/FJSVhanet/usr/sbin/hanetobserv delete -n hahostA -i vip1

The following shows an example of deleting the physical IP addresses (ipaddressC, ipaddressD) under the virtual IP address "vip1" in the TCP relay information.

# /opt/FJSVhanet/usr/sbin/hanetobserv delete -i vip1 -c ipaddressC,ipaddressD

Contents Index