cluvfy comp gns

Use the cluvfy comp gns component verification command to verify the integrity of the Grid Naming Service (GNS) on the cluster.

Syntax

cluvfy comp gns -precrsinst {-vip gns_vip [-___domain gns_domain] | -clientdata file_name}
  [-networks network_list] [-n node_list] [-verbose]

cluvfy comp gns -postcrsinst [-verbose]

Parameters

Table A-11 cluvfy comp gns Command Parameters

Parameter	Description
-precrsinst	Perform checks on GNS ___domain name and VIP address before Oracle Clusterware is installed.
-vip gns_vip	Specify the GNS virtual IP address. When you specify `-vip` and `-___domain` together, CVU validates that this cluster can become a GNS server (local GNS).
-___domain gns_domain	Optionally, you can specify the GNS sub ___domain name.
-clientdata file_name	Specify the name of the file that contains the GNS credentials. CVU validates that this cluster can use the specified client data to become a client GNS cluster of another GNS server cluster (shared GNS).
-networks network_list	Specify a list of network classifications for the cluster, including public networks for GNS, separated by forward slashes (`/`) that you want CVU to check, where each network is in the form of `"if_name"[:subnet_id[:if_type[,if_type...]]]`. In the preceding format, you must enclose `if_name` in double quotation marks, and you can use regular expressions, such as "`.`", as in `"eth"`, to match interfaces like `eth1` and `eth02`. The `subnet_id` is the subnet number of the network interface. The `if_type` is a comma-separated list of interface types: `{CLUSTER_INTERCONNECT \| PUBLIC \| ASM}`.
-n node_list	The comma-delimited list of nondomain qualified node names on which to conduct the verification. If you do not specify this option, then CVU checks only the local node.
-postcrsinst	Check the integrity of GNS on all nodes in the cluster
-verbose	CVU prints detailed output.