Use the cluvfy comp dhcp component verification command to verify that the DHCP server exists on the network, and that it can provide a required number of IP addresses. The required number of IP addresses is calculated, as follows:
Regardless of the size of the cluster, there must be three scan VIPs
One node VIP for each node you specify with the -n option
One application VIP for each application VIP resource you specify with the -vipresname option
This verification also verifies the response time for the DHCP server.
cluvfy comp dhcp -clustername cluster_name [-vipresname application_vip_resource_name] [-port dhcp_port] [-n node_list] [-method {sudo -user user_name [-location directory_path] | root}] [-networks network_list] [-verbose]
Table A-9 cluvfy comp dhcp Command Parameters
| Parameter | Description |
|---|---|
-clustername cluster_name |
The name of the cluster of which you want to check the integrity of DHCP. |
-vipresname application_vip_resource_name |
A comma-delimited list of the names of the application VIP resource. |
-port dhcp_port |
The port to which DHCP packages are sent. The default port is 67. |
-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. |
-method {sudo -user user_name
[-location directory_path] | root} |
Specify whether the privilege delegation method is |
-networks network_list |
Specify a list of network classifications for the cluster separated by forward slashes ( In the preceding format, you must enclose |
-verbose |
CVU prints detailed output. |
You must run this command as root.
Do not run this check while the default network Oracle Clusterware resource, configured to use a DHCP-provided IP address, is online (because the VIPs get released and, since the cluster is online, DHCP has provided IP, so there is no need to double the load on the DHCP server).
Run this check on the local node. This is unlike other CVU commands, which run on all nodes specified in node list. As a result, even though the local node is not included in the node list you specify with the -n option, the error messages get reported to the local node.
Before running this command, ensure that the network resource is offline. Use the srvctl stop nodeapps command to bring the network resource offline, if necessary.
See Also:
Oracle Real Application Clusters Administration and Deployment Guide for more information about the srvctl stop nodeapps command